Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-1044

Behavior on hard power shutdown


    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.4
    • core/index
    • None
    • Windows Server 2003, Standard Edition, Sun Hotspot Java 1.5

    • New


      When indexing a large number of documents, upon a hard power failure (e.g. pull the power cord), the index seems to get corrupted. We start a Java application as an Windows Service, and feed it documents. In some cases (after an index size of 1.7GB, with 30-40 index segment .cfs files) , the following is observed.

      The 'segments' file contains only zeros. Its size is 265 bytes - all bytes are zeros.
      The 'deleted' file also contains only zeros. Its size is 85 bytes - all bytes are zeros.

      Before corruption, the segments file and deleted file appear to be correct. After this corruption, the index is corrupted and lost.

      This is a problem observed in Lucene 1.4.3. We are not able to upgrade our customer deployments to 1.9 or later version, but would be happy to back-port a patch, if the patch is small enough and if this problem is already solved.


        1. LUCENE-1044.take8.patch
          206 kB
          Michael McCandless
        2. LUCENE-1044.take7.patch
          205 kB
          Michael McCandless
        3. LUCENE-1044.take6.patch
          194 kB
          Michael McCandless
        4. LUCENE-1044.take5.patch
          86 kB
          Michael McCandless
        5. LUCENE-1044.take4.patch
          7 kB
          Michael McCandless
        6. LUCENE-1044.take3.patch
          16 kB
          Michael McCandless
        7. LUCENE-1044.take2.patch
          7 kB
          Michael McCandless
        8. LUCENE-1044.patch
          6 kB
          Michael McCandless
        9. FSyncPerfTest.java
          6 kB
          Doron Cohen



            mikemccand Michael McCandless
            ts01 venkat rangan
            1 Vote for this issue
            4 Start watching this issue