Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
3

It seems to me like these are likely reasons for your stated combination of observations: you deleted files that are still open, in such a situation the files are no longer visible in the filesystem but the space cannot be reclaimed until they are closed you may want to look at eg lsof -n | grep DEL there are a large number of files smaller than what you ...


3

Setting up container resource requests and limits is the first step towards using resources effectively in your Kubernetes cluster. After you set them, make sure you have monitoring and alerting in place to determine if you need to adapt these values or upgrade your cluster. If your container experiences memory pressure, the kernel will aggressively drop ...


3

I believe nowadays the recommended way to limit the impact of one task on others is use a cgroup to limit the memory it can use. The easiest way I found is to use systemd-run. For example, this starts ls with a ridiculously low memory limit of 1000 bytes: sudo systemd-run --uid $USER --gid $UID -p MemoryMax=1000 ls Running journalctl -f, you will see that ...


2

Disable the oom killer (vm.oom-kill = 0 in a file read by sysctl) and disable memory overcommit (vm.overcommit_memory = 2). Any process that tries to allocate more memory than available will be killed. No other process will be killed. All memory can be used; no memory is wasted. This doesn't prevent memory hogs. The memory cgroup has the memory....


2

As you saw in the article you references, the whole set of calculations around MemAvailable is built around calculating how much memory is free to use without causing any swapping. You can see in the actual patch that implemented the MemAvailable number that MemAvailable = MemFree - LowWaterMark + (PageCache - min(PageCache / 2, LowWaterMark)) This formula ...


2

You want to run an app that needs 1.5GB on a 2GB machine - that's quite a stretch as there won't be much left for the system, disk caches, other processes, etc. I wouldn't expect a great performance even if it didn't crash. Run it on t3.medium and see if it still crashes. If it does you may have a memory leak. If it doesn't it means you app simply needs ...


1

The ZFS ARC is a subject to automatic scaling in any system using ZFS. ARC limiting is only a workaround; the behavior you’re experiencing was pretty much usual for FreeBSD older than 11.x (however, I personally haven’t seen any crashes -only ineffective memory usage); after 11.0 release this behavior was massively mitigated (thus, if you’re using 10.x or ...


1

You can check cAdvisor a tool by google and it's on github


1

You can set the sysctl vm.oom_kill_allocating_task. When this is set, and a process memory request would lead to running out of memory, Linux will kill that process. From the documentation: This enables or disables killing the OOM-triggering task in out-of-memory situations. If this is set to zero, the OOM killer will scan through the entire ...


1

Ok, I had been having the same problem for a while. I found another answer that helped. Run "netstat -ano" from a Command Prompt. In my case, the response was an almost-endless list of connections all having the same number in the last column. That last column is the process id. I then used Process Explorer (add-on available free, google it) to show all ...


1

In case someone comes here for a solution, this is an update : I rolledback all the config modifications and I did a fresh reboot of the server. Since 2 months the server looks good and the problem dissapeared. Not sure what happened here ...


1

Try to find which process using your RAM with ps aux --sort -rss. Regards to server's output for free -m most of RAM got buffered/cached. Try to clear caches with these command : # free && sync && echo 3 > /proc/sys/vm/drop_caches && free


Only top voted, non community-wiki answers of a minimum length are eligible