cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Noordzij (JIRA)" <>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-13540) QUORUM CL is used for new superuser
Date Wed, 31 May 2017 13:31:04 GMT


Dennis Noordzij updated CASSANDRA-13540:
    Comment: was deleted

(was: No corresponding errors other than this really. 
Well, yes, but I removed `SUPERUSER` privileges for the default `cassandra` user. 
Once all nodes join again, I can login again. )

> QUORUM CL is used for new superuser
> -----------------------------------
>                 Key: CASSANDRA-13540
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata
>            Reporter: Dennis Noordzij
> After bootstrapping Cassandra, we're creating a new superuser, and setting RF of system_auth
keyspace to 2, NetworkTopologyStrategy. Then a nodetool repair on the system_auth KS. 
> Documentation says 
> {quote}
> The system_auth keyspace uses a QUORUM consistency level when checking authentication
for the default cassandra user. For all other users created, superuser or otherwise, a LOCAL_ONE
consistency level is used for authenticating.
> {quote}
> But for my new superuser, new node members are rejected because QUORUM CL can't be achieved:

> {code}
> May 19th 2017, 17:40:14.462	Connection error: ('Unable to connect to any servers', {'xx.xx.xx.xx':
AuthenticationFailed('Failed to authenticate to xx.xx.xx.xx: Error from server: code=0100
[Bad credentials] message="org.apache.cassandra.exceptions.UnavailableException: Cannot achieve
consistency level QUORUM"',)})
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message