Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 18 Sep 2014 00:41:33 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12742320.1410998147000.61725.1411000893889@Atlassian.JIRA>
In-Reply-To: <JIRA.12742320.1410998147000@Atlassian.JIRA>
References: <JIRA.12742320.1410998147000@Atlassian.JIRA>
 <JIRA.12742320.1410998147494@arcas>
Subject: [jira] [Updated] (CASSANDRA-7968) permissions_validity_in_ms should
 be settable via JMX
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams updated CASSANDRA-7968:
----------------------------------------
    Attachment:     (was: 7968.txt)

> permissions_validity_in_ms should be settable via JMX
> -----------------------------------------------------
>
>                 Key: CASSANDRA-7968
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7968
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 2.0.11, 2.1.1
>
>         Attachments: 7968.txt
>
>
> Oftentimes people don't think about auth problems and just run with the default of RF=2 and 2000ms until it's too late, and at that point doing a rolling restart to change the permissions cache can be a bit painful vs setting it via JMX everywhere and then updating the yaml for future restarts.


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