[JAVA-3581] Problem with Canonical Service Name while connecting to Atlas with Private Link Created: 07/Jan/20  Updated: 22/Sep/21  Resolved: 08/Jan/20

Status: Closed
Project: Java Driver
Component/s: Cluster Management
Affects Version/s: 3.12.0
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Vadzim Lauresh Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File MongoAtlas.log    
Issue Links:
Duplicate
duplicates SERVER-45396 fix the "me" field in isMaster respon... Closed
Related

 Description   

Can I kindly ask someone to check  Monglo Atlas behavior for VPC Endpoint (Private link connection). Looks like Java mongo driver 3.12 isn't prepared for resolving mongo cluster with VPC Endpoint (Private endpoint).
Java mongo driver states that
"Canonical address cluster0-shard-00-00-v7y4t.mongodb.net:27017 does not match server address. Removing pl-0-eu-west-1-v7y4t.mongodb.net:1 from client view of cluster" (please see logs attached), which seems to be wrong assumption for Private Endpoint.
My connection string is:
mongodb+srv://vlauresh:<pass>@cluster0-pl-0-v7y4t.mongodb.net/test?ssl=true&authSource=admin&retryWrites=true&w=majority



 Comments   
Comment by Vadzim Lauresh [ 08/Jan/20 ]

Sorry for off topic as it is related to support&testing procedures:
I think that new should be treated differently - I had first contact with the support  on 26-Dec-19 and by 27 it was clear that it is PrivateLink related issue, unfortunately there were no help, but marketing stuff.
I hope that conclusions will be drawn.
Thank again, information about an issue help me to plan my work till the issue will be resolved 

Comment by Jeffrey Yemin [ 08/Jan/20 ]

Hi vadzim.lauresh@suredatum.com,

FYI, the issue with Private Link was only diagnosed yesterday afternoon.  Until then it was not a known issue.  

Comment by Vadzim Lauresh [ 08/Jan/20 ]

Thanks a lot, really appreciate your help. 
Hope it will be fixed soon.

Comment by Jeffrey Yemin [ 08/Jan/20 ]

Yes, I believe it is unusable for replica sets.

If you want to get this working ASAPI, you could fork the driver and see if removing this conditional works around the issue. That is not a good long term solution though, as the conditional is necessary for other use cases.  See DRIVERS-230 for details.

Comment by Vadzim Lauresh [ 08/Jan/20 ]

So Private Endpoint feature with java driver  is currently unusable?
Can it be hackfixed on java driver side?

Comment by Jeffrey Yemin [ 08/Jan/20 ]

Thanks for reporting this. Through a separate report of the same issue, we've determined that this is a server bug (SERVER-45396), so closing this as a duplicate.

Please watch SERVER-45396 for updates.

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