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-1502) Remove need for heartbeats in HBase
Date Mon, 14 Feb 2011 17:49:57 GMT

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

stack commented on HBASE-1502:

Yeah, 'registration' is via an RPC.  The RS sends over startcode and port only (should probably
pass the webui port too).  The master returns the hostname only.  On receipt, the RS writes
up into ZK, a znode whose name is the 'servername -- i.e. the master passed domain, port,
and startcode -- and whose content is the RS 'load' updated every 5 minutes or so.  I think
load should be JSON serialized (I think all zk content should be JSON serialized)

I'm willing to entertain suggestions on how we might do away with the startup RPC but we need
to get to the RS the hostname the Master sees; currently it does this by doing lookup on the
remote ip the RPCServer sees on registration RPC.  The RS needs what the master  has for a
hostname so when it writes .META., it writes the same name the master will write.

> Remove need for heartbeats in HBase
> -----------------------------------
>                 Key: HBASE-1502
>                 URL: https://issues.apache.org/jira/browse/HBASE-1502
>             Project: HBase
>          Issue Type: Task
>            Reporter: Nitay Joffe
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.92.0
>         Attachments: 1502-v2.txt, 1502.txt
> HBase currently uses heartbeats between region servers and the master, piggybacking information
on them when it can. This issue is to investigate if we can get rid of the need for those
using ZooKeeper events.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message