Den tis 10 juni 2025 kl 19:39 skrev Gregory Farnum <gfar...@redhat.com>: > > I'm sure at some scale on some hardware it is possible to run into > bottlenecks, but no reported issues with scaling come to mind. > > CephX keys are durably stored in the monitor's RocksDB instance, which > it uses to store all of its data. This scales well but not infinitely, > but I don't think we've run into monitor issues with scaling after > some early teething issues and switching from LevelDB to RocksDB.
Also, its a key-value store right? So you would normally do lookups based on a known key, and you get the value (ie, password+caps) back. In this case it would not matter much if it was a 1000 keys or a million, it would do the lookups really fast in both cases. Only commands like "ceph auth list" would have to traverse it from 0 .. 1000. So while the keys (with pw and caps) might eat a kB or two of ram, I would not guess there are practical limits on size, unless you do crazy numbers of keys, and the first issue you get might be mon RAM running out or adding an entry to the list takes a long while, more than "auth takes too long for client.something6789". > If there is an issue, it's definitely closer to 1 million keys than to > 1 thousand. Yeah. -- May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
