Can I limit IOBandwith or IOPS?

[link89]

I find that there are users running IO heavy command on login node from time to time, which often freeze the ssh sessions of all users.

I hope that I can add some rule to limit the IOBandwidth or IOPS with arbiter, The rule can just be a simple limit like IOPSRead=3000. Is it possible to add such extra limits with arbiter. If that's possbile, then where I can add those rules.

[jay-mckay]

Hello,

This is currently not a feature of arbiter2. We have explored this in the past, but the cgroup v1 properties associated with this only work for physical devices on the machine - at our site most of the data is read/written over NFS.

As for whether this feature should be in arbiter2, we could discuss that further. it would fit well if we were monitoring IO usage an wanted to dynamically limit the IO usage, but it sounds like you just want a simple rule, which can just be configured once outside of arbiter. For example, updating blkio.throttle.read_iops_device in the user.slice cgroup for the device you wish to throttle.