Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TiDB binlog: update descriptions about commit ts and passoword #5986

Merged
merged 3 commits into from
Jul 27, 2021
Merged

TiDB binlog: update descriptions about commit ts and passoword #5986

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
601cc32
updated-binlog-docs-for-commits-and-passoword
en-jin19 Jul 15, 2021
29aa56d
Apply suggestions from code review
en-jin19 Jul 16, 2021
739928c
Update tidb-binlog/tidb-binlog-configuration-file.md
TomShawn Jul 16, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tidb-binlog/deploy-tidb-binlog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,9 +331,9 @@ The following part shows how to use Pump and Drainer based on the nodes above.
[syncer.to]
host = "192.168.0.13"
user = "root"
# If you do not want to set a cleartext `password` in the configuration file, you can create `encrypted_password` using `./binlogctl -cmd encrypt -text string`.
# When you have created an `encrypted_password` that is not empty, the `password` above will be ignored, because `encrypted_password` and `password` cannot take effect at the same time.
password = ""
# `encrypted_password` is encrypted using `./binlogctl -cmd encrypt -text string`.
# When `encrypted_password` is not empty, the `password` above will be ignored.
encrypted_password = ""
port = 3306

Expand Down
8 changes: 6 additions & 2 deletions tidb-binlog/tidb-binlog-configuration-file.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,8 +173,12 @@ This section introduces the configuration items of Drainer. For the example of a

### initial-commit-ts

* Specifies from which commit timestamp the replication task starts. This configuration is only applicable to the Drainer node that starts replication for the first time. If a checkpoint already exists downstream, the replication will be performed according to the time recorded in the checkpoint.
* Default value: `-1`. Drainer will get a new timestamp from PD as the starting time.
* Specifies from which commit timestamp of the transaction the replication process starts. This configuration is applicable only to the Drainer node that is in the replication process for the first time. If a checkpoint already exists in the downstream, the replication will be performed according to the time recorded in the checkpoint.
* commit ts (commit timestamp) is a specific point in time for [transaction](/transaction-overview.md#transactions) commits in TiDB. It is a globally unique and increasing timestamp from PD as the unique ID of the current transaction. You can get the `initial-commit-ts` configuration in the following typical ways:
- If BR is used, you can get `initial-commit-ts` from the backup TS recorded in the metadata backed up by BR (backupmeta).
- If Dumpling is used, you can get `initial-commit-ts` from the Pos recorded in the metadata backed up by Dumpling (metadata),
- If PD Control is used, `initial-commit-ts` is in the output of the `tso` command.
* Default value: `-1`. Drainer will get a new timestamp from PD as the starting time, which means that the replication process starts from the current time.

### synced-check-time

Expand Down