[
https://issues.apache.org/jira/browse/BEAM-14225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Weaver updated BEAM-14225:
-------------------------------
Description:
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 used by all precommit cron jobs and others is
currently '0 */6 * * *' [2]. This means "every six hours, starting from exactly
00:00 (UTC)." Which creates load spikes every 6 hours, since all the precommits
and postcommits 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
was:
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 used by all precommit cron jobs and others is
currently '0 */6 * * *' [2]. This means "every six hours, starting from exactly
00:00 (UTC)." Which creates load spikes every 6 hours, since all the precommits
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
> 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
>
> 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 used by all precommit cron jobs and others is
> currently '0 */6 * * *' [2]. This means "every six hours, starting from
> exactly 00:00 (UTC)." Which creates load spikes every 6 hours, since all the
> precommits and postcommits 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)
