To flesh this out a bit, I set roles_validity_in_ms and permissions_validity_in_ms to 3600000 (10 minutes). The default of 2000 is far too often for my use cases. Usually I set the RF for system_auth to 3 per DC. On a larger, busier cluster I have set it to 6 per DC. NOTE: if you set the validity higher, it may take that amount of time before a change in password or table permissions is picked up (usually less).
Sean Durity -----Original Message----- From: Jeff Jirsa <jji...@gmail.com> Sent: Tuesday, June 2, 2020 2:39 AM To: user@cassandra.apache.org Subject: [EXTERNAL] Re: Impact of enabling authentication on performance Set the Auth cache to a long validity Don’t go crazy with RF of system auth Drop bcrypt rounds if you see massive cpu spikes on reconnect storms > On Jun 1, 2020, at 11:26 PM, Gil Ganz <gilg...@gmail.com> wrote: > > > Hi > I have a production 3.11.6 cluster which I'm might want to enable > authentication in, I'm trying to understand what will be the performance > impact, if any. > I understand each use case might be different, trying to understand if there > is a common % people usually see their performance hit, or if someone has > looked into this. > Gil --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
