Briefly, this error occurs when Elasticsearch is unable to delete outdated transform configurations due to issues like insufficient permissions, network problems, or the configurations being in use. To resolve this, you can ensure the user has the necessary permissions to delete configurations. If it’s a network issue, check the connectivity between nodes. If the configurations are in use, stop the running transforms before attempting deletion. Also, ensure the cluster health is green and there are no ongoing recovery or reindexing operations.
This guide will help you check for common problems that cause the log ” [{}] failed deleting old transform configurations. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[{}] failed deleting old transform configurations.” classname is TransformUpdater.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
config.getId();
ActionListener.wrap(r -> {
logger.trace("[{}] successfully deleted old transform configurations"; config.getId());
listener.onResponse(null);
}; e -> {
logger.warn(LoggerMessageFormat.format("[{}] failed deleting old transform configurations."; config.getId()); e);
listener.onResponse(null);
})
);
// If we failed to INDEX AND we created the destination index; the destination index will still be around
// This is a similar behavior to _start
