lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lucas F. A. Teixeira" <lucas.teixe...@accurate.com.br>
Subject Re: Index "corruption" makes it return a different result
Date Thu, 27 Mar 2008 12:09:34 GMT
I see...

I think we will CheckIndex before opening it. With fix option set to 
true. If the fix is needed, we will lose some entries, but the index 
will not be corrupted. We can alarm this to generate another index, and 
replace the missed entries one.

Thanks everybody, if I get any other clue about how those logs got 
there, I'll report.

Thanks Michael for your support!

[]s,

Lucas

Michael McCandless wrote:
> [Lucas sent me a zip of the index - thanks!]
>
> I ran CheckIndex on the index and it said this on your _al1 segment:
>
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1000
> 	at org.apache.lucene.util.BitVector.get(BitVector.java:72)
> 	at org.apache.lucene.index.SegmentTermDocs.next(SegmentTermDocs.java:120)
> 	at org.apache.lucene.index.SegmentTermPositions.next(SegmentTermPositions.java:95)
> 	at org.apache.lucene.index.CheckIndex.check(CheckIndex.java:205)
> 	at org.apache.lucene.index.CheckIndex.main(CheckIndex.java:382)
>
> I unpacked the CFS file and sure enough the file _al1.frq, which
> holds the frequency of each term in each doc, was somehow modified: it
> had 78 of those log lines (8148 bytes) inserted in the front.  When I
> removed those lines then CheckIndex runs fine.
>
> This is very odd.  Somehow your app server modified the frq file
> before it was added to the CFS file.  Very strange.
>
> Mike
>
> Lucas F. A. Teixeira <lucas.teixeira@accurate.com.br> wrote:
>   
>> 100% Impossible...
>>
>>  My index has 1 xml, 3 number fields, 1 aphanumeric field. *always*
>>
>>  :-)
>>
>>
>>
>>  Lucas
>>
>>
>>
>>  Michael McCandless wrote:
>>  >
>>  > OK.
>>  >
>>  > I would recommend upgrading to 2.3.1.  There were some corruption
>>  > issues with term vectors that could cause the wrong document's term
>>  > vectors to come back.
>>  >
>>  > That screen shot is spooky!  Is it possible that one of the documents
>>  > you indexed had that content?  (It could simply be a stored field).
>>  >
>>  > Mike
>>  >
>>  > Lucas F. A. Teixeira wrote:
>>  >> Thanks Michael!
>>  >>
>>  >> Lucene version: 2.3.0
>>  >>
>>  >> Here is some screenshot of editing the cfs file:
>>  >> http://img296.imageshack.us/my.php?image=indexow4.jpg
>>  >>
>>  >> Take a look!
>>  >>
>>  >> []s,
>>  >>
>>  >> Lucas
>>  >>
>>  >> Michael McCandless wrote:
>>  >>>
>>  >>> OK I think I follow now.
>>  >>>
>>  >>> Which version of Lucene was this?
>>  >>>
>>  >>> If it's not too large, can you post the CFS file that got mixed up?
>>  >>> Be sure to cc me directly on the mail because the mailing list
>>  >>> software removes attachments.
>>  >>>
>>  >>> Mike
>>  >>>
>>  >>> Lucas F. A. Teixeira wrote:
>>  >>>> This is just one of the index files.
>>  >>>>
>>  >>>> As I said, the local disk where the index is generated, it's not
>>  >>>> full, the full disk it's the shared storage where my application
>>  >>>> server store its logs.
>>  >>>> When this disk hitted 100%, all the indexing process stop (of
>>  >>>> course, all the processing instances of this managed server stopped).
>>  >>>>
>>  >>>> The "thing" is that the index was not corrupted, one of the index
>>  >>>> files has these log messages from my application server inside
it,
>>  >>>> problably a JVM problem on mixing two IO buffers when one of them
>>  >>>> coudn't flush (the logs partition). For me it would be normal if
it
>>  >>>> causes index corruption... :-)
>>  >>>>
>>  >>>> The second and most weird thing it's that my clients application
>>  >>>> just read the index, and did some queries on it, always returning
>>  >>>> different (but consistent) results.
>>  >>>>
>>  >>>> I tried to edit the index file, and remove the application server
>>  >>>> logs that was inside it, and after that?? Index Corrupted
>>  >>>> Exception! :-)
>>  >>>>
>>  >>>> Wow!
>>  >>>>
>>  >>>> I think this issue involves more stuff than just lucene... I had
>>  >>>> some problems in my JVM IO buffer handling of course. But my
>>  >>>> point(s) is the both above... ;-)
>>  >>>>
>>  >>>> []s,
>>  >>>>
>>  >>>> Lucas
>>  >>>>
>>  >>>>
>>  >>>>
>>  >>>>
>>  >>>> Michael McCandless wrote:
>>  >>>>>
>>  >>>>> I couldn't quite follow the part about "_al1.cfs".
>>  >>>>>
>>  >>>>> It sounds like your indexing process hit a disk full event,
that
>>  >>>>> led to this error? Can you post the full exception(s) from
the
>>  >>>>> disk full?
>>  >>>>>
>>  >>>>> Which version of Lucene are you using?
>>  >>>>>
>>  >>>>> Mike
>>  >>>>>
>>  >>>>> Lucas F. A. Teixeira wrote:
>>  >>>>>> Hello all!
>>  >>>>>>
>>  >>>>>> I had a problem this week, and I like to share with you
all.
>>  >>>>>> My weblogic server that generate my index hrows its logs
in a
>>  >>>>>> shared storage. During my indexing process (SOLR+Lucene),
this
>>  >>>>>> shared storage became 100% full, and everything collapsed
(all
>>  >>>>>> servers that uses this shared storage). But my index (that
is
>>  >>>>>> generated in the local filesystem, just "grabbed" some
logs of
>>  >>>>>> the server (who knows weblogic knows the managed server
>>  >>>>>> accesslog, that's the guy) from the buffer (my supposition),
and
>>  >>>>>> put inside my index files! Take a look how my "_al1.cfs"
became
>>  >>>>>> between some binary parts of the file:
>>  >>>>>>
>>  >>>>>> 2008-03-19    -    02:31:03    -    [ip]    -    POST 
  -
>>  >>>>>> 200    -    /AcomProductSyncServiceWeb/AcomProductSyncService
>>  >>>>>> 2008-03-19    -    02:31:03    -    [ip]    -    POST 
  -
>>  >>>>>> 200    -    /AcomProductSyncServiceWeb/AcomProductSyncService
>>  >>>>>> 2008-03-19    -    02:31:04    -    [ip]    -    POST 
  -
>>  >>>>>> 200    -    /AcomProductSyncServiceWeb/AcomProductSyncService
>>  >>>>>> 2008-03-19    -    02:31:04    -    [ip]    -    POST 
  -
>>  >>>>>> 200    -    /AcomProductSyncServiceWeb/AcomProductSyncService
>>  >>>>>> 2008-03-19    -    02:31:04    -    [ip]    -    POST 
  -
>>  >>>>>> 200    -    /AcomProductSyncServiceWeb/AcomProductSyncService
>>  >>>>>>
>>  >>>>>> The most incredible thing, is that I can open the index
without a
>>  >>>>>> CorruptedIndexException, normally. That's really bad for
me,
>>  >>>>>> cause the application didn't warn about a corrupted index
(of
>>  >>>>>> course, it is not). I can open it with the Luke App, and
with
>>  >>>>>> this simple code snippet accessing directly the lucene
index
>>  >>>>>> without solr:
>>  >>>>>>
>>  >>>>>>        IndexReader indexReader =
>>  >>>>>> IndexReader.open(FSDirectory.getDirectory("C/index/index.2008-03-19"));
>>  >>>>>>
>>  >>>>>>        IndexSearcher indexSearcher = new IndexSearcher(indexReader);
>>  >>>>>>              TermQuery termQuery = new TermQuery(new
>>  >>>>>> Term("itemId", "680804"));
>>  >>>>>>        Hits hits = indexSearcher.search(termQuery);
>>  >>>>>>              Iterator itHits = hits.iterator();
>>  >>>>>>        while (itHits.hasNext()) {
>>  >>>>>>            Hit hit = (Hit) itHits.next();
>>  >>>>>>            Document document = hit.getDocument();
>>  >>>>>>            String itemId =
>>  >>>>>> document.getField("itemId").stringValue();
>>  >>>>>>            System.out.println("itemId="+itemId);
>>  >>>>>>        }
>>  >>>>>>              indexSearcher.close();
>>  >>>>>>        indexReader.close();
>>  >>>>>>
>>  >>>>>>
>>  >>>>>> Ok, ok. But, if it's opening, whats my real problem?  Making
this
>>  >>>>>> little search above, the Document that I got, was another
one,
>>  >>>>>> with other information different from the original one
that I was
>>  >>>>>> looking for (the one with the itemId field = 680804). The
whole
>>  >>>>>> document was another document (but a valid document, that
I've
>>  >>>>>> indexed before). The itemId value that I got, the one that
was
>>  >>>>>> printed from that application above was 578340. Wow!!
>>  >>>>>>
>>  >>>>>> I can reproduce this error anytime with this code or with
luke on
>>  >>>>>> this corrupted index, but was terrible for me to find the
exact
>>  >>>>>> point of this fault.
>>  >>>>>>
>>  >>>>>> I've reindexed everything, it solves my problem. But I
wants to
>>  >>>>>> know if someone have any idea why this happened...
>>  >>>>>>
>>  >>>>>> Thanks people!
>>  >>>>>>
>>  >>>>>> []s,
>>  >>>>>>
>>  >>>>>> Lucas Teixeira
>>  >>>>>> lucas.teixeira@accurate.com.br
>>  >>>>>>
>>  >>>>>>
>>  >>>>>> ---------------------------------------------------------------------
>>  >>>>>>
>>  >>>>>> 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
>>  >>>>>
>>  >>>>>
>>  >>>>>
>>  >>>>
>>  >>>> ---------------------------------------------------------------------
>>  >>>> 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
>>  >>>
>>  >>>
>>  >>>
>>  >>
>>  >> ---------------------------------------------------------------------
>>  >> 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
>>  >
>>  >
>>  >
>>
>>  ---------------------------------------------------------------------
>>  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
>
>
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message