vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

CSS UMN 22.5.1 Version

Browse Source 
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: Zheng, Xiu <zhengxiu@huawei.com>
Co-committed-by: Zheng, Xiu <zhengxiu@huawei.com>
This commit is contained in:
Zheng, Xiu 2023-03-29 17:17:49 +00:00 committed by zuul
parent 70c0715827
commit 5b5876528a
183 changed files with 4700 additions and 1566 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

878
docs/css/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

842
docs/css/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

14
docs/css/umn/css_01_0001.html
View File

@ -6,21 +6,19 @@
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_04_0001.html">CSS</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0002.html">Applicable Scenarios for Elasticsearch Clusters</a></strong><br>
<li class="ulchildlink"><strong><a href="css_04_0010.html">Advantages</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0003.html">Basic Concepts</a></strong><br>
<li class="ulchildlink"><strong><a href="css_04_0007.html">Product Components</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0007.html">Kibana</a></strong><br>
<li class="ulchildlink"><strong><a href="css_04_0002.html">Scenarios</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0022.html">Cerebro</a></strong><br>
<li class="ulchildlink"><strong><a href="css_04_0014.html">Permissions Management</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0019.html">Clusters in Security Mode</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0023.html">Multi-AZ HA</a></strong><br>
<li class="ulchildlink"><strong><a href="css_04_0005.html">Constraints</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0004.html">Related Services</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0005.html">Constraints</a></strong><br>
<li class="ulchildlink"><strong><a href="css_04_0003.html">Basic Concepts</a></strong><br>
</li>
</ul>
</div>

30
docs/css/umn/css_01_0002.html
View File

@ -8,12 +8,30 @@
</th>
</tr>
</thead>
<tbody><tr id="css_01_0002__row154879371204"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p558874305710">2022-06-30</p>
<tbody><tr id="css_01_0002__row82938366110"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p132941836218">2023-03-01</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><ul id="css_01_0002__ul196098186522"><li id="css_01_0002__li866004554310">Added cluster version Opensearch_1.3.6.</li><li id="css_01_0002__li132265210494">Updated the procedure description in:<ul id="css_01_0002__ul81831921175012"><li id="css_01_0002__li21831121175010"><a href="css_04_0001.html">CSS</a></li><li id="css_01_0002__li74423445113"><a href="css_04_0004.html">Related Services</a></li><li id="css_01_0002__li15907154465818"><a href="css_01_0007.html">Getting Started with Elasticsearch</a></li><li id="css_01_0002__li7638194315210"><a href="css_04_0019.html">Clusters in Security Mode</a></li><li id="css_01_0002__li15925721958"><a href="css_01_0011.html">Creating an Elasticsearch Cluster in Security Mode</a></li><li id="css_01_0002__li154975356520"><a href="css_01_0094.html">Creating an Elasticsearch Cluster in Non-Security Mode</a></li><li id="css_01_0002__li16371558175311"><a href="css_01_0074.html">Changing Specifications</a></li><li id="css_01_0002__li14989139207"><a href="css_01_0078.html">Managing Plugins</a></li><li id="css_01_0002__li1389672423517"><a href="css_01_0061.html">Elasticsearch SQL</a></li></ul>
</li><li id="css_01_0002__li1828852714526">Added:<ul id="css_01_0002__ul2040763065220"><li id="css_01_0002__li43052012125314"><a href="css_04_0010.html">Advantages</a></li><li id="css_01_0002__li7261521115316"><a href="css_04_0007.html">Product Components</a></li><li id="css_01_0002__li4827193835217"><a href="css_04_0014.html">Permissions Management</a></li><li id="css_01_0002__li151264422525"><a href="css_01_0072.html">Creating a User and Granting Permissions</a></li><li id="css_01_0002__li1940773035219"><a href="css_01_0086.html">CSS Custom Policies</a></li><li id="css_01_0002__li1696953975911"><a href="css_01_0190.html">Accessing an Elasticsearch Cluster</a></li><li id="css_01_0002__li1933068102"><a href="css_01_0185.html">Viewing Cluster Information</a></li><li id="css_01_0002__li3111134115718"><a href="css_01_0151.html">Scaling Out a Cluster</a></li><li id="css_01_0002__li9350114516577"><a href="css_01_0153.html">Scaling in a Cluster</a></li><li id="css_01_0002__li1778745616574"><a href="css_01_0081.html">Removing Specified Nodes</a></li><li id="css_01_0002__li8675381105"><a href="css_01_0058.html">Binding an Enterprise Project</a></li><li id="css_01_0002__li1985135424514"><a href="css_01_0107.html">Working with Kibana</a></li><li id="css_01_0002__li5650164312353"><a href="css_01_0155.html">Configuring Cluster Monitoring</a></li><li id="css_01_0002__li553861116319"><a href="css_02_0042.html">Why All New Index Shards Are Allocated to the Same Node?</a></li><li id="css_01_0002__li82173267292"><a href="css_02_0106.html">How Do I Obtain the Security Certificate of CSS?</a></li><li id="css_01_0002__li293735010306"><a href="css_02_0064.html">What Is the Relationship Between the Filebeat Version and Cluster Version?</a></li><li id="css_01_0002__li626620732612"><a href="css_02_0120.html">Can I Restore a Deleted Cluster?</a></li><li id="css_01_0002__li777923219320"><a href="css_02_0132.html">How Do I Create a Type Under an Index in an Elasticsearch 7.x Cluster?</a></li><li id="css_01_0002__li3312145719312"><a href="css_02_0128.html">How Do I Convert the Format of a CER Security Certificate?</a></li><li id="css_01_0002__li392710208413"><a href="css_02_0124.html">What Are the Impacts If an Elasticsearch Cluster Has Too Many Shards?</a></li><li id="css_01_0002__li17332836144"><a href="css_02_0125.html">How Do I Set the Default Maximum Number of Records Displayed on a Page for an Elasticsearch Cluster</a></li><li id="css_01_0002__li20767715313"><a href="css_02_0126.html">Why Does the Disk Usage Increase After the delete_by_query Command Was Executed to Delete Data?</a></li><li id="css_01_0002__li12750014451"><a href="css_02_0130.html">How Do I Clear the Cache of a CSS Cluster?</a></li><li id="css_01_0002__li1038118447519"><a href="css_02_0131.html">The Average Memory Usage of an Elasticsearch Cluster Reaches 98%</a></li><li id="css_01_0002__li14813821467"><a href="css_02_0088.html">Can I Install Search Guard on CSS?</a></li><li id="css_01_0002__li10819038103718"><a href="css_02_0098.html">Can I Export Data from Kibana?</a></li><li id="css_01_0002__li7280125673710"><a href="css_02_0099.html">How Do I Query Index Data on Kibana in an ES Cluster?</a></li><li id="css_01_0002__li6235131263910"><a href="css_02_0078.html">Can a New Cluster Use the IP Address of the Old Cluster?</a></li><li id="css_01_0002__li129011524153911"><a href="css_02_0081.html">Can I Use x-pack-sql-jdbc to Access CSS Clusters and Query Data?</a></li><li id="css_01_0002__li5732195217397"><a href="css_02_0083.html">Do Ports 9200 and 9300 Both Open?</a></li></ul>
</li><li id="css_01_0002__li19853143114182">Deleted:<ul id="css_01_0002__ul74347406187"><li id="css_01_0002__li312913565318">Kibana</li><li id="css_01_0002__li68888795412">Cerebro</li><li id="css_01_0002__li843411409188">Suggestions on Using Elasticsearch</li><li id="css_01_0002__li1646124517187">Creating Alarm Rules</li><li id="css_01_0002__li16754226175413">Viewing Audit Logs</li></ul>
</li></ul>
</td>
</tr>
<tr id="css_01_0002__row19140105916317"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p83241613215">2022-09-14</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><p id="css_01_0002__p690091223314">Updated: <a href="css_01_0033.html">Index Backup and Restoration</a></p>
</td>
</tr>
<tr id="css_01_0002__row56234388454"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p1662312387451">2022-07-28</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><p id="css_01_0002__p580095714520">Added cluster version 7.10.2.</p>
</td>
</tr>
<tr id="css_01_0002__row154879371204"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p558874305710">2022-06-30</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><p id="css_01_0002__p12143175155715">Added cluster version 7.9.3.</p>
<p id="css_01_0002__p283414310011">Supported the VPC endpoint service: <a href="css_01_0082.html">VPC Endpoint Service</a></p>
<p id="css_01_0002__p51041137181512">Optimized the following content based on use scenarios and operation processes:</p>
<ul id="css_01_0002__ul891123318501"><li id="css_01_0002__li1591123395017"><a href="css_01_0031.html">Modifying Specifications</a></li><li id="css_01_0002__li718714279400"><a href="css_01_0011.html">Creating an Elasticsearch Cluster in Security Mode</a></li><li id="css_01_0002__li186731612204115"><a href="css_01_0094.html">Creating an Elasticsearch Cluster in Non-Security Mode</a></li><li id="css_01_0002__li592313188414"><a href="css_01_0033.html">Index Backup and Restoration</a></li><li id="css_01_0002__li948116215426"><a href="css_01_0075.html">Managing Tags</a></li><li id="css_01_0002__li1418517399415"><a href="css_01_0077.html">Managing Logs</a></li><li id="css_01_0002__li16953848204118"><a href="css_01_0079.html">Hot and Cold Data Storage</a></li><li id="css_01_0002__li1310411375157"><a href="css_01_0044.html">Viewing Metrics</a></li></ul>
<ul id="css_01_0002__ul891123318501"><li id="css_01_0002__li1591123395017">Modifying Specifications</li><li id="css_01_0002__li718714279400"><a href="css_01_0011.html">Creating an Elasticsearch Cluster in Security Mode</a></li><li id="css_01_0002__li186731612204115"><a href="css_01_0094.html">Creating an Elasticsearch Cluster in Non-Security Mode</a></li><li id="css_01_0002__li592313188414"><a href="css_01_0033.html">Index Backup and Restoration</a></li><li id="css_01_0002__li948116215426"><a href="css_01_0075.html">Managing Tags</a></li><li id="css_01_0002__li1418517399415"><a href="css_01_0077.html">Managing Logs</a></li><li id="css_01_0002__li16953848204118"><a href="css_01_0079.html">Hot and Cold Data Storage</a></li><li id="css_01_0002__li1310411375157">Viewing Metrics</li></ul>
</td>
</tr>
<tr id="css_01_0002__row1414420368167"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p18145936161614">2020-08-30</p>
@ -28,7 +46,7 @@
<tr id="css_01_0002__row127612443154"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p9761144131510">2019-03-15</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><ul id="css_01_0002__ul1324657161511"><li id="css_01_0002__li6324115711520">Updated the following section based on software changes:<p id="css_01_0002__p1083814250163"><a name="css_01_0002__li6324115711520"></a><a name="li6324115711520"></a><a href="css_01_0033.html">Index Backup and Restoration</a></p>
<p id="css_01_0002__p75001833575"><a href="css_01_0043.html">Creating Alarm Rules</a></p>
<p id="css_01_0002__p75001833575">Creating Alarm Rules</p>
</li><li id="css_01_0002__li5156161181617">Added the operation guide for managing failed tasks.<p id="css_01_0002__p87404460166"><a name="css_01_0002__li5156161181617"></a><a name="li5156161181617"></a><a href="css_01_0060.html">Managing Failed Tasks</a></p>
</li></ul>
</td>
@ -58,7 +76,7 @@
</tr>
<tr id="css_01_0002__row10147256175513"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p171481956155511">2018-12-03</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><ul id="css_01_0002__ul4696249155614"><li id="css_01_0002__li4696154910562">Updated screenshots in the following sections based on software changes:<p id="css_01_0002__p626971935715"><a name="css_01_0002__li4696154910562"></a><a name="li4696154910562"></a><a href="css_02_0025.html">Why Does My ECS Fail to Connect to a Cluster?</a></p>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><ul id="css_01_0002__ul4696249155614"><li id="css_01_0002__li4696154910562">Updated screenshots in the following sections based on software changes:<p id="css_01_0002__p626971935715"><a name="css_01_0002__li4696154910562"></a><a name="li4696154910562"></a>1Why Does My ECS Fail to Connect to a Cluster?</p>
</li></ul>
</td>
</tr>
@ -71,7 +89,7 @@
<tr id="css_01_0002__row16894164118176"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p12894134117173">2018-10-19</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><ul id="css_01_0002__ul1586034413114"><li id="css_01_0002__li128596442113">Added parameter descriptions and modified the description of operations in the following section:<p id="css_01_0002__p025465131911"><a name="css_01_0002__li128596442113"></a><a name="li128596442113"></a><a href="css_01_0033.html">Index Backup and Restoration</a></p>
</li><li id="css_01_0002__li184311931115214">Optimized the Elasticsearch usage suggestions.<p id="css_01_0002__p27131753145210"><a name="css_01_0002__li184311931115214"></a><a name="li184311931115214"></a><a href="css_01_0032.html">Suggestions on Using Elasticsearch</a></p>
</li><li id="css_01_0002__li184311931115214">Optimized the Elasticsearch usage suggestions.<p id="css_01_0002__p27131753145210"><a name="css_01_0002__li184311931115214"></a><a name="li184311931115214"></a>Suggestions on Using Elasticsearch</p>
</li></ul>
</td>
</tr>
@ -102,7 +120,7 @@
<tr id="css_01_0002__row811710311589"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.1.1.3.1.1 "><p id="css_01_0002__p2117331883">2018-08-20</p>
</td>
<td class="cellrowborder" valign="top" width="79%" headers="mcps1.3.1.1.3.1.2 "><ul id="css_01_0002__ul147624101395"><li id="css_01_0002__li976816241597">Modified the screenshots and output examples.<p id="css_01_0002__p2819192141116"><a name="css_01_0002__li976816241597"></a><a name="li976816241597"></a><a href="css_01_0007.html">Getting Started with Elasticsearch</a></p>
</li><li id="css_01_0002__li171692551095">Added operation examples in the following section:<p id="css_01_0002__p645718436111"><a name="css_01_0002__li171692551095"></a><a name="li171692551095"></a><a href="css_01_0032.html">Suggestions on Using Elasticsearch</a></p>
</li><li id="css_01_0002__li171692551095">Added operation examples in the following section:<p id="css_01_0002__p645718436111"><a name="css_01_0002__li171692551095"></a><a name="li171692551095"></a>Suggestions on Using Elasticsearch</p>
</li><li id="css_01_0002__li6636142361011">Added the link to the operation guide for enabling CTS in the following section:<p id="css_01_0002__p159671491110"><a name="css_01_0002__li6636142361011"></a><a name="li6636142361011"></a><a href="css_01_0050.html">Key Operations Recorded by CTS</a></p>
</li><li id="css_01_0002__li1166913915100">Deleted the following two sections:<ul id="css_01_0002__ul4756195091010"><li id="css_01_0002__li3208141918513">What is CSS?</li><li id="css_01_0002__li32559472103">Which Scenarios Can CSS Be Applied To?</li></ul>
</li></ul>

30
docs/css/umn/css_01_0007.html
View File

@ -1,7 +1,7 @@
<a name="css_01_0007"></a><a name="css_01_0007"></a>
<h1 class="topictitle1">Getting Started with Elasticsearch</h1>
<div id="body0000001282179454"><p id="css_01_0007__p173715321378">This section describes how to use Elasticsearch to provide the search function for users. You can use the Elasticsearch search engine of CSS to search for data based on the scenario example. The basic operation process is as follows:</p>
<div id="body0000001282179454"><p id="css_01_0007__p173715321378">This section describes how to use Elasticsearch for product search. You can use the Elasticsearch search engine of CSS to search for data based on the scenario example. The basic operation process is as follows:</p>
<ul id="css_01_0007__ul13335102293410"><li id="css_01_0007__li1867161816352"><a href="#css_01_0007__section96881833619">Step 1: Create a Cluster</a></li><li id="css_01_0007__li13335192283412"><a href="#css_01_0007__section398512163445">Step 2: Import Data</a></li><li id="css_01_0007__li1733518226347"><a href="#css_01_0007__section167624221443">Step 3: Search for Data</a></li><li id="css_01_0007__li203359221346"><a href="#css_01_0007__section75027114374">Step 4: Delete the Cluster</a></li></ul>
<div class="section" id="css_01_0007__section15177859183319"><h4 class="sectiontitle">Scenario Description</h4><p id="css_01_0007__p98074268319">A women's clothing brand builds an e-commerce website. It uses traditional databases to provide a product search function for users. However, due to an increase in the number of users and business growth, the traditional databases have slow response and low accuracy. To improve user experience and user retention, the e-commerce website plans to use Elasticsearch to provide the product search function for users.</p>
<p id="css_01_0007__p94791144716">This section describes how to use Elasticsearch to provide the search function for users.</p>
@ -18,13 +18,14 @@
]
}</pre>
</div>
<div class="section" id="css_01_0007__section96881833619"><a name="css_01_0007__section96881833619"></a><a name="section96881833619"></a><h4 class="sectiontitle">Step 1: Create a Cluster</h4><p id="css_01_0007__p898232016369">Create a cluster using Elasticsearch as the search engine. In this example, suppose that you create a cluster named <span class="parmname" id="css_01_0007__parmname93661543523"><b>Es-xfx</b></span>. This cluster is used only for getting started with Elasticsearch. For this cluster, you are advised to select <span class="parmvalue" id="css_01_0007__parmvalue63521310203014"><b>css.medium.8</b></span> for <span class="parmname" id="css_01_0007__parmname11961113171811"><b>Node Specifications</b></span>, <span class="parmvalue" id="css_01_0007__parmvalue612116254209"><b>Common I/O</b></span> for <span class="parmname" id="css_01_0007__parmname08622023155111"><b>Node Storage Type</b></span>, and <span class="parmvalue" id="css_01_0007__parmvalue13449183511816"><b>40 GB</b></span> for <span class="parmname" id="css_01_0007__parmname1299602881818"><b>Node Storage Capacity</b></span>. For details, see <a href="css_01_0094.html">Creating an Elasticsearch Cluster in Non-Security Mode</a>.</p>
<div class="section" id="css_01_0007__section96881833619"><a name="css_01_0007__section96881833619"></a><a name="section96881833619"></a><h4 class="sectiontitle">Step 1: Create a Cluster</h4><p id="css_01_0007__p898232016369">Create a cluster using Elasticsearch as the search engine. In this example, suppose that you create a cluster named <span class="parmname" id="css_01_0007__parmname93661543523"><b>Es-xfx</b></span>. This cluster is used only for getting started with Elasticsearch. For this cluster, you are advised to select <span class="parmvalue" id="css_01_0007__parmvalue63521310203014"><b>css.medium.8</b></span> for <span class="parmname" id="css_01_0007__parmname11961113171811"><b>Node Specifications</b></span>, <span class="parmvalue" id="css_01_0007__parmvalue612116254209"><b>Common I/O</b></span> for <span class="parmname" id="css_01_0007__parmname08622023155111"><b>Node Storage Type</b></span>, and <span class="parmvalue" id="css_01_0007__parmvalue13449183511816"><b>40 GB</b></span> for <span class="parmname" id="css_01_0007__parmname1299602881818"><b>Node Storage Capacity</b></span>. For details, see <a href="css_01_0011.html">Creating an Elasticsearch Cluster in Non-Security Mode</a>.</p>
<p id="css_01_0007__p9981114851314">Create a cluster using Elasticsearch as the search engine. In this example, suppose that you create a cluster named <span class="parmvalue" id="css_01_0007__parmvalue4187134718420"><b>Sample-ESCluster</b></span>. This cluster is used only for getting started with Elasticsearch. For this cluster, you are advised to select <strong id="css_01_0007__b191855817415">ess.spec-4u8g</strong> for <strong id="css_01_0007__b168451802614">Node Specifications</strong>, <span class="parmvalue" id="css_01_0007__parmvalue121817581546"><b>High I/O</b></span> for <span class="parmname" id="css_01_0007__parmname10193580410"><b>Node Storage Type</b></span>, and <span class="parmvalue" id="css_01_0007__parmvalue141955811416"><b>40 GB</b></span> for <span class="parmname" id="css_01_0007__parmname201911582041"><b>Node Storage Capacity</b></span>. For details, see or .</p>
<p id="css_01_0007__p1358232011214">After you create the cluster, switch to the cluster list to view the created cluster. If the <strong id="css_01_0007__b3483163615715">Status</strong> of the cluster is <strong id="css_01_0007__b5485173611579">Available</strong>, the cluster is created successfully. </p>
<div class="fignone" id="css_01_0007__fig1388755803117"><span class="figcap"><b>Figure 1 </b>Creating a cluster</span><br><span><img id="css_01_0007__image11315212105215" src="en-us_image_0000001286116742.png" width="480.795" height="34.155065" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div class="section" id="css_01_0007__section398512163445"><a name="css_01_0007__section398512163445"></a><a name="section398512163445"></a><h4 class="sectiontitle">Step 2: Import Data</h4><p id="css_01_0007__p109714181508"><span id="css_01_0007__text7335958205618">CSS</span> supports importing data to Elasticsearch using Logstash, Kibana, or APIs. Kibana lets you visualize your Elasticsearch data. The following procedure illustrates how to import data to Elasticsearch using Kibana.</p>
<ol id="css_01_0007__ol721112814243"><li id="css_01_0007__li12211102818242">On the <span class="parmname" id="css_01_0007__parmname1893267523152010"><b>Clusters</b></span> page of the <span id="css_01_0007__text4357931152027">CSS</span> management console, locate the row containing the target cluster and click <span class="parmname" id="css_01_0007__parmname1862724866152037"><b>Access Kibana</b></span> in the <span class="parmname" id="css_01_0007__parmname50483114315214"><b>Operation</b></span> column.</li><li id="css_01_0007__li221115281242">In the left navigation pane of Kibana, choose <strong id="css_01_0007__b830264193410">Dev Tools</strong>.<p id="css_01_0007__p821152882417">The text box on the left is the input box. The triangle icon in the upper right corner of the input box is the command execution button. The text box on the right area is the result output box.</p>
<div class="fignone" id="css_01_0007__fig1830133281516"><span class="figcap"><b>Figure 2 </b>Console page</span><br><span><img id="css_01_0007__image357642471516" src="en-us_image_0000001338716641.png" width="437.89053" height="177.39939" title="Click to enlarge" class="imgResize"></span></div>
<ol id="css_01_0007__ol8733172515314"><li id="css_01_0007__li7655153392911">On the <span class="uicontrol" id="css_01_0007__uicontrol2655733162910"><b>Clusters</b></span> page, locate the target cluster and click <strong id="css_01_0007__b820219462171">More</strong> &gt; <strong id="css_01_0007__b07204415178">Cerebro</strong> in the <span class="uicontrol" id="css_01_0007__uicontrol18655533122910"><b>Operation</b></span> column to go to the Cerebro login page.<ul id="css_01_0007__ul75232028195712"><li id="css_01_0007__li20523122816570">Non-security cluster: Click the cluster name on the Cerebro login page to go to the Cerebro console.</li><li id="css_01_0007__li134787055820">Security cluster: Click the cluster name on the Cerebro login page, enter the username and password, and click <span class="uicontrol" id="css_01_0007__uicontrol15959165212110"><b>Authenticate</b></span> to go to the Cerebro console. The default username is <strong id="css_01_0007__b39827080224321">admin</strong> and the password is the one specified during cluster creation.</li></ul>
</li></ol><ol start="2" id="css_01_0007__ol721112814243"><li id="css_01_0007__li221115281242">In the navigation pane of Kibana on the left, choose <strong id="css_01_0007__b830264193410">Dev Tools</strong>.<p id="css_01_0007__p821152882417">The text box on the left is the input box. The triangle icon in the upper right corner of the input box is the command execution button. The text box on the right area is the result output box.</p>
<div class="fignone" id="css_01_0007__fig1830133281516"><span class="figcap"><b>Figure 1 </b>Console page</span><br><span><img id="css_01_0007__image357642471516" src="en-us_image_0000001476610606.png"></span></div>
<div class="note" id="css_01_0007__note681964235017"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0007__p188211742195017">The Kibana UI varies depending on the Kibana version.</p>
</div></div>
</li><li id="css_01_0007__li11211328172416">On the <strong id="css_01_0007__b64617712383">Console</strong> page, run the following command to create index named <span class="parmname" id="css_01_0007__parmname23541417123812"><b>my_store</b></span>:<div class="p" id="css_01_0007__p1583315530414">(Versions earlier than 7.<em id="css_01_0007__i1860645555612">x</em>)<pre class="screen" id="css_01_0007__screen1112385214416">PUT /my_store
@ -106,7 +107,7 @@
<p id="css_01_0007__p1280919176267">If the value of the <span class="parmname" id="css_01_0007__parmname1301102314392"><b>errors</b></span> field in the command output is <span class="parmvalue" id="css_01_0007__parmvalue5302122313392"><b>false</b></span>, the data is imported successfully.</p>
</li></ol>
</div>
<div class="section" id="css_01_0007__section167624221443"><a name="css_01_0007__section167624221443"></a><a name="section167624221443"></a><h4 class="sectiontitle">Step 3: Search for Data</h4><ul id="css_01_0007__ul1826814131366"><li id="css_01_0007__li826816134618"><strong id="css_01_0007__b83672071469">Full-text search</strong><p id="css_01_0007__p1123422620167">If you access the e-commerce website and want to search for commodities whose names include "spring jeans", enter "spring jeans" to begin your search. The following text provides the command to be executed on Kibana and the command output.</p>
<div class="section" id="css_01_0007__section167624221443"><a name="css_01_0007__section167624221443"></a><a name="section167624221443"></a><h4 class="sectiontitle">Step 3: Search for Data</h4><ul id="css_01_0007__ul1826814131366"><li id="css_01_0007__li826816134618"><strong id="css_01_0007__b83672071469">Full-text search</strong><p id="css_01_0007__p1123422620167">If you access the e-commerce website and want to search for commodities whose names include "spring jeans", enter "spring jeans" to begin your search. The following example shows the command to be executed on Kibana and the command output.</p>
<p id="css_01_0007__p13713546141016">Command to be executed on Kibana:</p>
<p id="css_01_0007__p1965195514348">(Versions earlier than 7.<em id="css_01_0007__i4903102310480">x</em>)</p>
<pre class="screen" id="css_01_0007__screen18763165016431">GET /my_store/products/_search
@ -179,9 +180,9 @@
]
}
}</pre>
<ul id="css_01_0007__ul1515122217247"><li id="css_01_0007__li61511122152415">Elasticsearch supports full-text search. The preceding command searches for the information about all commodities whose names include "spring" or "jeans".</li><li id="css_01_0007__li14281247258">Unlike traditional databases, Elasticsearch can return results in milliseconds by using inverted indices.</li><li id="css_01_0007__li1345681018563">Elasticsearch supports sorting by score. In the command output, information about the first two commodities contains both "spring" and "jeans", while that about the last two products contains only "spring". Therefore, the first two commodities rank prior to the last two due to high keyword match.</li></ul>
<ul id="css_01_0007__ul1515122217247"><li id="css_01_0007__li61511122152415">Elasticsearch supports full-text search. The preceding command searches for the information about all commodities whose names include "spring" or "jeans".</li><li id="css_01_0007__li14281247258">Unlike traditional databases, Elasticsearch can return results in milliseconds by using inverted indexes.</li><li id="css_01_0007__li1345681018563">Elasticsearch supports sorting by score. In the command output, information about the first two commodities contains both "spring" and "jeans", while that about the last two products contain only "spring". Therefore, the first two commodities rank prior to the last two due to high keyword match.</li></ul>
</li></ul>
<ul id="css_01_0007__ul4149154594416"><li id="css_01_0007__li1093164683813"><strong id="css_01_0007__b129772018038">Aggregation result display</strong><p id="css_01_0007__p19910171720276">The e-commerce website provides the function of displaying aggregation results. For example, it classifies commodities corresponding to "spring" based on the size so that you can collect the number of products of different sizes. The following provides the command to be executed on Kibana and the command output.</p>
<ul id="css_01_0007__ul4149154594416"><li id="css_01_0007__li1093164683813"><strong id="css_01_0007__b129772018038">Aggregation result display</strong><p id="css_01_0007__p19910171720276">The e-commerce website provides the function of displaying aggregation results. For example, it classifies commodities corresponding to "spring" based on the size so that you can collect the number of products of different sizes. The following example shows the command to be executed on Kibana and the command output.</p>
<p id="css_01_0007__p207753616243">Command to be executed on Kibana:</p>
<p id="css_01_0007__p6929112817554">(Versions earlier than 7.<em id="css_01_0007__i1811735635315">x</em>)</p>
<pre class="screen" id="css_01_0007__screen1875916312110">GET /my_store/products/_search
@ -196,7 +197,6 @@
}
}
}</pre>
<p id="css_01_0007__p1058514510542"></p>
<p id="css_01_0007__p1623161075615">(Versions later than 7.<em id="css_01_0007__i1202165818539">x</em>)</p>
<pre class="screen" id="css_01_0007__screen48531811195511">GET /my_store/_search
{
@ -289,8 +289,9 @@
</li></ul>
</div>
<div class="section" id="css_01_0007__section75027114374"><a name="css_01_0007__section75027114374"></a><a name="section75027114374"></a><h4 class="sectiontitle">Step 4: Delete the Cluster</h4><p id="css_01_0007__p1972792353814">Once you understand the process and method of using Elasticsearch, you can perform the following steps to delete the cluster you created for the example and its data to avoid resource wastage.</p>
<p id="css_01_0007__p872752313816">After you delete a cluster, its data cannot be restored. Exercise caution when deleting a cluster.</p>
<ol id="css_01_0007__ol197114498387"><li id="css_01_0007__li271949183818">Log in to the <span id="css_01_0007__text9242163412576">CSS</span> management console. In the left navigation pane, click <span class="uicontrol" id="css_01_0007__uicontrol131976736917344"><b>Clusters</b></span> to switch to the <strong id="css_01_0007__b19839183919612">Clusters</strong> page.</li><li id="css_01_0007__li671154953820">Locate the row that contains cluster <span class="parmname" id="css_01_0007__parmname47927612562"><b>Es-xfx</b></span> and click <span class="uicontrol" id="css_01_0007__uicontrol711114465463"><b>More</b></span> &gt; <strong id="css_01_0007__b025713403818">Delete</strong> in the <strong id="css_01_0007__b7112104617469">Operation</strong> column.</li><li id="css_01_0007__li13711149113813">In the displayed dialog box, enter the name of the cluster to be deleted and click <strong id="css_01_0007__b134517496378">OK</strong>.</li></ol>
<div class="note" id="css_01_0007__note462220010358"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0007__p13627600357">After you delete a cluster, its data cannot be restored. Exercise caution when deleting a cluster.</p>
</div></div>
<ol id="css_01_0007__ol197114498387"><li id="css_01_0007__li271949183818">Log in to the <span id="css_01_0007__text9242163412576">CSS</span> management console. In the navigation pane on the left, choose <span class="uicontrol" id="css_01_0007__uicontrol131976736917344"><b>Clusters</b></span> &gt; <strong id="css_01_0007__b19839183919612">Elasticsearch</strong>.</li><li id="css_01_0007__li671154953820">Locate the row that contains cluster <span class="parmname" id="css_01_0007__parmname47927612562"><b>Es-xfx</b></span> and click <span class="uicontrol" id="css_01_0007__uicontrol711114465463"><b>More</b></span> &gt; <strong id="css_01_0007__b025713403818">Delete</strong> in the <strong id="css_01_0007__b7112104617469">Operation</strong> column.</li><li id="css_01_0007__li13711149113813">In the displayed dialog box, enter the name of the cluster to be deleted and click <strong id="css_01_0007__b134517496378">OK</strong>.</li></ol>
</div>
</div>
<div>
@ -299,10 +300,3 @@
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

8
docs/css/umn/css_01_0008.html
View File

@ -4,12 +4,20 @@
<div id="body0000001282339370"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_04_0023.html">Multi-AZ HA</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_04_0019.html">Clusters in Security Mode</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0011.html">Creating an Elasticsearch Cluster in Security Mode</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0094.html">Creating an Elasticsearch Cluster in Non-Security Mode</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0190.html">Accessing an Elasticsearch Cluster</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0012.html">Accessing a Cluster</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0185.html">Viewing Cluster Information</a></strong><br>
</li>
</ul>
</div>

2
docs/css/umn/css_01_0009.html
View File

@ -10,7 +10,7 @@
</li>
<li class="ulchildlink"><strong><a href="css_01_0033.html">Index Backup and Restoration</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0031.html">Modifying Specifications</a></strong><br>
<li class="ulchildlink"><strong><a href="css_01_0058.html">Binding an Enterprise Project</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0014.html">Restarting a Cluster</a></strong><br>
</li>

199
docs/css/umn/css_01_0011.html
View File

File diff suppressed because it is too large Load Diff

1581
docs/css/umn/css_01_0012.html
View File

File diff suppressed because it is too large Load Diff

21
docs/css/umn/css_01_0014.html
View File

@ -1,13 +1,20 @@
<a name="css_01_0014"></a><a name="css_01_0014"></a>
<h1 class="topictitle1">Restarting a Cluster</h1>
<div id="body0000001334459445"><p id="css_01_0014__p16296586613">If a cluster becomes faulty, you can restart it to check if it can run normally. Only clusters in the <span class="parmname" id="css_01_0014__parmname259181158"><b>Available</b></span> or <span class="parmname" id="css_01_0014__parmname1353503833"><b>Abnormal</b></span> status can be restarted.</p>
<div class="section" id="css_01_0014__section144817324321"><h4 class="sectiontitle">Quick Restart</h4><ul id="css_01_0014__ul49520302474"><li id="css_01_0014__li19950303471">The cluster is in the <span class="parmname" id="css_01_0014__parmname107392306"><b>Available</b></span> or <span class="parmname" id="css_01_0014__parmname244742386"><b>Abnormal</b></span> status.</li><li id="css_01_0014__li788484074719">There are no running tasks, such as importing data, searching for data on the cluster.</li></ul>
<div class="notice" id="css_01_0014__note13745848122116"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="css_01_0014__ul0234702403"><li id="css_01_0014__li152341701403">The cluster will be unavailable during quick restart. If quick restart fails, data may be lost or the cluster may become unavailable. Therefore, exercise caution when performing this operation.</li><li id="css_01_0014__li6675205994314">If the cluster you want to restart is available, you are advised to stop all data processing tasks on the cluster before restarting it. If there are running tasks, for example, importing data, searching for data, the transmitted data may be lost upon the restart. Therefore you are advised to stop all cluster tasks before the quick restart.</li></ul>
</div></div>
<ol id="css_01_0014__ol59716110339"><li id="css_01_0014__li93271911152510">Log in to the <span id="css_01_0014__text16667181662611">CSS</span> management console.</li><li id="css_01_0014__li163277114258">Click <span class="uicontrol" id="css_01_0014__uicontrol5967163616264"><b>Clusters</b></span> to switch to the <strong id="css_01_0014__b842352706142756">Clusters</strong> page. In the row that contains the cluster you want to restart, click <span class="uicontrol" id="css_01_0014__uicontrol531390369142823"><b><span id="css_01_0014__text1377280500142823">More &gt; Restart</span></b></span> in the <span class="parmname" id="css_01_0014__parmname1696723617269"><b>Operation</b></span> column. The <strong id="css_01_0014__b55488491813">Restart Cluster</strong> page is displayed. Select <strong id="css_01_0014__b157313552115">Quick Restart</strong>.<p id="css_01_0014__p142881347172614"></p>
<ul id="css_01_0014__ul8288134732613"><li id="css_01_0014__li22889479268">You can quick restart nodes by <strong id="css_01_0014__b4158064720">Node type</strong> or <strong id="css_01_0014__b1515916619712">Node name</strong>. If you select <strong id="css_01_0014__b8894115316257">Node type</strong>, then you can select multiple node types and perform quick restart at the time. If you select <strong id="css_01_0014__b0665123982915">Node name</strong>, you can perform quick restart only on one node at a time.</li><li id="css_01_0014__li9288144710268">The cluster is unavailable during quick restart.</li></ul>
</li><li id="css_01_0014__li129710111332">Refresh the page and check the cluster status. During the restart, the cluster status is <span class="parmvalue" id="css_01_0014__parmvalue1888591966"><b><span id="css_01_0014__text893002244">Processing</span></b></span>, and the task status is <span class="parmvalue" id="css_01_0014__parmvalue1047968926"><b>Restarting</b></span>. If the cluster status changes to <span class="parmvalue" id="css_01_0014__parmvalue301409242"><b>Available</b></span>, the cluster has been restarted successfully. If the cluster status changes to <span class="parmvalue" id="css_01_0014__parmvalue1390470181814"><b>Abnormal</b></span>, contact the technical support for troubleshooting.</li></ol>
<div id="body0000001334459445"><p id="css_01_0014__p16296586613">If a cluster becomes faulty, you can restart it to check if it can run normally.</p>
<div class="section" id="css_01_0014__section5511250184611"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0014__ul1188663672716"><li id="css_01_0014__li158861636162718">The target cluster is not frozen and has no task in progress.</li><li id="css_01_0014__li19886193642716">If a cluster is available, ensure that it has stopped processing service requests (such as importing data and searching for data). Otherwise, data may be lost when the cluster is restarted. You are advised to perform this operation during off-peak hours.</li></ul>
</div>
<div class="section" id="css_01_0014__section5655101110386"><h4 class="sectiontitle">Context</h4><p id="css_01_0014__p82405141385">CSS supports quick restart and rolling restart.</p>
<div class="p" id="css_01_0014__p576222812384"><strong id="css_01_0014__b1927144863812"><a href="#css_01_0014__section144817324321">Quick Restart</a></strong><ul id="css_01_0014__ul16520140203912"><li id="css_01_0014__li20520305396">All clusters support this function.</li><li id="css_01_0014__li6615718164312">If you select a node type for quick restart, all nodes of the selected type will be restarted together.</li><li id="css_01_0014__li14520180113920">If you select a node name for quick restart, only the specified node will be restarted.</li><li id="css_01_0014__li15142832104512">The cluster is unavailable during quick restart.</li></ul>
</div>
<div class="p" id="css_01_0014__p6128833193818"><strong id="css_01_0014__b15477105143913"><a href="#css_01_0014__section1533564513219">Rolling Restart</a></strong><ul id="css_01_0014__ul384620179392"><li id="css_01_0014__li13389305394">Rolling restart is supported only when a cluster has more than three nodes (including master nodes, client nodes, and cold data nodes).</li><li id="css_01_0014__li151315237450">Rolling restart can be performed only by specifying node types. If you select a node type for rolling restart, the nodes of the selected type will be restarted in sequence.</li><li id="css_01_0014__li2846117163913">During the rolling restart, only the nodes that are being restarted are unavailable and other nodes can run normally.</li><li id="css_01_0014__li1156733104113">When the data volume is large, rolling restart will take a long time.</li></ul>
</div>
</div>
<div class="section" id="css_01_0014__section144817324321"><a name="css_01_0014__section144817324321"></a><a name="section144817324321"></a><h4 class="sectiontitle">Quick Restart</h4><ol id="css_01_0014__ol59716110339"><li id="css_01_0014__li93271911152510">Log in to the <span id="css_01_0014__text16667181662611">CSS</span> management console.</li><li id="css_01_0014__li163277114258">In the navigation pane on the left, choose <strong id="css_01_0014__b030318381241">Clusters</strong> &gt; <strong id="css_01_0014__b8303153817248">Elasticsearch</strong>. On the displayed <strong id="css_01_0014__b9303838122419">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0014__b10303838192410">More</strong> &gt; <strong id="css_01_0014__b4303838102412">Restart</strong> in the <strong id="css_01_0014__b103031838142412">Operation</strong> column.</li><li id="css_01_0014__li2820155185915">On the <strong id="css_01_0014__b4392142141814">Restart Cluster</strong> page, select <strong id="css_01_0014__b725525561811">Quick Restart</strong>.<p id="css_01_0014__p893112380447">You can quick restart nodes by <strong id="css_01_0014__b6506175621814">Node type</strong> or <strong id="css_01_0014__b165071856111816">Node name</strong>. If you select <strong id="css_01_0014__b1836518091919">Node type</strong>, then you can select multiple node types and perform quick restart at the time. If you select <strong id="css_01_0014__b1225167141915">Node name</strong>, you can perform quick restart only on one node at a time.</p>
</li><li id="css_01_0014__li129710111332">Refresh the page and check the cluster status. During the restart, the cluster status is <span class="parmvalue" id="css_01_0014__parmvalue37917438911533"><b>Processing</b></span>, and the task status is <span class="parmvalue" id="css_01_0014__parmvalue624425664115314"><b>Restarting</b></span>. If the cluster status changes to <span class="parmvalue" id="css_01_0014__parmvalue1024814826142925"><b>Available</b></span>, the cluster has been restarted successfully.</li></ol>
</div>
<div class="section" id="css_01_0014__section1533564513219"><a name="css_01_0014__section1533564513219"></a><a name="section1533564513219"></a><h4 class="sectiontitle">Rolling Restart</h4><ol id="css_01_0014__ol14670132413362"><li id="css_01_0014__li176702024193612">Log in to the <span id="css_01_0014__text467002423615">CSS</span> management console.</li><li id="css_01_0014__li1067012453614">In the navigation pane on the left, choose <strong id="css_01_0014__b19567845162411">Clusters</strong> &gt; <strong id="css_01_0014__b356704517248">Elasticsearch</strong>. On the displayed <strong id="css_01_0014__b556874517241">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0014__b13568164522417">More</strong> &gt; <strong id="css_01_0014__b1056944552420">Restart</strong> in the <strong id="css_01_0014__b95691245112415">Operation</strong> column.</li><li id="css_01_0014__li39318693">On the <strong id="css_01_0014__b16868122120190">Restart Cluster</strong> page, select <strong id="css_01_0014__b61141824111919">Rolling Restart</strong>.<p id="css_01_0014__p15868102621017">You can perform rolling restart by <strong id="css_01_0014__b198126151912">Node type</strong>. Select specific node types for restart.</p>
</li><li id="css_01_0014__li9670024103619">Refresh the page and check the cluster status. During the restart, the cluster status is <span class="parmvalue" id="css_01_0014__parmvalue423772516"><b>Processing</b></span>, and the task status is <span class="parmvalue" id="css_01_0014__parmvalue2054022180"><b>Restarting</b></span>. If the cluster status changes to <span class="parmvalue" id="css_01_0014__parmvalue420594605"><b>Available</b></span>, the cluster has been restarted successfully.</li></ol>
</div>
</div>
<div>

2
docs/css/umn/css_01_0024.html
View File

@ -49,7 +49,7 @@
{"index":{}}
{"productName":"Latest art shirts for women in 2017 autumn","size":"L"}</pre>
<p id="css_01_0024__p116351525183015">The command output is similar to that shown in <a href="#css_01_0024__fig86351225133018">Figure 1</a>. If the value of the <span class="parmname" id="css_01_0024__parmname19219201981614"><b>errors</b></span> field in the result is <span class="parmvalue" id="css_01_0024__parmvalue1321951912167"><b>false</b></span>, the data is successfully imported.</p>
<div class="fignone" id="css_01_0024__fig86351225133018"><a name="css_01_0024__fig86351225133018"></a><a name="fig86351225133018"></a><span class="figcap"><b>Figure 1 </b>Response message</span><br><span><img id="css_01_0024__image19635132563018" src="en-us_image_0000001338956001.png" width="NaN" height="NaN"></span></div>
<div class="fignone" id="css_01_0024__fig86351225133018"><a name="css_01_0024__fig86351225133018"></a><a name="fig86351225133018"></a><span class="figcap"><b>Figure 1 </b>Response message</span><br><span><img id="css_01_0024__image19635132563018" src="en-us_image_0000001525365841.png"></span></div>
</li></ol>
</div>
</div>

41
docs/css/umn/css_01_0033.html
View File

@ -8,10 +8,7 @@
<div class="section" id="css_01_0033__section914018211934"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0033__p1353111291039">To use the function of creating or restoring snapshots, the account or IAM user that logs in to the <span id="css_01_0033__text384635914619">CSS</span> management console must have both of the following permissions:</p>
<ul id="css_01_0033__ul10364413962"><li id="css_01_0033__li111102134120"><span class="parmname" id="css_01_0033__parmname195505992117166"><b>Tenant Administrator</b></span> for project <span class="parmname" id="css_01_0033__parmname77759080917166"><b>OBS</b></span> in region <span class="parmname" id="css_01_0033__parmname127798320017166"><b>Global service</b></span></li><li id="css_01_0033__li754585517113"><span class="parmname" id="css_01_0033__parmname748916545244"><b>CSS Administrator</b></span> in the current region</li></ul>
</div>
<div class="section" id="css_01_0033__section18551039928"><a name="css_01_0033__section18551039928"></a><a name="section18551039928"></a><h4 class="sectiontitle">Managing Automatic Snapshot Creation</h4><ol id="css_01_0033__ol1072514121135"><li id="css_01_0033__li07251912434">In the left navigation pane of the <span id="css_01_0033__text19360182541711">CSS</span> management console, click <span class="parmname" id="css_01_0033__parmname15282708197"><b>Clusters</b></span>.</li><li id="css_01_0033__li392216231538">On the <span class="wintitle" id="css_01_0033__wintitle803835227104550"><b>Clusters</b></span> page that is displayed, click the name of the target cluster. On the displayed page, click <span class="wintitle" id="css_01_0033__wintitle14518182417449"><b>Cluster Snapshots</b></span>.<p id="css_01_0033__p1521215181812">Alternatively, on the <span class="wintitle" id="css_01_0033__wintitle477136537"><b>Clusters</b></span> page, locate the row that contains the target cluster and click <span class="uicontrol" id="css_01_0033__uicontrol148571443193"><b>More &gt; Back Up and Restore</b></span> in the <span class="parmname" id="css_01_0033__parmname9501131031911"><b>Operation</b></span> column to switch to the <span class="wintitle" id="css_01_0033__wintitle159181351161810"><b>Cluster Snapshots</b></span> page.</p>
</li><li id="css_01_0033__li15189162455017">On the displayed <span class="wintitle" id="css_01_0033__wintitle66381133203511"><b>Cluster Snapshots</b></span> page, click the icon to the right of <span class="parmname" id="css_01_0033__parmname106381433183513"><b>Cluster Snapshot</b></span> to enable the cluster snapshot function.<p id="css_01_0033__p1778916379331"><span><img id="css_01_0033__image167893373336" src="en-us_image_0000001286436602.png"></span> indicates that the cluster snapshot function is disabled.</p>
<p id="css_01_0033__p818982685014"><span><img id="css_01_0033__image8410195516444" src="en-us_image_0000001286116718.png"></span> indicates that the cluster snapshot function is enabled.</p>
</li><li id="css_01_0033__li1597517249415"><a name="css_01_0033__li1597517249415"></a><a name="li1597517249415"></a>(Optional) After the cluster snapshot function is enabled, <span id="css_01_0033__text893113713717">CSS</span> automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click <span><img id="css_01_0033__image1493257471" src="en-us_image_0000001286116714.png"></span> to the right of <strong id="css_01_0033__b149326714716">Basic Configuration</strong>. To ensure the security of snapshot data, you can select a key to encrypt the snapshot.<p id="css_01_0033__p088212510411">In the displayed <strong id="css_01_0033__b175492416811">Edit Basic Configuration</strong> dialog box, you can either select an existing OBS bucket and IAM agency or create an OBS bucket and IAM agency. To create an OBS bucket, click <span class="uicontrol" id="css_01_0033__uicontrol13611524388"><b>Create Bucket</b></span>. To create an IAM agency, click <span class="uicontrol" id="css_01_0033__uicontrol861424186"><b>Create IAM Agency</b></span>. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/obs/en-us_topic_0045853662.html" target="_blank" rel="noopener noreferrer">Creating a Bucket</a> and <a href="https://docs.otc.t-systems.com/en-us/usermanual/iam/en-us_topic_0046613147.html" target="_blank" rel="noopener noreferrer">Creating an Agency</a>. To encrypt the snapshot, select <strong id="css_01_0033__b190019283419">Snapshot Encryption</strong> and select a key.</p>
<div class="section" id="css_01_0033__section18551039928"><a name="css_01_0033__section18551039928"></a><a name="section18551039928"></a><h4 class="sectiontitle">Managing Automatic Snapshot Creation</h4><ol id="css_01_0033__ol1072514121135"><li id="css_01_0033__li07251912434">In the left navigation pane of the <span id="css_01_0033__text19360182541711">CSS</span> management console, click <span class="parmname" id="css_01_0033__parmname15282708197"><b>Clusters</b></span>.</li><li id="css_01_0033__li392216231538">On the <span class="wintitle" id="css_01_0033__wintitle803835227104550"><b>Clusters</b></span> page that is displayed, click the name of the target cluster. On the displayed page, click <span class="wintitle" id="css_01_0033__wintitle14518182417449"><b>Cluster Snapshots</b></span>.</li><li id="css_01_0033__li15189162455017">On the displayed <span class="wintitle" id="css_01_0033__wintitle66381133203511"><b>Cluster Snapshots</b></span> page, click the icon to the right of <span class="parmname" id="css_01_0033__parmname106381433183513"><b>Cluster Snapshot</b></span> to enable the cluster snapshot function.</li><li id="css_01_0033__li1597517249415"><a name="css_01_0033__li1597517249415"></a><a name="li1597517249415"></a>(Optional) After the cluster snapshot function is enabled, <span id="css_01_0033__text893113713717">CSS</span> automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click <span><img id="css_01_0033__image1493257471" src="en-us_image_0000001474246364.png"></span> to the right of <strong id="css_01_0033__b149326714716">Basic Configuration</strong>. To ensure the security of snapshot data, you can select a key to encrypt the snapshot.<p id="css_01_0033__p088212510411">In the displayed <strong id="css_01_0033__b175492416811">Edit Basic Configuration</strong> dialog box, you can either select an existing OBS bucket and IAM agency or create an OBS bucket and IAM agency. To create an OBS bucket, click <span class="uicontrol" id="css_01_0033__uicontrol13611524388"><b>Create Bucket</b></span>. To create an IAM agency, click <span class="uicontrol" id="css_01_0033__uicontrol861424186"><b>Create IAM Agency</b></span>. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/obs/en-us_topic_0045853662.html" target="_blank" rel="noopener noreferrer">Creating a Bucket</a> and <a href="https://docs.otc.t-systems.com/en-us/usermanual/iam/en-us_topic_0046613147.html" target="_blank" rel="noopener noreferrer">Creating an Agency</a>. To encrypt the snapshot, select <strong id="css_01_0033__b190019283419">Snapshot Encryption</strong> and select a key.</p>
<div class="p" id="css_01_0033__p87651121105618">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0033__table109611127114919" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="css_01_0033__row595810278493"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.5.2.4.5.1.2.4.1.1"><p id="css_01_0033__p695812714916">Parameter</p>
</th>
@ -51,29 +48,26 @@
</table>
</div>
</div>
<div class="fignone" id="css_01_0033__fig5965112764919"><span class="figcap"><b>Figure 1 </b>Edit Basic configuration</span><br><span><img id="css_01_0033__image1143918271686" src="en-us_image_0000001338955921.png" width="478.8" height="249.53061" title="Click to enlarge" class="imgResize"></span></div>
<p id="css_01_0033__p1623118111318"></p>
</li><li id="css_01_0033__li17312102775013">Click the icon to the right of <span class="parmname" id="css_01_0033__parmname79609170530"><b>Automatic Snapshot Creation</b></span> to enable the automatic snapshot creation function.<p id="css_01_0033__p149181435135220"><span><img id="css_01_0033__image169181835165213" src="en-us_image_0000001338836473.png" width="42.892500000000005" height="24.9375" title="Click to enlarge" class="imgResize"></span> indicates that the automatic snapshot function is enabled.</p>
<p id="css_01_0033__p451318123509"><span><img id="css_01_0033__image1837225104813" src="en-us_image_0000001286436602.png"></span> indicates that the automatic snapshot function is disabled.</p>
</li><li id="css_01_0033__li2251154818503">In the displayed <span class="wintitle" id="css_01_0033__wintitle4492124155012"><b>Edit Snapshot Policy</b></span> dialog box, specify parameters as required.<ul id="css_01_0033__ul1149362415019"><li id="css_01_0033__li20492132417509"><strong id="css_01_0033__b1632713121415">Snapshot Name Prefix</strong>: Enter a maximum of 31 characters starting with a letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed.. A snapshot name consists of a snapshot name prefix and a timestamp. For example, <strong id="css_01_0033__b18316113210165">snapshot-2018022405925</strong>.</li><li id="css_01_0033__li202435371780"><span class="parmname" id="css_01_0033__parmname1371612219571"><b>Time Zone</b></span>: indicates the time zone for the backup time. Specify <span class="parmname" id="css_01_0033__parmname54531038111517"><b>Backup Started</b></span> based on the time zone.</li><li id="css_01_0033__li141069525163"><span class="parmname" id="css_01_0033__parmname2068818825618"><b>Index</b></span>: Enter the name of an index. The automatic snapshot creation function supports backup of certain indices in the cluster. Uppercase letters, spaces, and certain special characters (including "\&lt;|&gt;/?) are not allowed. Use commas (,) to separate multiple indices. If you do not specify this parameter, data of all indices in the cluster is backed up by default. You can use the asterisk (<span class="parmname" id="css_01_0033__parmname82931638265"><b>*</b></span>) to back up data of certain indices. For example, if you enter <strong id="css_01_0033__b1529463192613">index*</strong>, then data of indices with the name prefix of <strong id="css_01_0033__b829417314269">index</strong> will be backed up.<p id="css_01_0033__p7407254171620">You can run the <strong id="css_01_0033__b12606169152316">GET /_cat/indices</strong> command in Kibana to query names of all indices in the cluster. You can then enter the names of the indices you want to back up.</p>
</li><li id="css_01_0033__li164929248506"><span class="parmname" id="css_01_0033__parmname3680251557"><b>Backup Started</b></span>: indicates the time when the backup starts automatically every day. You can specify this parameter only in hours and not minutes, for example, <strong id="css_01_0033__b868018516551">00:00</strong> or <strong id="css_01_0033__b1768005125511">01:00</strong>. The value ranges from <strong id="css_01_0033__b8681254558">00:00</strong> to <strong id="css_01_0033__b146811851559">23:00</strong>. Select the backup time from the drop-down list box.</li><li id="css_01_0033__li9493824155013"><span class="parmname" id="css_01_0033__parmname2457445135517"><b>Retention Period (days)</b></span>: indicates the duration when snapshots are retained in the OBS bucket, in days. The value ranges from <strong id="css_01_0033__b1151115755418">1</strong> to <strong id="css_01_0033__b134975119556">90</strong>. You can specify this parameter as required. The system automatically deletes snapshots that are retained over the specified retention period on the half hour. For example, if you set the snapshot policy as shown in <a href="#css_01_0033__fig1797311351298">Figure 2</a>, the system will automatically delete in 35 days at 00:30 the automated snapshots that were created 35 days earlier at 00:00.</li></ul>
<div class="fignone" id="css_01_0033__fig1797311351298"><a name="css_01_0033__fig1797311351298"></a><a name="fig1797311351298"></a><span class="figcap"><b>Figure 2 </b>Automatic snapshot creation</span><br><span><img id="css_01_0033__image890613211913" src="en-us_image_0000001339036357.png" width="389.02500000000003" height="326.12863500000003" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="css_01_0033__li175372485117">Click <span class="uicontrol" id="css_01_0033__uicontrol64700751811611"><b>OK</b></span>.<p id="css_01_0033__p263819436501">After the policy for automatic snapshot creation is created, the policy information will be displayed on the <strong id="css_01_0033__b19901623182914">Cluster Snapshots</strong> page. If you need to change the policy due to business changes, click <span><img id="css_01_0033__image4370919114915" src="en-us_image_0000001286116714.png"></span>.</p>
<p id="css_01_0033__p156381843125015">Snapshots that are automatically created according to the snapshot policy are displayed in the snapshot list, along with manually created snapshots. You can distinguish them by the <strong id="css_01_0033__b56548137183">Snapshot Type</strong> setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click <span><img id="css_01_0033__image887164910374" src="en-us_image_0000001286436618.png"></span> to sort snapshots based on related parameter settings.</p>
<div class="fignone" id="css_01_0033__fig4952193916114"><span class="figcap"><b>Figure 3 </b>Automatic snapshot creation</span><br><span><img id="css_01_0033__image58049126119" src="en-us_image_0000001286116726.png" width="462.84000000000003" height="190.010849" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="css_01_0033__li17312102775013">Click the icon to the right of <span class="parmname" id="css_01_0033__parmname79609170530"><b>Automatic Snapshot Creation</b></span> to enable the automatic snapshot creation function.</li><li id="css_01_0033__li2251154818503">In the displayed <span class="wintitle" id="css_01_0033__wintitle4492124155012"><b>Edit Snapshot Policy</b></span> dialog box, specify parameters as required.<ul id="css_01_0033__ul1149362415019"><li id="css_01_0033__li20492132417509"><strong id="css_01_0033__b1632713121415">Snapshot Name Prefix</strong>: Enter a maximum of 31 characters starting with a letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed.. A snapshot name consists of a snapshot name prefix and a timestamp. For example, <strong id="css_01_0033__b18316113210165">snapshot-2018022405925</strong>.</li><li id="css_01_0033__li202435371780"><span class="parmname" id="css_01_0033__parmname1371612219571"><b>Time Zone</b></span>: indicates the time zone for the backup time. Specify <span class="parmname" id="css_01_0033__parmname54531038111517"><b>Backup Started</b></span> based on the time zone.</li><li id="css_01_0033__li141069525163"><span class="parmname" id="css_01_0033__parmname2068818825618"><b>Index</b></span>: Enter the name of an index. The automatic snapshot creation function supports backup of certain indices in the cluster. Uppercase letters, spaces, and certain special characters (including "\&lt;|&gt;/?) are not allowed. Use commas (,) to separate multiple indices. If you do not specify this parameter, data of all indices in the cluster is backed up by default. You can use the asterisk (<span class="parmname" id="css_01_0033__parmname82931638265"><b>*</b></span>) to back up data of certain indices. For example, if you enter <strong id="css_01_0033__b1529463192613">index*</strong>, then data of indices with the name prefix of <strong id="css_01_0033__b829417314269">index</strong> will be backed up.<p id="css_01_0033__p7407254171620">You can run the <strong id="css_01_0033__b12606169152316">GET /_cat/indices</strong> command in Kibana to query names of all indices in the cluster. You can then enter the names of the indices you want to back up.</p>
</li><li id="css_01_0033__li164929248506"><span class="parmname" id="css_01_0033__parmname3680251557"><b>Backup Started</b></span>: indicates the time when the backup starts automatically every day. You can specify this parameter only in hours and not minutes, for example, <strong id="css_01_0033__b868018516551">00:00</strong> or <strong id="css_01_0033__b1768005125511">01:00</strong>. The value ranges from <strong id="css_01_0033__b8681254558">00:00</strong> to <strong id="css_01_0033__b146811851559">23:00</strong>. Select the backup time from the drop-down list box.</li><li id="css_01_0033__li9493824155013"><span class="parmname" id="css_01_0033__parmname2457445135517"><b>Retention Period (days)</b></span>: indicates the duration when snapshots are retained in the OBS bucket, in days. The value ranges from <strong id="css_01_0033__b1151115755418">1</strong> to <strong id="css_01_0033__b134975119556">90</strong>. You can specify this parameter as required. The system automatically deletes snapshots that are retained over the specified retention period on the half hour. For example, if you set the snapshot policy as shown in <a href="#css_01_0033__fig1797311351298">Figure 1</a>, the system will automatically delete in 35 days at 00:30 the automated snapshots that were created 35 days earlier at 00:00.</li></ul>
<div class="fignone" id="css_01_0033__fig1797311351298"><a name="css_01_0033__fig1797311351298"></a><a name="fig1797311351298"></a><span class="figcap"><b>Figure 1 </b>Automatic snapshot creation</span><br><span><img id="css_01_0033__image890613211913" src="en-us_image_0000001474725844.png"></span></div>
</li><li id="css_01_0033__li175372485117">Click <span class="uicontrol" id="css_01_0033__uicontrol64700751811611"><b>OK</b></span>.<p id="css_01_0033__p263819436501">After the policy for automatic snapshot creation is created, the policy information will be displayed on the <strong id="css_01_0033__b19901623182914">Cluster Snapshots</strong> page. If you need to change the policy due to business changes, click <span><img id="css_01_0033__image4370919114915" src="en-us_image_0000001474246364.png"></span>.</p>
<p id="css_01_0033__p156381843125015">Snapshots that are automatically created according to the snapshot policy are displayed in the snapshot list, along with manually created snapshots. You can distinguish them by the <strong id="css_01_0033__b56548137183">Snapshot Type</strong> setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click <span><img id="css_01_0033__image887164910374" src="en-us_image_0000001474246376.png"></span> to sort snapshots based on related parameter settings.</p>
<div class="fignone" id="css_01_0033__fig4952193916114"><span class="figcap"><b>Figure 2 </b>Automatic snapshot creation</span><br><span><img id="css_01_0033__image58049126119" src="en-us_image_0000001524766289.png"></span></div>
</li><li id="css_01_0033__li48981519132317">(Optional) Disable the automatic snapshot creation function.<p id="css_01_0033__p622541042417"><a name="css_01_0033__li48981519132317"></a><a name="li48981519132317"></a>After you disable the automatic snapshot creation function, the system stops automatic creation of snapshots. If the system is creating a snapshot based on the automatic snapshot creation policy and the snapshot is not yet displayed in the snapshot list, you cannot disable the automatic snapshot creation function. In this case, if you click the button next to <strong id="css_01_0033__b129214495615">Automatic Snapshot Creation</strong>, a message is displayed, indicating that you cannot disable the function. You are advised to disable the function after the system completes automatic creation of the snapshot, and the created snapshot is displayed in the snapshot list.</p>
<p id="css_01_0033__p196228429309">When disabling the automatic snapshot creation function, you can choose whether to delete the snapshots that have been automatically created by selecting <span class="parmname" id="css_01_0033__parmname1311414393420"><b>Delete automated snapshots</b></span> in the displayed dialog box. By default, automatically created snapshots are not deleted.</p>
<ul id="css_01_0033__ul599135212309"><li id="css_01_0033__li5991052103012">If you do not select <span class="parmname" id="css_01_0033__parmname1183151161215"><b>Delete automated snapshots</b></span>, automatically created snapshots are not deleted when you disable the automatic snapshot creation function. You can manually delete them later. For details, see <a href="#css_01_0033__section3105193716428">Deleting a Snapshot</a>. If you do not manually delete the automatically created snapshots and enable the automatic snapshot creation function again, then all snapshots with <span class="parmname" id="css_01_0033__parmname186791716181118"><b>Snapshot Type</b></span> set to <strong id="css_01_0033__b1868091681118">Automated</strong> in the snapshot list of the cluster can only be automatically deleted by the system. Specifically, the system automatically deletes snapshots based on the snapshot policy configured when you enable the automatic snapshot creation function again. For example, if you set <strong id="css_01_0033__b16983134319121">Retention Period (days)</strong> to <strong id="css_01_0033__b11834145615124">10</strong>, the system will automatically delete the snapshots that have been retained for more than 10 days.</li><li id="css_01_0033__li989615428317">If you select <span class="parmname" id="css_01_0033__parmname1759414932"><b>Delete automated snapshots</b></span>, all snapshots with <span class="parmname" id="css_01_0033__parmname1978752653214"><b>Snapshot Type</b></span> set to <strong id="css_01_0033__b1145124833914">Automated</strong> in the snapshot list will be deleted when you disable the automatic snapshot creation function.</li></ul>
</li></ol>
</div>
<div class="section" id="css_01_0033__section43906502025"><a name="css_01_0033__section43906502025"></a><a name="section43906502025"></a><h4 class="sectiontitle">Manually Creating a Snapshot</h4><ol id="css_01_0033__ol1597157201819"><li id="css_01_0033__li928020151910">In the left navigation pane of the <span id="css_01_0033__text1622158152316">CSS</span> management console, click <span class="parmname" id="css_01_0033__parmname1962278152313"><b>Clusters</b></span>.</li><li id="css_01_0033__li12822019195">On the <span class="wintitle" id="css_01_0033__wintitle1528218001917"><b>Clusters</b></span> page that is displayed, click the name of the target cluster. On the displayed page, click <span class="wintitle" id="css_01_0033__wintitle31445126442"><b>Cluster Snapshots</b></span>.<p id="css_01_0033__p13860113612194">Alternatively, on the <span class="wintitle" id="css_01_0033__wintitle1582091415440"><b>Clusters</b></span> page, locate the row that contains the target cluster and click <span class="uicontrol" id="css_01_0033__uicontrol17798537171919"><b>More</b></span> &gt; <span class="uicontrol" id="css_01_0033__uicontrol814301719112"><b>Back Up and Restore</b></span> in the <span class="parmname" id="css_01_0033__parmname208201914194412"><b>Operation</b></span> column to switch to the <span class="wintitle" id="css_01_0033__wintitle182101494419"><b>Cluster Snapshots</b></span> page.</p>
</li><li id="css_01_0033__li05161823125719">On the displayed <span class="wintitle" id="css_01_0033__wintitle351616231575"><b>Cluster Snapshots</b></span> page, click the icon to the right of <span class="parmname" id="css_01_0033__parmname48147403573"><b>Cluster Snapshot</b></span> to enable the cluster snapshot function.<p id="css_01_0033__p1611195019520"><span><img id="css_01_0033__image1611185014528" src="en-us_image_0000001286436602.png"></span> indicates that the cluster snapshot function is disabled.</p>
<p id="css_01_0033__p08141040195719"><span><img id="css_01_0033__image7713134075419" src="en-us_image_0000001286596218.png"></span> indicates that the cluster snapshot function is enabled.</p>
</li><li id="css_01_0033__li1371711473">(Optional) After the cluster snapshot function is enabled, <span id="css_01_0033__text089714310162">CSS</span> automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click <span><img id="css_01_0033__image17898154371617" src="en-us_image_0000001286116714.png"></span> to the right of <strong id="css_01_0033__b9898154311165">Basic Configuration</strong>. For details about how to configure parameters involved in the basic configuration, see <a href="#css_01_0033__li1597517249415">4</a>.</li><li id="css_01_0033__li328516081910">After basic configurations are completed, click <strong id="css_01_0033__b1674112462533">Create</strong>.<ul id="css_01_0033__ul186887875617"><li id="css_01_0033__li143570341602"><strong id="css_01_0033__b19586434162914">Name</strong> indicates the name of the manually created snapshot, which can contain 4 to 64 characters and must start with a lowercase letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed. For snapshots you create manually, you can specify the snapshot name. The system will not automatically add the time information to the snapshot name.</li><li id="css_01_0033__li126881280561"><span class="parmname" id="css_01_0033__parmname1821891188"><b>Index</b></span>: Enter the name of an index. The manually created snapshot can back up data of certain indices in the cluster. The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\&lt;|&gt;/?) are not allowed. Multiple index names are separated by commas (,). If you do not specify this parameter, data of all indices in the cluster is backed up by default. You can use the asterisk (<span class="parmname" id="css_01_0033__parmname2111668232"><b>*</b></span>) to back up data of certain indices. For example, if you enter <strong id="css_01_0033__b1584973572">2018-06*</strong>, then data of indices with the name prefix of <strong id="css_01_0033__b1240961941">2018-06</strong> will be backed up.<div class="note" id="css_01_0033__note97714385358"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0033__p677123811352">Run the <strong id="css_01_0033__b59612577164">GET /_cat/indices</strong> command in Kibana to query all index names in the cluster.</p>
</li><li id="css_01_0033__li05161823125719">On the displayed <span class="wintitle" id="css_01_0033__wintitle351616231575"><b>Cluster Snapshots</b></span> page, click the icon to the right of <span class="parmname" id="css_01_0033__parmname48147403573"><b>Cluster Snapshot</b></span> to enable the cluster snapshot function.<p id="css_01_0033__p1611195019520"><span><img id="css_01_0033__image1611185014528" src="en-us_image_0000001525365809.png"></span> indicates that the cluster snapshot function is disabled.</p>
<p id="css_01_0033__p08141040195719"><span><img id="css_01_0033__image7713134075419" src="en-us_image_0000001525365829.png"></span> indicates that the cluster snapshot function is enabled.</p>
</li><li id="css_01_0033__li1371711473">(Optional) After the cluster snapshot function is enabled, <span id="css_01_0033__text089714310162">CSS</span> automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click <span><img id="css_01_0033__image17898154371617" src="en-us_image_0000001474246364.png"></span> to the right of <strong id="css_01_0033__b9898154311165">Basic Configuration</strong>. For details about how to configure parameters involved in the basic configuration, see <a href="#css_01_0033__li1597517249415">4</a>.</li><li id="css_01_0033__li328516081910">After basic configurations are completed, click <strong id="css_01_0033__b1674112462533">Create</strong>.<ul id="css_01_0033__ul186887875617"><li id="css_01_0033__li143570341602"><strong id="css_01_0033__b19586434162914">Name</strong> indicates the name of the manually created snapshot, which can contain 4 to 64 characters and must start with a lowercase letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed. For snapshots you create manually, you can specify the snapshot name. The system will not automatically add the time information to the snapshot name.</li><li id="css_01_0033__li126881280561"><span class="parmname" id="css_01_0033__parmname1821891188"><b>Index</b></span>: Enter the name of an index. The manually created snapshot can back up data of certain indices in the cluster. The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\&lt;|&gt;/?) are not allowed. Multiple index names are separated by commas (,). If you do not specify this parameter, data of all indices in the cluster is backed up by default. You can use the asterisk (<span class="parmname" id="css_01_0033__parmname2111668232"><b>*</b></span>) to back up data of certain indices. For example, if you enter <strong id="css_01_0033__b1584973572">2018-06*</strong>, then data of indices with the name prefix of <strong id="css_01_0033__b1240961941">2018-06</strong> will be backed up.<div class="note" id="css_01_0033__note97714385358"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0033__p677123811352">Run the <strong id="css_01_0033__b59612577164">GET /_cat/indices</strong> command in Kibana to query all index names in the cluster.</p>
</div></div>
</li><li id="css_01_0033__li86881810563"><span class="parmname" id="css_01_0033__parmname8688118135615"><b>Description</b></span>: indicates the description of the created snapshot. The value contains 0 to 256 characters, and certain special characters (<span class="parmname" id="css_01_0033__parmname1958446316174047"><b>&lt;&gt;</b></span>) are not allowed.</li></ul>
<div class="fignone" id="css_01_0033__fig78421105010"><span class="figcap"><b>Figure 4 </b>Creating a snapshot</span><br><span><img id="css_01_0033__image1054884585019" src="en-us_image_0000001338716621.png" width="NaN" height="NaN"></span></div>
</li><li id="css_01_0033__li162011519182916">Click <span class="uicontrol" id="css_01_0033__uicontrol8133254474"><b>OK</b></span>.<p id="css_01_0033__p522415013344">After the snapshot is created, it will be displayed in the snapshot list. The status <strong id="css_01_0033__b1743911132515">Available</strong> indicates that the snapshot is created successfully. All automatically and manually created snapshots are displayed in the snapshot list. You can distinguish them by the <strong id="css_01_0033__b1896771072519">Snapshot Type</strong> setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click <span><img id="css_01_0033__image693591775317" src="en-us_image_0000001286436618.png"></span> to sort snapshots based on related parameter settings.</p>
<div class="fignone" id="css_01_0033__fig78421105010"><span class="figcap"><b>Figure 3 </b>Creating a snapshot</span><br><span><img id="css_01_0033__image1054884585019" src="en-us_image_0000001524766273.png"></span></div>
</li><li id="css_01_0033__li162011519182916">Click <span class="uicontrol" id="css_01_0033__uicontrol8133254474"><b>OK</b></span>.<p id="css_01_0033__p522415013344">After the snapshot is created, it will be displayed in the snapshot list. The status <strong id="css_01_0033__b1743911132515">Available</strong> indicates that the snapshot is created successfully. All automatically and manually created snapshots are displayed in the snapshot list. You can distinguish them by the <strong id="css_01_0033__b1896771072519">Snapshot Type</strong> setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click <span><img id="css_01_0033__image693591775317" src="en-us_image_0000001474246376.png"></span> to sort snapshots based on related parameter settings.</p>
</li></ol>
</div>
<div class="section" id="css_01_0033__section16538152014387"><a name="css_01_0033__section16538152014387"></a><a name="section16538152014387"></a><h4 class="sectiontitle">Restoring Data</h4><p id="css_01_0033__p67277218011">You can use snapshots whose <span class="parmname" id="css_01_0033__parmname732012502566"><b>Snapshot Status</b></span> is <span class="parmvalue" id="css_01_0033__parmvalue116606822101313"><b>Available</b></span> to restore cluster data. The stored snapshot data can be restored to other clusters.</p>
@ -82,9 +76,9 @@
<p id="css_01_0033__p1011936842"><span class="parmname" id="css_01_0033__parmname11775549718"><b>Rename Pattern</b></span>: Enter a regular expression. Indices that match the regular expression are restored. The default value <span class="parmvalue" id="css_01_0033__parmvalue215201401018"><b>index_(.+)</b></span> indicates restoring data of all indices. The value contains 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\&lt;|&gt;/?,) are not allowed.</p>
<p id="css_01_0033__p461114482049"><span class="parmname" id="css_01_0033__parmname1293745717712"><b>Rename Replacement</b></span>: Enter the index renaming rule. The default value <span class="parmvalue" id="css_01_0033__parmvalue563703423114216"><b>restored_index_$1</b></span> indicates that <span class="parmvalue" id="css_01_0033__parmvalue806962896114232"><b>restored_</b></span> is added in front of the names of all restored indices. The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\&lt;|&gt;/?,) are not allowed. You can set <span class="parmname" id="css_01_0033__parmname8406743125715"><b>Rename Replacement</b></span> only if you have specified <span class="parmname" id="css_01_0033__parmname12507141054718"><b>Rename Pattern</b></span>.</p>
<p id="css_01_0033__p114165551149"><span class="parmname" id="css_01_0033__parmname0874120486"><b>Cluster</b></span>: Select the cluster that you want to restore. You can select the current cluster or others. However, you can only restore the snapshot to clusters whose status is <span class="parmname" id="css_01_0033__parmname18702145212217"><b>Available</b></span>. If the status of the current cluster is <span class="parmname" id="css_01_0033__parmname232675192211"><b>Unavailable</b></span>, you cannot restore the snapshot to the current cluster. If you select another cluster and two or more indices in the cluster have the same name, data of all indices with the same name as the name you specify will be overwritten. Therefore, exercise caution when you set the parameters.</p>
<div class="fignone" id="css_01_0033__fig128071912118"><span class="figcap"><b>Figure 5 </b>Restoring a snapshot</span><br><span><img id="css_01_0033__image1343149208" src="en-us_image_0000001338955933.png" width="469.49" height="239.207815" title="Click to enlarge" class="imgResize"></span></div>
<div class="fignone" id="css_01_0033__fig128071912118"><span class="figcap"><b>Figure 4 </b>Restoring a snapshot</span><br><span><img id="css_01_0033__image1343149208" src="en-us_image_0000001525365813.png"></span></div>
<p id="css_01_0033__p1275412448014"></p>
</li><li id="css_01_0033__li14267162211412">Click <span class="uicontrol" id="css_01_0033__uicontrol1346108317431"><b>OK</b></span>. If restoration succeeds, <span class="parmname" id="css_01_0033__parmname316941968135515"><b>Task Status</b></span> of the snapshot in the snapshot list will change to <span class="parmvalue" id="css_01_0033__parmvalue1569249825135521"><b>Restoration succeeded</b></span>, and the index data is generated again according to the snapshot information.<div class="fignone" id="css_01_0033__fig25181595119"><span class="figcap"><b>Figure 6 </b>Successful restoration</span><br><span><img id="css_01_0033__image168371133144215" src="en-us_image_0000001286276646.png" width="469.49" height="44.171162" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="css_01_0033__li14267162211412">Click <span class="uicontrol" id="css_01_0033__uicontrol1346108317431"><b>OK</b></span>. If restoration succeeds, <span class="parmname" id="css_01_0033__parmname316941968135515"><b>Task Status</b></span> of the snapshot in the snapshot list will change to <span class="parmvalue" id="css_01_0033__parmvalue1569249825135521"><b>Restoration succeeded</b></span>, and the index data is generated again according to the snapshot information.<div class="fignone" id="css_01_0033__fig25181595119"><span class="figcap"><b>Figure 5 </b>Successful restoration</span><br><span><img id="css_01_0033__image168371133144215" src="en-us_image_0000001474566000.png"></span></div>
</li></ol>
</div>
<div class="section" id="css_01_0033__section3105193716428"><a name="css_01_0033__section3105193716428"></a><a name="section3105193716428"></a><h4 class="sectiontitle">Deleting a Snapshot</h4><p id="css_01_0033__p17436039154214">If you no longer need a snapshot, delete it to release storage resources. If the automatic snapshot creation function is enabled, snapshots that are automatically created cannot be deleted manually, and the system automatically deletes these snapshots on the half hour after the time specified by <span class="parmname" id="css_01_0033__parmname1728812311264"><b>Retention Period (days)</b></span>. If you disable the automatic snapshot creation function while retaining the automated snapshots, then you can manually delete them later. If you do not manually delete the automatically created snapshots and enable the automatic snapshot creation function again, then all snapshots with <span class="parmname" id="css_01_0033__parmname23829423573"><b>Snapshot Type</b></span> set to <strong id="css_01_0033__b17638024456">Automated</strong> in the snapshot list of the cluster can only be automatically deleted by the system.</p>
@ -99,10 +93,3 @@
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

9
docs/css/umn/css_01_0040.html
View File

@ -8,10 +8,8 @@
</div>
<p id="css_01_0040__p55571487450">In this section, assume that data of cluster <span class="parmname" id="css_01_0040__parmname387402189135847"><b>Es-1</b></span> is migrated to cluster <span class="parmname" id="css_01_0040__parmname1357640787135851"><b>Es-2</b></span>. Cluster <span class="parmname" id="css_01_0040__parmname102297251973"><b>Es-2</b></span> runs a version later than that of cluster <span class="parmname" id="css_01_0040__parmname112294253712"><b>Es-1</b></span> and the number of nodes in cluster <span class="parmname" id="css_01_0040__parmname451451525311"><b>Es-2</b></span> is greater than half of that in cluster <span class="parmname" id="css_01_0040__parmname42295256716"><b>Es-1</b></span>.</p>
<div class="section" id="css_01_0040__section339824743111"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0040__ol119181710193211"><li id="css_01_0040__li1691871014323">On the <strong id="css_01_0040__b842352706135948">Clusters</strong> page, click <span class="parmvalue" id="css_01_0040__parmvalue334615753114655"><b>Es-1</b></span>. On the displayed page, click <span class="parmname" id="css_01_0040__parmname61088115336"><b>Cluster Snapshots</b></span>.</li><li id="css_01_0040__li357514343420">Click <span class="uicontrol" id="css_01_0040__uicontrol2057633173418"><b>Create Snapshot</b></span> to manually create a snapshot. In the displayed dialog box, enter the snapshot name and click <span class="uicontrol" id="css_01_0040__uicontrol15138165414344"><b>OK</b></span>.<p id="css_01_0040__p15741433418">If you use the index backup and restoration function for the first time, you need to perform basic configurations first. For more details, see <a href="css_01_0033.html#css_01_0033__section43906502025">Manually Creating a Snapshot</a>.</p>
<div class="fignone" id="css_01_0040__fig78421105010"><span class="figcap"><b>Figure 1 </b>Creating a snapshot</span><br><span><img id="css_01_0040__image9861681773" src="en-us_image_0000001286596238.png" width="NaN" height="NaN"></span></div>
</li><li id="css_01_0040__li1470891763718">In the snapshot list, locate the row that contains the target snapshot and click <span class="uicontrol" id="css_01_0040__uicontrol12708717113716"><b>Restore</b></span> in the <strong id="css_01_0040__b84235270614229">Operation</strong> column to restore data to cluster <strong id="css_01_0040__b84235270614233">Es-2</strong>.<ul id="css_01_0040__ul165644811396"><li id="css_01_0040__li556416810396">Leave the <span class="parmname" id="css_01_0040__parmname19061915331"><b>Index</b></span> option blank (default setting), indicating that you want to restore data of all indices in cluster <span class="parmname" id="css_01_0040__parmname1290817143310"><b>Es-1</b></span>.</li><li id="css_01_0040__li1156410873915">From the <span class="parmname" id="css_01_0040__parmname148094791814318"><b>Cluster</b></span> drop-down list, select <span class="parmvalue" id="css_01_0040__parmvalue172345045214323"><b>Es-2</b></span>.</li></ul>
<p id="css_01_0040__p777024033818">Click <span class="uicontrol" id="css_01_0040__uicontrol127843639314335"><b>OK</b></span>. You can also rename the restored index.</p>
<div class="fignone" id="css_01_0040__fig128071912118"><span class="figcap"><b>Figure 2 </b>Restoring a snapshot</span><br><span><img id="css_01_0040__image1281217511349" src="en-us_image_0000001286436626.png" width="469.49" height="251.100143" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="css_01_0040__li6183045404">After restoration is complete, data in cluster <span class="parmname" id="css_01_0040__parmname16723637381449"><b>Es-1</b></span> will be migrated to cluster <span class="parmname" id="css_01_0040__parmname165705345314413"><b>Es-2</b></span>.</li></ol>
</div>
</div>
@ -21,10 +19,3 @@
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

4
docs/css/umn/css_01_0041.html
View File

@ -6,9 +6,7 @@
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_01_0042.html">Supported Metrics</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0043.html">Creating Alarm Rules</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0044.html">Viewing Metrics</a></strong><br>
<li class="ulchildlink"><strong><a href="css_01_0155.html">Configuring Cluster Monitoring</a></strong><br>
</li>
</ul>
</div>

19
docs/css/umn/css_01_0048.html
View File

@ -10,7 +10,7 @@
</li><li id="css_01_0048__li16377162604714">After installing Logstash, perform the following steps to import data. For details about how to install Logstash, visit the following website: <a href="https://www.elastic.co/guide/en/logstash/current/installing-logstash.html" target="_blank" rel="noopener noreferrer">https://www.elastic.co/guide/en/logstash/current/installing-logstash.html</a></li><li id="css_01_0048__li9641131917016">The JDK must be installed before Logstash is installed. In Linux OS, you can run the <strong id="css_01_0048__b20393185013114">yum -y install java-1.8.0</strong> command to install JDK 1.8.0. In Windows OS, you can download the required JDK version from the <a href="https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html" target="_blank" rel="noopener noreferrer">official website of JDK</a>, and install it by following the installation guide.</li><li id="css_01_0048__li1995041711115">In the <a href="#css_01_0048__section1098217174335">Importing Data When Logstash Is Deployed on an ECS</a> scenario, ensure that the ECS and the Elasticsearch cluster to which data is imported reside in the same VPC.</li></ul>
</div>
<div class="section" id="css_01_0048__section072813417814"><a name="css_01_0048__section072813417814"></a><a name="section072813417814"></a><h4 class="sectiontitle">Importing Data When Logstash Is Deployed on the External Network</h4><p id="css_01_0048__p4281513171111"><a href="#css_01_0048__fig471717481106">Figure 1</a> illustrates how data is imported when Logstash is deployed on an external network.</p>
<div class="fignone" id="css_01_0048__fig471717481106"><a name="css_01_0048__fig471717481106"></a><a name="fig471717481106"></a><span class="figcap"><b>Figure 1 </b>Importing data when Logstash is deployed on an external network</span><br><span><img class="imgResize" id="css_01_0048__image11185034163311" src="en-us_image_0000001338716669.png" width="522.69" height="192.44847300000004" title="Click to enlarge"></span></div>
<div class="fignone" id="css_01_0048__fig471717481106"><a name="css_01_0048__fig471717481106"></a><a name="fig471717481106"></a><span class="figcap"><b>Figure 1 </b>Importing data when Logstash is deployed on an external network</span><br><span><img class="vsd" id="css_01_0048__image11185034163311" src="en-us_image_0000001524925945.png"></span></div>
<p id="css_01_0048__p12185123416332"></p>
<ol id="css_01_0048__ol20180835132314"><li id="css_01_0048__li1648853125014"><a name="css_01_0048__li1648853125014"></a><a name="li1648853125014"></a>Create a jump host and configure it as follows:<ul id="css_01_0048__ul2807152315574"><li id="css_01_0048__li18807132310572">The jump host is an ECS running the Linux OS and has been bound with an EIP.</li><li id="css_01_0048__li1692633435810">The jump host resides in the same VPC as the CSS cluster.</li><li id="css_01_0048__li129110535017">SSH local port forwarding is configured for the jump host to forward requests from a chosen local port to port <strong id="css_01_0048__b181343814612">9200</strong> on one node of the CSS cluster.</li><li id="css_01_0048__li1277830155915">Refer to <a href="https://man.openbsd.org/ssh.1#L" target="_blank" rel="noopener noreferrer">SSH documentation</a> for the local port forwarding configuration.</li></ul>
</li><li id="css_01_0048__li19164183513237">Use PuTTY to log in to the created jump host with the EIP.</li><li id="css_01_0048__li1316473511236">Run the following command to perform port mapping and transfer the request sent to the port on the jump host to the target cluster:<pre class="screen" id="css_01_0048__screen716453518231">ssh -g -L <em id="css_01_0048__i31643353232">&lt;Local port of the jump host</em>:<em id="css_01_0048__i716443572314">Private network address and port number of a node&gt;</em> -N -f root@<em id="css_01_0048__i216416353238">&lt;Private IP address of the jump host</em>&gt;</pre>
@ -69,7 +69,7 @@ output {
<div class="note" id="css_01_0048__note29452405213"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0048__p12945184092114">If a license error is reported, set <strong id="css_01_0048__b199511958194712">ilm_enabled</strong> to <strong id="css_01_0048__b17967105964711">false</strong>.</p>
</div></div>
<p id="css_01_0048__p154751181388">If the cluster has the security mode enabled, you need to download a certificate first.</p>
<ol type="a" id="css_01_0048__ol45911713483"><li id="css_01_0048__li45915135814">Download a certificate on the <strong id="css_01_0048__b116761120201015">Basic Information</strong> page of the cluster.<div class="fignone" id="css_01_0048__fig11031228135019"><span class="figcap"><b>Figure 2 </b>Downloading a certificate</span><br><span><img id="css_01_0048__image1045615019490" src="en-us_image_0000001286276694.png" width="438.90000000000003" height="227.91385400000001" title="Click to enlarge" class="imgResize"></span></div>
<ol type="a" id="css_01_0048__ol45911713483"><li id="css_01_0048__li45915135814">Download a certificate on the <strong id="css_01_0048__b116761120201015">Basic Information</strong> page of the cluster.<div class="fignone" id="css_01_0048__fig11031228135019"><span class="figcap"><b>Figure 2 </b>Downloading a certificate</span><br><span><img id="css_01_0048__image1045615019490" src="en-us_image_0000001525365801.png"></span></div>
</li><li id="css_01_0048__li107224618910">Store the certificate to the server where Logstash is deployed.</li><li id="css_01_0048__li84281357121313">Modify the <strong id="css_01_0048__b3469133941110">logstash-simple.conf</strong> configuration file.<div class="p" id="css_01_0048__p14897136193">Consider the data files in the <span class="filepath" id="css_01_0048__filepath376984121915"><b>/tmp/access_log/</b></span> path mentioned in <a href="#css_01_0048__li5164153542312">4</a> as an example. Assume that data import starts from data in the first row of the data file, the filtering condition is left unspecified (indicating no data processing operations are performed), and the public IP address and port number of the jump host are <span class="parmvalue" id="css_01_0048__parmvalue1774888517"><b>192.168.0.227</b></span> and <span class="parmvalue" id="css_01_0048__parmvalue1925348551"><b>9200</b></span>, respectively. The name of the index for importing data is <strong id="css_01_0048__b104220143134">myindex</strong>, and the certificate is stored in <strong id="css_01_0048__b177982020111311">/logstash/logstash6.8/config/CloudSearchService.cer</strong>. Edit the configuration file as follows, and enter <span class="parmvalue" id="css_01_0048__parmvalue197616546346"><b>:wq</b></span> to save the configuration file and exit.<pre class="screen" id="css_01_0048__screen588712113193">input{
file {
path =&gt; "/tmp/access_log/*"
@ -94,13 +94,13 @@ output{
</li><li id="css_01_0048__li14164163582313">Run the following command to import the data collected by Logstash to the cluster:<pre class="screen" id="css_01_0048__screen121641135152312">./bin/logstash -f logstash-simple.conf</pre>
<div class="note" id="css_01_0048__note19357111419509"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0048__p3258910205713">This command must be executed in the directory where the <strong id="css_01_0048__b750418485328">logstash-simple.conf</strong> file is stored. For example, if the <strong id="css_01_0048__b733614818335">logstash-simple.conf</strong> file is stored in <strong id="css_01_0048__b15562151313313">/root/logstash-7.1.1/</strong>, go to the directory before running the command.</p>
</div></div>
</li><li id="css_01_0048__li11641535192318">Log in to the <span id="css_01_0048__text2182135054613">CSS</span> management console.</li><li id="css_01_0048__li1716433502318">In the left navigation pane, click <span class="uicontrol" id="css_01_0048__uicontrol393210564379"><b>Clusters</b></span> to switch to the <strong id="css_01_0048__b11932105673718">Clusters</strong> page.</li><li id="css_01_0048__li31807350237">From the cluster list, locate the row that contains the cluster to which you want to import data and click <span class="parmname" id="css_01_0048__parmname1569018551468"><b>Access Kibana</b></span> in the <span class="parmname" id="css_01_0048__parmname3690105511469"><b>Operation</b></span> column.</li><li id="css_01_0048__li9180335132310">In the left navigation pane of the displayed Kibana window, click <span class="parmname" id="css_01_0048__parmname13948820476"><b>Dev Tools</b></span>.<div class="fignone" id="css_01_0048__fig164001949115016"><span class="figcap"><b>Figure 3 </b>Logging in to Dev Tools</span><br><span><img id="css_01_0048__image15885941135018" src="en-us_image_0000001286596270.png" width="202.4925" height="381.20061000000004" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="css_01_0048__li11641535192318">Log in to the <span id="css_01_0048__text2182135054613">CSS</span> management console.</li><li id="css_01_0048__li1716433502318">In the left navigation pane, click <span class="uicontrol" id="css_01_0048__uicontrol393210564379"><b>Clusters</b></span> to switch to the <strong id="css_01_0048__b11932105673718">Clusters</strong> page.</li><li id="css_01_0048__li31807350237">From the cluster list, locate the row that contains the cluster to which you want to import data and click <span class="parmname" id="css_01_0048__parmname1569018551468"><b>Access Kibana</b></span> in the <span class="parmname" id="css_01_0048__parmname3690105511469"><b>Operation</b></span> column.</li><li id="css_01_0048__li9180335132310">In the left navigation pane of the displayed Kibana window, click <span class="parmname" id="css_01_0048__parmname13948820476"><b>Dev Tools</b></span>.<div class="fignone" id="css_01_0048__fig164001949115016"><span class="figcap"><b>Figure 3 </b>Logging in to Dev Tools</span><br><span><img id="css_01_0048__image15885941135018" src="en-us_image_0000001474725816.png"></span></div>
</li><li id="css_01_0048__li418033592313">On the <strong id="css_01_0048__b119311594497">Console</strong> page of Kibana, search for the imported data.<p id="css_01_0048__p118053518234">On the <strong id="css_01_0048__b1685619109106">Console</strong> page of Kibana, enter the following command to search for data. View the search results. If the searched data is consistent with the imported data, the data has been imported successfully.</p>
<pre class="screen" id="css_01_0048__screen1718063513237">GET myindex/_search</pre>
</li></ol>
</div>
<div class="section" id="css_01_0048__section1098217174335"><a name="css_01_0048__section1098217174335"></a><a name="section1098217174335"></a><h4 class="sectiontitle">Importing Data When Logstash Is Deployed on an ECS</h4><p id="css_01_0048__p110725613115"><a href="#css_01_0048__fig124034434127">Figure 4</a> illustrates how data is imported when Logstash is deployed on an ECS that resides in the same VPC as the cluster to which data is to be imported.</p>
<div class="fignone" id="css_01_0048__fig124034434127"><a name="css_01_0048__fig124034434127"></a><a name="fig124034434127"></a><span class="figcap"><b>Figure 4 </b>Importing data when Logstash is deployed on an ECS</span><br><span><img class="vsd" id="css_01_0048__image3127102312364" src="en-us_image_0000001338716673.png"></span></div>
<div class="fignone" id="css_01_0048__fig124034434127"><a name="css_01_0048__fig124034434127"></a><a name="fig124034434127"></a><span class="figcap"><b>Figure 4 </b>Importing data when Logstash is deployed on an ECS</span><br><span><img class="vsd" id="css_01_0048__image3127102312364" src="en-us_image_0000001524925937.png"></span></div>
<ol id="css_01_0048__ol3524114322310"><li id="css_01_0048__li1852474313235">Ensure that the ECS where Logstash is deployed and the cluster to which data is to be imported reside in the same VPC, port <strong id="css_01_0048__b694015623710">9200</strong> of the ECS security group has been assigned external network access permissions, and an EIP has been bound to the ECS.<div class="note" id="css_01_0048__note866415302112"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="css_01_0048__ul112263151393"><li id="css_01_0048__li1722615151999">If there are multiple servers in a VPC, you do not need to associate EIPs to other servers as long as one server is associated with an EIP. Switch to the node where Logstash is deployed from the node with which the EIP is associated.</li><li id="css_01_0048__li1363015162912">If a private line or VPN is available, you do not need to associate an EIP.</li></ul>
</div></div>
</li><li id="css_01_0048__li1652411439236"><a name="css_01_0048__li1652411439236"></a><a name="li1652411439236"></a>Use PuTTY to log in to the ECS.<div class="p" id="css_01_0048__p12524643162314"><a name="css_01_0048__li1652411439236"></a><a name="li1652411439236"></a>For example, data file <span class="filepath" id="css_01_0048__filepath1388819169466"><b>access_20181029_log</b></span> is stored in the <span class="filepath" id="css_01_0048__filepath138891516164613"><b>/tmp/access_log/</b></span> path of the ECS, and the data file includes the following data:<pre class="screen" id="css_01_0048__screen19524243192319">| All | Heap used for segments | | 18.6403 | MB |
@ -153,7 +153,7 @@ output {
}
}</pre>
<p id="css_01_0048__p0370830125513">If the cluster has the security mode enabled, you need to download a certificate first.</p>
<div class="p" id="css_01_0048__p63682983810"><ol type="a" id="css_01_0048__ol1817087143812"><li id="css_01_0048__en-us_topic_0111222977_li45915135814">Download a certificate on the <strong id="css_01_0048__b172536140">Basic Information</strong> page of the cluster.<div class="fignone" id="css_01_0048__fig1877019549519"><span class="figcap"><b>Figure 5 </b>Downloading a certificate</span><br><span><img id="css_01_0048__image2793173420519" src="en-us_image_0000001338955977.png" width="445.88250000000005" height="231.53571" title="Click to enlarge" class="imgResize"></span></div>
<div class="p" id="css_01_0048__p63682983810"><ol type="a" id="css_01_0048__ol1817087143812"><li id="css_01_0048__en-us_topic_0111222977_li45915135814">Download a certificate on the <strong id="css_01_0048__b172536140">Basic Information</strong> page of the cluster.<div class="fignone" id="css_01_0048__fig1877019549519"><span class="figcap"><b>Figure 5 </b>Downloading a certificate</span><br><span><img id="css_01_0048__image2793173420519" src="en-us_image_0000001525205841.png"></span></div>
</li><li id="css_01_0048__en-us_topic_0111222977_li107224618910">Store the certificate to the server where Logstash is deployed.</li><li id="css_01_0048__en-us_topic_0111222977_li84281357121313">Modify the <strong id="css_01_0048__b1330784117147">logstash-simple.conf</strong> configuration file.<div class="p" id="css_01_0048__en-us_topic_0111222977_p14897136193">Consider the data files in the <span class="filepath" id="css_01_0048__filepath16776174361415"><b>/tmp/access_log/</b></span> path mentioned in <a href="#css_01_0048__li1652411439236">2</a> as an example. Assume that data import starts from data in the first row of the data file, the filtering condition is left unspecified (indicating no data processing operations are performed), the public IP address and port number of the jump host are <span class="parmvalue" id="css_01_0048__parmvalue102421758201415"><b>192.168.0.227</b></span> and <span class="parmvalue" id="css_01_0048__parmvalue42431758131415"><b>9200</b></span>, respectively. The name of the index for importing data is <strong id="css_01_0048__b296498935">myindex</strong>, and the certificate is stored in <strong id="css_01_0048__b861142389">/logstash/logstash6.8/config/CloudSearchService.cer</strong>. Edit the configuration file as follows, and enter <span class="parmvalue" id="css_01_0048__parmvalue956834074"><b>:wq</b></span> to save the configuration file and exit.<pre class="screen" id="css_01_0048__en-us_topic_0111222977_screen588712113193">input{
file {
path =&gt; "/tmp/access_log/*"
@ -177,7 +177,7 @@ output{
</li></ol>
</div>
</li><li id="css_01_0048__li115241243142312">Run the following command to import the ECS data collected by Logstash to the cluster:<pre class="screen" id="css_01_0048__screen3524143132312">./bin/logstash -f logstash-simple.conf</pre>
</li><li id="css_01_0048__li75241643172310">Log in to the <span id="css_01_0048__text1041162757">CSS</span> management console.</li><li id="css_01_0048__li115241343152311">In the left navigation pane, click <span class="uicontrol" id="css_01_0048__uicontrol1253985733720"><b>Clusters</b></span> to switch to the <strong id="css_01_0048__b1553919572372">Clusters</strong> page.</li><li id="css_01_0048__li3524114302314">From the cluster list, locate the row that contains the cluster to which you want to import data and click <span class="parmname" id="css_01_0048__parmname1561592889"><b>Access Kibana</b></span> in the <span class="parmname" id="css_01_0048__parmname788721907"><b>Operation</b></span> column.</li><li id="css_01_0048__li18524164302316">In the left navigation pane of the displayed Kibana window, click <span class="parmname" id="css_01_0048__parmname264720407106"><b>Dev Tools</b></span>.<div class="fignone" id="css_01_0048__fig14934191615547"><span class="figcap"><b>Figure 6 </b>Choosing Dev Tools</span><br><span><img id="css_01_0048__en-us_topic_0000001268314481_image3902622164718" src="en-us_image_0000001338955981.png" width="236.4075" height="445.0465950000001" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="css_01_0048__li75241643172310">Log in to the <span id="css_01_0048__text1041162757">CSS</span> management console.</li><li id="css_01_0048__li115241343152311">In the left navigation pane, click <span class="uicontrol" id="css_01_0048__uicontrol1253985733720"><b>Clusters</b></span> to switch to the <strong id="css_01_0048__b1553919572372">Clusters</strong> page.</li><li id="css_01_0048__li3524114302314">From the cluster list, locate the row that contains the cluster to which you want to import data and click <span class="parmname" id="css_01_0048__parmname1561592889"><b>Access Kibana</b></span> in the <span class="parmname" id="css_01_0048__parmname788721907"><b>Operation</b></span> column.</li><li id="css_01_0048__li18524164302316">In the left navigation pane of the displayed Kibana window, click <span class="parmname" id="css_01_0048__parmname264720407106"><b>Dev Tools</b></span>.<div class="fignone" id="css_01_0048__fig14934191615547"><span class="figcap"><b>Figure 6 </b>Choosing Dev Tools</span><br><span><img id="css_01_0048__en-us_topic_0000001268314481_image3902622164718" src="en-us_image_0000001524766265.png"></span></div>
</li><li id="css_01_0048__li1252410433236">On the <strong id="css_01_0048__b519438726">Console</strong> page of Kibana, search for the imported data.<p id="css_01_0048__p115241343172312">On the <strong id="css_01_0048__b217115189110">Console</strong> page of Kibana, enter the following command to search for data. View the search results. If the searched data is consistent with the imported data, the data has been imported successfully.</p>
<pre class="screen" id="css_01_0048__screen75241543182320">GET myindex/_search</pre>
</li></ol>
@ -189,10 +189,3 @@ output{
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

4
docs/css/umn/css_01_0051.html
View File

@ -2,12 +2,12 @@
<h1 class="topictitle1">Viewing Audit Logs</h1>
<div id="body0000001282659030"><p id="css_01_0051__p20746153363">After you enable CTS, it starts recording operations related to <span id="css_01_0051__text474395010409">CSS</span>. The CTS management console stores the last seven days of operation records. This section describes how to query the last seven days of operation records on the CTS management console.</p>
<div class="section" id="css_01_0051__section1482553663115"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0051__ol83121137162615"><li id="css_01_0051__li4312937122611">Log in to the CTS management console.</li><li id="css_01_0051__li11312183732611">Click <span><img id="css_01_0051__image2418101875814" src="en-us_image_0000001286436610.png"></span> in the upper left corner and select a region.</li><li id="css_01_0051__li16312123713262">In the left navigation pane, click <span class="uicontrol" id="css_01_0051__uicontrol615166351144256"><b>Trace List</b></span>.</li><li id="css_01_0051__li15312837142614">You can use filters to query traces. The following four filter criteria are available:<ul id="css_01_0051__ul33127373267"><li id="css_01_0051__li163121737182612"><strong id="css_01_0051__b15899193113919">Trace Source</strong>, <strong id="css_01_0051__b1590110319397">Resource Type</strong>, and <strong id="css_01_0051__b109021313398">Search By</strong><p id="css_01_0051__p831263713262">Select a filter criterion from the drop-down list.</p>
<div class="section" id="css_01_0051__section1482553663115"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0051__ol83121137162615"><li id="css_01_0051__li4312937122611">Log in to the CTS management console.</li><li id="css_01_0051__li11312183732611">Click <span><img id="css_01_0051__image2418101875814" src="en-us_image_0000001524925949.png"></span> in the upper left corner and select a region.</li><li id="css_01_0051__li16312123713262">In the left navigation pane, click <span class="uicontrol" id="css_01_0051__uicontrol615166351144256"><b>Trace List</b></span>.</li><li id="css_01_0051__li15312837142614">You can use filters to query traces. The following four filter criteria are available:<ul id="css_01_0051__ul33127373267"><li id="css_01_0051__li163121737182612"><strong id="css_01_0051__b15899193113919">Trace Source</strong>, <strong id="css_01_0051__b1590110319397">Resource Type</strong>, and <strong id="css_01_0051__b109021313398">Search By</strong><p id="css_01_0051__p831263713262">Select a filter criterion from the drop-down list.</p>
<p id="css_01_0051__p1231217377266">When you select <strong id="css_01_0051__b584335163910">Trace name</strong> for <strong id="css_01_0051__b208553511397">Search By</strong>, select a specific trace name.</p>
<p id="css_01_0051__p20312637112616">When you select <strong id="css_01_0051__b13540436173918">Resource ID</strong> for <strong id="css_01_0051__b35411536203910">Search By</strong>, enter a specific resource ID.</p>
<p id="css_01_0051__p12312183720261">When you select <strong id="css_01_0051__b1281012362411">Resource name</strong> for <strong id="css_01_0051__b48101036174112">Search By</strong>, select or enter a specific resource name.</p>
</li><li id="css_01_0051__li11312183716264"><strong id="css_01_0051__b52131130161011">Operator</strong>: Select a specific operator (at user level rather than tenant level).</li><li id="css_01_0051__li1331233713267"><strong id="css_01_0051__b481214363413">Trace Status</strong>: Available options include <span class="parmvalue" id="css_01_0051__parmvalue1588298194144416"><b>All trace statuses</b></span>, <span class="parmvalue" id="css_01_0051__parmvalue1235033399144416"><b>normal</b></span>, <span class="parmvalue" id="css_01_0051__parmvalue1279281076144416"><b>warning</b></span>, and <span class="parmvalue" id="css_01_0051__parmvalue850432214144416"><b>incident</b></span>. You can only select one of them.</li><li id="css_01_0051__li8312337152615"><strong id="css_01_0051__b5982164017102">Time Range</strong>: You can query traces generated during any time range of the last seven days.</li></ul>
</li><li id="css_01_0051__li18312137182611">Click <span><img id="css_01_0051__image7310334701" src="en-us_image_0000001286276642.png"></span> on the left of a trace to expand its details.</li><li id="css_01_0051__li19312637142615">Click <span class="uicontrol" id="css_01_0051__uicontrol1638706428144446"><b>View Trace</b></span> in the <span class="parmname" id="css_01_0051__parmname1195542321144457"><b>Operation</b></span> column. In the displayed <strong id="css_01_0051__b13818236104119">View Trace</strong> dialog box, the trace structure details are displayed.<p id="css_01_0051__p19312183719261">For details about the key fields in the CTS trace structure, see the <a href="https://docs.otc.t-systems.com/en-us/usermanual/cts/en-us_topic_0030579718.html" target="_blank" rel="noopener noreferrer">Cloud Trace Service User Guide</a>.</p>
</li><li id="css_01_0051__li18312137182611">Click <span><img id="css_01_0051__image7310334701" src="en-us_image_0000001525205849.png"></span> on the left of a trace to expand its details.</li><li id="css_01_0051__li19312637142615">Click <span class="uicontrol" id="css_01_0051__uicontrol1638706428144446"><b>View Trace</b></span> in the <span class="parmname" id="css_01_0051__parmname1195542321144457"><b>Operation</b></span> column. In the displayed <strong id="css_01_0051__b13818236104119">View Trace</strong> dialog box, the trace structure details are displayed.<p id="css_01_0051__p19312183719261">For details about the key fields in the CTS trace structure, see the <a href="https://docs.otc.t-systems.com/en-us/usermanual/cts/en-us_topic_0030579718.html" target="_blank" rel="noopener noreferrer">Cloud Trace Service User Guide</a>.</p>
</li></ol>
</div>
</div>

4
docs/css/umn/css_01_0056.html
View File

@ -2,8 +2,8 @@
<h1 class="topictitle1">Introduction to the Cluster List</h1>
<div id="body0000001334459441"><p id="css_01_0056__p13682314536">The cluster list displays all <span id="css_01_0056__text1735672613716">CSS</span> clusters. If there are a large number of clusters, these clusters will be displayed on multiple pages. You can view clusters of all statuses from the cluster list.</p>
<p id="css_01_0056__p19515494">Clusters are listed in chronological order by default in the cluster list, with the most recent cluster displayed at the top. You can click <span><img id="css_01_0056__image4198154112417" src="en-us_image_0000001338716693.png"></span> next to the related parameter in the table heading to modify cluster sorting. <a href="#css_01_0056__table163431019544">Table 1</a> describes the parameters involved in the cluster list.</p>
<p id="css_01_0056__p11177205951113">In the upper right corner of the cluster list, you can enter the name or ID of a cluster and click <span><img id="css_01_0056__image1933221354210" src="en-us_image_0000001286276722.png"></span> to search for a cluster. You can also click <span><img id="css_01_0056__image1871215426420" src="en-us_image_0000001286116794.png"></span> in the upper right corner to refresh the cluster list.</p>
<p id="css_01_0056__p19515494">Clusters are listed in chronological order by default in the cluster list, with the most recent cluster displayed at the top. You can click <span><img id="css_01_0056__image4198154112417" src="en-us_image_0000001524925973.png"></span> next to the related parameter in the table heading to modify cluster sorting. <a href="#css_01_0056__table163431019544">Table 1</a> describes the parameters involved in the cluster list.</p>
<p id="css_01_0056__p11177205951113">In the upper right corner of the cluster list, you can enter the name or ID of a cluster and click <span><img id="css_01_0056__image1933221354210" src="en-us_image_0000001525365833.png"></span> to search for a cluster. You can also click <span><img id="css_01_0056__image1871215426420" src="en-us_image_0000001474566012.png"></span> in the upper right corner to refresh the cluster list.</p>
<div class="tablenoborder"><a name="css_01_0056__table163431019544"></a><a name="table163431019544"></a><table cellpadding="4" cellspacing="0" summary="" id="css_01_0056__table163431019544" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Cluster list parameter description</caption><thead align="left"><tr id="css_01_0056__row5343319241"><th align="left" class="cellrowborder" valign="top" width="28.060000000000002%" id="mcps1.3.4.2.3.1.1"><p id="css_01_0056__p9343151913413">Parameter</p>
</th>

17
docs/css/umn/css_01_0058.html Normal file
View File

@ -0,0 +1,17 @@
<a name="css_01_0058"></a><a name="css_01_0058"></a>
<h1 class="topictitle1">Binding an Enterprise Project</h1>
<div id="body0000001334778797"><p id="css_01_0058__p8060118">You must configure an enterprise project for each cluster. If you do not need to distinguish enterprise projects for clusters, you can bind clusters to the <span class="parmname" id="css_01_0058__parmname42261657916"><b>default</b></span> project. For clusters created before the binding an enterprise project feature was released, their enterprise projects were bound to the <span class="parmname" id="css_01_0058__parmname1446711441992"><b>default</b></span> project. You can modify the enterprise project based on the site requirements.</p>
<div class="section" id="css_01_0058__section57873201918"><h4 class="sectiontitle">Binding an Enterprise Project</h4><p id="css_01_0058__p2210251391">When creating a cluster, you can bind it to an enterprise project by specifying the <strong id="css_01_0058__b752050115510">Enterprise Project</strong> parameter. For details, see .</p>
</div>
<div class="section" id="css_01_0058__section2120201511011"><h4 class="sectiontitle">Modifying an Enterprise Project</h4><p id="css_01_0058__p7438234131011">For a cluster that has been created, you can modify its enterprise project based on the site requirements.</p>
<ol id="css_01_0058__ol1947141411194"><li id="css_01_0058__li6302956053">On the CSS management console, click <span class="parmname" id="css_01_0058__parmname936245316361"><b>Clusters</b></span>.</li><li id="css_01_0058__li8302155619516">In the cluster list on the displayed page, click the target cluster name to switch to the <strong id="css_01_0058__b655595516369">Basic Information</strong> page.</li><li id="css_01_0058__li4230112181920">On the displayed page, click the parameter value on the right of <span class="parmname" id="css_01_0058__parmname134661313141218"><b>Enterprise Project</b></span>. The <span class="parmname" id="css_01_0058__parmname2060416474121"><b>Project Management</b></span> page of the <span class="parmname" id="css_01_0058__parmname976302910137"><b>Resource Management</b></span> is displayed.</li><li id="css_01_0058__li1669213196206">On the <strong id="css_01_0058__b5846204814424">Resources</strong> tab page, select the corresponding <span class="parmname" id="css_01_0058__parmname8854134814427"><b>Region</b></span> and select<span class="uicontrol" id="css_01_0058__uicontrol158862591569"><b> Cloud Search Service</b></span> from <span class="parmname" id="css_01_0058__parmname128551348144211"><b>Service</b></span>. In this case, the corresponding CSS cluster is displayed in the resource list.</li><li id="css_01_0058__li78671469217">Select the cluster whose enterprise project you want to modify and click <span class="uicontrol" id="css_01_0058__uicontrol5366101511813"><b>Remove</b></span>.</li><li id="css_01_0058__li19166117162317">On the <span class="wintitle" id="css_01_0058__wintitle1516933271819"><b>Remove Resource</b></span> page, specify <span class="parmname" id="css_01_0058__parmname1674851311229"><b>Mode</b></span> and select <span class="parmname" id="css_01_0058__parmname1365814264018"><b>Destination Enterprise Project</b></span>, and click <span class="uicontrol" id="css_01_0058__uicontrol199034303020"><b>OK</b></span>.</li><li id="css_01_0058__li13873203814243">After you complete the preceding steps, you can view the enterprise project bound to the cluster in either of the following ways:<ul id="css_01_0058__ul8138036202718"><li id="css_01_0058__li1013819363273">Switch to the CSS cluster list, where the value of <strong id="css_01_0058__b776025217558">Enterprise Project</strong> for the cluster is changed to the new enterprise project.</li><li id="css_01_0058__li142531336284">On the <strong id="css_01_0058__b1569165910223">Resource Management</strong> page, click <strong id="css_01_0058__b612004014105">Project Management</strong> in the navigation pane on the left. On the displayed page, click <strong id="css_01_0058__b92663492111">View Migration Event</strong> to obtain the cluster information.</li></ul>
</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0009.html">Managing Elasticsearch Clusters</a></div>
</div>
</div>

13
docs/css/umn/css_01_0060.html
View File

@ -2,13 +2,11 @@
<h1 class="topictitle1">Managing Failed Tasks</h1>
<div id="body0000001282658982"><p id="css_01_0060__p8060118">In the <strong id="css_01_0060__b17876132011117">Failed Tasks</strong> dialog box, you can view the failed tasks related to a cluster, such as failing to create, restart, scale out, back up, or restore a cluster. In addition, you can view the failure cause of each task and choose to delete one or all failed tasks.</p>
<div class="section" id="css_01_0060__section1393913131117"><h4 class="sectiontitle">Viewing Failed Tasks</h4><ol id="css_01_0060__ol47861611101112"><li id="css_01_0060__li11622242616">Log in to the <span id="css_01_0060__text208055615149">CSS</span> management console.</li><li id="css_01_0060__li9160224260">Click <span class="uicontrol" id="css_01_0060__uicontrol181612228265"><b>Clusters</b></span> to switch to the <strong id="css_01_0060__b1867018334565">Clusters</strong> page. Click the digit next to <strong id="css_01_0060__b3305185125714">Failed Tasks</strong> to switch to the <strong id="css_01_0060__b143225195814">Failed Tasks</strong> dialog box.<div class="fignone" id="css_01_0060__fig9871436121212"><span class="figcap"><b>Figure 1 </b>Clicking the digit next to Failed Tasks</span><br><span><img id="css_01_0060__image273203201211" src="en-us_image_0000001286116770.png" width="492.1" height="71.665055" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="css_01_0060__li20774101315127">The <span class="wintitle" id="css_01_0060__wintitle1966611331973"><b>Failed Tasks</b></span> dialog box presents all failed tasks of the current account. The following information about the failed tasks is displayed: <span class="parmname" id="css_01_0060__parmname731134883416"><b>Name/ID</b></span>, <span class="parmname" id="css_01_0060__parmname186392053143412"><b>Task Status</b></span>, and <span class="parmname" id="css_01_0060__parmname9729165663420"><b>Failure Time</b></span>.</li><li id="css_01_0060__li1372895910228">Click the question mark in the <strong id="css_01_0060__b09881747205910">Task Status</strong> column to view the failure cause of a task. You are advised to troubleshoot faults based on failure causes. For details about failure causes, see <a href="#css_01_0060__section155001521193312">Error Code</a>.<div class="fignone" id="css_01_0060__fig85418382253"><span class="figcap"><b>Figure 2 </b>Viewing the failure cause of a task</span><br><span><img id="css_01_0060__image1590019713599" src="en-us_image_0000001339036413.png" width="492.1" height="290.46761100000003" title="Click to enlarge" class="imgResize"></span></div>
</li></ol>
<div class="section" id="css_01_0060__section1393913131117"><h4 class="sectiontitle">Viewing Failed Tasks</h4><ol id="css_01_0060__ol47861611101112"><li id="css_01_0060__li11622242616">Log in to the <span id="css_01_0060__text208055615149">CSS</span> management console.</li><li id="css_01_0060__li9160224260">Click <span class="uicontrol" id="css_01_0060__uicontrol181612228265"><b>Clusters</b></span> to switch to the <strong id="css_01_0060__b1867018334565">Clusters</strong> page. Click the digit next to <strong id="css_01_0060__b3305185125714">Failed Tasks</strong> to switch to the <strong id="css_01_0060__b143225195814">Failed Tasks</strong> dialog box.</li><li id="css_01_0060__li20774101315127">The <span class="wintitle" id="css_01_0060__wintitle1966611331973"><b>Failed Tasks</b></span> dialog box presents all failed tasks of the current account. The following information about the failed tasks is displayed: <span class="parmname" id="css_01_0060__parmname731134883416"><b>Name/ID</b></span>, <span class="parmname" id="css_01_0060__parmname186392053143412"><b>Task Status</b></span>, and <span class="parmname" id="css_01_0060__parmname9729165663420"><b>Failure Time</b></span>.</li><li id="css_01_0060__li1372895910228">Click the question mark in the <strong id="css_01_0060__b09881747205910">Task Status</strong> column to view the failure cause of a task. You are advised to troubleshoot faults based on failure causes. For details about failure causes, see <a href="#css_01_0060__section155001521193312">Error Code</a>.</li></ol>
</div>
<div class="section" id="css_01_0060__section82881811133120"><h4 class="sectiontitle">Deleting a Failed Task</h4><p id="css_01_0060__p28053248314">You can delete one or all failed tasks at a time.</p>
<ul id="css_01_0060__ul432662312313"><li id="css_01_0060__li15326723173111">To delete a failed task, perform the following operations: Locate the row that contains the target task and click <span class="uicontrol" id="css_01_0060__uicontrol148121620193317"><b>Delete</b></span> in the <strong id="css_01_0060__b191281311428">Operation</strong> column. In the displayed dialog box, confirm the task you want to delete and click <span class="uicontrol" id="css_01_0060__uicontrol1933113257334"><b>Yes</b></span>.</li><li id="css_01_0060__li33151127173319">To delete all failed tasks, perform the following operations: In the <span class="wintitle" id="css_01_0060__wintitle4538332105018"><b>Failed Tasks</b></span> dialog box, click <span class="uicontrol" id="css_01_0060__uicontrol323703312351"><b>Delete All</b></span>. In the displayed dialog box, confirm the information about all failed tasks and click <span class="uicontrol" id="css_01_0060__uicontrol18326203013516"><b>Yes</b></span>.</li></ul>
<div class="fignone" id="css_01_0060__fig1419120710386"><span class="figcap"><b>Figure 3 </b>Deleting a failed task</span><br><span><img id="css_01_0060__image549413524592" src="en-us_image_0000001338836521.png" width="492.1" height="291.159211" title="Click to enlarge" class="imgResize"></span></div>
<div class="fignone" id="css_01_0060__fig1419120710386"><span class="figcap"><b>Figure 1 </b>Deleting a failed task</span><br><span><img id="css_01_0060__image549413524592" src="en-us_image_0000001524925993.png"></span></div>
</div>
<div class="section" id="css_01_0060__section155001521193312"><a name="css_01_0060__section155001521193312"></a><a name="section155001521193312"></a><h4 class="sectiontitle">Error Code</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0060__table16751996354" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Failure causes</caption><thead align="left"><tr id="css_01_0060__row376129113519"><th align="left" class="cellrowborder" valign="top" width="21.512151215121513%" id="mcps1.3.4.2.2.4.1.1"><p id="css_01_0060__p19760913357">Error Code</p>
@ -86,10 +84,3 @@
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

22
docs/css/umn/css_01_0061.html
View File

@ -3,20 +3,20 @@
<h1 class="topictitle1">Elasticsearch SQL</h1>
<div id="body0000001334778845"><p id="css_01_0061__p412122212308">For Elasticsearch 6.5.4 and later versions, Open Distro for Elasticsearch SQL lets you write queries in SQL rather than in the Elasticsearch query domain-specific language (DSL).</p>
<p id="css_01_0061__p14906121217302">If you are already familiar with SQL and do not want to learn query DSL, this feature is a great option.</p>
<div class="section" id="css_01_0061__section59231342303"><h4 class="sectiontitle">Basic Operations</h4><p id="css_01_0061__p169071501307">To use this function, send requests to the <strong id="css_01_0061__b41848422118">_opendistro/_sql</strong> URI. You can use a request parameter or the request body (recommended).</p>
<pre class="screen" id="css_01_0061__screen17665419123718">GET https://&lt;host&gt;:&lt;port&gt;/_opendistro/_sql?sql=select * from my-index limit 50</pre>
<pre class="screen" id="css_01_0061__screen961982613711">POST https://&lt;host&gt;:&lt;port&gt;/_opendistro/_sql
<div class="section" id="css_01_0061__section12911051103415"><h4 class="sectiontitle">Basic Operations</h4><ul id="css_01_0061__ul165831326120"><li id="css_01_0061__li05831021116">Kibana (recommended)<ul id="css_01_0061__ul67081305120"><li id="css_01_0061__li14709103011119">Log in to Kibana and send requests using request parameters or request body to <strong id="css_01_0061__b13214411195512">_opendistro/_sqlURI</strong> in the <strong id="css_01_0061__b17268815105516">Dev Tools</strong> page.<pre class="screen" id="css_01_0061__screen887920471045">GET _opendistro/_sql?sql=select * from my-index limit 50</pre>
<pre class="screen" id="css_01_0061__screen158809477411">POST _opendistro/_sql
{
"query": "SELECT * FROM my-index LIMIT 50"
}</pre>
<p id="css_01_0061__p15508452193715">You can run the cURL command:</p>
<pre class="screen" id="css_01_0061__screen16326715173820">curl -XPOST https://localhost:9200/_opendistro/_sql -u username:password -k -d '{"query": "SELECT * FROM kibana_sample_data_flights LIMIT 10"}' -H 'Content-Type: application/json'</pre>
<p id="css_01_0061__p8898339203811">By default, JSON is returned for query. You can also set the format parameter for the data to be returned in CSV format.</p>
<pre class="screen" id="css_01_0061__screen15165124973920">POST _opendistro/_sql?format=csv
</li><li id="css_01_0061__li19313824444">By default, the result is returned in the JSON structure. If you want the result to be returned in the CSV format, run the following command:<pre class="screen" id="css_01_0061__screen120515501255">POST _opendistro/_sql?format=csv
{
"query": "SELECT * FROM my-index LIMIT 50"
}</pre>
<p id="css_01_0061__p488812144013">When data is returned in CSV format, each row corresponds to a document and each column corresponds to a field.</p>
<p id="css_01_0061__p14212203148">When data is returned in the CSV format, each row corresponds to a document and each column corresponds to a field.</p>
</li></ul>
</li><li id="css_01_0061__li343015161417">cURL commands<p id="css_01_0061__p10352171713713"><a name="css_01_0061__li343015161417"></a><a name="li343015161417"></a>You can also run cURL commands in ECS to execute SQL statements.</p>
<pre class="screen" id="css_01_0061__screen048591921014">curl -XPOST https://localhost:9200/_opendistro/_sql -u username:password -k -d '{"query": "SELECT * FROM kibana_sample_data_flights LIMIT 10"}' -H 'Content-Type: application/json'</pre>
</li></ul>
</div>
<div class="section" id="css_01_0061__section17251759164012"><h4 class="sectiontitle">Supported Operations</h4><p id="css_01_0061__p162295419416">Open Distro for Elasticsearch supports the following SQL operations: statements, conditions, aggregations, include and exclude fields, common functions, joins, and show.</p>
<ul id="css_01_0061__ul465451824513"><li id="css_01_0061__li1765481815457">Statements
@ -266,17 +266,17 @@
</thead>
<tbody><tr id="css_01_0061__row13632937105516"><td class="cellrowborder" valign="top" width="11.59%" headers="mcps1.3.4.7.1.1.2.3.1.1 "><p id="css_01_0061__p616054985515">Inner join</p>
</td>
<td class="cellrowborder" valign="top" width="88.41%" headers="mcps1.3.4.7.1.1.2.3.1.2 "><p id="css_01_0061__p5160849115513">SELECT p.firstname, p.lastname, p.gender, dogs.name FROM people p JOIN dogs d ON d.holdersName = p.firstname WHERE p.age &gt; 12 AND d.age &gt; 1</p>
<td class="cellrowborder" valign="top" width="88.41%" headers="mcps1.3.4.7.1.1.2.3.1.2 "><p id="css_01_0061__p1281322512377">SELECT s.firstname, s.lastname, s.gender, sc.name FROM student s JOIN school sc ON sc.name = s.school_name WHERE s.age &gt; 20</p>
</td>
</tr>
<tr id="css_01_0061__row18632153725514"><td class="cellrowborder" valign="top" width="11.59%" headers="mcps1.3.4.7.1.1.2.3.1.1 "><p id="css_01_0061__p19160124955518">Left outer join</p>
</td>
<td class="cellrowborder" valign="top" width="88.41%" headers="mcps1.3.4.7.1.1.2.3.1.2 "><p id="css_01_0061__p1516064917557">SELECT p.firstname, p.lastname, p.gender, dogs.name FROM people p LEFT JOIN dogs d ON d.holdersName = p.firstname</p>
<td class="cellrowborder" valign="top" width="88.41%" headers="mcps1.3.4.7.1.1.2.3.1.2 "><p id="css_01_0061__p19882134153819">SELECT s.firstname, s.lastname, s.gender, sc.name FROM student s LEFT JOIN school sc ON sc.name = s.school_name</p>
</td>
</tr>
<tr id="css_01_0061__row6632203785510"><td class="cellrowborder" valign="top" width="11.59%" headers="mcps1.3.4.7.1.1.2.3.1.1 "><p id="css_01_0061__p131615491559">Cross join</p>
</td>
<td class="cellrowborder" valign="top" width="88.41%" headers="mcps1.3.4.7.1.1.2.3.1.2 "><p id="css_01_0061__p20161144995515">SELECT p.firstname, p.lastname, p.gender, dogs.name FROM people p CROSS JOIN dogs d</p>
<td class="cellrowborder" valign="top" width="88.41%" headers="mcps1.3.4.7.1.1.2.3.1.2 "><p id="css_01_0061__p93604212399">SELECT s.firstname, s.lastname, s.gender, sc.name FROM student s CROSS JOIN school sc</p>
</td>
</tr>
</tbody>

13
docs/css/umn/css_01_0070.html Normal file
View File

@ -0,0 +1,13 @@
<a name="css_01_0070"></a><a name="css_01_0070"></a>
<h1 class="topictitle1">Permissions Management</h1>
<div id="body0000001334619285"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_01_0072.html">Creating a User and Granting Permissions</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0086.html">CSS Custom Policies</a></strong><br>
</li>
</ul>
</div>

22
docs/css/umn/css_01_0072.html Normal file
View File

@ -0,0 +1,22 @@
<a name="css_01_0072"></a><a name="css_01_0072"></a>
<h1 class="topictitle1">Creating a User and Granting Permissions</h1>
<div id="body0000001334459429"><p id="css_01_0072__p47111042131913">This chapter describes how to use to implement fine-grained permissions control for your CloudSearch Service (CSS) resources. With IAM, you can:</p>
<ul id="css_01_0072__ul1848820457453"><li id="css_01_0072__li348974516454">Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing CSS resources.</li><li id="css_01_0072__li11681126173515">Grant only the permissions required for users to perform a specific task.</li><li id="css_01_0072__li12185165313915">Entrust a account or cloud service to perform efficient O&amp;M on your CSS resources.</li></ul>
<p id="css_01_0072__p14662743155318">If your account does not require individual IAM users, skip this chapter.</p>
<p id="css_01_0072__p158501603165">This section describes the procedure for granting permissions (see <a href="#css_01_0072__fig342064620244">Figure 1</a>).</p>
<div class="section" id="css_01_0072__section17110143884619"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0072__p148607912478">Before assigning permissions to user groups, you should learn about the system policies listed in <a href="css_04_0014.html">Permissions Management</a>.</p>
</div>
<div class="section" id="css_01_0072__section85262192392"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="css_01_0072__fig342064620244"><a name="css_01_0072__fig342064620244"></a><a name="fig342064620244"></a><span class="figcap"><b>Figure 1 </b>Process for granting CSS permissions</span><br><span><img id="css_01_0072__image237123492418" src="en-us_image_0000001525365837.png"></span></div>
<ol id="css_01_0072__ol155777193394"><li id="css_01_0072__li8182365323"><a name="css_01_0072__li8182365323"></a><a name="li8182365323"></a><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0030.html" target="_blank" rel="noopener noreferrer">Create a user group and assign permissions</a><p id="css_01_0072__p2829617113210">Create a user group on the IAM console, and assign the CSS permission to the group.</p>
</li><li id="css_01_0072__li1557731911394"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0031.html" target="_blank" rel="noopener noreferrer">Create a user and add it to a user group</a><p id="css_01_0072__p357781916392">Create a user on the IAM console and add the user to the group created in <a href="#css_01_0072__li8182365323">1. Create a user group a...</a>.</p>
</li><li id="css_01_0072__li55771919173916"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html" target="_blank" rel="noopener noreferrer">Log in as an IAM user</a> and verify permissions.<p id="css_01_0072__p20577191943913">Log in to the CSS console as the created user, and verify that it only has read permissions for CSS.</p>
</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0070.html">Permissions Management</a></div>
</div>
</div>

20
docs/css/umn/css_01_0074.html Normal file
View File

@ -0,0 +1,20 @@
<a name="css_01_0074"></a><a name="css_01_0074"></a>
<h1 class="topictitle1">Changing Specifications</h1>
<div id="body0000001282339382"><p id="css_01_0074__p952841510302">If the workloads on the data plane of a cluster change, you can change its node specifications as needed.</p>
<div class="section" id="css_01_0074__section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0074__ul1977488417"><li id="css_01_0074__li157741281010">The target cluster is available and has no tasks in progress.</li><li id="css_01_0074__li13774781313">The target cluster has sufficient quotas available.</li></ul>
</div>
<div class="section" id="css_01_0074__section12477125117522"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0074__ul133851234195413"><li id="css_01_0074__li776243913339">The node number and storage capacity cannot be modified when you change the node specifications.</li><li id="css_01_0074__li2968184010249">The specifications can only be increased. To decrease cluster specifications, create a cluster with smaller specifications and migrate the data from the current cluster to it.</li><li id="css_01_0074__li9394184952715">If a cluster has multiple node types, you can change the specifications of only one type at a time. After the change, nodes in other types still maintain their original specifications.</li><li id="css_01_0074__li11208141072513">If the data volume is large, it may take long to modify the node specifications. You are advised to modify specifications during off-peak hours.</li><li id="css_01_0074__li4349142752218">Kibana is unavailable during specification change.</li><li id="css_01_0074__li82081010152517">When changing the node specifications, ensure that all service data has copies so the services will not be interrupted.<p id="css_01_0074__p103331126538"><a name="css_01_0074__li82081010152517"></a><a name="li82081010152517"></a>Run the <b><span class="cmdname" id="css_01_0074__cmdname6700234541">GET _cat/indices?v</span></b> command in Kibana. If the returned <strong id="css_01_0074__b6712450484">rep</strong> value is greater than <strong id="css_01_0074__b4712135194810">0</strong>, the data has copies. If the returned <strong id="css_01_0074__b171217517481">rep</strong> value is <strong id="css_01_0074__b171211534817">0</strong>, the data has no copies. In this case, create snapshot for the cluster by referring to <a href="css_01_0033.html#css_01_0033__section43906502025">Manually Creating a Snapshot</a>.</p>
</li><li id="css_01_0074__li144781317132514">During the specification modification, the nodes are stopped and restarted in sequence. It is a rolling process.</li></ul>
</div>
<div class="section" id="css_01_0074__section1177713055318"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0074__ol373518361145"><li id="css_01_0074__li1173513611411">Log in to the CSS management console.</li><li id="css_01_0074__li17735636141417">In the navigation pane on the left, choose <strong id="css_01_0074__b6994346194014">Clusters</strong>. On the displayed <strong id="css_01_0074__b139951546184015">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0074__b1299524674011">More</strong> &gt; <span class="uicontrol" id="css_01_0074__uicontrol799618463406"><b>Scale Cluster</b></span> in the <strong id="css_01_0074__b9996746184013">Operation</strong> column.</li><li id="css_01_0074__li13735736141416">On the <strong id="css_01_0074__b139701824122116">Modify Configuration</strong> page, set parameters to change specifications.<ul id="css_01_0074__ul02151151205413"><li id="css_01_0074__li22151851165410"><strong id="css_01_0074__b1610123684611">New Node Specifications</strong> The specifications of the default data nodes. Select the specifications from the drop-down list as required.</li><li id="css_01_0074__li3856947564">If a cluster has master nodes, client nodes, or cold data nodes, you can change their specifications.</li></ul>
</li><li id="css_01_0074__li173623641418">Click <strong id="css_01_0074__b4516462531">Next: Scale Now</strong>.</li><li id="css_01_0074__li47662104588">Confirm the information and click <strong id="css_01_0074__b7215174717539">Submit</strong>.</li><li id="css_01_0074__li2715619173320">In the displayed <strong id="css_01_0074__b443918125715">Verify Index Copy</strong> dialog box, select <strong id="css_01_0074__b18430641403">Verify index copies</strong> if you need. Click <strong id="css_01_0074__b4625153716117">OK</strong>.<ul id="css_01_0074__ul11251317014"><li id="css_01_0074__li71251712015">If you selected <strong id="css_01_0074__b175584311537">Verify index copies</strong> and the cluster has no master node, indexes must have at least one copy and the cluster must have at least three nodes.</li><li id="css_01_0074__li10125417018">If you selected <strong id="css_01_0074__b5645112558">Verify index copies</strong> and the cluster has no master node, indexes must have at least one copy.</li></ul>
</li><li id="css_01_0074__li13737436141418">Click <span class="uicontrol" id="css_01_0074__uicontrol959313376555"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0074__b059913712551">Clusters</strong> page. The <span class="parmname" id="css_01_0074__parmname14828181315618"><b>Cluster Status</b></span> is <span class="parmvalue" id="css_01_0074__parmvalue158281513185618"><b>Configuration modified</b></span>. When <span class="parmname" id="css_01_0074__parmname1688618895611"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="css_01_0074__parmvalue168861889568"><b>Available</b></span>, the cluster specifications have been successfully modified.</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0149.html">Scaling In/Out a Cluster</a></div>
</div>
</div>

10
docs/css/umn/css_01_0077.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">Managing Logs</h1>
<div id="body0000001334619305"><p id="css_01_0077__p8060118">CSS provides log backup and search functions to help you locate faults. You can back up cluster logs to OBS buckets and download required log files to analyze and locate faults.</p>
<div class="section" id="css_01_0077__section3460103108"><h4 class="sectiontitle">Enabling Log Management</h4><ol id="css_01_0077__ol17582191371010"><li id="css_01_0077__li1142971461017">Log in to the <span id="css_01_0077__text208055615149">CSS</span> management console.</li><li id="css_01_0077__li174291147108">On the <span class="wintitle" id="css_01_0077__wintitle8360185213588"><b>Clusters</b></span> page, click the name of the cluster whose logs you want to back up. The <strong id="css_01_0077__b1367251018">Basic Information</strong> page is displayed.</li><li id="css_01_0077__li193846159103">Click the <strong id="css_01_0077__b2144835102913">Logs</strong> tab and enable <strong id="css_01_0077__b1980234311305">Log Management</strong>.<p id="css_01_0077__p2678171913911"><span><img id="css_01_0077__image1967812191691" src="en-us_image_0000001286596282.png"></span> indicates that the log management function is disabled. <span><img id="css_01_0077__image8410195516444" src="en-us_image_0000001338716685.png"></span> indicates that it is enabled.</p>
<div class="section" id="css_01_0077__section3460103108"><h4 class="sectiontitle">Enabling Log Management</h4><ol id="css_01_0077__ol17582191371010"><li id="css_01_0077__li1142971461017">Log in to the <span id="css_01_0077__text208055615149">CSS</span> management console.</li><li id="css_01_0077__li174291147108">On the <span class="wintitle" id="css_01_0077__wintitle8360185213588"><b>Clusters</b></span> page, click the name of the cluster whose logs you want to back up. The <strong id="css_01_0077__b1367251018">Basic Information</strong> page is displayed.</li><li id="css_01_0077__li193846159103">Click the <strong id="css_01_0077__b2144835102913">Logs</strong> tab and enable <strong id="css_01_0077__b1980234311305">Log Management</strong>.<p id="css_01_0077__p2678171913911"><span><img id="css_01_0077__image1967812191691" src="en-us_image_0000001474565996.png"></span> indicates that the log management function is disabled. <span><img id="css_01_0077__image8410195516444" src="en-us_image_0000001524925961.png"></span> indicates that it is enabled.</p>
</li><li id="css_01_0077__li51851453313">Enable the <strong id="css_01_0077__b950811661914">Log Management</strong> function. In the <strong id="css_01_0077__b632317184">Edit Log Backup Configuration</strong> dialog box, set the parameters.<p id="css_01_0077__p95434531512">In the displayed dialog box, <strong id="css_01_0077__b15941312014">OBS Bucket</strong>, <strong id="css_01_0077__b0228191212015">Backup Path</strong>, and <strong id="css_01_0077__b21966174205">IAM Agency</strong> are automatically created for log backup. You can modify the default value by referring to <a href="#css_01_0077__table109611127114919">Table 1</a>.</p>
<div class="tablenoborder"><a name="css_01_0077__table109611127114919"></a><a name="table109611127114919"></a><table cellpadding="4" cellspacing="0" summary="" id="css_01_0077__table109611127114919" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="css_01_0077__row595810278493"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.2.2.4.4.2.4.1.1"><p id="css_01_0077__p695812714916">Parameter</p>
@ -33,16 +33,16 @@
</tbody>
</table>
</div>
</li><li id="css_01_0077__li196572027145716">(Optional) If the <strong id="css_01_0077__b1369342514332">Log Management</strong> function has been enabled for the cluster, you can modify the log backup parameters.<p id="css_01_0077__p1227972805710">Click <span><img id="css_01_0077__image1727110018566" src="en-us_image_0000001286116778.png"></span> on the right of <span class="parmname" id="css_01_0077__parmname027115045612"><b>Log Backup Configuration</b></span>. The <strong id="css_01_0077__b382312516334">Edit Log Backup Configuration</strong> dialog box is displayed. You can modify the log backup parameters.</p>
</li><li id="css_01_0077__li196572027145716">(Optional) If the <strong id="css_01_0077__b1369342514332">Log Management</strong> function has been enabled for the cluster, you can modify the log backup parameters.<p id="css_01_0077__p1227972805710">Click <span><img id="css_01_0077__image1727110018566" src="en-us_image_0000001524925965.png"></span> on the right of <span class="parmname" id="css_01_0077__parmname027115045612"><b>Log Backup Configuration</b></span>. The <strong id="css_01_0077__b382312516334">Edit Log Backup Configuration</strong> dialog box is displayed. You can modify the log backup parameters.</p>
</li><li id="css_01_0077__li98491420132518">Back up logs.<ul id="css_01_0077__ul91221854141616"><li id="css_01_0077__li10122205417169">Automatically backing up logs<p id="css_01_0077__p2044412216265"><a name="css_01_0077__li10122205417169"></a><a name="li10122205417169"></a>Click the icon on the right of <span class="parmname" id="css_01_0077__parmname79609170530"><b>Auto Backup</b></span> to enable the auto backup function.</p>
<p id="css_01_0077__p17014512439"><span><img id="css_01_0077__image11999195014317" src="en-us_image_0000001338955993.png"></span> indicates that the auto backup function is enabled, and <span><img id="css_01_0077__image19958175044319" src="en-us_image_0000001286596282.png"></span> indicates that it is disabled.</p>
<p id="css_01_0077__p1372917352620">After the automatic backup function is enabled, set the backup start time in the <strong id="css_01_0077__b12645161514561">Modify Log Backup Policy</strong> dialog box. When the scheduled time arrives, the system will back up logs automatically. Click <span><img id="css_01_0077__image1702444111517" src="en-us_image_0000001338716677.png"></span> on the right of the switch to change <span class="parmname" id="css_01_0077__parmname18195113613169"><b>Backup Start Time</b></span>.</p>
<p id="css_01_0077__p17014512439"><span><img id="css_01_0077__image11999195014317" src="en-us_image_0000001525205857.png"></span> indicates that the auto backup function is enabled, and <span><img id="css_01_0077__image19958175044319" src="en-us_image_0000001474565996.png"></span> indicates that it is disabled.</p>
<p id="css_01_0077__p1372917352620">After the automatic backup function is enabled, set the backup start time in the <strong id="css_01_0077__b12645161514561">Modify Log Backup Policy</strong> dialog box. When the scheduled time arrives, the system will back up logs automatically. Click <span><img id="css_01_0077__image1702444111517" src="en-us_image_0000001474246372.png"></span> on the right of the switch to change <span class="parmname" id="css_01_0077__parmname18195113613169"><b>Backup Start Time</b></span>.</p>
</li><li id="css_01_0077__li08181026122616">Manually backing up logs<p id="css_01_0077__p158454714287"><a name="css_01_0077__li08181026122616"></a><a name="li08181026122616"></a>On the <strong id="css_01_0077__b45486296411">Log Backup</strong> tab page, click <strong id="css_01_0077__b138724501035">Back Up</strong>. On the displayed page, click <span class="uicontrol" id="css_01_0077__uicontrol856611561879"><b>Yes</b></span> to start backup.</p>
<p id="css_01_0077__p218113822620">If <strong id="css_01_0077__b1618119568920">Task Status</strong> in the log backup list is <strong id="css_01_0077__b840532321317">Successful</strong>, the backup is successful.</p>
<div class="note" id="css_01_0077__note13497430133916"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0077__p19497143018398">All logs in the cluster are copied to a specified OBS path. You can view or download log files from the path of the OBS bucket.</p>
</div></div>
</li></ul>
</li><li id="css_01_0077__li74758710224">Search for logs.<p id="css_01_0077__p594025005113"><a name="css_01_0077__li74758710224"></a><a name="li74758710224"></a>On the <strong id="css_01_0077__b8786450104110">Log Search</strong> page, select the desired node, log type, and log level, and click <span><img id="css_01_0077__image878610507412" src="en-us_image_0000001286276702.png"></span>. The search results are displayed.</p>
</li><li id="css_01_0077__li74758710224">Search for logs.<p id="css_01_0077__p594025005113"><a name="css_01_0077__li74758710224"></a><a name="li74758710224"></a>On the <strong id="css_01_0077__b8786450104110">Log Search</strong> page, select the desired node, log type, and log level, and click <span><img id="css_01_0077__image878610507412" src="en-us_image_0000001524766285.png"></span>. The search results are displayed.</p>
<p id="css_01_0077__p13365112615198">When you search for logs, the latest 10,000 logs are matched. A maximum of 100 logs are displayed.</p>
</li></ol>
</div>

15
docs/css/umn/css_01_0078.html
View File

@ -1,11 +1,20 @@
<a name="css_01_0078"></a><a name="css_01_0078"></a>
<h1 class="topictitle1">Managing Plugins</h1>
<div id="body0000001334778801"><p id="css_01_0078__p8060118">CSS allows you to view default plugins. </p>
<ol id="css_01_0078__ol10542121115215"><li id="css_01_0078__li268718155528">Log in to the <span id="css_01_0078__text106981435525">CSS</span> management console.</li><li id="css_01_0078__li126881515125217">On the <strong id="css_01_0078__b842352706161126">Clusters</strong> page, click the name of a cluster for which you want to install a plugin.<p id="css_01_0078__p14688161585217">The <strong id="css_01_0078__b1721173414116">Basic Information</strong> page is displayed.</p>
</li><li id="css_01_0078__li1568891595211">Click the <strong id="css_01_0078__b1076118567116">Plugins</strong> tab.</li><li id="css_01_0078__li1713152216523">View the information about default plugins.<p id="css_01_0078__p1431114470344"><a name="css_01_0078__li1713152216523"></a><a name="li1713152216523"></a>On the <strong id="css_01_0078__b1715852119">Default</strong> page, view default plugins supported by the current version.</p>
<div id="body0000001334778801"><p id="css_01_0078__p8060118">CSS clusters have default plugins. You can view the default plugin information on the console or Kibana.</p>
<div class="section" id="css_01_0078__section453693291618"><h4 class="sectiontitle">Viewing Plugins on the Console</h4><ol id="css_01_0078__ol1777116816175"><li id="css_01_0078__li1777128131713">Log in to the <span id="css_01_0078__text14590956181419">CSS</span> management console.</li><li id="css_01_0078__li27711380178">In the navigation pane, choose <strong id="css_01_0078__b4752122753314">Clusters</strong>. Click the target cluster name and go to the <strong id="css_01_0078__b222652583417">Basic Information</strong> page of the cluster.</li><li id="css_01_0078__li1177198181710">Click the <strong id="css_01_0078__b128811734172017">Plugins</strong> tab.</li><li id="css_01_0078__li4771885179">On the <strong id="css_01_0078__b64951129102915">Default</strong> page, view default plugins supported by the current version.</li></ol>
</div>
<div class="section" id="css_01_0078__section720910400168"><h4 class="sectiontitle">Viewing Plugins on the Kibana</h4><ol id="css_01_0078__ol8973119141910"><li id="css_01_0078__li483113274712">Log in to the CSS management console.</li><li id="css_01_0078__li201191431164715">In the navigation pane, choose <strong id="css_01_0078__b17723525183419">Clusters</strong>. Locate the target cluster and click <strong id="css_01_0078__b7219134473419">Access Kibana</strong> in the <strong id="css_01_0078__b219794824215">Operation</strong> column to log in to Kibana.</li><li id="css_01_0078__li1390318464482">Go to <strong id="css_01_0078__b71607553420">Dev Tools</strong> and run the following command to view the cluster plugin information:<pre class="screen" id="css_01_0078__screen2057975202912">GET _cat/plugins?v</pre>
<p id="css_01_0078__p1633995812820">The following is an example of the response body:</p>
<pre class="screen" id="css_01_0078__screen14121119194212">name component version
css-2918-ess-esn-1-1 analysis-dynamic-synonym 7.10.2-h0.cbu.css.v1.0.0.0.r1
css-2918-ess-esn-1-1 analysis-icu 7.10.2-h0.cbu.css.v1.0.0.3.r1
css-2918-ess-esn-1-1 analysis-ik 7.10.2-h0.cbu.css.v1.0.0.0.r1
......</pre>
<p id="css_01_0078__p129152395303"><strong id="css_01_0078__b980593118438">name</strong> indicates the cluster node name, <strong id="css_01_0078__b193853924317">component</strong> indicates the plugin name, and <strong id="css_01_0078__b148461459154319">version</strong> indicates the plugin version.</p>
</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0009.html">Managing Elasticsearch Clusters</a></div>

17
docs/css/umn/css_01_0081.html Normal file
View File

@ -0,0 +1,17 @@
<a name="css_01_0081"></a><a name="css_01_0081"></a>
<h1 class="topictitle1">Removing Specified Nodes</h1>
<div id="body0000001282179470"><p id="css_01_0081__p18220112044212">If a cluster can process existing data without fully using its nodes, you can remove one or more specified nodes from the cluster to reduce costs. Services will not be interrupted during the removal of specified nodes.</p>
<div class="section" id="css_01_0081__section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0081__p11955155417393">The target cluster is available and has no tasks in progress.</p>
</div>
<div class="section" id="css_01_0081__section12477125117522"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0081__ul4155162820100"><li id="css_01_0081__li108232692012">Ensure that the disk usage after scale-in is less than 80% and each AZ of each node type has at least one node.</li><li id="css_01_0081__li1176612232246">In a cross-AZ cluster, the difference between the numbers of the same type nodes in different AZs cannot exceed 1.</li><li id="css_01_0081__li16801597451">For a cluster without master nodes, the number of removed data nodes and cold data nodes in a scale-in must be fewer than half of the original number of data nodes and cold data nodes, and the number of remaining data nodes and cold data nodes after a scale-in must be greater than the maximum number of index replicas.</li><li id="css_01_0081__li973819931412">For a cluster with master nodes, the number of removed master nodes in a scale-in must be fewer than half of the original master node number. After scale-in, there has to be an odd number of master nodes, and there has to be at least three of them.</li></ul>
</div>
<div class="section" id="css_01_0081__section1177713055318"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0081__ol373518361145"><li id="css_01_0081__li1173513611411">Log in to the CSS management console.</li><li id="css_01_0081__li17735636141417">In the navigation pane on the left, choose <strong id="css_01_0081__b4581281416">Clusters</strong>. On the displayed <strong id="css_01_0081__b1359386417">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0081__b205968174115">More</strong> &gt; <span class="uicontrol" id="css_01_0081__uicontrol4606818419"><b>Scale Cluster</b></span> in the <strong id="css_01_0081__b1760138194116">Operation</strong> column.</li><li id="css_01_0081__li239201117417">Choose the <strong id="css_01_0081__b157985124360">Scale In</strong> tab.</li><li id="css_01_0081__li13735736141416">Select the target nodes.</li><li id="css_01_0081__li173623641418">Click <strong id="css_01_0081__b132739503017">Scale Now</strong>.</li><li id="css_01_0081__li462507104311">Confirm the information and click <strong id="css_01_0081__b0322651152714">Submit</strong>.</li><li id="css_01_0081__li13737436141418">Click <span class="uicontrol" id="css_01_0081__uicontrol17971144202913"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0081__b480424442912">Clusters</strong> page. The <span class="parmname" id="css_01_0081__parmname14976203323714"><b>Task Status</b></span> is <span class="parmvalue" id="css_01_0081__parmvalue19824339375"><b>Scaling in</b></span>. When <span class="parmname" id="css_01_0081__parmname4178951132918"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="css_01_0081__parmvalue13177185162918"><b>Available</b></span>, the cluster has been successfully scaled in.</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0149.html">Scaling In/Out a Cluster</a></div>
</div>
</div>

4
docs/css/umn/css_01_0082.html
View File

@ -4,7 +4,7 @@
<div id="body0000001282658986"><p id="css_01_0082__p8060118">The VPC endpoint service allows you to access the cluster through a private domain name. When the VPC endpoint service is enabled, the system creates a VPC endpoint for you by default. To create a VPC endpoint, you must have the required permissions. For details, see .</p>
<div class="caution" id="css_01_0082__note91924414116"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="css_01_0082__p131922418116">The public IP address access and VPC endpoint service share a load balancer. If you have configured a public access whitelist, public and private IP addresses that access the cluster through VPCEP are restricted because the public IP address access shares the load balancer with the VPC endpoint service. In this case, you need to add IP address <strong id="css_01_0082__b18782184310187">198.19.128.0/17</strong> to the public access whitelist to allow traffic through VPCEP.</p>
</div></div>
<div class="section" id="css_01_0082__section115745793915"><h4 class="sectiontitle">Enabling the VPC Endpoint Service</h4><ol id="css_01_0082__ol77309120406"><li id="css_01_0082__li1142971461017">Log in to the <span id="css_01_0082__text7429314121020">CSS</span> management console.</li><li id="css_01_0082__li19621829513">On the <strong id="css_01_0082__b192581638133917">Create Cluster</strong> page, set <strong id="css_01_0082__b11258193833914">Advanced Settings</strong> to <strong id="css_01_0082__b1125853873915">Custom</strong>. Enable the VPC endpoint service.<div class="p" id="css_01_0082__p1137224919313"><ul id="css_01_0082__ul1376659192617"><li id="css_01_0082__li97412595266"><strong id="css_01_0082__b1725875612216">Private Domain Name Creation</strong>: If you enable this function, the system automatically creates a private domain name for you, which you can use to access the cluster.</li><li id="css_01_0082__li67635972618"><strong id="css_01_0082__b8285569516">VPC Endpoint Service Whitelist</strong>: You can add an authorized account ID to the VPC endpoint service whitelist. Then you can access the cluster using the domain name or the node IP address.<p id="css_01_0082__p1676659142611">Click <span><img id="css_01_0082__image881313257920" src="en-us_image_0000001286276706.png"></span> to add multiple accounts. You can also click <strong id="css_01_0082__b155432384615">Delete</strong> in the <strong id="css_01_0082__b355562384612">Operation</strong> column to delete accounts.</p>
<div class="section" id="css_01_0082__section115745793915"><h4 class="sectiontitle">Enabling the VPC Endpoint Service</h4><ol id="css_01_0082__ol77309120406"><li id="css_01_0082__li1142971461017">Log in to the <span id="css_01_0082__text7429314121020">CSS</span> management console.</li><li id="css_01_0082__li19621829513">On the <strong id="css_01_0082__b192581638133917">Create Cluster</strong> page, set <strong id="css_01_0082__b11258193833914">Advanced Settings</strong> to <strong id="css_01_0082__b1125853873915">Custom</strong>. Enable the VPC endpoint service.<div class="p" id="css_01_0082__p1137224919313"><ul id="css_01_0082__ul1376659192617"><li id="css_01_0082__li97412595266"><strong id="css_01_0082__b1725875612216">Private Domain Name Creation</strong>: If you enable this function, the system automatically creates a private domain name for you, which you can use to access the cluster.</li><li id="css_01_0082__li67635972618"><strong id="css_01_0082__b8285569516">VPC Endpoint Service Whitelist</strong>: You can add an authorized account ID to the VPC endpoint service whitelist. Then you can access the cluster using the domain name or the node IP address.<p id="css_01_0082__p1676659142611">Click <span><img id="css_01_0082__image881313257920" src="en-us_image_0000001524766309.png"></span> to add multiple accounts. You can also click <strong id="css_01_0082__b155432384615">Delete</strong> in the <strong id="css_01_0082__b355562384612">Operation</strong> column to delete accounts.</p>
</li></ul>
<div class="note" id="css_01_0082__note47795914269"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="css_01_0082__ul127765992615"><li id="css_01_0082__li2076259172619">If the authorization account ID is set to <strong id="css_01_0082__b42893549528">*</strong>, all users are allowed to access the cluster.</li><li id="css_01_0082__li107614595262">You can view authorized account IDs on the <strong id="css_01_0082__b82340124535">My Credentials</strong> page.</li><li id="css_01_0082__li177785972613">After the VPC endpoint service is enabled for a cluster, you will be billed per use. For more information, see .</li></ul>
</div></div>
@ -12,7 +12,7 @@
</li></ol>
</div>
<div class="section" id="css_01_0082__section12521512195113"><h4 class="sectiontitle">Managing VPC Endpoint Service</h4><p id="css_01_0082__p8328122613523">You can enable the VPC endpoint service while creating a cluster, and also enable it by performing the following steps after cluster creation.</p>
<ol id="css_01_0082__ol146347435519"><li id="css_01_0082__li7625635121410">Log in to the <span id="css_01_0082__text1762514356145">CSS</span> management console.</li><li id="css_01_0082__li106254357143">On the <span class="wintitle" id="css_01_0082__wintitle20562115115114"><b>Clusters</b></span> page, click the name of the target cluster.</li><li id="css_01_0082__li1068041913586">Click the <strong id="css_01_0082__b14205337339">VPC Endpoint Service</strong> tab, and turn on the button next to <strong id="css_01_0082__b315831114818">VPC Endpoint Service</strong>.<p id="css_01_0082__p114151437125520"><span><img id="css_01_0082__image84151437185519" src="en-us_image_0000001338955989.png"></span> indicates disabling the VPC endpoint service and <span><img id="css_01_0082__image8410195516444" src="en-us_image_0000001338836529.png"></span> indicates enabling the VPC endpoint service.</p>
<ol id="css_01_0082__ol146347435519"><li id="css_01_0082__li7625635121410">Log in to the <span id="css_01_0082__text1762514356145">CSS</span> management console.</li><li id="css_01_0082__li106254357143">On the <span class="wintitle" id="css_01_0082__wintitle20562115115114"><b>Clusters</b></span> page, click the name of the target cluster.</li><li id="css_01_0082__li1068041913586">Click the <strong id="css_01_0082__b14205337339">VPC Endpoint Service</strong> tab, and turn on the button next to <strong id="css_01_0082__b315831114818">VPC Endpoint Service</strong>.<p id="css_01_0082__p114151437125520"><span><img id="css_01_0082__image84151437185519" src="en-us_image_0000001474246392.png"></span> indicates disabling the VPC endpoint service and <span><img id="css_01_0082__image8410195516444" src="en-us_image_0000001474406048.png"></span> indicates enabling the VPC endpoint service.</p>
<p id="css_01_0082__p186900304331">In the displayed dialog box, you can determine whether to enable the private domain name. After a private domain name is created, you can access the cluster using the private domain name.</p>
<div class="note" id="css_01_0082__note365442833217"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="css_01_0082__ul10498537163212"><li id="css_01_0082__li74981437183213">After you enable the VPC endpoint service, you can use the private domain name or node IP address generated by the endpoint to access the cluster. For details, see <a href="#css_01_0082__section19864153679">Accessing the Cluster Using the Private Domain Name or Node IP Address</a>.</li><li id="css_01_0082__li4254839163219">If you disable the VPC endpoint service, none of the users can access the cluster using the private domain name.</li></ul>
</div></div>

82
docs/css/umn/css_01_0086.html Normal file
View File

@ -0,0 +1,82 @@
<a name="css_01_0086"></a><a name="css_01_0086"></a>
<h1 class="topictitle1">CSS Custom Policies</h1>
<div id="body0000001334739173"><p id="css_01_0086__p8060118">Custom policies can be created to supplement the system-defined policies of CSS. For the actions supported for custom policies, see Permissions Policies and Supported Actions.</p>
<p id="css_01_0086__p18119246101411">You can create custom policies in either of the following ways:</p>
<ul id="css_01_0086__ul611914619143"><li id="css_01_0086__li51194467143">Visual editor: Select cloud services, actions, resources, and request conditions. You do not need to have knowledge of the policy syntax.</li><li id="css_01_0086__li1012004631418">JSON: Create a JSON policy or edit based on an existing policy.</li></ul>
<p id="css_01_0086__p1761612181719">For details about how to create custom policies, see <a href="https://docs.otc.t-systems.com/usermanual/iam/en-us_topic_0274187246.html" target="_blank" rel="noopener noreferrer">Creating a Custom Policy</a>. The following section contains examples of common CSS custom policies.</p>
<div class="note" id="css_01_0086__note185014141059"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0086__p05121415516">IAM permissions and data plane cluster permissions are managed separately. To enable the security capability of the data plane, you need to use the security mode.</p>
</div></div>
<div class="section" id="css_01_0086__section11742221141718"><h4 class="sectiontitle">Example Custom Policies</h4><div class="p" id="css_01_0086__p1432933191710">Example 1: Allowing users to create a CSS cluster<pre class="screen" id="css_01_0086__screen152401381336">{
"Version": "1.1",
"Statement": [
{
"Action": [
"css:cluster:create",
"vpc:securityGroups:get",
"vpc:securityGroups:create",
"vpc:securityGroups:delete",
"vpc:securityGroupRules:get",
"vpc:securityGroupRules:create",
"vpc:securityGroupRules:delete",
"vpc:vpcs:list",
"vpc:privateIps:list",
"vpc:ports:get",
"vpc:ports:create",
"vpc:ports:update",
"vpc:ports:delete",
"vpc:quotas:list",
"vpc:subnets:get",
"ecs:cloudServerFlavors:get",
"ecs:serverInterfaces:use",
"ecs:cloudServers:addNics",
"ecs:quotas:get",
"evs:types:get",
"evs:quotas:get"
],
"Effect": "Allow"
}
]
}</pre>
</div>
</div>
<p id="css_01_0086__p621012411612">Example 2: Denying cluster deletion</p>
<p id="css_01_0086__p330217517918">A policy with only <strong id="css_01_0086__b280663672512">Deny</strong> permissions must be used in conjunction with other policies for it to take effect. If the permissions assigned to a user contain both <strong id="css_01_0086__b10916207112917">Allow</strong> and <strong id="css_01_0086__b18462108298">Deny</strong>, the <strong id="css_01_0086__b136841411142913">Deny</strong> permissions take precedence over the <strong id="css_01_0086__b449222772919">Allow</strong> permissions.</p>
<p id="css_01_0086__p153024511596">The following method can be used if you need to assign permissions of the <strong id="css_01_0086__b58500418547">CSS Admin</strong> policy to a user but you want to prevent the user from deleting clusters. Create a custom policy for denying cluster deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on CSS except deleting clusters. The following is an example of a deny policy:</p>
<pre class="screen" id="css_01_0086__screen16334701457">{
"Version": "1.1",
"Statement": [
{
"Effect": "Deny",
"Action": [
"css:cluster:delete"
]
}
]
}
</pre>
<p id="css_01_0086__p878717221976">Example 3: Defining permissions for multiple services in a policy</p>
<p id="css_01_0086__p3199162311713">A custom policy can contain the actions of multiple services that are of the global or project-level type. The following is an example policy containing actions of multiple services:</p>
<pre class="screen" id="css_01_0086__screen1481815563226">{
"Version": "1.1",
"Statement": [
{
"Action": [
"ecs:cloudServers:resize",
"ecs:cloudServers:delete",
"ecs:cloudServers:delete",
"css:cluster:restart",
"css:*:get*",
"css:*:list*"
],
"Effect": "Allow"
}
]
}</pre>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0070.html">Permissions Management</a></div>
</div>
</div>

2
docs/css/umn/css_01_0088.html
View File

@ -38,7 +38,7 @@
</li></ol>
</div>
<div class="section" id="css_01_0088__section18851031541"><h4 class="sectiontitle">Configuring Kibana Public Access for an Existing Cluster</h4><p id="css_01_0088__p2871748088">You can enable, disable, modify, and view Kibana public access for an existing cluster that has security mode enabled.</p>
<ol id="css_01_0088__ol179019266146"><li id="css_01_0088__li7625635121410">Log in to the <span id="css_01_0088__text1762514356145">CSS</span> management console.</li><li id="css_01_0088__li106254357143">On the <span class="wintitle" id="css_01_0088__wintitle108694343394957"><b>Clusters</b></span> page, click the name of the target cluster.</li><li id="css_01_0088__li341918231507">Click the <strong id="css_01_0088__b2415171162914">Kibana Public Access</strong> tab. Turn on the <strong id="css_01_0088__b1564719586297">Kibana Public Access</strong> switch to enable the Kibana public access function.<p id="css_01_0088__p64191523304"><span><img id="css_01_0088__image24191623101" src="en-us_image_0000001286116734.png"></span> indicates that Kibana public access is disabled. <span><img id="css_01_0088__image64198231605" src="en-us_image_0000001338836489.png"></span> indicates that Kibana public access is enabled.</p>
<ol id="css_01_0088__ol179019266146"><li id="css_01_0088__li7625635121410">Log in to the <span id="css_01_0088__text1762514356145">CSS</span> management console.</li><li id="css_01_0088__li106254357143">On the <span class="wintitle" id="css_01_0088__wintitle108694343394957"><b>Clusters</b></span> page, click the name of the target cluster.</li><li id="css_01_0088__li341918231507">Click the <strong id="css_01_0088__b2415171162914">Kibana Public Access</strong> tab. Turn on the <strong id="css_01_0088__b1564719586297">Kibana Public Access</strong> switch to enable the Kibana public access function.<p id="css_01_0088__p64191523304"><span><img id="css_01_0088__image24191623101" src="en-us_image_0000001524766281.png"></span> indicates that Kibana public access is disabled. <span><img id="css_01_0088__image64198231605" src="en-us_image_0000001474725836.png"></span> indicates that Kibana public access is enabled.</p>
</li><li id="css_01_0088__li78118230213">On the displayed page, set parameters.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0088__table145611511676" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Kibana public access parameters</caption><thead align="left"><tr id="css_01_0088__en-us_topic_0000001268394285_row13115543918"><th align="left" class="cellrowborder" valign="top" width="23.830000000000002%" id="mcps1.3.5.3.4.1.2.3.1.1"><p id="css_01_0088__en-us_topic_0000001268394285_p6115643517">Parameter</p>
</th>

17
docs/css/umn/css_01_0091.html Normal file
View File

@ -0,0 +1,17 @@
<a name="css_01_0091"></a><a name="css_01_0091"></a>
<h1 class="topictitle1">Managing Index Statuses</h1>
<div id="body0000001334459465"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_01_0093.html">Creating and Managing Indices</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0092.html">Changing Policies</a></strong><br>
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0107.html">Working with Kibana</a></div>
</div>
</div>

40
docs/css/umn/css_01_0092.html Normal file
View File

@ -0,0 +1,40 @@
<a name="css_01_0092"></a><a name="css_01_0092"></a>
<h1 class="topictitle1">Changing Policies</h1>
<div id="body0000001282659002"><p id="css_01_0092__p8060118">You can change any managed index policy. ISM has constraints to ensure that policy changes do not break indices.</p>
<p id="css_01_0092__p317933310020">If an index is stuck in its current status, never proceeding, and you want to update its policy immediately, make sure that the new policy includes the same status (same name, action, and order) as the old policy. In this case, ISM applies the new policy even if the policy is being executed.</p>
<p id="css_01_0092__p91801033106">If you update the policy without including an identical status, ISM updates the policy only after all actions in the current status finish executing. Alternatively, you can select a specific status in the old policy and have the new policy take effect.</p>
<p id="css_01_0092__p17977472381">To change a policy using Kibana, do the following:</p>
<ol id="css_01_0092__ol139071917142615"><li id="css_01_0092__li139081178269">Under <strong id="css_01_0092__b3928175511">Managed Indices</strong>, select the indices to which you want to attach the new policy.</li><li id="css_01_0092__li811711485413">Click <strong id="css_01_0092__b684434613237">Change policy</strong> in the upper right corner. The <strong id="css_01_0092__b161196186246">Choose managed indices</strong> page is displayed. Configure parameters required for changing a policy.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0092__table11166742131412" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters required for changing a policy</caption><thead align="left"><tr id="css_01_0092__row21661542181412"><th align="left" class="cellrowborder" valign="top" width="32.9%" id="mcps1.3.5.2.3.2.3.1.1"><p id="css_01_0092__p191676429141">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="67.10000000000001%" id="mcps1.3.5.2.3.2.3.1.2"><p id="css_01_0092__p10167174219141">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="css_01_0092__row61676422144"><td class="cellrowborder" valign="top" width="32.9%" headers="mcps1.3.5.2.3.2.3.1.1 "><p id="css_01_0092__p1663164571516">Managed indices</p>
</td>
<td class="cellrowborder" valign="top" width="67.10000000000001%" headers="mcps1.3.5.2.3.2.3.1.2 "><p id="css_01_0092__p016714423147">Select the indices to which you want to attach the new policy. Multiple indices can be selected.</p>
</td>
</tr>
<tr id="css_01_0092__row11670424145"><td class="cellrowborder" valign="top" width="32.9%" headers="mcps1.3.5.2.3.2.3.1.1 "><p id="css_01_0092__p171671242181412">State filters</p>
</td>
<td class="cellrowborder" valign="top" width="67.10000000000001%" headers="mcps1.3.5.2.3.2.3.1.2 "><p id="css_01_0092__p3167642151413">Select an index status. When a status is selected, the new policy is attached to an index in this status.</p>
</td>
</tr>
<tr id="css_01_0092__row1916784213145"><td class="cellrowborder" valign="top" width="32.9%" headers="mcps1.3.5.2.3.2.3.1.1 "><p id="css_01_0092__p191671842121419">New policy</p>
</td>
<td class="cellrowborder" valign="top" width="67.10000000000001%" headers="mcps1.3.5.2.3.2.3.1.2 "><p id="css_01_0092__p1416716426142">Select a new policy.</p>
</td>
</tr>
</tbody>
</table>
</div>
</li><li id="css_01_0092__li163651259194420">After configuration is complete, click <strong id="css_01_0092__b8509562124322">Change</strong>.</li></ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0091.html">Managing Index Statuses</a></div>
</div>
</div>

38
docs/css/umn/css_01_0093.html Normal file
View File

@ -0,0 +1,38 @@
<a name="css_01_0093"></a><a name="css_01_0093"></a>
<h1 class="topictitle1">Creating and Managing Indices</h1>
<div id="body0000001334739209"><p id="css_01_0093__p95505610163">Clusters of versions 7.6.2 and 7.9.3 support index status management (ISM). ISM is a plugin that allows you to automate periodic and administrative operations based on changes on the index age, index size, or number of documents. When using the ISM plug-in, you can define policies that automatically handle index rolleovers or deletions based on your needs.</p>
<div class="note" id="css_01_0093__note822313154811"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0093__p17221113124818">The following procedure uses Kibana 7.6.2 as an example. The Kibana UI varies depending on the Kibana version, but their operations are similar.</p>
</div></div>
<div class="section" id="css_01_0093__section779154094817"><h4 class="sectiontitle">Creating an Index Policy</h4><ol id="css_01_0093__ol1881418555550"><li id="css_01_0093__li18815455105512">Log in to Kibana and choose <strong id="css_01_0093__b9634124610193">IM</strong> or <strong id="css_01_0093__b38241057131913">Index Management</strong> on the left. The <strong id="css_01_0093__b072011974018">Index Management</strong> page is displayed.<div class="fignone" id="css_01_0093__fig1447493074011"><span class="figcap"><b>Figure 1 </b>Choosing IM</span><br><span><img id="css_01_0093__image1630162416013" src="en-us_image_0000001474566008.png"></span></div>
</li><li id="css_01_0093__li6804104711597">Click <strong id="css_01_0093__b1972915323208">Create policy</strong> to create an index policy.</li><li id="css_01_0093__li66234455115"><a name="css_01_0093__li66234455115"></a><a name="li66234455115"></a>Enter a policy ID in the <strong id="css_01_0093__b1925817592111">Policy ID</strong> text box and enter your policy in the <strong id="css_01_0093__b572101772117">Define policy</strong> text box.<div class="fignone" id="css_01_0093__fig11427149204015"><span class="figcap"><b>Figure 2 </b>Configuring a policy</span><br><span><img id="css_01_0093__image318610322918" src="en-us_image_0000001474246380.png"></span></div>
</li><li id="css_01_0093__li652213431799">Click <strong id="css_01_0093__b10356135519333">Create</strong>.<p id="css_01_0093__p19382202715116">After you create a policy, attach the policy to one or more indices. You can also include <strong id="css_01_0093__b5223758202316">policy_id</strong> in an index template, so when you create an index that matches the index template pattern, the policy is attached to the index.</p>
<p id="css_01_0093__p41700444314">For details about how to create an index template, see <a href="https://opendistro.github.io/for-elasticsearch-docs/docs/elasticsearch/index-templates/#create-template" target="_blank" rel="noopener noreferrer">Index Templates</a>.</p>
<pre class="screen" id="css_01_0093__screen1339616615129">PUT _template/&lt;template_name&gt;<strong id="css_01_0093__b1518219200134"> </strong>
{
"index_patterns": [
"index_name-*"
],
"settings": {
"opendistro.index_state_management.policy_id": "policy_id"
}
}</pre>
<ul id="css_01_0093__ul205914411053"><li id="css_01_0093__li859111412518"><em id="css_01_0093__i195052985813">&lt;template_name&gt;</em>: Replace it with the name of the created index template.</li><li id="css_01_0093__li158820217618"><em id="css_01_0093__i1722182117584">policy_id</em>: Replace it with the policy ID created in <a href="#css_01_0093__li66234455115">3</a>.</li></ul>
</li></ol>
</div>
<div class="section" id="css_01_0093__section11451321182815"><h4 class="sectiontitle">Attach the policy to an index.</h4><ol id="css_01_0093__ol157431012114419"><li id="css_01_0093__li147431512154414">Click <strong id="css_01_0093__b162348576256">Indices</strong>.<div class="fignone" id="css_01_0093__fig1194814714117"><span class="figcap"><b>Figure 3 </b>Choosing Indices</span><br><span><img id="css_01_0093__image8628141811453" src="en-us_image_0000001474406040.png"></span></div>
</li><li id="css_01_0093__li9472146174518">In the <strong id="css_01_0093__b12310153193010">Indices</strong> list, select the target index to which you want to attach the policy.</li><li id="css_01_0093__li177231867478">Click <strong id="css_01_0093__b4659330664225">Apply policy</strong> in the upper right corner.<div class="fignone" id="css_01_0093__fig02609262411"><span class="figcap"><b>Figure 4 </b>Adding a policy</span><br><span><img id="css_01_0093__image1225731525110" src="en-us_image_0000001524766301.png"></span></div>
</li><li id="css_01_0093__li7836174314115">Select the policy you created from the <strong id="css_01_0093__b1616122633210">Policy ID</strong> drop-down list.<div class="fignone" id="css_01_0093__fig2537324154211"><span class="figcap"><b>Figure 5 </b>Selecting a policy</span><br><span><img id="css_01_0093__image1219214421953" src="en-us_image_0000001525205869.png"></span></div>
</li><li id="css_01_0093__li943478933">Click <strong id="css_01_0093__b991611301244">Apply</strong>.<p id="css_01_0093__p648510212617">After you attach a policy to an index, ISM creates a job that runs every five minutes by default, to execute the policy, check conditions, and convert the index to different statuses.</p>
</li></ol>
</div>
<div class="section" id="css_01_0093__section87941257192"><h4 class="sectiontitle">Managing Indices</h4><ol id="css_01_0093__ol15110119124"><li id="css_01_0093__li4512211151214">Click <strong id="css_01_0093__b867302793819">Managed Indices</strong>.</li><li id="css_01_0093__li1770054817133">If you want to change the policy, click <strong id="css_01_0093__b11334114593813">Change policy</strong>. For details, see <a href="css_01_0092.html">Changing Policies</a>.</li><li id="css_01_0093__li189823731912">To delete a policy, select your policy, and click <strong id="css_01_0093__b1323102854017">Remove policy</strong>.</li><li id="css_01_0093__li78981237171911">To retry a policy, select your policy, and click <strong id="css_01_0093__b350914715419">Retry policy</strong>.</li></ol>
<p id="css_01_0093__p1509136183817">For details, see <a href="https://opendistro.github.io/for-elasticsearch-docs/docs/im/ism/" target="_blank" rel="noopener noreferrer">Index State Management</a>.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0091.html">Managing Index Statuses</a></div>
</div>
</div>

228
docs/css/umn/css_01_0094.html
View File

File diff suppressed because it is too large Load Diff

19
docs/css/umn/css_01_0107.html Normal file
View File

@ -0,0 +1,19 @@
<a name="css_01_0107"></a><a name="css_01_0107"></a>
<h1 class="topictitle1">Working with Kibana</h1>
<div id="body0000001282339402"><p id="css_01_0107__p8060118"></p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_01_0108.html">Logging In to Kibana</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0109.html">Creating a User and Granting Permissions by Using Kibana</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0091.html">Managing Index Statuses</a></strong><br>
</li>
</ul>
</div>

19
docs/css/umn/css_01_0108.html Normal file
View File

@ -0,0 +1,19 @@
<a name="css_01_0108"></a><a name="css_01_0108"></a>
<h1 class="topictitle1">Logging In to Kibana</h1>
<div id="body0000001282179490"><div class="section" id="css_01_0108__section97601154132319"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0108__p137103449255">A CSS cluster has been created.</p>
</div>
<div class="section" id="css_01_0108__section1819121316265"><h4 class="sectiontitle">Procedure</h4><ul id="css_01_0108__ul169550164571"><li id="css_01_0108__li4955416185710">Logging in to the console<ol id="css_01_0108__ol8123172192918"><li id="css_01_0108__li812320214292">Log in to the <span id="css_01_0108__text7429314121020">CSS</span> management console.</li><li id="css_01_0108__li51301404296">On the <strong id="css_01_0108__b16672558105916">Clusters</strong> page, in the row of a cluster, and click <strong id="css_01_0108__b145011421502">Access Kibana</strong> in the <strong id="css_01_0108__b1857154517018">Operation</strong> column.<div class="note" id="css_01_0108__note48512541238"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0108__p19852155414233">If the cluster has the security mode enabled, enter the username and password you for login. Generally, the username is <strong id="css_01_0108__b1852810470119">admin</strong> and the password is the one specified during cluster creation.</p>
<p id="css_01_0108__p8060118">If you forget the password, you can reset it on the cluster details page and then log in. Log in and perform operations on the Kibana page.</p>
</div></div>
</li></ol>
</li><li id="css_01_0108__li551963515714">Logging in using an EIP<p id="css_01_0108__p384714316576"><a name="css_01_0108__li551963515714"></a><a name="li551963515714"></a>If you have enabled Kibana public access during cluster creation, you can use the Kibana public IP address to log in to the cluster.</p>
</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0107.html">Working with Kibana</a></div>
</div>
</div>

37
docs/css/umn/css_01_0109.html Normal file
View File

@ -0,0 +1,37 @@
<a name="css_01_0109"></a><a name="css_01_0109"></a>
<h1 class="topictitle1">Creating a User and Granting Permissions by Using Kibana</h1>
<div id="body0000001334619321"><div class="section" id="css_01_0109__section27211243194416"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0109__p7463739987">The security mode has been enabled for the cluster.</p>
</div>
<div class="section" id="css_01_0109__section12163507442"><h4 class="sectiontitle">Procedure</h4><div class="note" id="css_01_0109__note11864519122717"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0109__p2042932512322">This section takes Kibana 7.6.2 as an example to describe the procedure.</p>
</div></div>
<ol id="css_01_0109__ol13831428473"><li id="css_01_0109__li483113274712">Log in to the CSS management console.</li><li id="css_01_0109__li201191431164715">Click <strong id="css_01_0109__b174921177179">Access Kibana</strong> in the <strong id="css_01_0109__b18835161461719">Operation</strong> column of a cluster.<div class="fignone" id="css_01_0109__fig1591311517013"><span class="figcap"><b>Figure 1 </b>Logging in to Kibana (1)</span><br><span><img id="css_01_0109__image88061840202" src="en-us_image_0000001474725864.png"></span></div>
</li><li id="css_01_0109__li1390318464482">Log in to Kibana.<div class="fignone" id="css_01_0109__fig921015524911"><span class="figcap"><b>Figure 2 </b>Logging in to Kibana (2)</span><br><span><img id="css_01_0109__image32151031135017" src="en-us_image_0000001525365849.png"></span></div>
<div class="p" id="css_01_0109__p72171755134917"><ul id="css_01_0109__ul16115366518"><li id="css_01_0109__li61163625113">Username: <strong id="css_01_0109__en-us_topic_0108417047_b84235270617014_1">admin</strong></li><li id="css_01_0109__li141117361515"><strong id="css_01_0109__b18347195820180">Password</strong>: Enter the password set during cluster creation.</li></ul>
</div>
</li><li id="css_01_0109__li19408194265113">Click the <span class="uicontrol" id="css_01_0109__uicontrol516381513180"><b>Security</b></span> icon on the Kibana operation page.<div class="fignone" id="css_01_0109__fig1523553195019"><span class="figcap"><b>Figure 3 </b>Going to the Security page</span><br><span><img id="css_01_0109__image19226155695816" src="en-us_image_0000001474406052.png"></span></div>
</li><li id="css_01_0109__li1402081945">Create a user.<ol type="a" id="css_01_0109__ol79872015420"><li id="css_01_0109__li1525633919011">Choose <span class="uicontrol" id="css_01_0109__uicontrol487317128112"><b>Authentication Backends</b></span> &gt;<span class="uicontrol" id="css_01_0109__uicontrol894610151018"><b>Internal Users Database</b></span>.<div class="fignone" id="css_01_0109__fig7556653115014"><span class="figcap"><b>Figure 4 </b>Adding a user (1)</span><br><span><img id="css_01_0109__image127854321549" src="en-us_image_0000001525365845.png"></span></div>
</li><li id="css_01_0109__li932013304416">On the <strong id="css_01_0109__b2494612152112">Internal Users Database</strong> page, choose <span><img id="css_01_0109__image1829195432614" src="en-us_image_0000001474566028.png"></span>. The page for adding user information is displayed.<div class="fignone" id="css_01_0109__fig566616365112"><span class="figcap"><b>Figure 5 </b>Adding a user (2)</span><br><span><img id="css_01_0109__image75850121657" src="en-us_image_0000001474406056.png"></span></div>
</li><li id="css_01_0109__li98518431168">On the user creation page, configure <strong id="css_01_0109__b185672012182216">Username</strong> and <strong id="css_01_0109__b893571317221">Password</strong>, and click <strong id="css_01_0109__b12627131510226">Submit</strong>.<p id="css_01_0109__p119611315206">The user will be displayed in the user list.</p>
</li></ol>
</li><li id="css_01_0109__li792019310012">Configure roles and permissions for the user.<ol type="a" id="css_01_0109__ol4219544995"><li id="css_01_0109__li17373173916916">Click <strong id="css_01_0109__b1934411117233">Roles</strong>.<div class="fignone" id="css_01_0109__fig652304645115"><span class="figcap"><b>Figure 6 </b>Adding a role</span><br><span><img id="css_01_0109__image622325681714" src="en-us_image_0000001524766313.png"></span></div>
</li><li id="css_01_0109__li2102145414179">On the <strong id="css_01_0109__b17736499238">Open Distro Security Roles</strong> page, click <span><img id="css_01_0109__image1848451232711" src="en-us_image_0000001474566028.png"></span>.<ol class="substepthirdol" id="css_01_0109__ol4402357265"><li id="css_01_0109__li12578173113267">Enter a role name on the <strong id="css_01_0109__b8606152262419">Overview</strong> page.<div class="fignone" id="css_01_0109__fig126181617527"><span class="figcap"><b>Figure 7 </b>Entering a role name</span><br><span><img id="css_01_0109__image17606343162717" src="en-us_image_0000001524766321.png"></span></div>
</li><li id="css_01_0109__li9544154162720">Configure CSS cluster permissions on the <strong id="css_01_0109__b090484472415">Cluster Permissions</strong> page. You can skip this step.</li><li id="css_01_0109__li1334947203119">Configure index permissions on the <strong id="css_01_0109__b1028010258255">Index Permissions</strong> page.<div class="p" id="css_01_0109__p3343474313"><strong id="css_01_0109__b68781410271">Index patterns</strong>: Set this parameter to the name of the index whose permission needs to be configured. For example, <strong id="css_01_0109__b1083813317271">my_store</strong>.<div class="note" id="css_01_0109__note114066412109"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0109__p174073412100">Use different names for the index and the user.</p>
</div></div>
</div>
<p id="css_01_0109__p854571394514">Configure <strong id="css_01_0109__b1134411514289">Permissions: Action Groups</strong> as required, for example, select the read-only permission <strong id="css_01_0109__b695115176289">Search</strong>.</p>
</li><li id="css_01_0109__li52028582413">Retain the default settings on the <strong id="css_01_0109__b575817367288">Tenant Permissions</strong> page.<p id="css_01_0109__p4217105281512">After the configuration is complete, the role will be displayed.</p>
</li></ol>
</li></ol>
</li><li id="css_01_0109__li113356691613">Assign a role to the user.<ol type="a" id="css_01_0109__ol1997112961612"><li id="css_01_0109__li18729627101619">Click <strong id="css_01_0109__b52401941182914">Role Mappings</strong>.<div class="fignone" id="css_01_0109__fig16883226185320"><span class="figcap"><b>Figure 8 </b>Role mapping</span><br><span><img id="css_01_0109__image142327489358" src="en-us_image_0000001474246400.png"></span></div>
</li><li id="css_01_0109__li126721159153513">Click <span><img id="css_01_0109__image1840193116275" src="en-us_image_0000001474566028.png"></span> to add the mapping between users and roles.<div class="fignone" id="css_01_0109__fig16582134110537"><span class="figcap"><b>Figure 9 </b>Users and roles</span><br><span><img id="css_01_0109__image179851630133" src="en-us_image_0000001474725872.png"></span></div>
</li><li id="css_01_0109__li9487184185112">Click <strong id="css_01_0109__b3117122311316">Submit</strong>.</li></ol>
</li><li id="css_01_0109__li38991045175">Verify that the configuration takes effect in Kibana.</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0107.html">Working with Kibana</a></div>
</div>
</div>

17
docs/css/umn/css_01_0149.html Normal file
View File

@ -0,0 +1,17 @@
<a name="css_01_0149"></a><a name="css_01_0149"></a>
<h1 class="topictitle1">Scaling In/Out a Cluster</h1>
<div id="body0000001476921486"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_01_0151.html">Scaling Out a Cluster</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0074.html">Changing Specifications</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0153.html">Scaling in a Cluster</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_01_0081.html">Removing Specified Nodes</a></strong><br>
</li>
</ul>
</div>

86
docs/css/umn/css_01_0151.html Normal file
View File

@ -0,0 +1,86 @@
<a name="css_01_0151"></a><a name="css_01_0151"></a>
<h1 class="topictitle1">Scaling Out a Cluster</h1>
<div id="body0000001527241393"><p id="css_01_0151__p18220112044212">If the workloads on the data plane of a cluster change, you can scale out the cluster by increasing the number or capacity of its nodes. Services are not interrupted during cluster scale-out.</p>
<div class="section" id="css_01_0151__section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0151__ul1977488417"><li id="css_01_0151__li157741281010">The target cluster is available and has no tasks in progress.</li><li id="css_01_0151__li13774781313">The target cluster has sufficient quotas available.</li></ul>
</div>
<div class="section" id="css_01_0151__section12477125117522"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0151__ul1549322814277"><li id="css_01_0151__li776243913339">Node specifications cannot be modified during cluster scale-out.</li><li id="css_01_0151__li2821830236">If you change the number and storage capacity of a specified type of node, nodes in other types will not be changed.</li><li id="css_01_0151__li7493162820274">The quota of nodes in different types varies. For details, see <a href="#css_01_0151__table10730243193816">Table 1</a>.
<div class="tablenoborder"><a name="css_01_0151__table10730243193816"></a><a name="table10730243193816"></a><table cellpadding="4" cellspacing="0" summary="" id="css_01_0151__table10730243193816" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Number of nodes in different types</caption><thead align="left"><tr id="css_01_0151__row1976920435387"><th align="left" class="cellrowborder" valign="top" width="50.529999999999994%" id="mcps1.3.3.2.3.2.2.3.1.1"><p id="css_01_0151__p1976954343811">Node Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="49.47%" id="mcps1.3.3.2.3.2.2.3.1.2"><p id="css_01_0151__p1276920435389">Number</p>
</th>
</tr>
</thead>
<tbody><tr id="css_01_0151__row1769164393820"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p18769184333816">ess</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p127691243123819">ess: 1-32</p>
</td>
</tr>
<tr id="css_01_0151__row177691843183816"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p776964317385">ess, ess-master</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p9769194317381">ess: 1-200</p>
<p id="css_01_0151__p1976911438384">ess-master: an odd number ranging from 3 to 9</p>
</td>
</tr>
<tr id="css_01_0151__row107691743183814"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p1769443133816">ess, ess-client</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p157691943163815">ess: 1-32</p>
<p id="css_01_0151__p1976917431383">ess-client: 1-32</p>
</td>
</tr>
<tr id="css_01_0151__row57692432388"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p18769343203813">ess, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p12769194317384">ess: 1-32</p>
<p id="css_01_0151__p1138220591537">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0151__row187701743193815"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p1477054314389">ess, ess-master, ess-client</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p2770164303816">ess: 1-200</p>
<p id="css_01_0151__p877020432386">ess-master: an odd number ranging from 3 to 9</p>
<p id="css_01_0151__p177044313389">ess-client: 1-32</p>
</td>
</tr>
<tr id="css_01_0151__row27701443143811"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p2770443173816">ess, ess-master, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p1777074316382">ess: 1-200</p>
<p id="css_01_0151__p5770124393818">ess-master: an odd number ranging from 3 to 9</p>
<p id="css_01_0151__p161801250733">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0151__row67708433382"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p777018438384">ess, ess-client, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p077074353816">ess: 1-32</p>
<p id="css_01_0151__p12770194393813">ess-client: 1-32</p>
<p id="css_01_0151__p1841425314">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0151__row7770143153811"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.3.2.2.3.1.1 "><p id="css_01_0151__p577044333818">ess, ess-master, ess-client, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.3.2.2.3.1.2 "><p id="css_01_0151__p1777017437384">ess: 1-200</p>
<p id="css_01_0151__p077034315388">ess-master: an odd number ranging from 3 to 9</p>
<p id="css_01_0151__p5770144314386">ess-client: 1-32</p>
<p id="css_01_0151__p1278719254314">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0151__row14267396512"><td class="cellrowborder" colspan="2" valign="top" headers="mcps1.3.3.2.3.2.2.3.1.1 mcps1.3.3.2.3.2.2.3.1.2 "><div class="p" id="css_01_0151__p3497523687">Details about the four node types:<ul id="css_01_0151__ul12497123683"><li id="css_01_0151__li64981323284"><strong id="css_01_0151__b1543078192814">ess</strong>: the default node type that is mandatory for cluster creation. The other three node types are optional.</li><li id="css_01_0151__li6498112311818"><strong id="css_01_0151__b14242174542716">ess-master</strong>: master node</li><li id="css_01_0151__li114982231584"><strong id="css_01_0151__b051753122720">ess-client</strong>: client node</li><li id="css_01_0151__li64984238813"><strong id="css_01_0151__b151201057162715">ess-cold</strong>: cold data node</li></ul>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</li></ul>
</div>
<div class="section" id="css_01_0151__section88251810174819"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0151__ol282541054817"><li id="css_01_0151__li1173513611411">Log in to the CSS management console.</li><li id="css_01_0151__li17735636141417">In the navigation pane on the left, choose <strong id="css_01_0151__b468415893218">Clusters</strong>. On the displayed <strong id="css_01_0151__b17863162743213">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0151__b6658165419328">More</strong> &gt; <span class="uicontrol" id="css_01_0151__uicontrol666505023119"><b>Scale Cluster</b></span> in the <strong id="css_01_0151__b2129936123313">Operation</strong> column.</li><li id="css_01_0151__li13735736141416">On the <strong id="css_01_0151__b3319153162310">Modify Configuration</strong> page, set scale-out parameters.<ul id="css_01_0151__ul02151151205413"><li id="css_01_0151__li22151851165410"><span class="parmname" id="css_01_0151__parmname72931116554"><b>New Nodes</b></span>: The number of default nodes. For details about the quota, see <a href="#css_01_0151__table10730243193816">Table 1</a>.</li><li id="css_01_0151__li10215165155417"><span class="parmname" id="css_01_0151__parmname112574145512"><b>Node Storage Capacity</b></span>: The storage capacity of the default nodes. The quota is determined by the <strong id="css_01_0151__b156751340201412">New Node Specifications</strong>. The value must be a multiple of 20.</li></ul>
<div class="note" id="css_01_0151__note12801383526"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0151__p78018805211">If a cluster has master, client, or cold data nodes, you can change the number of these nodes and expand the storage capacity of cold data nodes. For details about the quotas of the master, client, and cold data node, see <a href="#css_01_0151__table10730243193816">Table 1</a>.</p>
</div></div>
</li><li id="css_01_0151__li196007301612">Click <span class="uicontrol" id="css_01_0151__uicontrol19980126142514"><b>Next</b></span>.</li><li id="css_01_0151__li13737436141418">Confirm the information and click <strong id="css_01_0151__b650894219561">Submit</strong>.</li><li id="css_01_0151__li18826191011484">Click <span class="uicontrol" id="css_01_0151__uicontrol116381731145616"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0151__b06381431145612">Clusters</strong> page. The <span class="parmname" id="css_01_0151__parmname69181756145512"><b>Task Status</b></span> is <span class="parmvalue" id="css_01_0151__parmvalue57378369140"><b>Scaling out</b></span>. When <span class="parmname" id="css_01_0151__parmname1986518302534"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="css_01_0151__parmvalue1086511305538"><b>Available</b></span>, the cluster has been successfully scaled out.</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0149.html">Scaling In/Out a Cluster</a></div>
</div>
</div>

84
docs/css/umn/css_01_0153.html Normal file
View File

@ -0,0 +1,84 @@
<a name="css_01_0153"></a><a name="css_01_0153"></a>
<h1 class="topictitle1">Scaling in a Cluster</h1>
<div id="body0000001527641717"><p id="css_01_0153__p18220112044212">If a cluster can process existing data without fully using its resources, you can scale in the cluster to reduce costs. Services are not interrupted during cluster scale-in.</p>
<div class="section" id="css_01_0153__section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0153__p388384925216">The target cluster is available and has no tasks in progress.</p>
</div>
<div class="section" id="css_01_0153__section12477125117522"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0153__ul1549322814277"><li id="css_01_0153__li744816402511">The node specifications and storage capacity cannot be modified during scale-in.</li><li id="css_01_0153__li2821830236">If you change the number and storage capacity of a specified type of node, nodes in other types will not be changed.</li><li id="css_01_0153__li108232692012">Ensure that the disk usage after scale-in is less than 80% and each AZ of each node type has at least one node.</li><li id="css_01_0153__li194371964368">When scaling in a cluster, the data in the node to be deleted is migrated to other nodes. The timeout threshold for data migration is five hours. If data migration is not complete within 5 hours, the cluster scale-in fails. You are advised to perform scale-in for multiple times when the cluster has huge amounts of data.</li><li id="css_01_0153__li18828244182018">For a cluster without master nodes, the number of remaining data nodes (including cold data nodes and other types of nodes) after scale-in must be greater than half of the original node number, and greater than the maximum number of index replicas.</li><li id="css_01_0153__li7493162820274">The quota of nodes in different types varies. For details, see <a href="#css_01_0153__table10730243193816">Table 1</a>.
<div class="tablenoborder"><a name="css_01_0153__table10730243193816"></a><a name="table10730243193816"></a><table cellpadding="4" cellspacing="0" summary="" id="css_01_0153__table10730243193816" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Number of nodes in different types</caption><thead align="left"><tr id="css_01_0153__en-us_topic_0000001285669680_row1976920435387"><th align="left" class="cellrowborder" valign="top" width="50.529999999999994%" id="mcps1.3.3.2.6.2.2.3.1.1"><p id="css_01_0153__en-us_topic_0000001285669680_p1976954343811">Node Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="49.47%" id="mcps1.3.3.2.6.2.2.3.1.2"><p id="css_01_0153__en-us_topic_0000001285669680_p1276920435389">Number</p>
</th>
</tr>
</thead>
<tbody><tr id="css_01_0153__en-us_topic_0000001285669680_row1769164393820"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p18769184333816">ess</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p127691243123819">ess: 1-32</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row177691843183816"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p776964317385">ess, ess-master</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p9769194317381">ess: 1-200</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p1976911438384">ess-master: an odd number ranging from 3 to 9</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row107691743183814"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p1769443133816">ess, ess-client</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p157691943163815">ess: 1-32</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p1976917431383">ess-client: 1-32</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row57692432388"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p18769343203813">ess, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p12769194317384">ess: 1-32</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p1138220591537">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row187701743193815"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p1477054314389">ess, ess-master, ess-client</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p2770164303816">ess: 1-200</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p877020432386">ess-master: an odd number ranging from 3 to 9</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p177044313389">ess-client: 1-32</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row27701443143811"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p2770443173816">ess, ess-master, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p1777074316382">ess: 1-200</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p5770124393818">ess-master: an odd number ranging from 3 to 9</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p161801250733">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row67708433382"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p777018438384">ess, ess-client, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p077074353816">ess: 1-32</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p12770194393813">ess-client: 1-32</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p1841425314">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row7770143153811"><td class="cellrowborder" valign="top" width="50.529999999999994%" headers="mcps1.3.3.2.6.2.2.3.1.1 "><p id="css_01_0153__en-us_topic_0000001285669680_p577044333818">ess, ess-master, ess-client, ess-cold</p>
</td>
<td class="cellrowborder" valign="top" width="49.47%" headers="mcps1.3.3.2.6.2.2.3.1.2 "><p id="css_01_0153__en-us_topic_0000001285669680_p1777017437384">ess: 1-200</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p077034315388">ess-master: an odd number ranging from 3 to 9</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p5770144314386">ess-client: 1-32</p>
<p id="css_01_0153__en-us_topic_0000001285669680_p1278719254314">ess-cold: 1-32</p>
</td>
</tr>
<tr id="css_01_0153__en-us_topic_0000001285669680_row14267396512"><td class="cellrowborder" colspan="2" valign="top" headers="mcps1.3.3.2.6.2.2.3.1.1 mcps1.3.3.2.6.2.2.3.1.2 "><div class="p" id="css_01_0153__en-us_topic_0000001285669680_p3497523687">Details about the four node types:<ul id="css_01_0153__en-us_topic_0000001285669680_ul12497123683"><li id="css_01_0153__en-us_topic_0000001285669680_li64981323284"><strong id="css_01_0153__en-us_topic_0000001285669680_b1543078192814">ess</strong>: the default node type that is mandatory for cluster creation. The other three node types are optional.</li><li id="css_01_0153__en-us_topic_0000001285669680_li6498112311818"><strong id="css_01_0153__en-us_topic_0000001285669680_b14242174542716">ess-master</strong>: master node</li><li id="css_01_0153__en-us_topic_0000001285669680_li114982231584"><strong id="css_01_0153__en-us_topic_0000001285669680_b051753122720">ess-client</strong>: client node</li><li id="css_01_0153__en-us_topic_0000001285669680_li64984238813"><strong id="css_01_0153__en-us_topic_0000001285669680_b151201057162715">ess-cold</strong>: cold data node</li></ul>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</li></ul>
</div>
<div class="section" id="css_01_0153__section1177713055318"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0153__ol373518361145"><li id="css_01_0153__li1173513611411">Log in to the CSS management console.</li><li id="css_01_0153__li17735636141417">In the navigation pane on the left, choose <strong id="css_01_0153__b195621759184010">Clusters</strong>. On the displayed <strong id="css_01_0153__b185631859154013">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0153__b05638593409">More</strong> &gt; <span class="uicontrol" id="css_01_0153__uicontrol1756495916402"><b>Scale Cluster</b></span> in the <strong id="css_01_0153__b10564205917403">Operation</strong> column.</li><li id="css_01_0153__li13735736141416">On the <strong id="css_01_0153__b11321024153317">Modify Configuration</strong> page, set scale-in parameters.<ul id="css_01_0153__ul02151151205413"><li id="css_01_0153__li22151851165410"><span class="parmname" id="css_01_0153__parmname72931116554"><b>New Nodes</b></span>: The number of default nodes. For details about the quota, see <a href="#css_01_0153__table10730243193816">Table 1</a>.</li><li id="css_01_0153__li3856947564">If a cluster has master nodes, client nodes, or cold data nodes, you can change the node number. For details about the quotas of the master, client, and cold data node, see <a href="#css_01_0153__table10730243193816">Table 1</a>.</li></ul>
</li><li id="css_01_0153__li173623641418">Click <strong id="css_01_0153__b54423243124">Next</strong>.</li><li id="css_01_0153__li13737436141418">Confirm the information and click <strong id="css_01_0153__b17057534894732">Submit</strong>.</li><li id="css_01_0153__li11772194412145">Click <span class="uicontrol" id="css_01_0153__uicontrol26178789894732"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0153__b137271613994732">Clusters</strong> page. The <span class="parmname" id="css_01_0153__parmname76355443715"><b>Task Status</b></span> is <span class="parmvalue" id="css_01_0153__parmvalue269155419375"><b>Scaling in</b></span>. When <span class="parmname" id="css_01_0153__parmname31911726162420"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="css_01_0153__parmvalue121972262247"><b>Available</b></span>, the cluster has been successfully scaled in.</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0149.html">Scaling In/Out a Cluster</a></div>
</div>
</div>

80
docs/css/umn/css_01_0155.html Normal file
View File

@ -0,0 +1,80 @@
<a name="css_01_0155"></a><a name="css_01_0155"></a>
<h1 class="topictitle1">Configuring Cluster Monitoring</h1>
<div id="body0000001282659026"><p id="css_01_0155__p978417177594">You can use Cloud Eye to monitor the created clusters. After configuring the cluster monitoring, you can log in to the Cloud Eye management console to view cluster metrics.</p>
<p id="css_01_0155__p1049333316218">The procedure for configuring cluster monitoring:</p>
<ol id="css_01_0155__ol18531155235311"><li id="css_01_0155__li85311952105311"><a href="#css_01_0155__section15621114112420">Creating Alarm Rules</a>: Customize alarm rules for the monitoring metrics. Once a metric exceeds the threshold, the system will notify you by sending emails or HTTP/HTTPS requests.</li><li id="css_01_0155__li25311252185310"><a href="#css_01_0155__section1136460963">Configuring Monitoring Metrics</a>: Configure monitoring metrics for a cluster or a node in the cluster.</li><li id="css_01_0155__li953165275310"><a href="#css_01_0155__section322123712611">Viewing Monitoring Metrics</a>: View the statistics of the monitoring metrics in specific periods.</li></ol>
<div class="section" id="css_01_0155__section1839919421279"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0155__ul53371598273"><li id="css_01_0155__li167406482618">The cluster is in the <strong id="css_01_0155__b396114042119">Available</strong> or <strong id="css_01_0155__b13564184213213">Processing</strong> status.</li><li id="css_01_0155__li168813194715">The cluster has been running properly for more than 10 minutes.</li></ul>
</div>
<div class="section" id="css_01_0155__section93561128195816"><h4 class="sectiontitle">Recommended Monitoring Metrics</h4><ul id="css_01_0155__ul95103285119"><li id="css_01_0155__li13510152841118">Cluster CPU and JVM usage. You are advised to configure the following monitoring metrics: average JVM heap usage, maximum JVM heap usage, average CPU usage, and maximum CPU usage.</li><li id="css_01_0155__li1451042821116">Cluster write and query latency and throughput. You are advised to configure the following monitoring metrics: average index latency, average index rate, average search latency, and average QPS.</li><li id="css_01_0155__li1551022861115">Cluster write and query queue and rejected tasks. You are advised to configure the following monitoring metrics: tasks in write queue, tasks in search queue, rejected tasks in write queue, and rejected tasks in search queue.</li></ul>
</div>
<div class="section" id="css_01_0155__section15621114112420"><a name="css_01_0155__section15621114112420"></a><a name="section15621114112420"></a><h4 class="sectiontitle">Creating Alarm Rules</h4><ol id="css_01_0155__ol373518361145"><li id="css_01_0155__li1173513611411">Log in to the Cloud Eye console.</li><li id="css_01_0155__li17735636141417">In the navigation pane on the left, choose <strong id="css_01_0155__b202086538232">Alarm Management</strong> &gt; <strong id="css_01_0155__b15264558162320">Alarm Rules</strong>.</li><li id="css_01_0155__li12905188145814">In the <strong id="css_01_0155__b611484582519">Resource Type</strong> column, select <strong id="css_01_0155__b1616491269">Cloud Search Service</strong> as criteria to search for alarm rules that meet the requirements.<p id="css_01_0155__p3293151085811">If no alarm rules are available, create one by referring to <em id="css_01_0155__i2315647102917">Creating an Alarm Rule and Notification</em>. For details about how to set <strong id="css_01_0155__b9229203810300">Resource Type</strong> and <strong id="css_01_0155__b156281742193019">Dimension</strong>, see <a href="#css_01_0155__table15676621164617">Table 1</a>.</p>
<div class="tablenoborder"><a name="css_01_0155__table15676621164617"></a><a name="table15676621164617"></a><table cellpadding="4" cellspacing="0" summary="" id="css_01_0155__table15676621164617" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Alarm rule configuration parameter</caption><thead align="left"><tr id="css_01_0155__row867782112464"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.6.2.3.4.2.4.1.1"><p id="css_01_0155__p1167742194617">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.6.2.3.4.2.4.1.2"><p id="css_01_0155__p367712213469">Description</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="60%" id="mcps1.3.6.2.3.4.2.4.1.3"><p id="css_01_0155__p36771121194612">Remark</p>
</th>
</tr>
</thead>
<tbody><tr id="css_01_0155__row567711212464"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.6.2.3.4.2.4.1.1 "><p id="css_01_0155__p467719215465">Resource Type</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.6.2.3.4.2.4.1.2 "><p id="css_01_0155__p1967722111460">Type of the resource that the alarm rule is created for</p>
</td>
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.6.2.3.4.2.4.1.3 "><p id="css_01_0155__p1369144575118">Select <strong id="css_01_0155__b14411124143310">Cloud Search Service</strong>.</p>
</td>
</tr>
<tr id="css_01_0155__row867762174614"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.6.2.3.4.2.4.1.1 "><p id="css_01_0155__p2067710212463">Dimension</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.6.2.3.4.2.4.1.2 "><p id="css_01_0155__p1944145814492">Metric dimension of the selected resource type</p>
</td>
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.6.2.3.4.2.4.1.3 "><p id="css_01_0155__p145197534519">CSS supports two dimensions. Select a dimension as required.</p>
<ul id="css_01_0155__ul651916538517"><li id="css_01_0155__li1151915305115"><strong id="css_01_0155__b142929414347">CSS Clusters</strong>: Alarm rules are specified by cluster.</li><li id="css_01_0155__li1851975325114"><strong id="css_01_0155__b10738810193420">CSS Clusters - CSS Instances</strong>: Alarm rules are specified by node in a cluster.</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
</li></ol>
</div>
<div class="section" id="css_01_0155__section1136460963"><a name="css_01_0155__section1136460963"></a><a name="section1136460963"></a><h4 class="sectiontitle">Configuring Monitoring Metrics</h4><ol id="css_01_0155__ol101061030154514"><li id="css_01_0155__li181062306458">Create a monitoring panel. For details, see <em id="css_01_0155__i4884731133515">Creating a Monitoring Panel</em>. If an available monitoring panel has been created, skip this step.</li><li id="css_01_0155__li97271346171712">Add CSS monitoring graphs. For details, see <em id="css_01_0155__i26148216373">Adding a Graph</em>.<p id="css_01_0155__p8410193819194">For details about how to set <strong id="css_01_0155__b1678010491374">Resource Type</strong> and <strong id="css_01_0155__b0780114973710">Dimension</strong>, see <a href="#css_01_0155__table10410173801911">Table 2</a>.</p>
<div class="tablenoborder"><a name="css_01_0155__table10410173801911"></a><a name="table10410173801911"></a><table cellpadding="4" cellspacing="0" summary="" id="css_01_0155__table10410173801911" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Graph configuration parameter</caption><thead align="left"><tr id="css_01_0155__row241043841914"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.7.2.2.3.2.4.1.1"><p id="css_01_0155__p94109385190">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.7.2.2.3.2.4.1.2"><p id="css_01_0155__p13410153891917">Description</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="60%" id="mcps1.3.7.2.2.3.2.4.1.3"><p id="css_01_0155__p104104382193">Remark</p>
</th>
</tr>
</thead>
<tbody><tr id="css_01_0155__row18410123841917"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.7.2.2.3.2.4.1.1 "><p id="css_01_0155__p11410113811196">Resource Type</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.7.2.2.3.2.4.1.2 "><p id="css_01_0155__p1041016385191">Type of the resource to be monitored</p>
</td>
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.7.2.2.3.2.4.1.3 "><p id="css_01_0155__p6410123819194">Select <strong id="css_01_0155__b162211958143819">Cloud Search Service</strong>.</p>
</td>
</tr>
<tr id="css_01_0155__row1441033819196"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.7.2.2.3.2.4.1.1 "><p id="css_01_0155__p44113382190">Dimension</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.7.2.2.3.2.4.1.2 "><p id="css_01_0155__p1541123816193">Metric dimension</p>
</td>
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.7.2.2.3.2.4.1.3 "><p id="css_01_0155__p1341111382193">CSS supports two dimensions. Select a dimension as required.</p>
<ul id="css_01_0155__ul3411183817193"><li id="css_01_0155__li64114381195"><strong id="css_01_0155__b15120126193916">CSS Clusters</strong>: Monitoring is executed by cluster.</li><li id="css_01_0155__li16411183817198"><strong id="css_01_0155__b142662312390">CSS Clusters - CSS Instances</strong>: Monitoring is executed by node in a cluster.</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
</li></ol>
</div>
<div class="section" id="css_01_0155__section322123712611"><a name="css_01_0155__section322123712611"></a><a name="section322123712611"></a><h4 class="sectiontitle">Viewing Monitoring Metrics</h4><ol id="css_01_0155__ol19658192094114"><li id="css_01_0155__li0658320174111">Log in to the CSS management console.</li><li id="css_01_0155__li8290135311119">Choose <strong id="css_01_0155__b6311622104011">Clusters</strong>. Locate the target cluster and choose <strong id="css_01_0155__b13217228401">More</strong> &gt; <strong id="css_01_0155__b1932202244014">View Metric</strong> in the <strong id="css_01_0155__b831132218404">Operation</strong> column.</li><li id="css_01_0155__li16658620174114">Select a time range.</li><li id="css_01_0155__li465815208416">View the monitoring metrics.</li></ol>
</div>
<p id="css_01_0155__p17616411315"></p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0041.html">Monitoring a Cluster</a></div>
</div>
</div>

164
docs/css/umn/css_01_0185.html Normal file
View File

File diff suppressed because it is too large Load Diff

17
docs/css/umn/css_01_0190.html Normal file
View File

@ -0,0 +1,17 @@
<a name="css_01_0190"></a><a name="css_01_0190"></a>
<h1 class="topictitle1">Accessing an Elasticsearch Cluster</h1>
<div id="body0000001527533317"><p id="css_01_0190__p14218749144719">Elasticsearch clusters have built-in Kibana and Cerebro components. You can quickly access an Elasticsearch cluster through Kibana and Cerebro.</p>
<div class="section" id="css_01_0190__section3544291266"><h4 class="sectiontitle">Access a Cluster Through Kibana</h4><ol id="css_01_0190__ol19122182891618"><li id="css_01_0190__li17122102801616">Log in to the <span id="css_01_0190__text151611229181220">CSS</span> management console.</li><li id="css_01_0190__li112262815169">On the <span class="uicontrol" id="css_01_0190__uicontrol51229281162"><b>Clusters</b></span> page, locate the target cluster and click <span class="parmvalue" id="css_01_0190__parmvalue4122102817161"><b>Access Kibana</b></span> in the <span class="uicontrol" id="css_01_0190__uicontrol14122328131613"><b>Operation</b></span> column to go to the Kibana login page.<ul id="css_01_0190__ul20122192891614"><li id="css_01_0190__li412212815169">Non-security cluster: The Kibana console is displayed.</li><li id="css_01_0190__li612219289162">Security cluster: Enter the username and password on the login page and click <span class="uicontrol" id="css_01_0190__uicontrol01221228121616"><b>Log In</b></span> to go to the Kibana console. The default username is <strong id="css_01_0190__b58112074224321">admin</strong> and the password is the one specified during cluster creation.</li></ul>
</li><li id="css_01_0190__li1812242815165">After the login is successful, you can access the Elasticsearch cluster through Kibana.</li></ol>
</div>
<div class="section" id="css_01_0190__section138869481791"><h4 class="sectiontitle">Accessing a Cluster Through Cerebro</h4><ol id="css_01_0190__ol8123172192918"><li id="css_01_0190__li196551933142913">Log in to the <span id="css_01_0190__text382883771820">CSS</span> management console.</li><li id="css_01_0190__li7655153392911">On the <span class="uicontrol" id="css_01_0190__uicontrol2655733162910"><b>Clusters</b></span> page, locate the target cluster and click <strong id="css_01_0190__b820219462171">More</strong> &gt; <strong id="css_01_0190__b07204415178">Cerebro</strong> in the <span class="uicontrol" id="css_01_0190__uicontrol18655533122910"><b>Operation</b></span> column to go to the Cerebro login page.<ul id="css_01_0190__ul75232028195712"><li id="css_01_0190__li20523122816570">Non-security cluster: Click the cluster name on the Cerebro login page to go to the Cerebro console.</li><li id="css_01_0190__li134787055820">Security cluster: Click the cluster name on the Cerebro login page, enter the username and password, and click <span class="uicontrol" id="css_01_0190__uicontrol15959165212110"><b>Authenticate</b></span> to go to the Cerebro console. The default username is <strong id="css_01_0190__b39827080224321">admin</strong> and the password is the one specified during cluster creation.</li></ul>
</li><li id="css_01_0190__li0655183310296">After the login is successful, you can access the Elasticsearch cluster through Cerebro.</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0008.html">Creating and Accessing a Cluster</a></div>
</div>
</div>

32
docs/css/umn/css_02_0001.html
View File

@ -1,38 +1,24 @@
<a name="css_02_0001"></a><a name="css_02_0001"></a>
<h1 class="topictitle1">FAQs</h1>
<div id="body1503460464688"></div>
<div id="body0000001477005082"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="css_02_0034.html">What Are Regions and AZs?</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0051_0.html">General Consulting</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0006.html">How Does CSS Ensure Data and Service Security?</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0055.html">Functions</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0007.html">Which CSS Metrics Should I Focus On?</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0063.html">Clusters in Security Mode</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0008.html">What Storage Options Does CSS Provide?</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0066.html">Resource Usage and Change</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0009.html">What Is the Maximum Storage Capacity of CSS?</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0070.html">Components</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0010.html">What Can the Disk Space of a CSS Cluster Be Used For?</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0073.html">Kibana</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0017.html">How Can I Manage CSS?</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0077.html">Clusters</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0020.html">Which Elasticsearch Versions Does CSS Support?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0023.html">Can CSS Interconnect with Logstash?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0025.html">Why Does My ECS Fail to Connect to a Cluster?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0027.html">Which Search Functions Does CSS Support?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0028.html">Why Does Cluster Creation Fail?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0029.html">Why Does Index Backup Fail?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0018.html">How Can I Improve Filebeat Performance?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="css_02_0019.html">Failed to Open Kibana</a></strong><br>
<li class="ulchildlink"><strong><a href="css_02_0082.html">Ports</a></strong><br>
</li>
</ul>
</div>

17
docs/css/umn/css_02_0006_0.html Normal file
View File

@ -0,0 +1,17 @@
<a name="css_02_0006_0"></a><a name="css_02_0006_0"></a>
<h1 class="topictitle1">How Does <span id="en-us_topic_0076852832_text1724143149145256">CSS</span> Ensure Data and Service Security?</h1>
<div id="body8662426"><p id="css_02_0006_0__en-us_topic_0076852832_p25071515153118">CSS uses network isolation, in addition to various host and data security measures.</p>
<ul id="css_02_0006_0__en-us_topic_0076852832_ul1892414323310"><li id="css_02_0006_0__en-us_topic_0076852832_li8924163263111">Network isolation<p id="css_02_0006_0__en-us_topic_0076852832_p4650609320"><a name="css_02_0006_0__en-us_topic_0076852832_li8924163263111"></a><a name="en-us_topic_0076852832_li8924163263111"></a>The entire network is divided into two planes: service plane and management plane. The two planes are deployed and isolated physically to ensure the security of the service and management networks.</p>
<ul id="css_02_0006_0__en-us_topic_0076852832_ul06574073313"><li id="css_02_0006_0__en-us_topic_0076852832_li1515616590327">Service plane: This is the network plane of the cluster. It provides service channels for users and delivers data definitions, indexing, and search capabilities. </li><li id="css_02_0006_0__en-us_topic_0076852832_li6182175917322">Management plane: This is the management console, where you manage <span id="css_02_0006_0__en-us_topic_0076852832_text17947472920">CSS</span>.</li></ul>
</li><li id="css_02_0006_0__en-us_topic_0076852832_li137646345314">Host security<p id="css_02_0006_0__en-us_topic_0076852832_p143720134517"><a name="css_02_0006_0__en-us_topic_0076852832_li137646345314"></a><a name="en-us_topic_0076852832_li137646345314"></a><span id="css_02_0006_0__en-us_topic_0076852832_text14734145515910">CSS</span> provides the following security measures:</p>
<ul id="css_02_0006_0__en-us_topic_0076852832_ul17390102914514"><li id="css_02_0006_0__en-us_topic_0076852832_li13901298458">The VPC security group ensures the security of the hosts in a VPC.</li><li id="css_02_0006_0__en-us_topic_0076852832_li4390102918458">Network access control lists (ACLs) allow you to control what data can enter or exit your network.</li><li id="css_02_0006_0__en-us_topic_0076852832_li1839012916458">The internal security infrastructure (including the network firewall, intrusion detection system, and protection system) monitors all network traffic that enters or exits the VPC through an IPsec VPN.</li></ul>
</li><li id="css_02_0006_0__en-us_topic_0076852832_li55738695818">Data security<p id="css_02_0006_0__en-us_topic_0076852832_p1532919171598"><a name="css_02_0006_0__en-us_topic_0076852832_li55738695818"></a><a name="en-us_topic_0076852832_li55738695818"></a>Multiple replicas, cross-AZ deployment of clusters, and third-party (OBS) backup of index data ensure the security of user data.</p>
</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0051_0.html">General Consulting</a></div>
</div>
</div>

15
docs/css/umn/css_02_0007_0.html Normal file
View File

@ -0,0 +1,15 @@
<a name="css_02_0007_0"></a><a name="css_02_0007_0"></a>
<h1 class="topictitle1">Which <span id="en-us_topic_0076852833_text1198699159145457">CSS</span> Metrics Should I Focus On?</h1>
<div id="body8662426"><p id="css_02_0007_0__en-us_topic_0076852833_p318918598270">Disk usage and cluster health status are two key metrics that you can focus on. You can log in to Cloud Eye and configure alarm rules for these metrics. If alarms are reported, handle them by taking appropriate measures. </p>
<p id="css_02_0007_0__en-us_topic_0076852833_p17539173719574"><strong id="css_02_0007_0__en-us_topic_0076852833_b1399253714584">Configuration examples:</strong></p>
<ul id="css_02_0007_0__en-us_topic_0076852833_ul0852462013"><li id="css_02_0007_0__en-us_topic_0076852833_li168521361704">Alarms are reported if the disk usage is higher than or equal to a specified value (for example, 85%) and has reached this value multiple times (for example, 5 times) within a specified time period (for example, 5 minutes).</li><li id="css_02_0007_0__en-us_topic_0076852833_li1827414131209">Alarms are reported if the value of the cluster health status metric exceeds 0 for multiple times (for example, 5 times) within a specified time period (for example, 5 minutes).</li></ul>
<p id="css_02_0007_0__en-us_topic_0076852833_p123861320183212"><strong id="css_02_0007_0__en-us_topic_0076852833_b84235270610289">Measures:</strong></p>
<ul id="css_02_0007_0__en-us_topic_0076852833_ul9117152219018"><li id="css_02_0007_0__en-us_topic_0076852833_li15117142216013">If disk usage alarms are reported, view available disk space, check whether data can be deleted from cluster nodes or archived to other systems to free up space, or check if you can expand the disk capacity.</li><li id="css_02_0007_0__en-us_topic_0076852833_li228621275519">If cluster health status alarms are reported, check whether shard allocation is normal, whether shards have been lost, and check whether the process has been restarted on Cerebro.</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0051_0.html">General Consulting</a></div>
</div>
</div>

12
docs/css/umn/css_02_0008_0.html Normal file
View File

@ -0,0 +1,12 @@
<a name="css_02_0008_0"></a><a name="css_02_0008_0"></a>
<h1 class="topictitle1">What Storage Options Does <span id="en-us_topic_0076828131_text887253839145630">CSS</span> Provide?</h1>
<div id="body8662426"><p id="css_02_0008_0__en-us_topic_0076828131_p46058374172"><span id="css_02_0008_0__en-us_topic_0076828131_text323513111100">CSS</span> uses EVS and local disks to store your indices. During cluster creation, you can specify the EVS disk type and specifications (the EVS disk size).</p>
<ul id="css_02_0008_0__en-us_topic_0076828131_ul205641122141814"><li id="css_02_0008_0__en-us_topic_0076828131_li1956415223184">Supported EVS disk types include common I/O, high I/O, and ultra-high I/O.</li><li id="css_02_0008_0__en-us_topic_0076828131_li938912592116">The EVS disk size varies depending on the node specifications selected when you create a cluster.</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0051_0.html">General Consulting</a></div>
</div>
</div>

11
docs/css/umn/css_02_0009_0.html Normal file
View File

@ -0,0 +1,11 @@
<a name="css_02_0009_0"></a><a name="css_02_0009_0"></a>
<h1 class="topictitle1">What Is the Maximum Storage Capacity of CSS?</h1>
<div id="body8662426"><p id="css_02_0009_0__en-us_topic_0076789800_p1086131310252">You can configure up to 200 nodes for a cluster (each node corresponds to an ECS). The maximum storage capacity of an ECS is the total capacity of EVS disks attached to the ECS. You can calculate the total storage capacity of CSS based on the sizes of EVS disks attached to different ECSs. The EVS disk size is determined by the node specifications selected when you create the cluster.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0051_0.html">General Consulting</a></div>
</div>
</div>

12
docs/css/umn/css_02_0010_0.html Normal file
View File

@ -0,0 +1,12 @@
<a name="css_02_0010_0"></a><a name="css_02_0010_0"></a>
<h1 class="topictitle1">What Can the Disk Space of a CSS Cluster Be Used For?</h1>
<div id="body8662426"><p id="css_02_0010_0__en-us_topic_0076834511_p16592039133812">You can store the following logs and files:</p>
<ul id="css_02_0010_0__en-us_topic_0076834511_ul24263067112650"><li id="css_02_0010_0__en-us_topic_0076834511_li43185740112650">Log files: Elasticsearch logs</li><li id="css_02_0010_0__en-us_topic_0076834511_li27648471112652">Data files: Elasticsearch index files</li><li id="css_02_0010_0__en-us_topic_0076834511_li6126736211273">Other files: cluster configuration files</li><li id="css_02_0010_0__en-us_topic_0076834511_li1822837411278">OS: 5% storage space reserved for the OS by default</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0051_0.html">General Consulting</a></div>
</div>
</div>

17
docs/css/umn/css_02_0017_0.html Normal file
View File

@ -0,0 +1,17 @@
<a name="css_02_0017_0"></a><a name="css_02_0017_0"></a>
<h1 class="topictitle1">How Can I Manage CSS?</h1>
<div id="body8662426"><div class="p" id="css_02_0017_0__en-us_topic_0076841222_p1674154701514">You can use any of the following three methods to manage CSS or to use search engine APIs. You can initiate requests based on constructed request messages.<ul id="css_02_0017_0__en-us_topic_0076841222_ul712872915166"><li id="css_02_0017_0__en-us_topic_0076841222_li9127122921617">curl<p id="css_02_0017_0__en-us_topic_0076841222_p187062119200"><a name="css_02_0017_0__en-us_topic_0076841222_li9127122921617"></a><a name="en-us_topic_0076841222_li9127122921617"></a>curl is a command-line tool used to transfer data to or from a given URL. It serves as an HTTP client that can send HTTP requests to the HTTP server and receive response messages. You can also use curl to debug APIs. For more information about curl, visit <a href="https://curl.haxx.se/" target="_blank" rel="noopener noreferrer">https://curl.haxx.se/</a>.</p>
</li><li id="css_02_0017_0__en-us_topic_0076841222_li11271429201615">Code<p id="css_02_0017_0__en-us_topic_0076841222_p13440131314225"><a name="css_02_0017_0__en-us_topic_0076841222_li11271429201615"></a><a name="en-us_topic_0076841222_li11271429201615"></a>You can call APIs through code to assemble, send, and process request messages.</p>
</li><li id="css_02_0017_0__en-us_topic_0076841222_li212802911614">REST client<p id="css_02_0017_0__en-us_topic_0076841222_p1896019217223"><a name="css_02_0017_0__en-us_topic_0076841222_li212802911614"></a><a name="en-us_topic_0076841222_li212802911614"></a>Both Mozilla Firefox and Google Chrome provide a graphical browser plugin, the REST client, which you can use to send and process requests.</p>
<p id="css_02_0017_0__en-us_topic_0076841222_p274164715152">– For Mozilla Firefox, see <a href="https://addons.mozilla.org/en-US/firefox/addon/restclient/" target="_blank" rel="noopener noreferrer">Firefox REST Client</a>.</p>
<p id="css_02_0017_0__en-us_topic_0076841222_p10597432122217">– For Google Chrome, see <a href="https://www.getpostman.com/" target="_blank" rel="noopener noreferrer">Postman</a>.</p>
</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0051_0.html">General Consulting</a></div>
</div>
</div>

20
docs/css/umn/css_02_0025_0.html Normal file
View File

@ -0,0 +1,20 @@
<a name="css_02_0025_0"></a><a name="css_02_0025_0"></a>
<h1 class="topictitle1">Why Does My ECS Fail to Connect to a Cluster?</h1>
<div id="body8662426"><p id="css_02_0025_0__en-us_topic_0076847546_p202759561556">Perform the following steps to troubleshoot this problem:</p>
<ol id="css_02_0025_0__en-us_topic_0076847546_ol157021444182611"><li id="css_02_0025_0__en-us_topic_0076847546_li0702114414263">Check whether the ECS instance and cluster are in the same VPC.<ul id="css_02_0025_0__en-us_topic_0076847546_ul137021644182615"><li id="css_02_0025_0__en-us_topic_0076847546_li1570234472614">If they are, go to <a href="#css_02_0025_0__en-us_topic_0076847546_li47021920155415">2</a>.</li><li id="css_02_0025_0__en-us_topic_0076847546_li1670284422617">If they are not, create an ECS instance and ensure that the ECS instance is in the same VPC as the cluster.</li></ul>
</li><li id="css_02_0025_0__en-us_topic_0076847546_li47021920155415"><a name="css_02_0025_0__en-us_topic_0076847546_li47021920155415"></a><a name="en-us_topic_0076847546_li47021920155415"></a>View the security group rule setting of the cluster to check whether port <strong id="css_02_0025_0__en-us_topic_0076847546_b1185735191620">9200</strong> (TCP protocol) is allowed or port <strong id="css_02_0025_0__en-us_topic_0076847546_b1117213112175">9200</strong> is included in the port range allowed in both the outbound and inbound directions.<ul id="css_02_0025_0__en-us_topic_0076847546_ul159483195518"><li id="css_02_0025_0__en-us_topic_0076847546_li1159453115517">If it is allowed, go to <a href="#css_02_0025_0__en-us_topic_0076847546_li770210445265">3</a>.</li><li id="css_02_0025_0__en-us_topic_0076847546_li162562815512">If it is not allowed, switch to the VPC management console and configure the security group rule of the cluster to allow port <strong id="css_02_0025_0__en-us_topic_0076847546_b65601236163512">9200</strong> in both the outbound and inbound directions.</li></ul>
</li><li id="css_02_0025_0__en-us_topic_0076847546_li770210445265"><a name="css_02_0025_0__en-us_topic_0076847546_li770210445265"></a><a name="en-us_topic_0076847546_li770210445265"></a>Check whether the ECS instance has been added to a security group.<ul id="css_02_0025_0__en-us_topic_0076847546_ul1702164410262"><li id="css_02_0025_0__en-us_topic_0076847546_li1870254416262">If the instance has been added to a security group, check whether the security group configuration rules are appropriate. You can view the <strong id="css_02_0025_0__en-us_topic_0076847546_b16181325114210">Security Group</strong> information on the <strong id="css_02_0025_0__en-us_topic_0076847546_b8802162717418">Basic Information</strong> tab page of the cluster. Then, go to step <a href="#css_02_0025_0__en-us_topic_0076847546_li12702114432619">4</a>.<div class="fignone" id="css_02_0025_0__en-us_topic_0076847546_fig753791214329"><span class="figcap"><b>Figure 1 </b>Viewing security group information</span><br><span><img id="css_02_0025_0__en-us_topic_0076847546_image199847314327" src="en-us_image_0000001477297370.png"></span></div>
</li><li id="css_02_0025_0__en-us_topic_0076847546_li870214422614">If the instance has not been added to the security group, go to the VPC page from the ECS instance details page, select a security group, and add the ECS to the group.</li></ul>
</li><li id="css_02_0025_0__en-us_topic_0076847546_li12702114432619"><a name="css_02_0025_0__en-us_topic_0076847546_li12702114432619"></a><a name="en-us_topic_0076847546_li12702114432619"></a>Check whether the ECS instance can connect to the cluster.<div class="p" id="css_02_0025_0__en-us_topic_0076847546_p1170224452618"><a name="css_02_0025_0__en-us_topic_0076847546_li12702114432619"></a><a name="en-us_topic_0076847546_li12702114432619"></a><i><b><span class="cmdname" style="font-family:Arial" id="css_02_0025_0__en-us_topic_0076847546_cmdname2937185034614">ssh</span></b></i> <i><span class="varname" id="css_02_0025_0__en-us_topic_0076847546_varname1581114391496">&lt;Private network address and port number of a node&gt;</span></i><div class="note" id="css_02_0025_0__en-us_topic_0076847546_note37026444266"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_02_0025_0__en-us_topic_0076847546_p15702104462613">If the cluster contains multiple nodes, check whether the ECS can be connected to each node in the cluster.</p>
</div></div>
</div>
<ul id="css_02_0025_0__en-us_topic_0076847546_ul10702104432615"><li id="css_02_0025_0__en-us_topic_0076847546_li37029446266">If the connection is normal, the network is running properly.</li><li id="css_02_0025_0__en-us_topic_0076847546_li570294412263">If the connection still fails, contact technical support.</li></ul>
</li></ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0077.html">Clusters</a></div>
</div>
</div>

Some files were not shown because too many files have changed in this diff Show More