[
https://issues.apache.org/jira/browse/HIVE-19821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517685#comment-16517685
]
Hive QA commented on HIVE-19821:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12928256/HIVE-19821.2.WIP.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/11933/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11933/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11933/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12928256/HIVE-19821.2.WIP.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: 12928256 - PreCommit-HIVE-Build
> Distributed HiveServer2
> -----------------------
>
> Key: HIVE-19821
> URL: https://issues.apache.org/jira/browse/HIVE-19821
> Project: Hive
> Issue Type: New Feature
> Components: HiveServer2
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
> Attachments: HIVE-19821.1.WIP.patch, HIVE-19821.2.WIP.patch,
> HIVE-19821_ Distributed HiveServer2.pdf
>
>
> HS2 deployments often hit OOM issues due to a number of factors: (1) too many
> concurrent connections, (2) query that scan a large number of partitions have
> to pull a lot of metadata into memory (e.g. a query reading thousands of
> partitions requires loading thousands of partitions into memory), (3) very
> large queries can take up a lot of heap space, especially during query
> parsing. There are a number of other factors that cause HiveServer2 to run
> out of memory, these are just some of the more commons ones.
> Distributed HS2 proposes to do all query parsing, compilation, planning, and
> execution coordination inside a dedicated container. This should
> significantly decrease memory pressure on HS2 and allow HS2 to scale to a
> larger number of concurrent users.
> For HoS (and I think Hive-on-Tez) this just requires moving all query
> compilation, planning, etc. inside the application master for the
> corresponding Hive session.
> The main benefit here is isolation. A poorly written Hive query cannot bring
> down an entire HiveServer2 instance and force all other queries to fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
