[
https://issues.apache.org/jira/browse/HBASE-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152118#comment-14152118
]
Hudson commented on HBASE-6290:
-------------------------------
FAILURE: Integrated in HBase-TRUNK #5572 (See
[https://builds.apache.org/job/HBase-TRUNK/5572/])
HBASE-6290 Add a function a mark a server as dead and start the recovery the
process (Talat Uyarer) (stack: rev 4be3cf8fec8390c4129fa037b63718e84db01656)
* bin/considerAsDead.sh
HBASE-6290 Add a function a mark a server as dead and start the recovery the
process (Talat Uyarer) (stack: rev 8e5aad43a2fbde2aac6aff6dd01582933bd8db9b)
* bin/considerAsDead.sh
HBASE-6290 Add a function a mark a server as dead and start the recovery the
process (Talat Uyarer) DOC ADDENDUM (stack: rev
82bb37070379bb8e135ee566589e8e348e0bdd78)
* src/main/docbkx/ops_mgt.xml
> 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: 6290.doc.addendum.txt, 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)
