<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:16:07 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-15177]  cs_update live batch update hung waiting for MDT recovery to complete</title>
                <link>https://jira.whamcloud.com/browse/LU-15177</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Problem: MDT-MDT interop check prevents (single MDT) rolling update from 2.12.0.5-based -&amp;gt; 2.12.4.1-based Lustre because the versions are too far away from one another to complete inter-op recovery. &lt;/p&gt;

&lt;p&gt;two similar code snippets found in ptlrpc_connect_interpret() and &lt;br/&gt;
target_handle_connect():&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
                        /*
                         * We &lt;span class=&quot;code-keyword&quot;&gt;do&lt;/span&gt; not support the MDT-MDT interoperations with
                         * different version MDT because of protocol changes.
                         */
                        &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (unlikely(major != LUSTRE_MAJOR ||
                                     minor != LUSTRE_MINOR ||
                                     abs(patch - LUSTRE_PATCH) &amp;gt; 3)) {
                                LCONSOLE_WARN(&lt;span class=&quot;code-quote&quot;&gt;&quot;%s (%u.%u.%u.%u) refused the connection from different version MDT (%d.%d.%d.%d) %s %s\n&quot;&lt;/span&gt;,
                                              target-&amp;gt;obd_name, LUSTRE_MAJOR,
                                              LUSTRE_MINOR, LUSTRE_PATCH,
                                              LUSTRE_FIX, major, minor, patch,
                                              OBD_OCD_VERSION_FIX(data-&amp;gt;ocd_version),
                                              libcfs_nid2str(req-&amp;gt;rq_peer.nid),
                                              str);
                                GOTO(out, rc = -EPROTO);
                        }

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;looks the constant of &quot;3&quot; was chosen for some specific protocol changes in the past, but is it still needed ?&lt;/p&gt;</description>
                <environment></environment>
        <key id="66906">LU-15177</key>
            <summary> cs_update live batch update hung waiting for MDT recovery to complete</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="zam">Alexander Zarochentsev</assignee>
                                    <reporter username="zam">Alexander Zarochentsev</reporter>
                        <labels>
                    </labels>
                <created>Fri, 29 Oct 2021 14:20:33 +0000</created>
                <updated>Tue, 22 Mar 2022 14:35:41 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="316997" author="gerrit" created="Fri, 29 Oct 2021 14:40:35 +0000"  >&lt;p&gt;&quot;Alexander Zarochentsev &amp;lt;alexander.zarochentsev@hpe.com&amp;gt;&quot; uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/45408&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/45408&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-15177&quot; title=&quot; cs_update live batch update hung waiting for MDT recovery to complete&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-15177&quot;&gt;LU-15177&lt;/a&gt; ldlm: do not check patch version&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: cae10c33a8672d72a4b2c07cc8af14e51b7a362c&lt;/p&gt;</comment>
                            <comment id="317076" author="adilger" created="Sat, 30 Oct 2021 00:51:51 +0000"  >&lt;p&gt;The version delta was chosen somewhat arbitrarily.  There really should not be a significant version skew between MDS versions, as this is &lt;b&gt;never&lt;/b&gt; tested.  Even with rolling upgrades, it is typical to failover 1/2 of the MDTs to their backup, upgrade half of the RPMs, then failover all MDTs to their peer and upgrade the other half of the peers.  Since there is also not currently good support for DNE to work with offline MDTs (i.e. the system will wait for all MDTs to recover before it is usable), doing something like upgrading only 1/4 of the MDS nodes doesn&apos;t reduce downtime at all, but rather lengthens the downtime.&lt;/p&gt;

&lt;p&gt;I&apos;m curious why you would want to do this?&lt;/p&gt;</comment>
                    </comments>
                    <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|i028tj:</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>