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

Hive QA commented on HIVE-21866:
--------------------------------



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

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16056 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.llap.cache.TestBuddyAllocator.testMTT[2] (batchId=349)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17552/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17552/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17552/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
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: 12971601 - PreCommit-HIVE-Build

> LLAP status service driver may get stuck with wrong Yarn app ID
> ---------------------------------------------------------------
>
>                 Key: HIVE-21866
>                 URL: https://issues.apache.org/jira/browse/HIVE-21866
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Adam Szita
>            Assignee: Adam Szita
>            Priority: Major
>         Attachments: HIVE-21866.0.patch
>
>
> LLAPStatusDriver might get stuck polling status from Yarn if the following 
> happen in this order:
>  * there was a running LLAP Yarn app previously which is now finished / killed
>  * Yarn was restarted
>  * LLAPStatusDriver is invoked before any new LLAP app gets kicked off
>  * LLAPStatusDriver receives the old app ID, which is then cached in the Yarn 
> serviceClient object (no evicition)
>  * In the meantime if any new LLAP app gets kicked off, LLAPStatusDriver will 
> not see it, as it constantly retries fetching info about the wrong, old app 
> ID (this is because we don't create new serviceClient objects)
> {code:java}
> ERROR status.LlapStatusServiceDriver: FAILED: 20: Failed to get Yarn AppReport
> org.apache.hadoop.hive.llap.cli.status.LlapStatusCliException: 20: Failed to 
> get Yarn AppReport
>       at 
> org.apache.hadoop.hive.llap.cli.status.LlapStatusServiceDriver.getAppReport(LlapStatusServiceDriver.java:292)
>  [hive-llap-server-3.1.0.7.0.0.0-112.jar:3.1.0.7.0.0.0-134]
>       at 
> org.apache.hadoop.hive.llap.cli.status.LlapStatusServiceDriver.run(LlapStatusServiceDriver.java:209)
>  [hive-llap-server-3.1.0.7.0.0.0-112.jar:3.1.0.7.0.0.0-134]
>       at 
> org.apache.hadoop.hive.llap.cli.status.LlapStatusServiceDriver.main(LlapStatusServiceDriver.java:537)
>  [hive-llap-server-3.1.0.7.0.0.0-112.jar:3.1.0.7.0.0.0-134]....{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to