Briefly, this error occurs when there’s a discrepancy between the number of documents sent for indexing and the number of documents actually indexed in Elasticsearch. This could be due to various reasons such as network issues, insufficient resources, or data inconsistency. To resolve this, you can: 1) Check your network connection and ensure it’s stable. 2) Verify that your Elasticsearch cluster has enough resources (CPU, memory, disk space). 3) Check your data for inconsistencies or corruption that might prevent successful indexing. 4) Review your Elasticsearch logs for more detailed error messages.
This guide will help you check for common problems that cause the log ” Successfully sent [” + numIndexed.get() + “]; indexed [” + numIndexed.get() + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Successfully sent [” + numIndexed.get() + “]; indexed [” + numIndexed.get() + “]” classname is RollupShardIndexer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
do {
bucket = computeBucket(bucket);
} while (bucket != null);
}
// TODO: check that numIndexed == numSent; otherwise throw an exception
logger.info("Successfully sent [" + numIndexed.get() + "]; indexed [" + numIndexed.get() + "]");
return numIndexed.get();
}
private BulkProcessor createBulkProcessor() {
final BulkProcessor.Listener listener = new BulkProcessor.Listener() {
