[
https://issues.apache.org/jira/browse/CASSANDRA-16327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Gusa updated CASSANDRA-16327:
------------------------------------
Change Category: Quality Assurance
Complexity: Low Hanging Fruit
Component/s: Observability/Metrics
Status: Open (was: Triage Needed)
> Add metric for checking the token-awarness of the users
> -------------------------------------------------------
>
> Key: CASSANDRA-16327
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16327
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Metrics
> Reporter: Stefan Gusa
> Priority: Normal
>
> In order to increase the speed of the interaction with a Cassandra database,
> especially when the consistency level and the replication factor settings
> make one node enough for responding, having knowledge of the token allocation
> among the nodes and querying the specific node which holds the data requested
> might be a good solution. Basically, in these conditions, the internode
> communication latency is eliminated.
> A metric which counts the number of queries that resolve on the coordinator
> node, and the number of those which do not, might be useful for the client
> applications which are designed to be token-aware as this way it would be
> easy to see if they work as expected (the number of remote executed queries
> is low) or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
