Hi,
We have 11/11 node cluster running Cassandra 2.1.15 version.
We are observing that 3 nodes from each data center are becoming
unresponsive for short period of time.
This behavior is happening only in 6 nodes (i.e. 3 from each data center)
and we are seeing a lot of Gossip stage has pending
Thanks Ben,
RF 3 isn't sufficient for system_auth? as we are using 3 RF for other
production KS, do you see any challenges?
On Wed, Jan 18, 2017 at 2:39 PM, Ben Bromhead wrote:
> We have a process that syncs and manages RF==N and we also control and
> manage users,
We have a process that syncs and manages RF==N and we also control and
manage users, however that entails it's own set of challenges and
maintenance.
For most users I would suggest 3 < RF <=5 is sufficient. Also make sure you
don't use the user "Cassandra" in production as authentication queries
the volume of data is pretty low + you still want to be able to
authenticate even if you have more nodes down than the RF for other
keyspaces. Essentially you don't want auth to be the thing that stops you
serving requests.
On Wed, 18 Jan 2017 at 14:57 Jai Bheemsen Rao Dhanwada <
Thank you
On Wed, Jan 18, 2017 at 10:10 PM, Ben Bromhead wrote:
> the volume of data is pretty low + you still want to be able to
> authenticate even if you have more nodes down than the RF for other
> keyspaces. Essentially you don't want auth to be the thing that stops
Hello, fellow Apache enthusiast. Thanks for your participation, and
interest in, the projects of the Apache Software Foundation.
I wanted to remind you that the Call For Papers (CFP) for ApacheCon
North America, and Apache: Big Data North America, closes in less than a
month. If you've been
Hello,
When enabling Authentication on cassandra, is it required to set the RF
same as the no.of nodes(
https://docs.datastax.com/en/cql/3.1/cql/cql_using/update_ks_rf_t.html)? or
can I live with RF of 3 in each DC (other KS are using 3)
If it has to be equal to the number of nodes then, every