forked from docs/doc-exports
Yang, Tong
3b1f73dece
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Yang, Tong <yangtong2@huawei.com> Co-committed-by: Yang, Tong <yangtong2@huawei.com>
115 lines
24 KiB
HTML
115 lines
24 KiB
HTML
<a name="ALM-14013"></a><a name="ALM-14013"></a>
|
|
|
|
<h1 class="topictitle1">ALM-14013 Failed to Update the NameNode FsImage File</h1>
|
|
<div id="body29984249"><div class="section" id="ALM-14013__s1689cfea021141bb8602e5c9acef0a52"><h4 class="sectiontitle">Description</h4><p id="ALM-14013__en-us_topic_0070543650_p28768780">HDFS metadata is stored in the FsImage file of the NameNode data directory, which is specified by the <strong id="ALM-14013__en-us_topic_0070543650_b57592428">dfs.namenode.name.dir</strong> configuration item. The standby NameNode periodically combines existing FsImage files and Editlog files stored in the JournalNode to generate a new FsImage file, and then pushes the new FsImage file to the data directory of the active NameNode. This period is specified by the <strong id="ALM-14013__en-us_topic_0070543650_b48569804">dfs.namenode.checkpoint.period</strong> configuration item of HDFS. The default value is 3600s, namely, one hour. If the FsImage file in the data directory of the active NameNode is not updated, the HDFS metadata combination function is abnormal and requires rectification.</p>
|
|
<p id="ALM-14013__en-us_topic_0070543650_p34475053">On the active NameNode, the system checks the FsImage file information every five minutes. This alarm is generated when no FsImage file is generated within three combination periods.</p>
|
|
<p id="ALM-14013__en-us_topic_0070543650_p41840024">This alarm is cleared when a new FsImage file is generated and pushed to the active NameNode, which indicates that the HDFS metadata combination function can be properly used.</p>
|
|
</div>
|
|
<div class="section" id="ALM-14013__sbe06d15ff56840c3ba20e25f24d470b2"><h4 class="sectiontitle">Attribute</h4>
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ALM-14013__en-us_topic_0070543650_table33598809" frame="border" border="1" rules="all"><thead align="left"><tr id="ALM-14013__en-us_topic_0070543650_row62616296"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.1"><p id="ALM-14013__en-us_topic_0070543650_p38755211">Alarm ID</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.2"><p id="ALM-14013__en-us_topic_0070543650_p52164395">Alarm Severity</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.3"><p id="ALM-14013__en-us_topic_0070543650_p64566447">Automatically Cleared</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="ALM-14013__en-us_topic_0070543650_row62499712"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.1 "><p id="ALM-14013__en-us_topic_0070543650_p29311877">14013</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.2 "><p id="ALM-14013__en-us_topic_0070543650_p25451814">Major</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.3 "><p id="ALM-14013__en-us_topic_0070543650_p48331085">Yes</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div class="section" id="ALM-14013__s52a785f6f3b447d7b281951aab43c82c"><h4 class="sectiontitle">Parameters</h4>
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ALM-14013__en-us_topic_0070543650_table22503775" frame="border" border="1" rules="all"><thead align="left"><tr id="ALM-14013__en-us_topic_0070543650_row2834622"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.3.2.1.3.1.1"><p id="ALM-14013__en-us_topic_0070543650_p28277831">Name</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.3.2.1.3.1.2"><p id="ALM-14013__en-us_topic_0070543650_p8803009">Meaning</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="ALM-14013__row177954215357"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-14013__p192431315431">Source</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-14013__p692551319435">Specifies the cluster for which the alarm is generated.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ALM-14013__en-us_topic_0070543650_row41955156"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-14013__en-us_topic_0070543650_p42924455">ServiceName</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-14013__en-us_topic_0070543650_p54328802">Specifies the service for which the alarm is generated.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ALM-14013__en-us_topic_0070543650_row19197174"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-14013__en-us_topic_0070543650_p11467298">RoleName</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-14013__en-us_topic_0070543650_p56435913">Specifies the role for which the alarm is generated.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ALM-14013__en-us_topic_0070543650_row38161175"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-14013__en-us_topic_0070543650_p4047493">HostName</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-14013__en-us_topic_0070543650_p59411491">Specifies the host for which the alarm is generated.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ALM-14013__en-us_topic_0070543650_row64941371"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-14013__p8343823141916">NameServiceName</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-14013__en-us_topic_0070543642_p6743286">Specifies the NameService for which the alarm is generated.</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div class="section" id="ALM-14013__s4416b4deee244bb9aa10dbb8feb3406a"><h4 class="sectiontitle">Impact on the System</h4><p id="ALM-14013__en-us_topic_0070543650_p29386158">If the FsImage file in the data directory of the active NameNode is not updated, the HDFS metadata combination function is abnormal and requires rectification. If it is not rectified, the Editlog files increase continuously after HDFS runs for a period. In this case, HDFS restart is time-consuming because a large number of Editlog files need to be loaded. In addition, this alarm also indicates that the standby NameNode is abnormal and the NameNode high availability (HA) mechanism becomes invalid. When the active NameNode is faulty, the HDFS service becomes unavailable.</p>
|
|
</div>
|
|
<div class="section" id="ALM-14013__s391973199c69496182134119c0f86322"><h4 class="sectiontitle">Possible Causes</h4><ul id="ALM-14013__en-us_topic_0070543650_ul31468573"><li id="ALM-14013__en-us_topic_0070543650_li14781704">The standby NameNode is stopped.</li><li id="ALM-14013__en-us_topic_0070543650_li65926473">The standby NameNode instance is working incorrectly.</li><li id="ALM-14013__en-us_topic_0070543650_li56467345">The standby NameNode fails to generate a new FsImage file.</li><li id="ALM-14013__en-us_topic_0070543650_li38444057">Space of the data directory on the standby NameNode is insufficient.</li><li id="ALM-14013__en-us_topic_0070543650_li10452194">The standby NameNode fails to push the FsImage file to the active NameNode.</li><li id="ALM-14013__en-us_topic_0070543650_li26960885">Space of the data directory on the active NameNode is insufficient.</li></ul>
|
|
</div>
|
|
<div class="section" id="ALM-14013__sdfe825344e994a6abfee04fad1309080"><h4 class="sectiontitle">Procedure</h4><p class="tableheading" id="ALM-14013__en-us_topic_0070543650_p36348102"><strong id="ALM-14013__b6018197291327">Check whether the standby NameNode is stopped.</strong></p>
|
|
<ol id="ALM-14013__ol5829812392435"><li id="ALM-14013__li3530723391333"><span>On the FusionInsight Manager portal, choose <strong id="ALM-14013__b4866226891333">O&M > Alarm<strong id="ALM-14013__b27872374104950"> > Alarms</strong></strong>. In the alarm list, click the alarm.</span></li><li id="ALM-14013__li3627831091333"><span>View <strong id="ALM-14013__b4131362591333">Location</strong> and obtain the host name of the active NameNode for which the alarm is generated and name of the NameService where the active NameNode resides.</span></li><li id="ALM-14013__li4868989791333"><span>Choose <strong id="ALM-14013__b1978705113411">Cluster > </strong><em id="ALM-14013__i4789951173411">Name of the desired cluster</em><strong id="ALM-14013__b1678845112341"> > Services</strong> > <strong id="ALM-14013__b5286203291333">HDFS</strong> > <strong id="ALM-14013__b599624791333">Instance</strong>, find the standby NameNode instance of the NameService in the instance list, and check whether its <strong id="ALM-14013__b5396622791333"><strong id="ALM-14013__b7013131973">Configuration</strong> Status</strong> is <strong id="ALM-14013__b63118180973">Synchronized</strong>.</span><p><ul class="subitemlist" id="ALM-14013__ul2032306991333"><li id="ALM-14013__li1558535191333">If yes, go to <a href="#ALM-14013__li1445415191333">6</a>.</li><li id="ALM-14013__li5445390191333">If no, go to <a href="#ALM-14013__li6145479091333">4</a>.</li></ul>
|
|
</p></li><li id="ALM-14013__li6145479091333"><a name="ALM-14013__li6145479091333"></a><a name="li6145479091333"></a><span>Select the standby NameNode instance, choose <strong id="ALM-14013__b5156755291333">Start Instance</strong>, and wait until the startup is complete.</span></li><li id="ALM-14013__li6016175291333"><span>Wait for a NameNode metadata combination period and check whether the alarm is cleared.</span><p><ul class="subitemlist" id="ALM-14013__ul1482731491333"><li id="ALM-14013__li1622220491333">If yes, no further action is required.</li><li id="ALM-14013__li3893018191333">If no, go to <a href="#ALM-14013__li1445415191333">6</a>.</li></ul>
|
|
</p></li></ol>
|
|
<p class="tableheading" id="ALM-14013__p6633696291333"><strong id="ALM-14013__b5155124192443">Check whether the NameNode instance is working correctly.</strong></p>
|
|
<ol start="6" id="ALM-14013__ol2815654692457"><li id="ALM-14013__li1445415191333"><a name="ALM-14013__li1445415191333"></a><a name="li1445415191333"></a><span>Check whether <strong id="ALM-14013__b458486091333">Running Status</strong> of the standby NameNode instance is <strong id="ALM-14013__b4126374391333">Normal</strong>.</span><p><ul class="subitemlist" id="ALM-14013__ul6125834091333"><li id="ALM-14013__li5402887891333">If yes, go to <a href="#ALM-14013__li3200639691333">9</a>.</li><li id="ALM-14013__li1426302291333">If no, go to <a href="#ALM-14013__li98451291333">7</a>.</li></ul>
|
|
</p></li><li id="ALM-14013__li98451291333"><a name="ALM-14013__li98451291333"></a><a name="li98451291333"></a><span>Select the standby NameNode instance, choose <strong id="ALM-14013__b6297849691333">More</strong> > <strong id="ALM-14013__b2993555291333">Restart Instance</strong>, and wait until the startup is complete.</span></li><li id="ALM-14013__li2942212391333"><span>Wait for a NameNode metadata combination period and check whether the alarm is cleared.</span><p><ul class="subitemlist" id="ALM-14013__ul1693332591333"><li id="ALM-14013__li886060991333">If yes, no further action is required.</li><li id="ALM-14013__li4662072391333">If no, go to <a href="#ALM-14013__li795604191333">30</a>.</li></ul>
|
|
</p></li></ol>
|
|
<p class="tableheading" id="ALM-14013__p1818220591333"><strong id="ALM-14013__b586692219254">Check whether </strong><strong id="ALM-14013__b1513291616388">the standby NameNode fails to generate a new FsImage file.</strong></p>
|
|
<ol start="9" id="ALM-14013__ol4613452592529"><li id="ALM-14013__li3200639691333"><a name="ALM-14013__li3200639691333"></a><a name="li3200639691333"></a><span>On the FusionInsight Manager portal, choose <strong id="ALM-14013__b1315079163512">Cluster > </strong><em id="ALM-14013__i1215279143517">Name of the desired cluster</em><strong id="ALM-14013__b51509933513"> > Services</strong> > <strong id="ALM-14013__b3438177391333">HDFS</strong> > <strong id="ALM-14013__b4100050891333">Configurations</strong> > <strong id="ALM-14013__b3270681591333">All</strong> <strong id="ALM-14013__b19372066511">Configurations</strong>, and search and obtain the value of <strong id="ALM-14013__b2592588791333">dfs.namenode.checkpoint.period</strong>. This value is the period of NameNode metadata combination.</span></li><li id="ALM-14013__li1033107091333"><span>Choose <strong id="ALM-14013__b176611418356">Cluster > </strong><em id="ALM-14013__i1768111414352">Name of the desired cluster</em><strong id="ALM-14013__b1767181413512"> > Services</strong> > <strong id="ALM-14013__b4238127391333">HDFS</strong> > <strong id="ALM-14013__b4588713991333">Instance</strong> and obtain the service IP addresses of the active and standby NameNodes of the NameService for which the alarm is generated.</span></li><li id="ALM-14013__li1515775391333"><span>Click the<strong id="ALM-14013__b12460132015269"> NameNode(</strong><em id="ALM-14013__i2097652052618">xx</em><strong id="ALM-14013__b154624203268">,Standy) </strong>and <strong id="ALM-14013__b2587077291333">Instance Configurations</strong> to obtain the value of <strong id="ALM-14013__b3151035691333">dfs.namenode.name.dir</strong>. This value is the FsImage storage directory of the standby NameNode.</span></li><li id="ALM-14013__li4414840191333"><span>Log in to the standby NameNode as user <strong id="ALM-14013__b220205091333">root</strong> or <strong id="ALM-14013__b1981845891333">omm</strong>. <span id="ALM-14013__text101733453110"></span></span></li><li id="ALM-14013__li4826550291333"><span>Go to the FsImage storage directory and check the generation time of the newest FsImage file.</span><p><p class="litext" id="ALM-14013__p1580779391333"><strong id="ALM-14013__b6179129791333">cd </strong><em id="ALM-14013__i1925076191333">Storage directory of the standby NameNode</em><strong id="ALM-14013__b3903912391333">/current</strong></p>
|
|
<p class="litext" id="ALM-14013__p536283391333"><strong id="ALM-14013__b805241091333">stat -c %y $(ls -t | grep "fsimage_[0-9]*$" | head -1)</strong></p>
|
|
</p></li><li id="ALM-14013__li1719159091333"><span>Run the <strong id="ALM-14013__b3173633891333">date</strong> command to obtain the current system time.</span></li><li id="ALM-14013__li4827716291333"><span>Calculate the time difference between the generation time of the newest FsImage file and the current system time and check whether the time difference is greater than three times of the metadata combination period.</span><p><ul class="subitemlist" id="ALM-14013__ul5755991291333"><li id="ALM-14013__li5034156391333">If yes, go to <a href="#ALM-14013__li4970764591333">16</a>.</li><li id="ALM-14013__li5113478891333">If no, go to <a href="#ALM-14013__li3432370991333">20</a>.</li></ul>
|
|
</p></li><li id="ALM-14013__li4970764591333"><a name="ALM-14013__li4970764591333"></a><a name="li4970764591333"></a><span>The metadata combination function of the standby NameNode is faulty. Run the following command to check whether the fault is caused by insufficient storage space.</span><p><p class="litext" id="ALM-14013__p3184127591333">Go to the FsImage storage directory and check the size of the newest FsImage file (in MB).</p>
|
|
<p class="litext" id="ALM-14013__p71257891333"><strong id="ALM-14013__b1813602091333">cd </strong><em id="ALM-14013__i2900645491333">Storage directory of the standby NameNode</em><strong id="ALM-14013__b5973149891333">/current</strong></p>
|
|
<p class="litext" id="ALM-14013__p5771885491333"><strong id="ALM-14013__b641320691333">du -m $(ls -t | grep "fsimage_[0-9]*$" | head -1) | awk '{print $1}'</strong></p>
|
|
</p></li><li id="ALM-14013__li6689632991333"><span>Run the following command to check the available disk space of the standby NameNode (in MB).</span><p><p class="litext" id="ALM-14013__p4471562791333">df -m ./ | awk 'END{print $4}'</p>
|
|
</p></li><li id="ALM-14013__li6199669791333"><span>Compare the FsImage file size and the available disk space and determine whether another FsImage file can be stored on the disk.</span><p><ul class="subitemlist" id="ALM-14013__ul6654084591333"><li id="ALM-14013__li4989360291333">If yes, go to <a href="#ALM-14013__li98451291333">7</a>.</li><li id="ALM-14013__li1484996791333">If no, go to <a href="#ALM-14013__li2030785791333">19</a>.</li></ul>
|
|
</p></li><li id="ALM-14013__li2030785791333"><a name="ALM-14013__li2030785791333"></a><a name="li2030785791333"></a><span>Clear the redundant files on the disk where the directory resides to reserve sufficient space for metadata. After the clearance, wait for a NameNode metadata combination period and check whether the alarm is cleared.</span><p><ul class="subitemlist" id="ALM-14013__ul1350678691333"><li id="ALM-14013__li2109936491333">If yes, no further action is required.</li><li id="ALM-14013__li3132691591333">If no, go to <a href="#ALM-14013__li3432370991333">20</a>.</li></ul>
|
|
</p></li></ol>
|
|
<p class="tableheading" id="ALM-14013__p5445221191333"><strong id="ALM-14013__b1199509192536">Check whether the standby NameNode fails to push the FsImage file to the active NameNode.</strong></p>
|
|
<ol start="20" id="ALM-14013__ol5485807592717"><li id="ALM-14013__li3432370991333"><a name="ALM-14013__li3432370991333"></a><a name="li3432370991333"></a><span>Log in to the standby NameNode as user <strong id="ALM-14013__b4855298891333">root</strong>. <span id="ALM-14013__text89471284567"></span></span></li><li id="ALM-14013__li5748645491333"><span>Run the <strong id="ALM-14013__b4047792591333">su - omm</strong> command to switch to user <strong id="ALM-14013__b2875700591333">omm</strong>.</span></li><li id="ALM-14013__li2484364691333"><span>Run the following command to check whether the standby NameNode can push the file to the active NameNode.</span><p><p class="litext" id="ALM-14013__p2589119291333"><strong id="ALM-14013__b4761604191333">tmpFile=/tmp/tmp_test_$(date +%s)</strong></p>
|
|
<p class="litext" id="ALM-14013__p1681179491333"><strong id="ALM-14013__b3169413891333">echo "test" > $tmpFile</strong></p>
|
|
<p class="litext" id="ALM-14013__p4232171391333"><strong id="ALM-14013__b1708842491333">scp $tmpFile </strong><em id="ALM-14013__i1957809391333">Service IP address of the active NameNode</em><strong id="ALM-14013__b4198511491333">:/tmp</strong></p>
|
|
<ul class="subitemlist" id="ALM-14013__ul5495618891333"><li id="ALM-14013__li550669291333">If yes, go to <a href="#ALM-14013__li2740963991333">24</a>.</li><li id="ALM-14013__li4338894591333">If no, go to <a href="#ALM-14013__li1279432791333">23</a>.</li></ul>
|
|
</p></li><li id="ALM-14013__li1279432791333"><a name="ALM-14013__li1279432791333"></a><a name="li1279432791333"></a><span>When the standby NameNode fails to push data to the active NameNode as user <strong id="ALM-14013__b2226622491333">omm</strong>, contact the system administrator to handle the fault. Wait for a NameNode metadata combination period and check whether the alarm is cleared.</span><p><ul class="subitemlist" id="ALM-14013__ul5981027891333"><li id="ALM-14013__li6617829191333">If yes, no further action is required.</li><li id="ALM-14013__li5884136991333">If no, go to <a href="#ALM-14013__li2740963991333">24</a>.</li></ul>
|
|
</p></li></ol>
|
|
<p class="tableheading" id="ALM-14013__p142159191333"><strong id="ALM-14013__b3649047692723">Check whether space on the data directory of the active NameNode is insufficient.</strong></p>
|
|
<ol start="24" id="ALM-14013__ol3250789092727"><li id="ALM-14013__li2740963991333"><a name="ALM-14013__li2740963991333"></a><a name="li2740963991333"></a><span>On the FusionInsight Manager portal, choose <strong id="ALM-14013__b364852873517">Cluster > </strong><em id="ALM-14013__i3649172812357">Name of the desired cluster</em><strong id="ALM-14013__b164817284354"> > Services</strong> > <strong id="ALM-14013__b2970759891333">HDFS</strong> > <strong id="ALM-14013__b6604179091333">Instance</strong>, click the active NameNode of the NameService for which the alarm is generated, and then click <strong id="ALM-14013__b5750520091333">Instance Configurations</strong> to obtain the value of <strong id="ALM-14013__b4778475891333">dfs.namenode.name.dir</strong>. This value is the FsImage storage directory of the active NameNode.</span></li><li id="ALM-14013__li5029483991333"><span>Log in to the active NameNode as user <strong id="ALM-14013__b4536016691333">root</strong> or <strong id="ALM-14013__b558831591333">omm</strong>.</span></li><li id="ALM-14013__li2305155991333"><span>Go to the FsImage storage directory and check the size of the newest FsImage file (in MB).</span><p><p class="litext" id="ALM-14013__p1015778691333"><strong id="ALM-14013__b5000037191333">cd </strong><em id="ALM-14013__i4735016091333">Storage directory of the active NameNode</em><strong id="ALM-14013__b2349826491333">/current</strong></p>
|
|
<p class="litext" id="ALM-14013__p1747436591333"><strong id="ALM-14013__b2431121791333">du -m $(ls -t | grep "fsimage_[0-9]*$" | head -1) | awk '{print $1}'</strong></p>
|
|
</p></li><li id="ALM-14013__li5523696191333"><span>Run the following command to check the available disk space of the active NameNode (in MB).</span><p><p class="litext" id="ALM-14013__p613744091333">df -m ./ | awk 'END{print $4}'</p>
|
|
</p></li><li id="ALM-14013__li2399724291333"><span>Compare the FsImage file size and the available disk space and determine whether another FsImage file can be stored on the disk.</span><p><ul class="subitemlist" id="ALM-14013__ul6231868391333"><li id="ALM-14013__li4500883991333">If yes, go to <a href="#ALM-14013__li795604191333">30</a>.</li><li id="ALM-14013__li2183737991333">If no, go to <a href="#ALM-14013__li1860623691333">29</a>.</li></ul>
|
|
</p></li><li id="ALM-14013__li1860623691333"><a name="ALM-14013__li1860623691333"></a><a name="li1860623691333"></a><span>Clear the redundant files on the disk where the directory resides to reserve sufficient space for metadata. After the clearance, wait for a NameNode metadata combination period and check whether the alarm is cleared.</span><p><ul class="subitemlist" id="ALM-14013__ul851475191333"><li id="ALM-14013__li1464859291333">If yes, no further action is required.</li><li id="ALM-14013__li4568532691333">If no, go to <a href="#ALM-14013__li795604191333">30</a>.</li></ul>
|
|
</p></li></ol>
|
|
<p class="tableheading" id="ALM-14013__p952390091333"><strong id="ALM-14013__b119380499265">Collect fault information.</strong></p>
|
|
<ol start="30" id="ALM-14013__ol147722779268"><li id="ALM-14013__li795604191333"><a name="ALM-14013__li795604191333"></a><a name="li795604191333"></a><span>On the FusionInsight Manager portal, choose <strong id="ALM-14013__b39977366113627">O&M</strong> > <strong id="ALM-14013__b24251979113627">Log > Download</strong>.</span></li><li id="ALM-14013__li5600024891333"><span>Select <strong id="ALM-14013__b449550891333">NameNode</strong> in the required cluster from the <strong id="ALM-14013__b4045957691333">Service</strong>.</span></li><li id="ALM-14013__li1145664103113"><span>Click <span><img id="ALM-14013__image1945644173117" src="en-us_image_0269383968.png"></span> in the upper right corner, and set <strong id="ALM-14013__b6456941173117">Start Date</strong> and <strong id="ALM-14013__b11456154113318">End Date</strong> for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click <strong id="ALM-14013__b13456164113319">Download</strong>.</span></li><li id="ALM-14013__li6025399591333"><span>Contact the <span id="ALM-14013__text4614151421417">O&M personnel</span> and send the collected logs.</span></li></ol>
|
|
</div>
|
|
<div class="section" id="ALM-14013__section1529716184534"><h4 class="sectiontitle">Alarm Clearing</h4><p id="ALM-14013__p4677152685316">After the fault is rectified, the system automatically clears this alarm.</p>
|
|
</div>
|
|
<div class="section" id="ALM-14013__s3473ba3799e54e41bee049e2be802313"><h4 class="sectiontitle">Related Information</h4><p id="ALM-14013__en-us_topic_0070543650_p61245481">None</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_01_1298.html">Alarm Reference (Applicable to MRS 3.x)</a></div>
|
|
</div>
|
|
</div>
|
|
|