[SERVER-64577] Must not accept tags in write concern defaults in FCV < 5.3 Created: 16/Mar/22 Updated: 29/Oct/23 Resolved: 17/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.0, 5.3.0-rc3 |
| Fix Version/s: | 5.3.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matt Broadstone |
| 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 | ||||||||
| Backport Requested: |
v5.3
|
||||||||
| Sprint: | Server Serverless 2022-03-21 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 183 | ||||||||
| Description |
|
Because write concern defaults are replicated via the oplog, when in a downgrade FCV we must ensure a downgraded binary can handle them. So the new feature which allows tags in write concerns must be FCV-gated. |
| Comments |
| Comment by Githook User [ 17/Mar/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |
| Comment by Githook User [ 17/Mar/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: also fixes |
| Comment by Githook User [ 17/Mar/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: also fixes |