[LU-18183] shared rate limit for a TBF rule

• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Severity: 3
• Assignee: Qian Yingjin
• Reporter: Qian Yingjin

Description

In the current design of NRS TBF, for each TBF rule, there is a set of  TBF buckets (classes) corresponded to it. We schedule and limit the RPC rate per TBC bucket based.

Each bucket is in unit of "TBF type" (nid, gid, uid, jobid or opcode). It means that each TBF type unit (nid, gid, mid, jobid or opcode...) has a corresponding separate TBF bucket.

The TBF rule only classifies the matching requests into the TBF buckets.

However, there is a requirement that all I/O requests meeting a special TBF rule with shared rate limiting.

lctl set_param ost.OSS.ost_io.nrs_tbf_rule="start sharedlimit nid={192.168.23.*@tcp} rate=3000 share=1"

It means that all I/O requests coming from NID in 192.168.23.* are shared with rate limit of 3000.

Issue Links

• is related to: LU-18179 Implementation of Round-Robin/Fair Share response with Token Bucket Filters
• is related to: LU-17920 Add permanent TBF rules
• is related to: LU-14501 NRS TBF UID: limit per "any" user?
• is related to: LU-17044 TBF: minimum guarantee RPC rate when the server is overloaded

Comments

[Gerrit Updater]

"Qian Yingjin <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/56351
Subject: LU-18183 nrs: rule-based share rate limit for NRS TBF
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: d9cbfd94b17b5b48839c3092959eab0ea02bc655