[
https://issues.apache.org/jira/browse/AMBARI-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty resolved AMBARI-4441.
-----------------------------------
Resolution: Fixed
committed to trunk
> Add support for hbase decommisison
> ----------------------------------
>
> Key: AMBARI-4441
> URL: https://issues.apache.org/jira/browse/AMBARI-4441
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 1.5.0
>
>
> Add the API support for hbase decommission. The API calls are:
> HBase decommission is different than the other decommissions. The
> decommission is actually a graceful stop of the RS allowing to move all the
> regions. This involves three steps from the perspective of API calls.
> * Mark the RS to be draining and start moving the regions out
> * Stop the RS
> * Get the RS out of draining mode
> {noformat}
> 1. curl -u admin:admin -H "X-Requested-By: ambari" -X POST -d
> '{"RequestInfo":{"context":"Decommission
> DataNode","command":"DECOMMISSION","service_name":"HBASE",
> "component_name":"HBASE_MASTER",
> "parameters":{"slave_type":"HBASE_REGIONSERVER",
> "excluded_hosts":"c6401.ambari.apache.org,c6403.ambari.apache.org"}}}'
> http://localhost:8080/api/v1/clusters/c1/requests
> 2. A call to STOP the region server being decommissioned
> 3. curl -u admin:admin -H "X-Requested-By: ambari" -X POST -d
> '{"RequestInfo":{"context":"Decommission
> DataNode","command":"DECOMMISSION","service_name":"HBASE",
> "component_name":"HBASE_MASTER",
> "parameters":{"slave_type":"HBASE_REGIONSERVER",
> "excluded_hosts":"c6401.ambari.apache.org,c6403.ambari.apache.org",
> "mark_draining_only":"true"}}}'
> http://localhost:8080/api/v1/clusters/c1/requests
> {noformat}
> These calls should be batched so that the order is maintained and if one call
> fails then the other calls can also fail. The tolerance for this batch should
> be 0.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
