[jira] [Commented] (CASSANDRA-7939) checkForEndpointCollision should ignore joining nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144850#comment-14144850 ] Brandon Williams commented on CASSANDRA-7939: - bq. Based on the description I'm not clear why the patch is to check if it's not a fatClient? Because you can't retry a failed bootstrap until the fat client expires from gossip. bq. nit: in the 2.1 patch you should use RangeStreamer.useStrictConsistency vs re-parsing the property Fair enough, can fix on commit. checkForEndpointCollision should ignore joining nodes - Key: CASSANDRA-7939 URL: https://issues.apache.org/jira/browse/CASSANDRA-7939 Project: Cassandra Issue Type: Bug Components: Core Reporter: Brandon Williams Assignee: Brandon Williams Priority: Minor Fix For: 2.0.11, 2.1.1 Attachments: 7939-2.1.txt, 7939.txt If you fail a bootstrap, then immediately retry it, cFEC erroneously tells you to replace it: {noformat} ERROR 00:04:50 Exception encountered during startup java.lang.RuntimeException: A node with address bw-3/10.208.8.63 already exists, cancelling join. Use cassandra.replace_address if you want to replace this node. at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:453) ~[main/:na] at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:666) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:614) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:507) ~[main/:na] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:338) [main/:na] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:457) [main/:na] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:546) [main/:na] {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-7939) checkForEndpointCollision should ignore joining nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144880#comment-14144880 ] T Jake Luciani commented on CASSANDRA-7939: --- +1 checkForEndpointCollision should ignore joining nodes - Key: CASSANDRA-7939 URL: https://issues.apache.org/jira/browse/CASSANDRA-7939 Project: Cassandra Issue Type: Bug Components: Core Reporter: Brandon Williams Assignee: Brandon Williams Priority: Minor Fix For: 2.0.11, 2.1.1 Attachments: 7939-2.1.txt, 7939.txt If you fail a bootstrap, then immediately retry it, cFEC erroneously tells you to replace it: {noformat} ERROR 00:04:50 Exception encountered during startup java.lang.RuntimeException: A node with address bw-3/10.208.8.63 already exists, cancelling join. Use cassandra.replace_address if you want to replace this node. at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:453) ~[main/:na] at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:666) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:614) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:507) ~[main/:na] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:338) [main/:na] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:457) [main/:na] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:546) [main/:na] {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-7939) checkForEndpointCollision should ignore joining nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144236#comment-14144236 ] T Jake Luciani commented on CASSANDRA-7939: --- Based on the description I'm not clear why the patch is to check if it's not a fatClient? nit: in the 2.1 patch you should use RangeStreamer.useStrictConsistency vs re-parsing the property checkForEndpointCollision should ignore joining nodes - Key: CASSANDRA-7939 URL: https://issues.apache.org/jira/browse/CASSANDRA-7939 Project: Cassandra Issue Type: Bug Components: Core Reporter: Brandon Williams Assignee: Brandon Williams Priority: Minor Fix For: 2.0.11, 2.1.1 Attachments: 7939-2.1.txt, 7939.txt If you fail a bootstrap, then immediately retry it, cFEC erroneously tells you to replace it: {noformat} ERROR 00:04:50 Exception encountered during startup java.lang.RuntimeException: A node with address bw-3/10.208.8.63 already exists, cancelling join. Use cassandra.replace_address if you want to replace this node. at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:453) ~[main/:na] at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:666) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:614) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:507) ~[main/:na] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:338) [main/:na] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:457) [main/:na] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:546) [main/:na] {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-7939) checkForEndpointCollision should ignore joining nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136025#comment-14136025 ] Brandon Williams commented on CASSANDRA-7939: - On second thought, there's probably no need to remove the original check for 2.1; we can just double up for better protection. checkForEndpointCollision should ignore joining nodes - Key: CASSANDRA-7939 URL: https://issues.apache.org/jira/browse/CASSANDRA-7939 Project: Cassandra Issue Type: Bug Components: Core Reporter: Brandon Williams Assignee: Brandon Williams Priority: Minor Fix For: 2.0.11, 2.1.1 Attachments: 7939-2.1.txt, 7939.txt If you fail a bootstrap, then immediately retry it, cFEC erroneously tells you to replace it: {noformat} ERROR 00:04:50 Exception encountered during startup java.lang.RuntimeException: A node with address bw-3/10.208.8.63 already exists, cancelling join. Use cassandra.replace_address if you want to replace this node. at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:453) ~[main/:na] at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:666) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:614) ~[main/:na] at org.apache.cassandra.service.StorageService.initServer(StorageService.java:507) ~[main/:na] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:338) [main/:na] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:457) [main/:na] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:546) [main/:na] {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)