<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:24:48 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-2389] move sync out of facet_failover</title>
                <link>https://jira.whamcloud.com/browse/LU-2389</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Comments from Andreas,&lt;br/&gt;
&quot;in facet_failover() I still don&apos;t agree with the inclusion of sync before triggering failover (which is apparently from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-924&quot; title=&quot;Test failure on test suite recovery-small, subtest test_105&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-924&quot;&gt;&lt;del&gt;LU-924&lt;/del&gt;&lt;/a&gt;). That is not how failover works in real life and I think it will hide bugs during testing. Also, a change like that does not belong in a patch which describes only changes for DNE testing. Per inspections in the &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-924&quot; title=&quot;Test failure on test suite recovery-small, subtest test_105&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-924&quot;&gt;&lt;del&gt;LU-924&lt;/del&gt;&lt;/a&gt; patch (which is where it should be landed), there are AFAIK only a very small number of tests that may be affected by this problem (basically only after a client first mounts or reconnects after eviction and then does nothing in the few seconds before another eviction) so I&apos;d rather add explicit sync to those tests than for every test, or add some mechanism to only force sync updates to last_rcvd for connections during testing.&quot;&lt;/p&gt;</description>
                <environment></environment>
        <key id="16772">LU-2389</key>
            <summary>move sync out of facet_failover</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="3">Duplicate</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="di.wang">Di Wang</reporter>
                        <labels>
                    </labels>
                <created>Tue, 27 Nov 2012 01:11:57 +0000</created>
                <updated>Tue, 27 Nov 2012 15:25:31 +0000</updated>
                            <resolved>Tue, 27 Nov 2012 15:25:31 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="48433" author="adilger" created="Tue, 27 Nov 2012 15:24:59 +0000"  >&lt;p&gt;Hmm, there is some confusion here.  facet_failover() in master does not have any sync calls in it, since commit 5458e96d82a103315095c234c22de0efff7956af landed via &lt;a href=&quot;http://review.whamcloud.com/3239&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/3239&lt;/a&gt; in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1582&quot; title=&quot;replay-ost-single.sh test_8b: client stuck with -115 (-EINPROGRESS)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1582&quot;&gt;&lt;del&gt;LU-1582&lt;/del&gt;&lt;/a&gt;.  It is only in your patch that sync calls are being added.&lt;/p&gt;</comment>
                            <comment id="48434" author="adilger" created="Tue, 27 Nov 2012 15:25:31 +0000"  >&lt;p&gt;Was fixed in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1582&quot; title=&quot;replay-ost-single.sh test_8b: client stuck with -115 (-EINPROGRESS)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1582&quot;&gt;&lt;del&gt;LU-1582&lt;/del&gt;&lt;/a&gt;, we just need to avoid adding them back.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="15089">LU-1582</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|hzvcsv:</customfieldvalue>

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