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 you
> serving requests.
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 <
jaibheem...@gmail
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, however that entails it's own
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 a
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 ti
You can build a jar from the SimpleAuthenticator and SimpleAuthority
classes found in the examples.
Then put the jar on the classpath of the cassandra, nicest way is to
modify the startup script:
put an s with options on line 148 in bin/cassandra:
args=`getopt vfhp:bD: "$@"`
becomes (note the add
Sent from my iPad
On Jun 28, 2012, at 8:45 AM, Christof Bornhoevd wrote:
> Hi,
>
> we are using Cassandra v1.0.8 with Hector v1.0-5 and would like to move our
> current system to an operational setting based on Amazon AWS. What are best
> practices for addessing security for Cassandra on A
Hi,
we are using Cassandra v1.0.8 with Hector v1.0-5 and would like to move our
current system to an operational setting based on Amazon AWS. What are best
practices for addessing security for Cassandra on AWS. Besides Security
Groups in AWS how is Cassandra Client to Cluster authentication handle
