Project Config Apply Command never finish
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Description
The ./craft project-config/apply command takes very long. We have about 64000 rows in structureelements table. Using show processlist; and console.log file I see that the most time takes to execute update SQL statements for structureelements table. It takes more than 12 hours and then it breaks. It never actually finish. The process never comes to an end. This blocks the whole update each time we release a new version to production.
And the one other instance has about 443000 rows in structureelements table.
Additional info
- Craft version: 3.5.17.1
- PHP version: 7.2.34
- Database driver & version: MySQL 5.5.5 MariaDB 10.1.37
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ./craft project-config/apply command and reproduce the long-running update against the structureelements table. Inspect show processlist; output and the console.log file while it runs, focusing on the update SQL statements reported there. Done means the command completes successfully for the reported table sizes without breaking the release update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, php
- Domain
- backend, databases, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100