Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 7 Oct 2011 20:52:29 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <334363376.9878.1318020749898.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2123691853.5252.1317935729719.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4547) TestAdmin failing in 0.92 because
 .tableinfo not found
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-4547:
-------------------------------

Integrated in HBase-0.92 #51 (See [https://builds.apache.org/job/HBase-0.92/51/])
    HBASE-4547 TestAdmin failing in 0.92 because .tableinfo not found

stack : 
Files : 
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java

                
> TestAdmin failing in 0.92 because .tableinfo not found
> ------------------------------------------------------
>
>                 Key: HBASE-4547
>                 URL: https://issues.apache.org/jira/browse/HBASE-4547
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.92.0
>
>         Attachments: 4547-part2.txt, 4547.txt
>
>
> I've been running tests before commit and found the following happens with some regularity, sporadic of course, but they fail fairly frequently:
> {code}
> Failed tests:   testOnlineChangeTableSchema(org.apache.hadoop.hbase.client.TestAdmin)
>   testForceSplit(org.apache.hadoop.hbase.client.TestAdmin): expected:<2> but was:<1>
>   testForceSplitMultiFamily(org.apache.hadoop.hbase.client.TestAdmin): expected:<2> but was:<1>
> {code}
> Looking, it seems like we fail to find .tableinfo in the tests that modify table schema while table is online.
> The update of a table schema just does an overwrite.  In the tests we sometimes fail to find the newly written file or we get EOFE reading it.

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