You need to make sure your storage does not lie in response to an fsync
command. If it does (most commercial stuff does), you cannot guaranty no
corruption. Search google for "your harddrive lies to you" or something.
It shouldnt be that hard to take the patch from the issue and apply it
to a checked out version of 2.3 right? I don't think it relies on other
2.4 stuff as there isnt much of it yet.
Simon Wistow wrote:
On Wed, Feb 27, 2008 at 09:38:55AM -0500, Michael McCandless said:
When you previously saw corruption was it due to an OS or machine
crash (or power cord got pulled)? If so, you were likely hitting
LUCENE-1044, which is fixed on the trunk version of Lucene (to be 2.4
at some point) but is not fixed in 2.3.
Yes - it's power outages and other unnatural events (sysadmins
accidentally kill -9ing the process) that caused it.
What's the chances of me backporting the fix to 2.3 or should I just
wait for 2.4?
Come 2.4 is my buffering to RAM redundant?
Thanks,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
