[SERVER-13306] replicasets/tags.js times out and fails occasionally on Windows Created: 21/Mar/14 Updated: 11/Jul/16 Resolved: 23/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0-rc2 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Happens because mongobridge is not passing back connection failures and keeps retrying forever if the target server is down. This causes the original call to time-out. This happens at shutdown time and only on Windows, when we cannot find the server's shutdown event and backing-off to the old method of connecting and invoking the shutdown command.
|
| Comments |
| Comment by Githook User [ 24/Mar/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: The connect timeout is set to 15 seconds of retrying, after which the Also added some extra logging and diagnostics so it is easier to analyse |
| Comment by Githook User [ 23/Mar/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: The connect timeout is set to 15 seconds of retrying, after which the Also added some extra logging and diagnostics so it is easier to analyse |