Feature #11934
rgw: metadata log sync work
% Done:
0%
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
We'll change the way we sync the metadata: instead of reading log on source zone and apply it on the metadata objects on the destination, we'll clone it into the destination, then apply the destination using the same versioning the source uses.
This will work in conjuction with the new Term that defines the interval where a specific master existed.
When switching to new Term, we need to roll back versions that were applied but do not exist on the new master.
History
#1 Updated by Yehuda Sadeh over 8 years ago
- Target version set to v9.0.4
#2 Updated by Yehuda Sadeh over 8 years ago
- Status changed from New to In Progress
#3 Updated by Yehuda Sadeh over 8 years ago
- Target version changed from v9.0.4 to v9.1.0
#4 Updated by Yehuda Sadeh over 8 years ago
- Target version changed from v9.1.0 to 10.0.1
#5 Updated by Matt Benjamin about 8 years ago
- Target version changed from 10.0.1 to 10.0.2
#6 Updated by Yehuda Sadeh about 8 years ago
- Status changed from In Progress to Fix Under Review
#7 Updated by Yehuda Sadeh about 8 years ago
- Target version changed from 10.0.2 to 10.0.3
#8 Updated by Yehuda Sadeh almost 8 years ago
- Status changed from Fix Under Review to Resolved