I stopped all container but one - watchtower - which is set to run at 15min intervals. time of containers which generates high cpu load this release improves overall cpu usage.
Maybe I was to hurry to report this but if we ignore the start-up. When I try to start same containers that are already downloaded cpu load increases for few seconds ( under 1 minute ) probably until containers finish loading some settingsĪfter those few seconds cpu load decreases again to 10% and stays in 10-30%Īll the tests were realised using docker compose mention earlier ( 3 containers - es - kibana - filbeat )
MAC OS DOCKER COMPOSE USE ALL CPU DOWNLOAD
When I try to start some containers with images that are not already downloaded locally the entire time ( download + build + run ) (about 10-15 minutes) cpu load increasesĪfter those 10-15 minutes everything is downloaded + started cpu decreases to 10% I've made now more tests and I've discovered following: So the high load appears only when I'm trying to start containers and after that load decreases to more than decent When I'm starting containers with docker-compose ( in my case ) for 10-15 minutes the load increases to between 100-500% and after those 10-15 minutes the load decreases back to 10% which is really great. That spike of 10-15 minutes of high CPU usage is triggered by docker-compose which creates 3 I can confirm that by default when all containers are stopped the load is small under 10% Users can in turn add propspectors to this directory and they will be dynamically loadedĮDIT: after 10-15 minutes of continuously "burning" CPU usage it seems that is eating between 8-30% CPU with 3 containers running ( kibana, Elasticsearch, filebeat ) filebeat.yml:/usr/share/filebeat/filebeat.yml #Mount the filebeat configuration so users can make edit "./kibana.yml:/usr/share/kibana/config/kibana.yml:ro" "./elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml:ro" The most common error is this: Neo4jError: connect ECONNREFUSED 172.20.0.2:7687Īt captureStacktrace (/code/node_modules/neo4j-driver/lib/v1/result.js:199:15)Īt new Result (/code/node_modules/neo4j-driver/lib/v1/result.js:65:19)Īt _newRunResult (/code/node_modules/neo4j-driver/lib/v1/transaction.js:354:10)Īt n (/code/node_modules/neo4j-driver/lib/v1/transaction.js:238:14)Īt n (/code/node_modules/neo4j-driver/lib/v1/transaction.js:104:26)Īt TransactionExecutor._safeExecuteTransactionWork (/code/node_modules/neo4j-driver/lib/v1/internal/transaction-executor.js:134:22)Īt TransactionExecutor._executeTransactionInsidePromise (/code/node_modules/neo4j-driver/lib/v1/internal/transaction-executor.js:122:32)Īt Timeout._onTimeout (/code/node_modules/neo4j-driver/lib/v1/internal/transaction-executor.js:98:18)Īt listOnTimeout (internal/timers.Image: /elasticsearch/elasticsearch:7.2.0
MAC OS DOCKER COMPOSE USE ALL CPU DRIVER
Where driver was previously initialized with const driver = neo4j.driver(neo4jUrl, (user, passwd), ) Session.writeTransaction((tx) => tx.run(query, params)) I execute queries to neo4j with: const session = ssion() docker-compose.yml up to start Docker, and my docker-compose.yml file looks like this: version: '3' I used to run Docker/docker desktop 3.1 and 10.20.2, now upgraded to 3.6.0 and 10.20.8. When it drops, I often (not always) first get an EPIPE error.
But it never works for long, before I get the errors again. The fact that this sometimes works is the baffling part. The neo4j browser interface on port 7474 is also gone, though it used to be there. Nothing in the logs, they don't seem to have crashed, they're just inaccessible. Neither neo4j nor Docker give any indication that anything is wrong. It works fine on Windows, it works fine for other people using a Macbook, and sometimes it also works for me, but then the connection mysteriously drops and I only get ECONNREFUSED errors anymore, until I restart the container. I can also run those imports manually from inside the Docker container or outside (locally). On startup, the api tries to import a lot of data into neo4j, accessing it through neo4-driver. I'm running a neo4j database as well as an node.js api in a Docker container.
0 kommentar(er)
