hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <>
Subject [jira] [Commented] (HIVE-7155) WebHCat controller job exceeds container memory limit
Date Mon, 02 Jun 2014 20:07:01 GMT


Thejas M Nair commented on HIVE-7155:

One concern I have with the default value of templeton.mapper.memory.mb being set to 1GB is
that the cluster might be having a larger value, but webhcat would
end up having a smaller limit for it.
I think we should take into consideration the current setting for
in the cluster. If the default value of is greater than the value
of templeton.mapper.memory.mb, I think we should use that. ie, templeton.mapper.memory.mb
should be used for setting a higher value if necessary.

What has been a good value for templeton.mapper.memory.mb in your experience ?

> WebHCat controller job exceeds container memory limit
> -----------------------------------------------------
>                 Key: HIVE-7155
>                 URL:
>             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,
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 to solve this problem, but this way we are
changing this setting system wise.
> We need to provide a WebHCat configuration to overwrite when
submitting the controller job.

This message was sent by Atlassian JIRA

View raw message