[SERVER-24211] Addition of oom killed processes to the system logs tab Created: 07/Mar/16  Updated: 20/Nov/16  Resolved: 09/Jun/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.2.8, 3.3.9

Type: New Feature Priority: Major - P3
Reporter: Mira Carey Assignee: Jonathan Abrahams
Resolution: Done Votes: 3
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-26349 Support running dmesg -T on platforms... Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: TIG 16 (06/24/16)
Participants:

 Description   

It'd be helpful when diagnosing out of memory errors to see which pids were killed by the oom killer on linux.

I believe something like:

dmesg | grep 'Out of memory: Kill process'

would work for detecting an oom kill, althought it would be useful to have the whole oom-killer log output. See: Understanding the Linux oom-killer's logs on stack overflow for what I'm talking about.



 Comments   
Comment by Githook User [ 21/Jun/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-24211 Add OOM killed process messages to system log

(cherry picked from commit 5e26352a654193b3d323b8cb1bac54d41ea03765)
Branch: v3.2
https://github.com/mongodb/mongo/commit/9756d828821e0fdeb9d58e9b993639148d07ba1a

Comment by Githook User [ 09/Jun/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-24211 Add OOM killed process messages to system log
Branch: master
https://github.com/mongodb/mongo/commit/5e26352a654193b3d323b8cb1bac54d41ea03765

Comment by Kamran K. [ 19/May/16 ]

ian.whalen, yes, we can do that.

Comment by Ian Whalen (Inactive) [ 19/May/16 ]

Awesome. kamran.khan would your team own updating the yml?

Comment by Michael O'Brien [ 19/May/16 ]

ian.whalen I'm working on EVG-904 right now, which blocks this ticket, but should be resolved very soon. After that is done, this ticket could be resolved with a trivial addition to the server's etc/evergreen.yml file. Since that's a server repo change, we should probably move this ticket to SERVER?

Comment by Ian Whalen (Inactive) [ 19/May/16 ]

What are the chances of accelerating this to next iteration? The world of build barons would be so happy if that was possible.

Generated at Thu Feb 08 04:05:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.