Barry Oglesby created GEODE-5478:
------------------------------------
Summary: The lowRedundancyBucketCount statistic is not maintained
properly when multiple members are stopped and restarted
Key: GEODE-5478
URL: https://issues.apache.org/jira/browse/GEODE-5478
Project: Geode
Issue Type: Bug
Components: regions, statistics
Reporter: Barry Oglesby
The lowRedundancyBucketCount statistic is not maintained properly when multiple
members are stopped and restarted
A test where multiple members are stopped simultaneously so that all copies of
a bucket are offlineshows the numBucketsWithoutRedundancy metric not set
properly:
Initially:
{noformat}
(2) Executing - show metrics --categories=partition --region=/rewards
Category | Metric | Value
--------- | --------------------------- | ------
partition | putLocalRate | 0.0
| putRemoteRate | 0.0
| putRemoteLatency | 0
| putRemoteAvgLatency | 0
| bucketCount | 226
| primaryBucketCount | 113
| numBucketsWithoutRedundancy | 0
| totalBucketSize | 200000
| averageBucketSize | 221
(3) Executing - show metrics --categories=partition --region=/customer
Category | Metric | Value
--------- | --------------------------- | -----
partition | putLocalRate | 0.0
| putRemoteRate | 0.0
| putRemoteLatency | 0
| putRemoteAvgLatency | 0
| bucketCount | 226
| primaryBucketCount | 113
| numBucketsWithoutRedundancy | 0
| totalBucketSize | 20000
| averageBucketSize | 22
{noformat}
After stopping 2 members (of 4):
{noformat}
(2) Executing - show metrics --categories=partition --region=/rewards
Category | Metric | Value
--------- | --------------------------- | -----
partition | putLocalRate | 0.0
| putRemoteRate | 0.0
| putRemoteLatency | 0
| putRemoteAvgLatency | 0
| bucketCount | 112
| primaryBucketCount | 73
| numBucketsWithoutRedundancy | 57
| totalBucketSize | 99107
| averageBucketSize | 442
(3) Executing - show metrics --categories=partition --region=/customer
Category | Metric | Value
--------- | --------------------------- | -----
partition | putLocalRate | 0.0
| putRemoteRate | 0.0
| putRemoteLatency | 0
| putRemoteAvgLatency | 0
| bucketCount | 112
| primaryBucketCount | 76
| numBucketsWithoutRedundancy | 57
| totalBucketSize | 9915
| averageBucketSize | 44
{noformat}
After restarting both members, numBucketsWithoutRedundancy > 0:
{noformat}
(2) Executing - show metrics --categories=partition --region=/rewards
Category | Metric | Value
--------- | --------------------------- | ------
partition | putLocalRate | 0.0
| putRemoteRate | 0.0
| putRemoteLatency | 0
| putRemoteAvgLatency | 0
| bucketCount | 226
| primaryBucketCount | 113
| numBucketsWithoutRedundancy | 0
| totalBucketSize | 200000
| averageBucketSize | 221
(3) Executing - show metrics --categories=partition --region=/customer
Category | Metric | Value
--------- | --------------------------- | -----
partition | putLocalRate | 0.0
| putRemoteRate | 0.0
| putRemoteLatency | 0
| putRemoteAvgLatency | 0
| bucketCount | 226
| primaryBucketCount | 113
| numBucketsWithoutRedundancy | 21
| totalBucketSize | 20000
| averageBucketSize | 22
{noformat}
All the buckets and data are recovered, but the numBucketsWithoutRedundancy is
not 0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
