Unable to initialize cursor across all shards in sharding_multiple_ns_rs.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • Environment:
      V2.0 Linux 64-bit
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      m31000| Wed Mar 28 10:26:55 [conn1] SocketException: remote: 10.110.9.236:31100 error: 9001 socket exception [0] server [10.110.9.236:31100] 
       m31000| Wed Mar 28 10:26:55 [conn1] DBClientCursor::init lazy say() failed
       m31000| Wed Mar 28 10:26:55 [conn1] DBClientCursor::init message from say() was empty
       m31000| Wed Mar 28 10:26:55 [conn1] warning: invalid result from blah-rs0/ip-10-110-9-236:31100,ip-10-110-9-236:31101,ip-10-110-9-236:31102
       m31000| Wed Mar 28 10:26:55 [conn1] DBException in process: could not initialize cursor across all shards because : error querying server: blah-rs0/ip-10-110-9-236:31100,ip-10-110-9-236:31101,ip-10-110-9-236:31102
      Wed Mar 28 10:26:55 uncaught exception: error {
      	"$err" : "could not initialize cursor across all shards because : error querying server: blah-rs0/ip-10-110-9-236:31100,ip-10-110-9-236:31101,ip-10-110-9-236:31102",
      	"code" : 14827
      }
      failed to load: /mnt/home/buildbot/slave/Linux_64bit_V2.0/mongo/jstests/slowNightly/sharding_multiple_ns_rs.js
      

      http://buildbot.mongodb.org/builders/V2.0%20Linux%2064-bit/builds/215/steps/test/logs/stdio

            Assignee:
            Unassigned
            Reporter:
            Ian Whalen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: