Return-Path: 
 <issues-return-31015-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id F2BC3B5B0
	for <apmail-hbase-issues-archive@www.apache.org>;
 Wed,  4 Jan 2012 18:54:26 +0000 (UTC)
Received: (qmail 71544 invoked by uid 500); 4 Jan 2012 18:54:26 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 71466 invoked by uid 500); 4 Jan 2012 18:54:26 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 71331 invoked by uid 99); 4 Jan 2012 18:54:26 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 18:54:26 +0000
X-ASF-Spam-Status: No, hits=-2001.6 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 18:54:24 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 57FDC138779
	for <issues@hbase.apache.org>; Wed,  4 Jan 2012 18:53:39 +0000 (UTC)
Date: Wed, 4 Jan 2012 18:53:39 +0000 (UTC)
From: "ramkrishna.s.vasudevan (Assigned) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1351315210.5870.1325703219361.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1883881803.3608.1325659239405.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HBASE-5121) MajorCompaction may affect scan's
 correctness
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/HBASE-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan reassigned HBASE-5121:
---------------------------------------------

    Assignee: chunhui shen
    
> MajorCompaction may affect scan's correctness
> ---------------------------------------------
>
>                 Key: HBASE-5121
>                 URL: https://issues.apache.org/jira/browse/HBASE-5121
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: hbase-5121.patch
>
>
> In our test, there are two families' keyvalue for one row.
> But we could find a infrequent problem when doing scan's next if majorCompaction happens concurrently.
> In the client's two continuous doing scan.next():
> 1.First time, scan's next returns the result where family A is null.
> 2.Second time, scan's next returns the result where family B is null.
> The two next()'s result have the same row.
> If there are more families, I think the scenario will be more strange...
> We find the reason is that storescanner.peek() is changed after majorCompaction if there are delete type KeyValue.
> This change causes the PriorityQueue<KeyValueScanner> of RegionScanner's heap is not sure to be sorted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira