Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 16 Jul 2013 21:02:48 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12657904.1373932007279.60653.1374008568759@arcas>
In-Reply-To: <JIRA.12657904.1373932007279@arcas>
References: <JIRA.12657904.1373932007279@arcas>
Subject: [jira] [Commented] (HBASE-8957) TestDrainingServer.
 testDrainingServerWithAbort fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-8957:
------------------------------

It looks to be a perms problem when doing dfs issues.  The jenkins user is cleared to do short circuit reading but then regionservers are running as jenkins.hfs.1, jenkins.hfs.2, etc.

Wondering why we usually pass this test, looking at a 'successful' build, it looks to me like it is not running at all:

https://builds.apache.org/view/H-L/view/HBase/job/HBase-TRUNK-on-Hadoop-2.0.0/617/testReport/org.apache.hadoop.hbase/TestDrainingServer/

The times given for the tests are suspiciously short.
                
> TestDrainingServer. testDrainingServerWithAbort fails
> -----------------------------------------------------
>
>                 Key: HBASE-8957
>                 URL: https://issues.apache.org/jira/browse/HBASE-8957
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>
> See here https://builds.apache.org/job/hbase-0.95-on-hadoop2/179/testReport/org.apache.hadoop.hbase/TestDrainingServer/testDrainingServerWithAbort/
> and here
> http://54.241.6.143/job/HBase-0.95-Hadoop-2/org.apache.hbase$hbase-server/600/testReport/org.apache.hadoop.hbase/TestDrainingServer/testDrainingServerWithAbort/
> It looks like .META. is not being assigned.  Am digging in  here now.

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