<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:06:45 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-14090] lctl replace_nids and starting target with local copy of logs</title>
                <link>https://jira.whamcloud.com/browse/LU-14090</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;There is a feature that starts a target with a local copy of&lt;br/&gt;
config log in order to avoid a delay in communicating with&lt;br/&gt;
an MGS and to load mgs log updates later on.&lt;br/&gt;
However, that feature is not always useful&lt;/p&gt;

&lt;p&gt;When replace_nids adds records with new nids it does not&lt;br/&gt;
append remote config logs but overwrite corresponding&lt;br/&gt;
records in place. If a target starts using local config&lt;br/&gt;
log - it gets confused by outdated nids.&lt;/p&gt;

&lt;p&gt;Let&apos;s add tunefs.lustre --nolocallogs key that&lt;br/&gt;
sets nolocallogs flag, which says ignore local configs copy.&lt;br/&gt;
The flag is reset once new logs are uploaded from MGS.&lt;/p&gt;

&lt;p&gt;tunefs.lustre --nolocallogs is suggested to be executed on&lt;br/&gt;
targets together with replace_nids on MGS.&lt;/p&gt;</description>
                <environment></environment>
        <key id="61424">LU-14090</key>
            <summary>lctl replace_nids and starting target with local copy of logs</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="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="artem_blagodarenko">Artem Blagodarenko</assignee>
                                    <reporter username="artem_blagodarenko">Artem Blagodarenko</reporter>
                        <labels>
                            <label>patch</label>
                    </labels>
                <created>Thu, 29 Oct 2020 13:00:17 +0000</created>
                <updated>Tue, 6 Apr 2021 03:41:51 +0000</updated>
                            <resolved>Tue, 6 Apr 2021 03:41:51 +0000</resolved>
                                                    <fixVersion>Lustre 2.15.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="283624" author="gerrit" created="Thu, 29 Oct 2020 13:04:33 +0000"  >&lt;p&gt;Artem Blagodarenko (artem.blagodarenko@hpe.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/40448&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/40448&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-14090&quot; title=&quot;lctl replace_nids and starting target with local copy of logs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-14090&quot;&gt;&lt;del&gt;LU-14090&lt;/del&gt;&lt;/a&gt; mgs: no local logs flag&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 88b959844c018aba667b384087c3559c7925d8b0&lt;/p&gt;</comment>
                            <comment id="295782" author="adilger" created="Tue, 23 Mar 2021 08:32:45 +0000"  >&lt;p&gt;The root of this problem is that the &quot;&lt;tt&gt;replace_nids&lt;/tt&gt;&quot; code is breaking one of the assumptions of the config llog - that changes are added to the end, and old config records are not rewritten.  That is why &lt;tt&gt;replace_nids&lt;/tt&gt; needs all of the servers and clients to be unmounted when rewriting the logs, which is inconvenient.  Something like &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7668&quot; title=&quot;permanently remove deactivated OSTs from configuration log&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7668&quot;&gt;&lt;del&gt;LU-7668&lt;/del&gt;&lt;/a&gt; &quot;&lt;tt&gt;del_ost&lt;/tt&gt;&quot; is OK because it is only cancelling the old records, and the next time that the config llog is processed it will be as if the records never existed, which is better than adding OSTs and later removing them.&lt;/p&gt;

&lt;p&gt;I think a better long-term solution for changing the server NIDs is to get patch &lt;a href=&quot;https://review.whamcloud.com/40736&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/40736&lt;/a&gt; &quot;&lt;tt&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10360&quot; title=&quot;use Imperative Recovery logs for client-&amp;gt;MDT/OST connections&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10360&quot;&gt;LU-10360&lt;/a&gt; mgs: Mount to dynamically added networks&lt;/tt&gt;&quot; updated and landed.  That avoids the need to manually update the config logs if the server NIDs are changing, and allows clients to keep using the filesystem even if the server NIDs are changing at runtime (with a timeout and recovery if the NID change is sudden, but it could be transparent if both the old and new NID were valid for some time).&lt;/p&gt;</comment>
                            <comment id="297860" author="gerrit" created="Tue, 6 Apr 2021 03:01:57 +0000"  >&lt;p&gt;Oleg Drokin (green@whamcloud.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/40448/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/40448/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-14090&quot; title=&quot;lctl replace_nids and starting target with local copy of logs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-14090&quot;&gt;&lt;del&gt;LU-14090&lt;/del&gt;&lt;/a&gt; mgs: no local logs flag&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: f38f09e02a05c82718344ad86f80a4a0f399af9d&lt;/p&gt;</comment>
                            <comment id="297881" author="pjones" created="Tue, 6 Apr 2021 03:41:51 +0000"  >&lt;p&gt;Landed for 2.15&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="49665">LU-10360</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="34119">LU-7668</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|i01do7:</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>