We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
broker 目前的Stop方法,不够优雅,不能做到处理掉进来的请求,不接受新的请求,至少很突然的就全部关掉
The text was updated successfully, but these errors were encountered:
从代码来看,关闭的步骤如下:
1.取消zk注册,这会通知客户端不要再使用这个broker 2.关闭网络层,拒绝接收新请求 3.关闭线程池,采用shutdown,会处理掉已经submit的请求,拒绝新请求 4.关闭其他服务
理论上可以做到比较优雅的关闭的。不过在1和2之间应该做一个短暂的sleep,因为zk通知到客户端需要一个时间差。
Sorry, something went wrong.
不错,多谢辛苦工作,在问一个问题,关于message store里面flush,delete的schedule为什么不使用HashedWheelTimer来做?
在 2012-05-19 20:42:32,"dennis zhuang" reply@reply.github.com 写道:
从代码来看,关闭的步骤如下: 1.取消zk注册,这会通知客户端不要再使用这个broker 2.关闭网络层,拒绝接收新请求 3.关闭线程池,采用shutdown,会处理掉已经submit的请求,拒绝新请求 4.关闭其他服务 理论上可以做到比较优雅的关闭的。不过在1和2之间应该做一个短暂的sleep,因为zk通知到客户端需要一个时间差。 Reply to this email directly or view it on GitHub: #10 (comment)
Reply to this email directly or view it on GitHub: #10 (comment)
1.4.3 released.
No branches or pull requests
broker 目前的Stop方法,不够优雅,不能做到处理掉进来的请求,不接受新的请求,至少很突然的就全部关掉
The text was updated successfully, but these errors were encountered: