-
Notifications
You must be signed in to change notification settings - Fork 65
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
Propagate queue pausing across multiple application instances #142
Comments
Yes! Our pause for now is per instance.
Yes, multiple instance deployment is a really common use-case. Using Do you want to take a stab implementing the status on One thing that we need to think about is that the status will become persistent across restarts. It's probably not an issue but something that we need to document so it's not a surprise to anyone. What do you think? Thanks again for creating relevant issues 👍 |
Currently Verk doesn't support distributed deployments. If you are running multiple application instances then pausing a queue in one instance will not pause the queue in the other N instances of Verk.
What if instead of writing queue pause/running status to
ets
we write to Redis, then check Redis during queue manager startup and at some interval to know if the queue status should be changed? Is a multiple instance Verk deployment a common use-case?The text was updated successfully, but these errors were encountered: