that after every request the transport client is closed. But
>> since
>> it lives on a webserver with lots of search requests coming in, we would
>> ideally like it to stay open because it takes 3-4 seconds for a transport
>> client to initialize and we are going
re.
>
> Also since we are having one central server to handle all search and index
> requests, can the TransportClient handle multiple simultaneous requests
> from
> different users at the same time? We just want to make sure that we are
> doing this correctly.
>
>
>
uests, can the TransportClient handle multiple simultaneous requests from
different users at the same time? We just want to make sure that we are
doing this correctly.
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/TransportClient-timeout-webserver-configuration
Check the DNS of the ES servers. Netty initializes DNS services to get the
publish address, which is used for setting the bound address, and this
network call seems to take a long time (>30secs) so the bound address is
null for a while.
If your DNS or network is misconfigured, a DNS call will stal
Thomas,
We can connect and do queries and index processes just fine. The problem we
are experiencing is that after a long time of idle (15 minutes or so) doing
nothing, when we go to perform another operation this occurs.
On Monday, March 10, 2014 8:46:53 AM UTC-5, Thomas wrote:
>
> As per the
As per the documentation Client is threadsafe and is suggested by the
elasticsearch team to use the same client instance across your app.
Considering your exception above you might need to look your configuration
first (like cluster name and host/port) and you should use port 9300 for
the Java
Hello,
I'm developing a tomcat webserver application that uses ElasticSearch 1.0
(Java API). There is a client facing desktop application that communicates
with the server so all the code for ElasticSearch is on that one instance
and it is used by all our clients. With that being said I am runn
