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@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
