Operations that fail against a secondary in a sharded cluster may have their error message swallowed

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding F (01/29/16), Sharding 10 (02/19/16), Integration 11 (03/14/16)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Instead of getting the real error message that mongod returned propagated back to the user, you get the message "Failed to do query, no good nodes in test-rs0, last error: can't query replica set node ubuntu:10011: :: caused by :: 0 assertion src/mongo/client/dbclientcursor.cpp:420"

      Seems to be coming from checkSlaveQueryResult() calling peekError() and it not finding a $err field

        1. error_propagation.js
          0.8 kB

              Assignee:
              Adam Midvidy (Inactive)
              Reporter:
              Ricardo Lorenzo (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: