[
https://issues.apache.org/jira/browse/HIVE-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768859#comment-15768859
]
Hive QA commented on HIVE-15487:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12844309/HIVE-15487.1.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 10808 tests
executed
*Failed tests:*
{noformat}
TestDerbyConnector - did not produce a TEST-*.xml file (likely timed out)
(batchId=234)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[dbtxnmgr_showlocks]
(batchId=71)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_2]
(batchId=93)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_4]
(batchId=93)
org.apache.hive.jdbc.TestJdbcDriver2.testSelectExecAsync2 (batchId=214)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/2685/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/2685/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-2685/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12844309 - PreCommit-HIVE-Build
> LLAP: Improvements to random selection while scheduling
> -------------------------------------------------------
>
> Key: HIVE-15487
> URL: https://issues.apache.org/jira/browse/HIVE-15487
> Project: Hive
> Issue Type: Bug
> Components: llap
> Affects Versions: 2.2.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-15487.1.patch
>
>
> Currently llap scheduler, picks up random host when no locality information
> is specified or when all requested hosts are busy serving other requests with
> forced locality. In such cases, we can pick up the next available node in
> consistent order to get better locality instead of random selection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
