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 OpenSearch expects a certain request count to be tracked but doesn’t find it. This could be due to a misconfiguration or a bug in the system. To resolve this issue, you can try the following: 1) Check your OpenSearch configuration to ensure it’s set up correctly. 2) Update your OpenSearch version to the latest one, as this might be a bug that has been fixed in newer versions. 3) Review your application’s code to ensure it’s making requests correctly and tracking them as expected.
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 ” Expected request count to be tracked for request [{}] but found not count. ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: repository-s3, request, repositories, plugins.
Log Context
Log “Expected request count to be tracked for request [{}] but found not count.” classname is S3BlobStore.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
}
private long getRequestCount(Request> request) {
Number requestCount = request.getAWSRequestMetrics().getTimingInfo().getCounter(AWSRequestMetrics.Field.RequestCount.name());
if (requestCount == null) {
logger.warn("Expected request count to be tracked for request [{}] but found not count."; request);
return 0L;
}
return requestCount.longValue();
}
