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

The --io-retries option doesn't seem to work correctly #1413

Closed
xiaogaozi opened this issue Feb 11, 2022 · 1 comment · Fixed by #1713
Closed

The --io-retries option doesn't seem to work correctly #1413

xiaogaozi opened this issue Feb 11, 2022 · 1 comment · Fixed by #1713
Labels
kind/feature New feature or request pending Solution to this issue is not decided
Milestone

Comments

@xiaogaozi
Copy link
Member

What would you like to be added:

The --io-retries option should be able to control the number of retries for all IO requests, including read and write data to data storage and metadata engine.

Currently, the maxRetries of dataReader and dataWriter is equal to conf.Meta.Retries, and conf.Meta.Retries is hard coded to 10 (like here).

Why is this needed:

User need to be able to control the number of retries of IO requests.

@xiaogaozi xiaogaozi added the kind/feature New feature or request label Feb 11, 2022
@SandyXSD
Copy link
Contributor

Confirmed, this option is ignored for now.
There are several kind of retries in the IO procedure; we should rethink about them and make the option more clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request pending Solution to this issue is not decided
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants