-
Notifications
You must be signed in to change notification settings - Fork 9
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
Graceful Shutdown for HTTP Server #8
Comments
👋 Thank you for raising an issue! We appreciate your effort in helping us improve. Our team will review it shortly. Stay tuned! |
I would like to work on this issue , kindly assign this issue to me . |
@muruga21
|
Nice find @vidhvath28, cant believe i missed it !! |
I have resolved the error and submitted a PR #9 , kindly please check it and consider this PR for Hacktoberfest and GSsoC by tagging it with hacktoberfest-accepted and gssoc-ext. |
I am a contributor for this repo too, @muruga21 please look into this. |
@toastsandwich just few minutes back I have fixed the issue and submitted an PR for it |
@toastsandwich can you please consider this PR for Hacktoberfest and GSsoC by tagging it with hacktoberfest-accepted and gssoc-ext. |
@vidhvath28 i am just contributor here, i am not project admin and for hacktober there must be tag added in repository as hacktober |
@vidhvath28 Great work man..! |
The current load balancer implementation lacks a graceful shutdown mechanism. This means that when the server receives termination signals (e.g., SIGINT or SIGTERM), it immediately stops processing new and ongoing requests, potentially leading to incomplete requests and loss of data. Implementing a graceful shutdown allows the server to stop accepting new requests, while still completing ongoing requests before shutting down. This ensures a smooth shutdown process and improves reliability during server restarts or deployments.
The text was updated successfully, but these errors were encountered: