[ 
https://issues.apache.org/jira/browse/CASSANDRA-12988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416761#comment-17416761
 ] 

Jeremiah Jordan edited comment on CASSANDRA-12988 at 9/17/21, 3:31 PM:
-----------------------------------------------------------------------

I have not gone through the implications of this change extensively, but from 
past experience with auth bootstrapping and multiple DC's, I do not know 
changing away from QUORUM for the default user is safe.

Because of the way people bring up new datacenter with bootstrap off, combined 
with the way we auto create the "cassandra" users, I do not think it is safe to 
stop using QUORUM for that user.  A read at LOCAL_QUORUM will not find any 
users and the nodes would then "create" the "cassandra" user, possibly over 
writing or bringing that user back if it removed.

I hate the fact that the "cassandra" user uses QUORUM as much as the next 
person, but until we have a way to create that user which is not "try to do it 
automatically during first startup", or we don't have "auto bootstrap:false" as 
an option, I think the use of QUORUM is actually needed.


was (Author: jjordan):
I have not gone through the implications of this change extensively, but from 
past experience with auth bootstrapping and multiple DC's, I do not know 
changing away from QUORUM is safe.

Because of the way people bring up new datacenter with bootstrap off, combined 
with the way we auto create the "cassandra" users, I do not think it is safe to 
stop using QUORUM for that user.  A read at LOCAL_QUORUM will not find any 
users and the nodes would then "create" the "cassandra" user, possibly over 
writing or bringing that user back if it removed.

I hate the fact that the "cassandra" user uses QUORUM as much as the next 
person, but until we have a way to create that user which is not "try to do it 
automatically during first startup", or we don't have "auto bootstrap:false" as 
an option, I think the use of QUORUM is actually needed.

> make the consistency level for user-level auth reads and writes configurable
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12988
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12988
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Legacy/Core
>            Reporter: Jason Brown
>            Assignee: Josh McKenzie
>            Priority: Low
>             Fix For: 4.x
>
>
> Most reads for the auth-related tables execute at {{LOCAL_ONE}}. We'd like to 
> make it configurable, with the default still being {{LOCAL_ONE}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to