The deletion of archival descriptions with a lot of descendants is prone to web server timeouts
|Assignee:||Dan Gillean||% Done:|
|Category:||Performance / scalability|
|Target version:||Release 2.6.0|
|Google Code Legacy ID:||Tested version:||2.5, 2.6|
When a full hierarchy of descriptions is deleted from the database it has to be deleted from the bottom to the top to avoid foreign key constraint errors related to the parent-son relations. This is taking too much time in large datasets causing web server timeouts in some cases (it depends on the amount of descendants and the position in the entire archival descriptions tree). Additionally, when the timeout occurs, the process keeps running causing issues in the MySQL server.
#1 Updated by José Raddaoui Marín 3 months ago
- Status changed from In progress to Code Review
This is ready for code review in https://github.com/artefactual/atom/pull/1000.
As you can see I broke the PR and it's already merged so I'll address the feedback and merge any changes in different PRs if needed.
#3 Updated by José Raddaoui Marín about 1 month ago
- Status changed from Code Review to QA/Review
- Assignee changed from David Juhasz to Dan Gillean