Bad Things Can Happen. Solr (well, Lucene in this case) tries very
hard to keep disk full operations from having repercussions., but it's
kind of like OOMs. What happens next?
It's not so much the merge/optimize, but what happens in the future
when the _next_ segment is written...
The merge or op
Hi all, I am curious to know what happens when solr begins a merge/optimize
operation, but then runs out of physical disk space. I havent had the
chance to try this out yet but I was wondering if anyone knows what the
underlying codes response to the situation would be if it happened. Thanks
-Dav
