Last week I moved all nodes back to cassandra 3.9. Everything worked fine
since then.
Yesterday I tried to upgrade again, running a rolling restart after the
upgrade.Nodes were just fine. Today one node started consuming 94.6% of its
CPU. Compacting is running all the time for this node.
I'm afraid
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
