[SERVER-28815] multi_rs.js - step down primary during upgrade/downgrade without {force:true} Created: 14/Apr/17 Updated: 12/Oct/17 Resolved: 19/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.16, 3.4.5, 3.5.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
update: fixed multi_rs.js to not use forced step downs. this reduces the likelihood of rollbacks in the upgraded/downgraded replica set. --------- These 3 tests have overlapping coverage and it's unclear what benefits are provided by the background ops started during the upgrade/downgrade process. |
| Comments |
| Comment by Githook User [ 13/Jul/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: (cherry picked from commit 53907c0094e26e39b813ae369be52a4e51fc3a08) |
| Comment by Githook User [ 22/Apr/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: (cherry picked from commit 53907c0094e26e39b813ae369be52a4e51fc3a08) |
| Comment by Githook User [ 19/Apr/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: Branch: master |