<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:41:19 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-11144] Dynamic Discovery is not triggered for router peers</title>
                <link>https://jira.whamcloud.com/browse/LU-11144</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;It appears to me that dynamic discovery will not be triggered for LNet routers under normal operating conditions (i.e. without an explicit lnetctl discover of the routers).&lt;/p&gt;

&lt;p&gt;The discovery logic is early in lnet_select_pathway() and based on the peer associated with the dst_nid. The only LNetGet where dst_nid is a router is going to be the router checker traffic. But that traffic goes on the LNET_RESERVED_PORTAL, so it will never trigger discovery.&lt;br/&gt;
Seems like we need to check for discovery of the router peer after selecting it later in lnet_select_pathway().&lt;/p&gt;</description>
                <environment></environment>
        <key id="52692">LU-11144</key>
            <summary>Dynamic Discovery is not triggered for router peers</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="ashehata">Amir Shehata</assignee>
                                    <reporter username="hornc">Chris Horn</reporter>
                        <labels>
                            <label>LNet</label>
                    </labels>
                <created>Wed, 11 Jul 2018 19:33:25 +0000</created>
                <updated>Fri, 27 Jan 2023 17:05:53 +0000</updated>
                            <resolved>Fri, 27 Jan 2023 17:05:53 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="230217" author="hornc" created="Thu, 12 Jul 2018 18:24:44 +0000"  >&lt;p&gt;I think what I was missing with router peers and dynamic discovery is the DD push&lt;br/&gt;
router should queue other peers for discovery based on where it is forwarding traffic, and the discovery thread should push the router&apos;s MR info to those peers as part of that. Right?&lt;/p&gt;

&lt;p&gt;So while the description in this ticket is, I believe, accurate it&apos;s probably by design and not necessarily a problem.&lt;/p&gt;</comment>
                            <comment id="231680" author="ashehata" created="Wed, 8 Aug 2018 22:35:27 +0000"  >&lt;p&gt;both &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11143&quot; title=&quot;Multi-Rail/Dynamic Discovery break LNet router checker and asymmetric route failure detection&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11143&quot;&gt;&lt;del&gt;LU-11143&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11144&quot; title=&quot;Dynamic Discovery is not triggered for router peers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11144&quot;&gt;&lt;del&gt;LU-11144&lt;/del&gt;&lt;/a&gt; are related.&lt;/p&gt;

&lt;p&gt;I address them here:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://wiki.whamcloud.com/display/LNet/Routing+and+MR+integration&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.whamcloud.com/display/LNet/Routing+and+MR+integration&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Might be a good idea to use that link for feedback on the proposals&lt;/p&gt;</comment>
                            <comment id="252055" author="spitzcor" created="Fri, 26 Jul 2019 03:55:36 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/secure/ViewProfile.jspa?name=ashehata&quot; class=&quot;user-hover&quot; rel=&quot;ashehata&quot;&gt;ashehata&lt;/a&gt;, ready to resolve this and &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11143&quot; title=&quot;Multi-Rail/Dynamic Discovery break LNet router checker and asymmetric route failure detection&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11143&quot;&gt;&lt;del&gt;LU-11143&lt;/del&gt;&lt;/a&gt;?&lt;/p&gt;</comment>
                            <comment id="252074" author="ashehata" created="Fri, 26 Jul 2019 15:23:40 +0000"  >&lt;p&gt;I believe this issue has been resolved in the new routing code.&lt;/p&gt;</comment>
                            <comment id="253597" author="spitzcor" created="Mon, 26 Aug 2019 16:06:57 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/secure/ViewProfile.jspa?name=ashehata&quot; class=&quot;user-hover&quot; rel=&quot;ashehata&quot;&gt;ashehata&lt;/a&gt;, will you be resolving this issue then?  Can you point at a specific commit or LU that resolved it?&lt;/p&gt;</comment>
                            <comment id="360686" author="hornc" created="Fri, 27 Jan 2023 17:05:53 +0000"  >&lt;p&gt;Resolved with MR routing feature&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="53153">LU-11297</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="52691">LU-11143</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzzz2f:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>