You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "shanyu zhao (JIRA)" <ji...@apache.org> on 2014/05/31 03:33:02 UTC

[jira] [Updated] (HIVE-7155) WebHCat controller job exceeds container memory limit

     [ https://issues.apache.org/jira/browse/HIVE-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

shanyu zhao updated HIVE-7155:
------------------------------

    Attachment: HIVE-7155.patch

Patch attached. a new configuration "templeton.mapper.memory.mb" is introduced so that users can set this property in webhcat-site.xml to overwrite mapreduce.map.memory.mb for the webhcat controller job.

> WebHCat controller job exceeds container memory limit
> -----------------------------------------------------
>
>                 Key: HIVE-7155
>                 URL: https://issues.apache.org/jira/browse/HIVE-7155
>             Project: Hive
>          Issue Type: Bug
>          Components: WebHCat
>    Affects Versions: 0.13.0
>            Reporter: shanyu zhao
>            Assignee: shanyu zhao
>         Attachments: HIVE-7155.patch
>
>
> Submit a Hive query on a large table via WebHCat results in failure because the WebHCat controller job is killed by Yarn since it exceeds the memory limit (set by mapreduce.map.memory.mb, defaults to 1GB):
> {code}
>  INSERT OVERWRITE TABLE Temp_InjusticeEvents_2014_03_01_00_00 SELECT * from Stage_InjusticeEvents where LogTimestamp > '2014-03-01 00:00:00' and LogTimestamp <= '2014-03-01 01:00:00';
> {code}
> We could increase mapreduce.map.memory.mb to solve this problem, but this way we are changing this setting system wise.
> We need to provide a WebHCat configuration to overwrite mapreduce.map.memory.mb when submitting the controller job.



--
This message was sent by Atlassian JIRA
(v6.2#6252)