Closed (fixed)
Project:
Reference to EntityReference Field Migration
Version:
7.x-2.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2013 at 14:34 UTC
Updated:
7 Jul 2013 at 19:40 UTC
I try to migrate a big site, and get: Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 31 bytes) in on my localhost. It means, 2GB memory is not enough.
The batch process does everything in one step. (table creation, get all values, insert all values) I think, it should be limited. e.g. one batch steps select/insert 100 data.
Comments
Comment #1
btmash commentedVery interesting. I hadn't thought of it. I **thought** I was moving X number of items at a time but I suppose something like this would be possible. Let me think about how to split this up some more.
Comment #2
btmash commentedAlso...to get more info, did you do this via the web ui or via drush? If not via drush, would you be able to see if you still run into the issue?
Comment #3
btmash commentedI'm making this a 2.x issue. It will be broken into 4 steps - create temp table, move data to temp table, create field (and field instances), and move data back to field. My understanding is that batches should run in order so I'm hoping the above is feasible. I'll be testing this out to make sure that is the case. But please let me know if that is *not* the case so I can figure out an alternative approach.
Comment #4
btmash commentedThis has now been committed to the 2.x branch of the module - I have done testing locally and it all seems to work (though ... I have taken whatever minimal views conversion I was doing so that would need to be done manually unless someone wants to provide patches). But please test it out and let me know if it works and I'll push out the 2.x release for folks to use.
Comment #5
btmash commentedHad not heard back on this issue - I'm marking it as fixed. Please reopen or create a new issue if this comes up again.