# Cluster went to red stage due to SearchContextMissingException **URL:** \ **Category:** Elasticsearch\ **Created:** [December 11, 2014, 2:44pm UTC](https://discuss.elastic.co/t/cluster-went-to-red-stage-due-to-searchcontextmissingexception/21214 "2014-12-11T14:44:13Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![balakrishnan\_cd](https://avatars.discourse-cdn.com/v4/letter/b/a3d4f5/32.png) [@balakrishnan\_cd](https://discuss.elastic.co/u/balakrishnan_cd)\ **Post date:** [December 11, 2014, 2:44pm UTC](https://discuss.elastic.co/t/cluster-went-to-red-stage-due-to-searchcontextmissingexception/21214/1 "2014-12-11T14:44:13Z")
Hi, We are using elasticsearch 1.3.1 version. And we are getting the below error in our production, [2014-12-10 19:11:00,534][DEBUG][action.search.type] [es\_f2\_02] [5031993] Failed to execute fetch phase org.elasticsearch.search. SearchContextMissingException: No search context found for id [5031993] at org.elasticsearch.search.SearchService.findContext(SearchService.java:480) at org.elasticsearch.search.SearchService.executeFetchPhase(SearchService. java:450) at org.elasticsearch.search.action.SearchServiceTransportAction$17 .call(SearchServiceTransportAction.java:410) at org.elasticsearch.search. action.SearchServiceTransportAction$17.call(SearchServiceTransportAction. java:407) at org.elasticsearch.search.action.SearchServiceTransportAction$23 .run(SearchServiceTransportAction.java:517) at java.util.concurrent. ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util. concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) After this error, nodes faced timeout,diconnected then finally causes the OOM error. Is there any suggestion to solve this issue? Thanks in advance! -- 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/2088ed2d-9ddc-48ba-8507-d399df3367f9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2088ed2d-9ddc-48ba-8507-d399df3367f9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\ **Post date:** [December 11, 2014, 3:44pm UTC](https://discuss.elastic.co/t/cluster-went-to-red-stage-due-to-searchcontextmissingexception/21214/2 "2014-12-11T15:44:16Z")
Hmm... few days ago, I asked a similar question, [https://groups.google.com/forum/#!topic/elasticsearch/1TlJDwuKXiA](https://groups.google.com/forum/#!topic/elasticsearch/1TlJDwuKXiA) But we dont' get timedout of oom error.. Jason On Thu, Dec 11, 2014 at 10:44 PM, Bala krishnan \< [balakrishnan.techs@gmail.com](mailto:balakrishnan.techs@gmail.com)\> wrote: > Hi, > > We are using elasticsearch 1.3.1 version. > > And we are getting the below error in our production, > > [2014-12-10 19:11:00,534][DEBUG][action.search.type] [es\_f2\_02] [5031993] > Failed to execute fetch phase org.elasticsearch.search. > SearchContextMissingException: No search context found for id [5031993] at > org.elasticsearch.search.SearchService.findContext(SearchService.java:480) > at org.elasticsearch.search.SearchService.executeFetchPhase(SearchService. > java:450) at org.elasticsearch.search.action.SearchServiceTransportAction$ > 17.call(SearchServiceTransportAction.java:410) at org.elasticsearch.search > .action.SearchServiceTransportAction$17.call(SearchServiceTransportAction. > java:407) at org.elasticsearch.search.action.SearchServiceTransportAction$ > 23.run(SearchServiceTransportAction.java:517) at java.util.concurrent. > ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util. > concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at > java.lang.Thread.run(Thread.java:722) > > After this error, nodes faced timeout,diconnected then finally causes the > OOM error. > > Is there any suggestion to solve this issue? > > Thanks in advance! > > -- > 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/2088ed2d-9ddc-48ba-8507-d399df3367f9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2088ed2d-9ddc-48ba-8507-d399df3367f9%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/2088ed2d-9ddc-48ba-8507-d399df3367f9%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/2088ed2d-9ddc-48ba-8507-d399df3367f9%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/CAHO4itxZ6PrYgzv6z8TCDeQG9FJoAcYt72hNYZqN1LdP\_PBepg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itxZ6PrYgzv6z8TCDeQG9FJoAcYt72hNYZqN1LdP_PBepg%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, 12:44am UTC](https://discuss.elastic.co/t/cluster-went-to-red-stage-due-to-searchcontextmissingexception/21214/3 "2017-07-06T00:44:08Z")