[SERVER-43992] Always close user sockets during global process shutdown Created: 14/Oct/19 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
During global process shutdown, we kill all operations and return a shutdown error over client sockets. But this doesn't actually make a lot of sense, as the host is unlikely to be a good target for more operations over those sockets and network errors are already retriable. Just closing the socket would probably produce better results than what we're doing today. This should be a reasonably simple change (a check, probably somewhere in the service state machine / entry point, to close the socket rather than return a result if we're in global shutdown and we've been killed with a shutdown error) |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ] |
|
We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |