[SERVER-31333] DBConnectionPool doesn't return code `ShutdownInProgress` when it is being shut down Created: 29/Sep/17 Updated: 30/Oct/23 Resolved: 02/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.4.9, 3.5.13 |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2017-10-02 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Some sharding code paths (such as migration commit) rely on a shutdown code to be specified in order to gracefully terminate. The DBConnectionPool stops working when the server starts the shutdown sequence, but returns code 17382, which cannot be used to infer a shutdown. We should make it return a ErrorCodes::ShutdownInProgress instead. |
| Comments |
| Comment by Githook User [ 02/Oct/17 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: |