# IllegalArgumentException followed by SearchContextMissingException **URL:** \ **Category:** Elasticsearch\ **Created:** [August 13, 2014, 4:57am UTC](https://discuss.elastic.co/t/illegalargumentexception-followed-by-searchcontextmissingexception/19240 "2014-08-13T04:57:36Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Michael\_Culhane](https://avatars.discourse-cdn.com/v4/letter/m/e19adc/32.png) [@Michael\_Culhane](https://discuss.elastic.co/u/Michael_Culhane)\ **Post date:** [August 13, 2014, 4:57am UTC](https://discuss.elastic.co/t/illegalargumentexception-followed-by-searchcontextmissingexception/19240/1 "2014-08-13T04:57:36Z")
Hello! I have a new three-node Elasticsearch cluster that's giving me some trouble. After a while of running smoothly (a couple hours, sometimes more, sometimes less), one of the three nodes gets the following error about 10 times: [2014-08-12 16:28:05,784][WARN][http.netty] [elasticsearch-01] Caught exception while handling client http traffic, closing connection [id: 0x05bf114e, /10.10.100.10:45980 =\> /10.10.100.20:9200] java.lang.IllegalArgumentException: empty text at org.elasticsearch.common.netty.handler.codec.http.HttpVersion.(HttpVersion.java:97) at org.elasticsearch.common.netty.handler.codec.http.HttpVersion.valueOf(HttpVersion.java:62) at org.elasticsearch.common.netty.handler.codec.http.HttpRequestDecoder.createMessage(HttpRequestDecoder.java:75) at org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:189) at org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:101) at org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:500) at org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Shortly after, each of the three nodes encounters the following error several dozen times: [2014-08-12 18:10:11,638][DEBUG][action.search.type] [elasticsearch-01] [614] Failed to execute fetch phase org.elasticsearch.search.SearchContextMissingException: No search context found for id [614] 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Restarting elasticsearch on each of the nodes will temporarily resolve the issue for another hour or two until it all starts again. Despite my best efforts, I haven't been able to pinpoint or reliably reproduce the issue. I have noticed, though, that the first error (which seems to trigger the second) always occurs on the same node. Furthermore, I have a single-node cluster which has been supporting identical traffic/queries on the same data without issue, leading me to believe that the issue might be related to the cluster configuration. Does anyone have thoughts about how I can go about resolving/troubleshooting this? Thank you for the help! -- 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/1a5531a2-8c4f-4a0f-bb71-239892c5f6f6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a5531a2-8c4f-4a0f-bb71-239892c5f6f6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 14, 2014, 6:48pm UTC](https://discuss.elastic.co/t/illegalargumentexception-followed-by-searchcontextmissingexception/19240/2 "2014-08-14T18:48:40Z")
The first error is from a HTTP connection hat did not send a HTTP command correctly to the cluster node (i.e. without HTTP version). Also possible is a connection attempt of a non-HTTP client, or a misconfiguration. The second error is probably from a search request using scan/scroll, but the lifetime of the scan/scroll had been exceeded. It could also be a runaway query. Jörg On Wed, Aug 13, 2014 at 6:57 AM, Michael Culhane [mculhane11@gmail.com](mailto:mculhane11@gmail.com) wrote: > Hello! > > I have a new three-node Elasticsearch cluster that's giving me some > trouble. After a while of running smoothly (a couple hours, sometimes more, > sometimes less), one of the three nodes gets the following error about 10 > times: > > [2014-08-12 16:28:05,784][WARN][http.netty] > [elasticsearch-01] Caught exception while handling client http traffic, > closing connection [id: 0x05bf114e, /10.10.100.10:45980 =\> / > 10.10.100.20:9200] > java.lang.IllegalArgumentException: empty text > at > org.elasticsearch.common.netty.handler.codec.http.HttpVersion.(HttpVersion.java:97) > at > org.elasticsearch.common.netty.handler.codec.http.HttpVersion.valueOf(HttpVersion.java:62) > at > org.elasticsearch.common.netty.handler.codec.http.HttpRequestDecoder.createMessage(HttpRequestDecoder.java:75) > at > org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:189) > at > org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:101) > at > org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:500) > at > org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) > at > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at > org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) > at > org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) > at > org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > at > org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > > Shortly after, each of the three nodes encounters the following error > several dozen times: > > [2014-08-12 18:10:11,638][DEBUG][action.search.type] > [elasticsearch-01] [614] Failed to execute fetch phase > org.elasticsearch.search.SearchContextMissingException: No search context > found for id [614] > 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:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > > Restarting elasticsearch on each of the nodes will temporarily resolve the > issue for another hour or two until it all starts again. > > Despite my best efforts, I haven't been able to pinpoint or reliably > reproduce the issue. I have noticed, though, that the first error (which > seems to trigger the second) always occurs on the same node. Furthermore, I > have a single-node cluster which has been supporting identical > traffic/queries on the same data without issue, leading me to believe that > the issue might be related to the cluster configuration. > > Does anyone have thoughts about how I can go about > resolving/troubleshooting this? > > Thank you for the help! > > -- > 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/1a5531a2-8c4f-4a0f-bb71-239892c5f6f6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a5531a2-8c4f-4a0f-bb71-239892c5f6f6%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/1a5531a2-8c4f-4a0f-bb71-239892c5f6f6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1a5531a2-8c4f-4a0f-bb71-239892c5f6f6%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/CAKdsXoFmhb2%2B1uWff9zS7mcUyTmwNKxtbvcz-0%2BOfzq2Y6aq%3Dw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFmhb2%2B1uWff9zS7mcUyTmwNKxtbvcz-0%2BOfzq2Y6aq%3Dw%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:08am UTC](https://discuss.elastic.co/t/illegalargumentexception-followed-by-searchcontextmissingexception/19240/3 "2017-07-06T01:08:25Z")