[jira] [Commented] (CASSANDRA-16411) Fix topology corruption on joining nodes without DC in dtests

["Berenguer Blasi (Jira)" <ji...@apache.org>]

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

Berenguer Blasi commented on CASSANDRA-16411:
---------------------------------------------

The change is in the ccm repo. Dtest repro just points to the new cmm and cassandra repro just points to the new dtests repro.

Testing involved raising at least 2 nodes + a 3rd one so it was unnecessarily heavy. Testing for this ticket will be added in CASSANDRA-16296 where we already need such a cluster for the sake QA speed.

> Fix topology corruption on joining nodes without DC in dtests
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-16411
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16411
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/dtest/python
>            Reporter: Berenguer Blasi
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0-beta5, 4.0
>
>
> Dtests with multi-dc setups don't update the topology properties file of a newly joining node without dc post cluster creation.
> The new node will join dc1 but it's snitch will report the default snitch config as it doesn't get updated == dc1 == all nodes are in dc1 == there are no other dcs. That leads to bootstrap, token, startup,... problems.
> Solution: When a new node is added without specifying a dc in dtests check for existing dcs. If there are any update the topology file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org