[
https://issues.apache.org/jira/browse/HIVE-16343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981608#comment-15981608
]
Siddharth Seth commented on HIVE-16343:
---------------------------------------
Getting access to the PID. Is there an easier and more reliable way to do this,
instead of relying on a pid file. Tez/YARN use the following - While launching
the process. environment.put("JVM_PID", "$$") / export. Within the process -
System.getenv().get("JVM_PID").
If retaining the current method of accessing the pid file, please move to a
helper class. The daemon class is getting a little noisy.
May want to introduce a config for which process monitor to use, instead of
relying on a YARN configuration.
How often will the metrics be collected?
> LLAP: Publish YARN's ProcFs based memory usage to metrics for monitoring
> ------------------------------------------------------------------------
>
> Key: HIVE-16343
> URL: https://issues.apache.org/jira/browse/HIVE-16343
> Project: Hive
> Issue Type: Improvement
> Components: llap
> Affects Versions: 3.0.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-16343.1.patch
>
>
> Publish MemInfo from ProcfsBasedProcessTree to llap metrics. This will useful
> for monitoring and also setting up triggers via JMC.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
