[
https://issues.apache.org/jira/browse/HBASE-28342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-28342:
----------------------------------
Sorry, I missed something in review.
Looking more closely at the other exceptions thrown, I think we should make two
small changes. First, the DecommissionedHostRejectedException should be in the
`org.apache.hadoop.hbase.ipc` package (still in the hbase-server module).
Second, It should be annotated as `@InterfaceAudience.Public` because it's part
of our RPC protocol.
> Decommissioned hosts should be rejected by the HMaster
> ------------------------------------------------------
>
> Key: HBASE-28342
> URL: https://issues.apache.org/jira/browse/HBASE-28342
> Project: HBase
> Issue Type: Improvement
> Components: master
> Reporter: Ahmad Alhour
> Assignee: Ahmad Alhour
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.0, 4.0.0-alpha-1, 3.0.0-beta-2
>
>
> We had an issue with a cluster, internally at HubSpot, where a decommissioned
> RegionServer was still being picked up by the HMaster. The host the
> RegionServer was living on was impaired, and we couldn't correctly kill the
> RegionServer, so the HMaster would periodically hear back from the host and
> remove it from its dead host's list.
> We would like to implement a fix so that this doesn't happen. We're thinking
> of adding a boolean flag to the Decommission RegionServer Admin API that
> signifies ignoring the startcode of the servername, when the boolean is True
> the host will be rejected every time it comes back even if it had a different
> startcode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
