[
https://issues.apache.org/jira/browse/CASSANDRA-17062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746975#comment-17746975
]
Stefan Miklosovic commented on CASSANDRA-17062:
-----------------------------------------------
As I was reviewing that, I think that what would be interesting is to make that
vtable mutable. If it is mutable, we might implement the functionality around
resetting. E.g. if I do this
{code}DELETE FROM system_views.unweighted_caches where name = 'roles';{code}
would invalidate and reset roles cache metrics.
{code}DELETE FROM system_views.unweighted_caches;{code}
Same might be done by "TRUNCATE system_views.unweighted_caches". Truncation
would reset and invalidate it as well.
This would just reset it all.
I see there are methods for the invalidation of a cache in CacheServiceMBean
but I just finds it.
[~samt] thoughts?
> Expose Auth Caches metrics
> --------------------------
>
> Key: CASSANDRA-17062
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17062
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Virtual Tables, Observability/Metrics,
> Tool/nodetool
> Reporter: Aleksei Zotov
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
>
> Unlike to other caches (row, key, counter), Auth Caches lack some monitoring
> capabilities. Here are a few particular changes to get this inequity fixed:
> # Add auth caches to _system_views.caches_ VT
> # Expose auth caches metrics via JMX
> # Add auth caches details to _nodetool info_
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
