Details
-
Bug
-
Status: Needs Feedback (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6.19
-
None
-
None
-
None
-
RHEL8, VMWare, 2 active nodes plus a witness in a cluster running Galera 26.4.19.
Description
Hi MariaDB support team,
Observation:
- no stack trace/coredump is produced for checking further
- no assertion error message appeared in mariadb-error.log
- sudden crash, no signal 6, signal 11 or other signals in mariadb-error.log
- sar CPU has spare capacity
- sar memory was enough and no swapping
- same version 10.6.19 executed for other similar systems (>300) but only 2 DBs w/ similar schema have this issue
Next action:
- suspect the problem is SQL / schema specific but could not pinpoint from binlog as failed SQLs are not captured in binlog
- plan to enable audit (initially for DMLs) to track the offending SQL(s), may extend to DDL or even queries later
- advise if there is better method to capture the offending SQL(s)
Thanks and best regards,
Lawrence
Attachments
Issue Links
- duplicates
-
MDEV-34683 Types mismatch when cloning items causes debug assertion
- Closed