You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Ahmad Alhour (Jira)" <ji...@apache.org> on 2024/02/05 14:00:00 UTC

[jira] [Assigned] (HBASE-28342) Decommissioned hosts should be rejected by the HMaster

     [ https://issues.apache.org/jira/browse/HBASE-28342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ahmad Alhour reassigned HBASE-28342:
------------------------------------

    Assignee: Ahmad Alhour

> Decommissioned hosts should be rejected by the HMaster
> ------------------------------------------------------
>
>                 Key: HBASE-28342
>                 URL: https://issues.apache.org/jira/browse/HBASE-28342
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ahmad Alhour
>            Assignee: Ahmad Alhour
>            Priority: Major
>
> 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)