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

Using OpStep timeout to replace operator timeout mechanism. #4547

Closed
Tracked by #4456
bufferflies opened this issue Jan 5, 2022 · 1 comment · Fixed by #4548
Closed
Tracked by #4456

Using OpStep timeout to replace operator timeout mechanism. #4547

bufferflies opened this issue Jan 5, 2022 · 1 comment · Fixed by #4548

Comments

@bufferflies
Copy link
Contributor

bufferflies commented Jan 5, 2022

Enhancement Task

  1. every step has independent timeout duration.
  2. adds max-region-size scheduler config
@ti-chi-bot
Copy link
Member

@bufferflies: There are no type labels on this issue. Please add an appropriate label by using the following command:

  • /type <type-name>

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/test-infra repository.

@ti-chi-bot ti-chi-bot added the needs-type Indicates an issue requires a type label. label Jan 5, 2022
@lhy1024 lhy1024 removed the needs-type Indicates an issue requires a type label. label Jan 7, 2022
@bufferflies bufferflies changed the title adds timeoutfactor property to operator struct, adds max-region-size and operator-time-factor to scheduler config. Using OpStep timeout to replace operator timeout mechanism. Feb 11, 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
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants