[SERVER-78798] Disable strict flag for TransactionCoordinatorDocument Created: 10/Jul/23 Updated: 29/Oct/23 Resolved: 11/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ivan Fefer | Assignee: | Ivan Fefer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v7.0, v6.0, v5.0, v4.4
|
||||||||||||||||
| Sprint: | QE 2023-07-24 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 42 | ||||||||||||||||
| Description |
|
In Now in rare cases when coordinator replica set is killed and downgraded after persisting decision, but before receiving acks from participants, it won't be able to start because old version will throw unknown field error during parsing of TransactionCoordinatorDocument. We want to disable strict flag for this document to avoid problems in the future. |
| Comments |
| Comment by Githook User [ 12/Jul/23 ] |
|
Author: {'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}Message: |
| Comment by Ivan Fefer [ 12/Jul/23 ] |
|
The backport is also required to prevent issues for users who may upgrade straight from 6.0 to 7.1 (for some reason). But latest discussion with Sharding was that it should be fine as long as 7.0.0 has this backport |
| Comment by Githook User [ 10/Jul/23 ] |
|
Author: {'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}Message: |
| Comment by Ivan Fefer [ 10/Jul/23 ] |
|
I also would like to backport it pretty far to avoid future upgrade issues for clients, looking for upgrade after PM-2782 release |