[SERVER-53875] Stop the JournalFlusher thread from running at all unless requested in unit tests so that it does not access infrastructure still being initialized Created: 19/Jan/21 Updated: 29/Oct/23 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| 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
|
||||||||||||||||||||
| Sprint: | Execution Team 2021-03-22 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 154 | ||||||||||||||||||||
| Description |
|
The JournalFlusher creates an OperationContext and runs a data flush before pausing for unit testing until a request comes in. There is already a flag for the JournalFlusher, created to stop the JournalFlusher from running until requested, specially added to make it only run upon request in unit testing. However, it doesn't stop it from running an initial flush and needs to be expanded to do so. |
| Comments |
| Comment by Githook User [ 11/Mar/21 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: This protects against concurrent access to the service context during infrastructure setup, when we (cherry picked from commit e2dd9ca37c2027541fe1eb8b4a14c767d4384d2a) |
| Comment by Githook User [ 11/Mar/21 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: This protects against concurrent access to the service context during infrastructure setup, when we |