How To Solve Issues Related to Log – Failed to send error response for action clear_sc and request

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Failed to send error response for action clear_sc and request” it’s important to understand common problems related to Elasticsearch concepts: request, response, scroll, search. See detailed explanations below complete with common problems, examples and useful tips.

Scroll in Elasticsearch

What it is

In Elasticsearch, the concept of scroll comes into play when you have a large set of search results. Large search results are exhaustive for both the Elasticsearch cluster and the requesting client in terms of memory and processing. The scroll API enables you  to take a snapshot of a large number of results from a single search request.

Examples

To perform a scroll search, you need to add the scroll parameter to search query and specify how long Elasticsearch should keep the search context viable.

GET mydocs-2019/_search?scroll=40s
{
"size": 5000,
"query": {
"match_all": {}
},
"sort": [
 {
 "_doc": {
  "order": "asc"
   }
  }
 ]
}

This query will return a maximum of  5000 hits and if the scroll is idle for more than 40  seconds, then it will be deleted. The response will return the first page of the results and a scroll id, you can use the scroll id to get additional documents from the scroll. You’re able to keep retrieving the documents until you have all of them.

Notes
  • Changes made to documents after the scroll will not show up in your results.
  • When you are done with the scroll, you can delete it manually using the scroll id.
DELETE _search/scroll/<sroll_id>

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Ravel Catch Tokenmismatchexception  

2Bulk Api Rejected Records But I Can  


Log Context

Log ”Failed to send error response for action [clear_sc] and request [“ classname is TransportClearScrollAction.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

                 
Override
                public void onFailure(Throwable e) {
                    try {
                        channel.sendResponse(e);
                    } catch (Exception e1) {
                        logger.warn("Failed to send error response for action [clear_sc] and request [" + request + "]"; e1);
                    }
                }
            });
        }






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster