[SERVER-45396] fix the "me" field in isMaster responses when using splithorizon Created: 07/Jan/20  Updated: 29/Oct/23  Resolved: 08/Jan/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.17, 4.2.3, 4.3.3, 4.0.15

Type: Bug Priority: Critical - P2
Reporter: Mira Carey Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by JAVA-3581 Problem with Canonical Service Name w... Closed
Problem/Incident
Related
Backwards Compatibility: Minor Change
Operating System: ALL
Backport Requested:
v4.2, v4.0, v3.6
Sprint: Repl 2020-01-13
Participants:
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.



 Comments   
Comment by Githook User [ 09/Jan/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-45396 Fix the 'me' field in isMaster responses when using splithorizon

(cherry picked from commit a1a1e4f0c14ab71a5fc8bc7913af25571089b65f)
Branch: v4.2
https://github.com/mongodb/mongo/commit/681bdb25525951fa298d339dd4b2ac50c95b05e8

Comment by Githook User [ 09/Jan/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-45396 Fix the 'me' field in isMaster responses when using splithorizon

(cherry picked from commit a1a1e4f0c14ab71a5fc8bc7913af25571089b65f)
Branch: v4.0
https://github.com/mongodb/mongo/commit/2c9bd38f5c9476f470d83c7452fcf8b62f63bf19

Comment by Githook User [ 09/Jan/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-45396 Fix the 'me' field in isMaster responses when using splithorizon

(cherry picked from commit a1a1e4f0c14ab71a5fc8bc7913af25571089b65f)
Branch: v3.6
https://github.com/mongodb/mongo/commit/b94da86ea3f85d4ba97ed14b0cef97d3df241902

Comment by Githook User [ 08/Jan/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-45396 Fix the 'me' field in isMaster responses when using splithorizon
Branch: master
https://github.com/mongodb/mongo/commit/a1a1e4f0c14ab71a5fc8bc7913af25571089b65f

Comment by Vadzim Lauresh [ 08/Jan/20 ]

I see you working hard on this, Thanks!

Comment by Danny Hatcher (Inactive) [ 08/Jan/20 ]

vadzim.lauresh@suredatum.com, this bug makes the Atlas Private Link feature inoperable for users utilizing a subset of drivers. We just became aware of this issue yesterday (Jan 07 2020) and are actively working to resolve it as soon as possible. Please watch this tickets for updates.

Comment by Vadzim Lauresh [ 08/Jan/20 ]

As far as I understand this issue makes Atlas Private Link feature unusable.
Can anyone confirm?
Upd:
I had very pleasant but not fruitful discussion with 1st line of Atlas support, that try hard to sell me advanced support to identify a problem. While paid support is totally OK, it is not good to sell it for known issues.
Can I please ask someone to add a note to documentation as well as to 1st line support scripts.
It's also will be convenient to put "Beta" label for new services.

Generated at Thu Feb 08 05:08:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.