This cluster is used as build node only and because of async snapshots sometimes it fails build with
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Cannot delete indices that are being snapshotted: [[jobs_build_tests/gaC4OZjdTY60Rb4lqk1w5g]]. Try again after snapshot finishes or cancel the currently running snapshot."}],"type":"illegal_argument_exception","reason":"Cannot delete indices that are being snapshotted: [[jobs_build_tests/gaC4OZjdTY60Rb4lqk1w5g]]. Try again after snapshot finishes or cancel the currently running snapshot."},"status":400}
I had a look at the logging from the cluster mentioned. I don't see any snapshot failures, however I did see that you were able to delete the [jobs_build_tests/gaC4OZjdTY60Rb4lqk1w5g] index.
Do you have reason to believe that snapshotting is causing your cluster deeper problems?
there are NO cluster operation issues due snapshotting
cyclic build tasks (with Jenkins) fail when snapshot is running. Rather then adding more complexity to build (which does purge index on startup) I think its better to disable snapshots on that cluster
I hope this makes sense.
Please let me know if you have other ides to tackle this.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.