It expected to nodes move huge volumes of data but what I was wondering why the objects are not being garbage collected. Also, there are 242 TransportSearchQueryThenFetchAction$AsyncAction; I don't think that kind of concurrency is not expected. I couldn't yet find from the code which object is holding those objects.
The timeouts that you are referring to, are these between client node and data nodes or client node and consumer? Is there any thing the consumer need to do to release objects.
Thanks for your time,
-VM
On Jul 2, 2014, at 7:08 AM, joergprante@gmail.com wrote:
I'm not sure but it looks like a node tries to move some GB of document hits around. This might have triggered timeouts at other places (probably with node disconnects) and maybe the GB chunk is not yet GC collected, so you see this in your heap analyzer tool.
It depends on the search results and search hits you generated if the heaviness of the search result is expected or not, so it would be useful to know more about your queries.
Jörg
On Wed, Jul 2, 2014 at 3:29 AM, Venkat Morampudi venkatmorampudi@gmail.com wrote:
Thanks for reply Jörg. I don't have any logs. I will try to enable them it would but it would take some time though. If there anything in particular that we need to enable, please let me know.
-VM
On Tuesday, July 1, 2014 12:58:21 PM UTC-7, Jörg Prante wrote:
Do you have anything in your logs, i.e. many disconnects/reconnects?
Jörg
On Tue, Jul 1, 2014 at 7:59 PM, Venkat Morampudi venkatm...@gmail.com wrote:
In the Elasticsearch deployment we are seeing random client node crashed due to out of memory exception. I got the memory dump from one of the crash and analysed using Eclipse memory analyzer. I have attached leak suspect report. Apparently 242 objects of type org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction are holding almost 8gb of memory. I have spent some time on source code but couldn't find anything obvious.
I would really appreciate any help with this issue.
-VM
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/37881ead-70c2-40d8-89b6-a771b2a36bdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9930fcfd-d2d4-4f62-b8a0-8f1f989069f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/EH76o1CIeQQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE_Xum%2BU%3D-M-X_R93qbDdOKx-QFS2PFCbxcik-uqtpBbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7E54C4B5-AE5A-4E64-8199-B923E8337676%40gmail.com.
For more options, visit https://groups.google.com/d/optout.