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-8782 Lustre <p>We would like to get clarification and verify configuration using patch <a href="https://jira.whamcloud.com/browse/LU-3322" title="ko2iblnd support for different map_on_demand and peer_credits between systems" class="issue-link" data-issue-key="LU-3322"><del>LU-3322</del></a>. </p> <p>We are running 2.7.2 with patch from <a href="https://jira.whamcloud.com/browse/LU-3322" title="ko2iblnd support for different map_on_demand and peer_credits between systems" class="issue-link" data-issue-key="LU-3322"><del>LU-3322</del></a>. When configureing two hosts with different peer_credits we get this error when the initial connection is made.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">LNetError: 81:0:(o2iblnd_cb.c:2325:kiblnd_passive_connect()) Can't accept conn from xxx.xxx.xxx.xxx@o2ib, queue depth too large: 63 (&lt;=16 wanted) </pre> </div></div> <p>Although we get the error lnet_selftest is working. </p> <p>Host1:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">options ko2iblnd timeout=150 retry_count=7 peer_timeout=0 peer_credits=63 concurrent_sends=63 </pre> </div></div> <p>Host2</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">options ko2iblnd timeout=150 retry_count=7 peer_credits=16 concurrent_sends=63 </pre> </div></div> <p>Attaching debug output from HOST2</p> LU-8782

queue depth too large: 63 (<=16 wanted)

Bug Minor Resolved Not a Bug Amir Shehata Mahmoud Hanafi Mon, 31 Oct 2016 17:39:24 +0000 Fri, 30 Jun 2017 17:46:22 +0000 Fri, 30 Jun 2017 17:46:22 +0000 Lustre 2.7.0 0 4 <p>Hi Doug,</p> <p>Any advice for this issue?</p> <p>Thanks.<br/> Joe</p> <p>Looking at the code for <a href="https://jira.whamcloud.com/browse/LU-3322" title="ko2iblnd support for different map_on_demand and peer_credits between systems" class="issue-link" data-issue-key="LU-3322"><del>LU-3322</del></a>, when a connection attempt is rejected due to a queue depth being too big, a new connection attempt should be done at the lower queue depth value. </p> <p>So, when you see this error message, do the two nodes still end up with a connection and everything works fine? If so, then we should just "turn-down" this error message to just be informational.</p> <p>Please close this case. This error is well understood.</p> <p>Thanks</p> Development Rank 1|hzytyf: Rank (Obsolete) 9223372036854775807 Severity