Comment 1 for bug 1476623

To my knowledge two ideas has been discussed as a possible resolution to this issue:

1) when a daemon that already walks the tree finds a database with container_sync keys in set in the stats table it drops a pointer to the container in a smaller tree that can be walked more efficiently by the container-sync daemon

2) when the replicator encounters a container with contaienr_sync keys it replicates the rows into sharded container sync accounts exactly like the reconciler, and the container_sync daemon is redesigned to horizontally scale using coordinated processes like the expirier.

Thank you for documenting this issue. Please feel free to jot down/discuss any other ideas you are pursuing.