Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Stop rgw process on master. Switch non-master zone to master.
3. Create new buckets and objects on current master.
4. Bring up rgw process on the old master zone.
5. Upload some more buckets and objects on the current master.
5. Check for sync
All the buckets were synced. The objects created before rgw process restart failed to sync but the other objects created later synced successfully.
I don't see a GET request sent to master on the buckets that are missing objects.
The only part that I'd clarify is "During this process, the master zone is down and object sync requests can be skipped under certain circumstances."
I'd suggest replacing that sentence with:
Generally, the master zone's gateway(s) will still be running when this happens. But in the case where its gateways are all down, it can take up to 30 seconds after restarting for them to notice that another zone was promoted. During this window, they can miss some changes to buckets that occur on other zones.
Is this yet to be documented in the release notes?
The behavior is expected in current multisite sync. In future releases, multisite sync may support more complex failover and recovery scenarios, there is no upstream tracker issue yet.