hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6290) Add a function a mark a server as dead and start the recovery the process
Date Mon, 28 Jul 2014 21:23:40 GMT

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

stack commented on HBASE-6290:
------------------------------

Now we are actively trying to hide our dependency on zk, we should put the delete of znodes
on other side of an Interface with default implementation being zk-based doing the znode delete
[~nkeywal] describes above.

Keep in mind, we might want to also do a kill compaction on same method... so a kill switch
that can kill server and kill compactions?

> 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: Nicolas Liochon
>            Priority: Minor
>              Labels: noob
>
> 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.2#6252)

Mime
View raw message