Provide oom_adj option for ceph-mon/osd
Bug #1428572 reported by
Peter Sabaini
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Ceph OSD Charm |
Triaged
|
Wishlist
|
Unassigned | ||
OpenStack Ceph Charm (Retired) |
Won't Fix
|
Wishlist
|
Unassigned | ||
ceph (Juju Charms Collection) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
In low-memory situations, a ceph-osd or ceph-mon could be killed by the oom killer. However this will trigger a ceph recovery, which will likely result in a memory usage spike, thus worsening the original problem. It would be good to have an option to tune ceph-osd and ceph-mon processes' oom_adj value so that they are less likely to attract the attention of the oom killer.
Changed in ceph (Juju Charms Collection): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
milestone: | none → 15.10 |
Changed in ceph (Juju Charms Collection): | |
milestone: | 15.10 → 16.04 |
Changed in ceph (Juju Charms Collection): | |
milestone: | 16.04 → 16.07 |
Changed in ceph (Juju Charms Collection): | |
milestone: | 16.07 → 16.10 |
Changed in charm-ceph: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in ceph (Juju Charms Collection): | |
status: | Triaged → Invalid |
To post a comment you must log in.
If the oom killer comes out chances are good that all bets are off. It can literally kill almost anything leaving your system in an undefined state. I would suggest that instead of trying to shield ceph from the oom killer that we just reboot the machine. I've seen the oom killer leave systems in all kinds of weird broken states that are hard to debug.