Thank you very much for the response!
I've created a bug and added all relevant details there:
https://issues.apache.org/jira/browse/LUCENE-9867
Please let me know if you have any questions, or if any other information
would be helpful.
--
Regards,
Alexander L
On Wed, Mar 24, 2021 at 10:09 AM
+1, this sounds like a bad bug in Lucene! We try hard to test for and
prevent such bugs!
As long as you succeeded in at least one commit since creating the
index before you hit the disk full, restarting Lucene on the index should
have recovered from that last successful commit.
How often do you
On Wed, Mar 24, 2021 at 1:41 AM Alexander Lukyanchikov <
alexanderlukyanchi...@gmail.com> wrote:
> Hello everyone,
>
> Recently we had a failed segment merge caused by "No space left on device".
> After restart, Lucene failed with the CorruptIndexException.
> The expectation was that Lucene
Hello everyone,
Recently we had a failed segment merge caused by "No space left on device".
After restart, Lucene failed with the CorruptIndexException.
The expectation was that Lucene automatically recovers in such
case, because there was no succesul commit. Is it a correct assumption, or
I am
