Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
The webhcat map only task does not need lot of memory. But when a java application is started with -server option, it allocates the memory specified as max heap size (-Xmx in oracle jre) upfront.
When combined with the memory used by pig or hive client, this can sometimes exceed the maximum memory limit for a map task (if configured).
Being able to specify the java options for the map task will be useful to avoid this issue.
Attachments
Attachments
Issue Links
- relates to
-
HCATALOG-597 improve AppConfig so values can only be retrieved one way
- Open