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

Handle Memtable flush failure

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.5.0
    • Component/s: None
    • Labels:
      None

      Description

      Consider the following scenario

      • currently bookie is in writemode but it is close to the diskusagethreshold and also entrymemtable is close to skipListSizeLimit
      • it received a addentry call, and now the size of the entrymemtable is greater than skipListSizeLimit
      • so onSizeLimitReached of SortedLedgerStorage will be called and now lets assume that memtable flush has failed because of diskusagethreshold
      • because of previous step, bookie would turn to readonly
      • now lets assume after certain rounds of compaction bookie reclaimed sufficient storage and went back to writemode
      • now bookie would be receiving addentry calls
      • because of outstanding snapshot from previous memtable flush failure, it will never retry to flush memtable
      • now the memory start keep going up and up and the process memory gets bloated

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                reddycharan18@gmail.com Charan Reddy Guttapalem
                Reporter:
                reddycharan18@gmail.com Charan Reddy Guttapalem
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: