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

Hive QA commented on HIVE-20853:
--------------------------------



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

{color:green}SUCCESS:{color} +1 due to 3 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 15527 tests passed

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

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
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12947255 - PreCommit-HIVE-Build

> Expose ShuffleHandler.registerDag in the llap daemon API
> --------------------------------------------------------
>
>                 Key: HIVE-20853
>                 URL: https://issues.apache.org/jira/browse/HIVE-20853
>             Project: Hive
>          Issue Type: Improvement
>          Components: llap
>    Affects Versions: 3.1.0
>            Reporter: Jaume M
>            Assignee: Jaume M
>            Priority: Critical
>         Attachments: HIVE-20853.1.patch, HIVE-20853.2.patch, 
> HIVE-20853.3.patch, HIVE-20853.4.patch, HIVE-20853.5.patch
>
>
> Currently DAGs are only registered when a submitWork is called for that DAG. 
> At this point the crendentials are added to the ShuffleHandler and it can 
> start serving.
> However Tez might (and will) schedule tasks to fetch from the ShuffleHandler 
> before anything of this happens and all this tasks will fail which may 
> results in the query failing.
> This happens in the scenario in which a LlapDaemon just comes up and tez 
> fetchers try to open a connection before a DAG has been registered.
> Adding this API will allow to register the DAG against the Daemon when the AM 
> notices that a new Daemon is up.



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

Reply via email to