container-sync doesn't work with sharded container

Bug #1981700 reported by Alistair Coles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
New
Undecided
Unassigned

Bug Description

Container sync reads object rows directly from the source container DB. Once a root container is sharded, the 'fresh' root DB will not generally* receive object updates, so the container sync process will not find new object rows.

Container sync metadata (e.g. X-Container-Sync-To) is not copied to shard containers, so these will not be sync'd to the destination.

(* Some misplaced object updates will be written to the fresh DB.)

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.