Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL)
Description
As discussed with Elkin. This (seemingly invalid) error is often seen during test runs:
|
10.8.0 347f6d01e3b570dce49aa1ab42cb83021905a14d (Optimized) |
2022-01-18 23:23:40 4 [Note] BINLOG_BASE64_EVENT: Rolling back unfinished transaction (no COMMIT or ROLLBACK in relay log). A probable cause is that the master died while writing the transaction to its binary log, thus rolled back too. Internal MariaDB error code: 0
|
However, no replication is active, it is a single server, a single SQL thread, and only a simple testcase is needed to produce either this message and/or a crash on debug:
CREATE TABLE t (c CHAR(1)); |
XA START 'a'; |
SELECT dt DIV 1 AS f,id FROM t GROUP BY f; |
BINLOG ' O1ZVRw8BAAAAZgAAAGoAAAAAAAQANS4xLjIzLXJjLWRlYnVnLWxvZwAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAA7VlVHEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC '; |
CREATE TABLE t (c INT KEY,c2 CHAR(1),c3 DATE); |
XA START 'b'; |
SELECT INTc,INTc2,CHARc,CHARc2,CHARc3 FROM t WHERE id=0; |
BINLOG ' SOgWTg8CAAAAbgAAAHIAAAAAAAQANS42LjMtbTUtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAABI6BZOEzgNAAgAEgAEBAQEEgAAVgAEGggAAAAICAgCAAAAAAVAYI8='; |
Optimized may see the message only, and debug the message and crash. The crash is after the message:
|
10.8.0 347f6d01e3b570dce49aa1ab42cb83021905a14d (Debug) |
2022-01-18 23:23:36 4 [Note] BINLOG_BASE64_EVENT: Rolling back unfinished transaction (no COMMIT or ROLLBACK in relay log). A probable cause is that the master died while writing the transaction to its binary log, thus rolled back too. Internal MariaDB error code: 0
|
mysqld: /test/10.8_dbg/sql/sql_error.cc:335: void Diagnostics_area::set_ok_status(ulonglong, ulonglong, const char*): Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' failed.
|
As discussed, it would be great to see this one resolved asap as the message shows up all over the test results, and clogs runs up. I have marked it critical as such for the moment. Thank you!
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | BINLOG_BASE64_EVENT: Rolling back unfinished transaction ... Internal MariaDB error code: 0 | Seemingly invalid 'BINLOG_BASE64_EVENT: Rolling back unfinished transaction ... Internal MariaDB error code: 0 |
| Summary | Seemingly invalid 'BINLOG_BASE64_EVENT: Rolling back unfinished transaction ... Internal MariaDB error code: 0 | Seemingly invalid 'BINLOG_BASE64_EVENT: Rolling back unfinished transaction ... Internal MariaDB error code: 0' Error |
| Summary | Seemingly invalid 'BINLOG_BASE64_EVENT: Rolling back unfinished transaction ... Internal MariaDB error code: 0' Error | Seemingly invalid 'BINLOG_BASE64_EVENT: Rolling back unfinished transaction ... Internal MariaDB error code: 0' Error | Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' failed in Diagnostics_area::set_ok_status |
| Link |
This issue relates to |
| Affects Version/s | 10.2 [ 14601 ] | |
| Affects Version/s | 10.3 [ 22126 ] | |
| Affects Version/s | 10.4 [ 22408 ] | |
| Affects Version/s | 10.5 [ 23123 ] | |
| Affects Version/s | 10.6 [ 24028 ] | |
| Affects Version/s | 10.7 [ 24805 ] |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Fix Version/s | 10.6 [ 24028 ] |
| Description |
As discussed with [~Elkin]. This (seemingly invalid) error is often seen during test runs:
{noformat:title=10.8.0 347f6d01e3b570dce49aa1ab42cb83021905a14d (Optimized)} 2022-01-18 23:23:40 4 [Note] BINLOG_BASE64_EVENT: Rolling back unfinished transaction (no COMMIT or ROLLBACK in relay log). A probable cause is that the master died while writing the transaction to its binary log, thus rolled back too. Internal MariaDB error code: 0 {noformat} However, no replication is active, it is a single server, a single SQL thread, and only a simple testcase is needed to produce either this message and/or a crash on debug: {code:sql} CREATE TABLE t (c CHAR(1)); XA START 'a'; SELECT dt DIV 1 AS f,id FROM t GROUP BY f; BINLOG ' O1ZVRw8BAAAAZgAAAGoAAAAAAAQANS4xLjIzLXJjLWRlYnVnLWxvZwAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAA7VlVHEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC '; {code} {code:sql} CREATE TABLE t (c INT KEY,c2 CHAR(1),c3 DATE); XA START 'b'; SELECT INTc,INTc2,CHARc,CHARc2,CHARc3 FROM t WHERE id=0; BINLOG ' SOgWTg8CAAAAbgAAAHIAAAAAAAQANS42LjMtbTUtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAABI6BZOEzgNAAgAEgAEBAQEEgAAVgAEGggAAAAICAgCAAAAAAVAYI8='; {code} Optimized may see the message only, and debug the message and crash. The crash is after the message: {noformat:title=10.8.0 347f6d01e3b570dce49aa1ab42cb83021905a14d (Debug)} 2022-01-18 23:23:36 4 [Note] BINLOG_BASE64_EVENT: Rolling back unfinished transaction (no COMMIT or ROLLBACK in relay log). A probable cause is that the master died while writing the transaction to its binary log, thus rolled back too. Internal MariaDB error code: 0 mysqld: /test/10.8_dbg/sql/sql_error.cc:335: void Diagnostics_area::set_ok_status(ulonglong, ulonglong, const char*): Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' failed. {noformat} Full affected versions will be added later. As discussed, it would be great to see this one resolved asap as the message shows up all over the test results, and clogs runs up. I have marked it critical as such for the moment. Thank you! |
As discussed with [~Elkin]. This (seemingly invalid) error is often seen during test runs:
{noformat:title=10.8.0 347f6d01e3b570dce49aa1ab42cb83021905a14d (Optimized)} 2022-01-18 23:23:40 4 [Note] BINLOG_BASE64_EVENT: Rolling back unfinished transaction (no COMMIT or ROLLBACK in relay log). A probable cause is that the master died while writing the transaction to its binary log, thus rolled back too. Internal MariaDB error code: 0 {noformat} However, no replication is active, it is a single server, a single SQL thread, and only a simple testcase is needed to produce either this message and/or a crash on debug: {code:sql} CREATE TABLE t (c CHAR(1)); XA START 'a'; SELECT dt DIV 1 AS f,id FROM t GROUP BY f; BINLOG ' O1ZVRw8BAAAAZgAAAGoAAAAAAAQANS4xLjIzLXJjLWRlYnVnLWxvZwAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAA7VlVHEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC '; {code} {code:sql} CREATE TABLE t (c INT KEY,c2 CHAR(1),c3 DATE); XA START 'b'; SELECT INTc,INTc2,CHARc,CHARc2,CHARc3 FROM t WHERE id=0; BINLOG ' SOgWTg8CAAAAbgAAAHIAAAAAAAQANS42LjMtbTUtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAABI6BZOEzgNAAgAEgAEBAQEEgAAVgAEGggAAAAICAgCAAAAAAVAYI8='; {code} Optimized may see the message only, and debug the message and crash. The crash is after the message: {noformat:title=10.8.0 347f6d01e3b570dce49aa1ab42cb83021905a14d (Debug)} 2022-01-18 23:23:36 4 [Note] BINLOG_BASE64_EVENT: Rolling back unfinished transaction (no COMMIT or ROLLBACK in relay log). A probable cause is that the master died while writing the transaction to its binary log, thus rolled back too. Internal MariaDB error code: 0 mysqld: /test/10.8_dbg/sql/sql_error.cc:335: void Diagnostics_area::set_ok_status(ulonglong, ulonglong, const char*): Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' failed. {noformat} As discussed, it would be great to see this one resolved asap as the message shows up all over the test results, and clogs runs up. I have marked it critical as such for the moment. Thank you! |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Andrei Elkin [ elkin ] | Sujatha Sivakumar [ sujatha.sivakumar ] |
| Status | In Progress [ 3 ] | In Testing [ 10301 ] |
| Assignee | Sujatha Sivakumar [ sujatha.sivakumar ] | Andrei Elkin [ elkin ] |
| Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
!| Assignee | Andrei Elkin [ elkin ] | Sujatha Sivakumar [ sujatha.sivakumar ] |
| Status | Stalled [ 10000 ] | In Review [ 10002 ] |
| Assignee | Sujatha Sivakumar [ sujatha.sivakumar ] | Brandon Nesterenko [ JIRAUSER48702 ] |
bnestere: Just pushed 42ae7659608..8b70b5bb625 HEAD -> bb-10.2-andrei .
| Assignee | Brandon Nesterenko [ JIRAUSER48702 ] | Andrei Elkin [ elkin ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
See bb-10.8-MDEV-27536-andrei branch for how to merge with log_event.cc -> log_event_server.cc hunk migration.
| Fix Version/s | 10.2.42 [ 26803 ] | |
| Fix Version/s | 10.3.33 [ 26805 ] | |
| Fix Version/s | 10.4.23 [ 26807 ] | |
| Fix Version/s | 10.5.14 [ 26809 ] | |
| Fix Version/s | 10.6.6 [ 26811 ] | |
| Fix Version/s | 10.7.2 [ 26813 ] | |
| Fix Version/s | 10.8.1 [ 26815 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Fix Version/s | 10.6 [ 24028 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Labels | affects-tests | affects-tests alter-replication |
With thanks to marko for the added assistance!