[SERVER-66011] Enable internal_transactions_resharding.js in the concurrency_sharded_multi_stmt_txn_with_balancer suite Created: 27/Apr/22 Updated: 29/Oct/23 Resolved: 21/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Erin Liang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-nyc-subteam3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2022-06-27 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This suite runs the RunDBCheckInBackground hook. The hook runs the dbCheck command which generates {op: "c"} oplog entries as follows:
Resharding doesn't ignore dbCheck oplog entries but it expects every {op: "c"} oplog entry to be an applyOps oplog entry or commitTransaction oplog entry or abortTransaction oplog entry. So upon seeing a dbCheck oplog entry, the ReshardingRecipientService would throw OplogOperationUnsupported here, and that would cause the resharding operation to fail/hang. dbCheck is a read-only operation so resharding should ignore dbCheck oplog entries. There is already a ticket for addressing this (SERVER-63855). Once that ticket is complete, we should be able to enable the internal_transactions_resharding.js run in that suite. |
| Comments |
| Comment by Githook User [ 21/Jun/22 ] |
|
Author: {'name': 'Erin Liang', 'email': 'erin.liang@mongodb.com', 'username': 'erl-ang'}Message: |