Briefly, this error occurs when Elasticsearch is updating its metadata location and format. This is part of the process when Elasticsearch is performing a backup or a snapshot. It’s not an error, but an informational message indicating that the conversion has been completed successfully. If you’re seeing this message frequently and it’s causing concern, you can adjust the logging level in your Elasticsearch configuration to reduce the verbosity. However, it’s generally a good idea to keep these messages as they provide useful information about the state of your Elasticsearch cluster.
This guide will help you check for common problems that cause the log ” conversion to new metadata 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: metadata.
Overview
Metadata in Elasticsearch refers to additional information stored for each document. This is achieved using the specific metadata fields available in Elasticsearch. The default behavior of some of these metadata fields can be customized during mapping creation.
Examples
Using _meta meta-field for storing application-specific information with the mapping:
PUT /my_index?pretty
{
"mappings": {
"_meta": {
"domain": "security",
"release_information": {
"date": "18-01-2020",
"version": "7.5"
}
}
}
}Notes
- In version 2.x, Elasticsearch had a total 13 meta fields available, which are: _index, _uid, _type, _id, _source, _size, _all, _field_names, _timestamp, _ttl, _parent, _routing, _meta
- In version 5.x, _timestamp and _ttl meta fields were removed.
- In version 6.x, the _parent meta field was removed.
- In version 7.x, _uid and _all meta fields were removed.
Log Context
Log “conversion to new metadata location and format done; backup create at [{}]” classname is LocalGatewayMetaState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
stateFile.delete();
}
}
logger.info("conversion to new metadata location and format done; backup create at [{}]"; backupFile.getAbsolutePath());
}
class RemoveDanglingIndex implements Runnable {
private final IndexMetaData metaData;
[ratemypost]
