Just to clarify that behaviour. QUORUM only applies to the default
superuser, subsequent superusers you create later on are still only queried
at LOCAL_ONE. E.g.
protected static ConsistencyLevel consistencyForRole(String role)
{
if (role.equals(DEFAULT_SUPERUSER_NAME))
return Consiste
More explicitly - if you have 60 nodes, setting rf=60 will likely make it very
difficult for you to log in as a superuser.
--
Jeff Jirsa
> On Sep 6, 2017, at 11:40 AM, Jon Haddad wrote:
>
> I wouldn’t worry about being meticulous about keeping RF = N as the cluster
> grows. If you had 60
I wouldn’t worry about being meticulous about keeping RF = N as the cluster
grows. If you had 60 nodes and your auth data was only on 9 you’d be
completely fine.
> On Sep 6, 2017, at 11:36 AM, Cogumelos Maravilha
> wrote:
>
> After insert a new node we should:
>
> ALTER KEYSPACE system_au
After insert a new node we should:
ALTER KEYSPACE system_auth WITH REPLICATION = { 'class' : ...
'replication_factor' : x };
x = number of nodes in dc
The default user and password should work:
-u cassandra -p cassandra
Cheers.
On 23-08-2017 11:14, kurt greaves wrote:
> The cassandra user requ
Common trap. It's an unfortunate default that is not so easy to change.
Community!!
From: kurt greaves [mailto:k...@instaclustr.com]
Sent: 23 August 2017 11:14
To: User
Subject: Re: C* 3 node issue -Urgent
The cassandra user requires QUORUM consistency to be achieved for
authentication. Normal users only require ONE. I suspect your system_auth
keyspace has an RF of
The cassandra user requires QUORUM consistency to be achieved for
authentication. Normal users only require ONE. I suspect your system_auth
keyspace has an RF of 1, and the node that owns the cassandra users data is
down.
Steps to recover:
1. Turn off authentication on all the nodes
2. Restart the
o I get the other 2 nodes back up?
>
> From: Akhil Mehra [mailto:akhilme...@gmail.com <mailto:akhilme...@gmail.com>]
> Sent: 23 August 2017 10:05
> To: user@cassandra.apache.org <mailto:user@cassandra.apache.org>
> Subject: Re: C* 3 node issue -Urgent
>
> The
t; CQLSH to change this? Or better, how do I get the other 2 nodes back up?
>
> From: Akhil Mehra [mailto:akhilme...@gmail.com <mailto:akhilme...@gmail.com>]
> Sent: 23 August 2017 10:05
> To: user@cassandra.apache.org <mailto:user@cassandra.apache.org>
> Subject: Re:
August 2017 10:05
To: user@cassandra.apache.org
Subject: Re: C* 3 node issue -Urgent
The cqlsh image say bad credentials. Just confirming that you have the correct
username/password when logging on.
By turing on authentication I am assuming you mean using the
PasswordAuthenticator instead of the
Error from
server: code=0100 [Bad credentials] message="Username and/or password are
incorrect"',)})
Yes you are correct I do have PasswordAuthenticator turned on .
From: Akhil Mehra [mailto:akhilme...@gmail.com]
Sent: 23 August 2017 10:05
To: user@cassandra.apache.org
Subject
PM, Jonathan Baynes
> wrote:
>
> I will also mention I am on:
>
> C* 3.0.11
> Linux Oracle red hat 7.1
> Java 1.8.0.31
> Python 2.7
>
> From: Jonathan Baynes
> Sent: 23 August 2017 09:47
> To: 'user@cassandra.apache.org <mailto:user@cassandra.apache.
I will also mention I am on:
C* 3.0.11
Linux Oracle red hat 7.1
Java 1.8.0.31
Python 2.7
From: Jonathan Baynes
Sent: 23 August 2017 09:47
To: 'user@cassandra.apache.org'
Cc: Stewart Allman
Subject: C* 3 node issue -Urgent
Hi Everyone.
I need the communities help here.
I have atte
Hi Everyone.
I need the communities help here.
I have attempted this morning to turn on JMX authentication for Nodetool. I've
gone into the Cassandra-env.sh file and updated the following:
LOCAL_JMX=No
JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.authenticate=true"
JVM_OPTS="$JVM_OPTS
-
14 matches
Mail list logo
