[SERVER-33552] Halt replication on last-stable secondary before FCV upgrade on latest binary primary in set_feature_compatibility_version.js Created: 28/Feb/18 Updated: 29/Oct/23 Resolved: 24/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc1, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||
| Sprint: | Storage NYC 2018-06-04 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 11 | ||||||||||||||||||||
| Description |
|
We've opted to close feature_compatibility_version_lagging_secondary.js avoids this problem by halting secondary replication while setFCV is called on the primary. I suspect it's only necessary to stop replication around the setFCV call. If so, perhaps modify feature_compatibility_version_lagging_secondary.js to do that, too, and add comments about why replication must stop! |
| Comments |
| Comment by Githook User [ 24/May/18 ] |
|
Author: {'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com'}Message: (cherry picked from commit 624922c6b9afd76dc24cceab8715ac305c973424) |
| Comment by Githook User [ 24/May/18 ] |
|
Author: {'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com'}Message: |
| Comment by Ian Whalen (Inactive) [ 26/Mar/18 ] |
|
dianna.hohensee - doing sprint planning with Geert and his understanding is that this is a test fix, not an rc0 blocker, and thus should get bumped out by a sprint. Marking for the future, but please talk to Geert if we misunderstood. |