Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.3.10, 10.2.22
-
Debian 9.5, kernel version 4.9.0-6-amd64
Description
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size according to the mysql doc, flashback failure should happend.
I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check
update at 2018.03.08:
Actually, I later realized that this bug was already fixed in release 10.3.13(seems like the same problem according to the commit message of mysys/mf_iocache.c) , but since it is not yet applied to branch 10.2, I still made this pull request , plus adding the required mtr test and result file.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size, flashback failure should happend. |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size, flashback failure should happend. I've create a pull request: https://github.com/MariaDB/server/pull/1214 |
| Description |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size, flashback failure should happend. I've create a pull request: https://github.com/MariaDB/server/pull/1214 |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size, flashback failure should happend. I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check |
| Affects Version/s | 10.2.22 [ 23250 ] |
| Description |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size, flashback failure should happend. I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size according to the mysql doc, flashback failure should happend. I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check |
| Assignee | Andrei Elkin [ elkin ] |
| Description |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size according to the mysql doc, flashback failure should happend. I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size according to the mysql doc, flashback failure should happend. I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check update at 2018.03.08: Actually, I later realized that this bug was already fixed in release 10.3.11 , but since it is not yet applied to branch 10.2, I still made this pull request , plus adding the required mtr test and result file. |
| Description |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size according to the mysql doc, flashback failure should happend. I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check update at 2018.03.08: Actually, I later realized that this bug was already fixed in release 10.3.11 , but since it is not yet applied to branch 10.2, I still made this pull request , plus adding the required mtr test and result file. |
Failed to get the result using mysqlbinlog flashback option on large binlog file , failing case is as shown in the attachment pictures.
I've already figured it out - as long as the io_cache used within the flashback operation larger than 2147479552, which is the max value for read_buffer_size according to the mysql doc, flashback failure should happend. I've created a pull request: https://github.com/MariaDB/server/pull/1214, please check update at 2018.03.08: Actually, I later realized that this bug was already fixed in release 10.3.13(seems like the same problem according to the commit message of mysys/mf_iocache.c) , but since it is not yet applied to branch 10.2, I still made this pull request , plus adding the required mtr test and result file. |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.3 [ 22126 ] |
| Fix Version/s | 10.2.25 [ 23408 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 92866 ] | MariaDB v4 [ 155812 ] |