Actions
Bug #18639
closedmultisite: incremental metadata sync does not properly advance to next period
% Done:
0%
Source:
Tags:
Backport:
jewel kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
There are 3 bugs present:
- RGWMetaSyncCR does not correctly detect whether the syncing period is the current_period
- RGWMetaSyncShardCR incorrectly compares the markers between different period logs
- when RGWMetaSyncShardCR is done with a period, RGWBackoffControlCR retries RGWMetaSyncShardCR on the same period
Updated by Casey Bodley about 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Casey Bodley about 7 years ago
tests for this also need review in https://github.com/ceph/ceph/pull/13067
Updated by Casey Bodley almost 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #19847: jewel: multisite: incremental metadata sync does not properly advance to next period added
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #19848: kraken: multisite: incremental metadata sync does not properly advance to next period added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions