[ https://issues.apache.org/jira/browse/CASSANDRA-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138588#comment-14138588 ]
Benedict commented on CASSANDRA-7968: ------------------------------------- Well, it depends what you mean by deeper trouble. I don't think anybody with access to JMX can get access to any raw data, so you won't be at any risk of breaking a data policy or data _laws_. This potentially introduces that risk > 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)