forked from docs/doc-exports
qiujiandong1
ab1e53a279
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com> Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
69 lines
8.4 KiB
HTML
69 lines
8.4 KiB
HTML
<a name="cce_faq_00440"></a><a name="cce_faq_00440"></a>
|
|
|
|
<h1 class="topictitle1">What Should I Do If a Node Pool Is Abnormal?</h1>
|
|
<div id="body0000001860276282"><div class="section" id="cce_faq_00440__section146798219817"><h4 class="sectiontitle">Fault Locating</h4><p id="cce_faq_00440__p997211345215">Locate the fault based on the status of the abnormal node pool, as shown in <a href="#cce_faq_00440__table230510269532">Table 1</a>.</p>
|
|
|
|
<div class="tablenoborder"><a name="cce_faq_00440__table230510269532"></a><a name="table230510269532"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_faq_00440__table230510269532" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Node pool exceptions</caption><thead align="left"><tr id="cce_faq_00440__row7305112615310"><th align="left" class="cellrowborder" valign="top" width="19.93%" id="mcps1.3.1.3.2.4.1.1"><p id="cce_faq_00440__p12742270810">Abnormal Node Pool Status</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="24.62%" id="mcps1.3.1.3.2.4.1.2"><p id="cce_faq_00440__p171315365819">Description</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="55.45%" id="mcps1.3.1.3.2.4.1.3"><p id="cce_faq_00440__p5305142645320">Solution</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="cce_faq_00440__row8305192615537"><td class="cellrowborder" valign="top" width="19.93%" headers="mcps1.3.1.3.2.4.1.1 "><p id="cce_faq_00440__p49234561811">Error</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.3.2.4.1.2 "><p id="cce_faq_00440__p99230566812">The node pool cannot be deleted.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="55.45%" headers="mcps1.3.1.3.2.4.1.3 "><p id="cce_faq_00440__p9923165612815">Delete the node pool again. If the node pool still cannot be deleted, submit a service ticket and delete the node pool.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_faq_00440__row23051626145317"><td class="cellrowborder" valign="top" width="19.93%" headers="mcps1.3.1.3.2.4.1.1 "><p id="cce_faq_00440__p2923175610815">QuotaInsufficient</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.3.2.4.1.2 "><p id="cce_faq_00440__p12923756187">The node pool cannot be scaled out due to insufficient quota.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="55.45%" headers="mcps1.3.1.3.2.4.1.3 "><p id="cce_faq_00440__p6923185610812">Submit a service ticket and increase the quota.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_faq_00440__row63061226105316"><td class="cellrowborder" valign="top" width="19.93%" headers="mcps1.3.1.3.2.4.1.1 "><p id="cce_faq_00440__p2092345614816">SoldOut</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.3.2.4.1.2 "><p id="cce_faq_00440__p169235567815">The underlying resources are insufficient.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="55.45%" headers="mcps1.3.1.3.2.4.1.3 "><p id="cce_faq_00440__p19230561681">Update the node pool configuration and select other available resources.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_faq_00440__row1130662675311"><td class="cellrowborder" valign="top" width="19.93%" headers="mcps1.3.1.3.2.4.1.1 "><p id="cce_faq_00440__p199232561815">ConfigurationInvalid</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.3.2.4.1.2 "><p id="cce_faq_00440__p1151119324916">The ECS group does not exist (<strong id="cce_faq_00440__b0961022017">ServerGroupNotExists</strong>).</p>
|
|
<p id="cce_faq_00440__p99236561818">The ECS group to which the node pool belongs is not present. This may be because you manually deleted the ECS group.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="55.45%" headers="mcps1.3.1.3.2.4.1.3 "><ol id="cce_faq_00440__ol182391227111016"><li id="cce_faq_00440__li1523982718106">Log in to the CCE console. In the navigation pane, choose <strong id="cce_faq_00440__b191961151274">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00440__b71964511072">Node Pools</strong> tab and click the name of the target node pool. On the displayed page, click the <strong id="cce_faq_00440__b141965512710">Overview</strong> tab, click <strong id="cce_faq_00440__b719713511777">Expand</strong>, and check the ECS group to which the node pool belongs.</li><li id="cce_faq_00440__li623982761019">Log in to the ECS console, choose <strong id="cce_faq_00440__b8899315141516">Elastic Cloud Server</strong> > <strong id="cce_faq_00440__b0899615111516">ECS Group</strong> in the navigation pane, and see if the target ECS group is present.</li><li id="cce_faq_00440__li2086874951417">If the ECS group is not present, log in to the CCE console. In the navigation pane, choose <strong id="cce_faq_00440__b4234174317273">Nodes</strong>, click the <strong id="cce_faq_00440__b1530234511275">Node Pools</strong> tab, locate the row containing the target node pool, and click <strong id="cce_faq_00440__b333418652816">Update</strong>. In the <strong id="cce_faq_00440__b1186813555343">Advanced Settings</strong> area, unbind or change the ECS group.</li></ol>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_faq_00440__row1675614169453"><td class="cellrowborder" valign="top" width="19.93%" headers="mcps1.3.1.3.2.4.1.1 "><p id="cce_faq_00440__p1075720162459">InstanceAboveServerGroup</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.3.2.4.1.2 "><p id="cce_faq_00440__p18715939115015">The number of ECSs in the ECS group exceeds the upper limit.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="55.45%" headers="mcps1.3.1.3.2.4.1.3 "><ol id="cce_faq_00440__ol1844865315211"><li id="cce_faq_00440__li544935317528">Log in to the CCE console. In the navigation pane, choose <strong id="cce_faq_00440__b111117239156">Nodes</strong>. In the right pane, click the <strong id="cce_faq_00440__b111119230155">Node Pools</strong> tab and click the name of the target node pool. On the displayed page, click the <strong id="cce_faq_00440__b161111123121518">Overview</strong> tab, click <strong id="cce_faq_00440__b1711117238156">Expand</strong>, and check the ECS group to which the node pool belongs.</li><li id="cce_faq_00440__li4698145805213">Log in to the ECS console, choose <strong id="cce_faq_00440__b8656727131513">Elastic Cloud Server</strong> > <strong id="cce_faq_00440__b1865692717156">ECS Group</strong> in the navigation pane, and check the quota of the target ECS group.</li><li id="cce_faq_00440__li1836431913532">If the quota is insufficient, log in to the CCE console. In the navigation pane, choose <strong id="cce_faq_00440__b11134173391516">Nodes</strong>, click the <strong id="cce_faq_00440__b1213493381518">Node Pools</strong> tab, locate the row containing the target node pool, and click <strong id="cce_faq_00440__b613553315152">Update</strong>. In the <strong id="cce_faq_00440__b213553310159">Advanced Settings</strong> area, unbind or change the ECS group.</li></ol>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_faq_00440__row1928364225811"><td class="cellrowborder" valign="top" width="19.93%" headers="mcps1.3.1.3.2.4.1.1 "><p id="cce_faq_00440__p13739154725810">MaxNodeCountReached</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.3.2.4.1.2 "><p id="cce_faq_00440__p1628319421580">The number of expected nodes in the current node pool or scaling group has reached the maximum allowed limit.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="55.45%" headers="mcps1.3.1.3.2.4.1.3 "><ul id="cce_faq_00440__ul15473121114594"><li id="cce_faq_00440__li5473311105915">Manually add nodes to the node pool or scaling group as needed. If the expected number of nodes in a node pool or scaling group reaches the maximum allowed limit, auto scaling will no longer be triggered for that node pool or scaling group. However, this does not affect manual scale-out operations.</li><li id="cce_faq_00440__li5111628506">Choose <strong id="cce_faq_00440__b1440018569356">Nodes</strong> in the navigation pane, click the <strong id="cce_faq_00440__b1788825818356">Node Pools</strong> tab in the right pane, locate the row containing the target node pool, click <strong id="cce_faq_00440__b8699165318357">Auto Scaling</strong>, and change the value of <strong id="cce_faq_00440__b819132183620">Nodes</strong>.<p id="cce_faq_00440__p6581112810019">Or simply disable auto scaling of the node pool or scaling group.</p>
|
|
</li></ul>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_faq_00163.html">Node Pool</a></div>
|
|
</div>
|
|
</div>
|
|
|