<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:32: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-10203] A stonith device  &apos;Monitor&apos;  operation report &quot;Time Out&quot; in Lustre HA cluster with pacemaker </title>
                <link>https://jira.whamcloud.com/browse/LU-10203</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Hi All,&lt;/p&gt;

&lt;p&gt;We have got one problem about using stonith device in Lustre HA (MGS/MDS) cluster with pacemaker.&lt;/p&gt;

&lt;p&gt;Our stonith device often reports &quot;Time out&quot; errors in &quot;Monitor&quot; operation, and then fails to start.&lt;/p&gt;

&lt;p&gt;Finally, it is in &quot;Stopped&quot; state.&lt;/p&gt;

&lt;p&gt;Please kindly give us suggestions for debugging this issue.&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://jira.whamcloud.com/secure/attachment/28601/28601_Selection_018.png&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt; &#160;&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://jira.whamcloud.com/secure/attachment/28600/28600_Selection_017.png&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;br/&gt;
 &#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment>REHL7.3, Lustre 2.10.0 </environment>
        <key id="49156">LU-10203</key>
            <summary>A stonith device  &apos;Monitor&apos;  operation report &quot;Time Out&quot; in Lustre HA cluster with pacemaker </summary>
                <type id="9" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/undefined.png">Question/Request</type>
                                            <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="4">Incomplete</resolution>
                                        <assignee username="brian">Brian Murrell</assignee>
                                    <reporter username="sebg-crd-pm">sebg-crd-pm</reporter>
                        <labels>
                    </labels>
                <created>Tue, 7 Nov 2017 03:53:25 +0000</created>
                <updated>Tue, 27 Feb 2018 14:24:21 +0000</updated>
                            <resolved>Tue, 27 Feb 2018 14:24:21 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="212949" author="adilger" created="Tue, 7 Nov 2017 05:34:23 +0000"  >&lt;p&gt;Since the Lustre MDS code is running in the kernel, it is possible that the HA threads running on the server can be starved if there is a high load, so the current timeout is not long enough.  You might consider to update the token timeout in the &lt;tt&gt;/etc/corosync/corosync.conf&lt;/tt&gt; file.  &lt;/p&gt;</comment>
                            <comment id="213243" author="pjones" created="Thu, 9 Nov 2017 16:30:20 +0000"  >&lt;p&gt;Brian&lt;/p&gt;

&lt;p&gt;Any additional advice to provide here?&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="213260" author="brian" created="Thu, 9 Nov 2017 18:47:20 +0000"  >&lt;p&gt;Is this a Pacemaker configuration that IML constructed or one that you built up yourself?&lt;/p&gt;

&lt;p&gt;In any case, it looks like your fencing devices are not functioning properly.&#160; It could be a configuration problem or unfortunately just par for the course for IPMI fencing devices.&lt;/p&gt;</comment>
                            <comment id="214190" author="brian" created="Mon, 20 Nov 2017 21:18:39 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.whamcloud.com/secure/ViewProfile.jspa?name=sebg-crd-pm&quot; class=&quot;user-hover&quot; rel=&quot;sebg-crd-pm&quot;&gt;sebg-crd-pm&lt;/a&gt;.&#160; Do you have any more information&#160;you can add to&#160;this ticket or shall I close it?&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="28600" name="Selection_017.png" size="38811" author="sebg-crd-pm" created="Tue, 7 Nov 2017 03:41:12 +0000"/>
                            <attachment id="28601" name="Selection_018.png" size="71757" author="sebg-crd-pm" created="Tue, 7 Nov 2017 03:41:13 +0000"/>
                    </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|hzzn87:</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>