Resolved: https://github.com/elasticsearch/elasticsearch/issues/7386
For posterity: if you nuke the contents of your node's disk after stopping Elasticsearch 1.2 but before starting Elasticsearch 1.3 then you won't end up with too much data that can't be cleared. The more nodes you upgrade the more shards you'll be able to delete any way. <https://github.com/s1monw> On Thu, Aug 21, 2014 at 2:37 PM, Nikolas Everett <[email protected]> wrote: > Moving this to https://github.com/elasticsearch/elasticsearch/issues/7386 > . Its a bug, but I have no idea what caused it. > > Side note: after digging through the code for two hours I can't find > anything that sweeps up files/directories/local shard storage that is > unused. I see lots of deletes done in finally blocks but I'm not sure how > I got in this state nor if there is something designed to dig me out of it. > -- 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/CAPmjWd2-fEGDd0gChr7WQvj4ZHfP_6SX59yV8AL9jYZLW4QJ8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
