https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-14566 Lustre <p>If discovery is disabled locally then the discovery thread will not<br/> modify any peer objects as a result of the discovery process. Thus,<br/> the primary NID of any peer we're asked to discover will not change<br/> as a result of discovery. Therefore, we do not need to actually<br/> perform discovery in LNetPrimaryNID() if discovery is disabled<br/> locally. Since this routine can result in long client mount times<br/> when a Lustre server is down we should avoid this unnecessary<br/> discovery.</p> LU-14566

Skip discovery in LNetPrimaryNID when lnet_peer_discovery_disabled is set

Improvement Minor Resolved Fixed Chris Horn Chris Horn Fri, 26 Mar 2021 18:53:50 +0000 Thu, 15 Jul 2021 02:42:26 +0000 Wed, 28 Apr 2021 04:11:19 +0000 Lustre 2.15.0 0 5 <p>Chris Horn (chris.horn@hpe.com) uploaded a new patch: <a href="https://review.whamcloud.com/43141" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/43141</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14566" title="Skip discovery in LNetPrimaryNID when lnet_peer_discovery_disabled is set" class="issue-link" data-issue-key="LU-14566"><del>LU-14566</del></a> lnet: Skip discovery in LNetPrimaryNID if DD disabled<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: eebda0deedd9a053f432b9638c70db2ce1cdf8ca</p> <p>Do you see this issue even with:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> LU-13972 o2iblnd: Don't retry indefinitely</pre> </div></div> <p>?</p> <p>That change will only impact local peers. Remote clients will still have to wait for the full lnet transaction timeout</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/43141/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/43141/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14566" title="Skip discovery in LNetPrimaryNID when lnet_peer_discovery_disabled is set" class="issue-link" data-issue-key="LU-14566"><del>LU-14566</del></a> lnet: Skip discovery in LNetPrimaryNID if DD disabled<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 16264da9e3c43a6368a25b6ded4113e8cfa57427</p> <p>Landed for 2.15</p> <p>Etienne AUJAMES (eaujames@ddn.com) uploaded a new patch: <a href="https://review.whamcloud.com/43537" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/43537</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14566" title="Skip discovery in LNetPrimaryNID when lnet_peer_discovery_disabled is set" class="issue-link" data-issue-key="LU-14566"><del>LU-14566</del></a> lnet: Skip discovery in LNetPrimaryNID if DD disabled<br/> Project: fs/lustre-release<br/> Branch: b2_12<br/> Current Patch Set: 1<br/> Commit: 58cab53ba8c387722e638c097c0496af007f091f</p> <p>We encountered an issue with 2 LNet routes missing on the server side (OSS): the clients could communicate with server but the servers could not answer.</p> <p>Clients tried periodically to connect to the servers maintaining the missing peers in the discovery list (the_lnet.ln_dc_working). This have the consequences to wait indefinitely for peer discovery in ll_ostXX_XXX threads and progressively contaminating all the available threads (the client keep sending connection requests).</p> <p>The server became unavailable for all the clients.</p> <p>The "LNet discovery" and the "LNet health" is disabled on the clients and on the servers.</p> Related LU-14668 Development Rank 1|i01qpr: Rank (Obsolete) 9223372036854775807