<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:38:30 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-3970] Add procfs interface for clearing lustre caches in parallel</title>
                <link>https://jira.whamcloud.com/browse/LU-3970</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Cray experienced slowness clearing the lustre caches after job termination.  This slowness is a result of clearing the caches for each namespace in series.  Lustre should provide a high-level procfs interface which clears lustre caches across namespaces in parallel and returns when all caches are cleared.&lt;/p&gt;

&lt;p&gt;The interface should be at /proc/fs/lustre/ldlm/drop_caches, and when written to, it must clear all lustre caches in parallel and return when finished.&lt;/p&gt;

&lt;p&gt;It must have the same effect as the following, but in parallel:&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;for LRU in $(ls /proc/fs/lustre/ldlm/namespaces/*osc*/lru_size); do
    echo clear &amp;gt; $LRU
done

for LRU in $(ls /proc/fs/lustre/ldlm/namespaces/*mdc*/lru_size); do
    echo clear &amp;gt; $LRU
done
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="21007">LU-3970</key>
            <summary>Add procfs interface for clearing lustre caches in parallel</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="yujian">Jian Yu</assignee>
                                    <reporter username="haasken">Ryan Haasken</reporter>
                        <labels>
                            <label>patch</label>
                            <label>performance</label>
                    </labels>
                <created>Wed, 18 Sep 2013 16:19:07 +0000</created>
                <updated>Tue, 9 Feb 2016 15:47:19 +0000</updated>
                            <resolved>Fri, 18 Jul 2014 21:47:49 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="66930" author="haasken" created="Wed, 18 Sep 2013 16:20:15 +0000"  >&lt;p&gt;I am working on uploading a patch to Gerrit.&lt;/p&gt;</comment>
                            <comment id="67124" author="green" created="Fri, 20 Sep 2013 16:06:23 +0000"  >&lt;p&gt;I wonder if why doing hte echos in parallel won&apos;t work?&lt;/p&gt;</comment>
                            <comment id="67130" author="haasken" created="Fri, 20 Sep 2013 16:17:58 +0000"  >&lt;p&gt;That would work as well.  However, Cray&apos;s ALPS (Application Level Placement Scheduler) team requested that Lustre provide a higher level interface which clears all the caches in parallel.  Do you feel that this is an appropriate enhancement?  I&apos;ve already tested a patch, but I am still learning how to submit it to Gerrit for review.&lt;/p&gt;</comment>
                            <comment id="67775" author="haasken" created="Thu, 26 Sep 2013 22:20:30 +0000"  >&lt;p&gt;I have submitted a patch to Gerrit: &lt;a href=&quot;http://review.whamcloud.com/#/c/7783/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/7783/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="85515" author="haasken" created="Mon, 2 Jun 2014 20:52:09 +0000"  >&lt;p&gt;Can somebody please mark this bug related to &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5134&quot; title=&quot;Add option to lctl set_param for setting parameters in parallel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5134&quot;&gt;&lt;del&gt;LU-5134&lt;/del&gt;&lt;/a&gt;?  &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5134&quot; title=&quot;Add option to lctl set_param for setting parameters in parallel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5134&quot;&gt;&lt;del&gt;LU-5134&lt;/del&gt;&lt;/a&gt; will resolve this issue by allowing lctl set_param to spawn threads in user space when setting lru_size=clear.&lt;/p&gt;</comment>
                            <comment id="89545" author="spitzcor" created="Fri, 18 Jul 2014 21:32:57 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#/c/7783&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/7783&lt;/a&gt; is abandoned in favor of the approach taken with &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5134&quot; title=&quot;Add option to lctl set_param for setting parameters in parallel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5134&quot;&gt;&lt;del&gt;LU-5134&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This bug ought to be closed now.  Jian, can you please make it so?&lt;/p&gt;</comment>
                            <comment id="89550" author="pjones" created="Fri, 18 Jul 2014 21:47:49 +0000"  >&lt;p&gt;ok Cory&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="24991">LU-5134</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_10030" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Epic/Theme</customfieldname>
                        <customfieldvalues>
                                        <label>Performance</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzw327:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10579</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>