Briefly, this error occurs when Elasticsearch is unable to update the mapping of an index due to a conflict or an incorrect mapping configuration. This could be due to a change in the data type of a field or an attempt to modify an existing field which is not allowed. To resolve this issue, you can either reindex your data with the correct mapping or create a new index with the correct mapping and reindex your data into the new index. Also, ensure that your mapping configuration is correct before updating it.
This guide will help you check for common problems that cause the log ” [{}] Failed to update mapping; not clearing finished_time ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[{}] Failed to update mapping; not clearing finished_time” classname is TransportOpenJobAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
listener.onResponse(response);
});
ActionListener mappingsUpdatedListener = ActionListener.wrap(
mappingUpdateResponse -> jobConfigProvider.updateJob(jobId; update; null; clearedTimeListener);
e -> {
logger.error(new ParameterizedMessage("[{}] Failed to update mapping; not clearing finished_time"; jobId); e);
// Not a critical error so continue without attempting to clear finish time
listener.onResponse(response);
}
);
ElasticsearchMappings.addDocMappingIfMissing(
