Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.1.25
-
Amazon AWS, CentOS 6 x86_64, Galera 3 nodes cluster
Description
This is first and one-time bug, I have "mysqlcheck --skip-write-binlog -a -A" running nightly on Galera cluster by cron, each node runs it different time. The last time this analyze or mysqld during analyze crashed, here is log from mysqld.log:
2017-07-14 13:24:50 7f649b1fa700 InnoDB: FTS Optimize Removing table doc_live_wi/#sql2-5c22-112eeb4
|
170716 5:40:19 [ERROR] 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.
|
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
|
|
We will try our best to scrape up some info that will hopefully help
|
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail.
|
|
|
Server version: 10.1.25-MariaDB
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=77
|
max_threads=3002
|
thread_count=50
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6725132 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x7f62d7e8a008
|
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 = 0x7f61bdf14140 thread_stack 0x48400
|
2017-07-16 10:25:28 140094283446016 [Note] WSREP: (01c439e4, 'tcp://0.0.0.0:4567') turning message relay requesting on, nonlive peers: tcp://10.10.1.133:4567
|
This Galera node did not failed, did not make SST, nothing, it just continue running. However I had stalled "ANALYZE NO_WRITE_TO_BINLOG TABLE `wo
rkflow_state`" statement in "Unlocking tables" state. And next day when "DROP TRIGGER" on the same table was executed - it stalls in the same "Unlocking tables" state and locked whole Galera cluster. I tried to kill the ANALYZE thread with no luck, then I tried to shutdown this Galera node also with no luck - it stalled, the last message was
2017-07-17 3:26:22 140030532045568 [Note] WSREP: killing local connection: 28899415
|
I waited almost 30 minutes, then made kill -9 to mysqld and after start this node successfully connected to Galera using IST.
Attachments
Issue Links
- relates to
-
-
- Closed
-