Automatically Replacing Cluster Nodes

• Console
• CLI
• API

• 1. On the Clusters list page, select the cluster that you want to work with. If you need help finding the list page or the cluster, see Listing Clusters in a Compartment.
  2. On the Cluster details page, under Resources, select Replace node configurations.
  3. Select Create replace node configuration.
  4. Enter the Replace node configuration name.
  5. Select the Level type.
  6. If you select Node level in the Node level field, the Host name field is displayed. Select host from the available hosts in the dropdown list.
  7. If you select Node type level in the Node level field, the Node type field is displayed. Select Master, Utility, or Edge from the dropdown list.
  8. Select the Host name.
  9. Select the Metric type. The options available include:
     • Instance status
     • Instance accessibility status
  10. To set the number of minutes to wait before triggering automatic replacement, enter the Duration in minutes.
  11. Enter the Cluster admin password.
  12. Select Submit.
      Note
      
      

      If you replace an active Ambari node (un0), the Ambari node is moved to a standby node (un1).

  13. After node replacement is successful, sign in to Ambari and verify the health of services. Then, restart the services that are flagged for stale configuration.

• Use the create-node-replace-configuration command and required parameters to automatically replace cluster nodes.

  oci bds instance create-node-replace-configuration  [OPTIONS]

  For a complete list of flags and variable options for CLI commands, see the Command Line Reference for Big Data.

• Use the CreateNodeReplaceConfiguration operation to automatically replace nodes in a cluster.