[MDEV-24306] src/replicator_smm.cpp:1054(galera::ReplicatorSMM::replay_trx(galera::TrxHandleMaster&, galera::TrxHandleLock&, void*)) Created: 2020-11-30 Updated: 2021-05-23 Resolved: 2021-05-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.5.6 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Allen Lee (Inactive) | Assignee: | Seppo Jaakola |
| Resolution: | Incomplete | Votes: | 1 |
| Labels: | galera_4, need_feedback | ||
| Environment: |
RedHat Enterprise Linux, On-Premise, Virtualized |
||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Description |
|
User is hitting Signal 11 repeatedly(114 times) after applying SSL(TDE). Here is the stacktrace.
This is 5 ndoe galara cluster and some galera config as below.
|
| Comments |
| Comment by Roger Eisentrager [ 2021-02-22 ] |
|
CS0168361 - I did let the client know to upgrade and retest, java errors thrown still (from the mariaDB connector), and disconnects after that. New log of these errors in the CS ticket I linked. Client really needs to advice here as moving them off of Galera, might not be a viable solution. I am still unsure of this an issue with the connector, mariaDB server, or galera or a combination here. This is impacting the client's rollout to production. |
| Comment by Roger Eisentrager [ 2021-02-22 ] |
|
Caused by: java.sql.SQLException: Connection reset |
| Comment by Roger Eisentrager [ 2021-02-22 ] |
|
1789 error code refers back to: The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. — 1789 HY000 ER_MASTER_HAS_PURGED_REQUIRED_GTIDS ----> not sure if that helps at all. |
| Comment by Seppo Jaakola [ 2021-03-31 ] |
|
I tried some test scenarios on 10.5.8 cluster using conflicting XA load, and could reproduce a crash fairly easily. However, the stack trace is not identical with the the one posted in this jira tracker: 210331 15:58:06 [ERROR] mysqld got signal 11 ; 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 Server version: 10.5.7-MariaDB-log Thread pointer: 0x7fbb00000c58 Trying to get some variables. I suspect there are more crashing issues with different XA test load scenarios. As the cluster configuration appears to at least prepare the cluster for XA transaction usage, I assume the the crash with this tracker is also due to XA transactions run on the cluster. Later 10.5 versions reject XA transactions in cluster, but 10.5.8 still allows this harmful cluster usage. |