[SERVER-26806] Randomly restart initial sync in the dynamic initial sync passthrough Created: 27/Oct/16 Updated: 05/Apr/17 Resolved: 13/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.2, 3.5.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Robert Guo (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 | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | TIG 2016-11-21, TIG 2016-12-12, TIG 2017-01-02 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently we randomly restart initial sync during initial sync in the dynamic resync passthrough: https://github.com/mongodb/mongo/blob/r3.4.0-rc1/buildscripts/resmokelib/testing/hooks.py#L261 We should remove the self.use_resync check so that we add coverage for shutting down initial sync during initial sync. Given the bugs we've had at shutdown recently, extra test coverage there would be good. |
| Comments |
| Comment by Githook User [ 22/Dec/16 ] |
|
Author: {u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}Message: (cherry picked from commit b74f90afc1164e0357c5649659aeed345b5f4fcd) |
| Comment by Githook User [ 13/Dec/16 ] |
|
Author: {u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}Message: |
| Comment by Robert Guo (Inactive) [ 12/Dec/16 ] |
|
Closing as won't fix for now. I haven't seen any failures related to starting/shutting down initial sync in the past couple of weeks. On the other hand, adding an initial sync node has caused the suites' runtime to fluctuate more; doing more restarts could make it worse. If we see any initial sync restart related failures elsewhere, I'd be happy to revisit this ticket. |