diff options
| author | Stan Hu <stanhu@gmail.com> | 2019-07-21 23:00:37 -0700 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2019-07-22 10:23:07 -0700 |
| commit | 583c12acf44ba18adea45eb0e61f287861c44e43 (patch) | |
| tree | bd8e973c57a2c50396f0286b376713f30ec2abcb /changelogs | |
| parent | 3cc5535c0c7a52c93b00c1a1260eb8d828a3e9dc (diff) | |
| download | gitlab-ce-sh-use-shared-state-cluster-pubsub.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 'changelogs')
| -rw-r--r-- | changelogs/unreleased/sh-use-shared-state-cluster-pubsub.yml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changelogs/unreleased/sh-use-shared-state-cluster-pubsub.yml b/changelogs/unreleased/sh-use-shared-state-cluster-pubsub.yml new file mode 100644 index 00000000000..5e72f23d7ad --- /dev/null +++ b/changelogs/unreleased/sh-use-shared-state-cluster-pubsub.yml @@ -0,0 +1,5 @@ +--- +title: Use persistent Redis cluster for Workhorse pub/sub notifications +merge_request: 30990 +author: +type: fixed |