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

Ekaterina Dimitrova commented on CASSANDRA-16411:
-------------------------------------------------

Thanks [~Bereng], I found the links.

Posting here for visibility:
 * 
[2.1|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/370/]
 * 
[2.2|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/371/]
 * 
[3.0|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/372/]
 * 
[3.11|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/373/]
 * 
[trunk|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/374/]

I saw only one new commitlog related test failure on trunk but it is also 
failing with other unrelated patches in dev, also it seems it has nothing in 
common with this one.

+1 from me, thank you

> 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-beta
>
>
> 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