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

Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2022/04/04 21:04:00 UTC

[jira] [Commented] (BEAM-14225) load balance jenkins jobs

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

Kyle Weaver commented on BEAM-14225:
------------------------------------

Surveyed a number of cron jobs and found they still running every six hours, but their schedules are staggered throughout the day now, in contrast to the earlier concentration of jobs around 12 AM, 6 AM, 12PM, 6PM.

> load balance jenkins jobs
> -------------------------
>
>                 Key: BEAM-14225
>                 URL: https://issues.apache.org/jira/browse/BEAM-14225
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Kyle Weaver
>            Priority: P2
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Jenkins can do automatic load balancing for cron jobs that use the "H" syntax [1], but we apply it only sporadically (and often incorrectly) in Beam. For example, the default setting is currently '0 */6 * * *' [2]. This means "every six hours, starting from exactly 00:00 (UTC)." Which creates load spikes every 6 hours, since a ton of jobs are run at once, rather than being staggered.
> [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.jelly#L40-L41
> [2] https://github.com/apache/beam/blob/4dddaf9c3d70b5b858c16265abee4cdbf0c72631/.test-infra/jenkins/CronJobBuilder.groovy#L40



--
This message was sent by Atlassian Jira
(v8.20.1#820001)