Replies: 1 comment
-
|
I guess migration should be faster =) But yes, we need a way to monitor and change timeouts. Default timeout can be changed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Deployer Version
v7.5.12
Target OS
Debian 6.1.76-1
Which PHP version are you using?
PHP 8.3
Content of deploy.php or deploy.yaml
When running the magento:db:upgrade step, the command will be killed if it takes more than 5 minutes, due to the default timeout being applied with the
run()invocation: https://github.com/deployphp/deployer/blob/master/recipe/magento2.php#L307-L314We find that DB upgrades can often take a long time (especially on production databases) if for example updating DB schema for tables with many rows (customers, orders).
I propose that this task specifically disables the timeout entirely, because killing this process halfway through can make it very complex to recover from (i.e. if a module's updates are partially processed)
Steps to reproduce
Run deployment with schema updates to a table with millions of rows would potentially trigger this
Beta Was this translation helpful? Give feedback.
All reactions