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

Remove ShardRegistry::kWriteConcernError in favor of using an error_class

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.5
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 13 (04/22/16), Repl 14 (05/13/16)

      Description

      https://github.com/mongodb/mongo/commit/889ca31c1a1e7725b14f291233a4ee4f7afea111 introduces an error code set of write concern errors and hung it in the ShardRegistry, even though the only users of this set are the user management commands. This is not the right place for this set to live. Instead we should define an error_class in error_codes.err and use the is*Error method it creates

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: