Regardless, if you are not modifying users frequently (with five you most
likely are not), make sure turn the permission cache wyyy up.
In 2.1 that is just: permissions_validity_in_ms (default is 2000 or 2
seconds). Feel free to set it to 1 day or some such. The corresponding
async update para
8-30
> 10:51:25.015000 | xx.xx.xx.113 | 601190
>
> REQUEST_RESPONSE message received from
> /xx.xx.xx.116 [MessagingService-Incoming-/xx.xx.xx.116] | 2017-08-30
> 10:51:25.015000 | xx.xx.xx.113 | 601771
>
>
> Processing re
For that many nodes mixed with vnodes you probably want a lower RF than N
per datacenter. 5 or 7 would be reasonable. The only down side is that auth
queries may take slightly longer as they will often have to go to other
nodes to be resolved, but in practice this is likely not a big deal as the
da
Request complete | 2017-08-30 10:51:25.014874
| xx.xx.xx.113 | 601874
From: Oleksandr Shulgin
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, August 30, 2017 at 10:42 AM
To: User
Subject: Re: system_auth replication
On Wed, Aug 30, 2017 at 6:40 PM, Chuck Reynolds
wrote:
> How many users do you have (or expect to be found in system_auth.users)?
>
> 5 users.
>
> What are the current RF for system_auth and consistency level you are
> using in cqlsh?
>
> 135 in one DC and 227 in the other DC. Consistency lev
TRACING ON)?
Tracing timeout even though I increased it to 120 seconds.
From: Oleksandr Shulgin
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, August 30, 2017 at 10:19 AM
To: User
Subject: Re: system_auth replication factor in Cassandra 2.1
On Wed, Aug 30, 2017 at 5:50 PM, Chuc
On Wed, Aug 30, 2017 at 6:20 PM, Chuck Reynolds
wrote:
> So I tried to run a repair with the following on one of the server.
>
> nodetool repair system_auth -pr –local
>
>
>
> After two hours it hadn’t finished. I had to kill the repair because of
> another issue and haven’t tried again.
>
>
>
>
if I set the RF back to a lower number like 5?
Thanks
From: on behalf of Sam Tunnicliffe
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, August 30, 2017 at 10:10 AM
To: "user@cassandra.apache.org"
Subject: Re: system_auth replication factor in Cassandra 2.1
It'
On Wed, Aug 30, 2017 at 5:50 PM, Chuck Reynolds
wrote:
> So I’ve read that if your using authentication in Cassandra 2.1 that your
> replication factor should match the number of nodes in your datacenter.
>
>
>
> *Is that true?*
>
>
>
> I have two datacenter cluster, 135 nodes in datacenter 1 & 2
It's a better rule of thumb to use an RF of 3 to 5 per DC and this is what
the docs now suggest:
http://cassandra.apache.org/doc/latest/operating/security.html#authentication
Out of the box, the system_auth keyspace is setup with SimpleStrategy and
RF=1 so that it works on any new system including
I recently came across an issue where by my user Keyspace was replicated by 3
(I have 3 nodes) but my system_auth was default to 1, we also use
authentication, I then lost 2 of my nodes and because authentication wasn’t
replicated I couldn’t log in.
Once I resolved the issue, and got the nodes
11 matches
Mail list logo
