The `addNode` action dynamically adds one or more machines to a running SAS Cloud Analytic Services (CAS) server. This is a fundamental administrative task for scaling a CAS environment, allowing for the expansion of computational resources without restarting the entire server. It can be used to add either worker nodes to increase processing power and data capacity, or a backup controller to enhance high availability. This action is typically performed by administrators to manage the cluster's topology in response to changing workloads.
| Parameter | Description |
|---|---|
| node | Specifies the hostnames of the machines to be added to the server. You can provide a single hostname or a list of multiple hostnames. |
| role | Specifies the role of the new machine(s). Use 'WORKER' to add computational nodes for processing data. Use 'CONTROLLER' to add a backup controller for high availability. Note that only two controllers (one primary, one backup) are supported in a CAS cluster. The default value is 'WORKER'. |
The `addNode` action is an administrative function used to manage the CAS server infrastructure. It does not operate on or require any specific dataset. The examples below demonstrate how to call the action to modify the server topology.
/* No data setup is needed for this action. The examples focus on server administration. */
This example demonstrates the most common use case: adding a single new worker machine to the CAS cluster to increase its processing capacity.
| 1 | PROC CAS; |
| 2 | BUILTINS.addNode / |
| 3 | node={"casworker01.example.com"}, |
| 4 | role="WORKER"; |
| 5 | RUN; |
To significantly scale up the cluster's computational power, you can add a list of multiple worker machines in a single action call. This is efficient for large-scale expansions.
| 1 | PROC CAS; |
| 2 | BUILTINS.addNode / |
| 3 | node={"casworker02.example.com", "casworker03.example.com", "casworker04.example.com"}, |
| 4 | role="WORKER"; |
| 5 | RUN; |
This example shows how to add a backup controller to a CAS server that was initially started with only a primary controller. This is a critical step for establishing a high-availability (HA) configuration, ensuring server operations can failover if the primary controller becomes unavailable.
| 1 | PROC CAS; |
| 2 | BUILTINS.addNode / |
| 3 | node={"cascontroller02.example.com"}, |
| 4 | role="CONTROLLER"; |
| 5 | RUN; |
A retail analytics team is preparing for a major holiday sales event. They anticipate a surge in data processing for real-time customer behavior analysis and need to expand thei...
A financial services firm is upgrading its CAS environment to ensure business continuity. The current setup has a single point of failure at the controller level. The objective ...
An administrator, unaware that the CAS cluster is already configured for high availability (with a primary and a backup controller), attempts to add another controller. This tes...