Briefly, this error occurs when Elasticsearch is converting to a new shards state location and format. This is part of a process where Elasticsearch is updating its internal data structures. It’s not an error but an informational message indicating that the conversion has been completed and a backup has been created at the specified location. If you’re seeing issues related to this, ensure that Elasticsearch has the necessary permissions to write to the backup location. Also, check that there’s enough disk space for the backup and that the backup process is not being interrupted.
This guide will help you check for common problems that cause the log ” conversion to new shards state location and format done; backup create at [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shards.
Log Context
Log “conversion to new shards state location and format done; backup create at [{}]” classname is LocalGatewayShardsState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
stateFile.delete();
}
}
logger.info("conversion to new shards state location and format done; backup create at [{}]"; backupFile.getAbsolutePath());
}
private Map pre09ReadState(byte[] data) throws IOException {
final Map shardsState = Maps.newHashMap();
try (XContentParser parser = XContentHelper.createParser(data; 0; data.length)) {
[ratemypost]
