You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
mreiferson
changed the title
nsqadmin: set a node into busy out mode so it can finish it's work but not take on additional work
nsqd/nsqadmin: "busy out" mode
Apr 26, 2018
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.
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: