[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[
https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033527#comment-16033527
]
Sam Tunnicliffe commented on CASSANDRA-13540:
-
No worries, glad we got to the bottom of it!
> QUORUM CL is used for new superuser
> ---
>
> Key: CASSANDRA-13540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13540
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
>Reporter: Dennis
>
> 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
(v6.3.15#6346)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[
https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033481#comment-16033481
]
Dennis Noordzij commented on CASSANDRA-13540:
-
Yep, I screwed up. My bootstrap script was repeating the replacement of the
default cassandra user on an existing cluster, which is done with the default
cassandra user of course. That's where this error came from.
Sorry for consuming your time here...
> QUORUM CL is used for new superuser
> ---
>
> Key: CASSANDRA-13540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13540
> 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
(v6.3.15#6346)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[
https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033377#comment-16033377
]
Sam Tunnicliffe commented on CASSANDRA-13540:
-
Hmm, I cannot repro this or see a path in the code that would produce it. What
is the cluster topology and can you reproduce with a clean cluster, perhaps
using ccm?
http://www.datastax.com/dev/blog/ccm-a-development-tool-for-creating-local-cassandra-clusters
> QUORUM CL is used for new superuser
> ---
>
> Key: CASSANDRA-13540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13540
> 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
(v6.3.15#6346)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[
https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031151#comment-16031151
]
Dennis Noordzij commented on CASSANDRA-13540:
-
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: https://issues.apache.org/jira/browse/CASSANDRA-13540
> 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
(v6.3.15#6346)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[
https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031148#comment-16031148
]
Dennis Noordzij commented on CASSANDRA-13540:
-
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: https://issues.apache.org/jira/browse/CASSANDRA-13540
> 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
(v6.3.15#6346)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[
https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031101#comment-16031101
]
Sam Tunnicliffe commented on CASSANDRA-13540:
-
[~denno] are you sure that's a response to a request using your new superuser
credentials as {{org.apache.cassandra.auth.PasswordAuthenticator}} should
definitely only issue queries at {{QUORUM}} for the {{cassandra}} user
Are there any corresponding errors in the server log when you attempt to log in
with the new user?
Are you still able to use the default superuser credentials?
If rf=2, then at least 1 node must be partitioned from the one you're logging
into, what happens when there are no nodes being reported {{DOWN}}?
> QUORUM CL is used for new superuser
> ---
>
> Key: CASSANDRA-13540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13540
> 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
(v6.3.15#6346)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
