Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6C51C200D62 for ; Sat, 2 Dec 2017 01:59:35 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6AC35160C18; Sat, 2 Dec 2017 00:59:35 +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 AFA9C160C06 for ; Sat, 2 Dec 2017 01:59:34 +0100 (CET) Received: (qmail 89556 invoked by uid 500); 2 Dec 2017 00:59:33 -0000 Mailing-List: contact commits-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list commits@hbase.apache.org Received: (qmail 89546 invoked by uid 99); 2 Dec 2017 00:59:33 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Dec 2017 00:59:33 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B4DD4F6024; Sat, 2 Dec 2017 00:59:33 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: zghao@apache.org To: commits@hbase.apache.org Message-Id: X-Mailer: ASF-Git Admin Mailer Subject: hbase git commit: HBASE-18626 Handle the incompatible change about the replication TableCFs' config Date: Sat, 2 Dec 2017 00:59:33 +0000 (UTC) archived-at: Sat, 02 Dec 2017 00:59:35 -0000 Repository: hbase Updated Branches: refs/heads/branch-1.4 fd1f62079 -> 0e930bdd5 HBASE-18626 Handle the incompatible change about the replication TableCFs' config Project: http://git-wip-us.apache.org/repos/asf/hbase/repo Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/0e930bdd Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/0e930bdd Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/0e930bdd Branch: refs/heads/branch-1.4 Commit: 0e930bdd516b69fb0b87be1c6082f8b5f365489a Parents: fd1f620 Author: Guanghao Zhang Authored: Sat Nov 18 15:33:08 2017 +0800 Committer: Guanghao Zhang Committed: Sat Dec 2 08:59:00 2017 +0800 ---------------------------------------------------------------------- src/main/asciidoc/_chapters/upgrading.adoc | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hbase/blob/0e930bdd/src/main/asciidoc/_chapters/upgrading.adoc ---------------------------------------------------------------------- diff --git a/src/main/asciidoc/_chapters/upgrading.adoc b/src/main/asciidoc/_chapters/upgrading.adoc index 9c02210..4256e47 100644 --- a/src/main/asciidoc/_chapters/upgrading.adoc +++ b/src/main/asciidoc/_chapters/upgrading.adoc @@ -175,6 +175,26 @@ In the minor version-particular sections below, we call out where the versions a == Upgrade Paths +[[upgrade1.4]] +=== Upgrading to 1.4+ + +==== Replication peer's TableCFs config + +Before 1.4, the table name can't include namespace for replication peer's TableCFs config. It was fixed by add TableCFs to ReplicationPeerConfig which was stored on Zookeeper. So when upgrade to 1.4, you have to update the original ReplicationPeerConfig data on Zookeeper firstly. There are four steps to upgrade when your cluster have a replication peer with TableCFs config. + +* Disable the replication peer. +* If master has permission to write replication peer znode, then rolling update master directly. If not, use TableCFsUpdater tool to update the replication peer's config. +[source,bash] +---- +$ bin/hbase org.apache.hadoop.hbase.replication.master.TableCFsUpdater update +---- +* Rolling update regionservers. +* Enable the replication peer. + +Notes: + +* Can't use the old client(before 1.4) to change the replication peer's config. Because the client will write config to Zookeeper directly, the old client will miss TableCFs config. And the old client write TableCFs config to the old tablecfs znode, it will not work for new version regionserver. + [[upgrade1.0]] === Upgrading from 0.98.x to 1.x