[SERVER-20903] AsyncResultsMerger should not do target host resolution under a mutex Created: 13/Oct/15 Updated: 14/Oct/15 Resolved: 14/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
See Filing this ticket in case we decide to do a short-term fix for not doing hostname resolution under a mutex in 3.2. |
| Comments |
| Comment by Kaloian Manassiev [ 14/Oct/15 ] |
|
Closing as 'won't fix', because the way ReplicaSetMonitor works now, it sets socket timeout of 5 sec on the connection which calls isMaster, so the block will not last more than 5 seconds. The proper fix is described in |