add full backup ftwrl details in dumpling-overview.md #5444
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ti-chi-bot
added
missing-translation-status
|
/label needs-cherry-pick-5.0 |
ti-chi-bot
added
translation/from-docs-cn
lichunzhu
reviewed
Apr 23, 2021
dumpling-overview.md
Outdated
| @@ -262,7 +262,7 @@ With the above options specified, Dumpling can have a quicker speed of data expo | |||
|
|
|||
| Dumpling uses the `--consistency <consistency level>` option to control the way in which data is exported for "consistency assurance". For TiDB, data consistency is guaranteed by getting a snapshot of a certain timestamp by default (namely, `--consistency snapshot`). When using snapshot for consistency, you can use the `--snapshot` option to specify the timestamp to be backed up. You can also use the following levels of consistency: | |||
|
|
|||
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to ensure consistency. | |||
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to temporarily interrupt the DML and DDL operations of the backup database, ensure the global consistency of the backup connection, and record POS information. The lock is released after all backup connections start transactions. It is recommended to perform full backups at low business peaks or on the MySQL backup database. | |||
There was a problem hiding this comment.
Suggested change
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to temporarily interrupt the DML and DDL operations of the backup database, ensure the global consistency of the backup connection, and record POS information. The lock is released after all backup connections start transactions. It is recommended to perform full backups at low business peaks or on the MySQL backup database. | |
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to temporarily interrupt the DML and DDL operations of the backup database, ensure the global consistency of the backup connection, and record the binlog postition. The lock is released after all backup connections start transactions. It is recommended to perform full backups at low business valleys or on the MySQL replica database. |
|
/lgtm |
TomShawn
reviewed
Apr 23, 2021
dumpling-overview.md
Outdated
| @@ -262,7 +262,7 @@ With the above options specified, Dumpling can have a quicker speed of data expo | |||
|
|
|||
| Dumpling uses the `--consistency <consistency level>` option to control the way in which data is exported for "consistency assurance". For TiDB, data consistency is guaranteed by getting a snapshot of a certain timestamp by default (namely, `--consistency snapshot`). When using snapshot for consistency, you can use the `--snapshot` option to specify the timestamp to be backed up. You can also use the following levels of consistency: | |||
|
|
|||
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to ensure consistency. | |||
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to temporarily interrupt the DML and DDL operations of the replica database, ensure the global consistency of the backup connection, and record the binlog position information. The lock is released after all backup connections start transactions. It is recommended to perform full backups during off-peak business hours or on the MySQL replica database. | |||
There was a problem hiding this comment.
Suggested change
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to temporarily interrupt the DML and DDL operations of the replica database, ensure the global consistency of the backup connection, and record the binlog position information. The lock is released after all backup connections start transactions. It is recommended to perform full backups during off-peak business hours or on the MySQL replica database. | |
| - `flush`: Use [`FLUSH TABLES WITH READ LOCK`](https://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock) to temporarily interrupt the DML and DDL operations of the replica database, to ensure the global consistency of the backup connection, and to record the binlog position (POS) information. The lock is released after all backup connections start transactions. It is recommended to perform full backups during off-peak hours or on the MySQL replica database. |
|
rest |
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
ti-chi-bot
added
status/LGT2
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
|
/merge |
|
This pull request has been accepted and is ready to merge. Commit hash: c733783
|
ti-chi-bot
added
the
status/can-merge
ti-srebot
pushed a commit
to ti-srebot/docs
that referenced
this pull request
Apr 23, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
11 tasks
|
cherry pick to release-4.0 in PR #5455 |
ti-srebot
pushed a commit
to ti-srebot/docs
that referenced
this pull request
Apr 23, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
11 tasks
|
cherry pick to release-5.0 in PR #5456 |
ti-chi-bot
pushed a commit
that referenced
this pull request
Apr 23, 2021
ti-chi-bot
pushed a commit
that referenced
this pull request
Apr 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First-time contributors' checklist
What is changed, added or deleted? (Required)
add full backup ftwrl details
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?