Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-1735

Cluster revision file should contain identifier to detect file journal log replacement

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: core 1.4.5
    • Fix Version/s: None
    • Component/s: clustering, jackrabbit-core
    • Labels:
      None

      Description

      Given the following scenario:

      (1) We have two nodes CN1 and CN2 in a cluster, where CN2's latest revision is R > 0
      (2) Stop CN1 and CN2
      (3) Remove CN1's local revision file and all journal files
      (4) Restart CN1, append some records, until we have a revision R' > R
      (5) Restart CN2

      This will produce an unrecoverable error, because CN2 will stay in a loop, trying to read the journal record following revision R, i.e. starting at file position R, which points to the middle of some record.

      Therefore, in order to easily detect this situation, a journal log should contain a unique identifier, which will also be recorded in the local file revision.

        Attachments

          Activity

            People

            • Assignee:
              dpfister Dominique Pfister
              Reporter:
              dpfister Dominique Pfister
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: