From issues-return-342040-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Wed Apr 4 21:39:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1EA9F18067C for ; Wed, 4 Apr 2018 21:39:05 +0200 (CEST) Received: (qmail 90560 invoked by uid 500); 4 Apr 2018 19:39:05 -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 90534 invoked by uid 99); 4 Apr 2018 19:39: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; Wed, 04 Apr 2018 19:39: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 2BAFE1A05A2 for ; Wed, 4 Apr 2018 19:39:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 Xbh1p2-zNfkJ for ; Wed, 4 Apr 2018 19:39: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 4E5C85FD0D for ; Wed, 4 Apr 2018 19:39:03 +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 A5213E024A for ; Wed, 4 Apr 2018 19:39:02 +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 B6E5E25620 for ; Wed, 4 Apr 2018 19:39:00 +0000 (UTC) Date: Wed, 4 Apr 2018 19:39:00 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-20305) Add option to SyncTable that skip deletes on target cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-20305?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-20305: --------------------------- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the patch, Wellington. Thanks for the review, Dave. > Add option to SyncTable that skip deletes on target cluster > ----------------------------------------------------------- > > Key: HBASE-20305 > URL: https://issues.apache.org/jira/browse/HBASE-20305 > Project: HBase > Issue Type: Improvement > Components: mapreduce > Affects Versions: 2.0.0-alpha-4 > Reporter: Wellington Chevreuil > Assignee: Wellington Chevreuil > Priority: Minor > Fix For: 3.0.0 > > Attachments: 0001-HBASE-20305.master.001.patch, HBASE-20305.maste= r.002.patch > > > We had a situation where two clusters with active-active replication got = out of sync, but both had data that should be kept. The tables in question = never have data deleted, but ingestion had happened on the two different cl= usters, some rows had been even updated. > In this scenario,=C2=A0a cell that is present in one of the table cluster= s should not be deleted, but replayed on the other. Also, for cells with sa= me identifier but different values, the most recent value should be kept. C= urrent version of SyncTable would not be applicable here, because it would = simply copy the whole state from source to target, then losing any addition= al rows that might be only in target, as well as cell values that got most = recent update. This could be solved by adding an option to skip deletes for= SyncTable. This way, the additional cells not present on source would stil= l be kept. For cells with same identifier but different values, it would ju= st perform a Put for the cell version from source, but client scans would s= till fetch the most recent timestamp. > I'm attaching a patch with this additional option shortly. Please share y= our thoughts. > =C2=A0 > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)