summaryrefslogtreecommitdiff
path: root/app/models
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2019-07-21 23:00:37 -0700
committerStan Hu <stanhu@gmail.com>2019-07-22 10:23:07 -0700
commit583c12acf44ba18adea45eb0e61f287861c44e43 (patch)
treebd8e973c57a2c50396f0286b376713f30ec2abcb /app/models
parent3cc5535c0c7a52c93b00c1a1260eb8d828a3e9dc (diff)
downloadgitlab-ce-583c12acf44ba18adea45eb0e61f287861c44e43.tar.gz
Use persistent Redis cluster for Workhorse pub/sub notificationssh-use-shared-state-cluster-pubsub
Previously, in Omnibus, Workhorse expected to listen via the Redis shared state cluster for the `workhorse:notifications` publish/subscribe channel, but the Rails code was using the Sidekiq queue cluster for this. To fix this inconsistency, we make the Rails code use the persistent cluster, since we don't want Workhorse to be looking at anything Sidekiq-related.
Diffstat (limited to 'app/models')
-rw-r--r--app/models/ci/runner.rb2
1 files changed, 1 insertions, 1 deletions
diff --git a/app/models/ci/runner.rb b/app/models/ci/runner.rb
index 07d00503861..43ff874ac23 100644
--- a/app/models/ci/runner.rb
+++ b/app/models/ci/runner.rb
@@ -264,7 +264,7 @@ module Ci
private
def cleanup_runner_queue
- Gitlab::Redis::Queues.with do |redis|
+ Gitlab::Redis::SharedState.with do |redis|
redis.del(runner_queue_key)
end
end