Geo: Limit max backoff time by 1 hour, instead of 7 days
What does this MR do?
This is an alternative solution for https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9553
We just limit max backoff time by 1 hour to mitigate https://gitlab.com/gitlab-org/gitlab-ee/issues/5348
The complete fix of https://gitlab.com/gitlab-org/gitlab-ee/issues/5348 conflicts with progressive backoff time.
What are the relevant issue numbers?
https://gitlab.com/gitlab-org/gitlab-ee/issues/5348
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
~~Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.~~ -
EE specific content should be in the top level /ee
folder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan? -
Security reports checked/validated by reviewer
Closes #5348 (closed) and https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9553
Edited by Michael Kozono