You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Xinyu Liu (JIRA)" <ji...@apache.org> on 2017/11/21 19:39:00 UTC

[jira] [Resolved] (SAMZA-1011) Better report event loop utilization metrics in AsyncRunLoop

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

Xinyu Liu resolved SAMZA-1011.
------------------------------
    Resolution: Won't Fix

> Better report event loop utilization metrics in AsyncRunLoop
> ------------------------------------------------------------
>
>                 Key: SAMZA-1011
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1011
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.11.0
>            Reporter: Xinyu Liu
>            Assignee: Xinyu Liu
>            Priority: Minor
>              Labels: newbie++
>
> This metric can be ambiguous in the new AsyncRunLoop. When running in the single thread mode, it means the time spent on task.processAsync(), window() and commit(), while in multithreading mode it will be the time spent on scheduling the tasks operations. So we need to figure out a better way to report it.



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