Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-55616

Instances of ShardingDDLCoordinator are not throwing on NotPrimaryError nor ShutdownError

    XMLWordPrintableJSON

Details

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

    Description

      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.

      Attachments

        Activity

          People

            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: