-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
nsqd/nsqadmin: "busy out" mode #1022
Comments
I'm on the fence whether this belongs in NSQ proper or not :) |
Since so many things live in a container world, i can see a control exposed from nsqd that makes it easier to put that node into a mode where it rejects incoming messages but allows any messages it does have to drain. You could then combine that with clients that properly handler write errors (which is actually infrequent in my experience) to retry against a secondary nsqd target. On the consumer side, this can be handled outside of NSQ pretty straight forwardly; I do this by watching for a touch file and having QR's go into "RDY 0" mode when that touch file is present. |
ping #1254 |
right now we need to go on a node manually and shut down the ingress services manually to a box to busy it out. it would be nice if that was exposed so we don't have to ssh into each box.
http://www.yourdictionary.com/busy-out
The text was updated successfully, but these errors were encountered: