Activity log for bug #1981700

Date Who What changed Old value New value Message
2022-07-14 11:15:39 Alistair Coles bug added bug
2022-07-14 11:16:06 Alistair Coles description Container sync reds 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.) 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.)