the 'bucket sync disable/enable' commands were added in https://github.com/ceph/ceph/pull/15801, and predate the per-bucket replication feature from https://github.com/ceph/ceph/pull/31686 by a couple years. the goal was to deprecate the earlier commands, but it's still not clear to me that bucket sync policy provides a drop-in replacement. in the meantime, we've continued to support and test 'bucket sync disable' Soumya recently fixed a sync policy interaction between the bucket and zonegroup in https://github.com/ceph/ceph/pull/49803 that helps with this, but i still think there are consistency issues around changes to the sync policy. whereas 'bucket sync enable' automatically triggers a bucket full sync (by writing datalog entries for each of its index shards), i don't believe the same happens when a bucket sync policy is reenabled On Wed, May 3, 2023 at 12:44 PM Yixin Jin <yjin77@yahoo.ca> wrote:

Hi folks,

It appears that we have multiple ways to disable/enable bucket sync. Either from "bucket sync disable/enable", which can run without bucket-specific sync policy. Or from "sync group create/modify" with --status=allowed/enabled/forbidden. What is the relationship between the two?

I notice that after I did "bucket sync disable" on a bucket and then enabling it with "sync group create --status=enabled", "bucket sync status" shows the status of all related pipes and it claims all 11 shards are behind, which is a bit strange since my bucket only has 4 objects. The sync status looks the same in both zones that are involved in the newly create sync policy. It appears to be bogus since both cannot be behind to the other.

Then I run "bucket sync init" in both zones and that changes the sync status as "init: bucket sync has not started". "bucket sync run" that follows this step changes the sync status again to be "stopped: bucket sync is disabled".

It seems to be some disconnect between the effect of "bucket sync disable" and sync policy. The latter wonders around and eventually figures out that the bucket sync has been disabled. The plus side is that sync never happens so it is truly disabled. After I use "bucket sync enable" to enable it, eventually the bucket is synced up between the two zones without explicit run of "bucket sync run" again.

So, what is the relationship between these two ways and what is recommended practice of using them together?

Thanks, Yixin _______________________________________________ Dev mailing list -- dev@ceph.io To unsubscribe send an email to dev-leave@ceph.io