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 encounters an unrecognized rounding ID during a date histogram aggregation. The rounding ID is used to group date fields into specific time intervals. If the ID is unknown, it means the specified interval is not supported. To resolve this issue, you can check the OpenSearch documentation for the correct rounding ID values. Alternatively, you can use a different, supported time interval for your date histogram aggregation. Lastly, ensure that your OpenSearch version supports the rounding ID you’re using.
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 ” unknown rounding id [” + id + “] ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: .
Log Context
Log “unknown rounding id [” + id + “]” class name is Rounding.java. We extracted the following from OpenSearch source code for those seeking an in-depth context :
case TimeIntervalRounding.ID:
return new TimeIntervalRounding(in);
case OffsetRounding.ID:
return new OffsetRounding(in);
default:
throw new OpenSearchException("unknown rounding id [" + id + "]");
}
} /**
* Implementation of {@link Prepared} using pre-calculated "round down" points.
