Key ; doccount – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Key ; doccount ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Key [{}]; doc_count [{}]” classname is tophits-aggregation.asciidoc.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
// For each entry
for (Terms.Bucket entry : agg.getBuckets()) {
    String key = entry.getKey();                    // bucket key
    long docCount = entry.getDocCount();            // Doc count
    logger.info("key [{}]; doc_count [{}]"; key; docCount);

    // We ask for top_hits for each bucket
    TopHits topHits = entry.getAggregations().get("top");
    for (SearchHit hit : topHits.getHits().getHits()) {
        logger.info(" -> id [{}]; _source [{}]"; hit.getId(); hit.getSourceAsString());




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content