-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to Replica Set or Sharded Cluster #663
Comments
@jukkakilponen, thanks for reporting. Would you like to raise a PR? |
@dhmlau |
closes: loopbackio#663 Signed-off-by: jaishirole <[email protected]>
Any updates on this issue since we are also facing the same issue and we are not able to use SRV in our current deployment architecture |
@manarhusrieh My PR has been awaiting merge. @achrinza could you please confirm who would be reviewing and merging the PR? |
@jaishirole I think you will need to resolve conflicts in your PR and rebase again on the latest version |
Hi guys, |
I think the PR is close to being merged, but it needs some conflicts resolved by @jaishirole and final approval. |
It's worth mentioning that 6.1.0 do not have this issue |
closes: loopbackio#663 Signed-off-by: Manar Husrieh <[email protected]>
closes: #663 Signed-off-by: Manar Husrieh <[email protected]>
Steps to reproduce
Have a mongodb connection string with multiple hosts and ports (Replica Set or Sharded Cluster) as in https://www.mongodb.com/docs/manual/reference/connection-string/.
For example mongodb://mongos0.example.com:27017,mongos1.example.com:27017,mongos2.example.com:27017
Current Behavior
Cannot start the application. TypeError [ERR_INVALID_URL]: Invalid URL: mongodb://mongos0.example.com:27017,mongos1.example.com:27017,mongos2.example.com:27017
Expected Behavior
Should connect to database.
Additional information
Tested with 6.2.0.
The problem seems to be the use of nodejs URL to parse the connection string. The URL does not support multiple hosts with port numbers.
See whatwg/url#398.
Problem introduced in commit 1d8a84b.
Related Issues
The text was updated successfully, but these errors were encountered: