Actually if factor is equal to total number of nodes with SimpleStrategy one
copy will be placed on each node.Does LOCAL_ONE know to choose local (the same)
node with SimpleStrategy?
On Sunday, April 2, 2017 4:02 PM, Sam Tunnicliffe wrote:
auth logins for super users is 101 replicas s
>
> auth logins for super users is 101 replicas serving the read
This only applies to the default superuser (i.e. 'cassandra'), which is one
of the reasons for recommending it is only used during initial setup[1].
Reads for all other users, including superusers, are done at LOCAL_ONE
[1]
http://
> You should use a network topology strategy with high RF in each DC
There's some debate here - some blogs/speakers will say to put a replica on
each instance, but that falls down above a few dozen instances. Imagine if you
have (for example) 200 instances per DC, auth logins for super users i
You should use a network topology strategy with high RF in each DC or something
like the everywhere strategy.
You should never really use SimpleStrategy, especially if you have multiple DCs
and are using LOCAL or EACH consistencies. Its more for test and dev setups
then a prod environment.
The
Hi,
what is the suitable replication strategy for system_auth keyspace?As I
understand factor should be equal to total nodes number, so can we use
SimpleStrategy? Does it ensure that queries with LOCAL_ONE consistency level
will be targeted to local DC (or the same node)?
Thanks.
