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-12291 Lustre <p>If the sending node is MultiRail and the receiving node is non-MultiRail,<br/> the sending node use always the same NI (even if the sending NI is blocken, the blocken NI is used).<br/> This may be the specification of MultiRail, but blocken device should be used.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> REMOTE IB0 (non-MultiRail node) ↑ x | LOCAL IB0 IB1 &lt;- always use IB0(not in round-robin fashion) failure </pre> </div></div> <p>If the receiving node is non-MultiRail, we check whether its device is normal or out of service and reset the device in case of failure.</p> LU-12291

Wrong NI selection on asymmetric Multi-rail environment

Bug Minor Open Unresolved Tatsushi Takamura Tatsushi Takamura Mon, 13 May 2019 09:25:18 +0000 Fri, 16 Oct 2020 06:21:56 +0000 0 3 <p>The reason we always stick with the same device is because doing otherwise will confuse the non-MR peer. If the non-MR peer initiated the connection on a specific NID, it always expects communication from that same NID. If the MR node uses another NID, then it will consider it communication from a different node.</p> <p>The reset of the device on failure sounds interesting. How do you do that?</p> Development Epic/Theme lnet Rank 1|i00g5r: Rank (Obsolete) 9223372036854775807 Severity