LeoMcA
3월 2, 2017, 5:12오후
1
Currently when using d/sidekiq to run sidekiq in the docker dev image, it starts a sidekiq process only for the critical queue.
The problem line is:
https://github.com/discourse/discourse/blob/master/bin/docker/sidekiq#L4
When I change sidekiq -q critical,low,default to sidekiq -q default,critical,low it starts a process only for the default queue, so there’s something wrong with the commas.
The workaround I’m using is just removing -q critical,low,default in its entirety, which starts a process servicing every queue.
2개의 좋아요
sam
3월 2, 2017, 5:34오후
2
Sure, send a pr through to fix
2개의 좋아요
LeoMcA
3월 2, 2017, 5:43오후
3
2개의 좋아요
sam
3월 2, 2017, 5:54오후
4
LeoMcA:
The workaround I’m using is just removing -q critical,low,default in its entirety, which starts a process servicing every queue.
are you 100% sure of that, I am finding this super confusing
LeoMcA
3월 2, 2017, 6:01오후
5
Yep, but from playing around I’ve also found -q critical -q low -q default works, which is a clearer fix, so I’ve updated my PR.
2개의 좋아요
tgxworld
3월 5, 2017, 3:22오전
8
I believe we don’t need to pass the queue options in dev since we have
3개의 좋아요