-
Notifications
You must be signed in to change notification settings - Fork 26.5k
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
DEFAULT_SERVER_SHUTDOWN_TIMEOUT,This number is too big #2877
Comments
Can u give some reason? |
I know it can change value by change the dubbo.service.shutdown.wait, But, 10 second is not a appropriate value. In 2.5.x , it will sleep 10 second between Registry destroy and Protocol |
Since this sleep occurs when the service goes offline, what problems will it cause when you sleep longer? |
In my opinion, the difference between 10s or 5s is not very big. I can't decide which is better. Each has its own advantages and disadvantages. 5s is better? maybe. |
It will make the application shutdown slow in old version。 |
I agree with what you said. But personally think that the difference between fast closing and slow closing is not very big. |
I have pull a request to talk about it #2901 |
@LiZhenNet I've already merge #2901 For the particular issue against com.alibaba.dubbo.common.Constants#DEFAULT_SERVER_SHUTDOWN_TIMEOUT, it is unnecessary any longer to sleep 10 second between Registry destroy and Protocol. Ps. verify. If you still have confusion on this, pls. send email to dev@dubbo.apache.org and ask @yuyijq to give more comments. |
Environment
Steps to reproduce this issue
com.alibaba.dubbo.common.Constants#DEFAULT_SERVER_SHUTDOWN_TIMEOUT,
I think this number is too big,2~3 second is enough。
Expected Result
make a small default value 。
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
The text was updated successfully, but these errors were encountered: