[FOLIO-3374] Okapi heap size for platform-complete "Check Platform Dependencies" Created: 21/Dec/21 Updated: 15/Feb/22 Resolved: 15/Feb/22 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | Continuous Integration |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Julian Ladisch | Assignee: | John Malconian |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 133 |
| Development Team: | FOLIO DevOps |
| Description |
|
Build pipeline for platform-complete fails in the "Check Platform Dependencies" stage: POST http://172.17.0.2:9130/_/proxy/pull/modules HTTP/1.1 400 Bad Request vary: origin Content-Type: text/plain content-length: 15 Java heap space Starting Okapi with more heap size (at least 1400M) fixes this, for example
docker run -d -e JAVA_OPTS="-Xms3000M -Xmx3000M" folioorg/okapi:4.11.1 dev
|
| Comments |
| Comment by John Malconian [ 15/Feb/22 ] |
|
This was all due to the size of the folio-registry when all module descriptors were pulled to a local instance of Okapi. This should no longer be an issue since the registry has been pruned of about half of its MDs and is now pruned regularly. |