[
https://issues.apache.org/jira/browse/HIVE-16343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981631#comment-15981631
]
Prasanth Jayachandran commented on HIVE-16343:
----------------------------------------------
bq. While launching the process. environment.put("JVM_PID", "$$") / export.
Within the process - System.getenv().get("JVM_PID").
does it also happen for process launched by slider?
bq. Is there an easier and more reliable way to do this, instead of relying on
a pid file
I thought this is the reliable when compared to others :) The current default
location for the pid file is not reliable as it defaults to /tmp/user location.
If JVM_PID is guaranteed to be set I can add that option as well.
bq. May want to introduce a config for which process monitor to use, instead of
relying on a YARN configuration.
hmm.. why do we need this? Unless LLAP adds its own class it is not that
useful. Isn't it?
bq. How often will the metrics be collected?
Configurable in hadoop-metrics2.properties file. The template and Ambari
default is to collect every 10s and publish every 5 mins.
> 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)
