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

Add test to ensure that read-only operations against the config db continue to work if the config server primary is unreachable from mongos

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.5
    • Affects Version/s: 3.2.4
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 13 (04/22/16)

      Original Title and description: Some read-only operations (eg count,aggregate) fail against the config database when the config server primary is unreachable
      If you have a sharded cluster where the mongos cannot reach the config server primary, and you try to run count on any collection in the config server, it fails saying it cannot find the primary, even if you set the read preference to 'secondary'. This seems to only affect 3.2, this seems to have been fixed somehow in master

        1. primary_shard_server_blackholed_from_mongos.js
          2 kB

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: