Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 24 Jun 2015 12:54:04 +0000 (UTC)
From: "Tommy Stendahl (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12837510.1434141538000.1601.1435150444660@Atlassian.JIRA>
In-Reply-To: <JIRA.12837510.1434141538000@Atlassian.JIRA>
References: <JIRA.12837510.1434141538000@Atlassian.JIRA>
 <JIRA.12837510.1434141538871@arcas>
Subject: [jira] [Commented] (CASSANDRA-9594) metrics reporter doesn't start
 until after a bootstrap
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tommy Stendahl commented on CASSANDRA-9594:
-------------------------------------------

I created a patch that starts the metrics reporter before {{o.a.c.service.StorageService#registerDaemon}}. Its based on the 2.0 branch and should merge to other branches without problem.

> metrics reporter doesn't start until after a bootstrap
> ------------------------------------------------------
>
>                 Key: CASSANDRA-9594
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9594
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Eric Evans
>            Priority: Minor
>              Labels: lhf
>         Attachments: 9594.txt
>
>
> In {{o.a.c.service.CassandraDaemon#setup}}, the metrics reporter is started immediately after the invocation of {{o.a.c.service.StorageService#initServer}}, which for a bootstrapping node may block for a considerable period of time.  If the metrics reporter is your only source of visibility, then you are blind until the bootstrap completes.


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