MongoDB node doesn't recover when mongo is restarted

General
1

Hello!

I'm using node-red-node-mongodb which I believe is the default mongo node. When the mongo database gets restarted for whatever reason, it doesn't recover and throws the following error repeatedly:

"MongoError: Topology was destroyed"

Restarting the flow fixes the issue. It's the same as in here:

It seems it's possible to evade the issue by messing with the mongo client configurations like "socketTimeoutMS" and "keepAlive" by what I gathered but I couldn't find how to change these configurations in the node.

Does anyone know of a workaround? Thanks in advance.

2

Hi, does anyone have at least a tip or a direction? This is a production problem for us in a covid-19 tracking application being used by the government in Brazil to help the population. If I'm asking in the wrong place or anything like that, please let me know.

Thank you

3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.