how-to/maintain: refine BR doc description and organization#2088
Merged
Conversation
lilin90
reviewed
Dec 2, 2019
TomShawn
added
translation/done
Contributor
Author
|
@3pointer PTAL, thanks~ |
3pointer
reviewed
Dec 4, 2019
|
|
||
| 2. 把解析出来的 SST 文件，根据表进行 `GroupBy` 聚合。 | ||
|
|
||
| 3. 根据 SST 文件的 Key Range 进行预切分 Region，使得每个 Region 对应一个 SST 文件。 |
Contributor
There was a problem hiding this comment.
Suggested change
| 3. 根据 SST 文件的 Key Range 进行预切分 Region，使得每个 Region 对应一个 SST 文件。 | |
| 3. 根据 SST 文件的 Key Range 进行预切分 Region，使得每个 Region 至少对应一个 SST 文件。 |
lilin90
reviewed
Dec 4, 2019
|
|
||
| 5. 找到该文件对应的 Region，发送下载文件的请求到对应的 TiKV 节点，并在下载成功后，发送加载请求。 | ||
|
|
||
| TiKV 收到加载 SST 文件的请求后, 利用 Raft 机制保证加载 SST 数据的强一致性。在加载成功后，下载下来的 SST 文件会被异步删除。 |
Member
There was a problem hiding this comment.
Suggested change
| TiKV 收到加载 SST 文件的请求后, 利用 Raft 机制保证加载 SST 数据的强一致性。在加载成功后，下载下来的 SST 文件会被异步删除。 | |
| TiKV 收到加载 SST 文件的请求后，利用 Raft 机制保证加载 SST 数据的强一致性。在加载成功后，下载下来的 SST 文件会被异步删除。 |
lilin90
reviewed
Dec 4, 2019
| @@ -241,14 +183,14 @@ br restore table \ | |||
|
|
|||
| ## 注意事项 | |||
| - BR 只支持 TiDB 3.1 及以上版本。 | ||
| - 如果在没有网络存储的集群上备份，在恢复前需要将所有备份下来的 SST 文件拷贝到各个 TiKV 节点上 `--storage` 指定的目录下。 | ||
| - BR 只支持 TiDB v3.1 及以上版本。 | ||
| - 如果备份的集群没有网络存储，在恢复前需要将所有备份的 SST 文件拷贝到各个 TiKV 节点上 `--storage` 指定的目录下。 |
Member
There was a problem hiding this comment.
Suggest moving this item to 恢复集群数据.
| - 目前不支持 Partition Table 的备份恢复。 | ||
| - 目前只支持在全新的集群上执行恢复操作。 | ||
| - 如果备份时间可能超过设定的 GC lifetime（默认 10 分钟），则需要将 GC lifetime 调大。 | ||
| - 如果备份时间可能超过设定的 [`tikv_gc_life_time`](/dev/reference/garbage-collection/configuration.md#tikv_gc_life_time)（默认 `10m0s`），则需要将该参数调大。 |
Member
There was a problem hiding this comment.
How about moving this item to the backup section?
| 例如，将 `tikv_gc_life_time` 调整为 `720h`： | ||
|
|
||
| {{< copyable "sql" >}} | ||
|
|
Member
There was a problem hiding this comment.
@3pointer Can we take this item (为了加快数据恢复速度...) as one of the best practices section?
| @@ -241,14 +183,14 @@ br restore table \ | |||
|
|
|||
| ## 注意事项 | |||
3pointer
reviewed
Dec 4, 2019
3pointer
approved these changes
Dec 4, 2019
lilin90
reviewed
Dec 4, 2019
|
|
||
| - BR 只支持 TiDB v3.1 及以上版本。 | ||
| - TiDB 执行 DDL 期间不能执行备份操作。 | ||
| - 目前不支持 Partition Table 的备份恢复。 |
Member
There was a problem hiding this comment.
Suggested change
| - 目前不支持 Partition Table 的备份恢复。 | |
| - 目前不支持分区表的备份恢复。 |
| "update mysql.tidb set variable_value='720h' where variable_name='tikv_gc_life_time'"; | ||
| ``` | ||
|
|
||
| - 为了加快数据恢复速度，可以在恢复操作前，使用 pd-ctl 关闭与调度相关的 schedulers。恢复完成后，再重新添加这些 schedulers。 |
Member
There was a problem hiding this comment.
Suggested change
| - 为了加快数据恢复速度，可以在恢复操作前，使用 pd-ctl 关闭与调度相关的 schedulers。恢复完成后，再重新添加这些 schedulers。 | |
| - 为了加快数据恢复速度，可以在恢复操作前，使用 pd-ctl 关闭与调度相关的 scheduler。恢复完成后，再重新添加这些 scheduler。 |
lilin90
changed the title
lilin90
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What is changed, added or deleted?
Refine the BR document and update v3.1
What is the related PR or file link(s)?
#2084
Which version does your change affect?
dev, v3.1