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-10295) Refactor the replication implementation to eliminate permanent zk node
Date Fri, 10 Jan 2014 20:37:50 GMT

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

stack commented on HBASE-10295:

Make Master arbiter for these new system tables -- only the master can mod them -- and then
add a response on the heartbeat to update regionservers on last edit?  Currently we return
a void.  See RegionServerReportResponse in http://svn.apache.org/viewvc/hbase/trunk/hbase-protocol/src/main/protobuf/RegionServerStatus.proto?view=markup
 Could be as simple as master just replying w/ timestamp of last edit.  If RS has not seen
the new edit, it goes and reads the table....

> Refactor the replication  implementation to eliminate permanent zk node
> -----------------------------------------------------------------------
>                 Key: HBASE-10295
>                 URL: https://issues.apache.org/jira/browse/HBASE-10295
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Feng Honghua
>            Assignee: Feng Honghua
>             Fix For: 0.99.0
> Though this is a broader and bigger change, it original motivation derives from [HBASE-8751|https://issues.apache.org/jira/browse/HBASE-8751]:
the newly introduced per-peer tableCFs attribute should be treated the same way as the peer-state,
which is a permanent sub-node under peer node but using permanent zk node is deemed as an
incorrect practice. So let's refactor to eliminate the permanent zk node. And the HBASE-8751
can then align its newly introduced per-peer tableCFs attribute with this *correct* implementation

This message was sent by Atlassian JIRA

View raw message