[SERVER-60061] [Upgrade/downgrade] Avoid checking internal transactions feature flag more than once when constructing transaction oplog entries and config.transactions entry Created: 17/Sep/21 Updated: 29/Oct/23 Resolved: 21/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2021-10-04 | ||||
| Participants: | |||||
| Linked BF Score: | 132 | ||||
| Story Points: | 1 | ||||
| Description |
|
Currently, we check the feature flag for internal transactions twice when committing a transaction (once to decide if we should add the txnRetryCounter to the applyOps oplog entry and once to decide if we should add the txnRetryCounter to the config.transactions entry) and the FCV can change between those checks, and this can cause the config.transactions entry on the primary to be inconsistent with the config.transactions entries on secondaries. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |