Using CosmosDB instead of MongoDB cause Error

jnahlovsky commented 4 years ago

Hi, is there any chance to get CosmosDB working under Waterline ORM and sails-mongo adapter? I just tried to only change the connection string with provided one from MS Azure pointing to CosmosDB instance, but some error shows up. Thanks for any information.

{"message":"A hook (orm`) failed to load!","level":"error","timestamp":"2020-03-27T15:34:04.327Z"} {"level":"error","message":"Could not tear down the ORM hook. Error details:","timestamp":"2020-03-27T15:34:04.329Z"} error: error: Error: Consistency violation: Unexpected error creating db connection manager:


ImplementationError: Internal error occurred while running `createManager`.  Got non-Error: { MongoError: connection 0 to mal-ms-tmdb.documents.azure.com:10255 timed out
    at Function.MongoError.create (/Users/jn/Work/MALL/messaging/mg-ms-tmbe/node_modules/mongodb-core/lib/error.js:29:11)
    at Socket.<anonymous> (/Users/jn/Work/MALL/messaging/mg-ms-tmbe/node_modules/mongodb-core/lib/connection/connection.js:188:20)
    at Object.onceWrapper (events.js:273:13)
    at Socket.emit (events.js:182:13)
    at Socket.EventEmitter.emit (domain.js:442:20)
    at Socket._onTimeout (net.js:449:8)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
  name: 'MongoError',
  message:
   'connection 0 to mal-ms-tmdb.documents.azure.com:10255 timed out' }`

sailsbot commented 4 years ago

@VonSandberg Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
make sure you've provided clear instructions on how to reproduce the bug from a clean install.
double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
read the code of conduct.
if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.

jnahlovsky commented 4 years ago

If it will be necessary to provide further info (system, versions, etc.), just let me know. Peace

johnabrams7 commented 4 years ago

@VonSandberg Are you entering your DB credentials from the command-line or similar? Sure, more version info could help: what versions of Sails, sails-mongo, and CosmosDB?

jnahlovsky commented 4 years ago

Here is more info (and sorry for the delay).

connection string I used mongodb://<USER>:<PWD>@my-project.documents.azure.com:10255/db-name?ssl=true&replicaSet=globaldb

sails: 1.2.4 sails-mongo: 1.0.1 mongodb: 2.2.25

Azure's CosmoDB was 3.6 I think (their latest supported version of MongoDB).

It is possible that I just missed something and somebody already figure that out.

a1dxn commented 4 years ago

Hi @VonSandberg @johnabrams7,

I'm a newbie to sails.js and cosmosDB and I encountered this error myself... Luckily from ruffling through the sails-mongo code and reading up on the cosmosDB and mongoDB driver docs I've solved it. Hopefully this can solve your issue too as it looks to be the same!

Cosmos DB requires authentication and secure communication via TLS, and the connection string cosmosDB provides is in the format mongodb://username:password@host:port/[database]?ssl=true&replicaSet=globaldb

So I initially setup my configuration as default : { adapter: 'sails-mongo', url: 'the one used above with my info' } Didn't work :(

I could access my db using 3T, so I knew that the string worked, and the error which sails gave me of connection 0 to XXX timed out meant that the problem stemmed from the connection being used by sails... I then found this issue logged elsewhere here, heavily meantioning the SSL statement, made me think about those added url queries... After looking into the sails-mongo code, I saw a file called config-whitelist.constant.js and it had options matching ones listed here in the mongoDB driver documentation including SSL and replicaSet - both of which are included in the url that cosmosDB provided...

TL;DR

I updated my datastore configuration to: default: { adapter : 'sails-mongo', url : 'mongodb://username:password@host:port', database : 'database-name', ssl : true, replicaSet : 'globaldb', autoReconnect : true, } And it worked! Hooray! Fingers crossed this may solve your issue too 👍

Aidan

balderdashy / sails

Using CosmosDB instead of MongoDB cause Error #6964

TL;DR