The procedure for deleting slave servers is shown below.
Edit and reflect slave server definition file
Delete DFS clients
The procedure for editing the slave server definition file and then effecting these changes is explained below.
If the login to the master server (primary) has not been performed yet, log in to the server with root permissions.
Stop the Hadoop of the Interstage Big Data Parallel Processing Server if it is running before deleting slave servers.
Use the "bdpp_stop" command to stop the Hadoop of the Interstage Big Data Parallel Processing Server.
Refer to "A.1.13 bdpp_stop" for details of the bdpp_stop command.
# /opt/FJSVbdpp/bin/bdpp_stop <Enter>
Delete the slave server to be removed from the slave server definition file (/etc/opt/FJSVbdpp/conf/slaves) and the TaskTracker definition file (/etc/hadoop/mapred.include).
Refer to "A.2.2 slaves" for details on the slave server definition file.
Execute bdpp_changeslaves command to effect the changes that were made to the slave server definition file.
Refer to "A.1.3 bdpp_changeslaves" for information on the bdpp_changeslaves command.
# /opt/FJSVbdpp/bin/bdpp_changeslaves <Enter>
Copy the edited file to the master server (secondary), slave server and development server.
# scp -p /etc/opt/FJSVbdpp/conf/slaves root@master2:/etc/opt/FJSVbdpp/conf <Enter>
# scp -pr /etc/opt/FJSVbdpp/data root@master2:/etc/opt/FJSVbdpp/ <Enter>
# scp -p /etc/hadoop/mapred.include root@master2:/etc/hadoop <Enter>
Also copy the edited file to the slave server and development server.Start the Hadoop of the Interstage Big Data Parallel Processing Server.
Use the bdpp_start command to start the Hadoop of the Interstage Big Data Parallel Processing Server.
Refer to "A.1.11 bdpp_start" for details of the bdpp_start command.
# /opt/FJSVbdpp/bin/bdpp_start
Refer to "E.4 Deleting a Slave Server" in "Appendix E DFS Operation Changes" for information on deleting a DFS client.