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 2AB302004A1 for ; Thu, 24 Aug 2017 17:16:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2901116B092; Thu, 24 Aug 2017 15:16: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 6DAFA16B08E for ; Thu, 24 Aug 2017 17:16:05 +0200 (CEST) Received: (qmail 71514 invoked by uid 500); 24 Aug 2017 15:16:02 -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 71503 invoked by uid 99); 24 Aug 2017 15:16:02 -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; Thu, 24 Aug 2017 15:16:02 +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 521BA1A0226 for ; Thu, 24 Aug 2017 15:16:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 3IuRiYSGFN4c for ; Thu, 24 Aug 2017 15:16:01 +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 5707F5F3CC for ; Thu, 24 Aug 2017 15:16: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 B2BBAE0041 for ; Thu, 24 Aug 2017 15:16: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 651922537F for ; Thu, 24 Aug 2017 15:16:00 +0000 (UTC) Date: Thu, 24 Aug 2017 15:16:00 +0000 (UTC) From: "Anoop Sam John (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-18448) EndPoint example for refreshing HFiles for stores MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 24 Aug 2017 15:16:06 -0000 [ https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-18448: ----------------------------------- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-2 +. Thanks. > EndPoint example for refreshing HFiles for stores > -------------------------------------------------- > > Key: HBASE-18448 > URL: https://issues.apache.org/jira/browse/HBASE-18448 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors > Affects Versions: 2.0.0, 1.3.1 > Reporter: Ajay Jadhav > Assignee: Ajay Jadhav > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-18448.branch-1.001.patch, HBASE-18448.branch-1.002.patch, HBASE-18448.branch-1.003.patch, HBASE-18448.branch-1.004.patch, HBASE-18448.branch-1.005.patch, HBASE-18448.branch-1.006.patch, HBASE-18448.branch-1.007.patch, HBASE-18448.master.001.patch, HBASE-18448.master.002.patch > > > In the case where multiple HBase clusters are sharing a common rootDir, even after flushing the data from > one cluster doesn't mean that other clusters (replicas) will automatically pick the new HFile. Through this patch, > we are exposing the refresh HFiles API which when issued from a replica will update the in-memory file handle list > with the newly added file. > This allows replicas to be consistent with the data written through the primary cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)