[SERVER-37483] Reintroduce live changes to table logging settings Created: 05/Oct/18  Updated: 29/Oct/23  Resolved: 15/Nov/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.6

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-37484 Only alter table logging settings on ... Closed
Related
is related to SERVER-37227 Reintroduce enableMajorityReadConcern... Closed
is related to WT-4354 Improve fast path WT_SESSION:alter Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-11-19
Participants:

 Description   

SERVER-37227 [re-]introduced turning off majority reads into master via a forward port from 4.0. However, the change to table settings in the constructor did not get reintroduced. This means that tables are created with the appropriate logging settings, but restarting while toggling majority reads will not adjust the table settings accordingly.



 Comments   
Comment by Githook User [ 15/Nov/18 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-37483: Ensure correct table logging configuration on startup.
Branch: master
https://github.com/mongodb/mongo/commit/014ba2b0a86281a7bd52e4c99a25d10915e137c1

Comment by Daniel Gottlieb (Inactive) [ 13/Nov/18 ]

PM-1191 (disable majority reads) is changing its strategy. 4.2 will log tables the same way (roughly: replicated tables are not logged) with majority reads on and off, but replication will report a "stable" timestamp that moves forward despite potential problems in advancing the majority commit point.

Additionally, data upgraded from 4.0 can now be in a state where tables are logged for either setting.

For this ticket, that means the code in master should always ensure table logging is changed on startup. SERVER-37897 will make the change to disregard the majority reads flag for deciding how the logging should be configured.

Generated at Thu Feb 08 04:46:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.