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

Replset metadata is not attached to command response on the exception path

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Both ConfigServerMetadata and ReplSetMetadata are added to a command response in Command::run on the normal path:

      https://github.com/mongodb/mongo/blob/ee5fbdd8540d93d2e0d6fa19ba9a5595bb1829cb/src/mongo/db/dbcommands.cpp#L1463-L1480

      but the ReplSetMetadata is not added on the exception path (though ConfigServerMetadata is):

      https://github.com/mongodb/mongo/blob/ee5fbdd8540d93d2e0d6fa19ba9a5595bb1829cb/src/mongo/db/dbcommands.cpp#L1324-L1342

      (Since the config server opTime from a config itself is reported as part of ReplSetMetadata, the ReplSetMetadata should always be returned.)

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: