Hi James, I don't recall reading anything related to performance degradation due to an excessive number of keyrings generated in a Ceph cluster. Could you elaborate on your use case? E.g. why you would have so many clients not able to share a common keyring. FWIW, the orchestrator can take care of pushing ceph.conf and keyrings on clients based on a host label [1]. This might help your case. Best regards, Frédéric. [1] https://docs.ceph.com/en/latest/cephadm/operations/#client-keyrings-and-conf... ----- Le 6 Juin 25, à 5:28, James Tocknell james.tocknell@mq.edu.au a écrit :
Hi All
As far as I can see, there is no guidance on the number of cephx keys that can be in use at one time. Is there a number at which ceph becomes much slower e.g. 100, 10000, 1000000? I'm wondering how best to manage keys across many clients (let's say 1000s for now), most of which won't actually be connected at the same time.
Regards James _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io