cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Schnitzerling (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-6463) cleanup causes permission problems
Date Mon, 09 Dec 2013 13:10:07 GMT
Andreas Schnitzerling created CASSANDRA-6463:
------------------------------------------------

             Summary: cleanup causes permission problems
                 Key: CASSANDRA-6463
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6463
             Project: Cassandra
          Issue Type: Bug
          Components: Core, Tools
         Environment: Windows 7 / Java 1.7.0.25
            Reporter: Andreas Schnitzerling
             Fix For: 2.0.4


After a cleanup I loose permissions (f.e. SELECT, MODIFY). When I listed the system_auth/permissions
CF after cleanup I recognized, around the half of all permissions lost - BUT: If I list the
permissions table with consistency ALL, all entries appear again and my programm continues
working. Only if I manual trigger that read-repair! That tells me indirect, that system_auth
is reading using consistency ONE, what causes problems after cleanup (?). A good approach
(?) could be to re-read system_auth after permission fail with consistency > ONE to trigger
read-repair once and keep speed.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message