I have a system with a custom entity that gets imported from a remote system.
The aliases are generated based on the locally imported entities.
From time to time it's needed to make a refresh on the whole set of data, meaning delete all + update all.
When the command is executed against a set of ~90k such entities, the process fails with the out of memory PHP error during the delete phase (with drush pathauto:aliases-delete canonical_entities:TYPE --purge).
The issue is that once the error is experienced, the DB transaction is rolled back and the data is not deleted. So it is essentially preventing the completion of the whole operation.
In comparison, the bulk generation is using constant memory for it's work and it is not experiencing the same memory issues.
All the 90K aliases were generated with running a single command.
Discussion, patch, etc.
New option on the drush interface (maybe).
None expected.
None expected.
None expected.
Needs review
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
It would be better, I think, to break the list of deletions into manageable chunks of 100 or so, rather than doing one at a time.
Something like this:
public function deleteMultiple($pids) {
foreach (array_chunk($pids, 100) as $chunk) {
$this->entityTypeManager->getStorage('path_alias')->delete($this->entityTypeManager->getStorage('path_alias')->loadMultiple($chunk));
}
}