crash when start group replication
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Expired
|
Undecided
|
Unassigned |
Bug Description
data dir are created by oracle mysql 5.7. percona server can start successfully. But crashes when start group replication.
version: Percona-
os: Centos 6.8 2.6.32-
error log:
2017-07-
2017-07-
2017-07-
2017-07-
e58b03-
,10.215.
eplication_
10:02:02 UTC - mysqld got signal 11 ;
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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=4001
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f5c9440e000
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 0x30000
/opt/percona-
/opt/percona-
/lib64/
/opt/percona-
/opt/mysql-
/opt/mysql-
/opt/mysql-
/opt/percona-
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 7
Status: NOT_KILLED
Thank you for the report.
Please describe step-by-step your actions which you did when enabled group replication.
For example:
- stopped mysqld
- added options X, Y, Z (specify which) to the configuraiton file
- started mysqld
- got crash immediately
Please also provide configuration file you use.