Updated to latest stable release and again. After some days I noticed high CPU and i/o. Looks like java and mysql (rancher internal) process are cause it.
Maybe triggered by a failed stack deployment (error in compose file, deleted and deployed again).
There are just few stacks (minimal load / activity!!!) active and I disabled all to test it.
Only Rancher internal processes still running. Single Host Environment. RancherOS latest stable.
17468 17465 root S 4672m 116% 0% java -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Xms128m -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/lib/cattle/logs -Dlogback.bootstrap.level=WARN -cp /usr/share/
17492 17466 102 S 1335m 33% 0% /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/log/mysql/error.log --pid-file=/var/run/mysqld/mysqld.pid --socket=/v
1606 1399 root S 974m 24% 0% dockerd --group docker --host unix:///var/run/docker.sock --log-opt max-file=2 --log-opt max-size=25m
3730 3682 root S 834m 21% 0% plugin-manager --metadata-url http://169.254.169.250/2016-07-29
9340 1861 root S 268m 7% 0% /var/lib/cattle/pyagent/agent
18586 17468 root S 203m 5% 0% websocket-proxy
4592 3827 root S 202m 5% 0% healthcheck --metadata-address 169.254.169.250
961 1 root S 125m 3% 0% container-crontab
7 2 root SW 0 0% 0% [rcu_sched]
4875 4814 root S 1178m 29% 0% charon --debug-dmn 1 --debug-mgr 1 --debug-ike 1 --debug-chd 1 --debug-cfg 1 --debug-knl 1 --debug-net 1 --debug-asn 1 --debug-tnc 1 --debug-imc 1 --debug-imv 1 --debug-pts 1 --debug-tls 1 --
1 0 root S 875m 22% 0% system-docker daemon --pidfile /var/run/system-docker.pid --storage-driver overlay --config-file /etc/docker/system-docker.json --userland-proxy=false --graph /var/lib/system-docker --host un
Anyone have this problem too?
Which logs are needed to check it?
If it’s Rancher 1.x related. Will it be fixed with Rancher 2.0?