Closed matentzn closed 4 years ago
@Robbie1977 and I looked a bit around this issue, but its very difficult to pinpoint. After the pipeline has run, the memory of KB hovers around the maximum possible (37GB); a second trigger of CALL ebi.spot.neo4j2owl.exportOWL()
simply crashes the database.. @Robbie1977 has now added some additional GC and OOPS parameters to the container, and we will experiment with that.
Use the backup version of the kb on a fresh container..
We need to built a restart into the pipeline.
Backup version is used after pipeline build
After a while, this shows up in log: