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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.1
    • Fix Version/s: 3.2.4, 3.3.3
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Completed:
    • Sprint:
      Sharding F (01/29/16), Sharding 10 (02/19/16), Integration 11 (03/14/16)
    • Case:

      Description

      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

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-23160 error_propagation.js checks for the wrong error message.

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                4 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: