I am running a 4 node cluster running in EC2 and for the past few days, I have noticed that some nodes occasionally timeout on a request resulting in the following:
ConnectionError(HTTPConnectionPool(host='HOST', port=9200): Read timed out. (read timeout=10)) caused by: ReadTimeoutError(HTTPConnectionPool(host='HOST', port=9200): Read timed out. (read timeout=10)) >From the error, I figured it was something to do with my application keeping the elasticsearch instance open to long, so I decided to spawn it fresh every time a request was made. Still, this issue appear to pop up without much explanation. I figure it could be due to the nodes communicating, so I checked my log and saw the following: [2014-07-08 16:19:29,965][DEBUG][action.index ] [Node Name] observer: timeout notification from cluster service. timeout setting [1m], time since start [1m] I see this in all of my log files, but googling around doesn't seem to lead me to a direct cause. I would guess whatever is causing the above log entry is either corresponding to the timeouts I see or is the reason they are occurring. Any ideas? -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3229d028-01b1-4015-b9ae-b7e2d86faf11%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
