Hi Vitali,
>From my point of view, I think that what you propose is the right solution.
With READ ONE and WRITE ALL, we shall still have a strong consistency.
I am going to add a comment in the ticket 5310.
Thanks.
Jean Armel
2013/3/7 Vitalii Tymchyshyn
> Why not WRITE.ALL READ.ONE? I don'
Why not WRITE.ALL READ.ONE? I don't think permissions are updated often and
READ.ONE provides maximum availability.
2013/3/4 aaron morton
> In this case, it means that if there is a network split between the 2
> datacenters, it is impossible to get the quorum, and all connections will
> be reje
AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Consistency level for system_auth keyspace
Hi Dean,
The new authentication modules currently uses a QUORUM consistency level when
checking the user.
That is the rea
, 2013 9:12 AM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Subject: Re: Consistency level for system_auth keyspace
>
> Hi Aaron,
>
> I have open a ticket in Jira
...@gmail.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Monday, March 4, 2013 9:12 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>&
Hi Aaron,
I have open a ticket in Jira :
https://issues.apache.org/jira/browse/CASSANDRA-5310
Reading the user using the QUORUM consistency level means that in case of
network outage, you are unable to open a connection, and all your data
become unavailable.
Regards.
Jean Armel
2013/3/4 aaron m
> In this case, it means that if there is a network split between the 2
> datacenters, it is impossible to get the quorum, and all connections will be
> rejected.
Yes.
> Is there a reason why Cassandra uses the Quorum consistency level ?
I would guess to ensure there is a single, cluster wide,
