You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2019/11/26 05:06:23 UTC
[GitHub] [camel-k] davsclaus opened a new issue #1092: Configure memory
resource requests on builder pods
davsclaus opened a new issue #1092: Configure memory resource requests on builder pods
URL: https://github.com/apache/camel-k/issues/1092
If you have set a memory limit range on a namespace, such as
```
davsclaus:/workspace/camel-k/examples (master)/$ k describe LimitRange mem-limit-range
Name: mem-limit-range
Namespace: default
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio
---- -------- --- --- --------------- ------------- -----------------------
Container memory - - 25Mi 100Mi -
```
And then for example run a kamel integration where a new build is needed, then the builder pod runs out of memory.
```
│Status: │
│ Base Image: fabric8/s2i-java:3.0-java8 │
│ Duration: 2.142086252s │
│ Error: failure while determining classpath: signal: killed │
│ Failure: │
│ Reason: failure while determining classpath: signal: killed │
│ Recovery: │
│ Attempt: 5 │
│ Attempt Max: 5 │
│ Attempt Time: 2019-11-25T17:09:23Z │
│ Time: 2019-11-25T17:07:06Z │
│ Image: fabric8/s2i-java:3.0-java8 │
│ Phase: Error │
│ Started At: 2019-11-25T17:09:25Z │
│Events: <none>
```
So we should set some reasonable memory requests for the builder pods so they wont run out of memory, as they are Java Maven builds then they take up a good portion of memory.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services