Allow set LimitIOPS = 0 #14

Closed
opened 2025-03-26 11:14:35 +00:00 by dstepanov-yadro · 0 comments

Expected Behavior

If I define LimitIOPS as not nill, but equals 0, then I expect, that operations with this tag will be prohibited (error will be returned).

Current Behavior

Scheduler doesn't allow 0 as LimitIOPS value:

if v.LimitIOPS != nil && (math.IsNaN(*v.LimitIOPS) || *v.LimitIOPS <= float64(0)) {

## Expected Behavior If I define `LimitIOPS` as not nill, but equals 0, then I expect, that operations with this tag will be prohibited (error will be returned). ## Current Behavior Scheduler doesn't allow 0 as `LimitIOPS` value: https://git.frostfs.info/TrueCloudLab/frostfs-qos/src/commit/32079ad7c2752b2ee1ed89c927e11418b641655a/scheduling/mclock.go#L156
dstepanov-yadro added the
bug
label 2025-03-26 11:14:35 +00:00
Sign in to join this conversation.
No description provided.