Investigate if ShardNotFound special-case handling in migration recovery can be avoided

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the ShardRegistry rewrite on SERVER-46202, it was necessary to add special-case handling for ShardNotFound errors to migration recovery (here and here, for when the recipient shard has been removed). We should investigate if it's possible to rework this interaction so that this special case isn't needed.

            Assignee:
            [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: