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

Posted to commits@samza.apache.org by "Shanthoosh Venkataraman (JIRA)" <ji...@apache.org> on 2018/02/15 20:38:00 UTC

[jira] [Updated] (SAMZA-1588) Add random jitter to monitor’s scheduling interval.

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

Shanthoosh Venkataraman updated SAMZA-1588:
-------------------------------------------
    Description: 
We’ve observed in LinkedIn execution environments that, all the monitors running on the YARN node-manager machines hitting an external service at the same time based upon the configured monitor scheduling interval.

 To eliminate unnecessary monitor execution spike and congestion caused to an external service at the same time, it’s essential to add a random jitter to the monitor scheduling interval.

Creating this ticket for book-keeping purposes to track these changes and this random jitter will be added based upon a boolean monitor configuration.

  was:
We’ve observed in LinkedIn execution environments that, all the monitors running on the YARN node-manager machines hitting an external service at the same time based upon the configured monitor scheduling interval.

 To eliminate unnecessary monitor execution spike and congestion caused to an external service at the same time, it’s essential to add a random jitter to the monitor scheduling interval.

Creating this ticket for book-keeping purposes to track these changes.


> Add random jitter to monitor’s scheduling interval.
> ---------------------------------------------------
>
>                 Key: SAMZA-1588
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1588
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Shanthoosh Venkataraman
>            Assignee: Shanthoosh Venkataraman
>            Priority: Minor
>
> We’ve observed in LinkedIn execution environments that, all the monitors running on the YARN node-manager machines hitting an external service at the same time based upon the configured monitor scheduling interval.
>  To eliminate unnecessary monitor execution spike and congestion caused to an external service at the same time, it’s essential to add a random jitter to the monitor scheduling interval.
> Creating this ticket for book-keeping purposes to track these changes and this random jitter will be added based upon a boolean monitor configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)