# Cluster gets stuck after full re-index **URL:** \ **Category:** Elasticsearch\ **Created:** [June 3, 2014, 10:14am UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882 "2014-06-03T10:14:15Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Florian\_Munz\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/florian_munz_2/32/1506_2.png) [@Florian\_Munz\_2](https://discuss.elastic.co/u/Florian_Munz_2)\ **Post date:** [June 3, 2014, 10:14am UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/1 "2014-06-03T10:14:15Z")
Hello, we recently moved our ES cluster from dedicated hardware to AWS instances, they have less memory available, but use SSDs for the ES data directory. We kept JVM (1.7.0\_17) and ES (0.90.9) version exactly the same. On the new hardware, after running a full re-index (creating a new index, pointing an alias to the new and one alias to the old index, sending realtime updates to both aliases and running a script to fill up the new index) our cluster gets stuck. 10 minutes after the re-index finishes and we move both aliases to the new index, ES stops answering any search or index queries, no errors in the logs apart from it not answering queries anymore: org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution (queue capacity 1000) on org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$4@172018e5 CPU load is low, it doesn't look like it's doing anything expensive. A request to hot\_threads times out. I've put the output from jstack and jmap here: > We tried upgrading to 0.90.13, since the changelog mentioned a problem with infinite loops, but same behavior. We're planning to upgrade to a more recent version of ES soon, but it'll take a bit to fully test that. Any ideas what could be causing this? thanks, Florian -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 3, 2014, 10:20am UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/2 "2014-06-03T10:20:57Z")
How does your heap look during all this? Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 3 June 2014 20:14, Florian Munz [surf@theflow.de](mailto:surf@theflow.de) wrote: > Hello, > > we recently moved our ES cluster from dedicated hardware to AWS instances, > they have less memory available, but use SSDs for the ES data directory. We > kept JVM (1.7.0\_17) and ES (0.90.9) version exactly the same. On the new > hardware, after running a full re-index (creating a new index, pointing an > alias to the new and one alias to the old index, sending realtime updates > to both aliases and running a script to fill up the new index) our cluster > gets stuck. > > 10 minutes after the re-index finishes and we move both aliases to the new > index, ES stops answering any search or index queries, no errors in the > logs apart from it not answering queries anymore: > > org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: > rejected execution (queue capacity 1000) on > org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$4@172018e5 > > CPU load is low, it doesn't look like it's doing anything expensive. A > request to hot\_threads times out. I've put the output from jstack and jmap > here: > > [ES cluster stuck · GitHub](https://gist.github.com/theflow/b983d512ea344545f7f6) > > We tried upgrading to 0.90.13, since the changelog mentioned a problem > with infinite loops, but same behavior. We're planning to upgrade to a more > recent version of ES soon, but it'll take a bit to fully test that. > > Any ideas what could be causing this? > > thanks, > Florian > > -- > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Z-RX\_ggzJzjLaP2%2B7Dt7a8aotvcwF7kQ98mpDS1cvZkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Z-RX_ggzJzjLaP2%2B7Dt7a8aotvcwF7kQ98mpDS1cvZkQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Florian\_Munz\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/florian_munz_2/32/1506_2.png) [@Florian\_Munz\_2](https://discuss.elastic.co/u/Florian_Munz_2)\ **Post date:** [June 3, 2014, 10:27am UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/3 "2014-06-03T10:27:43Z")
Other than the jmap -heap I didn't manage to look more specifically into it: > The same process runs fine on much smaller machines in our staging environment, without the live traffic, of course. Anything particular I should run that would give more insights? Cheers, Florian On Tuesday, June 3, 2014 12:21:32 PM UTC+2, Mark Walkom wrote: > How does your heap look during all this? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 3 June 2014 20:14, Florian Munz \<[su...@theflow.de](mailto:su...@theflow.de) \\> wrote: > > > Hello, > > > > we recently moved our ES cluster from dedicated hardware to AWS > > instances, they have less memory available, but use SSDs for the ES data > > directory. We kept JVM (1.7.0\_17) and ES (0.90.9) version exactly the same. > > On the new hardware, after running a full re-index (creating a new index, > > pointing an alias to the new and one alias to the old index, sending > > realtime updates to both aliases and running a script to fill up the new > > index) our cluster gets stuck. > > > > 10 minutes after the re-index finishes and we move both aliases to the > > new index, ES stops answering any search or index queries, no errors in the > > logs apart from it not answering queries anymore: > > > > org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: > > rejected execution (queue capacity 1000) on > > org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$4@172018e5 > > > > CPU load is low, it doesn't look like it's doing anything expensive. A > > request to hot\_threads times out. I've put the output from jstack and jmap > > here: > > > > [ES cluster stuck · GitHub](https://gist.github.com/theflow/b983d512ea344545f7f6) > > > > We tried upgrading to 0.90.13, since the changelog mentioned a problem > > with infinite loops, but same behavior. We're planning to upgrade to a more > > recent version of ES soon, but it'll take a bit to fully test that. > > > > Any ideas what could be causing this? > > > > thanks, > > Florian > > > > -- > > 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](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-a47e-47c6-8411-eb619c3c54bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-a47e-47c6-8411-eb619c3c54bc%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 3, 2014, 10:36am UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/4 "2014-06-03T10:36:10Z")
Am I reading that right, you're basically at 100% heap usage? If that is the case then it'd be GC that's killing you. Did you add more nodes when you moved to AWS or do you have the same number? Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 3 June 2014 20:27, Florian Munz [surf@theflow.de](mailto:surf@theflow.de) wrote: > Other than the jmap -heap I didn't manage to look more specifically into > it: > > [ES cluster stuck · GitHub](https://gist.github.com/theflow/b983d512ea344545f7f6#file-jmap) > > The same process runs fine on much smaller machines in our staging > environment, without the live traffic, of course. > > Anything particular I should run that would give more insights? > > Cheers, > Florian > > On Tuesday, June 3, 2014 12:21:32 PM UTC+2, Mark Walkom wrote: > > > How does your heap look during all this? > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 3 June 2014 20:14, Florian Munz [su...@theflow.de](mailto:su...@theflow.de) wrote: > > > > > Hello, > > > > > > we recently moved our ES cluster from dedicated hardware to AWS > > > instances, they have less memory available, but use SSDs for the ES data > > > directory. We kept JVM (1.7.0\_17) and ES (0.90.9) version exactly the same. > > > On the new hardware, after running a full re-index (creating a new index, > > > pointing an alias to the new and one alias to the old index, sending > > > realtime updates to both aliases and running a script to fill up the new > > > index) our cluster gets stuck. > > > > > > 10 minutes after the re-index finishes and we move both aliases to the > > > new index, ES stops answering any search or index queries, no errors in the > > > logs apart from it not answering queries anymore: > > > > > > org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: > > > rejected execution (queue capacity 1000) on org.elasticsearch.action. > > > search.type.TransportSearchTypeAction$BaseAsyncAction$4@172018e5 > > > > > > CPU load is low, it doesn't look like it's doing anything expensive. A > > > request to hot\_threads times out. I've put the output from jstack and jmap > > > here: > > > > > > [ES cluster stuck · GitHub](https://gist.github.com/theflow/b983d512ea344545f7f6) > > > > > > We tried upgrading to 0.90.13, since the changelog mentioned a problem > > > with infinite loops, but same behavior. We're planning to upgrade to a more > > > recent version of ES soon, but it'll take a bit to fully test that. > > > > > > Any ideas what could be causing this? > > > > > > thanks, > > > Florian > > > > > > -- > > > 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](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-a47e-47c6-8411-eb619c3c54bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-a47e-47c6-8411-eb619c3c54bc%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-a47e-47c6-8411-eb619c3c54bc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-a47e-47c6-8411-eb619c3c54bc%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Florian\_Munz\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/florian_munz_2/32/1506_2.png) [@Florian\_Munz\_2](https://discuss.elastic.co/u/Florian_Munz_2)\ **Post date:** [June 4, 2014, 9:18pm UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/5 "2014-06-04T21:18:55Z")
I don't see any signs of GC in the logs or somewhere else, shouldn't there be high CPU usage in that case? We moved from 4 to 2 nodes and from 2 to 1 number of replicas. Cheers, Florian On 03.06.14 12:36, Mark Walkom wrote: > Am I reading that right, you're basically at 100% heap usage? If that is > the case then it'd be GC that's killing you. > > Did you add more nodes when you moved to AWS or do you have the same number? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) [mailto:markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) [http://www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 3 June 2014 20:27, Florian Munz \<[surf@theflow.de](mailto:surf@theflow.de) > [mailto:surf@theflow.de](mailto:surf@theflow.de)\> wrote: > > ``` > Other than the jmap -heap I didn't manage to look more specifically > into it: > > https://gist.github.com/theflow/b983d512ea344545f7f6#file-jmap > > The same process runs fine on much smaller machines in our staging > environment, without the live traffic, of course. > > Anything particular I should run that would give more insights? > > Cheers, > Florian > > On Tuesday, June 3, 2014 12:21:32 PM UTC+2, Mark Walkom wrote: > > How does your heap look during all this? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > On 3 June 2014 20:14, Florian Munz wrote: > > Hello, > > we recently moved our ES cluster from dedicated hardware to > AWS instances, they have less memory available, but use SSDs > for the ES data directory. We kept JVM (1.7.0_17) and ES > (0.90.9) version exactly the same. On the new hardware, > after running a full re-index (creating a new index, > pointing an alias to the new and one alias to the old index, > sending realtime updates to both aliases and running a > script to fill up the new index) our cluster gets stuck. > > 10 minutes after the re-index finishes and we move both > aliases to the new index, ES stops answering any search or > index queries, no errors in the logs apart from it not > answering queries anymore: > > org.elasticsearch.common.util. __concurrent.__ EsRejectedExecutionException: > rejected execution (queue capacity 1000) on > org.elasticsearch.action. __search.type.__ TransportSearchTypeAction$__BaseAsyncAction$4@172018e5 > > CPU load is low, it doesn't look like it's doing anything > expensive. A request to hot_threads times out. I've put the > output from jstack and jmap here: > > https://gist.github.com/__theflow/b983d512ea344545f7f6 > > > We tried upgrading to 0.90.13, since the changelog mentioned > a problem with infinite loops, but same behavior. We're > planning to upgrade to a more recent version of ES soon, but > it'll take a bit to fully test that. > > Any ideas what could be causing this? > > thanks, > Florian > > -- > 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/7a347529-__ df1a-4a21-9ac1-d3af882a035a%__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/04b3d0a2-a47e-47c6-8411-eb619c3c54bc%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/NFGiLsmPkk0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/NFGiLsmPkk0/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com) > [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ%40mail.gmail.com?utm_medium=email&utm_source=footer). > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/538F8D3F.40503%40theflow.de](https://groups.google.com/d/msgid/elasticsearch/538F8D3F.40503%40theflow.de). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [June 4, 2014, 9:28pm UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/6 "2014-06-04T21:28:32Z")
Many concurrent costly operations (range queries or faceting when I/O ops are required, segment merges, shard allocations etc) are known to starve ES out of threads or processing power, and this is what you are experiencing - no threads are capable of taking your requests. Immediate solution is to run a master-only node (node.data = false) so you have one node that acts as master and cluster coordinator that is known to never starve out of system resources. Even running this node side-by-side on the same server as one of the data nodes can protect you as it doesn't have the same memory requirements etc as a data node. Finally, there has been (and still is) a lot of work put into this so I strongly recommend upgrading to the latest (currently it is 1.2.1). -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Tue, Jun 3, 2014 at 1:14 PM, Florian Munz [surf@theflow.de](mailto:surf@theflow.de) wrote: > Hello, > > we recently moved our ES cluster from dedicated hardware to AWS instances, > they have less memory available, but use SSDs for the ES data directory. We > kept JVM (1.7.0\_17) and ES (0.90.9) version exactly the same. On the new > hardware, after running a full re-index (creating a new index, pointing an > alias to the new and one alias to the old index, sending realtime updates > to both aliases and running a script to fill up the new index) our cluster > gets stuck. > > 10 minutes after the re-index finishes and we move both aliases to the new > index, ES stops answering any search or index queries, no errors in the > logs apart from it not answering queries anymore: > > org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: > rejected execution (queue capacity 1000) on > org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$4@172018e5 > > CPU load is low, it doesn't look like it's doing anything expensive. A > request to hot\_threads times out. I've put the output from jstack and jmap > here: > > [ES cluster stuck · GitHub](https://gist.github.com/theflow/b983d512ea344545f7f6) > > We tried upgrading to 0.90.13, since the changelog mentioned a problem > with infinite loops, but same behavior. We're planning to upgrade to a more > recent version of ES soon, but it'll take a bit to fully test that. > > Any ideas what could be causing this? > > thanks, > Florian > > -- > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7a347529-df1a-4a21-9ac1-d3af882a035a%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZvRJK\_pR6nskv8ujpH8cCRp890UZ1d8M\_iU0Zi-OULO%3DQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZvRJK_pR6nskv8ujpH8cCRp890UZ1d8M_iU0Zi-OULO%3DQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 4, 2014, 10:44pm UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/7 "2014-06-04T22:44:01Z")
If you're halved your node count and also reduced the amount of RAM, then you're probably running into GC problems. Install something like elastichq or marvel, and then check what is happening on a cluster and node level. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 5 June 2014 07:18, Florian Munz [surf@theflow.de](mailto:surf@theflow.de) wrote: > I don't see any signs of GC in the logs or somewhere else, shouldn't there > be high CPU usage in that case? > > We moved from 4 to 2 nodes and from 2 to 1 number of replicas. > > Cheers, > Florian > > On 03.06.14 12:36, Mark Walkom wrote: > > > Am I reading that right, you're basically at 100% heap usage? If that is > > the case then it'd be GC that's killing you. > > > > Did you add more nodes when you moved to AWS or do you have the same > > number? > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) [mailto:markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) [http://www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 3 June 2014 20:27, Florian Munz \<[surf@theflow.de](mailto:surf@theflow.de) > > [mailto:surf@theflow.de](mailto:surf@theflow.de)\> wrote: > > > > ``` > > Other than the jmap -heap I didn't manage to look more specifically > > into it: > > > > https://gist.github.com/theflow/b983d512ea344545f7f6#file-jmap > > > > The same process runs fine on much smaller machines in our staging > > environment, without the live traffic, of course. > > > > Anything particular I should run that would give more insights? > > > > Cheers, > > Florian > > > > On Tuesday, June 3, 2014 12:21:32 PM UTC+2, Mark Walkom wrote: > > > > How does your heap look during all this? > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: ma...@campaignmonitor.com > > web: www.campaignmonitor.com > > > > On 3 June 2014 20:14, Florian Munz wrote: > > > > Hello, > > > > we recently moved our ES cluster from dedicated hardware to > > AWS instances, they have less memory available, but use SSDs > > for the ES data directory. We kept JVM (1.7.0_17) and ES > > (0.90.9) version exactly the same. On the new hardware, > > after running a full re-index (creating a new index, > > pointing an alias to the new and one alias to the old index, > > sending realtime updates to both aliases and running a > > script to fill up the new index) our cluster gets stuck. > > > > 10 minutes after the re-index finishes and we move both > > aliases to the new index, ES stops answering any search or > > index queries, no errors in the logs apart from it not > > answering queries anymore: > > > > org.elasticsearch.common.util. __concurrent.__ > > > > ``` > > > > EsRejectedExecutionException: > > rejected execution (queue capacity 1000) on > > org.elasticsearch.action. **search.type.** > > TransportSearchTypeAction$\_\_BaseAsyncAction$4@172018e5 > > > > ``` > > CPU load is low, it doesn't look like it's doing anything > > expensive. A request to hot_threads times out. I've put the > > output from jstack and jmap here: > > > > https://gist.github.com/__theflow/b983d512ea344545f7f6 > > > > > > We tried upgrading to 0.90.13, since the changelog mentioned > > a problem with infinite loops, but same behavior. We're > > planning to upgrade to a more recent version of ES soon, but > > it'll take a bit to fully test that. > > > > Any ideas what could be causing this? > > > > thanks, > > Florian > > > > -- > > 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/7a347529-_ > > > > ``` > > > > \_df1a-4a21-9ac1-d3af882a035a%\_\_40googlegroups.com > > \<[https://groups.google.com/d/msgid/elasticsearch/7a347529-](https://groups.google.com/d/msgid/elasticsearch/7a347529-) > > df1a-4a21-9ac1-d3af882a035a%[40GGGROUPS CASINO – Real Slot Casino for 10,000+ Senior Players](http://40googlegroups.com?utm_medium=) > > email&utm\_source=footer\>. > > For more options, visit [https://groups.google.com/d/\_\_optout](https://groups.google.com/d/__optout) > > [https://groups.google.com/d/optout](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/04b3d0a2- > > > > ``` > > > > a47e-47c6-8411-eb619c3c54bc%[40googlegroups.com](http://40googlegroups.com) > > \<[https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-](https://groups.google.com/d/msgid/elasticsearch/04b3d0a2-) > > a47e-47c6-8411-eb619c3c54bc%[40GGGROUPS CASINO – Real Slot Casino for 10,000+ Senior Players](http://40googlegroups.com?utm_medium=) > > email&utm\_source=footer\>. > > For more options, visit [https://groups.google.com/d/optout](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/NFGiLsmPkk0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/NFGiLsmPkk0/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com) > > [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/](https://groups.google.com/d/msgid/elasticsearch/) > > CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ%[40mail.gmail.com](http://40mail.gmail.com) > > \<[https://groups.google.com/d/msgid/elasticsearch/](https://groups.google.com/d/msgid/elasticsearch/) > > CAEM624YTb8m1qRZ5iuAf3eq6v-2FkSpemmw8d2UhVJep8zt0BQ% > > [40mail.gmail.com?utm\_medium=email&utm\_source=footer](http://40mail.gmail.com?utm_medium=email&utm_source=footer)\>. > > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > msgid/elasticsearch/538F8D3F.40503%[40theflow.de](http://40theflow.de). > For more options, visit [https://groups.google.com/d/optout](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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Y2fLafpPeVZ7foGjADMV7pGrGNekUr\_FURe2XonT-ccg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Y2fLafpPeVZ7foGjADMV7pGrGNekUr_FURe2XonT-ccg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:24am UTC](https://discuss.elastic.co/t/cluster-gets-stuck-after-full-re-index/17882/8 "2017-07-06T01:24:37Z")