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

Opeator life cycle will adjust by region size not hard code includes expired、timeout、influence #4456

Closed
6 tasks done
bufferflies opened this issue Dec 13, 2021 · 0 comments
Assignees
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@bufferflies
Copy link
Contributor

bufferflies commented Dec 13, 2021

Enhancement Task

Every step should have individual timeout that should depence on the size of the region and the time factor. The time factor should be adjust by config, like:
timeout=min(10m,RegionSize* TimeFactor)

SubTask

@bufferflies bufferflies added the type/enhancement The issue or PR belongs to an enhancement. label Dec 13, 2021
@bufferflies bufferflies self-assigned this Jan 6, 2022
ti-chi-bot added a commit that referenced this issue Mar 1, 2022
ref #4456, close #4547

Signed-off-by: bufferflies <1045931706@qq.com>

Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

No branches or pull requests

1 participant