Re: CorruptIndexException with some versions of java

2008-03-24 Thread Michael McCandless
Spookily, I believe this is in fact some sort of JVM hotspot compiler bug. Adding -Xbatch (forces up-front compilation) prevents (works around) the problem. I added a counter, to IndexOutput, of total bytes written, and then in SegmentMerger.mergeFields, I added an assert that the #docs

Re: CorruptIndexException with some versions of java

2008-03-19 Thread Yonik Seeley
On Wed, Mar 19, 2008 at 1:18 PM, Michael McCandless <[EMAIL PROTECTED]> wrote: > I'm CC'ing java-dev. To sum up: sometimes when we merge fields, the > fdx file ends up exactly one document too short. In adding numerous > asserts around this code in SegmentMerger.java, insanely, somehow the > c

Re: CorruptIndexException with some versions of java

2008-03-19 Thread Michael McCandless
Hi Ian, Can you try this patch? Grasping at straws at this point, trying to isolate where the JVM fails us... I'm CC'ing java-dev. To sum up: sometimes when we merge fields, the fdx file ends up exactly one document too short. In adding numerous asserts around this code in SegmentMerge