[DOCS-13396] [Server] Enhance "Troubleshoot Replica Sets" with invalid MinValidDocument remediation details Created: 06/Feb/20  Updated: 30/Oct/23  Resolved: 30/Mar/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Alex Bevilacqua Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: docs-administration, reopened, triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 44 weeks, 6 days ago

 Description   

Description

When migrating from 3.4 to 3.6, some customers can experience an error on their SECONDARY nodes due to a replset.minvalid document:

2020-02-05T12:04:58.394+0000 I - [initandlisten] Detected data files in /var/lib/mongodb created by the ‘mmapv1’ storage engine, so setting the active storage engine to ‘mmapv1’.
2020-02-05T12:04:58.403+0000 I JOURNAL [initandlisten] journal dir=/var/lib/mongodb/journal
2020-02-05T12:04:58.403+0000 I JOURNAL [initandlisten] recover : no journal files present, no recovery needed
2020-02-05T12:04:58.404+0000 I JOURNAL [durability] Durability thread started
2020-02-05T12:04:58.405+0000 I JOURNAL [journal writer] Journal writer thread started
2020-02-05T12:04:58.405+0000 I CONTROL [initandlisten]
2020-02-05T12:04:58.405+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
2020-02-05T12:04:58.405+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
2020-02-05T12:04:58.405+0000 I CONTROL [initandlisten]
2020-02-05T12:04:58.913+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory ‘/var/lib/mongodb/diagnostic.data’
2020-02-05T12:04:58.984+0000 I REPL [initandlisten] Did not find local initialized voted for document at startup.
2020-02-05T12:04:58.985+0000 I REPL [initandlisten] Did not find local Rollback ID document at startup. Creating one.
2020-02-05T12:04:58.985+0000 I STORAGE [initandlisten] createCollection: local.system.rollback.id with no UUID.
2020-02-05T12:04:58.986+0000 I REPL [initandlisten] Initialized the rollback ID to 1
2020-02-05T12:04:59.032+0000 F REPL [initandlisten] Caught exception during replication recovery: Location40415: BSON field ‘MinValidDocument.h’ is an unknown field.
2020-02-05T12:04:59.032+0000 F - [initandlisten] terminate() called. An exception is active; attempting to gather more information
2020-02-05T12:04:59.055+0000 F - [initandlisten] DBException::toString(): Location40415: BSON field ‘MinValidDocument.h’ is an unknown field.
Actual exception type: mongo::error_details::throwExceptionForStatus(mongo::Status const&)::NonspecificAssertionException

Scope of changes

Add a section to https://docs.mongodb.com/manual/tutorial/troubleshoot-replica-sets/ that outlines:

1. how to identify the replset.minvalid contains invalid docs

db.getSiblingDB("local").replset.minvalid.find({}, { _id: 0, h: 1, op: 1, ns: 1, o: 1 })

If the query displays any values then step 2 will be necessary

2. how to update the docs:

db.getSiblingDB("local").replset.minvalid.update({},{$unset:{h:"",op:"",ns:"",o:""}})

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Ashley Brown [ 30/Mar/23 ]

Closing because improvement no longer applies per comments. 

Comment by Ashley Brown [ 30/Mar/23 ]

Hi dmitry.ryabtsev@mongodb.com, thanks for clarifying! I'd be happy to discuss our backlog philosophy and the plan for general docs improvements with you, either over Slack or Zoom Just drop some time on my calendar and we can chat. I'll close this ticket per the discussion in the last few comments. 

Comment by Ashley Brown [ 28/Mar/23 ]

Hi dmitry.ryabtsev@mongodb.com – same question here. Could you verify that this work still applies to currently-supported versions of MongoDB? If so, which ones? Thanks!

Comment by Alex Bevilacqua [ 28/Mar/23 ]

ashley.brown@mongodb.com this likely should have been actioned a few years ago, however at this point the versions of the server this would impact have all reached EOL. dmitry.ryabtsev@mongodb.com indicated there was still a need for docs improvements here, however if he no longer feels strongly that this is beneficial we can close this out as Won't Do.

Comment by Ashley Brown [ 27/Mar/23 ]

Hi alex.bevilacqua@mongodb.com, could you verify that this work still applies to currently-supported versions of MongoDB? If so, which ones? Thanks!

Comment by Sarah Olson [ 03/Nov/22 ]

Thanks dmitry.ryabtsev@mongodb.com!

Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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