The ApplicationMaster
requests a NodeManager
to start a {@link Container} allocated to it using this interface.
The ApplicationMaster
has to provide details such as allocated resource capability, security tokens (if enabled), command to be executed to start the container, environment for the process, necessary binaries/jar/shared-objects etc. via the {@link ContainerLaunchContext} in the {@link StartContainerRequest}.
Currently the NodeManager
sends an immediate, empty response via {@link StartContainerResponse} to signify acceptance of therequest and throws an exception in case of errors. The ApplicationMaster
can use {@link #getContainerStatus(GetContainerStatusRequest)} to get updated status of the to-be-launched or launched container.
Start an allocated container.
The ApplicationMaster
or other applications that use the client must provide the details of the allocated container, including the Id, the assigned node's Id and the token via {@link Container}. In addition, the AM needs to provide the {@link ContainerLaunchContext} aswell.
NodeManager
to launch the container
@return a map between the auxiliary service names and their outputs
@throws YarnException
@throws IOException
|
|
|
|
|
|
|
|