From 424681c94b19363a5b5006d2eaa55f4b81ea4f71 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 20 Dec 2023 11:38:40 +0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Aolin --- tidb-lightning/tidb-lightning-physical-import-mode.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tidb-lightning/tidb-lightning-physical-import-mode.md b/tidb-lightning/tidb-lightning-physical-import-mode.md index 527b94832b482..1cc3ad215d66c 100644 --- a/tidb-lightning/tidb-lightning-physical-import-mode.md +++ b/tidb-lightning/tidb-lightning-physical-import-mode.md @@ -97,5 +97,5 @@ It is recommended that you allocate CPU more than 32 cores and memory greater th - When you use TiDB Lightning with BR, note the following: - When BR backs up snapshots of tables that are being imported by TiDB Lightning, it might result in inconsistent backup data for those tables. - - When BR backs up data based on the AWS EBS volume snapshots, TiDB Lightning might fail to import data. - - Point-in-time recovery (PITR) can not back up data imported by TiDB Lightning. + - When BR backs up data using AWS EBS volume snapshots, TiDB Lightning might fail to import data. + - Point-in-time recovery (PITR) cannot back up data imported by TiDB Lightning.