Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-15161 Umbrella: Miscellaneous improvements from production usage
  3. HBASE-15740

Replication source.shippedKBs metric is undercounting because it is in KB

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.3.0, 0.98.20, 2.0.0
    • None
    • None
    • Reviewed
    • Removed Replication source.shippedKBs metric in favor of source.shippedBytes

    Description

      In a cluster where there is replication going on, I've noticed that this is always 0:

          "source.shippedKBs" : 0,
      

      Looking at the source reveals why:

                metrics.shipBatch(currentNbOperations, currentSize / 1024, currentNbHFiles);
      

      It is always undercounting because we discard remaining bytes after KB boundary. This is specially a problem when we are always shipping small batches <1KB.

      Attachments

        Activity

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

          People

            enis Enis Soztutar Assign to me
            enis Enis Soztutar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment