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

mongos_no_replica_set_refresh.js must always obtain config from the primary node

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.7, 3.3.3
    • Component/s: None
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding 10 (02/19/16), Sharding 11 (03/11/16)
    • Linked BF Score:
      0

      Description

      sharding_legacy failed on enterprise-rhel-62-64-bit

      mongos_no_replica_set_refresh.js - Logs | History

      BF Ticket Generated by Randolph Tan

       
      assert.soon failed: function (){ return numRSHosts() < 3; }
      doassert@src/mongo/shell/assert.js:15:14
      assert.soon@src/mongo/shell/assert.js:176:13
      @jstests/sharding/mongos_no_replica_set_refresh.js:53:1
      @jstests/sharding/mongos_no_replica_set_refresh.js:4:2
       
      2016-02-08T22:19:36.100+0000 E QUERY    [thread1] Error: assert.soon failed: function (){ return numRSHosts() < 3; } :
      doassert@src/mongo/shell/assert.js:15:14
      assert.soon@src/mongo/shell/assert.js:176:13
      @jstests/sharding/mongos_no_replica_set_refresh.js:53:1
      @jstests/sharding/mongos_no_replica_set_refresh.js:4:2
       
      failed to load: jstests/sharding/mongos_no_replica_set_refresh.js
      

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: