search

brooklyncentral / clocker

Apache Brooklyn cloud native infrastructure blueprints
Apache License 2.0
426 stars 66 forks source link

Memory Issues with long running Clocker instance #195

Open Graeme-Miller opened 8 years ago

Graeme-Miller commented 8 years ago

Fix memory issues with having long running Clocker instances Add soak testing to ensure that issues like this are automatically picked up

ahgittin commented 8 years ago

using 1.1.0-PREVIEW.20150917 have observed the following error on a clocker after running for many weeks

Cannot start container 6a9e2e1c4be191a8ae98de933ca6cc89275a01908ed955861f71f27d72c26e9a: iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 32877 -j DNAT --to-destination 172.17.0.29:8443 ! -i docker0: (fork/exec /sbin/iptables: cannot allocate memory)

the docker host seems to have a memory leak? i think this is docker 1.7.1.

it worked fine for the first few weeks, there was nothing different in the blueprints i tried.