Elasticsearch start failure related to snapshot reconfigure

Elasticsearch 2.3, single server, Centos 7
The server used to store snapshots was lost. Tried to reconfigure for new backup server and ended up here.
Is there a way to recover ?

[2016-12-12 11:02:29,793][WARN ][rest.suppressed ] /_snapshot/es-backup Params: {repository=es-backup}
java.lang.IllegalStateException: trying to modify or unregister repository that is currently used
at org.elasticsearch.repositories.RepositoriesService.ensureRepositoryNotInUse(RepositoriesService.java:417)
at org.elasticsearch.repositories.RepositoriesService.access$000(RepositoriesService.java:55)
at org.elasticsearch.repositories.RepositoriesService$1.execute(RepositoriesService.java:108)
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)

[2016-12-12 11:39:04,281][WARN ][rest.suppressed ] /_snapshot/es-backup/snapshot_2016-11-30-08:06:36 Params: {repository=es-backup, snapshot=snapshot_2016-11-30-08:06:36}
ConcurrentSnapshotExecutionException[[es-backup:snapshot_2016-11-30-08:06:36] another snapshot is currently running cannot delete]
at org.elasticsearch.snapshots.SnapshotsService$7.execute(SnapshotsService.java:886)
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)
[2016-12-12 11:40:18,637][INFO ][node ] [Ogre] stopping ...
[2016-12-12 11:40:19,074][INFO ][node ] [Ogre] stopped
[2016-12-12 11:40:19,074][INFO ][node ] [Ogre] closing ...
[2016-12-12 11:40:29,091][INFO ][node ] [Ogre] closed

This has been resolved. The elasticsearch config file data path entry had become set to snapshot NFS share instead of actual db data.

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