Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when the system fails to delete Point-In-Time (PIT) identifiers on a specific node in OpenSearch. PITs are used for consistent search results during long-running searches. The failure could be due to network issues, node failure, or insufficient permissions. To resolve this, you can try to manually delete the PITs, ensure the node is running properly, check network connectivity, or verify the user has the necessary permissions to delete PITs. If the issue persists, consider checking the OpenSearch logs for more detailed error information.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” Delete PITs failed on node [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: delete, search, node.
Overview
Delete a document
DELETE /my_index/_doc/1
Notes
- A delete request throws 404 error code if the document does not already exist in the index.
- If you want to delete a set of documents that matches a query, you need to use delete by query API.
Quick links
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 “Delete PITs failed on node [{}]” classname is PitService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
try {
final Transport.Connection connection = searchTransportService.getConnection(clusterAlias; node);
searchTransportService.sendFreePITContexts(connection; entry.getValue(); groupedListener);
} catch (Exception e) {
String nodeName = node.getName();
logger.error(() -> new ParameterizedMessage("Delete PITs failed on node [{}]"; nodeName); e);
List deletePitInfos = new ArrayList();
for (PitSearchContextIdForNode pitSearchContextIdForNode : entry.getValue()) {
deletePitInfos.add(new DeletePitInfo(false; pitSearchContextIdForNode.getPitId()));
}
groupedListener.onResponse(new DeletePitResponse(deletePitInfos));
