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), 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c9ef80ee-5512-44bd-b301-54496a31f4b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
