> So when I run out of shm in Kubernetes because of the 64MB limit, what is actually causing it to run out?
on (postgres) docker it is a frequent problem and documented .. and the result is a simple ERROR ... :(
"Also note that the default
/dev/shm size for containers is 64MB. If the shared memory is exhausted you will encounter ERROR: could not resize shared memory segment . . . : No space left on device. You will want to pass --shm-size=256MB for example to docker run, or alternatively in docker-compose"best,
Imre
Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx> ezt írta (időpont: 2020. márc. 5., Cs, 15:43):
What is POSIX shared memory used for anymore? Shared buffers now defaults to mmap, right? So when I run out of shm in Kubernetes because of the 64MB limit, what is actually causing it to run out?
(I know about creating the memory-based volume and mounting it at /dev/shm, and have implemented that workaround. Still want to know what is causing this memory use.)
--
Scott Ribe
scott_ribe@xxxxxxxxxxxxxxxx
https://www.linkedin.com/in/scottribe/
