Node crash after DROP DATABASE
Description
Environment
Activity
Nour September 6, 2024 at 1:12 PM
Hi
Sorry for taking that match time to get back here,
unfortunately because of those issues we had to stop using the cluster (right now we are on single node master/slave) so no way for us to reproduce or get more info, since our issue is only in prod not in staging or dev.
We are planing to bring cluster with 3 nodes in the coming weeks and sure I will ping here if I get more details/info
TY again
Aaditya Dubey September 6, 2024 at 12:10 PM
Hi
We still haven't heard any news from you. So, I assume the issue no longer persists and will close the ticket. If you disagree, reply and create a follow-up with a new Jira report.
Aaditya Dubey August 6, 2024 at 11:20 AM
Hi
Please let us know if the issue exists with the latest version of PXC.
Kamil Holubicki June 24, 2024 at 10:18 AM
Hi , Have you maybe tried the newest 8.0.36 version?
Nour February 28, 2024 at 6:30 PM
sure, we are on AlmaLinux release 9.3
db running on the official docker image percona/percona-xtradb-cluster:8.0.33
here is the my.cnf
Details
Details
Assignee
Reporter
NourNeeds QA
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
We are experiencing a node crash after DROP DATABASE with this crash log,
2024-02-16T13:54:21.410220Z 84222382 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2024-02-19T10:01:30.949666Z 0 [Warning] [MY-000000] [Galera] last inactive check more than PT1.5S (3evs.inactive_check_period) ago (PT1.60456S), skipping check
2024-02-19T10:02:04.429792Z 0 [Warning] [MY-000000] [Galera] last inactive check more than PT1.5S (3evs.inactive_check_period) ago (PT1.71076S), skipping check
2024-02-19T13:14:03.434996Z 91848441 [Note] [MY-000000] [WSREP] MDL conflict db= table= ticket=1 solved by abort
2024-02-19T13:14:03.435345Z 91925881 [Note] [MY-000000] [WSREP] MDL conflict db= table= ticket=10 solved by abort
2024-02-19T14:04:21.466262Z 92219986 [Note] [MY-000000] [WSREP] Initiating SST cancellation
2024-02-19T14:04:21Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=1794b64918b6420e8430816186ecb12644628136
Server Version: 8.0.33-25.1 Percona XtraDB Cluster (GPL), Release rel25, Revision 0c56202, WSREP version 26.1.4.3, wsrep_26.1.4.3
Thread pointer: 0x7f8350b52180
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 = 7f813a74ec10 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x22683b1]
/usr/sbin/mysqld(print_fatal_signal(int)+0x39f) [0x127293f]
/usr/sbin/mysqld(handle_fatal_signal+0xd8) [0x1272a28]
/lib64/libpthread.so.0(+0x12cf0) [0x7f8b3dfd7cf0]
/usr/sbin/mysqld(wsrep_handle_mdl_conflict(MDL_context const*, MDL_ticket*, MDL_key const*)+0x81) [0x1290171]
/usr/sbin/mysqld(MDL_lock::can_grant_lock(enum_mdl_type, MDL_context const*) const+0x8de) [0xf57dfe]
/usr/sbin/mysqld(MDL_context::try_acquire_lock_impl(MDL_request*, MDL_ticket**)+0x54d) [0xf5bc5d]
/usr/sbin/mysqld(MDL_context::acquire_lock(MDL_request*, unsigned long)+0xae) [0xf5c09e]
/usr/sbin/mysqld(MDL_context::acquire_locks(I_P_List<MDL_request, I_P_List_adapter<MDL_request, &MDL_request::next_in_list, &MDL_request::prev_in_list>, I_P_List_counter, I_P_List_no_push_back<MDL_request> >, unsigned long)+0xf6) [0xf5d6c6]
/usr/sbin/mysqld(lock_table_names(THD, Table_ref*, Table_ref*, unsigned long, unsigned int, Prealloced_array<MDL_request*, 1ul>)+0x8c8) [0x1044de8]
/usr/sbin/mysqld(mysql_rm_db(THD, MYSQL_LEX_CSTRING const&, bool)+0x691) [0x1080441]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x4660) [0x10e3e40]
/usr/sbin/mysqld(dispatch_sql_command(THD*, Parser_state*, bool)+0x61e) [0x10e60ee]
/usr/sbin/mysqld() [0x10e6735]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x3966) [0x10eaed6]
/usr/sbin/mysqld(do_command(THD*)+0x204) [0x10eb584]
/usr/sbin/mysqld() [0x12614b8]
/usr/sbin/mysqld() [0x271eb19]
/lib64/libpthread.so.0(+0x81ca) [0x7f8b3dfcd1ca]
/lib64/libc.so.6(clone+0x43) [0x7f8b3c371e73]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f8350e9fdc0): DROP DATABASE dbName
Connection ID (thread ID): 92219986
Status: NOT_KILLED