Bug #84792 | Idle GR Cluster: Member CPU hog | ||
---|---|---|---|
Submitted: | 2 Feb 2017 12:49 | Modified: | 3 May 2017 13:18 |
Reporter: | Kenny Gryp | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Group Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.17 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[2 Feb 2017 12:49]
Kenny Gryp
[2 Feb 2017 12:50]
Kenny Gryp
gdb
Attachment: 84792_gdb.txt (text/plain), 50.39 KiB.
[2 Feb 2017 12:50]
Kenny Gryp
perf
Attachment: 84792_perf.txt (text/plain), 3.25 KiB.
[2 Feb 2017 13:11]
Kenny Gryp
I was able to trace it down to: my mysql got killed (OOM, see #84785), and then mysql started again with: [mysqld] symbolic-links=0 log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid server_id=2 gtid_mode=ON enforce_gtid_consistency=ON master_info_repository=TABLE relay_log_info_repository=TABLE relay-log=gr-2-relay-bin binlog_checksum=NONE log_slave_updates=ON log_bin=binlog binlog_format=ROW transaction_write_set_extraction=XXHASH64 group_replication_group_name="da7aba5e-dead-da7a-ba55-da7aba5e57ab" group_replication_start_on_boot=on super_read_only=on group_replication_local_address= "gr-2:24901" group_replication_group_seeds= "gr-1:24901,gr-2:24901,gr-3:24901" group_replication_bootstrap_group= off Note that super_read_only=on breaks group replication from starting. (#84733) But somehow mysql got stuck. I do not have the CPU problems every time I start mysql. The node must be in some kind of state before it happens
[6 Mar 2017 12:48]
MySQL Verification Team
Hi, I'm having issues reproducing this! Can you share your full config? Are you using bare metal or VM for reproducing this? all best Bogdan
[6 Mar 2017 14:21]
Kenny Gryp
See my last comment, it contains more information on how to reproduce it and includes my configuration. I did this test on VMs with low amount of RAM (as you need to get MySQL OOM first to reproduce this)
[6 Mar 2017 14:54]
MySQL Verification Team
Hi Kenny, I hoped there's more and that you "just sent parts of config" :( as I can't reproduce this .. I easily get OOM but mysql starts after it ?! .. tried few times (>5) Now, I have to ask, what binary are you using? Might be related. Do you have some statistics of "what % of starts go into high cpu usage"? Is mysql completely "stuck" (eating cpu, not responding), or is responsive, just eating cpu? thanks Bogdan
[7 Apr 2017 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[18 Apr 2017 18:49]
Kenny Gryp
$ rpm -qa | grep mysql mysql-community-common-5.7.17-1.el7.x86_64 mysql-community-libs-compat-5.7.17-1.el7.x86_64 mysql-community-libs-5.7.17-1.el7.x86_64 mysql-community-server-5.7.17-1.el7.x86_64 mysql57-community-release-el7-9.noarch mysql-community-client-5.7.17-1.el7.x86_64 [vagrant@gr-2 ~]$ mpstat 1 Linux 3.10.0-514.2.2.el7.x86_64 (gr-2) 04/18/2017 _x86_64_ (1 CPU) 06:49:12 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle 06:49:13 PM all 5.56 0.00 76.67 1.11 0.00 12.22 0.00 0.00 0.00 4.44 06:49:14 PM all 6.59 0.00 79.12 0.00 0.00 10.99 0.00 0.00 0.00 3.30 06:49:15 PM all 4.55 0.00 80.68 0.00 0.00 10.23 0.00 0.00 0.00 4.55 06:49:16 PM all 4.21 0.00 81.05 1.05 0.00 10.53 0.00 0.00 0.00 3.16 06:49:17 PM all 4.35 0.00 78.26 0.00 0.00 15.22 0.00 0.00 0.00 2.17 ^C Average: all 5.04 0.00 79.17 0.44 0.00 11.84 0.00 0.00 0.00 3.51 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2778 mysql 20 0 1195028 56592 560 S 64.0 23.4 24:28.72 mysqld This is running on a VM.
[3 May 2017 13:18]
MySQL Verification Team
Hi, I still can't reproduce this. Used few different VM's, low RAM, your config.. as I said, OOM is easy to get but I don't get the bug (cpu load and process stuck). How easily you can reproduce this?