Uploaded image for project: 'Bookkeeper'
  1. Bookkeeper
  2. BOOKKEEPER-623

LedgerChecker should avoid segments of closed ledger with higher start entryId than closed entry.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.2.1, 4.3.0
    • Fix Version/s: 4.2.2, 4.3.0
    • Component/s: bookkeeper-server
    • Labels:
      None

      Description

      With the almost same testcase mentioned in the BOOKKEEPER-584, Ledger metadata is getting added with extra segment during failure handling of bookies along with fencing.

      Only difference in the testcase is .
      1. Before bookie failures some entries were already written
      2. And after bookies failed ( First bookie will throw LedgerFenced/Unauthorized exception, and second bookie is slow/dead bookie ), Number of entries written asynchrounously is n*ensembleSize+1

      Note that, Unauthorized/FencedException callback comes first, then other bookie failure callback comes.

      I will attach a TestCase along with patch for this shortly. Testcase is modified version of attached testcase in BOOKKEEPER-584

        Attachments

        1. BOOKKEEPER-623.patch
          4 kB
          Vinayakumar B
        2. BOOKKEEPER-623.patch
          5 kB
          Vinayakumar B
        3. BOOKKEEPER-623.patch
          4 kB
          Vinayakumar B
        4. BOOKKEEPER-623.patch
          4 kB
          Vinayakumar B
        5. BOOKKEEPER-623.patch
          4 kB
          Vinayakumar B
        6. BOOKKEEPER-623.patch
          4 kB
          Vinayakumar B

          Activity

            People

            • Assignee:
              vinayakumarb Vinayakumar B
              Reporter:
              vinayakumarb Vinayakumar B
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: