Hi,
I am having SS Cluster with 1 MA, 1 CA and 2 Leaf Nodes.
SS Version: 8.0.9, HA Enabled.
Then I promote CA to MA using this command: PROMOTE AGGREGATOR 'xxx.x.x.x':3307 TO MASTER; it worked sucessfully and CA is promoted to MA & MA demoted to CA.
When I run sdb-admin list-nodes from Newly Promoted MA, I got this error: The following nodes need to be added to the toolbox: · <>:<> [Aggregator]
[memsql@rnd-4 singlestoredb-toolbox-1.14.4-e432b273e6]$ ./sdb-admin restart-node
Before restarting the nodes, do you want to take a snapshot of all databases?
A database snapshot is beneficial in reducing the time the nodes take to recover after being restarted, but it may delay the node stopping process. [y/N]: y
+-------+------------+----------------+--------+------+---------------+---------+
| Index | MemSQL ID | Host | Role | Port | Process State | Version |
+-------+------------+----------------+--------+------+---------------+---------+
| 1 | 8029C | <> | Master | 33xx | Running | 8.0.9 |
| 2 | 9E6D0 | <> | Leaf | 33xx | Running | 8.0.9 |
| 3 | 96C19D | <> | Leaf | 33xx | Running | 8.0.9 |
| 4 | All Nodes | | | | | |
+-------+------------+----------------+--------+------+---------------+---------+
Select an option: 4
Toolbox is about to perform the following actions:
· Restart all nodes in the cluster
Would you like to continue? [y/N]: y
✓ Snapshots completed
✓ Successfully connected to host <>
✓ Successfully connected to host <>
✓ Successfully connected to host <>
Discovered 1 SingleStore DB nodes in the cluster which do not appear in 'sdb-admin list-nodes'.
Make sure all nodes in the cluster are visible and online.
The following nodes need to be added to the toolbox:
· <>:<> [Aggregator]
To ignore the error and continue, re-run this command with the --force flag
Pls let me know how to add [AGGREEGATOR] Node in toolbox so that I can run restart,stop,start all nodes in SS Cluster from Newly Promoted MA.
Also Newly Promoted MA is not showing the CA(AGGREGATOR) in sdb-admin list-nodes command:
Logs:
[memsql@rnd-4 singlestoredb-toolbox-1.14.4-e432b273e6]$ ./sdb-admin list-nodes
+------------+--------+----------------+------+---------------+--------------+---------+----------------+--------------------+--------------+
| MemSQL ID | Role | Host | Port | Process State | Connectable? | Version | Recovery State | Availability Group | Bind Address |
+------------+--------+----------------+------+---------------+--------------+---------+----------------+--------------------+--------------+
| 8029C> | Master | <> | 33xx | Running | True | 8.0.9 | Online | | 0.0.0.0 |
| 9E6D0> | Leaf | <> | 33xx | Running | True | 8.0.9 | Online | 2 | 0.0.0.0 |
| 96C19> | Leaf | <> | 33xx | Running | True | 8.0.9 | Online | 1 | 0.0.0.0 |
+------------+--------+----------------+------+---------------+--------------+---------+----------------+--------------------+--------------+
The Newly Demoted CA is showing CA+MA nodes in sdb-admin commands:
As Newly Demoted CA is able to run sdb-admin start, stop ,restart commands as MA and CA both nodes are seen in list-nodes command.
[memsql@rnd-2 singlestoredb-toolbox-1.14.4-e432b273e6]$ ./sdb-admin list-nodes
+------------+------------+----------------+------+---------------+--------------+---------+----------------+--------------------+--------------+
| MemSQL ID | Role | Host | Port | Process State | Connectable? | Version | Recovery State | Availability Group | Bind Address |
+------------+------------+----------------+------+---------------+--------------+---------+----------------+--------------------+--------------+
| 8029C> | Master | <> | 33xx | Running | True | 8.0.9 | Online | | 0.0.0.0 |
| 284B> | Aggregator | <>< | 33xx | Running | True | 8.0.9 | Online | | 0.0.0.0 |
| 9E6D> | Leaf | <> | 33xx | Running | True | 8.0.9 | Online | 2 | 0.0.0.0 |
| 96C1> | Leaf | <> | 33xx | Running | True | 8.0.9 | Online | 1 | 0.0.0.0 |
+------------+------------+----------------+------+---------------+--------------+---------+----------------+--------------------+--------------+