From issues-return-328238-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Fri Jan 5 14:23:06 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 61305180647 for ; Fri, 5 Jan 2018 14:23:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5103D160C3B; Fri, 5 Jan 2018 13:23:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 96BED160C19 for ; Fri, 5 Jan 2018 14:23:05 +0100 (CET) Received: (qmail 49565 invoked by uid 500); 5 Jan 2018 13:23:04 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 49554 invoked by uid 99); 5 Jan 2018 13:23:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2018 13:23:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3C17F1A0992 for ; Fri, 5 Jan 2018 13:23:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id am5weXYVl5BC for ; Fri, 5 Jan 2018 13:23:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 53DAE5FB04 for ; Fri, 5 Jan 2018 13:23:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AEB2DE0E16 for ; Fri, 5 Jan 2018 13:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6B2BD240F2 for ; Fri, 5 Jan 2018 13:23:00 +0000 (UTC) Date: Fri, 5 Jan 2018 13:23:00 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-19397) Design procedures for ReplicationManager to notify peer change event from master MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-19397: ------------------------------ Attachment: HBASE-19397-master.patch OK, we need to include a 'master' in the name of the patch... > 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-master.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)