Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 5 Oct 2016 06:50:20 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13009767.1475640909000.739675.1475650220636@Atlassian.JIRA>
In-Reply-To: <JIRA.13009767.1475640909000@Atlassian.JIRA>
References: <JIRA.13009767.1475640909000@Atlassian.JIRA> <JIRA.13009767.1475640909891@arcas>
Subject: [jira] [Commented] (HBASE-16768) Inconsistent results from the
 Append/Increment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 05 Oct 2016 06:50:22 -0000


    [ https://issues.apache.org/jira/browse/HBASE-16768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547869#comment-15547869 ] 

ramkrishna.s.vasudevan commented on HBASE-16768:
------------------------------------------------

As the older comment says getting seqID is expensive should you do the for loop thing only if you are sure the WAL is being skipped rather than every time Append/increment is performed?

> Inconsistent results from the Append/Increment
> ----------------------------------------------
>
>                 Key: HBASE-16768
>                 URL: https://issues.apache.org/jira/browse/HBASE-16768
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ChiaPing Tsai
>            Priority: Minor
>         Attachments: HBASE-16768.v0.patch
>
>
> If the Append/Increment skips the WAL, the sequential id will not be updated.
> It introduces that the AbstractMemStore#upsert may remove the cell even though the cell is visible to the oldest scanner.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)