Replication should not depend on the presence of lastStableCheckpointTimestamp in status reports to identify recoverable rollback capable nodes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.2
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-07-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

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

              Assignee:
              Dianna Hohensee (Inactive)
              Reporter:
              Dianna Hohensee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: