Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9EAFD9B1E for ; Mon, 6 Feb 2012 05:14:55 +0000 (UTC) Received: (qmail 94054 invoked by uid 500); 6 Feb 2012 05:14:48 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 93438 invoked by uid 500); 6 Feb 2012 05:14:27 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 93406 invoked by uid 99); 6 Feb 2012 05:14:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Feb 2012 05:14:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Feb 2012 05:14:19 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 952C61A52B7 for ; Mon, 6 Feb 2012 05:13:59 +0000 (UTC) Date: Mon, 6 Feb 2012 05:13:59 +0000 (UTC) From: "Peter Schuller (Created) (JIRA)" To: commits@cassandra.apache.org Message-ID: <53377643.816.1328505239612.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (CASSANDRA-3858) expose "propagation delay" metric in JMX MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 expose "propagation delay" metric in JMX ---------------------------------------- Key: CASSANDRA-3858 URL: https://issues.apache.org/jira/browse/CASSANDRA-3858 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Peter Schuller Priority: Minor My idea is to augment the gossip protocol to contain timestamps. We wouldn't use the timestamps for anything "important", but we could use them to allow each node to expose a number which is the number of milliseconds (or seconds) "old" information is about nodes that are "the oldest" and also alive. When nodes go down you'd see spikes, but for most cases where nodes live, this information should give you a pretty good idea of how fast gossip information is propagating through the cluster, assuming you keep your clocks in synch. It should be a good thing to have graphed, and to have alerts on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira