After adding new node or replacing node, it will be necessary to rebalance disks across all cluster nodes.
After adding new node or replacing node, it's advisable to rebalance adapters across cluster nodes.
Aria Operations 8.x
After adding new analytics node or replacing node, disks usage will be unbalanced between the nodes. The process will start automatically after some time after new node is added. However, in some cases it's desired to start rebalance as soon as new node is added or replaced.
After adding new analytics node or replacing node, adapter instances may be unbalanced across the cluster, and it's recommended to spread the load amongst the collectors in the cluster.
After successfully adding a new data node or replacing a node in Aria Operations you will need to:
/storage/db
, /storage/log
, and /storage/core
Note: Analytics nodes are: Primary, Primary replica, and data nodes.
Aria/vRealize Operations require that all Analytics nodes have close to the same amount of disk space. This is due to collected data being shared across the analytics nodes. If one node has less disk space available for /storage/db the cluster will go down when the node with the least amount of disk space will fill up before the nodes with more disk space available for the FSDB database.
The FSDB database will balance the data across all the analytics nodes in the cluster.
Issue command df -h
in console or SSH session when logged in with root account, to determine how much disk space is required.