Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-7631

Per Region read/write sizes in metrics (WAS: Region w/ few, fat reads was hard to find on a box carrying hundreds of regions)

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Not A Problem
    • None
    • None
    • metrics
    • None

    Description

      Of a sudden on a prod cluster, a table's rows gained girth... hundreds of thousands of rows... and the application was pulling them all back every time but only once a second or so. Regionserver was carrying hundreds of regions. Was plain that there was lots of network out traffic. It was tough figuring which region was the culprit (JD's trick was moving the regions off one at a time while watching network out traffic on cluster to see whose spiked next – it worked but just some time).

      If we had per region read/write sizes in metrics, that would have saved a bunch of diagnostic time.

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            stack Michael Stack
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment