[SERVER-61735] Add a new timing log step in MigrationDestinationManager to track the time waiting for critical section release Created: 25/Nov/21 Updated: 29/Oct/23 Resolved: 07/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-01-10 |
| Participants: |
| Description |
|
Before We should restore the former semantics of 'step 7'; and introduce a new 'step 8', which exists only when the new migration protocol is in use that is stepped after the critical section has been exited. |
| Comments |
| Comment by Githook User [ 07/Jan/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |