Lesen und beachten Sie die Automation Anywhere-Dokumentation

Automation Anywhere Automation 360

Inhalt schließen

Inhalte

Inhalt öffnen

Remove nodes in cluster setup

  • Aktualisiert: 2021/10/13
    • Automation 360 v.x
    • Erkunden
    • RPA Workspace

Remove nodes in cluster setup

As a RPA platform administrator, you can remove one or more existing original nodes from the multi node Control Room cluster if any of the existing nodes needs replacement for upgrade or to enhance the performance.

Vorbereitungen

Ensure the following:

  • All primary nodes and databases have a backup in place.
  • You have administrator/root privileges on the Control Room Servers.
You can remove one or more nodes from an existing cluster. This task describes about the scenario to remove the three existing nodes and replacing with three new nodes in an existing cluster.

Prozedur

  1. To verify the master node, use the following Elasticsearch API through a browser or API tool.
    https://172.31.18.37/_cat/nodes
  2. Log in to the server as an administrator and run the following command to stop all Control Room services.
    services.msc
    Log in on any one of the original nodes N2 or N3 and not the master node N1.
    Similarly, shut down all Control Room services for the master node N1.
  3. To verify the cluster health, use the following Elasticsearch API through a browser or API tool.
    From a browser navigate to any cluster node IP address using the Elasticsearch port 47599 and use the _cat/nodes API.
    https://172.31.18.37/_cat/nodes
    Anmerkung: The master node is indicated by the asterix (*).
  4. Edit the cluster.properties file located at: C:\Program Files\Automation Anywhere\Automation 360\config.
  5. Remove the IP addresses for the original three nodes.
    Anmerkung: Perform this action for all the nodes in the cluster. Do not disturb the sequence of the IP address while removing the IP address of the original three nodes.
  6. Edit the elasticsearch.yml file at: C:\Program Files\Automation Anywhere\Automation 360\elasticsearch\config.
  7. Remove the IP addresses for the original three nodes from the discovery.zen.ping.unicast.hosts attribute.
    Anmerkung: The discovery.zen.ping.unicast.hosts attribute must contain the IP addresses for new nodes only and in the same sequence within the file on each node.
  8. To verify the new master node, use the following Elasticsearch API through a browser or API tool.
    https://172.31.18.37/_cat/nodes
  9. Update the new master IP address in the cluster.initial_master_nodes attribute.
  10. Run the following command to start the services on each node.
    services.msc
    You must start the services on the master node at the end.
  11. To verify the final cluster health, use the Elasticsearch API through a browser or API tool.
    1. From a browser navigate to any cluster node IP address using the Elasticsearch port 47599 and use the _cat/nodes API.
      https://172.31.30.120:47599/_cat/nodes
      Anmerkung: The master node is indicated by the asterix (*).
    2. From a browser navigate to any cluster node IP address using the Elasticsearch port 47599 and use the _cat/health?pretty API
      https://172.31.30.120:47599/_cat/health?pretty
    Anmerkung: You must wait until the replication status is showing green. The replication time varies depending on the amount of data load in the clusters. The replication status turns green when the cluster is fully synchronized.
Feedback senden