Was this page helpful?
Caution
You're viewing documentation for a previous version of Scylla Manager. Switch to the latest stable version.
Although Scylla Manager is aware of all topology changes made within every cluster it manages, it cannot properly manage a cluster without establishing connections with every node in the cluster using the Scylla Manager Agent which is on each managed node.
Procedure
Add Scylla Manager Agent to the new node. Use the same authentication token as you did for the other nodes in this cluster. Do not generate a new token.
Confirm the node / datacenter was added by checking its sctool status. From the node running Scylla Manager server run the sctool status command, using the name of the managed cluster.
sctool status -c prod-cluster
Datacenter: eu-west
╭────┬────────────┬───────────┬───────────┬───────────────┬──────────┬──────┬──────────┬────────┬──────────┬──────────────────────────────────────╮
│ │ Alternator │ CQL │ REST │ Address │ Uptime │ CPUs │ Memory │ Scylla │ Agent │ Host ID │
├────┼────────────┼───────────┼───────────┼───────────────┼──────────┼──────┼──────────┼────────┼──────────┼──────────────────────────────────────┤
│ UN │ UP (4ms) │ UP (3ms) │ UP (2ms) │ 34.203.122.52 │ 237h2m1s │ 4 │ 15.43GiB │ 4.1.0 │ 2.2.0 │ 8bfd18f1-ac3b-4694-bcba-30bc272554df │
│ UN │ UP (15ms) │ UP (11ms) │ UP (12ms) │ 10.0.138.46 │ 237h2m1s │ 4 │ 15.43GiB │ 4.1.0 │ 2.2.0 │ 238acd01-813c-4c55-bd65-5219bb19bc20 │
│ UN │ UP (17ms) │ UP (5ms) │ UP (7ms) │ 10.0.196.204 │ 237h2m1s │ 4 │ 15.43GiB │ 4.1.0 │ 2.2.0 │ bde4581a-b25e-49fc-8cd9-1651d7683f80 │
│ UN │ UP (10ms) │ UP (4ms) │ UP (5ms) │ 10.0.66.115 │ 237h2m1s │ 4 │ 15.43GiB │ 4.1.0 │ 2.2.0 │ 918a52aa-cc42-43a4-a499-f7b1ccb53b18 │
╰────┴────────────┴───────────┴───────────┴───────────────┴──────────┴──────┴──────────┴────────┴──────────┴──────────────────────────────────────╯
There is no need to perform any action in Scylla Manager after removing a node or datacenter from a Scylla cluster.
Was this page helpful?