The description here sounds exactly like what we were seeing before
LUCENE-669 was fixed -- from his writeup it doesn't look like he
tested with Lucene 2.2 to see if the problem went away. I think it
very well may.
That said, as a precaution, maybe we should no longer call close() on
o
On Wed, Jul 23, 2008 at 7:47 PM, Jamie <[EMAIL PROTECTED]> wrote:
> Could this error be the result of the bad file descriptor close bug as
> described in
> http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml.
Hmmm, that's an interesting read.
Seems like maybe we should kill most
I think that is the best strategy at this point.
The head of 2.3 has a workaround (that so far *seems* to work around)
for that JRE bug.
Mike
Jamie wrote:
Hi
I feel like we are having to tip toe across JRE bugs to get this to
work right. I am definitely not pointing fingers, since the
Hi
I feel like we are having to tip toe across JRE bugs to get this to work
right. I am definitely not pointing fingers, since the issues and their
resolutions are complex but
I would appreciate some insight on the most reliable combination of JRE
6 and Lucene. I cannot downgrade the JRE to 5
Hi All,
I found something interesting
Could this error be the result of the bad file descriptor close bug as
described in
http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml.
This would definitely fit the description since this happened on JRE
1.6u3 apparently, up
This log looks healthy.
Mike
Jamie wrote:
Hi
The index log file is attached. Many thanks in advance for your
consideration!
Jamie
Jamie wrote:
Wasn't there some index corruption issue with Java 1.6 and Lucene
2.3.2? Could this be the problem?
Jamie
Jamie wrote:
Hi Matthew
Thanks
Mindaugas ?ak?auskas wrote:
On Wed, Jul 23, 2008 at 5:46 PM, Matthew Hall <[EMAIL PROTECTED]
> wrote:
<..>As for the jave 1.6 lucene 2.3.2 index corruption issue <..>
Correct me if I'm wrong, but doesnt' the particular Sun bug [1] only
manifests itself if -Xbatch option is used? Also, the ex
On Wed, Jul 23, 2008 at 5:46 PM, Matthew Hall <[EMAIL PROTECTED]> wrote:
> <..>As for the jave 1.6 lucene 2.3.2 index corruption issue <..>
Correct me if I'm wrong, but doesnt' the particular Sun bug [1] only
manifests itself if -Xbatch option is used? Also, the exceptions
mentioned in LUCENE-1282
org.apache.lucene.index.CheckIndex checks the index for corruption,
and (if you specify -fix) will "repair" the index by removing any
segments that have problems.
There is this issue with Java 1.6.0_0{4,5}:
https://issues.apache.org/jira/browse/LUCENE-1282
Sun is making progress on fi
I'm not sure which file in particular would be the one
corrupter/missing, which is why I suggested looking at the index with luke.
As for the jave 1.6 lucene 2.3.2 index corruption issue, I'm not 100%
familiar with the details on that one, but as a quick test, you should
be able to swap to a 1
Hi
The index log file is attached. Many thanks in advance for your
consideration!
Jamie
Jamie wrote:
Wasn't there some index corruption issue with Java 1.6 and Lucene
2.3.2? Could this be the problem?
Jamie
Jamie wrote:
Hi Matthew
Thanks in advance for the suggestion.
Which file do you
Wasn't there some index corruption issue with Java 1.6 and Lucene 2.3.2?
Could this be the problem?
Jamie
Jamie wrote:
Hi Matthew
Thanks in advance for the suggestion.
Which file do you think does not exist?
This is what we have:
_15zw.cfs _19od.cfs _1a5d.cfs _1a7n.cfs _1ahf.cfs _1ahh
Hi Matthew
Thanks in advance for the suggestion.
Which file do you think does not exist?
This is what we have:
_15zw.cfs _19od.cfs _1a5d.cfs _1a7n.cfs _1ahf.cfs _1ahh.cfs
_qzl.cfs segments.gen
_1993.cfs _1a0w.cfs _1a7c.cfs _1a9m.cfs _1ahg.cfs _1ahi.cfs
segments_158j
Aside
Did you try to open the index using Luke?
Luke will be able to tell you whether or not the index is in fact
corrupted, but looking at your stack trace, it almost looks like the
file.. simply isn't there?
Matt
Jamie wrote:
Hi Everyone
I am getting the the following error when executing Hi
Hi Everyone
I am getting the the following error when executing Hits hits =
searchers.search(query, queryFilter, sort):
18007414-java.io.IOException: Bad file descriptor
18007455- at java.io.RandomAccessFile.seek(Native Method)
18007504- at
org.apache.lucene.store.FSDirectory$FSI
15 matches
Mail list logo
