Deleting an ASE cluster node
You can delete an inactive API Security Enforcer (ASE) cluster node that has either become unreachable or has been stopped.
About this task
To identify which cluster nodes are inactive and should be removed:
Steps
-
Run the
cluster_info
command.Example:
/opt/pingidentity/ase/bin/cli.sh cluster_info -u admin -p cluster id : ase_cluster cluster nodes 127.0.0.1:8020 active Step 1.1.1.1:8020 active Step 2.2.2.2:8020 inactive 172.17.0.4:8020(tasks.aseservice) active 172.17.0.5:8020(tasks.aseservice) inactive tasks.aseservice2:8020 not resolved
-
To delete the inactive node, run the
delete_cluster_node
command:/opt/pingidentity/ase/bin/cli.sh delete_cluster_node <IP:Port>
Example:
From the previous example, to remove inactive cluster nodes 2.2.2.2:8020 and 172.17.05:8020, it would look like the following:
/opt/pingidentity/ase/bin/cli.sh delete_cluster_node 2.2.2.2:8020 /opt/pingidentity/ase/bin/cli.sh delete_cluster_node 172.17.05:8020