Start sidekiq-cluster in a service called sidekiq when enabling through sidekiq configuration
As @balasankarc mentioned in #239 (comment 312517057), it might be confusing for admins that they configure sidekiq, but manage a service called sidekiq-cluster
. Furthermore, we do intend to change that later (as discussed in the linked thread).
So we should make sure the service started is already called sidekiq:
-
sidekiq['cluster']
is nottrue
by default. - If
sidekiq['cluster]
is set totrue
-
sidekiq_cluster[*]
has no effect - The service spawned is still
sidekiq
, but it will runsidekiq-cluster
under the hood. It is managed bygitlab-ctl
commands tosidekiq
- The logs go to
/var/log/gitlab/sidekiq
.
-
- If
sidekiq_cluster[*]
is set- The service spawned is still
sidekiq-cluster
and will runsidekiq-cluster
under the hood. It is managed bygitlab-ctl
commands tosidekiq-cluster
- The logs go to
/var/log/gitlab/sidekiq-cluster
.
- The service spawned is still