Interstage Big DataParallel Processing ServerV1.0.1 User's Guide

12.1.6 Editing and Reflecting the Slave Server Definition File

The procedure for editing the slave server definition file, and then reflecting the changes is explained below.

Change the various definition files on the primary master server and distribute to all slave servers and development servers. If replicated configuration is used for master servers, also distribute to the secondary master server.

1. Edit the slave server definition file (/etc/opt/FJSVbdpp/conf/slaves), and define the slave servers to be added.

   Example

   Slave server definition file example:

   slave1,slave2,slave3,slave4,slave5,slave6,slave7,slave8,slave9,slave10

   Note: The underlining indicates the slave servers to be added.

2. Execute the bdpp_changeslaves command to reflect the changes made to the slave server definition file.

   # /opt/FJSVbdpp/bin/bdpp_changeslaves <Enter>

3. Copy the edited file to the secondary master server. (Only if replicated configuration is used for the master 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>

4. Also, copy the edited file to slave servers and development servers.

See

• Refer to "B.2 slaves" for information on the slave server definition file.

• Refer to "A.4 bdpp_changeslaves" for information on this command.