[LU-8908] Add USER ID NRS Policy to TBF Created: 05/Dec/16  Updated: 16/Sep/17  Resolved: 16/Sep/17

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.7.0
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Mahmoud Hanafi Assignee: Peter Jones
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates LU-9658 Add QoS for uid and gid in NRS-TBF Resolved
Rank (Obsolete): 9223372036854775807

 Description   

Our users run a variety of application with different I/O characteristic. Some applications have well-formed large sequential I/O, while others can have small random I/O access patterns. Lustre is the principal scratch filesystem and there are six individual filesystems. Each user is assigned to one filesystem. This helps to distribute storage allocations and utilization across all filesystems. But, there are occasions when a single user’s code adversely impact the whole filesystem. This results in poor filesystem throughput effecting job runtimes and poor interactive response for all users.

Although TBF provides some of the QoS functionally, it doesn’t meet all our requirements. We would like these additional capablilies added to TBF NRS.

  1. Add user id tracking
  2. Default value for all users
  3. Allow of setting of token buckets for each user
  4. Add a control trigger for enforcement of tokens. (ie RPC queue size or RPC queue wait)  


 Comments   
Comment by Peter Jones [ 05/Dec/16 ]

Thanks Mahmoud

Comment by Andreas Dilger [ 16/Sep/17 ]

This is being implemented via LU-9658, closing this ticket.

Generated at Sat Feb 10 02:21:35 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.