# Elasticsearch died with threaddump
**URL:** https://discuss.elastic.co/t/elasticsearch-died-with-threaddump/14390
**Category:** Elasticsearch
**Created:** [November 13, 2013, 7:08pm UTC](https://discuss.elastic.co/t/elasticsearch-died-with-threaddump/14390 "2013-11-13T19:08:12Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jae](https://discuss.elastic.co/u/Jae)
#### Post date: [November 13, 2013, 7:08pm UTC](https://discuss.elastic.co/t/elasticsearch-died-with-threaddump/14390/1 "2013-11-13T19:08:12Z")
Hi
Could somebody investigate threaddump? I think that elasticsearch itself is
not a problem but I don't understand why it's being killed. FYI, I upgraded
a certain river library, only changes are related with the shutdown part,
not initialization part. The symptom is, when I created \_river index to
start indexing, instances are being killed with the attached threadump.
Thank you
Best, Jae
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:07am UTC](https://discuss.elastic.co/t/elasticsearch-died-with-threaddump/14390/2 "2017-07-06T02:07:26Z")