Watcher VersionConflictEngineException

I am receiving alerts of the following type on every execution of a watch :

[.watches/i29-EeXVQsO4S8rDpGWRqw][[.watches][0]] VersionConflictEngineException[[watch][my_watch]: version conflict, current version [73048] is different than the one provided [73047]] at org.elasticsearch.index.engine.Engine.getFromSearcher( at org.elasticsearch.index.engine.InternalEngine.get( at org.elasticsearch.index.shard.IndexShard.get( at org.elasticsearch.index.get.ShardGetService.innerGet( at org.elasticsearch.index.get.ShardGetService.get( at org.elasticsearch.action.update.UpdateHelper.prepare( at org.elasticsearch.action.update.TransportUpdateAction.shardOperation( at org.elasticsearch.action.update.TransportUpdateAction.shardOperation( at org.elasticsearch.action.update.TransportUpdateAction.shardOperation( at$ShardTransportHandler.messageReceived( at$ShardTransportHandler.messageReceived( at org.elasticsearch.transport.TransportRequestHandler.messageReceived( at$ProfileSecuredRequestHandler.messageReceived( at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived( at org.elasticsearch.transport.TcpTransport$RequestHandler.doRun( at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun( at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at

I have found the following explanation on the board :

"so what happens here, is that each Watch stores itself after it has run. In order to store versioning is used. What happened here specifically was the fact, that a watch was loaded together with its version information, then executed and then this version was specified to store again. However this failed, because another process already did exactly the same. So somehow you triggered the same watch twice in your cluster."

So possibly the Watch executed multiple times at a point where the master node switched nodes,
however I am unclear as to what the solution is ? Does the Watch need to be deleted and recreated to solve the issue, or is there a way to "reset" the versioning to make it correct ? Also I can't seem to find exactly where the versioning information is stored.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.