[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: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v4.2, v4.0, v3.6
|
||||||||||||||||||||||||
| Sprint: | Repl 2020-01-13 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||
| 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: (cherry picked from commit a1a1e4f0c14ab71a5fc8bc7913af25571089b65f) |
| Comment by Githook User [ 09/Jan/20 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: (cherry picked from commit a1a1e4f0c14ab71a5fc8bc7913af25571089b65f) |
| Comment by Githook User [ 09/Jan/20 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: (cherry picked from commit a1a1e4f0c14ab71a5fc8bc7913af25571089b65f) |
| Comment by Githook User [ 08/Jan/20 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: |
| 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. |