Business Context
A CAS administrator is performing a routine, planned scale-out of the environment during a low-traffic maintenance window. They are adding two new worker nodes to an existing CAS cluster to increase processing capacity for the marketing analytics team's quarterly reporting. The goal is to simply confirm that the new nodes are joining the cluster as expected.
Data Preparation
This action is for server monitoring and does not operate on CAS tables. No data preparation is required. The test assumes the administrator has already initiated the `addNode` action on the controller.
Copied!
| 1 | /* No |
| 2 | data creation is necessary. This action monitors the state of the CAS server itself. */ |
Étapes de réalisation
1
Execute the addNodeStatus action to get a real-time list of nodes currently being added.
Copied!
| 1 | PROC CAS; |
| 2 | SESSION.addNodeStatus; |
| 3 | RUN; |
Expected Result
The action is expected to return a result table listing the two new machines being added. The table should contain columns like 'Node' and 'State', with the state indicating that the nodes are in the process of joining (e.g., 'pending', 'authenticating', 'connected'). This provides a quick and successful validation of the scale-out operation.