[SERVER-13375] don't rely on ConnectBG thread for nonblocking connect Created: 27/Mar/14 Updated: 28/May/19 Resolved: 28/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
We should use a standard nonblocking connect. ConnectBG is particularly fragile when large numbers of connections are created, since it provides poor control over timing and is subject to thread scheduling problems. |
| Comments |
| Comment by Mira Carey [ 28/May/19 ] |
|
We removed ConnectBG in |
| Comment by Greg Studer [ 28/Aug/14 ] |
|
Putting this on hold again - this won't work generically and will require a deeper custom Windows solution: |