Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.9(EOL), 10.10(EOL), 10.11, 11.4
Description
mleich provided an rr replay trace where InnoDB would crash soon after a SET GLOBAL innodb_log_file_size=4194304 was completed. The reason appears to be that in log_t::resize_write() we fail to wrap around the log_sys.resize_lsn when the start offset (disregarding the length of the mini-transaction) exceeds the log_sys.resize_target (the requested size of the file). We would only perform the wrap-around when the start offset + the length would wrap around.
In the trace that I analyzed, we would catch a SIGSEGV on an attempt to write to log_sys.buf at an offset somewhere between 4 MiB and 8 MiB while the size of the memory mapped region is 4 MiB.
Attachments
Issue Links
- is caused by
-
MDEV-27812 Allow innodb_log_file_size to change without server restart
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue is caused by |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Marko Mäkelä [ marko ] | Debarun Banerjee [ JIRAUSER54513 ] |
| Status | In Progress [ 3 ] | In Review [ 10002 ] |
| Assignee | Debarun Banerjee [ JIRAUSER54513 ] | Marko Mäkelä [ marko ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| Assignee | Marko Mäkelä [ marko ] | Debarun Banerjee [ JIRAUSER54513 ] |
| Status | Stalled [ 10000 ] | In Review [ 10002 ] |
| Assignee | Debarun Banerjee [ JIRAUSER54513 ] | Marko Mäkelä [ marko ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| issue.field.resolutiondate | 2024-09-05 05:07:49.0 | 2024-09-05 05:07:49.447 |
| Fix Version/s | 10.11.10 [ 29904 ] | |
| Fix Version/s | 11.2.6 [ 29906 ] | |
| Fix Version/s | 11.4.4 [ 29907 ] | |
| Fix Version/s | 11.6.2 [ 29908 ] | |
| Fix Version/s | 10.11 [ 27614 ] | |
| Fix Version/s | 11.4 [ 29301 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |