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

fix the "me" field in isMaster responses when using splithorizon

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.17, 4.2.3, 4.3.3, 4.0.15
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0, v3.6
    • Sprint:
      Repl 2020-01-13
    • Case:

      Description

      When returning an ismaster response based on the non-default split horizon (see PM-1289), we update the 'primary', 'hosts', 'arbiters', and 'passives' fields of the ismaster response, but not the 'me' field.

      This is inconsistently enforced across drivers, and prevents those that do enforce it to be unable to connect to split horizon deployments.

      Given the few internal dependencies on the field, it makes the most sense to update "me" as well when generating split horizon responses, as this will allow existing drivers to smoothly access the split horizon functionality.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                21 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: