Btw.: I created an issue for that some months ago
https://issues.apache.org/jira/browse/CASSANDRA-12991
2017-04-01 22:25 GMT+02:00 Roland Otta :
> thank you both chris and benjamin for taking time to clarify that.
>
>
> On Sat, 2017-04-01 at 21:17 +0200, benjamin roth wrote:
>
> Tl;Dr: there are
>
> 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://
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
where can we check gossip information of a node ?? I couldn't find
anything in System keyspace.
Is it possible to update or refresh Gossiping information on a node without
restarting. Does enabling and disabling Gossip will help to refresh Gossip
information on that node.
Thanks
Prany.
Hi –
We’ve had what looks like an OOM situation with Cassandra (we have a dump
file that got generated) in our staging (performance/load testing environment)
and I wanted to reach out to this user group to see if you had any
recommendations on how we should approach our investigation as to the
