hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19397) Design procedures for ReplicationManager to notify peer change event from master
Date Fri, 05 Jan 2018 13:21:00 GMT

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

Hadoop QA commented on HBASE-19397:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red}
HBASE-19397 does not apply to HBASE-19397. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.6.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-19397 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12904793/HBASE-19397.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/10901/console |
| Powered by | Apache Yetus 0.6.0   http://yetus.apache.org |


This message was automatically generated.



> Design  procedures for ReplicationManager to notify peer change event from master
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-19397
>                 URL: https://issues.apache.org/jira/browse/HBASE-19397
>             Project: HBase
>          Issue Type: New Feature
>          Components: proc-v2, Replication
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>         Attachments: HBASE-19397.patch
>
>
> After we store peer states / peer queues information into hbase table,   RS can not track
peer config change by adding watcher znode.   
> So we need design procedures for ReplicationManager to notify peer change event.   the
replication rpc interfaces which may be implemented by procedures are following: 
> {code}
> 1. addReplicationPeer
> 2. removeReplicationPeer
> 3. enableReplicationPeer
> 4. disableReplicationPeer
> 5. updateReplicationPeerConfig
> {code}
> BTW,  our RS states will still be store in zookeeper,  so when RS crash, the tracker
which will trigger to transfer queues of crashed RS will still be a Zookeeper Tracker.  we
need NOT implement that by  procedures.  
> As we will  release 2.0 in next weeks,  and the HBASE-15867 can not be resolved before
the release,  so I'd prefer to create a new feature branch for HBASE-15867. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message