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

Posted to commits@samza.apache.org by "Shenoda Guirguis (JIRA)" <ji...@apache.org> on 2019/07/26 15:37:00 UTC

[jira] [Commented] (SAMZA-2282) Samza-sql diagnostics: Latency metrics are zero

    [ https://issues.apache.org/jira/browse/SAMZA-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893916#comment-16893916 ] 

Shenoda Guirguis commented on SAMZA-2282:
-----------------------------------------

I added some logging, and SamzaSqlEndToEnd test local run shows that these metrics are updated correctly (below) which means it is a matter of time unit/resolution. It is currently captured in milli-seconds:
{quote}[Samza StreamProcessor Container Thread-0] QueryTranslator [INFO] scanTime is: 2019-02-25T18:08:12.079Z

[Samza StreamProcessor Container Thread-0] QueryTranslator [INFO] outputTime is: 2019-02-25T18:08:12.113Z

[Samza StreamProcessor Container Thread-0] QueryTranslator [INFO] updating queryLatency with: 34

[Samza StreamProcessor Container Thread-0] QueryTranslator [INFO] arrivalTime is: 2019-02-25T18:08:12.035Z
{quote}

> Samza-sql diagnostics: Latency metrics are zero
> -----------------------------------------------
>
>                 Key: SAMZA-2282
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2282
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Shenoda Guirguis
>            Priority: Major
>
> All processing latency metrics are reported as zero, which doesn't seem correct



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)