repair can cause spurious NamespaceNotFound errors with concurrent initial sync operations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.1, 4.1.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-07-16
    • 68
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Replication ignores certain NamespaceNotFound errors for idempotency reasons, but this bug makes those assumptions unsafe.

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

                Created:
                Updated:
                Resolved: