<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:46:58 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-11792] Causal HSM request processing</title>
                <link>https://jira.whamcloud.com/browse/LU-11792</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Current HSM llapi provides a interface llapi_hsm_request for a client to submit HSM requests to Lustre, but it does not handle well for the HSM requests with causality relationship. For example, a client send a HSM resotre request immediatly followed with a HSM archive request (or a HSM remove request followed with a HSM resotre request), since the requests has causal relationship, the MDT will ignore to process the subsequent HSM request.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
#!/bin/bash
lfs hsm_restore $1
lfs hsm_remove $1
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;


&lt;p&gt;One use case for this requirement is evicting cached file from PCC (actually a HSM backend). To free up space for new files, a client deployed with PCC may want to send a HSM restore and HSM remove together to MDT CDT to remove the corresponding archive from PCC device.&lt;br/&gt;
In the sanity-hsm, it provdes a no elegance way to hanlde this problem to query the processing state the the HSM request via wait_request_state of &quot;hsm.actions&quot;. Or similarly, the client can query to HSM state of a file until the HSM state of the file transimt a coresponding appropriate state (the correspond HSM request is finished), and then execute the following HSM request with causal relationship. But All these methods are not good for perfomance.&lt;/p&gt;

&lt;p&gt;Here open this ticket to track the discusses and solution for this problem.&lt;/p&gt;</description>
                <environment></environment>
        <key id="54316">LU-11792</key>
            <summary>Causal HSM request processing</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="qian_wc">Qian Yingjin</reporter>
                        <labels>
                            <label>HSM</label>
                    </labels>
                <created>Mon, 17 Dec 2018 09:23:13 +0000</created>
                <updated>Wed, 19 Dec 2018 15:29:09 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                    <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|i0085r:</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>