I answered a similar question here: https://groups.google.com/forum/#!topic/nosql-databases/lLBebUCjD8Y
Sean Durity – Lead Cassandra Admin From: Felipe Esteves [mailto:felipe.este...@b2wdigital.com] Sent: Tuesday, June 07, 2016 12:07 PM To: user@cassandra.apache.org Subject: Change authorization from AllowAllAuthorizer to CassandraAuthorizer Hi guys, I have a Cassandra 2.1.8 Community cluster running with AllowAllAuthorizer and have to change it, so I can implement permissions in different users. As I've checked in the docs, seems like a simple change, from AllowAllAuthorizer to CassandraAuthorizer in cassandra.yaml. However, I'm a litte concerned about the performance of the cluster while I'm restarting all the nodes. Is it possible to have any downtime (access errors, maybe), as all the data was created with AllowAllAuthorizer? -- Felipe Esteves Tecnologia felipe.este...@b2wdigital.com<mailto:seu.em...@b2wdigital.com> Tel.: (21) 3504-7162 ramal 57162 ________________________________ 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.
