Commit a3bfd4b6 authored by Mike Kozono's avatar Mike Kozono

Geo: Reduce unnecessary resource usage

I didn't set `retry: false` for two reasons:

1. These are enqueued from events as well as cronjobs, so it could
   occasionally help to retry once after 30 seconds.
2. The existing log failure would have to be moved into a rescue if
   `retry: false`, since `sidekiq_retries_exhausted` would not get
   executed by Sidekiq code. And it's not worth the bother.

Changelog: changed
EE: true
parent 93127cfc
...@@ -8,7 +8,7 @@ module Geo ...@@ -8,7 +8,7 @@ module Geo
include GeoQueue include GeoQueue
include Gitlab::Geo::LogHelpers include Gitlab::Geo::LogHelpers
sidekiq_options retry: 3, dead: false sidekiq_options retry: 1, dead: false
sidekiq_retry_in { |count| 30 * count } sidekiq_retry_in { |count| 30 * count }
......
...@@ -8,7 +8,7 @@ module Geo ...@@ -8,7 +8,7 @@ module Geo
include GeoQueue include GeoQueue
include Gitlab::Geo::LogHelpers include Gitlab::Geo::LogHelpers
sidekiq_options retry: 3, dead: false sidekiq_options retry: 1, dead: false
sidekiq_retry_in { |count| 30 * count } sidekiq_retry_in { |count| 30 * count }
......
...@@ -8,7 +8,7 @@ module Geo ...@@ -8,7 +8,7 @@ module Geo
include GeoQueue include GeoQueue
include Gitlab::Geo::LogHelpers include Gitlab::Geo::LogHelpers
sidekiq_options retry: 3, dead: false sidekiq_options retry: 1, dead: false
sidekiq_retry_in { |count| 30 * count } sidekiq_retry_in { |count| 30 * count }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment