Error trying to create a copy of RunningStats – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch attempts to create a copy of RunningStats, a statistical data structure, and fails. This could be due to insufficient memory, corrupted data, or a bug in the software. To resolve this issue, you can try increasing the memory allocation for Elasticsearch, checking and repairing any corrupted data, or updating Elasticsearch to the latest version to fix any potential bugs.

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 ” Error trying to create a copy of RunningStats ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations.

Log Context

Log “Error trying to create a copy of RunningStats” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public RunningStats clone() {
 try {
 return (RunningStats) super.clone();
 } catch (CloneNotSupportedException e) {
 throw new ElasticsearchException("Error trying to create a copy of RunningStats");
 }  public Set getAllFieldNames() {
 final Set allFieldNames = Collections.unmodifiableSet(this.counts.keySet());


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?