You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Hari Sankar Sivarama Subramaniyan (JIRA)" <ji...@apache.org> on 2013/11/16 02:49:20 UTC

[jira] [Created] (HIVE-5836) Improve logging in ExecReducer.reduce()

Hari Sankar Sivarama Subramaniyan created HIVE-5836:
-------------------------------------------------------

             Summary: 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
             Fix For: 0.13.0


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.1#6144)