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.

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

update: zh/tikv_best_practices.md #4167

Merged
merged 2 commits into from
Nov 16, 2023
Merged
Changes from 1 commit
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
6 changes: 6 additions & 0 deletions docs/zh_cn/administration/metadata/tikv_best_practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -187,3 +187,9 @@ CFQ 尝试提供由发起 I/O 进程决定的公平的 I/O 调度,该算法为
##### deadline

deadline 调度算法主要针对 I/O 请求的延时,每个 I/O 请求都被附加一个最后执行期限。读请求和写请求被分成了两个队列,默认优先处理读 IO,除非写快到 deadline 时才调度。当系统中存在的 I/O 请求进程数量比较少时,与 CFQ 算法相比,deadline 算法可以提供较高的 I/O 吞吐率。

## 常见问题

### 多机并发读写同一个目录,如何避免持续的事务重启现象?

JuiceFS v1.1 版本开始提供 `--skip-dir-nlink value` 挂载选项,用以指定跳过目录的 nlink 检查之前的重试次数,默认为 20 次。可以适当调小该值,或者设置为 0 禁止重试,以避免持续的事务重启现象,详情参考[元数据相关的挂载选项](https://juicefs.com/docs/zh/community/command_reference#mount-metadata-options)。
Copy link
Contributor

@Hexilee Hexilee Nov 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

我认为“跳过目录的 nlink 检查之前的重试次数” 这个描述不是很直观,应该强调一下这个 case 的具体场景:只有多客户端在同一个目录下频繁创建/删除子目录情况下才可能会遇到