stop_host_component
Stops a specified component on a single Ambari host, enabling targeted shutdown without affecting other hosts or services. Use it for node-level troubleshooting, isolation, or decommissioning.
Instructions
Stops a specific component on a specific host in the Ambari cluster.
[Tool Role]: Dedicated tool for stopping individual host-level components, enabling fine-grained control without affecting other hosts or the overall service.
[Core Functions]:
Stop the specified component on the given host
Skip if the component is already in INSTALLED (stopped) state
Return request information for progress tracking
[Required Usage Scenarios]:
When users request to stop a component on a specific host (e.g., "stop DataNode on host-A")
When decommissioning or isolating a specific node's component
When troubleshooting a single component instance
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"host_name": "<host_name>",
"component_name": "<component_name>"
},
"name": "stop_host_component"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host_name | Yes | Hostname where the component resides (e.g., "hdp-node-01.example.com") | |
| component_name | Yes | Name of the component to stop (e.g., "DATANODE", "NODEMANAGER") |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |