[SERVER-47475] Make PeriodicJob aware of cancelation at global shutdown Created: 10/Apr/20 Updated: 29/Oct/23 Resolved: 21/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.7, 4.4.0-rc2, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Amirsaman Memaripour |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||||||
| Sprint: | Service arch 2020-04-20, Service arch 2020-05-04 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Linked BF Score: | 7 | ||||||||||||
| Description |
|
Starting a PeriodicJob that is not in the NOT_SCHEDULED state causes an invariant failure (see here). However, a PeriodicJob might get stopped before it's even started if its process receives a kill signals before it has fully initialized. To tolerate such scenarios, PeriodicJob should check if shutdown is in progress and quick return before checking the invariant. |
| Comments |
| Comment by Githook User [ 22/Apr/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: (cherry picked from commit e7165a3e49beb6b6904ba5047301a142cccea646) |
| Comment by Githook User [ 22/Apr/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: (cherry picked from commit e7165a3e49beb6b6904ba5047301a142cccea646) |
| Comment by Githook User [ 21/Apr/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |