This topic was automatically generated from Slack. You can find the original thread here.
Hi, I have a nodejs step in my workflow which uses mysqldump package to create a backup of a small DB and dump it in a file ‘/tmp/dump.sql’. While creating the workflow, I defined the timeout as 300 seconds and memory as 1.5 GB. However while testing and with deployed version, it runs only for around 18-61 seconds and then returns this error that code was still running. How to have a code step which runs longer than 60 seconds?
Hi , the warning shows there might be because you have not close the connection to MySQL. The action will is still completed, but the resource might not be cleanup
I would suggest you to check the mysqldump library for the function to close mysql connection
Hi , I don’t find any such function in mysqldump package. Besides that, the package core contributor mentioned in one of the closed issues that it automatically closes the connection. So probably that isn’t the root cause.
I ran this similar code in my local node and it generates a 450 MB file for my db and takes around 32 seconds so I don’t particularly understand the reason of it running only for 18 seconds for instance.
The warning there might be a false positive. Could you try to execute the action again, then get the file from tmp dir?
I ran this similar code in my local node and it generates a 450 MB file for my db and takes around 32 seconds
The different might be because of the network connection
