[jira] [Resolved] (HBASE-6290) Add a function a mark a server as dead and start the recovery the process

["stack (JIRA)" <ji...@apache.org>]

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

stack resolved HBASE-6290.
--------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0
     Release Note: 
Adds a script to mark a server as dead.

Usage: considerAsDead.sh --hostname serverName
     Hadoop Flags: Reviewed

Committed to master.  Thanks [~talat]

> Add a function a mark a server as dead and start the recovery the process
> -------------------------------------------------------------------------
>
>                 Key: HBASE-6290
>                 URL: https://issues.apache.org/jira/browse/HBASE-6290
>             Project: HBase
>          Issue Type: Improvement
>          Components: monitoring
>    Affects Versions: 0.95.2
>            Reporter: Nicolas Liochon
>            Assignee: Talat UYARER
>            Priority: Minor
>              Labels: beginner
>             Fix For: 2.0.0
>
>         Attachments: 6290v2.txt, HBASE-6290.patch
>
>
> ZooKeeper is used a a monitoring tool: we use znode and we start the recovery process when a znode is deleted by ZK because it got a timeout. This timeout is defaulted to 90 seconds, and often set to 30s
> However, some HW issues could be detected by specialized hw monitoring tools before the ZK timeout. For this reason, it makes sense to offer a very simple function to mark a RS as dead. This should not take in
> It could be a hbase shell function such as
> considerAsDead ipAddress|serverName
> This would delete all the znodes of the server running on this box, starting the recovery process.
> Such a function would be easily callable (at callers risk) by any fault detection tool... We could have issues to identify the right master & region servers around ipv4 vs ipv6 vs and multi networked boxes however.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)