# DELETE snapshot request (which was long-running and had not yet completed) is hung **URL:** \ **Category:** Elasticsearch\ **Created:** [March 10, 2014, 8:39am UTC](https://discuss.elastic.co/t/delete-snapshot-request-which-was-long-running-and-had-not-yet-completed-is-hung/16259 "2014-03-10T08:39:24Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Swaroop\_CH](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@Swaroop\_CH](https://discuss.elastic.co/u/Swaroop_CH)\ **Post date:** [March 10, 2014, 8:39am UTC](https://discuss.elastic.co/t/delete-snapshot-request-which-was-long-running-and-had-not-yet-completed-is-hung/16259/1 "2014-03-10T08:39:24Z")
Hi, I had started a snapshot request on a freshly-indexed ES 1.0.1 cluster with cloud plugin installed, but unfortunately the EC2 access keys configured did not have S3 permissions, so ES was in a weird state, so I sent a DELETE snapshot request and it's stuck for more than a couple of hours, any advice on what to do here to cleanup the snapshot request? Logs don't reveal anything relevant. Regards, Swaroop -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/531801394440764%40web11j.yandex.ru](https://groups.google.com/d/msgid/elasticsearch/531801394440764%40web11j.yandex.ru). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [March 10, 2014, 12:10pm UTC](https://discuss.elastic.co/t/delete-snapshot-request-which-was-long-running-and-had-not-yet-completed-is-hung/16259/2 "2014-03-10T12:10:09Z")
That's strange. Wrong S3 permissions should have caused it to failed immediately. Could you provide any more details about the permissions, so I can reproduce it? Meanwhile, restarting the nodes where primary shards of the stuck index are located is the only option that I can think of. We are working on improving the performance of snapshot cancelation ([Improve speed of running snapshot cancelation by imotov · Pull Request #5244 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/5244)), but it didn't make it to a release yet. On Monday, March 10, 2014 4:39:24 AM UTC-4, Swaroop wrote: > Hi, > > I had started a snapshot request on a freshly-indexed ES 1.0.1 cluster > with cloud plugin installed, but unfortunately the EC2 access keys > configured did not have S3 permissions, so ES was in a weird state, so I > sent a DELETE snapshot request and it's stuck for more than a couple of > hours, any advice on what to do here to cleanup the snapshot request? Logs > don't reveal anything relevant. > > Regards, > Swaroop -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Swaroop\_CH](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@Swaroop\_CH](https://discuss.elastic.co/u/Swaroop_CH)\ **Post date:** [March 11, 2014, 5:44am UTC](https://discuss.elastic.co/t/delete-snapshot-request-which-was-long-running-and-had-not-yet-completed-is-hung/16259/3 "2014-03-11T05:44:00Z")
Hi Igor, It seems that the S3 bucket had "PUT only permissions". Regards, Swaroop 10.03.2014, 17:40, "Igor Motov" \: > That's strange. Wrong S3 permissions should have caused it to failed immediately. Could you provide any more details about the permissions, so I can reproduce it? Meanwhile, restarting the nodes where primary shards of the stuck index are located is the only option that I can think of. We are working on improving the performance of snapshot cancelation ([https://github.com/elasticsearch/elasticsearch/pull/5244](https://github.com/elasticsearch/elasticsearch/pull/5244)), but it didn't make it to a release yet. > > On Monday, March 10, 2014 4:39:24 AM UTC-4, Swaroop wrote: > > > Hi, > > > > I had started a snapshot request on a freshly-indexed ES 1.0.1 cluster with cloud plugin installed, but unfortunately the EC2 access keys configured did not have S3 permissions, so ES was in a weird state, so I sent a DELETE snapshot request and it's stuck for more than a couple of hours, any advice on what to do here to cleanup the snapshot request? Logs don't reveal anything relevant. > > > > Regards, > > > > Swaroop > > -- > > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com?utm_medium=email&utm_source=footer). > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1015081394516640%40web27h.yandex.ru](https://groups.google.com/d/msgid/elasticsearch/1015081394516640%40web27h.yandex.ru?utm_medium=email&utm_source=footer). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [March 18, 2014, 12:48am UTC](https://discuss.elastic.co/t/delete-snapshot-request-which-was-long-running-and-had-not-yet-completed-is-hung/16259/4 "2014-03-18T00:48:00Z")
Hi Swaroop, I tried to reproduce it, but in my case snapshot failed with AccessDenied almost immediately after I started it. Any other pointers besides PUT only permissions? On Tuesday, March 11, 2014 1:44:00 AM UTC-4, Swaroop wrote: > Hi Igor, > > It seems that the S3 bucket had "PUT only permissions". > > Regards, > Swaroop > > 10.03.2014, 17:40, "Igor Motov" \<[imo...@gmail.com](mailto:imo...@gmail.com) \\>: > > That's strange. Wrong S3 permissions should have caused it to failed > immediately. Could you provide any more details about the permissions, so I > can reproduce it? Meanwhile, restarting the nodes where primary shards of > the stuck index are located is the only option that I can think of. > > We are working on improving the performance of snapshot cancelation ( > [Improve speed of running snapshot cancelation by imotov · Pull Request #5244 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/5244)), but it didn't > make it to a release yet. > > On Monday, March 10, 2014 4:39:24 AM UTC-4, Swaroop wrote: > > Hi, > > I had started a snapshot request on a freshly-indexed ES 1.0.1 cluster > with cloud plugin installed, but unfortunately the EC2 access keys > configured did not have S3 permissions, so ES was in a weird state, so I > sent a DELETE snapshot request and it's stuck for more than a couple of > hours, any advice on what to do here to cleanup the snapshot request? Logs > don't reveal anything relevant. > > Regards, > Swaroop > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5eb27214-a53e-40a6-8ce4-29a312df0b63%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5eb27214-a53e-40a6-8ce4-29a312df0b63%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:42am UTC](https://discuss.elastic.co/t/delete-snapshot-request-which-was-long-running-and-had-not-yet-completed-is-hung/16259/5 "2017-07-06T01:42:39Z")