Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.6.18
-
None
-
centos7 x64
Description
Hello
After upgrading from 10.6.17 to 10.6.18 we are seeing crashes while running optimize on a specific table. Table as about 5GB and 900k records.
The optimize starts everything goes ok and after 2 minutes suddenly all connections to all databases are stuck. Processstatus reports "copy to tmp table". A few moments latter server crashes with the following:
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 = 0x0 thread_stack 0x20000
|
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x559042ea3eae]
|
/usr/sbin/mariadbd(handle_fatal_signal+0x2f7)[0x5590428f7707]
|
sigaction.c:0(__restore_rt)[0x7f173c8fa630]
|
/lib64/libc.so.6(gsignal+0x37)[0x7f173bd45387]
|
/lib64/libc.so.6(abort+0x148)[0x7f173bd46a78]
|
/usr/sbin/mariadbd(+0xe47e50)[0x559042d32e50]
|
/usr/sbin/mariadbd(+0xe01166)[0x559042cec166]
|
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x40)[0x559042e2fdd0]
|
/usr/sbin/mariadbd(_ZN5tpool4task7executeEv+0x2b)[0x559042e30d7b]
|
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x69)[0x559042e2e149]
|
/lib64/libstdc++.so.6(+0xb5330)[0x7f173c494330]
|
pthread_create.c:0(start_thread)[0x7f173c8f2ea5]
|
/lib64/libc.so.6(clone+0x6d)[0x7f173be0db0d]
|
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
|
information that should help you find out what is causing the crash.
|
Thank you