[SERVER-29798] Ensure 3.4 secondary replicates featureCompatibilityVersion document in set_feature_compatibility_version.js Created: 22/Jun/17 Updated: 30/Oct/23 Resolved: 22/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | 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 | ||||
| Sprint: | Query 2017-07-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Since the secondary has no votes, "majority" for the replica set equals 1, so the secondary need not receive the featureCompatibilityDocument for the setFeatureCompatibilityVersion command to succeed. In this case, the primary closes the connection to the secondary, and it spins, outputting the error message "IncompatibleServerVersion". We should give the secondary votes, so that the write is required to reach the secondary. |
| Comments |
| Comment by Githook User [ 22/Jun/17 ] |
|
Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}Message: |