Follow the steps here when the Aster Software running on a worker node is having problems, but the node VM is fine.
- Remove the worker node from AMC. Log on to AMC, select X. and remove the worker node by clicking the
- Balance data across all available nodes. In AMC, select Balance Data. and click
- Terminate the worker node from AWS. Log on to AWS, select EC2, search for the instance and pick the worker node, then select .
-
Expand the number of nodes in AWS. Select Details page shown, update Desired, Min and Max to N+1, where N is the current number of nodes.
, and select the affected cluster . On the Make sure that all the three parameters Desired, Min and Max are set to the same number.Wait until the newly added node is deployed and initialized in AWS.
-
SSH to the queen node, load the Aster environment /home/beehive/config/asterenv.sh, and balance data across all available nodes.
source /home/beehive/config/asterenv.sh > ncli system balancedata
-
Verify the failover is complete.
-
Make sure that all nodes are in active mode.
> ncli node show
- Make sure the value in /home/beehive/config/initialPartitionCount is the same as that in /home/beehive/config/totalPartitionCount.
- In AWS, verify that the newly added node has the same network configuration (VPC, Availability Zone, Subnet, Security Group) as the existing nodes.
- Make sure you are be able to ssh on to the new node using the same key pair.
- Log on to AMC, in Nodes tab, verify that the new node has at least one primary partition.
-
Make sure that all nodes are in active mode.