Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-1453

corrupted logs may not be correctly identified by FileTxnIterator

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 3.3.3
    • Fix Version/s: None
    • Component/s: server
    • Labels:
      None

      Description

      See ZOOKEEPER-1449 for background on this issue. The main problem is that during server recovery org.apache.zookeeper.server.persistence.FileTxnLog.FileTxnIterator.next() does not indicate if the available logs are valid or not. In some cases (say a truncated record and a single txnlog in the datadir) we will not detect that the file is corrupt, vs reaching the end of the file.

        Attachments

        1. 10.10.5.123-withPath1489.tar.gz
          4.51 MB
          Marshall McMullen
        2. 10.10.5.44-withPath1489.tar.gz
          1.50 MB
          Marshall McMullen
        3. 10.10.5.42-withPath1489.tar.gz
          871 kB
          Marshall McMullen
        4. 10.10.5.123.tar.gz
          4.16 MB
          Marshall McMullen
        5. 10.10.5.44.tar.gz
          1.71 MB
          Marshall McMullen
        6. 10.10.5.42.tar.gz
          1.09 MB
          Marshall McMullen

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              phunt Patrick Hunt
            • Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: