Can you try and explain the problem again? How you run your tests, how many
concurrent clients, what are you running.
On Wed, Mar 28, 2012 at 11:18 AM, Ihor Hnedysh igorgnedish@gmail.comwrote:
Are the search request concurrent? If so, how many concurrent search
requests are you sending?
Yes. Requests are sent in parallel. Portionally. By five requests per
portion. Total 25 requests.Are you opening a new socket on each request? The OS can stall opening
new
sockets if you do that excessively over time.
I'm not sure about your question since we're not using sockets directly. I
will recheck it. But as far as I understand problem is that response did
not
came from Elasticsearch in the same time while it received it. I believe
in
it because request that was previously hanging is aborted right after
Elasticsearch instance stopped. Also, frequency of problem reproducibility
has been decreased after we have added additional data node.How the machine stats on the two nodes? CPU, load?
No CPU load. ProcessExplorer shows some cycles performed by Elasticsearch.How much memory do you ahve allocated on the machine, how many
CPUs/cores?
How much memory Have you allocated to ES?
I have standard JVM settings set. I did not tune them. PC is the following:
RAM: 6GB
CPU: 4 cores 3.2 GHz
I have win7 on board but we have current problem reproduced not only on
windows machine but on Ubuntu as well.--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/ES-hangs-up-when-sending-too-much-index-requests-tp3857628p3863994.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.