[SERVER-30464] Edit startup warning when running replset member as standalone to mention that data may look inconsistent Created: 01/Aug/17  Updated: 30/Oct/23  Resolved: 19/Mar/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Kyle Suarez
Resolution: Fixed Votes: 0
Labels: neweng, rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-33292 Have storage dictate where replicatio... Closed
Documented
is documented by DOCS-11475 Docs for SERVER-30464: Edit startup w... Closed
Related
related to SERVER-33986 Log stable checkpoint when restarting... Closed
is related to SERVER-33349 Add command to get stable checkpoint ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-03-26
Participants:

 Description   

With the recover to timestamp project now when you restart a replica set node as a standalone, the data will be at the checkpoint timestamp even though the oplog may contain entries past that time that have 'logically' been applied to this node (and would get applied at startup before accepting connections if the node was restarted as a replica set member again).

We already log the following startupWarning when a standalone is brought up that detects a replica set configuration:

2017-08-01T14:47:29.115-0400 I STORAGE  [initandlisten] ** WARNING: mongod started without --replSet yet 1 documents are present in local.system.replset
2017-08-01T14:47:29.115-0400 I STORAGE  [initandlisten] **          Restart with --replSet unless you are doing maintenance and  no other clients are connected.
2017-08-01T14:47:29.115-0400 I STORAGE  [initandlisten] **          The TTL collection monitor will not start because of this.
2017-08-01T14:47:29.115-0400 I STORAGE  [initandlisten] **         

We should amend that message to also say that the data may look inconsistent with the oplog. Perhaps something like adding the line "Database contents may appear inconsistent with the contents of the oplog and may appear to not contain writes that were visible when this node was running as part of a replica set." between the first and second lines of the existing message.



 Comments   
Comment by Kyle Suarez [ 19/Mar/18 ]

judah.schvimer, this has been pushed in [https://github.com/mongodb/mongo/commit/08f5647db5fc54395a0c1bb3a0622d058e338ec7|08f5647d] but without logging the value of the stable checkpoint. Want me to make a new ticket for that and put it in rollback-optional?

Comment by Githook User [ 19/Mar/18 ]

Author:

{'email': 'kyle.suarez@mongodb.com', 'name': 'Kyle Suarez', 'username': 'ksuarz'}

Message: SERVER-30464 edit startup warning when replset member started as standalone
Branch: master
https://github.com/mongodb/mongo/commit/08f5647db5fc54395a0c1bb3a0622d058e338ec7

Comment by Kyle Suarez [ 12/Mar/18 ]

alyson.cabral – done.

Comment by Alyson Cabral (Inactive) [ 12/Mar/18 ]

Can we add docs needed to this ticket?

Comment by Judah Schvimer [ 01/Mar/18 ]

It would be very helpful if this could specify if we restarted at a stable checkpoint, and if so the timestamp of that checkpoint.

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