Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Thousands of SearchContextMissingException: No search context found for id

See original GitHub issue

Version 2.1.1 We are using es-hadoop with spark, but each time our job runs the elasticsearch logs are spoiled with the errors like below:

This is causing the logfiles to grow by many gigabytes each day

[2015-10-15 06:31:11,699][DEBUG][action.search.type       ] [es-007] [120600] Failed to execute query phase
org.elasticsearch.transport.RemoteTransportException [es-012][inet[/192.168.0.12:9300]][indices:data/read/search[phase/scan/scroll]]
Caused by: org.elasticsearch.search.SearchContextMissingException: No search context found for id [120600]
    at org.elasticsearch.search.SearchService.findContext(SearchService.java:537)
    at org.elasticsearch.search.SearchService.executeScan(SearchService.java:265)
    at org.elasticsearch.search.action.SearchServiceTransportAction$SearchScanScrollTransportHandler.messageReceived(SearchServiceTransportAction.java:939)
    at org.elasticsearch.search.action.SearchServiceTransportAction$SearchScanScrollTransportHandler.messageReceived(SearchServiceTransportAction.java:930)
    at org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.doRun(MessageChannelHandler.java:279)
    at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:36)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

Issue Analytics

State:
Created 8 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

costincommented, Oct 28, 2015

@sjoerdmulder Since the issue was detected (thanks for the test) and fixed I’m closing the issue. Feel free to open another one if it keeps occuring.

Cheers,

0reactions

costincommented, Oct 27, 2015

@sjoerdmulder I managed to replicate the issue and track it down (thanks to @clintongormley ) to 2.1.x not picking up the new scrol;_id when iterating across the index. The issue did not appear in master (2.2.x). The work for this in master was done as part of #537. I’ll back port it to 2.1.x as well