Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 13 May 2017 15:03:04 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13062203.1491503671000.204010.1494687784158@Atlassian.JIRA>
In-Reply-To: <JIRA.13062203.1491503671000@Atlassian.JIRA>
References: <JIRA.13062203.1491503671000@Atlassian.JIRA> <JIRA.13062203.1491503671886@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-17887) Row-level consistency is broken
 for read
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sat, 13 May 2017 15:03:09 -0000


    [ https://issues.apache.org/jira/browse/HBASE-17887?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D160=
09363#comment-16009363 ]=20

Ted Yu commented on HBASE-17887:
--------------------------------

Another case:
http://104.198.223.121:8080/job/HBase-Flaky-Tests/24813/testReport/junit/or=
g.apache.hadoop.hbase/TestAcidGuarantees/testMobScanAtomicity_0_/

Overall, the test only occasionally fails - much improvement.

> Row-level consistency is broken for read
> ----------------------------------------
>
>                 Key: HBASE-17887
>                 URL: https://issues.apache.org/jira/browse/HBASE-17887
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 2.0.0, 1.3.0
>            Reporter: Umesh Agashe
>            Assignee: Chia-Ping Tsai
>            Priority: Blocker
>             Fix For: 2.0.0, 1.4.0, 1.3.2
>
>         Attachments: HBASE-17887.branch-1.v0.patch, HBASE-17887.branch-1.=
v1.patch, HBASE-17887.branch-1.v1.patch, HBASE-17887.branch-1.v2.patch, HBA=
SE-17887.branch-1.v2.patch, HBASE-17887.branch-1.v3.patch, HBASE-17887.bran=
ch-1.v4.patch, HBASE-17887.branch-1.v4.patch, HBASE-17887.branch-1.v4.patch=
, HBASE-17887.branch-1.v5.patch, HBASE-17887.branch-1.v6.patch, HBASE-17887=
.ut.patch, HBASE-17887.v0.patch, HBASE-17887.v1.patch, HBASE-17887.v2.patch=
, HBASE-17887.v3.patch, HBASE-17887.v4.patch, HBASE-17887.v5.patch, HBASE-1=
7887.v5.patch
>
>
> The scanner of latest memstore may be lost if we make quick flushes. The =
following step may help explain this issue.
> # put data_A (seq id =3D 10, active store data_A and snapshots is empty)
> # snapshot of 1st flush (active is empty and snapshot stores data_A)
> # put data_B (seq id =3D 11, active store data_B and snapshot store data_=
A)
> # create user scanner (read point =3D 11, so It should see the data_B)
> # commit of 1st flush
> #* clear snapshot ((hfile_A has data_A, active store data_B, and snapshot=
 is empty)
> #* update the reader (the user scanner receives the hfile_A)
> # snapshot of 2st flush (active is empty and snapshot store data_B)
> # commit of 2st flush
> #* clear snapshot (hfile_A has data_A, hfile_B has data_B, active is empt=
y, and snapshot is empty) =E2=80=93 this is critical piece.
> #* -update the reader- (haven't happen)
> # user scanner update the kv scanners (it creates scanner of hfile_A but =
nothing of memstore)
> # user see the older data A =E2=80=93 wrong result


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)