<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:19: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-8609] connect client health_check file to client import state</title>
                <link>https://jira.whamcloud.com/browse/LU-8609</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;The &lt;tt&gt;/proc/fs/lustre/health_check&lt;/tt&gt; file on the client does not currently report anything besides &lt;tt&gt;health=healthy&lt;/tt&gt;, since this is only wired up to report request handling state on the server nodes, and if the ldiskfs filesystem has been mounted read-only.&lt;/p&gt;

&lt;p&gt;It would be desirable to have &lt;tt&gt;health_check&lt;/tt&gt; print out the OSC and MDC import states on the client (e.g. if &lt;tt&gt;imp-&amp;gt;imp_state != LUSTRE_IMP_FULL&lt;/tt&gt; as long as the import is not marked &lt;tt&gt;imp_deactive&lt;/tt&gt;).  &lt;/p&gt;</description>
                <environment></environment>
        <key id="39813">LU-8609</key>
            <summary>connect client health_check file to client import state</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="emoly.liu">Emoly Liu</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Tue, 13 Sep 2016 17:41:13 +0000</created>
                <updated>Mon, 27 Aug 2018 15:02:54 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="218971" author="emoly.liu" created="Wed, 24 Jan 2018 04:05:38 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/secure/ViewProfile.jspa?name=adilger&quot; class=&quot;user-hover&quot; rel=&quot;adilger&quot;&gt;adilger&lt;/a&gt;, &lt;br/&gt;
What kind of OSC and MDC import states on the client should be printed by health_check? Is the following format OK?&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;health_check=healthy
target state:
  lustre-OST0000_UUID: FULL
  lustre-OST0001_UUID: FULL
  ...
  MGS: FULL
  ...   
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="218996" author="simmonsja" created="Wed, 24 Jan 2018 14:25:57 +0000"  >&lt;p&gt;This over laps with something Andreas suggested. In that we create two files for the health_checker. One to report the health and the second in debugfs that has more in depth details why it failed.&lt;/p&gt;</comment>
                            <comment id="219229" author="adilger" created="Fri, 26 Jan 2018 04:38:17 +0000"  >&lt;p&gt;James, why not just move the whole file to debugfs?  There are already &quot;&lt;tt&gt;lfs osts}&quot; and &quot;{{lfs mdts&lt;/tt&gt;&quot; commands to print this state for users, the &quot;health_check&quot; file is mostly for HA monitoring scripts.&lt;/p&gt;</comment>
                            <comment id="219230" author="adilger" created="Fri, 26 Jan 2018 04:46:46 +0000"  >&lt;p&gt;Hmm, looking at this more closely, it seems that the &lt;tt&gt;health_check&lt;/tt&gt; file never prints anything but &quot;health=healthy&quot; even on the server under normal circumstances, and I guess this shouldn&apos;t change.  If there is a problem it will print &quot;LBUG&quot; or &quot;NOT HEALTHY&quot;.  What is more important is that the client report &quot;health=NOT HEALTHY&quot; if the import states are bad, not that individual connection states are printed.&lt;/p&gt;</comment>
                            <comment id="232621" author="simmonsja" created="Mon, 27 Aug 2018 15:02:54 +0000"  >&lt;p&gt;Link the work of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10756&quot; title=&quot;Send Uevents for interesting Lustre changes&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10756&quot;&gt;LU-10756&lt;/a&gt; since a patch exist that send uevents about the client imports state. Admins can setup udev rules to log or handle specific states. That is a more dynamic approach. We can supply more in depth information related to this ticket.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="36381">LU-8066</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="51084">LU-10756</issuekey>
        </issuelink>
                            </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|hzyof3:</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>