<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:24:41 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-2375] MDS RPC stats should be under /proc/fs/lustre/mds</title>
                <link>https://jira.whamcloud.com/browse/LU-2375</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;In &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-718&quot; title=&quot;pull out ptlrpc service from mdt stack to create a mds layer&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-718&quot;&gt;&lt;del&gt;LU-718&lt;/del&gt;&lt;/a&gt; the MDS RPC service handling is being modified to be independent of the MDT devices.&lt;/p&gt;

&lt;p&gt;However, the current /proc files for the MDS RPC services are located under the target directory /proc/fs/lustre/mdt/&lt;/p&gt;
{fsname}
&lt;p&gt;-MDT0000/&lt;/p&gt;
{mdt,mdt_*}
&lt;p&gt;, but they do not relate to the target, but are instead node-wide RPC service thread statistics.  They should properly be under /proc/fs/lustre/mds and/or /proc/fs/lustre/mdt/MDS/ (as they were in 1.8).&lt;/p&gt;

&lt;p&gt;It wouldn&apos;t be a terrible idea to rename some of the service ports from their current names of &quot;mdt_mdss&quot;, &quot;mdt_mdsc&quot;, &quot;mdt_fld&quot;, etc to match the 1.8 names (&quot;mds&quot;, &quot;mds_readpage&quot;, &quot;mds_setattr&quot;) since they are properly &quot;MDS&quot; statistics.  However, there may be compatibility issues that prevent renaming all of these files immediately.  Creating symlinks is useful for transitioning to a new naming scheme in the future.&lt;/p&gt;

&lt;p&gt;I&apos;ve already submitted &lt;a href=&quot;http://review.whamcloud.com/4618&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/4618&lt;/a&gt; to link the OSS statistics under /proc/fs/lustre/oss from their current location in /proc/fs/lustre/ost/OSS/.&lt;/p&gt;</description>
                <environment></environment>
        <key id="16748">LU-2375</key>
            <summary>MDS RPC stats should be under /proc/fs/lustre/mds</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="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="10200">Won&apos;t Do</resolution>
                                        <assignee username="di.wang">Di Wang</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                            <label>mq313</label>
                    </labels>
                <created>Wed, 21 Nov 2012 17:00:52 +0000</created>
                <updated>Fri, 8 Oct 2021 23:42:28 +0000</updated>
                            <resolved>Fri, 8 Oct 2021 23:42:28 +0000</resolved>
                                    <version>Lustre 2.1.5</version>
                    <version>Lustre 2.4.1</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="48277" author="tappro" created="Thu, 22 Nov 2012 05:35:56 +0000"  >&lt;p&gt;considering unified server efforts that might be even better to move that under common /proc/fs/lustre/server as well as oss and mgs stats. Although we can use mds, oss and mgs separated proc directories if there are compatibility issues.&lt;/p&gt;</comment>
                            <comment id="50709" author="adilger" created="Thu, 17 Jan 2013 13:57:17 +0000"  >&lt;p&gt;Di, didn&apos;t you already have a patch for this?  What is the patch number?&lt;/p&gt;</comment>
                            <comment id="50721" author="di.wang" created="Thu, 17 Jan 2013 15:11:23 +0000"  >&lt;p&gt;Hmm, those RPC services are already located under /proc/fs/lustre/mds/MDS&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@testnode tests&amp;#93;&lt;/span&gt;# cat /proc/fs/lustre/mds/MDS/&lt;br/&gt;
mdt/          mdt_fld/      mdt_readpage/ mdt_seqm/     mdt_seqs/     mdt_setattr/  uuid          &lt;/p&gt;

&lt;p&gt;And I checked the code, in current implementation, these RPC service proc entry is registered in ptlrpc_register_service, since MDS will start these service, so these entry should be in MDS/ already.  Please correct me, if I miss the point. Thanks. &lt;/p&gt;</comment>
                            <comment id="51055" author="adilger" created="Wed, 23 Jan 2013 15:24:18 +0000"  >&lt;p&gt;Hmm, maybe I was looking at 2.1 instead of master:&lt;/p&gt;

&lt;p&gt;Lustre 2.1.3.50:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;find /proc/fs/lustre/md[dst] -name stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt_mds/stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt_fld/stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt_dtss/stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt_mdss/stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt_mdsc/stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt_setattr/stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt_readpage/stats
/proc/fs/lustre/mdt/myth-MDT0000/mdt/stats
/proc/fs/lustre/mdt/myth-MDT0000/exports/0@lo/stats
/proc/fs/lustre/mdt/myth-MDT0000/exports/192.168.20.159@tcp/stats
/proc/fs/lustre/mdt/myth-MDT0000/exports/192.168.20.147@tcp/stats
/proc/fs/lustre/mdt/myth-MDT0000/stats
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Lustre 2.3.58:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;find /proc/fs/lustre/md[dst] -name stats
/proc/fs/lustre/mds/MDS/mdt_fld/stats
/proc/fs/lustre/mds/MDS/mdt_seqm/stats
/proc/fs/lustre/mds/MDS/mdt_seqs/stats
/proc/fs/lustre/mds/MDS/mdt_setattr/stats
/proc/fs/lustre/mds/MDS/mdt_readpage/stats
/proc/fs/lustre/mds/MDS/mdt/stats
/proc/fs/lustre/mdt/testfs-MDT0000/exports/0@lo/stats
/proc/fs/lustre/mdt/testfs-MDT0000/stats
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I guess it makes more sense to add a symlink in 2.1.5 from /proc/fs/lustre/mds/MDS/mds_* to /proc/fs/lustre/mdt/$fsname-MDT0000/mdt_* to keep more continuity of the stats location, since this is also where stats were located in 1.8.&lt;/p&gt;

&lt;p&gt;Should the stats files in 2.4 also be named &quot;mds_&lt;b&gt;&quot; instead of &quot;mdt_&lt;/b&gt;&quot;, since they are really per-MDS statistics under .../mds/MDS?  That would get them 100% back in line with the 1.8 stats files names.&lt;/p&gt;</comment>
                            <comment id="315088" author="adilger" created="Fri, 8 Oct 2021 23:42:28 +0000"  >&lt;p&gt;Compatibility with 1.8 is no longer a concern.&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|hzvcnz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5641</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>