Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11924

Docs for SERVER-36101: Replication should not depend on the presence of lastStableCheckpointTimestamp in status reports to identify recoverable rollback capable nodes

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.2
    • manual, Server
    • None

    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)

      Attachments

        Issue Links

          Activity

            People

              kay.kim@mongodb.com Kay Kim (Inactive)
              kay.kim@mongodb.com Kay Kim (Inactive)
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                2 years, 50 weeks, 5 days ago