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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16269920#comment-16269920 ] 

ASF GitHub Bot commented on SAMZA-1518:
---------------------------------------

GitHub user jmakes opened a pull request:

    https://github.com/apache/samza/pull/372

    SAMZA-1518: Add CPU utilization and thread count to JVM metrics

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jmakes/samza samza-1518

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/samza/pull/372.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #372
    
----
commit 7993193d4bf331e120aed5dcb877c37b5bb2d1f1
Author: Jacob Maes <jm...@linkedin.com>
Date:   2017-11-29T01:45:51Z

    SAMZA-1518: Add CPU utilization and thread count to JVM metrics

----


> 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)