Briefly, this error occurs when Elasticsearch attempts to clear the search context on a specific node but fails. This could be due to a variety of reasons such as network issues, node unavailability, or insufficient resources. To resolve this issue, you can try the following: 1) Check the health status of your nodes and ensure they are all up and running. 2) Verify your network connectivity. 3) Check if there are sufficient resources available for Elasticsearch to operate. 4) Review your Elasticsearch logs for more detailed error information.
This log is related to search problems, in addition to reading the guide below you can use the free Search Log Analyzer. With Opster’s Analyzer, you can easily locate slow searches and understand what led to them adding additional load to your system. The tool is free and takes just 2 minutes to run.
Overview
Search refers to the searching of documents in an index or multiple indices. The simple search is just a GET API request to the _search endpoint. The search query can either be provided in query string or through a request body.
Examples
When looking for any documents in this index, if search parameters are not provided, every document is a hit and by default 10 hits will be returned.
GET my_documents/_search
A JSON object is returned in response to a search query. A 200 response code means the request was completed successfully.
{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [
...
]
}
}Notes and good things to know
- Distributed search is challenging and every shard of the index needs to be searched for hits, and then those hits are combined into a single sorted list as a final result.
- There are two phases of search: the query phase and the fetch phase.
- In the query phase, the query is executed on each shard locally and top hits are returned to the coordinating node. The coordinating node merges the results and creates a global sorted list.
- In the fetch phase, the coordinating node brings the actual documents for those hit IDs and returns them to the requesting client.
- A coordinating node needs enough memory and CPU in order to handle the fetch phase.
Log Context
Log “Clear SC failed on node[{}]” classname is ClearScrollController.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
listener.onResponse(new ClearScrollResponse(succeeded; freedSearchContexts.get()));
}
}
private void onFailedFreedContext(Throwable e; DiscoveryNode node) {
logger.warn(() -> new ParameterizedMessage("Clear SC failed on node[{}]"; node); e);
/*
* We have to set the failure marker before we count down otherwise we can expose the failure marker before we have set it to a
* racing thread successfully freeing a context. This would lead to that thread responding that the clear scroll succeeded.
*/
hasFailed.set(true);
[ratemypost]