innodb - Mysql replication falling behind Update_rows_log_event::ha_update_row(-1) -
i managed (with here) setup replication master server running mysql 5.6 (centos 6) slave running mariadb 10.1.22 (centos 7).
my issue this, have server exact mariadb version , specs replication not catching up, instead increasing.
when started 48000 seconds behind , dropped 46000 after few minutes. after steadily increasing. atm of writing 48k seconds
show full processlist; shows sql thread spending 8 seconds running update_rows_log_event::ha_update_row(-1) back google search cannot find means.
mariadb [(none)]> show full processlist; +-----+------------------+---------------------------------------+--------------+---------+------+------------------------------------------+-----------------------+----------+ | id | user | host | db | command | time | state | info | progress | +-----+------------------+---------------------------------------+--------------+---------+------+------------------------------------------+-----------------------+----------+ | 3 | system user | | null | connect | 3640 | queueing master event relay log | null | 0.000 | | 2 | system user | | null | connect | 5 | update_rows_log_event::ha_update_row(-1) | null | 0.000 | also caught simple update table set timestamp = now() static_ip = 'a-valid-ip' , process_id = '13217' taking 6 seconds while table has static_ip , process_id columns pk , command takes 0.078 seconds when executed directly.
contents of /etc/my.cnf
[mysqld] max_allowed_packet = 1g max_connections = 600 thread_cache_size = 16 query_cache_size = 64m tmp_table_size= 512m max_heap_table_size= 512m wait_timeout=60 #innodb settings innodb_file_per_table=1 innodb_buffer_pool_size = 25g innodb_log_file_size = 2048m innodb_flush_log_at_trx_commit = 0 innodb_file_format = barracuda innodb_flush_neighbors = 0 #log log-error =/var/log/error.log tmpdir = /dev/shm #replication slave server-id=6 slave-skip-errors=1062 my.cnf same server running ok except slave-id.
any suggestions/help on happening?
thank you.
from guys @ mariadb ha_update_rows not relevant , reason slowness dual disk failure on machine.
[root@ser3 ~]# dd if=/dev/zero of=/tmp/output conv=fdatasync bs=384k count=1k; 1024+0 records in 1024+0 records out 402653184 bytes (403 mb) copied, 43.1096 s, 9.3 mb/s this ssd.
Comments
Post a Comment