[MDEV-28735] Signal 6 after "[Note] WSREP: UP-UP trx conflict for key ..." Created: 2022-05-17  Updated: 2023-06-19  Resolved: 2023-06-19

Status: Closed
Project: MariaDB Server
Component/s: Galera, Platform FreeBSD
Affects Version/s: 10.6.8
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: Hartmut Holzgraefe
Resolution: Incomplete Votes: 1
Labels: None
Environment:

FreeBSD 13, using custom build TODO-3345; datadir on ZFS volumes

https://jira.mariadb.org/browse/TODO-3345


Issue Links:
Relates

 Description   

Two nodes failed with an assertion failure at the same time:

2022-05-15 20:51:00 9 [Note] WSREP: UP-UP trx conflict for key (2,FLAT8)e6a8a3a7 0237511a: source: 17e55081-d3ba-11ec-ae1f-031dc5dab92f
version: 5 local: 0 flags: 65 conn_id: 6342 trx_id: 228670428 tstamp: 276357303469703; state:  seqnos (l: 39052478, g: 8142481111, s:
8142480998, d: 8142480998) WS pa_range: 65535; state history: REPLICATING:0->CERTIFYING:3240 <---> source: bc319d65-d14f-11ec-a78c-a618ebfceb77
version: 5 local: 1 flags: 65 conn_id: 13905640 trx_id: 1037125527 tstamp: 347389853227489; state:  seqnos (l: 39052389, g: 8142481022, s:
8142480998, d: 8142480999) WS pa_range: 23; state history: REPLICATING:0->CERTIFYING:3240->APPLYING:1026 Assertion failed: (mode_ == m_local ||
transaction_.is_streaming()), function <unknown>, file
/tmp/workspace/Build-Package/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/wsrep-lib/include/wsrep/client_state.hpp, line 668. 220515 20:51:00
[ERROR] 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.
 
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.6.8-4-MariaDB-enterprise-log
key_buffer_size=5242880
read_buffer_size=2097152
max_used_connections=1501
max_threads=1502
thread_count=1600
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 18500018 K  bytes of memory

Both nodes did not print any backtrace unless they were submitted with truncation, checking that right now



 Comments   
Comment by Jan Lindström (Inactive) [ 2022-06-09 ]

hholzgra Based on code review UK-UK conflict comes from Galera library and it is basically certification error. I strongly suggest to use primary keys on tables. We have done tests on both normal Linux as well as FreeBSD. I can't comment on what is in ports build and how it does differ from what we provided. Based on given stack trace it does crash on lock_wait_wsrep i.e. there is long BF-BF wait scenario.

Comment by Jan Lindström (Inactive) [ 2022-06-17 ]

julien.fritsch No we do not have a way to reproduce this bug. We have tried on both galapq and FreeBSD with no luck.

Generated at Thu Feb 08 10:03:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.