Briefly, this error occurs when Elasticsearch expects a certain request count to be tracked but it doesn’t find the count. This could be due to a bug in the system or a misconfiguration. To resolve this issue, you can try the following: 1) Check your Elasticsearch configuration and ensure it’s set up correctly. 2) Update your Elasticsearch version to the latest one as it might be a bug that has been fixed in newer versions. 3) Check your application code to ensure it’s correctly tracking the request count.
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 Elasticsearch concepts: repository-s3, repositories, request.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
Log Context
Log “Expected request count to be tracked for request [{}] but found not count.” classname is S3BlobStore.java.
We extracted the following from Elasticsearch 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();
}
