[LU-8429] Add option for gnilnd to not reconnect after connection timeout

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.9.0
• Labels: patch
• Severity: 3
• Assignee: Chris Horn
• Reporter: Chris Horn

Description

When routers time out a client connection during a catastrophic
network disturbance like a cabinet EPO, there still may be
traffic from the file system that is using the router for the
return path to the client. This will cause a new connection to try
to be formed before the network has quiesced causing multiple failed
connection attempts which need to be put in purgatory since they could
possibly connect in the future. This can cause the gart space to be
consumed with registrations.

So we'll add an option to not reconnect after connection timeout

Comments

[Peter Jones]

Landed for 2.9

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/21459/
Subject: LU-8429 gnilnd: Option to not reconnect after conn timeout
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 99bc4ba277637656f6329a67158af6cee7070b48

[Gerrit Updater]

Chris Horn ([e-mail]) uploaded a new patch: http://review.whamcloud.com/21459
Subject: LU-8429 gnilnd: Option to not reconnect after conn timeout
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: e226eff34f1c9331fa73619e97851c57d7808b09