|
@@ -16,6 +16,57 @@ limitations under the License.
|
|
-->
|
|
-->
|
|
|
|
|
|
# Host Component Resources
|
|
# Host Component Resources
|
|
|
|
+###API Summary
|
|
|
|
+
|
|
|
|
+
|
|
|
|
+- [List host components](host-components.md)
|
|
|
|
+- [View host component information](host-component.md)
|
|
|
|
+- [Create host component](create-hostcomponent.md)
|
|
|
|
+- [Update host component](update-hostcomponent.md)
|
|
|
|
+
|
|
|
|
+###Properties
|
|
|
|
+
|
|
|
|
+<table>
|
|
|
|
+ <tr>
|
|
|
|
+ <th>Property</th>
|
|
|
|
+ <th>Description</th>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/role_id</td>
|
|
|
|
+ <td>The host component id</td>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/cluster_name</td>
|
|
|
|
+ <td>The name of the parent cluster</td>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/host_name</td>
|
|
|
|
+ <td>The name of the parent host</td>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/component_name</td>
|
|
|
|
+ <td>The name of the parenbt component</td>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/state</td>
|
|
|
|
+ <td>The state of the host component</td>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/actual_configs</td>
|
|
|
|
+ <td>The actual configuration</td>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/desired_configs</td>
|
|
|
|
+ <td>The desired configuration</td>
|
|
|
|
+ </tr>
|
|
|
|
+ <tr>
|
|
|
|
+ <td>HostRoles/stack_id</td>
|
|
|
|
+ <td>The stack id (e.g. HDP-1.3.0)</td>
|
|
|
|
+ </tr>
|
|
|
|
+</table>
|
|
|
|
+
|
|
|
|
+
|
|
|
|
+
|
|
###States
|
|
###States
|
|
|
|
|
|
The current state of a host component resource can be determined by looking at the ServiceComponentInfo/state property.
|
|
The current state of a host component resource can be determined by looking at the ServiceComponentInfo/state property.
|
|
@@ -23,8 +74,6 @@ The current state of a host component resource can be determined by looking at t
|
|
|
|
|
|
GET api/v1/clusters/c1/services/HDFS/components/NAMENODE?fields=ServiceComponentInfo/state
|
|
GET api/v1/clusters/c1/services/HDFS/components/NAMENODE?fields=ServiceComponentInfo/state
|
|
|
|
|
|
-**Response**
|
|
|
|
-
|
|
|
|
200 OK
|
|
200 OK
|
|
{
|
|
{
|
|
"href" : "http://your.ambari.server/api/v1/clusters/c1/services/HDFS/components/NAMENODE?fields=ServiceComponentInfo/state",
|
|
"href" : "http://your.ambari.server/api/v1/clusters/c1/services/HDFS/components/NAMENODE?fields=ServiceComponentInfo/state",
|
|
@@ -97,22 +146,15 @@ The following table lists the possible values of the service resource ServiceCom
|
|
</tr>
|
|
</tr>
|
|
</table>
|
|
</table>
|
|
|
|
|
|
-###Starting
|
|
|
|
|
|
+
|
|
|
|
+###Starting a Host Component
|
|
A component can be started through the API by setting its state to be STARTED (see [update host component](update-hostcomponent.md)).
|
|
A component can be started through the API by setting its state to be STARTED (see [update host component](update-hostcomponent.md)).
|
|
|
|
|
|
-###Starting
|
|
|
|
|
|
+###Stopping a Host Component
|
|
A component can be stopped through the API by setting its state to be INSTALLED (see [update host component](update-hostcomponent.md)).
|
|
A component can be stopped through the API by setting its state to be INSTALLED (see [update host component](update-hostcomponent.md)).
|
|
|
|
|
|
###Maintenance
|
|
###Maintenance
|
|
|
|
|
|
-The user can update the desired state of a component through the API to be MAINTENANCE (see [update host component](update-hostcomponent.md)). When a host component is into maintenance state it is basically taken off line. This state can be used, for example, to move a component like NameNode. The NameNode component can be put in MAINTENANCE mode and then a new NameNode can be created for the service.
|
|
|
|
-
|
|
|
|
-
|
|
|
|
|
|
+The user can update the desired state of a host component through the API to be MAINTENANCE (see [update host component](update-hostcomponent.md)). When a host component is into maintenance state it is basically taken off line. This state can be used, for example, to move a component like NameNode. The NameNode component can be put in MAINTENANCE mode and then a new NameNode can be created for the service.
|
|
|
|
|
|
-###Examples
|
|
|
|
|
|
|
|
-
|
|
|
|
-- [List host components](host-components.md)
|
|
|
|
-- [View host component information](host-component.md)
|
|
|
|
-- [Create host component](create-hostcomponent.md)
|
|
|
|
-- [Update host component](update-hostcomponent.md)
|
|
|