Limit JVM for Jenkins
Bug #1498440 reported by
Sergii Golovatiuk
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
Low
|
Fuel CI | ||
| Mitaka |
Won't Fix
|
Low
|
Fuel CI | ||
| Newton |
Won't Fix
|
Low
|
Fuel CI | ||
Bug Description
Debugging one environment I realized we have memory overcommitment. If you run
sgolovatiuk@XXX:~$ ps axo vsize,rss,comm | sort -nr | head -n 10
36144152 189368 java
20413060 15474828 qemu-system-x86
20174116 6700848 qemu-system-x86
20072664 15538572 qemu-system-x86
19384344 5521988 qemu-system-x86
18627984 15479232 qemu-system-x86
18458900 3829572 qemu-system-x86
18214948 3758492 qemu-system-x86
11258144 6191416 qemu-system-x86
1573088 6136 nscd
This means we allow jenkins to allocate too much RAM even if it won't consume it ... I propose to add -Xmx<memory> to java process to limit java to 2-4Gb. In this case atop will show more accurate result in vmcom/vmlim
| Changed in fuel: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Fuel DevOps (fuel-devops) |
| milestone: | none → 8.0 |
| status: | New → Confirmed |
| description: | updated |
| tags: | added: area-devops |
Revision history for this message
| Igor Shishkin (teran) wrote | #1 |
| Changed in fuel: | |
| assignee: | Fuel DevOps (fuel-devops) → Fuel CI (fuel-ci) |
| Changed in fuel: | |
| importance: | Medium → Low |
| tags: |
added: area-ci removed: area-devops |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
Revision history for this message
| Ivan (iremizov) wrote | #2 |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
Unfortunately it's impossible to do from our side but it's possible to set in Jenkins node configuration.
Assigning to CI team to perform a task.