I think your concern makes sense. The challenge is that multisite is not only about zone-to-zone replication — it also introduces multiple zonegroups, and you want to make sure one team cannot accidentally consume all available capacity and impact other users. For example, if Team A is not actively using the main zonegroup but is storing a large amount of data in an archive zonegroup, they could still potentially exhaust cluster resources. Maintaining high quotas in the main zonegroup alone would not fully protect the cluster if the underlying storage capacity is shared. My goal is to manage only the logical resources (accounts) while still having some protection against a single tenant filling the cluster. Maybe I am missing some existing mechanism or recommended approach for this scenario. Is there a way to enforce storage limits per tenant/account across zonegroups, or otherwise prevent one group from consuming capacity needed by others? Thanks. On Thu, 2026-08-06 at 09:14 -0400, Casey Bodley wrote:
On Thu, Aug 6, 2026 at 3:44 AM Danila Reznichuk via ceph-users <ceph-users@ceph.io> wrote:
Hi,
I have a question about account quotas in an RGW multisite setup.
My configuration is fairly simple:
Main zonegroup with the master zone. Archive zonegroup with two zones: A and B.
I created an account on the master zone of the main zonegroup and set the account quota (--quota-scope account) to 1 GiB. As expected, this change was synchronized to all other zones in all zonegroups.
Then, by mistake, I changed the quota for the same account on zone A of the archive zonegroup to 2 GiB. This change was not synchronized to the other zones. That seems reasonable to me and could even be considered a feature, since different zonegroups may represent different locations with different storage policies or usage patterns.
After some testing, I found that updating the account quota again on the master zone of the main zonegroup overwrites the locally modified quota on zone A.
So I have a few questions:
Is this the intended behavior? Is there a supported way to configure different account quotas for different zones or zonegroups? If not, is the account quota expected to be globally consistent across the entire multisite deployment?
the intent of multisite is to keep all metadata (accounts, users, buckets, etc) consistent across zones, with the metadata master zone as the source of truth. there are several radosgw-admin commands that can modify metadata on secondary zones, but they're supposed to print a warning message and require --yes-i-really-mean-it. that logic was missing from the quota commands, so i've raised https://tracker.ceph.com/issues/79120 to track the fix and its backports
Thanks! _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io