Questions about mongodb transactions

I know that mongodb 4.0 + has begun to support transactions. But now the company requires meteor for development, while meteor uses version 3.6.x of mongodb. Transactions cannot be natively supported. I have also looked up a lot of practices for implementing mongodb transactions on the Internet. The more recommended practice is the secondary commit method, that is, using a collection to store transactions. Give each transaction a state, such as initialization, waiting, completion, etc. I wonder, if there is a sudden power outage on the server or something. For example, the transaction is now only updated to wait. Then the next time I restart the server, this data is also waiting. Does this mean that I have to check the transaction set regularly to find out the transaction whose state exception is to be rolled back or undone? For example, check the transaction set every 30 minutes? Check the transaction set once a day?

to be clear, how can I find an exception in this process during this step-by-step operation?

May.01,2021
Menu