Comments (5)
Thanks for the data.
This seems to confirm an issue that we've now also encountered (and fixing) locally.
from arangodb.
For me, it looks like that version 0.9.0
of the ArangoDB-Starter Image fixes this issue. @ewoutp thank you for the changes from yesterday.
docker stats
CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
4aafddefdd69 0.75% 185.2MiB / 11.71GiB 1.54% 1.47MB / 1.05MB 0B / 0B 32
43442af14db1 1.69% 232.3MiB / 11.71GiB 1.94% 2.41MB / 2.63MB 4.63MB / 0B 35
a3967027a134 1.55% 143.6MiB / 11.71GiB 1.20% 1.39MB / 1.02MB 360kB / 0B 33
f0031ec76d40 1.16% 123.5MiB / 11.71GiB 1.03% 1.83MB / 640kB 344kB / 0B 32
1098b8b3059a 2.57% 129.6MiB / 11.71GiB 1.08% 3.57MB / 2.72MB 28.7kB / 0B 31
7df1becf0556 0.78% 117.1MiB / 11.71GiB 0.98% 1.39MB / 425kB 0B / 0B 31
306ca83e2317 0.93% 121.7MiB / 11.71GiB 1.02% 696kB / 474kB 0B / 0B 35
a3b5b2bc8279 5.25% 129.1MiB / 11.71GiB 1.08% 3.46MB / 7.9MB 0B / 0B 36
60c8c1da5409 0.99% 121.1MiB / 11.71GiB 1.01% 699kB / 476kB 0B / 0B 35
8658c231774a 0.00% 5.508MiB / 11.71GiB 0.05% 235kB / 195kB 0B / 0B 8
7a534d44122e 0.00% 5.215MiB / 11.71GiB 0.04% 180kB / 122kB 0B / 0B 8
f2f6dee80a35 0.00% 5.176MiB / 11.71GiB 0.04% 180kB / 125kB 0B / 0B 8
from arangodb.
It is expected that a cluster uses more cpu than a single node (e.g. because of the cluster heartbeats and coordination between cluster members).
Which of the containers is using up the cpu that high?
Note that the starter launches 2 or 3 containers (dbserver, container or agent, dbserver, container).
from arangodb.
I started 3 arango_db-starter
images. With the intent, that 2 and 3 join the cluster of 1.
Some statistics about the CPU usage:
The command docker ps
shows 12 containers (3x4):
CONTAINER ID IMAGE COMMAND PORTS NAMES
6f46767cb314 arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8534->8534/tcp arango_db_staging_db3-coordinator-6ef428c5-0-192.168.0.4-8534
ecba1e0aa2e9 arangodb/arangodb:latest "/usr/sbin/arangod..." 0.0.0.0:8529->8529/tcp arango_db_staging_db1-coordinator-4fc11a17-0-192.168.0.4-8529
a09decdea150 arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8535->8535/tcp arango_db_staging_db3-dbserver-6ef428c5-0-192.168.0.4-8535
795e46c487e6 arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8539->8539/tcp arango_db_staging_db2-coordinator-b2ca2b24-0-192.168.0.4-8539
e39e4c8dc3da arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8530->8530/tcp arango_db_staging_db1-dbserver-4fc11a17-0-192.168.0.4-8530
622f67d4624d arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8536->8536/tcp arango_db_staging_db3-agent-6ef428c5-0-192.168.0.4-8536
04a02ad8f1e0 arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8540->8540/tcp arango_db_staging_db2-dbserver-b2ca2b24-0-192.168.0.4-8540
2e5cc7312396 arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8531->8531/tcp arango_db_staging_db1-agent-4fc11a17-0-192.168.0.4-8531
c6a21343ad7a arangodb/arangodb:latest "/usr/sbin/arangod..." 8529/tcp, 0.0.0.0:8541->8541/tcp arango_db_staging_db2-agent-b2ca2b24-0-192.168.0.4-8541
56cd82883124 arangodb/arangodb-starter "/app/arangodb --s..." 0.0.0.0:8528->8528/tcp arango_db_staging_db1
5735925e83c2 arangodb/arangodb-starter:latest "/app/arangodb --s..." 0.0.0.0:8533->8528/tcp arango_db_staging_db2
63f51050c3ac arangodb/arangodb-starter:latest "/app/arangodb --s..." 0.0.0.0:8538->8528/tcp arango_db_staging_db3
docker stats
CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
6f46767cb314 0.26% 168.6MiB / 9.743GiB 1.69% 1.12MB / 497kB 0B / 0B 33
ecba1e0aa2e9 0.03% 149.9MiB / 9.743GiB 1.50% 731kB / 400kB 0B / 0B 32
a09decdea150 0.30% 117.2MiB / 9.743GiB 1.18% 991kB / 283kB 0B / 0B 31
795e46c487e6 0.26% 121.7MiB / 9.743GiB 1.22% 760kB / 431kB 0B / 0B 33
e39e4c8dc3da 0.93% 125.6MiB / 9.743GiB 1.26% 1.63MB / 865kB 0B / 0B 32
622f67d4624d 1.79% 124.3MiB / 9.743GiB 1.25% 2.28MB / 5.76MB 0B / 0B 35
04a02ad8f1e0 0.38% 120.1MiB / 9.743GiB 1.20% 1.38MB / 479kB 0B / 0B 32
2e5cc7312396 0.37% 120.5MiB / 9.743GiB 1.21% 435kB / 281kB 0B / 0B 37
c6a21343ad7a 0.55% 118.4MiB / 9.743GiB 1.19% 412kB / 264kB 0B / 0B 36
56cd82883124 172.37% 4.285MiB / 9.743GiB 0.04% 70.5kB / 60.2kB 0B / 0B 11
5735925e83c2 278.58% 4.363MiB / 9.743GiB 0.04% 71.5kB / 60.4kB 0B / 0B 11
63f51050c3ac 151.62% 4.301MiB / 9.743GiB 0.04% 71.8kB / 59.8kB 0B / 0B 11
The top
command called from insead the arango_db_staging_db2
container shows:
Mem: 2875440K used, 7341116K free, 167988K shrd, 17824K buff, 1463052K cached
CPU0: 99% usr 0% sys 0% nic 0% idle 0% io 0% irq 0% sirq
CPU1: 98% usr 0% sys 0% nic 0% idle 0% io 0% irq 0% sirq
CPU2: 99% usr 0% sys 0% nic 0% idle 0% io 0% irq 0% sirq
CPU3: 97% usr 1% sys 0% nic 0% idle 0% io 0% irq 0% sirq
CPU4: 97% usr 1% sys 0% nic 1% idle 0% io 0% irq 0% sirq
CPU5: 98% usr 0% sys 0% nic 0% idle 0% io 0% irq 0% sirq
Load average: 8.52 5.72 2.82 10/869 19
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
1 0 root S 12736 0% 3 32% /app/arangodb --starter.address=192.168.0.4 --starter.join=192.168.0.4
13 0 root S 1516 0% 3 0% sh
19 13 root R 1512 0% 3 0% top
For me, this looks like it' neither the agent
nor the dbserver
nor the coordinator
have a high CPU usage. The arangodb-starter
containers produce / show this high load.
from arangodb.
Great! thx for the feedback.
from arangodb.
Related Issues (20)
- starter on windows process control HOT 1
- restart coordinator only node will get error: "data/ENGINE: no such file or directory"
- After recovery agency, the db server and coordinator meet error "ERROR [92522] {agencycomm} Cannot find an agency persisted in RAFT 8|" HOT 1
- Starter should process version control check with empty configuration
- Implement `--starter.force-minor-upgrade` option to let overcome limitations
- Single server rolling upgrade commander exits early
- --starter.port of "leader" starter not persisted across restarts
- arangodb start command bug: different results of different order in the whole command HOT 2
- arangorestore command terminated arangodb process
- Support go1.16 and Apple Silicon HOT 2
- Adjust terminology: master/slave => leader/follower
- Starter usability improvements: arangod_command.txt
- Starter usability: show arangod log errors HOT 1
- File descriptors and ulimits
- Upgrade from 3.6.5 to 3.7.11 fails. HOT 2
- Failed quick restart attempts
- Entrypoint HOT 1
- Is the starter tool in the compilation result of ArangoDB?
- Improve warning "Flag --all.xxx has been deprecated, Deprecated" HOT 1
- documentation of alert rules HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from arangodb.