hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8452) Cleanup handling of resource configuration for tez
Date Tue, 14 Oct 2014 22:41:36 GMT

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

Hive QA commented on HIVE-8452:
-------------------------------



{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12674666/HIVE-8452.1.patch

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 6554 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_parallel
{noformat}

Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1265/testReport
Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1265/console
Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1265/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12674666

> Cleanup handling of resource configuration for tez
> --------------------------------------------------
>
>                 Key: HIVE-8452
>                 URL: https://issues.apache.org/jira/browse/HIVE-8452
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gunther Hagleitner
>            Assignee: Gunther Hagleitner
>             Fix For: 0.14.0
>
>         Attachments: HIVE-8452.1.patch
>
>
> Currently there's a way to configure container size for tez as well as java opts to start
containers.
> However, if you only set container size and not java opts, we fall back to MR settings
for java opts which will likely fail (killed by yarn).
> vcores is always taken from the MR settings. Need to have a way to overwrite that too.
> Tez 0.5 and onwards will automatically generate the right java opts string when the container/cpus
are specified. This is preferable to falling back to MR.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message