[SERVER-43236] Reconfig cmd should wrap the no-op oplog write in writeConflictRetry block. Created: 09/Sep/19 Updated: 29/Oct/23 Resolved: 24/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Ali Mir |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.2, v4.0, v3.6
|
||||||||
| Sprint: | Repl 2019-10-21, Repl 2019-11-04 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 19 | ||||||||
| Description |
|
Currently, reconfig cmd does not wrap the no-op oplog write write in a writeConflictRetry block. It's always safe to wrap any writes to a record store in a writeConflictRetry block because writeConflict exception can be thrown in the mongodb layer even for some memory pressure/issues in WiredTiger. |
| Comments |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'username': 'ali-mir', 'email': 'ali.mir@mongodb.com', 'name': 'Ali Mir'}Message: (cherry picked from commit 55e80afa2d511b9bd1a316d3fd4cb6185baa829b) |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'name': 'Ali Mir', 'username': 'ali-mir', 'email': 'ali.mir@mongodb.com'}Message: (cherry picked from commit 55e80afa2d511b9bd1a316d3fd4cb6185baa829b) |
| Comment by Githook User [ 05/Nov/19 ] |
|
Author: {'username': 'ali-mir', 'email': 'ali.mir@mongodb.com', 'name': 'Ali Mir'}Message: (cherry picked from commit 55e80afa2d511b9bd1a316d3fd4cb6185baa829b) |
| Comment by Githook User [ 24/Oct/19 ] |
|
Author: {'name': 'Ali Mir', 'username': 'ali-mir', 'email': 'ali.mir@mongodb.com'}Message: |