[LU-13735] Loosen restrictions on LNet Health parameter settings Created: 01/Jul/20  Updated: 08/Dec/20  Resolved: 08/Sep/20

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

Type: Improvement Priority: Minor
Reporter: Chris Horn Assignee: Chris Horn
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
Rank (Obsolete): 9223372036854775807

 Description   

The functions that set various LNet Health related parameters require
that the parameters be set in a specific order depending on whether
health is enabled or disabled. This is not user-friendly.

  • Don't overwrite lnet_transaction_timeout when health is being
    enabled or disabled.
  • Don't overwrite lnet_retry_count when health is being enabled
    (still set it to zero when health is disabled).
  • Allow lnet_retry_count to be set to 0 when health is disabled
  • Correct off-by-one error in transaction_to_set() to ensure
    lnet_transaction_timeout is greater than lnet_retry_count


 Comments   
Comment by Gerrit Updater [ 01/Jul/20 ]

Chris Horn (chris.horn@hpe.com) uploaded a new patch: https://review.whamcloud.com/39228
Subject: LU-13735 lnet: Loosen restrictions on LNet Health params
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: c7ccd1ddb916bac849b5773df522fd82495b4d43

Comment by Gerrit Updater [ 08/Sep/20 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/39228/
Subject: LU-13735 lnet: Loosen restrictions on LNet Health params
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: b8ff97611717d6f4cafd26d1e7e418fd745f5297

Comment by Peter Jones [ 08/Sep/20 ]

Landed for 2.14

Generated at Sat Feb 10 03:03:46 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.