Terrakube
|
Hello occasionally I am getting this error in the executor:
I've deployed Terrakube with the standard helm chart and not changed any resource allocations. It's well within the 2GB limit set. Is there any way I tweak this? I'm not too familiar with Java.
|
Replies: 2 comments 11 replies
|
This also leaves the job in a broken state thats pending forever. Even if I cancel it any subsequent jobs are also stuck
|
|
If for some reason a job is stuck it will be cancelled after 6 hours. Other option is go to the database a change the status tu CANCELLED |
|
The strange thing here is the job is already marked as cancelled and in the DB too |
|
Could you check all the jobs for that particular workspace? Maybe some job is pending queue or running? The queue should continue if all the previous jobs are failed or completed state |
|
It looks like I will have to add cancelled state to that validation |
|
Yes I think so, changed the job state to failed and the pending one started right away, thanks :) |
|
I think you can fix that changing the resource allocation, check this: |
|
I can see at runtime it's calculated automatically. Maybe just increasing the memory overall would help, but being able to override that may be useful |
|
The container is built using the java buildpack there is a feature that automatically allocate the JVM memory based on the available resources for the pod |
|
You could do some customization using that Java tools option like in this example: https://docs.terrakube.io/getting-started/deployment/proxy-configuration |
|
Yes that looks like it could work, thank you! |
You could do some customization using that Java tools option like in this example:
https://docs.terrakube.io/getting-started/deployment/proxy-configuration