[SERVER-68773] Move scoped range deleter lock under the range deleter service Created: 12/Aug/22 Updated: 29/Oct/23 Resolved: 15/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | auto-reverted, pm-2849-optimizations, range-deleter-cleanup, range-deleter-improvements, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29 |
| Participants: |
| Description |
|
Currently, the scoped range deleter lock is exposed by the balancer stats registry because it was the first component needing it. Purpose of this ticket is to move it under the range deleter service as it is directly related with range deletions. |
| Comments |
| Comment by Githook User [ 15/May/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by xgen-buildbaron-user [ 13/May/23 ] |
|
Ticket re-opened due to revert. concurrency_sharded_local_read_write_multi_stmt_txn began a consistent failure of drop_database_sharded_setFCV:CheckReplDBHashInBackground,drop_database_sharded_setFCV:CheckMetadataConsistencyInBackground,jstests/concurrency/fsm_workloads/drop_database_sharded_setFCV.js |
| Comment by Githook User [ 13/May/23 ] |
|
Author: {'name': 'auto-revert-processor', 'email': 'dev-prod-dag@mongodb.com', 'username': ''}Message: Revert " This reverts commit 3814bf328c42f7ec3754d79a7cc0701a575d3027. |
| Comment by Githook User [ 12/May/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |