Handle yield and restore in direct shard connection warnings

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 7.0.0, 8.0.0, 8.2.0-rc0, 8.1.0
    • Component/s: None
    • None
    • Catalog and Routing
    • 0
    • 1
    • None
    • 3
    • TBD
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      The direct shard connection checks are performed in both the auto getters and the shard role both at the initial acquisition and during a restore after a yield. This is very important when issuing errors because we need to ensure that an operation via direct connection which restores after we add a second shard cannot restore and continue running.

      For warnings, however, this can cause multiple errors to be emitted for a single operation since emitting the warning during the original acquisition would not prevent the operation from beginning to run and so if that operation yields and restores it will issue another warning for that same operation.

            Assignee:
            Unassigned
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: