[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: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Storage NYC 2018-11-19 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
|
| Comments |
| Comment by Githook User [ 15/Nov/18 ] |
|
Author: {'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}Message: |
| 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. |