hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1158) Include start code as part of HServerAddress
Date Tue, 27 Jan 2009 16:32:59 GMT

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

Jim Kellerman commented on HBASE-1158:

The start code needs to be associated with the address in some manner for server death recovery
(see HBASE-1156). Whether it is carried around with the HServerAddress or not is really more
a consideration for ZK than anything else. Inside the master we currently pass around HServerInfo's
which carry both the start code and the load information (although one could make a case to
separate the load from HServerInfo as well, since the master manipulates load information
separately from the address and start code)

> Include start code as part of HServerAddress
> --------------------------------------------
>                 Key: HBASE-1158
>                 URL: https://issues.apache.org/jira/browse/HBASE-1158
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>    Affects Versions: 0.20.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.20.0
> If we do not take the startcode into consideration when recovering from a server death,
then we cannot know if the data in ROOT or META pertains to the the current instance or the
previous one.
> With ZK this should be easier if we modify HServerAddress to contain the startCode of
a HRegionServer instance. It would be immediately visible whether or not the region was on
the dead server or the new server.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message