[
https://issues.apache.org/jira/browse/HIVE-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harish Butani updated HIVE-5836:
--------------------------------
Fix Version/s: (was: 0.13.0)
> Improve logging in ExecReducer.reduce()
> ---------------------------------------
>
> Key: HIVE-5836
> URL: https://issues.apache.org/jira/browse/HIVE-5836
> Project: Hive
> Issue Type: Bug
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
>
> Although ExecReducer.reduce() logs the used JVM heap memory, we need to log
> the committed, max and used memory
> (http://docs.oracle.com/javase/6/docs/api/java/lang/management/MemoryUsage.html)
> to debug any future outofmemory issues.
> l4j.info("ExecReducer: processing " + cntr
> + " rows: used memory = " + used_memory);
> i.e. the above log info should include max_memory as well as committed_memory
> for a propery analysis of memory usage at runtime.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
