|
In 2.7 we did change the shell to print stack traces upon all exceptions, mostly as an internal debugging aid for our unit tests.
|
|
You are correct, there is no difference in 2.6.4, or even 2.4. The resulting assert just looks different in the shell:
2.4.11:
Mon Sep 29 09:27:50.005 Error: error doing query: failed at src/mongo/shell/collection.js:53
|
failed to load: /tmp/repl.js
|
2.6.4:
2014-09-29T09:26:51.049-0400 Error: error doing query: failed at src/mongo/shell/query.js:
|
81
|
failed to load: /tmp/repl.js
|
2.7.6
2014-09-29T09:25:31.349-0400 I QUERY Error: error doing query: failed
|
at DBQuery._exec (src/mongo/shell/query.js:83:36)
|
at DBQuery.hasNext (src/mongo/shell/query.js:114:10)
|
at DBCollection.findOne (src/mongo/shell/collection.js:185:19)
|
at DB.runCommand (src/mongo/shell/db.js:58:41)
|
at Mongo.adminCommand (src/mongo/shell/mongo.js:52:34)
|
at /tmp/repl.js:8:9 at src/mongo/shell/query.js:83
|
failed to load: /tmp/repl.js
|
|
|
Can you attach a server log from a 2.6.4 run? It's unlikely the shell has changed in 2.7 so I am guessing it's something different server side.
|
|
It looks like everything is working as designed. Since your new configuration causes the primary to immediately step down, it closes the connection with your driver (the shell). Subsequently, the shell reports a query failure due to the disconnected socket.
|
|
Log from scenario attached
|
|
jonathan.abrahams ramon.fernandez Can you post the command error text from the server log?
|
Generated at Thu Feb 08 03:37:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.