lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Williams <ch...@manawiz.com>
Subject Re: After kill -9 index was corrupt
Date Mon, 11 Sep 2006 19:56:14 GMT
robert engels wrote on 09/11/2006 07:34 AM:
> A kill -9 should not affect the OS's writing of dirty buffers
> (including directory modifications). If this were the case, massive
> system corruption would almost always occur every time a kill -9 was
> used with any program.
>
> The only thing a kill -9 affects is user level buffering. The OS
> always maintains a consistent view of directory modifications and or
> file modification that were requesting by programs.
>
> This entire discussion is pointless.
>
Thanks everyone for your analysis.  It appears I do not have any
explanation.  In my case, the process was in gc-limbo due to the memory
leak and having butted up against its -Xmx.  The process was kill -9'd
and then restarted.  The OS never crashed.  The server this is on is
healthy; it has been used continually since this happened without being
rebooted and no file system or any other issues.  When the process was
killed, one thread was merging segments as part of flushing the ram
buffer while closing the index, due to the prior kill -15.  When Lucene
restarted, the segments file contained a segment name for which there
were no corresponding index data files.

Chuck


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message