[SERVER-84087] Make sure ExecutorPool gets terminated after migrations have completed Created: 12/Dec/23 Updated: 03/Jan/24 Resolved: 14/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.0, 4.4.0, 5.0.0, 6.0.0, 7.0.0, 7.2.0 |
| Fix Version/s: | 7.2.1, 7.3.0-rc0, 7.0.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Sander | Assignee: | Robert Sander |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | car-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v7.2, v7.0, v6.0, v5.0, v4.4
|
||||||||
| Sprint: | CAR Team 2023-12-25 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 32 | ||||||||
| Description |
|
When the system is being shutdown, it might happen that migrations are still ongoing [in cleanup], while the ExecutorPool they schedule work on gets terminated. In order to prevent this, we should make sure that all migrations have completed before the ExecutorPool they use terminates. |
| Comments |
| Comment by Githook User [ 03/Jan/24 ] |
|
Author: {'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'}Message: (cherry picked from commit fbcc593e99ee8178295c1cd0808ad775d3e01b90) |
| Comment by Githook User [ 19/Dec/23 ] |
|
Author: {'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'}Message: (cherry picked from commit fbcc593e99ee8178295c1cd0808ad775d3e01b90) GitOrigin-RevId: 39a0481f61bbca447f9b83ad48c584c0351e66fc |
| Comment by Githook User [ 14/Dec/23 ] |
|
Author: {'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'}Message: GitOrigin-RevId: fbcc593e99ee8178295c1cd0808ad775d3e01b90 |