Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 7 Apr 2013 05:01:20 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12608206.1348043135983.123432.1365310880460@arcas>
In-Reply-To: <JIRA.12608206.1348043135983@arcas>
References: <JIRA.12608206.1348043135983@arcas>
Subject: [jira] [Updated] (HBASE-6839) Operations may be executed without
 holding rowLock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HBASE-6839?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-6839:
-------------------------

    Fix Version/s:     (was: 0.95.0)
                   0.94.2

Fix up after bulk move overwrote some 0.94.2 fix versions w/ 0.95.0 (Notice=
d by Lars Hofhansl)
               =20
> Operations may be executed without holding rowLock
> --------------------------------------------------
>
>                 Key: HBASE-6839
>                 URL: https://issues.apache.org/jira/browse/HBASE-6839
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>            Priority: Critical
>             Fix For: 0.94.2
>
>         Attachments: HBASE-6839.patch
>
>
> HRegion#internalObtainRowLock will return null if timed out,
> but many place which call this method don't handle this case
> The bad result is operation will be executed even if it havn't obtained t=
he row lock. Such as put=E3=80=81delete=E3=80=81increment=E3=80=82=E3=80=82=
=E3=80=82

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira