[
https://issues.apache.org/jira/browse/TEZ-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Balamohan updated TEZ-1335:
----------------------------------
Attachment: JMXHistoryLoggingService.java
Attaching the crude patch which i used to generate the screenshot. Plz set the
following properties
tez.am.launch.cmd-opts="-Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jremote.ssl=false" and
tez.history.logging.service.class=org.apache.tez.dag.history.logging.impl.JMXHistoryLoggingService
JMC can be used to connect to the running AM by providing the hostname & port
number. Once connected, DAGMetrics can be viewed by adding
hadoop->tez-DAGMetrics attributes to JMC.
> JMX based history logging service
> ---------------------------------
>
> Key: TEZ-1335
> URL: https://issues.apache.org/jira/browse/TEZ-1335
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Rajesh Balamohan
> Labels: performance
> Attachments: jmc_test_screenshot.png
>
>
> Expose important metrics of tez via JMX (metrics2 impl of hadoop can be handy
> here).
> This would be helpful in quickly creating visualizations
> (monitoring/debugging) via JMC console when the application is running.
> Users can enable this optionally by enabling
> tez.history.logging.service.class=org.apache.tez.dag.history.logging.impl.JMXHistoryLoggingService
--
This message was sent by Atlassian JIRA
(v6.2#6252)
