Instances of ShardingDDLCoordinator are not throwing on NotPrimaryError nor ShutdownError

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2021-04-05
    • 165
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The current implementation of the onCompletion callback on the instances of the ShardingDDLCoordinator are simply returning if there was a NotPrimaryError or ShutdownError category, if there is a write and the DDL operation fails because of a stepdown, then that error would not propagate to the router nor the operation retried, giving an ok:0 result to the user when actually the operation haven't finished. We should throw on those categories but leaving the current approach of not removing the coordinator document on those scenarios.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: