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

timing error in replsets_priority1.js

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker - P1 Blocker - P1
    • None
    • 2.2.0
    • Replication
    • ALL

    Description

      http://buildlogs.mongodb.org/V2.2%20OS%20X%2010.5%2064-bit/builds/63/test/slow%20nightly/replsets_priority1.js

      Mon Oct 15 07:28:35 uncaught exception: assert.soon failed: function () {
          var ok = true;
          try {
              status = master.adminCommand({replSetGetStatus:1});
          } catch (e) {
              print(e);
              print("nreplsets_priority1.js checkPrimaryIs reconnecting");
              reconnect(master);
              status = master.adminCommand({replSetGetStatus:1});
          }
          var str = "goal: " + node.host + "==1 states: ";
          if (!status || !status.members) {
              return false;
          }
          status.members.forEach(function (m) {str += m.name + ": " + m.state + " ";if (m.name == node.host) {ok &= m.state == 1;} else {ok &= m.state != 1 || m.state == 1 && m.health == 0;}});
          print();
          print(str);
          print();
          occasionally(function () {print("\nstatus:");printjson(status);print();}, 15);
          return ok;
      }, msg:bs-osx-106-x86-64-1.local:31001==1

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            ian@mongodb.com Ian Whalen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: