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

Ariel Weisberg commented on CASSANDRA-9526:
-------------------------------------------

|[Updated pull request (branch name is 
wrong)|https://github.com/apache/cassandra/compare/cassandra-2.2...aweisberg:CASSANDRA-9525-v2?expand=1]|[utests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-9525-v2-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-9525-v2-dtest/]|

> Provide a JMX hook to monitor phi values in the FailureDetector
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-9526
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9526
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Ron Kuris
>            Assignee: Ron Kuris
>              Labels: docs-impacting
>             Fix For: 2.2.4, 3.0.0
>
>         Attachments: Monitor-Phi-JMX.patch, Phi-Log-Debug-When-Close.patch, 
> Tiny-Race-Condition.patch
>
>
> phi_convict_threshold can be tuned, but there's currently no way to monitor 
> the phi values to see if you're getting close.
> The attached patch adds the ability to get these values via JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to