Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion dm/dm-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,7 @@ If this issue occurs, you need to pause the task, delete all migrated data in th

You can avoid this issue in advance by configuring in the following ways:

1. Increase the value of `expire_logs_days` in the upstream MySQL database to avoid wrongly purging needed binlog files before the full migration task completes. If the data volume is large, it is recommended to use dumpling and TiDB-Lightning at the same time to speed up the task.
1. Increase the value of `expire_logs_days` in the upstream MySQL database to avoid wrongly purging needed binlog files before the full migration task completes. If the data volume is large, it is recommended to use Dumpling and TiDB Lightning at the same time to speed up the task.
2. Enable the relay log feature for this task so that DM can read data from relay logs even though the binlog position is purged.

## Why does the Grafana dashboard of a DM cluster display `failed to fetch dashboard` if the cluster is deployed using TiUP v1.3.0 or v1.3.1?
Expand Down
2 changes: 1 addition & 1 deletion get-started-with-tidb-lightning.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ This document provides a quick guide on getting started with TiDB Lightning by i

## Step 1: Prepare full backup data

First, you can use [dumpling](/dumpling-overview.md) to export data from MySQL.
First, use [Dumpling](/dumpling-overview.md) to export data from MySQL.

1. Run `tiup --version` to check if TiUP is already installed. If TiUP is installed, skip this step. If TiUP is not installed, run the following command:

Expand Down
2 changes: 1 addition & 1 deletion releases/release-4.0.3.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ TiDB version: 4.0.3
- Fix the issue that `getSchedulers` might cause a data race [#2638](https://github.com/pingcap/pd/pull/2638)
- Fix the issue that deleting the scheduler might cause deadlocks [#2637](https://github.com/pingcap/pd/pull/2637)
- Fix the bug that placement rules are not considered when `balance-leader-scheduler` is enabled [#2636](https://github.com/pingcap/pd/pull/2636)
- Fix the issue that sometimes service `safepoint` cannot be set properly, which might make BR and dumpling fail [#2635](https://github.com/pingcap/pd/pull/2635)
- Fix the issue that sometimes service `safepoint` cannot be set properly, which might make BR and Dumpling fail [#2635](https://github.com/pingcap/pd/pull/2635)
- Fix the issue that the target store in `hot region scheduler` is incorrectly selected [#2627](https://github.com/pingcap/pd/pull/2627)
- Fix the issue that the TSO request might take too long when PD leader is switched [#2622](https://github.com/pingcap/pd/pull/2622)
- Fix the issue of stale scheduler after leader change [#2608](https://github.com/pingcap/pd/pull/2608)
Expand Down
Loading