hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahil Takiar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16334) Query lock contains the query string, which can cause OOM on ZooKeeper
Date Mon, 03 Apr 2017 17:42:41 GMT

    [ https://issues.apache.org/jira/browse/HIVE-16334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953897#comment-15953897
] 

Sahil Takiar commented on HIVE-16334:
-------------------------------------

[~pvary] yes its good to display the actual query when running {{show locks ...}} but the
full query string should already be stored in HS2, right? So there shouldn't be a reason to
store the same query string inside Zookeeper. Hive should just store the query-id in ZK, and
then use the query-id to do a lookup of the full query string in HS2. This should reduce a
lot of memory pressure on ZK nodes.

> Query lock contains the query string, which can cause OOM on ZooKeeper
> ----------------------------------------------------------------------
>
>                 Key: HIVE-16334
>                 URL: https://issues.apache.org/jira/browse/HIVE-16334
>             Project: Hive
>          Issue Type: Improvement
>          Components: Locking
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>         Attachments: HIVE-16334.patch
>
>
> When there are big number of partitions in a query this will result in a huge number
of locks on ZooKeeper. Since the query object contains the whole query string this might cause
serious memory pressure on the ZooKeeper services.
> It would be good to have the possibility to truncate the query strings that are written
into the locks



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message