tikv/tikv

Copr SIG: Per-Request Max Execution Time

Open

#5,712 创建于 2019年10月23日

在 GitHub 查看
 (9 评论) (0 反应) (1 负责人)Rust (15,922 star) (2,189 fork)batch import
difficulty/easyhelp wanted

描述

Feature Request

In 3.0 TiDB supports max execution time. However TiKV is still using a configuration end-point-request-max-handle-duration to limit the task execution time, which is not flexible enough: a reboot is required and it cannot be applied over single request.

This task is to support push down TiDB's max execution time to TiKV's, so that we can have a per-request max execution time support.

贡献者指南

技术栈
rust
领域
backenddatabaseperformance
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
RustTiDBTiKV internalsdistributed systems
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
Investigate how TiDB implements per request max execution time and how TiKV currently uses `end point request max handle duration`. Look into TiKV's request handling code to identify where execution time can be limited per request. Review comments in the issue for any previous discussion or pointers. Files of interest: `src/server/` and `src/coprocessor/` in the TiKV repository.