[SERVER-74426] Release the DB lock before comparing collection in shardsvr participant Created: 28/Feb/23 Updated: 29/Oct/23 Resolved: 08/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20 |
| Participants: |
| Description |
|
At this moment, the shardsvr participant holds the DB lock even after we extrapolated the collections from local catalog. We should be able to release the lock and compare the two catalogs without holding the lock. The goal of this ticket is to change the code in shardsvr_check_metadata_consistency_participant_command.cpp in order to release the DB lock before comparing collections. |
| Comments |
| Comment by Githook User [ 08/Mar/23 ] |
|
Author: {'name': 'Pol Piñol Castuera', 'email': '67922619+PolPinol@users.noreply.github.com', 'username': 'PolPinol'}Message: |