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

New sharded connections to a namespace trigger setShardVersion on all shards

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.9, 2.5.5
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Linked BF Score:
      0

      Description

      Issue Status as of January 8th, 2014

      ISSUE SUMMARY
      New sharded connections may fail to connect if any shard primary is down.

      This issue is part of 4 related issues which impact cluster availability when there is no primary available for a shard. See SERVER-7246, SERVER-5625, SERVER-11971 and SERVER-12041 for more details.

      USER IMPACT
      When any replica set in a sharded cluster has no available primary, new connections may fail to perform secondary reads due to an initial heuristic shard version check, or initial authorization check.

      It is present in versions of MongoDB prior to and including v2.4.8.

      SOLUTION
      Ignore failures of initial version check during connection and allow authorization against secondaries (primary is preferred when available).

      In v2.4.9 only (this is set by default in v2.6.0 and later), it is necessary to use the following two startup parameters for mongos:

      --setParameter ignoreInitialVersionFailure=true
      --setParameter authOnPrimaryOnly=false

      WORKAROUNDS
      There is no workaround.

      PATCHES
      Production release v2.4.9 contains the fix for this issue, and production release v2.6.0 will contain the fix as well.

      Original Description

      ... if a shard is down, we get a socket exception or no master exception. Issue is in _check in s/shardConnection.cpp

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: