[jira] [Comment Edited] (CASSANDRA-7341) Emit metrics related to CAS/Paxos

["sankalp kohli (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-7341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038039#comment-14038039 ] 

sankalp kohli edited comment on CASSANDRA-7341 at 6/19/14 10:48 PM:
--------------------------------------------------------------------

[~jbellis] You mean I move the metrics in PaxosState to CF Metrics?  This make sense to move these to individual CFs metrics. 

The metrics in StorageProxy is on lines of other ClientRequestMetrics we have there. I am not sure whether these belong to CF Metrics. 


Also regarding my last comment, should I do it here or in a different JIRA
"I am thinking about adding "top k" for contenting row. We need to know more about contention. 
Adding number of contentions in the writetimout will help a lot because it will tell us whether the failure is due to contention."



was (Author: kohlisankalp):
[~jbellis] You mean I move the metrics in PaxosState to CF Metrics?  This make sense to move these to individual CFs metrics. 

The metrics in StorageProxy is on lines of other ClientRequestMetrics we have there. I am not sure whether these belong to CF Metrics. 

> Emit metrics related to CAS/Paxos
> ---------------------------------
>
>                 Key: CASSANDRA-7341
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7341
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>            Assignee: sankalp kohli
>            Priority: Minor
>         Attachments: CASClientRequestMetrics.java, trunk-7341.diff
>
>
> We can emit metrics based on Paxos. One of them is when there is contention. I will add more metric in this JIRA if it is helpful. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)