<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:21:57 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-2051] verify lod_alloc_rr() code is doing what we want</title>
                <link>https://jira.whamcloud.com/browse/LU-2051</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Per comments in &lt;a href=&quot;http://review.whamcloud.com/4058&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/4058&lt;/a&gt;, we need to have some discussion/investigation on how the lod_alloc_rr() code is behaving under various circumstances.  It isn&apos;t clear that it is as flexible as the previous lov alloc_rr/osc_precreate behaviour, and this is an area that has needed a lot of tuning in the past to work well under a variety of conditions.&lt;/p&gt;</description>
                <environment></environment>
        <key id="16181">LU-2051</key>
            <summary>verify lod_alloc_rr() code is doing what we want</summary>
                <type id="7" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/task_agile.png">Technical task</type>
                            <parent id="13933">LU-1303</parent>
                                    <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</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="bzzz">Alex Zhuravlev</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Fri, 28 Sep 2012 18:30:23 +0000</created>
                <updated>Mon, 29 May 2017 04:10:04 +0000</updated>
                            <resolved>Mon, 29 May 2017 04:10:04 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                    <fixVersion>Lustre 2.4.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="46422" author="bzzz" created="Fri, 12 Oct 2012 01:24:36 +0000"  >&lt;p&gt;any specific concern ?&lt;/p&gt;</comment>
                            <comment id="46508" author="adilger" created="Sat, 13 Oct 2012 12:25:03 +0000"  >&lt;p&gt;Several previous bugs come to mind:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;ensure that precreate count is scaling with load&lt;/li&gt;
	&lt;li&gt;precreate starts early enough so that MDS create doesn&apos;t stall&lt;/li&gt;
	&lt;li&gt;skip inactive or degraded OSTs
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;ideally ZFS OSD can set this flag itself?&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;RR allocation is properly balancing objects on OSTs&lt;/li&gt;
	&lt;li&gt;QOS space balance works properly with imbalanced OSTs&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I think there are tests foremost of these conditions, but it would be good to verify this. &lt;/p&gt;</comment>
                            <comment id="129670" author="bzzz" created="Wed, 7 Oct 2015 07:40:51 +0000"  >&lt;p&gt;Andreas, do you think we still need to do this? there was a patch from Seagate (landed now) where they improved RR and they reported it&apos;s now doing much more predictable.&lt;/p&gt;</comment>
                            <comment id="129804" author="adilger" created="Thu, 8 Oct 2015 09:48:14 +0000"  >&lt;p&gt;The lod_alloc_rr() code itself was fixed to avoid races in updating the state, but it still isn&apos;t clear if things like OST object precreation is working optimally (e.g. precreate starts early enough).  In particular, there was a benefit shown at LUG a long time ago to start precreate when only 1/4 of the MDS objects were used, rather than waiting until 1/2 were used.&lt;/p&gt;

&lt;p&gt;The ZFS DEGRADED flag setting is &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-4277&quot; title=&quot;Integrate ZFS zpool resilver status with OFD OS_STATE_DEGRADED flag&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-4277&quot;&gt;&lt;del&gt;LU-4277&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
The QOS balance and RR balance is &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9&quot; title=&quot;Optimize weighted QOS Round-Robin allocator&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9&quot;&gt;LU-9&lt;/a&gt;.&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|hzv4m7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4281</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>