Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
During batch processing, we should give better context for where we are the process:
- Show the number of migrations and where we are there (migration X of Y).
- Show the one it's doing now rather than the last one completed. Requires a bit of looking ahead.
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedThis would be helpful. I'm testing with a "real" dataset today and I have 61,000 url_aliases. Initially I thought I was stalled at 28% but as it turns out that it is just running through the insane number of aliases for this site.
It seems like I'm getting about 1000 aliases per minute, which means that it is likely going to be "stuck" at 28% for a little over an hour. There could be a performance issue here, but in any case, things are working.
Comment #2
anavarreI'm testing the Migration API with a large dataset as well and have to query the DB quite often to determine if the migration is still running or not. For a migration process that can take hours to complete (url aliases, users, nodes...), I'd indeed be super useful to have some visual progress showing where we are with the migration, at least periodically.
Comment #3
anavarreHere are some numbers for the migration I've played with:
Worked as a charm but took ages to complete always.
Comment #4
mikeryanWith #2535458: Dispatch events at key points during migration, we'll be able to track the number of items imported on each batch and output feedback as we go along.
Comment #5
mikeryanSome of this work was added in the core patch #2281691: User interface for migration-based upgrades. It'll be a while before that is refined and committed, so we should get those improvements in here where they'll be visible to people doing migrations today.
Comment #7
mikeryan(oops, wrong issue)
Comment #8
mikeryan