<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:36:03 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-17514] parameter hint for expected number of connected clients</title>
                <link>https://jira.whamcloud.com/browse/LU-17514</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;It would be useful to have a variable that can be set early in startup (e.g. libcfs module parameter that is also a tunable parameter) that gives the system a hint on how many clients will be mounting the filesystem.&lt;/p&gt;

&lt;p&gt;While we try to tune filesystem parameters dynamically, sometimes that is complex to get right from the start, and by the time 1000 or 10000 clients have connected, then the values used when 10 or 100 clients had mounted are no longer optimal.  For example, &lt;tt&gt;conns_per_peer&lt;/tt&gt; at the LNet level could be 4 for 100 clients but should be 1 for 10000 clients or the servers can run out of TCP ports and have too many open sockets.  Similarly, &lt;tt&gt;at_min&lt;/tt&gt; should be low (5s) for smaller clusters for faster recovery, but with 10000 clients it should be larger (15s+), but since it is only set at mount time there is no easy way to update it on remote clients afterward.&lt;/p&gt;

&lt;p&gt;Having a simple parameter set in {{/etc/modprobe.d/lustre.conf, like:&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;options libcfs expected_clients=10000
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;gives us a ballpark figure to work with.  That doesn&apos;t obviate the need for dynamic tuning of parameters at runtime, but establishes some expectations for what is not obvious when the first 10 (of 10000) clients are mounting the filesystem.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80710">LU-17514</key>
            <summary>parameter hint for expected number of connected clients</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="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Wed, 7 Feb 2024 22:22:17 +0000</created>
                <updated>Wed, 7 Feb 2024 22:28:46 +0000</updated>
                                            <version>Lustre 2.17.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="403090" author="adilger" created="Wed, 7 Feb 2024 22:28:46 +0000"  >&lt;p&gt;Note that &lt;tt&gt;expected_clients&lt;/tt&gt; should never be mistaken as &quot;maximum possible number of clients&quot;, but only a ballpark figure for how many clients might be expected, and automatically tune parameters based on that expectation. &lt;/p&gt;

&lt;p&gt;There may be significantly more or fewer clients mounting the filesystem:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;2/3/4x as many mountpoints because of subdirectory mounting&lt;/li&gt;
	&lt;li&gt;2/4/8x as many socklnd connections because of multi-rail&lt;/li&gt;
	&lt;li&gt;far fewer mounts because of intermittent client mounting&lt;/li&gt;
	&lt;li&gt;far fewer connections because of LNet routing&lt;br/&gt;
but it is only intended to be an order-of-magnitude guideline and not cast in stone.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="80709">LU-17513</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80711">LU-17515</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="55145">LU-12064</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|i04aqn:</customfieldvalue>

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