Reinitializing Nodes

Reinitializes a node, such that all configuration settings and all data are lost. This HTTP method and URI should be used with caution: a backup of all data on the system is recommended to be performed before reinitialization.

This HTTP method and URI are intended for use subsequent to an unsafe failover; which results in multiple failed-over nodes needing reinitialization before they can be added back into the cluster.

The Full Admin role is required.

After its reinitialization, a reinitialized node can be reconfigured. Note that the call is idempotent, and can be used on the same node multiple times, with the same result.

For detailed information on unsafe failover and its consequences, see Hard Failover in Default and Unsafe Modes. For information on reinitialization, see Cluster Initialization and Provisioning.

The ip-address-or-domain-name must be that of the node that is to be reinitialized. The username and password must be those of a user with the Full Admin role.

Success returns 200 OK. Failure to authenticate returns 401 Unauthorized. A malformed URI returns 404 Object Not Found with the message requested resource not found.

The following example reinitializes node 10.145.250.103.

For the REST API for hard failover, see Performing Hard Failover. For detailed information on unsafe failover and its consequences, see Hard Failover in Default and Unsafe Modes. For information on reinitialization, see Cluster Initialization and Provisioning.