Add more testing around lastStableRecoveryTimestamp

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The lastStableRecoveryTimestamp field reported in replSetGetStatus contains a valuable timestamp that indicates that all data up to this timestamp is guaranteed to be in the checkpoint upon restart. It looks like we don't have a lot of testing for this timestamp today, so we should consider adding more testing. Specifically, we should test the value of the field when:

      • We have a stable checkpoint that is advancing
      • We have stable timestamp advancing but checkpoint does not advance
      • We don't have a checkpoint but we do have a recovery timestamp
      • We don't have a recovery timestamp or checkpoint

            Assignee:
            Unassigned
            Reporter:
            Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: