[
https://issues.apache.org/jira/browse/HIVE-21682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned HIVE-21682:
----------------------------------
Assignee: (was: Todd Lipcon)
I looked into this for a while and after hacking on it for a few days I
couldn't get things stable (after fixing the IOContext and ObjectRegistry
issues, I hit issues in that Tez and Hive assume they can write things into the
current working directory (and different threads in the same process obviously
share the same working directory). Chasing down all of those cases seemed like
too much of a pain, so i just moved to a pseudo-distributed YARN cluster for
our use case.
I think for this to work properly we'd need to make a Tez Local Mode which
actually forks out separate JVMs for each Tez child instead of using threads.
> Concurrent queries in tez local mode fail
> -----------------------------------------
>
> Key: HIVE-21682
> URL: https://issues.apache.org/jira/browse/HIVE-21682
> Project: Hive
> Issue Type: Bug
> Reporter: Todd Lipcon
> Priority: Major
>
> As noted in TEZ-3420, Hive running with Tez local mode breaks if multiple
> queries are submitted concurrently. As I noted
> [there|https://issues.apache.org/jira/browse/TEZ-3420?focusedCommentId=16831937&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16831937]
> it seems part of the problem is Hive's use of static global state for
> IOContext in the case of Tez. Another issue is the use of a JVM-wide
> ObjectRegistry
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
