[Feature]: Distinguish between limit repair and business limitio #3881
Description
Contact Details
Is there an existing issue for this?
- I have searched all the existing issues
Is your feature request related to a problem? Please describe.
The current storage system uses a unified IO current limiting strategy (limitIO) to manage all read requests, including business (user requests) and repair (data copy repair). As the cluster scale expands and the business complexity increases, the resource competition problem of the two types of requests becomes increasingly prominent, leading to the following problems:
- Business delay fluctuations: For example, repair reads occupy a large amount of bandwidth/IOPS, affecting the response time of user requests.
- Inefficient repair: During business peak periods, repair tasks cannot be completed in time due to current limiting, reducing data reliability.
Describe the solution you'd like.
Separate the throttling strategies for repair and business to achieve differentiated resource guarantees, while supporting dynamic adjustment of the throttling parameters of the two types of requests based on real-time load.
Describe an alternate solution.
No response
Anything else? (Additional Context)
No response