cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7968) permissions_validity_in_ms should be settable via JMX
Date Fri, 30 Jan 2015 22:17:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299288#comment-14299288
] 

Aleksey Yeschenko commented on CASSANDRA-7968:
----------------------------------------------

Can't get rid of something that's never been in, can you?

I'm against adding this because I want that whole cache thing gone in favor of pushing that
responsibility to individual implementations. Would be silly to add it, and almost immediately
deprecate it.

> 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)

Mime
View raw message