Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 7 Feb 2013 14:11:13 +0000 (UTC)
From: "Jonathan Hsieh (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12631263.1360246193370.260290.1360246273591@arcas>
In-Reply-To: <JIRA.12631263.1360246193370@arcas>
References: <JIRA.12631263.1360246193370@arcas>
Subject: [jira] [Assigned] (HBASE-7788) [snapshot 130201 merge] Fix flakey
 TestRestore*SnapshotFromClient#testCloneSnapshot
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Jonathan Hsieh reassigned HBASE-7788:
-------------------------------------

    Assignee: Jonathan Hsieh
   =20
> [snapshot 130201 merge] Fix flakey TestRestore*SnapshotFromClient#testClo=
neSnapshot
> -------------------------------------------------------------------------=
----------
>
>                 Key: HBASE-7788
>                 URL: https://issues.apache.org/jira/browse/HBASE-7788
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>
> In the current implementation the clone call waits until after the newly =
created table isTableEnabled. However there is another state (apparently or=
thogonal) that a newly created table is assumed to be =E2=80=93 isTableAvai=
lable (all regions assigned). The logic for checking after table creation a=
nd after clone creation are slightly different =E2=80=93 creation does the =
equivalent of isTableAvailable but clone does not check this availability c=
ondition.
> This causes flaky failures in tests that quickly try to use/delete a newl=
y cloned table.
> TestRestoreSnapshotFromClient#testCloneSnapshot
> TestRestoreFlushSnapshotFromCleitn#testCloneSnapshot
> I believe there also are race conditions because of the postTableCreateHa=
ndler corpco and postTableDeleteHandler coproc hooks.

--
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