revert yangtong2/doc-exports:mrs_umn_202506181 commit 465fa65574

revert MRS UMN 202506181 new version

Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: yangtong <yangtong2@huawei.com>
Co-committed-by: yangtong <yangtong2@huawei.com>

docs/mrs/umn/ALM-12033.html

@@ -92,7 +92,7 @@
 <div class="section" id="ALM-12033__section15140644"><h4 class="sectiontitle">Procedure</h4><p id="ALM-12033__p1856018391458"><strong id="ALM-12033__b3282392191458">Check the disk status.</strong></p>
 <ol id="ALM-12033__ol4468641992138"><li id="ALM-12033__li4149191591458"><span>On <span id="ALM-12033__text34789336432">MRS</span> Manager, choose <strong id="ALM-12033__b54488846544512">O&amp;M</strong>. In the navigation pane on the left, choose <strong id="ALM-12033__b20884598144512">Alarm</strong> &gt; <strong id="ALM-12033__b27619653444512">Alarms</strong>.</span></li><li id="ALM-12033__li3788291791458"><a name="ALM-12033__li3788291791458"></a><a name="li3788291791458"></a><span>View the detailed information about the alarm. Check the values of <strong id="ALM-12033__b1216047996">HostName</strong> and <strong id="ALM-12033__b43072495916">DiskName</strong> in the location information to obtain the information about the faulty disk for which the alarm is generated.</span></li><li id="ALM-12033__li540193791458"><span>Check whether the node for which the alarm is generated is in a virtualization environment.</span><p><ul id="ALM-12033__ul4861744191458"><li id="ALM-12033__li3490378991458">If yes, go to <a href="#ALM-12033__li2831628891458">4</a>.</li><li id="ALM-12033__li863462891458">If no, go to <a href="#ALM-12033__li2583597491458">7</a>.</li></ul>
 </p></li><li id="ALM-12033__li2831628891458"><a name="ALM-12033__li2831628891458"></a><a name="li2831628891458"></a><span>Check whether the storage performance provided by the virtualization environment meets the hardware requirements. Then, go to <a href="#ALM-12033__li1205527419227">5</a>.</span></li><li id="ALM-12033__li1205527419227"><a name="ALM-12033__li1205527419227"></a><a name="li1205527419227"></a><span>Log in to the alarm node as user <strong id="ALM-12033__b19653192618269">root</strong>, run the <strong id="ALM-12033__b13449155511259">df -h</strong> command, and check whether the command output contains the value of the <strong id="ALM-12033__b1074473672410">DiskName</strong> field. <span id="ALM-12033__text23715444267"></span></span><p><ul id="ALM-12033__ul12100362193111"><li id="ALM-12033__li56917037201355">If yes, go to <a href="#ALM-12033__li2583597491458">7</a>.</li><li id="ALM-12033__li8577348201455">If no, go to <a href="#ALM-12033__li2325719119312">6</a>.</li></ul>
-</p></li><li id="ALM-12033__li2325719119312"><a name="ALM-12033__li2325719119312"></a><a name="li2325719119312"></a><span>Run the <strong id="ALM-12033__b1673412214263">lsblk</strong> command to check whether the mapping between the value of <strong id="ALM-12033__b1388164762511">DiskName</strong> and the disk has been created.</span><p><div class="p" id="ALM-12033__p55380970201120"><span><img id="ALM-12033__image94412418324" src="en-us_image_0000001583127305.jpg"></span><ul id="ALM-12033__ul245583919286"><li id="ALM-12033__li40945773201617">If yes, go to <a href="#ALM-12033__li2583597491458">7</a>.</li><li id="ALM-12033__li4547636219286">If no, go to <a href="#ALM-12033__li4518231891458">22</a>.</li></ul>
+</p></li><li id="ALM-12033__li2325719119312"><a name="ALM-12033__li2325719119312"></a><a name="li2325719119312"></a><span>Run the <strong id="ALM-12033__b1673412214263">lsblk</strong> command to check whether the mapping between the value of <strong id="ALM-12033__b1388164762511">DiskName</strong> and the disk has been created.</span><p><div class="p" id="ALM-12033__p55380970201120"><span><img id="ALM-12033__image94412418324" src="en-us_image_0000001583127305.jpg"></span><ul id="ALM-12033__ul245583919286"><li id="ALM-12033__li40945773201617">If yes, go to <a href="#ALM-12033__li2583597491458">7</a>. .</li><li id="ALM-12033__li4547636219286">If no, go to <a href="#ALM-12033__li4518231891458">22</a>.</li></ul>
 </div>
 </p></li><li id="ALM-12033__li2583597491458"><a name="ALM-12033__li2583597491458"></a><a name="li2583597491458"></a><span>Log in to the alarm node as user <strong id="ALM-12033__b3119718091458">root</strong>, run the <strong id="ALM-12033__b1233916891458">lsscsi | grep "/dev/sd[x]"</strong> command to view the disk information, and check whether RAID has been set up. <span id="ALM-12033__text1899265513266"></span></span><p><div class="note" id="ALM-12033__note4394365191458"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p class="text" id="ALM-12033__p5994854291458">In the command, <strong id="ALM-12033__b470511334308">/dev/sd[x]</strong> indicates the disk name obtained in <a href="#ALM-12033__li3788291791458">2</a>.</p>
 </div></div>

docs/mrs/umn/ALM-13006.html

@@ -60,7 +60,7 @@
 </div>
 <div class="section" id="ALM-13006__section433103353311"><h4 class="sectiontitle">Procedure</h4><p class="tableheading" id="ALM-13006__p33897081"><strong id="ALM-13006__b393592515539">Check whether a large amount of data is written to the directory for which the alarm is generated.</strong></p>
 <ol id="ALM-13006__ol3765182111"><li id="ALM-13006__li1197412314339"><span>On <span id="ALM-13006__text34789336432">MRS</span> Manager, choose <strong id="ALM-13006__b0989163143314">O&amp;M</strong> &gt; <strong id="ALM-13006__b1098973103314">Alarm </strong>&gt; <strong id="ALM-13006__b39898316336">Alarms</strong>. On the displayed interface, click the drop-down button of <strong id="ALM-13006__b2449248133115">Znode Number or Capacity Exceeds the Threshold</strong>. Confirm the Znode for which the alarm is generated in Location Information.</span></li><li id="ALM-13006__li177641181818"><span>Log in to <span id="ALM-13006__text2021517588497">MRS</span> Manager, open the ZooKeeper service interface, and select <strong id="ALM-13006__b13283115325311">Resource</strong>. In the table <strong id="ALM-13006__b528317533538">Used Resources (By Second-Level Znode)</strong>, check whether a large amount of data is written to the top-level Znode for which the alarm is reported.</span><p><ul class="subitemlist" id="ALM-13006__ul1676458911"><li id="ALM-13006__li127642815115">If it is, go to <a href="#ALM-13006__li47651981813">3</a>.</li><li id="ALM-13006__li11764081814">If it is not, go to <a href="#ALM-13006__li3567539141610">4</a>.</li></ul>
-</p></li><li id="ALM-13006__li47651981813"><a name="ALM-13006__li47651981813"></a><a name="li47651981813"></a><span>Log in to the ZooKeeper client and delete the data in the top-level Znode.</span></li><li id="ALM-13006__li3567539141610"><a name="ALM-13006__li3567539141610"></a><a name="li3567539141610"></a><span>Log in to <span id="ALM-13006__text97277596492">MRS</span> Manager and open the ZooKeeper service interface. On the <strong id="ALM-13006__b1159282116553">Resource</strong> page, choose <span><img id="ALM-13006__image178981286259" src="en-us_image_0000002278171933.png"></span> &gt; <strong id="ALM-13006__b107518249458">By Znode quantity </strong>in<strong id="ALM-13006__b1027117321815"> Used Resources (By Second-Level Znode)</strong>. <strong id="ALM-13006__b6592132116551">Threshold </strong><strong id="ALM-13006__b1054211994713">Configuration of By Znode quantity</strong> is displayed. Click <strong id="ALM-13006__b459272120553">Modify</strong> under <strong id="ALM-13006__b105921721185516">Operation</strong>. Increase the threshold by referringto the value of <strong id="ALM-13006__b14592102195511">max.Znode.count</strong> by choosing <strong id="ALM-13006__b7433193216335">Cluster &gt; </strong><em id="ALM-13006__i421463722619">Name of the desired cluster</em><strong id="ALM-13006__b84331232113317"> &gt; Services</strong> &gt; <strong id="ALM-13006__b114333323337">ZooKeeper</strong> &gt; <strong id="ALM-13006__b164331732163312">Configurations &gt; All Configurations</strong><strong id="ALM-13006__b15927218551"> &gt; Quota</strong>.</span></li><li id="ALM-13006__li9765881211"><span>In the <strong id="ALM-13006__b102034289614">Used Resources (By Second-Level Znode)</strong>, choose <span><img id="ALM-13006__image163471626162517" src="en-us_image_0000002278292689.png"></span> &gt; <strong id="ALM-13006__b4208441362">By capacity</strong>. The <strong id="ALM-13006__b1569135817619">Threshold Settings</strong> page of <strong id="ALM-13006__b205691658961">By Capacity</strong> is displayed. Click <strong id="ALM-13006__b3240163445520">Modify</strong> under <strong id="ALM-13006__b1224015342551">Operation</strong>. Increase the threshold by referring to the value of <strong id="ALM-13006__b112404343558">max.data.size</strong> by choosing <strong id="ALM-13006__b6212173752610">Cluster &gt; </strong><em id="ALM-13006__i1526192312156">Name of the desired cluster</em><strong id="ALM-13006__b1421320375260"> &gt; Services</strong> &gt; <strong id="ALM-13006__b12335119161213">ZooKeeper</strong> &gt; <strong id="ALM-13006__b102081427618">Configurations &gt; All Configurations</strong> &gt; <strong id="ALM-13006__b12401834175516">Quota</strong>.</span></li><li id="ALM-13006__li776515817114"><span>Check whether the alarm is cleared.</span><p><ul id="ALM-13006__ul20765981117"><li id="ALM-13006__li11765382114">If it is, no further action is required.</li><li id="ALM-13006__li37651582017">If it is not, go to <a href="#ALM-13006__li27634817118">7</a>.</li></ul>
+</p></li><li id="ALM-13006__li47651981813"><a name="ALM-13006__li47651981813"></a><a name="li47651981813"></a><span>Log in to the ZooKeeper client and delete the data in the top-level Znode.</span></li><li id="ALM-13006__li3567539141610"><a name="ALM-13006__li3567539141610"></a><a name="li3567539141610"></a><span>Log in to <span id="ALM-13006__text97277596492">MRS</span> Manager and open the ZooKeeper service interface. On the <strong id="ALM-13006__b1159282116553">Resource</strong> page, choose <span><img id="ALM-13006__image2679205116712" src="en-us_image_0000001828886549.png"></span> &gt; <strong id="ALM-13006__b107518249458">By Znode quantity </strong>in<strong id="ALM-13006__b1027117321815"> Used Resources (By Second-Level Znode)</strong>. <strong id="ALM-13006__b6592132116551">Threshold </strong><strong id="ALM-13006__b1054211994713">Configuration of By Znode quantity</strong> is displayed. Click <strong id="ALM-13006__b459272120553">Modify</strong> under <strong id="ALM-13006__b105921721185516">Operation</strong>. Increase the threshold by referringto the value of <strong id="ALM-13006__b14592102195511">max.Znode.count</strong> by choosing <strong id="ALM-13006__b7433193216335">Cluster &gt; </strong><em id="ALM-13006__i421463722619">Name of the desired cluster</em><strong id="ALM-13006__b84331232113317"> &gt; Services</strong> &gt; <strong id="ALM-13006__b114333323337">ZooKeeper</strong> &gt; <strong id="ALM-13006__b164331732163312">Configurations &gt; All Configurations</strong><strong id="ALM-13006__b15927218551"> &gt; Quota</strong>.</span></li><li id="ALM-13006__li9765881211"><span>In the <strong id="ALM-13006__b102034289614">Used Resources (By Second-Level Znode)</strong>, choose <span><img id="ALM-13006__image22264151487" src="en-us_image_0000001782327888.png"></span> &gt; <strong id="ALM-13006__b4208441362">By capacity</strong>. The <strong id="ALM-13006__b1569135817619">Threshold Settings</strong> page of <strong id="ALM-13006__b205691658961">By Capacity</strong> is displayed. Click <strong id="ALM-13006__b3240163445520">Modify</strong> under <strong id="ALM-13006__b1224015342551">Operation</strong>. Increase the threshold by referring to the value of <strong id="ALM-13006__b112404343558">max.data.size</strong> by choosing <strong id="ALM-13006__b6212173752610">Cluster &gt; </strong><em id="ALM-13006__i1526192312156">Name of the desired cluster</em><strong id="ALM-13006__b1421320375260"> &gt; Services</strong> &gt; <strong id="ALM-13006__b12335119161213">ZooKeeper</strong> &gt; <strong id="ALM-13006__b102081427618">Configurations &gt; All Configurations</strong> &gt; <strong id="ALM-13006__b12401834175516">Quota</strong>.</span></li><li id="ALM-13006__li776515817114"><span>Check whether the alarm is cleared.</span><p><ul id="ALM-13006__ul20765981117"><li id="ALM-13006__li11765382114">If it is, no further action is required.</li><li id="ALM-13006__li37651582017">If it is not, go to <a href="#ALM-13006__li27634817118">7</a>.</li></ul>
 </p></li></ol>
 <p class="tableheading" id="ALM-13006__p4863846161727"><strong id="ALM-13006__b60263252161739">Collect fault information.</strong></p>
 <ol start="7" id="ALM-13006__ol117641584110"><li id="ALM-13006__li27634817118"><a name="ALM-13006__li27634817118"></a><a name="li27634817118"></a><span>On the <span id="ALM-13006__text11168914505">MRS</span> Manager portal, choose <strong id="ALM-13006__b476328715">O&amp;M</strong> &gt; <strong id="ALM-13006__b0763158616">Log &gt; Download</strong>.</span></li><li id="ALM-13006__li1676319812119"><span>Select <strong id="ALM-13006__b133686503436">ZooKeeper </strong>in the required cluster from the <strong id="ALM-13006__b107631681219">Service</strong>.</span></li><li id="ALM-13006__li47641815116"><span>Click <span><img id="ALM-13006__image107644811115" src="en-us_image_0000001583087513.png"></span> in the upper right corner, and set <strong id="ALM-13006__b10764198312">Start Date</strong> and <strong id="ALM-13006__b1376412817111">End Date</strong> for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click <strong id="ALM-13006__b1376468310">Download</strong>.</span></li><li id="ALM-13006__li1776418716"><span>Contact the <span id="ALM-13006__text4614151421417">O&amp;M personnel</span> and send the collected logs.</span></li></ol>

docs/mrs/umn/ALM-13007.html

@@ -75,7 +75,7 @@
 </div>
 <div class="section" id="ALM-13007__section433103353311"><h4 class="sectiontitle">Procedure</h4><p class="tableheading" id="ALM-13007__p33897081"><strong id="ALM-13007__b3926356627">Check whether there are a large number of client processes connected to ZooKeeper.</strong></p>
 <ol id="ALM-13007__ol167406317264"><li id="ALM-13007__li13925125054018"><span>On <span id="ALM-13007__text34789336432">MRS</span> Manager, choose <strong id="ALM-13007__b0989163143314">O&amp;M</strong> &gt; <strong id="ALM-13007__b1098973103314">Alarm </strong>&gt; <strong id="ALM-13007__b39898316336">Alarms</strong>. On the displayed interface, click the drop-down button of <strong id="ALM-13007__b077716111321">Available ZooKeeper Client Connections Are Insufficient</strong>. Confirm the node IP address of the host for which the alarm is generated in the Location Information.</span></li><li id="ALM-13007__li137391311268"><span>Open the ZooKeeper service interface, click <strong id="ALM-13007__b1783216211454">Resource</strong> to enter the <strong id="ALM-13007__b1783211215518">Resource</strong> page, and check whether the number of connections of the client with the IP address specified by <strong id="ALM-13007__b1683292115518">Number of Connections</strong><strong id="ALM-13007__b208321121756"> (By Client IP Address)</strong> is large.</span><p><ul class="subitemlist" id="ALM-13007__ul473915316264"><li id="ALM-13007__li10738153162617">If it is, go to <a href="#ALM-13007__li9739531132620">3</a>.</li><li id="ALM-13007__li57399316268">If it is not, go to <a href="#ALM-13007__li1373973122619">4</a>.</li></ul>
-</p></li><li id="ALM-13007__li9739531132620"><a name="ALM-13007__li9739531132620"></a><a name="li9739531132620"></a><span>Check whether connection leakage occurs on the client process.</span></li><li id="ALM-13007__li1373973122619"><a name="ALM-13007__li1373973122619"></a><a name="li1373973122619"></a><span>Click <span><img id="ALM-13007__image346064053012" src="en-us_image_0000002243257660.png"></span> in the <strong id="ALM-13007__b142081742268">Number of Connections</strong> <strong id="ALM-13007__b32086421668">(by Client IP Address) </strong>to enter the <strong id="ALM-13007__b22081942169">Thresholds</strong><strong id="ALM-13007__b912333161"> </strong>page, and click <strong id="ALM-13007__b22081842861">Modify</strong> under <strong id="ALM-13007__b22084425616">Operation</strong>. Increase the threshold by referring to the value of <strong id="ALM-13007__b620844217620">maxClientCnxns</strong> by choosing <strong id="ALM-13007__b6212173752610">Cluster &gt; </strong><em id="ALM-13007__i421463722619">Name of the desired cluster</em><strong id="ALM-13007__b1421320375260"> &gt; Services</strong> &gt; <strong id="ALM-13007__b12335119161213">ZooKeeper</strong> &gt; <strong id="ALM-13007__b102081427618">Configurations &gt; All Configurations &gt; quorumpeer</strong>.</span></li><li id="ALM-13007__li8740173118265"><span>Check whether the alarm is cleared.</span><p><ul id="ALM-13007__ul874073110261"><li id="ALM-13007__li3739153114263">If it is, no further action is required.</li><li id="ALM-13007__li574063120263">If it is not, go to <a href="#ALM-13007__li27361331112613">6</a>.</li></ul>
+</p></li><li id="ALM-13007__li9739531132620"><a name="ALM-13007__li9739531132620"></a><a name="li9739531132620"></a><span>Check whether connection leakage occurs on the client process.</span></li><li id="ALM-13007__li1373973122619"><a name="ALM-13007__li1373973122619"></a><a name="li1373973122619"></a><span>Click<span><img id="ALM-13007__image4415157111419" src="en-us_image_0000001830029997.png"></span> in the <strong id="ALM-13007__b142081742268">Number of Connections</strong> <strong id="ALM-13007__b32086421668">(by Client IP Address) </strong>to enter the <strong id="ALM-13007__b22081942169">Thresholds</strong><strong id="ALM-13007__b912333161"> </strong>page, and click <strong id="ALM-13007__b22081842861">Modify</strong> under <strong id="ALM-13007__b22084425616">Operation</strong>. Increase the threshold by referring to the value of <strong id="ALM-13007__b620844217620">maxClientCnxns</strong> by choosing <strong id="ALM-13007__b6212173752610">Cluster &gt; </strong><em id="ALM-13007__i421463722619">Name of the desired cluster</em><strong id="ALM-13007__b1421320375260"> &gt; Services</strong> &gt; <strong id="ALM-13007__b12335119161213">ZooKeeper</strong> &gt; <strong id="ALM-13007__b102081427618">Configurations &gt; All Configurations &gt; quorumpeer</strong>.</span></li><li id="ALM-13007__li8740173118265"><span>Check whether the alarm is cleared.</span><p><ul id="ALM-13007__ul874073110261"><li id="ALM-13007__li3739153114263">If it is, no further action is required.</li><li id="ALM-13007__li574063120263">If it is not, go to <a href="#ALM-13007__li27361331112613">6</a>.</li></ul>
 </p></li></ol>
 <p class="tableheading" id="ALM-13007__p4863846161727"><strong id="ALM-13007__b60263252161739">Collect fault information.</strong></p>
 <ol start="6" id="ALM-13007__ol1473843117261"><li id="ALM-13007__li27361331112613"><a name="ALM-13007__li27361331112613"></a><a name="li27361331112613"></a><span>On the <span id="ALM-13007__text1383113355017">MRS</span> Manager portal, choose <strong id="ALM-13007__b17735193112269">O&amp;M</strong> &gt; <strong id="ALM-13007__b1373518312260">Log &gt; Download</strong>.</span></li><li id="ALM-13007__li107369316261"><span>Select <strong id="ALM-13007__b18736183182620">ZooKeeper</strong> in the required cluster from the <strong id="ALM-13007__b6736331152610">Service</strong>.</span></li><li id="ALM-13007__li11736103132617"><span>Click <span><img id="ALM-13007__image157361231102619" src="en-us_image_0000001532927402.png"></span> in the upper right corner, and set <strong id="ALM-13007__b11736231122619">Start Date</strong> and <strong id="ALM-13007__b1873663112618">End Date</strong> for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click <strong id="ALM-13007__b1573619314263">Download</strong>.</span></li><li id="ALM-13007__li27381331192612"><span>Contact the <span id="ALM-13007__text4614151421417">O&amp;M personnel</span> and send the collected logs.</span></li></ol>

docs/mrs/umn/admin_guide_000222.html

@@ -7,7 +7,7 @@
 </li></ul>
 </div></div>
 </div>
-<div class="section" id="admin_guide_000222__s3d87a834c70a4833bd9f75d1f5ec3937"><h4 class="sectiontitle">Impact on the System</h4><ul id="admin_guide_000222__en-us_topic_0046736776_ul28599227"><li id="admin_guide_000222__en-us_topic_0046736776_li56066454">After the data is restored, the data generated after the data backup and before the data restoration is lost.</li><li id="admin_guide_000222__en-us_topic_0046736776_li34836040">After the data is recovered, the NameNode needs to be restarted and is unavailable during the restart.</li><li id="admin_guide_000222__en-us_topic_0046736776_li45088906">After data is restored, metadata and service data may not be matched, the HDFS enters the security mode, and the HDFS service fails to be started.</li></ul>
+<div class="section" id="admin_guide_000222__s3d87a834c70a4833bd9f75d1f5ec3937"><h4 class="sectiontitle">Impact on the System</h4><ul id="admin_guide_000222__en-us_topic_0046736776_ul28599227"><li id="admin_guide_000222__en-us_topic_0046736776_li56066454">After the data is restored, the data generated after the data backup and before the data restoration is lost.</li><li id="admin_guide_000222__en-us_topic_0046736776_li34836040">After the data is recovered, the NameNode needs to be restarted and is unavailable during the restart.</li><li id="admin_guide_000222__en-us_topic_0046736776_li45088906">After data is restored, metadata and service data may not be matched, the HDFS enters the security mode, and the HDFS service fails to be started. .</li></ul>
 </div>
 <div class="section" id="admin_guide_000222__sb52fec7351f043f98e59e033bbef9ed5"><h4 class="sectiontitle">Prerequisites</h4><ul id="admin_guide_000222__ul1222213533213"><li id="admin_guide_000222__l6b2ccbf0a54a4d7994c8b888340d4fc3">If you need to restore data from a remote HDFS, prepare a standby cluster. If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same <span id="admin_guide_000222__text13955105916179">MRS</span> Manager, mutual trust has been configured. For details, see <a href="admin_guide_000177.html">Configuring Cross-Manager Mutual Trust Between Clusters</a>. If the active cluster is deployed in normal mode, no mutual trust is required.</li></ul>
 <ul id="admin_guide_000222__en-us_topic_0046736776_ul53578275"><li id="admin_guide_000222__en-us_topic_0046736776_li1204049">Cross-cluster replication has been configured for the active and standby clusters. For details, see <a href="admin_guide_000200.html">Enabling Cross-Cluster Replication</a>.</li><li id="admin_guide_000222__en-us_topic_0046736776_li30419176">Time is consistent between the active and standby clusters and the NTP services on the active and standby clusters use the same time source.</li><li id="admin_guide_000222__en-us_topic_0046736776_li5337128">You have logged in to <span id="admin_guide_000222__text1660761101815">MRS</span> Manager. For details, see <a href="admin_guide_000004.html">Logging In to MRS Manager</a>.</li><li id="admin_guide_000222__en-us_topic_0046736776_li29654208">On <span id="admin_guide_000222__text914213313186">MRS</span> Manager, all the NameNode role instances whose data is to be recovered are stopped. Other HDFS role instances must keep running. After data is recovered, the NameNode role instances need to be restarted. The NameNode role instances cannot be accessed during the restart.</li><li id="admin_guide_000222__en-us_topic_0046736776_li65561281">The NameNode backup files are stored <strong id="admin_guide_000222__b20257618115318"><em id="admin_guide_000222__i1367672115536">Data path</em>/LocalBackup/</strong> on the active management node.</li></ul>

docs/mrs/umn/admin_guide_000238.html

@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Permission Verification Policies</h1>
 <div id="body1529658735918"><div class="section" id="admin_guide_000238__s979ad36438c54e09967ad6d230cecb54"><h4 class="sectiontitle">Security Mode</h4><p id="admin_guide_000238__en-us_topic_0046736678_p24562296">After a user is authenticated by the big data platform, the system determines whether to verify the user's permission based on the actual permission management configuration to ensure that the user has limited or all permission on resources. If the user does not have the permission for accessing cluster resources, the system administrator must grant the required permission to the user. Otherwise, the user fails to access the resources. The cluster provides permission verification capabilities in both security mode and normal mode. The specific permission items of the components are the same in the two modes.</p>
 <p id="admin_guide_000238__p14390455171710">By default, the Ranger service is installed and Ranger authentication is enabled for a newly installed cluster in security mode. You can set fine-grained security access policies for accessing component resources through the permission plug-in of the component. If Ranger authentication is not required, administrators can manually disable it on the service page. After Ranger authentication is disabled, the system continues to perform permission control based on the role model of <span id="admin_guide_000238__text67509419010">MRS</span> Manager when accessing component resources.</p>
-<p id="admin_guide_000238__p576644617223">In a cluster in security mode, the following components support Ranger authentication: HDFS, YARN, Kafka, Hive, HBase, Storm, Impala, and Spark2x.</p>
+<p id="admin_guide_000238__p576644617223">In a cluster in security mode, the following components support Ranger authentication: HDFS, YARN, Kafka, Hive, HBase, Storm,, Impala, and Spark2x.</p>
 <p id="admin_guide_000238__p5997645102113">For a cluster upgraded from an earlier version, Ranger authentication is not used by default when users access component resources. The administrator can manually enable Ranger authentication after installing Ranger.</p>
 <p id="admin_guide_000238__en-us_topic_0046736678_p19734077">By default, all components in the cluster of the security edition authenticate access. The authentication function cannot be disabled.</p>
 </div>

docs/mrs/umn/admin_guide_000272.html

@@ -7,11 +7,13 @@
 <div class="section" id="admin_guide_000272__s9e655cd471c0471aa6d81f53fafcf3e1"><h4 class="sectiontitle">Hardening LDAP</h4><p id="admin_guide_000272__en-us_topic_0046736699_p4753596">LDAP is hardened as follows after a cluster is installed:</p>
 <ul id="admin_guide_000272__en-us_topic_0046736699_ul42782368"><li id="admin_guide_000272__en-us_topic_0046736699_li49496992">In the LDAP configuration file, the password of the administrator account is encrypted using SHA. After the OpenLDAP is upgraded to 2.4.39 or later, data is automatically synchronized between the active and standby LDAP nodes using the SASL External mechanism, which prevents disclosure of the password.</li><li id="admin_guide_000272__en-us_topic_0046736699_li42819751">The LDAP service in the cluster supports the SSLv3 protocol by default, which can be used safely. When the OpenLDAP is upgraded to 2.4.39 or later, the LDAP automatically uses TLS1.0 or later to prevent unknown security risks.</li></ul>
 </div>
-<div class="section" id="admin_guide_000272__sdcb00b4084b144a8857f2cbd4256c116"><h4 class="sectiontitle">Hardening JDK</h4><p id="admin_guide_000272__p1096264551117">If the client process uses the AES256 encryption algorithm, JDK security hardening is required. The operations are as follows:</p>
-<p id="admin_guide_000272__p3219968112">Obtain the Java Cryptography Extension (JCE) package whose version matches that of JDK. The JCE package contains <strong id="admin_guide_000272__b779300107114915">local_policy.jar</strong> and <strong id="admin_guide_000272__b1677290344114915">US_export_policy.jar</strong>. Copy the JAR files to the following directory and replace the files in the directory.</p>
+<div class="section" id="admin_guide_000272__sdcb00b4084b144a8857f2cbd4256c116"><h4 class="sectiontitle">Hardening JDK</h4><ul id="admin_guide_000272__ul3716412951"><li id="admin_guide_000272__li157163127512">If the client process uses the AES256 encryption algorithm, JDK security hardening is required. The operations are as follows:<p id="admin_guide_000272__p3219968112"><a name="admin_guide_000272__li157163127512"></a><a name="li157163127512"></a>Obtain the Java Cryptography Extension (JCE) package whose version matches that of JDK. The JCE package contains <strong id="admin_guide_000272__b779300107114915">local_policy.jar</strong> and <strong id="admin_guide_000272__b1677290344114915">US_export_policy.jar</strong>. Copy the JAR files to the following directory and replace the files in the directory.</p>
 <ul id="admin_guide_000272__ul169611321194516"><li id="admin_guide_000272__li2344917144514">Linux: <em id="admin_guide_000272__i195288395114915">JDK installation directory</em><strong id="admin_guide_000272__b1272682312182">/jre/lib/security</strong></li><li id="admin_guide_000272__li1334501715453">Windows: <em id="admin_guide_000272__i1619381111114915">JDK installation directory</em><strong id="admin_guide_000272__b433525121918">\jre\lib\security</strong></li></ul>
 <div class="note" id="admin_guide_000272__note103641326306"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="admin_guide_000272__p731711371543">Access the Open JDK open-source community to obtain the JCE file.</p>
 </div></div>
+</li><li id="admin_guide_000272__li1013492211199">If the client process uses the SM4 encryption algorithm, the JAR package needs to be updated.<p id="admin_guide_000272__p16135822161912"><a name="admin_guide_000272__li1013492211199"></a><a name="li1013492211199"></a>Obtain <strong id="admin_guide_000272__b867330327114915">SMS4JA.jar</strong> in the <em id="admin_guide_000272__i686321128114915">client installation directory</em><strong id="admin_guide_000272__b2003830109114915">/JDK/jdk/jre/lib/ext/</strong> directory, and copy the JAR package to the following directory:</p>
+<ul id="admin_guide_000272__ul080063019454"><li id="admin_guide_000272__li579242764513">Linux: <em id="admin_guide_000272__i1984342231114915">JDK installation directory</em><strong id="admin_guide_000272__b8544550152717">/jre/lib/ext/</strong></li><li id="admin_guide_000272__li4793327164510">Windows: <em id="admin_guide_000272__i1927047002114915">JDK installation directory</em><strong id="admin_guide_000272__b14491145612274">\jre\lib\ext\</strong></li></ul>
+</li></ul>
 </div>
 </div>
 <div>

docs/mrs/umn/admin_guide_000415.html

@@ -3,7 +3,7 @@
 <h1 class="topictitle1">Switching Ranger Authentication</h1>
 <div id="body1593331493817"><div class="section" id="admin_guide_000415__section129911458858"><h4 class="sectiontitle">Scenario</h4><p id="admin_guide_000415__p14390455171710">By default, the Ranger service is installed and Ranger authentication is enabled for a newly installed cluster in security mode. You can set fine-grained security access policies for accessing component resources through the permission plug-in of the component. If Ranger authentication is not required, the cluster administrator can manually disable Ranger authentication on the service page. After Ranger authentication is disabled, the system continues to perform permission control based on the role model of <span id="admin_guide_000415__text154091129192818">MRS</span> Manager when accessing component resources.</p>
 <p id="admin_guide_000415__p1328751611431">In a cluster upgraded from an earlier version, Ranger authentication is not used by default when users access component resources. The cluster administrator can manually enable Ranger authentication after installing the Ranger service.</p>
-<div class="note" id="admin_guide_000415__note161556791410"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="admin_guide_000415__ul1190763463814"><li id="admin_guide_000415__li119071634183812">In a cluster in security mode, the following components support Ranger authentication: HDFS, YARN, Kafka, Hive, HBase, Storm, Impala, and Spark2x.</li><li id="admin_guide_000415__li05271254143916">In a cluster in non-security mode, Ranger supports permission control on component resources based on OS users. The following components support Ranger authentication: HBase, HDFS, Hive, Spark2x, and YARN.</li><li id="admin_guide_000415__li959713010817">After Ranger authentication is enabled, all authentication of the component will be managed by Ranger. The permissions set by the original authentication plug-in will become invalid (The ACL rules of HDFS and YARN components still take effect). Exercise caution when performing this operation. You are advised to deploy permissions on Ranger in advance.</li><li id="admin_guide_000415__li53715381485">After Ranger authentication is disabled, all authentication of the component will be managed by the permission plug-in of the component. The permission set on Ranger will become invalid. Exercise caution when performing this operation. You are advised to deploy permissions on Manager in advance.</li></ul>
+<div class="note" id="admin_guide_000415__note161556791410"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="admin_guide_000415__ul1190763463814"><li id="admin_guide_000415__li119071634183812">In a cluster in security mode, the following components support Ranger authentication: HDFS, YARN, Kafka, Hive, HBase, Storm,, Impala, and Spark2x.</li><li id="admin_guide_000415__li05271254143916">In a cluster in non-security mode, Ranger supports permission control on component resources based on OS users. The following components support Ranger authentication: HBase, HDFS, Hive, Spark2x, and YARN.</li><li id="admin_guide_000415__li959713010817">After Ranger authentication is enabled, all authentication of the component will be managed by Ranger. The permissions set by the original authentication plug-in will become invalid (The ACL rules of HDFS and YARN components still take effect). Exercise caution when performing this operation. You are advised to deploy permissions on Ranger in advance.</li><li id="admin_guide_000415__li53715381485">After Ranger authentication is disabled, all authentication of the component will be managed by the permission plug-in of the component. The permission set on Ranger will become invalid. Exercise caution when performing this operation. You are advised to deploy permissions on Manager in advance.</li></ul>
 </div></div>
 </div>
 <div class="section" id="admin_guide_000415__section3763331141310"><h4 class="sectiontitle">Enabling Ranger Authentication</h4><ol id="admin_guide_000415__ol13297879162010"><li id="admin_guide_000415__li164975055814"><span>Log in to <span id="admin_guide_000415__text13914312153315">MRS</span> Manager.</span></li><li id="admin_guide_000415__li7497505580"><span>Choose <strong id="admin_guide_000415__b1080972466114850">Cluster</strong> &gt; <strong id="admin_guide_000415__b1744541332114850">Services</strong>.</span></li><li id="admin_guide_000415__en-us_topic_0046736984_li56314915"><span>Click the specified service name on the service management page.</span></li><li id="admin_guide_000415__en-us_topic_0046737017_li66067432"><span>On the service details page, expand the <strong id="admin_guide_000415__b20588841104918">More</strong> drop-down list and select <strong id="admin_guide_000415__b137841953164911">Enable Ranger</strong>.</span></li><li id="admin_guide_000415__li58171183162647"><span>In the displayed dialog box, enter the password of the current login user and click <strong id="admin_guide_000415__b494871119114850">OK</strong>.</span></li><li id="admin_guide_000415__li271517458317"><span>In the service list, restart the service whose configuration has expired.</span></li></ol>

docs/mrs/umn/en-us_topic_0000001296775220.html

@@ -0,0 +1,6 @@
+<a name="EN-US_TOPIC_0000001296775220"></a><a name="EN-US_TOPIC_0000001296775220"></a>
+
+<h1 class="topictitle1">Glossary</h1>
+<div id="body0000001296775220"><p id="EN-US_TOPIC_0000001296775220__p8060118">For details about the terms involved in this document, see <a href="https://docs.otc.t-systems.com/en-us/glossary/index.html" target="_blank" rel="noopener noreferrer">Glossary</a>.</p>
+</div>
+

docs/mrs/umn/en-us_topic_0000001349137409.html

@@ -0,0 +1,52 @@
+<a name="EN-US_TOPIC_0000001349137409"></a><a name="EN-US_TOPIC_0000001349137409"></a>
+
+<h1 class="topictitle1">Interconnecting Flume with OBS</h1>
+<div id="body0000001212462997"><p id="EN-US_TOPIC_0000001349137409__p532513517410">This section applies to MRS 3.x or later.</p>
+<p id="EN-US_TOPIC_0000001349137409__p12530131917241">Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to <a href="mrs_01_0768.html">Configuring a Storage-Compute Decoupled Cluster (Agency)</a> or <a href="mrs_01_0468.html">Configuring a Storage-Compute Decoupled Cluster (AK/SK)</a>.</p>
+<ol id="EN-US_TOPIC_0000001349137409__ol799520136129"><li id="EN-US_TOPIC_0000001349137409__li18779193762419"><span>Configure an agency.</span><p><ol type="a" id="EN-US_TOPIC_0000001349137409__ol12137520155019"><li id="EN-US_TOPIC_0000001349137409__li155111612132617">Log in to the MRS console. In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001349137409__b15297094092512">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001349137409__b155103070092512">Active Clusters</strong>.</li><li id="EN-US_TOPIC_0000001349137409__li361522111198">Click the name of a cluster to go to the cluster details page.</li><li id="EN-US_TOPIC_0000001349137409__li181041531102718">On the <strong id="EN-US_TOPIC_0000001349137409__b207763208692512">Dashboard</strong> page, click <strong id="EN-US_TOPIC_0000001349137409__b11479814592512">Synchronize</strong> on the right of <strong id="EN-US_TOPIC_0000001349137409__b204263747292512">IAM User Sync</strong> to synchronize IAM users.</li><li id="EN-US_TOPIC_0000001349137409__li459950142012">Click <strong id="EN-US_TOPIC_0000001349137409__b72428010492512">Manage Agency</strong> on the right of <strong id="EN-US_TOPIC_0000001349137409__b116453244192512">Agency</strong>, select the target agency, and click <strong id="EN-US_TOPIC_0000001349137409__b172200337492512">OK</strong>.</li></ol>
+</p></li><li id="EN-US_TOPIC_0000001349137409__li3279721151214"><a name="EN-US_TOPIC_0000001349137409__li3279721151214"></a><a name="li3279721151214"></a><span>Create an OBS file system for storing data.</span><p><ol type="a" id="EN-US_TOPIC_0000001349137409__ol9802520203018"><li id="EN-US_TOPIC_0000001349137409__li59654512476">Log in to the OBS console.</li><li id="EN-US_TOPIC_0000001349137409__li12708191754713">In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001349137409__b84872514792512">Parallel File Systems</strong>. On the displayed page, click <strong id="EN-US_TOPIC_0000001349137409__b203357332292512">Create Parallel File System</strong>.</li><li id="EN-US_TOPIC_0000001349137409__li20208105412477">Enter the file system name, for example, <strong id="EN-US_TOPIC_0000001349137409__b86313410692512">esdk-c-test-pfs1</strong>, and set other parameters as required. Click <strong id="EN-US_TOPIC_0000001349137409__b30889856092512">Create Now</strong>.</li><li id="EN-US_TOPIC_0000001349137409__li59781748509">In the parallel file system list on the OBS console, click the created file system name to go to its details page.</li><li id="EN-US_TOPIC_0000001349137409__li476162515523">In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001349137409__b4777368692512">Files</strong> and click <strong id="EN-US_TOPIC_0000001349137409__b54270490492512">Create Folder</strong> to create the <strong id="EN-US_TOPIC_0000001349137409__b90984860792512">testFlumeOutput</strong> folder.</li></ol>
+</p></li><li id="EN-US_TOPIC_0000001349137409__li2137135171211"><span>Prepare the <strong id="EN-US_TOPIC_0000001349137409__b48239875992512">properties.properties</strong> file and upload it to the <strong id="EN-US_TOPIC_0000001349137409__b191548854792512">/opt/flumeInput</strong> directory.</span><p><ol type="a" id="EN-US_TOPIC_0000001349137409__ol169821722103717"><li id="EN-US_TOPIC_0000001349137409__li192551317183716"><a name="EN-US_TOPIC_0000001349137409__li192551317183716"></a><a name="li192551317183716"></a>Prepare the <strong id="EN-US_TOPIC_0000001349137409__b141156617092512">properties.properties</strong> file on the local host. Its content is as follows:<pre class="screen" id="EN-US_TOPIC_0000001349137409__screen13582185283918"># source
+server.sources = r1
+# channels
+server.channels = c1
+# sink
+server.sinks = obs_sink
+# ----- define net source -----
+server.sources.r1.type = seq
+server.sources.r1.spooldir = <em id="EN-US_TOPIC_0000001349137409__i17225456155816">/opt/flumeInput</em>
+# ---- define OBS sink ----
+server.sinks.obs_sink.type = hdfs
+server.sinks.obs_sink.hdfs.path = obs://<em id="EN-US_TOPIC_0000001349137409__i8234248105819">esdk-c-test-pfs1/testFlumeOutput</em>
+server.sinks.obs_sink.hdfs.filePrefix = %[localhost]
+server.sinks.obs_sink.hdfs.useLocalTimeStamp = true
+# set file size to trigger roll
+server.sinks.obs_sink.hdfs.rollSize = 0
+server.sinks.obs_sink.hdfs.rollCount = 0
+server.sinks.obs_sink.hdfs.rollInterval = 5
+#server.sinks.obs_sink.hdfs.threadsPoolSize = 30
+server.sinks.obs_sink.hdfs.fileType = DataStream
+server.sinks.obs_sink.hdfs.writeFormat = Text
+server.sinks.obs_sink.hdfs.fileCloseByEndEvent = false
+
+# define channel
+server.channels.c1.type = memory
+server.channels.c1.capacity = 1000
+# transaction size
+server.channels.c1.transactionCapacity = 1000
+server.channels.c1.byteCapacity = 800000
+server.channels.c1.byteCapacityBufferPercentage = 20
+server.channels.c1.keep-alive = 60
+server.sources.r1.channels = c1
+server.sinks.obs_sink.channel = c1</pre>
+<div class="note" id="EN-US_TOPIC_0000001349137409__note164311010276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001349137409__p46431402272">The value of <strong id="EN-US_TOPIC_0000001349137409__b1442813582490">server.sinks.obs_sink.hdfs.path</strong> is the OBS file system created in <a href="#EN-US_TOPIC_0000001349137409__li3279721151214">2</a>.</p>
+</div></div>
+</li><li id="EN-US_TOPIC_0000001349137409__li146028147427">Log in to the node where the Flume client is installed as user <strong id="EN-US_TOPIC_0000001349137409__b1560317146424">root</strong>.</li><li id="EN-US_TOPIC_0000001349137409__li10237175311403">Create the <strong id="EN-US_TOPIC_0000001349137409__b154299233392512">/opt/flumeInput</strong> directory and create a customized <strong id="EN-US_TOPIC_0000001349137409__b67861468592512">.txt</strong> file in this directory.</li><li id="EN-US_TOPIC_0000001349137409__li430015491542">Log in to <span id="EN-US_TOPIC_0000001349137409__text947920520358">MRS</span> Manager.</li><li id="EN-US_TOPIC_0000001349137409__li1153122214455">Choose <strong id="EN-US_TOPIC_0000001349137409__b151334116992512">Cluster</strong> &gt; <em id="EN-US_TOPIC_0000001349137409__i83560472292512">Name of the target cluster</em> &gt; <strong id="EN-US_TOPIC_0000001349137409__b1294736092512">Services</strong> &gt; <strong id="EN-US_TOPIC_0000001349137409__b110428489292512">Flume</strong>. On the displayed page, click <strong id="EN-US_TOPIC_0000001349137409__b8614102392512">Configurations</strong> and then <strong id="EN-US_TOPIC_0000001349137409__b117708436192512">Upload File</strong> in the <strong id="EN-US_TOPIC_0000001349137409__b179076253192512">Value</strong> column corresponding to the <strong id="EN-US_TOPIC_0000001349137409__b99572410092512">flume.config.file</strong> parameter, upload the <strong id="EN-US_TOPIC_0000001349137409__b75808688092512">properties.properties</strong> file prepared in <a href="#EN-US_TOPIC_0000001349137409__li192551317183716">3.a</a>, and click <strong id="EN-US_TOPIC_0000001349137409__b55007443392512">Save</strong>.</li></ol>
+</p></li><li id="EN-US_TOPIC_0000001349137409__li13812115714130"><span>View the result in the OBS system.</span><p><ol type="a" id="EN-US_TOPIC_0000001349137409__ol118251848142115"><li id="EN-US_TOPIC_0000001349137409__li976843922116">Log in to the OBS console.</li><li id="EN-US_TOPIC_0000001349137409__li1276853919211">Click <strong id="EN-US_TOPIC_0000001349137409__b206639009992512">Parallel File Systems</strong> and go to the folder created in <a href="#EN-US_TOPIC_0000001349137409__li3279721151214">2</a> to view the result.</li></ol>
+</p></li></ol>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_01_0643.html">Using a Storage-Compute Decoupled Cluster</a></div>
+</div>
+</div>
+

docs/mrs/umn/mrs_01_0453.html

@@ -5,7 +5,7 @@
 <ul id="mrs_01_0453__ul18306165665316"><li id="mrs_01_0453__li2306856195318">Create IAM users under your cloud account for employees based on your enterprise's organizational structure so that each employee is allowed to access MRS resources using their unique security credential (IAM user).</li><li id="mrs_01_0453__li83069568531">Grant only the permissions required for users to perform a specific task.</li><li id="mrs_01_0453__li193061561534">Entrust a cloud account or cloud service to perform efficient O&amp;M on your MRS resources.</li></ul>
 <p id="mrs_01_0453__p13306256205311">If your cloud account does not require IAM users, skip this section.</p>
 <p id="mrs_01_0453__p2030785645311">This section describes the procedure for granting permissions (see <a href="#mrs_01_0453__fig8523123435310">Figure 1</a>).</p>
-<div class="section" id="mrs_01_0453__section02683813578"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="mrs_01_0453__fig8523123435310"><a name="mrs_01_0453__fig8523123435310"></a><a name="fig8523123435310"></a><span class="figcap"><b>Figure 1 </b>Process for granting MRS permissions</span><br><span><img id="mrs_01_0453__image17650152692316" src="en-us_image_0000002243727990.png"></span></div>
+<div class="section" id="mrs_01_0453__section02683813578"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="mrs_01_0453__fig8523123435310"><a name="mrs_01_0453__fig8523123435310"></a><a name="fig8523123435310"></a><span class="figcap"><b>Figure 1 </b>Process for granting MRS permissions</span><br><span><img id="mrs_01_0453__image1233218178345" src="en-us_image_0000001782509630.png"></span></div>
 <ol id="mrs_01_0453__ol139492810017"><li id="mrs_01_0453__li895020818018"><a name="mrs_01_0453__li895020818018"></a><a name="li895020818018"></a><a href="https://docs.otc.t-systems.com/en-us/usermanual/iam/iam_01_0030.html" target="_blank" rel="noopener noreferrer">Create a user group and assign permissions to it</a>.<p id="mrs_01_0453__p99501985019">Create a user group on the IAM console, and assign MRS permissions to the group.</p>
 </li><li id="mrs_01_0453__li59503817014"><a href="https://docs.otc.t-systems.com/en-us/usermanual/iam/iam_01_0031.html" target="_blank" rel="noopener noreferrer">Create a user and add it to a user group</a>.<p id="mrs_01_0453__p4950882013">Create a user on the IAM console and add the user to the group created in <a href="#mrs_01_0453__li895020818018">1. Create a user group and assign permissions to it</a>.</p>
 </li><li id="mrs_01_0453__li159506814017">Log in and verify permissions.<p id="mrs_01_0453__p8759553135"><a name="mrs_01_0453__li159506814017"></a><a name="li159506814017"></a>Log in to the console by using the user created, and verify that the user has the granted permissions.</p>

docs/mrs/umn/mrs_01_0495.html

@@ -93,17 +93,13 @@
 <div class="note" id="mrs_01_0495__note87151030183219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_01_0495__p83951127103113">To facilitate user permission management, use fine-grained policies rather than RBAC policies. In fine-grained policies, the Deny action takes precedence over other actions.</p>
 <ul id="mrs_01_0495__ul167982355311"><li id="mrs_01_0495__li1655593813318">A user has permission to synchronize IAM users only when the user has the Tenant Administrator role or has the Server Administrator, Tenant Guest, and MRS Administrator roles at the same time.</li><li id="mrs_01_0495__li1799173533110">A user with the <strong id="mrs_01_0495__b348744414313">action:mrs:cluster:syncUser</strong> policy has permission to synchronize IAM users.</li></ul>
 </div></div>
-<div class="section" id="mrs_01_0495__section1968244415315"><h4 class="sectiontitle">Procedure</h4><ol id="mrs_01_0495__ol1399115193113"><li id="mrs_01_0495__li0751526153614"><span>Create a user and authorize the user to use MRS. For details, see <a href="mrs_01_0453.html">Creating an MRS User</a>.</span></li><li id="mrs_01_0495__li1717155310510"><span>Log in to the MRS management console and create a cluster. For details, see <a href="mrs_01_0513.html">Creating a Custom Cluster</a>.</span></li><li id="mrs_01_0495__li168712054205213"><span>In the left navigation pane, choose <span class="menucascade" id="mrs_01_0495__menucascade882112551715"><b><span class="uicontrol" id="mrs_01_0495__uicontrol138252595713">Clusters</span></b> &gt; <b><span class="uicontrol" id="mrs_01_0495__uicontrol26341265817">Active Clusters</span></b></span>. Click the cluster name to go to the cluster details page.</span></li><li id="mrs_01_0495__li6999515311"><a name="mrs_01_0495__li6999515311"></a><a name="li6999515311"></a><span>In the <strong id="mrs_01_0495__b1762920331212">Basic Information</strong> area on the <span class="parmname" id="mrs_01_0495__parmname145843311212"><b>Dashboard</b></span> page, click <span class="parmvalue" id="mrs_01_0495__parmvalue132811049183612"><b>Synchronize</b></span> on the right side of <span class="parmname" id="mrs_01_0495__parmname10856123651"><b>IAM User Sync</b></span> to synchronize IAM users.</span></li><li id="mrs_01_0495__li10106192919318"><span>In the <strong id="mrs_01_0495__b974374131610">IAM User Sync</strong> dialog box, search for the user group to which the IAM user to be synchronized belongs and click the user group name. In the <strong id="mrs_01_0495__b782312671618">User</strong> column, select the desired IAM user and click <strong id="mrs_01_0495__b8823461164">Synchronize</strong>.</span><p><div class="note" id="mrs_01_0495__note112105447346"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="mrs_01_0495__ul1211134416349"><li id="mrs_01_0495__li112111440345">You can select all users to synchronize them at a time.</li><li id="mrs_01_0495__li1434115814402">If you select user groups only, users will not be synchronized. You must select specific user names in the user group.</li><li id="mrs_01_0495__li2211114416342">All user groups are displayed. Those cannot be selected cannot be synchronized.</li></ul>
+<div class="section" id="mrs_01_0495__section1968244415315"><h4 class="sectiontitle">Procedure</h4><ol id="mrs_01_0495__ol1399115193113"><li id="mrs_01_0495__li0751526153614"><span>Create a user and authorize the user to use MRS. For details, see <a href="mrs_01_0453.html">Creating an MRS User</a>.</span></li><li id="mrs_01_0495__li1717155310510"><span>Log in to the MRS management console and create a cluster. For details, see <a href="mrs_01_0513.html">Creating a Custom Cluster</a>.</span></li><li id="mrs_01_0495__li168712054205213"><span>In the left navigation pane, choose <span class="menucascade" id="mrs_01_0495__menucascade882112551715"><b><span class="uicontrol" id="mrs_01_0495__uicontrol138252595713">Clusters</span></b> &gt; <b><span class="uicontrol" id="mrs_01_0495__uicontrol26341265817">Active Clusters</span></b></span>. Click the cluster name to go to the cluster details page.</span></li><li id="mrs_01_0495__li6999515311"><a name="mrs_01_0495__li6999515311"></a><a name="li6999515311"></a><span>In the <strong id="mrs_01_0495__b1762920331212">Basic Information</strong> area on the <span class="parmname" id="mrs_01_0495__parmname145843311212"><b>Dashboard</b></span> page, click <span class="parmvalue" id="mrs_01_0495__parmvalue132811049183612"><b>Synchronize</b></span> on the right side of <span class="parmname" id="mrs_01_0495__parmname10856123651"><b>IAM User Sync</b></span> to synchronize IAM users.</span></li><li id="mrs_01_0495__li125181329113613"><span>After a synchronization request is sent, choose <strong id="mrs_01_0495__b298011021019">Operation Logs</strong> in the left navigation pane on the MRS console to check whether the synchronization is successful. For details about the logs, see <a href="en-us_topic_0012808265.html">Viewing MRS Operation Logs</a>.</span></li><li id="mrs_01_0495__li10593415141112"><span>After the synchronization is successful, use the user synchronized with IAM to perform subsequent operations.</span><p><div class="note" id="mrs_01_0495__note33851651171910"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="mrs_01_0495__ul1768815257314"><li id="mrs_01_0495__li1468816258312">When the policy of the user group to which the IAM user belongs changes from <strong id="mrs_01_0495__b16281225153214">MRS ReadOnlyAccess</strong> to <strong id="mrs_01_0495__b9269528183211">MRS CommonOperations</strong>, <strong id="mrs_01_0495__b744510314322">MRS FullAccess</strong>, or <strong id="mrs_01_0495__b15811138173212">MRS Administrator</strong>, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the <strong id="mrs_01_0495__b2707173165617">SSSD</strong> (System Security Services Daemon) cache of cluster nodes needs time to be updated. Then, submit a job. Otherwise, the job may fail to be submitted.</li><li id="mrs_01_0495__li88202863111">When the policy of the user group to which the IAM user belongs changes from <strong id="mrs_01_0495__b510602618436">MRS CommonOperations</strong>, <strong id="mrs_01_0495__b72146296431">MRS FullAccess</strong>, or <strong id="mrs_01_0495__b3128193264315">MRS Administrator</strong> to <strong id="mrs_01_0495__b5863143618431">MRS ReadOnlyAccess</strong>, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the <strong id="mrs_01_0495__b2052564720569">SSSD</strong> cache of cluster nodes needs time to be updated.</li><li id="mrs_01_0495__li20583556151015">After you click <span class="parmvalue" id="mrs_01_0495__parmvalue5821358572"><b>Synchronize</b></span> on the right side of <span class="parmname" id="mrs_01_0495__parmname19407144435714"><b>IAM User Sync</b></span>, the cluster details page is blank for a short time, because user data is being synchronized. The page will be properly displayed after the data synchronization is complete.</li></ul>
 </div></div>
-</p></li><li id="mrs_01_0495__li125181329113613"><span>After a synchronization request is sent, choose <strong id="mrs_01_0495__b298011021019">Operation Logs</strong> in the left navigation pane on the MRS console to check whether the synchronization is successful. For details about the logs, see <a href="en-us_topic_0012808265.html">Viewing MRS Operation Logs</a>.</span></li><li id="mrs_01_0495__li10593415141112"><span>After the synchronization is successful, use the user synchronized with IAM to perform subsequent operations.</span><p><div class="note" id="mrs_01_0495__note33851651171910"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="mrs_01_0495__ul1768815257314"><li id="mrs_01_0495__li1468816258312">When the policy of the user group to which the IAM user belongs changes from <strong id="mrs_01_0495__b16281225153214">MRS ReadOnlyAccess</strong> to <strong id="mrs_01_0495__b9269528183211">MRS CommonOperations</strong>, <strong id="mrs_01_0495__b744510314322">MRS FullAccess</strong>, or <strong id="mrs_01_0495__b15811138173212">MRS Administrator</strong>, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the <strong id="mrs_01_0495__b2707173165617">SSSD</strong> (System Security Services Daemon) cache of cluster nodes needs time to be updated. Then, submit a job. Otherwise, the job may fail to be submitted.</li><li id="mrs_01_0495__li88202863111">When the policy of the user group to which the IAM user belongs changes from <strong id="mrs_01_0495__b510602618436">MRS CommonOperations</strong>, <strong id="mrs_01_0495__b72146296431">MRS FullAccess</strong>, or <strong id="mrs_01_0495__b3128193264315">MRS Administrator</strong> to <strong id="mrs_01_0495__b5863143618431">MRS ReadOnlyAccess</strong>, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the <strong id="mrs_01_0495__b2052564720569">SSSD</strong> cache of cluster nodes needs time to be updated.</li><li id="mrs_01_0495__li20583556151015">After you click <span class="parmvalue" id="mrs_01_0495__parmvalue5821358572"><b>Synchronize</b></span> on the right side of <span class="parmname" id="mrs_01_0495__parmname19407144435714"><b>IAM User Sync</b></span>, the cluster details page is blank for a short time, because user data is being synchronized. The page will be properly displayed after the data synchronization is complete.</li></ul>
-</div></div>
-<ul id="mrs_01_0495__ul1987313196114"><li id="mrs_01_0495__li5768182591113">Submitting jobs in a security cluster: Users can submit jobs using the job management function on the GUI in the security cluster. For details, see <a href="mrs_01_0052.html">Running a MapReduce Job</a>.</li><li id="mrs_01_0495__li1803195116252">All tabs are displayed on the cluster details page, including <strong id="mrs_01_0495__b790294933511">Components</strong>, <strong id="mrs_01_0495__b14902144943514">Tenants</strong>, and <strong id="mrs_01_0495__b189021649183519">Backups &amp; Restorations</strong>.</li><li id="mrs_01_0495__li6640151115167">Logging in to Manager<ol type="a" id="mrs_01_0495__ol11293181518167"><li id="mrs_01_0495__li172511719101610">Log in to Manager as user <strong id="mrs_01_0495__b8412104751111">admin</strong>. For details, see <a href="mrs_01_0128.html">Accessing Manager</a>.</li><li id="mrs_01_0495__li169901714175"><a name="mrs_01_0495__li169901714175"></a><a name="li169901714175"></a>Initialize the password of the user synchronized with IAM. For details, see <a href="mrs_01_0351.html">Initializing the Password of a System User</a>.</li><li id="mrs_01_0495__li1656212219199">Modify the role bound to the user group to which the user belongs to control user permissions on Manager. For details, see <a href="mrs_01_0344.html#mrs_01_0344__s855da92cb75446818be082dff6e197f1">Related Tasks</a>. For details about how to create and modify a role, see <a href="mrs_01_0343.html">Creating a Role</a>. After the component role bound to the user group to which the user belongs is modified, it takes some time for the role permissions to take effect.</li><li id="mrs_01_0495__li171483712172">Log in to Manager using the user synchronized with IAM and the password after the initialization in <a href="#mrs_01_0495__li169901714175">7.b</a>.</li></ol>
+<ul id="mrs_01_0495__ul1987313196114"><li id="mrs_01_0495__li5768182591113">Submitting jobs in a security cluster: Users can submit jobs using the job management function on the GUI in the security cluster. For details, see <a href="mrs_01_0052.html">Running a MapReduce Job</a>.</li><li id="mrs_01_0495__li1803195116252">All tabs are displayed on the cluster details page, including <strong id="mrs_01_0495__b790294933511">Components</strong>, <strong id="mrs_01_0495__b14902144943514">Tenants</strong>, and <strong id="mrs_01_0495__b189021649183519">Backups &amp; Restorations</strong>.</li><li id="mrs_01_0495__li6640151115167">Logging in to Manager<ol type="a" id="mrs_01_0495__ol11293181518167"><li id="mrs_01_0495__li172511719101610">Log in to Manager as user <strong id="mrs_01_0495__b8412104751111">admin</strong>. For details, see <a href="mrs_01_0128.html">Accessing Manager</a>.</li><li id="mrs_01_0495__li169901714175"><a name="mrs_01_0495__li169901714175"></a><a name="li169901714175"></a>Initialize the password of the user synchronized with IAM. For details, see <a href="mrs_01_0351.html">Initializing the Password of a System User</a>.</li><li id="mrs_01_0495__li1656212219199">Modify the role bound to the user group to which the user belongs to control user permissions on Manager. For details, see <a href="mrs_01_0344.html#mrs_01_0344__s855da92cb75446818be082dff6e197f1">Related Tasks</a>. For details about how to create and modify a role, see <a href="mrs_01_0343.html">Creating a Role</a>. After the component role bound to the user group to which the user belongs is modified, it takes some time for the role permissions to take effect.</li><li id="mrs_01_0495__li171483712172">Log in to Manager using the user synchronized with IAM and the password after the initialization in <a href="#mrs_01_0495__li169901714175">6.b</a>.</li></ol>
 <div class="note" id="mrs_01_0495__note7891115913188"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_01_0495__p5575145111357">If the IAM user's permission changes, go to <a href="#mrs_01_0495__li6999515311">4</a> to perform second synchronization. After the second synchronization, a system user's permissions are the union of the permissions defined in the IAM system policy and the permissions of roles added by the system user on Manager. After the second synchronization, a custom user's permissions are subject to the permissions configured on Manager.</p>
 <ul id="mrs_01_0495__ul1535419203441"><li id="mrs_01_0495__li1151291413274">System user: If all user groups to which an IAM user belongs are bound to system policies (RABC policies and fine-grained policies belong to system policies), the IAM user is a system user.</li><li id="mrs_01_0495__li93541220154415">Custom user: If the user group to which an IAM user belongs is bound to any custom policy, the IAM user is a custom user.</li></ul>
 </div></div>
 </li></ul>
-</p></li></ol><ol start="8" id="mrs_01_0495__ol15568816163817"><li id="mrs_01_0495__li19974196311"><span>Undo IAM user synchronization.</span><p><p id="mrs_01_0495__p378015201314">To undo the synchronization of an IAM user, select the user in the <strong id="mrs_01_0495__b63010195162">User</strong> column in the <strong id="mrs_01_0495__b430319161612">Synchronized</strong> tab and click <strong id="mrs_01_0495__b830111981616">Undo Sync</strong>.</p>
-<p id="mrs_01_0495__p9869144112315">To undo the synchronization of all users in an IAM user group, select the user group in the <strong id="mrs_01_0495__b1287052118165">User Group</strong> column in the <strong id="mrs_01_0495__b3870122119169">Synchronized</strong> tab and click <strong id="mrs_01_0495__b208702021161611">Undo Sync</strong>.</p>
 </p></li></ol>
 </div>
 </div>

docs/mrs/umn/mrs_01_0513.html

@@ -46,6 +46,14 @@
 <td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.2.3.1.2 "><p id="mrs_01_0513__p11302191119226">Currently, MRS 3.1.2-LTS.6, MRS 3.2.0-LTS.2 and MRS 3.3.0-LTS.1 are supported. The default value displayed on the UI varies depending on the version.</p>
 </td>
 </tr>
+<tr id="mrs_01_0513__row3780823165720"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.2.3.1.1 "><p id="mrs_01_0513__p197518710224">Cluster Type</p>
+</td>
+<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.2.3.1.2 "><div class="p" id="mrs_01_0513__p2978676228">The cluster types are as follows:<ul id="mrs_01_0513__ul6981207172215"><li id="mrs_01_0513__li09831579227"><strong id="mrs_01_0513__b438421415114">Analysis cluster</strong>: is used for offline data analysis and provides Hadoop components.</li><li id="mrs_01_0513__li129892719221"><strong id="mrs_01_0513__b9519472019">Streaming cluster</strong>: is used for streaming tasks and provides stream processing components.</li><li id="mrs_01_0513__li14421115332919"><strong id="mrs_01_0513__b12462142310014">Hybrid cluster</strong>: is used for both offline data analysis and streaming processing and provides Hadoop components and streaming processing components. You are advised to use a hybrid cluster to perform offline data analysis and streaming processing tasks at the same time.</li><li id="mrs_01_0513__li203010814186"><strong id="mrs_01_0513__b1435135911312">Custom</strong>: You can adjust the cluster service deployment mode based on service requirements. For details, see <a href="mrs_01_0121.html">Creating a Custom Topology Cluster</a>. </li></ul>
+</div>
+<div class="note" id="mrs_01_0513__note3116811229"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="mrs_01_0513__ul186112507468"><li id="mrs_01_0513__li1261195020464">MRS streaming clusters do not support job and file management functions.</li><li id="mrs_01_0513__li453865214610">To install all components in a cluster, select <strong id="mrs_01_0513__b796263323412">Custom</strong>.</li></ul>
+</div></div>
+</td>
+</tr>
 <tr id="mrs_01_0513__row19962132916585"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.2.3.1.1 "><p id="mrs_01_0513__p18240812214">Components</p>
 </td>
 <td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.2.3.1.2 "><p id="mrs_01_0513__p1631113286327">MRS cluster components. For details about component versions supported by different versions of MRS clusters, see <a href="mrs_08_0005.html">List of MRS Component Versions</a>.</p>
@@ -125,7 +133,7 @@
 <td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.5.3.2.3.1.2 "><p id="mrs_01_0513__p149421718154314">This parameter is valid only when <strong id="mrs_01_0513__b20882175521311">Cluster Type</strong> is set to <strong id="mrs_01_0513__b18505457111316">Custom</strong>. For details, see <a href="mrs_01_0121.html#mrs_01_0121__section126281336123311">Custom Cluster Template Description</a>.</p>
 </td>
 </tr>
-<tr id="mrs_01_0513__row180675274914"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.5.3.2.3.1.1 "><p id="mrs_01_0513__p18806145213491"><span id="mrs_01_0513__ph114861817161117">Cluster </span>Node<span id="mrs_01_0513__ph1982419292117">s</span></p>
+<tr id="mrs_01_0513__row180675274914"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.5.3.2.3.1.1 "><p id="mrs_01_0513__p18806145213491">Node Type</p>
 </td>
 <td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.5.3.2.3.1.2 "><p id="mrs_01_0513__p148141452161618">MRS provides three types of nodes:</p>
 <ul id="mrs_01_0513__ul1681485281617"><li id="mrs_01_0513__li981485214163">Master: A Master node in an MRS cluster manages the cluster, assigns executable cluster files to Core nodes, traces the execution status of each job, and monitors the DataNode running status.</li><li id="mrs_01_0513__li081413524165">Core: A Core node in a cluster processes data and stores process data in HDFS. Analysis Core nodes are created in an analysis cluster. Streaming Core nodes are created in a streaming cluster. Both analysis and streaming Core nodes are created in a hybrid cluster.</li><li id="mrs_01_0513__li108147526165">Task: A Task node in a cluster is used for computing and does not store persistent data. Yarn and Storm are mainly installed on Task nodes. Task nodes are optional, and the number of Task nodes can be zero. Analysis Task nodes are created in an analysis cluster. Streaming Task nodes are created in a streaming cluster. Both analysis and streaming Task nodes are created in a hybrid cluster.<div class="p" id="mrs_01_0513__p2081455251613"><a name="mrs_01_0513__li108147526165"></a><a name="li108147526165"></a>When the data volume change is small in a cluster but the cluster's service processing capabilities need to be remarkably and temporarily improved, add Task nodes to address the following situations:<ul id="mrs_01_0513__ul1814452121612"><li id="mrs_01_0513__li1360443813175">Service volumes temporarily increase, for example, report processing at the end of the year.</li><li id="mrs_01_0513__li781415251610">Long-term tasks must be completed in a short time, for example, some urgent analysis tasks.</li></ul>
@@ -157,7 +165,7 @@
 </div></div>
 </td>
 </tr>
-<tr id="mrs_01_0513__row556415580433"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.5.3.2.3.1.1 "><p id="mrs_01_0513__p10532152114442">Topology</p>
+<tr id="mrs_01_0513__row556415580433"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.5.3.2.3.1.1 "><p id="mrs_01_0513__p10532152114442">Topology Adjustment</p>
 </td>
 <td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.5.3.2.3.1.2 "><p id="mrs_01_0513__p253292110441">If the deployment mode in the <strong id="mrs_01_0513__b2247185420586">Common Node</strong> does not meet the requirements, set <strong id="mrs_01_0513__b7253454195817">Topology Adjustment</strong> to <strong id="mrs_01_0513__b6253954195818">Enable</strong> and adjust the instance deployment mode based on service requirements. For details, see <a href="mrs_01_0121.html#mrs_01_0121__section1948791193417">Topology Adjustment for a Custom Cluster</a>. This parameter is valid only when <strong id="mrs_01_0513__b89581125593">Cluster Type</strong> is set to <strong id="mrs_01_0513__b91201414165920">Custom</strong>.</p>
 </td>
@@ -188,7 +196,7 @@
 </td>
 <td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.6.2.2.3.1.2 "><p id="mrs_01_0513__p48390488484">Password of the Manager administrator</p>
 <p id="mrs_01_0513__p12839204894816">The following requirements must be met:</p>
-<ul id="mrs_01_0513__ul19839184874811"><li id="mrs_01_0513__li11840144820480">Must contain <span id="mrs_01_0513__ph75591438173412">12</span> to 26 characters.</li><li id="mrs_01_0513__li4840194819482">Must contain at least four of the following:<ul id="mrs_01_0513__ul178411448164811"><li id="mrs_01_0513__li484104854820">Lowercase letters</li><li id="mrs_01_0513__li118419483487">Uppercase letters</li><li id="mrs_01_0513__li484214814484">Digits</li><li id="mrs_01_0513__li38426481487">At least one of the following special characters: `~!@#$%^&amp;*()-_=+|[{}];:',&lt;.&gt;/?</li></ul>
+<ul id="mrs_01_0513__ul19839184874811"><li id="mrs_01_0513__li11840144820480">Must contain 8 to 26 characters.</li><li id="mrs_01_0513__li4840194819482">Must contain at least four of the following:<ul id="mrs_01_0513__ul178411448164811"><li id="mrs_01_0513__li484104854820">Lowercase letters</li><li id="mrs_01_0513__li118419483487">Uppercase letters</li><li id="mrs_01_0513__li484214814484">Digits</li><li id="mrs_01_0513__li38426481487">At least one of the following special characters: `~!@#$%^&amp;*()-_=+|[{}];:',&lt;.&gt;/?</li></ul>
 </li><li id="mrs_01_0513__li184224816480">Cannot be the same as the username or the username spelled backwards.</li></ul>
 <p id="mrs_01_0513__p1484210486482">Password Strength: The colorbar in red, orange, and green indicates weak, medium, and strong password, respectively.</p>
 </td>
@@ -252,19 +260,23 @@
 <p id="mrs_01_0513__p736312339211">The <strong id="mrs_01_0513__b1792986913">MRS_ECS_DEFAULT_AGENCY</strong> agency has the OBSOperateAccess permission of OBS and the CESFullAccess (for users who have enabled fine-grained policies), CES Administrator, and KMS Administrator permissions in the region where the cluster is located.</p>
 </td>
 </tr>
-<tr id="mrs_01_0513__row1367906151915"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.6.3.2.3.1.1 "><p id="mrs_01_0513__p1227121912195">Metric Sharing</p>
+<tr id="mrs_01_0513__row5222520183117"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.6.3.2.3.1.1 "><p id="mrs_01_0513__p16926825133">Data Disk Encryption</p>
 </td>
-<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.6.3.2.3.1.2 "><p id="mrs_01_0513__p127151910192">Monitoring metrics of big data components are collected. If a fault occurs when you use a cluster, share the monitoring metrics with technical support for troubleshooting.</p>
+<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.6.3.2.3.1.2 "><p id="mrs_01_0513__p1492642512315">Whether to encrypt data in the data disk mounted to the cluster. This function is disabled by default. To use this function, you must have the Security Administrator and KMS Administrator permissions. This parameter is not available for MRS 3.1.0 and MRS 3.1.2-LTS.3.</p>
+<p id="mrs_01_0513__p139271251531">Keys used by encrypted data disks are provided by the Key Management Service (KMS) of the Data Encryption Workshop (DEW), secure and convenient. Therefore, you do not need to establish and maintain the key management infrastructure.</p>
+<p id="mrs_01_0513__p29273251314">Click <span class="parmname" id="mrs_01_0513__parmname1634306059"><b>Data Disk Encryption</b></span> to enable or disable the data disk encryption function.</p>
 </td>
 </tr>
-<tr id="mrs_01_0513__row6637103344411"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.6.3.2.3.1.1 "><p id="mrs_01_0513__p551495471016">System Disk Encryption</p>
+<tr id="mrs_01_0513__row8807922111617"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.6.3.2.3.1.1 "><p id="mrs_01_0513__p490533101613">Data Disk Key ID</p>
 </td>
-<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.6.3.2.3.1.2 "><p id="mrs_01_0513__p16616174715518">Whether to encrypt data in the system disk mounted to the MRS cluster node. This function is disabled by default.</p>
-<p id="mrs_01_0513__p1441105061214">Keys used by encrypted system disks are provided by Key Management Service (KMS) in Data Encryption Workshop (DEW). You do not need to build and maintain the key management infrastructure. To enable this function, you must have the <strong id="mrs_01_0513__b143041286241">Security Administrator</strong> and <strong id="mrs_01_0513__b13525121192414">KMS Administrator</strong> permissions.</p>
-<p id="mrs_01_0513__p3292519115214">Configure the following parameters to enable this function:</p>
-<ul id="mrs_01_0513__ul149446705314"><li id="mrs_01_0513__li49441773537"><strong id="mrs_01_0513__b9801538102514">System Disk Key ID</strong>: key ID of the selected key name.</li><li id="mrs_01_0513__li793870185414"><strong id="mrs_01_0513__b205085622718">System Disk Key Name</strong>: Select the name of the key used to encrypt the data disk. By default, the default master key named <strong id="mrs_01_0513__b94805322835145">evs/default</strong> is selected. You can select another master key from the drop-down list.<p id="mrs_01_0513__p67951219547">If cloud disks are encrypted using a master key and it is then disabled or scheduled for deletion, the cloud disks can no longer be read from or written to, and data on these disks may never be restored. Exercise caution when performing this operation.</p>
-<p id="mrs_01_0513__p0590940175311">Click <span class="parmname" id="mrs_01_0513__parmname14607192651415"><b>View the Key List</b></span> to enter a page where you can create and manage keys.</p>
-</li></ul>
+<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.6.3.2.3.1.2 "><p id="mrs_01_0513__p19905332163">This parameter is displayed only when the <span class="parmname" id="mrs_01_0513__parmname2135547238"><b>Data Disk Encryption</b></span> function is enabled. This parameter indicates the key ID corresponding to the selected key name. This parameter is not available for MRS 3.1.0 and MRS 3.1.2-LTS.3.</p>
+</td>
+</tr>
+<tr id="mrs_01_0513__row16422131031711"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.6.3.2.3.1.1 "><p id="mrs_01_0513__p080216111178">Data Disk Key Name</p>
+</td>
+<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.6.3.2.3.1.2 "><p id="mrs_01_0513__p10802161121715">This parameter is mandatory when the <span class="parmname" id="mrs_01_0513__parmname451787605"><b>Data Disk Encryption</b></span> function is enabled. Select the name of the key used to encrypt the data disk. By default, the default master key named <strong id="mrs_01_0513__b241925909">evs/default</strong> is selected. You can select another master key from the drop-down list. This parameter is not available for MRS 3.1.0 and MRS 3.1.2-LTS.3.</p>
+<p id="mrs_01_0513__p178021911151718">If disks are encrypted using a CMK, which is then disabled or scheduled for deletion, the disks can no longer be read from or written to, and data on these disks may never be restored. Exercise caution when performing this operation.</p>
+<p id="mrs_01_0513__p2802111191715">Click <span class="parmname" id="mrs_01_0513__parmname552038909"><b>View Key List</b></span> to enter a page where you can create and manage keys.</p>
 </td>
 </tr>
 <tr id="mrs_01_0513__row837834410410"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.6.3.2.3.1.1 "><p id="mrs_01_0513__p1924916486420">Alarm</p>

docs/mrs/umn/mrs_01_0536.html

@@ -11,7 +11,7 @@
 </p></li><li id="mrs_01_0536__en-us_topic_0035209694_li10076998185956"><span>Modify the <strong id="mrs_01_0536__b1416643122616">default </strong>configuration group of the service pool.</span><p><ol type="a" id="mrs_01_0536__en-us_topic_0035209694_ol371752051924"><li id="mrs_01_0536__en-us_topic_0035209694_li370207371924">Click <strong id="mrs_01_0536__b2500165315405">default</strong>. In the <strong id="mrs_01_0536__b1350695315406">Service Pool Configuration</strong> table, set <strong id="mrs_01_0536__b450615537400">CPU LIMIT(%)</strong>, <strong id="mrs_01_0536__b14506253164013">CPU SHARE(%)</strong>, <strong id="mrs_01_0536__b1507195324016">I/O(%)</strong>, and <strong id="mrs_01_0536__b12507205317402">Memory(%)</strong> for the Flume, HBase, HDFS, Impala and YARN services.</li></ol>
 <div class="note" id="mrs_01_0536__en-us_topic_0035209694_note5054453919129"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="mrs_01_0536__en-us_topic_0035209694_ul6075374919139"><li id="mrs_01_0536__en-us_topic_0035209694_li2062276419139">The sum of <strong id="mrs_01_0536__b1290750152612">CPU LIMIT(%)</strong> used by all services can exceed 100%.</li><li id="mrs_01_0536__en-us_topic_0035209694_li1448592019139">The sum of <strong id="mrs_01_0536__b11161951112617">CPU SHARE(%)</strong> and <strong id="mrs_01_0536__b311645119266">I/O(%)</strong> used by all services must be 100%. For example, if CPU resources are allocated to the HDFS and Yarn services, the total CPU resources allocated to the two services are 100%.</li><li id="mrs_01_0536__en-us_topic_0035209694_li953825319139">The sum of <strong id="mrs_01_0536__b23521153102613">Memory(%)</strong> used by all services can be greater than, smaller than, or equal to 100%.</li><li id="mrs_01_0536__en-us_topic_0035209694_li4672589619139"><strong id="mrs_01_0536__b15800165442617">Memory(%)</strong> cannot take effect dynamically and can only be modified in the default configuration group.</li></ul>
 </div></div>
-<ol type="a" start="2" id="mrs_01_0536__en-us_topic_0035209694_ol1399905619253"><li id="mrs_01_0536__en-us_topic_0035209694_li6144419219258">Click in the blank area of the page to complete the editing. MRS Manager generates the correct values of service pool parameters in the <strong id="mrs_01_0536__b14555712265">Detailed Configuration</strong> area based on the cluster hardware resources and allocation information.</li><li id="mrs_01_0536__en-us_topic_0035209694_li4325598319323">You can click <span><img id="mrs_01_0536__image241019572276" src="en-us_image_0000002278456009.png"></span> on the right of <strong id="mrs_01_0536__b20181459122618">Detailed Configuration</strong> to modify the parameter values of the service pool based on service requirements.<p id="mrs_01_0536__en-us_topic_0035209694_p4064609919324">In the <strong id="mrs_01_0536__b1258213129277">Service Pool Configuration</strong> area, click the specified service name. The <strong id="mrs_01_0536__b358771216271">Detailed Configuration</strong> area displays only the parameters of the service. Manual changing of parameter values does not refresh the service resource usage. In added configuration groups, the configuration group numbers of the parameters that take effect dynamically will be displayed. For example, <strong id="mrs_01_0536__b9667101522712">HBase: RegionServer: dynamic-config1.RES_CPUSET_PERCENTAGE</strong>. The parameter functions do not change.</p>
+<ol type="a" start="2" id="mrs_01_0536__en-us_topic_0035209694_ol1399905619253"><li id="mrs_01_0536__en-us_topic_0035209694_li6144419219258">Click in the blank area of the page to complete the editing. MRS Manager generates the correct values of service pool parameters in the <strong id="mrs_01_0536__b14555712265">Detailed Configuration</strong> area based on the cluster hardware resources and allocation information.</li><li id="mrs_01_0536__en-us_topic_0035209694_li4325598319323">You can click <span><img id="mrs_01_0536__image18571738142613" src="en-us_image_0000001829060901.png"></span> on the right of <strong id="mrs_01_0536__b20181459122618">Detailed Configuration</strong> to modify the parameter values of the service pool based on service requirements.<p id="mrs_01_0536__en-us_topic_0035209694_p4064609919324">In the <strong id="mrs_01_0536__b1258213129277">Service Pool Configuration</strong> area, click the specified service name. The <strong id="mrs_01_0536__b358771216271">Detailed Configuration</strong> area displays only the parameters of the service. Manual changing of parameter values does not refresh the service resource usage. In added configuration groups, the configuration group numbers of the parameters that take effect dynamically will be displayed. For example, <strong id="mrs_01_0536__b9667101522712">HBase: RegionServer: dynamic-config1.RES_CPUSET_PERCENTAGE</strong>. The parameter functions do not change.</p>
 
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="mrs_01_0536__en-us_topic_0035209694_table1090518719336" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters of the static service pool</caption><thead align="left"><tr id="mrs_01_0536__en-us_topic_0035209694_row6120169419340"><th align="left" class="cellrowborder" valign="top" width="46.5%" id="mcps1.3.3.2.2.2.3.2.4.2.3.1.1"><p id="mrs_01_0536__en-us_topic_0035209694_p5839019519340"><strong id="mrs_01_0536__b67299191278">Parameter</strong></p>
 </th>
@@ -70,11 +70,11 @@
 </li></ol>
 </p></li><li id="mrs_01_0536__en-us_topic_0035209694_li3287335219511"><span>Add a customized resource configuration group.</span><p><ol type="a" id="mrs_01_0536__en-us_topic_0035209694_ol868577319525"><li id="mrs_01_0536__en-us_topic_0035209694_li6268931719525">Determine whether to automatically adjust resource configurations based on the time.<p id="mrs_01_0536__en-us_topic_0035209694_p2968074519530"><a name="mrs_01_0536__en-us_topic_0035209694_li6268931719525"></a><a name="en-us_topic_0035209694_li6268931719525"></a>If yes, go to <a href="#mrs_01_0536__en-us_topic_0035209694_li207277341970">3.b</a>.</p>
 <p id="mrs_01_0536__en-us_topic_0035209694_p4970967419534">If no, go to <a href="#mrs_01_0536__en-us_topic_0035209694_li5675506119820">4</a>.</p>
-</li><li id="mrs_01_0536__en-us_topic_0035209694_li207277341970"><a name="mrs_01_0536__en-us_topic_0035209694_li207277341970"></a><a name="en-us_topic_0035209694_li207277341970"></a>Click <span><img id="mrs_01_0536__en-us_topic_0035209694_image92145291386" src="en-us_image_0000001295738420.jpg"></span> to add a resource configuration group. In the <strong id="mrs_01_0536__b161802514289">Scheduling Time</strong> area, click <span><img id="mrs_01_0536__image14994789288" src="en-us_image_0000002278456193.png"></span>. The time policy configuration page is displayed.<p id="mrs_01_0536__en-us_topic_0035209694_p1625398919545">Modify the following parameters based on service requirements and click <strong id="mrs_01_0536__b2060513277284">OK</strong>.</p>
+</li><li id="mrs_01_0536__en-us_topic_0035209694_li207277341970"><a name="mrs_01_0536__en-us_topic_0035209694_li207277341970"></a><a name="en-us_topic_0035209694_li207277341970"></a>Click <span><img id="mrs_01_0536__en-us_topic_0035209694_image92145291386" src="en-us_image_0000001295738420.jpg"></span> to add a resource configuration group. In the <strong id="mrs_01_0536__b161802514289">Scheduling Time</strong> area, click <span><img id="mrs_01_0536__image19695135582618" src="en-us_image_0000001829066453.png"></span>. The time policy configuration page is displayed.<p id="mrs_01_0536__en-us_topic_0035209694_p1625398919545">Modify the following parameters based on service requirements and click <strong id="mrs_01_0536__b2060513277284">OK</strong>.</p>
 <ul id="mrs_01_0536__en-us_topic_0035209694_ul2751418019725"><li id="mrs_01_0536__en-us_topic_0035209694_li4447274519725"><strong id="mrs_01_0536__b18617123511286">Repeat</strong>: If selected, the resource configuration group runs repeatedly based on the scheduling period. If not selected, set the date and time when the configuration of the group of resources can be applied.</li><li id="mrs_01_0536__en-us_topic_0035209694_li6345143019725"><strong id="mrs_01_0536__b16477439162815">Repeat Policy</strong>: can be set to <strong id="mrs_01_0536__b17482173914281">Daily</strong>, <strong id="mrs_01_0536__b15482839142810">Weekly</strong>, and <strong id="mrs_01_0536__b748363932817">Monthly</strong>. This parameter is valid only when <strong id="mrs_01_0536__b0419124017286">Repeat</strong> is selected.</li><li id="mrs_01_0536__en-us_topic_0035209694_li5563151819725"><strong id="mrs_01_0536__b422919413286">Between</strong>: indicates the time period between the start time and end time when the resource configuration is applied. Set a unique time range. If the time range overlaps with that of an existing group of resource configuration, the time range cannot be saved. This parameter is valid only when <strong id="mrs_01_0536__b971364416288">Repeat</strong> is selected.</li></ul>
 <div class="note" id="mrs_01_0536__en-us_topic_0035209694_note5587338519734"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="mrs_01_0536__en-us_topic_0035209694_ul5296919619740"><li id="mrs_01_0536__en-us_topic_0035209694_li1021366019740">The <strong id="mrs_01_0536__b14557145102815">default </strong>group of resource configuration takes effect in all undefined time segments.</li><li id="mrs_01_0536__en-us_topic_0035209694_li3718171619740">The newly added resource group is a parameter set that takes effect dynamically in a specified time range.</li><li id="mrs_01_0536__en-us_topic_0035209694_li958494519740">The newly added resource group can be deleted. A maximum of four resource configuration groups that take effect dynamically can be added.</li><li id="mrs_01_0536__en-us_topic_0035209694_li5237376619740">Select a repetition policy. If the end time is earlier than the start time, the next day is labeled by default. For example, if a validity period ranges from 22:00 to 06:00, the customized resource configuration takes effect from 22:00 on the current day to 06:00 on the next day.</li><li id="mrs_01_0536__en-us_topic_0035209694_li4077691419740">If the repeat policy types of multiple configuration groups are different, the time ranges can overlap. The policy types are listed as follows by priority from low to high: daily, weekly, and monthly. The following is an example. There are two resource configuration groups using the monthly and daily policies, respectively. Their application time ranges in a day overlap as follows: [04:00 to 07:00] and [06:00 to 08:00]. In this case, the configuration of the group that uses the monthly policy prevails.</li><li id="mrs_01_0536__en-us_topic_0035209694_li3710127319740">If the repeat policy types of multiple resource configuration groups are the same, the time ranges of different dates can overlap. For example, if there are two weekly scheduling groups, you can set the same time range on different day for them, such as to 04:00 to 07:00, on Monday and Wednesday, respectively.</li></ul>
 </div></div>
-</li><li id="mrs_01_0536__en-us_topic_0035209694_li855388319755">On the <strong id="mrs_01_0536__b13231145122915">Service Pool Configuration</strong> page, modify the resource configuration of each service. Click the blank area on the page to complete the editing, and go to <a href="#mrs_01_0536__en-us_topic_0035209694_li5675506119820">4</a>.<p id="mrs_01_0536__en-us_topic_0035209694_p5545326019751">You can click <span><img id="mrs_01_0536__image1164562072818" src="en-us_image_0000002243537010.png"></span> on the right of <strong id="mrs_01_0536__b88435134297">Service Pool Configuration</strong> to modify the parameters. Click <span><img id="mrs_01_0536__image9999111612818" src="en-us_image_0000002278536077.png"></span> in the <strong id="mrs_01_0536__b778023110291">Detailed Configuration</strong> area to manually update the parameter values generated by the system based on service requirements.</p>
+</li><li id="mrs_01_0536__en-us_topic_0035209694_li855388319755">On the <strong id="mrs_01_0536__b13231145122915">Service Pool Configuration</strong> page, modify the resource configuration of each service. Click the blank area on the page to complete the editing, and go to <a href="#mrs_01_0536__en-us_topic_0035209694_li5675506119820">4</a>.<p id="mrs_01_0536__en-us_topic_0035209694_p5545326019751">You can click <span><img id="mrs_01_0536__image5801971278" src="en-us_image_0000001829186485.png"></span> on the right of <strong id="mrs_01_0536__b88435134297">Service Pool Configuration</strong> to modify the parameters. Click <span><img id="mrs_01_0536__image1917020572713" src="en-us_image_0000001782506694.png"></span> in the <strong id="mrs_01_0536__b778023110291">Detailed Configuration</strong> area to manually update the parameter values generated by the system based on service requirements.</p>
 </li></ol>
 </p></li><li id="mrs_01_0536__en-us_topic_0035209694_li5675506119820"><a name="mrs_01_0536__en-us_topic_0035209694_li5675506119820"></a><a name="en-us_topic_0035209694_li5675506119820"></a><span>Saves the settings.</span><p><p id="mrs_01_0536__en-us_topic_0035209694_p6187704619835">Click <strong id="mrs_01_0536__b1790904518293">Save</strong>. In the <strong id="mrs_01_0536__b09151945162918">Save Configuration</strong> dialog box, select <strong id="mrs_01_0536__b10915134519291">Restart the affected services or instances</strong>. Click <strong id="mrs_01_0536__b219914471294">OK </strong>to save the settings and restart related services.</p>
 <p id="mrs_01_0536__en-us_topic_0035209694_p4598484319835"><strong id="mrs_01_0536__b2919104820297">Operation succeeded</strong> is displayed. click <strong id="mrs_01_0536__b153181050152912">Finish</strong>. The service is started successfully.</p>

docs/mrs/umn/mrs_01_0547.html

@@ -5,7 +5,7 @@
 </div>
 <div class="section" id="mrs_01_0547__en-us_topic_0035271549_section3962351620239"><h4 class="sectiontitle">Prerequisites</h4><p id="mrs_01_0547__en-us_topic_0035271549_p1570718520232">A tenant associated with Yarn and allocated dynamic resources has been added.</p>
 </div>
-<div class="section" id="mrs_01_0547__en-us_topic_0035271549_section61061662030"><h4 class="sectiontitle">Procedure</h4><ol id="mrs_01_0547__en-us_topic_0035271549_ol606446202036"><li id="mrs_01_0547__en-us_topic_0035271549_li267199042036"><span>On MRS Manager, click <strong id="mrs_01_0547__b205968275446">Tenant</strong>.</span></li><li id="mrs_01_0547__en-us_topic_0035271549_li209420022036"><span>Click the <strong id="mrs_01_0547__b11974328174410">Dynamic Resource Plan</strong> tab.</span></li><li id="mrs_01_0547__en-us_topic_0035271549_li317648142036"><span>Click the <strong id="mrs_01_0547__b1336813119443">Queue Configuration</strong> tab.</span></li><li id="mrs_01_0547__en-us_topic_0035271549_li548648332036"><span>In the tenant queue table, click <span class="uicontrol" id="mrs_01_0547__uicontrol196314330441"><b>Modify</b></span> in the <strong id="mrs_01_0547__b16433320446">Operation</strong> column of the specified tenant queue.</span><p><div class="note" id="mrs_01_0547__en-us_topic_0035271549_note4344592120355"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_01_0547__en-us_topic_0035271549_p5546897720355">In the tenant list on the left of the <strong id="mrs_01_0547__b15870740124413">Tenant Management</strong> tab, click the target tenant. In the window that is displayed, choose <strong id="mrs_01_0547__b1877194019441">Resource</strong>. On the page that is displayed, click <span><img id="mrs_01_0547__image241019572276" src="en-us_image_0000002278903341.png"></span> to open the queue modification page.</p>
+<div class="section" id="mrs_01_0547__en-us_topic_0035271549_section61061662030"><h4 class="sectiontitle">Procedure</h4><ol id="mrs_01_0547__en-us_topic_0035271549_ol606446202036"><li id="mrs_01_0547__en-us_topic_0035271549_li267199042036"><span>On MRS Manager, click <strong id="mrs_01_0547__b205968275446">Tenant</strong>.</span></li><li id="mrs_01_0547__en-us_topic_0035271549_li209420022036"><span>Click the <strong id="mrs_01_0547__b11974328174410">Dynamic Resource Plan</strong> tab.</span></li><li id="mrs_01_0547__en-us_topic_0035271549_li317648142036"><span>Click the <strong id="mrs_01_0547__b1336813119443">Queue Configuration</strong> tab.</span></li><li id="mrs_01_0547__en-us_topic_0035271549_li548648332036"><span>In the tenant queue table, click <span class="uicontrol" id="mrs_01_0547__uicontrol196314330441"><b>Modify</b></span> in the <strong id="mrs_01_0547__b16433320446">Operation</strong> column of the specified tenant queue.</span><p><div class="note" id="mrs_01_0547__en-us_topic_0035271549_note4344592120355"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_01_0547__en-us_topic_0035271549_p5546897720355">In the tenant list on the left of the <strong id="mrs_01_0547__b15870740124413">Tenant Management</strong> tab, click the target tenant. In the window that is displayed, choose <strong id="mrs_01_0547__b1877194019441">Resource</strong>. On the page that is displayed, click <span><img id="mrs_01_0547__image1917020572713" src="en-us_image_0000001782347050.png"></span> to open the queue modification page.</p>
 </div></div>
 
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="mrs_01_0547__en-us_topic_0035271549_table4944872120414" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Queue configuration parameters</caption><thead align="left"><tr id="mrs_01_0547__en-us_topic_0035271549_row5801156820414"><th align="left" class="cellrowborder" valign="top" width="30.5%" id="mcps1.3.3.2.4.2.2.2.3.1.1"><p id="mrs_01_0547__en-us_topic_0035271549_p131655020414"><strong id="mrs_01_0547__b122279284513">Parameter</strong></p>

docs/mrs/umn/mrs_01_0768.html

@@ -52,7 +52,7 @@
 </li><li id="mrs_01_0768__li916515534175">Run <strong id="mrs_01_0768__b125133509164">exit</strong> to exit the client.</li></ol>
 </li><li id="mrs_01_0768__li163715156">For security clusters with Kerberos authentication enabled<ol type="a" id="mrs_01_0768__ol1452811171911"><li id="mrs_01_0768__li251015403210"><a name="mrs_01_0768__li251015403210"></a><a name="li251015403210"></a>Log in to MRS Manager and create a role with the Hive Admin Privilege permissions, for example, <strong id="mrs_01_0768__b12745124612612">prestorole</strong>. For details about how to create a role, see <a href="mrs_01_0343.html">Creating a Role</a>.</li><li id="mrs_01_0768__li55542531841"><a name="mrs_01_0768__li55542531841"></a><a name="li55542531841"></a>Create a user that belongs to the Presto and Hive groups and bind the role created in <a href="#mrs_01_0768__li251015403210">6.a</a> to the user, for example, <strong id="mrs_01_0768__b15368515614">presto001</strong>. For details about how to create a user, see <a href="mrs_01_0345.html">Creating a User</a>.</li><li id="mrs_01_0768__li19959121416512">Authenticate the current user.<p id="mrs_01_0768__p10138151815517"><a name="mrs_01_0768__li19959121416512"></a><a name="li19959121416512"></a><b><span class="cmdname" id="mrs_01_0768__cmdname1014424710">kinit presto001</span></b></p>
 </li><li id="mrs_01_0768__li179713453812">Download the user credential.<ol class="substepthirdol" id="mrs_01_0768__ol16243193163811"><li id="mrs_01_0768__li113442161795">For MRS 3.x earlier, on MRS Manager, choose <strong id="mrs_01_0768__b13142154118133">System</strong> &gt; <strong id="mrs_01_0768__b714410415138">Manage User</strong>. In the row of the new user, choose <strong id="mrs_01_0768__b91442041201315">More</strong> &gt; <strong id="mrs_01_0768__b15145141131312">Download Authentication Credential</strong>.<div class="fignone" id="mrs_01_0768__fig101744231123"><span class="figcap"><b>Figure 5 </b>Downloading the Presto user authentication credential</span><br><span><img id="mrs_01_0768__image4894581220" src="en-us_image_0000001349057901.png"></span></div>
-</li><li id="mrs_01_0768__li056114501436">On <span id="mrs_01_0768__text947920520358">MRS</span> Manager for MRS 3.x or later, choose <strong id="mrs_01_0768__b693551123911">System &gt; Permission &gt; User</strong>. In the row that contains the newly added user, click <strong id="mrs_01_0768__b1167918514019">More &gt; Download Authentication Credential</strong>.<div class="fignone" id="mrs_01_0768__fig855205014432"><span class="figcap"><b>Figure 6 </b>Downloading the Presto user authentication credential</span><br><span><img id="mrs_01_0768__image1260143920433" src="en-us_image_0000001296058088.png"></span></div>
+</li><li id="mrs_01_0768__li056114501436">On <span id="mrs_01_0768__text947920520358">MRS</span> Manager for MRS 3.x or later,, choose <strong id="mrs_01_0768__b693551123911">System &gt; Permission &gt; User</strong>. In the row that contains the newly added user, click <strong id="mrs_01_0768__b1167918514019">More &gt; Download Authentication Credential</strong>.<div class="fignone" id="mrs_01_0768__fig855205014432"><span class="figcap"><b>Figure 6 </b>Downloading the Presto user authentication credential</span><br><span><img id="mrs_01_0768__image1260143920433" src="en-us_image_0000001296058088.png"></span></div>
 </li></ol>
 </li><li id="mrs_01_0768__li65281811161910"><a name="mrs_01_0768__li65281811161910"></a><a name="li65281811161910"></a>Decompress the downloaded user credential file, and save the obtained <span class="parmvalue" id="mrs_01_0768__parmvalue19703191220140"><b>krb5.conf</b></span> and <span class="parmvalue" id="mrs_01_0768__parmvalue8715171281411"><b>user.keytab</b></span> files to the client directory, for example, <span class="parmvalue" id="mrs_01_0768__parmvalue371718126144"><b>/opt/Bigdata/client/Presto/</b></span>.</li><li id="mrs_01_0768__li165280118198"><a name="mrs_01_0768__li165280118198"></a><a name="li165280118198"></a>Run the following command to obtain a user principal:<p id="mrs_01_0768__p984910411453"><a name="mrs_01_0768__li165280118198"></a><a name="li165280118198"></a><b><span class="cmdname" id="mrs_01_0768__cmdname196551137181310">klist -kt /opt/Bigdata/client/Presto/user.keytab</span></b></p>
 </li><li id="mrs_01_0768__li19528101114196">For clusters with Kerberos authentication enabled, run the following command to connect to the Presto Server of the cluster:<p id="mrs_01_0768__p1599493212018"><a name="mrs_01_0768__li19528101114196"></a><a name="li19528101114196"></a><b><span class="cmdname" id="mrs_01_0768__cmdname9978943111512">presto_cli.sh --krb5-config-path {krb5.conf file path} --krb5-principal {user principal} --krb5-keytab-path {user.keytab file path} --user {presto username}</span></b></p>

docs/mrs/umn/mrs_01_248997.html

@@ -8,7 +8,7 @@
 </li><li id="mrs_01_248997__en-us_topic_0000001657144846_li127819023915">Create a directory in the OBS file system.<p id="mrs_01_248997__en-us_topic_0000001657144846_p9937201816153"><a name="mrs_01_248997__en-us_topic_0000001657144846_li127819023915"></a><a name="en-us_topic_0000001657144846_li127819023915"></a><strong id="mrs_01_248997__en-us_topic_0000001657144846_b1480962713593">hdfs dfs -mkdir obs://</strong><em id="mrs_01_248997__en-us_topic_0000001657144846_i16809027175919">OBS parallel file system name</em><em id="mrs_01_248997__en-us_topic_0000001657144846_i138103272598">/hadoop1</em></p>
 </li><li id="mrs_01_248997__en-us_topic_0000001657144846_li15996457161612">Execute the Yarn task to access OBS.<p id="mrs_01_248997__en-us_topic_0000001657144846_p10292319175"><a name="mrs_01_248997__en-us_topic_0000001657144846_li15996457161612"></a><a name="en-us_topic_0000001657144846_li15996457161612"></a><strong id="mrs_01_248997__en-us_topic_0000001657144846_b8395113918123">yarn jar </strong><em id="mrs_01_248997__en-us_topic_0000001657144846_i1339512398125">Client installation directory</em><strong id="mrs_01_248997__en-us_topic_0000001657144846_b12396183919120">/HDFS/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar pi -Dmapreduce.job.hdfs-servers=NAMESERVICE  -fs obs://</strong><em id="mrs_01_248997__en-us_topic_0000001657144846_i1339743991218">OBS parallel file system name</em><strong id="mrs_01_248997__en-us_topic_0000001657144846_b83971139141216"> 1 1</strong></p>
 </li></ul>
-<p id="mrs_01_248997__en-us_topic_0000001657144846_p7885187121011"><strong id="mrs_01_248997__en-us_topic_0000001657144846_b10324202391312">NAMESERVICE</strong> indicates the NameService in HDFS. The default value is <strong id="mrs_01_248997__en-us_topic_0000001657144846_b15692832171319">hdfs://hacluster</strong>. If there are multiple NameServices, separate them with <strong id="mrs_01_248997__en-us_topic_0000001657144846_b124768405476">",</strong>".</p>
+<p id="mrs_01_248997__en-us_topic_0000001657144846_p7885187121011"><strong id="mrs_01_248997__en-us_topic_0000001657144846_b10324202391312">NAMESERVICE</strong> indicates the NameService in HDFS. The default value is <strong id="mrs_01_248997__en-us_topic_0000001657144846_b15692832171319">hdfs://hacluster</strong>. If there are multiple NameServices, separate them with <strong id="mrs_01_248997__en-us_topic_0000001657144846_b124768405476">,</strong>.</p>
 <p id="mrs_01_248997__en-us_topic_0000001657144846_p136841127205617">The following command is an example:</p>
 <p id="mrs_01_248997__en-us_topic_0000001657144846_p7201517184819"><strong id="mrs_01_248997__en-us_topic_0000001657144846_b208853711016">yarn jar /opt/hadoopclient/HDFS/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar pi -Dmapreduce.job.hdfs-servers=hdfs://hacluster  -fs obs://bucketname</strong><strong id="mrs_01_248997__en-us_topic_0000001657144846_b78857701019"> 1 1</strong></p>
 <ul id="mrs_01_248997__en-us_topic_0000001657144846_ul1321352941818"><li id="mrs_01_248997__en-us_topic_0000001657144846_li13213172981814">Run the following command to write data to OBS:<p id="mrs_01_248997__en-us_topic_0000001657144846_p15849918191911"><a name="mrs_01_248997__en-us_topic_0000001657144846_li13213172981814"></a><a name="en-us_topic_0000001657144846_li13213172981814"></a><strong id="mrs_01_248997__en-us_topic_0000001657144846_b15491214131912">yarn jar </strong><em id="mrs_01_248997__en-us_topic_0000001657144846_i1464717159188">Client installation directory</em><strong id="mrs_01_248997__en-us_topic_0000001657144846_b1655013144192">/HDFS/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar teragen 100 obs://</strong><em id="mrs_01_248997__en-us_topic_0000001657144846_i4939138141912">OBS parallel file system name</em><strong id="mrs_01_248997__en-us_topic_0000001657144846_b165021115161916">/hadoop1/teragen1</strong></p>

docs/mrs/umn/mrs_01_9003.html

@@ -8,23 +8,7 @@
 </th>
 </tr>
 </thead>
-<tbody><tr id="mrs_01_9003__row64952129612"><td class="cellrowborder" valign="top" width="25.19%" headers="mcps1.3.1.2.3.1.1 "><p id="mrs_01_9003__p1734422813616"><span id="mrs_01_9003__ph1034412818617">2025-06-11</span></p>
-</td>
-<td class="cellrowborder" valign="top" width="74.81%" headers="mcps1.3.1.2.3.1.2 "><p id="mrs_01_9003__p183066580610">Added the operations to interconnect MRS with LTS. For details, see <a href="mrs_03_1244.html">How Do I Interconnect MRS with LTS?</a></p>
-</td>
-</tr>
-<tr id="mrs_01_9003__row546018223489"><td class="cellrowborder" valign="top" width="25.19%" headers="mcps1.3.1.2.3.1.1 "><p id="mrs_01_9003__p164601022124818">2025-04-18</p>
-</td>
-<td class="cellrowborder" valign="top" width="74.81%" headers="mcps1.3.1.2.3.1.2 "><p id="mrs_01_9003__p1946016222489">Optimized the image format.</p>
-</td>
-</tr>
-<tr id="mrs_01_9003__row16700116122918"><td class="cellrowborder" valign="top" width="25.19%" headers="mcps1.3.1.2.3.1.1 "><p id="mrs_01_9003__p47001216122913"><span id="mrs_01_9003__ph19273152962916">2025-03-14</span></p>
-</td>
-<td class="cellrowborder" valign="top" width="74.81%" headers="mcps1.3.1.2.3.1.2 "><p id="mrs_01_9003__p5700141613298"><span id="mrs_01_9003__ph81911346192918">Modified the following content:</span></p>
-<ul id="mrs_01_9003__ul93223352348"><li id="mrs_01_9003__li16322113514341">Modified description about IAM user synchronization. For details, see <a href="mrs_01_0495.html">Synchronizing IAM Users to MRS</a>.</li><li id="mrs_01_9003__li163221935123417">Modified the descriptions of some parameters for configuring a cluster. For details, see <a href="mrs_01_0513.html">Creating a Custom Cluster</a></li><li id="mrs_01_9003__li04701916121314">Deleted descriptions about the SM algorithm. For details, see <a href="admin_guide_000272.html">Hardening Policies</a>.</li></ul>
-</td>
-</tr>
-<tr id="mrs_01_9003__row14232035161717"><td class="cellrowborder" valign="top" width="25.19%" headers="mcps1.3.1.2.3.1.1 "><p id="mrs_01_9003__p4423835131710">2024-08-02</p>
+<tbody><tr id="mrs_01_9003__row14232035161717"><td class="cellrowborder" valign="top" width="25.19%" headers="mcps1.3.1.2.3.1.1 "><p id="mrs_01_9003__p4423835131710">2024-08-02</p>
 </td>
 <td class="cellrowborder" valign="top" width="74.81%" headers="mcps1.3.1.2.3.1.2 "><p id="mrs_01_9003__p616383192012">Modified the following content:</p>
 <ul id="mrs_01_9003__ul6775145901914"><li id="mrs_01_9003__li169914011198">Fixed link errors in some sections.</li><li id="mrs_01_9003__li7775359131919">Added components and version information for MRS 3.3.0-LTS.1. For details, see <a href="mrs_08_0005.html">List of MRS Component Versions</a>.</li><li id="mrs_01_9003__li3312545591">Added Creating a Doris Cluster. For details, see <a href="mrs_01_249283.html">Quickly Creating a Doris Cluster</a></li><li id="mrs_01_9003__li287112310019">Modified the descriptions of some parameters for configuring a cluster. For details, see <a href="mrs_01_0027.html">Creating a Cluster</a>, <a href="mrs_01_0512.html">Quick Creation of a Hadoop Analysis Cluster</a>, <a href="mrs_01_0496.html">Quick Creation of an HBase Analysis Cluster</a>, <a href="mrs_01_2354.html">Quick Creation of a ClickHouse Cluster</a>, <a href="mrs_01_2355.html">Quick Creation of a Real-time Analysis Cluster</a>, <a href="mrs_01_0513.html">Creating a Custom Cluster</a> and <a href="mrs_01_0121.html">Creating a Custom Topology Cluster</a>.</li><li id="mrs_01_9003__li109703445294">Added descriptions about adding a tag to a cluster/node. For details, see <a href="mrs_01_0048.html">Adding a Tag to a Cluster/Node</a>.</li><li id="mrs_01_9003__li4419152517151">Modified descriptions about storage and compute decoupling, adjusted the sections, and added Guardian-based storage and compute decoupling. For details, see <a href="mrs_01_0440.html">Configuring a Cluster with Storage and Compute Decoupled</a>.</li><li id="mrs_01_9003__li1733101117226">The following functions are modified on FusionInsight Manager:<ul id="mrs_01_9003__ul1441019293226"><li id="mrs_01_9003__li141582441904">The home page of Manager is changed. You can download the client and start or stop a cluster on the home page. For details, see <a href="admin_guide_000010.html">Cluster Management</a>.</li><li id="mrs_01_9003__li13805810125619">The monitoring indicator data report supports the change of the user-defined time length. For details, see <a href="admin_guide_000006.html">Home Page</a>.</li><li id="mrs_01_9003__li15423145917136">You can view the monitoring metric values in <strong id="mrs_01_9003__b36131255143">Additional Information</strong> if thresholds are set for the metrics to generate alarms. For details, see <a href="admin_guide_000069.html">Alarms</a>.</li><li id="mrs_01_9003__li2071864091510">When downloading logs on Manager, you can configure the <strong id="mrs_01_9003__b14504436151416">Max. Concurrent Nodes</strong>. For details, see <a href="admin_guide_000075.html">Log Download</a>.</li><li id="mrs_01_9003__li120152617234">Configure parameters on FusionInsight Manager. On some configuration pages, you do not need to manually select the current cluster name. For example,<span id="mrs_01_9003__ph1643305811542"> </span><a href="admin_guide_000101.html">Adding a Tenant</a>.</li></ul>

docs/mrs/umn/mrs_03_1244.html

@@ -1,50 +0,0 @@
-<a name="mrs_03_1244"></a><a name="mrs_03_1244"></a>
-
-<h1 class="topictitle1">How Do I Interconnect MRS with LTS?</h1>
-<div id="body0000001338914418"><div class="section" id="mrs_03_1244__section1475974782616"><h4 class="sectiontitle">Prerequisites</h4><p id="mrs_03_1244__p0824186172716">You have obtained the account AK and SK. For details, see <a href="https://docs.otc.t-systems.com/identity-access-management/mycredential/how_do_i_manage_access_keys.html" target="_blank" rel="noopener noreferrer">How Do I Manage Access Keys?</a></p>
-</div>
-<div class="section" id="mrs_03_1244__section10392150171710"><h4 class="sectiontitle">Procedure</h4><ol id="mrs_03_1244__ol1567887416"><li id="mrs_03_1244__li95619136447"><a name="mrs_03_1244__li95619136447"></a><a name="li95619136447"></a>Install ICAgent on the MRS node. For details, see <a href="https://docs.otc.t-systems.com/log-tank-service/umn/getting_started/installing_icagent.html" target="_blank" rel="noopener noreferrer">Installing ICAgent</a>.<div class="note" id="mrs_03_1244__note429211292810"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_03_1244__p829319125286">For the first installation, install one server first, and then batch install all other hosts in the same way.</p>
-</div></div>
-</li><li id="mrs_03_1244__li11114745132412"><a name="mrs_03_1244__li11114745132412"></a><a name="li11114745132412"></a>Create a host group and add the ICAgent host installed in <a href="#mrs_03_1244__li95619136447">1</a> to the host group.<ol type="a" id="mrs_03_1244__ol26411107267"><li id="mrs_03_1244__li126412102262">Log in to the Log Tank Service (LTS) console, and choose <strong id="mrs_03_1244__b21229045604230">Host Management</strong> in the left navigation pane. On the displayed page, click <strong id="mrs_03_1244__b8798380104230">Create Host Group</strong> in the upper right corner.</li><li id="mrs_03_1244__li87161433162614">In the <strong id="mrs_03_1244__b1840110210209">Create Host Group</strong> slide-out panel that is displayed, enter a host group name in the <strong id="mrs_03_1244__b74015282019">Host Group</strong> field and set <strong id="mrs_03_1244__b15402122112017">Host OS</strong> to <strong id="mrs_03_1244__b9437155417279">Linux</strong> or <strong id="mrs_03_1244__b04025214208">Windows</strong>.</li><li id="mrs_03_1244__li116381949172611">In the host list, select one or more hosts to add to the group and click <strong id="mrs_03_1244__b13049755104230">OK</strong>.<ul id="mrs_03_1244__ul162151727271"><li id="mrs_03_1244__li22157211273">You can filter hosts by host name or host IP address. You can also click <strong id="mrs_03_1244__b24541216104611">Search by Host IP Address</strong> and enter multiple host IP addresses in the displayed search box to search for matches.</li><li id="mrs_03_1244__li1872719345289">If your desired hosts are not in the list, click <strong id="mrs_03_1244__b6076914454230">Install ICAgent</strong>. In the <strong id="mrs_03_1244__b74538338484">Install ICAgent</strong> slide-out panel displayed, install ICAgent on the hosts as prompted.</li></ul>
-</li></ol>
-</li><li id="mrs_03_1244__li14896202013307">Create a log group.<ol type="a" id="mrs_03_1244__ol2521102514615"><li id="mrs_03_1244__li7521122514466">Log in to the LTS console. On the <strong id="mrs_03_1244__b6886120133015">Log Management</strong> page, click <strong id="mrs_03_1244__b78861602308">Create Log Group</strong>.</li><li id="mrs_03_1244__li1059710614477">In the <strong id="mrs_03_1244__b20137820165415">Create Log Group</strong> slide-out panel displayed, enter a log group name. A log group name:<ul id="mrs_03_1244__ul12665151616482"><li id="mrs_03_1244__li1665131614485">Can contain only letters, numbers, hyphens (-), underscores (_), and periods (.).</li><li id="mrs_03_1244__li19665181644817">Cannot start with a period (.) or underscore (_), and cannot end with a period (.).</li><li id="mrs_03_1244__li566581616484">Can contain 1 to 64 characters.</li></ul>
-</li><li id="mrs_03_1244__li74781135451">Select an enterprise project. You can click <strong id="mrs_03_1244__b19161258359">View Enterprise Projects</strong> to view all enterprise projects.</li><li id="mrs_03_1244__li78063374817">Set <strong id="mrs_03_1244__b18768182472516">Log Retention Duration</strong>. The system stores logs for 30 days by default. You can change the log retention duration after the log group is created.<p id="mrs_03_1244__p0971355154814">LTS offers a free quota of 500 MB per month for log read/write, retention, and indexing. When the free quota is used up, you will be billed for excess usage on a pay-per-use basis.</p>
-</li><li id="mrs_03_1244__li1485783034818">Click <strong id="mrs_03_1244__b12520272184230">OK</strong>.<ul id="mrs_03_1244__ul085716305488"><li id="mrs_03_1244__li7857330184815">On the <strong id="mrs_03_1244__b2287104553112">Log Management</strong> page, you can view log group details, including name, retention duration, creation time, creation type, and tags. You can also modify retention duration and tags. Click <strong id="mrs_03_1244__b138927526316">Modify</strong> in the <strong id="mrs_03_1244__b2892552183117">Operation</strong> column of the log group to modify the name and retention duration.</li><li id="mrs_03_1244__li14857430184813">Click the log group name to access the log stream details page.</li></ul>
-</li></ol>
-</li><li id="mrs_03_1244__li20459104510490">Create a log stream.<ol type="a" id="mrs_03_1244__ol12701851174912"><li id="mrs_03_1244__li4456121445019">On the LTS console, click the expansion button of a log group.</li><li id="mrs_03_1244__li6456101416508">Click <strong id="mrs_03_1244__b1895471181112">Create Log Stream</strong>. In the <strong id="mrs_03_1244__b17498581116">Create Log Stream</strong> slide-out panel displayed, enter a log stream name. A log stream name:<ul id="mrs_03_1244__ul17978183995111"><li id="mrs_03_1244__li4978539115110">Can contain only letters, numbers, hyphens (-), underscores (_), and periods (.).</li><li id="mrs_03_1244__li1697843911516">Cannot start with a period (.) or underscore (_), and cannot end with a period (.).</li><li id="mrs_03_1244__li20978183914514">Can contain 1 to 64 characters.</li></ul>
-</li><li id="mrs_03_1244__li9978173915511">Select an enterprise project. You can click <strong id="mrs_03_1244__b4241355191213">View Enterprise Projects</strong> to view all enterprise projects.</li><li id="mrs_03_1244__li1769993525013">Click <strong id="mrs_03_1244__b11354357614230">OK</strong>.<p id="mrs_03_1244__p869919352508">On the log stream page, you can view details of the log stream, including log stream name, enterprise project, log retention duration, creation time, and creation type.</p>
-<div class="note" id="mrs_03_1244__note2545012195215"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_03_1244__p1254641275218">You can configure different log streams for different components.</p>
-</div></div>
-</li></ol>
-</li><li id="mrs_03_1244__li1471152010531">Add hosts for log ingestion.<ol type="a" id="mrs_03_1244__ol2031611165410"><li id="mrs_03_1244__li8583553192918">In the navigation pane of the LTS management console, choose <strong id="mrs_03_1244__b321162914323">Log Ingestion</strong> &gt; <strong id="mrs_03_1244__b5666143114326">Ingestion Center</strong>.</li><li id="mrs_03_1244__li831611145419">On the <strong id="mrs_03_1244__b131291332357">All</strong> tab page displayed, click <strong id="mrs_03_1244__b92747910354">Elastic Cloud Server (ECS)</strong>.</li><li id="mrs_03_1244__li113831925164218">In the <strong id="mrs_03_1244__b14971526113316">Select Log Stream</strong> step, set <strong id="mrs_03_1244__b260110311339">Log Group</strong> and <strong id="mrs_03_1244__b12171635103314">Log Stream</strong> to the created log group and log stream name, and click <strong id="mrs_03_1244__b086919394334">Next</strong>.</li><li id="mrs_03_1244__li1958281724516">In the <strong id="mrs_03_1244__b4605114117399">(Optional) Select Host Group</strong> step, select the host group created in <a href="#mrs_03_1244__li11114745132412">2</a> and click <strong id="mrs_03_1244__b1638165810393">Next</strong>.</li><li id="mrs_03_1244__li624910419505">In the <strong id="mrs_03_1244__b76181528114011">Collections</strong> step, set <strong id="mrs_03_1244__b3637741164018">Collection Configuration Name</strong> and <strong id="mrs_03_1244__b586234912403">Collection Paths</strong>, and click <strong id="mrs_03_1244__b02635704015">Next</strong>.<div class="note" id="mrs_03_1244__note117255718419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_03_1244__p47345714115">Path configurations</p>
-<ul id="mrs_03_1244__ul18731957194116"><li id="mrs_03_1244__li5297105542315">You can configure multiple collection paths by clicking <strong id="mrs_03_1244__b128475210428">Add Collection Path</strong>.</li><li id="mrs_03_1244__li1273105754118">Each collection path must be unique. That is, the same path of the same host cannot be configured for different log groups and log streams.</li><li id="mrs_03_1244__li173195714417">Collection paths support recursion. You can use double asterisks (**) to collect logs from up to five directory levels.</li><li id="mrs_03_1244__li273185713416">Collection paths support fuzzy match. You can use an asterisk (*) to represent one or more characters of a directory or file name.</li><li id="mrs_03_1244__li373185774110">If the collection path is set to a directory (such as <strong id="mrs_03_1244__b20962750163015">/var/logs/</strong>), only <strong id="mrs_03_1244__b189623505302">.log</strong>, <strong id="mrs_03_1244__b1596245018302">.trace</strong>, and <strong id="mrs_03_1244__b149625505301">.out</strong> files in the directory are collected.</li></ul>
-</div></div>
-<p id="mrs_03_1244__p153405326429">For example, configure the following collection paths:</p>
-<p id="mrs_03_1244__p756911874117">YARN task log path:</p>
-<pre id="mrs_03_1244__pre285533792611">/srv/BigData/*/nm/containerlogs/**/container-localizer-syslog
-/srv/BigData/*/nm/containerlogs/**/directory.info
-/srv/BigData/*/nm/containerlogs/**/launch_container.sh
-/srv/BigData/*/nm/containerlogs/**/prelaunch.err
-/srv/BigData/*/nm/containerlogs/**/prelaunch.out
-/srv/BigData/*/nm/containerlogs/**/stderr
-/srv/BigData/*/nm/containerlogs/**/stdout
-/srv/BigData/*/nm/containerlogs/**/syslog*
-/srv/BigData/*/nm/containerlogs/**/*.log</pre>
-<p id="mrs_03_1244__p19570388417">All HDFS service logs:</p>
-<pre id="mrs_03_1244__pre29281910192719">/var/log/Bigdata/audit/hdfs/jn/hdfs-audit-journalnode.log
-/var/log/Bigdata/audit/hdfs/jn/SecurityAuth.audit
-/var/log/Bigdata/hdfs/*/</pre>
-<p id="mrs_03_1244__p55711087416">Configure log collection paths for other components by referring to HDFS service logs.</p>
-</li><li id="mrs_03_1244__li14930113911561">Skip the <strong id="mrs_03_1244__b33281219145215">Index Settings</strong> step and submit.<div class="note" id="mrs_03_1244__note1485483414446"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_03_1244__p1854163410448">For details about how to configure index settings, see the <em id="mrs_03_1244__i1884321110504">Log Tank Service User Guide</em>.</p>
-</div></div>
-</li></ol>
-</li><li id="mrs_03_1244__li26915212476">View the logs.<ol type="a" id="mrs_03_1244__ol1246095264812"><li id="mrs_03_1244__li3216104919486">Log in to the LTS console and choose <strong id="mrs_03_1244__b13964125814300">Log Management</strong> in the navigation pane.</li><li id="mrs_03_1244__li17217134964817">In the <strong id="mrs_03_1244__b5351941145012">Log Group Name</strong> column, click the name of the created log group to view logs.</li></ol>
-</li></ol>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_03_2013.html">Cluster Access</a></div>
-</div>
-</div>
-

docs/mrs/umn/mrs_03_2013.html

@@ -16,8 +16,6 @@
 </li>
 <li class="ulchildlink"><strong><a href="mrs_03_1234.html">How Do I Access an MRS Cluster from a Node Outside the Cluster?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="mrs_03_1244.html">How Do I Interconnect MRS with LTS?</a></strong><br>
-</li>
 </ul>
 
 <div class="familylinks">