[DOCS-11924] Docs for SERVER-36101: Replication should not depend on the presence of lastStableCheckpointTimestamp in status reports to identify recoverable rollback capable nodes Created: 30/Jul/18  Updated: 13/Nov/23  Resolved: 11/Jul/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.2, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

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

Issue Links:
Documented
documents SERVER-36101 Replication should not depend on the ... Closed
Participants:
Days since reply: 4 years, 30 weeks, 6 days ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

----------------------------

Original Description

Description:

The lastStableCheckpointTimestamp field of replSetGetStatus is deprecated in v4.2

We have introduced a new field in v4.2 called lastStableRecoveryTimestamp in replSetGetStatus. It should be documented as for internal replication use, and no further details given.

Thanks!

Engineering Ticket Description:

This might require surfacing some other indicator in the storage engine up into replication. Also replication test infrastructure changes.

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Githook User [ 11/Jul/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-11924: 4.2 deprecates lastStableCheckpointTimestamp
Branch: master
https://github.com/mongodb/docs/commit/ec53706ca8687d73eea476292c30ba76897675fc

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