Close inference pool after request servers are stopped #2292
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
Close inference pool after request servers are stopped.
We have seen a couple of 500 errors occur from MLServer after a shutdown has started. The stacktrace for that is as follows:
Based on the above, the router attempts to route a request to worker 17, but it no longer exists. We probably want to close the servers for all requests (and drain them) prior to closing the inference workers.
Changes Made
Moves the inference pool close call to after kafka, grpc, and rest servers are stopped
Related Issues
N/A
Screenshots (if applicable)
N/A
Checklist
Additional Notes