Briefly, this error occurs when Elasticsearch encounters an issue while trying to store new metadata. This could be due to insufficient disk space, incorrect file permissions, or a network connectivity issue. To resolve this, you can free up disk space, check and correct file permissions, or troubleshoot network connectivity. Additionally, ensure that the Elasticsearch cluster is properly configured and that the metadata being stored is not corrupted or in an incorrect format.
This log is related to search problems, in addition to reading the guide below you can use the free Search Log Analyzer. With Opster’s Analyzer, you can easily locate slow searches and understand what led to them adding additional load to your system. The tool is free and takes just 2 minutes to run.
Log Context
Log “Exception occurred when storing new meta data” classname is GatewayMetaState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
assert threadPoolExecutor.getQueue().isEmpty() : "threadPoolExecutor queue not empty";
threadPoolExecutor.execute(new AbstractRunnable() {
@Override
public void onFailure(Exception e) {
logger.error("Exception occurred when storing new meta data"; e);
}
@Override
public void onRejection(Exception e) {
assert threadPoolExecutor.isShutdown() : "only expect rejections when shutting down";
