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

lightning: add enable-diagnose-logs param #14303

Merged
merged 5 commits into from
Aug 3, 2023
Merged

lightning: add enable-diagnose-logs param #14303

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
18947a8
change
D3Hunter Jul 21, 2023
ae2f255
Update tidb-lightning/tidb-lightning-configuration.md
hfxsd Jul 21, 2023
92a03d3
Update tidb-lightning/tidb-lightning-configuration.md
hfxsd Jul 21, 2023
44aa670
Update tidb-lightning/tidb-lightning-configuration.md
hfxsd Jul 26, 2023
6ea1d69
Apply suggestions from code review
hfxsd Aug 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 8 additions & 3 deletions tidb-lightning/tidb-lightning-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,11 @@ file = "tidb-lightning.log"
max-size = 128 # MB
max-days = 28
max-backups = 14

# Whether to enable the diagnose log, the default is false, that is, only the logs related to the import will be output, and the logs of other dependent components will not be output.
# After it is enabled, the logs of other components that TiDB Lightning depends on will be output, and GRPC debug will be enabled, which can be used for problem diagnosis.
# This parameter has been introduced since v7.3.0.
enable-diagnose-logs = false
hfxsd marked this conversation as resolved.
Show resolved Hide resolved
```

### TiDB Lightning (Task)
Expand Down Expand Up @@ -148,10 +153,10 @@ addr = "172.16.31.10:8287"
# The following resolution algorithms are supported:
# - none: does not detect duplicate records, which has the best performance of the two algorithms.
# But if there are duplicate records in the data source, it might lead to inconsistent data in the target TiDB.
# - remove: if there are primary key or unique key conflicts between the inserting data A and B,
# - remove: if there are primary key or unique key conflicts between the inserting data A and B,
# A and B will be removed from the target table and recorded
# in the `lightning_task_info.conflict_error_v1` table in the target TiDB.
# You can manually insert the correct records into the target table based on your business requirements.
# in the `lightning_task_info.conflict_error_v1` table in the target TiDB.
# You can manually insert the correct records into the target table based on your business requirements.
# Note that the target TiKV must be v5.2.0 or later versions; otherwise it falls back to 'none'.
# The default value is 'none'.
# duplicate-resolution = 'none'
Expand Down