Hi Ed,

I my case I have created a singleton TransportClient and querying ES with 
the same in frequent interval to get data. I'm not doing any bulk 
operations only searching index. threadPool needs to be shutdown once 
Tomcat stops I guess, But when my webapplication is up and running is there 
any need to shutdown the threadPool ? I'm getting this error recently. 
Previously if the ES server goes down I used to get 
NoNodeAvailableException and that's OK with me. But now the whole tomcat 
goes down and no app is working showing OutOfMemoryError. Please suggest.

-- 
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 protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/00bad24d-b036-4613-b3f3-7a2802778d24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to