diff options
| author | Sean McGivern <sean@gitlab.com> | 2017-10-13 12:22:38 +0100 |
|---|---|---|
| committer | Sean McGivern <sean@gitlab.com> | 2017-10-16 10:31:20 +0100 |
| commit | f4e94c6ff7b2b5e96edb56d30737687becc4a1a8 (patch) | |
| tree | bde6d5e7dc650aceef551b67331f55a600d0b750 /changelogs | |
| parent | 5843a43c16e007193f5e26522d1e7368a0bdb2d7 (diff) | |
| download | gitlab-ce-f4e94c6ff7b2b5e96edb56d30737687becc4a1a8.tar.gz | |
Make usage ping scheduling more robust39017-gitlabusagepingworker-is-not-running-on-gitlab-com
On GitLab.com, we see that cron jobs sometimes don't run. This appears to be
because the process that polls for current cron jobs only has a 60 second
validity period, so if (for whatever reason) it misses those 60 seconds, we have
to wait until the next execution.
For the usage ping, this is particularly problematic, as that's only scheduled
to run once a week.
Changing it to run for every minute in a 10 minute period should work around
this, if the above diagnosis is correct. The job itself obtains an exclusive
lease for 24 hours, so rescheduling in quick succession is safe.
Diffstat (limited to 'changelogs')
| -rw-r--r-- | changelogs/unreleased/39017-gitlabusagepingworker-is-not-running-on-gitlab-com.yml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changelogs/unreleased/39017-gitlabusagepingworker-is-not-running-on-gitlab-com.yml b/changelogs/unreleased/39017-gitlabusagepingworker-is-not-running-on-gitlab-com.yml new file mode 100644 index 00000000000..89506f88637 --- /dev/null +++ b/changelogs/unreleased/39017-gitlabusagepingworker-is-not-running-on-gitlab-com.yml @@ -0,0 +1,5 @@ +--- +title: Make usage ping scheduling more robust +merge_request: +author: +type: fixed |