Closed glenrobson closed 4 months ago
This is likely related to https://jira.duraspace.org/browse/FCREPO-1294. We've escalated the issue (discussed it as a high priority last week) and I think we have an idea how to fix it, but no one's had the time yet to work on it. Do you have any interest in working on the Fedora 4 code base? ;)
Thanks Mike, I can't promise Ill be able to sort the issue but I can have a look around and see if there is anything I can do. Is there a writeup of how you think it can be fixed? I read the issue above and the related tech meeting notes and it looks like its been identified as a blank node issue. Are there any pointers on where I should start looking?
I was mostly kidding. I'm going to look first into whether it's the blank nodes that is causing the problem, by changing the way we migrate some information to avoid using them.
few...., wasn't sure what I was letting myself in for :-). Still happy to help with testing.
Closing stale issues and this was related to Fedora4 by Mike's comments so no longer valid
I'm trying to load an object using the migration utils which has 203 versions of RELS-EXT. Details of the migration are contained in #15. The object which caused the problems (llgc-id:3143635) was the last to be migrated and all of the other objects and datastreams were created quickly in Fedora 4.
Creating the RELS-EXT datastream versions for llgc-id:3143635 was slow (about a minute per version) to load and after loading the first 7 caused Fedora4 to throw a OutOfMemoryError. This object also has 102 versions of METS documents and the first 77 loaded quickly.
The output for the migration of this object is below:
The output from Fedora is below: