Briefly, this error occurs when two or more processes attempt to modify the same Elasticsearch alias simultaneously during a rollover operation. This can lead to data inconsistency or loss. To resolve this issue, you can implement a queue system to manage rollover requests, ensuring only one operation is performed at a time. Alternatively, you can use a lock mechanism to prevent concurrent modifications. Lastly, you can schedule rollovers at different times to avoid overlap.
This guide will help you check for common problems that cause the log ” Concurrent modification of alias [{}] during rollover ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, alias, indices.
Log Context
Log “Concurrent modification of alias [{}] during rollover” class name is TransportRolloverAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
public ClusterState execute(ClusterState currentState) throws Exception {
MetadataRolloverService.RolloverResult rolloverResult = rolloverService.rolloverClusterState(currentState;
rolloverRequest.getRolloverTarget(); rolloverRequest.getNewIndexName();
rolloverRequest.getCreateIndexRequest(); metConditions; false; false);
if (rolloverResult.sourceIndexName.equals(sourceIndexName) == false) {
throw new ElasticsearchException("Concurrent modification of alias [{}] during rollover";
rolloverRequest.getRolloverTarget());
}
return rolloverResult.clusterState;
}
