Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
10.2.0-1, 10.2.0-5, 10.2.0-6
Description
This is a request to add continuous binary log backup to mysqlbinlog, such as exists in the MySQL mysqlbinlog as of 5.6.
"As of MySQL 5.6, mysqlbinlog can read binary log files and write new files containing the same content—that is, in binary format rather than text format. This capability enables you to easily back up a binary log in its original format. mysqlbinlog can make a static backup, backing up a set of log files and stopping when the end of the last file is reached. It can also make a continuous (“live”) backup, staying connected to the server when it reaches the end of the last log file and continuing to copy new events as they are generated. In continuous-backup operation, mysqlbinlog runs until the connection ends (for example, when the server exits) or mysqlbinlog is forcibly terminated. When the connection ends, mysqlbinlog does not wait and retry the connection, unlike a slave replication server. To continue a live backup after the server has been restarted, you must also restart mysqlbinlog."
https://dev.mysql.com/doc/refman/5.6/en/mysqlbinlog-backup.html
This also requires the addition of 2 new mysqlbinlog options:
--stop-never
--stop-never-slave-server-id=id
https://dev.mysql.com/doc/refman/5.6/en/mysqlbinlog.html#option_mysqlbinlog_stop-never
https://dev.mysql.com/doc/refman/5.6/en/mysqlbinlog.html#option_mysqlbinlog_stop-never-slave-server-id
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
MDEV-8473 mysqlbinlog -v does not properly decode DECIMAL values in an RBR log
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Issue Type | Bug [ 1 ] | Task [ 3 ] |
| Fix Version/s | 10.2 [ 14601 ] |
| Fix Version/s | 10.1 [ 16100 ] |
I've added 10.1 to the list of 'Fix version(s)' just in case it can somehow be added there, although I highly doubt that, please don't see it as a promise.
| Component/s | Scripts & Clients [ 11002 ] |
Yes, thank you, the --raw option should also be included with this.
--raw
"By default, mysqlbinlog reads binary log files and writes events in text format. The --raw option tells mysqlbinlog to write them in their original binary format. Its use requires that --read-from-remote-server also be used because the files are requested from a server. mysqlbinlog writes one output file for each file read from the server. The --raw option can be used to make a backup of a server's binary log. With the --stop-never option, the backup is “live” because mysqlbinlog stays connected to the server. By default, output files are written in the current directory with the same names as the original log files. Output file names can be modified using the --result-file option. For more information, see Section 4.6.8.3, 'Using mysqlbinlog to Back Up Binary Log Files'. This option was added in MySQL 5.6.0."
https://dev.mysql.com/doc/refman/5.6/en/mysqlbinlog.html#option_mysqlbinlog_raw
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.1 [ 16100 ] |
| Fix Version/s | 10.2 [ 14601 ] |
| Sprint | 10.2.0-1 [ 21 ] |
| Rank | Ranked lower |
| Assignee | Alexey Botchkov [ holyfoot ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Please note that semi sync was added to this feature in WebScaleSQL
| Assignee | Alexey Botchkov [ holyfoot ] | Sergei Golubchik [ serg ] |
| Status | In Progress [ 3 ] | In Review [ 10002 ] |
| Sprint | 10.2.0-1 [ 21 ] | 10.2.0-1, 5.5.47-1 [ 21, 22 ] |
| Rank | Ranked higher |
| Sprint | 10.2.0-1, 5.5.47-1 [ 21, 22 ] | 10.2.0-1 [ 21 ] |
| Rank | Ranked lower |
| Sprint | 10.2.0-1 [ 21 ] | 10.2.0-1, 10.2.0-5 [ 21, 32 ] |
| Rank | Ranked higher |
| Assignee | Sergei Golubchik [ serg ] | Alexey Botchkov [ holyfoot ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| Sprint | 10.2.0-1, 10.2.0-5 [ 21, 32 ] | 10.2.0-1, 10.2.0-5, 10.2.0-6 [ 21, 32, 37 ] |
Patch proposal v2:
http://lists.askmonty.org/pipermail/commits/2016-February/009051.html
| Assignee | Alexey Botchkov [ holyfoot ] | Sergei Golubchik [ serg ] |
| Status | Stalled [ 10000 ] | In Review [ 10002 ] |
| Assignee | Sergei Golubchik [ serg ] | Alexey Botchkov [ holyfoot ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.2.0 [ 20700 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
Are the only real changes here to mysqlbinlong.cc?
If so, can this be backported to a GA version, say 10.1, and/or even 10.0?
Chris,
from the technical point of view yes, it can be backported to 10.0.
| Component/s | Replication [ 10100 ] |
| Link |
This issue relates to |
| Workflow | MariaDB v3 [ 71312 ] | MariaDB v4 [ 132676 ] |
We already have a similar request,
MDEV-8473. But that entry describes two separate issues – a feature request for new options from 5.6, and an upstream bug https://bugs.mysql.com/bug.php?id=65812. So, I am going to convert this one,MDEV-8713, to a feature request, whileMDEV-8473will remain a bug report.