You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2017/08/04 16:44:00 UTC
[jira] [Commented] (CASSANDRA-13744) Better bootstrap failure
message when blocked by (potential) range movement
[ https://issues.apache.org/jira/browse/CASSANDRA-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114605#comment-16114605 ]
Jeff Jirsa commented on CASSANDRA-13744:
----------------------------------------
Patch looks good to me, but before we commit, can you kick off a unit test run with circleci or jenkins, and a dtest run using the ASF jenkins? Just to be sure we don't
break any existing tests.
> Better bootstrap failure message when blocked by (potential) range movement
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-13744
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13744
> Project: Cassandra
> Issue Type: Bug
> Reporter: mck
> Assignee: mck
> Priority: Trivial
> Fix For: 4.0, 3.11.x
>
> Attachments: cassandra-3.11_13744.txt, trunk_13744.txt
>
>
> The UnsupportedOperationException thrown from {{StorageService.joinTokenRing(..)}} when it's detected that other nodes are bootstrapping|leaving|moving offers no information as to which are those other nodes.
> In a large cluster this might not be obvious nor easy to discover, gossipinfo can hold information that takes a bit of effort to uncover. Even when it is easily seen which nodes are in those states it's helpful to have it confirmed.
> Attached is the patch that provides a more thorough exception message to the failed bootstrap attempt.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org