[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:
Backports
Related
related to SERVER-43664 Speedup WiredTiger storage engine sta... Closed
is related to SERVER-53247 Disable enableMajorityReadConcern:false Closed
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: SERVER-54074 Log start and end of changes to table log settings
Branch: v4.0
https://github.com/mongodb/mongo/commit/95d8e9e4ecbc53daad0dd637da8ac85931ff2b04

Comment by Gregory Wlodarek [ 28/Jan/21 ]

SERVER-43664, which has been backported all the way to v4.2, already logs a message if and when the table logging settings are being changed. https://github.com/mongodb/mongo/blob/da30ce1eb1884dd54bcb005da128b43ef4038bbf/src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp#L764-L779

 

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 SERVER-53247, so I think it would be good to have it in 5.0.

Comment by Gregory Wlodarek [ 27/Jan/21 ]

The table logging settings change under these circumstances:

  • (v4.0+) Switching between eMRC=on and eMRC=off for replica sets.
  • (v4.0+) Switching between standalone mode and replica set mode running on eMRC=on.
  • Upgrading from 3.6 to 4.0 with eMRC=on.
Generated at Thu Feb 08 05:32:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.