hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-11363) Prewarm Hive on Spark containers [Spark Branch]
Date Fri, 24 Jul 2015 05:19:04 GMT


Hive QA commented on HIVE-11363:

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

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 9266 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

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: 5 tests failed

This message is automatically generated.

ATTACHMENT ID: 12746937 - PreCommit-HIVE-SPARK-Build

> Prewarm Hive on Spark containers [Spark Branch]
> -----------------------------------------------
>                 Key: HIVE-11363
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>    Affects Versions: 1.1.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>         Attachments: HIVE-11363.1-spark.patch, HIVE-11363.2-spark.patch, HIVE-11363.3-spark.patch
> When Hive job is launched by Oozie, a Hive session is created and job script is executed.
Session is closed when Hive job is completed. Thus, Hive session is not shared among Hive
jobs either in an Oozie workflow or across workflows. Since the parallelism of a Hive job
executed on Spark is impacted by the available executors, such Hive jobs will suffer the executor
ramp-up overhead. The idea here is to wait a bit so that enough executors can come up before
a job can be executed.

This message was sent by Atlassian JIRA

View raw message