hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahil Takiar (JIRA)" <>
Subject [jira] [Updated] (HIVE-19821) Distributed HiveServer2
Date Mon, 18 Jun 2018 14:58:00 GMT


Sahil Takiar updated HIVE-19821:
    Attachment: HIVE-19821_ Distributed HiveServer2.pdf

> Distributed HiveServer2
> -----------------------
>                 Key: HIVE-19821
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: HiveServer2
>            Reporter: Sahil Takiar
>            Assignee: Sahil Takiar
>            Priority: Major
>         Attachments: HIVE-19821.1.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

View raw message