<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:02:20 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-13564] WBC: inode and space grant mechanism under WBC</title>
                <link>https://jira.whamcloud.com/browse/LU-13564</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Under WBC, all metadata and data are cached in MemFS, not being flushed to MDT and OSTs. To void running out of the server space, it needs to design a grant mechanism similar to current OST space grant to control inodes grant from MDT.&lt;br/&gt;
The following points need to consider for grant mechanism under WBC:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;In the DNE environment, how to select MDT for the newly creation? Maybe the whole root WBC subtree should be located on the same MDT?&lt;/li&gt;
	&lt;li&gt;In current WBC implementation, the data objects for the regular file will be created when flush the file to MDT and the layout will be instantiated also. This can be optimized as follows:
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;It could send the current size of the file to MDT, then it can determine how to allocate data object more clear accordingly.&lt;/li&gt;
		&lt;li&gt;Delay to allocate data objects and instantiate the layout for the regular file unless it is necessary.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="59201">LU-13564</key>
            <summary>WBC: inode and space grant mechanism under WBC</summary>
                <type id="7" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/task_agile.png">Technical task</type>
                            <parent id="51932">LU-10938</parent>
                                    <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="qian_wc">Qian Yingjin</reporter>
                        <labels>
                    </labels>
                <created>Fri, 15 May 2020 15:23:01 +0000</created>
                <updated>Wed, 15 Feb 2023 11:52:58 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="270400" author="adilger" created="Sat, 16 May 2020 00:08:16 +0000"  >&lt;p&gt;As a general rule, it is much more efficient to keep subdirectory trees on a single MDT, since this avoids expensive cross-MDT transactions.  The good thing with metadata vs. data, is that it is relatively easy to change over to a new MDT if one is getting full by creating a remote directory entry.&lt;/p&gt;

&lt;p&gt;There is already a protocol for OSTs to grant clients space for data at connect time, and the same should be used for grant from the MDTs.  Since DoM is using the OST read/write protocol to the MDS, it should be possible to use this for data grant, but some changes may be needed to add in metadata grant (e.g. inodes).&lt;/p&gt;

&lt;p&gt;As for MDT/OST selection, the client already has &quot;LMV QOS&quot; logic for directory selection with &quot;&lt;tt&gt;lfs mkdir -i -1&lt;/tt&gt;&quot; so this can be reused (&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-13417&quot; title=&quot;DNE3: mkdir() automatically create remote directory on MDS which has more space&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-13417&quot;&gt;&lt;del&gt;LU-13417&lt;/del&gt;&lt;/a&gt;).&lt;/p&gt;</comment>
                            <comment id="342172" author="gerrit" created="Mon, 1 Aug 2022 09:52:46 +0000"  >&lt;p&gt;&quot;Yingjin Qian &amp;lt;qian@ddn.com&amp;gt;&quot; uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/48099&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/48099&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-13564&quot; title=&quot;WBC: inode and space grant mechanism under WBC&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-13564&quot;&gt;LU-13564&lt;/a&gt; wbc: check low inode threshold for MDT&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 0cdacc7e46243ef6e541ee8a678dd9dbf6783ad7&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </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_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i010gv:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>