Answer the question
In order to leave comments, you need to log in
Why do tasks in sidekiq go to different processes?
Hi guys! I can't find an answer on how to solve this problem. We have staging and production environments of the same application on our server, respectively, both environments run their own sidekiq. When a task is added to production, from time to time it goes into the process, which is intended for staging. What is the best way to solve this problem?
Answer the question
In order to leave comments, you need to log in
Hello. Most likely, you have tasks from both environments put into one database in radish. Try to play around with the radish database settings, there it is somehow indicated through the url, I don’t remember from memory. And just in case, make sure you run sidekiq correctly, in the right environment and with the right gemfile.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question