You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksei Zotov (Jira)" <ji...@apache.org> on 2021/10/24 21:08:00 UTC
[jira] [Updated] (CASSANDRA-17063) Make
capacity/validity/updateinterval for Auth Caches configurable
[ https://issues.apache.org/jira/browse/CASSANDRA-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksei Zotov updated CASSANDRA-17063:
--------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Fix Version/s: 4.x
Status: Open (was: Triage Needed)
> Make capacity/validity/updateinterval for Auth Caches configurable
> ------------------------------------------------------------------
>
> 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) 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org