[
https://issues.apache.org/jira/browse/HIVE-24204?focusedWorklogId=520390&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-520390
]
ASF GitHub Bot logged work on HIVE-24204:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Dec/20 00:48
Start Date: 05/Dec/20 00:48
Worklog Time Spent: 10m
Work Description: github-actions[bot] closed pull request #1530:
URL: https://github.com/apache/hive/pull/1530
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 520390)
Time Spent: 0.5h (was: 20m)
> LLAP: Invalid TEZ Job token in multi fragment query
> ---------------------------------------------------
>
> Key: HIVE-24204
> URL: https://issues.apache.org/jira/browse/HIVE-24204
> Project: Hive
> Issue Type: Bug
> Components: llap
> Affects Versions: 2.3.0
> Reporter: Yuriy Baltovskyy
> Assignee: Yuriy Baltovskyy
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When using LLAP server in the Kerberized environment and submitting the query
> via LLAP client that is planned as multi fragment (multiple splits), the
> following error occurs and the query fails:
> org.apache.hadoop.ipc.Server: javax.security.sasl.SaslException: DIGEST-MD5:
> digest response format violation. Mismatched response.
> This occurs because each split uses its own connection to LLAP server and its
> own TEZ job token while LLAP server stores only one token binding it to the
> whole query and not the separate fragment. When LLAP server communicates to
> the clients and uses the stored token, this causes Sasl exception due to
> using invalid token.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
