The mongo instance going down is because of the too many update/insert calls from the fork flow. This is an issue from mongo server, i have noticed this in import export flow as well. The db instance is cannot handle these and hence it is going down and hence the Appsmith instance becomes irresponsive for that period. We can suggest the user to export and import via file for large apps.
I personally don't see any ROI on spending time and fixing the fork flow when we have an alternative. Plus the effort in maintaining this in the future.
I am thinking to remove the logic of fork flow and use import export flow itself under the hood. This saves us so much time. We don't have to spend time on fixing two different flow which pretty much solves a similar use case. The experience for end user will be the same but the infra of import export will be used for Forking as well. This is what i am thinking now. Let me know if you think otherwise.
The mongo instance going down is because of the too many update/insert calls from the fork flow. This is an issue from mongo server, i have noticed this in import export flow as well. The db instance is cannot handle these and hence it is going down and hence the Appsmith instance becomes irresponsive for that period. We can suggest the user to export and import via file for large apps. I personally don't see any ROI on spending time and fixing the fork flow when we have an alternative. Plus the effort in maintaining this in the future. I am thinking to remove the logic of fork flow and use import export flow itself under the hood. This saves us so much time. We don't have to spend time on fixing two different flow which pretty much solves a similar use case. The experience for end user will be the same but the infra of import export will be used for Forking as well. This is what i am thinking now. Let me know if you think otherwise.
Slack Message