t;
> > >
> > > Analyzer analyzer = new StandardAnalyzer(Version.LUCENE_46);
> > > IndexWriterConfig iwc = new IndexWriterConfig(Version.LUCENE_46,
> > > analyzer);
> > >
> > >
> > > With this probably the line related to the co
gt; > > A little background of our experiment. We are storing lucene (version
> > > 4.6.0) on top of cassandra. We are using the demo IndexFiles.java from
> > the
> > > lucene with minor modification such that the directory used is
> reference
> > to
> > > the Cassand
; is done, and set forceMerge(1) and get the following exception.
> >
> >
> > BufferedIndexInput readBytes [ERROR] bufferStart = '0' bufferPosition =
> > '1024' len = '9252' after = '10276'
> > BufferedIndexInput readBytes [ERRO
BufferedIndexInput readBytes [ERROR] bufferStart = '0' bufferPosition =
> '1024' len = '9252' after = '10276'
> BufferedIndexInput readBytes [ERROR] length = '8192'
> caught a class java.io.IOException
> with message: background merge
x27;8192'
caught a class java.io.IOException
with message: background merge hit exception: _1(4.6):c10250
_0(4.6):c10355 _2(4.6):c10297 _3(4.6):c10217 _4(4.6):c8882 into _5
[maxNumSegments=1]
java.io.IOException: background merge hit exception: _1(4.6):c10250
_0(4.6):c10355 _2(4.6):c10297 _3(4
ssor.LogUpdateProcessor finish
INFO: {} 0 52334
2011/09/07 9:40:52 org.apache.solr.common.SolrException log
FATAL: java.io.IOException: background merge hit exception: _73ie:C290089
_73if:C34 _73ig:C31
_73ir:C356 into _73is [optimize] [mergeDocStores]
at org.apache.lucene.index.IndexWriter.optimize
On Sat, Sep 10, 2011 at 12:58 PM, Michael McCandless
wrote:
> On Fri, Sep 9, 2011 at 6:50 PM, Koji Sekiguchi wrote:
Also: what java version are they running? We added this check
originally as a workaround for a JRE bug... but usually when that bug
strikes the file size is very clos
On Fri, Sep 9, 2011 at 6:50 PM, Koji Sekiguchi wrote:
>>> Also: what java version are they running? We added this check
>>> originally as a workaround for a JRE bug... but usually when that bug
>>> strikes the file size is very close (like off by just 1 byte or 8
>>> bytes or something).
>>
>> I t
Also: what java version are they running? We added this check
originally as a workaround for a JRE bug... but usually when that bug
strikes the file size is very close (like off by just 1 byte or 8
bytes or something).
I think they are using 1.6, but I should ask the minor number.
Could you show
.update.processor.LogUpdateProcessor finish
INFO: {} 0 52334
2011/09/07 9:40:52 org.apache.solr.common.SolrException log
FATAL: java.io.IOException: background merge hit exception: _73ie:C290089
_73if:C34 _73ig:C31
_73ir:C356 into _73is [optimize] [mergeDocStores]
at org.apache.lucene.
ctUpdateHandler2 commit
> INFO: start
> commit(optimize=true,waitFlush=true,waitSearcher=true,expungeDeletes=false)
>
> :
>
> 2011/09/07 9:40:52 org.apache.solr.update.processor.LogUpdateProcessor finish
> INFO: {} 0 52334
> 2011/09/07 9:40:52 org.apache.solr.common.SolrExcepti
1/09/07 9:40:52 org.apache.solr.update.processor.LogUpdateProcessor finish
INFO: {} 0 52334
2011/09/07 9:40:52 org.apache.solr.common.SolrException log
FATAL: java.io.IOException: background merge hit exception: _73ie:C290089
_73if:C34 _73ig:C31
_73ir:C356 into _73is [optimize] [mergeDocSto
BTW if you have the CheckIndex output when you ran it on the two
failed indices, can you forward that?
Mike
On Thu, Jul 29, 2010 at 6:32 AM, Michael McCandless
wrote:
> On Wed, Jul 28, 2010 at 1:08 AM, David Sitsky wrote:
>> Incidentally.. this is what TerminateProcess does say from MSDN:
>>
>>
On Wed, Jul 28, 2010 at 1:08 AM, David Sitsky wrote:
> Incidentally.. this is what TerminateProcess does say from MSDN:
>
> TerminateProcess initiates termination and returns immediately. This
> stops execution of all threads within the process and requests
> cancellation of all pending I/O. The t
Incidentally.. this is what TerminateProcess does say from MSDN:
TerminateProcess initiates termination and returns immediately. This
stops execution of all threads within the process and requests
cancellation of all pending I/O. The terminated process cannot exit
until all pending I/O has been co
Hi Mike,
Definitely no OOME (or other critical errors), and if there were, we
would have terminated the program straight away.
Cheers,
David
On 28 July 2010 01:44, Michael McCandless wrote:
> Were there any exceptions during indexing, before the
> TerminateProcess() call? EG OOME?
>
> Mike
>
>
Were there any exceptions during indexing, before the
TerminateProcess() call? EG OOME?
Mike
On Tue, Jul 27, 2010 at 8:43 AM, Michael McCandless
wrote:
> On Mon, Jul 26, 2010 at 7:10 PM, David Sitsky wrote:
>> During processing.. there might be a number of reasons why we need to
>> shutdown th
On Mon, Jul 26, 2010 at 7:10 PM, David Sitsky wrote:
> During processing.. there might be a number of reasons why we need to
> shutdown the indexing process, but perhaps what is unusual is we call
> the win32 API TerminateProcess() call rather than System.exit(), for
> slightly obscure reasons. W
tected.
>>
>> So any ideas on what might have caused this in the first place?
>>
>> On 26 July 2010 16:58, David Sitsky wrote:
>>> As another data point, this happened on another index:
>>>
>>> java.io.IOException: background merge hit exception
1 broken segment containing 1 document detected.
>
> So any ideas on what might have caused this in the first place?
>
> On 26 July 2010 16:58, David Sitsky wrote:
>> As another data point, this happened on another index:
>>
>> java.io.IOException: background mer
her index:
>
> java.io.IOException: background merge hit exception: _17a:C1003710
> _18h:C66391 _1ct:C45384 _1wt:C104479 _1zo:C23469 _271:C58570
> _2dk:C53760 _2h5:C109879 _2ik:C7713 _2ii:C121 _2ij:C243 _2il:C124
> _2im:C122 _2in:C115 _2io:C138 _2ip:C131 _2iq:C116 _2ir:C141 _2is:C183
>
As another data point, this happened on another index:
java.io.IOException: background merge hit exception: _17a:C1003710
_18h:C66391 _1ct:C45384 _1wt:C104479 _1zo:C23469 _271:C58570
_2dk:C53760 _2h5:C109879 _2ik:C7713 _2ii:C121 _2ij:C243 _2il:C124
_2im:C122 _2in:C115 _2io:C138 _2ip:C131
tly appreciated.
>
> Is this possible this is a bug with 2.9.0?
>
> java.io.IOException: background merge hit exception: _8d:C110892
> _9s:C29548 _b7:C30930 _co:C20063 _e1:C43786 _fj:C102309 _gv:C67123
> _ia:C26329 _jr:C61859 _l5:C38116 _mj:C33069 _ny:C14417 _pe:C13849
> _qs:C21354
on a local RAID disk configuration on a Windows machine. Is there
anything we can do to somehow "recover" this index to make it useable?
Any help would be greatly appreciated.
Is this possible this is a bug with 2.9.0?
java.io.IOException: background merge hit exception: _8d:C110892
_
sure how could it get
corrupted. Here is the exception,
Caused by: java.io.IOException: background merge hit exception:
_io5:c66777491 _nh9:c10656736 _taq:c2021563 _s8m:c1421051
_uh5:c2065961 _r0y:c1124653 _s4s:c2477731 _t6w:c4340938 _ucx:c8018451
_xkb:c13842776 _xkd:c3394 _xke:c3379 _xkg:c1231
using Lucene 2.4.0.
There was no outage or system reboot - not sure how could it get
corrupted. Here is the exception,
Caused by: java.io.IOException: background merge hit exception:
_io5:c66777491 _nh9:c10656736 _taq:c2021563 _s8m:c1421051
_uh5:c2065961 _r0y:c1124653 _s4s:c2477731 _t6w:c434093
Hi,
We ran into the same issue (corrupted index) using Lucene 2.4.0.
There was no outage or system reboot - not sure how could it get
corrupted. Here is the exception,
Caused by: java.io.IOException: background merge hit exception:
_io5:c66777491 _nh9:c10656736 _taq:c2021563 _s8m:c1421051
_uh5
>
>
> It's very strange that CheckIndex -fix did not resolve the issue. After
> fixing it, if you re-run CheckIndex on the index do you still see that
> original one broken segment present? CheckIndex should have removed
> reference to that one segment.
>
I just ran it again, and it detected the
It's remotely possible you hit a JVM bug in the past and that caused the
corruption.
EG there is at least one JVM bug lurking that can affect Lucene (though
apparently with an OS-level fault):
https://issues.apache.org/jira/browse/LUCENE-1342
I don't know much about Amazon's elastic block stor
So my apologies for the duplicate comments, I went to go get proof of
duplicates and was confused as we apparently have duplicates across
different shards now in our distributed setup (a bug on our end.) I assumed
when I saw duplicates that it was the same problem as last time. Still
doesn't help m
:
> >
> >> It looks like your index has some kind of corruption. Were there any
> >> other
> >> exceptions prior to this one, or, any previous problems with the OS/IO
> >> system?
> >>
> >> Can you run CheckI
Also, this (Solr server going down during an add) should not be able to
cause this kind of corruption.
Mike
Yonik Seeley wrote:
> On Fri, Jan 2, 2009 at 3:47 PM, Brian Whitman wrote:
> > I will but I bet I can guess what happened -- this index has many
> duplicates
> > in it as well (same uniqu
On Fri, Jan 2, 2009 at 3:47 PM, Brian Whitman wrote:
> I will but I bet I can guess what happened -- this index has many duplicates
> in it as well (same uniqueKey id multiple times) - this happened to us once
> before and it was because the solr server went down during an add.
That should no lon
dex (java org.apache.lucene.index.CheckIndex to see
>> usage) and post the output?
>> Mike
>>
>> Brian Whitman wrote:
>>
>> > I am getting this on a 10GB index (via solr 1.3) during an optimize:
>> > Jan 2, 2009 6:51:52 PM org.apache.solr.common.SolrExcept
GB index (via solr 1.3) during an optimize:
> > Jan 2, 2009 6:51:52 PM org.apache.solr.common.SolrException log
> > SEVERE: java.io.IOException: background merge hit exception:
> _ks4:C2504982
> > _oaw:C514635 _tll:C827949 _tdx:C18372 _te8:C19929 _tej:C222
ing this on a 10GB index (via solr 1.3) during an optimize:
> Jan 2, 2009 6:51:52 PM org.apache.solr.common.SolrException log
> SEVERE: java.io.IOException: background merge hit exception: _ks4:C2504982
> _oaw:C514635 _tll:C827949 _tdx:C18372 _te8:C19929 _tej:C22201
> _1agw:C1717926
I am getting this on a 10GB index (via solr 1.3) during an optimize:
Jan 2, 2009 6:51:52 PM org.apache.solr.common.SolrException log
SEVERE: java.io.IOException: background merge hit exception: _ks4:C2504982
_oaw:C514635 _tll:C827949 _tdx:C18372 _te8:C19929 _tej:C22201 _1agw:C1717926
_1agz:C1 into
OK I found one path whereby optimize would detect that the
ConcurrentMergeScheduler had hit an exception while merging in a BG
thread, and correctly throw an IOException back to its caller, but
fail to set the root cause in that exception. I just committed it, so
it should be fixed in 2.
vivek sar wrote:
Thanks Mike for the insight. I did check the stdout log and found it
was complaining of not having enough disk space. I thought we need
only x2 of the index size. Our index size is 10G (max) and we had 45G
left on that parition - should it still complain of the space?
Is ther
gt;
> Mike
>
> On Sep 17, 2008, at 4:24 PM, vivek sar wrote:
>
>> Hi,
>>
>> We have been running Lucene 2.3 for last few months with our
>> application and all the sudden we have hit the following exception,
>>
>> java.lang.RuntimeException: java.io.IOExc
he sudden we have hit the following exception,
java.lang.RuntimeException: java.io.IOException: background
merge hit exception: _2uxy:c11345949 _2uxz:c150 _2uy0:c150 _2uy1:c150
_2uy2:c150 _2uy3:c150 _2uy4:c82 into _2uy5 [optimize]
I don't see any other error messages (or stacktrace) around this
Hi,
We have been running Lucene 2.3 for last few months with our
application and all the sudden we have hit the following exception,
java.lang.RuntimeException: java.io.IOException: background
merge hit exception: _2uxy:c11345949 _2uxz:c150 _2uy0:c150 _2uy1:c150
_2uy2:c150 _2uy3:c150
n records and after indexing 4 million record i got this
exception)
java.io.IOException: background merge hit exception: _8n:c7759352
_8o:c57658
_8p:c55810 into _8q [optimize]
please give me the solution.
--
View this message in context:
http://www.nabble.com/background-merge-hit-exception-tp184179
g wrote:
>
>>
>>
>>
>> Hi ALL ,
>> This is the exception raised when when am indexing the records (I
>> have 10
>> million records and after indexing 4 million record i got this
>> exception)
>>
>> java.io.IOException: background merge
ackground merge hit exception: _8n:c7759352
_8o:c57658
_8p:c55810 into _8q [optimize]
please give me the solution.
--
View this message in context:
http://www.nabble.com/background-merge-hit-exception-tp18417970p18417970.html
Sent from the Lucene - Java Users mailing list archiv
Hi ALL ,
This is the exception raised when when am indexing the records (I have 10
million records and after indexing 4 million record i got this exception)
java.io.IOException: background merge hit exception: _8n:c7759352 _8o:c57658
_8p:c55810 into _8q [optimize]
please give me the
46 matches
Mail list logo
