hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16546) LLAP: Fail map join tasks if hash table memory exceeds threshold
Date Thu, 04 May 2017 10:38:04 GMT

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

Lefty Leverenz commented on HIVE-16546:
---------------------------------------

Doc note:  This adds *hive.llap.mapjoin.memory.monitor.check.interval* to HiveConf.java, so
it needs to be documented in the wiki for release 3.0.0.

* [Configuration Properties -- LLAP | https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-LLAP]

Added a TODOC3.0 label.

> LLAP: Fail map join tasks if hash table memory exceeds threshold
> ----------------------------------------------------------------
>
>                 Key: HIVE-16546
>                 URL: https://issues.apache.org/jira/browse/HIVE-16546
>             Project: Hive
>          Issue Type: Bug
>          Components: llap
>    Affects Versions: 3.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>              Labels: TODOC3.0
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16546.1.patch, HIVE-16546.2.patch, HIVE-16546.3.patch, HIVE-16546.4.patch,
HIVE-16546.5.patch, HIVE-16546.WIP.patch
>
>
> When map join task is running in llap, it can potentially use lot more memory than its
limit which could be memory per executor or no conditional task size. If it uses more memory,
it can adversely affect other query performance or it can even bring down the daemon. In such
cases, it is better to fail the query than to bring down the daemon. 



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

Mime
View raw message