[jira] [Commented] (SAMZA-539) Add generic lag metric from high watermark - last processed message

["Chris Riccomini (JIRA)" <ji...@apache.org>]

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

Chris Riccomini commented on SAMZA-539:
---------------------------------------

bq. we could add a IncomingMessageEnvelope.getMaxOffset() API .

One slightly confusing thing about this API is that getMaxOffset would return the max offset at the point the fetch request was made. If there is a significant delay between when the message was fetched, and when it was processed, then the maxOffset that's returned might not actually be the max anymore.

Nevertheless, I think this API is still useful, and with the right documentation, should be fine. It mirrors Kafka's API and behavior, which also helps make it intuitive.

> Add generic lag metric from high watermark - last processed message
> -------------------------------------------------------------------
>
>                 Key: SAMZA-539
>                 URL: https://issues.apache.org/jira/browse/SAMZA-539
>             Project: Samza
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Yan Fang
>             Fix For: 0.9.0
>
>
> This is a follow-up ticket for SAMZA-503 .
> The gauge is to show the lag between _the offset of the most recent message on the incoming stream_ and _the offset of the most recent message that the StreamTask has processed_.
> As discussed in SAMZA-503, we could add a IncomingMessageEnvelope.getMaxOffset() API .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)