[SERVER-40158] Make failure to create an eventfd non-fatal Created: 15/Mar/19 Updated: 29/Oct/23 Resolved: 19/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Service Arch 2019-03-25 |
| Participants: |
| Description |
|
After introducing the linux baton more widely (on each client, on creation, rather than during an ARS dispatch), users are more likely to encounter that condition, and we can handle it more gracefully. By changing the failure to create an eventfd into a throwing exception, we'll cause new client object creation to throw, which will cause us to close the incoming client socket. |
| Comments |
| Comment by Githook User [ 19/Mar/19 ] |
|
Author: {'name': 'Jason Carey', 'username': 'hanumantmk', 'email': 'jcarey@argv.me'}Message: After introducing the linux baton more widely (on each client, on By changing the failure to create an eventfd into a throwing exception, |