Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-7001

Add a gauge to track region entry count

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.10.0
    • Component/s: statistics
    • Labels:

      Description

      Add a gauge to RegionPerfStats to track the entry count.

      As part of understanding system state and health, knowing what regions exist with how much data in them is an often asked question of a data store. The underlying metric is the CachePerfStats.entries value. This is only a piece of the information that customers need as it does not expose the region or region type to the users which is critical to understanding how things are setup.

      Scenario: REPLICATE region
      Given a cluster with the following servers:

      • server1
      • server2
        And the cluster has a "REPLICATE" region named X
        And the user has put 10 entries with distinct keys into region X
        Then server1's meter registry has the following meter
      • meter name: member.region.entries
      • tag: region_name = X
      • tag: <all the common tags>
      • tag: data_policy = REPLICATE
      • value: 10
        Then server2's meter registry has the following meter
      • name: member.region.entries
      • tag: region_name = X
      • tag: <all the common tags>
      • tag: data_policy = REPLICATE
      • value: 10

      Scenario: PARTITION region with no redundancy
      Given a cluster with the following servers:

      • server1
      • server2
        And the cluster has a "PARTITION" region named X
        And the user has put 10 entries with distinct keys into region X
        Then server1's meter registry has the following meter
      • meter name: member.region.entries
      • tag: region_name = X
      • tag: <all the common tags>
      • tag: data_policy = PARTITION
      • value: between 0 and 10
        Then server2's meter registry has the following meter
      • name: member.region.entries
      • tag: region_name = X
      • tag: <all the common tags>
      • tag: data_policy = PARTITION
      • value: between 0 and 10
        And the values of those meters add up to 10

      Scenario: PARTITIONED REDUNDANT
      Given a cluster with the following servers:

      • server1
      • server2
      • server3
        And the cluster has a "PARTITION_REDUNDANT" region named X
        And the redundancy level is set to 1 copy (2 total copies of each key should exist)
        And the user has put 10 entries with distinct keys into region X
        Then server1's meter registry has the following meter
      • meter name: member.region.entries
      • tag: region_name = X
      • tag: <all the common tags>
      • tag: data_policy = PARTITION
      • value: between 0 and 10
        Then server2's meter registry has the following meter
      • name: member.region.entries
      • tag: region_name = X
      • tag: <all the common tags>
      • tag: data_policy = PARTITION
      • value: between 0 and 10
        Then server3's meter registry has the following meter
      • name: member.region.entries
      • tag: region_name = X
      • tag: <all the common tags>
      • tag: data_policy = PARTITION
      • value: between 0 and 10
        And the values of those meters add up to 20

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              demery Dale Emery
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 8h 20m
                8h 20m