{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/4455","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/4455/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/4455/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/4455/events","html_url":"https://github.com/kubernetes/kubernetes/issues/4455","id":57791514,"number":4455,"title":"Influxdb is using 1 core on 4 core cluster","user":{"login":"fgrzadkowski","id":10820726,"avatar_url":"https://avatars.githubusercontent.com/u/10820726?v=3","gravatar_id":"","url":"https://api.github.com/users/fgrzadkowski","html_url":"https://github.com/fgrzadkowski","followers_url":"https://api.github.com/users/fgrzadkowski/followers","following_url":"https://api.github.com/users/fgrzadkowski/following{/other_user}","gists_url":"https://api.github.com/users/fgrzadkowski/gists{/gist_id}","starred_url":"https://api.github.com/users/fgrzadkowski/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgrzadkowski/subscriptions","organizations_url":"https://api.github.com/users/fgrzadkowski/orgs","repos_url":"https://api.github.com/users/fgrzadkowski/repos","events_url":"https://api.github.com/users/fgrzadkowski/events{/privacy}","received_events_url":"https://api.github.com/users/fgrzadkowski/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/area/monitoring","name":"area/monitoring","color":"fef2c0"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/priority/P3","name":"priority/P3","color":"fef2c0"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/node","name":"team/node","color":"d2b48c"}],"state":"open","locked":false,"assignee":{"login":"vishh","id":7063592,"avatar_url":"https://avatars.githubusercontent.com/u/7063592?v=3","gravatar_id":"","url":"https://api.github.com/users/vishh","html_url":"https://github.com/vishh","followers_url":"https://api.github.com/users/vishh/followers","following_url":"https://api.github.com/users/vishh/following{/other_user}","gists_url":"https://api.github.com/users/vishh/gists{/gist_id}","starred_url":"https://api.github.com/users/vishh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vishh/subscriptions","organizations_url":"https://api.github.com/users/vishh/orgs","repos_url":"https://api.github.com/users/vishh/repos","events_url":"https://api.github.com/users/vishh/events{/privacy}","received_events_url":"https://api.github.com/users/vishh/received_events","type":"User","site_admin":false},"milestone":null,"comments":9,"created_at":"2015-02-16T11:09:44Z","updated_at":"2015-10-14T21:59:50Z","closed_at":null,"body":"For a clean, empty cluster with 4 1-core nodes, 1 core (i.e. 1 machine cpu-wise) is used by influxdb. This is really high! It is particularly bad if a container is scheduled on that node."},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/148215374","html_url":"https://github.com/kubernetes/kubernetes/issues/4455#issuecomment-148215374","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/4455","id":148215374,"user":{"login":"vishh","id":7063592,"avatar_url":"https://avatars.githubusercontent.com/u/7063592?v=3","gravatar_id":"","url":"https://api.github.com/users/vishh","html_url":"https://github.com/vishh","followers_url":"https://api.github.com/users/vishh/followers","following_url":"https://api.github.com/users/vishh/following{/other_user}","gists_url":"https://api.github.com/users/vishh/gists{/gist_id}","starred_url":"https://api.github.com/users/vishh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vishh/subscriptions","organizations_url":"https://api.github.com/users/vishh/orgs","repos_url":"https://api.github.com/users/vishh/repos","events_url":"https://api.github.com/users/vishh/events{/privacy}","received_events_url":"https://api.github.com/users/vishh/received_events","type":"User","site_admin":false},"created_at":"2015-10-14T21:59:50Z","updated_at":"2015-10-14T21:59:50Z","body":"On Wed, Oct 14, 2015 at 8:02 AM, Ravindar Reddy <notifications@github.com>\nwrote:\n\n> Seems like pods are killed and only some restarted on machine where\n> influxDB running. See StackOverflow here\n> <http://stackoverflow.com/questions/33068639/kubernetes-pods-some-die-after-running-for-a-day>\n>\n> I noticed that these pods are on machine where *influxdb* is running\n> (this process has high cpu usage). *There were 5 pods before and only 2\n> new ones with replication controller came back now*\n> (fluentd-elasticsearch, spark-worker-controller) other 3 pods - influxdb\n> and 2 directly run ones did not\n>\nPods are not immortal. Unless you set an appropriate restart policy, pods\nwill disappear.\nReplication Controllers are meant to handle this situation. When a new pod\nis created to replace a dead pod, the new pod can either be scheduled on\nthe same node or on a different node.\n\n> I can disable monitoring however would be good to know what happened on\n> this node. Where would I look for this info in logs?\n>\nYou can set env `ENABLE_CLUSTER_MONITORING=none` while running\n `kube-up.sh` to disable monitoring.\nInstead on an existing cluster, you can try running the following commands\non the master:\n`kubectl delete -f /etc/kubernetes/addons/cluster_monitoring/influxdb/`\n`mv /etc/kubernetes/addons/cluster_monitoring /tmp`\n\n\n\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/kubernetes/kubernetes/issues/4455#issuecomment-148077482>\n> .\n>\n"}}