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

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2019/03/26 00:27:00 UTC

[jira] [Commented] (HBASE-22107) make dead server metric work for HBase in a compute fabric (e.g. YARN) use case

    [ https://issues.apache.org/jira/browse/HBASE-22107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801263#comment-16801263 ] 

Sean Busbey commented on HBASE-22107:
-------------------------------------

How about a TTL for how long to keep the info around?

 

Default it to -1 for current behavior and when set to something else we effectively have a "recently dead server" list

> make dead server metric work for HBase in a compute fabric (e.g. YARN) use case
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-22107
>                 URL: https://issues.apache.org/jira/browse/HBASE-22107
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>            Reporter: Sergey Shelukhin
>            Priority: Minor
>
> dead servers appear to only be cleaned up when a server comes up on the same host and port; however, if HBase is running on smth like YARN with many more hosts than RSes, RS may come up on a different server and the dead one will never be cleaned.
> The metric should be improved to account for that... it will potentially require configuring master with expected number of region servers, so that the metric could be output based on that.
> Dead server list should also be expired based on timestamp in such cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)