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

Better request latency and size histograms

    XMLWordPrintableJSON

Details

    • Brainstorming
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.2.0, 1.3.0, 1.0.3, 1.1.3, 0.98.17, 2.0.0
    • None
    • None
    • Reviewed

    Description

      I just discussed this with a colleague.
      The get, put, etc, histograms that each region server keeps are somewhat useless (depending on what you want to achieve of course), as they are aggregated and calculated by each region server.

      It would be better to record the number of requests in certainly latency bands in addition to what we do now.
      For example the number of gets that took 0-5ms, 6-10ms, 10-20ms, 20-50ms, 50-100ms, 100-1000ms, > 1000ms, etc. (just as an example, should be configurable).

      That way we can do further calculations after the fact, and answer questions like: How often did we miss our SLA? Percentage of requests that missed an SLA, etc.

      Comments?

      Attachments

        1. Get.png
          13 kB
          Vikas Vishwakarma
        2. AppendSizeTime.png
          25 kB
          Vikas Vishwakarma
        3. 14869-v6-0.98.txt
          56 kB
          Lars Hofhansl
        4. 14869-v5-0.98.txt
          56 kB
          Vikas Vishwakarma
        5. 14869-v4-0.98.txt
          51 kB
          Vikas Vishwakarma
        6. 14869-v3-0.98.txt
          27 kB
          Vikas Vishwakarma
        7. 14869-v2-2.0.txt
          30 kB
          Vikas Vishwakarma
        8. 14869-v2-0.98.txt
          21 kB
          Vikas Vishwakarma
        9. 14869-v1-2.0.txt
          26 kB
          Vikas Vishwakarma
        10. 14869-v1-0.98.txt
          2 kB
          Lars Hofhansl
        11. 14869-test-0.98.txt
          2 kB
          Lars Hofhansl

        Activity

          People

            vik.karma Vikas Vishwakarma
            larsh Lars Hofhansl
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: