dbstats | golang database/sql driver wrapper | Database library

The problem here is that Db class from MongoDB Node.js driver doesn't have methods version() and hostInfo() corresponding to Mongo shell

Please consider the following alternatives depending on your needs:

1. Use Db.command

make sure, you have enabled auth in config and restart mongodb.

For more details, Please follow below link: https://docs.mongodb.com/manual/reference/configuration-options/index.html#security.authorization

It seems your /home/nim1com/SkyCrypt/credentials.json file need to be corrected ...

Looks like you're missing a session option in findOne():

Thanks ernest_k, it was careless,So this works:

Depending on the way your app is designed, data-wise, there can be several reasons for this lack of performance.

A few suggestions:

• check that you have indexes in your collections
• avoid doing aggregation in the publication process, i.e. denormalize the db, publish array of cursors instead, limit the size of the documents, etc.
• filter the useless fields in the query
• limit the amount of data to the relevant part (lazy load & paginated subscribe)
• consider global pubs/subs for the collections you use a lot, instead of reloading them too often on a route based pattern
• track small component based subs and try to put them at a higher level to avoid making for instance 30 subs instead of one

My best guess is that you probably need a mix of rationalizing the db "structure" and avoid the data aggregation as much as you can.

You may also have a misuse of the low level collection api (e.g. cursor.observe() stuff) somewhere.

So I was running into the same issue today, but ended up resolving it by installing a previous version of pymongo, e.g. pip install pymongo==3.4.0 instead of the latest version 3.7.0. There might be a bug...

I was having the same issue. The Support Department said that since I was using Mongoose, they couldn't help. However, they were kind enough to gift me 10$ in credit so I could test it out with a higher tier.

That was the issue, as soon as I upgraded to M10 tier (the next one after M0) transactions started working as intended. Your code is very similar as mine, only that I was creating one document and updating 2 others at the same time. Just like in your case, the first one went through (no matter the order) and the next just timed out with the same error.

I think, you have to make sure at first that your database connection has been established. In the provided example, you may notice db.once call which waits for open event to occur. In other words, we have a pending connection to the database running and the goal is to get notified if we connect successfully. Therefore, your connection object is still in the process of its creation, and thus undefined yet.

Try to modify your files accordingly assuming you have defined logger, config and settings appropriately:

db.js: