similar to: OOM and Swappiness

On 09/16/2015 09:11 AM, Callum Scott wrote: > It is running a little > tight on memory and so there have been a couple of events where the > OOM_killer has been invoked and killed off MySQL, which you would expect. One thing that should be noted is that regardless of swappiness, overcommit might be an issue. If a single process is using most of the memory in a system, and attempts to

Gordon Messmer wrote: > On 09/16/2015 09:11 AM, Callum Scott wrote: >> It is running a little >> tight on memory and so there have been a couple of events where the >> OOM_killer has been invoked and killed off MySQL, which you would >> expect. > > One thing that should be noted is that regardless of swappiness, > overcommit might be an issue. If a single

Hi, I'm looking for a way to prevent qemu processes on a libvirt host to use swap unless there is no physical memory free but apparently this is not as easy as I'd hoped it would be. This is on a CentOS 7 system. At first I tried setting /proc/sys/vm/swappiness to 1 (apparently setting it to 0 now means even the OOM killer takes precedence over swapping:

Hai, How is the swappiness set? cat /proc/sys/vm/swappiness Its probely set to 60, i suggest, lower it to 10 or 20. That wil help keeping the samba processes out of swap. I've see more programs gettting OOM Killed due too out of swap. echo 10 > /proc/sys/vm/swappiness Stop and start samba Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

Am 05.06.2015 um 17:40 schrieb Greg Lindahl: > On Fri, Jun 05, 2015 at 12:29:04PM +0200, Markus "Shorty" Uckelmann wrote: > >> How can I further debug this >> problem and find out what's the culprit? > > It's working as designed. Sadly. It is just my first time I see this behaviour to this extent/on so many servers. So you can say that I'm kind of a

Hi all, This might not be CentOS related at all. Sorry about that. I have lots of C6 & C7 machines in use and all of them have the default swappiness of 60. The problem now is that a lot of those machines do swap although there is no memory pressure. I'm now thinking about lowering swappiness to 1. But I'd still like to find out why this happens. The only common thing between all

Am 05.06.2015 um 00:23 schrieb Dennis Jacobfeuerborn: > If I'd have to venture a guess then I'd say there are memory pages that > are never touched by any processes and as a result the algorithm has > decided that it's more effective to swap out these pages to disk and use > the freed ram for the page-cache. That's my guess too. [...] > impact. If however these

I think I wrote not very clearly. I say ''swap in domU will save in case lag or little mistake with balloon''. If course, there is no any kind of ballooning for dom0. Right now we running pretty much VMs for our cloud services and we use heavy memory management (it grabs and gives memory with lag less then second depends on usage in customers VM). And we have some statistics

Am 05.06.2015 um 23:32 schrieb Gordon Messmer: >>> Those two things can't really both be true. If the pages >>> swapped out are unused, then the application won't suffer as a >>> result. >> >> Why not? If you have an application which sees action only every >> 12 to 24 hours,I think this can happen. > > Well, that's not

Hi, I'm trying to compile vmkit but am running into some problems. I followed the instructions at http://vmkit.llvm.org/get_started.html and checked out llvm and clang from svn, compiled them no problem and the same with classpath 0.97.2. I then checked out vmkit from svn and tried to build it. All these are located at /home/callum/vmkit/{llvm,classpath-0.97.2,vmkit}. I used this to

Under both XEN 3.0.4 (2.6.16.33) and XEN 3.1 (2.6.18), I can make the OOM killer appear in dom0 of my server by doing heavy I/O from within a VM. If I start 5 VMs on the same server, each VM doing constant I/O over its boot disk (read/write a 2GB file), after about 30 minutes the OOM killer appears in dom0 and starts killing processes. This was observed using 256MB in dom0. If I bump the memory in

Hi, We upgraded a legacy (NT4) domain from 3.6 series to 4.8 and then 4.9.4 samba version (using sernet subscription packages / debian stable) The setup is composed of 4 DCs with each 2 CPU/16GB RAM. We currently have ~700 user accounts / ~600 computers / ~150 groups Our mail setup, SSO, ... query the 4 DCs constantly. Every 5 to 10 days the RAM consumption and CPU usage (due to kswapd)

On Wed, 2015-09-16 at 13:36 -0400, m.roth at 5-cent.us wrote: > Excerpt on heavy-duty servers. We're certainly not going to allocate > hundreds of gigs, or a terabyte or so, for swap. (Yes, we do have servers > with that kind of RAM, and that's not counting the small SGI > supercomputer....) Do you really run Centos on the SGI ? -- Regards, Paul. England, EU.

I have continous oom&panic situation unresolved. I am not sure system fills up all the ram (36GB). Why this system triggered this oom situation? Is it about some other memory? highmem? lowmem? stack size? Best Regards, Kernel 3.10.24 Dec 27 09:19:05 2013 kernel: : [277622.359064] squid invoked oom-killer: gfp_mask=0x42d0, order=3, oom_score_adj=0 Dec 27 09:19:05 2013 kernel: :

Am 05.06.2015 um 18:33 schrieb Gordon Messmer: > On 06/05/2015 03:29 AM, Markus "Shorty" Uckelmann wrote: >> some (probably unused) parts are swapped out. But, some of >> those parts are the salt-minion, php-fpm or mysqld. All services which >> are important for us and which suffer badly from being swapped out. > > Those two things can't really both be

On 06/05/2015 12:09 PM, Markus "Shorty" Uckelmann wrote: > Am 05.06.2015 um 18:33 schrieb Gordon Messmer: >> On 06/05/2015 03:29 AM, Markus "Shorty" Uckelmann wrote: >>> some (probably unused) parts are swapped out. But, some of >>> those parts are the salt-minion, php-fpm or mysqld. All services which >>> are important for us and which

Hi all, Please find below a complete transcript of the emails between debian/kernel-mm mailing lists. I've had a response back from someone on the deb mailing list stating: ==================================== The bug seems to be that sshd does not reset the OOM adjustment before running the login shell (or other program). Therefore, please report a bug against openssh-server.

On Sun, Oct 01, 2017 at 02:44:34PM +0900, Tetsuo Handa wrote: > Tetsuo Handa wrote: > > Michael S. Tsirkin wrote: > > > On Mon, Sep 11, 2017 at 07:27:19PM +0900, Tetsuo Handa wrote: > > > > Hello. > > > > > > > > I noticed that virtio_balloon is using register_oom_notifier() and > > > > leak_balloon() from virtballoon_oom_notify()

On 04.06.2015 22:18, Markus "Shorty" Uckelmann wrote: > Hi all, > > This might not be CentOS related at all. Sorry about that. > > I have lots of C6 & C7 machines in use and all of them have the default > swappiness of 60. The problem now is that a lot of those machines do > swap although there is no memory pressure. I'm now thinking about > lowering

Hey guys and gals, Yesterday I had one of my scientists kill one of my servers when his program ran amok and gobbled up all the memory, or forked too many processes, or I'm just not exactly sure what to be honest. Is there something I can run manually in cron to look for rampant programs and kill them? I know that may be hard to discern but I could also include a list if "known