<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:11: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-918] ensure that BRW requests prevent lock timeout</title>
                <link>https://jira.whamcloud.com/browse/LU-918</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;To avoid lock timeouts in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-874&quot; title=&quot;Client eviction on lock callback timeout &quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-874&quot;&gt;&lt;del&gt;LU-874&lt;/del&gt;&lt;/a&gt;, one point of discussion was to ensure that BRW requests under a DLM extent lock ensure that the client does not get evicted, even under heavy OST load.  The best option is if a client sends a BRW request under a DLM lock that the lock timeout is stopped entirely for that lock until the IO has completed.  That would avoid overhead from continually refresh the DLM lock during operation, but may be more complex to implement than having the DLM lock timeout first check for BRW requests in the hpreq queue or in-progress by an OSS thread that would refresh it.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12655">LU-918</key>
            <summary>ensure that BRW requests prevent lock timeout</summary>
                <type id="7" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/task_agile.png">Technical task</type>
                            <parent id="12519">LU-874</parent>
                                    <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="jay">Jinshan Xiong</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Tue, 13 Dec 2011 04:34:34 +0000</created>
                <updated>Mon, 30 Jan 2012 14:02:48 +0000</updated>
                            <resolved>Mon, 30 Jan 2012 14:02:38 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                            <comments>
                            <comment id="24574" author="adilger" created="Tue, 13 Dec 2011 04:36:36 +0000"  >&lt;p&gt;Add dependency on OSS read cache issues&lt;/p&gt;</comment>
                            <comment id="27600" author="pjones" created="Mon, 30 Jan 2012 13:21:03 +0000"  >&lt;p&gt;Jinshan&lt;/p&gt;

&lt;p&gt;Did you cover this already under one of your LU874 patches?&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="27610" author="jay" created="Mon, 30 Jan 2012 13:52:03 +0000"  >&lt;p&gt;I solved this problem by refreshing lock timeout each time.&lt;/p&gt;

&lt;p&gt;Yes, I have ever had a patch to take locks out of waiting list if a covering RPC is coming. However, this way will have to modify the state of dlm lock, for example, to remember how many active RPCs existing. That&apos;s a stateful implementation.&lt;/p&gt;

&lt;p&gt;After thinking about it, I decided to stay with current stateless implementation because of:&lt;br/&gt;
1. less possibilities of producing bugs;&lt;br/&gt;
2. lock timeout is rare event in the system, so performance shouldn&apos;t be a problem.&lt;/p&gt;

&lt;p&gt;How do you think?&lt;/p&gt;</comment>
                            <comment id="27611" author="adilger" created="Mon, 30 Jan 2012 13:57:59 +0000"  >&lt;p&gt;I think if we have a simple solution to the problem that works, then we don&apos;t need a complex solution to the problem.  If there is nothing here left to be fixed, then this bug can be closed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="10112">LU-15</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11158">LU-410</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|hzw0bz:</customfieldvalue>

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