[ 
https://issues.apache.org/jira/browse/CASSANDRA-16411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-16411:
-------------------------------------------
          Since Version: NA
    Source Control Link: 8762267b13fffb921ae79b0220630f10695ee9d9 
https://github.com/riptano/ccm/commit/e5870fd081a927b6d4bad47719b1b1f893d70c3e 
https://github.com/apache/cassandra-dtest/commit/ad9462ee737ebc92a86cb5b266fccdd93e1111a9
  (was: 
https://issues.apache.org/jira/browse/CASSANDRA-16411?focusedCommentId=17282541&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17282541)
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

Coordinated with everyone, and committed remaining fix as 
[8762267b13fffb921ae79b0220630f10695ee9d9|https://github.com/apache/cassandra-dtest/commit/8762267b13fffb921ae79b0220630f10695ee9d9].

> 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, 4.0-beta
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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. Let's see 
> an example:
> - populate [1, 1, 1]
> - Node1 sees: dc1/ip1, dc2/ip2 and dc3/ip3
> - Node2 sees: dc1/ip1, dc2/ip2 and dc3/ip3
> - Node3 sees: dc1/ip1, dc2/ip2 and dc3/ip3
> - Add a new Node4
> - Node4 sees: dc1/ip1+ip2+ip3+ip4
> All multi-dc dtests that add a node after cluster creation suffer this 
> problem.
> Solution: When a new node is added without specifying a dc in dtests check 
> for existing dcs. If there are any force to specify one to update the 
> topology file.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to