-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Note about Resque.redis config #469
base: master
Are you sure you want to change the base?
Conversation
In regards to #468. I missed that resque-scheduler was *completely* stand-alone and wouldn't catch on I use a different redis database for resque jobs. I've added this warning in the hopes that other people who also use a different redis database like will avoid this problem.
@@ -147,6 +147,17 @@ default `'text'`) | |||
* `VERBOSE` - Maximize log verbosity if non-empty (equivalent to a level | |||
of `MonoLogger::DEBUG`, default `false`) | |||
|
|||
*Warning: If you use a different redis database, other than the default database (0), to store your redis jobs, you will have store the Resque.redis into the initializer file* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't necessarily true, though. I think it would be clearer to say that specifying the full Redis URL within the schedule process is important and perhaps give some examples of how to do this, just like in the resque web example. I would also support adding the Redis URL as an env/cli option so that initializers are not necessary.
Does it run standalone even if a dependency to "environment" is specified? In that case it should pick up Redis config from an initializer, right? The weirdest thing for me is that schedules actually work, but delayed jobs don't. I think. |
@juanibiapina Sorry for delay! I don't think your question can be answered without knowing the specifics of how your code is loaded. The flexibility of this part of the configuration is a constant source of question bugs, unfortunately 🙍 |
My problem was another issue. Scheduler wasn't able to elect a master node properly. I cleaned up redis and it worked. |
@danlo Is this still relevant? It seems like simply stating that configuration comes from |
In regards to #468. I missed that resque-scheduler was completely stand-alone and wouldn't catch on to that I use a different redis database other than the default 0 for resque jobs.
I've added this warning in the hopes that other people who also use a different redis database like will avoid this problem.