Tibor Repasi created CASSANDRA-20051:
----------------------------------------
Summary: nodetool reloadseeds does not actually 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
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
