[ https://issues.apache.org/jira/browse/CASSANDRA-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863039#comment-13863039 ]
Andreas Schnitzerling commented on CASSANDRA-6463: -------------------------------------------------- Which node(s) need repair? The one(s) cleaned up or all nodes of the cluster? > 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 > Labels: authentication, cleanup, consistency, cql3, newbie, > nodetool, permissions > Fix For: 2.0.5 > > > 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.5#6160)