My elasticsearch cluster recently has a high response time.
Elasticsearch cluster (version 1.1.1 + number of node : 8)
Java client (client.transport.sniff is true)
After checking, I found that all java clients have the exception
it only happens to the connection to the same node(the problem node).
Master node and other nodes are fine. The cluster doing fine after removing
the problem node.
I've enabled the DEBUG level in the logging.yml and checked all the log in
master and nodes. there is no exception and hints for the timeout.
Any other options to trace this error?
The nodes in the cluster can see each others. There should be no problem
for the zen discovery.
I also try to use telnet in the client machine to connect the problem node.
It is working.
in the problem node,
we found the log of dmesg : possible syn flooding on port 9300. sending
Fixing the net.ipv4.tcp_max_syn_backlog does not help.
Reboot the machine and re-install the elasticsearch do not help.
I try to use the problem node to host a cluster by itself and use the same
java client to connect it. It is working fine.
There is not exception and stack trace in both server side and client side
when client side has the exception :
Not sure is it related to network issue / machine issue / elasticsearch
issue. What can I do to know more about this timeout exception?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1a211bd9-9d8f-46a1-a311-384912ed8da8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.