Checking Redundancy in Partitioned Regions

Under some circumstances, it can be important to verify that your partitioned region data is redundant and that upon member restart, redundancy has been recovered properly across partitioned region members.

For example, you need to verify that redundancy has been recovered prior to a rolling upgrade and during the rolling upgrade process. See Performing a Rolling Upgrade for more information.

You can verify partitioned region redundancy by making sure that the numBucketsWithoutRedundancy statistic is zero for all your partitioned regions. To check this statistic, use the following gfsh command:
gfsh>show metrics --categories=partition --region=region_name
For example:
gfsh>show metrics --categories=partition --region=posts

Cluster-wide Region Metrics
--------- | --------------------------- | -----
partition | putLocalRate                | 0
          | putRemoteRate               | 0
          | putRemoteLatency            | 0
          | putRemoteAvgLatency         | 0
          | bucketCount                 | 1
          | primaryBucketCount          | 1
          | numBucketsWithoutRedundancy | 1
          | minBucketSize               | 1
          | maxBucketSize               | 0
          | totalBucketSize             | 1
          | averageBucketSize           | 1

If you have start-recovery-delay=-1 configured for your partitioned region, you will need to perform a rebalance on your region after you restart any members in your cluster in order to recover redundancy.

If you have start-recovery-delay set to a low number, you may need to wait extra time until the region has recovered redundancy.