[
https://issues.apache.org/jira/browse/CASSANDRA-20051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896412#comment-17896412
]
Stefan Miklosovic edited comment on CASSANDRA-20051 at 11/7/24 5:12 PM:
------------------------------------------------------------------------
??The node that's wrong has a seed pointing to itself, so if you remove it, you
remove both the invalid reference and the source of the invalid reference???
That would be done WITH this patch.
1. I have 5 nodes, 10.0.0.1 to 10.0.0.5
2. All nodes have 10.0.0.5 set as a seed in cassandra.yaml
3. I execute a script which sets a seed to 10.0.0.1 on every node
4. Nodes 10.0.0.2 - 10.0.0.5 will have seed to point to 10.0.0.1 but 10.0.0.1
will still point to 10.0.0.5 because 10.0.0.1 can not set the seed to itself.
5. I go to remove 10.0.0.5
6. I will have 10.0.0.1 still pointing to 10.0.0.5
was (Author: smiklosovic):
??The node that's wrong has a seed pointing to itself, so if you remove it, you
remove both the invalid reference and the source of the invalid reference???
That would be done WITH this patch.
1. I have 5 nodes, 10.0.0.1 to 10.0.0.5
2. All nodes have 10.0.0.5 set as a seed in cassanra.yaml
3. I execute a script which sets a seed to 10.0.0.1 on every node
4. Nodes 10.0.0.2 - 10.0.0.5 will have seed to point to 10.0.0.1 but 10.0.0.1
will still point to 10.0.0.5 because 10.0.0.1 can not set the seed to itself.
5. I go to remove 10.0.0.5
6. I will have 10.0.0.1 still pointing to 10.0.0.5
> nodetool reloadseeds does not reliably reload the seeds
> -------------------------------------------------------
>
> Key: CASSANDRA-20051
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20051
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Tibor Repasi
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> During re-deploying lots of Cassandra nodes I've observed that some nodes
> does not reliably reload the seeds when {{nodetool reloadseeds}} command was
> issued.
> After the seeds list was changed in the config:
> {code}
> $ grep seeds /etc/cassandra/cassandra.yaml
> - seeds: 10.90.44.82
> $ nodetool getseeds
> Current list of seed node IPs, excluding the current node's IP:
> /10.90.40.86:7000 /10.90.44.86:7000
> $ nodetool reloadseeds
> Updated seed node IP list, excluding the current node's IP: /10.90.40.86:7000
> /10.90.44.86:7000
> {code}
> At this instance the following line was logged to debug.log:
> {code}
> DEBUG [RMI TCP Connection(103568)-127.0.0.1] 2024-11-04 14:04:27,638
> YamlConfigurationLoader.java:124 - Loading settings from
> file:/etc/cassandra/cassandra.yaml
> {code}
> However, getting the old list:
> {code}
> $ nodetool getseeds
> Current list of seed node IPs, excluding the current node's IP:
> /10.90.40.86:7000 /10.90.44.86:7000
> {code}
> These nodes read the seed list only after Cassandra was restarted:
> {code}
> $ sudo systemctl restart cassandra.service
> $ nodetool getseeds
> Seed node list does not contain any remote node IPs
> {code}
> Note: this was observed on a seed node.
> Observed on Cassandra 4.1.7.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
