[JAVA-3892] Проблема с canonicalAddress когда соединяюсь с к кластеру Mongo Created: 20/Nov/20  Updated: 20/Nov/20  Resolved: 20/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Rakymzhan Kenzhegul Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


Attachments: Text File mongo-error.txt    

 Description   

При соединении к кластеру MongoDB version 4.4.1, получаю следующую ошибку com.mongodb.MongoSocketException: s3200: Name or service not known. 

В логах видно, что почему-то canonicalAddress отличается от hostname.

Например, я задаю hostname s3200.j, а Mongo canonicalAddress делает s3200.

Логи во вложении.



 Comments   
Comment by Jeffrey Yemin [ 20/Nov/20 ]

Hi there, thank you for reaching out. As this sounds like a support issue, I wanted to give you some resources to get this questioned answered more quickly:

  • our MongoDB support portal, located at support.mongodb.com
  • our MongoDB community portal, located here
  • If you are an Atlas customer, there is free support offered 24/7 in the lower right hand corner of the UI.

Just in case you have already opened a support case and are not receiving sufficient help, please let me know and I can facilitate escalating your issue.
Thank you!

Comment by Rakymzhan Kenzhegul [ 20/Nov/20 ]

When connecting to MongoDB (version 4.4.1) I get the error com.mongodb.MongoSocketException: s3200: Name or service not known. 

And you can see in logs that canonicalAddress differs from the hostname.

For example, I set hostname to  s3200.j but MongoDB sets canonicalAddress to s3200

Logs in the attachment.
 

Generated at Thu Feb 08 09:00:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.