Comment 2 for bug 1428572
Revision history for this message
| James Troup (elmo) wrote Re: [Bug 1428572] Re: Provide oom_adj option for ceph-mon/osd | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Chris Holcombe <email address hidden> writes:
> 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.
Sorry but this makes no sense. In the Canonical Cloud Reference
Architecture, ceph will often be running with a bunch of eminently
killable processes (e.g. user KVM instances) and it makes a ton of
sense to have the OOM killer go after them before ceph. Saying "just
never run out of memory" isn't realistic IMO.
--
James