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

BookKeeper: Throttling improved for reads

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.3.1
    • 3.4.0
    • contrib-bookkeeper
    • None

    Description

      Reads and writes in BookKeeper are asymmetric: a write request writes one entry, whereas a read request may read multiple requests. The current implementation of throttling only counts the number of read requests instead of counting the number of entries being read. Consequently, a few read requests reading a large number of entries each will spawn a large number of read-entry requests.

      Attachments

        1. ZOOKEEPER-831.patch
          13 kB
          Flavio Paiva Junqueira
        2. ZOOKEEPER-831.patch
          11 kB
          Flavio Paiva Junqueira
        3. ZOOKEEPER-831.patch
          10 kB
          Flavio Paiva Junqueira
        4. ZOOKEEPER-831.patch
          6 kB
          Flavio Paiva Junqueira

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            fpj Flavio Paiva Junqueira Assign to me
            fpj Flavio Paiva Junqueira
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment