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

The writes of _configsvrEnableSharding to config.databases do not use local write concern

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.6.3
    • Sharding
    • Sharding
    • 36

    Description

      ShardLocal is given a Shard::RetryPolicy::kIdempotent retry policy for the config.databases write, where WriteConcernError is a retryable error (see remote_command_retry_scheduler.cpp. However, it runs into a DuplicateKeyError when it retries the write. See BF-6713 for details of the failure.

      I hypothesize that the issue is that ShardLocal/CatalogClient uses majority write/read concern, and instead it should use local and then mongos should call _configsvrEnableSharding with majority write concern so it waits after the write. Might want to make sure the mongos can deal with the WriteConcernError properly, so the config stepdown suite doesn't fail loudly.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: