[LU-15275] Skip router discovery on send path Created: 23/Nov/21  Updated: 30/Aug/22  Resolved: 06/Jan/22

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

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

Rank (Obsolete): 9223372036854775807

 Description   

When the router checker is enabled, routes are regularly marked as out
of date w.r.t. discovery. This can cause upper level messages to be
delayed while the router undergoes discovery. We can avoid delaying
messages by relying on the router checker to initiate discovery of
routers. If we happen to send a message to a router before it has
been discovered then the worst case scenario is that the route is
actually down or we end up utilizing a subset of a multi-rail router's
interfaces. Both situations can be remedied by utilizing the
check_routers_before_use parameter.

Change the logic in lnet_handle_find_routed_path() so that we only
initiate discovery if the alive_router_check_interval is <= 0 (i.e.
router checker pings are disabled).



 Comments   
Comment by Gerrit Updater [ 23/Nov/21 ]

"Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/45655
Subject: LU-15275 lnet: Prioritize routes that are already up to date
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 856513eddcc2e478b013952cf075c1d3d5cf7cf2

Comment by Gerrit Updater [ 30/Nov/21 ]

"Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/45684
Subject: LU-15275 lnet: Skip router discovery on send path
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 178ea10ef4f2bb0781d0bdcc495aace48b30de6f

Comment by Gerrit Updater [ 06/Jan/22 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45684/
Subject: LU-15275 lnet: Skip router discovery on send path
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: c8e74c395d5634dbb0d9d8a86605bb36ab2b8233

Comment by Peter Jones [ 06/Jan/22 ]

Landed for 2.15

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