You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/05/16 00:31:26 UTC

[jira] [Commented] (HBASE-6330) TestImportExport has been failing against hadoop 0.23/2.0 profile

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

Hudson commented on HBASE-6330:
-------------------------------

Integrated in HBase-0.94-security #141 (See [https://builds.apache.org/job/HBase-0.94-security/141/])
    HBASE-8381 TestTableInputFormatScan on Hadoop 2 fails because YARN kills our applications

This patch bumps up the vmem-pmem ratio so that yarn's resource checker does not kill jobs that exceed the vmem (virtual memory!) allocation limit.  Related to HBASE-6330. (Revision 1471570)

     Result = FAILURE
jmhsieh : 
Files : 
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java

                
> TestImportExport has been failing against hadoop 0.23/2.0 profile
> -----------------------------------------------------------------
>
>                 Key: HBASE-6330
>                 URL: https://issues.apache.org/jira/browse/HBASE-6330
>             Project: HBase
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: 0.94.1, 0.95.2
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>              Labels: hadoop-2.0
>             Fix For: 0.98.0, 0.95.1
>
>         Attachments: hbase-6330-94.patch, hbase-6330-trunk.patch, hbase-6330-v2.patch, hbase-6330.v4.patch
>
>
> See HBASE-5876.  I'm going to commit the v3 patches under this name since there has been two months (my bad) since the first half was committed and found to be incomplte.
> ---
> 4/9/13 Updated - this will take the patch from HBASE-8258 to fix this specific problem.  The umbrella that used to be HBASE-8258 is now handled with HBASE-6891.

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