lensesio / fast-data-dev

Kafka Docker for development. Kafka, Zookeeper, Schema Registry, Kafka-Connect, Landoop Tools, 20+ connectors
https://lenses.io
Apache License 2.0
2.01k stars 330 forks source link

Zookeeper using all my cpu #162

Open NadavkOptimalQ opened 3 years ago

NadavkOptimalQ commented 3 years ago

I've been running and using this docker for a while and everything worked great until today. For some reason all of my CPU is getting used by zookeeper (see in attached picture) its using 200% CPU image

I am running ubuntu 16.04 with docker version:

docker version
Client:
 Version:           19.03.6
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        369ce74a3c
 Built:             Wed Oct 14 19:00:27 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          19.03.6
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       369ce74a3c
  Built:            Wed Oct 14 16:52:50 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.3.3-0ubuntu1~18.04.2
  GitCommit:        
 runc:
  Version:          spec: 1.0.1-dev
  GitCommit:        
 docker-init:
  Version:          0.18.0
  GitCommit:        

These are the logs from the container:

You may visit http://localhost:3030 in about a minute.
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/01-zookeeper.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/02-broker.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/03-schema-registry.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/04-rest-proxy.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/05-connect-distributed.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/06-caddy.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/07-smoke-tests.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/08-logs-to-kafka.conf" during parsing
2020-10-22 12:06:06,817 INFO Included extra file "/etc/supervisord.d/99-supervisord-sample-data.conf" during parsing
2020-10-22 12:06:06,817 INFO Set uid to user 0 succeeded
2020-10-22 12:06:06,822 INFO RPC interface 'supervisor' initialized
2020-10-22 12:06:06,822 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-10-22 12:06:06,823 INFO supervisord started with pid 6
2020-10-22 12:06:07,825 INFO spawned: 'broker' with pid 178
2020-10-22 12:06:07,827 INFO spawned: 'caddy' with pid 179
2020-10-22 12:06:07,828 INFO spawned: 'connect-distributed' with pid 180
2020-10-22 12:06:07,831 INFO spawned: 'logs-to-kafka' with pid 181
2020-10-22 12:06:07,833 INFO spawned: 'rest-proxy' with pid 183
2020-10-22 12:06:07,836 INFO spawned: 'sample-data' with pid 185
2020-10-22 12:06:07,838 INFO spawned: 'schema-registry' with pid 189
2020-10-22 12:06:07,840 INFO spawned: 'smoke-tests' with pid 192
2020-10-22 12:06:07,842 INFO spawned: 'zookeeper' with pid 194
2020-10-22 12:06:08,845 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,846 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,846 INFO success: connect-distributed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,846 INFO success: logs-to-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,847 INFO success: rest-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,847 INFO success: sample-data entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,847 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,847 INFO success: smoke-tests entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-22 12:06:08,848 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Any idea what caused this and what I can do? Thank you

michaelahlers commented 3 years ago

I'm having this problem, too. All works well enough but my system heats up and drags to a crawl whenever I run this.

NadavkOptimalQ commented 3 years ago

I'm having this problem, too. All works well enough but my system heats up and drags to a crawl whenever I run this.

I solved this issue by...well... I moved to a Macbook pro

michaelahlers commented 3 years ago

Mine has an i9, so… I'm wondering how long until it starts hovering. 😉