A.14 bdpp

Name: /opt/FJSVbdpp/bin/bdpp_start - Starts Hadoop

Format: bdpp_start [-f]

Description: This command starts Hadoop for this product.
It starts the Hadoop JobTracker on the master server and the Hadoop TaskTracker on all the connection target slave servers.

Options

-f

Forces Hadoop to start.

Specify this option only to force Hadoop to start, such as when an error occurs on the master servers that use replicated configuration and the JobTracker cannot start automatically.

See

Refer to "15.1.1 If the Master Servers Use Replicated Configuration" for information on situations that may require forced start.

Required permissions and execution environment

Permissions: root permissions

Execution environment: Master server

End status

The following status codes are returned:

0: Processed normally

Other than 0: Error occurred

Note

If the bdpp_start command and the bdpp_stop command are executed simultaneously, a mismatch may arise in the run state of the Hadoop JobTracker on the master server or the Hadoop TaskTracker on the slave server.

If this occurs, use the bdpp_stat -all command to check the status, then re-execute the bdpp_start command so that the Hadoop JobTrackers on the master server or the Hadoop TaskTrackers on the slave servers are all running, as shown in the following table.

Table A.1 Status of the bdpp_stat -all command and the execution results of the bdpp_start command
Master server JobTracker	Slave server TaskTracker	bdpp_start execution results
Not running	Not running	Start the master server JobTracker and all slave server TaskTrackers
	Running on some slave servers	Start the master server JobTracker and all slave server TaskTrackers that are not running
	Running on all slave servers	Start only the master server JobTracker
Running	Not running	"bdpp: WARN : 001: bdpp Hadoop is already started." message is output Start all slave server TaskTrackers
	Running on some slave servers	"bdpp: WARN : 001: bdpp Hadoop is already started." message is output Start all slave server TaskTrackers that are not running
	Running on all slave servers	"bdpp: WARN : 001: bdpp Hadoop is already started." message is output

A.14 bdpp_start