# Curator 4.2.6 showing Concurrent Snapshot Execution Exception? **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2017, 7:11am UTC](https://discuss.elastic.co/t/curator-4-2-6-showing-concurrent-snapshot-execution-exception/88981 "2017-06-12T07:11:51Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Yaswanth](https://avatars.discourse-cdn.com/v4/letter/y/94ad74/32.png) [@Yaswanth](https://discuss.elastic.co/u/Yaswanth)\ **Post date:** [June 12, 2017, 7:11am UTC](https://discuss.elastic.co/t/curator-4-2-6-showing-concurrent-snapshot-execution-exception/88981/1 "2017-06-12T07:11:52Z")
Hi, Elasticsearch 2.4.1 My environment has 3 VM's that is hosted on azure and in all the VM's i had installed curator and they are `master enabled` and in every week i am running 3 snapshots at particular time (9.00AM) . Upto yesterday i didnt shown any error but today i had seeing following ERROR and shocked to see no snapshot has been created. ``` [2017-06-11 12:00:03,714][WARN][snapshots] [data-1] [backup][snapshot-2017-06-11] failed to create snapshot ConcurrentSnapshotExecutionException[[backup:snapshot-2017-06-11] a snapshot is already running] at org.elasticsearch.snapshots.SnapshotsService$1.execute(SnapshotsService.java:209) at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45) at org.elasticsearch.cluster.service.InternalClusterService.runTasksForExecutor(InternalClusterService.java:468) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:772) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:194) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) [2017-06-11 12:00:03,715][WARN][rest.suppressed] path: /_snapshot/backup/snapshot-2017-06-11, params: {repository=backup, wait_for_completion=true, snapshot=snapshot-2017-06-11} ConcurrentSnapshotExecutionException[[backup:snapshot-2017-06-11] a snapshot is already running] at org.elasticsearch.snapshots.SnapshotsService$1.execute(SnapshotsService.java:209) at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45) at org.elasticsearch.cluster.service.InternalClusterService.runTasksForExecutor(InternalClusterService.java:468) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:772) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:194) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) [2017-06-11 12:00:04,169][WARN][snapshots] [data-1] [backup][snapshot-2017-06-11] failed to create snapshot ConcurrentSnapshotExecutionException[[backup:snapshot-2017-06-11] a snapshot is already running] at org.elasticsearch.snapshots.SnapshotsService$1.execute(SnapshotsService.java:209) at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45) at org.elasticsearch.cluster.service.InternalClusterService.runTasksForExecutor(InternalClusterService.java:468) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:772) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadP ``` It is showing snapshot is already running if this is the case then this error should have to error long before when i started running 3 snapshots at the same time but it came yesterday only . Why? Did `wait_for_completion:false` will avoid these type of snapshots failure? Thanks ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [June 15, 2017, 2:36am UTC](https://discuss.elastic.co/t/curator-4-2-6-showing-concurrent-snapshot-execution-exception/88981/2 "2017-06-15T02:36:14Z")
Snapshots cannot run concurrently. Because Elasticsearch must pause segment merging of the segments being snapshotted, and this consumes extra resources and overhead, Elasticsearch does not allow concurrent snapshots. I believe your other question regarding this has been answered elsewhere. ---
**Author:** ![Yaswanth](https://avatars.discourse-cdn.com/v4/letter/y/94ad74/32.png) [@Yaswanth](https://discuss.elastic.co/u/Yaswanth)\ **Post date:** [June 15, 2017, 2:38am UTC](https://discuss.elastic.co/t/curator-4-2-6-showing-concurrent-snapshot-execution-exception/88981/3 "2017-06-15T02:38:53Z")
Thanks @theuntergeek > [@theuntergeek](#): > > I believe your other question regarding this has been answered elsewhere Yeah it is 😄 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 13, 2017, 2:39am UTC](https://discuss.elastic.co/t/curator-4-2-6-showing-concurrent-snapshot-execution-exception/88981/4 "2017-07-13T02:39:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.