[
https://issues.apache.org/jira/browse/CASSANDRA-9594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937951#comment-14937951
]
Joshua McKenzie commented on CASSANDRA-9594:
--------------------------------------------
Sorry for the delay on this. I don't see any immediate side-effects from this
swap in ordering.
Doing a CI run on this patch just to sanity check:
[utest|https://cassci.datastax.com/view/Dev/view/josh-mckenzie/job/josh-mckenzie-9594-testall/1/]
[dtest|https://cassci.datastax.com/view/Dev/view/josh-mckenzie/job/josh-mckenzie-9594-dtest/1/]
[~yukim]: in your work w/bootstrap and/or thinking surrounding CASSANDRA-10283,
can you think of any reason why this order swap would be an issue?
> 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
> Assignee: Tommy Stendahl
> 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)
