[SERVER-40225] Updates to the shard key field of a doc that will remain on the same shard will not error if the shard is in FCV4.2 even if other shards are in FCV4.0 Created: 19/Mar/19 Updated: 29/Oct/23 Resolved: 30/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2019-04-22, Sharding 2019-05-06 |
| Participants: |
| Description |
|
Currently, if an update to a shard key field will not cause the document to change shards, and this doc lives on a shard in FCV 4.2, the write will not error even if other shards are in FCV 4.0. We should investigate if it is possible to error in this case. |
| Comments |
| Comment by Githook User [ 30/Apr/19 ] |
|
Author: {'name': 'jannaerin', 'username': 'jannaerin', 'email': 'golden.janna@gmail.com'}Message: |
| Comment by Andy Schwerin [ 20/Mar/19 ] |
|
If a 4.0 secondary can process the operation, maybe we don’t need to prohibit it. FCV is there to prevent data corruption and incorrect results, primarily. |