[ https://issues.apache.org/jira/browse/CASSANDRA-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksei Zotov updated CASSANDRA-17063: -------------------------------------- Summary: Make capacity/validity/updateinterval/activeupdate for Auth Caches configurable via nodetool (was: Make capacity/validity/updateinterval/active_update for Auth Caches configurable via nodetool) > Make capacity/validity/updateinterval/activeupdate for Auth Caches > configurable via nodetool > -------------------------------------------------------------------------------------------- > > Key: CASSANDRA-17063 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17063 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool > Reporter: Aleksei Zotov > Assignee: Aleksei Zotov > Priority: Normal > Fix For: 4.x > > > Currently Auth Caches configuration options > (capacity/validity/updateinterval/active_update) exposed via JMX or yaml > only. We need to introduce a _nodetool setauthcachecapacity_ command. > Also we can think of some VT-based alternative to {_}nodetool{_}. But I feel > there is no need to have a separate table for Auth Caches configs. It would > be an overhead. Ideally we need to have a separate VT that shows/sets all the > configs, but it is out of the scope. -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org