lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Keegan <peterlkee...@gmail.com>
Subject Re: IO exception during merge/optimize
Date Mon, 26 Oct 2009 00:54:08 GMT
The environment involves a lot of I/O from merge/optimize operations on
multiple indexes (shards) on one server.
I will try running the indexers in console mode, where I would expect to see
all errors and exceptions.

Peter


On Sun, Oct 25, 2009 at 8:40 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:

> Hmm, if you got no exception whatsoever, something more fundamental
> seems to be wrong w/ the error reporting when running as a windows
> service.  Maybe make a simple Java test program that throws an
> exception and try to get that working?
>
> Mike
>
> On Sun, Oct 25, 2009 at 7:35 PM, Peter Keegan <peterlkeegan@gmail.com>
> wrote:
> >>Did you get any traceback printed at all?
> > no, only what I reported.
> >
> >>Did you see any BG thread exceptions on wherever your System.err is
> > directed to?
> > The jvm was running as a windows service, so output to System.err may
> have
> > gone to the bit bucket.
> > That's an interesting point, though.
> >
> > Peter
> >
> >
> > On Sun, Oct 25, 2009 at 8:47 AM, Michael McCandless <
> > lucene@mikemccandless.com> wrote:
> >
> >> Hmm... Lucene tries to catch the original cause (from the BG thread
> >> doing the merge) and forward it to the main thread waiting for
> >> optimize to complete.
> >>
> >> Did you get any traceback printed at all?  It should include one
> >> traceback into Lucene's optimized method, and then another (under
> >> "caused by") showing the exception from the BG merge thread.
> >>
> >> Did you see any BG thread exceptions on wherever your System.err is
> >> directed to?
> >>
> >> Mike
> >>
> >> On Sat, Oct 24, 2009 at 5:21 PM, Peter Keegan <peterlkeegan@gmail.com>
> >> wrote:
> >> > btw, this is with Lucene 2.9
> >> >
> >> > On Sat, Oct 24, 2009 at 5:20 PM, Peter Keegan <peterlkeegan@gmail.com
> >> >wrote:
> >> >
> >> >> I'm sometimes seeing the following exception from an operation that
> does
> >> a
> >> >> merge and optimize:
> >> >>  java.io.IOException: background merge hit exception: _0:C1082866
> _1:C79
> >> >> into _2 [optimize] [mergeDocStores]
> >> >> I'm pretty sure that it's caused by a temporary low disk space
> >> condition,
> >> >> but I'd like to be able to confirm this. It would be nice to have the
> >> java
> >> >> exception included in the Lucene exception. Any way to get this?
> >> >>
> >> >> Peter
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: java-user-help@lucene.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message