[SERVER-54074] [v4.0] Log start and end of changes to table log settings Created: 27/Jan/21 Updated: 29/Oct/23 Resolved: 04/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 4.0.22 |
| Fix Version/s: | 4.0.23 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||||||||||
| Sprint: | Execution Team 2021-02-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Under some circumstances we can change the table log (journaling) settings of every table on startup, and this can take a long time if the user has a lot of tables. This occurs in particular in conjunction with enableReadConcerMajority settings. We should log the start and end of this activity so that users and MongoDB support know why startup is slow. |
| Comments |
| Comment by Githook User [ 04/Feb/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Gregory Wlodarek [ 28/Jan/21 ] |
|
I'm going to make this a v4.0 ticket to add some logging there. |
| Comment by Bruce Lucas (Inactive) [ 27/Jan/21 ] |
|
This will hit every PSA customer due to |
| Comment by Gregory Wlodarek [ 27/Jan/21 ] |
|
The table logging settings change under these circumstances:
|