[SERVER-26256] increase assert.soon() timeout in mongos_no_replica_set_refresh.js to 5 minutes Created: 22/Sep/16 Updated: 19/Nov/16 Resolved: 22/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.12 |
| Fix Version/s: | 3.3.14 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| 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: | Sharding 2016-10-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The default assert.soon() timeout was raised to 5 minutes from 30 seconds as of commit: Replica set monitor refresh is 30 seconds as of 3.3.12. Prior to raising the timeout, mongos_no_replica_set_refresh.js was sometimes failing if the mongos refreshed its replica set monitor just before a replica set node was removed, so we should send a higher timeout in the assert.soon() calls in mongos_no_replica_set_refresh.js in case the default assert.soon() timeout is lowered again. |
| Comments |
| Comment by Githook User [ 22/Sep/16 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: |