You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2015/01/20 18:09:54 UTC

[jira] [Updated] (CASSANDRA-8016) Auth tables should use higher consistency level

     [ https://issues.apache.org/jira/browse/CASSANDRA-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

T Jake Luciani updated CASSANDRA-8016:
--------------------------------------
    Fix Version/s:     (was: 2.0.12)
                   2.0.13

> Auth tables should use higher consistency level
> -----------------------------------------------
>
>                 Key: CASSANDRA-8016
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8016
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: Aleksey Yeschenko
>             Fix For: 2.0.13
>
>
> The Auth code in Cassandra uses CL.ONE or CL.LOCAL_ONE except in the case of the superuser.
> Since the Auth keyspace is created with RF=1 the default experience is fine.
> However if you change to RF > 1 suddenly the select statements are open to misses.
> We should change reads/writes in Auth, PasswordAuthenticator, CassandraAuthorizer to always use LOCAL_QUORUM/QUORUM.
> For reads we could optimize the code to start with CL.ONE and on a miss increase to CL.QUORUM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)