[ https://issues.apache.org/jira/browse/HIVE-20853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674301#comment-16674301 ]
Hive QA commented on HIVE-20853: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12946800/HIVE-20853.2.patch {color:red}ERROR:{color} -1 due to build exiting with an error Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/14742/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14742/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14742/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12946800/HIVE-20853.2.patch was found in seen patch url's cache and a test was probably run already on it. Aborting... {noformat} This message is automatically generated. ATTACHMENT ID: 12946800 - 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 > > > 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)