[
https://issues.apache.org/jira/browse/CASSANDRA-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115266#comment-16115266
]
mck commented on CASSANDRA-13744:
---------------------------------
|| branch || testall || dtest ||
|
[cassandra-3.11_13744|https://github.com/michaelsembwever/cassandra/tree/thelastpickle/cassandra-3.11_13744]
|
[testall|https://circleci.com/gh/michaelsembwever/cassandra/tree/thelastpickle%2Fcassandra-3.11_13744]
|
[dtest|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/161]
|
|
[trunk_13744|https://github.com/michaelsembwever/cassandra/tree/thelastpickle/trunk_13744]
|
[testall|https://circleci.com/gh/michaelsembwever/cassandra/tree/thelastpickle%2Ftrunk_13744]
|
[dtest|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/162]
|
> 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: 3.11.x, 4.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
