[
https://issues.apache.org/jira/browse/CASSANDRA-17062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747436#comment-17747436
]
Stefan Miklosovic commented on CASSANDRA-17062:
-----------------------------------------------
The name of the newly introduced table - "unweighted_caches" is somehow
unfortunate. As a user, I would not have a clue what I get by querying that.
Maybe renaming that table to "auth_caches" is more appropriate? However, that
limits us to putting auth-related caches there in the future.
I was trying to model how one table with both cache types would look like and
there are two columns which are not in unweighted (capacity_bytes and
size_bytes) and one in unweighted which is not in weighted (capacity) so we
would need to come up with some "n/a" values if we combine that and that looks
even worse.
Also, if mutation is going to be introduced and one e.g. do TRUNCATE, I do not
think that an operator truly wants to invalidate both caches at once. If we
wanted to invalidate just e.g. unweighted, we would do "DELETE FROM
system_views.caches WHERE unweighted = true" but again, TRUNCATE would not make
any difference.
I think we just need to go with the original proposal - to name in
"unweighted_caches" and so to dedicate a separate table for that.
> 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]
