{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/13885","labels_url":"https://api.github.com/repos/docker/docker/issues/13885/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/13885/comments","events_url":"https://api.github.com/repos/docker/docker/issues/13885/events","html_url":"https://github.com/docker/docker/issues/13885","id":87342643,"number":13885,"title":"Docker Daemon Hangs under load","user":{"login":"mjsalinger","id":2452620,"avatar_url":"https://avatars.githubusercontent.com/u/2452620?v=3","gravatar_id":"","url":"https://api.github.com/users/mjsalinger","html_url":"https://github.com/mjsalinger","followers_url":"https://api.github.com/users/mjsalinger/followers","following_url":"https://api.github.com/users/mjsalinger/following{/other_user}","gists_url":"https://api.github.com/users/mjsalinger/gists{/gist_id}","starred_url":"https://api.github.com/users/mjsalinger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjsalinger/subscriptions","organizations_url":"https://api.github.com/users/mjsalinger/orgs","repos_url":"https://api.github.com/users/mjsalinger/repos","events_url":"https://api.github.com/users/mjsalinger/events{/privacy}","received_events_url":"https://api.github.com/users/mjsalinger/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":39,"created_at":"2015-06-11T13:15:09Z","updated_at":"2015-09-20T10:18:02Z","closed_at":null,"body":"Docker Daemon hangs under heavy load.  Scenario is starting/stopping/killing/removing many containers/second - high utilization.  Containers contain one port, and are run without logging and in detached mode.  The container receives an incoming TCP connection, does some work, sends a response, and then exits.  An outside process cleans up by killing/removing and starting a new container.\r\n\r\nI cannot get docker info from an actual hung instance, as once it is hung I can't get docker to run without a reboot.  The below info is from one of the instances that has had the problem after a reboot.\r\n\r\nWe also have instances where something completely locks up and the instance cannot even be ssh'd into.  This usually happens sometime after the docker lockup occurs.  \r\n\r\nDocker Info\r\n\r\nContainers: 8\r\nImages: 65\r\nStorage Driver: overlay\r\n Backing Filesystem: extfs\r\nExecution Driver: native-0.2\r\nKernel Version: 3.18.0-031800-generic\r\nOperating System: Ubuntu 14.04.2 LTS\r\nCPUs: 2\r\nTotal Memory: 3.675 GiB\r\nName: <hidden>\r\nID: FAEG:2BHA:XBTO:CNKH:3RCA:GV3Z:UWIB:76QS:6JAG:SVCE:67LH:KZBP\r\nWARNING: No swap limit support\r\n\r\nDocker Version\r\n\r\nClient version: 1.6.0\r\nClient API version: 1.18\r\nGo version (client): go1.4.2\r\nGit commit (client): 4749651\r\nOS/Arch (client): linux/amd64\r\nServer version: 1.6.0\r\nServer API version: 1.18\r\nGo version (server): go1.4.2\r\nGit commit (server): 4749651\r\nOS/Arch (server): linux/amd64\r\n\r\nuname -a\r\nLinux <hidden> 3.18.0-031800-generic #201412071935 SMP Mon Dec 8 00:36:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux\r\n\r\nulimit -a\r\ncore file size          (blocks, -c) 0\r\ndata seg size           (kbytes, -d) unlimited\r\nscheduling priority             (-e) 0\r\nfile size               (blocks, -f) unlimited\r\npending signals                 (-i) 14972\r\nmax locked memory       (kbytes, -l) 64\r\nmax memory size         (kbytes, -m) unlimited\r\nopen files                      (-n) 1024\r\npipe size            (512 bytes, -p) 8\r\nPOSIX message queues     (bytes, -q) 819200\r\nreal-time priority              (-r) 0\r\nstack size              (kbytes, -s) 8192\r\ncpu time               (seconds, -t) unlimited\r\nmax user processes              (-u) 14972\r\nvirtual memory          (kbytes, -v) unlimited\r\nfile locks                      (-x) unlimited\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/141773230","html_url":"https://github.com/docker/docker/issues/13885#issuecomment-141773230","issue_url":"https://api.github.com/repos/docker/docker/issues/13885","id":141773230,"user":{"login":"filex","id":505666,"avatar_url":"https://avatars.githubusercontent.com/u/505666?v=3","gravatar_id":"","url":"https://api.github.com/users/filex","html_url":"https://github.com/filex","followers_url":"https://api.github.com/users/filex/followers","following_url":"https://api.github.com/users/filex/following{/other_user}","gists_url":"https://api.github.com/users/filex/gists{/gist_id}","starred_url":"https://api.github.com/users/filex/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/filex/subscriptions","organizations_url":"https://api.github.com/users/filex/orgs","repos_url":"https://api.github.com/users/filex/repos","events_url":"https://api.github.com/users/filex/events{/privacy}","received_events_url":"https://api.github.com/users/filex/received_events","type":"User","site_admin":false},"created_at":"2015-09-20T10:18:02Z","updated_at":"2015-09-20T10:18:02Z","body":"in my case, it was only a hand full of containers being started simultaneously (maybe 3-5). but all of them receive a large input stream through STDIN (of docker run), which may have put extra stress on the daemon."}}