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 A3007200D60 for ; Fri, 1 Dec 2017 09:46:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A1593160C06; Fri, 1 Dec 2017 08:46:05 +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 E5379160BFB for ; Fri, 1 Dec 2017 09:46:04 +0100 (CET) Received: (qmail 36190 invoked by uid 500); 1 Dec 2017 08:46: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 36179 invoked by uid 99); 1 Dec 2017 08:46: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, 01 Dec 2017 08:46: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 340F21A060A for ; Fri, 1 Dec 2017 08:46:03 +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-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 5PUEJkECR-s6 for ; Fri, 1 Dec 2017 08:46:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C95CE5F20B for ; Fri, 1 Dec 2017 08:46: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 20145E015F for ; Fri, 1 Dec 2017 08:46: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 42A5821064 for ; Fri, 1 Dec 2017 08:46:00 +0000 (UTC) Date: Fri, 1 Dec 2017 08:46:00 +0000 (UTC) From: "Chia-Ping Tsai (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-19339) Eager policy results in the negative size of memstore MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 01 Dec 2017 08:46:05 -0000 [ https://issues.apache.org/jira/browse/HBASE-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-19339: ----------------------------------- Attachment: HBASE-19339.v0.patch The root cause is that our flush suppose the size of snapshot won't be changed after requiring the update lock from region, but the eager policy still run the in-memory compaction which can change the flushable size. Instead of using the size got from {{getFlushable}}, we should honor the size from snapshot since the size got from snapshot is stable for all policies. > Eager policy results in the negative size of memstore > ----------------------------------------------------- > > Key: HBASE-19339 > URL: https://issues.apache.org/jira/browse/HBASE-19339 > Project: HBase > Issue Type: Bug > Reporter: Chia-Ping Tsai > Assignee: Chia-Ping Tsai > Priority: Critical > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19339.v0.patch > > > It is a follow-up of HBASE-19266. -- This message was sent by Atlassian JIRA (v6.4.14#64029)