Decommissioning a Node and Uninstalling Data Fabric Software from the Command-line
Use the following procedure to remove a node and uninstall the data-fabric software. This procedure detaches the node from the cluster and removes the data-fabric packages, log files, and configuration files, but does not format the disks.
Complete the following steps to permanently decommission a node:
- Drain the node of data by moving the node to the
/decommissioned
physical topology. All the data on a node in the/decommissioned
topology is migrated to volumes and nodes in thedata
topology. - Run the following command to check if a given volume is present on the node:
maprcli dump volumenodes -volumename <volume> -json | grep <ip:port>
Note: Run this command for each non-local volume in your cluster to verify that the node being decommissioned is not storing any volume data. - Change to the root user (or use sudo for the following commands).
- Stop Warden on the node by running the following command:
service mapr-warden stop
- If ZooKeeper is installed on the node, stop it:
service mapr-zookeeper stop
-
Determine which data-fabric packages are installed on the node:
dpkg --list | grep mapr
(Ubuntu)rpm -qa | grep mapr
(Red Hat or CentOS)
- Remove the packages by issuing the appropriate command for the operating system,
followed by the list of services. Examples:
apt-get purge mapr-core mapr-cldb mapr-fileserver
(Ubuntu)yum erase mapr-core mapr-cldb mapr-fileserver
(Red Hat or CentOS)
- Remove the
/opt/mapr
directory to remove any instances ofhostid
,hostname
,zkdata
, andzookeeper
left behind by the package manager. -
Remove any data-fabric
cores in the
/opt/cores
directory. - If the node you have decommissioned is a CLDB node or a ZooKeeper node, then run
configure.sh
on all other nodes in the cluster. See Configuring the Node. -
Remove the node by running the following command:
maprcli node remove <node hostname|ip>