You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2017/11/29 00:57:00 UTC

[jira] [Assigned] (SAMZA-1518) Add CPU utilization and thread count to JVM metrics

     [ https://issues.apache.org/jira/browse/SAMZA-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jake Maes reassigned SAMZA-1518:
--------------------------------

    Assignee: Jake Maes

> Add CPU utilization and thread count to JVM metrics
> ---------------------------------------------------
>
>                 Key: SAMZA-1518
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1518
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>            Assignee: Jake Maes
>              Labels: newbie
>
> With the addition of multithreading in Samza, we've seen more jobs become bottlenecked on CPU. In order to help trouble shoot these cases, we should add the following metrics to JvmMetrics.scala:
> process-cpu-usage - com.sun.management.OperatingSystemMXBean#getProcessCpuLoad()
> system-cpu-usage - com.sun.management.OperatingSystemMXBean#getSystemCpuLoad()
> open-file-descriptor-count - com.sun.management.UnixOperatingSystemMXBean#getOpenFileDescriptorCount()
> thread-count - java.lang.management.ThreadMXBean#getThreadCount()
> The first three metrics will only be emitted if the bean returned by ManagementFactory.getOperatingSystemMXBean() is of the appropriate type.
> All of the new metrics should be gauges, not counters.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)