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 38A91200BAB for ; Sat, 8 Oct 2016 00:33:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3748D160AE9; Fri, 7 Oct 2016 22:33:19 +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 7D636160AE8 for ; Sat, 8 Oct 2016 00:33:18 +0200 (CEST) Received: (qmail 43221 invoked by uid 500); 7 Oct 2016 22:33:17 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 43208 invoked by uid 99); 7 Oct 2016 22:33:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Oct 2016 22:33:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3D1B618060C for ; Fri, 7 Oct 2016 22:33:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.711 X-Spam-Level: *** X-Spam-Status: No, score=3.711 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wlk70TP9WAGg for ; Fri, 7 Oct 2016 22:33:13 +0000 (UTC) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 2C9125FB2F for ; Fri, 7 Oct 2016 22:33:13 +0000 (UTC) Received: by mail-io0-f180.google.com with SMTP id j37so60845787ioo.3 for ; Fri, 07 Oct 2016 15:33:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3S4QUk479fguMBfff0lskBkt3hqrtyeQIWY7NCUtGRI=; b=WukEjQDw+ZKXSiq/F+qfpwKwbwfQh7xBQ90rBKydVXpuBBEBOTRAOIsHJnu49jG/6r FC50Qru3E8jco5WPEQJNzXyg+uKP5idJzbeXERf6a1efQ5q/5zATeoXLD3Ss7/u00NQH +FUo8iObFIFGkp/nVV+jJnuPs3uD4LBseGeTTBYE829O6hF0hijAnSo2ybznJMNDLzpU MSKOqIscdIF5NRGuxxzLO+5J7iI927+6o9IHn292dkCuHV9oCaKdUuIVxCdN8r5lQ2fX 5h1KMzUXjAjFz5I7FYtsg+GnPmvPd8AZOGPuLS/qpc7yisK1vzu7+bEptjLf3bmBQEBL YrvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3S4QUk479fguMBfff0lskBkt3hqrtyeQIWY7NCUtGRI=; b=TEwjX13f7aL/xX/Og9/NWqFOAIw7+wih54iOLDzA8em6LqmpFsOCuSkiPSWpgC2wRa SIMI7c6j4Jw9jclcDBNCJ+LxfuEfSKqrvJ5nZV+Sj8XkUyHEggnlN1LUQOzrovJc3FPq jOR6GefBhd8RnIMkBrdZGyqXl6UXsG09n3wXFwxeFi6PwJTrdMBbZk+L0hAlnjHOMK4R u8omhX7Orvc/Zi33e8lFSxritKCrZzqIqTEeMCWgJnTShwCcQnCE9dvi7PoRSBv9G7xX j6abCK6+vYYCQeNX+wdrRCBUod9J02+12KufzqqUnpdQrAQnopZyab+Is5LSgyWTsJ6M BGpw== X-Gm-Message-State: AA6/9RkaexTEqPuux4DLa7FycreuAPiBTqvbUekS3FeyqDx+3oNR97/Mlba+Ad7VoA2l8p9ag2FN/JxpIkNvEA== X-Received: by 10.107.8.79 with SMTP id 76mr22340514ioi.154.1475879592010; Fri, 07 Oct 2016 15:33:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.44.195 with HTTP; Fri, 7 Oct 2016 15:33:10 -0700 (PDT) Received: by 10.79.44.195 with HTTP; Fri, 7 Oct 2016 15:33:10 -0700 (PDT) In-Reply-To: References: <1475551090402-4083081.post@n3.nabble.com> From: sudhir patil Date: Sat, 8 Oct 2016 06:33:10 +0800 Message-ID: Subject: RE: Best way to disable & enable HBASE replication To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a113f3034d02d26053e4dfe64 archived-at: Fri, 07 Oct 2016 22:33:19 -0000 --001a113f3034d02d26053e4dfe64 Content-Type: text/plain; charset=UTF-8 Thanks Chein. Yes, disable_peer and enable_peer worked without any issues. On Oct 5, 2016 6:02 AM, "Chien Le" wrote: > The documentation for disabling the peer sounds wrong, I think it applies > to option #1, not #2. > > From my memory, disabling/re-enabling the peer did not require any manual > intervention, it just resumed from whatever info was in zk but admittedly, > this was back on 0.94 so things might've changed. > > -Chien > > -----Original Message----- > From: spats [mailto:spatil.sudhir@gmail.com] > Sent: Monday, October 3, 2016 8:18 PM > To: user@hbase.apache.org > Subject: Best way to disable & enable HBASE replication > > If we have to stop hbase replication and re enable after sometime, which > one > is better way to do > 1. stop_replication, later enable by running start_replication and copy > missing data for that duration using copyTable command. > 2. disable_peer("1") , later enable_peer("1") > > 2nd option looks better as we don't have to copy missing data manually & > data gets replicated automatically when we enable peer. But i see warning > here > https://www.cloudera.com/documentation/enterprise/5-5- > x/topics/cdh_bdr_hbase_replication.html#topic_20_11_5 > "If you disable replication, and then later decide to enable it again, you > must manually remove the old replication data from ZooKeeper by deleting > the > contents of the replication queue", don't understand statement clearly. Is > it really required to delete znode? > > I would like to go ahead with option 2, is there any risk? deleting znode > is > mandatory in that case? > > Thanks in advance > > > > -- > View this message in context: http://apache-hbase.679495.n3. > nabble.com/Best-way-to-disable-enable-HBASE-replication-tp4083081.html > Sent from the HBase User mailing list archive at Nabble.com. > --001a113f3034d02d26053e4dfe64--