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

Assing read/write request for same ledger to a single thread

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.4.0
    • Fix Version/s: 4.5.0
    • Component/s: None
    • Labels:
      None

      Description

      When entries for the same ledger are processed by the bookie we should avoid
      the reordering of the request. Currently, if multiple read/write threads are
      configured, the requests will be passed to the executor and writes for same
      ledger will be spread across multiple threads.

      This poses 2 issues:

      1. Mutex contention to access the LedgerDescriptor
      2. If the client receives add-entry acks out of order it has anyway to wait
        for the acks of previous entries before acknowledging the whole sequence
        to the application. In practice, the reordering is increasing the latency
        experienced by the application.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mmerli Matteo Merli
                Reporter:
                mmerli Matteo Merli
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: