Actions
Tasks #44424
closedTasks #44423: multisite: support dynamic bucket index resharding
multisite: track bucket sync status in a single object
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Tags:
multisite
Reviewed:
Affected Versions:
Pull request ID:
Description
Bucket sync status is split across the bucket's shards, and each tracks full- vs. incremental sync separately. Instead, a single sync status object should store an array of shard markers.
For backward compatibility, when we see that this per-bucket status object doesn't exist, we should try to read from any existing per-shard status objects when initializing the bucket sync status.
Updated by Casey Bodley about 4 years ago
- Blocks Tasks #44426: multisite: each data sync shard caches its bucket sync status added
Actions