Sorry,I can't reproduce in local...
"If at any time you accidentally had two writers open on the same
index, it could have created this corruption. "
I use singleton to create/get IndexWriter ,and change LockFactory to
SimpleFSLockFactory (NativeFSLockFactory before) .Maybe a long time it was
run
https://issues.apache.org/jira/browse/SOLR-4032
-Original message-
> From:Mark Miller
> Sent: Sat 03-Nov-2012 14:20
> To: java-user@lucene.apache.org
> Subject: Re: "read past EOF" when merge
>
> Can you file a JIRA Markus? This is probably related
a:932)
>
>
> Markus
>
> -Original message-----
>> From:Michael McCandless
>> Sent: Fri 02-Nov-2012 11:46
>> To: java-user@lucene.apache.org
>> Subject: Re: "read past EOF" when merge
>>
>> Are you able to reproduce the corruption
No this is not using NFS but EXT3 on SSD.
Thanks
-Original message-
> From:Michael McCandless
> Sent: Fri 02-Nov-2012 16:22
> To: java-user@lucene.apache.org
> Subject: Re: "read past EOF" when merge
>
> On Fri, Nov 2, 2012 at 6:53 AM, Markus Jelsma
&
On Fri, Nov 2, 2012 at 6:53 AM, Markus Jelsma
wrote:
> Hi,
>
> For what it's worth, we have seen similar issues with Lucene/Solr from this
> week's trunk. The issue manifests itself when it want to replicate. The
> servers have not been taken offline and did not crash when this happenend.
>
> 20
nHandler$3.write(ReplicationHandler.java:932)
Markus
-Original message-
> From:Michael McCandless
> Sent: Fri 02-Nov-2012 11:46
> To: java-user@lucene.apache.org
> Subject: Re: "read past EOF" when merge
>
> Are you able to reproduce the corruption?
&
Are you able to reproduce the corruption?
If at any time you accidentally had two writers open on the same
index, it could have created this corruption.
Writing to an index over NFS ought to be OK, however, it's not well
tested. You should use SimpleFSLockFactory (not the default
NativeFSLockFac
oh ,thx,I don't know CheckIndex before...and I use to fix my error index,it
is OK...
I use NFS to share my index,and no change to the LogFactory.
How could I avoid this problem,and not only fix after it was broken
suddenly?
--
View this message in context:
http://lucene.472066.n3.nabble.com/rea
Well somehow you have a corrupt index. I'd be very interested in how
that happened :)
You need to run CheckIndex with -fix (it's a command-line tool, too)
to remove that bad segment else some search will eventually hit an
exception on that segment ... and merging can never be done with that
segme
Hi Mike,
I got the same problem as above. My search project is running on two
servers(1 master for index writing and reading and 1 slaver for index
reading), and the master server writes the index into a seperate disk(not
belong to master) which is shared by the slaver. I have never changed the
Loc
Run CheckIndex on the index?
What filesystem is IndexWriter using to write to the index...?
Have you changed the LockFactory on the Directory?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Oct 30, 2012 at 11:27 PM, superruiye wrote:
> The exception "read past EOF" Bothering me a lon
11 matches
Mail list logo