[SERVER-20526] investigate ASIO DNS resolution errors on Windows Created: 21/Sep/15 Updated: 15/Oct/15 Resolved: 15/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Adam Midvidy | Assignee: | Adam Midvidy |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Platform A (10/09/15), Platform B (10/30/15) | ||||
| Participants: | |||||
| Description |
|
Before we added the connection pool to ASIO we found that Windows hosts would sometimes have strange DNS resolution errors on long-running tests. The error mentioned finding duplicate hostnames on the network. After we added the connection pool in, the issue stopped surfacing, probably because we do way fewer DNS lookups. We should try to resurface this issue by disabling the pool (or setting max connections per host to Infinity). |
| Comments |
| Comment by Adam Midvidy [ 15/Oct/15 ] |
|
Other errors in the log suggest that this is a result of ephemeral port exhaustion. This hypothesis is supported by the fact that the symptoms went away with the addition of the connection pool, which makes ASIO far-more efficient w.r.t. port reuse. As such, I am going to close this out as 'Gone Away'. |