-
Notifications
You must be signed in to change notification settings - Fork 1.2k
add tiflash config storage.temp #20151
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.
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: guo-shaoge <[email protected]>
related tiflash pr: pingcap/tiflash#10035 |
Signed-off-by: guo-shaoge <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@windtalker: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: guo-shaoge <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: guo-shaoge <[email protected]>
Signed-off-by: guo-shaoge <[email protected]>
Signed-off-by: guo-shaoge <[email protected]>
Signed-off-by: guo-shaoge <[email protected]>
@joey-yez: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Co-authored-by: guo-shaoge <[email protected]>
- 从 v9.0.0 版本开始,不推荐使用 `tmp_path`。推荐使用 [`storage.temp`](#storage.temp-从-v900-版本开始引入)下的配置项代替,因为新的配置项支持设置 capacity 限制临时文件使用的空间。 | ||
- 当 `storage.temp` 配置存在时,会忽略 `tmp_path`。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 从 v9.0.0 版本开始,不推荐使用 `tmp_path`。推荐使用 [`storage.temp`](#storage.temp-从-v900-版本开始引入)下的配置项代替,因为新的配置项支持设置 capacity 限制临时文件使用的空间。 | |
- 当 `storage.temp` 配置存在时,会忽略 `tmp_path`。 | |
- 从 v9.0.0 开始,不推荐使用 `tmp_path`。建议使用 [`storage.temp`](#storage.temp-从-v900-版本开始引入) 中的配置项替代,因其支持设置容量限制,控制临时文件的空间使用。 | |
- 当 `storage.temp` 配置存在时,`tmp_path` 配置会被忽略。 |
|
||
##### `dir` | ||
|
||
- 用于存储查询落盘文件。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 用于存储查询落盘文件。 | |
- 指定用于存储查询结果的落盘文件路径。 |
##### `dir` | ||
|
||
- 用于存储查询落盘文件。 | ||
- 默认使用 [`storage.latest.dir`](#dir-1) 的第一个目录\] + "/tmp" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 默认使用 [`storage.latest.dir`](#dir-1) 的第一个目录\] + "/tmp" | |
- 默认使用 \[[`storage.latest.dir`](#dir-1) 的第一个目录\] + "/tmp" |
|
||
##### `capacity` | ||
|
||
- 用于限制临时文件目录所能使用的总空间。如果查询落盘过程中落盘文件超过该值,则会报错结束。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 用于限制临时文件目录所能使用的总空间。如果查询落盘过程中落盘文件超过该值,则会报错结束。 | |
- 限制临时文件目录的总空间使用量。如果查询过程中生成的落盘文件超过该限制,将导致错误并中止操作。 |
##### `capacity` | ||
|
||
- 用于限制临时文件目录所能使用的总空间。如果查询落盘过程中落盘文件超过该值,则会报错结束。 | ||
- 单位:Byte。目前不支持如 `"10GB"` 的设置。范围:[0, 9223372036854775807]。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 单位:Byte。目前不支持如 `"10GB"` 的设置。范围:[0, 9223372036854775807]。 | |
- 单位:Byte。目前不支持类似 `"10GB"` 的格式。 | |
- 范围:`[0, 9223372036854775807]` |
|
||
- 用于限制临时文件目录所能使用的总空间。如果查询落盘过程中落盘文件超过该值,则会报错结束。 | ||
- 单位:Byte。目前不支持如 `"10GB"` 的设置。范围:[0, 9223372036854775807]。 | ||
- 如果不设置该值或者将该值设置为 0,表示不限制临时文件所占用的空间,落盘文件可以使用整个硬盘容量。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 如果不设置该值或者将该值设置为 0,表示不限制临时文件所占用的空间,落盘文件可以使用整个硬盘容量。 | |
- 如果未设置该值或将其设置为 `0`,表示不限制临时文件的空间使用,落盘文件可以使用整个硬盘的容量。 |
- 用于限制临时文件目录所能使用的总空间。如果查询落盘过程中落盘文件超过该值,则会报错结束。 | ||
- 单位:Byte。目前不支持如 `"10GB"` 的设置。范围:[0, 9223372036854775807]。 | ||
- 如果不设置该值或者将该值设置为 0,表示不限制临时文件所占用的空间,落盘文件可以使用整个硬盘容量。 | ||
- 如果该值大于 0,TiFlash 启动时会做如下检查: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 如果该值大于 0,TiFlash 启动时会做如下检查: | |
- 如果设置了大于 `0` 的值,TiFlash 在启动时会执行以下检查: |
- 如果不设置该值或者将该值设置为 0,表示不限制临时文件所占用的空间,落盘文件可以使用整个硬盘容量。 | ||
- 如果该值大于 0,TiFlash 启动时会做如下检查: | ||
- `storage.temp.capacity` 必须小于等于 `storage.temp.dir` 所在硬盘的总空间。 | ||
- 如果 `storage.temp.dir` 是 `storage.main.dir` 的子目录,且 `storage.main.capacity` 大于 0,则 `storage.temp.capacity` 必须小于等于 `storage.main.capacity`。(同理如果是 `storage.latest.dir` 的子目录,也会做类似的检查)。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 如果 `storage.temp.dir` 是 `storage.main.dir` 的子目录,且 `storage.main.capacity` 大于 0,则 `storage.temp.capacity` 必须小于等于 `storage.main.capacity`。(同理如果是 `storage.latest.dir` 的子目录,也会做类似的检查)。 | |
- 如果 `storage.temp.dir` 是 `storage.main.dir` 的子目录,且 `storage.main.capacity` 大于 `0`,则 `storage.temp.capacity` 必须小于等于 `storage.main.capacity`。同理,如果是 `storage.latest.dir` 的子目录,也会进行类似检查。 |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?