Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 3 Jun 2015 17:37:38 +0000 (UTC)
From: "Ron Kuris (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12834351.1433186954000.2454.1433353058313@Atlassian.JIRA>
In-Reply-To: <JIRA.12834351.1433186954000@Atlassian.JIRA>
References: <JIRA.12834351.1433186954000@Atlassian.JIRA>
 <JIRA.12834351.1433186954076@arcas>
Subject: [jira] [Commented] (CASSANDRA-9526) Provide a JMX hook to monitor
 phi values in the FailureDetector
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ron Kuris commented on CASSANDRA-9526:
--------------------------------------

Blog post with related info: http://hackers.lookout.com/2015/06/cassandra-phi/

> 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
>             Fix For: 2.0.x
>
>         Attachments: Monitor-Phi-JMX.patch.txt, PHI-Log-Debug-When-Close.patch.txt, PHI-Race-Condition.patch.txt
>
>
> 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)