Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3E24B106FC for ; Tue, 7 Jan 2014 23:15:51 +0000 (UTC) Received: (qmail 83983 invoked by uid 500); 7 Jan 2014 23:15:51 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 83962 invoked by uid 500); 7 Jan 2014 23:15:51 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 83953 invoked by uid 99); 7 Jan 2014 23:15:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jan 2014 23:15:51 +0000 Date: Tue, 7 Jan 2014 23:15:50 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6463) cleanup causes permission problems MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864837#comment-13864837 ] Aleksey Yeschenko commented on CASSANDRA-6463: ---------------------------------------------- Can't say, b/c I don't know what caused the issue in the first place. A topology change? Increasing RF on system_auth without running repair afterwards? Either way, just run repair on every node (just for the system_auth keyspace) - it won't take much time. > 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)