MySQL Forums
Forum List  »  InnoDB

about master-slave replication crash
Posted by: derek fu
Date: February 15, 2019 03:07AM

1.The master was tested using sysbench stress, the test scripts used for the master stress tests is the oltp_write_only.lua
2.The slave was tested using sysbench stress, the test scripts used for the master stress tests is the oltp_read_only.lua

but, slave restart!!

2019-02-15T07:57:10.566034Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2019-02-15 15:57:10 0x7fc7b1811700 InnoDB: Assertion failure in thread 140495653246720 in file line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
07:57:10 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2171036 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000

Options: ReplyQuote

Written By
about master-slave replication crash
February 15, 2019 03:07AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.