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

chaining.js timing out on OS X 10.5 64-bit, Windows 64-bit, Linux 64-bit

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.6, 2.5.1
    • Component/s: Testing Infrastructure
    • Labels:
    • Environment:
      OS X 10.5 64-bit since #5547
      Nightly OS X 10.5 64-bit since #1355
      Windows 64-bit build 5594
      Linux 64-bit Build 5580
      Linux 64-bit Weekly Slow Tests
      V2.4 Linux 32-bit Build #134
    • Operating System:
      ALL

      Description

      Occurred on build #5547 and #5548

      http://buildbot.mongodb.org/builders/OS%20X%2010.5%2064-bit/builds/5547/steps/test_9/logs/stdio
      http://buildlogs.mongodb.org/OS%20X%2010.5%2064-bit/builds/5547/test/replica%20sets/chaining.js

      ReplSetTest awaitReplication: checking secondaries against timestamp Timestamp(1372900459, 3)
      ReplSetTest awaitReplication: checking secondary #1: bs-osx-106-x86-64-2.10gen.cc:31001
      ReplSetTest awaitReplication: secondary #1, bs-osx-106-x86-64-2.10gen.cc:31001, is synced
      ReplSetTest awaitReplication: checking secondary #2: bs-osx-106-x86-64-2.10gen.cc:31002
      ReplSetTest awaitReplication: timestamp for secondary #2, bs-osx-106-x86-64-2.10gen.cc:31002, is Timestamp(1372900459, 2) but latest is Timestamp(1372900459, 3)
      ReplSetTest awaitReplication: last oplog entry (of 4) for secondary #2, bs-osx-106-x86-64-2.10gen.cc:31002, is {  "ts" : Timestamp(1372900459, 2),  "h" : NumberLong("-4910588404677798978"),  "v" : 2,  "op" : "i",  "ns" : "chaining.foo",  "o" : {  "_id" : ObjectId("51d4cc6bd1e446f928d201a9"),  "a" : 1 } }
      ReplSetTest awaitReplication: secondary #2, bs-osx-106-x86-64-2.10gen.cc:31002, is NOT synced
      2013-07-03 21:14:51 EDT	
       m31000| Wed Jul  3 21:14:50.554 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31005: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31005
       m31000| Wed Jul  3 21:14:50.554 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31005: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31005
       m31000| Wed Jul  3 21:14:50.555 [rsHealthPoll] replset info bs-osx-106-x86-64-2.10gen.cc:31005 heartbeat failed, retrying
       m31000| Wed Jul  3 21:14:50.556 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31005: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31005
       m31000| Wed Jul  3 21:14:50.556 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31005: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31005
       m31000| Wed Jul  3 21:14:50.557 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31005: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31005
       m31002| Wed Jul  3 21:14:50.964 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31010: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31010
       m31002| Wed Jul  3 21:14:50.965 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31010: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31010
       m31002| Wed Jul  3 21:14:50.966 [rsHealthPoll] replset info bs-osx-106-x86-64-2.10gen.cc:31010 heartbeat failed, retrying
       m31002| Wed Jul  3 21:14:50.966 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31010: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31010
       m31002| Wed Jul  3 21:14:50.967 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31010: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31010
       m31002| Wed Jul  3 21:14:50.968 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31010: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31010
       m31002| Wed Jul  3 21:14:50.994 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31009: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31009
       m31002| Wed Jul  3 21:14:50.995 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31009: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31009
       m31002| Wed Jul  3 21:14:50.996 [rsHealthPoll] replset info bs-osx-106-x86-64-2.10gen.cc:31009 heartbeat failed, retrying
       m31002| Wed Jul  3 21:14:50.997 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31009: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31009
       m31002| Wed Jul  3 21:14:50.997 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31009: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31009
       m31002| Wed Jul  3 21:14:50.998 [rsHealthPoll] couldn't connect to bs-osx-106-x86-64-2.10gen.cc:31009: couldn't connect to server bs-osx-106-x86-64-2.10gen.cc:31009
      Wed Jul  3 21:14:51.366 [awaiting replication] timed out after 30000ms ( 16 tries ) at src/mongo/shell/utils.js:492
      failed to load: /data/buildslaves/OS_X_105_64bit/mongo/jstests/replsets/chaining.js

      I cannot reproduce this on Linux 64-bit DEBUG. On the OS X builder it did not occur before build #5547 (#5546 was green).

      Recommend trying to repro on another OS X box, and if successful, bisect between c11ea25c522c (good) and master (bad).

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: