On 4/27/16 0:55 , David Preece wrote: > >> On 27/04/2016, at 12:48 PM, Jerry Jelinek <[email protected]> wrote: >> >> Can you provide more information about what did not work when you set the >> zone's memory cap? > > This afternoon I had an enormously overloaded but completely 'stock' Debian 8 > lx zone, running on VMWare Fusion, live-locked completely. It would ping but > was otherwise totally unresponsive. I've had the problem with two physical > machines today, too: They were both 8GB machines with the zones capped to > 4GB; with 4 and 8 physical cores; and Images were 20160330T234717Z and > 20160414T011743Z. I was running a make -j8 of mesos.
There's been a lot of focus on your memory resource cap; however, that's not the only piece of the puzzle. To me the thing that actually stands out much more is that you have said that the zone can use 16 GiB of swap. In this context, swap refers to the maximum amount of allocated anonymous virtual memory where as the max physical memory is only referring to the amount that's currently paged in. I suspect you may have overprovisioned this value based on the machine in question. I suspect that because the zone is allowed to allocate say 16 GiB of VA, even though you only have 8 GiB, that makes it very easy for it to start paging in and having things being paged out. Though as Jerry mentioned, the amount of information that we have at the moment is quite minimal, so it's rather hard to say. However, I'd note that what you see in the JPC and this are likely different and with lx, we have to honor the Linux tradition of mapping anonymous memory without a guaranteed reservation. Therefore if you're running lots of processes in parallel and exceeding your memory and swap, the offending process will die. It's not too hard to confirm that from core files. Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
