-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrator stalls at a certain record number #740
Comments
I identified and fixed two problems: problem 1sorting of lineages wasn't using an index efficiently - that caused mongo to run out of memory for sorting and throw:
The solution is to create an index.
problem 2The migrator stopped on certain lineages and eventually the JVM run out of memory. |
|
and another one occurs often:
|
problem 3
This was cause but non-standard data source (Cobol) with missing data source URI. Unfortunately the URI is required in Spline 0.4+. I solved the problem by assigning artificial URI to all Cobol operations in the mongo database.
|
problem 4
This seems to be a problem or bug directly in ArangoDB. I created a ticket for it: |
it doesn't seem to require any Spline code change so far. The only remaining issue seems to be caused by the size of the lineage document. We don't see any feasible workaround so far and are rather waiting for the aforementioned Arrangodb issue resolution. To proceed with the migration we could either:
|
problem 4 According to Arango team this is not a bug, but simply ArangoDB limitation. It doesn't support more than 63 levels of nesting.
|
So I think we can close it then. There is nothing we can do about it in Spline 0.5. |
The text was updated successfully, but these errors were encountered: