From 2195db241c8df8d962571f5b2fcfaad73dd6f56c Mon Sep 17 00:00:00 2001 From: "Yang, Tong" Date: Thu, 16 May 2024 09:40:21 +0000 Subject: [PATCH] MRS UMN 20231220 version update Reviewed-by: Pruthi, Vineet Reviewed-by: Rechenburg, Matthias Co-authored-by: Yang, Tong Co-committed-by: Yang, Tong --- docs/mrs/umn/ALL_META.TXT.json | 2488 ++++----- docs/mrs/umn/ALM-12001.html | 6 +- docs/mrs/umn/ALM-12004.html | 4 +- docs/mrs/umn/ALM-12005.html | 6 +- docs/mrs/umn/ALM-12006.html | 4 +- docs/mrs/umn/ALM-12007.html | 6 +- docs/mrs/umn/ALM-12010.html | 4 +- docs/mrs/umn/ALM-12011.html | 6 +- docs/mrs/umn/ALM-12012.html | 8 +- docs/mrs/umn/ALM-12014.html | 4 +- docs/mrs/umn/ALM-12015.html | 2 +- docs/mrs/umn/ALM-12016.html | 6 +- docs/mrs/umn/ALM-12017.html | 6 +- docs/mrs/umn/ALM-12018.html | 4 +- docs/mrs/umn/ALM-12027.html | 4 +- docs/mrs/umn/ALM-12028.html | 6 +- docs/mrs/umn/ALM-12033.html | 16 +- docs/mrs/umn/ALM-12034.html | 4 +- docs/mrs/umn/ALM-12035.html | 6 +- docs/mrs/umn/ALM-12037.html | 4 +- docs/mrs/umn/ALM-12038.html | 8 +- docs/mrs/umn/ALM-12039.html | 4 +- docs/mrs/umn/ALM-12040.html | 4 +- docs/mrs/umn/ALM-12041.html | 4 +- docs/mrs/umn/ALM-12042.html | 4 +- docs/mrs/umn/ALM-12045.html | 12 +- docs/mrs/umn/ALM-12046.html | 4 +- docs/mrs/umn/ALM-12047.html | 4 +- docs/mrs/umn/ALM-12048.html | 4 +- docs/mrs/umn/ALM-12049.html | 6 +- docs/mrs/umn/ALM-12050.html | 6 +- docs/mrs/umn/ALM-12051.html | 4 +- docs/mrs/umn/ALM-12052.html | 4 +- docs/mrs/umn/ALM-12053.html | 6 +- docs/mrs/umn/ALM-12054.html | 4 +- docs/mrs/umn/ALM-12055.html | 4 +- docs/mrs/umn/ALM-12057.html | 4 +- docs/mrs/umn/ALM-12061.html | 8 +- docs/mrs/umn/ALM-12062.html | 4 +- docs/mrs/umn/ALM-12063.html | 4 +- docs/mrs/umn/ALM-12064.html | 4 +- docs/mrs/umn/ALM-12066.html | 4 +- docs/mrs/umn/ALM-12067.html | 4 +- docs/mrs/umn/ALM-12068.html | 6 +- docs/mrs/umn/ALM-12069.html | 6 +- docs/mrs/umn/ALM-12070.html | 8 +- docs/mrs/umn/ALM-12071.html | 8 +- docs/mrs/umn/ALM-12072.html | 10 +- docs/mrs/umn/ALM-12073.html | 8 +- docs/mrs/umn/ALM-12074.html | 8 +- docs/mrs/umn/ALM-12075.html | 8 +- docs/mrs/umn/ALM-12076.html | 4 +- docs/mrs/umn/ALM-12077.html | 4 +- docs/mrs/umn/ALM-12078.html | 4 +- docs/mrs/umn/ALM-12079.html | 4 +- docs/mrs/umn/ALM-12080.html | 4 +- docs/mrs/umn/ALM-12081.html | 4 +- docs/mrs/umn/ALM-12082.html | 2 +- docs/mrs/umn/ALM-12083.html | 2 +- docs/mrs/umn/ALM-12084.html | 4 +- docs/mrs/umn/ALM-12085.html | 4 +- docs/mrs/umn/ALM-12087.html | 2 +- docs/mrs/umn/ALM-12089.html | 6 +- docs/mrs/umn/ALM-12101.html | 2 +- docs/mrs/umn/ALM-12102.html | 2 +- docs/mrs/umn/ALM-12103.html | 4 +- docs/mrs/umn/ALM-12104.html | 4 +- docs/mrs/umn/ALM-12110.html | 2 +- docs/mrs/umn/ALM-12172.html | 2 +- docs/mrs/umn/ALM-12180.html | 4 +- docs/mrs/umn/ALM-13000.html | 8 +- docs/mrs/umn/ALM-13001.html | 6 +- docs/mrs/umn/ALM-13002.html | 6 +- docs/mrs/umn/ALM-13003.html | 8 +- docs/mrs/umn/ALM-13004.html | 6 +- docs/mrs/umn/ALM-13005.html | 4 +- docs/mrs/umn/ALM-13006.html | 6 +- docs/mrs/umn/ALM-13007.html | 6 +- docs/mrs/umn/ALM-13008.html | 6 +- docs/mrs/umn/ALM-13009.html | 6 +- docs/mrs/umn/ALM-13010.html | 6 +- docs/mrs/umn/ALM-14000.html | 6 +- docs/mrs/umn/ALM-14001.html | 4 +- docs/mrs/umn/ALM-14002.html | 6 +- docs/mrs/umn/ALM-14003.html | 6 +- docs/mrs/umn/ALM-14006.html | 4 +- docs/mrs/umn/ALM-14007.html | 6 +- docs/mrs/umn/ALM-14008.html | 6 +- docs/mrs/umn/ALM-14009.html | 12 +- docs/mrs/umn/ALM-14010.html | 12 +- docs/mrs/umn/ALM-14011.html | 8 +- docs/mrs/umn/ALM-14012.html | 6 +- docs/mrs/umn/ALM-14013.html | 8 +- docs/mrs/umn/ALM-14014.html | 6 +- docs/mrs/umn/ALM-14015.html | 6 +- docs/mrs/umn/ALM-14016.html | 8 +- docs/mrs/umn/ALM-14017.html | 6 +- docs/mrs/umn/ALM-14018.html | 6 +- docs/mrs/umn/ALM-14019.html | 6 +- docs/mrs/umn/ALM-14020.html | 4 +- docs/mrs/umn/ALM-14021.html | 12 +- docs/mrs/umn/ALM-14022.html | 14 +- docs/mrs/umn/ALM-14023.html | 6 +- docs/mrs/umn/ALM-14024.html | 6 +- docs/mrs/umn/ALM-14025.html | 6 +- docs/mrs/umn/ALM-14026.html | 12 +- docs/mrs/umn/ALM-14027.html | 4 +- docs/mrs/umn/ALM-14028.html | 6 +- docs/mrs/umn/ALM-14029.html | 4 +- docs/mrs/umn/ALM-14030.html | 4 +- docs/mrs/umn/ALM-16000.html | 4 +- docs/mrs/umn/ALM-16001.html | 6 +- docs/mrs/umn/ALM-16002.html | 8 +- docs/mrs/umn/ALM-16003.html | 6 +- docs/mrs/umn/ALM-16004.html | 14 +- docs/mrs/umn/ALM-16005.html | 12 +- docs/mrs/umn/ALM-16006.html | 10 +- docs/mrs/umn/ALM-16007.html | 10 +- docs/mrs/umn/ALM-16008.html | 10 +- docs/mrs/umn/ALM-16009.html | 4 +- docs/mrs/umn/ALM-16047.html | 4 +- docs/mrs/umn/ALM-17003.html | 10 +- docs/mrs/umn/ALM-17004.html | 6 +- docs/mrs/umn/ALM-17005.html | 6 +- docs/mrs/umn/ALM-17006.html | 6 +- docs/mrs/umn/ALM-17007.html | 6 +- docs/mrs/umn/ALM-18000.html | 10 +- docs/mrs/umn/ALM-18002.html | 10 +- docs/mrs/umn/ALM-18003.html | 6 +- docs/mrs/umn/ALM-18008.html | 6 +- docs/mrs/umn/ALM-18009.html | 6 +- docs/mrs/umn/ALM-18010.html | 6 +- docs/mrs/umn/ALM-18011.html | 6 +- docs/mrs/umn/ALM-18012.html | 6 +- docs/mrs/umn/ALM-18013.html | 6 +- docs/mrs/umn/ALM-18014.html | 6 +- docs/mrs/umn/ALM-18015.html | 6 +- docs/mrs/umn/ALM-18016.html | 6 +- docs/mrs/umn/ALM-18017.html | 6 +- docs/mrs/umn/ALM-18018.html | 6 +- docs/mrs/umn/ALM-18019.html | 6 +- docs/mrs/umn/ALM-18020.html | 6 +- docs/mrs/umn/ALM-18021.html | 12 +- docs/mrs/umn/ALM-18022.html | 6 +- docs/mrs/umn/ALM-18023.html | 8 +- docs/mrs/umn/ALM-18024.html | 8 +- docs/mrs/umn/ALM-18025.html | 4 +- docs/mrs/umn/ALM-18026.html | 4 +- docs/mrs/umn/ALM-19000.html | 12 +- docs/mrs/umn/ALM-19006.html | 10 +- docs/mrs/umn/ALM-19007.html | 12 +- docs/mrs/umn/ALM-19008.html | 10 +- docs/mrs/umn/ALM-19009.html | 12 +- docs/mrs/umn/ALM-19011.html | 14 +- docs/mrs/umn/ALM-19012.html | 6 +- docs/mrs/umn/ALM-19013.html | 4 +- docs/mrs/umn/ALM-19014.html | 8 +- docs/mrs/umn/ALM-19015.html | 8 +- docs/mrs/umn/ALM-19016.html | 8 +- docs/mrs/umn/ALM-19017.html | 8 +- docs/mrs/umn/ALM-19018.html | 6 +- docs/mrs/umn/ALM-19019.html | 10 +- docs/mrs/umn/ALM-19020.html | 10 +- docs/mrs/umn/ALM-19021.html | 10 +- docs/mrs/umn/ALM-20002.html | 10 +- docs/mrs/umn/ALM-23001.html | 20 +- docs/mrs/umn/ALM-23003.html | 6 +- docs/mrs/umn/ALM-23004.html | 6 +- docs/mrs/umn/ALM-23005.html | 6 +- docs/mrs/umn/ALM-23006.html | 6 +- docs/mrs/umn/ALM-23007.html | 6 +- docs/mrs/umn/ALM-24000.html | 2 +- docs/mrs/umn/ALM-24001.html | 5 +- docs/mrs/umn/ALM-24003.html | 2 +- docs/mrs/umn/ALM-24004.html | 4 +- docs/mrs/umn/ALM-24005.html | 10 +- docs/mrs/umn/ALM-24006.html | 6 +- docs/mrs/umn/ALM-24007.html | 6 +- docs/mrs/umn/ALM-24008.html | 6 +- docs/mrs/umn/ALM-24009.html | 6 +- docs/mrs/umn/ALM-24010.html | 4 +- docs/mrs/umn/ALM-24011.html | 4 +- docs/mrs/umn/ALM-24012.html | 4 +- docs/mrs/umn/ALM-24013.html | 4 +- docs/mrs/umn/ALM-24014.html | 4 +- docs/mrs/umn/ALM-24015.html | 4 +- docs/mrs/umn/ALM-25000.html | 8 +- docs/mrs/umn/ALM-25004.html | 10 +- docs/mrs/umn/ALM-25005.html | 6 +- docs/mrs/umn/ALM-25006.html | 6 +- docs/mrs/umn/ALM-25500.html | 6 +- docs/mrs/umn/ALM-26051.html | 6 +- docs/mrs/umn/ALM-26052.html | 2 +- docs/mrs/umn/ALM-26053.html | 4 +- docs/mrs/umn/ALM-26054.html | 6 +- docs/mrs/umn/ALM-27001.html | 8 +- docs/mrs/umn/ALM-27003.html | 4 +- docs/mrs/umn/ALM-27004.html | 4 +- docs/mrs/umn/ALM-27005.html | 10 +- docs/mrs/umn/ALM-27006.html | 4 +- docs/mrs/umn/ALM-27007.html | 8 +- docs/mrs/umn/ALM-38000.html | 4 +- docs/mrs/umn/ALM-38001.html | 10 +- docs/mrs/umn/ALM-38002.html | 6 +- docs/mrs/umn/ALM-38004.html | 6 +- docs/mrs/umn/ALM-38005.html | 6 +- docs/mrs/umn/ALM-38006.html | 6 +- docs/mrs/umn/ALM-38007.html | 8 +- docs/mrs/umn/ALM-38008.html | 4 +- docs/mrs/umn/ALM-38009.html | 6 +- docs/mrs/umn/ALM-38010.html | 8 +- docs/mrs/umn/ALM-38011.html | 8 +- docs/mrs/umn/ALM-43001.html | 4 +- docs/mrs/umn/ALM-43006.html | 6 +- docs/mrs/umn/ALM-43007.html | 6 +- docs/mrs/umn/ALM-43008.html | 6 +- docs/mrs/umn/ALM-43009.html | 6 +- docs/mrs/umn/ALM-43010.html | 6 +- docs/mrs/umn/ALM-43011.html | 6 +- docs/mrs/umn/ALM-43012.html | 6 +- docs/mrs/umn/ALM-43013.html | 6 +- docs/mrs/umn/ALM-43017.html | 4 +- docs/mrs/umn/ALM-43018.html | 4 +- docs/mrs/umn/ALM-43019.html | 6 +- docs/mrs/umn/ALM-43020.html | 6 +- docs/mrs/umn/ALM-43021.html | 6 +- docs/mrs/umn/ALM-43022.html | 6 +- docs/mrs/umn/ALM-43023.html | 6 +- docs/mrs/umn/ALM-45000.html | 10 +- docs/mrs/umn/ALM-45001.html | 4 +- docs/mrs/umn/ALM-45175.html | 4 +- docs/mrs/umn/ALM-45176.html | 4 +- docs/mrs/umn/ALM-45177.html | 4 +- docs/mrs/umn/ALM-45178.html | 4 +- docs/mrs/umn/ALM-45179.html | 4 +- docs/mrs/umn/ALM-45180.html | 4 +- docs/mrs/umn/ALM-45181.html | 4 +- docs/mrs/umn/ALM-45182.html | 4 +- docs/mrs/umn/ALM-45275.html | 4 +- docs/mrs/umn/ALM-45276.html | 4 +- docs/mrs/umn/ALM-45277.html | 6 +- docs/mrs/umn/ALM-45278.html | 8 +- docs/mrs/umn/ALM-45279.html | 6 +- docs/mrs/umn/ALM-45280.html | 10 +- docs/mrs/umn/ALM-45281.html | 6 +- docs/mrs/umn/ALM-45282.html | 8 +- docs/mrs/umn/ALM-45283.html | 6 +- docs/mrs/umn/ALM-45284.html | 10 +- docs/mrs/umn/ALM-45285.html | 6 +- docs/mrs/umn/ALM-45286.html | 8 +- docs/mrs/umn/ALM-45287.html | 6 +- docs/mrs/umn/ALM-45288.html | 10 +- docs/mrs/umn/ALM-45425.html | 8 +- docs/mrs/umn/ALM-45426.html | 12 +- docs/mrs/umn/ALM-45427.html | 12 +- docs/mrs/umn/ALM-45428.html | 6 +- docs/mrs/umn/ALM-45429.html | 8 +- docs/mrs/umn/ALM-45430.html | 8 +- docs/mrs/umn/ALM-45431.html | 6 +- docs/mrs/umn/ALM-45432.html | 8 +- docs/mrs/umn/ALM-45433.html | 4 +- docs/mrs/umn/ALM-45434.html | 4 +- docs/mrs/umn/ALM-45585.html | 6 +- docs/mrs/umn/ALM-45586.html | 4 +- docs/mrs/umn/ALM-45587.html | 8 +- docs/mrs/umn/ALM-45588.html | 6 +- docs/mrs/umn/ALM-45589.html | 4 +- docs/mrs/umn/ALM-45590.html | 4 +- docs/mrs/umn/ALM-45591.html | 6 +- docs/mrs/umn/ALM-45592.html | 2 +- docs/mrs/umn/ALM-45593.html | 2 +- docs/mrs/umn/ALM-45594.html | 2 +- docs/mrs/umn/ALM-45595.html | 2 +- docs/mrs/umn/ALM-45615.html | 8 +- docs/mrs/umn/ALM-45616.html | 4 +- docs/mrs/umn/ALM-45617.html | 4 +- docs/mrs/umn/ALM-45640.html | 6 +- docs/mrs/umn/ALM-45641.html | 6 +- docs/mrs/umn/CLASS.TXT.json | 4552 +++++++++-------- docs/mrs/umn/admin_guide_000001.html | 8 +- docs/mrs/umn/admin_guide_000002.html | 8 +- docs/mrs/umn/admin_guide_000003.html | 8 +- docs/mrs/umn/admin_guide_000004.html | 6 +- docs/mrs/umn/admin_guide_000005.html | 4 +- docs/mrs/umn/admin_guide_000006.html | 2 +- docs/mrs/umn/admin_guide_000007.html | 6 +- docs/mrs/umn/admin_guide_000008.html | 8 +- docs/mrs/umn/admin_guide_000009.html | 2 +- docs/mrs/umn/admin_guide_000011.html | 2 +- docs/mrs/umn/admin_guide_000012.html | 2 +- docs/mrs/umn/admin_guide_000013.html | 2 +- docs/mrs/umn/admin_guide_000014.html | 4 +- docs/mrs/umn/admin_guide_000015.html | 4 +- docs/mrs/umn/admin_guide_000016.html | 4 +- docs/mrs/umn/admin_guide_000019.html | 8 +- docs/mrs/umn/admin_guide_000020.html | 4 +- docs/mrs/umn/admin_guide_000022.html | 4 +- docs/mrs/umn/admin_guide_000023.html | 4 +- docs/mrs/umn/admin_guide_000024.html | 2 +- docs/mrs/umn/admin_guide_000027.html | 2 +- docs/mrs/umn/admin_guide_000030.html | 2 +- docs/mrs/umn/admin_guide_000031.html | 2 +- docs/mrs/umn/admin_guide_000032.html | 4 +- docs/mrs/umn/admin_guide_000033.html | 4 +- docs/mrs/umn/admin_guide_000035.html | 4 +- docs/mrs/umn/admin_guide_000036.html | 6 +- docs/mrs/umn/admin_guide_000038.html | 4 +- docs/mrs/umn/admin_guide_000040.html | 8 +- docs/mrs/umn/admin_guide_000043.html | 8 +- docs/mrs/umn/admin_guide_000044.html | 4 +- docs/mrs/umn/admin_guide_000046.html | 8 +- docs/mrs/umn/admin_guide_000047.html | 4 +- docs/mrs/umn/admin_guide_000048.html | 4 +- docs/mrs/umn/admin_guide_000049.html | 2 +- docs/mrs/umn/admin_guide_000051.html | 2 +- docs/mrs/umn/admin_guide_000052.html | 2 +- docs/mrs/umn/admin_guide_000053.html | 2 +- docs/mrs/umn/admin_guide_000056.html | 4 +- docs/mrs/umn/admin_guide_000057.html | 2 +- docs/mrs/umn/admin_guide_000058.html | 8 +- docs/mrs/umn/admin_guide_000059.html | 2 +- docs/mrs/umn/admin_guide_000062.html | 4 +- docs/mrs/umn/admin_guide_000064.html | 2 +- docs/mrs/umn/admin_guide_000065.html | 2 +- docs/mrs/umn/admin_guide_000066.html | 2 +- docs/mrs/umn/admin_guide_000067.html | 2 +- docs/mrs/umn/admin_guide_000068.html | 2 +- docs/mrs/umn/admin_guide_000070.html | 4 +- docs/mrs/umn/admin_guide_000071.html | 12 +- docs/mrs/umn/admin_guide_000072.html | 6 +- docs/mrs/umn/admin_guide_000074.html | 4 +- docs/mrs/umn/admin_guide_000075.html | 4 +- docs/mrs/umn/admin_guide_000077.html | 2 +- docs/mrs/umn/admin_guide_000078.html | 4 +- docs/mrs/umn/admin_guide_000079.html | 2 +- docs/mrs/umn/admin_guide_000081.html | 4 +- docs/mrs/umn/admin_guide_000082.html | 4 +- docs/mrs/umn/admin_guide_000083.html | 4 +- docs/mrs/umn/admin_guide_000084.html | 2 +- docs/mrs/umn/admin_guide_000085.html | 2 +- docs/mrs/umn/admin_guide_000086.html | 4 +- docs/mrs/umn/admin_guide_000087.html | 2 +- docs/mrs/umn/admin_guide_000091.html | 16 +- docs/mrs/umn/admin_guide_000092.html | 4 +- docs/mrs/umn/admin_guide_000094.html | 2 +- docs/mrs/umn/admin_guide_000098.html | 2 +- docs/mrs/umn/admin_guide_000101.html | 4 +- docs/mrs/umn/admin_guide_000102.html | 4 +- docs/mrs/umn/admin_guide_000103.html | 6 +- docs/mrs/umn/admin_guide_000105.html | 10 +- docs/mrs/umn/admin_guide_000106.html | 4 +- docs/mrs/umn/admin_guide_000107.html | 4 +- docs/mrs/umn/admin_guide_000109.html | 4 +- docs/mrs/umn/admin_guide_000110.html | 4 +- docs/mrs/umn/admin_guide_000111.html | 4 +- docs/mrs/umn/admin_guide_000112.html | 4 +- docs/mrs/umn/admin_guide_000113.html | 6 +- docs/mrs/umn/admin_guide_000114.html | 4 +- docs/mrs/umn/admin_guide_000115.html | 6 +- docs/mrs/umn/admin_guide_000118.html | 4 +- docs/mrs/umn/admin_guide_000119.html | 4 +- docs/mrs/umn/admin_guide_000120.html | 6 +- docs/mrs/umn/admin_guide_000122.html | 10 +- docs/mrs/umn/admin_guide_000123.html | 4 +- docs/mrs/umn/admin_guide_000124.html | 4 +- docs/mrs/umn/admin_guide_000125.html | 8 +- docs/mrs/umn/admin_guide_000127.html | 4 +- docs/mrs/umn/admin_guide_000128.html | 4 +- docs/mrs/umn/admin_guide_000129.html | 4 +- docs/mrs/umn/admin_guide_000130.html | 4 +- docs/mrs/umn/admin_guide_000131.html | 2 +- docs/mrs/umn/admin_guide_000132.html | 4 +- docs/mrs/umn/admin_guide_000133.html | 6 +- docs/mrs/umn/admin_guide_000134.html | 2 +- docs/mrs/umn/admin_guide_000137.html | 10 +- docs/mrs/umn/admin_guide_000138.html | 4 +- docs/mrs/umn/admin_guide_000139.html | 4 +- docs/mrs/umn/admin_guide_000140.html | 4 +- docs/mrs/umn/admin_guide_000141.html | 4 +- docs/mrs/umn/admin_guide_000142.html | 4 +- docs/mrs/umn/admin_guide_000143.html | 6 +- docs/mrs/umn/admin_guide_000144.html | 4 +- docs/mrs/umn/admin_guide_000145.html | 4 +- docs/mrs/umn/admin_guide_000147.html | 4 +- docs/mrs/umn/admin_guide_000148.html | 4 +- docs/mrs/umn/admin_guide_000150.html | 14 +- docs/mrs/umn/admin_guide_000151.html | 6 +- docs/mrs/umn/admin_guide_000154.html | 4 +- docs/mrs/umn/admin_guide_000155.html | 6 +- docs/mrs/umn/admin_guide_000156.html | 6 +- docs/mrs/umn/admin_guide_000157.html | 8 +- docs/mrs/umn/admin_guide_000160.html | 10 +- docs/mrs/umn/admin_guide_000162.html | 8 +- docs/mrs/umn/admin_guide_000165.html | 4 +- docs/mrs/umn/admin_guide_000166.html | 4 +- docs/mrs/umn/admin_guide_000171.html | 4 +- docs/mrs/umn/admin_guide_000173.html | 6 +- docs/mrs/umn/admin_guide_000175.html | 4 +- docs/mrs/umn/admin_guide_000176.html | 10 +- docs/mrs/umn/admin_guide_000177.html | 10 +- docs/mrs/umn/admin_guide_000178.html | 6 +- docs/mrs/umn/admin_guide_000182.html | 4 +- docs/mrs/umn/admin_guide_000183.html | 14 +- docs/mrs/umn/admin_guide_000189.html | 14 +- docs/mrs/umn/admin_guide_000191.html | 2 +- docs/mrs/umn/admin_guide_000192.html | 2 +- docs/mrs/umn/admin_guide_000193.html | 12 +- docs/mrs/umn/admin_guide_000194.html | 2 +- docs/mrs/umn/admin_guide_000195.html | 6 +- docs/mrs/umn/admin_guide_000197.html | 4 +- docs/mrs/umn/admin_guide_000198.html | 4 +- docs/mrs/umn/admin_guide_000200.html | 6 +- docs/mrs/umn/admin_guide_000202.html | 8 +- docs/mrs/umn/admin_guide_000203.html | 6 +- docs/mrs/umn/admin_guide_000204.html | 6 +- docs/mrs/umn/admin_guide_000205.html | 8 +- docs/mrs/umn/admin_guide_000208.html | 6 +- docs/mrs/umn/admin_guide_000209.html | 6 +- docs/mrs/umn/admin_guide_000210.html | 8 +- docs/mrs/umn/admin_guide_000211.html | 6 +- docs/mrs/umn/admin_guide_000216.html | 16 +- docs/mrs/umn/admin_guide_000217.html | 8 +- docs/mrs/umn/admin_guide_000218.html | 10 +- docs/mrs/umn/admin_guide_000219.html | 12 +- docs/mrs/umn/admin_guide_000222.html | 12 +- docs/mrs/umn/admin_guide_000223.html | 10 +- docs/mrs/umn/admin_guide_000224.html | 10 +- docs/mrs/umn/admin_guide_000225.html | 10 +- docs/mrs/umn/admin_guide_000229.html | 6 +- docs/mrs/umn/admin_guide_000230.html | 4 +- docs/mrs/umn/admin_guide_000231.html | 6 +- docs/mrs/umn/admin_guide_000233.html | 2 +- docs/mrs/umn/admin_guide_000234.html | 4 +- docs/mrs/umn/admin_guide_000235.html | 6 +- docs/mrs/umn/admin_guide_000236.html | 8 +- docs/mrs/umn/admin_guide_000237.html | 2 +- docs/mrs/umn/admin_guide_000238.html | 2 +- docs/mrs/umn/admin_guide_000239.html | 10 +- docs/mrs/umn/admin_guide_000240.html | 14 +- docs/mrs/umn/admin_guide_000241.html | 6 +- docs/mrs/umn/admin_guide_000246.html | 10 +- docs/mrs/umn/admin_guide_000247.html | 10 +- docs/mrs/umn/admin_guide_000250.html | 4 +- docs/mrs/umn/admin_guide_000251.html | 2 +- docs/mrs/umn/admin_guide_000255.html | 4 +- docs/mrs/umn/admin_guide_000256.html | 4 +- docs/mrs/umn/admin_guide_000257.html | 2 +- docs/mrs/umn/admin_guide_000260.html | 2 +- docs/mrs/umn/admin_guide_000261.html | 2 +- docs/mrs/umn/admin_guide_000272.html | 2 +- docs/mrs/umn/admin_guide_000274.html | 4 +- docs/mrs/umn/admin_guide_000276.html | 8 +- docs/mrs/umn/admin_guide_000277.html | 4 +- docs/mrs/umn/admin_guide_000278.html | 2 +- docs/mrs/umn/admin_guide_000279.html | 4 +- docs/mrs/umn/admin_guide_000280.html | 4 +- docs/mrs/umn/admin_guide_000281.html | 6 +- docs/mrs/umn/admin_guide_000282.html | 2 +- docs/mrs/umn/admin_guide_000284.html | 6 +- docs/mrs/umn/admin_guide_000285.html | 2 +- docs/mrs/umn/admin_guide_000289.html | 2 +- docs/mrs/umn/admin_guide_000291.html | 2 +- docs/mrs/umn/admin_guide_000315.html | 2 +- docs/mrs/umn/admin_guide_000343.html | 6 +- docs/mrs/umn/admin_guide_000345.html | 8 +- docs/mrs/umn/admin_guide_000348.html | 8 +- docs/mrs/umn/admin_guide_000349.html | 8 +- docs/mrs/umn/admin_guide_000350.html | 4 +- docs/mrs/umn/admin_guide_000351.html | 6 +- docs/mrs/umn/admin_guide_000357.html | 8 +- docs/mrs/umn/admin_guide_000358.html | 8 +- docs/mrs/umn/admin_guide_000359.html | 10 +- docs/mrs/umn/admin_guide_000360.html | 6 +- docs/mrs/umn/admin_guide_000361.html | 8 +- docs/mrs/umn/admin_guide_000363.html | 2 +- docs/mrs/umn/admin_guide_000399.html | 6 +- docs/mrs/umn/admin_guide_000415.html | 6 +- docs/mrs/umn/en-us_image_0000001072559365.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0000001080201158.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0000001085773316.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0000001086795516.png | Bin 89216 -> 0 bytes docs/mrs/umn/en-us_image_0000001087171010.png | Bin 74602 -> 0 bytes docs/mrs/umn/en-us_image_0000001087459671.png | Bin 56434 -> 0 bytes docs/mrs/umn/en-us_image_0000001088608580.png | Bin 9933 -> 0 bytes docs/mrs/umn/en-us_image_0000001127057881.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0000001133372255.png | Bin 35649 -> 0 bytes docs/mrs/umn/en-us_image_0000001135452179.png | Bin 10674 -> 0 bytes docs/mrs/umn/en-us_image_0000001135745627.png | Bin 9105 -> 0 bytes docs/mrs/umn/en-us_image_0000001151336594.png | Bin 174 -> 0 bytes docs/mrs/umn/en-us_image_0000001151963015.png | Bin 505852 -> 0 bytes docs/mrs/umn/en-us_image_0000001159847251.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001169371695.png | Bin 7270 -> 0 bytes docs/mrs/umn/en-us_image_0000001184290228.png | Bin 84226 -> 0 bytes docs/mrs/umn/en-us_image_0000001194201259.png | Bin 9106 -> 0 bytes docs/mrs/umn/en-us_image_0000001194201487.png | Bin 10922 -> 0 bytes docs/mrs/umn/en-us_image_0000001194317737.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001195220440.png | Bin 924615 -> 0 bytes docs/mrs/umn/en-us_image_0000001197336255.png | Bin 264 -> 0 bytes docs/mrs/umn/en-us_image_0000001205479339.png | Bin 118232 -> 0 bytes docs/mrs/umn/en-us_image_0000001214152530.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001214312492.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001214315364.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001216164294.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0000001223688037.png | Bin 14527 -> 0 bytes docs/mrs/umn/en-us_image_0000001226576418.png | Bin 51022 -> 0 bytes docs/mrs/umn/en-us_image_0000001227056330.png | Bin 42647 -> 0 bytes docs/mrs/umn/en-us_image_0000001229609903.png | Bin 68280 -> 0 bytes docs/mrs/umn/en-us_image_0000001229690017.png | Bin 106594 -> 0 bytes docs/mrs/umn/en-us_image_0000001258875319.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001259115323.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001259272397.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001261300062.png | Bin 11785 -> 0 bytes docs/mrs/umn/en-us_image_0000001271157721.png | Bin 62234 -> 0 bytes docs/mrs/umn/en-us_image_0000001271536445.png | Bin 76699 -> 0 bytes docs/mrs/umn/en-us_image_0000001296365606.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001296525586.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001297838112.png | Bin 15992 -> 0 bytes docs/mrs/umn/en-us_image_0000001297841644.png | Bin 15737 -> 0 bytes docs/mrs/umn/en-us_image_0000001298155472.png | Bin 16078 -> 0 bytes docs/mrs/umn/en-us_image_0000001318119582.png | Bin 271 -> 0 bytes docs/mrs/umn/en-us_image_0000001318122266.png | Bin 346 -> 0 bytes docs/mrs/umn/en-us_image_0000001318123498.png | Bin 391 -> 0 bytes docs/mrs/umn/en-us_image_0000001318157588.png | Bin 391 -> 0 bytes docs/mrs/umn/en-us_image_0000001318160568.png | Bin 15749 -> 0 bytes docs/mrs/umn/en-us_image_0000001318441686.png | Bin 306 -> 0 bytes docs/mrs/umn/en-us_image_0000001318563432.png | Bin 294 -> 0 bytes docs/mrs/umn/en-us_image_0000001318636944.png | Bin 450 -> 0 bytes docs/mrs/umn/en-us_image_0000001337953138.png | Bin 42571 -> 0 bytes docs/mrs/umn/en-us_image_0000001338429394.png | Bin 10878 -> 0 bytes docs/mrs/umn/en-us_image_0000001349057889.png | Bin 738 -> 0 bytes docs/mrs/umn/en-us_image_0000001349137781.png | Bin 738 -> 0 bytes docs/mrs/umn/en-us_image_0000001349257369.png | Bin 738 -> 0 bytes docs/mrs/umn/en-us_image_0000001349390641.png | Bin 92184 -> 0 bytes docs/mrs/umn/en-us_image_0000001349585581.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001349825057.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001351040425.png | Bin 15927 -> 0 bytes docs/mrs/umn/en-us_image_0000001369746545.png | Bin 53428 -> 0 bytes docs/mrs/umn/en-us_image_0000001369765657.png | Bin 391 -> 0 bytes docs/mrs/umn/en-us_image_0000001369765661.png | Bin 391 -> 0 bytes docs/mrs/umn/en-us_image_0000001369864353.png | Bin 294 -> 0 bytes docs/mrs/umn/en-us_image_0000001369886993.png | Bin 50248 -> 0 bytes docs/mrs/umn/en-us_image_0000001369925585.png | Bin 362 -> 0 bytes docs/mrs/umn/en-us_image_0000001369944573.png | Bin 69271 -> 0 bytes docs/mrs/umn/en-us_image_0000001369953797.png | Bin 33131 -> 0 bytes docs/mrs/umn/en-us_image_0000001369960209.png | Bin 32592 -> 0 bytes docs/mrs/umn/en-us_image_0000001369965777.png | Bin 294 -> 0 bytes docs/mrs/umn/en-us_image_0000001369965781.png | Bin 391 -> 0 bytes docs/mrs/umn/en-us_image_0000001369965785.png | Bin 391 -> 0 bytes docs/mrs/umn/en-us_image_0000001370061921.png | Bin 101883 -> 0 bytes docs/mrs/umn/en-us_image_0000001370085637.png | Bin 391 -> 0 bytes docs/mrs/umn/en-us_image_0000001374635732.png | Bin 6931 -> 0 bytes docs/mrs/umn/en-us_image_0000001375852797.png | Bin 303 -> 0 bytes docs/mrs/umn/en-us_image_0000001375901064.png | Bin 20872 -> 0 bytes docs/mrs/umn/en-us_image_0000001376041769.png | Bin 303 -> 0 bytes docs/mrs/umn/en-us_image_0000001383088002.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001388541980.png | Bin 53164 -> 0 bytes docs/mrs/umn/en-us_image_0000001388629905.png | Bin 23882 -> 0 bytes docs/mrs/umn/en-us_image_0000001388630241.png | Bin 64020 -> 0 bytes docs/mrs/umn/en-us_image_0000001388681282.png | Bin 90492 -> 0 bytes docs/mrs/umn/en-us_image_0000001388835338.png | Bin 369 -> 0 bytes docs/mrs/umn/en-us_image_0000001388996278.png | Bin 211 -> 0 bytes docs/mrs/umn/en-us_image_0000001390459444.png | Bin 37235 -> 0 bytes docs/mrs/umn/en-us_image_0000001390459688.png | Bin 111433 -> 0 bytes docs/mrs/umn/en-us_image_0000001390618824.png | Bin 38622 -> 0 bytes docs/mrs/umn/en-us_image_0000001390618884.png | Bin 37235 -> 0 bytes docs/mrs/umn/en-us_image_0000001390619040.png | Bin 37235 -> 0 bytes docs/mrs/umn/en-us_image_0000001390936180.png | Bin 15375 -> 0 bytes docs/mrs/umn/en-us_image_0000001390938104.png | Bin 55806 -> 0 bytes docs/mrs/umn/en-us_image_0000001405224197.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0000001410107141.png | Bin 50748 -> 0 bytes docs/mrs/umn/en-us_image_0000001426500589.png | Bin 50748 -> 0 bytes docs/mrs/umn/en-us_image_0000001438033333.png | Bin 425348 -> 0 bytes docs/mrs/umn/en-us_image_0000001438841461.png | Bin 601 -> 0 bytes docs/mrs/umn/en-us_image_0000001438954277.png | Bin 601 -> 0 bytes docs/mrs/umn/en-us_image_0000001439442217.png | Bin 75075 -> 0 bytes docs/mrs/umn/en-us_image_0000001439562477.png | Bin 71575 -> 0 bytes docs/mrs/umn/en-us_image_0000001439594513.png | Bin 16047 -> 0 bytes docs/mrs/umn/en-us_image_0000001440858201.png | Bin 16475 -> 0 bytes docs/mrs/umn/en-us_image_0000001440858217.png | Bin 16475 -> 0 bytes docs/mrs/umn/en-us_image_0000001440858625.png | Bin 38175 -> 0 bytes docs/mrs/umn/en-us_image_0000001440977805.png | Bin 16475 -> 0 bytes docs/mrs/umn/en-us_image_0000001440977873.png | Bin 16475 -> 0 bytes docs/mrs/umn/en-us_image_0000001440978021.png | Bin 16475 -> 0 bytes docs/mrs/umn/en-us_image_0000001441097977.png | Bin 48958 -> 0 bytes docs/mrs/umn/en-us_image_0000001441098753.png | Bin 42441 -> 0 bytes docs/mrs/umn/en-us_image_0000001441218249.png | Bin 37235 -> 0 bytes docs/mrs/umn/en-us_image_0000001441218685.png | Bin 74715 -> 0 bytes docs/mrs/umn/en-us_image_0000001532448294.gif | Bin 229 -> 0 bytes docs/mrs/umn/en-us_image_0000001532607870.png | Bin 10674 -> 0 bytes docs/mrs/umn/en-us_image_0000001532927594.gif | Bin 229 -> 0 bytes docs/mrs/umn/en-us_image_0000001582807801.gif | Bin 605 -> 0 bytes docs/mrs/umn/en-us_image_0000001582807813.png | Bin 9105 -> 0 bytes docs/mrs/umn/en-us_image_0000001582927749.gif | Bin 605 -> 0 bytes docs/mrs/umn/en-us_image_0000001583087521.png | Bin 9933 -> 0 bytes ...1.gif => en-us_image_0000001782327888.png} | Bin ...5.png => en-us_image_0000001782333252.png} | Bin ...7.gif => en-us_image_0000001782347050.png} | Bin ...1.png => en-us_image_0000001782496978.png} | Bin docs/mrs/umn/en-us_image_0000001782506694.png | Bin 0 -> 228 bytes ...2.gif => en-us_image_0000001782509630.png} | Bin ...1.gif => en-us_image_0000001828886549.png} | Bin docs/mrs/umn/en-us_image_0000001829060901.png | Bin 0 -> 228 bytes docs/mrs/umn/en-us_image_0000001829066453.png | Bin 0 -> 228 bytes docs/mrs/umn/en-us_image_0000001829186485.png | Bin 0 -> 228 bytes ...6.gif => en-us_image_0000001830029997.png} | Bin docs/mrs/umn/en-us_image_0263895369.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895376.png | Bin 18410 -> 0 bytes docs/mrs/umn/en-us_image_0263895382.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895386.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895407.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895412.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895445.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895453.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895513.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895526.png | Bin 4356 -> 0 bytes docs/mrs/umn/en-us_image_0263895532.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895540.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895551.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895574.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895577.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895589.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895594.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895607.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895617.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895663.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895680.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895683.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895733.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895749.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895751.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895771.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895776.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895789.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895796.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895802.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895811.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895818.jpg | Bin 41142 -> 0 bytes docs/mrs/umn/en-us_image_0263895827.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263895859.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263895883.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0263899217.png | Bin 200 -> 0 bytes docs/mrs/umn/en-us_image_0263899218.png | Bin 449 -> 0 bytes docs/mrs/umn/en-us_image_0263899222.png | Bin 14800 -> 0 bytes docs/mrs/umn/en-us_image_0263899235.png | Bin 267 -> 0 bytes docs/mrs/umn/en-us_image_0263899238.png | Bin 688 -> 0 bytes docs/mrs/umn/en-us_image_0263899257.png | Bin 1166 -> 0 bytes docs/mrs/umn/en-us_image_0263899268.png | Bin 511 -> 0 bytes docs/mrs/umn/en-us_image_0263899271.png | Bin 22285 -> 0 bytes docs/mrs/umn/en-us_image_0263899280.png | Bin 481 -> 0 bytes docs/mrs/umn/en-us_image_0263899283.png | Bin 174 -> 0 bytes docs/mrs/umn/en-us_image_0263899288.png | Bin 210 -> 0 bytes docs/mrs/umn/en-us_image_0263899289.png | Bin 357 -> 0 bytes docs/mrs/umn/en-us_image_0263899291.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263899293.png | Bin 889 -> 0 bytes docs/mrs/umn/en-us_image_0263899299.png | Bin 173 -> 0 bytes docs/mrs/umn/en-us_image_0263899304.png | Bin 267 -> 0 bytes docs/mrs/umn/en-us_image_0263899311.png | Bin 207 -> 0 bytes docs/mrs/umn/en-us_image_0263899316.png | Bin 152 -> 0 bytes docs/mrs/umn/en-us_image_0263899322.png | Bin 688 -> 0 bytes docs/mrs/umn/en-us_image_0263899323.png | Bin 339 -> 0 bytes docs/mrs/umn/en-us_image_0263899329.png | Bin 210 -> 0 bytes docs/mrs/umn/en-us_image_0263899334.png | Bin 200 -> 0 bytes docs/mrs/umn/en-us_image_0263899339.png | Bin 889 -> 0 bytes docs/mrs/umn/en-us_image_0263899343.png | Bin 232 -> 0 bytes docs/mrs/umn/en-us_image_0263899363.png | Bin 889 -> 0 bytes docs/mrs/umn/en-us_image_0263899376.png | Bin 337 -> 0 bytes docs/mrs/umn/en-us_image_0263899383.png | Bin 581 -> 0 bytes docs/mrs/umn/en-us_image_0263899384.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263899392.png | Bin 200 -> 0 bytes docs/mrs/umn/en-us_image_0263899401.png | Bin 200 -> 0 bytes docs/mrs/umn/en-us_image_0263899403.png | Bin 224 -> 0 bytes docs/mrs/umn/en-us_image_0263899406.png | Bin 499 -> 0 bytes docs/mrs/umn/en-us_image_0263899409.png | Bin 513 -> 0 bytes docs/mrs/umn/en-us_image_0263899411.png | Bin 174 -> 0 bytes docs/mrs/umn/en-us_image_0263899420.png | Bin 24488 -> 0 bytes docs/mrs/umn/en-us_image_0263899424.png | Bin 207 -> 0 bytes docs/mrs/umn/en-us_image_0263899436.png | Bin 26176 -> 0 bytes docs/mrs/umn/en-us_image_0263899446.png | Bin 830 -> 0 bytes docs/mrs/umn/en-us_image_0263899452.png | Bin 581 -> 0 bytes docs/mrs/umn/en-us_image_0263899453.png | Bin 523 -> 0 bytes docs/mrs/umn/en-us_image_0263899454.png | Bin 481 -> 0 bytes docs/mrs/umn/en-us_image_0263899456.png | Bin 21415 -> 0 bytes docs/mrs/umn/en-us_image_0263899458.png | Bin 337 -> 0 bytes docs/mrs/umn/en-us_image_0263899471.png | Bin 336 -> 0 bytes docs/mrs/umn/en-us_image_0263899476.png | Bin 889 -> 0 bytes docs/mrs/umn/en-us_image_0263899493.png | Bin 383 -> 0 bytes docs/mrs/umn/en-us_image_0263899495.png | Bin 182 -> 0 bytes docs/mrs/umn/en-us_image_0263899496.png | Bin 449 -> 0 bytes docs/mrs/umn/en-us_image_0263899498.png | Bin 449 -> 0 bytes docs/mrs/umn/en-us_image_0263899504.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263899520.png | Bin 264 -> 0 bytes docs/mrs/umn/en-us_image_0263899528.png | Bin 210 -> 0 bytes docs/mrs/umn/en-us_image_0263899531.png | Bin 151 -> 0 bytes docs/mrs/umn/en-us_image_0263899538.png | Bin 40916 -> 0 bytes docs/mrs/umn/en-us_image_0263899546.png | Bin 132 -> 0 bytes docs/mrs/umn/en-us_image_0263899555.png | Bin 245 -> 0 bytes docs/mrs/umn/en-us_image_0263899556.png | Bin 334 -> 0 bytes docs/mrs/umn/en-us_image_0263899570.png | Bin 1166 -> 0 bytes docs/mrs/umn/en-us_image_0263899582.png | Bin 392 -> 0 bytes docs/mrs/umn/en-us_image_0263899589.png | Bin 327 -> 0 bytes docs/mrs/umn/en-us_image_0263899593.png | Bin 467 -> 0 bytes docs/mrs/umn/en-us_image_0263899597.png | Bin 450 -> 0 bytes docs/mrs/umn/en-us_image_0263899610.png | Bin 336 -> 0 bytes docs/mrs/umn/en-us_image_0263899616.png | Bin 242 -> 0 bytes docs/mrs/umn/en-us_image_0263899617.png | Bin 329 -> 0 bytes docs/mrs/umn/en-us_image_0263899621.png | Bin 337 -> 0 bytes docs/mrs/umn/en-us_image_0263899635.png | Bin 337 -> 0 bytes docs/mrs/umn/en-us_image_0263899637.png | Bin 152 -> 0 bytes docs/mrs/umn/en-us_image_0263899641.png | Bin 63069 -> 0 bytes docs/mrs/umn/en-us_image_0263899644.png | Bin 206 -> 0 bytes docs/mrs/umn/en-us_image_0263899649.png | Bin 33024 -> 0 bytes docs/mrs/umn/en-us_image_0263899656.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0263899662.png | Bin 511 -> 0 bytes docs/mrs/umn/en-us_image_0263899673.png | Bin 264 -> 0 bytes docs/mrs/umn/en-us_image_0263899675.png | Bin 242 -> 0 bytes docs/mrs/umn/en-us_image_0264281176.png | Bin 17946 -> 0 bytes docs/mrs/umn/en-us_image_0265768517.png | Bin 33335 -> 0 bytes docs/mrs/umn/en-us_image_0267694670.jpg | Bin 703 -> 0 bytes docs/mrs/umn/en-us_image_0268284607.png | Bin 60814 -> 0 bytes docs/mrs/umn/en-us_image_0268298534.png | Bin 164965 -> 0 bytes docs/mrs/umn/en-us_image_0269383808.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383809.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383810.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383814.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383815.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383816.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383817.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383818.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383822.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383823.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383824.png | Bin 41881 -> 0 bytes docs/mrs/umn/en-us_image_0269383826.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383828.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383829.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383830.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383831.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383832.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383834.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383843.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383844.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383845.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383846.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383850.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383851.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383852.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383855.jpg | Bin 13772 -> 0 bytes docs/mrs/umn/en-us_image_0269383856.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383857.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383872.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383873.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383875.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383876.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383877.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383878.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383880.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383881.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383882.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383883.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383884.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383889.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269383890.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383906.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383907.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383908.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383909.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383915.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383916.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383917.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383918.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383919.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383920.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383921.jpg | Bin 28700 -> 0 bytes docs/mrs/umn/en-us_image_0269383922.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383923.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383924.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383925.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383926.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383927.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383928.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383929.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383930.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383932.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383933.png | Bin 11929 -> 0 bytes docs/mrs/umn/en-us_image_0269383934.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383936.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383940.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383942.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383943.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383945.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383946.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383949.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383950.gif | Bin 605 -> 0 bytes docs/mrs/umn/en-us_image_0269383952.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383953.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383956.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383957.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383958.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383960.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383961.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383962.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383963.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383964.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383966.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383967.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383968.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383969.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383970.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269383972.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417342.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417343.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417344.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417365.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417366.png | Bin 403 -> 0 bytes docs/mrs/umn/en-us_image_0269417367.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417368.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417369.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417370.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417373.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417374.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417375.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417376.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417377.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417379.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417380.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417381.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417382.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417383.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417384.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417385.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417388.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417389.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417390.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417391.png | Bin 263 -> 0 bytes docs/mrs/umn/en-us_image_0269417392.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417393.png | Bin 259 -> 0 bytes docs/mrs/umn/en-us_image_0269417394.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417395.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417396.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417397.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417398.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417399.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417400.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417401.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417402.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417403.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417404.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417405.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417406.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417409.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417410.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417413.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417414.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417415.png | Bin 30503 -> 0 bytes docs/mrs/umn/en-us_image_0269417416.png | Bin 40999 -> 0 bytes docs/mrs/umn/en-us_image_0269417417.png | Bin 51611 -> 0 bytes docs/mrs/umn/en-us_image_0269417418.png | Bin 53792 -> 0 bytes docs/mrs/umn/en-us_image_0269417419.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417420.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417421.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417422.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417423.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417427.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417428.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417429.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417439.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417447.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417449.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417455.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417456.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417458.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417459.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417460.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417461.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417462.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417463.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417464.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417465.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269417466.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417468.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417469.png | Bin 8545 -> 0 bytes docs/mrs/umn/en-us_image_0269417473.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417499.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417500.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417501.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417502.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417503.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417504.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417505.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417506.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417510.png | Bin 270 -> 0 bytes docs/mrs/umn/en-us_image_0269417534.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417535.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417537.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417538.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417539.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417540.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417541.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417542.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417543.gif | Bin 229 -> 0 bytes docs/mrs/umn/en-us_image_0269417544.gif | Bin 229 -> 0 bytes docs/mrs/umn/en-us_image_0269417545.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417546.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417547.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417548.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269417549.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269623978.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0269624001.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0270938821.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0276137853.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0276137857.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0276137858.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0276137859.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0276801805.png | Bin 26470 -> 0 bytes docs/mrs/umn/en-us_image_0278119935.png | Bin 182 -> 0 bytes docs/mrs/umn/en-us_image_0279536633.png | Bin 514 -> 0 bytes docs/mrs/umn/en-us_image_0293101307.png | Bin 15748 -> 0 bytes docs/mrs/umn/en-us_image_0293131436.png | Bin 77581 -> 0 bytes docs/mrs/umn/en-us_image_0293180907.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293234930.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293235730.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293242788.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293245149.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293246465.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293246731.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293247048.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293247437.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293267262.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293268152.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293269028.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293269047.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0293269551.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0295310731.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0295554634.png | Bin 366 -> 0 bytes docs/mrs/umn/en-us_image_0295706662.png | Bin 366 -> 0 bytes .../mrs/umn/en-us_topic_0000001098596550.html | 11 - .../mrs/umn/en-us_topic_0000001145356345.html | 14 - .../mrs/umn/en-us_topic_0000001145596307.html | 11 - .../mrs/umn/en-us_topic_0000001145597621.html | 11 - .../mrs/umn/en-us_topic_0000001145676237.html | 11 - .../mrs/umn/en-us_topic_0000001152828323.html | 19 - .../mrs/umn/en-us_topic_0000001295768772.html | 25 - .../mrs/umn/en-us_topic_0000001349137409.html | 2 +- docs/mrs/umn/en-us_topic_0012808231.html | 2 +- docs/mrs/umn/mrs_01_0060.html | 8 +- docs/mrs/umn/mrs_01_0089.html | 4 +- docs/mrs/umn/mrs_01_0090.html | 16 +- docs/mrs/umn/mrs_01_0091.html | 2 +- docs/mrs/umn/mrs_01_0101.html | 2 +- docs/mrs/umn/mrs_01_0102.html | 10 +- docs/mrs/umn/mrs_01_0107.html | 6 +- docs/mrs/umn/mrs_01_0128.html | 4 +- docs/mrs/umn/mrs_01_0129.html | 12 +- docs/mrs/umn/mrs_01_0210.html | 2 +- docs/mrs/umn/mrs_01_0224.html | 2 +- docs/mrs/umn/mrs_01_0294.html | 2 +- docs/mrs/umn/mrs_01_0341.html | 2 +- docs/mrs/umn/mrs_01_0343.html | 2 +- docs/mrs/umn/mrs_01_0344.html | 2 +- docs/mrs/umn/mrs_01_0345.html | 2 +- docs/mrs/umn/mrs_01_0346.html | 2 +- docs/mrs/umn/mrs_01_0347.html | 2 +- docs/mrs/umn/mrs_01_0348.html | 2 +- docs/mrs/umn/mrs_01_0349.html | 2 +- docs/mrs/umn/mrs_01_0350.html | 2 +- docs/mrs/umn/mrs_01_0351.html | 2 +- docs/mrs/umn/mrs_01_0352.html | 2 +- docs/mrs/umn/mrs_01_0353.html | 2 +- docs/mrs/umn/mrs_01_0354.html | 2 +- docs/mrs/umn/mrs_01_0362.html | 4 +- docs/mrs/umn/mrs_01_0363.html | 2 +- docs/mrs/umn/mrs_01_0409.html | 2 + docs/mrs/umn/mrs_01_0410.html | 6 +- docs/mrs/umn/mrs_01_0412.html | 2 +- docs/mrs/umn/mrs_01_0431.html | 4 +- docs/mrs/umn/mrs_01_0453.html | 2 +- docs/mrs/umn/mrs_01_0468.html | 4 +- docs/mrs/umn/mrs_01_0494.html | 6 +- docs/mrs/umn/mrs_01_0497.html | 18 - docs/mrs/umn/mrs_01_0513.html | 2 +- docs/mrs/umn/mrs_01_0524.html | 2 +- docs/mrs/umn/mrs_01_0526.html | 2 +- docs/mrs/umn/mrs_01_0536.html | 6 +- docs/mrs/umn/mrs_01_0547.html | 2 +- docs/mrs/umn/mrs_01_0574.html | 2 +- docs/mrs/umn/mrs_01_0575.html | 6 +- docs/mrs/umn/mrs_01_0576.html | 2 +- docs/mrs/umn/mrs_01_0577.html | 4 +- docs/mrs/umn/mrs_01_0578.html | 2 +- docs/mrs/umn/mrs_01_0604.html | 2 +- docs/mrs/umn/mrs_01_0606.html | 2 +- docs/mrs/umn/mrs_01_0614.html | 8 +- docs/mrs/umn/mrs_01_0645.html | 2 +- docs/mrs/umn/mrs_01_0646.html | 2 +- docs/mrs/umn/mrs_01_0768.html | 2 +- docs/mrs/umn/mrs_01_1226.html | 6 +- docs/mrs/umn/mrs_01_1227.html | 2 +- docs/mrs/umn/mrs_01_1286.html | 4 +- docs/mrs/umn/mrs_01_1289.html | 2 +- docs/mrs/umn/mrs_01_1298.html | 6 +- docs/mrs/umn/mrs_01_1595.html | 4 +- docs/mrs/umn/mrs_01_2354.html | 1 - docs/mrs/umn/mrs_01_24051.html | 10 +- docs/mrs/umn/mrs_01_24184.html | 77 +- docs/mrs/umn/mrs_01_24185.html | 4 +- docs/mrs/umn/mrs_01_24186.html | 2 +- docs/mrs/umn/mrs_01_24187.html | 11 +- docs/mrs/umn/mrs_01_24191.html | 11 +- docs/mrs/umn/mrs_01_24209.html | 4 +- docs/mrs/umn/mrs_01_24296.html | 2 + docs/mrs/umn/mrs_01_248971.html | 18 + docs/mrs/umn/mrs_01_248972.html | 85 + docs/mrs/umn/mrs_01_248973.html | 23 + docs/mrs/umn/mrs_01_9003.html | 118 +- docs/mrs/umn/mrs_01_9043.html | 58 + docs/mrs/umn/mrs_03_0002.html | 4 +- docs/mrs/umn/mrs_03_1005.html | 261 +- docs/mrs/umn/mrs_03_1020.html | 2 +- docs/mrs/umn/mrs_03_1035.html | 2 +- docs/mrs/umn/mrs_03_1061.html | 2 +- docs/mrs/umn/mrs_03_1071.html | 6 +- docs/mrs/umn/mrs_03_1082.html | 6 +- docs/mrs/umn/mrs_03_1090.html | 4 +- docs/mrs/umn/mrs_03_1151.html | 4 +- docs/mrs/umn/mrs_03_1153.html | 2 +- docs/mrs/umn/mrs_03_1172.html | 14 - docs/mrs/umn/mrs_03_1194.html | 2 +- docs/mrs/umn/mrs_03_1197.html | 2 +- docs/mrs/umn/mrs_03_1202.html | 2 +- docs/mrs/umn/mrs_03_1204.html | 2 +- docs/mrs/umn/mrs_03_1217.html | 2 +- docs/mrs/umn/mrs_03_1219.html | 2 +- docs/mrs/umn/mrs_03_1221.html | 2 +- docs/mrs/umn/mrs_03_1222.html | 2 +- docs/mrs/umn/mrs_03_1233.html | 112 +- docs/mrs/umn/mrs_03_1243.html | 2 +- docs/mrs/umn/mrs_03_1257.html | 17 - docs/mrs/umn/mrs_03_2014.html | 2 +- docs/mrs/umn/mrs_08_0005.html | 11 +- docs/mrs/umn/mrs_08_00661.html | 2 +- docs/mrs/umn/mrs_09_0003.html | 2 +- 1040 files changed, 5599 insertions(+), 5409 deletions(-) delete mode 100644 docs/mrs/umn/en-us_image_0000001072559365.png delete mode 100644 docs/mrs/umn/en-us_image_0000001080201158.png delete mode 100644 docs/mrs/umn/en-us_image_0000001085773316.png delete mode 100644 docs/mrs/umn/en-us_image_0000001086795516.png delete mode 100644 docs/mrs/umn/en-us_image_0000001087171010.png delete mode 100644 docs/mrs/umn/en-us_image_0000001087459671.png delete mode 100644 docs/mrs/umn/en-us_image_0000001088608580.png delete mode 100644 docs/mrs/umn/en-us_image_0000001127057881.png delete mode 100644 docs/mrs/umn/en-us_image_0000001133372255.png delete mode 100644 docs/mrs/umn/en-us_image_0000001135452179.png delete mode 100644 docs/mrs/umn/en-us_image_0000001135745627.png delete mode 100644 docs/mrs/umn/en-us_image_0000001151336594.png delete mode 100644 docs/mrs/umn/en-us_image_0000001151963015.png delete mode 100644 docs/mrs/umn/en-us_image_0000001159847251.png delete mode 100644 docs/mrs/umn/en-us_image_0000001169371695.png delete mode 100644 docs/mrs/umn/en-us_image_0000001184290228.png delete mode 100644 docs/mrs/umn/en-us_image_0000001194201259.png delete mode 100644 docs/mrs/umn/en-us_image_0000001194201487.png delete mode 100644 docs/mrs/umn/en-us_image_0000001194317737.png delete mode 100644 docs/mrs/umn/en-us_image_0000001195220440.png delete mode 100644 docs/mrs/umn/en-us_image_0000001197336255.png delete mode 100644 docs/mrs/umn/en-us_image_0000001205479339.png delete mode 100644 docs/mrs/umn/en-us_image_0000001214152530.png delete mode 100644 docs/mrs/umn/en-us_image_0000001214312492.png delete mode 100644 docs/mrs/umn/en-us_image_0000001214315364.png delete mode 100644 docs/mrs/umn/en-us_image_0000001216164294.png delete mode 100644 docs/mrs/umn/en-us_image_0000001223688037.png delete mode 100644 docs/mrs/umn/en-us_image_0000001226576418.png delete mode 100644 docs/mrs/umn/en-us_image_0000001227056330.png delete mode 100644 docs/mrs/umn/en-us_image_0000001229609903.png delete mode 100644 docs/mrs/umn/en-us_image_0000001229690017.png delete mode 100644 docs/mrs/umn/en-us_image_0000001258875319.png delete mode 100644 docs/mrs/umn/en-us_image_0000001259115323.png delete mode 100644 docs/mrs/umn/en-us_image_0000001259272397.png delete mode 100644 docs/mrs/umn/en-us_image_0000001261300062.png delete mode 100644 docs/mrs/umn/en-us_image_0000001271157721.png delete mode 100644 docs/mrs/umn/en-us_image_0000001271536445.png delete mode 100644 docs/mrs/umn/en-us_image_0000001296365606.png delete mode 100644 docs/mrs/umn/en-us_image_0000001296525586.png delete mode 100644 docs/mrs/umn/en-us_image_0000001297838112.png delete mode 100644 docs/mrs/umn/en-us_image_0000001297841644.png delete mode 100644 docs/mrs/umn/en-us_image_0000001298155472.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318119582.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318122266.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318123498.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318157588.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318160568.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318441686.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318563432.png delete mode 100644 docs/mrs/umn/en-us_image_0000001318636944.png delete mode 100644 docs/mrs/umn/en-us_image_0000001337953138.png delete mode 100644 docs/mrs/umn/en-us_image_0000001338429394.png delete mode 100644 docs/mrs/umn/en-us_image_0000001349057889.png delete mode 100644 docs/mrs/umn/en-us_image_0000001349137781.png delete mode 100644 docs/mrs/umn/en-us_image_0000001349257369.png delete mode 100644 docs/mrs/umn/en-us_image_0000001349390641.png delete mode 100644 docs/mrs/umn/en-us_image_0000001349585581.png delete mode 100644 docs/mrs/umn/en-us_image_0000001349825057.png delete mode 100644 docs/mrs/umn/en-us_image_0000001351040425.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369746545.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369765657.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369765661.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369864353.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369886993.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369925585.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369944573.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369953797.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369960209.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369965777.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369965781.png delete mode 100644 docs/mrs/umn/en-us_image_0000001369965785.png delete mode 100644 docs/mrs/umn/en-us_image_0000001370061921.png delete mode 100644 docs/mrs/umn/en-us_image_0000001370085637.png delete mode 100644 docs/mrs/umn/en-us_image_0000001374635732.png delete mode 100644 docs/mrs/umn/en-us_image_0000001375852797.png delete mode 100644 docs/mrs/umn/en-us_image_0000001375901064.png delete mode 100644 docs/mrs/umn/en-us_image_0000001376041769.png delete mode 100644 docs/mrs/umn/en-us_image_0000001383088002.png delete mode 100644 docs/mrs/umn/en-us_image_0000001388541980.png delete mode 100644 docs/mrs/umn/en-us_image_0000001388629905.png delete mode 100644 docs/mrs/umn/en-us_image_0000001388630241.png delete mode 100644 docs/mrs/umn/en-us_image_0000001388681282.png delete mode 100644 docs/mrs/umn/en-us_image_0000001388835338.png delete mode 100644 docs/mrs/umn/en-us_image_0000001388996278.png delete mode 100644 docs/mrs/umn/en-us_image_0000001390459444.png delete mode 100644 docs/mrs/umn/en-us_image_0000001390459688.png delete mode 100644 docs/mrs/umn/en-us_image_0000001390618824.png delete mode 100644 docs/mrs/umn/en-us_image_0000001390618884.png delete mode 100644 docs/mrs/umn/en-us_image_0000001390619040.png delete mode 100644 docs/mrs/umn/en-us_image_0000001390936180.png delete mode 100644 docs/mrs/umn/en-us_image_0000001390938104.png delete mode 100644 docs/mrs/umn/en-us_image_0000001405224197.png delete mode 100644 docs/mrs/umn/en-us_image_0000001410107141.png delete mode 100644 docs/mrs/umn/en-us_image_0000001426500589.png delete mode 100644 docs/mrs/umn/en-us_image_0000001438033333.png delete mode 100644 docs/mrs/umn/en-us_image_0000001438841461.png delete mode 100644 docs/mrs/umn/en-us_image_0000001438954277.png delete mode 100644 docs/mrs/umn/en-us_image_0000001439442217.png delete mode 100644 docs/mrs/umn/en-us_image_0000001439562477.png delete mode 100644 docs/mrs/umn/en-us_image_0000001439594513.png delete mode 100644 docs/mrs/umn/en-us_image_0000001440858201.png delete mode 100644 docs/mrs/umn/en-us_image_0000001440858217.png delete mode 100644 docs/mrs/umn/en-us_image_0000001440858625.png delete mode 100644 docs/mrs/umn/en-us_image_0000001440977805.png delete mode 100644 docs/mrs/umn/en-us_image_0000001440977873.png delete mode 100644 docs/mrs/umn/en-us_image_0000001440978021.png delete mode 100644 docs/mrs/umn/en-us_image_0000001441097977.png delete mode 100644 docs/mrs/umn/en-us_image_0000001441098753.png delete mode 100644 docs/mrs/umn/en-us_image_0000001441218249.png delete mode 100644 docs/mrs/umn/en-us_image_0000001441218685.png delete mode 100644 docs/mrs/umn/en-us_image_0000001532448294.gif delete mode 100644 docs/mrs/umn/en-us_image_0000001532607870.png delete mode 100644 docs/mrs/umn/en-us_image_0000001532927594.gif delete mode 100644 docs/mrs/umn/en-us_image_0000001582807801.gif delete mode 100644 docs/mrs/umn/en-us_image_0000001582807813.png delete mode 100644 docs/mrs/umn/en-us_image_0000001582927749.gif delete mode 100644 docs/mrs/umn/en-us_image_0000001583087521.png rename docs/mrs/umn/{en-us_image_0000001239292351.gif => en-us_image_0000001782327888.png} (100%) rename docs/mrs/umn/{en-us_image_0000001125163135.png => en-us_image_0000001782333252.png} (100%) rename docs/mrs/umn/{en-us_image_0000001348738077.gif => en-us_image_0000001782347050.png} (100%) rename docs/mrs/umn/{en-us_image_0000001159690571.png => en-us_image_0000001782496978.png} (100%) create mode 100644 docs/mrs/umn/en-us_image_0000001782506694.png rename docs/mrs/umn/{en-us_image_0000001296217532.gif => en-us_image_0000001782509630.png} (100%) rename docs/mrs/umn/{en-us_image_0000001239732331.gif => en-us_image_0000001828886549.png} (100%) create mode 100644 docs/mrs/umn/en-us_image_0000001829060901.png create mode 100644 docs/mrs/umn/en-us_image_0000001829066453.png create mode 100644 docs/mrs/umn/en-us_image_0000001829186485.png rename docs/mrs/umn/{en-us_image_0000001532767466.gif => en-us_image_0000001830029997.png} (100%) delete mode 100644 docs/mrs/umn/en-us_image_0263895369.png delete mode 100644 docs/mrs/umn/en-us_image_0263895376.png delete mode 100644 docs/mrs/umn/en-us_image_0263895382.png delete mode 100644 docs/mrs/umn/en-us_image_0263895386.png delete mode 100644 docs/mrs/umn/en-us_image_0263895407.png delete mode 100644 docs/mrs/umn/en-us_image_0263895412.png delete mode 100644 docs/mrs/umn/en-us_image_0263895445.png delete mode 100644 docs/mrs/umn/en-us_image_0263895453.png delete mode 100644 docs/mrs/umn/en-us_image_0263895513.png delete mode 100644 docs/mrs/umn/en-us_image_0263895526.png delete mode 100644 docs/mrs/umn/en-us_image_0263895532.png delete mode 100644 docs/mrs/umn/en-us_image_0263895540.png delete mode 100644 docs/mrs/umn/en-us_image_0263895551.png delete mode 100644 docs/mrs/umn/en-us_image_0263895574.png delete mode 100644 docs/mrs/umn/en-us_image_0263895577.png delete mode 100644 docs/mrs/umn/en-us_image_0263895589.png delete mode 100644 docs/mrs/umn/en-us_image_0263895594.png delete mode 100644 docs/mrs/umn/en-us_image_0263895607.png delete mode 100644 docs/mrs/umn/en-us_image_0263895617.png delete mode 100644 docs/mrs/umn/en-us_image_0263895663.png delete mode 100644 docs/mrs/umn/en-us_image_0263895680.png delete mode 100644 docs/mrs/umn/en-us_image_0263895683.png delete mode 100644 docs/mrs/umn/en-us_image_0263895733.png delete mode 100644 docs/mrs/umn/en-us_image_0263895749.png delete mode 100644 docs/mrs/umn/en-us_image_0263895751.png delete mode 100644 docs/mrs/umn/en-us_image_0263895771.png delete mode 100644 docs/mrs/umn/en-us_image_0263895776.png delete mode 100644 docs/mrs/umn/en-us_image_0263895789.png delete mode 100644 docs/mrs/umn/en-us_image_0263895796.png delete mode 100644 docs/mrs/umn/en-us_image_0263895802.png delete mode 100644 docs/mrs/umn/en-us_image_0263895811.png delete mode 100644 docs/mrs/umn/en-us_image_0263895818.jpg delete mode 100644 docs/mrs/umn/en-us_image_0263895827.png delete mode 100644 docs/mrs/umn/en-us_image_0263895859.png delete mode 100644 docs/mrs/umn/en-us_image_0263895883.png delete mode 100644 docs/mrs/umn/en-us_image_0263899217.png delete mode 100644 docs/mrs/umn/en-us_image_0263899218.png delete mode 100644 docs/mrs/umn/en-us_image_0263899222.png delete mode 100644 docs/mrs/umn/en-us_image_0263899235.png delete mode 100644 docs/mrs/umn/en-us_image_0263899238.png delete mode 100644 docs/mrs/umn/en-us_image_0263899257.png delete mode 100644 docs/mrs/umn/en-us_image_0263899268.png delete mode 100644 docs/mrs/umn/en-us_image_0263899271.png delete mode 100644 docs/mrs/umn/en-us_image_0263899280.png delete mode 100644 docs/mrs/umn/en-us_image_0263899283.png delete mode 100644 docs/mrs/umn/en-us_image_0263899288.png delete mode 100644 docs/mrs/umn/en-us_image_0263899289.png delete mode 100644 docs/mrs/umn/en-us_image_0263899291.png delete mode 100644 docs/mrs/umn/en-us_image_0263899293.png delete mode 100644 docs/mrs/umn/en-us_image_0263899299.png delete mode 100644 docs/mrs/umn/en-us_image_0263899304.png delete mode 100644 docs/mrs/umn/en-us_image_0263899311.png delete mode 100644 docs/mrs/umn/en-us_image_0263899316.png delete mode 100644 docs/mrs/umn/en-us_image_0263899322.png delete mode 100644 docs/mrs/umn/en-us_image_0263899323.png delete mode 100644 docs/mrs/umn/en-us_image_0263899329.png delete mode 100644 docs/mrs/umn/en-us_image_0263899334.png delete mode 100644 docs/mrs/umn/en-us_image_0263899339.png delete mode 100644 docs/mrs/umn/en-us_image_0263899343.png delete mode 100644 docs/mrs/umn/en-us_image_0263899363.png delete mode 100644 docs/mrs/umn/en-us_image_0263899376.png delete mode 100644 docs/mrs/umn/en-us_image_0263899383.png delete mode 100644 docs/mrs/umn/en-us_image_0263899384.png delete mode 100644 docs/mrs/umn/en-us_image_0263899392.png delete mode 100644 docs/mrs/umn/en-us_image_0263899401.png delete mode 100644 docs/mrs/umn/en-us_image_0263899403.png delete mode 100644 docs/mrs/umn/en-us_image_0263899406.png delete mode 100644 docs/mrs/umn/en-us_image_0263899409.png delete mode 100644 docs/mrs/umn/en-us_image_0263899411.png delete mode 100644 docs/mrs/umn/en-us_image_0263899420.png delete mode 100644 docs/mrs/umn/en-us_image_0263899424.png delete mode 100644 docs/mrs/umn/en-us_image_0263899436.png delete mode 100644 docs/mrs/umn/en-us_image_0263899446.png delete mode 100644 docs/mrs/umn/en-us_image_0263899452.png delete mode 100644 docs/mrs/umn/en-us_image_0263899453.png delete mode 100644 docs/mrs/umn/en-us_image_0263899454.png delete mode 100644 docs/mrs/umn/en-us_image_0263899456.png delete mode 100644 docs/mrs/umn/en-us_image_0263899458.png delete mode 100644 docs/mrs/umn/en-us_image_0263899471.png delete mode 100644 docs/mrs/umn/en-us_image_0263899476.png delete mode 100644 docs/mrs/umn/en-us_image_0263899493.png delete mode 100644 docs/mrs/umn/en-us_image_0263899495.png delete mode 100644 docs/mrs/umn/en-us_image_0263899496.png delete mode 100644 docs/mrs/umn/en-us_image_0263899498.png delete mode 100644 docs/mrs/umn/en-us_image_0263899504.png delete mode 100644 docs/mrs/umn/en-us_image_0263899520.png delete mode 100644 docs/mrs/umn/en-us_image_0263899528.png delete mode 100644 docs/mrs/umn/en-us_image_0263899531.png delete mode 100644 docs/mrs/umn/en-us_image_0263899538.png delete mode 100644 docs/mrs/umn/en-us_image_0263899546.png delete mode 100644 docs/mrs/umn/en-us_image_0263899555.png delete mode 100644 docs/mrs/umn/en-us_image_0263899556.png delete mode 100644 docs/mrs/umn/en-us_image_0263899570.png delete mode 100644 docs/mrs/umn/en-us_image_0263899582.png delete mode 100644 docs/mrs/umn/en-us_image_0263899589.png delete mode 100644 docs/mrs/umn/en-us_image_0263899593.png delete mode 100644 docs/mrs/umn/en-us_image_0263899597.png delete mode 100644 docs/mrs/umn/en-us_image_0263899610.png delete mode 100644 docs/mrs/umn/en-us_image_0263899616.png delete mode 100644 docs/mrs/umn/en-us_image_0263899617.png delete mode 100644 docs/mrs/umn/en-us_image_0263899621.png delete mode 100644 docs/mrs/umn/en-us_image_0263899635.png delete mode 100644 docs/mrs/umn/en-us_image_0263899637.png delete mode 100644 docs/mrs/umn/en-us_image_0263899641.png delete mode 100644 docs/mrs/umn/en-us_image_0263899644.png delete mode 100644 docs/mrs/umn/en-us_image_0263899649.png delete mode 100644 docs/mrs/umn/en-us_image_0263899656.png delete mode 100644 docs/mrs/umn/en-us_image_0263899662.png delete mode 100644 docs/mrs/umn/en-us_image_0263899673.png delete mode 100644 docs/mrs/umn/en-us_image_0263899675.png delete mode 100644 docs/mrs/umn/en-us_image_0264281176.png delete mode 100644 docs/mrs/umn/en-us_image_0265768517.png delete mode 100644 docs/mrs/umn/en-us_image_0267694670.jpg delete mode 100644 docs/mrs/umn/en-us_image_0268284607.png delete mode 100644 docs/mrs/umn/en-us_image_0268298534.png delete mode 100644 docs/mrs/umn/en-us_image_0269383808.png delete mode 100644 docs/mrs/umn/en-us_image_0269383809.png delete mode 100644 docs/mrs/umn/en-us_image_0269383810.png delete mode 100644 docs/mrs/umn/en-us_image_0269383814.png delete mode 100644 docs/mrs/umn/en-us_image_0269383815.png delete mode 100644 docs/mrs/umn/en-us_image_0269383816.png delete mode 100644 docs/mrs/umn/en-us_image_0269383817.png delete mode 100644 docs/mrs/umn/en-us_image_0269383818.png delete mode 100644 docs/mrs/umn/en-us_image_0269383822.png delete mode 100644 docs/mrs/umn/en-us_image_0269383823.png delete mode 100644 docs/mrs/umn/en-us_image_0269383824.png delete mode 100644 docs/mrs/umn/en-us_image_0269383826.png delete mode 100644 docs/mrs/umn/en-us_image_0269383828.png delete mode 100644 docs/mrs/umn/en-us_image_0269383829.png delete mode 100644 docs/mrs/umn/en-us_image_0269383830.png delete mode 100644 docs/mrs/umn/en-us_image_0269383831.png delete mode 100644 docs/mrs/umn/en-us_image_0269383832.png delete mode 100644 docs/mrs/umn/en-us_image_0269383834.png delete mode 100644 docs/mrs/umn/en-us_image_0269383843.png delete mode 100644 docs/mrs/umn/en-us_image_0269383844.png delete mode 100644 docs/mrs/umn/en-us_image_0269383845.png delete mode 100644 docs/mrs/umn/en-us_image_0269383846.png delete mode 100644 docs/mrs/umn/en-us_image_0269383850.png delete mode 100644 docs/mrs/umn/en-us_image_0269383851.png delete mode 100644 docs/mrs/umn/en-us_image_0269383852.png delete mode 100644 docs/mrs/umn/en-us_image_0269383855.jpg delete mode 100644 docs/mrs/umn/en-us_image_0269383856.png delete mode 100644 docs/mrs/umn/en-us_image_0269383857.png delete mode 100644 docs/mrs/umn/en-us_image_0269383872.png delete mode 100644 docs/mrs/umn/en-us_image_0269383873.png delete mode 100644 docs/mrs/umn/en-us_image_0269383875.png delete mode 100644 docs/mrs/umn/en-us_image_0269383876.png delete mode 100644 docs/mrs/umn/en-us_image_0269383877.png delete mode 100644 docs/mrs/umn/en-us_image_0269383878.png delete mode 100644 docs/mrs/umn/en-us_image_0269383880.png delete mode 100644 docs/mrs/umn/en-us_image_0269383881.png delete mode 100644 docs/mrs/umn/en-us_image_0269383882.png delete mode 100644 docs/mrs/umn/en-us_image_0269383883.png delete mode 100644 docs/mrs/umn/en-us_image_0269383884.png delete mode 100644 docs/mrs/umn/en-us_image_0269383889.png delete mode 100644 docs/mrs/umn/en-us_image_0269383890.png delete mode 100644 docs/mrs/umn/en-us_image_0269383906.png delete mode 100644 docs/mrs/umn/en-us_image_0269383907.png delete mode 100644 docs/mrs/umn/en-us_image_0269383908.png delete mode 100644 docs/mrs/umn/en-us_image_0269383909.png delete mode 100644 docs/mrs/umn/en-us_image_0269383915.png delete mode 100644 docs/mrs/umn/en-us_image_0269383916.png delete mode 100644 docs/mrs/umn/en-us_image_0269383917.png delete mode 100644 docs/mrs/umn/en-us_image_0269383918.png delete mode 100644 docs/mrs/umn/en-us_image_0269383919.png delete mode 100644 docs/mrs/umn/en-us_image_0269383920.png delete mode 100644 docs/mrs/umn/en-us_image_0269383921.jpg delete mode 100644 docs/mrs/umn/en-us_image_0269383922.png delete mode 100644 docs/mrs/umn/en-us_image_0269383923.png delete mode 100644 docs/mrs/umn/en-us_image_0269383924.png delete mode 100644 docs/mrs/umn/en-us_image_0269383925.png delete mode 100644 docs/mrs/umn/en-us_image_0269383926.png delete mode 100644 docs/mrs/umn/en-us_image_0269383927.png delete mode 100644 docs/mrs/umn/en-us_image_0269383928.png delete mode 100644 docs/mrs/umn/en-us_image_0269383929.png delete mode 100644 docs/mrs/umn/en-us_image_0269383930.png delete mode 100644 docs/mrs/umn/en-us_image_0269383932.png delete mode 100644 docs/mrs/umn/en-us_image_0269383933.png delete mode 100644 docs/mrs/umn/en-us_image_0269383934.png delete mode 100644 docs/mrs/umn/en-us_image_0269383936.png delete mode 100644 docs/mrs/umn/en-us_image_0269383940.png delete mode 100644 docs/mrs/umn/en-us_image_0269383942.png delete mode 100644 docs/mrs/umn/en-us_image_0269383943.png delete mode 100644 docs/mrs/umn/en-us_image_0269383945.png delete mode 100644 docs/mrs/umn/en-us_image_0269383946.png delete mode 100644 docs/mrs/umn/en-us_image_0269383949.png delete mode 100644 docs/mrs/umn/en-us_image_0269383950.gif delete mode 100644 docs/mrs/umn/en-us_image_0269383952.png delete mode 100644 docs/mrs/umn/en-us_image_0269383953.png delete mode 100644 docs/mrs/umn/en-us_image_0269383956.png delete mode 100644 docs/mrs/umn/en-us_image_0269383957.png delete mode 100644 docs/mrs/umn/en-us_image_0269383958.png delete mode 100644 docs/mrs/umn/en-us_image_0269383960.png delete mode 100644 docs/mrs/umn/en-us_image_0269383961.png delete mode 100644 docs/mrs/umn/en-us_image_0269383962.png delete mode 100644 docs/mrs/umn/en-us_image_0269383963.png delete mode 100644 docs/mrs/umn/en-us_image_0269383964.png delete mode 100644 docs/mrs/umn/en-us_image_0269383966.png delete mode 100644 docs/mrs/umn/en-us_image_0269383967.png delete mode 100644 docs/mrs/umn/en-us_image_0269383968.png delete mode 100644 docs/mrs/umn/en-us_image_0269383969.png delete mode 100644 docs/mrs/umn/en-us_image_0269383970.png delete mode 100644 docs/mrs/umn/en-us_image_0269383972.png delete mode 100644 docs/mrs/umn/en-us_image_0269417342.png delete mode 100644 docs/mrs/umn/en-us_image_0269417343.png delete mode 100644 docs/mrs/umn/en-us_image_0269417344.png delete mode 100644 docs/mrs/umn/en-us_image_0269417365.png delete mode 100644 docs/mrs/umn/en-us_image_0269417366.png delete mode 100644 docs/mrs/umn/en-us_image_0269417367.png delete mode 100644 docs/mrs/umn/en-us_image_0269417368.png delete mode 100644 docs/mrs/umn/en-us_image_0269417369.png delete mode 100644 docs/mrs/umn/en-us_image_0269417370.png delete mode 100644 docs/mrs/umn/en-us_image_0269417373.png delete mode 100644 docs/mrs/umn/en-us_image_0269417374.png delete mode 100644 docs/mrs/umn/en-us_image_0269417375.png delete mode 100644 docs/mrs/umn/en-us_image_0269417376.png delete mode 100644 docs/mrs/umn/en-us_image_0269417377.png delete mode 100644 docs/mrs/umn/en-us_image_0269417379.png delete mode 100644 docs/mrs/umn/en-us_image_0269417380.png delete mode 100644 docs/mrs/umn/en-us_image_0269417381.png delete mode 100644 docs/mrs/umn/en-us_image_0269417382.png delete mode 100644 docs/mrs/umn/en-us_image_0269417383.png delete mode 100644 docs/mrs/umn/en-us_image_0269417384.png delete mode 100644 docs/mrs/umn/en-us_image_0269417385.png delete mode 100644 docs/mrs/umn/en-us_image_0269417388.png delete mode 100644 docs/mrs/umn/en-us_image_0269417389.png delete mode 100644 docs/mrs/umn/en-us_image_0269417390.png delete mode 100644 docs/mrs/umn/en-us_image_0269417391.png delete mode 100644 docs/mrs/umn/en-us_image_0269417392.png delete mode 100644 docs/mrs/umn/en-us_image_0269417393.png delete mode 100644 docs/mrs/umn/en-us_image_0269417394.png delete mode 100644 docs/mrs/umn/en-us_image_0269417395.png delete mode 100644 docs/mrs/umn/en-us_image_0269417396.png delete mode 100644 docs/mrs/umn/en-us_image_0269417397.png delete mode 100644 docs/mrs/umn/en-us_image_0269417398.png delete mode 100644 docs/mrs/umn/en-us_image_0269417399.png delete mode 100644 docs/mrs/umn/en-us_image_0269417400.png delete mode 100644 docs/mrs/umn/en-us_image_0269417401.png delete mode 100644 docs/mrs/umn/en-us_image_0269417402.png delete mode 100644 docs/mrs/umn/en-us_image_0269417403.png delete mode 100644 docs/mrs/umn/en-us_image_0269417404.png delete mode 100644 docs/mrs/umn/en-us_image_0269417405.png delete mode 100644 docs/mrs/umn/en-us_image_0269417406.png delete mode 100644 docs/mrs/umn/en-us_image_0269417409.png delete mode 100644 docs/mrs/umn/en-us_image_0269417410.png delete mode 100644 docs/mrs/umn/en-us_image_0269417413.png delete mode 100644 docs/mrs/umn/en-us_image_0269417414.png delete mode 100644 docs/mrs/umn/en-us_image_0269417415.png delete mode 100644 docs/mrs/umn/en-us_image_0269417416.png delete mode 100644 docs/mrs/umn/en-us_image_0269417417.png delete mode 100644 docs/mrs/umn/en-us_image_0269417418.png delete mode 100644 docs/mrs/umn/en-us_image_0269417419.png delete mode 100644 docs/mrs/umn/en-us_image_0269417420.png delete mode 100644 docs/mrs/umn/en-us_image_0269417421.png delete mode 100644 docs/mrs/umn/en-us_image_0269417422.png delete mode 100644 docs/mrs/umn/en-us_image_0269417423.png delete mode 100644 docs/mrs/umn/en-us_image_0269417427.png delete mode 100644 docs/mrs/umn/en-us_image_0269417428.png delete mode 100644 docs/mrs/umn/en-us_image_0269417429.png delete mode 100644 docs/mrs/umn/en-us_image_0269417439.png delete mode 100644 docs/mrs/umn/en-us_image_0269417447.png delete mode 100644 docs/mrs/umn/en-us_image_0269417449.png delete mode 100644 docs/mrs/umn/en-us_image_0269417455.png delete mode 100644 docs/mrs/umn/en-us_image_0269417456.png delete mode 100644 docs/mrs/umn/en-us_image_0269417458.png delete mode 100644 docs/mrs/umn/en-us_image_0269417459.png delete mode 100644 docs/mrs/umn/en-us_image_0269417460.png delete mode 100644 docs/mrs/umn/en-us_image_0269417461.png delete mode 100644 docs/mrs/umn/en-us_image_0269417462.png delete mode 100644 docs/mrs/umn/en-us_image_0269417463.png delete mode 100644 docs/mrs/umn/en-us_image_0269417464.png delete mode 100644 docs/mrs/umn/en-us_image_0269417465.png delete mode 100644 docs/mrs/umn/en-us_image_0269417466.png delete mode 100644 docs/mrs/umn/en-us_image_0269417468.png delete mode 100644 docs/mrs/umn/en-us_image_0269417469.png delete mode 100644 docs/mrs/umn/en-us_image_0269417473.png delete mode 100644 docs/mrs/umn/en-us_image_0269417499.png delete mode 100644 docs/mrs/umn/en-us_image_0269417500.png delete mode 100644 docs/mrs/umn/en-us_image_0269417501.png delete mode 100644 docs/mrs/umn/en-us_image_0269417502.png delete mode 100644 docs/mrs/umn/en-us_image_0269417503.png delete mode 100644 docs/mrs/umn/en-us_image_0269417504.png delete mode 100644 docs/mrs/umn/en-us_image_0269417505.png delete mode 100644 docs/mrs/umn/en-us_image_0269417506.png delete mode 100644 docs/mrs/umn/en-us_image_0269417510.png delete mode 100644 docs/mrs/umn/en-us_image_0269417534.png delete mode 100644 docs/mrs/umn/en-us_image_0269417535.png delete mode 100644 docs/mrs/umn/en-us_image_0269417537.png delete mode 100644 docs/mrs/umn/en-us_image_0269417538.png delete mode 100644 docs/mrs/umn/en-us_image_0269417539.png delete mode 100644 docs/mrs/umn/en-us_image_0269417540.png delete mode 100644 docs/mrs/umn/en-us_image_0269417541.png delete mode 100644 docs/mrs/umn/en-us_image_0269417542.png delete mode 100644 docs/mrs/umn/en-us_image_0269417543.gif delete mode 100644 docs/mrs/umn/en-us_image_0269417544.gif delete mode 100644 docs/mrs/umn/en-us_image_0269417545.png delete mode 100644 docs/mrs/umn/en-us_image_0269417546.png delete mode 100644 docs/mrs/umn/en-us_image_0269417547.png delete mode 100644 docs/mrs/umn/en-us_image_0269417548.png delete mode 100644 docs/mrs/umn/en-us_image_0269417549.png delete mode 100644 docs/mrs/umn/en-us_image_0269623978.png delete mode 100644 docs/mrs/umn/en-us_image_0269624001.png delete mode 100644 docs/mrs/umn/en-us_image_0270938821.png delete mode 100644 docs/mrs/umn/en-us_image_0276137853.png delete mode 100644 docs/mrs/umn/en-us_image_0276137857.png delete mode 100644 docs/mrs/umn/en-us_image_0276137858.png delete mode 100644 docs/mrs/umn/en-us_image_0276137859.png delete mode 100644 docs/mrs/umn/en-us_image_0276801805.png delete mode 100644 docs/mrs/umn/en-us_image_0278119935.png delete mode 100644 docs/mrs/umn/en-us_image_0279536633.png delete mode 100644 docs/mrs/umn/en-us_image_0293101307.png delete mode 100644 docs/mrs/umn/en-us_image_0293131436.png delete mode 100644 docs/mrs/umn/en-us_image_0293180907.png delete mode 100644 docs/mrs/umn/en-us_image_0293234930.png delete mode 100644 docs/mrs/umn/en-us_image_0293235730.png delete mode 100644 docs/mrs/umn/en-us_image_0293242788.png delete mode 100644 docs/mrs/umn/en-us_image_0293245149.png delete mode 100644 docs/mrs/umn/en-us_image_0293246465.png delete mode 100644 docs/mrs/umn/en-us_image_0293246731.png delete mode 100644 docs/mrs/umn/en-us_image_0293247048.png delete mode 100644 docs/mrs/umn/en-us_image_0293247437.png delete mode 100644 docs/mrs/umn/en-us_image_0293267262.png delete mode 100644 docs/mrs/umn/en-us_image_0293268152.png delete mode 100644 docs/mrs/umn/en-us_image_0293269028.png delete mode 100644 docs/mrs/umn/en-us_image_0293269047.png delete mode 100644 docs/mrs/umn/en-us_image_0293269551.png delete mode 100644 docs/mrs/umn/en-us_image_0295310731.png delete mode 100644 docs/mrs/umn/en-us_image_0295554634.png delete mode 100644 docs/mrs/umn/en-us_image_0295706662.png delete mode 100644 docs/mrs/umn/en-us_topic_0000001098596550.html delete mode 100644 docs/mrs/umn/en-us_topic_0000001145356345.html delete mode 100644 docs/mrs/umn/en-us_topic_0000001145596307.html delete mode 100644 docs/mrs/umn/en-us_topic_0000001145597621.html delete mode 100644 docs/mrs/umn/en-us_topic_0000001145676237.html delete mode 100644 docs/mrs/umn/en-us_topic_0000001152828323.html delete mode 100644 docs/mrs/umn/en-us_topic_0000001295768772.html delete mode 100644 docs/mrs/umn/mrs_01_0497.html create mode 100644 docs/mrs/umn/mrs_01_248971.html create mode 100644 docs/mrs/umn/mrs_01_248972.html create mode 100644 docs/mrs/umn/mrs_01_248973.html create mode 100644 docs/mrs/umn/mrs_01_9043.html delete mode 100644 docs/mrs/umn/mrs_03_1172.html delete mode 100644 docs/mrs/umn/mrs_03_1257.html diff --git a/docs/mrs/umn/ALL_META.TXT.json b/docs/mrs/umn/ALL_META.TXT.json index 0017ed0f..a514b31d 100644 --- a/docs/mrs/umn/ALL_META.TXT.json +++ b/docs/mrs/umn/ALL_META.TXT.json @@ -3471,11 +3471,62 @@ "title":"Manually Scaling In a Cluster", "githuburl":"" }, + { + "uri":"mrs_01_248971.html", + "node_id":"mrs_01_248971.xml", + "product_code":"", + "code":"188", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"", + "kw":"Removing ClickHouseServer Instance Nodes", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Removing ClickHouseServer Instance Nodes", + "githuburl":"" + }, + { + "uri":"mrs_01_248972.html", + "node_id":"mrs_01_248972.xml", + "product_code":"", + "code":"189", + "des":"If a cluster has only one shard, the instance nodes cannot be removed from the cluster.Multiple instance nodes in the same shard must be decommissioned or recommissioned ", + "doc_type":"", + "kw":"Constraints on ClickHouseServer Scale-in,Removing ClickHouseServer Instance Nodes,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Constraints on ClickHouseServer Scale-in", + "githuburl":"" + }, + { + "uri":"mrs_01_248973.html", + "node_id":"mrs_01_248973.xml", + "product_code":"", + "code":"190", + "des":"Before removing ClickHouseServer instance nodes, you need to decommission them. Multiple node replicas of the same shard must be decommissioned at the same time. If there", + "doc_type":"", + "kw":"Scaling In ClickHouseServer Nodes,Removing ClickHouseServer Instance Nodes,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Scaling In ClickHouseServer Nodes", + "githuburl":"" + }, { "uri":"mrs_01_0211.html", "node_id":"mrs_01_0211.xml", "product_code":"mrs", - "code":"188", + "code":"191", "des":"To check an abnormal or faulty host (node), you need to stop all host roles on MRS. To recover host services after the host fault is rectified, restart all roles.You have", "doc_type":"usermanual", "kw":"Managing a Host (Node),Managing Nodes,User Guide", @@ -3495,7 +3546,7 @@ "uri":"mrs_01_0212.html", "node_id":"mrs_01_0212.xml", "product_code":"mrs", - "code":"189", + "code":"192", "des":"If a host is found to be abnormal or faulty, affecting cluster performance or preventing services from being provided, you can temporarily exclude that host from the avai", "doc_type":"usermanual", "kw":"Isolating a Host,Managing Nodes,User Guide", @@ -3515,7 +3566,7 @@ "uri":"mrs_01_0213.html", "node_id":"mrs_01_0213.xml", "product_code":"mrs", - "code":"190", + "code":"193", "des":"After the exception or fault of a host is handled, you must cancel the isolation of the host for proper usage.You can cancel the isolation of a host on MRS.The host is in", "doc_type":"usermanual", "kw":"Canceling Host Isolation,Managing Nodes,User Guide", @@ -3535,7 +3586,7 @@ "uri":"mrs_01_0522.html", "node_id":"mrs_01_0522.xml", "product_code":"mrs", - "code":"191", + "code":"194", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Job Management", @@ -3554,7 +3605,7 @@ "uri":"mrs_01_0051.html", "node_id":"mrs_01_0051.xml", "product_code":"mrs", - "code":"192", + "code":"195", "des":"An MRS job is the program execution platform of MRS. It is used to process and analyze user data. After a job is created, all job information is displayed on the Jobs tab", "doc_type":"usermanual", "kw":"Introduction to MRS Jobs,Job Management,User Guide", @@ -3574,7 +3625,7 @@ "uri":"mrs_01_0052.html", "node_id":"mrs_01_0052.xml", "product_code":"mrs", - "code":"193", + "code":"196", "des":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a MapReduce job on the MRS management c", "doc_type":"usermanual", "kw":"Running a MapReduce Job,Job Management,User Guide", @@ -3594,7 +3645,7 @@ "uri":"mrs_01_0524.html", "node_id":"mrs_01_0524.xml", "product_code":"mrs", - "code":"194", + "code":"197", "des":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a Spark job on the MRS console.You have", "doc_type":"usermanual", "kw":"Running a SparkSubmit Job,Job Management,User Guide", @@ -3614,7 +3665,7 @@ "uri":"mrs_01_0525.html", "node_id":"mrs_01_0525.xml", "product_code":"mrs", - "code":"195", + "code":"198", "des":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a HiveSQL job on the MRS management con", "doc_type":"usermanual", "kw":"Running a HiveSQL Job,Job Management,User Guide", @@ -3634,7 +3685,7 @@ "uri":"mrs_01_0526.html", "node_id":"mrs_01_0526.xml", "product_code":"mrs", - "code":"196", + "code":"199", "des":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a SparkSQL job on the MRS console. Spar", "doc_type":"usermanual", "kw":"Running a SparkSql Job,Job Management,User Guide", @@ -3654,7 +3705,7 @@ "uri":"mrs_01_0527.html", "node_id":"mrs_01_0527.xml", "product_code":"mrs", - "code":"197", + "code":"200", "des":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a Flink job on the MRS management conso", "doc_type":"usermanual", "kw":"Running a Flink Job,Job Management,User Guide", @@ -3674,7 +3725,7 @@ "uri":"mrs_01_0494.html", "node_id":"mrs_01_0494.xml", "product_code":"mrs", - "code":"198", + "code":"201", "des":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This topic describes how to generate and consume messages in a Kafka topic.C", "doc_type":"usermanual", "kw":"Running a Kafka Job,Job Management,User Guide", @@ -3694,7 +3745,7 @@ "uri":"mrs_01_0055.html", "node_id":"mrs_01_0055.xml", "product_code":"mrs", - "code":"199", + "code":"202", "des":"This section describes how to view job configuration and logs.You can view configuration information of all jobs.You can only view logs of running jobs.Because logs of Sp", "doc_type":"usermanual", "kw":"Viewing Job Configuration and Logs,Job Management,User Guide", @@ -3713,7 +3764,7 @@ "uri":"mrs_01_0056.html", "node_id":"mrs_01_0056.xml", "product_code":"mrs", - "code":"200", + "code":"203", "des":"This section describes how to stop running MRS jobs.You cannot stop Spark SQL jobs. After a job is stopped, its status changes to Terminated and the job cannot be execute", "doc_type":"usermanual", "kw":"Stopping a Job,Job Management,User Guide", @@ -3732,7 +3783,7 @@ "uri":"mrs_01_0057.html", "node_id":"mrs_01_0057.xml", "product_code":"mrs", - "code":"201", + "code":"204", "des":"This section describes how to copy new MRS jobs. Only clusters whose version is MRS 1.7.2 or earlier support job replication.Currently, all types of jobs except for Spark", "doc_type":"usermanual", "kw":"Copying Jobs,Job Management,User Guide", @@ -3752,7 +3803,7 @@ "uri":"mrs_01_0058.html", "node_id":"mrs_01_0058.xml", "product_code":"mrs", - "code":"202", + "code":"205", "des":"This section describes how to delete an MRS job. After a job is executed, you can delete it if you do not need to view its information.Jobs can be deleted one after anoth", "doc_type":"usermanual", "kw":"Deleting a Job,Job Management,User Guide", @@ -3770,7 +3821,7 @@ "uri":"mrs_01_0762.html", "node_id":"mrs_01_0762.xml", "product_code":"mrs", - "code":"203", + "code":"206", "des":"MRS uses SMN to offer a publish/subscribe model to achieve one-to-multiple message subscriptions and notifications in a variety of message types (SMSs and emails). You ca", "doc_type":"usermanual", "kw":"Configuring Job Notification Rules,Job Management,User Guide", @@ -3790,7 +3841,7 @@ "uri":"mrs_01_0200.html", "node_id":"mrs_01_0200.xml", "product_code":"mrs", - "code":"204", + "code":"207", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Component Management", @@ -3809,7 +3860,7 @@ "uri":"mrs_01_0201.html", "node_id":"mrs_01_0201.xml", "product_code":"mrs", - "code":"205", + "code":"208", "des":"MRS contains different types of basic objects. Table 1 describes these objects.", "doc_type":"usermanual", "kw":"Object Management,Component Management,User Guide", @@ -3828,7 +3879,7 @@ "uri":"mrs_01_0202.html", "node_id":"mrs_01_0202.xml", "product_code":"mrs", - "code":"206", + "code":"209", "des":"On MRS, you can view the configuration of services (including roles) and role instances.You have synchronized IAM users. (On the Dashboard page, click Synchronize on the ", "doc_type":"usermanual", "kw":"Viewing Configuration,Component Management,User Guide", @@ -3848,7 +3899,7 @@ "uri":"mrs_01_0203.html", "node_id":"mrs_01_0203.xml", "product_code":"mrs", - "code":"207", + "code":"210", "des":"You can perform the following operations on MRS:Start the service in the Stopped, Stop Failed, or Failed to Start state to use the service.Stop the services or stop abnor", "doc_type":"usermanual", "kw":"Managing Services,Component Management,User Guide", @@ -3868,7 +3919,7 @@ "uri":"mrs_01_0204.html", "node_id":"mrs_01_0204.xml", "product_code":"mrs", - "code":"208", + "code":"211", "des":"On the MRS console, you can view and modify the default service configurations based on site requirements and export or import the configurations.You need to download and", "doc_type":"usermanual", "kw":"Configuring Service Parameters,Component Management,User Guide", @@ -3888,7 +3939,7 @@ "uri":"mrs_01_0205.html", "node_id":"mrs_01_0205.xml", "product_code":"mrs", - "code":"209", + "code":"212", "des":"Each component of MRS supports all open-source parameters. MRS supports the modification of some parameters for key application scenarios. Some component clients may not ", "doc_type":"usermanual", "kw":"Configuring Customized Service Parameters,Component Management,User Guide", @@ -3908,7 +3959,7 @@ "uri":"mrs_01_0206.html", "node_id":"mrs_01_0206.xml", "product_code":"mrs", - "code":"210", + "code":"213", "des":"If Configuration Status of some services is Configuration expired or Configuration failed, synchronize configuration for the cluster or service to restore its configurati", "doc_type":"usermanual", "kw":"Synchronizing Service Configuration,Component Management,User Guide", @@ -3928,7 +3979,7 @@ "uri":"mrs_01_0207.html", "node_id":"mrs_01_0207.xml", "product_code":"mrs", - "code":"211", + "code":"214", "des":"You can start a role instance that is in the Stopped, Failed to stop or Failed to start status, stop an unused or abnormal role instance or restart an abnormal role insta", "doc_type":"usermanual", "kw":"Managing Role Instances,Component Management,User Guide", @@ -3948,7 +3999,7 @@ "uri":"mrs_01_0208.html", "node_id":"mrs_01_0208.xml", "product_code":"mrs", - "code":"212", + "code":"215", "des":"You can view and modify default role instance configuration on MRS based on site requirements. The configurations can be imported and exported.You need to download and up", "doc_type":"usermanual", "kw":"Configuring Role Instance Parameters,Component Management,User Guide", @@ -3968,7 +4019,7 @@ "uri":"mrs_01_0209.html", "node_id":"mrs_01_0209.xml", "product_code":"mrs", - "code":"213", + "code":"216", "des":"When Configuration Status of a role instance is Configuration expired or Configuration failed, you can synchronize the configuration data of the role instance with the ba", "doc_type":"usermanual", "kw":"Synchronizing Role Instance Configuration,Component Management,User Guide", @@ -3988,7 +4039,7 @@ "uri":"mrs_01_0210.html", "node_id":"mrs_01_0210.xml", "product_code":"mrs", - "code":"214", + "code":"217", "des":"If a Core or Task node is faulty, the cluster status may be displayed as Abnormal. In an MRS cluster, data can be stored on different Core nodes. You can decommission the", "doc_type":"usermanual", "kw":"Decommissioning and Recommissioning a Role Instance,Component Management,User Guide", @@ -4008,7 +4059,7 @@ "uri":"mrs_01_0214.html", "node_id":"mrs_01_0214.xml", "product_code":"mrs", - "code":"215", + "code":"218", "des":"A cluster is a collection of service components. You can start or stop all services in a cluster.You have synchronized IAM users. (On the Dashboard page, click Synchroniz", "doc_type":"usermanual", "kw":"Starting and Stopping a Cluster,Component Management,User Guide", @@ -4028,7 +4079,7 @@ "uri":"mrs_01_0215.html", "node_id":"mrs_01_0215.xml", "product_code":"mrs", - "code":"216", + "code":"219", "des":"If Configuration Status of all services or some services is Configuration expired or Configuration failed, synchronize configuration for the cluster or service to restore", "doc_type":"usermanual", "kw":"Synchronizing Cluster Configuration,Component Management,User Guide", @@ -4048,7 +4099,7 @@ "uri":"mrs_01_0216.html", "node_id":"mrs_01_0216.xml", "product_code":"mrs", - "code":"217", + "code":"220", "des":"You can export all configuration data of a cluster using MRS to meet site requirements. The exported configuration data is used to rapidly update service configuration.In", "doc_type":"usermanual", "kw":"Exporting Cluster Configuration,Component Management,User Guide", @@ -4068,7 +4119,7 @@ "uri":"mrs_01_0628.html", "node_id":"mrs_01_0628.xml", "product_code":"mrs", - "code":"218", + "code":"221", "des":"After modifying the configuration items of a big data component, you need to restart the corresponding service to make new configurations take effect. If you use a normal", "doc_type":"usermanual", "kw":"Performing Rolling Restart,Component Management,User Guide", @@ -4087,7 +4138,7 @@ "uri":"mrs_01_0112.html", "node_id":"mrs_01_0112.xml", "product_code":"mrs", - "code":"219", + "code":"222", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarm Management", @@ -4106,7 +4157,7 @@ "uri":"en-us_topic_0040980162.html", "node_id":"en-us_topic_0040980162.xml", "product_code":"mrs", - "code":"220", + "code":"223", "des":"The alarm list displays all alarms in the MRS cluster. The MRS page displays the alarms that need to be handled in a timely manner and the events.On the MRS management co", "doc_type":"usermanual", "kw":"Viewing the Alarm List,Alarm Management,User Guide", @@ -4125,7 +4176,7 @@ "uri":"mrs_01_0602.html", "node_id":"mrs_01_0602.xml", "product_code":"mrs", - "code":"221", + "code":"224", "des":"The event list displays information about all events in a cluster, such as service restart and service termination.Events are listed in chronological order by default in ", "doc_type":"usermanual", "kw":"Viewing the Event List,Alarm Management,User Guide", @@ -4145,7 +4196,7 @@ "uri":"mrs_01_0113.html", "node_id":"mrs_01_0113.xml", "product_code":"mrs", - "code":"222", + "code":"225", "des":"You can view and clear alarms on MRS.Generally, the system automatically clears an alarm when the fault is rectified. If the fault has been rectified and the alarm cannot", "doc_type":"usermanual", "kw":"Viewing and Manually Clearing an Alarm,Alarm Management,User Guide", @@ -4164,7 +4215,7 @@ "uri":"mrs_01_0409.html", "node_id":"mrs_01_0409.xml", "product_code":"mrs", - "code":"223", + "code":"226", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Patch Management", @@ -4183,7 +4234,7 @@ "uri":"mrs_01_0410.html", "node_id":"mrs_01_0410.xml", "product_code":"mrs", - "code":"224", + "code":"227", "des":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", "doc_type":"usermanual", "kw":"Patch Operation Guide for Versions Earlier than MRS 1.7.0,Patch Management,User Guide", @@ -4203,7 +4254,7 @@ "uri":"mrs_01_0411.html", "node_id":"mrs_01_0411.xml", "product_code":"mrs", - "code":"225", + "code":"228", "des":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", "doc_type":"usermanual", "kw":"Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0,Patch Management,User Guide", @@ -4223,7 +4274,7 @@ "uri":"mrs_01_0431.html", "node_id":"mrs_01_0431.xml", "product_code":"mrs", - "code":"226", + "code":"229", "des":"The rolling patch function indicates that patches are installed or uninstalled for one or more services in a cluster by performing a rolling service restart (restarting s", "doc_type":"usermanual", "kw":"Rolling Patches,Patch Management,User Guide", @@ -4243,7 +4294,7 @@ "uri":"mrs_01_0412.html", "node_id":"mrs_01_0412.xml", "product_code":"mrs", - "code":"227", + "code":"230", "des":"If some hosts are isolated in a cluster, perform the following operations to restore patches for these isolated hosts after patch installation on other hosts in the clust", "doc_type":"usermanual", "kw":"Restoring Patches for the Isolated Hosts,Patch Management,User Guide", @@ -4263,7 +4314,7 @@ "uri":"mrs_01_248926.html", "node_id":"mrs_01_248926.xml", "product_code":"mrs", - "code":"228", + "code":"231", "des":"When a new patch is available in the cluster, the system pushes the patch online. You can install the patch in a few clicks.This section applies only to MRS 2.x and earli", "doc_type":"usermanual", "kw":"Patch Update,Patch Management,User Guide", @@ -4277,11 +4328,28 @@ "title":"Patch Update", "githuburl":"" }, + { + "uri":"mrs_01_9043.html", + "node_id":"mrs_01_9043.xml", + "product_code":"", + "code":"232", + "des":"After the MRS 3.1.2-LTS.2.14 patch is installed, a message may be displayed indicating that the client patch package fails to be generated. To solve this problem, perform", + "doc_type":"", + "kw":"MRS 3.1.2-LTS.2 Patch Description,Patch Management,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"MRS 3.1.2-LTS.2 Patch Description", + "githuburl":"" + }, { "uri":"mrs_01_0303.html", "node_id":"mrs_01_0303.xml", "product_code":"mrs", - "code":"229", + "code":"233", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Tenant Management", @@ -4301,7 +4369,7 @@ "uri":"mrs_01_0604.html", "node_id":"mrs_01_0604.xml", "product_code":"mrs", - "code":"230", + "code":"234", "des":"This section describes how to manage tenants on the MRS console.Tenant management operations on the console apply only to clusters of versions earlier than MRS 3.x.Tenant", "doc_type":"usermanual", "kw":"Before You Start,Tenant Management,User Guide", @@ -4321,7 +4389,7 @@ "uri":"mrs_01_0304.html", "node_id":"mrs_01_0304.xml", "product_code":"mrs", - "code":"231", + "code":"235", "des":"An MRS cluster provides various resources and services for multiple organizations, departments, or applications to share. The cluster provides tenants as a logical entity", "doc_type":"usermanual", "kw":"Overview,Tenant Management,User Guide", @@ -4341,7 +4409,7 @@ "uri":"mrs_01_0305.html", "node_id":"mrs_01_0305.xml", "product_code":"mrs", - "code":"232", + "code":"236", "des":"You can create a tenant on MRS Manager to specify the resource usage.A tenant name has been planned. The name must not be the same as that of a role or Yarn queue that ex", "doc_type":"usermanual", "kw":"Creating a Tenant,Tenant Management,User Guide", @@ -4361,7 +4429,7 @@ "uri":"mrs_01_0306.html", "node_id":"mrs_01_0306.xml", "product_code":"mrs", - "code":"233", + "code":"237", "des":"You can create a sub-tenant on MRS if the resources of the current tenant need to be further allocated.A parent tenant has been added.A tenant name has been planned. The ", "doc_type":"usermanual", "kw":"Creating a Sub-tenant,Tenant Management,User Guide", @@ -4381,7 +4449,7 @@ "uri":"mrs_01_0307.html", "node_id":"mrs_01_0307.xml", "product_code":"mrs", - "code":"234", + "code":"238", "des":"You can delete a tenant that is not required on MRS.A tenant has been added.You have checked whether the tenant to be deleted has sub-tenants. If the tenant has sub-tenan", "doc_type":"usermanual", "kw":"Deleting a Tenant,Tenant Management,User Guide", @@ -4401,7 +4469,7 @@ "uri":"mrs_01_0308.html", "node_id":"mrs_01_0308.xml", "product_code":"mrs", - "code":"235", + "code":"239", "des":"You can manage the HDFS storage directory used by a specific tenant on MRS. The management operations include adding a tenant directory, modifying the directory file quot", "doc_type":"usermanual", "kw":"Managing a Tenant Directory,Tenant Management,User Guide", @@ -4421,7 +4489,7 @@ "uri":"mrs_01_0309.html", "node_id":"mrs_01_0309.xml", "product_code":"mrs", - "code":"236", + "code":"240", "des":"Tenant data is stored on Manager and in cluster components by default. When components are restored from faults or reinstalled, some tenant configuration data may be abno", "doc_type":"usermanual", "kw":"Restoring Tenant Data,Tenant Management,User Guide", @@ -4441,7 +4509,7 @@ "uri":"mrs_01_0310.html", "node_id":"mrs_01_0310.xml", "product_code":"mrs", - "code":"237", + "code":"241", "des":"In an MRS cluster, users can logically divide Yarn cluster nodes to combine multiple NodeManagers into a Yarn resource pool. Each NodeManager belongs to one resource pool", "doc_type":"usermanual", "kw":"Creating a Resource Pool,Tenant Management,User Guide", @@ -4461,7 +4529,7 @@ "uri":"mrs_01_0311.html", "node_id":"mrs_01_0311.xml", "product_code":"mrs", - "code":"238", + "code":"242", "des":"You can modify members of an existing resource pool on MRS.You have synchronized IAM users. (On the Dashboard page, click Synchronize on the right side of IAM User Sync t", "doc_type":"usermanual", "kw":"Modifying a Resource Pool,Tenant Management,User Guide", @@ -4481,7 +4549,7 @@ "uri":"mrs_01_0312.html", "node_id":"mrs_01_0312.xml", "product_code":"mrs", - "code":"239", + "code":"243", "des":"You can delete an existing resource pool on MRS.Any queue in a cluster cannot use the resource pool to be deleted as the default resource pool. Before deleting the resour", "doc_type":"usermanual", "kw":"Deleting a Resource Pool,Tenant Management,User Guide", @@ -4501,7 +4569,7 @@ "uri":"mrs_01_0313.html", "node_id":"mrs_01_0313.xml", "product_code":"mrs", - "code":"240", + "code":"244", "des":"You can modify the queue configuration of a specified tenant on MRS based on service requirements.A tenant associated with Yarn and allocated dynamic resources has been a", "doc_type":"usermanual", "kw":"Configuring a Queue,Tenant Management,User Guide", @@ -4521,7 +4589,7 @@ "uri":"mrs_01_0314.html", "node_id":"mrs_01_0314.xml", "product_code":"mrs", - "code":"241", + "code":"245", "des":"After a resource pool is added, the capacity policies of available resources need to be configured for Yarn task queues. This ensures that tasks in the resource pool are ", "doc_type":"usermanual", "kw":"Configuring the Queue Capacity Policy of a Resource Pool,Tenant Management,User Guide", @@ -4541,7 +4609,7 @@ "uri":"mrs_01_0315.html", "node_id":"mrs_01_0315.xml", "product_code":"mrs", - "code":"242", + "code":"246", "des":"Users can clear the configuration of a queue on MRS Manager when the queue does not need resources from a resource pool or if a resource pool needs to be disassociated fr", "doc_type":"usermanual", "kw":"Clearing Configuration of a Queue,Tenant Management,User Guide", @@ -4561,7 +4629,7 @@ "uri":"mrs_01_24565.html", "node_id":"mrs_01_24565.xml", "product_code":"mrs", - "code":"243", + "code":"247", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Bootstrap Actions", @@ -4579,7 +4647,7 @@ "uri":"mrs_01_0414.html", "node_id":"mrs_01_0414.xml", "product_code":"mrs", - "code":"244", + "code":"248", "des":"Bootstrap actions indicate that you can run your scripts on a specified cluster node before or after starting big data components. You can run bootstrap actions to instal", "doc_type":"usermanual", "kw":"Introduction to Bootstrap Actions,Bootstrap Actions,User Guide", @@ -4599,7 +4667,7 @@ "uri":"mrs_01_0417.html", "node_id":"mrs_01_0417.xml", "product_code":"mrs", - "code":"245", + "code":"249", "des":"Currently, bootstrap actions support Linux shell scripts only. Script files must end with .sh.Before compiling a script, you need to upload all required installation pack", "doc_type":"usermanual", "kw":"Preparing the Bootstrap Action Script,Bootstrap Actions,User Guide", @@ -4619,7 +4687,7 @@ "uri":"mrs_01_0415.html", "node_id":"mrs_01_0415.xml", "product_code":"mrs", - "code":"246", + "code":"250", "des":"You can view the execution result of the bootstrap operation on the Bootstrap Action page.Log in to the MRS console.In the left navigation pane, choose Clusters > Active ", "doc_type":"usermanual", "kw":"View Execution Records,Bootstrap Actions,User Guide", @@ -4639,7 +4707,7 @@ "uri":"mrs_01_0416.html", "node_id":"mrs_01_0416.xml", "product_code":"mrs", - "code":"247", + "code":"251", "des":"Add a bootstrap action.This operation applies to clusters earlier than MRS 3.x.", "doc_type":"usermanual", "kw":"Adding a Bootstrap Action,Bootstrap Actions,User Guide", @@ -4659,7 +4727,7 @@ "uri":"mrs_01_24566.html", "node_id":"mrs_01_24566.xml", "product_code":"mrs", - "code":"248", + "code":"252", "des":"Modify an existing bootstrap action on an MRS cluster.", "doc_type":"usermanual", "kw":"Modifying a Bootstrap Action,Bootstrap Actions,User Guide", @@ -4679,7 +4747,7 @@ "uri":"mrs_01_24567.html", "node_id":"mrs_01_24567.xml", "product_code":"mrs", - "code":"249", + "code":"253", "des":"Delete a bootstrap action on an MRS cluster.", "doc_type":"usermanual", "kw":"Deleting a Bootstrap Action,Bootstrap Actions,User Guide", @@ -4699,7 +4767,7 @@ "uri":"mrs_01_0418.html", "node_id":"mrs_01_0418.xml", "product_code":"mrs", - "code":"250", + "code":"254", "des":"Zeppelin is a web-based notebook that supports interactive data analysis. For more information, visit the Zeppelin official website at http://zeppelin.apache.org/.This sa", "doc_type":"usermanual", "kw":"Sample Scripts,Bootstrap Actions,User Guide", @@ -4719,7 +4787,7 @@ "uri":"mrs_01_0088.html", "node_id":"mrs_01_0088.xml", "product_code":"mrs", - "code":"251", + "code":"255", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Using an MRS Client", @@ -4738,7 +4806,7 @@ "uri":"mrs_01_24212.html", "node_id":"mrs_01_24212.xml", "product_code":"mrs", - "code":"252", + "code":"256", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Installing a Client", @@ -4756,7 +4824,7 @@ "uri":"mrs_01_0090.html", "node_id":"mrs_01_0090.xml", "product_code":"mrs", - "code":"253", + "code":"257", "des":"This section describes how to install clients of all services (excluding Flume) in an MRS cluster. For details about how to install the Flume client, see Installing the F", "doc_type":"usermanual", "kw":"Installing a Client (Version 3.x or Later),Installing a Client,User Guide", @@ -4776,7 +4844,7 @@ "uri":"mrs_01_0091.html", "node_id":"mrs_01_0091.xml", "product_code":"mrs", - "code":"254", + "code":"258", "des":"An MRS client is required. The MRS cluster client can be installed on the Master or Core node in the cluster or on a node outside the cluster.After a cluster of versions ", "doc_type":"usermanual", "kw":"Installing a Client (Versions Earlier Than 3.x),Installing a Client,User Guide", @@ -4796,7 +4864,7 @@ "uri":"mrs_01_24213.html", "node_id":"mrs_01_24213.xml", "product_code":"mrs", - "code":"255", + "code":"259", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Updating a Client", @@ -4814,7 +4882,7 @@ "uri":"mrs_01_24209.html", "node_id":"mrs_01_24209.xml", "product_code":"mrs", - "code":"256", + "code":"260", "des":"A cluster provides a client for you to connect to a server, view task results, or manage data. If you modify service configuration parameters on Manager and restart the s", "doc_type":"usermanual", "kw":"Updating a Client (Version 3.x or Later),Updating a Client,User Guide", @@ -4834,7 +4902,7 @@ "uri":"mrs_01_0089.html", "node_id":"mrs_01_0089.xml", "product_code":"mrs", - "code":"257", + "code":"261", "des":"This section applies to clusters of versions earlier than MRS 3.x. For MRS 3.x or later, see Updating a Client (Version 3.x or Later).ScenarioAn MRS cluster provides a cl", "doc_type":"usermanual", "kw":"Updating a Client (Versions Earlier Than 3.x),Updating a Client,User Guide", @@ -4854,7 +4922,7 @@ "uri":"mrs_01_24183.html", "node_id":"mrs_01_24183.xml", "product_code":"mrs", - "code":"258", + "code":"262", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Using the Client of Each Component", @@ -4872,7 +4940,7 @@ "uri":"mrs_01_24184.html", "node_id":"mrs_01_24184.xml", "product_code":"mrs", - "code":"259", + "code":"263", "des":"ClickHouse is a column-based database oriented to online analysis and processing. It supports SQL query and provides good query performance. The aggregation analysis and ", "doc_type":"cmpntguide", "kw":"Using a ClickHouse Client,Using the Client of Each Component,User Guide", @@ -4890,7 +4958,7 @@ "uri":"mrs_01_24185.html", "node_id":"mrs_01_24185.xml", "product_code":"mrs", - "code":"260", + "code":"264", "des":"This section describes how to use Flink to run wordcount jobs.Flink has been installed in an MRS cluster.The cluster runs properly and the client has been correctly insta", "doc_type":"cmpntguide", "kw":"Using a Flink Client,Using the Client of Each Component,User Guide", @@ -4908,7 +4976,7 @@ "uri":"mrs_01_24186.html", "node_id":"mrs_01_24186.xml", "product_code":"mrs", - "code":"261", + "code":"265", "des":"You can use Flume to import collected log information to Kafka.A streaming cluster that contains components such as Flume and Kafka and has Kerberos authentication enable", "doc_type":"cmpntguide", "kw":"Using a Flume Client,Using the Client of Each Component,User Guide", @@ -4926,7 +4994,7 @@ "uri":"mrs_01_24187.html", "node_id":"mrs_01_24187.xml", "product_code":"mrs", - "code":"262", + "code":"266", "des":"This section describes how to use the HBase client in an O&M scenario or a service scenario.The client has been installed. For example, the installation directory is /opt", "doc_type":"cmpntguide", "kw":"Using an HBase Client,Using the Client of Each Component,User Guide", @@ -4944,7 +5012,7 @@ "uri":"mrs_01_24188.html", "node_id":"mrs_01_24188.xml", "product_code":"mrs", - "code":"263", + "code":"267", "des":"This section describes how to use the HDFS client in an O&M scenario or service scenario.The client has been installed.For example, the installation directory is /opt/had", "doc_type":"cmpntguide", "kw":"Using an HDFS Client,Using the Client of Each Component,User Guide", @@ -4962,7 +5030,7 @@ "uri":"mrs_01_24189.html", "node_id":"mrs_01_24189.xml", "product_code":"mrs", - "code":"264", + "code":"268", "des":"This section guides users to use a Hive client in an O&M or service scenario.The client has been installed. For example, the client is installed in the /opt/hadoopclient ", "doc_type":"cmpntguide", "kw":"Using a Hive Client,Using the Client of Each Component,User Guide", @@ -4980,7 +5048,7 @@ "uri":"mrs_01_24191.html", "node_id":"mrs_01_24191.xml", "product_code":"mrs", - "code":"265", + "code":"269", "des":"You can create, query, and delete topics on a cluster client.The client has been installed. For example, the client is installed in the /opt/hadoopclient directory. The c", "doc_type":"cmpntguide", "kw":"Using a Kafka Client,Using the Client of Each Component,User Guide", @@ -4998,7 +5066,7 @@ "uri":"mrs_01_24193.html", "node_id":"mrs_01_24193.xml", "product_code":"mrs", - "code":"266", + "code":"270", "des":"This section describes how to use the Oozie client in an O&M scenario or service scenario.The client has been installed. For example, the installation directory is /opt/c", "doc_type":"cmpntguide", "kw":"Using the Oozie Client,Using the Client of Each Component,User Guide", @@ -5016,7 +5084,7 @@ "uri":"mrs_01_24194.html", "node_id":"mrs_01_24194.xml", "product_code":"mrs", - "code":"267", + "code":"271", "des":"This section describes how to use the Storm client in an O&M scenario or service scenario.You have installed the client. For example, the installation directory is /opt/h", "doc_type":"usermanual", "kw":"Using a Storm Client,Using the Client of Each Component,User Guide", @@ -5036,7 +5104,7 @@ "uri":"mrs_01_24196.html", "node_id":"mrs_01_24196.xml", "product_code":"mrs", - "code":"268", + "code":"272", "des":"This section guides users to use a Yarn client in an O&M or service scenario.The client has been installed.For example, the installation directory is /opt/hadoopclient. T", "doc_type":"cmpntguide", "kw":"Using a Yarn Client,Using the Client of Each Component,User Guide", @@ -5054,7 +5122,7 @@ "uri":"mrs_01_0440.html", "node_id":"mrs_01_0440.xml", "product_code":"mrs", - "code":"269", + "code":"273", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring a Cluster with Storage and Compute Decoupled", @@ -5074,7 +5142,7 @@ "uri":"mrs_01_0467.html", "node_id":"mrs_01_0467.xml", "product_code":"mrs", - "code":"270", + "code":"274", "des":"In scenarios that require large storage capacity and elastic compute resources, MRS enables you to store data in OBS and use an MRS cluster for data computing only. In th", "doc_type":"usermanual", "kw":"Introduction to Storage-Compute Decoupling,Configuring a Cluster with Storage and Compute Decoupled,", @@ -5094,7 +5162,7 @@ "uri":"mrs_01_0768.html", "node_id":"mrs_01_0768.xml", "product_code":"mrs", - "code":"271", + "code":"275", "des":"MRS allows you to store data in OBS and use an MRS cluster for data computing only. In this way, storage and compute are separated. You can create an IAM agency, which en", "doc_type":"usermanual", "kw":"Configuring a Storage-Compute Decoupled Cluster (Agency),Configuring a Cluster with Storage and Comp", @@ -5114,7 +5182,7 @@ "uri":"mrs_01_0468.html", "node_id":"mrs_01_0468.xml", "product_code":"mrs", - "code":"272", + "code":"276", "des":"In MRS 1.9.2 or later, OBS can be interconnected with MRS using obs://. Currently, Hadoop, Hive, Spark, Presto, and Flink are supported. HBase cannot use obs:// to interc", "doc_type":"usermanual", "kw":"Configuring a Storage-Compute Decoupled Cluster (AK/SK),Configuring a Cluster with Storage and Compu", @@ -5134,7 +5202,7 @@ "uri":"mrs_01_0643.html", "node_id":"mrs_01_0643.xml", "product_code":"mrs", - "code":"273", + "code":"277", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Using a Storage-Compute Decoupled Cluster", @@ -5152,7 +5220,7 @@ "uri":"mrs_01_1288.html", "node_id":"mrs_01_1288.xml", "product_code":"mrs", - "code":"274", + "code":"278", "des":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", "doc_type":"usermanual", "kw":"Interconnecting Flink with OBS,Using a Storage-Compute Decoupled Cluster,User Guide", @@ -5172,7 +5240,7 @@ "uri":"en-us_topic_0000001349137409.html", "node_id":"en-us_topic_0000001349137409.xml", "product_code":"mrs", - "code":"275", + "code":"279", "des":"This section applies to MRS 3.x or later.Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to C", "doc_type":"usermanual", "kw":"Interconnecting Flume with OBS,Using a Storage-Compute Decoupled Cluster,User Guide", @@ -5192,7 +5260,7 @@ "uri":"mrs_01_1292.html", "node_id":"mrs_01_1292.xml", "product_code":"mrs", - "code":"276", + "code":"280", "des":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", "doc_type":"usermanual", "kw":"Interconnecting HDFS with OBS,Using a Storage-Compute Decoupled Cluster,User Guide", @@ -5212,7 +5280,7 @@ "uri":"mrs_01_1286.html", "node_id":"mrs_01_1286.xml", "product_code":"mrs", - "code":"277", + "code":"281", "des":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", "doc_type":"usermanual", "kw":"Interconnecting Hive with OBS,Using a Storage-Compute Decoupled Cluster,User Guide", @@ -5232,7 +5300,7 @@ "uri":"mrs_01_0617.html", "node_id":"mrs_01_0617.xml", "product_code":"mrs", - "code":"278", + "code":"282", "des":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", "doc_type":"usermanual", "kw":"Interconnecting MapReduce with OBS,Using a Storage-Compute Decoupled Cluster,User Guide", @@ -5252,7 +5320,7 @@ "uri":"mrs_01_1289.html", "node_id":"mrs_01_1289.xml", "product_code":"mrs", - "code":"279", + "code":"283", "des":"The OBS file system can be interconnected with Spark2x after an MRS cluster is installed.Before performing the following operations, ensure that you have configured a sto", "doc_type":"usermanual", "kw":"Interconnecting Spark2x with OBS,Using a Storage-Compute Decoupled Cluster,User Guide", @@ -5272,7 +5340,7 @@ "uri":"mrs_01_24294.html", "node_id":"mrs_01_24294.xml", "product_code":"mrs", - "code":"280", + "code":"284", "des":"source /opt/client/bigdata_envsqoop export --connect jdbc:mysql://10.100.231.134:3306/test --username root --password xxxxxx --table component13 -export-dir hdfs://haclu", "doc_type":"usermanual", "kw":"Interconnecting Sqoop with External Storage Systems,Using a Storage-Compute Decoupled Cluster,User G", @@ -5292,7 +5360,7 @@ "uri":"mrs_01_24171.html", "node_id":"mrs_01_24171.xml", "product_code":"mrs", - "code":"281", + "code":"285", "des":"source ${client_home}/bigdata_envsource ${client_home}/Hudi/component_envvim ${client_home}/Hudi/hudi/conf/hdfs-site.xmlkinit Usernameimport org.apache.hudi.QuickstartUti", "doc_type":"usermanual", "kw":"Interconnecting Hudi with OBS,Using a Storage-Compute Decoupled Cluster,User Guide", @@ -5312,7 +5380,7 @@ "uri":"mrs_01_0644.html", "node_id":"mrs_01_0644.xml", "product_code":"mrs", - "code":"282", + "code":"286", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Accessing Web Pages of Open Source Components Managed in MRS Clusters", @@ -5332,7 +5400,7 @@ "uri":"mrs_01_0362.html", "node_id":"mrs_01_0362.xml", "product_code":"mrs", - "code":"283", + "code":"287", "des":"Web UIs of different components are created and hosted on the Master or Core nodes in the MRS cluster by default. You can view information about the components on these w", "doc_type":"usermanual", "kw":"Web UIs of Open Source Components,Accessing Web Pages of Open Source Components Managed in MRS Clust", @@ -5352,7 +5420,7 @@ "uri":"mrs_01_0504.html", "node_id":"mrs_01_0504.xml", "product_code":"mrs", - "code":"284", + "code":"288", "des":"The protocol type of all ports in the table is TCP (for MRS 1.6.3 or later).The protocol type of all ports in the table is TCP (for MRS 1.7.0 or later).The protocol type ", "doc_type":"usermanual", "kw":"List of Open Source Component Ports,Accessing Web Pages of Open Source Components Managed in MRS Clu", @@ -5372,7 +5440,7 @@ "uri":"mrs_01_0645.html", "node_id":"mrs_01_0645.xml", "product_code":"mrs", - "code":"285", + "code":"289", "des":"MRS allows you to access MRS clusters using Direct Connect. Direct Connect is a high-speed, low-latency, stable, and secure dedicated network connection that connects you", "doc_type":"usermanual", "kw":"Access Through Direct Connect,Accessing Web Pages of Open Source Components Managed in MRS Clusters,", @@ -5391,7 +5459,7 @@ "uri":"mrs_01_0646.html", "node_id":"mrs_01_0646.xml", "product_code":"mrs", - "code":"286", + "code":"290", "des":"You can bind an EIP to a cluster to access the web UIs of the open-source components managed in the MRS cluster. This method is simple and easy to use and is recommended ", "doc_type":"usermanual", "kw":"EIP-based Access,Accessing Web Pages of Open Source Components Managed in MRS Clusters,User Guide", @@ -5411,7 +5479,7 @@ "uri":"mrs_01_0647.html", "node_id":"mrs_01_0647.xml", "product_code":"mrs", - "code":"287", + "code":"291", "des":"MRS allows you to access the web UIs of open-source components through a Windows ECS. This method is complex and is recommended for MRS clusters that do not support the E", "doc_type":"usermanual", "kw":"Access Using a Windows ECS,Accessing Web Pages of Open Source Components Managed in MRS Clusters,Use", @@ -5431,7 +5499,7 @@ "uri":"mrs_01_0363.html", "node_id":"mrs_01_0363.xml", "product_code":"mrs", - "code":"288", + "code":"292", "des":"Users and an MRS cluster are in different networks. As a result, an SSH channel needs to be created to send users' requests for accessing websites to the MRS cluster and ", "doc_type":"usermanual", "kw":"Creating an SSH Channel for Connecting to an MRS Cluster and Configuring the Browser,Accessing Web P", @@ -5451,7 +5519,7 @@ "uri":"mrs_01_0128.html", "node_id":"mrs_01_0128.xml", "product_code":"mrs", - "code":"289", + "code":"293", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Accessing Manager", @@ -5471,10 +5539,10 @@ "uri":"mrs_01_0129.html", "node_id":"mrs_01_0129.xml", "product_code":"mrs", - "code":"290", - "des":"In MRS 3.x or later, FusionInsight Manager is used to monitor, configure, and manage clusters. After the cluster is installed, you can use the account to log in to Fusion", + "code":"294", + "des":"In an MRS cluster of version 3.x, MRS Manager is used to monitor, configure, and manage clusters. After the cluster is installed, you can use the account to log in to MRS", "doc_type":"usermanual", - "kw":"Accessing FusionInsight Manager (MRS 3.x or Later),Accessing Manager,User Guide", + "kw":"Accessing MRS Manager,Accessing Manager,User Guide", "search_title":"", "metedata":[ { @@ -5484,17 +5552,17 @@ "documenttype":"usermanual" } ], - "title":"Accessing FusionInsight Manager (MRS 3.x or Later)", + "title":"Accessing MRS Manager", "githuburl":"" }, { "uri":"mrs_01_0102.html", "node_id":"mrs_01_0102.xml", "product_code":"mrs", - "code":"291", - "des":"MRS uses FusionInsight Manager to monitor, configure, and manage clusters. You can access FusionInsight Manager by clicking Access Manager on the Dashboard tab page of yo", + "code":"295", + "des":"In an MRS cluster of version 2.x and earlier, MRS uses MRS Manager to monitor, configure, and manage clusters. You can access MRS Manager by clicking Access Manager on th", "doc_type":"usermanual", - "kw":"Accessing MRS Manager MRS 2.1.0 or Earlier),Accessing Manager,User Guide", + "kw":"Accessing MRS Manager (MRS 2.x or Earlier),Accessing Manager,User Guide", "search_title":"", "metedata":[ { @@ -5504,17 +5572,17 @@ "documenttype":"usermanual" } ], - "title":"Accessing MRS Manager MRS 2.1.0 or Earlier)", + "title":"Accessing MRS Manager (MRS 2.x or Earlier)", "githuburl":"" }, { "uri":"mrs_01_0606.html", "node_id":"mrs_01_0606.xml", "product_code":"mrs", - "code":"292", + "code":"296", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"FusionInsight Manager Operation Guide (Applicable to 3.x)", + "kw":"MRS Manager Operation Guide (Applicable to 3.x)", "search_title":"", "metedata":[ { @@ -5522,14 +5590,14 @@ "documenttype":"usermanual" } ], - "title":"FusionInsight Manager Operation Guide (Applicable to 3.x)", + "title":"MRS Manager Operation Guide (Applicable to 3.x)", "githuburl":"" }, { "uri":"admin_guide_000001.html", "node_id":"admin_guide_000001.xml", "product_code":"mrs", - "code":"293", + "code":"297", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Getting Started", @@ -5548,10 +5616,10 @@ "uri":"admin_guide_000002.html", "node_id":"admin_guide_000002.xml", "product_code":"mrs", - "code":"294", + "code":"298", "des":"MRS allows you to manage and analyze massive amounts of structured and unstructured data for rapid data mining. Open source components have complex structures and therefo", "doc_type":"usermanual", - "kw":"FusionInsight Manager Introduction,Getting Started,User Guide", + "kw":"MRS Manager Introduction,Getting Started,User Guide", "search_title":"", "metedata":[ { @@ -5559,17 +5627,17 @@ "prodname":"mrs" } ], - "title":"FusionInsight Manager Introduction", + "title":"MRS Manager Introduction", "githuburl":"" }, { "uri":"admin_guide_000003.html", "node_id":"admin_guide_000003.xml", "product_code":"mrs", - "code":"295", - "des":"By viewing the FusionInsight Manager version, you can prepare for system upgrade and routine maintenance.Using the GUI:Log in to FusionInsight Manager. On the home page, ", + "code":"299", + "des":"By viewing the MRS Manager version, you can prepare for system upgrade and routine maintenance.Using the GUI:Log in to MRS Manager. On the home page, click in the upper ", "doc_type":"usermanual", - "kw":"Querying the FusionInsight Manager Version,Getting Started,User Guide", + "kw":"Querying the MRS Manager Version,Getting Started,User Guide", "search_title":"", "metedata":[ { @@ -5577,17 +5645,17 @@ "prodname":"mrs" } ], - "title":"Querying the FusionInsight Manager Version", + "title":"Querying the MRS Manager Version", "githuburl":"" }, { "uri":"admin_guide_000004.html", "node_id":"admin_guide_000004.xml", "product_code":"mrs", - "code":"296", - "des":"Log in to FusionInsight Manager using an account.The password must:Contain 8 to 64 characters.Contain at least four types of the following characters: uppercase letters, ", + "code":"300", + "des":"Log in to MRS Manager using an account.The password must:Contain 8 to 64 characters.Contain at least four types of the following characters: uppercase letters, lowercase ", "doc_type":"usermanual", - "kw":"Logging In to FusionInsight Manager,Getting Started,User Guide", + "kw":"Logging In to MRS Manager,Getting Started,User Guide", "search_title":"", "metedata":[ { @@ -5595,14 +5663,14 @@ "prodname":"mrs" } ], - "title":"Logging In to FusionInsight Manager", + "title":"Logging In to MRS Manager", "githuburl":"" }, { "uri":"admin_guide_000005.html", "node_id":"admin_guide_000005.xml", "product_code":"mrs", - "code":"297", + "code":"301", "des":"Some O&M operation scripts and commands need to be run or can be run only on the active management node. You can identify and log in to the active or standby management n", "doc_type":"usermanual", "kw":"Logging In to the Management Node,Getting Started,User Guide", @@ -5620,7 +5688,7 @@ "uri":"admin_guide_000006.html", "node_id":"admin_guide_000006.xml", "product_code":"mrs", - "code":"298", + "code":"302", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Home Page", @@ -5639,8 +5707,8 @@ "uri":"admin_guide_000007.html", "node_id":"admin_guide_000007.xml", "product_code":"mrs", - "code":"299", - "des":"After you log in to FusionInsight Manager, Homepage is displayed by default. On this page, the Summary tab displays the service statuses and monitoring status reports of ", + "code":"303", + "des":"After you log in to MRS Manager, Homepage is displayed by default. On this page, the Summary tab displays the service statuses and monitoring status reports of each clust", "doc_type":"usermanual", "kw":"Overview,Home Page,User Guide", "search_title":"", @@ -5657,8 +5725,8 @@ "uri":"admin_guide_000008.html", "node_id":"admin_guide_000008.xml", "product_code":"mrs", - "code":"300", - "des":"On FusionInsight Manager, you can customize monitoring items to display on the homepage and export monitoring data.The interval on the horizontal axis of the chart varies", + "code":"304", + "des":"On MRS Manager, you can customize monitoring items to display on the homepage and export monitoring data.The interval on the horizontal axis of the chart varies depending", "doc_type":"usermanual", "kw":"Managing Monitoring Metric Reports,Home Page,User Guide", "search_title":"", @@ -5675,7 +5743,7 @@ "uri":"admin_guide_000009.html", "node_id":"admin_guide_000009.xml", "product_code":"mrs", - "code":"301", + "code":"305", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Cluster", @@ -5693,7 +5761,7 @@ "uri":"admin_guide_000010.html", "node_id":"admin_guide_000010.xml", "product_code":"mrs", - "code":"302", + "code":"306", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Cluster Management", @@ -5712,8 +5780,8 @@ "uri":"admin_guide_000011.html", "node_id":"admin_guide_000011.xml", "product_code":"mrs", - "code":"303", - "des":"Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Dashboard to view the status of the current cluster.On the Dashboard tab page, you can ", + "code":"307", + "des":"Log in to MRS Manager and choose Cluster > Name of the desired cluster > Dashboard to view the status of the current cluster.On the Dashboard tab page, you can start, sto", "doc_type":"usermanual", "kw":"Overview,Cluster Management,User Guide", "search_title":"", @@ -5730,7 +5798,7 @@ "uri":"admin_guide_000012.html", "node_id":"admin_guide_000012.xml", "product_code":"mrs", - "code":"304", + "code":"308", "des":"A rolling restart is batch restarting all services in a cluster after they are modified or upgraded without interrupting workloads.You can perform a rolling restart of a ", "doc_type":"usermanual", "kw":"Performing a Rolling Restart of a Cluster,Cluster Management,User Guide", @@ -5748,7 +5816,7 @@ "uri":"admin_guide_000013.html", "node_id":"admin_guide_000013.xml", "product_code":"mrs", - "code":"305", + "code":"309", "des":"If a new configuration needs to be delivered to all services in the cluster, or Configuration Status of multiple services changes to Expired or Failed after a configurati", "doc_type":"usermanual", "kw":"Managing Expired Configurations,Cluster Management,User Guide", @@ -5766,7 +5834,7 @@ "uri":"admin_guide_000014.html", "node_id":"admin_guide_000014.xml", "product_code":"mrs", - "code":"306", + "code":"310", "des":"Use the default client provided by MRS clusters to manage the cluster, run services, and perform secondary development. Before you use this client, you need to download i", "doc_type":"usermanual", "kw":"Downloading the Client,Cluster Management,User Guide", @@ -5784,8 +5852,8 @@ "uri":"admin_guide_000015.html", "node_id":"admin_guide_000015.xml", "product_code":"mrs", - "code":"307", - "des":"View basic cluster attributes on FusionInsight Manager.By default, you can view the cluster name, cluster description, product type, cluster ID, authentication mode, crea", + "code":"311", + "des":"View basic cluster attributes on MRS Manager.By default, you can view the cluster name, cluster description, product type, cluster ID, authentication mode, creation time,", "doc_type":"usermanual", "kw":"Modifying Cluster Attributes,Cluster Management,User Guide", "search_title":"", @@ -5802,8 +5870,8 @@ "uri":"admin_guide_000016.html", "node_id":"admin_guide_000016.xml", "product_code":"mrs", - "code":"308", - "des":"FusionInsight Manager allows you to view the changes of service configuration parameters in a cluster with one click, helping you quickly locate faults and improve config", + "code":"312", + "des":"MRS Manager allows you to view the changes of service configuration parameters in a cluster with one click, helping you quickly locate faults and improve configuration ma", "doc_type":"usermanual", "kw":"Managing Cluster Configurations,Cluster Management,User Guide", "search_title":"", @@ -5820,7 +5888,7 @@ "uri":"admin_guide_000017.html", "node_id":"admin_guide_000017.xml", "product_code":"mrs", - "code":"309", + "code":"313", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Static Service Pools", @@ -5839,7 +5907,7 @@ "uri":"admin_guide_000018.html", "node_id":"admin_guide_000018.xml", "product_code":"mrs", - "code":"310", + "code":"314", "des":"A cluster allocates static service resources to services Flume, HBase, HDFS, and YARN. The total volume of computing resources allocated to each service is fixed, and the", "doc_type":"usermanual", "kw":"Static Service Resources,Managing Static Service Pools,User Guide", @@ -5857,8 +5925,8 @@ "uri":"admin_guide_000019.html", "node_id":"admin_guide_000019.xml", "product_code":"mrs", - "code":"311", - "des":"You can adjust resource base on FusionInsight Manager and customize resource configuration groups if you need to control service resources used on each node in a cluster ", + "code":"315", + "des":"You can adjust resource base on MRS Manager and customize resource configuration groups if you need to control service resources used on each node in a cluster or the ava", "doc_type":"usermanual", "kw":"Configuring Cluster Static Resources,Managing Static Service Pools,User Guide", "search_title":"", @@ -5875,7 +5943,7 @@ "uri":"admin_guide_000020.html", "node_id":"admin_guide_000020.xml", "product_code":"mrs", - "code":"312", + "code":"316", "des":"The big data management platform can manage and isolate service resources that are not running on YARN using static service resource pools. The system supports time-based", "doc_type":"usermanual", "kw":"Viewing Cluster Static Resources,Managing Static Service Pools,User Guide", @@ -5893,7 +5961,7 @@ "uri":"admin_guide_000021.html", "node_id":"admin_guide_000021.xml", "product_code":"mrs", - "code":"313", + "code":"317", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Clients", @@ -5912,8 +5980,8 @@ "uri":"admin_guide_000022.html", "node_id":"admin_guide_000022.xml", "product_code":"mrs", - "code":"314", - "des":"FusionInsight Manager supports unified management of cluster client installation information. After a user downloads and installs a client, FusionInsight Manager automati", + "code":"318", + "des":"MRS Manager supports unified management of cluster client installation information. After a user downloads and installs a client, MRS Manager automatically records inform", "doc_type":"usermanual", "kw":"Managing a Client,Managing Clients,User Guide", "search_title":"", @@ -5930,8 +5998,8 @@ "uri":"admin_guide_000023.html", "node_id":"admin_guide_000023.xml", "product_code":"mrs", - "code":"315", - "des":"The client package downloaded from FusionInsight Manager contains the client batch upgrade tool. When multiple clients need to be upgraded after the cluster upgrade or sc", + "code":"319", + "des":"The client package downloaded from MRS Manager contains the client batch upgrade tool. When multiple clients need to be upgraded after the cluster upgrade or scale-out, y", "doc_type":"usermanual", "kw":"Batch Upgrading Clients,Managing Clients,User Guide", "search_title":"", @@ -5948,8 +6016,8 @@ "uri":"admin_guide_000024.html", "node_id":"admin_guide_000024.xml", "product_code":"mrs", - "code":"316", - "des":"The client package downloaded from FusionInsight Manager contains the client batch upgrade tool. This tool provides the function of upgrading clients in batches and the l", + "code":"320", + "des":"The client package downloaded from MRS Manager contains the client batch upgrade tool. This tool provides the function of upgrading clients in batches and the lightweight", "doc_type":"usermanual", "kw":"Updating the hosts File in Batches,Managing Clients,User Guide", "search_title":"", @@ -5966,7 +6034,7 @@ "uri":"admin_guide_000026.html", "node_id":"admin_guide_000026.xml", "product_code":"mrs", - "code":"317", + "code":"321", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing a Service", @@ -5984,8 +6052,8 @@ "uri":"admin_guide_000027.html", "node_id":"admin_guide_000027.xml", "product_code":"mrs", - "code":"318", - "des":"Log in to FusionInsight Manager. Choose Cluster, click the name of the desired cluster, and choose Services. The service management page is displayed, including the funct", + "code":"322", + "des":"Log in to MRS Manager. Choose Cluster, click the name of the desired cluster, and choose Services. The service management page is displayed, including the functional area", "doc_type":"usermanual", "kw":"Overview,Managing a Service,User Guide", "search_title":"", @@ -6002,7 +6070,7 @@ "uri":"admin_guide_000029.html", "node_id":"admin_guide_000029.xml", "product_code":"mrs", - "code":"319", + "code":"323", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Other Service Management Operations", @@ -6020,8 +6088,8 @@ "uri":"admin_guide_000030.html", "node_id":"admin_guide_000030.xml", "product_code":"mrs", - "code":"320", - "des":"Log in to FusionInsight Manager and choose Cluster >Name of the desired cluster > Services. In the service list, click the specified service name to go to the service det", + "code":"324", + "des":"Log in to MRS Manager and choose Cluster >Name of the desired cluster > Services. In the service list, click the specified service name to go to the service details page,", "doc_type":"usermanual", "kw":"Service Details Page,Other Service Management Operations,User Guide", "search_title":"", @@ -6038,7 +6106,7 @@ "uri":"admin_guide_000031.html", "node_id":"admin_guide_000031.xml", "product_code":"mrs", - "code":"321", + "code":"325", "des":"Some service roles are deployed in active/standby mode. If the active instance needs to be maintained and cannot provide services, or other maintenance is required, you c", "doc_type":"usermanual", "kw":"Performing Active/Standby Switchover of a Role Instance,Other Service Management Operations,User Gui", @@ -6056,8 +6124,8 @@ "uri":"admin_guide_000032.html", "node_id":"admin_guide_000032.xml", "product_code":"mrs", - "code":"322", - "des":"Log in to FusionInsight Manager, choose Cluster >Name of the desired cluster > Services, and click Resource. The resource monitoring page is displayed.Some services in th", + "code":"326", + "des":"Log in to MRS Manager, choose Cluster >Name of the desired cluster > Services, and click Resource. The resource monitoring page is displayed.Some services in the cluster ", "doc_type":"usermanual", "kw":"Resource Monitoring,Other Service Management Operations,User Guide", "search_title":"", @@ -6074,8 +6142,8 @@ "uri":"admin_guide_000033.html", "node_id":"admin_guide_000033.xml", "product_code":"mrs", - "code":"323", - "des":"To meet actual service requirements, the cluster administrator can collect stack information about a specified role or instance on FusionInsight Manager, save the informa", + "code":"327", + "des":"To meet actual service requirements, the cluster administrator can collect stack information about a specified role or instance on MRS Manager, save the information to a ", "doc_type":"usermanual", "kw":"Collecting Stack Information,Other Service Management Operations,User Guide", "search_title":"", @@ -6092,7 +6160,7 @@ "uri":"admin_guide_000415.html", "node_id":"admin_guide_000415.xml", "product_code":"mrs", - "code":"324", + "code":"328", "des":"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 ", "doc_type":"usermanual", "kw":"Switching Ranger Authentication,Other Service Management Operations,User Guide", @@ -6110,7 +6178,7 @@ "uri":"admin_guide_000034.html", "node_id":"admin_guide_000034.xml", "product_code":"mrs", - "code":"325", + "code":"329", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Service Configuration", @@ -6128,8 +6196,8 @@ "uri":"admin_guide_000035.html", "node_id":"admin_guide_000035.xml", "product_code":"mrs", - "code":"326", - "des":"To meet actual service requirements, cluster administrators can quickly view and modify default service configurations on FusionInsight Manager. Configure parameters base", + "code":"330", + "des":"To meet actual service requirements, cluster administrators can quickly view and modify default service configurations on MRS Manager. Configure parameters based on the i", "doc_type":"usermanual", "kw":"Modifying Service Configuration Parameters,Service Configuration,User Guide", "search_title":"", @@ -6146,8 +6214,8 @@ "uri":"admin_guide_000036.html", "node_id":"admin_guide_000036.xml", "product_code":"mrs", - "code":"327", - "des":"All open source parameters can be configured for all MRS cluster components. Parameters used in some key application scenarios can be modified on FusionInsight Manager, a", + "code":"331", + "des":"All open source parameters can be configured for all MRS cluster components. Parameters used in some key application scenarios can be modified on MRS Manager, and some pa", "doc_type":"usermanual", "kw":"Modifying Custom Configuration Parameters of a Service,Service Configuration,User Guide", "search_title":"", @@ -6164,7 +6232,7 @@ "uri":"admin_guide_000037.html", "node_id":"admin_guide_000037.xml", "product_code":"mrs", - "code":"328", + "code":"332", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Management", @@ -6183,8 +6251,8 @@ "uri":"admin_guide_000038.html", "node_id":"admin_guide_000038.xml", "product_code":"mrs", - "code":"329", - "des":"Log in to FusionInsight Manager, click Cluster, click the name of the desired cluster, and choose Service > KrbServer. On the displayed page, click Instance. The displaye", + "code":"333", + "des":"Log in to MRS Manager, click Cluster, click the name of the desired cluster, and choose Service > KrbServer. On the displayed page, click Instance. The displayed instance", "doc_type":"usermanual", "kw":"Overview,Instance Management,User Guide", "search_title":"", @@ -6201,7 +6269,7 @@ "uri":"admin_guide_000040.html", "node_id":"admin_guide_000040.xml", "product_code":"mrs", - "code":"330", + "code":"334", "des":"Some role instances provide services for external services in distributed and parallel mode. Services independently store information about whether each instance can be u", "doc_type":"usermanual", "kw":"Decommissioning and Recommissioning an Instance,Instance Management,User Guide", @@ -6219,7 +6287,7 @@ "uri":"admin_guide_000043.html", "node_id":"admin_guide_000043.xml", "product_code":"mrs", - "code":"331", + "code":"335", "des":"Configuration parameters of each role instance can be modified. In the scenario where instances are migrated to a new cluster or the service is redeployed, the cluster ad", "doc_type":"usermanual", "kw":"Managing Instance Configurations,Instance Management,User Guide", @@ -6237,8 +6305,8 @@ "uri":"admin_guide_000044.html", "node_id":"admin_guide_000044.xml", "product_code":"mrs", - "code":"332", - "des":"FusionInsight Manager allows O&M personnel to view the content configuration files such as environment variables and role configurations of the instance node on the manag", + "code":"336", + "des":"MRS Manager allows O&M personnel to view the content configuration files such as environment variables and role configurations of the instance node on the management page", "doc_type":"usermanual", "kw":"Viewing the Instance Configuration File,Instance Management,User Guide", "search_title":"", @@ -6255,7 +6323,7 @@ "uri":"admin_guide_000045.html", "node_id":"admin_guide_000045.xml", "product_code":"mrs", - "code":"333", + "code":"337", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Group", @@ -6274,8 +6342,8 @@ "uri":"admin_guide_000046.html", "node_id":"admin_guide_000046.xml", "product_code":"mrs", - "code":"334", - "des":"Instance groups can be managed on FusionInsight Manager. That is, you can group multiple instances in the same role based on a specified principle, such as the nodes with", + "code":"338", + "des":"Instance groups can be managed on MRS Manager. That is, you can group multiple instances in the same role based on a specified principle, such as the nodes with the same ", "doc_type":"usermanual", "kw":"Managing Instance Groups,Instance Group,User Guide", "search_title":"", @@ -6292,8 +6360,8 @@ "uri":"admin_guide_000047.html", "node_id":"admin_guide_000047.xml", "product_code":"mrs", - "code":"335", - "des":"The cluster administrator can view the instance group of a specified service on FusionInsight Manager.To move an instance from an instance group to another, perform the f", + "code":"339", + "des":"The cluster administrator can view the instance group of a specified service on MRS Manager.To move an instance from an instance group to another, perform the following o", "doc_type":"usermanual", "kw":"Viewing Information About an Instance Group,Instance Group,User Guide", "search_title":"", @@ -6310,8 +6378,8 @@ "uri":"admin_guide_000048.html", "node_id":"admin_guide_000048.xml", "product_code":"mrs", - "code":"336", - "des":"In a large cluster, users can configure parameters for multiple instances in batches by configuring the related instance groups on FusionInsight Manager, reducing redunda", + "code":"340", + "des":"In a large cluster, users can configure parameters for multiple instances in batches by configuring the related instance groups on MRS Manager, reducing redundant instanc", "doc_type":"usermanual", "kw":"Configuring Instantiation Group Parameters,Instance Group,User Guide", "search_title":"", @@ -6328,7 +6396,7 @@ "uri":"admin_guide_000049.html", "node_id":"admin_guide_000049.xml", "product_code":"mrs", - "code":"337", + "code":"341", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Hosts", @@ -6347,7 +6415,7 @@ "uri":"admin_guide_000050.html", "node_id":"admin_guide_000050.xml", "product_code":"mrs", - "code":"338", + "code":"342", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Host Management Page", @@ -6366,8 +6434,8 @@ "uri":"admin_guide_000051.html", "node_id":"admin_guide_000051.xml", "product_code":"mrs", - "code":"339", - "des":"Log in to FusionInsight Manager, click Hosts, and the host list is displayed on the host management page. You can view the host list and basic information of each host.Yo", + "code":"343", + "des":"Log in to MRS Manager, click Hosts, and the host list is displayed on the host management page. You can view the host list and basic information of each host.You can swit", "doc_type":"usermanual", "kw":"Viewing the Host List,Host Management Page,User Guide", "search_title":"", @@ -6384,8 +6452,8 @@ "uri":"admin_guide_000052.html", "node_id":"admin_guide_000052.xml", "product_code":"mrs", - "code":"340", - "des":"Log in to FusionInsight Manager, click Hosts, and click a host name in the host list. The host details page contains the basic information area, disk status area, role li", + "code":"344", + "des":"Log in to MRS Manager, click Hosts, and click a host name in the host list. The host details page contains the basic information area, disk status area, role list area, a", "doc_type":"usermanual", "kw":"Viewing the Host Dashboard,Host Management Page,User Guide", "search_title":"", @@ -6402,8 +6470,8 @@ "uri":"admin_guide_000053.html", "node_id":"admin_guide_000053.xml", "product_code":"mrs", - "code":"341", - "des":"Log in to FusionInsight Manager, click Hosts, and click the specified host name in the host list. On the host details page, click the Process and Resource tabs.On the Pro", + "code":"345", + "des":"Log in to MRS Manager, click Hosts, and click the specified host name in the host list. On the host details page, click the Process and Resource tabs.On the Process tab p", "doc_type":"usermanual", "kw":"Checking Host Processes and Resources,Host Management Page,User Guide", "search_title":"", @@ -6420,7 +6488,7 @@ "uri":"admin_guide_000054.html", "node_id":"admin_guide_000054.xml", "product_code":"mrs", - "code":"342", + "code":"346", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Host Maintenance Operations", @@ -6439,7 +6507,7 @@ "uri":"admin_guide_000056.html", "node_id":"admin_guide_000056.xml", "product_code":"mrs", - "code":"343", + "code":"347", "des":"If a host is faulty, you may need to stop all the roles on the host and perform maintenance check on the host. After the host fault is rectified, start all roles running ", "doc_type":"usermanual", "kw":"Starting and Stopping All Instances on a Host,Host Maintenance Operations,User Guide", @@ -6457,7 +6525,7 @@ "uri":"admin_guide_000057.html", "node_id":"admin_guide_000057.xml", "product_code":"mrs", - "code":"344", + "code":"348", "des":"If the running status of a host is not Normal, you can perform health checks on the host to check whether some basic functions are abnormal. During routine O&M, you can p", "doc_type":"usermanual", "kw":"Performing a Host Health Check,Host Maintenance Operations,User Guide", @@ -6475,7 +6543,7 @@ "uri":"admin_guide_000058.html", "node_id":"admin_guide_000058.xml", "product_code":"mrs", - "code":"345", + "code":"349", "des":"All hosts in a large cluster are usually deployed on multiple racks. Hosts on different racks communicate with each other through switches. The network bandwidth between ", "doc_type":"usermanual", "kw":"Configuring Racks for Hosts,Host Maintenance Operations,User Guide", @@ -6493,7 +6561,7 @@ "uri":"admin_guide_000059.html", "node_id":"admin_guide_000059.xml", "product_code":"mrs", - "code":"346", + "code":"350", "des":"If a host is abnormal or faulty and cannot provide services or affects the cluster performance, you can remove the host from the available node in the cluster temporarily", "doc_type":"usermanual", "kw":"Isolating a Host,Host Maintenance Operations,User Guide", @@ -6511,8 +6579,8 @@ "uri":"admin_guide_000062.html", "node_id":"admin_guide_000062.xml", "product_code":"mrs", - "code":"347", - "des":"Administrators can export information about all hosts on FusionInsight Manager.", + "code":"351", + "des":"Administrators can export information about all hosts on MRS Manager.", "doc_type":"usermanual", "kw":"Exporting Host Information,Host Maintenance Operations,User Guide", "search_title":"", @@ -6529,7 +6597,7 @@ "uri":"admin_guide_000063.html", "node_id":"admin_guide_000063.xml", "product_code":"mrs", - "code":"348", + "code":"352", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Resource Overview", @@ -6548,8 +6616,8 @@ "uri":"admin_guide_000064.html", "node_id":"admin_guide_000064.xml", "product_code":"mrs", - "code":"349", - "des":"Log in to FusionInsight Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Distribution tab to view resource distrib", + "code":"353", + "des":"Log in to MRS Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Distribution tab to view resource distribution of e", "doc_type":"usermanual", "kw":"Distribution,Resource Overview,User Guide", "search_title":"", @@ -6566,8 +6634,8 @@ "uri":"admin_guide_000065.html", "node_id":"admin_guide_000065.xml", "product_code":"mrs", - "code":"350", - "des":"Log in to FusionInsight and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Trend tab to view resource trends of all clusters", + "code":"354", + "des":"Log in to MRS and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Trend tab to view resource trends of all clusters or a sing", "doc_type":"usermanual", "kw":"Trend,Resource Overview,User Guide", "search_title":"", @@ -6584,8 +6652,8 @@ "uri":"admin_guide_000066.html", "node_id":"admin_guide_000066.xml", "product_code":"mrs", - "code":"351", - "des":"Log in to FusionInsight Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Cluster tab to view resource monitoring o", + "code":"355", + "des":"Log in to MRS Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Cluster tab to view resource monitoring of all clus", "doc_type":"usermanual", "kw":"Cluster,Resource Overview,User Guide", "search_title":"", @@ -6602,8 +6670,8 @@ "uri":"admin_guide_000067.html", "node_id":"admin_guide_000067.xml", "product_code":"mrs", - "code":"352", - "des":"Log in to FusionInsight Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Host tab to view host resource overview, ", + "code":"356", + "des":"Log in to MRS Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Host tab to view host resource overview, including ", "doc_type":"usermanual", "kw":"Host,Resource Overview,User Guide", "search_title":"", @@ -6620,7 +6688,7 @@ "uri":"admin_guide_000068.html", "node_id":"admin_guide_000068.xml", "product_code":"mrs", - "code":"353", + "code":"357", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"O&M", @@ -6639,7 +6707,7 @@ "uri":"admin_guide_000069.html", "node_id":"admin_guide_000069.xml", "product_code":"mrs", - "code":"354", + "code":"358", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarms", @@ -6658,8 +6726,8 @@ "uri":"admin_guide_000070.html", "node_id":"admin_guide_000070.xml", "product_code":"mrs", - "code":"355", - "des":"Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. You can view information about alarms reported by all clusters, including the alarm name, ID, severity, a", + "code":"359", + "des":"Log in to MRS Manager and choose O&M > Alarm > Alarms. You can view information about alarms reported by all clusters, including the alarm name, ID, severity, and generat", "doc_type":"usermanual", "kw":"Overview of Alarms and Events,Alarms,User Guide", "search_title":"", @@ -6676,8 +6744,8 @@ "uri":"admin_guide_000071.html", "node_id":"admin_guide_000071.xml", "product_code":"mrs", - "code":"356", - "des":"You can configure monitoring indicator thresholds to monitor the health status of indicators on FusionInsight Manager. If abnormal data occurs and the preset conditions a", + "code":"360", + "des":"You can configure monitoring indicator thresholds to monitor the health status of indicators on MRS Manager. If abnormal data occurs and the preset conditions are met, th", "doc_type":"usermanual", "kw":"Configuring the Threshold,Alarms,User Guide", "search_title":"", @@ -6694,8 +6762,8 @@ "uri":"admin_guide_000072.html", "node_id":"admin_guide_000072.xml", "product_code":"mrs", - "code":"357", - "des":"If you do not want FusionInsight Manager to report specified alarms in the following scenarios, you can manually mask the alarms.Some unimportant alarms and minor alarms ", + "code":"361", + "des":"If you do not want MRS Manager to report specified alarms in the following scenarios, you can manually mask the alarms.Some unimportant alarms and minor alarms need to be", "doc_type":"usermanual", "kw":"Configuring the Alarm Masking Status,Alarms,User Guide", "search_title":"", @@ -6712,7 +6780,7 @@ "uri":"admin_guide_000073.html", "node_id":"admin_guide_000073.xml", "product_code":"mrs", - "code":"358", + "code":"362", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Log", @@ -6731,8 +6799,8 @@ "uri":"admin_guide_000074.html", "node_id":"admin_guide_000074.xml", "product_code":"mrs", - "code":"359", - "des":"FusionInsight Manager allows you to search for logs online and view the log content of components to locate faults.You can click Stop to forcibly stop the search. You can", + "code":"363", + "des":"MRS Manager allows you to search for logs online and view the log content of components to locate faults.You can click Stop to forcibly stop the search. You can view the ", "doc_type":"usermanual", "kw":"Log Online Search,Log,User Guide", "search_title":"", @@ -6749,8 +6817,8 @@ "uri":"admin_guide_000075.html", "node_id":"admin_guide_000075.xml", "product_code":"mrs", - "code":"360", - "des":"FusionInsight Manager allows you to batch export logs generated on all instances of each service.Service: Click and select a service.Host: Enter the IP address of the ho", + "code":"364", + "des":"MRS Manager allows you to batch export logs generated on all instances of each service.Service: Click and select a service.Host: Enter the IP address of the host where t", "doc_type":"usermanual", "kw":"Log Download,Log,User Guide", "search_title":"", @@ -6767,7 +6835,7 @@ "uri":"admin_guide_000076.html", "node_id":"admin_guide_000076.xml", "product_code":"mrs", - "code":"361", + "code":"365", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Perform a Health Check", @@ -6785,7 +6853,7 @@ "uri":"admin_guide_000077.html", "node_id":"admin_guide_000077.xml", "product_code":"mrs", - "code":"362", + "code":"366", "des":"Administrators can view all health check tasks in the health check management center to check whether the cluster is affected after the modification.By default, all saved", "doc_type":"usermanual", "kw":"Viewing a Health Check Task,Perform a Health Check,User Guide", @@ -6803,8 +6871,8 @@ "uri":"admin_guide_000078.html", "node_id":"admin_guide_000078.xml", "product_code":"mrs", - "code":"363", - "des":"FusionInsight Manager allows you to download and delete health check reports.", + "code":"367", + "des":"MRS Manager allows you to download and delete health check reports.", "doc_type":"usermanual", "kw":"Managing Health Check Reports,Perform a Health Check,User Guide", "search_title":"", @@ -6821,7 +6889,7 @@ "uri":"admin_guide_000079.html", "node_id":"admin_guide_000079.xml", "product_code":"mrs", - "code":"364", + "code":"368", "des":"Administrators can enable automatic health check to reduce manual operation time. By default, the automatic health check checks the entire cluster.Periodic Health Check i", "doc_type":"usermanual", "kw":"Modifying Health Check Configuration,Perform a Health Check,User Guide", @@ -6839,7 +6907,7 @@ "uri":"admin_guide_000080.html", "node_id":"admin_guide_000080.xml", "product_code":"mrs", - "code":"365", + "code":"369", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring Backup and Backup Restoration", @@ -6857,8 +6925,8 @@ "uri":"admin_guide_000081.html", "node_id":"admin_guide_000081.xml", "product_code":"mrs", - "code":"366", - "des":"You can create backup tasks on FusionInsight Manager. Executing backup tasks backs up related data.Metadata and service data can be backed up.For details about how to bac", + "code":"370", + "des":"You can create backup tasks on MRS Manager. Executing backup tasks backs up related data.Metadata and service data can be backed up.For details about how to back up data ", "doc_type":"usermanual", "kw":"Creating a Backup Task,Configuring Backup and Backup Restoration,User Guide", "search_title":"", @@ -6875,8 +6943,8 @@ "uri":"admin_guide_000082.html", "node_id":"admin_guide_000082.xml", "product_code":"mrs", - "code":"367", - "des":"You can create a backup restoration task on FusionInsight Manager. After the restoration task is executed, the specified backup data is restored to the cluster.Metadata a", + "code":"371", + "des":"You can create a backup restoration task on MRS Manager. After the restoration task is executed, the specified backup data is restored to the cluster.Metadata and service", "doc_type":"usermanual", "kw":"Creating a Backup Restoration Task,Configuring Backup and Backup Restoration,User Guide", "search_title":"", @@ -6893,8 +6961,8 @@ "uri":"admin_guide_000083.html", "node_id":"admin_guide_000083.xml", "product_code":"mrs", - "code":"368", - "des":"You can also maintain and manage backup restoration tasks on FusionInsight Manager.", + "code":"372", + "des":"You can also maintain and manage backup restoration tasks on MRS Manager.", "doc_type":"usermanual", "kw":"Managing Backup and Backup Restoration Tasks,Configuring Backup and Backup Restoration,User Guide", "search_title":"", @@ -6911,7 +6979,7 @@ "uri":"admin_guide_000084.html", "node_id":"admin_guide_000084.xml", "product_code":"mrs", - "code":"369", + "code":"373", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Audit", @@ -6929,7 +6997,7 @@ "uri":"admin_guide_000085.html", "node_id":"admin_guide_000085.xml", "product_code":"mrs", - "code":"370", + "code":"374", "des":"The Audit page displays the user operations on Manager. On this page, administrators can view historical user operations on Manager. For details about the audit informati", "doc_type":"usermanual", "kw":"Overview,Audit,User Guide", @@ -6947,8 +7015,8 @@ "uri":"admin_guide_000086.html", "node_id":"admin_guide_000086.xml", "product_code":"mrs", - "code":"371", - "des":"The audit logs of FusionInsight Manager are stored in the database by default. If the audit logs are retained for a long time, the disk space of the data directory may be", + "code":"375", + "des":"The audit logs of MRS Manager are stored in the database by default. If the audit logs are retained for a long time, the disk space of the data directory may be insuffici", "doc_type":"usermanual", "kw":"Configuring Audit Log Dumping,Audit,User Guide", "search_title":"", @@ -6965,7 +7033,7 @@ "uri":"admin_guide_000087.html", "node_id":"admin_guide_000087.xml", "product_code":"mrs", - "code":"372", + "code":"376", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Tenant Resources", @@ -6984,7 +7052,7 @@ "uri":"admin_guide_000088.html", "node_id":"admin_guide_000088.xml", "product_code":"mrs", - "code":"373", + "code":"377", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Multi-Tenancy", @@ -7003,7 +7071,7 @@ "uri":"admin_guide_000089.html", "node_id":"admin_guide_000089.xml", "product_code":"mrs", - "code":"374", + "code":"378", "des":"Multi-tenancy refers to multiple resource sets (a resource set is a tenant) in the MRS big data cluster and is able to allocate and schedule resources. The resources incl", "doc_type":"usermanual", "kw":"Overview,Multi-Tenancy,User Guide", @@ -7021,7 +7089,7 @@ "uri":"admin_guide_000090.html", "node_id":"admin_guide_000090.xml", "product_code":"mrs", - "code":"375", + "code":"379", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Technical Principles", @@ -7040,8 +7108,8 @@ "uri":"admin_guide_000091.html", "node_id":"admin_guide_000091.xml", "product_code":"mrs", - "code":"376", - "des":"Log in to FusionInsight Manager and choose Tenant Resources > Tenant Resources Management. On the page that is displayed, you can find that FusionInsight Manager is a uni", + "code":"380", + "des":"Log in to MRS Manager and choose Tenant Resources > Tenant Resources Management. On the page that is displayed, you can find that MRS Manager is a unified multi-tenant ma", "doc_type":"usermanual", "kw":"Multi-Tenant Management,Technical Principles,User Guide", "search_title":"", @@ -7058,7 +7126,7 @@ "uri":"admin_guide_000092.html", "node_id":"admin_guide_000092.xml", "product_code":"mrs", - "code":"377", + "code":"381", "des":"The following figure shows a multi-tenant model.Table 1 describes the concepts involved in Figure 1.If a user wants to use a tenant's resources or add or delete a sub-ten", "doc_type":"usermanual", "kw":"Multi-Tenant Model,Technical Principles,User Guide", @@ -7076,7 +7144,7 @@ "uri":"admin_guide_000093.html", "node_id":"admin_guide_000093.xml", "product_code":"mrs", - "code":"378", + "code":"382", "des":"MRS cluster resources are classified into computing resources and storage resources. The multi-tenant architecture implements resource isolation.Computing resourcesComput", "doc_type":"usermanual", "kw":"Resource Overview,Technical Principles,User Guide", @@ -7094,7 +7162,7 @@ "uri":"admin_guide_000094.html", "node_id":"admin_guide_000094.xml", "product_code":"mrs", - "code":"379", + "code":"383", "des":"Yarn provides distributed resource management for a big data cluster. The total volume of resources allocated to Yarn can be configured. Then Yarn allocates and schedules", "doc_type":"usermanual", "kw":"Dynamic Resources,Technical Principles,User Guide", @@ -7112,7 +7180,7 @@ "uri":"admin_guide_000095.html", "node_id":"admin_guide_000095.xml", "product_code":"mrs", - "code":"380", + "code":"384", "des":"As a distributed file storage service in a big data cluster, HDFS stores all the user data of the upper-layer applications in the big data cluster, including the data wri", "doc_type":"usermanual", "kw":"Storage Resources,Technical Principles,User Guide", @@ -7130,7 +7198,7 @@ "uri":"admin_guide_000096.html", "node_id":"admin_guide_000096.xml", "product_code":"mrs", - "code":"381", + "code":"385", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Multi-Tenancy Usage", @@ -7149,7 +7217,7 @@ "uri":"admin_guide_000097.html", "node_id":"admin_guide_000097.xml", "product_code":"mrs", - "code":"382", + "code":"386", "des":"Tenants are used in resource control and service isolation scenarios. Administrators need to determine the service scenarios of cluster resources and then plan tenants.Ya", "doc_type":"usermanual", "kw":"Overview,Multi-Tenancy Usage,User Guide", @@ -7167,7 +7235,7 @@ "uri":"admin_guide_000098.html", "node_id":"admin_guide_000098.xml", "product_code":"mrs", - "code":"383", + "code":"387", "des":"Administrators need to determine the service scenarios of cluster resources and then plan tenants. After that, administrators add tenants and configure dynamic resources,", "doc_type":"usermanual", "kw":"Process Overview,Multi-Tenancy Usage,User Guide", @@ -7185,7 +7253,7 @@ "uri":"admin_guide_000099.html", "node_id":"admin_guide_000099.xml", "product_code":"mrs", - "code":"384", + "code":"388", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Using the Superior Scheduler", @@ -7204,7 +7272,7 @@ "uri":"admin_guide_000100.html", "node_id":"admin_guide_000100.xml", "product_code":"mrs", - "code":"385", + "code":"389", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Creating Tenants", @@ -7223,8 +7291,8 @@ "uri":"admin_guide_000101.html", "node_id":"admin_guide_000101.xml", "product_code":"mrs", - "code":"386", - "des":"You can create tenants on FusionInsight Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based", + "code":"390", + "des":"You can create tenants on MRS Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based on servic", "doc_type":"usermanual", "kw":"Adding a Tenant,Creating Tenants,User Guide", "search_title":"", @@ -7241,8 +7309,8 @@ "uri":"admin_guide_000102.html", "node_id":"admin_guide_000102.xml", "product_code":"mrs", - "code":"387", - "des":"You can create sub-tenants on FusionInsight Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planni", + "code":"391", + "des":"You can create sub-tenants on MRS Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planning and req", "doc_type":"usermanual", "kw":"Adding a Sub-Tenant,Creating Tenants,User Guide", "search_title":"", @@ -7259,8 +7327,8 @@ "uri":"admin_guide_000103.html", "node_id":"admin_guide_000103.xml", "product_code":"mrs", - "code":"388", - "des":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on FusionInsight Manager and bind the user to the ", + "code":"392", + "des":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on MRS Manager and bind the user to the role of th", "doc_type":"usermanual", "kw":"Adding a User and Binding the User to a Tenant Role,Creating Tenants,User Guide", "search_title":"", @@ -7277,7 +7345,7 @@ "uri":"admin_guide_000104.html", "node_id":"admin_guide_000104.xml", "product_code":"mrs", - "code":"389", + "code":"393", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Tenants", @@ -7296,8 +7364,8 @@ "uri":"admin_guide_000105.html", "node_id":"admin_guide_000105.xml", "product_code":"mrs", - "code":"390", - "des":"You can manage the HDFS storage directories used by specified tenants based on service requirements on FusionInsight Manager, such as adding tenant directories, changing ", + "code":"394", + "des":"You can manage the HDFS storage directories used by specified tenants based on service requirements on MRS Manager, such as adding tenant directories, changing the quotas", "doc_type":"usermanual", "kw":"Managing Tenant Directories,Managing Tenants,User Guide", "search_title":"", @@ -7314,8 +7382,8 @@ "uri":"admin_guide_000106.html", "node_id":"admin_guide_000106.xml", "product_code":"mrs", - "code":"391", - "des":"Tenant data is stored on FusionInsight Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants ", + "code":"395", + "des":"Tenant data is stored on MRS Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants may become", "doc_type":"usermanual", "kw":"Restoring Tenant Data,Managing Tenants,User Guide", "search_title":"", @@ -7332,8 +7400,8 @@ "uri":"admin_guide_000107.html", "node_id":"admin_guide_000107.xml", "product_code":"mrs", - "code":"392", - "des":"You can delete tenants that are no longer used on FusionInsight Manager based on service requirements to release resources occupied by the tenants.A tenant has been added", + "code":"396", + "des":"You can delete tenants that are no longer used on MRS Manager based on service requirements to release resources occupied by the tenants.A tenant has been added.The tenan", "doc_type":"usermanual", "kw":"Deleting a Tenant,Managing Tenants,User Guide", "search_title":"", @@ -7350,7 +7418,7 @@ "uri":"admin_guide_000108.html", "node_id":"admin_guide_000108.xml", "product_code":"mrs", - "code":"393", + "code":"397", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Resources", @@ -7369,7 +7437,7 @@ "uri":"admin_guide_000109.html", "node_id":"admin_guide_000109.xml", "product_code":"mrs", - "code":"394", + "code":"398", "des":"In a cluster, you can logically group Yarn NodeManagers into Yarn resource pools. Each NodeManager belongs to only one resource pool. You can create a custom resource poo", "doc_type":"usermanual", "kw":"Adding a Resource Pool,Managing Resources,User Guide", @@ -7387,8 +7455,8 @@ "uri":"admin_guide_000110.html", "node_id":"admin_guide_000110.xml", "product_code":"mrs", - "code":"395", - "des":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on FusionInsight Manager.Adding hosts: Select", + "code":"399", + "des":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on MRS Manager.Adding hosts: Select desired h", "doc_type":"usermanual", "kw":"Modifying a Resource Pool,Managing Resources,User Guide", "search_title":"", @@ -7405,8 +7473,8 @@ "uri":"admin_guide_000111.html", "node_id":"admin_guide_000111.xml", "product_code":"mrs", - "code":"396", - "des":"If a resource pool is no longer used based on service requirements, you can delete it on FusionInsight Manager.Any queue in the cluster does not use the resource pool to ", + "code":"400", + "des":"If a resource pool is no longer used based on service requirements, you can delete it on MRS Manager.Any queue in the cluster does not use the resource pool to be deleted", "doc_type":"usermanual", "kw":"Deleting a Resource Pool,Managing Resources,User Guide", "search_title":"", @@ -7423,8 +7491,8 @@ "uri":"admin_guide_000112.html", "node_id":"admin_guide_000112.xml", "product_code":"mrs", - "code":"397", - "des":"You can modify the queue configurations for a specified tenant on FusionInsight Manager.A tenant who uses the Superior scheduler has been added.You can also access the Mo", + "code":"401", + "des":"You can modify the queue configurations for a specified tenant on MRS Manager.A tenant who uses the Superior scheduler has been added.You can also access the Modify Queue", "doc_type":"usermanual", "kw":"Configuring a Queue,Managing Resources,User Guide", "search_title":"", @@ -7441,7 +7509,7 @@ "uri":"admin_guide_000113.html", "node_id":"admin_guide_000113.xml", "product_code":"mrs", - "code":"398", + "code":"402", "des":"After a resource pool is added, you can configure the capacity policy of available resources for Yarn queues so that jobs in the queues can be properly executed in the re", "doc_type":"usermanual", "kw":"Configuring the Queue Capacity Policy of a Resource Pool,Managing Resources,User Guide", @@ -7459,8 +7527,8 @@ "uri":"admin_guide_000114.html", "node_id":"admin_guide_000114.xml", "product_code":"mrs", - "code":"399", - "des":"You can clear the configurations of a queue on FusionInsight MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disass", + "code":"403", + "des":"You can clear the configurations of a queue on MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disassociated from t", "doc_type":"usermanual", "kw":"Clearing Queue Configurations,Managing Resources,User Guide", "search_title":"", @@ -7477,7 +7545,7 @@ "uri":"admin_guide_000115.html", "node_id":"admin_guide_000115.xml", "product_code":"mrs", - "code":"400", + "code":"404", "des":"If a tenant uses a Superior scheduler, you can configure the global policy for users to use the resource scheduler, including:Maximum running appsMaximum pending appsDefa", "doc_type":"usermanual", "kw":"Managing Global User Policies,Using the Superior Scheduler,User Guide", @@ -7495,7 +7563,7 @@ "uri":"admin_guide_000116.html", "node_id":"admin_guide_000116.xml", "product_code":"mrs", - "code":"401", + "code":"405", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Using the Capacity Scheduler", @@ -7514,7 +7582,7 @@ "uri":"admin_guide_000117.html", "node_id":"admin_guide_000117.xml", "product_code":"mrs", - "code":"402", + "code":"406", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Creating Tenants", @@ -7533,8 +7601,8 @@ "uri":"admin_guide_000118.html", "node_id":"admin_guide_000118.xml", "product_code":"mrs", - "code":"403", - "des":"You can create tenants on FusionInsight Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based", + "code":"407", + "des":"You can create tenants on MRS Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based on servic", "doc_type":"usermanual", "kw":"Adding a Tenant,Creating Tenants,User Guide", "search_title":"", @@ -7551,8 +7619,8 @@ "uri":"admin_guide_000119.html", "node_id":"admin_guide_000119.xml", "product_code":"mrs", - "code":"404", - "des":"You can create sub-tenants on FusionInsight Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planni", + "code":"408", + "des":"You can create sub-tenants on MRS Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planning and req", "doc_type":"usermanual", "kw":"Adding a Sub-Tenant,Creating Tenants,User Guide", "search_title":"", @@ -7569,8 +7637,8 @@ "uri":"admin_guide_000120.html", "node_id":"admin_guide_000120.xml", "product_code":"mrs", - "code":"405", - "des":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on FusionInsight Manager and bind the user to the ", + "code":"409", + "des":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on MRS Manager and bind the user to the role of th", "doc_type":"usermanual", "kw":"Adding a User and Binding the User to a Tenant Role,Creating Tenants,User Guide", "search_title":"", @@ -7587,7 +7655,7 @@ "uri":"admin_guide_000121.html", "node_id":"admin_guide_000121.xml", "product_code":"mrs", - "code":"406", + "code":"410", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Tenants", @@ -7606,8 +7674,8 @@ "uri":"admin_guide_000122.html", "node_id":"admin_guide_000122.xml", "product_code":"mrs", - "code":"407", - "des":"You can manage the HDFS storage directories used by specified tenants based on service requirements on FusionInsight Manager, such as adding tenant directories, changing ", + "code":"411", + "des":"You can manage the HDFS storage directories used by specified tenants based on service requirements on MRS Manager, such as adding tenant directories, changing the quotas", "doc_type":"usermanual", "kw":"Managing Tenant Directories,Managing Tenants,User Guide", "search_title":"", @@ -7624,8 +7692,8 @@ "uri":"admin_guide_000123.html", "node_id":"admin_guide_000123.xml", "product_code":"mrs", - "code":"408", - "des":"Tenant data is stored on FusionInsight Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants ", + "code":"412", + "des":"Tenant data is stored on MRS Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants may become", "doc_type":"usermanual", "kw":"Restoring Tenant Data,Managing Tenants,User Guide", "search_title":"", @@ -7642,8 +7710,8 @@ "uri":"admin_guide_000124.html", "node_id":"admin_guide_000124.xml", "product_code":"mrs", - "code":"409", - "des":"You can delete tenants that are no longer used on FusionInsight Manager based on service requirements to release resources occupied by the tenants.A tenant has been added", + "code":"413", + "des":"You can delete tenants that are no longer used on MRS Manager based on service requirements to release resources occupied by the tenants.A tenant has been added.The tenan", "doc_type":"usermanual", "kw":"Deleting a Tenant,Managing Tenants,User Guide", "search_title":"", @@ -7660,7 +7728,7 @@ "uri":"admin_guide_000125.html", "node_id":"admin_guide_000125.xml", "product_code":"mrs", - "code":"410", + "code":"414", "des":"If Yarn uses the Capacity scheduler, deleting a tenant only sets the queue capacity of the tenant to 0 and the tenant status to STOPPED but does not clear the queues of t", "doc_type":"usermanual", "kw":"Clearing Non-associated Queues of a Tenant,Managing Tenants,User Guide", @@ -7678,7 +7746,7 @@ "uri":"admin_guide_000126.html", "node_id":"admin_guide_000126.xml", "product_code":"mrs", - "code":"411", + "code":"415", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Resources", @@ -7697,7 +7765,7 @@ "uri":"admin_guide_000127.html", "node_id":"admin_guide_000127.xml", "product_code":"mrs", - "code":"412", + "code":"416", "des":"In a cluster, you can logically group Yarn NodeManagers into Yarn resource pools. Each NodeManager belongs to only one resource pool. You can create a custom resource poo", "doc_type":"usermanual", "kw":"Adding a Resource Pool,Managing Resources,User Guide", @@ -7715,8 +7783,8 @@ "uri":"admin_guide_000128.html", "node_id":"admin_guide_000128.xml", "product_code":"mrs", - "code":"413", - "des":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on FusionInsight Manager.Adding hosts: Select", + "code":"417", + "des":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on MRS Manager.Adding hosts: Select desired h", "doc_type":"usermanual", "kw":"Modifying a Resource Pool,Managing Resources,User Guide", "search_title":"", @@ -7733,8 +7801,8 @@ "uri":"admin_guide_000129.html", "node_id":"admin_guide_000129.xml", "product_code":"mrs", - "code":"414", - "des":"If a resource pool is no longer used based on service requirements, you can delete it on FusionInsight Manager.Any queue in the cluster does not use the resource pool to ", + "code":"418", + "des":"If a resource pool is no longer used based on service requirements, you can delete it on MRS Manager.Any queue in the cluster does not use the resource pool to be deleted", "doc_type":"usermanual", "kw":"Deleting a Resource Pool,Managing Resources,User Guide", "search_title":"", @@ -7751,8 +7819,8 @@ "uri":"admin_guide_000130.html", "node_id":"admin_guide_000130.xml", "product_code":"mrs", - "code":"415", - "des":"You can modify the queue configurations for a specified tenant on FusionInsight Manager.A tenant who uses the Capacity scheduler has been added.The Resource Distribution ", + "code":"419", + "des":"You can modify the queue configurations for a specified tenant on MRS Manager.A tenant who uses the Capacity scheduler has been added.The Resource Distribution Policy pag", "doc_type":"usermanual", "kw":"Configuring a Queue,Managing Resources,User Guide", "search_title":"", @@ -7769,7 +7837,7 @@ "uri":"admin_guide_000131.html", "node_id":"admin_guide_000131.xml", "product_code":"mrs", - "code":"416", + "code":"420", "des":"After a resource pool is added, you can configure the capacity policy of available resources for Yarn queues so that jobs in the queues can be properly executed in the re", "doc_type":"usermanual", "kw":"Configuring the Queue Capacity Policy of a Resource Pool,Managing Resources,User Guide", @@ -7787,8 +7855,8 @@ "uri":"admin_guide_000132.html", "node_id":"admin_guide_000132.xml", "product_code":"mrs", - "code":"417", - "des":"You can clear the configurations of a queue on FusionInsight MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disass", + "code":"421", + "des":"You can clear the configurations of a queue on MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disassociated from t", "doc_type":"usermanual", "kw":"Clearing Queue Configurations,Managing Resources,User Guide", "search_title":"", @@ -7805,7 +7873,7 @@ "uri":"admin_guide_000133.html", "node_id":"admin_guide_000133.xml", "product_code":"mrs", - "code":"418", + "code":"422", "des":"The newly installed MRS cluster uses the Superior scheduler by default. If the cluster is upgraded from an earlier version, you can switch the YARN scheduler from the Cap", "doc_type":"usermanual", "kw":"Switching the Scheduler,Tenant Resources,User Guide", @@ -7823,7 +7891,7 @@ "uri":"admin_guide_000134.html", "node_id":"admin_guide_000134.xml", "product_code":"mrs", - "code":"419", + "code":"423", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"System Configuration", @@ -7842,7 +7910,7 @@ "uri":"admin_guide_000135.html", "node_id":"admin_guide_000135.xml", "product_code":"mrs", - "code":"420", + "code":"424", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring Permissions", @@ -7861,7 +7929,7 @@ "uri":"admin_guide_000136.html", "node_id":"admin_guide_000136.xml", "product_code":"mrs", - "code":"421", + "code":"425", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Users", @@ -7880,8 +7948,8 @@ "uri":"admin_guide_000137.html", "node_id":"admin_guide_000137.xml", "product_code":"mrs", - "code":"422", - "des":"FusionInsight Manager supports a maximum of 50,000 users (including built-in users). By default, only user admin has the highest operation permissions of FusionInsight Ma", + "code":"426", + "des":"MRS Manager supports a maximum of 50,000 users (including built-in users). By default, only user admin has the highest operation permissions of MRS Manager. You need to c", "doc_type":"usermanual", "kw":"Creating a User,Managing Users,User Guide", "search_title":"", @@ -7898,8 +7966,8 @@ "uri":"admin_guide_000138.html", "node_id":"admin_guide_000138.xml", "product_code":"mrs", - "code":"423", - "des":"You can modify user information on FusionInsight Manager, including the user group, primary group, role permission assignment, and user description.Modify the parameters ", + "code":"427", + "des":"You can modify user information on MRS Manager, including the user group, primary group, role permission assignment, and user description.Modify the parameters based on s", "doc_type":"usermanual", "kw":"Modifying User Information,Managing Users,User Guide", "search_title":"", @@ -7916,8 +7984,8 @@ "uri":"admin_guide_000139.html", "node_id":"admin_guide_000139.xml", "product_code":"mrs", - "code":"424", - "des":"You can export information about all created users on FusionInsight Manager.The exported user information contains the username, creation time, description, user type (0 ", + "code":"428", + "des":"You can export information about all created users on MRS Manager.The exported user information contains the username, creation time, description, user type (0 indicates ", "doc_type":"usermanual", "kw":"Exporting User Information,Managing Users,User Guide", "search_title":"", @@ -7934,7 +8002,7 @@ "uri":"admin_guide_000140.html", "node_id":"admin_guide_000140.xml", "product_code":"mrs", - "code":"425", + "code":"429", "des":"A user may be suspended for a long period of time due to service changes. For security purposes, you can lock such a user.You can lock a user in using either of the follo", "doc_type":"usermanual", "kw":"Locking a User,Managing Users,User Guide", @@ -7952,8 +8020,8 @@ "uri":"admin_guide_000141.html", "node_id":"admin_guide_000141.xml", "product_code":"mrs", - "code":"426", - "des":"You can unlock a user on FusionInsight Manager if the user has been locked because the number of login attempts exceeds the threshold. Only users created on FusionInsight", + "code":"430", + "des":"You can unlock a user on MRS Manager if the user has been locked because the number of login attempts exceeds the threshold. Only users created on MRS Manager can be unlo", "doc_type":"usermanual", "kw":"Unlocking a User,Managing Users,User Guide", "search_title":"", @@ -7970,8 +8038,8 @@ "uri":"admin_guide_000142.html", "node_id":"admin_guide_000142.xml", "product_code":"mrs", - "code":"427", - "des":"Based on service requirements, you can delete system users that are no longer used on FusionInsight Manager.After a user is deleted, the provisioned ticket granting ticke", + "code":"431", + "des":"Based on service requirements, you can delete system users that are no longer used on MRS Manager.After a user is deleted, the provisioned ticket granting ticket (TGT) is", "doc_type":"usermanual", "kw":"Deleting a User,Managing Users,User Guide", "search_title":"", @@ -7988,8 +8056,8 @@ "uri":"admin_guide_000143.html", "node_id":"admin_guide_000143.xml", "product_code":"mrs", - "code":"428", - "des":"For security purposes, the password of a human-machine user must be changed periodically.If users have the permission to use FusionInsight Manager, they can change their ", + "code":"432", + "des":"For security purposes, the password of a human-machine user must be changed periodically.If users have the permission to use MRS Manager, they can change their passwords ", "doc_type":"usermanual", "kw":"Changing a User Password,Managing Users,User Guide", "search_title":"", @@ -8006,8 +8074,8 @@ "uri":"admin_guide_000144.html", "node_id":"admin_guide_000144.xml", "product_code":"mrs", - "code":"429", - "des":"If a user forgets the password or the public account password needs to be changed periodically, you can initialize the password on FusionInsight Manager. After the passwo", + "code":"433", + "des":"If a user forgets the password or the public account password needs to be changed periodically, you can initialize the password on MRS Manager. After the password is init", "doc_type":"usermanual", "kw":"Initializing a Password,Managing Users,User Guide", "search_title":"", @@ -8024,7 +8092,7 @@ "uri":"admin_guide_000145.html", "node_id":"admin_guide_000145.xml", "product_code":"mrs", - "code":"430", + "code":"434", "des":"If a user uses a security mode cluster to develop applications, the keytab file of the user needs to be obtained for security authentication. You can export keytab files ", "doc_type":"usermanual", "kw":"Exporting an Authentication Credential File,Managing Users,User Guide", @@ -8042,8 +8110,8 @@ "uri":"admin_guide_000147.html", "node_id":"admin_guide_000147.xml", "product_code":"mrs", - "code":"431", - "des":"FusionInsight Manager supports a maximum of 5000 user groups (including built-in user groups). You can create and manage different user groups based on service scenarios ", + "code":"435", + "des":"MRS Manager supports a maximum of 5000 user groups (including built-in user groups). You can create and manage different user groups based on service scenarios on MRS Man", "doc_type":"usermanual", "kw":"Managing User Groups,Configuring Permissions,User Guide", "search_title":"", @@ -8060,8 +8128,8 @@ "uri":"admin_guide_000148.html", "node_id":"admin_guide_000148.xml", "product_code":"mrs", - "code":"432", - "des":"FusionInsight Manager supports a maximum of 5000 roles (including system built-in roles but excluding roles automatically created by tenants). Based on different service ", + "code":"436", + "des":"MRS Manager supports a maximum of 5000 roles (including system built-in roles but excluding roles automatically created by tenants). Based on different service requiremen", "doc_type":"usermanual", "kw":"Managing Roles,Configuring Permissions,User Guide", "search_title":"", @@ -8078,7 +8146,7 @@ "uri":"admin_guide_000149.html", "node_id":"admin_guide_000149.xml", "product_code":"mrs", - "code":"433", + "code":"437", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Policies", @@ -8097,8 +8165,8 @@ "uri":"admin_guide_000150.html", "node_id":"admin_guide_000150.xml", "product_code":"mrs", - "code":"434", - "des":"To keep up with service security requirements, you can set password security rules, user login security rules, and user locking rules on FusionInsight Manager.Modify pass", + "code":"438", + "des":"To keep up with service security requirements, you can set password security rules, user login security rules, and user locking rules on MRS Manager.Modify password polic", "doc_type":"usermanual", "kw":"Configuring Password Policies,Security Policies,User Guide", "search_title":"", @@ -8115,8 +8183,8 @@ "uri":"admin_guide_000151.html", "node_id":"admin_guide_000151.xml", "product_code":"mrs", - "code":"435", - "des":"User admin or administrators who are bound to the Manager_administrator role can configure the independent attribute on FusionInsight Manager so that common users (all se", + "code":"439", + "des":"User admin or administrators who are bound to the Manager_administrator role can configure the independent attribute on MRS Manager so that common users (all service user", "doc_type":"usermanual", "kw":"Configuring the Independent Attribute,Security Policies,User Guide", "search_title":"", @@ -8133,7 +8201,7 @@ "uri":"admin_guide_000153.html", "node_id":"admin_guide_000153.xml", "product_code":"mrs", - "code":"436", + "code":"440", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring Interconnections", @@ -8152,8 +8220,8 @@ "uri":"admin_guide_000154.html", "node_id":"admin_guide_000154.xml", "product_code":"mrs", - "code":"437", - "des":"If users need to view alarms and monitoring data of a cluster on the O&M platform, you can use Simple Network Management Protocol (SNMP) on FusionInsight Manager to repor", + "code":"441", + "des":"If users need to view alarms and monitoring data of a cluster on the O&M platform, you can use Simple Network Management Protocol (SNMP) on MRS Manager to report related ", "doc_type":"usermanual", "kw":"Configuring SNMP Northbound Parameters,Configuring Interconnections,User Guide", "search_title":"", @@ -8170,8 +8238,8 @@ "uri":"admin_guide_000155.html", "node_id":"admin_guide_000155.xml", "product_code":"mrs", - "code":"438", - "des":"If users need to view alarms and events of a cluster on the unified alarm reporting platform, you can use the Syslog protocol on FusionInsight Manager to report related d", + "code":"442", + "des":"If users need to view alarms and events of a cluster on the unified alarm reporting platform, you can use the Syslog protocol on MRS Manager to report related data to the", "doc_type":"usermanual", "kw":"Configuring Syslog Northbound Parameters,Configuring Interconnections,User Guide", "search_title":"", @@ -8188,7 +8256,7 @@ "uri":"admin_guide_000156.html", "node_id":"admin_guide_000156.xml", "product_code":"mrs", - "code":"439", + "code":"443", "des":"The monitoring data reporting function writes the monitoring data collected in the system into a text file and uploads the file to a specified server in FTP or SFTP mode.", "doc_type":"usermanual", "kw":"Configuring Monitoring Metric Dumping,Configuring Interconnections,User Guide", @@ -8206,8 +8274,8 @@ "uri":"admin_guide_000157.html", "node_id":"admin_guide_000157.xml", "product_code":"mrs", - "code":"440", - "des":"CA certificates are used to encrypt data during communication between FusionInsight Manager modules and between cluster component clients and servers to ensure security. ", + "code":"444", + "des":"CA certificates are used to encrypt data during communication between MRS Manager modules and between cluster component clients and servers to ensure security. CA certifi", "doc_type":"usermanual", "kw":"Importing a Certificate,System Configuration,User Guide", "search_title":"", @@ -8224,7 +8292,7 @@ "uri":"admin_guide_000159.html", "node_id":"admin_guide_000159.xml", "product_code":"mrs", - "code":"441", + "code":"445", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"OMS Management", @@ -8242,8 +8310,8 @@ "uri":"admin_guide_000160.html", "node_id":"admin_guide_000160.xml", "product_code":"mrs", - "code":"442", - "des":"Log in to FusionInsight Manager and choose System > OMS. You can perform maintenance operations on the OMS page, including viewing basic information, viewing the service ", + "code":"446", + "des":"Log in to MRS Manager and choose System > OMS. You can perform maintenance operations on the OMS page, including viewing basic information, viewing the service status of ", "doc_type":"usermanual", "kw":"Overview of the OMS Page,OMS Management,User Guide", "search_title":"", @@ -8260,8 +8328,8 @@ "uri":"admin_guide_000162.html", "node_id":"admin_guide_000162.xml", "product_code":"mrs", - "code":"443", - "des":"Based on the security requirements of the user environment, you can modify the Kerberos and LDAP configurations in the OMS on FusionInsight Manager.After the OMS service ", + "code":"447", + "des":"Based on the security requirements of the user environment, you can modify the Kerberos and LDAP configurations in the OMS on MRS Manager.After the OMS service configurat", "doc_type":"usermanual", "kw":"Modifying OMS Service Configuration Parameters,OMS Management,User Guide", "search_title":"", @@ -8278,7 +8346,7 @@ "uri":"admin_guide_000164.html", "node_id":"admin_guide_000164.xml", "product_code":"mrs", - "code":"444", + "code":"448", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Component Management", @@ -8297,8 +8365,8 @@ "uri":"admin_guide_000165.html", "node_id":"admin_guide_000165.xml", "product_code":"mrs", - "code":"445", - "des":"A complete MRS cluster consists of multiple component packages. Before installing some services on FusionInsight Manager, check whether the component packages of those se", + "code":"449", + "des":"A complete MRS cluster consists of multiple component packages. Before installing some services on MRS Manager, check whether the component packages of those services hav", "doc_type":"usermanual", "kw":"Viewing Component Packages,Component Management,User Guide", "search_title":"", @@ -8315,7 +8383,7 @@ "uri":"admin_guide_000166.html", "node_id":"admin_guide_000166.xml", "product_code":"mrs", - "code":"446", + "code":"450", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Cluster Management", @@ -8334,7 +8402,7 @@ "uri":"admin_guide_000170.html", "node_id":"admin_guide_000170.xml", "product_code":"mrs", - "code":"447", + "code":"451", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring Client", @@ -8352,7 +8420,7 @@ "uri":"admin_guide_000171.html", "node_id":"admin_guide_000171.xml", "product_code":"mrs", - "code":"448", + "code":"452", "des":"This section describes how to install the clients of all services, except Flume, in the MRS cluster. MRS provides shell scripts for different services so that maintenance", "doc_type":"usermanual", "kw":"Installing a Client,Configuring Client,User Guide", @@ -8370,7 +8438,7 @@ "uri":"admin_guide_000172.html", "node_id":"admin_guide_000172.xml", "product_code":"mrs", - "code":"449", + "code":"453", "des":"After the client is installed, you can use the shell command on the client in O&M or service scenarios, or use the sample project on the client during application develop", "doc_type":"usermanual", "kw":"Using a Client,Configuring Client,User Guide", @@ -8388,8 +8456,8 @@ "uri":"admin_guide_000173.html", "node_id":"admin_guide_000173.xml", "product_code":"mrs", - "code":"450", - "des":"The cluster provides a client for you to connect to a server, view task results, or manage data. If you modify service configuration parameters on FusionInsight Manager a", + "code":"454", + "des":"The cluster provides a client for you to connect to a server, view task results, or manage data. If you modify service configuration parameters on MRS Manager and restart", "doc_type":"usermanual", "kw":"Updating the Configuration of an Installed Client,Configuring Client,User Guide", "search_title":"", @@ -8406,7 +8474,7 @@ "uri":"admin_guide_000174.html", "node_id":"admin_guide_000174.xml", "product_code":"mrs", - "code":"451", + "code":"455", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Cluster Mutual Trust Management", @@ -8425,7 +8493,7 @@ "uri":"admin_guide_000175.html", "node_id":"admin_guide_000175.xml", "product_code":"mrs", - "code":"452", + "code":"456", "des":"By default, users of a big data cluster in security mode can only access resources in the cluster but cannot perform identity authentication or access resources in other ", "doc_type":"usermanual", "kw":"Overview of Mutual Trust Between Clusters,Cluster Mutual Trust Management,User Guide", @@ -8443,8 +8511,8 @@ "uri":"admin_guide_000176.html", "node_id":"admin_guide_000176.xml", "product_code":"mrs", - "code":"453", - "des":"The secure usage scope of users in each system is called a domain. Each system must have a unique domain name. The domain name of FusionInsight Manager is generated durin", + "code":"457", + "des":"The secure usage scope of users in each system is called a domain. Each system must have a unique domain name. The domain name of MRS Manager is generated during installa", "doc_type":"usermanual", "kw":"Changing Manager's Domain Name,Cluster Mutual Trust Management,User Guide", "search_title":"", @@ -8461,8 +8529,8 @@ "uri":"admin_guide_000177.html", "node_id":"admin_guide_000177.xml", "product_code":"mrs", - "code":"454", - "des":"When two security-mode clusters managed by different FusionInsight Managers need to access each other's resources, the system administrator can configure cross-Manager mu", + "code":"458", + "des":"When two security-mode clusters managed by different MRS Managers need to access each other's resources, the system administrator can configure cross-Manager mutual trust", "doc_type":"usermanual", "kw":"Configuring Cross-Manager Mutual Trust Between Clusters,Cluster Mutual Trust Management,User Guide", "search_title":"", @@ -8479,8 +8547,8 @@ "uri":"admin_guide_000178.html", "node_id":"admin_guide_000178.xml", "product_code":"mrs", - "code":"455", - "des":"After cross-Manager cluster mutual trust is configured, assign user access permissions on FusionInsight Managers so that these users can perform service operations in the", + "code":"459", + "des":"After cross-Manager cluster mutual trust is configured, assign user access permissions on MRS Managers so that these users can perform service operations in the mutually ", "doc_type":"usermanual", "kw":"Assigning User Permissions After Cross-Cluster Mutual Trust Is Configured,Cluster Mutual Trust Manag", "search_title":"", @@ -8497,8 +8565,8 @@ "uri":"admin_guide_000182.html", "node_id":"admin_guide_000182.xml", "product_code":"mrs", - "code":"456", - "des":"You can modify the configuration file to periodically back up FusionInsight Manager alarm information, FusionInsight Manager audit information, and audit information of a", + "code":"460", + "des":"You can modify the configuration file to periodically back up MRS Manager alarm information, MRS Manager audit information, and audit information of all services to the s", "doc_type":"usermanual", "kw":"Configuring Scheduled Backup of Alarm and Audit Information,Cluster Management,User Guide", "search_title":"", @@ -8515,10 +8583,10 @@ "uri":"admin_guide_000183.html", "node_id":"admin_guide_000183.xml", "product_code":"mrs", - "code":"457", - "des":"When FusionInsight Manager is installed, two pieces of routing information are automatically created on the active management node. You can run the ip rule list command t", + "code":"461", + "des":"When MRS Manager is installed, two pieces of routing information are automatically created on the active management node. You can run the ip rule list command to view the", "doc_type":"usermanual", - "kw":"Modifying the FusionInsight Manager Routing Table,Cluster Management,User Guide", + "kw":"Modifying the MRS Manager Routing Table,Cluster Management,User Guide", "search_title":"", "metedata":[ { @@ -8526,15 +8594,15 @@ "prodname":"mrs" } ], - "title":"Modifying the FusionInsight Manager Routing Table", + "title":"Modifying the MRS Manager Routing Table", "githuburl":"" }, { "uri":"admin_guide_000189.html", "node_id":"admin_guide_000189.xml", "product_code":"mrs", - "code":"458", - "des":"FusionInsight Manager allows you to set clusters, services, hosts, or OMSs to the maintenance mode. Objects in maintenance mode do not report alarms. This prevents the sy", + "code":"462", + "des":"MRS Manager allows you to set clusters, services, hosts, or OMSs to the maintenance mode. Objects in maintenance mode do not report alarms. This prevents the system from ", "doc_type":"usermanual", "kw":"Switching to the Maintenance Mode,Cluster Management,User Guide", "search_title":"", @@ -8551,7 +8619,7 @@ "uri":"admin_guide_000191.html", "node_id":"admin_guide_000191.xml", "product_code":"mrs", - "code":"459", + "code":"463", "des":"To ensure long-term and stable running of the system, administrators or maintenance engineers need to periodically check items listed in Table 1 and rectify the detected ", "doc_type":"usermanual", "kw":"Routine Maintenance,Cluster Management,User Guide", @@ -8569,7 +8637,7 @@ "uri":"admin_guide_000192.html", "node_id":"admin_guide_000192.xml", "product_code":"mrs", - "code":"460", + "code":"464", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Log Management", @@ -8588,7 +8656,7 @@ "uri":"admin_guide_000193.html", "node_id":"admin_guide_000193.xml", "product_code":"mrs", - "code":"461", + "code":"465", "des":"MRS cluster logs are stored in the /var/log/Bigdata directory. The following table lists the log types.The following table lists the MRS log directories.After the multi-i", "doc_type":"usermanual", "kw":"About Logs,Log Management,User Guide", @@ -8606,7 +8674,7 @@ "uri":"admin_guide_000194.html", "node_id":"admin_guide_000194.xml", "product_code":"mrs", - "code":"462", + "code":"466", "des":"Log path: The default storage path of Manager log files is /var/log/Bigdata/Manager component.ControllerService: /var/log/Bigdata/controller/ (OMS installation and run lo", "doc_type":"usermanual", "kw":"Manager Log List,Log Management,User Guide", @@ -8624,8 +8692,8 @@ "uri":"admin_guide_000195.html", "node_id":"admin_guide_000195.xml", "product_code":"mrs", - "code":"463", - "des":"You can change the log levels of FusionInsight Manager. For a specific service, you can change the log level and the log file size to prevent the failure in saving logs d", + "code":"467", + "des":"You can change the log levels of MRS Manager. For a specific service, you can change the log level and the log file size to prevent the failure in saving logs due to insu", "doc_type":"usermanual", "kw":"Configuring the Log Level and Log File Size,Log Management,User Guide", "search_title":"", @@ -8642,7 +8710,7 @@ "uri":"admin_guide_000196.html", "node_id":"admin_guide_000196.xml", "product_code":"mrs", - "code":"464", + "code":"468", "des":"Audit logs of cluster components are classified by name and stored in the /var/log/Bigdata/audit directory on each cluster node. The OMS automatically backs up the audit ", "doc_type":"usermanual", "kw":"Configuring the Number of Local Audit Log Backups,Log Management,User Guide", @@ -8660,8 +8728,8 @@ "uri":"admin_guide_000197.html", "node_id":"admin_guide_000197.xml", "product_code":"mrs", - "code":"465", - "des":"FusionInsight Manager allows users to view logs of each role instance.On the Hosts page, click a host name. In the instance list of the host, you can view the log files o", + "code":"469", + "des":"MRS Manager allows users to view logs of each role instance.On the Hosts page, click a host name. In the instance list of the host, you can view the log files of all role", "doc_type":"usermanual", "kw":"Viewing Role Instance Logs,Log Management,User Guide", "search_title":"", @@ -8678,7 +8746,7 @@ "uri":"admin_guide_000198.html", "node_id":"admin_guide_000198.xml", "product_code":"mrs", - "code":"466", + "code":"470", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backup and Recovery Management", @@ -8696,8 +8764,8 @@ "uri":"admin_guide_000399.html", "node_id":"admin_guide_000399.xml", "product_code":"mrs", - "code":"467", - "des":"FusionInsight Manager provides the backup and restoration of system data and user data by component. The system can back up Manager data, component metadata, and service ", + "code":"471", + "des":"MRS Manager provides the backup and restoration of system data and user data by component. The system can back up Manager data, component metadata, and service data.Data ", "doc_type":"usermanual", "kw":"Introduction,Backup and Recovery Management,User Guide", "search_title":"", @@ -8714,7 +8782,7 @@ "uri":"admin_guide_000201.html", "node_id":"admin_guide_000201.xml", "product_code":"mrs", - "code":"468", + "code":"472", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backing Up Data", @@ -8732,8 +8800,8 @@ "uri":"admin_guide_000202.html", "node_id":"admin_guide_000202.xml", "product_code":"mrs", - "code":"469", - "des":"To ensure data security of FusionInsight Manager routinely or before and after a critical operation (such as capacity expansion and reduction) on FusionInsight Manager, y", + "code":"473", + "des":"To ensure data security of MRS Manager routinely or before and after a critical operation (such as capacity expansion and reduction) on MRS Manager, you need to back up M", "doc_type":"usermanual", "kw":"Backing Up Manager Data,Backing Up Data,User Guide", "search_title":"", @@ -8750,7 +8818,7 @@ "uri":"admin_guide_000343.html", "node_id":"admin_guide_000343.xml", "product_code":"mrs", - "code":"470", + "code":"474", "des":"To ensure CDL service data security routinely or before a major operation on CDL (such as upgrade or migration), you need to back up CDL data. The backup data can be used", "doc_type":"usermanual", "kw":"Backing Up CDL Data,Backing Up Data,User Guide", @@ -8768,7 +8836,7 @@ "uri":"admin_guide_000348.html", "node_id":"admin_guide_000348.xml", "product_code":"mrs", - "code":"471", + "code":"475", "des":"To ensure ClickHouse metadata security or before a major operation on ZooKeeper (such as upgrade or migration), you need to back up ClickHouse metadata. The backup data c", "doc_type":"usermanual", "kw":"Backing Up ClickHouse Metadata,Backing Up Data,User Guide", @@ -8786,7 +8854,7 @@ "uri":"admin_guide_000349.html", "node_id":"admin_guide_000349.xml", "product_code":"mrs", - "code":"472", + "code":"476", "des":"To ensure ClickHouse service data security routinely or before a major operation on ClickHouse (such as upgrade or migration), you need to back up ClickHouse service data", "doc_type":"usermanual", "kw":"Backing Up ClickHouse Service Data,Backing Up Data,User Guide", @@ -8804,7 +8872,7 @@ "uri":"admin_guide_000203.html", "node_id":"admin_guide_000203.xml", "product_code":"mrs", - "code":"473", + "code":"477", "des":"To ensure DBService service data security routinely or before a major operation on DBService (such as upgrade or migration), you need to back up DBService data. The backu", "doc_type":"usermanual", "kw":"Backing Up DBService Data,Backing Up Data,User Guide", @@ -8822,7 +8890,7 @@ "uri":"admin_guide_000204.html", "node_id":"admin_guide_000204.xml", "product_code":"mrs", - "code":"474", + "code":"478", "des":"To ensure HBase metadata security (including tableinfo files and HFiles) or before a major operation on HBase system tables (such as upgrade or migration), you need to ba", "doc_type":"usermanual", "kw":"Backing Up HBase Metadata,Backing Up Data,User Guide", @@ -8840,7 +8908,7 @@ "uri":"admin_guide_000205.html", "node_id":"admin_guide_000205.xml", "product_code":"mrs", - "code":"475", + "code":"479", "des":"To ensure HBase service data security routinely or before a major operation on HBase (such as upgrade or migration), you need to back up HBase service data. The backup da", "doc_type":"usermanual", "kw":"Backing Up HBase Service Data,Backing Up Data,User Guide", @@ -8858,7 +8926,7 @@ "uri":"admin_guide_000208.html", "node_id":"admin_guide_000208.xml", "product_code":"mrs", - "code":"476", + "code":"480", "des":"To ensure NameNode service data security routinely or before a major operation on NameNode (such as upgrade or migration), you need to back up NameNode data. The backup d", "doc_type":"usermanual", "kw":"Backing Up NameNode Data,Backing Up Data,User Guide", @@ -8876,7 +8944,7 @@ "uri":"admin_guide_000209.html", "node_id":"admin_guide_000209.xml", "product_code":"mrs", - "code":"477", + "code":"481", "des":"To ensure HDFS service data security routinely or before a major operation on HDFS (such as upgrade or migration), you need to back up HDFS service data. The backup data ", "doc_type":"usermanual", "kw":"Backing Up HDFS Service Data,Backing Up Data,User Guide", @@ -8894,7 +8962,7 @@ "uri":"admin_guide_000210.html", "node_id":"admin_guide_000210.xml", "product_code":"mrs", - "code":"478", + "code":"482", "des":"To ensure Hive service data security routinely or before a major operation on Hive (such as upgrade or migration), you need to back up Hive service data. The backup data ", "doc_type":"usermanual", "kw":"Backing Up Hive Service Data,Backing Up Data,User Guide", @@ -8912,7 +8980,7 @@ "uri":"admin_guide_000350.html", "node_id":"admin_guide_000350.xml", "product_code":"mrs", - "code":"479", + "code":"483", "des":"To ensure IoTDB metadata security and prevent the IoTDB service from being unavailable due to IoTDB metadata file damages, you need to back up IoTDB metadata. The backup ", "doc_type":"usermanual", "kw":"Backing Up IoTDB Metadata,Backing Up Data,User Guide", @@ -8930,7 +8998,7 @@ "uri":"admin_guide_000360.html", "node_id":"admin_guide_000360.xml", "product_code":"mrs", - "code":"480", + "code":"484", "des":"To ensure IoTDB service data security routinely or before a major operation on IoTDB (such as upgrade or migration), you need to back up IoTDB service data. The backup da", "doc_type":"usermanual", "kw":"Backing Up IoTDB Service Data,Backing Up Data,User Guide", @@ -8948,7 +9016,7 @@ "uri":"admin_guide_000211.html", "node_id":"admin_guide_000211.xml", "product_code":"mrs", - "code":"481", + "code":"485", "des":"To ensure Kafka metadata security or before a major operation on ZooKeeper (such as upgrade or migration), you need to back up Kafka metadata. The backup data can be used", "doc_type":"usermanual", "kw":"Backing Up Kafka Metadata,Backing Up Data,User Guide", @@ -8966,7 +9034,7 @@ "uri":"admin_guide_000215.html", "node_id":"admin_guide_000215.xml", "product_code":"mrs", - "code":"482", + "code":"486", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Recovering Data", @@ -8984,7 +9052,7 @@ "uri":"admin_guide_000216.html", "node_id":"admin_guide_000216.xml", "product_code":"mrs", - "code":"483", + "code":"487", "des":"Manager data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical", "doc_type":"usermanual", "kw":"Restoring Manager Data,Recovering Data,User Guide", @@ -9002,7 +9070,7 @@ "uri":"admin_guide_000345.html", "node_id":"admin_guide_000345.xml", "product_code":"mrs", - "code":"484", + "code":"488", "des":"CDL data needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After an administrator performs major operati", "doc_type":"usermanual", "kw":"Restoring CDL Data,Recovering Data,User Guide", @@ -9020,7 +9088,7 @@ "uri":"admin_guide_000358.html", "node_id":"admin_guide_000358.xml", "product_code":"mrs", - "code":"485", + "code":"489", "des":"ClickHouse metadata needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After a user performs major operat", "doc_type":"usermanual", "kw":"Restoring ClickHouse Metadata,Recovering Data,User Guide", @@ -9038,7 +9106,7 @@ "uri":"admin_guide_000359.html", "node_id":"admin_guide_000359.xml", "product_code":"mrs", - "code":"486", + "code":"490", "des":"ClickHouse data needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After a user performs major operations", "doc_type":"usermanual", "kw":"Restoring ClickHouse Service Data,Recovering Data,User Guide", @@ -9056,7 +9124,7 @@ "uri":"admin_guide_000217.html", "node_id":"admin_guide_000217.xml", "product_code":"mrs", - "code":"487", + "code":"491", "des":"DBService data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critic", "doc_type":"usermanual", "kw":"Restoring DBService data,Recovering Data,User Guide", @@ -9074,7 +9142,7 @@ "uri":"admin_guide_000218.html", "node_id":"admin_guide_000218.xml", "product_code":"mrs", - "code":"488", + "code":"492", "des":"To ensure HBase metadata security (including tableinfo files and HFiles) or before a major operation on HBase system tables (such as upgrade or migration), you need to ba", "doc_type":"usermanual", "kw":"Restoring HBase Metadata,Recovering Data,User Guide", @@ -9092,7 +9160,7 @@ "uri":"admin_guide_000219.html", "node_id":"admin_guide_000219.xml", "product_code":"mrs", - "code":"489", + "code":"493", "des":"HBase data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical d", "doc_type":"usermanual", "kw":"Restoring HBase Service Data,Recovering Data,User Guide", @@ -9110,7 +9178,7 @@ "uri":"admin_guide_000222.html", "node_id":"admin_guide_000222.xml", "product_code":"mrs", - "code":"490", + "code":"494", "des":"NameNode data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critica", "doc_type":"usermanual", "kw":"Restoring NameNode Data,Recovering Data,User Guide", @@ -9128,7 +9196,7 @@ "uri":"admin_guide_000223.html", "node_id":"admin_guide_000223.xml", "product_code":"mrs", - "code":"491", + "code":"495", "des":"HDFS data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical da", "doc_type":"usermanual", "kw":"Restoring HDFS Service Data,Recovering Data,User Guide", @@ -9146,7 +9214,7 @@ "uri":"admin_guide_000224.html", "node_id":"admin_guide_000224.xml", "product_code":"mrs", - "code":"492", + "code":"496", "des":"Hive data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical da", "doc_type":"usermanual", "kw":"Restoring Hive Service Data,Recovering Data,User Guide", @@ -9164,7 +9232,7 @@ "uri":"admin_guide_000351.html", "node_id":"admin_guide_000351.xml", "product_code":"mrs", - "code":"493", + "code":"497", "des":"To ensure IoTDB metadata security and prevent the IoTDB service from being unavailable due to IoTDB file damage, IoTDB metadata needs to be backed up. In this way, the sy", "doc_type":"usermanual", "kw":"Restoring IoTDB Metadata,Recovering Data,User Guide", @@ -9182,7 +9250,7 @@ "uri":"admin_guide_000361.html", "node_id":"admin_guide_000361.xml", "product_code":"mrs", - "code":"494", + "code":"498", "des":"IoTDB service data needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After an administrator performs maj", "doc_type":"usermanual", "kw":"Restoring IoTDB Service Data,Recovering Data,User Guide", @@ -9200,7 +9268,7 @@ "uri":"admin_guide_000225.html", "node_id":"admin_guide_000225.xml", "product_code":"mrs", - "code":"495", + "code":"499", "des":"Kafka data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical d", "doc_type":"usermanual", "kw":"Restoring Kafka Metadata,Recovering Data,User Guide", @@ -9218,7 +9286,7 @@ "uri":"admin_guide_000200.html", "node_id":"admin_guide_000200.xml", "product_code":"mrs", - "code":"496", + "code":"500", "des":"DistCp is used to replicate the data stored in HDFS from a cluster to another cluster. DistCp depends on the cross-cluster replication function, which is disabled by defa", "doc_type":"usermanual", "kw":"Enabling Cross-Cluster Replication,Backup and Recovery Management,User Guide", @@ -9236,8 +9304,8 @@ "uri":"admin_guide_000229.html", "node_id":"admin_guide_000229.xml", "product_code":"mrs", - "code":"497", - "des":"When DistCp is used to back up data, the backup snapshot is saved to HDFS of the active cluster. FusionInsight Manager supports using the local snapshot for quick data re", + "code":"501", + "des":"When DistCp is used to back up data, the backup snapshot is saved to HDFS of the active cluster. MRS Manager supports using the local snapshot for quick data restoration,", "doc_type":"usermanual", "kw":"Managing Local Quick Restoration Tasks,Backup and Recovery Management,User Guide", "search_title":"", @@ -9254,8 +9322,8 @@ "uri":"admin_guide_000230.html", "node_id":"admin_guide_000230.xml", "product_code":"mrs", - "code":"498", - "des":"This section describes how to modify the parameters of a created backup task on FusionInsight Manager to meet changing service requirements. The parameters of restoration", + "code":"502", + "des":"This section describes how to modify the parameters of a created backup task on MRS Manager to meet changing service requirements. The parameters of restoration tasks can", "doc_type":"usermanual", "kw":"Modifying a Backup Task,Backup and Recovery Management,User Guide", "search_title":"", @@ -9272,8 +9340,8 @@ "uri":"admin_guide_000231.html", "node_id":"admin_guide_000231.xml", "product_code":"mrs", - "code":"499", - "des":"This section describes how to view created backup and recovery tasks and check their running status on FusionInsight Manager.You have logged in to FusionInsight Manager. ", + "code":"503", + "des":"This section describes how to view created backup and recovery tasks and check their running status on MRS Manager.You have logged in to MRS Manager. For details, see Log", "doc_type":"usermanual", "kw":"Viewing Backup and Restoration Tasks,Backup and Recovery Management,User Guide", "search_title":"", @@ -9290,10 +9358,10 @@ "uri":"admin_guide_000357.html", "node_id":"admin_guide_000357.xml", "product_code":"mrs", - "code":"500", - "des":"This section applies only to MRS 3.1.0.How do I configure the environment when I create a ClickHouse backup task on FusionInsight Manager and set the path type to RemoteH", + "code":"504", + "des":"This section applies only to MRS 3.1.0.How do I configure the environment when I create a ClickHouse backup task on MRS Manager and set the path type to RemoteHDFS?For ex", "doc_type":"usermanual", - "kw":"How Do I Configure the Environment When I Create a ClickHouse Backup Task on FusionInsight Manager a", + "kw":"How Do I Configure the Environment When I Create a ClickHouse Backup Task on MRS Manager and Set the", "search_title":"", "metedata":[ { @@ -9301,14 +9369,14 @@ "prodname":"mrs" } ], - "title":"How Do I Configure the Environment When I Create a ClickHouse Backup Task on FusionInsight Manager and Set the Path Type to RemoteHDFS?", + "title":"How Do I Configure the Environment When I Create a ClickHouse Backup Task on MRS Manager and Set the Path Type to RemoteHDFS?", "githuburl":"" }, { "uri":"admin_guide_000233.html", "node_id":"admin_guide_000233.xml", "product_code":"mrs", - "code":"501", + "code":"505", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Management", @@ -9326,7 +9394,7 @@ "uri":"admin_guide_000234.html", "node_id":"admin_guide_000234.xml", "product_code":"mrs", - "code":"502", + "code":"506", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Overview", @@ -9344,8 +9412,8 @@ "uri":"admin_guide_000235.html", "node_id":"admin_guide_000235.xml", "product_code":"mrs", - "code":"503", - "des":"FusionInsight adopts the role-based access control (RBAC) mode to manage rights on the big data system. It integrates the right management functions of the components to ", + "code":"507", + "des":"MRS adopts the role-based access control (RBAC) mode to manage rights on the big data system. It integrates the right management functions of the components to centrally ", "doc_type":"usermanual", "kw":"Right Model,Security Overview,User Guide", "search_title":"", @@ -9362,8 +9430,8 @@ "uri":"admin_guide_000236.html", "node_id":"admin_guide_000236.xml", "product_code":"mrs", - "code":"504", - "des":"FusionInsight adopts the Lightweight Directory Access Protocol (LDAP) to store data of users and user groups. Information about role definitions is stored in the relation", + "code":"508", + "des":"MRS adopts the Lightweight Directory Access Protocol (LDAP) to store data of users and user groups. Information about role definitions is stored in the relational databas", "doc_type":"usermanual", "kw":"Right Mechanism,Security Overview,User Guide", "search_title":"", @@ -9380,7 +9448,7 @@ "uri":"admin_guide_000237.html", "node_id":"admin_guide_000237.xml", "product_code":"mrs", - "code":"505", + "code":"509", "des":"The big data platform performs user identity authentication to prevent invalid users from accessing the cluster. The cluster provides authentication capabilities in both ", "doc_type":"usermanual", "kw":"Authentication Policies,Security Overview,User Guide", @@ -9398,7 +9466,7 @@ "uri":"admin_guide_000238.html", "node_id":"admin_guide_000238.xml", "product_code":"mrs", - "code":"506", + "code":"510", "des":"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 configurat", "doc_type":"usermanual", "kw":"Permission Verification Policies,Security Overview,User Guide", @@ -9416,10 +9484,10 @@ "uri":"admin_guide_000239.html", "node_id":"admin_guide_000239.xml", "product_code":"mrs", - "code":"507", + "code":"511", "des":"The MRS cluster provides the following three types of users. The system administrator needs to periodically change the passwords. It is not recommended to use the default", "doc_type":"usermanual", - "kw":"User Account List,Security Overview,User Guide", + "kw":"User Account ListUser Account ListSystem User Description,Security Overview,User Guide", "search_title":"", "metedata":[ { @@ -9427,15 +9495,15 @@ "prodname":"mrs" } ], - "title":"User Account List", + "title":"User Account ListUser Account ListSystem User Description", "githuburl":"" }, { "uri":"admin_guide_000240.html", "node_id":"admin_guide_000240.xml", "product_code":"mrs", - "code":"508", - "des":"If the current cluster is not the cluster that is installed for the first time in FusionInsight Manager, the default user group name of all components except Manager in t", + "code":"512", + "des":"If the current cluster is not the cluster that is installed for the first time in MRS Manager, the default user group name of all components except Manager in the cluster", "doc_type":"usermanual", "kw":"Default Permission Information,Security Overview,User Guide", "search_title":"", @@ -9452,10 +9520,10 @@ "uri":"admin_guide_000241.html", "node_id":"admin_guide_000241.xml", "product_code":"mrs", - "code":"509", - "des":"You can query and set user rights data through the following FusionInsight Manager modules:User management: Users can be added, deleted, modified, queried, bound to user ", + "code":"513", + "des":"You can query and set user rights data through the following MRS Manager modules:User management: Users can be added, deleted, modified, queried, bound to user groups, an", "doc_type":"usermanual", - "kw":"FusionInsight Manager Security Functions,Security Overview,User Guide", + "kw":"MRS Manager Security Functions,Security Overview,User Guide", "search_title":"", "metedata":[ { @@ -9463,14 +9531,14 @@ "prodname":"mrs" } ], - "title":"FusionInsight Manager Security Functions", + "title":"MRS Manager Security Functions", "githuburl":"" }, { "uri":"admin_guide_000242.html", "node_id":"admin_guide_000242.xml", "product_code":"mrs", - "code":"510", + "code":"514", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Account Management", @@ -9489,7 +9557,7 @@ "uri":"admin_guide_000243.html", "node_id":"admin_guide_000243.xml", "product_code":"mrs", - "code":"511", + "code":"515", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Account Security Settings", @@ -9508,7 +9576,7 @@ "uri":"admin_guide_000245.html", "node_id":"admin_guide_000245.xml", "product_code":"mrs", - "code":"512", + "code":"516", "des":"If the LDAP user cn=pg_search_dn,ou=Users,dc=hadoop,dc=com and LDAP management accounts cn=krbkdc,ou=Users,dc=hadoop,dc=com and cn=krbadmin,ou=Users,dc=hadoop,dc=com are ", "doc_type":"usermanual", "kw":"Unlocking LDAP Users and Management Accounts,Account Security Settings,User Guide", @@ -9526,7 +9594,7 @@ "uri":"admin_guide_000246.html", "node_id":"admin_guide_000246.xml", "product_code":"mrs", - "code":"513", + "code":"517", "des":"If the service is abnormal, the internal user of the system may be locked. Unlock the user promptly, or the cluster cannot run properly. For the list of system internal u", "doc_type":"usermanual", "kw":"Internal an Internal System User,Account Security Settings,User Guide", @@ -9544,7 +9612,7 @@ "uri":"admin_guide_000247.html", "node_id":"admin_guide_000247.xml", "product_code":"mrs", - "code":"514", + "code":"518", "des":"HDFS and ZooKeeper verify the permission of users who attempt to access the services in both security and normal clusters by default. Users without related permission can", "doc_type":"usermanual", "kw":"Enabling and Disabling Permission Verification on Cluster Components,Account Security Settings,User ", @@ -9562,7 +9630,7 @@ "uri":"admin_guide_000248.html", "node_id":"admin_guide_000248.xml", "product_code":"mrs", - "code":"515", + "code":"519", "des":"When the cluster is installed in normal mode, the component clients do not support security authentication and cannot use the kinit command. Therefore, nodes outside the ", "doc_type":"usermanual", "kw":"Logging In to a Non-Cluster Node Using a Cluster User in Normal Mode,Account Security Settings,User ", @@ -9580,7 +9648,7 @@ "uri":"admin_guide_000249.html", "node_id":"admin_guide_000249.xml", "product_code":"mrs", - "code":"516", + "code":"520", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Changing the Password for a System User", @@ -9599,8 +9667,8 @@ "uri":"admin_guide_000250.html", "node_id":"admin_guide_000250.xml", "product_code":"mrs", - "code":"517", - "des":"User admin is the system administrator account of FusionInsight Manager. You are advised to periodically change the password on FusionInsight Manager to improve system se", + "code":"521", + "des":"User admin is the system administrator account of MRS Manager. You are advised to periodically change the password on MRS Manager to improve system security.User admin is", "doc_type":"usermanual", "kw":"Changing the Password for User admin,Changing the Password for a System User,User Guide", "search_title":"", @@ -9617,8 +9685,8 @@ "uri":"admin_guide_000251.html", "node_id":"admin_guide_000251.xml", "product_code":"mrs", - "code":"518", - "des":"During FusionInsight Manager installation, the system automatically creates user omm and ommdba on each node in the cluster. Periodically change the login passwords of th", + "code":"522", + "des":"During MRS Manager installation, the system automatically creates user omm and ommdba on each node in the cluster. Periodically change the login passwords of the OS users", "doc_type":"usermanual", "kw":"Changing the Password for an OS User,Changing the Password for a System User,User Guide", "search_title":"", @@ -9635,7 +9703,7 @@ "uri":"admin_guide_000252.html", "node_id":"admin_guide_000252.xml", "product_code":"mrs", - "code":"519", + "code":"523", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Changing the Password for a System Internal User", @@ -9654,7 +9722,7 @@ "uri":"admin_guide_000253.html", "node_id":"admin_guide_000253.xml", "product_code":"mrs", - "code":"520", + "code":"524", "des":"It is recommended that the administrator periodically change the password of Kerberos administrator kadmin to improve the system O&M security.If the user password is chan", "doc_type":"usermanual", "kw":"Changing the Password for the Kerberos Administrator,Changing the Password for a System Internal Use", @@ -9672,7 +9740,7 @@ "uri":"admin_guide_000254.html", "node_id":"admin_guide_000254.xml", "product_code":"mrs", - "code":"521", + "code":"525", "des":"It is recommended that the administrator periodically change the password of OMS Kerberos administrator kadmin to improve the system O&M security.If the user password is ", "doc_type":"usermanual", "kw":"Changing the Password for the OMS Kerberos Administrator,Changing the Password for a System Internal", @@ -9690,7 +9758,7 @@ "uri":"admin_guide_000255.html", "node_id":"admin_guide_000255.xml", "product_code":"mrs", - "code":"522", + "code":"526", "des":"It is recommended that the administrator periodically changes the passwords of LDAP administrator cn=root,dc=hadoop,dc=com and LDAP user cn=pg_search_dn,ou=Users,dc=hadoo", "doc_type":"usermanual", "kw":"Changing the Passwords of the LDAP Administrator and the LDAP User (Including OMS LDAP),Changing the", @@ -9708,7 +9776,7 @@ "uri":"admin_guide_000256.html", "node_id":"admin_guide_000256.xml", "product_code":"mrs", - "code":"523", + "code":"527", "des":"It is recommended that the administrator periodically changes the passwords of LDAP administrator accounts cn=krbkdc,ou=Users,dc=hadoop,dc=com and cn=krbadmin,ou=Users,dc", "doc_type":"usermanual", "kw":"Changing the Password for the LDAP Administrator,Changing the Password for a System Internal User,Us", @@ -9726,7 +9794,7 @@ "uri":"admin_guide_000257.html", "node_id":"admin_guide_000257.xml", "product_code":"mrs", - "code":"524", + "code":"528", "des":"It is recommended that the administrator periodically change the password for each component running user to improve the system O&M security.Component running users can b", "doc_type":"usermanual", "kw":"Changing the Password for a Component Running User,Changing the Password for a System Internal User,", @@ -9744,7 +9812,7 @@ "uri":"admin_guide_000258.html", "node_id":"admin_guide_000258.xml", "product_code":"mrs", - "code":"525", + "code":"529", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Changing the Password for a Database User", @@ -9763,7 +9831,7 @@ "uri":"admin_guide_000259.html", "node_id":"admin_guide_000259.xml", "product_code":"mrs", - "code":"526", + "code":"530", "des":"It is recommended that the administrator periodically change the password of the OMS database administrator to improve the system O&M security.The password of user ommdba", "doc_type":"usermanual", "kw":"Changing the Password of the OMS Database Administrator,Changing the Password for a Database User,Us", @@ -9781,7 +9849,7 @@ "uri":"admin_guide_000260.html", "node_id":"admin_guide_000260.xml", "product_code":"mrs", - "code":"527", + "code":"531", "des":"It is recommended that the administrator periodically change the password of the user accessing the OMS database to improve the system O&M security.The OMS service needs ", "doc_type":"usermanual", "kw":"Changing the Password for the Data Access User of the OMS Database,Changing the Password for a Datab", @@ -9799,7 +9867,7 @@ "uri":"admin_guide_000261.html", "node_id":"admin_guide_000261.xml", "product_code":"mrs", - "code":"528", + "code":"532", "des":"It is recommended that the administrator periodically change the password for each component database user to improve the system O&M security.This section applies only to", "doc_type":"usermanual", "kw":"Changing the Password for a Component Database User,Changing the Password for a Database User,User G", @@ -9817,7 +9885,7 @@ "uri":"admin_guide_000363.html", "node_id":"admin_guide_000363.xml", "product_code":"mrs", - "code":"529", + "code":"533", "des":"Default passwords for components in the MRS cluster to connect to the DBService database are random. You are advised to periodically reset the passwords of component data", "doc_type":"usermanual", "kw":"Resetting the Component Database User Password,Changing the Password for a Database User,User Guide", @@ -9835,7 +9903,7 @@ "uri":"admin_guide_000354.html", "node_id":"admin_guide_000354.xml", "product_code":"mrs", - "code":"530", + "code":"534", "des":"The password of user omm for the DBService database cannot be changed on the standby DBService node. Change the password on the active DBService node only.su - ommsource ", "doc_type":"usermanual", "kw":"Changing the Password for User omm in DBService,Changing the Password for a Database User,User Guide", @@ -9853,7 +9921,7 @@ "uri":"admin_guide_000271.html", "node_id":"admin_guide_000271.xml", "product_code":"mrs", - "code":"531", + "code":"535", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Hardening", @@ -9871,8 +9939,8 @@ "uri":"admin_guide_000272.html", "node_id":"admin_guide_000272.xml", "product_code":"mrs", - "code":"532", - "des":"Tomcat is hardened as follows based on open-source software during FusionInsight Manager software installation and use:The Tomcat version is upgraded to the official vers", + "code":"536", + "des":"Tomcat is hardened as follows based on open-source software during MRS Manager software installation and use:The Tomcat version is upgraded to the official version.Permis", "doc_type":"usermanual", "kw":"Hardening Policies,Security Hardening,User Guide", "search_title":"", @@ -9889,7 +9957,7 @@ "uri":"admin_guide_000274.html", "node_id":"admin_guide_000274.xml", "product_code":"mrs", - "code":"533", + "code":"537", "des":"By default, the LDAP service deployed in the OMS and cluster can be accessed by any IP address. To enable the LDAP service to be accessed by only trusted IP addresses, yo", "doc_type":"usermanual", "kw":"Configuring a Trusted IP Address to Access LDAP,Security Hardening,User Guide", @@ -9907,7 +9975,7 @@ "uri":"admin_guide_000276.html", "node_id":"admin_guide_000276.xml", "product_code":"mrs", - "code":"534", + "code":"538", "des":"Setting the HFile and WAL encryption mode to SMS4 or AES has a great impact on the system and will cause data loss in case of any misoperation. Therefore, this operation ", "doc_type":"usermanual", "kw":"HFile and WAL Encryption,Security Hardening,User Guide", @@ -9925,7 +9993,7 @@ "uri":"admin_guide_000277.html", "node_id":"admin_guide_000277.xml", "product_code":"mrs", - "code":"535", + "code":"539", "des":"The channels between components are not encrypted by default. You can set the following parameters to configure security channel encryption.Page access for setting parame", "doc_type":"usermanual", "kw":"Configuring Hadoop Security Parameters,Security Hardening,User Guide", @@ -9943,7 +10011,7 @@ "uri":"admin_guide_000278.html", "node_id":"admin_guide_000278.xml", "product_code":"mrs", - "code":"536", + "code":"540", "des":"If the Replication function is enabled for HBase clusters, a protection mechanism for data modification is added on the standby HBase cluster to ensure data consistency b", "doc_type":"usermanual", "kw":"Configuring an IP Address Whitelist for Modification Allowed by HBase,Security Hardening,User Guide", @@ -9961,7 +10029,7 @@ "uri":"admin_guide_000279.html", "node_id":"admin_guide_000279.xml", "product_code":"mrs", - "code":"537", + "code":"541", "des":"When a cluster is installed, an encryption key is generated automatically by the system so that the security information in the cluster (such as all database user passwor", "doc_type":"usermanual", "kw":"Updating a Key for a Cluster,Security Hardening,User Guide", @@ -9979,7 +10047,7 @@ "uri":"admin_guide_000280.html", "node_id":"admin_guide_000280.xml", "product_code":"mrs", - "code":"538", + "code":"542", "des":"In the cluster adopting the dual-plane networking, the LDAP is deployed on the service plane. To ensure the LDAP data security, you are advised to configure the firewall ", "doc_type":"usermanual", "kw":"Hardening the LDAP,Security Hardening,User Guide", @@ -9997,7 +10065,7 @@ "uri":"admin_guide_000281.html", "node_id":"admin_guide_000281.xml", "product_code":"mrs", - "code":"539", + "code":"543", "des":"Data between the Kafka client and the broker is transmitted in plain text. The Kafka client may be deployed in an untrusted network, exposing the transmitting data to lea", "doc_type":"usermanual", "kw":"Configuring Kafka Data Encryption During Transmission,Security Hardening,User Guide", @@ -10015,8 +10083,8 @@ "uri":"admin_guide_000282.html", "node_id":"admin_guide_000282.xml", "product_code":"mrs", - "code":"540", - "des":"The channel between components is not encrypted by default. You can set parameters to enable security channel encryption.Navigation path for setting parameters: On Fusion", + "code":"544", + "des":"The channel between components is not encrypted by default. You can set parameters to enable security channel encryption.Navigation path for setting parameters: On MRS Ma", "doc_type":"usermanual", "kw":"Configuring HDFS Data Encryption During Transmission,Security Hardening,User Guide", "search_title":"", @@ -10033,7 +10101,7 @@ "uri":"admin_guide_000284.html", "node_id":"admin_guide_000284.xml", "product_code":"mrs", - "code":"541", + "code":"545", "des":"After a cluster is installed, Controller and Agent need to communicate with each other. The Kerberos authentication is used during the communication. By default, the comm", "doc_type":"usermanual", "kw":"Encrypting the Communication Between the Controller and the Agent,Security Hardening,User Guide", @@ -10051,7 +10119,7 @@ "uri":"admin_guide_000285.html", "node_id":"admin_guide_000285.xml", "product_code":"mrs", - "code":"542", + "code":"546", "des":"During cluster installation, the system automatically generate the SSH public key and private key for user omm to establish the trust relationship between nodes. After th", "doc_type":"usermanual", "kw":"Updating SSH Keys for User omm,Security Hardening,User Guide", @@ -10069,7 +10137,7 @@ "uri":"admin_guide_000287.html", "node_id":"admin_guide_000287.xml", "product_code":"mrs", - "code":"543", + "code":"547", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Maintenance", @@ -10087,8 +10155,8 @@ "uri":"admin_guide_000289.html", "node_id":"admin_guide_000289.xml", "product_code":"mrs", - "code":"544", - "des":"It is recommended that the administrator conduct routine checks on the accounts. The check covers the following items:Check whether the accounts of the OS, FusionInsight ", + "code":"548", + "des":"It is recommended that the administrator conduct routine checks on the accounts. The check covers the following items:Check whether the accounts of the OS, MRS Manager, a", "doc_type":"usermanual", "kw":"Account Maintenance Suggestions,Security Maintenance,User Guide", "search_title":"", @@ -10105,7 +10173,7 @@ "uri":"admin_guide_000290.html", "node_id":"admin_guide_000290.xml", "product_code":"mrs", - "code":"545", + "code":"549", "des":"User identity authentication is a must for accessing the application system. The complexity and validity period of user accounts and passwords must meet customers' securi", "doc_type":"usermanual", "kw":"Password Maintenance Suggestions,Security Maintenance,User Guide", @@ -10123,7 +10191,7 @@ "uri":"admin_guide_000291.html", "node_id":"admin_guide_000291.xml", "product_code":"mrs", - "code":"546", + "code":"550", "des":"Operation logs help discover exceptions such as illegal operations and login by unauthorized users. The system records important operations in logs. You can use operation", "doc_type":"usermanual", "kw":"Log Maintenance Suggestions,Security Maintenance,User Guide", @@ -10141,7 +10209,7 @@ "uri":"admin_guide_000315.html", "node_id":"admin_guide_000315.xml", "product_code":"mrs", - "code":"547", + "code":"551", "des":"MRS MRS cluster is a big data cluster that provides users with distributed data analysis and computing capabilities. The built-in JDK of MRS MRS is OpenJDK, which is used", "doc_type":"usermanual", "kw":"Security Statement,Security Management,User Guide", @@ -10159,7 +10227,7 @@ "uri":"mrs_01_1298.html", "node_id":"mrs_01_1298.xml", "product_code":"mrs", - "code":"548", + "code":"552", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarm Reference (Applicable to MRS 3.x)", @@ -10178,7 +10246,7 @@ "uri":"ALM-12001.html", "node_id":"alm-12001.xml", "product_code":"mrs", - "code":"549", + "code":"553", "des":"Cluster audit logs need to be dumped on a third-party server due to the local historical data backup policy. The system starts to check the dump server at 3 a.m. every da", "doc_type":"alarm", "kw":"ALM-12001 Audit Log Dumping Failure,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10196,7 +10264,7 @@ "uri":"ALM-12004.html", "node_id":"alm-12004.xml", "product_code":"mrs", - "code":"550", + "code":"554", "des":"The system checks LDAP resources every 60 seconds. This alarm is generated when the system detects that the LDAP resources in Manager are abnormal for six consecutive tim", "doc_type":"alarm", "kw":"ALM-12004 OLdap Resource Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10214,7 +10282,7 @@ "uri":"ALM-12005.html", "node_id":"alm-12005.xml", "product_code":"mrs", - "code":"551", + "code":"555", "des":"The alarm module checks the status of the Kerberos resource in Manager every 80 seconds. This alarm is generated when the alarm module detects that the Kerberos resources", "doc_type":"alarm", "kw":"ALM-12005 OKerberos Resource Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10232,7 +10300,7 @@ "uri":"ALM-12006.html", "node_id":"alm-12006.xml", "product_code":"mrs", - "code":"552", + "code":"556", "des":"Controller checks the NodeAgent heartbeat every 30 seconds. If Controller does not receive heartbeat messages from a NodeAgent, it attempts to restart the NodeAgent proce", "doc_type":"alarm", "kw":"ALM-12006 Node Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10250,7 +10318,7 @@ "uri":"ALM-12007.html", "node_id":"alm-12007.xml", "product_code":"mrs", - "code":"553", + "code":"557", "des":"This alarm is generated when the process health check module detects that the process connection status is Bad for three consecutive times. The process health check modul", "doc_type":"alarm", "kw":"ALM-12007 Process Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10268,7 +10336,7 @@ "uri":"ALM-12010.html", "node_id":"alm-12010.xml", "product_code":"mrs", - "code":"554", + "code":"558", "des":"This alarm is generated when the active Mager does not receive the heartbeat signal from the standby Manager within 7 seconds.This alarm is cleared when the active Manage", "doc_type":"alarm", "kw":"ALM-12010 Manager Heartbeat Interruption Between the Active and Standby Nodes,Alarm Reference (Appli", @@ -10286,7 +10354,7 @@ "uri":"ALM-12011.html", "node_id":"alm-12011.xml", "product_code":"mrs", - "code":"555", + "code":"559", "des":"The system checks data synchronization between the active and standby Manager nodes every 60 seconds. This alarm is generated when the standby Manager fails to synchroniz", "doc_type":"alarm", "kw":"ALM-12011 Manager Data Synchronization Exception Between the Active and Standby Nodes,Alarm Referenc", @@ -10304,7 +10372,7 @@ "uri":"ALM-12012.html", "node_id":"alm-12012.xml", "product_code":"mrs", - "code":"556", + "code":"560", "des":"The system checks whether the NTP service on a node synchronizes time with the NTP service on the active OMS node every 60 seconds. This alarm is generated when the NTP s", "doc_type":"alarm", "kw":"ALM-12012 NTP Service Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10322,7 +10390,7 @@ "uri":"ALM-12014.html", "node_id":"alm-12014.xml", "product_code":"mrs", - "code":"557", + "code":"561", "des":"The system checks the partition status every 60 seconds. This alarm is generated when the system detects that a partition to which service directories are mounted is lost", "doc_type":"alarm", "kw":"ALM-12014 Partition Lost,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10340,7 +10408,7 @@ "uri":"ALM-12015.html", "node_id":"alm-12015.xml", "product_code":"mrs", - "code":"558", + "code":"562", "des":"The system checks the partition status every 60 seconds. This alarm is generated when the system detects that a partition to which service directories are mounted enters ", "doc_type":"alarm", "kw":"ALM-12015 Partition Filesystem Readonly,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10358,7 +10426,7 @@ "uri":"ALM-12016.html", "node_id":"alm-12016.xml", "product_code":"mrs", - "code":"559", + "code":"563", "des":"The system checks the CPU usage every 30 seconds and compares the actual CPU usage with the threshold. The CPU usage has a default threshold. This alarm is generated when", "doc_type":"alarm", "kw":"ALM-12016 CPU Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10376,7 +10444,7 @@ "uri":"ALM-12017.html", "node_id":"alm-12017.xml", "product_code":"mrs", - "code":"560", + "code":"564", "des":"The system checks the host disk usage of the system every 30 seconds and compares the actual disk usage with the threshold. The disk usage has a default threshold, this a", "doc_type":"alarm", "kw":"ALM-12017 Insufficient Disk Capacity,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10394,7 +10462,7 @@ "uri":"ALM-12018.html", "node_id":"alm-12018.xml", "product_code":"mrs", - "code":"561", + "code":"565", "des":"The system checks the memory usage of the system every 30 seconds and compares the actual memory usage with the threshold. The memory usage has a default threshold, this ", "doc_type":"alarm", "kw":"ALM-12018 Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10412,7 +10480,7 @@ "uri":"ALM-12027.html", "node_id":"alm-12027.xml", "product_code":"mrs", - "code":"562", + "code":"566", "des":"The system checks the PID usage every 30 seconds and compares the actual PID usage with the default PID usage threshold. This alarm is generated when the system detects t", "doc_type":"alarm", "kw":"ALM-12027 Host PID Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10430,10 +10498,10 @@ "uri":"ALM-12028.html", "node_id":"alm-12028.xml", "product_code":"mrs", - "code":"563", + "code":"567", "des":"The system checks the number of processes in the D stateand Z state of user omm on the host every 30 seconds and compares the actual number with the threshold. The number", "doc_type":"alarm", - "kw":"ALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold,Alarm Refer", + "kw":"and Z StateALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold,", "search_title":"", "metedata":[ { @@ -10441,14 +10509,14 @@ "prodname":"mrs" } ], - "title":"ALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold", + "title":"and Z StateALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold", "githuburl":"" }, { "uri":"ALM-12033.html", "node_id":"alm-12033.xml", "product_code":"mrs", - "code":"564", + "code":"568", "des":"For HDDs, the alarm is triggered when any of the following conditions is met:The system runs the iostat command every 3 seconds, and detects that the svctm value exceeds ", "doc_type":"alarm", "kw":"ALM-12033 Slow Disk Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10466,7 +10534,7 @@ "uri":"ALM-12034.html", "node_id":"alm-12034.xml", "product_code":"mrs", - "code":"565", + "code":"569", "des":"The system executes the periodic backup task every 60 minutes. This alarm is generated when a periodical backup task fails to be executed. This alarm is cleared when the ", "doc_type":"alarm", "kw":"ALM-12034 Periodical Backup Failure,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10484,7 +10552,7 @@ "uri":"ALM-12035.html", "node_id":"alm-12035.xml", "product_code":"mrs", - "code":"566", + "code":"570", "des":"After the recovery task fails, the system automatically rolls back every 60 minutes. If the rollback fails, data may be lost. If this occurs, an alarm is reported. This a", "doc_type":"alarm", "kw":"ALM-12035 Unknown Data Status After Recovery Task Failure,Alarm Reference (Applicable to MRS 3.x),Us", @@ -10502,7 +10570,7 @@ "uri":"ALM-12037.html", "node_id":"alm-12037.xml", "product_code":"mrs", - "code":"567", + "code":"571", "des":"The system checks the NTP server status every 60 seconds. This alarm is generated when the system detects that the NTP server is abnormal for 10 consecutive times.This al", "doc_type":"alarm", "kw":"ALM-12037 NTP Server Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10520,8 +10588,8 @@ "uri":"ALM-12038.html", "node_id":"alm-12038.xml", "product_code":"mrs", - "code":"568", - "des":"After monitoring indicator dumping is configured on FusionInsight Manager, the system checks the monitoring indicator dumping result at the dumping interval (60 seconds b", + "code":"572", + "des":"After monitoring indicator dumping is configured on MRS Manager, the system checks the monitoring indicator dumping result at the dumping interval (60 seconds by default)", "doc_type":"alarm", "kw":"ALM-12038 Monitoring Indicator Dumping Failure,Alarm Reference (Applicable to MRS 3.x),User Guide", "search_title":"", @@ -10538,7 +10606,7 @@ "uri":"ALM-12039.html", "node_id":"alm-12039.xml", "product_code":"mrs", - "code":"569", + "code":"573", "des":"The system checks the data synchronization status between the active and standby OMS Databases every 10 seconds. This alarm is generated when the synchronization status c", "doc_type":"alarm", "kw":"ALM-12039 Active/Standby OMS Databases Not Synchronized,Alarm Reference (Applicable to MRS 3.x),User", @@ -10556,7 +10624,7 @@ "uri":"ALM-12040.html", "node_id":"alm-12040.xml", "product_code":"mrs", - "code":"570", + "code":"574", "des":"MRS 3.2.0-LTS.2 or later:The system checks whether the rng-tools or haveged tool has been enabled and correctly configured every 5 minutes. If neither tool is configured,", "doc_type":"alarm", "kw":"ALM-12040 Insufficient System Entropy,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10574,7 +10642,7 @@ "uri":"ALM-12041.html", "node_id":"alm-12041.xml", "product_code":"mrs", - "code":"571", + "code":"575", "des":"The system checks whether the permission, user, and user group information about critical directories or files is normal every 5 minutes. This alarm is generated when the", "doc_type":"alarm", "kw":"ALM-12041 Incorrect Permission on Key Files,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10592,7 +10660,7 @@ "uri":"ALM-12042.html", "node_id":"alm-12042.xml", "product_code":"mrs", - "code":"572", + "code":"576", "des":"The system checks whether critical configurations are correct every 5 minutes. This alarm is generated when the configurations are abnormal.This alarm is cleared when the", "doc_type":"alarm", "kw":"ALM-12042 Incorrect Configuration of Key Files,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10610,7 +10678,7 @@ "uri":"ALM-12045.html", "node_id":"alm-12045.xml", "product_code":"mrs", - "code":"573", + "code":"577", "des":"The system checks the read packet dropped rate every 30 seconds. This alarm is generated when the read packet dropped rate exceeds the threshold (the default threshold is", "doc_type":"alarm", "kw":"ALM-12045 Read Packet Dropped Rate Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -10628,7 +10696,7 @@ "uri":"ALM-12046.html", "node_id":"alm-12046.xml", "product_code":"mrs", - "code":"574", + "code":"578", "des":"The system checks the write packet dropped rate every 30 seconds. This alarm is generated when the write packet dropped rate exceeds the threshold (the default threshold ", "doc_type":"alarm", "kw":"ALM-12046 Write Packet Dropped Rate Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Us", @@ -10646,7 +10714,7 @@ "uri":"ALM-12047.html", "node_id":"alm-12047.xml", "product_code":"mrs", - "code":"575", + "code":"579", "des":"The system checks the read packet error rate every 30 seconds. This alarm is generated when the read packet error rate exceeds the threshold (the default threshold is 0.5", "doc_type":"alarm", "kw":"ALM-12047 Read Packet Error Rate Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User ", @@ -10664,7 +10732,7 @@ "uri":"ALM-12048.html", "node_id":"alm-12048.xml", "product_code":"mrs", - "code":"576", + "code":"580", "des":"The system checks the write packet error rate every 30 seconds. This alarm is generated when the write packet error rate exceeds the threshold (the default threshold is 0", "doc_type":"alarm", "kw":"ALM-12048 Write Packet Error Rate Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -10682,7 +10750,7 @@ "uri":"ALM-12049.html", "node_id":"alm-12049.xml", "product_code":"mrs", - "code":"577", + "code":"581", "des":"The system checks the network read throughput rate every 30 seconds and compares the actual throughput rate with the threshold (the default threshold is 80%). This alarm ", "doc_type":"alarm", "kw":"ALM-12049 Network Read Throughput Rate Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -10700,7 +10768,7 @@ "uri":"ALM-12050.html", "node_id":"alm-12050.xml", "product_code":"mrs", - "code":"578", + "code":"582", "des":"The system checks the network write throughput rate every 30 seconds and compares the actual throughput rate with the threshold (the default threshold is 80%). This alarm", "doc_type":"alarm", "kw":"ALM-12050 Network Write Throughput Rate Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -10718,7 +10786,7 @@ "uri":"ALM-12051.html", "node_id":"alm-12051.xml", "product_code":"mrs", - "code":"579", + "code":"583", "des":"The system checks the disk Inode usage every 30 seconds and compares the actual Inode usage with the threshold (the default threshold is 80%). This alarm is generated whe", "doc_type":"alarm", "kw":"ALM-12051 Disk Inode Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10736,7 +10804,7 @@ "uri":"ALM-12052.html", "node_id":"alm-12052.xml", "product_code":"mrs", - "code":"580", + "code":"584", "des":"The system checks the TCP temporary port usage every 30 seconds and compares the actual usage with the threshold (the default threshold is 80%). This alarm is generated w", "doc_type":"alarm", "kw":"ALM-12052 TCP Temporary Port Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -10754,7 +10822,7 @@ "uri":"ALM-12053.html", "node_id":"alm-12053.xml", "product_code":"mrs", - "code":"581", + "code":"585", "des":"The system checks the file handle usage every 30 seconds and compares the actual usage with the threshold (the default threshold is 80%). This alarm is generated when the", "doc_type":"alarm", "kw":"ALM-12053 Host File Handle Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User ", @@ -10772,7 +10840,7 @@ "uri":"ALM-12054.html", "node_id":"alm-12054.xml", "product_code":"mrs", - "code":"582", + "code":"586", "des":"The system checks whether the certificate file is invalid (has expired or is not valid yet) on 23:00 every day. This alarm is generated when the certificate file is inval", "doc_type":"alarm", "kw":"ALM-12054 Invalid Certificate File,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10790,7 +10858,7 @@ "uri":"ALM-12055.html", "node_id":"alm-12055.xml", "product_code":"mrs", - "code":"583", + "code":"587", "des":"The system checks the certificate file on 23:00 every day. This alarm is generated if the certificate file is about to expire within 30 days.This alarm is cleared when a ", "doc_type":"alarm", "kw":"ALM-12055 The Certificate File Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10808,7 +10876,7 @@ "uri":"ALM-12057.html", "node_id":"alm-12057.xml", "product_code":"mrs", - "code":"584", + "code":"588", "des":"After the system is installed, it checks whether the task for periodically backing up metadata to the third-party server, and then performs the check hourly. If the task ", "doc_type":"alarm", "kw":"ALM-12057 Metadata Not Configured with the Task to Periodically Back Up Data to a Third-Party Server", @@ -10826,7 +10894,7 @@ "uri":"ALM-12061.html", "node_id":"alm-12061.xml", "product_code":"mrs", - "code":"585", + "code":"589", "des":"The system checks the usage of the omm process every 30 seconds. Users can run the ps -o nlwp, pid, args, -u omm | awk '{sum+=$1} END {print \"\", sum}' command to obtain t", "doc_type":"alarm", "kw":"ALM-12061 Process Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10844,7 +10912,7 @@ "uri":"ALM-12062.html", "node_id":"alm-12062.xml", "product_code":"mrs", - "code":"586", + "code":"590", "des":"The system checks whether the OMS parameter configurations match with the cluster scale at each top hour. If the OMS parameter configurations do not meet the cluster scal", "doc_type":"alarm", "kw":"ALM-12062 OMS Parameter Configurations Mismatch with the Cluster Scale,Alarm Reference (Applicable t", @@ -10862,7 +10930,7 @@ "uri":"ALM-12063.html", "node_id":"alm-12063.xml", "product_code":"mrs", - "code":"587", + "code":"591", "des":"The system checks whether the data disk of the current host is available at the top of each hour. The system creates files, writes files, and deletes files in the mount d", "doc_type":"alarm", "kw":"ALM-12063 Unavailable Disk,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10880,7 +10948,7 @@ "uri":"ALM-12064.html", "node_id":"alm-12064.xml", "product_code":"mrs", - "code":"588", + "code":"592", "des":"The system checks whether the random port range of the host conflicts with the range of ports used by the Cluster system every hour. The alarm is generated if they confli", "doc_type":"alarm", "kw":"ALM-12064 Host Random Port Range Conflicts with Cluster Used Port,Alarm Reference (Applicable to MRS", @@ -10898,7 +10966,7 @@ "uri":"ALM-12066.html", "node_id":"alm-12066.xml", "product_code":"mrs", - "code":"589", + "code":"593", "des":"The system checks whether the trust relationship between the active OMS node and other Agent nodes is normal every hour. The alarm is generated if the mutual trust fails.", "doc_type":"alarm", "kw":"ALM-12066 Trust Relationships Between Nodes Become Invalid,Alarm Reference (Applicable to MRS 3.x),U", @@ -10916,7 +10984,7 @@ "uri":"ALM-12067.html", "node_id":"alm-12067.xml", "product_code":"mrs", - "code":"590", + "code":"594", "des":"HA checks the Tomcat resources of Manager every 85 seconds. This alarm is generated when HA detects that the Tomcat resources are abnormal for two consecutive times.This ", "doc_type":"alarm", "kw":"ALM-12067 Tomcat Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10934,7 +11002,7 @@ "uri":"ALM-12068.html", "node_id":"alm-12068.xml", "product_code":"mrs", - "code":"591", + "code":"595", "des":"HA checks the ACS resources of Manager every 80 seconds. This alarm is generated when HA detects that the ACS resources are abnormal for two consecutive times.This alarm ", "doc_type":"alarm", "kw":"ALM-12068 ACS Resource Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10952,7 +11020,7 @@ "uri":"ALM-12069.html", "node_id":"alm-12069.xml", "product_code":"mrs", - "code":"592", + "code":"596", "des":"HA checks the AOS resources of Manager every 81 seconds. This alarm is generated when HA detects that the AOS resources are abnormal for two consecutive times.This alarm ", "doc_type":"alarm", "kw":"ALM-12069 AOS Resource Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10970,7 +11038,7 @@ "uri":"ALM-12070.html", "node_id":"alm-12070.xml", "product_code":"mrs", - "code":"593", + "code":"597", "des":"HA checks the controller resources of Manager every 80 seconds. This alarm is generated when HA detects that the controller resources are abnormal for 2 consecutive times", "doc_type":"alarm", "kw":"ALM-12070 Controller Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -10988,7 +11056,7 @@ "uri":"ALM-12071.html", "node_id":"alm-12071.xml", "product_code":"mrs", - "code":"594", + "code":"598", "des":"HA checks the httpd resources of Manager every 120 seconds. This alarm is generated when HA detects that the httpd resources are abnormal for 10 consecutive times.This al", "doc_type":"alarm", "kw":"ALM-12071 Httpd Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11006,7 +11074,7 @@ "uri":"ALM-12072.html", "node_id":"alm-12072.xml", "product_code":"mrs", - "code":"595", + "code":"599", "des":"HA checks the floatip resources of Manager every 9 seconds. This alarm is generated when HA detects that the floatip resources are abnormal for 3 consecutive times.This a", "doc_type":"alarm", "kw":"ALM-12072 FloatIP Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11024,7 +11092,7 @@ "uri":"ALM-12073.html", "node_id":"alm-12073.xml", "product_code":"mrs", - "code":"596", + "code":"600", "des":"HA checks the cep resources of Manager every 60 seconds. This alarm is generated when HA detects that the cep resources are abnormal for 2 consecutive times.This alarm is", "doc_type":"alarm", "kw":"ALM-12073 CEP Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11042,7 +11110,7 @@ "uri":"ALM-12074.html", "node_id":"alm-12074.xml", "product_code":"mrs", - "code":"597", + "code":"601", "des":"HA checks the fms resources of Manager every 60 seconds. This alarm is generated when HA detects that the fms resources are abnormal for 2 consecutive times.This alarm is", "doc_type":"alarm", "kw":"ALM-12074 FMS Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11060,7 +11128,7 @@ "uri":"ALM-12075.html", "node_id":"alm-12075.xml", "product_code":"mrs", - "code":"598", + "code":"602", "des":"HA checks the pms resources of Manager every 55 seconds. This alarm is generated when HA detects that the pms resources are abnormal for three consecutive times.This alar", "doc_type":"alarm", "kw":"ALM-12075 PMS Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11078,7 +11146,7 @@ "uri":"ALM-12076.html", "node_id":"alm-12076.xml", "product_code":"mrs", - "code":"599", + "code":"603", "des":"HA checks the Manager database every 10 seconds. This alarm is generated when HA detects that the database is abnormal for 3 consecutive times.This alarm is cleared when ", "doc_type":"alarm", "kw":"ALM-12076 GaussDB Resource Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11096,7 +11164,7 @@ "uri":"ALM-12077.html", "node_id":"alm-12077.xml", "product_code":"mrs", - "code":"600", + "code":"604", "des":"The system starts at 00:00 every day to check whether user omm has expired every eight hours. This alarm is generated if the user account has expired.This alarm is cleare", "doc_type":"alarm", "kw":"ALM-12077 User omm Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11114,7 +11182,7 @@ "uri":"ALM-12078.html", "node_id":"alm-12078.xml", "product_code":"mrs", - "code":"601", + "code":"605", "des":"The system starts at 00:00 every day to check whether the password of user omm has expired every 8 hours. This alarm is generated if the password has expired.This alarm i", "doc_type":"alarm", "kw":"ALM-12078 Password of User omm Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11132,7 +11200,7 @@ "uri":"ALM-12079.html", "node_id":"alm-12079.xml", "product_code":"mrs", - "code":"602", + "code":"606", "des":"The system starts at 00:00 every day to check whether user omm is about to expire every 8 hours. This alarm is generated if the user account will expire no less than 15 d", "doc_type":"alarm", "kw":"ALM-12079 User omm Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11150,7 +11218,7 @@ "uri":"ALM-12080.html", "node_id":"alm-12080.xml", "product_code":"mrs", - "code":"603", + "code":"607", "des":"The system starts at 00:00 every day to check whether the password of user omm is about to expire every 8 hours. This alarm is generated if the password will expire no le", "doc_type":"alarm", "kw":"ALM-12080 Password of User omm Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11168,10 +11236,10 @@ "uri":"ALM-12081.html", "node_id":"alm-12081.xml", "product_code":"mrs", - "code":"604", + "code":"608", "des":"The system starts at 00:00 every day to check whether user ommdba has expired every 8 hours. This alarm is generated if the user account has expired.This alarm is cleared", "doc_type":"alarm", - "kw":"ALM-12081User ommdba Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", + "kw":"ALM-12081 User ommdba Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", "search_title":"", "metedata":[ { @@ -11179,14 +11247,14 @@ "prodname":"mrs" } ], - "title":"ALM-12081User ommdba Expired", + "title":"ALM-12081 User ommdba Expired", "githuburl":"" }, { "uri":"ALM-12082.html", "node_id":"alm-12082.xml", "product_code":"mrs", - "code":"605", + "code":"609", "des":"The system starts at 00:00 every day to check whether user ommdba is about to expire every 8 hours. This alarm is generated if the user account will expire no less than 1", "doc_type":"alarm", "kw":"ALM-12082 User ommdba Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11204,7 +11272,7 @@ "uri":"ALM-12083.html", "node_id":"alm-12083.xml", "product_code":"mrs", - "code":"606", + "code":"610", "des":"The system starts at 00:00 every day to check whether the password of user ommdba is about to expire every 8 hours. This alarm is generated if the password is about to ex", "doc_type":"alarm", "kw":"ALM-12083 Password of User ommdba Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Gu", @@ -11222,7 +11290,7 @@ "uri":"ALM-12084.html", "node_id":"alm-12084.xml", "product_code":"mrs", - "code":"607", + "code":"611", "des":"The system starts at 00:00 every day to check whether the password of user ommdba has expired every 8 hours. This alarm is generated if the password has expired.This alar", "doc_type":"alarm", "kw":"ALM-12084 Password of User ommdba Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11240,7 +11308,7 @@ "uri":"ALM-12085.html", "node_id":"alm-12085.xml", "product_code":"mrs", - "code":"608", + "code":"612", "des":"The system dumps service audit logs at 03:00 every day and stores them on the OMS node. This alarm is generated when the dump fails. This alarm is cleared when the next d", "doc_type":"alarm", "kw":"ALM-12085 Service Audit Log Dump Failure,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11258,7 +11326,7 @@ "uri":"ALM-12087.html", "node_id":"alm-12087.xml", "product_code":"mrs", - "code":"609", + "code":"613", "des":"The system checks whether it is in the upgrade observation period at 00:00 every day and checks whether the duration that it has been in the upgrade observation state exc", "doc_type":"alarm", "kw":"ALM-12087 System Is in the Upgrade Observation Period,Alarm Reference (Applicable to MRS 3.x),User G", @@ -11276,7 +11344,7 @@ "uri":"ALM-12089.html", "node_id":"alm-12089.xml", "product_code":"mrs", - "code":"610", + "code":"614", "des":"The alarm module checks the network health status of nodes in the cluster every 10 seconds. This alarm is generated when the network between two nodes is unreachable or t", "doc_type":"alarm", "kw":"ALM-12089 Inter-Node Network Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11294,7 +11362,7 @@ "uri":"ALM-12101.html", "node_id":"alm-12101.xml", "product_code":"mrs", - "code":"611", + "code":"615", "des":"After the AZ DR function is enabled, the system checks the AZ health status every 5 minutes. This alarm is generated when the system detects that the AZ is subhealthy or ", "doc_type":"alarm", "kw":"ALM-12101 AZ Unhealthy,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11312,7 +11380,7 @@ "uri":"ALM-12102.html", "node_id":"alm-12102.xml", "product_code":"mrs", - "code":"612", + "code":"616", "des":"The alarm module checks the deployment status of AZ HA components every 5 minutes. This alarm is generated when the components that support DR are not deployed based on D", "doc_type":"alarm", "kw":"ALM-12102 AZ HA Component Is Not Deployed Based on DR Requirements,Alarm Reference (Applicable to MR", @@ -11330,7 +11398,7 @@ "uri":"ALM-12103.html", "node_id":"alm-12103.xml", "product_code":"mrs", - "code":"613", + "code":"617", "des":"HA checks the Executor resources of Manager every 30 seconds. This alarm is generated when HA detects that the Executor resources are abnormal for two consecutive times.T", "doc_type":"alarm", "kw":"ALM-12103 Executor Resource Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11348,7 +11416,7 @@ "uri":"ALM-12104.html", "node_id":"alm-12104.xml", "product_code":"mrs", - "code":"614", + "code":"618", "des":"HA checks the Knox resources of Manager every 70 seconds. This alarm is generated when HA detects that the Knox resources are abnormal for three consecutive times.This al", "doc_type":"alarm", "kw":"ALM-12104 Abnormal Knox Resources,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11366,7 +11434,7 @@ "uri":"ALM-12110.html", "node_id":"alm-12110.xml", "product_code":"mrs", - "code":"615", + "code":"619", "des":"The meta service periodically obtains the temporary AK/SK of the ECS. This alarm is generated when the meta service fails to obtain the temporary AK/SK.In storage-compute", "doc_type":"alarm", "kw":"ALM-12110 Failed to get ECS temporary AK/SK,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11384,7 +11452,7 @@ "uri":"ALM-12172.html", "node_id":"alm-12172.xml", "product_code":"mrs", - "code":"616", + "code":"620", "des":"After metric sharing is enabled for a cluster, the Controller periodically collects cluster metrics and reports them to Cloud Eye.MRS monitoring metrics are unavailable o", "doc_type":"usermanual", "kw":"ALM-12172 Failed to Report Metrics to Cloud Eye,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11402,7 +11470,7 @@ "uri":"ALM-12180.html", "node_id":"alm-12180.xml", "product_code":"mrs", - "code":"617", + "code":"621", "des":"For HDDs, the alarm is triggered when any of the following conditions is met:The system collects data every 3 seconds, and detects that the svctm value exceeds 6s for 10 ", "doc_type":"usermanual", "kw":"ALM-12180 Suspended Disk I/O,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11420,7 +11488,7 @@ "uri":"ALM-12190.html", "node_id":"alm-12190.xml", "product_code":"mrs", - "code":"618", + "code":"622", "des":"The system periodically checks the number of connections to all Knox topologies. This alarm is generated when the number of connections to a topology exceeds the threshol", "doc_type":"usermanual", "kw":"ALM-12190 Number of Knox Connections Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -11438,7 +11506,7 @@ "uri":"ALM-13000.html", "node_id":"alm-13000.xml", "product_code":"mrs", - "code":"619", + "code":"623", "des":"The system checks the ZooKeeper service status every 60 seconds. This alarm is generated when the ZooKeeper service is unavailable.This alarm is cleared when the ZooKeepe", "doc_type":"alarm", "kw":"ALM-13000 ZooKeeper Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11456,7 +11524,7 @@ "uri":"ALM-13001.html", "node_id":"alm-13001.xml", "product_code":"mrs", - "code":"620", + "code":"624", "des":"The system checks ZooKeeper connections every 60 seconds. This alarm is generated when the system detects that the number of used ZooKeeper instance connections exceeds t", "doc_type":"alarm", "kw":"ALM-13001 Available ZooKeeper Connections Are Insufficient,Alarm Reference (Applicable to MRS 3.x),U", @@ -11474,7 +11542,7 @@ "uri":"ALM-13002.html", "node_id":"alm-13002.xml", "product_code":"mrs", - "code":"621", + "code":"625", "des":"The system checks the direct memory usage of the ZooKeeper service every 30 seconds. The alarm is generated when the direct memory usage of a ZooKeeper instance exceeds t", "doc_type":"alarm", "kw":"ALM-13002 ZooKeeper Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -11492,7 +11560,7 @@ "uri":"ALM-13003.html", "node_id":"alm-13003.xml", "product_code":"mrs", - "code":"622", + "code":"626", "des":"The system checks the garbage collection (GC) duration of the ZooKeeper process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 s", "doc_type":"alarm", "kw":"ALM-13003 GC Duration of the ZooKeeper Process Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -11510,7 +11578,7 @@ "uri":"ALM-13004.html", "node_id":"alm-13004.xml", "product_code":"mrs", - "code":"623", + "code":"627", "des":"The system checks the heap memory usage of the ZooKeeper service every 60 seconds. The alarm is generated when the heap memory usage of a ZooKeeper instance exceeds the t", "doc_type":"alarm", "kw":"ALM-13004 ZooKeeper Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", @@ -11528,7 +11596,7 @@ "uri":"ALM-13005.html", "node_id":"alm-13005.xml", "product_code":"mrs", - "code":"624", + "code":"628", "des":"The system sets quotas for each ZooKeeper top-level directory in the customized.quota configuration item and components every 5 hours. This alarm is generated when the sy", "doc_type":"alarm", "kw":"ALM-13005 Failed to Set the Quota of Top Directories of ZooKeeper Components,Alarm Reference (Applic", @@ -11546,7 +11614,7 @@ "uri":"ALM-13006.html", "node_id":"alm-13006.xml", "product_code":"mrs", - "code":"625", + "code":"629", "des":"The system periodically detects the status of secondary Znode in the ZooKeeper service data directory every four hours. This alarm is generated when the number or capacit", "doc_type":"alarm", "kw":"ALM-13006 Znode Number or Capacity Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -11564,7 +11632,7 @@ "uri":"ALM-13007.html", "node_id":"alm-13007.xml", "product_code":"mrs", - "code":"626", + "code":"630", "des":"The system periodically detects the number of active processes between the ZooKeeper client and the ZooKeeper server every 60 seconds. This alarm is generated when the nu", "doc_type":"alarm", "kw":"ALM-13007 Available ZooKeeper Client Connections Are Insufficient,Alarm Reference (Applicable to MRS", @@ -11582,7 +11650,7 @@ "uri":"ALM-13008.html", "node_id":"alm-13008.xml", "product_code":"mrs", - "code":"627", + "code":"631", "des":"The system checks the level-2 Znode status in the ZooKeeper data directory every hour. This alarm is generated when the system detects that the level-2 Znode usage exceed", "doc_type":"alarm", "kw":"ALM-13008 ZooKeeper Znode Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User G", @@ -11600,7 +11668,7 @@ "uri":"ALM-13009.html", "node_id":"alm-13009.xml", "product_code":"mrs", - "code":"628", + "code":"632", "des":"The system checks the level-2 ZNode status in the ZooKeeper data directory every hour. This alarm is generated when the system detects that the capacity usage exceeds the", "doc_type":"alarm", "kw":"ALM-13009 ZooKeeper Znode Capacity Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.", @@ -11618,7 +11686,7 @@ "uri":"ALM-13010.html", "node_id":"alm-13010.xml", "product_code":"mrs", - "code":"629", + "code":"633", "des":"The system checks the Znode usage of all service directories with quota configured every hour. This alarm is generated when the system detects that the level-2 Znode usag", "doc_type":"alarm", "kw":"ALM-13010 Znode Usage of a Directory with Quota Configured Exceeds the Threshold,Alarm Reference (Ap", @@ -11636,7 +11704,7 @@ "uri":"ALM-14000.html", "node_id":"alm-14000.xml", "product_code":"mrs", - "code":"630", + "code":"634", "des":"The system checks the NameService service status every 60 seconds. This alarm is generated when all the NameService services are abnormal and the system considers that th", "doc_type":"alarm", "kw":"ALM-14000 HDFS Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11654,7 +11722,7 @@ "uri":"ALM-14001.html", "node_id":"alm-14001.xml", "product_code":"mrs", - "code":"631", + "code":"635", "des":"The system checks the HDFS disk usage every 30 seconds and compares the actual HDFS disk usage with the threshold. The HDFS disk usage indicator has a default threshold, ", "doc_type":"alarm", "kw":"ALM-14001 HDFS Disk Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11672,7 +11740,7 @@ "uri":"ALM-14002.html", "node_id":"alm-14002.xml", "product_code":"mrs", - "code":"632", + "code":"636", "des":"The system checks the DataNode disk usage every 30 seconds and compares the actual disk usage with the threshold. A default threshold range is provided for the DataNode d", "doc_type":"alarm", "kw":"ALM-14002 DataNode Disk Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Gui", @@ -11690,7 +11758,7 @@ "uri":"ALM-14003.html", "node_id":"alm-14003.xml", "product_code":"mrs", - "code":"633", + "code":"637", "des":"The system checks the lost blocks every 30 seconds and compares the actual lost blocks with the threshold. The lost blocks indicator has a default threshold. This alarm i", "doc_type":"alarm", "kw":"ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -11708,7 +11776,7 @@ "uri":"ALM-14006.html", "node_id":"alm-14006.xml", "product_code":"mrs", - "code":"634", + "code":"638", "des":"The system periodically checks the number of HDFS files every 30 seconds and compares the number of HDFS files with the threshold. This alarm is generated when the system", "doc_type":"alarm", "kw":"ALM-14006 Number of HDFS Files Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Gu", @@ -11726,7 +11794,7 @@ "uri":"ALM-14007.html", "node_id":"alm-14007.xml", "product_code":"mrs", - "code":"635", + "code":"639", "des":"The system checks the HDFS NameNode Heap Memory usage every 30 seconds and compares the actual Heap memory usage with the threshold. The HDFS NameNode Heap Memory usage h", "doc_type":"alarm", "kw":"ALM-14007 NameNode Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -11744,7 +11812,7 @@ "uri":"ALM-14008.html", "node_id":"alm-14008.xml", "product_code":"mrs", - "code":"636", + "code":"640", "des":"The system checks the HDFS DataNode Heap Memory usage every 30 seconds and compares the actual Heap Memory usage with the threshold. The HDFS DataNode Heap Memory usage h", "doc_type":"alarm", "kw":"ALM-14008 DataNode Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -11762,7 +11830,7 @@ "uri":"ALM-14009.html", "node_id":"alm-14009.xml", "product_code":"mrs", - "code":"637", + "code":"641", "des":"The system periodically detects the number of dead DataNodes in the HDFS cluster every 30 seconds, and compares the number with the threshold. The number of DataNodes in ", "doc_type":"alarm", "kw":"ALM-14009 Number of Dead DataNodes Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -11780,7 +11848,7 @@ "uri":"ALM-14010.html", "node_id":"alm-14010.xml", "product_code":"mrs", - "code":"638", + "code":"642", "des":"The system checks the NameService service status every 180 seconds. This alarm is generated when the NameService service is unavailable.This alarm is cleared when the Nam", "doc_type":"alarm", "kw":"ALM-14010 NameService Service Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11798,7 +11866,7 @@ "uri":"ALM-14011.html", "node_id":"alm-14011.xml", "product_code":"mrs", - "code":"639", + "code":"643", "des":"The DataNode parameter dfs.datanode.data.dir specifies DataNode data directories. This alarm is generated when a configured data directory cannot be created, a data direc", "doc_type":"alarm", "kw":"ALM-14011 DataNode Data Directory Is Not Configured Properly,Alarm Reference (Applicable to MRS 3.x)", @@ -11816,7 +11884,7 @@ "uri":"ALM-14012.html", "node_id":"alm-14012.xml", "product_code":"mrs", - "code":"640", + "code":"644", "des":"On the active NameNode, the system checks the data consistency of all JournalNodes in the cluster every 5 minutes. This alarm is generated when the data on a JournalNode ", "doc_type":"alarm", "kw":"ALM-14012 JournalNode Is Out of Synchronization,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11834,7 +11902,7 @@ "uri":"ALM-14013.html", "node_id":"alm-14013.xml", "product_code":"mrs", - "code":"641", + "code":"645", "des":"HDFS metadata is stored in the FsImage file of the NameNode data directory, which is specified by the dfs.namenode.name.dir configuration item. The standby NameNode perio", "doc_type":"alarm", "kw":"ALM-14013 Failed to Update the NameNode FsImage File,Alarm Reference (Applicable to MRS 3.x),User Gu", @@ -11852,7 +11920,7 @@ "uri":"ALM-14014.html", "node_id":"alm-14014.xml", "product_code":"mrs", - "code":"642", + "code":"646", "des":"The system checks the garbage collection (GC) duration of the NameNode process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 se", "doc_type":"alarm", "kw":"ALM-14014 NameNode GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11870,7 +11938,7 @@ "uri":"ALM-14015.html", "node_id":"alm-14015.xml", "product_code":"mrs", - "code":"643", + "code":"647", "des":"The system checks the garbage collection (GC) duration of the DataNode process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 se", "doc_type":"alarm", "kw":"ALM-14015 DataNode GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11888,7 +11956,7 @@ "uri":"ALM-14016.html", "node_id":"alm-14016.xml", "product_code":"mrs", - "code":"644", + "code":"648", "des":"The system checks the direct memory usage of HDFS every 30 seconds. This alarm is generated when the direct memory usage of DataNode instances exceeds the threshold (90% ", "doc_type":"alarm", "kw":"ALM-14016 DataNode Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -11906,7 +11974,7 @@ "uri":"ALM-14017.html", "node_id":"alm-14017.xml", "product_code":"mrs", - "code":"645", + "code":"649", "des":"The system checks the direct memory usage of the HDFS service every 30 seconds. This alarm is generated when the direct memory usage of a NameNode instance exceeds the th", "doc_type":"alarm", "kw":"ALM-14017 NameNode Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -11924,7 +11992,7 @@ "uri":"ALM-14018.html", "node_id":"alm-14018.xml", "product_code":"mrs", - "code":"646", + "code":"650", "des":"The system checks the non-heap memory usage of the HDFS NameNode every 30 seconds and compares the actual usage with the threshold. The non-heap memory usage of the HDFS ", "doc_type":"alarm", "kw":"ALM-14018 NameNode Non-heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.", @@ -11942,7 +12010,7 @@ "uri":"ALM-14019.html", "node_id":"alm-14019.xml", "product_code":"mrs", - "code":"647", + "code":"651", "des":"The system checks the non-heap memory usage of the HDFS DataNode every 30 seconds and compares the actual usage with the threshold. The non-heap memory usage of the HDFS ", "doc_type":"alarm", "kw":"ALM-14019 DataNode Non-heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.", @@ -11960,7 +12028,7 @@ "uri":"ALM-14020.html", "node_id":"alm-14020.xml", "product_code":"mrs", - "code":"648", + "code":"652", "des":"The system obtains the number of subfiles and subdirectories in a specified directory every hour and checks whether it reaches the percentage of the threshold (the maximu", "doc_type":"alarm", "kw":"ALM-14020 Number of Entries in the HDFS Directory Exceeds the Threshold,Alarm Reference (Applicable ", @@ -11978,7 +12046,7 @@ "uri":"ALM-14021.html", "node_id":"alm-14021.xml", "product_code":"mrs", - "code":"649", + "code":"653", "des":"The system checks the average RPC processing time of NameNode every 30 seconds, and compares the actual average RPC processing time with the threshold (default value: 100", "doc_type":"alarm", "kw":"ALM-14021 NameNode Average RPC Processing Time Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -11996,7 +12064,7 @@ "uri":"ALM-14022.html", "node_id":"alm-14022.xml", "product_code":"mrs", - "code":"650", + "code":"654", "des":"The system checks the average RPC queuing time of NameNode every 30 seconds, and compares the actual average RPC queuing time with the threshold (default value: 200 ms). ", "doc_type":"alarm", "kw":"ALM-14022 NameNode Average RPC Queuing Time Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -12014,7 +12082,7 @@ "uri":"ALM-14023.html", "node_id":"alm-14023.xml", "product_code":"mrs", - "code":"651", + "code":"655", "des":"The system checks the percentage of total reserved disk space for replicas (Total reserved disk space for replicas/(Total reserved disk space for replicas + Total remaini", "doc_type":"alarm", "kw":"ALM-14023 Percentage of Total Reserved Disk Space for Replicas Exceeds the Threshold,Alarm Reference", @@ -12032,7 +12100,7 @@ "uri":"ALM-14024.html", "node_id":"alm-14024.xml", "product_code":"mrs", - "code":"652", + "code":"656", "des":"The system checks the space usage (used space of each directory/space allocated to each directory) of each directory associated with a tenant every hour and compares the ", "doc_type":"alarm", "kw":"ALM-14024 Tenant Space Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -12050,7 +12118,7 @@ "uri":"ALM-14025.html", "node_id":"alm-14025.xml", "product_code":"mrs", - "code":"653", + "code":"657", "des":"The system checks the file object usage (used file objects of each directory/number of file objects allocated to each directory) of each directory associated with a tenan", "doc_type":"alarm", "kw":"ALM-14025 Tenant File Object Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -12068,7 +12136,7 @@ "uri":"ALM-14026.html", "node_id":"alm-14026.xml", "product_code":"mrs", - "code":"654", + "code":"658", "des":"The system checks the number of blocks on each DataNode every 30 seconds. This alarm is generated when the number of blocks on the DataNode exceeds the threshold.If Trigg", "doc_type":"alarm", "kw":"ALM-14026 Blocks on DataNode Exceed the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12086,7 +12154,7 @@ "uri":"ALM-14027.html", "node_id":"alm-14027.xml", "product_code":"mrs", - "code":"655", + "code":"659", "des":"The system checks the disk status on DataNodes every 60 seconds. This alarm is generated when a disk is faulty.After all faulty disks on the DataNode are recovered, you n", "doc_type":"alarm", "kw":"ALM-14027 DataNode Disk Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12104,7 +12172,7 @@ "uri":"ALM-14028.html", "node_id":"alm-14028.xml", "product_code":"mrs", - "code":"656", + "code":"660", "des":"The system checks the number of blocks to be supplemented every 30 seconds and compares the number with the threshold. The number of blocks to be supplemented has a defau", "doc_type":"alarm", "kw":"ALM-14028 Number of Blocks to Be Supplemented Exceeds the Threshold,Alarm Reference (Applicable to M", @@ -12122,7 +12190,7 @@ "uri":"ALM-14029.html", "node_id":"alm-14029.xml", "product_code":"mrs", - "code":"657", + "code":"661", "des":"The system checks the number of blocks in a single replica every four hours and compares the number with the threshold. There is a threshold for the number of blocks in a", "doc_type":"alarm", "kw":"ALM-14029 Number of Blocks in a Replica Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -12140,7 +12208,7 @@ "uri":"ALM-14030.html", "node_id":"alm-14030.xml", "product_code":"mrs", - "code":"658", + "code":"662", "des":"This alarm is generated when dfs.single.replication.enable is set to true, indicating that HDFS is configured to allow write of single-replica data.This alarm is cleared ", "doc_type":"usermanual", "kw":"ALM-14030 HDFS Allows Write of Single-Replica Data,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -12158,7 +12226,7 @@ "uri":"ALM-16000.html", "node_id":"alm-16000.xml", "product_code":"mrs", - "code":"659", + "code":"663", "des":"The system detects the percentage of sessions connected to the HiveServer to the maximum number of allowed sessions every 30 seconds. This indicator can be viewed on the ", "doc_type":"alarm", "kw":"ALM-16000 Percentage of Sessions Connected to the HiveServer to Maximum Number Allowed Exceeds the T", @@ -12176,7 +12244,7 @@ "uri":"ALM-16001.html", "node_id":"alm-16001.xml", "product_code":"mrs", - "code":"660", + "code":"664", "des":"This alarm is generated when the Hive warehouse space usage exceeds the specified threshold (85% by default). The system checks the Hive data warehouse space usage every ", "doc_type":"alarm", "kw":"ALM-16001 Hive Warehouse Space Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -12194,7 +12262,7 @@ "uri":"ALM-16002.html", "node_id":"alm-16002.xml", "product_code":"mrs", - "code":"661", + "code":"665", "des":"The system checks the percentage of the HQL statements that are executed successfully in every 30 seconds. The formula is: Percentage of HQL statements that are executed ", "doc_type":"alarm", "kw":"ALM-16002 Hive SQL Execution Success Rate Is Lower Than the Threshold,Alarm Reference (Applicable to", @@ -12212,7 +12280,7 @@ "uri":"ALM-16003.html", "node_id":"alm-16003.xml", "product_code":"mrs", - "code":"662", + "code":"666", "des":"The system checks the background thread usage in every 30 seconds. This alarm is generated when the usage of the background thread pool of Hive exceeds the threshold, 90%", "doc_type":"alarm", "kw":"ALM-16003 Background Thread Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -12230,7 +12298,7 @@ "uri":"ALM-16004.html", "node_id":"alm-16004.xml", "product_code":"mrs", - "code":"663", + "code":"667", "des":"This alarm is generated when the HiveServer service is unavailable. The system checks the HiveServer service status every 60 seconds.This alarm is cleared when the HiveSe", "doc_type":"alarm", "kw":"ALM-16004 Hive Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12248,7 +12316,7 @@ "uri":"ALM-16005.html", "node_id":"alm-16005.xml", "product_code":"mrs", - "code":"664", + "code":"668", "des":"The system checks the Hive service status every 30 seconds. The alarm is generated when the heap memory usage of an Hive service exceeds the threshold (95% of the maximum", "doc_type":"alarm", "kw":"ALM-16005 The Heap Memory Usage of the Hive Process Exceeds the Threshold,Alarm Reference (Applicabl", @@ -12266,7 +12334,7 @@ "uri":"ALM-16006.html", "node_id":"alm-16006.xml", "product_code":"mrs", - "code":"665", + "code":"669", "des":"The system checks the Hive service status every 30 seconds. The alarm is generated when the direct memory usage of an Hive service exceeds the threshold (95% of the maxim", "doc_type":"alarm", "kw":"ALM-16006 The Direct Memory Usage of the Hive Process Exceeds the Threshold,Alarm Reference (Applica", @@ -12284,7 +12352,7 @@ "uri":"ALM-16007.html", "node_id":"alm-16007.xml", "product_code":"mrs", - "code":"666", + "code":"670", "des":"The system checks the garbage collection (GC) time of the Hive service every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (exceeds ", "doc_type":"alarm", "kw":"ALM-16007 Hive GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12302,7 +12370,7 @@ "uri":"ALM-16008.html", "node_id":"alm-16008.xml", "product_code":"mrs", - "code":"667", + "code":"671", "des":"The system checks the Hive service status every 30 seconds. The alarm is generated when the non-heap memory usage of an Hive service exceeds the threshold (95% of the max", "doc_type":"alarm", "kw":"ALM-16008 Non-Heap Memory Usage of the Hive Process Exceeds the Threshold,Alarm Reference (Applicabl", @@ -12320,7 +12388,7 @@ "uri":"ALM-16009.html", "node_id":"alm-16009.xml", "product_code":"mrs", - "code":"668", + "code":"672", "des":"The system checks the number of HQL maps in every 30 seconds. This alarm is generated if the number exceeds the threshold. By default, Trigger Count is set to 3, and the ", "doc_type":"alarm", "kw":"ALM-16009 Map Number Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12338,7 +12406,7 @@ "uri":"ALM-16045.html", "node_id":"alm-16045.xml", "product_code":"mrs", - "code":"669", + "code":"673", "des":"The system checks the Hive data warehouse in every 60 seconds.This alarm is generated when the Hive data warehouse is deleted.The default Hive data warehouse is deleted. ", "doc_type":"alarm", "kw":"ALM-16045 Hive Data Warehouse Is Deleted,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12356,7 +12424,7 @@ "uri":"ALM-16046.html", "node_id":"alm-16046.xml", "product_code":"mrs", - "code":"670", + "code":"674", "des":"The system checks the Hive data warehouse permission in every 60 seconds. This alarm is generated if the permission is modified.If the permission on the Hive default data", "doc_type":"alarm", "kw":"ALM-16046 Hive Data Warehouse Permission Is Modified,Alarm Reference (Applicable to MRS 3.x),User Gu", @@ -12374,7 +12442,7 @@ "uri":"ALM-16047.html", "node_id":"alm-16047.xml", "product_code":"mrs", - "code":"671", + "code":"675", "des":"The system checks the Hive service every 60 seconds. This alarm is generated when Hive registration information on ZooKeeper is lost or Hive cannot connect to ZooKeeper.I", "doc_type":"alarm", "kw":"ALM-16047 HiveServer Has Been Deregistered from ZooKeeper,Alarm Reference (Applicable to MRS 3.x),Us", @@ -12392,7 +12460,7 @@ "uri":"ALM-16048.html", "node_id":"alm-16048.xml", "product_code":"mrs", - "code":"672", + "code":"676", "des":"The system checks the Tez and Spark library paths every 180 seconds. This alarm is generated when the Tez or Spark library path does not exist.The Hive on Tez and Hive on", "doc_type":"usermanual", "kw":"ALM-16048 Tez or Spark Library Path Does Not Exist,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -12410,7 +12478,7 @@ "uri":"ALM-17003.html", "node_id":"alm-17003.xml", "product_code":"mrs", - "code":"673", + "code":"677", "des":"The system checks the Oozie service status in every 5 seconds. This alarm is generated when Oozie or a component on which Oozie depends cannot provide services properly.", "doc_type":"alarm", "kw":"ALM-17003 Oozie Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12428,7 +12496,7 @@ "uri":"ALM-17004.html", "node_id":"alm-17004.xml", "product_code":"mrs", - "code":"674", + "code":"678", "des":"The system checks the heap memory usage of the Oozie service every 60 seconds. The alarm is generated when the heap memory usage of a Metadata instance exceeds the thresh", "doc_type":"alarm", "kw":"ALM-17004 Oozie Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -12446,7 +12514,7 @@ "uri":"ALM-17005.html", "node_id":"alm-17005.xml", "product_code":"mrs", - "code":"675", + "code":"679", "des":"The system checks the non heap memory usage of Oozie every 30 seconds. This alarm is reported if the non heap memory usage of Oozie exceeds the threshold (80%). This alar", "doc_type":"alarm", "kw":"ALM-17005 Oozie Non Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", @@ -12464,7 +12532,7 @@ "uri":"ALM-17006.html", "node_id":"alm-17006.xml", "product_code":"mrs", - "code":"676", + "code":"680", "des":"The system checks the direct memory usage of the Oozie service every 30 seconds. The alarm is generated when the direct memory usage of an Oozie instance exceeds the thre", "doc_type":"alarm", "kw":"ALM-17006 Oozie Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Us", @@ -12482,7 +12550,7 @@ "uri":"ALM-17007.html", "node_id":"alm-17007.xml", "product_code":"mrs", - "code":"677", + "code":"681", "des":"The system checks GC time of the Oozie process every 60 seconds. The alarm is generated when GC time of the Oozie process exceeds the threshold (default value: 12 seconds", "doc_type":"alarm", "kw":"ALM-17007 Garbage Collection (GC) Time of the Oozie Process Exceeds the Threshold,Alarm Reference (A", @@ -12500,7 +12568,7 @@ "uri":"ALM-18000.html", "node_id":"alm-18000.xml", "product_code":"mrs", - "code":"678", + "code":"682", "des":"This alarm is generated when the Yarn service is unavailable. The alarm module checks the Yarn service status every 60 seconds.The alarm is cleared when the Yarn service ", "doc_type":"alarm", "kw":"ALM-18000 Yarn Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12518,7 +12586,7 @@ "uri":"ALM-18002.html", "node_id":"alm-18002.xml", "product_code":"mrs", - "code":"679", + "code":"683", "des":"The system checks the number of lost NodeManager nodes every 30 seconds, and compares the number with the threshold. The Number of Lost Nodes indicator has a default thre", "doc_type":"alarm", "kw":"ALM-18002 NodeManager Heartbeat Lost,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12536,7 +12604,7 @@ "uri":"ALM-18003.html", "node_id":"alm-18003.xml", "product_code":"mrs", - "code":"680", + "code":"684", "des":"The system checks the number of unhealthy NodeManager nodes every 30 seconds, and compares the number with the threshold. The Unhealthy Nodes indicator has a default thre", "doc_type":"alarm", "kw":"ALM-18003 NodeManager Unhealthy,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12554,7 +12622,7 @@ "uri":"ALM-18008.html", "node_id":"alm-18008.xml", "product_code":"mrs", - "code":"681", + "code":"685", "des":"The system checks the heap memory usage of Yarn ResourceManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap me", "doc_type":"alarm", "kw":"ALM-18008 Heap Memory Usage of ResourceManager Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -12572,7 +12640,7 @@ "uri":"ALM-18009.html", "node_id":"alm-18009.xml", "product_code":"mrs", - "code":"682", + "code":"686", "des":"The system checks the heap memory usage of Mapreduce JobHistoryServer every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the h", "doc_type":"alarm", "kw":"ALM-18009 Heap Memory Usage of JobHistoryServer Exceeds the Threshold,Alarm Reference (Applicable to", @@ -12590,7 +12658,7 @@ "uri":"ALM-18010.html", "node_id":"alm-18010.xml", "product_code":"mrs", - "code":"683", + "code":"687", "des":"The system checks the garbage collection (GC) duration of the ResourceManager process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold", "doc_type":"alarm", "kw":"ALM-18010 ResourceManager GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -12608,7 +12676,7 @@ "uri":"ALM-18011.html", "node_id":"alm-18011.xml", "product_code":"mrs", - "code":"684", + "code":"688", "des":"The system checks the garbage collection (GC) duration of the NodeManager process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12", "doc_type":"alarm", "kw":"ALM-18011 NodeManager GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Gui", @@ -12626,7 +12694,7 @@ "uri":"ALM-18012.html", "node_id":"alm-18012.xml", "product_code":"mrs", - "code":"685", + "code":"689", "des":"The system checks the garbage collection (GC) duration of the JobHistoryServer process every 60 seconds. This alarm is generated when the GC duration exceeds the threshol", "doc_type":"alarm", "kw":"ALM-18012 JobHistoryServer GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -12644,7 +12712,7 @@ "uri":"ALM-18013.html", "node_id":"alm-18013.xml", "product_code":"mrs", - "code":"686", + "code":"690", "des":"The system checks the direct memory usage of the Yarn service every 30 seconds. This alarm is generated when the direct memory usage of a ResourceManager instance exceeds", "doc_type":"alarm", "kw":"ALM-18013 ResourceManager Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to M", @@ -12662,7 +12730,7 @@ "uri":"ALM-18014.html", "node_id":"alm-18014.xml", "product_code":"mrs", - "code":"687", + "code":"691", "des":"The system checks the direct memory usage of the Yarn service every 30 seconds. This alarm is generated when the direct memory usage of a NodeManager instance exceeds the", "doc_type":"alarm", "kw":"ALM-18014 NodeManager Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", @@ -12680,7 +12748,7 @@ "uri":"ALM-18015.html", "node_id":"alm-18015.xml", "product_code":"mrs", - "code":"688", + "code":"692", "des":"The system checks the direct memory usage of the MapReduce service every 30 seconds. This alarm is generated when the direct memory usage of a JobHistoryServer instance e", "doc_type":"alarm", "kw":"ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -12698,7 +12766,7 @@ "uri":"ALM-18016.html", "node_id":"alm-18016.xml", "product_code":"mrs", - "code":"689", + "code":"693", "des":"The system checks the Non Heap memory usage of Yarn ResourceManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the Non", "doc_type":"alarm", "kw":"ALM-18016 Non Heap Memory Usage of ResourceManager Exceeds the Threshold,Alarm Reference (Applicable", @@ -12716,7 +12784,7 @@ "uri":"ALM-18017.html", "node_id":"alm-18017.xml", "product_code":"mrs", - "code":"690", + "code":"694", "des":"The system checks the Non Heap memory usage of Yarn NodeManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the Non Hea", "doc_type":"alarm", "kw":"ALM-18017 Non Heap Memory Usage of NodeManager Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -12734,7 +12802,7 @@ "uri":"ALM-18018.html", "node_id":"alm-18018.xml", "product_code":"mrs", - "code":"691", + "code":"695", "des":"The system checks the heap memory usage of Yarn NodeManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap memory", "doc_type":"alarm", "kw":"ALM-18018 NodeManager Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -12752,7 +12820,7 @@ "uri":"ALM-18019.html", "node_id":"alm-18019.xml", "product_code":"mrs", - "code":"692", + "code":"696", "des":"The system checks the Non Heap memory usage of MapReduce JobHistoryServer every 30 seconds and compares the actual usage with the threshold. The alarm is generated when t", "doc_type":"alarm", "kw":"ALM-18019 Non Heap Memory Usage of JobHistoryServer Exceeds the Threshold,Alarm Reference (Applicabl", @@ -12770,7 +12838,7 @@ "uri":"ALM-18020.html", "node_id":"alm-18020.xml", "product_code":"mrs", - "code":"693", + "code":"697", "des":"The system checks MapReduce and Spark tasks (except for permanent JDBC tasks) submitted to Yarn every 15 minutes. This alarm is generated when the task execution time exc", "doc_type":"alarm", "kw":"ALM-18020 Yarn Task Execution Timeout,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12788,7 +12856,7 @@ "uri":"ALM-18021.html", "node_id":"alm-18021.xml", "product_code":"mrs", - "code":"694", + "code":"698", "des":"The alarm module checks the MapReduce service status every 60 seconds. This alarm is generated when the system detects that the MapReduce service is unavailable.The alarm", "doc_type":"alarm", "kw":"ALM-18021 Mapreduce Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12806,7 +12874,7 @@ "uri":"ALM-18022.html", "node_id":"alm-18022.xml", "product_code":"mrs", - "code":"695", + "code":"699", "des":"The alarm module checks Yarn queue resources every 60 seconds. This alarm is generated when available resources or ApplicationMaster (AM) resources of a queue are insuffi", "doc_type":"alarm", "kw":"ALM-18022 Insufficient Yarn Queue Resources,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12824,7 +12892,7 @@ "uri":"ALM-18023.html", "node_id":"alm-18023.xml", "product_code":"mrs", - "code":"696", + "code":"700", "des":"The alarm module checks the number of pending applications in the Yarn root queue every 60 seconds. The alarm is generated when the number exceeds 60.It takes long time t", "doc_type":"alarm", "kw":"ALM-18023 Number of Pending Yarn Tasks Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -12842,7 +12910,7 @@ "uri":"ALM-18024.html", "node_id":"alm-18024.xml", "product_code":"mrs", - "code":"697", + "code":"701", "des":"The alarm module checks the pending memory of Yarn every 60 seconds. The alarm is generated when the pending memory exceeds the threshold. Pending memory indicates the to", "doc_type":"alarm", "kw":"ALM-18024 Pending Yarn Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Us", @@ -12860,7 +12928,7 @@ "uri":"ALM-18025.html", "node_id":"alm-18025.xml", "product_code":"mrs", - "code":"698", + "code":"702", "des":"The alarm module checks the number of terminated applications in the Yarn root queue every 60 seconds. The alarm is generated when the number exceeds 50 for three consecu", "doc_type":"alarm", "kw":"ALM-18025 Number of Terminated Yarn Tasks Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", @@ -12878,7 +12946,7 @@ "uri":"ALM-18026.html", "node_id":"alm-18026.xml", "product_code":"mrs", - "code":"699", + "code":"703", "des":"The alarm module checks the number of failed applications in the Yarn root queue every 60 seconds. The alarm is generated when the number exceeds 50 for three consecutive", "doc_type":"alarm", "kw":"ALM-18026 Number of Failed Yarn Tasks Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", @@ -12896,7 +12964,7 @@ "uri":"ALM-19000.html", "node_id":"alm-19000.xml", "product_code":"mrs", - "code":"700", + "code":"704", "des":"This alarm is generated when the HBase service is unavailable. The alarm module checks the HBase service status every 120 seconds.This alarm is cleared when the HBase ser", "doc_type":"alarm", "kw":"ALM-19000 HBase Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12914,7 +12982,7 @@ "uri":"ALM-19006.html", "node_id":"alm-19006.xml", "product_code":"mrs", - "code":"701", + "code":"705", "des":"The alarm module checks the HBase DR data synchronization status every 30 seconds. When disaster recovery (DR) data fails to be synchronized to a standby cluster, the ala", "doc_type":"alarm", "kw":"ALM-19006 HBase Replication Sync Failed,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12932,7 +13000,7 @@ "uri":"ALM-19007.html", "node_id":"alm-19007.xml", "product_code":"mrs", - "code":"702", + "code":"706", "des":"The system checks the old generation garbage collection (GC) time of the HBase service every 60 seconds. This alarm is generated when the detected old generation GC time ", "doc_type":"alarm", "kw":"ALM-19007 HBase GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12950,7 +13018,7 @@ "uri":"ALM-19008.html", "node_id":"alm-19008.xml", "product_code":"mrs", - "code":"703", + "code":"707", "des":"The system checks the HBase service status every 30 seconds. The alarm is generated when the heap memory usage of an HBase service exceeds the threshold (90% of the maxim", "doc_type":"alarm", "kw":"ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold,Alarm Reference (Applicable t", @@ -12968,7 +13036,7 @@ "uri":"ALM-19009.html", "node_id":"alm-19009.xml", "product_code":"mrs", - "code":"704", + "code":"708", "des":"The system checks the HBase service status every 30 seconds. The alarm is generated when the direct memory usage of an HBase service exceeds the threshold (90% of the max", "doc_type":"alarm", "kw":"ALM-19009 Direct Memory Usage of the HBase Process Exceeds the Threshold,Alarm Reference (Applicable", @@ -12986,7 +13054,7 @@ "uri":"ALM-19011.html", "node_id":"alm-19011.xml", "product_code":"mrs", - "code":"705", + "code":"709", "des":"The system checks the number of regions on each RegionServer in each HBase service instance every 30 seconds. The region number is displayed on the HBase service monitori", "doc_type":"alarm", "kw":"ALM-19011 RegionServer Region Number Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -13004,7 +13072,7 @@ "uri":"ALM-19012.html", "node_id":"alm-19012.xml", "product_code":"mrs", - "code":"706", + "code":"710", "des":"The system checks whether HBase directories and files exist on the HDFS every 120 seconds. This alarm is generated when the system detects that the files or directories d", "doc_type":"alarm", "kw":"ALM-19012 HBase System Table Directory or File Lost,Alarm Reference (Applicable to MRS 3.x),User Gui", @@ -13022,7 +13090,7 @@ "uri":"ALM-19013.html", "node_id":"alm-19013.xml", "product_code":"mrs", - "code":"707", + "code":"711", "des":"The system checks the number of regions in transaction state on HBase every 300 seconds. This alarm is generated when the system detects that the duration of regions in t", "doc_type":"alarm", "kw":"ALM-19013 Duration of Regions in transaction State Exceeds the Threshold,Alarm Reference (Applicable", @@ -13040,7 +13108,7 @@ "uri":"ALM-19014.html", "node_id":"alm-19014.xml", "product_code":"mrs", - "code":"708", + "code":"712", "des":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the ZNode capacity usage of the HBase service exceeds the critical ", "doc_type":"alarm", "kw":"ALM-19014 Capacity Quota Usage on ZooKeeper Exceeds the Threshold Severely,Alarm Reference (Applicab", @@ -13058,7 +13126,7 @@ "uri":"ALM-19015.html", "node_id":"alm-19015.xml", "product_code":"mrs", - "code":"709", + "code":"713", "des":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the system detects that the ZNode quantity usage of the HBase servi", "doc_type":"alarm", "kw":"ALM-19015 Quantity Quota Usage on ZooKeeper Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -13076,7 +13144,7 @@ "uri":"ALM-19016.html", "node_id":"alm-19016.xml", "product_code":"mrs", - "code":"710", + "code":"714", "des":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the znode usage of the HBase service exceeds the critical alarm thr", "doc_type":"alarm", "kw":"ALM-19016 Quantity Quota Usage on ZooKeeper Exceeds the Threshold Severely,Alarm Reference (Applicab", @@ -13094,7 +13162,7 @@ "uri":"ALM-19017.html", "node_id":"alm-19017.xml", "product_code":"mrs", - "code":"711", + "code":"715", "des":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the system detects that the ZNodes capacity usage of the HBase serv", "doc_type":"alarm", "kw":"ALM-19017 Capacity Quota Usage on ZooKeeper Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -13112,7 +13180,7 @@ "uri":"ALM-19018.html", "node_id":"alm-19018.xml", "product_code":"mrs", - "code":"712", + "code":"716", "des":"The system checks the HBase compaction queue size every 300 seconds. This alarm is generated when the compaction queue size exceeds the alarm threshold (100 by default). ", "doc_type":"alarm", "kw":"ALM-19018 HBase Compaction Queue Size Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", @@ -13130,7 +13198,7 @@ "uri":"ALM-19019.html", "node_id":"alm-19019.xml", "product_code":"mrs", - "code":"713", + "code":"717", "des":"The system checks the number of HFiles to be synchronized by the RegionServer of each HBase service instance every 30 seconds. This indicator can be viewed on the RegionS", "doc_type":"alarm", "kw":"ALM-19019 Number of HBase HFiles to Be Synchronized Exceeds the Threshold,Alarm Reference (Applicabl", @@ -13148,7 +13216,7 @@ "uri":"ALM-19020.html", "node_id":"alm-19020.xml", "product_code":"mrs", - "code":"714", + "code":"718", "des":"The system checks the number of WAL files to be synchronized by the RegionServer of each HBase service instance every 30 seconds. This indicator can be viewed on the Regi", "doc_type":"alarm", "kw":"ALM-19020 Number of HBase WAL Files to Be Synchronized Exceeds the Threshold,Alarm Reference (Applic", @@ -13166,7 +13234,7 @@ "uri":"ALM-19021.html", "node_id":"alm-19021.xml", "product_code":"mrs", - "code":"715", + "code":"719", "des":"The system checks the RegionServer handler usage of each HBase service instance every 30 seconds. This alarm is generated when the handler usage of a RegionServer exceeds", "doc_type":"usermanual", "kw":"ALM-19021 Handler Usage of RegionServer Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -13184,7 +13252,7 @@ "uri":"ALM-20002.html", "node_id":"alm-20002.xml", "product_code":"mrs", - "code":"716", + "code":"720", "des":"This alarm is generated when the Hue service is unavailable. The system checks the Hue service status every 60 seconds.This alarm is cleared when the Hue service is norma", "doc_type":"alarm", "kw":"ALM-20002 Hue Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13202,7 +13270,7 @@ "uri":"ALM-23001.html", "node_id":"alm-23001.xml", "product_code":"mrs", - "code":"717", + "code":"721", "des":"The system checks the Loader service availability every 60 seconds. This alarm is generated when the system detects that the Loader service is unavailable. This alarm is ", "doc_type":"alarm", "kw":"ALM-23001 Loader Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13220,7 +13288,7 @@ "uri":"ALM-23003.html", "node_id":"alm-23003.xml", "product_code":"mrs", - "code":"718", + "code":"722", "des":"This alarm is generated immediately when the system detects that the Loader job fails. This alarm is cleared when the failed job is manually handled by a user. This alarm", "doc_type":"alarm", "kw":"ALM-23003 Loader Task Execution Failure,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13238,7 +13306,7 @@ "uri":"ALM-23004.html", "node_id":"alm-23004.xml", "product_code":"mrs", - "code":"719", + "code":"723", "des":"The system checks the heap memory usage of the Loader service every 60 seconds. The alarm is generated when the heap memory usage of a Loader instance exceeds the thresho", "doc_type":"alarm", "kw":"ALM-23004 Loader Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -13256,7 +13324,7 @@ "uri":"ALM-23005.html", "node_id":"alm-23005.xml", "product_code":"mrs", - "code":"720", + "code":"724", "des":"The system checks the non-heap memory usage of the Loader service every 30 seconds. The alarm is generated when the non-heap memory usage of a Loader instance exceeds the", "doc_type":"alarm", "kw":"ALM-23005 Loader Non-Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -13274,7 +13342,7 @@ "uri":"ALM-23006.html", "node_id":"alm-23006.xml", "product_code":"mrs", - "code":"721", + "code":"725", "des":"The system checks the direct memory usage of the Loader service every 30 seconds. The alarm is generated when the direct memory usage of a Loader instance exceeds the thr", "doc_type":"alarm", "kw":"ALM-23006 Loader Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -13292,7 +13360,7 @@ "uri":"ALM-23007.html", "node_id":"alm-23007.xml", "product_code":"mrs", - "code":"722", + "code":"726", "des":"The system checks GC time of the Loader process every 60 seconds. The alarm is generated when GC time of the Loader process exceeds the threshold (default value: 12 secon", "doc_type":"alarm", "kw":"ALM-23007 Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold,Alarm Reference (", @@ -13310,7 +13378,7 @@ "uri":"ALM-24000.html", "node_id":"alm-24000.xml", "product_code":"mrs", - "code":"723", + "code":"727", "des":"The alarm module checks the Flume service status every 180 seconds. This alarm is generated if the Flume service is abnormal.This alarm is automatically cleared after the", "doc_type":"alarm", "kw":"ALM-24000 Flume Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13328,7 +13396,7 @@ "uri":"ALM-24001.html", "node_id":"alm-24001.xml", "product_code":"mrs", - "code":"724", + "code":"728", "des":"The Flume agent instance for which the alarm is generated cannot be started. This alarm is generated when the Flume agent process is faulty (The system checks in every 5 ", "doc_type":"alarm", "kw":"ALM-24001 Flume Agent Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13346,7 +13414,7 @@ "uri":"ALM-24003.html", "node_id":"alm-24003.xml", "product_code":"mrs", - "code":"725", + "code":"729", "des":"The alarm module monitors the port connection status on the Flume server. This alarm is generated if the Flume server fails to receive a connection message from the Flume", "doc_type":"alarm", "kw":"ALM-24003 Flume Client Connection Interrupted,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13364,7 +13432,7 @@ "uri":"ALM-24004.html", "node_id":"alm-24004.xml", "product_code":"mrs", - "code":"726", + "code":"730", "des":"The alarm module monitors the status of Flume Source. This alarm is generated immediately when the duration in which Source fails to read the data exceeds the threshold.T", "doc_type":"alarm", "kw":"ALM-24004 Exception Occurs When Flume Reads Data,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13382,7 +13450,7 @@ "uri":"ALM-24005.html", "node_id":"alm-24005.xml", "product_code":"mrs", - "code":"727", + "code":"731", "des":"The alarm module monitors the capacity status of Flume Channel. The alarm is generated immediately when the duration that Channel is fully occupied exceeds the threshold ", "doc_type":"alarm", "kw":"ALM-24005 Exception Occurs When Flume Transmits Data,Alarm Reference (Applicable to MRS 3.x),User Gu", @@ -13400,7 +13468,7 @@ "uri":"ALM-24006.html", "node_id":"alm-24006.xml", "product_code":"mrs", - "code":"728", + "code":"732", "des":"The system checks the heap memory usage of the Flume service every 60 seconds. This alarm is generated when the heap memory usage of the Flume instance exceeds the thresh", "doc_type":"alarm", "kw":"ALM-24006 Heap Memory Usage of Flume Server Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -13418,7 +13486,7 @@ "uri":"ALM-24007.html", "node_id":"alm-24007.xml", "product_code":"mrs", - "code":"729", + "code":"733", "des":"The system checks the direct memory usage of the Flume service every 60 seconds. This alarm is generated when the direct memory usage of the Flume instance exceeds the th", "doc_type":"alarm", "kw":"ALM-24007 Flume Server Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS ", @@ -13436,7 +13504,7 @@ "uri":"ALM-24008.html", "node_id":"alm-24008.xml", "product_code":"mrs", - "code":"730", + "code":"734", "des":"The system checks the non-heap memory usage of the Flume service every 60 seconds. This alarm is generated when the non-heap memory usage of the Flume instance exceeds th", "doc_type":"alarm", "kw":"ALM-24008 Flume Server Non Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MR", @@ -13454,7 +13522,7 @@ "uri":"ALM-24009.html", "node_id":"alm-24009.xml", "product_code":"mrs", - "code":"731", + "code":"735", "des":"The system checks the GC duration of the Flume process every 60 seconds. This alarm is generated when the GC duration of the Flume process exceeds the threshold (12 secon", "doc_type":"alarm", "kw":"ALM-24009 Flume Server Garbage Collection (GC) Time Exceeds the Threshold,Alarm Reference (Applicabl", @@ -13472,7 +13540,7 @@ "uri":"ALM-24010.html", "node_id":"alm-24010.xml", "product_code":"mrs", - "code":"732", + "code":"736", "des":"This section applies to MRS 3.2.0-LTS.2 or later.Flume checks whether the Flume certificate file is valid (whether the certificate exists and whether the certificate form", "doc_type":"usermanual", "kw":"ALM-24010 Flume Certificate File Is Invalid or Damaged,Alarm Reference (Applicable to MRS 3.x),User ", @@ -13490,7 +13558,7 @@ "uri":"ALM-24011.html", "node_id":"alm-24011.xml", "product_code":"mrs", - "code":"733", + "code":"737", "des":"This section applies to MRS 3.2.0-LTS.2 or later.Flume checks whether the Flume certificate file is about to expire every hour. This alarm is generated when the remaining", "doc_type":"usermanual", "kw":"ALM-24011 Flume Certificate File Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Gui", @@ -13508,7 +13576,7 @@ "uri":"ALM-24012.html", "node_id":"alm-24012.xml", "product_code":"mrs", - "code":"734", + "code":"738", "des":"This section applies to MRS 3.2.0-LTS.2 or later.Flume checks whether its certificate file in the system has expired every hour. This alarm is generated when the server c", "doc_type":"usermanual", "kw":"ALM-24012 Flume Certificate File Has Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13526,7 +13594,7 @@ "uri":"ALM-24013.html", "node_id":"alm-24013.xml", "product_code":"mrs", - "code":"735", + "code":"739", "des":"This section applies to MRS 3.2.0-LTS.2 or later.MonitorServer checks whether its certificate file is valid (whether the certificate exists and whether the certificate fo", "doc_type":"usermanual", "kw":"ALM-24013 Flume MonitorServer Certificate File Is Invalid or Damaged,Alarm Reference (Applicable to ", @@ -13544,7 +13612,7 @@ "uri":"ALM-24014.html", "node_id":"alm-24014.xml", "product_code":"mrs", - "code":"736", + "code":"740", "des":"This section applies to MRS 3.2.0-LTS.2 or later.MonitorServer checks whether its certificate file is about to expire every hour. This alarm is generated when the remaini", "doc_type":"usermanual", "kw":"ALM-24014 Flume MonitorServer Certificate Is About to Expire,Alarm Reference (Applicable to MRS 3.x)", @@ -13562,7 +13630,7 @@ "uri":"ALM-24015.html", "node_id":"alm-24015.xml", "product_code":"mrs", - "code":"737", + "code":"741", "des":"This section applies to MRS 3.2.0-LTS.2 or later.MonitorServer checks whether its certificate file in the system has expired every hour. This alarm is generated when the ", "doc_type":"usermanual", "kw":"ALM-24015 Flume MonitorServer Certificate File Has Expired,Alarm Reference (Applicable to MRS 3.x),U", @@ -13580,7 +13648,7 @@ "uri":"ALM-25000.html", "node_id":"alm-25000.xml", "product_code":"mrs", - "code":"738", + "code":"742", "des":"The system checks the LdapServer service status every 30 seconds. This alarm is generated when the system detects that both the active and standby LdapServer services are", "doc_type":"alarm", "kw":"ALM-25000 LdapServer Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13598,7 +13666,7 @@ "uri":"ALM-25004.html", "node_id":"alm-25004.xml", "product_code":"mrs", - "code":"739", + "code":"743", "des":"The system checks the LdapServer data every 30 seconds. This alarm is generated when the data on the active and standby LdapServers of Manager is inconsistent for 12 cons", "doc_type":"alarm", "kw":"ALM-25004 Abnormal LdapServer Data Synchronization,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -13616,7 +13684,7 @@ "uri":"ALM-25005.html", "node_id":"alm-25005.xml", "product_code":"mrs", - "code":"740", + "code":"744", "des":"The system checks the status of the nscd service every 60 seconds. This alarm is generated when the nscd process fails to be queried for four consecutive times (three min", "doc_type":"alarm", "kw":"ALM-25005 nscd Service Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13634,7 +13702,7 @@ "uri":"ALM-25006.html", "node_id":"alm-25006.xml", "product_code":"mrs", - "code":"741", + "code":"745", "des":"The system checks the status of the sssd service every 60 seconds. This alarm is generated when the sssd process fails to be queried for four consecutive times (three min", "doc_type":"alarm", "kw":"ALM-25006 Sssd Service Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13652,7 +13720,7 @@ "uri":"ALM-25500.html", "node_id":"alm-25500.xml", "product_code":"mrs", - "code":"742", + "code":"746", "des":"The system checks the KrbServer service status every 30 seconds. This alarm is generated when the system detects that the KrbServer service is abnormal.This alarm is clea", "doc_type":"alarm", "kw":"ALM-25500 KrbServer Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13670,7 +13738,7 @@ "uri":"ALM-26051.html", "node_id":"alm-26051.xml", "product_code":"mrs", - "code":"743", + "code":"747", "des":"The system checks the Storm service status every 30 seconds. This alarm is generated when all Nimbus nodes in the cluster are abnormal and the Storm service is unavailabl", "doc_type":"alarm", "kw":"ALM-26051 Storm Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13688,7 +13756,7 @@ "uri":"ALM-26052.html", "node_id":"alm-26052.xml", "product_code":"mrs", - "code":"744", + "code":"748", "des":"The system periodically checks the number of available Supervisors every 60 seconds and compares the number of available Supervisors with the threshold. This alarm is gen", "doc_type":"alarm", "kw":"ALM-26052 Number of Available Supervisors of the Storm Service Is Less Than the Threshold,Alarm Refe", @@ -13706,7 +13774,7 @@ "uri":"ALM-26053.html", "node_id":"alm-26053.xml", "product_code":"mrs", - "code":"745", + "code":"749", "des":"The system checks the slot usage every 60 seconds and compares the actual slot usage with the threshold. This alarm is generated when the slot usage is greater than the t", "doc_type":"alarm", "kw":"ALM-26053 Storm Slot Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13724,7 +13792,7 @@ "uri":"ALM-26054.html", "node_id":"alm-26054.xml", "product_code":"mrs", - "code":"746", + "code":"750", "des":"The system checks the heap memory usage of Storm Nimbus every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap memory usa", "doc_type":"alarm", "kw":"ALM-26054 Nimbus Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", @@ -13742,7 +13810,7 @@ "uri":"ALM-27001.html", "node_id":"alm-27001.xml", "product_code":"mrs", - "code":"747", + "code":"751", "des":"The alarm module checks the DBService service status every 30 seconds. This alarm is generated when the system detects that DBService service is unavailable.This alarm is", "doc_type":"alarm", "kw":"ALM-27001 DBService Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13760,7 +13828,7 @@ "uri":"ALM-27003.html", "node_id":"alm-27003.xml", "product_code":"mrs", - "code":"748", + "code":"752", "des":"This alarm is generated when the active or standby DBService node does not receive heartbeat messages from the peer node for 7 seconds.This alarm is cleared when the hear", "doc_type":"alarm", "kw":"ALM-27003 DBService Heartbeat Interruption Between the Active and Standby Nodes,Alarm Reference (App", @@ -13778,7 +13846,7 @@ "uri":"ALM-27004.html", "node_id":"alm-27004.xml", "product_code":"mrs", - "code":"749", + "code":"753", "des":"The system checks the data synchronization status between the active and standby DBService every 10 seconds. This alarm is generated when the synchronization status canno", "doc_type":"alarm", "kw":"ALM-27004 Data Inconsistency Between Active and Standby DBServices,Alarm Reference (Applicable to MR", @@ -13796,7 +13864,7 @@ "uri":"ALM-27005.html", "node_id":"alm-27005.xml", "product_code":"mrs", - "code":"750", + "code":"754", "des":"The system checks the usage of the number of database connections of the nodes where DBServer instances are located every 30 seconds and compares the usage with the thres", "doc_type":"alarm", "kw":"ALM-27005 Database Connections Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -13814,7 +13882,7 @@ "uri":"ALM-27006.html", "node_id":"alm-27006.xml", "product_code":"mrs", - "code":"751", + "code":"755", "des":"The system checks the disk space usage of the data directory on the active DBServer node every 30 seconds and compares the disk usage with the threshold. The alarm is gen", "doc_type":"alarm", "kw":"ALM-27006 Disk Space Usage of the Data Directory Exceeds the Threshold,Alarm Reference (Applicable t", @@ -13832,7 +13900,7 @@ "uri":"ALM-27007.html", "node_id":"alm-27007.xml", "product_code":"mrs", - "code":"752", + "code":"756", "des":"The system checks the disk space usage of the data directory on the active DBServer node every 30 seconds. The alarm is generated when the disk space usage exceeds 90%.Th", "doc_type":"alarm", "kw":"ALM-27007 Database Enters the Read-Only Mode,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13850,7 +13918,7 @@ "uri":"ALM-38000.html", "node_id":"alm-38000.xml", "product_code":"mrs", - "code":"753", + "code":"757", "des":"The system checks the Kafka service status every 30 seconds. This alarm is generated when the Kafka service is unavailable.This alarm is cleared when the Kafka service re", "doc_type":"alarm", "kw":"ALM-38000 Kafka Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13868,7 +13936,7 @@ "uri":"ALM-38001.html", "node_id":"alm-38001.xml", "product_code":"mrs", - "code":"754", + "code":"758", "des":"The system checks the Kafka disk usage every 60 seconds and compares the actual disk usage with the threshold. The disk usage has a default threshold. This alarm is gener", "doc_type":"alarm", "kw":"ALM-38001 Insufficient Kafka Disk Capacity,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13886,7 +13954,7 @@ "uri":"ALM-38002.html", "node_id":"alm-38002.xml", "product_code":"mrs", - "code":"755", + "code":"759", "des":"The system checks the Kafka service status every 30 seconds. The alarm is generated when the heap memory usage of a Kafka instance exceeds the threshold (95% of the maxim", "doc_type":"alarm", "kw":"ALM-38002 Kafka Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -13904,7 +13972,7 @@ "uri":"ALM-38004.html", "node_id":"alm-38004.xml", "product_code":"mrs", - "code":"756", + "code":"760", "des":"The system checks the direct memory usage of the Kafka service every 30 seconds. This alarm is generated when the direct memory usage of a Kafka instance exceeds the thre", "doc_type":"alarm", "kw":"ALM-38004 Kafka Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Us", @@ -13922,7 +13990,7 @@ "uri":"ALM-38005.html", "node_id":"alm-38005.xml", "product_code":"mrs", - "code":"757", + "code":"761", "des":"The system checks the garbage collection (GC) duration of the Broker process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seco", "doc_type":"alarm", "kw":"ALM-38005 GC Duration of the Broker Process Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -13940,7 +14008,7 @@ "uri":"ALM-38006.html", "node_id":"alm-38006.xml", "product_code":"mrs", - "code":"758", + "code":"762", "des":"The system checks the percentage of Kafka partitions that are not completely synchronized to the total number of partitions every 60 seconds. This alarm is generated when", "doc_type":"alarm", "kw":"ALM-38006 Percentage of Kafka Partitions That Are Not Completely Synchronized Exceeds the Threshold,", @@ -13958,7 +14026,7 @@ "uri":"ALM-38007.html", "node_id":"alm-38007.xml", "product_code":"mrs", - "code":"759", + "code":"763", "des":"The system checks the default user of Kafka every 60 seconds. This alarm is generated when the system detects that the user status is abnormal.Trigger Count is set to 1. ", "doc_type":"alarm", "kw":"ALM-38007 Status of Kafka Default User Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -13976,7 +14044,7 @@ "uri":"ALM-38008.html", "node_id":"alm-38008.xml", "product_code":"mrs", - "code":"760", + "code":"764", "des":"The system checks the Kafka data directory status every 60 seconds. This alarm is generated when the system detects that the status of a data directory is abnormal.Trigge", "doc_type":"alarm", "kw":"ALM-38008 Abnormal Kafka Data Directory Status,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13994,10 +14062,10 @@ "uri":"ALM-38009.html", "node_id":"alm-38009.xml", "product_code":"mrs", - "code":"761", + "code":"765", "des":"This section applies to versions later than MRS 3.1.0.The system checks the I/O status of each Kafka disk every 60 seconds. This alarm is generated when the disk I/O of a", "doc_type":"alarm", - "kw":"ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0),Alarm Reference (Appli", + "kw":"(Applicable to Versions Later Than MRS 3.1.0)ALM-38009 Busy Broker Disk I/Os (Applicable to Versions", "search_title":"", "metedata":[ { @@ -14005,14 +14073,14 @@ "prodname":"mrs" } ], - "title":"ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0)", + "title":"(Applicable to Versions Later Than MRS 3.1.0)ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0)", "githuburl":"" }, { "uri":"ALM-38010.html", "node_id":"alm-38010.xml", "product_code":"mrs", - "code":"762", + "code":"766", "des":"The system checks the number of replicas of each topic every 60 seconds on the node where the Kafka Controller resides. This alarm is generated when there is one replica ", "doc_type":"alarm", "kw":"ALM-38010 Topics with Single Replica,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14030,7 +14098,7 @@ "uri":"ALM-38011.html", "node_id":"alm-38011.xml", "product_code":"mrs", - "code":"763", + "code":"767", "des":"The system checks the number of connections of each user on Broker every 30 seconds. This alarm is generated when the connection usage of a user on the Broker exceeds the", "doc_type":"alarm", "kw":"ALM-38011 User Connection Usage on Broker Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", @@ -14048,7 +14116,7 @@ "uri":"ALM-43001.html", "node_id":"alm-43001.xml", "product_code":"mrs", - "code":"764", + "code":"768", "des":"The system checks the Spark2x service status every 300 seconds. This alarm is generated when the Spark2x service is unavailable.This alarm is cleared when the Spark2x ser", "doc_type":"alarm", "kw":"ALM-43001 Spark2x Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14066,7 +14134,7 @@ "uri":"ALM-43006.html", "node_id":"alm-43006.xml", "product_code":"mrs", - "code":"765", + "code":"769", "des":"The system checks the JobHistory2x Process status every 30 seconds. The alarm is generated when the heap memory usage of a JobHistory2x Process exceeds the threshold (95%", "doc_type":"alarm", "kw":"ALM-43006 Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold,Alarm Reference (Appli", @@ -14084,7 +14152,7 @@ "uri":"ALM-43007.html", "node_id":"alm-43007.xml", "product_code":"mrs", - "code":"766", + "code":"770", "des":"The system checks the JobHistory2x Process status every 30 seconds. The alarm is generated when the non-heap memory usage of a JobHistory2x Process exceeds the threshold ", "doc_type":"alarm", "kw":"ALM-43007 Non-Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold,Alarm Reference (A", @@ -14102,7 +14170,7 @@ "uri":"ALM-43008.html", "node_id":"alm-43008.xml", "product_code":"mrs", - "code":"767", + "code":"771", "des":"The system checks the JobHistory2x Process status every 30 seconds. The alarm is generated when the direct memory usage of a JobHistory2x Process exceeds the threshold (9", "doc_type":"alarm", "kw":"ALM-43008 The Direct Memory Usage of the JobHistory2x Process Exceeds the Threshold,Alarm Reference ", @@ -14120,7 +14188,7 @@ "uri":"ALM-43009.html", "node_id":"alm-43009.xml", "product_code":"mrs", - "code":"768", + "code":"772", "des":"The system checks the garbage collection (GC) time of the JobHistory2x Process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (", "doc_type":"alarm", "kw":"ALM-43009 JobHistory2x Process GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -14138,7 +14206,7 @@ "uri":"ALM-43010.html", "node_id":"alm-43010.xml", "product_code":"mrs", - "code":"769", + "code":"773", "des":"The system checks the JDBCServer2x Process status every 30 seconds. The alarm is generated when the heap memory usage of a JDBCServer2x Process exceeds the threshold (95%", "doc_type":"alarm", "kw":"ALM-43010 Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold,Alarm Reference (Appli", @@ -14156,7 +14224,7 @@ "uri":"ALM-43011.html", "node_id":"alm-43011.xml", "product_code":"mrs", - "code":"770", + "code":"774", "des":"The system checks the JDBCServer2x Process status every 30 seconds. The alarm is generated when the non-heap memory usage of an JDBCServer2x Process exceeds the threshold", "doc_type":"alarm", "kw":"ALM-43011 Non-Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold,Alarm Reference (A", @@ -14174,7 +14242,7 @@ "uri":"ALM-43012.html", "node_id":"alm-43012.xml", "product_code":"mrs", - "code":"771", + "code":"775", "des":"The system checks the JDBCServer2x Process status every 30 seconds. The alarm is generated when the direct heap memory usage of a JDBCServer2x Process exceeds the thresho", "doc_type":"alarm", "kw":"ALM-43012 Direct Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold,Alarm Reference", @@ -14192,7 +14260,7 @@ "uri":"ALM-43013.html", "node_id":"alm-43013.xml", "product_code":"mrs", - "code":"772", + "code":"776", "des":"The system checks the garbage collection (GC) time of the JDBCServer2x Process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (", "doc_type":"alarm", "kw":"ALM-43013 JDBCServer2x Process GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -14210,7 +14278,7 @@ "uri":"ALM-43017.html", "node_id":"alm-43017.xml", "product_code":"mrs", - "code":"773", + "code":"777", "des":"The system checks the number of Full garbage collection (GC) times of the JDBCServer2x process every 60 seconds. This alarm is generated when the detected Full GC number ", "doc_type":"alarm", "kw":"ALM-43017 JDBCServer2x Process Full GC Number Exceeds the Threshold,Alarm Reference (Applicable to M", @@ -14228,7 +14296,7 @@ "uri":"ALM-43018.html", "node_id":"alm-43018.xml", "product_code":"mrs", - "code":"774", + "code":"778", "des":"The system checks the number of Full garbage collection (GC) times of the JobHistory2x process every 60 seconds. This alarm is generated when the detected Full GC number ", "doc_type":"alarm", "kw":"ALM-43018 JobHistory2x Process Full GC Number Exceeds the Threshold,Alarm Reference (Applicable to M", @@ -14246,7 +14314,7 @@ "uri":"ALM-43019.html", "node_id":"alm-43019.xml", "product_code":"mrs", - "code":"775", + "code":"779", "des":"The system checks the IndexServer2x process status every 30 seconds. The alarm is generated when the heap memory usage of a IndexServer2x process exceeds the threshold (9", "doc_type":"alarm", "kw":"ALM-43019 Heap Memory Usage of the IndexServer2x Process Exceeds the Threshold,Alarm Reference (Appl", @@ -14264,7 +14332,7 @@ "uri":"ALM-43020.html", "node_id":"alm-43020.xml", "product_code":"mrs", - "code":"776", + "code":"780", "des":"The system checks the IndexServer2x process status every 30 seconds. The alarm is generated when the non-heap memory usage of the IndexServer2x process exceeds the thresh", "doc_type":"alarm", "kw":"ALM-43020 Non-Heap Memory Usage of the IndexServer2x Process Exceeds the Threshold,Alarm Reference (", @@ -14282,7 +14350,7 @@ "uri":"ALM-43021.html", "node_id":"alm-43021.xml", "product_code":"mrs", - "code":"777", + "code":"781", "des":"The system checks the IndexServer2x process status every 30 seconds. The alarm is generated when the direct heap memory usage of a IndexServer2x process exceeds the thres", "doc_type":"alarm", "kw":"ALM-43021 Direct Memory Usage of the IndexServer2x Process Exceeds the Threshold,Alarm Reference (Ap", @@ -14300,7 +14368,7 @@ "uri":"ALM-43022.html", "node_id":"alm-43022.xml", "product_code":"mrs", - "code":"778", + "code":"782", "des":"The system checks the GC time of the IndexServer2x process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (12 seconds) for thre", "doc_type":"alarm", "kw":"ALM-43022 IndexServer2x Process GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -14318,7 +14386,7 @@ "uri":"ALM-43023.html", "node_id":"alm-43023.xml", "product_code":"mrs", - "code":"779", + "code":"783", "des":"The system checks the Full GC number of the IndexServer2x process every 60 seconds. This alarm is generated when the detected Full GC number exceeds the threshold (12) fo", "doc_type":"alarm", "kw":"ALM-43023 IndexServer2x Process Full GC Number Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -14336,7 +14404,7 @@ "uri":"ALM-44004.html", "node_id":"alm-44004.xml", "product_code":"mrs", - "code":"780", + "code":"784", "des":"This alarm is generated when the system detects that the number of queuing tasks in a resource group exceeds the threshold. The system queries the number of queuing tasks", "doc_type":"alarm", "kw":"ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold,Alarm Reference (Appl", @@ -14354,7 +14422,7 @@ "uri":"ALM-44005.html", "node_id":"alm-44005.xml", "product_code":"mrs", - "code":"781", + "code":"785", "des":"The system collects GC time of the Presto Coordinator process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for thre", "doc_type":"alarm", "kw":"ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold,Alarm Reference (Applicable to MR", @@ -14372,7 +14440,7 @@ "uri":"ALM-44006.html", "node_id":"alm-44006.xml", "product_code":"mrs", - "code":"782", + "code":"786", "des":"The system collects GC time of the Presto Worker process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for three con", "doc_type":"alarm", "kw":"ALM-44006 Presto Worker Process GC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -14390,7 +14458,7 @@ "uri":"ALM-45000.html", "node_id":"alm-45000.xml", "product_code":"mrs", - "code":"783", + "code":"787", "des":"The system checks the HetuEngine service status every 300 seconds. This alarm is generated when the HetuEngine service is unavailable.This alarm is cleared when the HetuE", "doc_type":"alarm", "kw":"ALM-45000 HetuEngine Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14408,7 +14476,7 @@ "uri":"ALM-45001.html", "node_id":"alm-45001.xml", "product_code":"mrs", - "code":"784", + "code":"788", "des":"This alarm applies only to MRS 3.2.0-LTS.2 or later.The system checks the HetuEngine compute instance status every 60 seconds. This alarm is generated when a HetuEngine c", "doc_type":"alarm", "kw":"ALM-45001 Faulty HetuEngine Compute Instances,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14426,7 +14494,7 @@ "uri":"ALM-45175.html", "node_id":"alm-45175.xml", "product_code":"mrs", - "code":"785", + "code":"789", "des":"The system checks whether the average duration for calling OBS metadata APIs is greater than the threshold every 30 seconds. This alarm is generated when the number of co", "doc_type":"alarm", "kw":"ALM-45175 Average Time for Calling OBS Metadata APIs Is Greater than the Threshold,Alarm Reference (", @@ -14444,7 +14512,7 @@ "uri":"ALM-45176.html", "node_id":"alm-45176.xml", "product_code":"mrs", - "code":"786", + "code":"790", "des":"The system checks whether the success rate of calling OBS metadata APIs is lower than the threshold every 30 seconds. This alarm is generated when the success rate is low", "doc_type":"alarm", "kw":"ALM-45176 Success Rate of Calling OBS Metadata APIs Is Lower than the Threshold,Alarm Reference (App", @@ -14462,7 +14530,7 @@ "uri":"ALM-45177.html", "node_id":"alm-45177.xml", "product_code":"mrs", - "code":"787", + "code":"791", "des":"The system checks whether the success rate of calling APIs for reading OBS data is lower than the threshold every 30 seconds. This alarm is generated when the success rat", "doc_type":"alarm", "kw":"ALM-45177 Success Rate of Calling OBS Data Read APIs Is Lower than the Threshold,Alarm Reference (Ap", @@ -14480,7 +14548,7 @@ "uri":"ALM-45178.html", "node_id":"alm-45178.xml", "product_code":"mrs", - "code":"788", + "code":"792", "des":"The system checks whether the success rate of calling APIs for writing OBS data is lower than the threshold every 30 seconds. This alarm is generated when the success rat", "doc_type":"alarm", "kw":"ALM-45178 Success Rate of Calling OBS Data Write APIs Is Lower Than the Threshold,Alarm Reference (A", @@ -14498,7 +14566,7 @@ "uri":"ALM-45179.html", "node_id":"alm-45179.xml", "product_code":"mrs", - "code":"789", + "code":"793", "des":"The system checks whether the number of failed OBS readFully API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of failed API calls", "doc_type":"usermanual", "kw":"ALM-45179 Number of Failed OBS readFully API Calls Exceeds the Threshold,Alarm Reference (Applicable", @@ -14516,7 +14584,7 @@ "uri":"ALM-45180.html", "node_id":"alm-45180.xml", "product_code":"mrs", - "code":"790", + "code":"794", "des":"The system checks whether the number of failed OBS read API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of failed API calls exce", "doc_type":"usermanual", "kw":"ALM-45180 Number of Failed OBS read API Calls Exceeds the Threshold,Alarm Reference (Applicable to M", @@ -14534,7 +14602,7 @@ "uri":"ALM-45181.html", "node_id":"alm-45181.xml", "product_code":"mrs", - "code":"791", + "code":"795", "des":"The system checks whether the number of failed OBS write API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of failed API calls exc", "doc_type":"usermanual", "kw":"ALM-45181 Number of Failed OBS write API Calls Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -14552,7 +14620,7 @@ "uri":"ALM-45182.html", "node_id":"alm-45182.xml", "product_code":"mrs", - "code":"792", + "code":"796", "des":"The system checks whether the number of throttled OBS operations exceeds the threshold every 30 seconds. This alarm is generated when the number of throttled OBS operatio", "doc_type":"usermanual", "kw":"ALM-45182 Number of Throttled OBS Operations Exceeds the Threshold,Alarm Reference (Applicable to MR", @@ -14570,7 +14638,7 @@ "uri":"ALM-45275.html", "node_id":"alm-45275.xml", "product_code":"mrs", - "code":"793", + "code":"797", "des":"The alarm module checks the Ranger service status every 180 seconds. This alarm is generated if the Ranger service is abnormal.This alarm is cleared after the Ranger serv", "doc_type":"alarm", "kw":"ALM-45275 Ranger Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14588,7 +14656,7 @@ "uri":"ALM-45276.html", "node_id":"alm-45276.xml", "product_code":"mrs", - "code":"794", + "code":"798", "des":"The alarm module checks the RangerAdmin service status every 60 seconds. This alarm is generated if RangerAdmin is unavailable.This alarm is automatically cleared after t", "doc_type":"alarm", "kw":"ALM-45276 Abnormal RangerAdmin Status,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14606,7 +14674,7 @@ "uri":"ALM-45277.html", "node_id":"alm-45277.xml", "product_code":"mrs", - "code":"795", + "code":"799", "des":"The system checks the heap memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the system detects that the heap memory usage of the Ran", "doc_type":"alarm", "kw":"ALM-45277 RangerAdmin Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -14624,7 +14692,7 @@ "uri":"ALM-45278.html", "node_id":"alm-45278.xml", "product_code":"mrs", - "code":"796", + "code":"800", "des":"The system checks the direct memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the direct memory usage of the RangerAdmin instance ex", "doc_type":"alarm", "kw":"ALM-45278 RangerAdmin Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", @@ -14642,7 +14710,7 @@ "uri":"ALM-45279.html", "node_id":"alm-45279.xml", "product_code":"mrs", - "code":"797", + "code":"801", "des":"The system checks the non-heap memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the non-heap memory usage of the RangerAdmin instanc", "doc_type":"alarm", "kw":"ALM-45279 RangerAdmin Non Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -14660,7 +14728,7 @@ "uri":"ALM-45280.html", "node_id":"alm-45280.xml", "product_code":"mrs", - "code":"798", + "code":"802", "des":"The system checks the GC duration of the RangerAdmin process every 60 seconds. This alarm is generated when the GC duration of the RangerAdmin process exceeds the thresho", "doc_type":"alarm", "kw":"ALM-45280 RangerAdmin GC Duration Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -14678,7 +14746,7 @@ "uri":"ALM-45281.html", "node_id":"alm-45281.xml", "product_code":"mrs", - "code":"799", + "code":"803", "des":"The system checks the heap memory usage of the UserSync service every 60 seconds. This alarm is generated when the system detects that the heap memory usage of the UserSy", "doc_type":"alarm", "kw":"ALM-45281 UserSync Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),U", @@ -14696,7 +14764,7 @@ "uri":"ALM-45282.html", "node_id":"alm-45282.xml", "product_code":"mrs", - "code":"800", + "code":"804", "des":"The system checks the direct memory usage of the UserSync service every 60 seconds. This alarm is generated when the direct memory usage of the UserSync instance exceeds ", "doc_type":"alarm", "kw":"ALM-45282 UserSync Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -14714,7 +14782,7 @@ "uri":"ALM-45283.html", "node_id":"alm-45283.xml", "product_code":"mrs", - "code":"801", + "code":"805", "des":"The system checks the non-heap memory usage of the UserSync service every 60 seconds. This alarm is generated when the non-heap memory usage of the UserSync instance exce", "doc_type":"alarm", "kw":"ALM-45283 UserSync Non Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.", @@ -14732,7 +14800,7 @@ "uri":"ALM-45284.html", "node_id":"alm-45284.xml", "product_code":"mrs", - "code":"802", + "code":"806", "des":"The system checks the GC duration of the UserSync process every 60 seconds. This alarm is generated when the GC duration of the UserSync process exceeds the threshold (12", "doc_type":"alarm", "kw":"ALM-45284 UserSync Garbage Collection (GC) Time Exceeds the Threshold,Alarm Reference (Applicable to", @@ -14750,7 +14818,7 @@ "uri":"ALM-45285.html", "node_id":"alm-45285.xml", "product_code":"mrs", - "code":"803", + "code":"807", "des":"The system checks the heap memory usage of the TagSync service every 60 seconds. This alarm is generated when the heap memory usage of the TagSync instance exceeds the th", "doc_type":"alarm", "kw":"ALM-45285 TagSync Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Us", @@ -14768,7 +14836,7 @@ "uri":"ALM-45286.html", "node_id":"alm-45286.xml", "product_code":"mrs", - "code":"804", + "code":"808", "des":"The system checks the direct memory usage of the TagSync service every 60 seconds. This alarm is generated when the direct memory usage of the TagSync instance exceeds th", "doc_type":"alarm", "kw":"ALM-45286 TagSync Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", @@ -14786,7 +14854,7 @@ "uri":"ALM-45287.html", "node_id":"alm-45287.xml", "product_code":"mrs", - "code":"805", + "code":"809", "des":"The system checks the non-heap memory usage of the TagSync service every 60 seconds. This alarm is generated when the non-heap memory usage of the TagSync instance exceed", "doc_type":"alarm", "kw":"ALM-45287 TagSync Non Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -14804,7 +14872,7 @@ "uri":"ALM-45288.html", "node_id":"alm-45288.xml", "product_code":"mrs", - "code":"806", + "code":"810", "des":"The system checks the GC duration of the TagSync process every 60 seconds. This alarm is generated when the GC duration of the TagSync process exceeds the threshold (12 s", "doc_type":"alarm", "kw":"ALM-45288 TagSync Garbage Collection (GC) Time Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -14822,7 +14890,7 @@ "uri":"ALM-45425.html", "node_id":"alm-45425.xml", "product_code":"mrs", - "code":"807", + "code":"811", "des":"The alarm module checks the ClickHouse instance status every 60 seconds. This alarm is generated when the alarm module detects that all ClickHouse instances are abnormal.", "doc_type":"alarm", "kw":"ALM-45425 ClickHouse Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14840,7 +14908,7 @@ "uri":"ALM-45426.html", "node_id":"alm-45426.xml", "product_code":"mrs", - "code":"808", + "code":"812", "des":"The alarm module checks the quota usage of the ClickHouse service in the ZooKeeper every 60 seconds. This alarm is generated when the alarm module detects that the usage ", "doc_type":"alarm", "kw":"ALM-45426 ClickHouse Service Quantity Quota Usage in ZooKeeper Exceeds the Threshold,Alarm Reference", @@ -14858,7 +14926,7 @@ "uri":"ALM-45427.html", "node_id":"alm-45427.xml", "product_code":"mrs", - "code":"809", + "code":"813", "des":"The alarm module checks the quota usage of the ClickHouse service in the ZooKeeper every 60 seconds. This alarm is generated when the alarm module detects that the usage ", "doc_type":"alarm", "kw":"ALM-45427 ClickHouse Service Capacity Quota Usage in ZooKeeper Exceeds the Threshold,Alarm Reference", @@ -14876,7 +14944,7 @@ "uri":"ALM-45428.html", "node_id":"alm-45428.xml", "product_code":"mrs", - "code":"810", + "code":"814", "des":"This alarm is generated when the alarm module detects EIO or EROFS errors during ClickHouse read and write every 60 seconds.ClickHouse fails to read and write data. The I", "doc_type":"alarm", "kw":"ALM-45428 ClickHouse Disk I/O Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14894,7 +14962,7 @@ "uri":"ALM-45429.html", "node_id":"alm-45429.xml", "product_code":"mrs", - "code":"811", + "code":"815", "des":"This section applies only to MRS 3.1.2-LTS.6 or later.This alarm is generated when the local table corresponding to the distributed table fails to be created during Click", "doc_type":"alarm", "kw":"ALM-45429 Table Metadata Synchronization Failed on the Added ClickHouse Node,Alarm Reference (Applic", @@ -14912,7 +14980,7 @@ "uri":"ALM-45430.html", "node_id":"alm-45430.xml", "product_code":"mrs", - "code":"812", + "code":"816", "des":"This section applies only to MRS 3.1.2-LTS.6 or later.This alarm is generated when user and permission information fails to be synchronized during ClickHouse capacity exp", "doc_type":"alarm", "kw":"ALM-45430 Permission Metadata Synchronization Failed on the Added ClickHouse Node,Alarm Reference (A", @@ -14930,7 +14998,7 @@ "uri":"ALM-45431.html", "node_id":"alm-45431.xml", "product_code":"mrs", - "code":"813", + "code":"817", "des":"The ClickHouseServer instance distribution does not meet the topology allocation requirements.Some ClickHouseServer instances are unavailable.During installation or capac", "doc_type":"usermanual", "kw":"ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation,Alarm Reference (Applica", @@ -14948,7 +15016,7 @@ "uri":"ALM-45432.html", "node_id":"alm-45432.xml", "product_code":"mrs", - "code":"814", + "code":"818", "des":"The system checks the status of the ClickHouse user role synchronization process every 5 minutes. This alarm is generated when the system detects that the ClickHouse user", "doc_type":"usermanual", "kw":"ALM-45432 ClickHouse User Synchronization Process Fails,Alarm Reference (Applicable to MRS 3.x),User", @@ -14966,7 +15034,7 @@ "uri":"ALM-45433.html", "node_id":"alm-45433.xml", "product_code":"mrs", - "code":"815", + "code":"819", "des":"If the cross-AZ HA function is enabled for a cluster where ClickHouse has been deployed, the ClickHouse topology remains unchanged. This alarm is generated when the cross", "doc_type":"usermanual", "kw":"ALM-45433 ClickHouse AZ Topology Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14984,7 +15052,7 @@ "uri":"ALM-45434.html", "node_id":"alm-45434.xml", "product_code":"mrs", - "code":"816", + "code":"820", "des":"This alarm is generated when a single replica is detected in a custom logical cluster after the custom logical cluster is enabled for ClickHouse.This alarm is automatical", "doc_type":"usermanual", "kw":"ALM-45434 A Single Replica Exists in the ClickHouse Data Table,Alarm Reference (Applicable to MRS 3.", @@ -15002,7 +15070,7 @@ "uri":"ALM-45585.html", "node_id":"alm-45585.xml", "product_code":"mrs", - "code":"817", + "code":"821", "des":"The system checks the IoTDB service status every 300 seconds. This alarm is generated when the IoTDB service is unavailable. This alarm is cleared when the IoTDB service ", "doc_type":"alarm", "kw":"ALM-45585 IoTDB Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -15020,7 +15088,7 @@ "uri":"ALM-45586.html", "node_id":"alm-45586.xml", "product_code":"mrs", - "code":"818", + "code":"822", "des":"The system checks the IoTDBServer process status every 60 seconds. The alarm is generated when the heap memory usage of the IoTDBServer process exceeds the threshold (90%", "doc_type":"alarm", "kw":"ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -15038,7 +15106,7 @@ "uri":"ALM-45587.html", "node_id":"alm-45587.xml", "product_code":"mrs", - "code":"819", + "code":"823", "des":"The system checks the GC duration of the IoTDBServer process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seconds by default) ", "doc_type":"alarm", "kw":"ALM-45587 IoTDBServer GC Duration Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -15056,7 +15124,7 @@ "uri":"ALM-45588.html", "node_id":"alm-45588.xml", "product_code":"mrs", - "code":"820", + "code":"824", "des":"The system checks the direct memory usage of the IoTDBServer service every 60 seconds. This alarm is generated when the direct memory usage of the IoTDBServer instance ex", "doc_type":"alarm", "kw":"ALM-45588 IoTDBServer Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", @@ -15074,7 +15142,7 @@ "uri":"ALM-45589.html", "node_id":"alm-45589.xml", "product_code":"mrs", - "code":"821", + "code":"825", "des":"The system checks the heap memory usage of the ConfigNode process every 60 seconds. This alarm is generated when the heap memory usage of the ConfigNode process exceeds t", "doc_type":"alarm", "kw":"ALM-45589 ConfigNode Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -15092,7 +15160,7 @@ "uri":"ALM-45590.html", "node_id":"alm-45590.xml", "product_code":"mrs", - "code":"822", + "code":"826", "des":"The system checks the GC duration of the ConfigNode process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seconds by default) f", "doc_type":"usermanual", "kw":"ALM-45590 ConfigNode GC Duration Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User ", @@ -15110,7 +15178,7 @@ "uri":"ALM-45591.html", "node_id":"alm-45591.xml", "product_code":"mrs", - "code":"823", + "code":"827", "des":"The system checks the direct memory usage of the ConfigNode process every 60 seconds. This alarm is generated when the direct memory usage of the ConfigNode exceeds the t", "doc_type":"usermanual", "kw":"ALM-45591 ConfigNode Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.", @@ -15128,7 +15196,7 @@ "uri":"ALM-45592.html", "node_id":"alm-45592.xml", "product_code":"mrs", - "code":"824", + "code":"828", "des":"The system checks the RPC execution duration of the IoTDBServer process every 60 seconds. This alarm is generated when the execution duration exceeds the threshold. This ", "doc_type":"usermanual", "kw":"ALM-45592 IoTDBServer RPC Execution Duration Exceeds the Threshold,Alarm Reference (Applicable to MR", @@ -15146,7 +15214,7 @@ "uri":"ALM-45593.html", "node_id":"alm-45593.xml", "product_code":"mrs", - "code":"825", + "code":"829", "des":"This alarm is generated when the data flush duration exceeds the threshold. This alarm is cleared when the flush duration is less than the threshold.Data write is blocked", "doc_type":"usermanual", "kw":"ALM-45593 IoTDBServer Flush Execution Duration Exceeds the Threshold,Alarm Reference (Applicable to ", @@ -15164,7 +15232,7 @@ "uri":"ALM-45594.html", "node_id":"alm-45594.xml", "product_code":"mrs", - "code":"826", + "code":"830", "des":"This alarm is generated when the merge duration in the space exceeds the threshold. This alarm is cleared when the merge duration in the space is less than the threshold.", "doc_type":"usermanual", "kw":"ALM-45594 IoTDBServer Intra-Space Merge Duration Exceeds the Threshold,Alarm Reference (Applicable t", @@ -15182,7 +15250,7 @@ "uri":"ALM-45595.html", "node_id":"alm-45595.xml", "product_code":"mrs", - "code":"827", + "code":"831", "des":"This alarm is generated when the cross-space merge duration exceeds the threshold. This alarm is cleared when the cross-space merge duration is less than the threshold.Da", "doc_type":"usermanual", "kw":"ALM-45595 IoTDBServer Cross-Space Merge Duration Exceeds the Threshold,Alarm Reference (Applicable t", @@ -15200,7 +15268,7 @@ "uri":"ALM-45615.html", "node_id":"alm-45615.xml", "product_code":"mrs", - "code":"828", + "code":"832", "des":"The system checks the CDL health status every 60 seconds. This alarm is generated when the CDL health status is DOWN. This alarm is cleared when the system detects that t", "doc_type":"alarm", "kw":"ALM-45615 CDL Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -15218,7 +15286,7 @@ "uri":"ALM-45616.html", "node_id":"alm-45616.xml", "product_code":"mrs", - "code":"829", + "code":"833", "des":"The system checks whether a CDL job is normal every 60 seconds. This alarm is reported when the CDL job is abnormal. This alarm is cleared when the job is restored or sto", "doc_type":"usermanual", "kw":"ALM-45616 CDL Job Execution Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -15236,7 +15304,7 @@ "uri":"ALM-45617.html", "node_id":"alm-45617.xml", "product_code":"mrs", - "code":"830", + "code":"834", "des":"If a large number of write-ahead logs (WALs) are stacked in the PostgreSQL database, the PostgreSQL disk space may be used up. The system checks whether the amount of dat", "doc_type":"usermanual", "kw":"ALM-45617 Data Queued in the CDL Replication Slot Exceeds the Threshold,Alarm Reference (Applicable ", @@ -15254,7 +15322,7 @@ "uri":"ALM-45635.html", "node_id":"alm-45635.xml", "product_code":"mrs", - "code":"831", + "code":"835", "des":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks whether FlinkServer jobs fail to be executed every 10 seconds. This alarm is generated when a FlinkServ", "doc_type":"alarm", "kw":"ALM-45635 FlinkServer Job Execution Failure,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -15272,7 +15340,7 @@ "uri":"ALM-45636.html", "node_id":"alm-45636.xml", "product_code":"mrs", - "code":"832", + "code":"836", "des":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks the number of consecutive checkpoint failures based on the configured alarm checking interval. This ala", "doc_type":"alarm", "kw":"ALM-45636 FlinkServer Job Checkpoints Keep Failing,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -15290,7 +15358,7 @@ "uri":"ALM-45636-1.html", "node_id":"alm-45636-1.xml", "product_code":"mrs", - "code":"833", + "code":"837", "des":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks the number of consecutive checkpoint failures based on the configured alarm checking interval. This ala", "doc_type":"alarm", "kw":"ALM-45636 Flink Job Checkpoints Keep Failing,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -15308,7 +15376,7 @@ "uri":"ALM-45637.html", "node_id":"alm-45637.xml", "product_code":"mrs", - "code":"834", + "code":"838", "des":"This section applies to MRS 3.1.2-LTS.6 or later.The system checks the back pressure duration of FlinkServer tasks based on the configured alarm checking interval. This a", "doc_type":"alarm", "kw":"ALM-45637 FlinkServer Task Is Continuously Under Back Pressure,Alarm Reference (Applicable to MRS 3.", @@ -15326,7 +15394,7 @@ "uri":"ALM-45638.html", "node_id":"alm-45638.xml", "product_code":"mrs", - "code":"835", + "code":"839", "des":"This section applies to MRS 3.1.2-LTS.6 or later.The system checks the number of FlinkServer job restarts based on the alarm checking interval. This alarm is generated wh", "doc_type":"alarm", "kw":"ALM-45638 Number of Restarts After FlinkServer Job Failures Exceeds the Threshold,Alarm Reference (A", @@ -15344,7 +15412,7 @@ "uri":"ALM-45638-1.html", "node_id":"alm-45638-1.xml", "product_code":"mrs", - "code":"836", + "code":"840", "des":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks the number of Flink job restarts based on the alarm checking interval. This alarm is generated when the", "doc_type":"alarm", "kw":"ALM-45638 Number of Restarts After Flink Job Failures Exceeds the Threshold,Alarm Reference (Applica", @@ -15362,7 +15430,7 @@ "uri":"ALM-45640.html", "node_id":"alm-45640.xml", "product_code":"mrs", - "code":"837", + "code":"841", "des":"This section applies to MRS 3.2.0-LTS.2 or later.This alarm is generated when the FlinkServer active node or standby node does not receive heartbeat messages from the pee", "doc_type":"alarm", "kw":"ALM-45640 FlinkServer Heartbeat Interruption Between the Active and Standby Nodes,Alarm Reference (A", @@ -15380,7 +15448,7 @@ "uri":"ALM-45641.html", "node_id":"alm-45641.xml", "product_code":"mrs", - "code":"838", + "code":"842", "des":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks data synchronization between the active and standby FlinkServer nodes every 60 seconds. This alarm is g", "doc_type":"alarm", "kw":"ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes,Alarm Refe", @@ -15398,7 +15466,7 @@ "uri":"mrs_01_0648.html", "node_id":"mrs_01_0648.xml", "product_code":"mrs", - "code":"839", + "code":"843", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"MRS Manager Operation Guide (Applicable to 2.x and Earlier Versions)", @@ -15417,7 +15485,7 @@ "uri":"mrs_01_0101.html", "node_id":"mrs_01_0101.xml", "product_code":"mrs", - "code":"840", + "code":"844", "des":"MRS manages and analyzes massive data and helps you rapidly obtain desired data from structured and unstructured data. The structure of open-source components is complex.", "doc_type":"usermanual", "kw":"Introduction to MRS Manager,MRS Manager Operation Guide (Applicable to 2.x and Earlier Versions),Use", @@ -15437,7 +15505,7 @@ "uri":"mrs_01_0105.html", "node_id":"mrs_01_0105.xml", "product_code":"mrs", - "code":"841", + "code":"845", "des":"When you perform operations on MRS Manager to trigger a task, the task execution process and progress are displayed. After the task window is closed, you need to open the", "doc_type":"usermanual", "kw":"Checking Running Tasks,MRS Manager Operation Guide (Applicable to 2.x and Earlier Versions),User Gui", @@ -15456,7 +15524,7 @@ "uri":"mrs_01_0106.html", "node_id":"mrs_01_0106.xml", "product_code":"mrs", - "code":"842", + "code":"846", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitoring Management", @@ -15475,7 +15543,7 @@ "uri":"mrs_01_0107.html", "node_id":"mrs_01_0107.xml", "product_code":"mrs", - "code":"843", + "code":"847", "des":"On MRS Manager, nodes in a cluster can be classified into management nodes, control nodes, and data nodes. The change trends of key host monitoring metrics on each type o", "doc_type":"usermanual", "kw":"Dashboard,Monitoring Management,User Guide", @@ -15494,7 +15562,7 @@ "uri":"mrs_01_0232.html", "node_id":"mrs_01_0232.xml", "product_code":"mrs", - "code":"844", + "code":"848", "des":"You can manage the following status and indicators of all services (including role instances) and hosts on the MRS Manager:Status information: includes operation, health,", "doc_type":"usermanual", "kw":"Managing Services and Monitoring Hosts,Monitoring Management,User Guide", @@ -15513,7 +15581,7 @@ "uri":"mrs_01_0233.html", "node_id":"mrs_01_0233.xml", "product_code":"mrs", - "code":"845", + "code":"849", "des":"On MRS Manager, you can query the top value curves, bottom value curves, or average data curves of key service and host monitoring metrics, that is, the resource distribu", "doc_type":"usermanual", "kw":"Managing Resource Distribution,Monitoring Management,User Guide", @@ -15531,7 +15599,7 @@ "uri":"mrs_01_0235.html", "node_id":"mrs_01_0235.xml", "product_code":"mrs", - "code":"846", + "code":"850", "des":"You can configure interconnection parameters on MRS Manager to save monitoring metric data to a specified FTP server using the FTP or SFTP protocol. In this way, MRS clus", "doc_type":"usermanual", "kw":"Configuring Monitoring Metric Dumping,Monitoring Management,User Guide", @@ -15551,7 +15619,7 @@ "uri":"mrs_01_0236.html", "node_id":"mrs_01_0236.xml", "product_code":"mrs", - "code":"847", + "code":"851", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarm Management", @@ -15570,7 +15638,7 @@ "uri":"mrs_01_0237.html", "node_id":"mrs_01_0237.xml", "product_code":"mrs", - "code":"848", + "code":"852", "des":"You can view and clear alarms on MRS Manager.Generally, the system automatically clears an alarm when the fault is rectified. If the fault has been rectified and the alar", "doc_type":"usermanual", "kw":"Viewing and Manually Clearing an Alarm,Alarm Management,User Guide", @@ -15589,7 +15657,7 @@ "uri":"mrs_01_0238.html", "node_id":"mrs_01_0238.xml", "product_code":"mrs", - "code":"849", + "code":"853", "des":"You can configure an alarm threshold to learn the metric health status. After Send Alarm is selected, the system sends an alarm message when the monitored data reaches th", "doc_type":"usermanual", "kw":"Configuring an Alarm Threshold,Alarm Management,User Guide", @@ -15608,7 +15676,7 @@ "uri":"mrs_01_0239.html", "node_id":"mrs_01_0239.xml", "product_code":"mrs", - "code":"850", + "code":"854", "des":"You can configure the northbound interface so that alarms generated on MRS Manager can be reported to your monitoring O&M system using Syslog.If the Syslog protocol is no", "doc_type":"usermanual", "kw":"Configuring Syslog Northbound Interface Parameters,Alarm Management,User Guide", @@ -15627,7 +15695,7 @@ "uri":"mrs_01_0240.html", "node_id":"mrs_01_0240.xml", "product_code":"mrs", - "code":"851", + "code":"855", "des":"You can configure the northbound interface so that alarms and monitoring metrics on MRS Manager can be integrated to the network management platform using SNMP.The ECS co", "doc_type":"usermanual", "kw":"Configuring SNMP Northbound Interface Parameters,Alarm Management,User Guide", @@ -15646,7 +15714,7 @@ "uri":"mrs_01_0241.html", "node_id":"mrs_01_0241.xml", "product_code":"mrs", - "code":"852", + "code":"856", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarm Reference (Applicable to Versions Earlier Than MRS 3.x)", @@ -15665,7 +15733,7 @@ "uri":"alm_12001.html", "node_id":"alm_12001.xml", "product_code":"mrs", - "code":"853", + "code":"857", "des":"Cluster audit logs need to be dumped on a third-party server due to the local historical data backup policy. Audit logs can be successfully dumped if the dump server meet", "doc_type":"usermanual", "kw":"ALM-12001 Audit Log Dump Failure,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User ", @@ -15685,7 +15753,7 @@ "uri":"alm_12002.html", "node_id":"alm_12002.xml", "product_code":"mrs", - "code":"854", + "code":"858", "des":"The high availability (HA) software periodically checks the WebService floating IP addresses and databases of Manager. This alarm is generated when the HA software detect", "doc_type":"usermanual", "kw":"ALM-12002 HA Resource Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User", @@ -15704,7 +15772,7 @@ "uri":"alm_12004.html", "node_id":"alm_12004.xml", "product_code":"mrs", - "code":"855", + "code":"859", "des":"This alarm is generated when the Ldap resource in Manager is abnormal.This alarm is cleared when the Ldap resource in Manager recovers and the alarm handling is complete.", "doc_type":"usermanual", "kw":"ALM-12004 OLdap Resource Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),U", @@ -15723,7 +15791,7 @@ "uri":"alm_12005.html", "node_id":"alm_12005.xml", "product_code":"mrs", - "code":"856", + "code":"860", "des":"The alarm module monitors the status of the Kerberos resource in Manager. This alarm is generated when the Kerberos resource is abnormal.This alarm is cleared when the al", "doc_type":"usermanual", "kw":"ALM-12005 OKerberos Resource Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than MRS 3.", @@ -15742,7 +15810,7 @@ "uri":"alm_12006.html", "node_id":"alm_12006.xml", "product_code":"mrs", - "code":"857", + "code":"861", "des":"Controller checks the NodeAgent status every 30 seconds. This alarm is generated when Controller fails to receive the status report of a NodeAgent for three consecutive t", "doc_type":"usermanual", "kw":"ALM-12006 Node Fault,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User Guide", @@ -15761,7 +15829,7 @@ "uri":"alm_12007.html", "node_id":"alm_12007.xml", "product_code":"mrs", - "code":"858", + "code":"862", "des":"The process health check module checks the process status every 5 seconds. This alarm is generated when the process health check module detects that the process connectio", "doc_type":"usermanual", "kw":"ALM-12007 Process Fault,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User Guide", @@ -15780,7 +15848,7 @@ "uri":"alm_12010.html", "node_id":"alm_12010.xml", "product_code":"mrs", - "code":"859", + "code":"863", "des":"This alarm is generated when the active Manager does not receive any heartbeat signal from the standby Manager within 7 seconds.This alarm is cleared when the active Mana", "doc_type":"usermanual", "kw":"ALM-12010 Manager Heartbeat Interruption Between the Active and Standby Nodes,Alarm Reference (Appli", @@ -15800,7 +15868,7 @@ "uri":"alm_12011.html", "node_id":"alm_12011.xml", "product_code":"mrs", - "code":"860", + "code":"864", "des":"This alarm is generated when the standby Manager fails to synchronize files with the active Manager.This alarm is cleared when the standby Manager synchronizes files with", "doc_type":"usermanual", "kw":"ALM-12011 Data Synchronization Exception Between the Active and Standby Manager Nodes,Alarm Referenc", @@ -15819,7 +15887,7 @@ "uri":"alm_12012.html", "node_id":"alm_12012.xml", "product_code":"mrs", - "code":"861", + "code":"865", "des":"This alarm is generated when the NTP service on the current node fails to synchronize time with the NTP service on the active OMS node.This alarm is cleared when the NTP ", "doc_type":"usermanual", "kw":"ALM-12012 NTP Service Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User", @@ -15839,7 +15907,7 @@ "uri":"alm_12016.html", "node_id":"alm_12016.xml", "product_code":"mrs", - "code":"862", + "code":"866", "des":"The system checks the CPU usage every 30 seconds and compares the check result with the default threshold. The CPU usage has a default threshold. This alarm is generated ", "doc_type":"usermanual", "kw":"ALM-12016 CPU Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier Than MRS 3", @@ -15858,7 +15926,7 @@ "uri":"alm_12017.html", "node_id":"alm_12017.xml", "product_code":"mrs", - "code":"863", + "code":"867", "des":"The system checks the host disk usage every 30 seconds and compares the actual disk usage with the threshold. The disk usage has a default threshold. This alarm is genera", "doc_type":"usermanual", "kw":"ALM-12017 Insufficient Disk Capacity,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),U", @@ -15877,7 +15945,7 @@ "uri":"alm_12018.html", "node_id":"alm_12018.xml", "product_code":"mrs", - "code":"864", + "code":"868", "des":"The system checks the memory usage every 30 seconds and compares the actual memory usage with the threshold. The memory usage has a default threshold. This alarm is gener", "doc_type":"usermanual", "kw":"ALM-12018 Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier Than MR", @@ -15896,7 +15964,7 @@ "uri":"alm_12027.html", "node_id":"alm_12027.xml", "product_code":"mrs", - "code":"865", + "code":"869", "des":"The system checks the PID usage every 30 seconds and compares the actual PID usage with the default threshold. This alarm is generated when the PID usage exceeds the thre", "doc_type":"usermanual", "kw":"ALM-12027 Host PID Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier Than ", @@ -15916,7 +15984,7 @@ "uri":"alm_12028.html", "node_id":"alm_12028.xml", "product_code":"mrs", - "code":"866", + "code":"870", "des":"The system periodically checks the number of D state processes of user omm on the host every 30 seconds and compares the number with the threshold. The number of processe", "doc_type":"usermanual", "kw":"ALM-12028 Number of Processes in the D State on the Host Exceeds the Threshold,Alarm Reference (Appl", @@ -15935,7 +16003,7 @@ "uri":"alm_12031.html", "node_id":"alm_12031.xml", "product_code":"mrs", - "code":"867", + "code":"871", "des":"The system starts at 00:00 every day to check whether user omm and the password are about to expire every eight hours. This alarm is generated if the user or password is ", "doc_type":"usermanual", "kw":"ALM-12031 User omm or Password Is About to Expire,Alarm Reference (Applicable to Versions Earlier Th", @@ -15954,7 +16022,7 @@ "uri":"alm_12032.html", "node_id":"alm_12032.xml", "product_code":"mrs", - "code":"868", + "code":"872", "des":"The system starts at 00:00 every day to check whether user ommdba and the password are about to expire every eight hours. This alarm is generated if the user or password ", "doc_type":"usermanual", "kw":"ALM-12032 User ommdba or Password Is About to Expire,Alarm Reference (Applicable to Versions Earlier", @@ -15973,7 +16041,7 @@ "uri":"alm_12033.html", "node_id":"alm_12033.xml", "product_code":"mrs", - "code":"869", + "code":"873", "des":"The system runs the iostat command every second to monitor the disk I/O indicator. If there are more than 30 times that the svctm value is greater than 100 ms in 60 secon", "doc_type":"usermanual", "kw":"ALM-12033 Slow Disk Fault,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User Guide", @@ -15992,7 +16060,7 @@ "uri":"alm_12034.html", "node_id":"alm_12034.xml", "product_code":"mrs", - "code":"870", + "code":"874", "des":"This alarm is generated when a periodic backup task fails to be executed. This alarm is cleared when the next backup task is executed successfully.No backup package is av", "doc_type":"usermanual", "kw":"ALM-12034 Periodic Backup Failure,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User", @@ -16012,7 +16080,7 @@ "uri":"alm_12035.html", "node_id":"alm_12035.xml", "product_code":"mrs", - "code":"871", + "code":"875", "des":"If a recovery task fails, the system attempts to automatically roll back. If the rollback fails, data may be lost. If this occurs, an alarm is reported. This alarm is cle", "doc_type":"usermanual", "kw":"ALM-12035 Unknown Data Status After Recovery Task Failure,Alarm Reference (Applicable to Versions Ea", @@ -16032,7 +16100,7 @@ "uri":"alm_12037.html", "node_id":"alm_12037.xml", "product_code":"mrs", - "code":"872", + "code":"876", "des":"This alarm is generated when the NTP server is abnormal.This alarm is cleared when the NTP server recovers.The NTP server configured on the active OMS node is abnormal. I", "doc_type":"usermanual", "kw":"ALM-12037 NTP Server Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User ", @@ -16051,7 +16119,7 @@ "uri":"alm_12038.html", "node_id":"alm_12038.xml", "product_code":"mrs", - "code":"873", + "code":"877", "des":"This alarm is generated when dumping fails after monitoring indicator dumping is configured on MRS Manager.This alarm is cleared when dumping is successful.The upper-laye", "doc_type":"usermanual", "kw":"ALM-12038 Monitoring Indicator Dump Failure,Alarm Reference (Applicable to Versions Earlier Than MRS", @@ -16070,7 +16138,7 @@ "uri":"alm_12039.html", "node_id":"alm_12039.xml", "product_code":"mrs", - "code":"874", + "code":"878", "des":"The system checks the data synchronization status between the active and standby GaussDB nodes every 10 seconds. This alarm is generated when the synchronization status c", "doc_type":"usermanual", "kw":"ALM-12039 GaussDB Data Is Not Synchronized,Alarm Reference (Applicable to Versions Earlier Than MRS ", @@ -16089,7 +16157,7 @@ "uri":"alm_12040.html", "node_id":"alm_12040.xml", "product_code":"mrs", - "code":"875", + "code":"879", "des":"The system checks the entropy at 00:00:00 every day and performs five consecutive checks each time. First, the system checks whether the rng-tools tool is enabled and cor", "doc_type":"usermanual", "kw":"ALM-12040 Insufficient System Entropy,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),", @@ -16108,7 +16176,7 @@ "uri":"alm_13000.html", "node_id":"alm_13000.xml", "product_code":"mrs", - "code":"876", + "code":"880", "des":"The system checks the ZooKeeper service status every 30 seconds. This alarm is generated when the ZooKeeper service is unavailable.This alarm is cleared when the ZooKeepe", "doc_type":"usermanual", "kw":"ALM-13000 ZooKeeper Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x", @@ -16127,7 +16195,7 @@ "uri":"alm_13001.html", "node_id":"alm_13001.xml", "product_code":"mrs", - "code":"877", + "code":"881", "des":"The system checks ZooKeeper connections every 30 seconds. This alarm is generated when the system detects that the number of used ZooKeeper instance connections exceeds t", "doc_type":"usermanual", "kw":"ALM-13001 Available ZooKeeper Connections Are Insufficient,Alarm Reference (Applicable to Versions E", @@ -16146,7 +16214,7 @@ "uri":"alm_13002.html", "node_id":"alm_13002.xml", "product_code":"mrs", - "code":"878", + "code":"882", "des":"The system checks the ZooKeeper service status every 30 seconds. The alarm is generated when the memory usage of a ZooKeeper instance exceeds the threshold (80% of the ma", "doc_type":"usermanual", "kw":"ALM-13002 ZooKeeper Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earli", @@ -16166,7 +16234,7 @@ "uri":"alm_14000.html", "node_id":"alm_14000.xml", "product_code":"mrs", - "code":"879", + "code":"883", "des":"The system checks the service status of NameService every 30 seconds. This alarm is generated when the system considers that the HDFS service is unavailable because all t", "doc_type":"usermanual", "kw":"ALM-14000 HDFS Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Use", @@ -16185,7 +16253,7 @@ "uri":"alm_14001.html", "node_id":"alm_14001.xml", "product_code":"mrs", - "code":"880", + "code":"884", "des":"The system checks the disk usage of the HDFS cluster every 30 seconds and compares the actual disk usage with the threshold. The HDFS cluster disk usage indicator has a d", "doc_type":"usermanual", "kw":"ALM-14001 HDFS Disk Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier Than", @@ -16204,7 +16272,7 @@ "uri":"alm_14002.html", "node_id":"alm_14002.xml", "product_code":"mrs", - "code":"881", + "code":"885", "des":"The system checks the DataNode disk usage every 30 seconds and compares the actual disk usage with the threshold. The Percentage of DataNode Capacity indicator has a defa", "doc_type":"usermanual", "kw":"ALM-14002 DataNode Disk Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier ", @@ -16223,7 +16291,7 @@ "uri":"alm_14003.html", "node_id":"alm_14003.xml", "product_code":"mrs", - "code":"882", + "code":"886", "des":"The system checks the number of lost blocks every 30 seconds and compares the number of lost blocks with the threshold. The lost blocks indicator has a default threshold.", "doc_type":"usermanual", "kw":"ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold,Alarm Reference (Applicable to Versions E", @@ -16242,7 +16310,7 @@ "uri":"alm_14004.html", "node_id":"alm_14004.xml", "product_code":"mrs", - "code":"883", + "code":"887", "des":"The system checks the number of damaged blocks every 30 seconds and compares the number of damaged blocks with the threshold. The damaged blocks indicator has a default t", "doc_type":"usermanual", "kw":"ALM-14004 Number of Damaged HDFS Blocks Exceeds the Threshold,Alarm Reference (Applicable to Version", @@ -16261,7 +16329,7 @@ "uri":"alm_14006.html", "node_id":"alm_14006.xml", "product_code":"mrs", - "code":"884", + "code":"888", "des":"The system periodically checks the number of HDFS files every 30 seconds and compares the number of HDFS files with the threshold. This alarm is generated when the system", "doc_type":"usermanual", "kw":"ALM-14006 Number of HDFS Files Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier", @@ -16280,7 +16348,7 @@ "uri":"alm_14007.html", "node_id":"alm_14007.xml", "product_code":"mrs", - "code":"885", + "code":"889", "des":"The system checks the HDFS NameNode memory usage every 30 seconds and compares the actual memory usage with the threshold. The HDFS NameNode memory usage has a default th", "doc_type":"usermanual", "kw":"ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions E", @@ -16299,7 +16367,7 @@ "uri":"alm_14008.html", "node_id":"alm_14008.xml", "product_code":"mrs", - "code":"886", + "code":"890", "des":"The system checks the HDFS DataNode memory usage every 30 seconds and compares the actual memory usage with the threshold. The HDFS DataNode memory usage has a default th", "doc_type":"usermanual", "kw":"ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions E", @@ -16318,7 +16386,7 @@ "uri":"alm_14009.html", "node_id":"alm_14009.xml", "product_code":"mrs", - "code":"887", + "code":"891", "des":"The system periodically checks the number of faulty DataNodes in the HDFS cluster every 30 seconds, and compares the number with the threshold. The number of faulty DataN", "doc_type":"usermanual", "kw":"ALM-14009 Number of Faulty DataNodes Exceeds the Threshold,Alarm Reference (Applicable to Versions E", @@ -16337,7 +16405,7 @@ "uri":"alm_14010.html", "node_id":"alm_14010.xml", "product_code":"mrs", - "code":"888", + "code":"892", "des":"The system checks the NameService service status every 180 seconds. This alarm is generated when the NameService service is unavailable.This alarm is cleared when the Nam", "doc_type":"usermanual", "kw":"ALM-14010 NameService Service Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than MRS 3", @@ -16356,7 +16424,7 @@ "uri":"alm_14011.html", "node_id":"alm_14011.xml", "product_code":"mrs", - "code":"889", + "code":"893", "des":"The DataNode parameter dfs.datanode.data.dir specifies the DataNode data directory. This alarm is generated in any of the following scenarios:A configured data directory ", "doc_type":"usermanual", "kw":"ALM-14011 HDFS DataNode Data Directory Is Not Configured Properly,Alarm Reference (Applicable to Ver", @@ -16375,7 +16443,7 @@ "uri":"alm_14012.html", "node_id":"alm_14012.xml", "product_code":"mrs", - "code":"890", + "code":"894", "des":"On the active NameNode, the system checks data synchronization on all JournalNodes in the cluster every 5 minutes. This alarm is generated when data on a JournalNode is n", "doc_type":"usermanual", "kw":"ALM-14012 HDFS JournalNode Data Is Not Synchronized,Alarm Reference (Applicable to Versions Earlier ", @@ -16394,7 +16462,7 @@ "uri":"alm_16000.html", "node_id":"alm_16000.xml", "product_code":"mrs", - "code":"891", + "code":"895", "des":"The system checks the percentage of sessions connected to the HiveServer to the maximum number allowed every 30 seconds. This indicator can be viewed on the Hive service ", "doc_type":"usermanual", "kw":"ALM-16000 Percentage of Sessions Connected to the HiveServer to the Maximum Number Allowed Exceeds t", @@ -16413,7 +16481,7 @@ "uri":"alm_16001.html", "node_id":"alm_16001.xml", "product_code":"mrs", - "code":"892", + "code":"896", "des":"The system checks the Hive warehouse space usage every 30 seconds. The indicator Percentage of HDFS Space Used by Hive to the Available Space can be viewed on the Hive se", "doc_type":"usermanual", "kw":"ALM-16001 Hive Warehouse Space Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions E", @@ -16432,7 +16500,7 @@ "uri":"alm_16002.html", "node_id":"alm_16002.xml", "product_code":"mrs", - "code":"893", + "code":"897", "des":"The system checks the percentage of the HiveQL statements that are executed successfully every 30 seconds. Percentage of HiveQL statements that are executed successfully ", "doc_type":"usermanual", "kw":"ALM-16002 Hive SQL Execution Success Rate Is Lower Than the Threshold,Alarm Reference (Applicable to", @@ -16451,7 +16519,7 @@ "uri":"alm_16004.html", "node_id":"alm_16004.xml", "product_code":"mrs", - "code":"894", + "code":"898", "des":"The system checks the Hive service status every 30 seconds. This alarm is generated when the Hive service is unavailable.This alarm is cleared when the Hive service recov", "doc_type":"usermanual", "kw":"ALM-16004 Hive Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Use", @@ -16470,7 +16538,7 @@ "uri":"alm_18000.html", "node_id":"alm_18000.xml", "product_code":"mrs", - "code":"895", + "code":"899", "des":"The alarm module checks the Yarn service status every 30 seconds. This alarm is generated when the Yarn service is unavailable.This alarm is cleared when the Yarn service", "doc_type":"usermanual", "kw":"ALM-18000 Yarn Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Use", @@ -16489,7 +16557,7 @@ "uri":"alm_18002.html", "node_id":"alm_18002.xml", "product_code":"mrs", - "code":"896", + "code":"900", "des":"The system checks the number of lost NodeManager nodes every 30 seconds, and compares the number of lost nodes with the threshold. The Lost Nodes indicator has a default ", "doc_type":"usermanual", "kw":"ALM-18002 NodeManager Heartbeat Lost,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),U", @@ -16508,7 +16576,7 @@ "uri":"alm_18003.html", "node_id":"alm_18003.xml", "product_code":"mrs", - "code":"897", + "code":"901", "des":"The system checks the number of abnormal NodeManager nodes every 30 seconds, and compares the number of abnormal nodes with the threshold. The Unhealthy Nodes indicator h", "doc_type":"usermanual", "kw":"ALM-18003 NodeManager Unhealthy,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User G", @@ -16527,7 +16595,7 @@ "uri":"alm_18004.html", "node_id":"alm_18004.xml", "product_code":"mrs", - "code":"898", + "code":"902", "des":"The system checks the available disk space of each NodeManager node every 30 seconds and compares the disk availability rate with the threshold. A default threshold range", "doc_type":"usermanual", "kw":"ALM-18004 NodeManager Disk Usability Ratio Is Lower Than the Threshold,Alarm Reference (Applicable t", @@ -16546,7 +16614,7 @@ "uri":"alm_18006.html", "node_id":"alm_18006.xml", "product_code":"mrs", - "code":"899", + "code":"903", "des":"The alarm module checks the MapReduce job execution every 30 seconds. This alarm is generated when the execution of a submitted MapReduce job times out.This alarm must be", "doc_type":"usermanual", "kw":"ALM-18006 MapReduce Job Execution Timeout,Alarm Reference (Applicable to Versions Earlier Than MRS 3", @@ -16565,7 +16633,7 @@ "uri":"alm_19000.html", "node_id":"alm_19000.xml", "product_code":"mrs", - "code":"900", + "code":"904", "des":"The alarm module checks the HBase service status every 30 seconds. This alarm is generated when the HBase service is unavailable.This alarm is cleared when the HBase serv", "doc_type":"usermanual", "kw":"ALM-19000 HBase Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Us", @@ -16584,7 +16652,7 @@ "uri":"alm_19006.html", "node_id":"alm_19006.xml", "product_code":"mrs", - "code":"901", + "code":"905", "des":"This alarm is generated when disaster recovery (DR) data fails to be synchronized to a standby cluster.This alarm is cleared when DR data synchronization succeeds.HBase d", "doc_type":"usermanual", "kw":"ALM-19006 HBase Replication Sync Failed,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x", @@ -16603,7 +16671,7 @@ "uri":"alm_25000.html", "node_id":"alm_25000.xml", "product_code":"mrs", - "code":"902", + "code":"906", "des":"The system checks the LdapServer service status every 30 seconds. This alarm is generated when the active and standby LdapServer services are abnormal.This alarm is clear", "doc_type":"usermanual", "kw":"ALM-25000 LdapServer Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.", @@ -16622,7 +16690,7 @@ "uri":"alm_25004.html", "node_id":"alm_25004.xml", "product_code":"mrs", - "code":"903", + "code":"907", "des":"This alarm is generated when LdapServer data on Manager is inconsistent. This alarm is cleared when the data becomes consistent.This alarm is generated when LdapServer da", "doc_type":"usermanual", "kw":"ALM-25004 Abnormal LdapServer Data Synchronization,Alarm Reference (Applicable to Versions Earlier T", @@ -16641,7 +16709,7 @@ "uri":"alm_25500.html", "node_id":"alm_25500.xml", "product_code":"mrs", - "code":"904", + "code":"908", "des":"The system checks the KrbServer service status every 30 seconds. This alarm is generated when the KrbServer service is abnormal.This alarm is cleared when the KrbServer s", "doc_type":"usermanual", "kw":"ALM-25500 KrbServer Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x", @@ -16660,7 +16728,7 @@ "uri":"alm_27001.html", "node_id":"alm_27001.xml", "product_code":"mrs", - "code":"905", + "code":"909", "des":"The alarm module checks the DBService status every 30 seconds. This alarm is generated when the system detects that DBService is unavailable.This alarm is cleared when DB", "doc_type":"usermanual", "kw":"ALM-27001 DBService Is Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Use", @@ -16679,7 +16747,7 @@ "uri":"alm_27003.html", "node_id":"alm_27003.xml", "product_code":"mrs", - "code":"906", + "code":"910", "des":"This alarm is generated when the active or standby DBService node does not receive heartbeat messages from the peer node.This alarm is cleared when the heartbeat recovers", "doc_type":"usermanual", "kw":"ALM-27003 DBService Heartbeat Interruption Between the Active and Standby Nodes,Alarm Reference (App", @@ -16698,7 +16766,7 @@ "uri":"alm_27004.html", "node_id":"alm_27004.xml", "product_code":"mrs", - "code":"907", + "code":"911", "des":"The system checks the data synchronization status between the active and standby DBServices every 10 seconds. This alarm is generated when the synchronization status cann", "doc_type":"usermanual", "kw":"ALM-27004 Data Inconsistency Between Active and Standby DBServices,Alarm Reference (Applicable to Ve", @@ -16717,7 +16785,7 @@ "uri":"alm_28001.html", "node_id":"alm_28001.xml", "product_code":"mrs", - "code":"908", + "code":"912", "des":"The system checks the Spark service status every 30 seconds. This alarm is generated when the Spark service is unavailable.This alarm is cleared when the Spark service re", "doc_type":"usermanual", "kw":"ALM-28001 Spark Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Us", @@ -16736,7 +16804,7 @@ "uri":"alm_26051.html", "node_id":"alm_26051.xml", "product_code":"mrs", - "code":"909", + "code":"913", "des":"The system checks the Storm service availability every 30 seconds. This alarm is generated if the Storm service becomes unavailable after all Nimbus nodes in a cluster be", "doc_type":"usermanual", "kw":"ALM-26051 Storm Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Us", @@ -16755,7 +16823,7 @@ "uri":"alm_26052.html", "node_id":"alm_26052.xml", "product_code":"mrs", - "code":"910", + "code":"914", "des":"The system checks the number of supervisors every 60 seconds and compares it with the threshold. This alarm is generated if the number of supervisors is lower than the th", "doc_type":"usermanual", "kw":"ALM-26052 Number of Available Supervisors in Storm Is Lower Than the Threshold,Alarm Reference (Appl", @@ -16774,7 +16842,7 @@ "uri":"alm_26053.html", "node_id":"alm_26053.xml", "product_code":"mrs", - "code":"911", + "code":"915", "des":"The system checks the slot usage of Storm every 60 seconds and compares it with the threshold. This alarm is generated if the slot usage exceeds the threshold.To modify t", "doc_type":"usermanual", "kw":"ALM-26053 Slot Usage of Storm Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier ", @@ -16793,7 +16861,7 @@ "uri":"alm_26054.html", "node_id":"alm_26054.xml", "product_code":"mrs", - "code":"912", + "code":"916", "des":"The system checks the heap memory usage of Storm Nimbus every 30 seconds and compares it with the threshold. This alarm is generated if the heap memory usage exceeds the ", "doc_type":"usermanual", "kw":"ALM-26054 Heap Memory Usage of Storm Nimbus Exceeds the Threshold,Alarm Reference (Applicable to Ver", @@ -16812,7 +16880,7 @@ "uri":"alm_38000.html", "node_id":"alm_38000.xml", "product_code":"mrs", - "code":"913", + "code":"917", "des":"The system checks the Kafka service availability every 30 seconds. This alarm is generated if the Kafka service becomes unavailable.This alarm is cleared after the Kafka ", "doc_type":"usermanual", "kw":"ALM-38000 Kafka Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Us", @@ -16831,7 +16899,7 @@ "uri":"alm_38001.html", "node_id":"alm_38001.xml", "product_code":"mrs", - "code":"914", + "code":"918", "des":"The system checks the Kafka disk usage every 60 seconds and compares it with the threshold. This alarm is generated if the disk usage exceeds the threshold.To modify the ", "doc_type":"usermanual", "kw":"ALM-38001 Insufficient Kafka Disk Space,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x", @@ -16851,7 +16919,7 @@ "uri":"alm_38002.html", "node_id":"alm_38002.xml", "product_code":"mrs", - "code":"915", + "code":"919", "des":"The system checks the heap memory usage of Kafka every 30 seconds. This alarm is generated if the heap memory usage of Kafka exceeds the threshold (80%).This alarm is cle", "doc_type":"usermanual", "kw":"ALM-38002 Heap Memory Usage of Kafka Exceeds the Threshold,Alarm Reference (Applicable to Versions E", @@ -16870,7 +16938,7 @@ "uri":"alm_24000.html", "node_id":"alm_24000.xml", "product_code":"mrs", - "code":"916", + "code":"920", "des":"The alarm module checks the Flume service status every 180 seconds. This alarm is generated if the Flume service is abnormal.This alarm is cleared after the Flume service", "doc_type":"usermanual", "kw":"ALM-24000 Flume Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Us", @@ -16889,7 +16957,7 @@ "uri":"alm_24001.html", "node_id":"alm_24001.xml", "product_code":"mrs", - "code":"917", + "code":"921", "des":"This alarm is generated if the Flume agent monitoring module detects that the Flume agent process is abnormal.This alarm is cleared after the Flume agent process recovers", "doc_type":"usermanual", "kw":"ALM-24001 Flume Agent Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User", @@ -16908,7 +16976,7 @@ "uri":"alm_24003.html", "node_id":"alm_24003.xml", "product_code":"mrs", - "code":"918", + "code":"922", "des":"The alarm module monitors the port connection status on the Flume server. This alarm is generated if the Flume server fails to receive a connection message from the Flume", "doc_type":"usermanual", "kw":"ALM-24003 Flume Client Connection Failure,Alarm Reference (Applicable to Versions Earlier Than MRS 3", @@ -16927,7 +16995,7 @@ "uri":"alm_24004.html", "node_id":"alm_24004.xml", "product_code":"mrs", - "code":"919", + "code":"923", "des":"The alarm module monitors the Flume source status. This alarm is generated if the duration that Flume source fails to read data exceeds the threshold.Users can modify the", "doc_type":"usermanual", "kw":"ALM-24004 Flume Fails to Read Data,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Use", @@ -16946,7 +17014,7 @@ "uri":"alm_24005.html", "node_id":"alm_24005.xml", "product_code":"mrs", - "code":"920", + "code":"924", "des":"The alarm module monitors the capacity of Flume channels. This alarm is generated if the duration that a channel is full or the number of times that a source fails to sen", "doc_type":"usermanual", "kw":"ALM-24005 Data Transmission by Flume Is Abnormal,Alarm Reference (Applicable to Versions Earlier Tha", @@ -16965,7 +17033,7 @@ "uri":"alm_12041.html", "node_id":"alm_12041.xml", "product_code":"mrs", - "code":"921", + "code":"925", "des":"The system checks the permission, users, and user groups of key directories or files every hour. This alarm is generated if any of these is abnormal.This alarm is cleared", "doc_type":"usermanual", "kw":"ALM-12041 Permission of Key Files Is Abnormal,Alarm Reference (Applicable to Versions Earlier Than M", @@ -16984,7 +17052,7 @@ "uri":"alm_12042.html", "node_id":"alm_12042.xml", "product_code":"mrs", - "code":"922", + "code":"926", "des":"The system checks key file configurations every hour. This alarm is generated if any key configuration is abnormal.This alarm is cleared after the configuration becomes n", "doc_type":"usermanual", "kw":"ALM-12042 Key File Configurations Are Abnormal,Alarm Reference (Applicable to Versions Earlier Than ", @@ -17003,7 +17071,7 @@ "uri":"alm_23001.html", "node_id":"alm_23001.xml", "product_code":"mrs", - "code":"923", + "code":"927", "des":"The system checks the Loader service availability every 60 seconds. This alarm is generated if the Loader service is unavailable and is cleared after the Loader service r", "doc_type":"usermanual", "kw":"ALM-23001 Loader Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),U", @@ -17022,7 +17090,7 @@ "uri":"alm_12357.html", "node_id":"alm_12357.xml", "product_code":"mrs", - "code":"924", + "code":"928", "des":"If the user has configured audit log export to the OBS on MRS Manager, the system regularly exports audit logs to the OBS. This alarm is reported if the system fails to a", "doc_type":"usermanual", "kw":"ALM-12357 Failed to Export Audit Logs to OBS,Alarm Reference (Applicable to Versions Earlier Than MR", @@ -17041,7 +17109,7 @@ "uri":"alm_12014.html", "node_id":"alm_12014.xml", "product_code":"mrs", - "code":"925", + "code":"929", "des":"This alarm is generated when the system detects that a partition to which service directories are mounted is lost (because the device is removed or goes offline, or the p", "doc_type":"usermanual", "kw":"ALM-12014 Device Partition Lost,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User G", @@ -17060,7 +17128,7 @@ "uri":"alm_12015.html", "node_id":"alm_12015.xml", "product_code":"mrs", - "code":"926", + "code":"930", "des":"This alarm is generated when the system detects that a partition to which service directories are mounted enters the read-only mode (due to a bad sector or a faulty file ", "doc_type":"usermanual", "kw":"ALM-12015 Device Partition File System Read-Only,Alarm Reference (Applicable to Versions Earlier Tha", @@ -17079,7 +17147,7 @@ "uri":"alm_12043.html", "node_id":"alm_12043.xml", "product_code":"mrs", - "code":"927", + "code":"931", "des":"The system checks the DNS parsing duration every 30 seconds. This alarm is generated when the DNS parsing duration exceeds the threshold (the default threshold is 20,000 ", "doc_type":"usermanual", "kw":"ALM-12043 DNS Parsing Duration Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier", @@ -17098,7 +17166,7 @@ "uri":"alm_12045.html", "node_id":"alm_12045.xml", "product_code":"mrs", - "code":"928", + "code":"932", "des":"The system checks the read packet dropped rate every 30 seconds. This alarm is generated when the read packet dropped rate exceeds the threshold (the default threshold is", "doc_type":"usermanual", "kw":"ALM-12045 Read Packet Dropped Rate Exceeds the Threshold,Alarm Reference (Applicable to Versions Ear", @@ -17117,7 +17185,7 @@ "uri":"alm_12046.html", "node_id":"alm_12046.xml", "product_code":"mrs", - "code":"929", + "code":"933", "des":"The system checks the write packet dropped rate every 30 seconds. This alarm is generated when the write packet dropped rate exceeds the threshold (the default threshold ", "doc_type":"usermanual", "kw":"ALM-12046 Write Packet Dropped Rate Exceeds the Threshold,Alarm Reference (Applicable to Versions Ea", @@ -17136,7 +17204,7 @@ "uri":"alm_12047.html", "node_id":"alm_12047.xml", "product_code":"mrs", - "code":"930", + "code":"934", "des":"The system checks the read packet error rate every 30 seconds. This alarm is generated when the read packet error rate exceeds the threshold (the default threshold is 0.5", "doc_type":"usermanual", "kw":"ALM-12047 Read Packet Error Rate Exceeds the Threshold,Alarm Reference (Applicable to Versions Earli", @@ -17155,7 +17223,7 @@ "uri":"alm_12048.html", "node_id":"alm_12048.xml", "product_code":"mrs", - "code":"931", + "code":"935", "des":"The system checks the write packet error rate every 30 seconds. This alarm is generated when the write packet error rate exceeds the threshold (the default threshold is 0", "doc_type":"usermanual", "kw":"ALM-12048 Write Packet Error Rate Exceeds the Threshold,Alarm Reference (Applicable to Versions Earl", @@ -17174,7 +17242,7 @@ "uri":"alm_12049.html", "node_id":"alm_12049.xml", "product_code":"mrs", - "code":"932", + "code":"936", "des":"The system checks the read throughput rate every 30 seconds. This alarm is generated when the read throughput rate exceeds the threshold (the default threshold is 80%) fo", "doc_type":"usermanual", "kw":"ALM-12049 Read Throughput Rate Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier", @@ -17193,7 +17261,7 @@ "uri":"alm_12050.html", "node_id":"alm_12050.xml", "product_code":"mrs", - "code":"933", + "code":"937", "des":"The system checks the write throughput rate every 30 seconds. This alarm is generated when the write throughput rate exceeds the threshold (the default threshold is 80%) ", "doc_type":"usermanual", "kw":"ALM-12050 Write Throughput Rate Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlie", @@ -17212,7 +17280,7 @@ "uri":"alm_12051.html", "node_id":"alm_12051.xml", "product_code":"mrs", - "code":"934", + "code":"938", "des":"The system checks the disk inode usage every 30 seconds. This alarm is generated when the disk inode usage exceeds the threshold (the default threshold is 80%) for multip", "doc_type":"usermanual", "kw":"ALM-12051 Disk Inode Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier Tha", @@ -17231,7 +17299,7 @@ "uri":"alm_12052.html", "node_id":"alm_12052.xml", "product_code":"mrs", - "code":"935", + "code":"939", "des":"The system checks the usage of temporary TCP ports every 30 seconds. This alarm is generated when the usage of temporary TCP ports exceeds the threshold (the default thre", "doc_type":"usermanual", "kw":"ALM-12052 Usage of Temporary TCP Ports Exceeds the Threshold,Alarm Reference (Applicable to Versions", @@ -17250,7 +17318,7 @@ "uri":"alm_12053.html", "node_id":"alm_12053.xml", "product_code":"mrs", - "code":"936", + "code":"940", "des":"The system checks the handler usage every 30 seconds. This alarm is generated when the handle usage exceeds the threshold (the default threshold is 80%) for multiple time", "doc_type":"usermanual", "kw":"ALM-12053 File Handle Usage Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier Th", @@ -17269,7 +17337,7 @@ "uri":"alm_12054.html", "node_id":"alm_12054.xml", "product_code":"mrs", - "code":"937", + "code":"941", "des":"The system checks whether the certificate file is invalid (has expired or is not yet valid) on 23:00 every day. This alarm is generated when the certificate file is inval", "doc_type":"usermanual", "kw":"ALM-12054 The Certificate File Is Invalid,Alarm Reference (Applicable to Versions Earlier Than MRS 3", @@ -17289,7 +17357,7 @@ "uri":"alm_12055.html", "node_id":"alm_12055.xml", "product_code":"mrs", - "code":"938", + "code":"942", "des":"The system checks the certificate file on 23:00 every day. This alarm is generated if the certificate file is about to expire with a validity period less than days set in", "doc_type":"usermanual", "kw":"ALM-12055 The Certificate File Is About to Expire,Alarm Reference (Applicable to Versions Earlier Th", @@ -17309,7 +17377,7 @@ "uri":"alm_18008.html", "node_id":"alm_18008.xml", "product_code":"mrs", - "code":"939", + "code":"943", "des":"The system checks the heap memory usage of Yarn ResourceManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap me", "doc_type":"usermanual", "kw":"ALM-18008 Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold,Alarm Reference (Applicabl", @@ -17328,7 +17396,7 @@ "uri":"alm_18009.html", "node_id":"alm_18009.xml", "product_code":"mrs", - "code":"940", + "code":"944", "des":"The system checks the heap memory usage of MapReduce JobHistoryServer every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the h", "doc_type":"usermanual", "kw":"ALM-18009 Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold,Alarm Reference (App", @@ -17347,7 +17415,7 @@ "uri":"alm_20002.html", "node_id":"alm_20002.xml", "product_code":"mrs", - "code":"941", + "code":"945", "des":"The system checks the Hue service status every 60 seconds. This alarm is generated if the Hue service is unavailable.This alarm is cleared when the Hue service is normal.", "doc_type":"usermanual", "kw":"ALM-20002 Hue Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),User", @@ -17366,7 +17434,7 @@ "uri":"alm_43001.html", "node_id":"alm_43001.xml", "product_code":"mrs", - "code":"942", + "code":"946", "des":"The system checks the Spark service status every 60 seconds. This alarm is generated when the Spark service is unavailable.This alarm is cleared when the Spark service re", "doc_type":"usermanual", "kw":"ALM-43001 Spark Service Unavailable,Alarm Reference (Applicable to Versions Earlier Than MRS 3.x),Us", @@ -17385,7 +17453,7 @@ "uri":"alm_43006.html", "node_id":"alm_43006.xml", "product_code":"mrs", - "code":"943", + "code":"947", "des":"The system checks the JobHistory process status every 30 seconds. The alarm is generated when the heap memory usage of the JobHistory process exceeds the threshold (90% o", "doc_type":"usermanual", "kw":"ALM-43006 Heap Memory Usage of the JobHistory Process Exceeds the Threshold,Alarm Reference (Applica", @@ -17404,7 +17472,7 @@ "uri":"alm_43007.html", "node_id":"alm_43007.xml", "product_code":"mrs", - "code":"944", + "code":"948", "des":"The system checks the JobHistory process status every 30 seconds. The alarm is generated when the non-heap memory usage of the JobHistory process exceeds the threshold (9", "doc_type":"usermanual", "kw":"ALM-43007 Non-Heap Memory Usage of the JobHistory Process Exceeds the Threshold,Alarm Reference (App", @@ -17423,7 +17491,7 @@ "uri":"alm_43008.html", "node_id":"alm_43008.xml", "product_code":"mrs", - "code":"945", + "code":"949", "des":"The system checks the JobHistory process status every 30 seconds. The alarm is generated when the direct memory usage of the JobHistory process exceeds the threshold (90%", "doc_type":"usermanual", "kw":"ALM-43008 Direct Memory Usage of the JobHistory Process Exceeds the Threshold,Alarm Reference (Appli", @@ -17442,7 +17510,7 @@ "uri":"alm_43009.html", "node_id":"alm_43009.xml", "product_code":"mrs", - "code":"946", + "code":"950", "des":"The system checks the GC time of the JobHistory process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (12 seconds) for three c", "doc_type":"usermanual", "kw":"ALM-43009 JobHistory GC Time Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier T", @@ -17461,7 +17529,7 @@ "uri":"alm_43010.html", "node_id":"alm_43010.xml", "product_code":"mrs", - "code":"947", + "code":"951", "des":"The system checks the JDBCServer process status every 30 seconds. The alarm is generated when the heap memory usage of the JDBCServer process exceeds the threshold (90% o", "doc_type":"usermanual", "kw":"ALM-43010 Heap Memory Usage of the JDBCServer Process Exceeds the Threshold,Alarm Reference (Applica", @@ -17480,7 +17548,7 @@ "uri":"alm_43011.html", "node_id":"alm_43011.xml", "product_code":"mrs", - "code":"948", + "code":"952", "des":"The system checks the JDBCServer process status every 30 seconds. The alarm is generated when the non-heap memory usage of the JDBCServer process exceeds the threshold (9", "doc_type":"usermanual", "kw":"ALM-43011 Non-Heap Memory Usage of the JDBCServer Process Exceeds the Threshold,Alarm Reference (App", @@ -17499,7 +17567,7 @@ "uri":"alm_43012.html", "node_id":"alm_43012.xml", "product_code":"mrs", - "code":"949", + "code":"953", "des":"The system checks the JDBCServer process status every 30 seconds. The alarm is generated when the direct memory usage of the JDBCServer process exceeds the threshold (90%", "doc_type":"usermanual", "kw":"ALM-43012 Direct Memory Usage of the JDBCServer Process Exceeds the Threshold,Alarm Reference (Appli", @@ -17518,7 +17586,7 @@ "uri":"alm_43013.html", "node_id":"alm_43013.xml", "product_code":"mrs", - "code":"950", + "code":"954", "des":"The system checks the GC time of the JDBCServer process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (12 seconds) for three c", "doc_type":"usermanual", "kw":"ALM-43013 JDBCServer GC Time Exceeds the Threshold,Alarm Reference (Applicable to Versions Earlier T", @@ -17537,7 +17605,7 @@ "uri":"alm_44004.html", "node_id":"alm_44004.xml", "product_code":"mrs", - "code":"951", + "code":"955", "des":"This alarm is generated when the system detects that the number of queuing tasks in a resource group exceeds the threshold. The system queries the number of queuing tasks", "doc_type":"usermanual", "kw":"ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold,Alarm Reference (Appl", @@ -17556,7 +17624,7 @@ "uri":"alm_44005.html", "node_id":"alm_44005.xml", "product_code":"mrs", - "code":"952", + "code":"956", "des":"The system collects GC time of the Presto Coordinator process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for thre", "doc_type":"usermanual", "kw":"ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold,Alarm Reference (Applicable to Ve", @@ -17575,7 +17643,7 @@ "uri":"alm_44006.html", "node_id":"alm_44006.xml", "product_code":"mrs", - "code":"953", + "code":"957", "des":"The system collects GC time of the Presto Worker process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for three con", "doc_type":"usermanual", "kw":"ALM-44006 Presto Worker Process GC Time Exceeds the Threshold,Alarm Reference (Applicable to Version", @@ -17594,7 +17662,7 @@ "uri":"alm_18010.html", "node_id":"alm_18010.xml", "product_code":"mrs", - "code":"954", + "code":"958", "des":"The system checks the number of pending Yarn tasks every 30 seconds and compares the number of tasks with the threshold. This alarm is generated when the number of pendin", "doc_type":"usermanual", "kw":"ALM-18010 Number of Pending Yarn Tasks Exceeds the Threshold,Alarm Reference (Applicable to Versions", @@ -17614,7 +17682,7 @@ "uri":"alm_18011.html", "node_id":"alm_18011.xml", "product_code":"mrs", - "code":"955", + "code":"959", "des":"The system checks the memory of pending Yarn tasks every 30 seconds and compares the memory with the threshold. This alarm is generated when the memory of pending tasks e", "doc_type":"usermanual", "kw":"ALM-18011 Memory of Pending Yarn Tasks Exceeds the Threshold,Alarm Reference (Applicable to Versions", @@ -17634,7 +17702,7 @@ "uri":"alm_18012.html", "node_id":"alm_18012.xml", "product_code":"mrs", - "code":"956", + "code":"960", "des":"The system checks the number of terminated Yarn tasks every 10 minutes. This alarm is generated when the number of terminated Yarn tasks in the last 10 minutes is greater", "doc_type":"usermanual", "kw":"ALM-18012 Number of Terminated Yarn Tasks in the Last Period Exceeds the Threshold,Alarm Reference (", @@ -17653,7 +17721,7 @@ "uri":"alm_18013.html", "node_id":"alm_18013.xml", "product_code":"mrs", - "code":"957", + "code":"961", "des":"The system checks the number of failed Yarn tasks every 10 minutes. This alarm is generated when the number of failed Yarn tasks in the last 10 minutes is greater than th", "doc_type":"usermanual", "kw":"ALM-18013 Number of Failed Yarn Tasks in the Last Period Exceeds the Threshold,Alarm Reference (Appl", @@ -17672,7 +17740,7 @@ "uri":"alm_16005.html", "node_id":"alm_16005.xml", "product_code":"mrs", - "code":"958", + "code":"962", "des":"The system checks whether the number of Hive SQL statements that fail to be executed has exceeded the threshold in the last 10-minute period. This alarm is generated when", "doc_type":"usermanual", "kw":"ALM-16005 Number of Failed Hive SQL Executions in the Last Period Exceeds the Threshold,Alarm Refere", @@ -17691,7 +17759,7 @@ "uri":"mrs_01_0242.html", "node_id":"mrs_01_0242.xml", "product_code":"mrs", - "code":"959", + "code":"963", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Object Management", @@ -17710,7 +17778,7 @@ "uri":"mrs_01_0243.html", "node_id":"mrs_01_0243.xml", "product_code":"mrs", - "code":"960", + "code":"964", "des":"MRS contains different types of basic objects as described in Table 1.", "doc_type":"usermanual", "kw":"Managing Objects,Object Management,User Guide", @@ -17729,7 +17797,7 @@ "uri":"mrs_01_0244.html", "node_id":"mrs_01_0244.xml", "product_code":"mrs", - "code":"961", + "code":"965", "des":"On MRS Manager, users can view the configurations of services (including roles) and role instances.Query service configurations.On MRS Manager page, click Services.Select", "doc_type":"usermanual", "kw":"Viewing Configurations,Object Management,User Guide", @@ -17748,7 +17816,7 @@ "uri":"mrs_01_0245.html", "node_id":"mrs_01_0245.xml", "product_code":"mrs", - "code":"962", + "code":"966", "des":"You can perform the following operations on MRS Manager:Start the service in the Stopped, Stop Failed, or Start Failed state to use the service.Stop the services or stop ", "doc_type":"usermanual", "kw":"Managing Services,Object Management,User Guide", @@ -17767,7 +17835,7 @@ "uri":"mrs_01_0246.html", "node_id":"mrs_01_0246.xml", "product_code":"mrs", - "code":"963", + "code":"967", "des":"On MRS Manager, you can view and modify the default service configurations based on site requirements and export or import the configurations.You need to download and upd", "doc_type":"usermanual", "kw":"Configuring Service Parameters,Object Management,User Guide", @@ -17786,7 +17854,7 @@ "uri":"mrs_01_0247.html", "node_id":"mrs_01_0247.xml", "product_code":"mrs", - "code":"964", + "code":"968", "des":"Each component of MRS supports all open-source parameters. You can modify some parameters for key application scenarios on MRS Manager. Some component clients may not inc", "doc_type":"usermanual", "kw":"Configuring Customized Service Parameters,Object Management,User Guide", @@ -17805,7 +17873,7 @@ "uri":"mrs_01_0248.html", "node_id":"mrs_01_0248.xml", "product_code":"mrs", - "code":"965", + "code":"969", "des":"If Configuration Status of a service is Expired or Failed, synchronize configurations for the cluster or service to restore its configuration status. If all services in t", "doc_type":"usermanual", "kw":"Synchronizing Service Configurations,Object Management,User Guide", @@ -17825,7 +17893,7 @@ "uri":"mrs_01_0249.html", "node_id":"mrs_01_0249.xml", "product_code":"mrs", - "code":"966", + "code":"970", "des":"You can start a role instance that is in the Stopped, Failed to stop or Failed to start status, stop an unused or abnormal role instance or restart an abnormal role insta", "doc_type":"usermanual", "kw":"Managing Role Instances,Object Management,User Guide", @@ -17845,7 +17913,7 @@ "uri":"mrs_01_0250.html", "node_id":"mrs_01_0250.xml", "product_code":"mrs", - "code":"967", + "code":"971", "des":"You can view and modify default role instance configurations on MRS Manager based on site requirements. The configurations can be imported and exported.You need to downlo", "doc_type":"usermanual", "kw":"Configuring Role Instance Parameters,Object Management,User Guide", @@ -17864,7 +17932,7 @@ "uri":"mrs_01_0251.html", "node_id":"mrs_01_0251.xml", "product_code":"mrs", - "code":"968", + "code":"972", "des":"When Configuration Status of a role instance is Expired or Failed, you can synchronize the configuration data of the role instance with the background configuration.After", "doc_type":"usermanual", "kw":"Synchronizing Role Instance Configuration,Object Management,User Guide", @@ -17884,7 +17952,7 @@ "uri":"mrs_01_0252.html", "node_id":"mrs_01_0252.xml", "product_code":"mrs", - "code":"969", + "code":"973", "des":"If a Core or Task node is faulty, the cluster status may be displayed as Abnormal. In an MRS cluster, data can be stored on different Core nodes. Users can decommission t", "doc_type":"usermanual", "kw":"Decommissioning and Recommissioning a Role Instance,Object Management,User Guide", @@ -17903,7 +17971,7 @@ "uri":"mrs_01_0254.html", "node_id":"mrs_01_0254.xml", "product_code":"mrs", - "code":"970", + "code":"974", "des":"When a host is abnormal or faulty, you need to stop all roles of the host on MRS Manager to check the host. After the host fault is rectified, start all roles running on ", "doc_type":"usermanual", "kw":"Managing a Host,Object Management,User Guide", @@ -17922,7 +17990,7 @@ "uri":"mrs_01_0255.html", "node_id":"mrs_01_0255.xml", "product_code":"mrs", - "code":"971", + "code":"975", "des":"If a host is found to be abnormal or faulty, affecting cluster performance or preventing services from being provided, you can temporarily exclude that host from the avai", "doc_type":"usermanual", "kw":"Isolating a Host,Object Management,User Guide", @@ -17941,7 +18009,7 @@ "uri":"mrs_01_0256.html", "node_id":"mrs_01_0256.xml", "product_code":"mrs", - "code":"972", + "code":"976", "des":"After the exception or fault of a host is handled, you must cancel the isolation of the host for proper usage.Users can cancel the isolation of a host on MRS Manager.The ", "doc_type":"usermanual", "kw":"Canceling Host Isolation,Object Management,User Guide", @@ -17960,7 +18028,7 @@ "uri":"mrs_01_0258.html", "node_id":"mrs_01_0258.xml", "product_code":"mrs", - "code":"973", + "code":"977", "des":"A cluster is a collection of service components. You can start or stop all services in a cluster.", "doc_type":"usermanual", "kw":"Starting or Stopping a Cluster,Object Management,User Guide", @@ -17979,7 +18047,7 @@ "uri":"mrs_01_0259.html", "node_id":"mrs_01_0259.xml", "product_code":"mrs", - "code":"974", + "code":"978", "des":"If Configuration Status of all services or some services is Expired or Failed, synchronize configuration for the cluster or service to restore its configuration status.If", "doc_type":"usermanual", "kw":"Synchronizing Cluster Configurations,Object Management,User Guide", @@ -17998,7 +18066,7 @@ "uri":"mrs_01_0260.html", "node_id":"mrs_01_0260.xml", "product_code":"mrs", - "code":"975", + "code":"979", "des":"You can export all configuration data of a cluster on MRS Manager to meet site requirements. The exported configuration data is used to rapidly update service configurati", "doc_type":"usermanual", "kw":"Exporting Configuration Data of a Cluster,Object Management,User Guide", @@ -18017,7 +18085,7 @@ "uri":"mrs_01_0264.html", "node_id":"mrs_01_0264.xml", "product_code":"mrs", - "code":"976", + "code":"980", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Log Management", @@ -18036,7 +18104,7 @@ "uri":"mrs_01_1226.html", "node_id":"mrs_01_1226.xml", "product_code":"mrs", - "code":"977", + "code":"981", "des":"MRS cluster logs are stored in the /var/log/Bigdata directory. The following table lists the log types.The following table lists the MRS log directories.Table 3 describes", "doc_type":"usermanual", "kw":"About Logs,Log Management,User Guide", @@ -18056,7 +18124,7 @@ "uri":"mrs_01_1227.html", "node_id":"mrs_01_1227.xml", "product_code":"mrs", - "code":"978", + "code":"982", "des":"Log path: The default storage path of Manager log files is /var/log/Bigdata/Manager component.ControllerService: /var/log/Bigdata/controller/ (operation & maintenance sys", "doc_type":"usermanual", "kw":"Manager Log List,Log Management,User Guide", @@ -18074,7 +18142,7 @@ "uri":"mrs_01_0265.html", "node_id":"mrs_01_0265.xml", "product_code":"mrs", - "code":"979", + "code":"983", "des":"This section describes how to view and export audit logs on MRS Manager. The audit logs can be used to trace security events, locate fault causes, and determine responsib", "doc_type":"usermanual", "kw":"Viewing and Exporting Audit Logs,Log Management,User Guide", @@ -18094,7 +18162,7 @@ "uri":"mrs_01_0267.html", "node_id":"mrs_01_0267.xml", "product_code":"mrs", - "code":"980", + "code":"984", "des":"This section describes how to export logs generated by each service role from MRS Manager.You have obtained the access key ID (AK) and secret access key (SK) of the accou", "doc_type":"usermanual", "kw":"Exporting Service Logs,Log Management,User Guide", @@ -18113,7 +18181,7 @@ "uri":"mrs_01_0270.html", "node_id":"mrs_01_0270.xml", "product_code":"mrs", - "code":"981", + "code":"985", "des":"If MRS audit logs are stored in the system for a long time, the disk space of the data directory may be insufficient. Therefore, you can set export parameters to automati", "doc_type":"usermanual", "kw":"Configuring Audit Log Exporting Parameters,Log Management,User Guide", @@ -18133,7 +18201,7 @@ "uri":"mrs_01_0271.html", "node_id":"mrs_01_0271.xml", "product_code":"mrs", - "code":"982", + "code":"986", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Health Check Management", @@ -18152,7 +18220,7 @@ "uri":"mrs_01_0274.html", "node_id":"mrs_01_0274.xml", "product_code":"mrs", - "code":"983", + "code":"987", "des":"To ensure that cluster parameters, configurations, and monitoring are correct and that the cluster can run stably for a long time, you can perform a health check during r", "doc_type":"usermanual", "kw":"Performing a Health Check,Health Check Management,User Guide", @@ -18172,7 +18240,7 @@ "uri":"mrs_01_0275.html", "node_id":"mrs_01_0275.xml", "product_code":"mrs", - "code":"984", + "code":"988", "des":"You can view the health check result in MRS Manager and export the health check results for further analysis.A system health check includes MRS Manager, service-level, an", "doc_type":"usermanual", "kw":"Viewing and Exporting a Health Check Report,Health Check Management,User Guide", @@ -18191,7 +18259,7 @@ "uri":"mrs_01_0277.html", "node_id":"mrs_01_0277.xml", "product_code":"mrs", - "code":"985", + "code":"989", "des":"Health check reports of MRS clusters, services, and hosts may vary with the time and scenario. You can modify the number of health check reports to be reserved on MRS Man", "doc_type":"usermanual", "kw":"Configuring the Number of Health Check Reports to Be Reserved,Health Check Management,User Guide", @@ -18210,7 +18278,7 @@ "uri":"mrs_01_0278.html", "node_id":"mrs_01_0278.xml", "product_code":"mrs", - "code":"986", + "code":"990", "des":"On MRS Manager, users can manage historical health check reports, for example, viewing, downloading, and deleting historical health check reports.Download a specified hea", "doc_type":"usermanual", "kw":"Managing Health Check Reports,Health Check Management,User Guide", @@ -18229,7 +18297,7 @@ "uri":"mrs_01_0279.html", "node_id":"mrs_01_0279.xml", "product_code":"mrs", - "code":"987", + "code":"991", "des":"Indicator: Service StatusDescription: This indicator is used to check whether the DBService service status is normal. If the status is abnormal, the service is unhealthy.", "doc_type":"usermanual", "kw":"DBService Health Check Indicators,Health Check Management,User Guide", @@ -18248,7 +18316,7 @@ "uri":"mrs_01_0280.html", "node_id":"mrs_01_0280.xml", "product_code":"mrs", - "code":"988", + "code":"992", "des":"Indicator: Service StatusDescription: This indicator is used to check whether the Flume service status is normal. If the status is abnormal, the service is unhealthy.Reco", "doc_type":"usermanual", "kw":"Flume Health Check Indicators,Health Check Management,User Guide", @@ -18267,7 +18335,7 @@ "uri":"mrs_01_0281.html", "node_id":"mrs_01_0281.xml", "product_code":"mrs", - "code":"989", + "code":"993", "des":"Indicator: Normal RegionServer CountDescription: This indicator is used to check the number of RegionServers that are running properly in an HBase cluster.Recovery Guide:", "doc_type":"usermanual", "kw":"HBase Health Check Indicators,Health Check Management,User Guide", @@ -18286,7 +18354,7 @@ "uri":"mrs_01_0282.html", "node_id":"mrs_01_0282.xml", "product_code":"mrs", - "code":"990", + "code":"994", "des":"Indicator: Swap UsageDescription: Swap usage of the system. The value is calculated using the following formula: Swap usage = Used swap size/Total swap size. Assume that ", "doc_type":"usermanual", "kw":"Host Health Check Indicators,Health Check Management,User Guide", @@ -18305,7 +18373,7 @@ "uri":"mrs_01_0284.html", "node_id":"mrs_01_0284.xml", "product_code":"mrs", - "code":"991", + "code":"995", "des":"Indicator: Average Packet Sending TimeDescription: This indicator is used to collect statistics on the average time for the DataNode in the HDFS to execute SendPacket eac", "doc_type":"usermanual", "kw":"HDFS Health Check Indicators,Health Check Management,User Guide", @@ -18324,7 +18392,7 @@ "uri":"mrs_01_0285.html", "node_id":"mrs_01_0285.xml", "product_code":"mrs", - "code":"992", + "code":"996", "des":"Indicator: Maximum Number of Sessions Allowed by HiveServerDescription: This indicator is used to check the maximum number of sessions that can be connected to Hive.Recov", "doc_type":"usermanual", "kw":"Hive Health Check Indicators,Health Check Management,User Guide", @@ -18343,7 +18411,7 @@ "uri":"mrs_01_0288.html", "node_id":"mrs_01_0288.xml", "product_code":"mrs", - "code":"993", + "code":"997", "des":"Indicator: Number of BrokersDescription: This indicator is used to check the number of available Broker nodes in a cluster. If the number of available Broker nodes in a c", "doc_type":"usermanual", "kw":"Kafka Health Check Indicators,Health Check Management,User Guide", @@ -18362,7 +18430,7 @@ "uri":"mrs_01_0289.html", "node_id":"mrs_01_0289.xml", "product_code":"mrs", - "code":"994", + "code":"998", "des":"Indicator: KerberosAdmin Service AvailabilityDescription: The system checks the KerberosAdmin service status. If the check result is abnormal, the KerberosAdmin service i", "doc_type":"usermanual", "kw":"KrbServer Health Check Indicators,Health Check Management,User Guide", @@ -18381,7 +18449,7 @@ "uri":"mrs_01_0291.html", "node_id":"mrs_01_0291.xml", "product_code":"mrs", - "code":"995", + "code":"999", "des":"Indicator: SlapdServer Service AvailabilityDescription: The system checks the SlapdServer service status. If the status is abnormal, the SlapdServer service is unavailabl", "doc_type":"usermanual", "kw":"LdapServer Health Check Indicators,Health Check Management,User Guide", @@ -18400,7 +18468,7 @@ "uri":"mrs_01_0292.html", "node_id":"mrs_01_0292.xml", "product_code":"mrs", - "code":"996", + "code":"1000", "des":"Indicator: ZooKeeper health statusDescription: This indicator is used to check whether the ZooKeeper health status is normal. If the status is abnormal, the ZooKeeper ser", "doc_type":"usermanual", "kw":"Loader Health Check Indicators,Health Check Management,User Guide", @@ -18419,7 +18487,7 @@ "uri":"mrs_01_0293.html", "node_id":"mrs_01_0293.xml", "product_code":"mrs", - "code":"997", + "code":"1001", "des":"Indicator: Service StatusDescription: This indicator is used to check whether the MapReduce service status is normal. If the status is abnormal, the service is unhealthy.", "doc_type":"usermanual", "kw":"MapReduce Health Check Indicators,Health Check Management,User Guide", @@ -18438,7 +18506,7 @@ "uri":"mrs_01_0294.html", "node_id":"mrs_01_0294.xml", "product_code":"mrs", - "code":"998", + "code":"1002", "des":"Indicator: OMS Status CheckDescription: The OMS status check includes the HA status check and resource status check. The HA status includes active, standby, and NULL, ind", "doc_type":"usermanual", "kw":"OMS Health Check Indicators,Health Check Management,User Guide", @@ -18458,7 +18526,7 @@ "uri":"mrs_01_0530.html", "node_id":"mrs_01_0530.xml", "product_code":"mrs", - "code":"999", + "code":"1003", "des":"Indicator: Service StatusDescription: This indicator is used to check whether the Spark service status is normal. If the status is abnormal, the service is unhealthy.Reco", "doc_type":"usermanual", "kw":"Spark Health Check Indicators,Health Check Management,User Guide", @@ -18477,7 +18545,7 @@ "uri":"mrs_01_0531.html", "node_id":"mrs_01_0531.xml", "product_code":"mrs", - "code":"1000", + "code":"1004", "des":"Indicator: Number of SupervisorsDescription: This indicator is used to check the number of available Supervisors in a cluster. If the number of available Supervisors in a", "doc_type":"usermanual", "kw":"Storm Health Check Indicators,Health Check Management,User Guide", @@ -18496,7 +18564,7 @@ "uri":"mrs_01_0532.html", "node_id":"mrs_01_0532.xml", "product_code":"mrs", - "code":"1001", + "code":"1005", "des":"Indicator: Service StatusDescription: This indicator is used to check whether the Yarn service status is normal. If the number of NodeManager nodes cannot be obtained, th", "doc_type":"usermanual", "kw":"Yarn Health Check Indicators,Health Check Management,User Guide", @@ -18515,7 +18583,7 @@ "uri":"mrs_01_0533.html", "node_id":"mrs_01_0533.xml", "product_code":"mrs", - "code":"1002", + "code":"1006", "des":"Indicator: Average ZooKeeper Service Request Processing LatencyDescription: This indicator is used to check the average delay for the ZooKeeper service to process request", "doc_type":"usermanual", "kw":"ZooKeeper Health Check Indicators,Health Check Management,User Guide", @@ -18534,7 +18602,7 @@ "uri":"mrs_01_0534.html", "node_id":"mrs_01_0534.xml", "product_code":"mrs", - "code":"1003", + "code":"1007", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Static Service Pool Management", @@ -18553,7 +18621,7 @@ "uri":"mrs_01_0535.html", "node_id":"mrs_01_0535.xml", "product_code":"mrs", - "code":"1004", + "code":"1008", "des":"MRS Manager manages and isolates service resources that are not running on YARN through the static service resource pool. It dynamically manages the total CPU, I/O, and m", "doc_type":"usermanual", "kw":"Viewing the Status of a Static Service Pool,Static Service Pool Management,User Guide", @@ -18571,7 +18639,7 @@ "uri":"mrs_01_0536.html", "node_id":"mrs_01_0536.xml", "product_code":"mrs", - "code":"1005", + "code":"1009", "des":"If you need to control the node resources that can be used by the cluster service or the CPU usage of the node used by the cluster in different time periods, you can adju", "doc_type":"usermanual", "kw":"Configuring a Static Service Pool,Static Service Pool Management,User Guide", @@ -18591,7 +18659,7 @@ "uri":"mrs_01_0537.html", "node_id":"mrs_01_0537.xml", "product_code":"mrs", - "code":"1006", + "code":"1010", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Tenant Management", @@ -18610,7 +18678,7 @@ "uri":"mrs_01_0538.html", "node_id":"mrs_01_0538.xml", "product_code":"mrs", - "code":"1007", + "code":"1011", "des":"An MRS cluster provides various resources and services for multiple organizations, departments, or applications to share. The cluster provides tenants as a logical entity", "doc_type":"usermanual", "kw":"Overview,Tenant Management,User Guide", @@ -18629,7 +18697,7 @@ "uri":"mrs_01_0539.html", "node_id":"mrs_01_0539.xml", "product_code":"mrs", - "code":"1008", + "code":"1012", "des":"You can create a tenant on MRS Manager to specify the resource usage.A tenant name has been planned. The name must not be the same as that of a role or Yarn queue that ex", "doc_type":"usermanual", "kw":"Creating a Tenant,Tenant Management,User Guide", @@ -18648,7 +18716,7 @@ "uri":"mrs_01_0540.html", "node_id":"mrs_01_0540.xml", "product_code":"mrs", - "code":"1009", + "code":"1013", "des":"You can create a sub-tenant on MRS Manager if the resources of the current tenant need to be further allocated.A parent tenant has been added.A tenant name has been plann", "doc_type":"usermanual", "kw":"Creating a Sub-tenant,Tenant Management,User Guide", @@ -18667,7 +18735,7 @@ "uri":"mrs_01_0541.html", "node_id":"mrs_01_0541.xml", "product_code":"mrs", - "code":"1010", + "code":"1014", "des":"You can delete a tenant that is not required on MRS Manager.A tenant has been added.You have checked whether the tenant to be deleted has sub-tenants. If the tenant has s", "doc_type":"usermanual", "kw":"Deleting a tenant,Tenant Management,User Guide", @@ -18686,7 +18754,7 @@ "uri":"mrs_01_0542.html", "node_id":"mrs_01_0542.xml", "product_code":"mrs", - "code":"1011", + "code":"1015", "des":"You can manage the HDFS storage directory used by a specific tenant on MRS Manager. The management operations include adding a tenant directory, modifying the directory f", "doc_type":"usermanual", "kw":"Managing a Tenant Directory,Tenant Management,User Guide", @@ -18705,7 +18773,7 @@ "uri":"mrs_01_0543.html", "node_id":"mrs_01_0543.xml", "product_code":"mrs", - "code":"1012", + "code":"1016", "des":"Tenant data is stored on Manager and in cluster components by default. When components are restored from faults or reinstalled, some tenant configuration data may be abno", "doc_type":"usermanual", "kw":"Restoring Tenant Data,Tenant Management,User Guide", @@ -18724,7 +18792,7 @@ "uri":"mrs_01_0544.html", "node_id":"mrs_01_0544.xml", "product_code":"mrs", - "code":"1013", + "code":"1017", "des":"In an MRS cluster, users can logically divide Yarn cluster nodes to combine multiple NodeManagers into a Yarn resource pool. Each NodeManager belongs to one resource pool", "doc_type":"usermanual", "kw":"Creating a Resource Pool,Tenant Management,User Guide", @@ -18743,7 +18811,7 @@ "uri":"mrs_01_0545.html", "node_id":"mrs_01_0545.xml", "product_code":"mrs", - "code":"1014", + "code":"1018", "des":"You can modify members of an existing resource pool on MRS Manager.Adding a host: Select the name of a specified host in host list on the left and click to add the selec", "doc_type":"usermanual", "kw":"Modifying a Resource Pool,Tenant Management,User Guide", @@ -18762,7 +18830,7 @@ "uri":"mrs_01_0546.html", "node_id":"mrs_01_0546.xml", "product_code":"mrs", - "code":"1015", + "code":"1019", "des":"You can delete an existing resource pool on MRS Manager.Any queue in a cluster cannot use the resource pool to be deleted as the default resource pool. Before deleting th", "doc_type":"usermanual", "kw":"Deleting a Resource Pool,Tenant Management,User Guide", @@ -18781,7 +18849,7 @@ "uri":"mrs_01_0547.html", "node_id":"mrs_01_0547.xml", "product_code":"mrs", - "code":"1016", + "code":"1020", "des":"This section describes how to modify the queue configuration for a specified tenant on MRS Manager.A tenant associated with Yarn and allocated dynamic resources has been ", "doc_type":"usermanual", "kw":"Configuring a Queue,Tenant Management,User Guide", @@ -18800,7 +18868,7 @@ "uri":"mrs_01_0548.html", "node_id":"mrs_01_0548.xml", "product_code":"mrs", - "code":"1017", + "code":"1021", "des":"After a resource pool is added, the capacity policies of available resources need to be configured for Yarn task queues. This ensures that tasks in the resource pool are ", "doc_type":"usermanual", "kw":"Configuring the Queue Capacity Policy of a Resource Pool,Tenant Management,User Guide", @@ -18819,7 +18887,7 @@ "uri":"mrs_01_0549.html", "node_id":"mrs_01_0549.xml", "product_code":"mrs", - "code":"1018", + "code":"1022", "des":"Users can clear the configuration of a queue on MRS Manager when the queue does not need resources from a resource pool or if a resource pool needs to be disassociated fr", "doc_type":"usermanual", "kw":"Clearing Configuration of a Queue,Tenant Management,User Guide", @@ -18838,7 +18906,7 @@ "uri":"mrs_01_0550.html", "node_id":"mrs_01_0550.xml", "product_code":"mrs", - "code":"1019", + "code":"1023", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backup and Restoration", @@ -18857,7 +18925,7 @@ "uri":"mrs_01_0551.html", "node_id":"mrs_01_0551.xml", "product_code":"mrs", - "code":"1020", + "code":"1024", "des":"MRS Manager provides backup and restoration for user data and system data. The backup function is provided based on components to back up Manager data (including OMS data", "doc_type":"usermanual", "kw":"Introduction,Backup and Restoration,User Guide", @@ -18876,7 +18944,7 @@ "uri":"mrs_01_0553.html", "node_id":"mrs_01_0553.xml", "product_code":"mrs", - "code":"1021", + "code":"1025", "des":"To ensure the security of metadata either on a routine basis or before and after performing critical metadata operations (such as scale-out, scale-in, patch installation,", "doc_type":"usermanual", "kw":"Backing Up Metadata,Backup and Restoration,User Guide", @@ -18895,7 +18963,7 @@ "uri":"mrs_01_0555.html", "node_id":"mrs_01_0555.xml", "product_code":"mrs", - "code":"1022", + "code":"1026", "des":"You need to restore metadata in the following scenarios: A user modifies or deletes data unexpectedly, data needs to be retrieved, system data becomes abnormal or does no", "doc_type":"usermanual", "kw":"Restoring Metadata,Backup and Restoration,User Guide", @@ -18914,7 +18982,7 @@ "uri":"mrs_01_0558.html", "node_id":"mrs_01_0558.xml", "product_code":"mrs", - "code":"1023", + "code":"1027", "des":"This section describes how to modify the parameters of a created backup task on MRS Manager to meet changing service requirements. The parameters of restoration tasks can", "doc_type":"usermanual", "kw":"Modifying a Backup Task,Backup and Restoration,User Guide", @@ -18933,7 +19001,7 @@ "uri":"mrs_01_0559.html", "node_id":"mrs_01_0559.xml", "product_code":"mrs", - "code":"1024", + "code":"1028", "des":"This section describes how to view created backup and restoration tasks and check their running status on MRS Manager.In the displayed window, click View in the Details c", "doc_type":"usermanual", "kw":"Viewing Backup and Restoration Tasks,Backup and Restoration,User Guide", @@ -18952,7 +19020,7 @@ "uri":"mrs_01_0560.html", "node_id":"mrs_01_0560.xml", "product_code":"mrs", - "code":"1025", + "code":"1029", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Management", @@ -18971,7 +19039,7 @@ "uri":"mrs_01_0561.html", "node_id":"mrs_01_0561.xml", "product_code":"mrs", - "code":"1026", + "code":"1030", "des":"The MRS cluster provides the following two types of users. Users are advised to periodically change the passwords. It is not recommended to use the default passwords.User", "doc_type":"usermanual", "kw":"Default Users of Clusters with Kerberos Authentication Disabled,Security Management,User Guide", @@ -18991,7 +19059,7 @@ "uri":"mrs_01_24044.html", "node_id":"mrs_01_24044.xml", "product_code":"mrs", - "code":"1027", + "code":"1031", "des":"The MRS cluster provides the following three types of users. Users are advised to periodically change the passwords. It is not recommended to use the default passwords.Us", "doc_type":"usermanual", "kw":"Default Users of Clusters with Kerberos Authentication Enabled,Security Management,User Guide", @@ -19010,7 +19078,7 @@ "uri":"mrs_01_0562.html", "node_id":"mrs_01_0562.xml", "product_code":"mrs", - "code":"1028", + "code":"1032", "des":"This section describes how to periodically change the login passwords of the OS users omm, ommdba, and root on MRS cluster nodes to improve the system O&M security.Passwo", "doc_type":"usermanual", "kw":"Changing the Password of an OS User,Security Management,User Guide", @@ -19029,7 +19097,7 @@ "uri":"mrs_01_0563.html", "node_id":"mrs_01_0563.xml", "product_code":"mrs", - "code":"1029", + "code":"1033", "des":"This section describes how to periodically change the password of cluster user admin to improve the system O&M security.If the password is changed, the downloaded user cr", "doc_type":"usermanual", "kw":"Changing the password of user admin,Security Management,User Guide", @@ -19049,7 +19117,7 @@ "uri":"mrs_01_0564.html", "node_id":"mrs_01_0564.xml", "product_code":"mrs", - "code":"1030", + "code":"1034", "des":"This section describes how to periodically change the password of the Kerberos administrator kadmin of the MRS cluster to improve the system O&M security.If the password ", "doc_type":"usermanual", "kw":"Changing the Password of the Kerberos Administrator,Security Management,User Guide", @@ -19069,7 +19137,7 @@ "uri":"mrs_01_0565.html", "node_id":"mrs_01_0565.xml", "product_code":"mrs", - "code":"1031", + "code":"1035", "des":"This section describes how to periodically change the passwords of the LDAP administrator rootdn:cn=root,dc=hadoop,dc=com and the LDAP user pg_search_dn:cn=pg_search_dn,o", "doc_type":"usermanual", "kw":"Changing the Passwords of the LDAP Administrator and the LDAP User,Security Management,User Guide", @@ -19088,7 +19156,7 @@ "uri":"mrs_01_0566.html", "node_id":"mrs_01_0566.xml", "product_code":"mrs", - "code":"1032", + "code":"1036", "des":"This section describes how to periodically change the password of the component running user of the MRS cluster to improve the system O&M security.If the initial password", "doc_type":"usermanual", "kw":"Changing the Password of a Component Running User,Security Management,User Guide", @@ -19108,7 +19176,7 @@ "uri":"mrs_01_0567.html", "node_id":"mrs_01_0567.xml", "product_code":"mrs", - "code":"1033", + "code":"1037", "des":"This section describes how to periodically change the password of the OMS database administrator to improve the system O&M security.The password of user ommdba cannot be ", "doc_type":"usermanual", "kw":"Changing the Password of the OMS Database Administrator,Security Management,User Guide", @@ -19127,7 +19195,7 @@ "uri":"mrs_01_0568.html", "node_id":"mrs_01_0568.xml", "product_code":"mrs", - "code":"1034", + "code":"1038", "des":"This section describes how to periodically change the password of the data access user of the OMS database to improve the system O&M security.The OMS service needs to be ", "doc_type":"usermanual", "kw":"Changing the Password of the Data Access User of the OMS Database,Security Management,User Guide", @@ -19146,7 +19214,7 @@ "uri":"mrs_01_0569.html", "node_id":"mrs_01_0569.xml", "product_code":"mrs", - "code":"1035", + "code":"1039", "des":"This section describes how to periodically change the password of the component database user to improve the system O&M security.The services need to be restarted for the", "doc_type":"usermanual", "kw":"Changing the Password of a Component Database User,Security Management,User Guide", @@ -19166,7 +19234,7 @@ "uri":"mrs_01_0571.html", "node_id":"mrs_01_0571.xml", "product_code":"mrs", - "code":"1036", + "code":"1040", "des":"HA certificates are used to encrypt the communication between active/standby processes and HA processes to ensure the communication security. This section describes how t", "doc_type":"usermanual", "kw":"Replacing the HA Certificate,Security Management,User Guide", @@ -19186,7 +19254,7 @@ "uri":"mrs_01_0572.html", "node_id":"mrs_01_0572.xml", "product_code":"mrs", - "code":"1037", + "code":"1041", "des":"When a cluster is installed, an encryption key is generated automatically to store the security information in the cluster (such as all database user passwords and key fi", "doc_type":"usermanual", "kw":"Updating Cluster Keys,Security Management,User Guide", @@ -19205,7 +19273,7 @@ "uri":"mrs_01_0573.html", "node_id":"mrs_01_0573.xml", "product_code":"mrs", - "code":"1038", + "code":"1042", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Permissions Management", @@ -19224,7 +19292,7 @@ "uri":"mrs_01_0420.html", "node_id":"mrs_01_0420.xml", "product_code":"mrs", - "code":"1039", + "code":"1043", "des":"This section describes how to create a role on MRS Manager and authorize and manage Manager and components.Up to 1,000 roles can be created on MRS Manager.You have learne", "doc_type":"usermanual", "kw":"Creating a Role,Permissions Management,User Guide", @@ -19243,7 +19311,7 @@ "uri":"mrs_01_0421.html", "node_id":"mrs_01_0421.xml", "product_code":"mrs", - "code":"1040", + "code":"1044", "des":"This section describes how to create user groups and specify their operation permissions on MRS Manager. Management of single or multiple users can be unified in the user", "doc_type":"usermanual", "kw":"Creating a User Group,Permissions Management,User Guide", @@ -19262,7 +19330,7 @@ "uri":"mrs_01_0422.html", "node_id":"mrs_01_0422.xml", "product_code":"mrs", - "code":"1041", + "code":"1045", "des":"This section describes how to create users on MRS Manager based on site requirements and specify their operation permissions to meet service requirements.Up to 1,000 user", "doc_type":"usermanual", "kw":"Creating a User,Permissions Management,User Guide", @@ -19281,7 +19349,7 @@ "uri":"mrs_01_0423.html", "node_id":"mrs_01_0423.xml", "product_code":"mrs", - "code":"1042", + "code":"1046", "des":"This section describes how to modify user information on MRS Manager, including information about the user group, primary group, role, and description.If you change user ", "doc_type":"usermanual", "kw":"Modifying User Information,Permissions Management,User Guide", @@ -19300,7 +19368,7 @@ "uri":"mrs_01_0424.html", "node_id":"mrs_01_0424.xml", "product_code":"mrs", - "code":"1043", + "code":"1047", "des":"This section describes how to lock users in MRS clusters. A locked user cannot log in to MRS Manager or perform security authentication in the cluster.A locked user can b", "doc_type":"usermanual", "kw":"Locking a User,Permissions Management,User Guide", @@ -19319,7 +19387,7 @@ "uri":"mrs_01_0425.html", "node_id":"mrs_01_0425.xml", "product_code":"mrs", - "code":"1044", + "code":"1048", "des":"If a user is locked because the number of login attempts exceeds the value of Number of Password Retries, or the user is manually locked by the administrator, the adminis", "doc_type":"usermanual", "kw":"Unlocking a User,Permissions Management,User Guide", @@ -19338,7 +19406,7 @@ "uri":"mrs_01_0426.html", "node_id":"mrs_01_0426.xml", "product_code":"mrs", - "code":"1045", + "code":"1049", "des":"If an MRS cluster user is not required, the administrator can delete the user on MRS Manager.", "doc_type":"usermanual", "kw":"Deleting a User,Permissions Management,User Guide", @@ -19357,7 +19425,7 @@ "uri":"mrs_01_0427.html", "node_id":"mrs_01_0427.xml", "product_code":"mrs", - "code":"1046", + "code":"1050", "des":"Passwords of Human-Machine system users must be regularly changed to ensure MRS cluster security. This section describes how to change your passwords on MRS Manager.If a ", "doc_type":"usermanual", "kw":"Changing the Password of an Operation User,Permissions Management,User Guide", @@ -19377,7 +19445,7 @@ "uri":"mrs_01_0428.html", "node_id":"mrs_01_0428.xml", "product_code":"mrs", - "code":"1047", + "code":"1051", "des":"This section describes how to initialize a password on MRS Manager if a user forgets the password or the password of a public account needs to be changed regularly. After", "doc_type":"usermanual", "kw":"Initializing the Password of a System User,Permissions Management,User Guide", @@ -19397,7 +19465,7 @@ "uri":"mrs_01_0429.html", "node_id":"mrs_01_0429.xml", "product_code":"mrs", - "code":"1048", + "code":"1052", "des":"When a user develops big data applications and runs them in an MRS cluster that supports Kerberos authentication, the user needs to prepare a user authentication file for", "doc_type":"usermanual", "kw":"Downloading a User Authentication File,Permissions Management,User Guide", @@ -19416,7 +19484,7 @@ "uri":"mrs_01_0430.html", "node_id":"mrs_01_0430.xml", "product_code":"mrs", - "code":"1049", + "code":"1053", "des":"This section describes how to set password and user login security rules as well as user lock rules. Password policies set on MRS Manager take effect for Human-machine us", "doc_type":"usermanual", "kw":"Modifying a Password Policy,Permissions Management,User Guide", @@ -19435,7 +19503,7 @@ "uri":"mrs_01_0340.html", "node_id":"mrs_01_0340.xml", "product_code":"mrs", - "code":"1050", + "code":"1054", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"MRS Multi-User Permission Management", @@ -19454,7 +19522,7 @@ "uri":"mrs_01_0341.html", "node_id":"mrs_01_0341.xml", "product_code":"mrs", - "code":"1051", + "code":"1055", "des":"MRS Cluster UsersIndicate the security accounts of Manager, including usernames and passwords. These accounts are used to access resources in MRS clusters. Each MRS clust", "doc_type":"usermanual", "kw":"Users and Permissions of MRS Clusters,MRS Multi-User Permission Management,User Guide", @@ -19474,7 +19542,7 @@ "uri":"mrs_01_0342.html", "node_id":"mrs_01_0342.xml", "product_code":"mrs", - "code":"1052", + "code":"1056", "des":"The MRS cluster provides the following three types of users. Users are advised to periodically change the passwords. It is not recommended to use the default passwords.Us", "doc_type":"usermanual", "kw":"Default Users of Clusters with Kerberos Authentication Enabled,MRS Multi-User Permission Management,", @@ -19493,7 +19561,7 @@ "uri":"mrs_01_0343.html", "node_id":"mrs_01_0343.xml", "product_code":"mrs", - "code":"1053", + "code":"1057", "des":"This section describes how to create a role on Manager and authorize and manage Manager and components.Up to 1000 roles can be created on Manager.The operations described", "doc_type":"usermanual", "kw":"Creating a Role,MRS Multi-User Permission Management,User Guide", @@ -19513,7 +19581,7 @@ "uri":"mrs_01_0344.html", "node_id":"mrs_01_0344.xml", "product_code":"mrs", - "code":"1054", + "code":"1058", "des":"This section describes how to create user groups and specify their operation permissions on Manager. Management of single or multiple users can be unified in the user gro", "doc_type":"usermanual", "kw":"Creating a User Group,MRS Multi-User Permission Management,User Guide", @@ -19533,7 +19601,7 @@ "uri":"mrs_01_0345.html", "node_id":"mrs_01_0345.xml", "product_code":"mrs", - "code":"1055", + "code":"1059", "des":"This section describes how to create users on Manager based on site requirements and specify their operation permissions to meet service requirements.Up to 1000 users can", "doc_type":"usermanual", "kw":"Creating a User,MRS Multi-User Permission Management,User Guide", @@ -19553,7 +19621,7 @@ "uri":"mrs_01_0346.html", "node_id":"mrs_01_0346.xml", "product_code":"mrs", - "code":"1056", + "code":"1060", "des":"This section describes how to modify user information on Manager, including information about the user group, primary group, role, and description.This operation is suppo", "doc_type":"usermanual", "kw":"Modifying User Information,MRS Multi-User Permission Management,User Guide", @@ -19573,7 +19641,7 @@ "uri":"mrs_01_0347.html", "node_id":"mrs_01_0347.xml", "product_code":"mrs", - "code":"1057", + "code":"1061", "des":"This section describes how to lock users in MRS clusters. A locked user cannot log in to Manager or perform security authentication in the cluster. This operation is supp", "doc_type":"usermanual", "kw":"Locking a User,MRS Multi-User Permission Management,User Guide", @@ -19593,7 +19661,7 @@ "uri":"mrs_01_0348.html", "node_id":"mrs_01_0348.xml", "product_code":"mrs", - "code":"1058", + "code":"1062", "des":"If a user is locked because the number of login attempts exceeds the value of Number of Password Retries, or the user is manually locked by the administrator, the adminis", "doc_type":"usermanual", "kw":"Unlocking a User,MRS Multi-User Permission Management,User Guide", @@ -19613,7 +19681,7 @@ "uri":"mrs_01_0349.html", "node_id":"mrs_01_0349.xml", "product_code":"mrs", - "code":"1059", + "code":"1063", "des":"The administrator can delete an MRS cluster user that is not required on MRS Manager. Deleting a user is allowed only in clusters with Kerberos authentication enabled or ", "doc_type":"usermanual", "kw":"Deleting a User,MRS Multi-User Permission Management,User Guide", @@ -19633,7 +19701,7 @@ "uri":"mrs_01_0350.html", "node_id":"mrs_01_0350.xml", "product_code":"mrs", - "code":"1060", + "code":"1064", "des":"Passwords of Human-machine system users must be regularly changed to ensure MRS cluster security. This section describes how to change passwords on MRS Manager.If a new p", "doc_type":"usermanual", "kw":"Changing the Password of an Operation User,MRS Multi-User Permission Management,User Guide", @@ -19653,7 +19721,7 @@ "uri":"mrs_01_0351.html", "node_id":"mrs_01_0351.xml", "product_code":"mrs", - "code":"1061", + "code":"1065", "des":"This section describes how to initialize a password on Manager if a user forgets the password or the password of a public account needs to be changed regularly. After pas", "doc_type":"usermanual", "kw":"Initializing the Password of a System User,MRS Multi-User Permission Management,User Guide", @@ -19673,7 +19741,7 @@ "uri":"mrs_01_0352.html", "node_id":"mrs_01_0352.xml", "product_code":"mrs", - "code":"1062", + "code":"1066", "des":"When a user develops big data applications and runs them in an MRS cluster that supports Kerberos authentication, the user needs to prepare a Machine-machine user authent", "doc_type":"usermanual", "kw":"Downloading a User Authentication File,MRS Multi-User Permission Management,User Guide", @@ -19693,7 +19761,7 @@ "uri":"mrs_01_0353.html", "node_id":"mrs_01_0353.xml", "product_code":"mrs", - "code":"1063", + "code":"1067", "des":"Because password policies are critical to the user management security, modify them based on service security requirements. Otherwise, security risks may be incurred.This", "doc_type":"usermanual", "kw":"Modifying a Password Policy,MRS Multi-User Permission Management,User Guide", @@ -19713,7 +19781,7 @@ "uri":"mrs_01_0354.html", "node_id":"mrs_01_0354.xml", "product_code":"mrs", - "code":"1064", + "code":"1068", "des":"If cluster A needs to access the resources of cluster B, the mutual trust relationship must be configured between these two clusters.If no trust relationship is configure", "doc_type":"usermanual", "kw":"Configuring Cross-Cluster Mutual Trust Relationships,MRS Multi-User Permission Management,User Guide", @@ -19733,7 +19801,7 @@ "uri":"mrs_01_0355.html", "node_id":"mrs_01_0355.xml", "product_code":"mrs", - "code":"1065", + "code":"1069", "des":"After cross-cluster mutual trust is configured, permission must be configured for users in the local cluster, so that the users can access the same resources in the peer ", "doc_type":"usermanual", "kw":"Configuring Users to Access Resources of a Trusted Cluster,MRS Multi-User Permission Management,User", @@ -19753,7 +19821,7 @@ "uri":"mrs_01_0632.html", "node_id":"mrs_01_0632.xml", "product_code":"mrs", - "code":"1066", + "code":"1070", "des":"When fine-grained permission control is enabled, you can configure OBS access permissions to implement access control on directories in OBS file systems.This section appl", "doc_type":"usermanual", "kw":"Configuring Fine-Grained Permissions for MRS Multi-User Access to OBS,MRS Multi-User Permission Mana", @@ -19773,7 +19841,7 @@ "uri":"mrs_01_0574.html", "node_id":"mrs_01_0574.xml", "product_code":"mrs", - "code":"1067", + "code":"1071", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Patch Operation Guide", @@ -19792,7 +19860,7 @@ "uri":"mrs_01_0575.html", "node_id":"mrs_01_0575.xml", "product_code":"mrs", - "code":"1068", + "code":"1072", "des":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", "doc_type":"usermanual", "kw":"Patch Operation Guide for Versions Earlier than MRS 1.7.0,Patch Operation Guide,User Guide", @@ -19812,10 +19880,10 @@ "uri":"mrs_01_0576.html", "node_id":"mrs_01_0576.xml", "product_code":"mrs", - "code":"1069", + "code":"1073", "des":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", "doc_type":"usermanual", - "kw":"Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0,Patch Operation Guide,User Guide", + "kw":"from MRS 1.7.0 to MRS 2.1.0Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0Earlier Tha", "search_title":"", "metedata":[ { @@ -19824,14 +19892,14 @@ "documenttype":"usermanual" } ], - "title":"Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0", + "title":"from MRS 1.7.0 to MRS 2.1.0Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0Earlier Than MRS 3.x", "githuburl":"" }, { "uri":"mrs_01_0577.html", "node_id":"mrs_01_0577.xml", "product_code":"mrs", - "code":"1070", + "code":"1074", "des":"The rolling patch function indicates that patches are installed or uninstalled for one or more services in a cluster by performing a rolling service restart (restarting s", "doc_type":"usermanual", "kw":"Supporting Rolling Patches,Patch Operation Guide,User Guide", @@ -19850,7 +19918,7 @@ "uri":"mrs_01_0578.html", "node_id":"mrs_01_0578.xml", "product_code":"mrs", - "code":"1071", + "code":"1075", "des":"If some hosts are isolated in a cluster, perform the following operations to restore patches for these isolated hosts after patch installation on other hosts in the clust", "doc_type":"usermanual", "kw":"Restoring Patches for the Isolated Hosts,MRS Manager Operation Guide (Applicable to 2.x and Earlier ", @@ -19869,7 +19937,7 @@ "uri":"mrs_01_0579.html", "node_id":"mrs_01_0579.xml", "product_code":"mrs", - "code":"1072", + "code":"1076", "des":"After modifying the configuration items of a big data component, you need to restart the corresponding service to make new configurations take effect. If you use a normal", "doc_type":"usermanual", "kw":"Rolling Restart,MRS Manager Operation Guide (Applicable to 2.x and Earlier Versions),User Guide", @@ -19888,7 +19956,7 @@ "uri":"mrs_01_0528.html", "node_id":"mrs_01_0528.xml", "product_code":"mrs", - "code":"1073", + "code":"1077", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Description", @@ -19908,7 +19976,7 @@ "uri":"mrs_01_0419.html", "node_id":"mrs_01_0419.xml", "product_code":"mrs", - "code":"1074", + "code":"1078", "des":"The Hadoop community version provides two authentication modes: Kerberos authentication (security mode) and Simple authentication (normal mode). When creating a cluster, ", "doc_type":"usermanual", "kw":"Security Configuration Suggestions for Clusters with Kerberos Authentication Disabled,Security Descr", @@ -19927,7 +19995,7 @@ "uri":"mrs_07_020001.html", "node_id":"mrs_07_020001.xml", "product_code":"mrs", - "code":"1075", + "code":"1079", "des":"For clusters in security mode with Kerberos authentication enabled, security authentication is required during application development.Kerberos, is now used to a concept ", "doc_type":"usermanual", "kw":"Security Authentication Principles and Mechanisms,Security Description,User Guide", @@ -19945,7 +20013,7 @@ "uri":"mrs_01_0785.html", "node_id":"mrs_01_0785.xml", "product_code":"mrs", - "code":"1076", + "code":"1080", "des":"Table 1 lists forbidden operations during the routine cluster operation and maintenance process.The following tables list the high-risk operations during the operation an", "doc_type":"usermanual", "kw":"High-Risk Operations,User Guide", @@ -19963,7 +20031,7 @@ "uri":"mrs_01_0316.html", "node_id":"mrs_01_0316.xml", "product_code":"mrs", - "code":"1077", + "code":"1081", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backup and Restoration", @@ -19982,7 +20050,7 @@ "uri":"mrs_01_0605.html", "node_id":"mrs_01_0605.xml", "product_code":"mrs", - "code":"1078", + "code":"1082", "des":"This section describes how to back up and restore data on the MRS console.Backup and restoration operations on the console apply only to clusters of MRS 3.x or earlier.Ba", "doc_type":"usermanual", "kw":"Before You Start,Backup and Restoration,User Guide", @@ -20002,7 +20070,7 @@ "uri":"mrs_01_0317.html", "node_id":"mrs_01_0317.xml", "product_code":"mrs", - "code":"1079", + "code":"1083", "des":"MRS provides backup and restoration for user data and system data. The backup function is provided based on components to back up Manager data (including OMS data and Lda", "doc_type":"usermanual", "kw":"Introduction,Backup and Restoration,User Guide", @@ -20021,7 +20089,7 @@ "uri":"mrs_01_0319.html", "node_id":"mrs_01_0319.xml", "product_code":"mrs", - "code":"1080", + "code":"1084", "des":"To ensure metadata security or before and after a critical operation (such as scale-out/scale-in, patch installation, upgrade, or migration) on the metadata, you need to ", "doc_type":"usermanual", "kw":"Backing Up Metadata,Backup and Restoration,User Guide", @@ -20041,7 +20109,7 @@ "uri":"mrs_01_0321.html", "node_id":"mrs_01_0321.xml", "product_code":"mrs", - "code":"1081", + "code":"1085", "des":"Metadata needs to be recovered in the following scenarios:Data is modified or deleted unexpectedly and needs to be restored.After a critical operation (such as an upgrade", "doc_type":"usermanual", "kw":"Restoring Metadata,Backup and Restoration,User Guide", @@ -20061,7 +20129,7 @@ "uri":"mrs_01_0324.html", "node_id":"mrs_01_0324.xml", "product_code":"mrs", - "code":"1082", + "code":"1086", "des":"You can modify the parameters of a created backup task on MRS to meet changing service requirements. The parameters of restoration tasks can only be viewed but cannot be ", "doc_type":"usermanual", "kw":"Modifying Backup Tasks,Backup and Restoration,User Guide", @@ -20081,7 +20149,7 @@ "uri":"mrs_01_0325.html", "node_id":"mrs_01_0325.xml", "product_code":"mrs", - "code":"1083", + "code":"1087", "des":"You can view created backup and restoration tasks and check their running status on the MRS console.You have synchronized IAM users. (On the Dashboard page, click Synchro", "doc_type":"usermanual", "kw":"Viewing Backup and Restoration Tasks,Backup and Restoration,User Guide", @@ -20101,7 +20169,7 @@ "uri":"mrs_01_0444.html", "node_id":"mrs_01_0444.xml", "product_code":"mrs", - "code":"1084", + "code":"1088", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Backup and Restoration", @@ -20119,7 +20187,7 @@ "uri":"mrs_01_0445.html", "node_id":"mrs_01_0445.xml", "product_code":"mrs", - "code":"1085", + "code":"1089", "des":"If the source cluster and destination cluster are deployed in different VPCs in the same region, create a network connection between the two VPCs to establish a data tran", "doc_type":"usermanual", "kw":"HDFS Data,Data Backup and Restoration,User Guide", @@ -20139,7 +20207,7 @@ "uri":"mrs_01_0446.html", "node_id":"mrs_01_0446.xml", "product_code":"mrs", - "code":"1086", + "code":"1090", "des":"Hive table data is stored in HDFS. Table data and the metadata of the table data is centrally migrated in directories by HDFS in a unified manner. Metadata of Hive tables", "doc_type":"usermanual", "kw":"Hive Metadata,Data Backup and Restoration,User Guide", @@ -20158,7 +20226,7 @@ "uri":"mrs_01_0447.html", "node_id":"mrs_01_0447.xml", "product_code":"mrs", - "code":"1087", + "code":"1091", "des":"Hive data is not backed up independently. For details, see HDFS Data.", "doc_type":"usermanual", "kw":"Hive Data,Data Backup and Restoration,User Guide", @@ -20177,7 +20245,7 @@ "uri":"mrs_01_0448.html", "node_id":"mrs_01_0448.xml", "product_code":"mrs", - "code":"1088", + "code":"1092", "des":"Currently, HBase data can be backed up in the following modes:SnapshotsReplicationExportCopyTableHTable APIOffline backup of HDFS dataTable 1 compares the impact of opera", "doc_type":"usermanual", "kw":"HBase Data,Data Backup and Restoration,User Guide", @@ -20197,7 +20265,7 @@ "uri":"mrs_01_0449.html", "node_id":"mrs_01_0449.xml", "product_code":"mrs", - "code":"1089", + "code":"1093", "des":"MirrorMaker is a powerful tool for Kafka data synchronization. It is used when data needs to be synchronized between two Kafka clusters or when data in the original Kafka", "doc_type":"usermanual", "kw":"Kafka Data,Data Backup and Restoration,User Guide", @@ -20217,7 +20285,7 @@ "uri":"mrs_01_9002.html", "node_id":"mrs_01_9002.xml", "product_code":"mrs", - "code":"1090", + "code":"1094", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Appendix", @@ -20235,7 +20303,7 @@ "uri":"mrs_01_0614.html", "node_id":"mrs_01_0614.xml", "product_code":"mrs", - "code":"1091", + "code":"1095", "des":"Custers of versions earlier than MRS 3.x use MRS Manager to manage and monitor MRS clusters. On the Cluster Management page of the MRS management console, you can view cl", "doc_type":"usermanual", "kw":"Precautions for MRS 3.x,Appendix,User Guide", @@ -20253,7 +20321,7 @@ "uri":"mrs_01_0392.html", "node_id":"mrs_01_0392.xml", "product_code":"mrs", - "code":"1092", + "code":"1096", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"cmpntguide", "kw":"Installing the Flume Client", @@ -20271,7 +20339,7 @@ "uri":"mrs_01_1594.html", "node_id":"mrs_01_1594.xml", "product_code":"mrs", - "code":"1093", + "code":"1097", "des":"To use Flume to collect logs, you must install the Flume client on a log host. You can create an ECS and install the Flume client on it.This section applies to MRS 3.x or", "doc_type":"cmpntguide", "kw":"Installing the Flume Client on Clusters of Versions Earlier Than MRS 3.x,Installing the Flume Client", @@ -20289,7 +20357,7 @@ "uri":"mrs_01_1595.html", "node_id":"mrs_01_1595.xml", "product_code":"mrs", - "code":"1094", + "code":"1098", "des":"To use Flume to collect logs, you must install the Flume client on a log host. You can create an ECS and install the Flume client on it.This section applies to MRS 3.x or", "doc_type":"cmpntguide", "kw":"Installing the Flume Client on MRS 3.x or Later Clusters,Installing the Flume Client,User Guide", @@ -20307,7 +20375,7 @@ "uri":"en-us_topic_0000001349287889.html", "node_id":"en-us_topic_0000001349287889.xml", "product_code":"mrs", - "code":"1095", + "code":"1099", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQ", @@ -20325,7 +20393,7 @@ "uri":"mrs_03_0002.html", "node_id":"mrs_03_0002.xml", "product_code":"mrs", - "code":"1096", + "code":"1100", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"MRS Overview", @@ -20343,7 +20411,7 @@ "uri":"mrs_03_0001.html", "node_id":"mrs_03_0001.xml", "product_code":"mrs", - "code":"1097", + "code":"1101", "des":"MapReduce Service (MRS) is an enterprise-grade big data platform that allows you to quickly build and operate economical, secure, full-stack, cloud-native big data enviro", "doc_type":"faq", "kw":"What Is MRS Used For?,MRS Overview,User Guide", @@ -20362,7 +20430,7 @@ "uri":"mrs_03_1005.html", "node_id":"mrs_03_1005.xml", "product_code":"mrs", - "code":"1098", + "code":"1102", "des":"MRS supports Hadoop 3.1.x and will soon support other mainstream Hadoop versions released by the community. Table 1 lists the component versions supported by MRS.", "doc_type":"faq", "kw":"What Types of Distributed Storage Does MRS Support?,MRS Overview,User Guide", @@ -20381,7 +20449,7 @@ "uri":"mrs_03_1012.html", "node_id":"mrs_03_1012.xml", "product_code":"mrs", - "code":"1099", + "code":"1103", "des":"If you want to use a self-defined security group when buying a cluster, you need to enable port 9022 or select Auto create in Security Group on the MRS console.", "doc_type":"faq", "kw":"How Do I Create an MRS Cluster Using a Custom Security Group?,MRS Overview,User Guide", @@ -20399,7 +20467,7 @@ "uri":"mrs_03_1013.html", "node_id":"mrs_03_1013.xml", "product_code":"mrs", - "code":"1100", + "code":"1104", "des":"MapReduce Service (MRS) is a service you can use to deploy and manage Hadoop-based components on the Cloud. It enables you to deploy Hadoop clusters with a few clicks. MR", "doc_type":"faq", "kw":"How Do I Use MRS?,MRS Overview,User Guide", @@ -20418,7 +20486,7 @@ "uri":"mrs_03_1105.html", "node_id":"mrs_03_1105.xml", "product_code":"mrs", - "code":"1101", + "code":"1105", "des":"Phoenix does not support connection pool configuration. You are advised to write code to implement a tool class for managing connections and simulate a connection pool.", "doc_type":"faq", "kw":"Can I Configure a Phoenix Connection Pool?,MRS Overview,User Guide", @@ -20437,7 +20505,7 @@ "uri":"mrs_03_1019.html", "node_id":"mrs_03_1019.xml", "product_code":"mrs", - "code":"1102", + "code":"1106", "des":"You can change the network segment. On the cluster Dashboard page of MRS console, click Change Subnet to the right of Default Subnet, and select a subnet in the VPC of th", "doc_type":"faq", "kw":"Does MRS Support Change of the Network Segment?,MRS Overview,User Guide", @@ -20455,7 +20523,7 @@ "uri":"mrs_03_1125.html", "node_id":"mrs_03_1125.xml", "product_code":"mrs", - "code":"1103", + "code":"1107", "des":"You cannot downgrade the specifications of an MRS cluster node by using the console. If you want to downgrade an MRS cluster node's specifications, contact technical supp", "doc_type":"faq", "kw":"Can I Downgrade the Specifications of an MRS Cluster Node?,MRS Overview,User Guide", @@ -20473,7 +20541,7 @@ "uri":"mrs_03_1046.html", "node_id":"mrs_03_1046.xml", "product_code":"mrs", - "code":"1104", + "code":"1108", "des":"Hive and HDFSHive is an Apache Hadoop project. Hive uses Hadoop Distributed File System (HDFS) as its file storage system. Hive parses and processes structured data store", "doc_type":"faq", "kw":"What Is the Relationship Between Hive and Other Components?,MRS Overview,User Guide", @@ -20491,7 +20559,7 @@ "uri":"mrs_03_1048.html", "node_id":"mrs_03_1048.xml", "product_code":"mrs", - "code":"1105", + "code":"1109", "des":"Clusters of MRS 1.9.x support Hive on Spark.Clusters of MRS 3.x or later support Hive on Spark.You can use Hive on Tez for the clusters of other versions.", "doc_type":"faq", "kw":"Does an MRS Cluster Support Hive on Spark?,MRS Overview,User Guide", @@ -20510,7 +20578,7 @@ "uri":"mrs_03_1081.html", "node_id":"mrs_03_1081.xml", "product_code":"mrs", - "code":"1106", + "code":"1110", "des":"Hive 3.1 has the following differences when compared with Hive 1.2:String cannot be converted to int.The user-defined functions (UDFs) of the Date type are changed to Hiv", "doc_type":"faq", "kw":"What Are the Differences Between Hive Versions?,MRS Overview,User Guide", @@ -20528,7 +20596,7 @@ "uri":"mrs_03_1095.html", "node_id":"mrs_03_1095.xml", "product_code":"mrs", - "code":"1107", + "code":"1111", "des":"MRS cluster 2.0.5 or later supports Hive connections on DataLake Governance Center (DGC) and provides the IAM user synchronization function.", "doc_type":"faq", "kw":"Which MRS Cluster Version Supports Hive Connection and User Synchronization?,MRS Overview,User Guide", @@ -20546,7 +20614,7 @@ "uri":"mrs_03_1062.html", "node_id":"mrs_03_1062.xml", "product_code":"mrs", - "code":"1108", + "code":"1112", "des":"The data processed by MRS is from OBS or HDFS. OBS is an object-based storage service that provides secure, reliable, and cost-effective storage of huge amounts of data. ", "doc_type":"faq", "kw":"What Are the Differences Between OBS and HDFS in Data Storage?,MRS Overview,User Guide", @@ -20564,7 +20632,7 @@ "uri":"mrs_03_1092.html", "node_id":"mrs_03_1092.xml", "product_code":"mrs", - "code":"1109", + "code":"1113", "des":"Download it from https://github.com/Intel-bigdata/HiBench.", "doc_type":"faq", "kw":"How Do I Obtain the Hadoop Pressure Test Tool?,MRS Overview,User Guide", @@ -20582,7 +20650,7 @@ "uri":"mrs_03_1065.html", "node_id":"mrs_03_1065.xml", "product_code":"mrs", - "code":"1110", + "code":"1114", "des":"Impala and HDFSImpala uses HDFS as its file storage system. Impala parses and processes structured data, while HDFS provides reliable underlying storage. Impala provides ", "doc_type":"faq", "kw":"What Is the Relationship Between Impala and Other Components?,MRS Overview,User Guide", @@ -20600,7 +20668,7 @@ "uri":"mrs_03_2022.html", "node_id":"mrs_03_2022.xml", "product_code":"mrs", - "code":"1111", + "code":"1115", "des":"The open-source third-party packages on which the open-source components integrated by MRS depend contain SDK usage examples. Public IP addresses such as 12.1.2.3, 54.123", "doc_type":"faq", "kw":"Statement About the Public IP Addresses in the Open-Source Third-Party SDK Integrated by MRS,MRS Ove", @@ -20619,7 +20687,7 @@ "uri":"mrs_03_1066.html", "node_id":"mrs_03_1066.xml", "product_code":"mrs", - "code":"1112", + "code":"1116", "des":"Kudu is designed based on the HBase structure and can implement fast random read/write and update functions that HBase is good at. Kudu and HBase are similar in architect", "doc_type":"faq", "kw":"What Is the Relationship Between Kudu and HBase?,MRS Overview,User Guide", @@ -20637,7 +20705,7 @@ "uri":"mrs_03_1068.html", "node_id":"mrs_03_1068.xml", "product_code":"mrs", - "code":"1113", + "code":"1117", "des":"MRS does not support Hive on Kudu.Currently, MRS supports only the following two methods to access Kudu:Access Kudu through Impala tables.Access and operate Kudu tables u", "doc_type":"faq", "kw":"Does MRS Support Running Hive on Kudu?,MRS Overview,User Guide", @@ -20655,7 +20723,7 @@ "uri":"mrs_03_1133.html", "node_id":"mrs_03_1133.xml", "product_code":"mrs", - "code":"1114", + "code":"1118", "des":"GaussDB (for MySQL) is recommended for scenarios, such as data updates, online transaction processing (OLTP), and complex analysis of 1 billion data records.Impala and Ku", "doc_type":"faq", "kw":"What Are the Solutions for processing 1 Billion Data Records?,MRS Overview,User Guide", @@ -20673,7 +20741,7 @@ "uri":"mrs_03_1137.html", "node_id":"mrs_03_1137.xml", "product_code":"mrs", - "code":"1115", + "code":"1119", "des":"MRS does not support the change of the DBService IP address.", "doc_type":"faq", "kw":"Can I Change the IP address of DBService?,MRS Overview,User Guide", @@ -20691,7 +20759,7 @@ "uri":"mrs_03_1155.html", "node_id":"mrs_03_1155.xml", "product_code":"mrs", - "code":"1116", + "code":"1120", "des":"MRS sudo log files record operations performed by user omm and are helpful for fault locating. You can delete the logs of the earliest date to release storage space.If th", "doc_type":"faq", "kw":"Can I Clear MRS sudo Logs?,MRS Overview,User Guide", @@ -20709,7 +20777,7 @@ "uri":"en-us_topic_0000001442653893.html", "node_id":"en-us_topic_0000001442653893.xml", "product_code":"mrs", - "code":"1117", + "code":"1121", "des":"In MRS cluster 2.1.0, the Storm log cannot exceed 20 GB. If the Storm log exceeds 20 GB, the log files will be deleted cyclically. Logs are stored on the system disk, the", "doc_type":"usermanual", "kw":"Is the Storm Log also limited to 20 GB in MRS cluster 2.1.0?,MRS Overview,User Guide", @@ -20727,7 +20795,7 @@ "uri":"en-us_topic_0000001442773925.html", "node_id":"en-us_topic_0000001442773925.xml", "product_code":"mrs", - "code":"1118", + "code":"1122", "des":"ThriftServer is a JDBC API. You can use JDBC to connect to ThriftServer to access SparkSQL data. Therefore, you can see JDBCServer in Spark components, but not ThriftServ", "doc_type":"usermanual", "kw":"What Is Spark ThriftServer?,MRS Overview,User Guide", @@ -20745,7 +20813,7 @@ "uri":"en-us_topic_0000001442494337.html", "node_id":"en-us_topic_0000001442494337.xml", "product_code":"mrs", - "code":"1119", + "code":"1123", "des":"Kafka supports PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL.", "doc_type":"usermanual", "kw":"What Access Protocols Are Supported by Kafka?,MRS Overview,User Guide", @@ -20763,7 +20831,7 @@ "uri":"en-us_topic_0000001392255170.html", "node_id":"en-us_topic_0000001392255170.xml", "product_code":"mrs", - "code":"1120", + "code":"1124", "des":"Zstandard (zstd) is an open-source fast lossless compression algorithm. The compression ratio of zstd is twice that of orc. For details, see https://github.com/L-Angel/co", "doc_type":"usermanual", "kw":"What Is the Compression Ratio of zstd?,MRS Overview,User Guide", @@ -20781,10 +20849,10 @@ "uri":"mrs_03_1202.html", "node_id":"mrs_03_1202.xml", "product_code":"mrs", - "code":"1121", + "code":"1125", "des":"The HDFS, YARN, and MapReduce components are integrated in Hadoop. If the three components are unavailable when are MRS cluster is created, select Hadoop instead. After a", "doc_type":"faq", - "kw":"Why Are the HDFS, YARN, and MapReduce Components Unavailable When an MRS Cluster Is Created?,MRS Ove", + "kw":"CreatedWhy Are the HDFS, YARN, and MapReduce Components Unavailable When an MRS Cluster Is BoughtCre", "search_title":"", "metedata":[ { @@ -20793,17 +20861,17 @@ "prodname":"mrs" } ], - "title":"Why Are the HDFS, YARN, and MapReduce Components Unavailable When an MRS Cluster Is Created?", + "title":"CreatedWhy Are the HDFS, YARN, and MapReduce Components Unavailable When an MRS Cluster Is BoughtCreated?", "githuburl":"" }, { "uri":"mrs_03_1204.html", "node_id":"mrs_03_1204.xml", "product_code":"mrs", - "code":"1122", + "code":"1126", "des":"If you create a cluster of a version earlier than MRS 3.x, ZooKeeper is installed by default and is not displayed on the GUI.If you create a cluster of MRS 3.x or later, ", "doc_type":"faq", - "kw":"Why Is the ZooKeeper Component Unavailable When an MRS Cluster Is Created?,MRS Overview,User Guide", + "kw":"CreatedWhy Is the ZooKeeper Component Unavailable When an MRS Cluster Is BoughtCreated?,MRS Overview", "search_title":"", "metedata":[ { @@ -20812,14 +20880,14 @@ "prodname":"mrs" } ], - "title":"Why Is the ZooKeeper Component Unavailable When an MRS Cluster Is Created?", + "title":"CreatedWhy Is the ZooKeeper Component Unavailable When an MRS Cluster Is BoughtCreated?", "githuburl":"" }, { "uri":"mrs_03_1216.html", "node_id":"mrs_03_1216.xml", "product_code":"mrs", - "code":"1123", + "code":"1127", "des":"For MRS 3.1.0 clusters, Python 2.7 or 3.x is recommended for Spark tasks.", "doc_type":"usermanual", "kw":"Which Python Versions Are Supported by Spark Tasks in an MRS 3.1.0 Cluster?,MRS Overview,User Guide", @@ -20837,7 +20905,7 @@ "uri":"mrs_03_1221.html", "node_id":"mrs_03_1221.xml", "product_code":"mrs", - "code":"1124", + "code":"1128", "des":"Create a tenant on Manager.Roles, computing resources, and storage resources are automatically created when tenants are created.The new role has permissions on the comput", "doc_type":"usermanual", "kw":"How Do I Enable Different Service Programs to Use Different YARN Queues?,MRS Overview,User Guide", @@ -20855,8 +20923,8 @@ "uri":"mrs_03_1233.html", "node_id":"mrs_03_1233.xml", "product_code":"mrs", - "code":"1125", - "des":"You can access Manager from the MRS management console.Manager is classified as MRS Manager and FusionInsight Manager.MRS Manager is the manager page of MRS 2.x or earlie", + "code":"1129", + "des":"You can access Manager from the MRS management console.The following table lists the differences and relationships between the management console and MRS Manager.", "doc_type":"usermanual", "kw":"Differences and Relationships Between the MRS Management Console and Cluster Manager,MRS Overview,Us", "search_title":"", @@ -20873,7 +20941,7 @@ "uri":"mrs_03_1246.html", "node_id":"mrs_03_1246.xml", "product_code":"mrs", - "code":"1126", + "code":"1130", "des":"After an EIP is bound on the console, the EIP cannot be unbound in the EIP module of the VPC service.A dialog box is displayed, indicating that the operation cannot be pe", "doc_type":"usermanual", "kw":"How Do I Unbind an EIP from an MRS Cluster Node?,MRS Overview,User Guide", @@ -20891,7 +20959,7 @@ "uri":"mrs_03_2003.html", "node_id":"mrs_03_2003.xml", "product_code":"mrs", - "code":"1127", + "code":"1131", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Account and Password", @@ -20909,7 +20977,7 @@ "uri":"mrs_03_1027.html", "node_id":"mrs_03_1027.xml", "product_code":"mrs", - "code":"1128", + "code":"1132", "des":"The default account for logging in to Manager is admin, and the password is the one you set when you created the cluster.", "doc_type":"faq", "kw":"What Is the Account for Logging In to Manager?,Account and Password,User Guide", @@ -20927,7 +20995,7 @@ "uri":"mrs_03_1249.html", "node_id":"mrs_03_1249.xml", "product_code":"mrs", - "code":"1129", + "code":"1133", "des":"Querying the password validity period of a component running user (human-machine user or machine-machine user):cd /opt/Bigdata/clientsource bigdata_envkadmin -p kadmin/ad", "doc_type":"usermanual", "kw":"How Do I Query and Change the Password Validity Period of an Account?,Account and Password,User Guid", @@ -20945,7 +21013,7 @@ "uri":"mrs_03_2004.html", "node_id":"mrs_03_2004.xml", "product_code":"mrs", - "code":"1130", + "code":"1134", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Accounts and Permissions", @@ -20963,8 +21031,8 @@ "uri":"mrs_03_1020.html", "node_id":"mrs_03_1020.xml", "product_code":"mrs", - "code":"1131", - "des":"For MRS cluster 2.1.0 or earlier, choose System > Configuration > Permission on MRS Manager.For MRS cluster 3.x or later, choose System > Permission on FusionInsight Mana", + "code":"1135", + "des":"For MRS cluster 2.1.0 or earlier, choose System > Configuration > Permission on MRS Manager.For MRS cluster 3.x or later, choose System > Permission on MRS Manager.", "doc_type":"faq", "kw":"Does an MRS Cluster Support Access Permission Control If Kerberos Authentication Is not Enabled?,Acc", "search_title":"", @@ -20982,7 +21050,7 @@ "uri":"mrs_03_1035.html", "node_id":"mrs_03_1035.xml", "product_code":"mrs", - "code":"1132", + "code":"1136", "des":"You can assign tenant management permission only in analysis or hybrid clusters, but not in streaming clusters.The operations vary depending on the MRS cluster version:Pr", "doc_type":"faq", "kw":"How Do I Assign Tenant Management Permission to a New Account?,Accounts and Permissions,User Guide", @@ -21000,7 +21068,7 @@ "uri":"mrs_03_1118.html", "node_id":"mrs_03_1118.xml", "product_code":"mrs", - "code":"1133", + "code":"1137", "des":"On the IAM console, choose Permissions in the navigation pane, and click Create Custom Policy.Set a policy name in Policy Name.Set Scope to Project-level service for MRS.", "doc_type":"faq", "kw":"How Do I Customize an MRS Policy?,Accounts and Permissions,User Guide", @@ -21019,7 +21087,7 @@ "uri":"mrs_03_1037.html", "node_id":"mrs_03_1037.xml", "product_code":"mrs", - "code":"1134", + "code":"1138", "des":"Check whether you have the Manager_administrator permission. If you do not have this permission, Manage User will not be available on the System page of MRS Manager.", "doc_type":"faq", "kw":"Why Is the Manage User Function Unavailable on the System Page on MRS Manager?,Accounts and Permissi", @@ -21037,7 +21105,7 @@ "uri":"mrs_03_1121.html", "node_id":"mrs_03_1121.xml", "product_code":"mrs", - "code":"1135", + "code":"1139", "des":"Hue does not provide an entry for configuring account permissions on its web UI. However, you can configure user roles and user groups for Hue accounts on the System tab ", "doc_type":"faq", "kw":"Does Hue Support Account Permission Configuration?,Accounts and Permissions,User Guide", @@ -21055,7 +21123,7 @@ "uri":"mrs_03_2005.html", "node_id":"mrs_03_2005.xml", "product_code":"mrs", - "code":"1136", + "code":"1140", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Client Usage", @@ -21073,7 +21141,7 @@ "uri":"mrs_03_1031.html", "node_id":"mrs_03_1031.xml", "product_code":"mrs", - "code":"1137", + "code":"1141", "des":"Log in to any Master node as user root.Run the su - omm command to switch to user omm.Run the cdclient installation directory command to switch to the client.Run the sour", "doc_type":"faq", "kw":"How Do I Configure Environment Variables and Run Commands on a Component Client?,Client Usage,User G", @@ -21091,8 +21159,8 @@ "uri":"mrs_03_1219.html", "node_id":"mrs_03_1219.xml", "product_code":"mrs", - "code":"1138", - "des":"Log in to FusionInsight Manager, choose Cluster > Services > ZooKeeper, click the Configurations tab and then All Configurations. In the navigation pane on the left, choo", + "code":"1142", + "des":"Log in to MRS Manager, choose Cluster > Services > ZooKeeper, click the Configurations tab and then All Configurations. In the navigation pane on the left, choose quorump", "doc_type":"usermanual", "kw":"How Do I Disable ZooKeeper SASL Authentication?,Client Usage,User Guide", "search_title":"", @@ -21109,7 +21177,7 @@ "uri":"mrs_03_1251.html", "node_id":"mrs_03_1251.xml", "product_code":"mrs", - "code":"1139", + "code":"1143", "des":"After the client is installed on a node outside an MRS cluster and the kinit command is executed, the following error information is displayed:The following error informa", "doc_type":"usermanual", "kw":"An Error Is Reported When the kinit Command Is Executed on a Client Node Outside an MRS Cluster,Clie", @@ -21127,7 +21195,7 @@ "uri":"mrs_03_2006.html", "node_id":"mrs_03_2006.xml", "product_code":"mrs", - "code":"1140", + "code":"1144", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Web Page Access", @@ -21145,7 +21213,7 @@ "uri":"mrs_03_1151.html", "node_id":"mrs_03_1151.xml", "product_code":"mrs", - "code":"1141", + "code":"1145", "des":"You need to set a proper web session timeout duration for security purposes. To change the session timeout duration, do as follows:For MRS cluster versions earlier than 3", "doc_type":"faq", "kw":"How Do I Change the Session Timeout Duration for an Open Source Component Web UI?,Web Page Access,Us", @@ -21164,7 +21232,7 @@ "uri":"mrs_03_1156.html", "node_id":"mrs_03_1156.xml", "product_code":"mrs", - "code":"1142", + "code":"1146", "des":"You can run the ps -ef |grep aos command to check whether the AOS process restarts successfully. If the process exists, the restart is successful and the Dynamic Resource", "doc_type":"faq", "kw":"Why Cannot I Refresh the Dynamic Resource Plan Page on MRS Tenant Tab?,Web Page Access,User Guide", @@ -21182,7 +21250,7 @@ "uri":"mrs_03_1166.html", "node_id":"mrs_03_1166.xml", "product_code":"mrs", - "code":"1143", + "code":"1147", "des":"sh /opt/Bigdata/apache-tomcat-7.0.78/bin/shutdown.sh", "doc_type":"faq", "kw":"What Do I Do If the Kafka Topic Monitoring Tab Is Unavailable on Manager?,Web Page Access,User Guide", @@ -21200,7 +21268,7 @@ "uri":"mrs_03_2007.html", "node_id":"mrs_03_2007.xml", "product_code":"mrs", - "code":"1144", + "code":"1148", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Alarm Monitoring", @@ -21218,7 +21286,7 @@ "uri":"mrs_03_1055.html", "node_id":"mrs_03_1055.xml", "product_code":"mrs", - "code":"1145", + "code":"1149", "des":"The Kafka topic monitoring function cannot send alarms by email or SMS message. However, you can view alarm information on Manager.", "doc_type":"faq", "kw":"In an MRS Streaming Cluster, Can the Kafka Topic Monitoring Function Send Alarm Notifications?,Alarm", @@ -21236,8 +21304,8 @@ "uri":"mrs_03_1222.html", "node_id":"mrs_03_1222.xml", "product_code":"mrs", - "code":"1146", - "des":"Log in to FusionInsight Manager and choose Cluster > Services > Yarn. In the navigation pane on the left, choose ResourceManager(Active) and log in to the native Yarn pag", + "code":"1150", + "des":"Log in to MRS Manager and choose Cluster > Services > Yarn. In the navigation pane on the left, choose ResourceManager(Active) and log in to the native Yarn page.For deta", "doc_type":"usermanual", "kw":"Where Can I View the Running Resource Queues When the Alarm \"ALM-18022 Insufficient Yarn Queue Resou", "search_title":"", @@ -21254,8 +21322,8 @@ "uri":"mrs_03_1243.html", "node_id":"mrs_03_1243.xml", "product_code":"mrs", - "code":"1147", - "des":"The following uses the Operation Requests on RegionServers monitoring item as an example:Log in to FusionInsight Manager and choose Cluster > Services > HBase > Resource.", + "code":"1151", + "des":"The following uses the Operation Requests on RegionServers monitoring item as an example:Log in to MRS Manager and choose Cluster > Services > HBase > Resource. On the di", "doc_type":"usermanual", "kw":"How Do I Understand the Multi-Level Chart Statistics in the HBase Operation Requests Metric?,Alarm M", "search_title":"", @@ -21272,7 +21340,7 @@ "uri":"mrs_03_2008.html", "node_id":"mrs_03_2008.xml", "product_code":"mrs", - "code":"1148", + "code":"1152", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Performance Tuning", @@ -21290,7 +21358,7 @@ "uri":"mrs_03_1017.html", "node_id":"mrs_03_1017.xml", "product_code":"mrs", - "code":"1149", + "code":"1153", "des":"An MRS cluster does not support system reinstallation.", "doc_type":"faq", "kw":"Does an MRS Cluster Support System Reinstallation?,Performance Tuning,User Guide", @@ -21308,7 +21376,7 @@ "uri":"mrs_03_1203.html", "node_id":"mrs_03_1203.xml", "product_code":"mrs", - "code":"1150", + "code":"1154", "des":"The OS of an MRS cluster cannot be changed.", "doc_type":"faq", "kw":"Can I Change the OS of an MRS Cluster?,Performance Tuning,User Guide", @@ -21327,8 +21395,8 @@ "uri":"mrs_03_1090.html", "node_id":"mrs_03_1090.xml", "product_code":"mrs", - "code":"1151", - "des":"Go to the Yarn service configuration page.For versions earlier than 1.9.2, log in to MRS Manager, choose Services > Yarn > Service Configuration, and select All from the ", + "code":"1155", + "des":"Go to the Yarn service configuration page.For versions earlier than 1.9.2,log in to MRS Manager, choose Services > Yarn > Service Configuration, and select All from the B", "doc_type":"faq", "kw":"How Do I Improve the Resource Utilization of Core Nodes in a Cluster?,Performance Tuning,User Guide", "search_title":"", @@ -21346,7 +21414,7 @@ "uri":"mrs_03_1072.html", "node_id":"mrs_03_1072.xml", "product_code":"mrs", - "code":"1152", + "code":"1156", "des":"For example, to check the firewall status on EulerOS, run the systemctl status firewalld.service command.For example, to stop the firewall service on EulerOS, run the sys", "doc_type":"faq", "kw":"How Do I Stop the Firewall Service?,Performance Tuning,User Guide", @@ -21364,7 +21432,7 @@ "uri":"mrs_03_2009.html", "node_id":"mrs_03_2009.xml", "product_code":"mrs", - "code":"1153", + "code":"1157", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Job Development", @@ -21382,7 +21450,7 @@ "uri":"mrs_03_1015.html", "node_id":"mrs_03_1015.xml", "product_code":"mrs", - "code":"1154", + "code":"1158", "des":"MRS can process data in OBS and HDFS. You can get your data into OBS or HDFS as follows:Upload local data to OBS.Log in to the OBS console.Create a parallel file system n", "doc_type":"faq", "kw":"How Do I Get My Data into OBS or HDFS?,Job Development,User Guide", @@ -21400,7 +21468,7 @@ "uri":"mrs_03_1050.html", "node_id":"mrs_03_1050.xml", "product_code":"mrs", - "code":"1155", + "code":"1159", "des":"MRS clusters support Spark jobs submitted in Spark, Spark Script, or Spark SQL mode.", "doc_type":"faq", "kw":"What Types of Spark Jobs Can Be Submitted in a Cluster?,Job Development,User Guide", @@ -21418,7 +21486,7 @@ "uri":"mrs_03_1052.html", "node_id":"mrs_03_1052.xml", "product_code":"mrs", - "code":"1156", + "code":"1160", "des":"You can run only one Spark task at a time after the minimum tenant resources of an MRS cluster is changed to 0.", "doc_type":"faq", "kw":"Can I Run Multiple Spark Tasks at the Same Time After the Minimum Tenant Resources of an MRS Cluster", @@ -21436,7 +21504,7 @@ "uri":"en-us_topic_0000001392574214.html", "node_id":"en-us_topic_0000001392574214.xml", "product_code":"mrs", - "code":"1157", + "code":"1161", "des":"You need to understand the concept ApplicationMaster before understanding the essential differences between Yarn-client and Yarn-cluster.In Yarn, each application instanc", "doc_type":"usermanual", "kw":"What Are the Differences Between the Client Mode and Cluster Mode of Spark Jobs?,Job Development,Use", @@ -21454,7 +21522,7 @@ "uri":"mrs_03_1173.html", "node_id":"mrs_03_1173.xml", "product_code":"mrs", - "code":"1158", + "code":"1162", "des":"If IAM synchronization is not performed when a job is submitted in a security cluster, the error message \"The current user does not exist on MRS Manager. Grant the user s", "doc_type":"faq", "kw":"How Do I Do If the Message \"The current user does not exist on MRS Manager. Grant the user sufficien", @@ -21473,7 +21541,7 @@ "uri":"mrs_03_1174.html", "node_id":"mrs_03_1174.xml", "product_code":"mrs", - "code":"1159", + "code":"1163", "des":"The cause of the launcherJob failure is that the user who submits the job does not have the write permission on the hdfs /mrs/job-properties directory.This problem is fi", "doc_type":"usermanual", "kw":"LauncherJob Job Execution Is Failed And the Error Message \"jobPropertiesMap is null.\" Is Displayed,J", @@ -21491,7 +21559,7 @@ "uri":"mrs_03_1175.html", "node_id":"mrs_03_1175.xml", "product_code":"mrs", - "code":"1160", + "code":"1164", "des":"To save storage space, the Yarn configuration item yarn.resourcemanager.max-completed-applications is modified to reduce the number of historical job records stored on Ya", "doc_type":"usermanual", "kw":"How Do I Do If the Flink Job Status on the MRS Console Is Inconsistent with That on Yarn?,Job Develo", @@ -21509,7 +21577,7 @@ "uri":"mrs_03_1176.html", "node_id":"mrs_03_1176.xml", "product_code":"mrs", - "code":"1161", + "code":"1165", "des":"When a user submits a job that needs to read and write OBS, the job submission program adds the temporary access key (AK) and secret key (SK) for accessing OBS by default", "doc_type":"usermanual", "kw":"How Do I Do If a SparkStreaming Job Fails After Being Executed Dozens of Hours and the OBS Access 40", @@ -21527,7 +21595,7 @@ "uri":"mrs_03_1201.html", "node_id":"mrs_03_1201.xml", "product_code":"mrs", - "code":"1162", + "code":"1166", "des":"The ClickHouse client restricts the memory used by GROUP BY statements. When a SQL statement is executed on the ClickHouse client, the following error information is disp", "doc_type":"faq", "kw":"How Do I Do If an Alarm Is Reported Indicating that the Memory Is Insufficient When I Execute a SQL ", @@ -21546,7 +21614,7 @@ "uri":"mrs_03_1205.html", "node_id":"mrs_03_1205.xml", "product_code":"mrs", - "code":"1163", + "code":"1167", "des":"The Spark job keeps running and error message \"java.io.IOException: Connection reset by peer\" is displayed.Add the executor.memory Overhead parameter to the parameters fo", "doc_type":"faq", "kw":"How Do I Do If Error Message \"java.io.IOException: Connection reset by peer\" Is Displayed During the", @@ -21565,7 +21633,7 @@ "uri":"mrs_03_1207.html", "node_id":"mrs_03_1207.xml", "product_code":"mrs", - "code":"1164", + "code":"1168", "des":"Error message \"requestId=4971883851071737250\" is displayed when a Spark job accesses OBS.Log in to the node where the Spark client is located, go to the conf directory, a", "doc_type":"faq", "kw":"How Do I Do If Error Message \"requestId=4971883851071737250\" Is Displayed When a Spark Job Accesses ", @@ -21584,7 +21652,7 @@ "uri":"mrs_03_1208.html", "node_id":"mrs_03_1208.xml", "product_code":"mrs", - "code":"1165", + "code":"1169", "des":"DataArtsStudio occasionally fails to schedule Spark jobs and the rescheduling also fails. The following error information is displayed:Log in to the node where the Spark ", "doc_type":"faq", "kw":"Why DataArtsStudio Occasionally Fail to Schedule Spark Jobs and the Rescheduling also Fails?,Job Dev", @@ -21603,7 +21671,7 @@ "uri":"mrs_03_1215.html", "node_id":"mrs_03_1215.xml", "product_code":"mrs", - "code":"1166", + "code":"1170", "des":"A Flink job fails to be executed and the following error message is displayed:The third-party dependency package in the customer code conflicts with the cluster package. ", "doc_type":"usermanual", "kw":"How Do I Do If a Flink Job Fails to Execute and the Error Message \"java.lang.NoSuchFieldError: SECUR", @@ -21621,7 +21689,7 @@ "uri":"mrs_03_1223.html", "node_id":"mrs_03_1223.xml", "product_code":"mrs", - "code":"1167", + "code":"1171", "des":"After a Yarn job is created, it cannot be viewed if you log in to the web UI as the admin user.The admin user is a user on the cluster management page. Check whether the ", "doc_type":"usermanual", "kw":"Why Submitted Yarn Job Cannot Be Viewed on the Web UI?,Job Development,User Guide", @@ -21639,7 +21707,7 @@ "uri":"mrs_03_1224.html", "node_id":"mrs_03_1224.xml", "product_code":"mrs", - "code":"1168", + "code":"1172", "des":"You can modify or add the HDFS NameSpace (fs.defaultFS) of the cluster by modifying the core-site.xml and hdfs-site.xml files on the client. However, you are not advised ", "doc_type":"usermanual", "kw":"How Do I Modify the HDFS NameSpace (fs.defaultFS) of an Existing Cluster?,Job Development,User Guide", @@ -21657,7 +21725,7 @@ "uri":"mrs_03_1229.html", "node_id":"mrs_03_1229.xml", "product_code":"mrs", - "code":"1169", + "code":"1173", "des":"The launcher-job queue is stopped by YARN when a Flink job is submitted on the management plane.Increase the heap size of the launcher-job queue.Log in to the active OMS ", "doc_type":"usermanual", "kw":"How Do I Do If the launcher-job Queue Is Stopped by YARN due to Insufficient Heap Size When I Submit", @@ -21675,7 +21743,7 @@ "uri":"mrs_03_1237.html", "node_id":"mrs_03_1237.xml", "product_code":"mrs", - "code":"1170", + "code":"1174", "des":"When a Flink job is submitted, JobManager is started successfully. However, TaskManager remains in the starting state until timeout. The following error information is di", "doc_type":"usermanual", "kw":"How Do I Do If the Error Message \"slot request timeout\" Is Displayed When I Submit a Flink Job?,Job ", @@ -21693,7 +21761,7 @@ "uri":"mrs_03_1238.html", "node_id":"mrs_03_1238.xml", "product_code":"mrs", - "code":"1171", + "code":"1175", "des":"Does a DistCP job compare data consistency during data import and export?No. DistCP jobs only copy data but do not modify it.No. DistCP jobs only copy data but do not mod", "doc_type":"usermanual", "kw":"Data Import and Export of DistCP Jobs,Job Development,User Guide", @@ -21711,7 +21779,7 @@ "uri":"mrs_03_2010.html", "node_id":"mrs_03_2010.xml", "product_code":"mrs", - "code":"1172", + "code":"1176", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Cluster Upgrade/Patching", @@ -21729,7 +21797,7 @@ "uri":"mrs_03_1089.html", "node_id":"mrs_03_1089.xml", "product_code":"mrs", - "code":"1173", + "code":"1177", "des":"You cannot upgrade an MRS cluster. However, you can create a cluster of the target version and migrate data from the old cluster to the new cluster.", "doc_type":"usermanual", "kw":"Can I Upgrade an MRS Cluster?,Cluster Upgrade/Patching,User Guide", @@ -21748,7 +21816,7 @@ "uri":"mrs_03_1021.html", "node_id":"mrs_03_1021.xml", "product_code":"mrs", - "code":"1174", + "code":"1178", "des":"You cannot change the version of an MRS cluster. However, you can terminate the current cluster and create an MRS cluster of the version you require.", "doc_type":"usermanual", "kw":"Can I Change the MRS Cluster Version?,Cluster Upgrade/Patching,User Guide", @@ -21767,7 +21835,7 @@ "uri":"mrs_03_2013.html", "node_id":"mrs_03_2013.xml", "product_code":"mrs", - "code":"1175", + "code":"1179", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Cluster Access", @@ -21785,7 +21853,7 @@ "uri":"mrs_03_1029.html", "node_id":"mrs_03_1029.xml", "product_code":"mrs", - "code":"1176", + "code":"1180", "des":"No. You can select the login mode when creating the cluster. You cannot change the login mode after you created the cluster.", "doc_type":"usermanual", "kw":"Can I Switch Between the Two Login Modes of MRS?,Cluster Access,User Guide", @@ -21804,8 +21872,8 @@ "uri":"mrs_03_1071.html", "node_id":"mrs_03_1071.xml", "product_code":"mrs", - "code":"1177", - "des":"You can obtain the IP address and port number of a ZooKeeper instance through the MRS console or FusionInsight Manager.Method 1: Obtaining the IP address and port number ", + "code":"1181", + "des":"You can obtain the IP address and port number of a ZooKeeper instance through the MRS console or MRS Manager.Method 1: Obtaining the IP address and port number of a ZooKe", "doc_type":"faq", "kw":"How Can I Obtain the IP Address and Port Number of a ZooKeeper Instance?,Cluster Access,User Guide", "search_title":"", @@ -21823,7 +21891,7 @@ "uri":"mrs_03_1185.html", "node_id":"mrs_03_1185.xml", "product_code":"mrs", - "code":"1178", + "code":"1182", "des":"If you can log in to an existing node as the Linux user but fail to log in to the newly added node, log in to the newly added node as the root user.", "doc_type":"faq", "kw":"How Do I Do If a New Node Cannot Be logged In to as a Linux User?,Cluster Access,User Guide", @@ -21842,7 +21910,7 @@ "uri":"mrs_03_1234.html", "node_id":"mrs_03_1234.xml", "product_code":"mrs", - "code":"1179", + "code":"1183", "des":"Set AZ, VPC, and Security Group of the ECS to the same values as those of the cluster to be accessed.On the Dashboard tab page, click Add Security Group Rule. In the Add ", "doc_type":"usermanual", "kw":"How Do I Access an MRS Cluster from a Node Outside the Cluster?,Cluster Access,User Guide", @@ -21860,7 +21928,7 @@ "uri":"mrs_03_2014.html", "node_id":"mrs_03_2014.xml", "product_code":"mrs", - "code":"1180", + "code":"1184", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Big Data Service Development", @@ -21878,7 +21946,7 @@ "uri":"mrs_03_1059.html", "node_id":"mrs_03_1059.xml", "product_code":"mrs", - "code":"1181", + "code":"1185", "des":"The Flume client supports multiple independent data flows. You can configure and link multiple sources, channels, and sinks in the properties.properties configuration fil", "doc_type":"faq", "kw":"Can MRS Run Multiple Flume Tasks at a Time?,Big Data Service Development,User Guide", @@ -21896,7 +21964,7 @@ "uri":"mrs_03_1058.html", "node_id":"mrs_03_1058.xml", "product_code":"mrs", - "code":"1182", + "code":"1186", "des":"Log in to the node where FlumeClient is running.Go to the FlumeClient installation directory. For example, if the FlumeClient installation directory is /opt/FlumeClient, ", "doc_type":"faq", "kw":"How Do I Change FlumeClient Logs to Standard Logs?,Big Data Service Development,User Guide", @@ -21914,7 +21982,7 @@ "uri":"mrs_03_1064.html", "node_id":"mrs_03_1064.xml", "product_code":"mrs", - "code":"1183", + "code":"1187", "des":"hadoopstreaming.jar: /opt/share/hadoop-streaming-* (* indicates the Hadoop version.)JDK environment variables: /opt/client/JDK/component_envHadoop environment variables: ", "doc_type":"faq", "kw":"Where Are the JAR Files and Environment Variables of Hadoop Stored?,Big Data Service Development,Use", @@ -21933,7 +22001,7 @@ "uri":"mrs_03_1042.html", "node_id":"mrs_03_1042.xml", "product_code":"mrs", - "code":"1184", + "code":"1188", "des":"HBase supports the Snappy, LZ4, and gzip compression algorithms.", "doc_type":"faq", "kw":"What Compression Algorithms Does HBase Support?,Big Data Service Development,User Guide", @@ -21951,7 +22019,7 @@ "uri":"mrs_03_1044.html", "node_id":"mrs_03_1044.xml", "product_code":"mrs", - "code":"1185", + "code":"1189", "des":"No. Hive on HBase supports only data query.", "doc_type":"faq", "kw":"Can MRS Write Data to HBase Through the HBase External Table of Hive?,Big Data Service Development,U", @@ -21969,7 +22037,7 @@ "uri":"mrs_03_1045.html", "node_id":"mrs_03_1045.xml", "product_code":"mrs", - "code":"1186", + "code":"1190", "des":"Log in to the Master node in the cluster as user root.Run the su - omm command to switch to user omm.Run the cd /var/log/Bigdata/hbase/ command to go to the /var/log/Bigd", "doc_type":"faq", "kw":"How Do I View HBase Logs?,Big Data Service Development,User Guide", @@ -21988,7 +22056,7 @@ "uri":"mrs_03_1140.html", "node_id":"mrs_03_1140.xml", "product_code":"mrs", - "code":"1187", + "code":"1191", "des":"Set the time to live (TTL) when creating a table:Create the t_task_log table, set the column family to f, and set the TTL to 86400 seconds.create 't_task_log',{NAME => 'f", "doc_type":"faq", "kw":"How Do I Set the TTL for an HBase Table?,Big Data Service Development,User Guide", @@ -22006,7 +22074,7 @@ "uri":"mrs_03_1113.html", "node_id":"mrs_03_1113.xml", "product_code":"mrs", - "code":"1188", + "code":"1192", "des":"Log in to the master node of the cluster and run the corresponding command to configure environment variables. /opt/client indicates the client installation directory. Re", "doc_type":"faq", "kw":"How Do I Balance HDFS Data?,Big Data Service Development,User Guide", @@ -22025,7 +22093,7 @@ "uri":"mrs_03_1061.html", "node_id":"mrs_03_1061.xml", "product_code":"mrs", - "code":"1189", + "code":"1193", "des":"Go to the HDFS service configuration page.For MRS cluster versions earlier than 1.9.2:Log in to MRS Manager, choose Services > HDFS > Service Configuration, and select Al", "doc_type":"faq", "kw":"How Do I Change the Number of HDFS Replicas?,Big Data Service Development,User Guide", @@ -22044,7 +22112,7 @@ "uri":"mrs_03_1060.html", "node_id":"mrs_03_1060.xml", "product_code":"mrs", - "code":"1190", + "code":"1194", "des":"The default port of open source HDFS is 50070 for versions earlier than MRS 3.0.0, and 9870 for MRS 3.0.0 or later. Common HDFS Ports describes the common ports of HDFS.T", "doc_type":"faq", "kw":"What Is the Port for Accessing HDFS Using Python?,Big Data Service Development,User Guide", @@ -22063,7 +22131,7 @@ "uri":"mrs_03_1196.html", "node_id":"mrs_03_1196.xml", "product_code":"mrs", - "code":"1191", + "code":"1195", "des":"If the org.apache.hadoop.hdfs.server.namenode.ha.AdaptiveFailoverProxyProvider class is unavailable when a cluster of MRS 3.x connects to NameNodes using HDFS, the cause ", "doc_type":"faq", "kw":"How Do I Modify the HDFS Active/Standby Switchover Class?,Big Data Service Development,User Guide", @@ -22082,7 +22150,7 @@ "uri":"mrs_03_1047.html", "node_id":"mrs_03_1047.xml", "product_code":"mrs", - "code":"1192", + "code":"1196", "des":"smallint is recommended.", "doc_type":"faq", "kw":"What Is the Recommended Number Type of DynamoDB in Hive Tables?,Big Data Service Development,User Gu", @@ -22100,7 +22168,7 @@ "uri":"mrs_03_1049.html", "node_id":"mrs_03_1049.xml", "product_code":"mrs", - "code":"1193", + "code":"1197", "des":"The Hive driver cannot be interconnected with the DBCP2 database connection pool. The DBCP2 database connection pool invokes the isValid method to check whether a connect", "doc_type":"faq", "kw":"Can the Hive Driver Be Interconnected with DBCP2?,Big Data Service Development,User Guide", @@ -22118,7 +22186,7 @@ "uri":"mrs_03_1082.html", "node_id":"mrs_03_1082.xml", "product_code":"mrs", - "code":"1194", + "code":"1198", "des":"Versions earlier than MRS 3.x:Log in to MRS Manager and choose System > Permission > Manage Role.Click Create Role, and set Role Name and Description.In the Permission ta", "doc_type":"faq", "kw":"How Do I View the Hive Table Created by Another User?,Big Data Service Development,User Guide", @@ -22137,7 +22205,7 @@ "uri":"mrs_03_1149.html", "node_id":"mrs_03_1149.xml", "product_code":"mrs", - "code":"1195", + "code":"1199", "des":"Run the following statement to export the query result of Hive data:", "doc_type":"faq", "kw":"Can I Export the Query Result of Hive Data?,Big Data Service Development,User Guide", @@ -22155,10 +22223,10 @@ "uri":"mrs_03_1194.html", "node_id":"mrs_03_1194.xml", "product_code":"mrs", - "code":"1196", + "code":"1200", "des":"When Hive of MRS 3.x runs the beeline -e \" use default;show tables;\" command, the following error message is displayed: Error while compiling statement: FAILED: ParseExce", "doc_type":"faq", - "kw":"How Do I Do If an Error Occurs When Hive Runs the beeline -e Command to Execute Multiple Statements?", + "kw":"beeline -eHow Do I Do If an Error Occurs When Hive Runs the beeline -e Command to Execute Multiple S", "search_title":"", "metedata":[ { @@ -22167,14 +22235,14 @@ "prodname":"mrs" } ], - "title":"How Do I Do If an Error Occurs When Hive Runs the beeline -e Command to Execute Multiple Statements?", + "title":"beeline -eHow Do I Do If an Error Occurs When Hive Runs the beeline -e Command to Execute Multiple Statements?", "githuburl":"" }, { "uri":"mrs_03_1200.html", "node_id":"mrs_03_1200.xml", "product_code":"mrs", - "code":"1197", + "code":"1201", "des":"This issue occurs because the MRS CommonOperations permission bound to the user group to which the user who submits the job belongs does not include the Hive permission a", "doc_type":"faq", "kw":"How Do I Do If a \"hivesql/hivescript\" Job Fails to Submit After Hive Is Added?,Big Data Service Deve", @@ -22193,7 +22261,7 @@ "uri":"mrs_03_1160.html", "node_id":"mrs_03_1160.xml", "product_code":"mrs", - "code":"1198", + "code":"1202", "des":"This section applies only to versions earlier than MRS 3.x.Log in to a Master node as user root and switch to user omm.su - ommsu - ommCheck whether the current node is t", "doc_type":"faq", "kw":"What If an Excel File Downloaded on Hue Failed to Open?,Big Data Service Development,User Guide", @@ -22212,7 +22280,7 @@ "uri":"mrs_03_1214.html", "node_id":"mrs_03_1214.xml", "product_code":"mrs", - "code":"1199", + "code":"1203", "des":"Applicable versions: MRS 3.1.0 and earlierModify the following file on the two Hue nodes:/opt/Bigdata/FusionInsight_Porter_8.*/install/FusionInsight-Hue-*/hue/apps/beeswa", "doc_type":"usermanual", "kw":"How Do I Do If Sessions Are Not Released After Hue Connects to HiveServer and the Error Message \"ove", @@ -22230,7 +22298,7 @@ "uri":"mrs_03_1106.html", "node_id":"mrs_03_1106.xml", "product_code":"mrs", - "code":"1200", + "code":"1204", "des":"You can reset Kafka data by deleting Kafka topics.Delete a topic: kafka-topics.sh --delete --zookeeperZooKeeper Cluster service IP address:2181/kafka --topic topicnameQue", "doc_type":"faq", "kw":"How Do I Reset Kafka Data?,Big Data Service Development,User Guide", @@ -22248,7 +22316,7 @@ "uri":"mrs_03_1145.html", "node_id":"mrs_03_1145.xml", "product_code":"mrs", - "code":"1201", + "code":"1205", "des":"Run the --bootstrap-server command to query the information about the client.", "doc_type":"faq", "kw":"How Do I Obtain the Client Version of MRS Kafka?,Big Data Service Development,User Guide", @@ -22266,7 +22334,7 @@ "uri":"mrs_03_1146.html", "node_id":"mrs_03_1146.xml", "product_code":"mrs", - "code":"1202", + "code":"1206", "des":"Kafka supports PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL.", "doc_type":"faq", "kw":"What Access Protocols Are Supported by Kafka?,Big Data Service Development,User Guide", @@ -22284,7 +22352,7 @@ "uri":"mrs_03_1197.html", "node_id":"mrs_03_1197.xml", "product_code":"mrs", - "code":"1203", + "code":"1207", "des":"This issue is caused by the conflict between the Ranger authentication and ACL authentication of a cluster. If a Kafka cluster uses ACL for permission access control and ", "doc_type":"faq", "kw":"How Do I Do If Error Message \"Not Authorized to access group xxx\" Is Displayed When a Kafka Topic Is", @@ -22303,7 +22371,7 @@ "uri":"mrs_03_1067.html", "node_id":"mrs_03_1067.xml", "product_code":"mrs", - "code":"1204", + "code":"1208", "des":"Kudu supports Snappy, LZ4, and zlib. LZ4 is used by default.", "doc_type":"faq", "kw":"What Compression Algorithms Does Kudu Support?,Big Data Service Development,User Guide", @@ -22321,7 +22389,7 @@ "uri":"mrs_03_1069.html", "node_id":"mrs_03_1069.xml", "product_code":"mrs", - "code":"1205", + "code":"1209", "des":"Log in to the Master node in the cluster.Run the su - omm command to switch to user omm.Run the cd /var/log/Bigdata/kudu/ command to go to the /var/log/Bigdata/kudu/ dire", "doc_type":"faq", "kw":"How Do I View Kudu Logs?,Big Data Service Development,User Guide", @@ -22339,7 +22407,7 @@ "uri":"mrs_03_1169.html", "node_id":"mrs_03_1169.xml", "product_code":"mrs", - "code":"1206", + "code":"1210", "des":"Log in to the MRS console.Click the name of the cluster.On the page displayed, choose Components > Kudu > Instances and locate the IP address of the abnormal instance.If ", "doc_type":"faq", "kw":"How Do I Handle the Kudu Service Exceptions Generated During Cluster Creation?,Big Data Service Deve", @@ -22358,7 +22426,7 @@ "uri":"mrs_03_1070.html", "node_id":"mrs_03_1070.xml", "product_code":"mrs", - "code":"1207", + "code":"1211", "des":"OpenTSDB supports Python APIs. OpenTSDB provides HTTP-based RESTful APIs that are language-independent. Any language that supports HTTP requests can interconnect to OpenT", "doc_type":"faq", "kw":"Does OpenTSDB Support Python APIs?,Big Data Service Development,User Guide", @@ -22376,7 +22444,7 @@ "uri":"mrs_03_1147.html", "node_id":"mrs_03_1147.xml", "product_code":"mrs", - "code":"1208", + "code":"1212", "des":"In this section, MySQL is used as an example.For MRS 1.x and 3.x clusters, do the following:Log in to the MRS management console.Click the name of the cluster to go to it", "doc_type":"faq", "kw":"How Do I Configure Other Data Sources on Presto?,Big Data Service Development,User Guide", @@ -22395,7 +22463,7 @@ "uri":"mrs_03_1157.html", "node_id":"mrs_03_1157.xml", "product_code":"mrs", - "code":"1209", + "code":"1213", "des":"Log in to the Master node in the cluster as user root.Run the following command to configure environment variables:source Client installation directory/bigdata_envsource ", "doc_type":"faq", "kw":"How Do I Connect to Spark Shell from MRS?,Big Data Service Development,User Guide", @@ -22414,7 +22482,7 @@ "uri":"mrs_03_1158.html", "node_id":"mrs_03_1158.xml", "product_code":"mrs", - "code":"1210", + "code":"1214", "des":"Log in to the master node in the cluster as user root.Run the following command to configure environment variables:source Client installation directory/bigdata_envsource ", "doc_type":"faq", "kw":"How Do I Connect to Spark Beeline from MRS?,Big Data Service Development,User Guide", @@ -22433,7 +22501,7 @@ "uri":"mrs_03_1159.html", "node_id":"mrs_03_1159.xml", "product_code":"mrs", - "code":"1211", + "code":"1215", "des":"Logs of unfinished Spark jobs are stored in the /srv/BigData/hadoop/data1/nm/containerlogs/ directory on the Core node.Logs of finished Spark jobs are stored in the /tmp/", "doc_type":"faq", "kw":"Where Are the Execution Logs of Spark Jobs Stored?,Big Data Service Development,User Guide", @@ -22451,7 +22519,7 @@ "uri":"mrs_03_1127.html", "node_id":"mrs_03_1127.xml", "product_code":"mrs", - "code":"1212", + "code":"1216", "des":"You can modify the /opt/Bigdata/MRS_XXX/1_XX _Supervisor/etc/worker.xml file on the streaming Core node of MRS, set the value of filename to the path, and restart the cor", "doc_type":"faq", "kw":"How Do I Specify a Log Path When Submitting a Task in an MRS Storm Cluster?,Big Data Service Develop", @@ -22469,7 +22537,7 @@ "uri":"mrs_03_1163.html", "node_id":"mrs_03_1163.xml", "product_code":"mrs", - "code":"1213", + "code":"1217", "des":"root-default is hidden on the Manager page.If the sum is 100, the configuration is correct.If the sum is not 100, the configuration is incorrect. Perform the following st", "doc_type":"faq", "kw":"How Do I Check Whether the ResourceManager Configuration of Yarn Is Correct?,Big Data Service Develo", @@ -22488,7 +22556,7 @@ "uri":"mrs_03_1210.html", "node_id":"mrs_03_1210.xml", "product_code":"mrs", - "code":"1214", + "code":"1218", "des":"cd /opt/Client installation directorysourcebigdata_envkinit MRS cluster userThe user must have the ClickHouse administrator permissions.set allow_drop_detached=1;SELECT *", "doc_type":"faq", "kw":"How Do I Modify the allow_drop_detached Parameter of ClickHouse?,Big Data Service Development,User G", @@ -22507,7 +22575,7 @@ "uri":"mrs_03_1206.html", "node_id":"mrs_03_1206.xml", "product_code":"mrs", - "code":"1215", + "code":"1219", "des":"When a Spark task is executed, an alarm indicating insufficient memory is reported. The alarm ID is 18022. As a result, no available memory can be used.Set the executor p", "doc_type":"faq", "kw":"How Do I Do If an Alarm Indicating Insufficient Memory Is Reported During Spark Task Execution?,Big ", @@ -22526,7 +22594,7 @@ "uri":"mrs_03_1209.html", "node_id":"mrs_03_1209.xml", "product_code":"mrs", - "code":"1216", + "code":"1220", "des":"A user performs a large number of update operations using ClickHouse. This operation on a ClickHouse consumes a large number of resources. In addition, the operation will", "doc_type":"faq", "kw":"How Do I Do If ClickHouse Consumes Excessive CPU Resources?,Big Data Service Development,User Guide", @@ -22545,7 +22613,7 @@ "uri":"mrs_03_1217.html", "node_id":"mrs_03_1217.xml", "product_code":"mrs", - "code":"1217", + "code":"1221", "des":"vim /opt/Bigdata/components/current/ClickHouse/configurations.xmlChange hidden to advanced, as shown in the following information in bold. Then save the configuration and", "doc_type":"usermanual", "kw":"How Do I Enable the Map Type on ClickHouse?,Big Data Service Development,User Guide", @@ -22563,7 +22631,7 @@ "uri":"mrs_03_1248.html", "node_id":"mrs_03_1248.xml", "product_code":"mrs", - "code":"1218", + "code":"1222", "des":"When Spark SQL is used to access Hive partitioned tables stored in OBS, the acces speed is slow and a large number of OBS query APIs are called.Example SQL:According to t", "doc_type":"usermanual", "kw":"A Large Number of OBS APIs Are Called When Spark SQL Accesses Hive Partitioned Tables,Big Data Servi", @@ -22581,7 +22649,7 @@ "uri":"mrs_03_2015.html", "node_id":"mrs_03_2015.xml", "product_code":"mrs", - "code":"1219", + "code":"1223", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"API", @@ -22599,7 +22667,7 @@ "uri":"mrs_03_1139.html", "node_id":"mrs_03_1139.xml", "product_code":"mrs", - "code":"1220", + "code":"1224", "des":"When you use the API for adjusting cluster nodes, the value of node_id is fixed to node_orderadd.", "doc_type":"faq", "kw":"How Do I Configure the node_id Parameter When Using the API for Adjusting Cluster Nodes?,API,User Gu", @@ -22617,7 +22685,7 @@ "uri":"mrs_03_2016.html", "node_id":"mrs_03_2016.xml", "product_code":"mrs", - "code":"1221", + "code":"1225", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Cluster Management", @@ -22635,7 +22703,7 @@ "uri":"mrs_03_1002.html", "node_id":"mrs_03_1002.xml", "product_code":"mrs", - "code":"1222", + "code":"1226", "des":"You can view all MRS clusters on the Clusters page. You can view clusters in different status.Active Clusters: all clusters except clusters in Failed and Terminated state", "doc_type":"faq", "kw":"How Do I View All Clusters?,Cluster Management,User Guide", @@ -22654,7 +22722,7 @@ "uri":"mrs_03_1003.html", "node_id":"mrs_03_1003.xml", "product_code":"mrs", - "code":"1223", + "code":"1227", "des":"You can view operation logs of clusters and jobs on the Operation Logs page. The MRS operation logs record the following operations:Cluster operationsCreate, terminate, a", "doc_type":"faq", "kw":"How Do I View Log Information?,Cluster Management,User Guide", @@ -22673,7 +22741,7 @@ "uri":"mrs_03_1004.html", "node_id":"mrs_03_1004.xml", "product_code":"mrs", - "code":"1224", + "code":"1228", "des":"After a cluster is created, click the cluster name on the MRS console. On the page displayed, you can view basic configuration information about the cluster. The instance", "doc_type":"faq", "kw":"How Do I View Cluster Configuration Information?,Cluster Management,User Guide", @@ -22692,7 +22760,7 @@ "uri":"mrs_03_1054.html", "node_id":"mrs_03_1054.xml", "product_code":"mrs", - "code":"1225", + "code":"1229", "des":"You cannot install the Kafka and Flume components for a created cluster of MRS 3.1.0 or earlier. Kafka and Flume are components for a streaming cluster. To install Kafka ", "doc_type":"faq", "kw":"How Do I Install Kafka and Flume in an MRS Cluster?,Cluster Management,User Guide", @@ -22711,7 +22779,7 @@ "uri":"mrs_03_1016.html", "node_id":"mrs_03_1016.xml", "product_code":"mrs", - "code":"1226", + "code":"1230", "des":"To stop an MRS cluster, stop each node in the cluster on the ECS. Click the name of each node on the Nodes tab page to go to the Elastic Cloud Server page and click Stop.", "doc_type":"faq", "kw":"How Do I Stop an MRS Cluster?,Cluster Management,User Guide", @@ -22729,7 +22797,7 @@ "uri":"mrs_03_1018.html", "node_id":"mrs_03_1018.xml", "product_code":"mrs", - "code":"1227", + "code":"1231", "des":"You can expand data disk capacity for MRS during off-peak hours.Expand the EVS disk capacity, and then log in to the ECS and expand the partitions and file system. MRS no", "doc_type":"faq", "kw":"Can I Expand Data Disk Capacity for MRS?,Cluster Management,User Guide", @@ -22748,7 +22816,7 @@ "uri":"mrs_03_1024.html", "node_id":"mrs_03_1024.xml", "product_code":"mrs", - "code":"1228", + "code":"1232", "des":"You cannot add or remove any component to and from a created cluster of MRS 3.1.0. However, you can create an MRS cluster that contains the required components.", "doc_type":"faq", "kw":"Can I Add Components to an Existing Cluster?,Cluster Management,User Guide", @@ -22767,7 +22835,7 @@ "uri":"mrs_03_1028.html", "node_id":"mrs_03_1028.xml", "product_code":"mrs", - "code":"1229", + "code":"1233", "des":"You cannot delete any component from a created MRS cluster of MRS 3.1.0. If a component is not required, log in to MRS Manager and stop the component on the Services page", "doc_type":"faq", "kw":"Can I Delete Components Installed in an MRS Cluster?,Cluster Management,User Guide", @@ -22786,7 +22854,7 @@ "uri":"mrs_03_1034.html", "node_id":"mrs_03_1034.xml", "product_code":"mrs", - "code":"1230", + "code":"1234", "des":"You cannot change MRS cluster nodes on the MRS console. You are also advised not to change MRS cluster nodes on the ECS console. Manually stopping or deleting an ECS, mod", "doc_type":"faq", "kw":"Can I Change MRS Cluster Nodes on the MRS Console?,Cluster Management,User Guide", @@ -22804,7 +22872,7 @@ "uri":"mrs_03_1130.html", "node_id":"mrs_03_1130.xml", "product_code":"mrs", - "code":"1231", + "code":"1235", "des":"Log in to the MRS console.Click the name of the cluster.On the page displayed, choose Alarms > Notification Rules.Locate the row that contains the rule you want to modify", "doc_type":"faq", "kw":"How Do I Shield Cluster Alarm/Event Notifications?,Cluster Management,User Guide", @@ -22822,7 +22890,7 @@ "uri":"mrs_03_1161.html", "node_id":"mrs_03_1161.xml", "product_code":"mrs", - "code":"1232", + "code":"1236", "des":"In an MRS cluster, MRS allocates 50% of the cluster memory to Yarn by default. You manage Yarn nodes logically by resource pool. Therefore, the total memory of the resour", "doc_type":"faq", "kw":"Why Is the Resource Pool Memory Displayed in the MRS Cluster Smaller Than the Actual Cluster Memory?", @@ -22840,7 +22908,7 @@ "uri":"mrs_03_1162.html", "node_id":"mrs_03_1162.xml", "product_code":"mrs", - "code":"1233", + "code":"1237", "des":"su ommvim /opt/knox/bin/gateway.shsh /opt/knox/bin/gateway.sh stopsh /opt/knox/bin/gateway.sh start", "doc_type":"faq", "kw":"How Do I Configure the knox Memory?,Cluster Management,User Guide", @@ -22858,7 +22926,7 @@ "uri":"mrs_03_1171.html", "node_id":"mrs_03_1171.xml", "product_code":"mrs", - "code":"1234", + "code":"1238", "des":"Log in to a Master node as user root and run the Python3 command to query the Python version.", "doc_type":"faq", "kw":"What Is the Python Version Installed for an MRS Cluster?,Cluster Management,User Guide", @@ -22877,7 +22945,7 @@ "uri":"mrs_03_1198.html", "node_id":"mrs_03_1198.xml", "product_code":"mrs", - "code":"1235", + "code":"1239", "des":"The configuration file paths of commonly used components are as follows:", "doc_type":"faq", "kw":"How Do I View the Configuration File Directory of Each Component?,Cluster Management,User Guide", @@ -22896,7 +22964,7 @@ "uri":"mrs_03_1211.html", "node_id":"mrs_03_1211.xml", "product_code":"mrs", - "code":"1236", + "code":"1240", "des":"If the time on a node inside the cluster is incorrect, log in to the node and rectify the fault from 2.If the time on a node inside the cluster is different from that on ", "doc_type":"faq", "kw":"How Do I Do If the Time on MRS Nodes Is Incorrect?,Cluster Management,User Guide", @@ -22915,7 +22983,7 @@ "uri":"mrs_03_1250.html", "node_id":"mrs_03_1250.xml", "product_code":"mrs", - "code":"1237", + "code":"1241", "des":"Log in to the target node and run the following command to query the startup time:date -d \"$(awk -F. '{print $1}' /proc/uptime) second ago\" +\"%Y-%m-%d %H:%M:%S\"", "doc_type":"usermanual", "kw":"How Do I Query the Startup Time of an MRS Node?,Cluster Management,User Guide", @@ -22933,7 +23001,7 @@ "uri":"mrs_03_1212.html", "node_id":"mrs_03_1212.xml", "product_code":"mrs", - "code":"1238", + "code":"1242", "des":"If \"ALM-12066 Inter-Node Mutual Trust Fails\" is reported on Manager or there is no SSH trust relationship between nodes, rectify the fault by performing the following ope", "doc_type":"faq", "kw":"How Do I Do If Trust Relationships Between Nodes Are Abnormal?,Cluster Management,User Guide", @@ -22952,7 +23020,7 @@ "uri":"mrs_03_1228.html", "node_id":"mrs_03_1228.xml", "product_code":"mrs", - "code":"1239", + "code":"1243", "des":"The manager-executor process runs either on the Master1 or Master2 node in the MRS cluster in active/standby mode. This process is used to encapsulate the MRS management ", "doc_type":"usermanual", "kw":"How Do I Adjust the Memory Size of the manager-executor Process?,Cluster Management,User Guide", @@ -22970,7 +23038,7 @@ "uri":"mrs_03_2018.html", "node_id":"mrs_03_2018.xml", "product_code":"mrs", - "code":"1240", + "code":"1244", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Kerberos Usage", @@ -22988,7 +23056,7 @@ "uri":"mrs_03_1038.html", "node_id":"mrs_03_1038.xml", "product_code":"mrs", - "code":"1241", + "code":"1245", "des":"You cannot change the Kerberos service after an MRS cluster is created.", "doc_type":"faq", "kw":"How Do I Change the Kerberos Authentication Status of a Created MRS Cluster?,Kerberos Usage,User Gui", @@ -23007,7 +23075,7 @@ "uri":"mrs_03_1131.html", "node_id":"mrs_03_1131.xml", "product_code":"mrs", - "code":"1242", + "code":"1246", "des":"The Kerberos authentication service uses ports 21730 (TCP), 21731 (TCP/UDP), and 21732 (TCP/UDP).", "doc_type":"faq", "kw":"What Are the Ports of the Kerberos Authentication Service?,Kerberos Usage,User Guide", @@ -23025,7 +23093,7 @@ "uri":"mrs_03_1148.html", "node_id":"mrs_03_1148.xml", "product_code":"mrs", - "code":"1243", + "code":"1247", "des":"The MRS cluster does not support customized Kerberos installation and deployment, and the Kerberos authentication cannot be set up between components. To enable Kerberos ", "doc_type":"usermanual", "kw":"How Do I Deploy the Kerberos Service in a Running Cluster?,Kerberos Usage,User Guide", @@ -23044,7 +23112,7 @@ "uri":"mrs_03_1152.html", "node_id":"mrs_03_1152.xml", "product_code":"mrs", - "code":"1244", + "code":"1248", "des":"Log in to the master node in the cluster as user root.Run the following command to configure environment variables:source /opt/client/bigdata_envsource /opt/client/bigdat", "doc_type":"faq", "kw":"How Do I Access Hive in a Cluster with Kerberos Authentication Enabled?,Kerberos Usage,User Guide", @@ -23063,7 +23131,7 @@ "uri":"mrs_03_1153.html", "node_id":"mrs_03_1153.xml", "product_code":"mrs", - "code":"1245", + "code":"1249", "des":"Log in to the Master node in the cluster as user root.Run the following command to configure environment variables:source /opt/client/bigdata_envsource /opt/client/bigdat", "doc_type":"faq", "kw":"How Do I Access Presto in a Cluster with Kerberos Authentication Enabled?,Kerberos Usage,User Guide", @@ -23082,7 +23150,7 @@ "uri":"en-us_topic_0000001442653993.html", "node_id":"en-us_topic_0000001442653993.xml", "product_code":"mrs", - "code":"1246", + "code":"1250", "des":"Log in to the master node in the cluster as user root.Run the following command to configure environment variables:source /opt/client/bigdata_envsource /opt/client/bigdat", "doc_type":"faq", "kw":"How Do I Access Spark in a Cluster with Kerberos Authentication Enabled?,Kerberos Usage,User Guide", @@ -23101,7 +23169,7 @@ "uri":"mrs_03_1167.html", "node_id":"mrs_03_1167.xml", "product_code":"mrs", - "code":"1247", + "code":"1251", "des":"Java applications:Before connecting to HBase, HDFS, or other big data components, call loginUserFromKeytab() to create a UGI. Then, start a scheduled thread to periodical", "doc_type":"usermanual", "kw":"How Do I Prevent Kerberos Authentication Expiration?,Kerberos Usage,User Guide", @@ -23120,7 +23188,7 @@ "uri":"mrs_03_2019.html", "node_id":"mrs_03_2019.xml", "product_code":"mrs", - "code":"1248", + "code":"1252", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"faq", "kw":"Metadata Management", @@ -23138,7 +23206,7 @@ "uri":"mrs_03_1119.html", "node_id":"mrs_03_1119.xml", "product_code":"mrs", - "code":"1249", + "code":"1253", "des":"If Hive metadata is stored in GaussDB of an MRS cluster, log in to the master DBServer node of the cluster, switch to user omm, and run the gsql -p 20051 -U {USER} -W {PA", "doc_type":"faq", "kw":"Where Can I View Hive Metadata?,Metadata Management,User Guide", @@ -23157,7 +23225,7 @@ "uri":"en-us_topic_0000001296775220.html", "node_id":"en-us_topic_0000001296775220.xml", "product_code":"mrs", - "code":"1250", + "code":"1254", "des":"For details about the terms involved in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", @@ -23175,7 +23243,7 @@ "uri":"mrs_01_9003.html", "node_id":"mrs_01_9003.xml", "product_code":"mrs", - "code":"1251", + "code":"1255", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", diff --git a/docs/mrs/umn/ALM-12001.html b/docs/mrs/umn/ALM-12001.html index 907470e1..f12dd973 100644 --- a/docs/mrs/umn/ALM-12001.html +++ b/docs/mrs/umn/ALM-12001.html @@ -59,7 +59,7 @@

Possible Causes

  • The network connection is abnormal.
  • The username, password, or dump directory of the dump server does not meet the configuration conditions.
  • The disk space of the dump directory is insufficient.

Procedure

Check whether the network connection is normal.

-
  1. On the FusionInsight Manager home page, choose Audit > Configurations.
  2. Check whether the SFTP IP on the dump configuration page is valid.

    Log in to the node where Manager is located as user root and run the ping command to check whether the network connection between the SFTP server and the cluster is normal.
    • If yes, go to 5.
    • If no, go to 3.
    +
    1. On the MRS Manager home page, choose Audit > Configurations.
    2. Check whether the SFTP IP on the dump configuration page is valid.

      Log in to the node where Manager is located as user root and run the ping command to check whether the network connection between the SFTP server and the cluster is normal.
      • If yes, go to 5.
      • If no, go to 3.

    3. Repair the network connection, reset the SFTP password, and click OK.
    4. Wait for 2 minutes and check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 5.

    @@ -72,10 +72,10 @@

  3. Expand disk space capacity for the third-party server, Reset the SFTP password and click OK
  4. Wait for 2 minutes, view real-time alarms and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 11.

Reset the dump rule.

-
  1. On the FusionInsight Manager home page, choose Audit > Configurations.
  2. Reset dump rules, set the parameters properly, and click OK.
  3. Wait for 2 minutes, view real-time alarms and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 14.
    +
    1. On the MRS Manager home page, choose Audit > Configurations.
    2. Reset dump rules, set the parameters properly, and click OK.
    3. Wait for 2 minutes, view real-time alarms and check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 14.

    Collect fault information.

    -
    1. On the FusionInsight Manager, choose O&M > Log > Download.
    2. Select OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On the MRS Manager, choose O&M > Log > Download.
    2. Select OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

diff --git a/docs/mrs/umn/ALM-12004.html b/docs/mrs/umn/ALM-12004.html index 2d696d0a..1de9157a 100644 --- a/docs/mrs/umn/ALM-12004.html +++ b/docs/mrs/umn/ALM-12004.html @@ -60,7 +60,7 @@

Possible Causes

The LdapServer process in the Manager is abnormal.

Procedure

Check whether the LdapServer process in the Manager is normal.

-
  1. Log in the Manager node in the cluster as user omm.

    Log in to FusionInsight Manager using the floating IP address, and run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check the information about the current Manager two-node cluster.

    +
    1. Log in the Manager node in the cluster as user omm.

      Log in to MRS Manager using the floating IP address, and run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check the information about the current Manager two-node cluster.

    2. Run ps -ef | grep slapd command to check whether the LdapServer resource process in the ${BIGDATA_HOME}/om-server/om/ in the process configuration file is running properly.

      You can determine that the resource is normal by checking the following information:

      1. After the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command runs, ResHAStatus of the OLdap is Normal.
      2. After the ps -ef | grep slapd command runs, the slapd process of port 21750 can be viewed.
        • If yes, go to 3.
        • If no, go to 4.
      @@ -68,7 +68,7 @@

    3. Run the kill -2 ldap pid command to restart the LdapServer process and wait for 20 seconds. The HA starts the OLdap process automatically. Check whether the current OLdap resource is in normal state.

      • If yes, the operation is complete.
      • If no, go to 4.

    Collect fault information.

    -
    1. On the FusionInsight Manager home page, choose O&M > Log > Download.
    2. Select OmsLdapServer and OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On the MRS Manager home page, choose O&M > Log > Download.
    2. Select OmsLdapServer and OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

diff --git a/docs/mrs/umn/ALM-12005.html b/docs/mrs/umn/ALM-12005.html index 489fa52f..9633680c 100644 --- a/docs/mrs/umn/ALM-12005.html +++ b/docs/mrs/umn/ALM-12005.html @@ -55,17 +55,17 @@ -

Impact on the System

The component WebUI authentication services are unavailable and cannot provide security authentication functions for web upper-layer services. Users may be unable to log in to FusionInsight Manager and the WebUIs of components.

+

Impact on the System

The component WebUI authentication services are unavailable and cannot provide security authentication functions for web upper-layer services. Users may be unable to log in to MRS Manager and the WebUIs of components.

Possible Causes

The OLdap resource on which the Okerberos depends is abnormal.

Procedure

Check whether the OLdap resource on which the Okerberos depends is abnormal in the Manager.

-
  1. Log in the Manager node in the cluster as user omm.

    Log in to FusionInsight Manager using the floating IP address, and run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check the information about the current Manager two-node cluster.

    +
    1. Log in the Manager node in the cluster as user omm.

      Log in to MRS Manager using the floating IP address, and run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check the information about the current Manager two-node cluster.

    2. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the OLdap resource status managed by HA is normal. (In single-node mode, the OLdap resource is in the Active_normal state; in the two-node mode, the OLdap resource is in the Active_normal state on the active node and in the Standby_normal state on the standby node.)

      • If yes, go to 4.
      • If no, go to 3.

    3. See the procedure in ALM-12004 OLdap Resource Abnormal to resolve the problem. After the OLdap resource status recovers, check whether the OKerberos resource status is normal.

      • If yes, the operation is complete.
      • If no, go to 4.

    Collect fault information.

    -
    1. On the FusionInsight Manager home page, choose O&M > Log > Download.
    2. Select OmsKerberos and OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On the MRS Manager home page, choose O&M > Log > Download.
    2. Select OmsKerberos and OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

diff --git a/docs/mrs/umn/ALM-12006.html b/docs/mrs/umn/ALM-12006.html index 05b940b1..8924cc3e 100644 --- a/docs/mrs/umn/ALM-12006.html +++ b/docs/mrs/umn/ALM-12006.html @@ -60,7 +60,7 @@

Possible Causes

  • The network is disconnected, the hardware is faulty, or the operating system runs slowly.
  • The memory of the NodeAgent process is insufficient.

Procedure

Check whether the network is disconnected, whether the hardware is faulty, or whether the operating system runs commands slowly.

-
  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, click the host name, and view the IP address of the host for which the alarm is generated.
  2. Log in to the active management node as user root.

    If the faulty node is the active management node and fails login, the network of the active management node may be faulty. In this case, go to 4.

    +
    1. On MRS Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, click the host name, and view the IP address of the host for which the alarm is generated.
    2. Log in to the active management node as user root.

      If the faulty node is the active management node and fails login, the network of the active management node may be faulty. In this case, go to 4.

    3. Run the ping IP address of the faulty host command to check whether the faulty node is reachable.

      • If yes, go to 12.
      • If no, go to 4.

    4. Contact the network administrator to check whether the network is faulty.

      • If yes, go to 5.
      • If no, go to 6.
      @@ -98,7 +98,7 @@ Feb 11 11:44:44 10-120-205-33 ntpq: nss_ldap: failed to bind to LDAP server ldap

    5. Check whether the log file contains an error indicating that the metaspace size or heap memory size is insufficient.

      • If yes, contact O&M personnel personnel to change the memory size.
      • If no, go to 14.

    Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
    2. Select the following nodes from Services and click OK.

      • NodeAgent
      • Controller
      • OS
      +
      1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select the following nodes from Services and click OK.

        • NodeAgent
        • Controller
        • OS

      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12007.html b/docs/mrs/umn/ALM-12007.html index 1d9806ef..f82d2284 100644 --- a/docs/mrs/umn/ALM-12007.html +++ b/docs/mrs/umn/ALM-12007.html @@ -62,7 +62,7 @@

Procedure

Check whether the instance process is abnormal.

-
  1. In the FusionInsight Manager portal, click O&M > Alarm > Alarms, click in the row where the alarm is located , and click the host name to view the host address for which the alarm is generated
  2. On the Alarms page, check whether the ALM-12006 Node Fault is generated.

    • If yes, go to 3.
    • If no, go to 4.
    +
    1. In the MRS Manager portal, click O&M > Alarm > Alarms, click in the row where the alarm is located , and click the host name to view the host address for which the alarm is generated
    2. On the Alarms page, check whether the ALM-12006 Node Fault is generated.

      • If yes, go to 3.
      • If no, go to 4.

    3. Handle the alarm according to ALM-12006 Node Fault.
    4. Log in to the host for which the alarm is generated as user root. Check whether the installation directory user, user group, and permission of the alarm role are correct. The user, user group, and the permission must be omm:ficommon 750.

      For example, the NameNode installation directory is ${BIGDATA_HOME}/FusionInsight_Current/1_8_NameNode/etc.

      • If yes, go to 6.
      • If no, go to 5.

    5. Run the following command to set the permission to 750 and User:Group to omm:ficommon:

      chmod 750 <folder_name>

      @@ -70,12 +70,12 @@

    6. Wait for 5 minutes. In the alarm list, check whether ALM-12007 Process Fault is cleared.

      • If yes, no further action is required.
      • If no, go to 7.

    Check whether disk space is sufficient.

    -
    1. On the FusionInsight Manager, check whether the alarm list contains ALM-12017 Insufficient Disk Capacity.

      • If yes, go to 8.
      • If no, go to 11.
      +
      1. On the MRS Manager, check whether the alarm list contains ALM-12017 Insufficient Disk Capacity.

        • If yes, go to 8.
        • If no, go to 11.

      2. Rectify the fault by following the steps provided in ALM-12017 Insufficient Disk Capacity.
      3. Wait for 5 minutes. In the alarm list, check whether ALM-12017 Insufficient Disk Capacity is cleared.

        • If yes, go to 10.
        • If no, go to 11.

      4. Wait for 5 minutes. In the alarm list, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 11.

      Collect fault information.

      -
      1. On the FusionInsight Manager, choose O&M > Log > Download.
      2. According to the service name obtained in 1, select the component and NodeAgent from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager, choose O&M > Log > Download.
      2. According to the service name obtained in 1, select the component and NodeAgent from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

diff --git a/docs/mrs/umn/ALM-12010.html b/docs/mrs/umn/ALM-12010.html index 56aaaac2..27dacdab 100644 --- a/docs/mrs/umn/ALM-12010.html +++ b/docs/mrs/umn/ALM-12010.html @@ -61,7 +61,7 @@
  • The link between the active and standby Manager is abnormal.
  • The node name configuration is incorrect.
  • The port is disabled by the firewall.

Procedure

Check whether the network between the active and standby Manager server is normal.

-
  1. In the FusionInsight Manager portal, click O&M > Alarm > Alarms, click in the row containing the alarm and view the IP address of the standby Manager (Peer Manager) server in the alarm details.
  2. Log in to the active Manager server as user root.
  3. Run the ping standby Manager heartbeat IP address command to check whether the standby Manager server is reachable.

    • If yes, go to 6.
    • If no, go to 4.
    +
    1. In the MRS Manager portal, click O&M > Alarm > Alarms, click in the row containing the alarm and view the IP address of the standby Manager (Peer Manager) server in the alarm details.
    2. Log in to the active Manager server as user root.
    3. Run the ping standby Manager heartbeat IP address command to check whether the standby Manager server is reachable.

      • If yes, go to 6.
      • If no, go to 4.

    4. Contact the network administrator to check whether the network is faulty.

      • If yes, go to 5.
      • If no, go to 6.

    5. Rectify the network fault and check whether the alarm is cleared from the alarm list.

      • If yes, no further action is required.
      • If no, go to 6.

    6. Run the following command to go to the software installation directory:

      cd /opt

      @@ -76,7 +76,7 @@

    7. Check whether the alarm is cleared from the alarm list.

      • If yes, no further action is required.
      • If no, go to 16.

    Collect fault information.

    -
    1. On the FusionInsight Manager, choose O&M > Log > Download.
    2. Select the following nodes from the Service and click OK:

      • OmmServer
      • Controller
      • NodeAgent
      +
      1. On the MRS Manager, choose O&M > Log > Download.
      2. Select the following nodes from the Service and click OK:

        • OmmServer
        • Controller
        • NodeAgent

      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

diff --git a/docs/mrs/umn/ALM-12011.html b/docs/mrs/umn/ALM-12011.html index 7ed3e46d..24656c05 100644 --- a/docs/mrs/umn/ALM-12011.html +++ b/docs/mrs/umn/ALM-12011.html @@ -60,7 +60,7 @@

Possible Causes

  • The link between the active and standby Managers is interrupted or The storage space of the /srv/BigData/LocalBackup directory is full.
  • The synchronization file does not exist or the file permission is incorrect.

Procedure

Check whether the network between the active Manager server and the standby Manager server is normal.

-
  1. In the FusionInsight Manager portal, click O&M > Alarm > Alarms, click in the row where the alarm is located and obtain the standby Manager server IP address (Peer Manager IP address) in the alarm details.
  2. Log in to the active Manager server as user root.
  3. Run the ping standby Manager IP address command to check whether the standby Manager server is reachable.

    • If yes, go to 6.
    • If no, go to 4.
    +
    1. In the MRS Manager portal, click O&M > Alarm > Alarms, click in the row where the alarm is located and obtain the standby Manager server IP address (Peer Manager IP address) in the alarm details.
    2. Log in to the active Manager server as user root.
    3. Run the ping standby Manager IP address command to check whether the standby Manager server is reachable.

      • If yes, go to 6.
      • If no, go to 4.

    4. Contact the network administrator to check whether the network is faulty.

      • If yes, go to 5.
      • If no, go to 6.

    5. Rectify the network fault and check whether the alarm is cleared from the alarm list.

      • If yes, no further action is required.
      • If no, go to 6.

    @@ -70,7 +70,7 @@

  4. Run the following command to clear unnecessary backup files:

    rm -rf Directory to be cleared

    Example:

    rm -rf /srv/BigData/LocalBackup/0/default-oms_20191211143443

    -

  5. On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management.

    In the Operation column of the backup task to be performed, click Configure and change the value of Maximum Number of Backup Copies to reduce the number of backup file sets.

    +

  6. On MRS Manager, choose O&M > Backup and Restoration > Backup Management.

    In the Operation column of the backup task to be performed, click Configure and change the value of Maximum Number of Backup Copies to reduce the number of backup file sets.

  7. Wait about 1 minute and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 10.

Check whether the synchronization file exists and whether the file permission is normal.

@@ -93,7 +93,7 @@

  • Wait about 10 minute and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 14.

    • Collect fault information.

    -
    1. On the FusionInsight Manager, choose O&M > Log > Download.
    2. Select the following nodes from the Service and click OK:

      • OmmServer
      • Controller
      • NodeAgent
      +
      1. On the MRS Manager, choose O&M > Log > Download.
      2. Select the following nodes from the Service and click OK:

        • OmmServer
        • Controller
        • NodeAgent

      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12012.html b/docs/mrs/umn/ALM-12012.html index 38f5c0b3..129c26ea 100644 --- a/docs/mrs/umn/ALM-12012.html +++ b/docs/mrs/umn/ALM-12012.html @@ -55,7 +55,7 @@
    -

    Impact on the System

    The time on the node is inconsistent with that on other nodes in the cluster. Therefore, some FusionInsight applications on the node may not run properly.

    +

    Impact on the System

    The time on the node is inconsistent with that on other nodes in the cluster. Therefore, some MRS applications on the node may not run properly.

    Possible Causes

    • The NTP service on the current node cannot start properly.
    • The current node fails to synchronize time with the NTP service on the active OMS node.
    • The key value authenticated by the NTP service on the current node is inconsistent with that on the active OMS node.
    • The time offset between the node and the NTP service on the active OMS node is large.
    @@ -66,7 +66,7 @@

    Check whether the chrony service on the node is started properly.

    -
    1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and view the name of the host for which the alarm is generated in Location.
    2. Check whether the chronyd process is running on the node where the alarm is generated. Log in to the node for which the alarm is generated as user root and run the ps -ef | grep chronyd | grep -v grep command to check whether the command output contains the chronyd process.

      • If yes, go to 6.
      • If no, go to 4.
      +
      1. On MRS Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and view the name of the host for which the alarm is generated in Location.
      2. Check whether the chronyd process is running on the node where the alarm is generated. Log in to the node for which the alarm is generated as user root and run the ps -ef | grep chronyd | grep -v grep command to check whether the command output contains the chronyd process.

        • If yes, go to 6.
        • If no, go to 4.

      3. Run the systemctl chronyd start command to start the NTP service. (Currently, only CentOS and Red Hat Enterprise Linux 7.0 or later are supported.)
      4. Check whether the alarm is cleared 10 minutes later.

        • If yes, no further action is required.
        • If no, go to 6.

      Check whether the current node can synchronize time properly with the chrony service on the active OMS node.

      @@ -109,7 +109,7 @@ host01:~ #

    3. After 10 minutes, check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 38.

    Check whether the NTP service on the node is started properly.

    -
    1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and view the name of the host for which the alarm is generated in Location.
    2. Check whether the ntpd process is running on the node using the following method. Log in to the alarm node as user root and run the ps -ef | grep ntpd | grep -v grep command to check whether the command output contains the ntpd process.

      • If yes, go to 24.
      • If no, go to 22.
      +
      1. On MRS Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and view the name of the host for which the alarm is generated in Location.
      2. Check whether the ntpd process is running on the node using the following method. Log in to the alarm node as user root and run the ps -ef | grep ntpd | grep -v grep command to check whether the command output contains the ntpd process.

        • If yes, go to 24.
        • If no, go to 22.

      3. Run the service ntp start command (or the service ntpd start command in Red Hat Enterprise Linux) to start the NTP service.
      4. After 10 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 24.

      Check whether the node can synchronize time properly with the NTP service on the active OMS node.

      @@ -154,7 +154,7 @@ host01:~ #

    3. After 10 minutes, check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 38.

    Collect the fault information.

    -
    1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
    2. In the Services area, select NodeAgent and OmmServer, and click OK. Expand the Hosts dialog box and select the alarm node and the active OMS node.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
    4. Contact O&M personnel and provide the collected logs.
    +
    1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
    2. In the Services area, select NodeAgent and OmmServer, and click OK. Expand the Hosts dialog box and select the alarm node and the active OMS node.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
    4. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12014.html b/docs/mrs/umn/ALM-12014.html index e6de6b4d..efb75a1d 100644 --- a/docs/mrs/umn/ALM-12014.html +++ b/docs/mrs/umn/ALM-12014.html @@ -69,12 +69,12 @@

    Possible Causes

    • The hard disk is removed.
    • The hard disk is offline, or a bad sector exists on the hard disk.
    -

    Procedure

    1. On FusionInsight Manager, click O&M > Alarm > Alarms, and click in the row where the alarm is located.
    2. Obtain HostName, PartitionName and DirName from Location.
    3. Check whether the disk of PartitionName on HostName is inserted to the correct server slot.

      • If yes, go to 4.
      • If no, go to 5.
      +

      Procedure

      1. On MRS Manager, click O&M > Alarm > Alarms, and click in the row where the alarm is located.
      2. Obtain HostName, PartitionName and DirName from Location.
      3. Check whether the disk of PartitionName on HostName is inserted to the correct server slot.

        • If yes, go to 4.
        • If no, go to 5.

      4. Contact hardware engineers to remove the faulty disk.
      5. Log in to the HostName node where an alarm is reported and check whether there is a line containing DirName in the /etc/fstab file as user root.

        • If yes, go to 6.
        • If no, go to 7.

      6. Run the vi /etc/fstab command to edit the file and delete the line containing DirName.
      7. Contact hardware engineers to insert a new disk. For details, see the hardware product document of the relevant model. If the faulty disk is in a RAID group, configure the RAID group. For details, see the configuration methods of the relevant RAID controller card.
      8. Wait 20 to 30 minutes (The disk size determines the waiting time), and run the mount command to check whether the disk has been mounted to the DirName directory.

        • If yes, manually clear the alarm. No further operation is required.
        • If no, go to 9.

      Collect fault information.

      -
      1. On the FusionInsight Manager, choose O&M > Log > Download.
      2. Select the OmmServer from the Services drop-down list and click OK.
      3. Set Start Date for log collection to 10 minutes ahead of the alarm generation time and End Date to 10 minutes behind the alarm generation time and click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager, choose O&M > Log > Download.
      2. Select the OmmServer from the Services drop-down list and click OK.
      3. Set Start Date for log collection to 10 minutes ahead of the alarm generation time and End Date to 10 minutes behind the alarm generation time and click Download.
      4. Contact the O&M personnel and send the collected log information.

      Alarm Clearing

      After the fault is rectified, the system does not automatically clear this alarm, and you need to manually clear the alarm.

      diff --git a/docs/mrs/umn/ALM-12015.html b/docs/mrs/umn/ALM-12015.html index 1d51386c..cebf612d 100644 --- a/docs/mrs/umn/ALM-12015.html +++ b/docs/mrs/umn/ALM-12015.html @@ -69,7 +69,7 @@

    Possible Causes

    The hard disk is faulty, for example, a bad sector exists.

    -

    Procedure

    1. On FusionInsight Manager, choose O&M > Alarm > Alarms, click in the row where the alarm is located.
    2. Obtain HostName and PartitionName from Location. HostName is the node where the alarm is reported, and PartitionName is the partition of the faulty disk.
    3. Contact hardware engineers to check whether the disk is faulty. If the disk is faulty, remove it from the server.
    4. After the disk is removed, alarm ALM-12014 Partition Lost is reported. Handle the alarm. For details, see ALM-12014 Partition Lost. After the alarm ALM-12014 Partition Lost is cleared, alarm ALM-12015 Partition Filesystem Readonly is automatically cleared.
    +

    Procedure

    1. On MRS Manager, choose O&M > Alarm > Alarms, click in the row where the alarm is located.
    2. Obtain HostName and PartitionName from Location. HostName is the node where the alarm is reported, and PartitionName is the partition of the faulty disk.
    3. Contact hardware engineers to check whether the disk is faulty. If the disk is faulty, remove it from the server.
    4. After the disk is removed, alarm ALM-12014 Partition Lost is reported. Handle the alarm. For details, see ALM-12014 Partition Lost. After the alarm ALM-12014 Partition Lost is cleared, alarm ALM-12015 Partition Filesystem Readonly is automatically cleared.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12016.html b/docs/mrs/umn/ALM-12016.html index 27563bbc..435266eb 100644 --- a/docs/mrs/umn/ALM-12016.html +++ b/docs/mrs/umn/ALM-12016.html @@ -65,7 +65,7 @@

    Possible Causes

    • The alarm threshold or alarm smoothing times are incorrect.
    • CPU configuration cannot meet service requirements. The CPU usage reaches the upper limit.

    Procedure

    Check whether the alarm threshold or alarm Trigger Count are correct.

    -
    1. Change the alarm threshold and alarm Trigger Count based on CPU usage.

      On FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > CPU > Host CPU Usage and change the alarm smoothing times based on CPU usage, as shown in Figure 1.

      +
      1. Change the alarm threshold and alarm Trigger Count based on CPU usage.

        On MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > CPU > Host CPU Usage and change the alarm smoothing times based on CPU usage, as shown in Figure 1.

        This option defines the alarm check phase. Trigger Count indicates the alarm check threshold. An alarm is generated when the number of check times exceeds the threshold.

        Figure 1 Setting alarm smoothing times
        @@ -74,10 +74,10 @@

      2. After 2 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 3.

      Check whether the CPU usage reaches the upper limit.

      -
      1. In the alarm list on FusionInsight Manager, click in the row where the alarm is located to view the alarm host address in the alarm details.
      2. On the Hosts page, click the node on which the alarm is reported.
      3. View the CPU usage for 5 minutes. If the CPU usage exceeds the threshold for multiple times, contact the system administrator to add more CPUs.
      4. Check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 7.
        +
        1. In the alarm list on MRS Manager, click in the row where the alarm is located to view the alarm host address in the alarm details.
        2. On the Hosts page, click the node on which the alarm is reported.
        3. View the CPU usage for 5 minutes. If the CPU usage exceeds the threshold for multiple times, contact the system administrator to add more CPUs.
        4. Check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 7.

        Collect fault information.

        -
        1. On the FusionInsight Manager in the active cluster, choose O&M > Log > Download.
        2. Select OmmServer from the Service and click OK.
        3. Set Start Date for log collection to 10 minutes ahead of the alarm generation time and End Date to 10 minutes behind the alarm generation time in Time Range and click Download.
        4. Contact the O&M personnel and send the collected log information.
        +
        1. On the MRS Manager in the active cluster, choose O&M > Log > Download.
        2. Select OmmServer from the Service and click OK.
        3. Set Start Date for log collection to 10 minutes ahead of the alarm generation time and End Date to 10 minutes behind the alarm generation time in Time Range and click Download.
        4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12017.html b/docs/mrs/umn/ALM-12017.html index bc9564a0..bfb21ad0 100644 --- a/docs/mrs/umn/ALM-12017.html +++ b/docs/mrs/umn/ALM-12017.html @@ -70,12 +70,12 @@

    Possible Causes

    • The alarm threshold is incorrect.
    • Disk configuration of the server cannot meet service requirements.

    Procedure

    Check whether the alarm threshold is appropriate.

    -
    1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Disk > Disk Usage and check whether the threshold (configurable, 90% by default) is appropriate.

      • If yes, go to 2.
      • If no, go to 4.
      +
      1. Log in to MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Disk > Disk Usage and check whether the threshold (configurable, 90% by default) is appropriate.

        • If yes, go to 2.
        • If no, go to 4.

      2. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Disk > Disk Usage and click Modify in the Operation column to change the alarm threshold based on site requirements. As shown in Figure 1:

        Figure 1 Setting an alarm threshold

      3. After 2 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 4.

      Check whether the disk usage reaches the upper limit.

      -
      1. In the alarm list on FusionInsight Manager, click in the row where the alarm is located to view the alarm host name and disk partition information in the alarm details.
      2. Log in to the node where the alarm is generated as user root.
      3. Run the df -lmPT | awk '$2 != "iso9660"' | grep '^/dev/' | awk '{"readlink -m "$1 | getline real }{$1=real; print $0}' | sort -u -k 1,1 command to check the system disk partition usage. Check whether the disk is mounted to the following directories based on the disk partition name obtained in 4: /, /opt, /tmp, /var, /var/log, and /srv/BigData(can be customized).

        • If yes, the disk is a system disk. Then go to 10.
        • If no, the disk is not a system disk. Then go to 7.
        +
        1. In the alarm list on MRS Manager, click in the row where the alarm is located to view the alarm host name and disk partition information in the alarm details.
        2. Log in to the node where the alarm is generated as user root.
        3. Run the df -lmPT | awk '$2 != "iso9660"' | grep '^/dev/' | awk '{"readlink -m "$1 | getline real }{$1=real; print $0}' | sort -u -k 1,1 command to check the system disk partition usage. Check whether the disk is mounted to the following directories based on the disk partition name obtained in 4: /, /opt, /tmp, /var, /var/log, and /srv/BigData(can be customized).

          • If yes, the disk is a system disk. Then go to 10.
          • If no, the disk is not a system disk. Then go to 7.

        4. Run the df -lmPT | awk '$2 != "iso9660"' | grep '^/dev/' | awk '{"readlink -m "$1 | getline real }{$1=real; print $0}' | sort -u -k 1,1 command to check the system disk partition usage. Determine the role of the disk based on the disk partition name obtained in 4.
        5. Check the disk service.

          In MRS, check whether the disk service is HDFS, Yarn, Kafka, Supervisor.
          • If yes, adjust the capacity. Then go to 9.
          • If no, go to 12.

        6. After 2 minutes, check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 12.
          @@ -84,7 +84,7 @@

        7. Contact the system administrator to expand the disk capacity.
        8. After 2 minutes, check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 14.

        Collect fault information.

        -
        1. On FusionInsight Manager, choose O&M > Log > Download.
        2. Select OMS from the Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected log information.
        +
        1. On MRS Manager, choose O&M > Log > Download.
        2. Select OMS from the Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12018.html b/docs/mrs/umn/ALM-12018.html index c7f49172..9d9b59cc 100644 --- a/docs/mrs/umn/ALM-12018.html +++ b/docs/mrs/umn/ALM-12018.html @@ -72,10 +72,10 @@ MemAvailable: 227641452 kB

  • Calculate the real-world memory usage: Memory usage = 1 - (Memory available/Memory total)

    • If the memory usage is lower than 90%, manually disable transferring from monitoring indicators to alarms.
    • If the memory usage is higher than 90%, go to 4.

    • Expand the system.

    -
    1. In the alarm list on FusionInsight Manager, click in the row where the alarm is located to view the alarm host address in the alarm details.
    2. Log in to the host where the alarm is generated as user root.
    3. If the memory usage exceeds the threshold, perform memory capacity expansion.
    4. Run the command free -m | grep Mem\: | awk '{printf("%s,", $3 * 100 / $2)}' to check the system memory usage.
    5. Wait for 5 minutes, check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 9.
      +
      1. In the alarm list on MRS Manager, click in the row where the alarm is located to view the alarm host address in the alarm details.
      2. Log in to the host where the alarm is generated as user root.
      3. If the memory usage exceeds the threshold, perform memory capacity expansion.
      4. Run the command free -m | grep Mem\: | awk '{printf("%s,", $3 * 100 / $2)}' to check the system memory usage.
      5. Wait for 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 9.

      Collect fault information.

      -
      1. On the FusionInsight Manager in the active cluster, choose O&M > Log > Download.
      2. Select OmmServer from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager in the active cluster, choose O&M > Log > Download.
      2. Select OmmServer from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12027.html b/docs/mrs/umn/ALM-12027.html index 44469fe7..5d4ccef1 100644 --- a/docs/mrs/umn/ALM-12027.html +++ b/docs/mrs/umn/ALM-12027.html @@ -65,14 +65,14 @@

    Possible Causes

    Too many processes are running on the node. You need to increase the value of pid_max.

    Procedure

    Increase the value of pid_max.

    -
    1. In the alarm list on FusionInsight Manager, click in the row where the alarm is located to view the alarm host address in the alarm details.
    2. Log in to the host where the alarm is generated as user root.
    3. Run the cat /proc/sys/kernel/pid_maxcommand to check the value of pid_max.
    4. If the PID usage exceeds the threshold, run the command echo new value > /proc/sys/kernel/pid_max to enlarge the value of pid_max.

      Example: echo 65536 > /proc/sys/kernel/pid_max

      +
      1. In the alarm list on MRS Manager, click in the row where the alarm is located to view the alarm host address in the alarm details.
      2. Log in to the host where the alarm is generated as user root.
      3. Run the cat /proc/sys/kernel/pid_maxcommand to check the value of pid_max.
      4. If the PID usage exceeds the threshold, run the command echo new value > /proc/sys/kernel/pid_max to enlarge the value of pid_max.

        Example: echo 65536 > /proc/sys/kernel/pid_max

        The maximum value of pid_max is as follows:

        • On 32-bit systems: 32768
        • On 64-bit systems: 4194304 (2^22)

      5. Wait for 5 minutes, and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 6.

      Collect fault information.

      -
      1. On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
      2. Select all services from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
      2. Select all services from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12028.html b/docs/mrs/umn/ALM-12028.html index bb4fab0d..f93743af 100644 --- a/docs/mrs/umn/ALM-12028.html +++ b/docs/mrs/umn/ALM-12028.html @@ -1,6 +1,6 @@ -

    ALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold

    +

    and Z StateALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold

    Description

    The system checks the number of processes in the D stateand Z state of user omm on the host every 30 seconds and compares the actual number with the threshold. The number of processes in the D state and Z state on the host has a default threshold range. This alarm is generated when the number of processes exceeds the threshold.

    This alarm is cleared when the Trigger Count is 1 and the total number of processes in the D state and Z state of user omm on the host does not exceed the threshold. This alarm is cleared when the Trigger Count is greater than 1 and the total number of processes in the D state and Z state of user omm on the host is less than or equal to 90% of the threshold.

    The function of checking the number of processes in the Z state on the host applies to MRS 3.2.0-LTS.2 or later.

    @@ -67,12 +67,12 @@

    Possible Causes

    The host responds slowly to I/O (disk I/O and network I/O) requests and some processes are in the D state and Z state.

    Procedure

    Check the processes in the D state and Z state.

    -
    1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the IP address of the host for which the alarm is generated.
    2. Log in to the host for which the alarm is generated as user root. () Then run the su - omm command to switch to user omm.
    3. Run the following command as user omm to view the PID of the process that is in the D state and Z state:

      ps -elf | grep -v "\[thread_checkio\]" | awk 'NR!=1 {print $2, $3, $4}' | grep omm | awk -F' ' '{print $1, $3}' | grep -E "Z|D" | awk '{print $2}'

      +
      1. In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the IP address of the host for which the alarm is generated.
      2. Log in to the host for which the alarm is generated as user root. () Then run the su - omm command to switch to user omm.
      3. Run the following command as user omm to view the PID of the process that is in the D state and Z state:

        ps -elf | grep -v "\[thread_checkio\]" | awk 'NR!=1 {print $2, $3, $4}' | grep omm | awk -F' ' '{print $1, $3}' | grep -E "Z|D" | awk '{print $2}'

      4. Check whether the command output is empty.

        • If yes, the service process is running properly. Then go to 6.
        • If no, go to 5.

      5. Switch to user root and run the reboot command to restart the host for which the alarm is generated. (Restarting a host is risky. Ensure that the service process is normal after the restart.)
      6. Check whether the alarm is cleared 5 minutes later.

        • If yes, no further action is required.
        • If no, go to 7.

      Collect the fault information.

      -
      1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.
      +
      1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12033.html b/docs/mrs/umn/ALM-12033.html index 2f488dc5..b8212119 100644 --- a/docs/mrs/umn/ALM-12033.html +++ b/docs/mrs/umn/ALM-12033.html @@ -82,7 +82,7 @@

    Possible Causes

    The disk is aged or has bad sectors.

    Procedure

    Check the disk status.

    -
    1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms.
    2. View the detailed information about the alarm. Check the values of HostName and DiskName in the location information to obtain the information about the faulty disk for which the alarm is generated.
    3. Check whether the node for which the alarm is generated is in a virtualization environment.

      • If yes, go to 4.
      • If no, go to 7.
      +
      1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms.
      2. View the detailed information about the alarm. Check the values of HostName and DiskName in the location information to obtain the information about the faulty disk for which the alarm is generated.
      3. Check whether the node for which the alarm is generated is in a virtualization environment.

        • If yes, go to 4.
        • If no, go to 7.

      4. Check whether the storage performance provided by the virtualization environment meets the hardware requirements. Then, go to 5.
      5. Log in to the alarm node as user root, run the df -h command, and check whether the command output contains the value of the DiskName field.

        • If yes, go to 7.
        • If no, go to 6.

      6. Run the lsblk command to check whether the mapping between the value of DiskName and the disk has been created.

        • If yes, go to 7. .
        • If no, go to 22.
        @@ -90,7 +90,7 @@

    Example:

    lsscsi | grep "/dev/sda"

    -

    In the command output, if ATA, SATA, or SAS is displayed in the third line, the disk has not been organized into a RAID group. If other information is displayed, RAID has been set up.

    +

    In the command output, if ATA, SATA, or SAS is displayed in the third line, the disk has not been organized into a RAID group. If other information is displayed, RAID has been set up.

    • If yes, go to 12.
    • If no, go to 8.

  • Run the smartctl -i /dev/sd[x] command to check whether the hardware supports the SMART tool.

    Example:

    smartctl -i /dev/sda

    @@ -105,7 +105,7 @@

    Check the Command/Feature_name column in the command output. If READ SECTOR(S) or WRITE SECTOR(S) is displayed, the disk has bad sectors. If other errors occur, the disk circuit board is faulty. Both errors indicate that the disk is abnormal and needs to be replaced.

    If "No Errors Logged" is displayed, no error log exists. You can trigger the disk SMART self-check.

    • If yes, go to 11.
    • If no, go to 18.
    -

  • Run the smartctl -t long /dev/sd[x] command to trigger the disk SMART self-check. After the command is executed, the time when the self-check is to be completed is displayed. After the self-check is completed, repeat 9 and 10 to check whether the disk is working properly.

    Example:

    +

  • Run the smartctl -t long /dev/sd[x] command to trigger the disk SMART self-check. After the command is executed, the time when the self-check is to be completed is displayed. After the self-check is completed, repeat 9 and 10 to check whether the disk is working properly.

    Example:

    smartctl -t long /dev/sda

    • If yes, go to 17.
    • If no, go to 18.

  • Run the smartctl -d [sat|scsi]+megaraid,[DID] -H --all /dev/sd[x] command to check whether the hardware supports SMART.

    • In the command, [sat|scsi] indicates the disk type. Both types need to be used.
    • [DID] indicates the slot information. Slots 0 to 15 need to be used.
    @@ -126,18 +126,18 @@

    Check the Command/Feature_name column in the command output. If READ SECTOR(S) or WRITE SECTOR(S) is displayed, the disk has bad sectors. If other errors occur, the disk circuit board is faulty. Both errors indicate that the disk is abnormal and needs to be replaced.

    If "No Errors Logged" is displayed, no error log exists. You can trigger the disk SMART self-check.

    • If yes, go to 15.
    • If no, go to 18.
    -

  • Run the smartctl -d [sat|scsi]+megaraid,[DID] -t long /dev/sd[x] command to trigger the disk SMART self-check. After the command is executed, the time when the self-check is to be completed is displayed. After the self-check is completed, repeat 13 and 14 to check whether the disk is working properly.

    Example:

    +

  • Run the smartctl -d [sat|scsi]+megaraid,[DID] -t long /dev/sd[x] command to trigger the disk SMART self-check. After the command is executed, the time when the self-check is to be completed is displayed. After the self-check is completed, repeat 13 and 14 to check whether the disk is working properly.

    Example:

    smartctl -d sat+megaraid,2 -t long /dev/sda

    • If yes, go to 17.
    • If no, go to 18.
    -

  • If the configured RAID controller card does not support SMART, the disk does not support SMART. In this case, use the check tool provided by the corresponding RAID controller card vendor to rectify the fault. Then go to 17.

    For example, LSI is a MegaCLI tool.

    -

  • On FusionInsight Manager, choose O&M > Alarm > Alarms, click Clear in the Operation column of the alarm, and check whether the alarm is reported on the same disk again.

    If the alarm is reported for three times, replace the disk.

    +

  • If the configured RAID controller card does not support SMART, the disk does not support SMART. In this case, use the check tool provided by the corresponding RAID controller card vendor to rectify the fault. Then go to 17.

    For example, LSI is a MegaCLI tool.

    +

  • On MRS Manager, choose O&M > Alarm > Alarms, click Clear in the Operation column of the alarm, and check whether the alarm is reported on the same disk again.

    If the alarm is reported for three times, replace the disk.

    • If yes, go to 18.
    • If no, no further action is required.

    • Replace the disk.

    -
    1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms.
    2. View the detailed information about the alarm. Check the values of HostName and DiskName in the location information to obtain the information about the faulty disk for which the alarm is reported.
    3. Replace the disk.
    4. Check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 22.
      +
      1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms.
      2. View the detailed information about the alarm. Check the values of HostName and DiskName in the location information to obtain the information about the faulty disk for which the alarm is reported.
      3. Replace the disk.
      4. Check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 22.

      Collect the fault information.

      -
      1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.
      +
      1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12034.html b/docs/mrs/umn/ALM-12034.html index 2ad9740f..1e03b1ff 100644 --- a/docs/mrs/umn/ALM-12034.html +++ b/docs/mrs/umn/ALM-12034.html @@ -64,7 +64,7 @@

    Possible Causes

    The alarm cause depends on the task details. Handle the alarm according to the logs and alarm details.

    Procedure

    Check whether the disk space is sufficient.

    -
    1. In the FusionInsight Manager portal, click O&M > Alarm > Alarms.
    2. In the alarm list, click in the row where the alarm is located and obtain TaskName from Location.
    3. Choose O&M > Backup and Restoration > Backup Management.
    4. Search for the backup task based on TaskName and click More in the Operation column. In the displayed dialog box, click View History and view the task details.
    5. In the displayed dialog box and click to check whether the following message is displayed: Failed to backup xx due to insufficient disk space, move the data in the xx directory to other directories.

      • If yes, go to 6.
      • If no, go to 13.
      +
      1. In the MRS Manager portal, click O&M > Alarm > Alarms.
      2. In the alarm list, click in the row where the alarm is located and obtain TaskName from Location.
      3. Choose O&M > Backup and Restoration > Backup Management.
      4. Search for the backup task based on TaskName and click More in the Operation column. In the displayed dialog box, click View History and view the task details.
      5. In the displayed dialog box and click to check whether the following message is displayed: Failed to backup xx due to insufficient disk space, move the data in the xx directory to other directories.

        • If yes, go to 6.
        • If no, go to 13.

      6. Choose Backup Path > View and obtain the Backup Path.
      7. Log in to the node as user root and run the following command to check the node mounting details:

        df -h

      8. Check whether the available space of the node to which the backup path is mounted is less than 20 GB.

        • If yes, go to 9.
        • If no, go to 13.
        @@ -73,7 +73,7 @@

      9. After 2 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 13.

      Collect fault information.

      -
      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
      2. Select Controller from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager portal, choose O&M > Log > Download.
      2. Select Controller from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12035.html b/docs/mrs/umn/ALM-12035.html index 5b84f288..3195abe5 100644 --- a/docs/mrs/umn/ALM-12035.html +++ b/docs/mrs/umn/ALM-12035.html @@ -64,12 +64,12 @@

    Possible Causes

    The alarm cause depends on the task details. Handle the alarm according to the logs and alarm details.

    Procedure

    Collect fault information.

    -
    1. In the FusionInsight Manager, choose Cluster > Name of the desired cluster > Services, and check whether the running status of the component meets the requirements. (The OMS and DBService must be in the normal state, and other components must be stopped.)

      • If yes, go to 9.
      • If no, go to 2.
      -

    2. Restore the component status as required and start the recovery task again.
    3. Log in to the FusionInsight Manager portal and click O&M > Alarm > Alarms.
    4. In the alarm list, click in the row where the alarm is located to obtain TaskName from Location.
    5. Choose O&M > Backup and Restoration > Restoration Management.
    6. Find the restoration task by Task Name and view the task details.
    7. Perform the recovery task again and check whether the recovery task execution is successful.

      • If yes, go to 8.
      • If no, go to 9.
      +
      1. In the MRS Manager, choose Cluster > Name of the desired cluster > Services, and check whether the running status of the component meets the requirements. (The OMS and DBService must be in the normal state, and other components must be stopped.)

        • If yes, go to 9.
        • If no, go to 2.
        +

      2. Restore the component status as required and start the recovery task again.
      3. Log in to the MRS Manager portal and click O&M > Alarm > Alarms.
      4. In the alarm list, click in the row where the alarm is located to obtain TaskName from Location.
      5. Choose O&M > Backup and Restoration > Restoration Management.
      6. Find the restoration task by Task Name and view the task details.
      7. Perform the recovery task again and check whether the recovery task execution is successful.

        • If yes, go to 8.
        • If no, go to 9.

      8. After 2 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 9.

      Collect fault information.

      -
      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
      2. Select Controller from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager portal, choose O&M > Log > Download.
      2. Select Controller from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12037.html b/docs/mrs/umn/ALM-12037.html index 60df8657..63c6b7c9 100644 --- a/docs/mrs/umn/ALM-12037.html +++ b/docs/mrs/umn/ALM-12037.html @@ -60,7 +60,7 @@

    Possible Causes

    • The NTP server network is abnormal.
    • The NTP server authentication fails.
    • The NTP server time cannot be obtained.
    • The time obtained from the NTP server is not continuously updated.

    Procedure

    Check the NTP server network.

    -
    1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and click in the row where the alarm is located.
    2. View the alarm additional information to check whether the NTP server fails to be pinged.

      • If yes, go to 3.
      • If no, go to 4.
      +
      1. On the MRS Manager portal, click O&M > Alarm > Alarms and click in the row where the alarm is located.
      2. View the alarm additional information to check whether the NTP server fails to be pinged.

        • If yes, go to 3.
        • If no, go to 4.

      3. Contact the network administrator to check the network configuration and ensure that the network between the NTP server and the active OMS node is normal. Then, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 4.

      Check whether the NTP server authentication fails.

      @@ -83,7 +83,7 @@

    3. Contact the provider of the NTP server to rectify the NTP server fault. After the NTP server is normal, check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 12.

    Collect fault information.

    -
    1. On the FusionInsight Manager, choose O&M > Log > Download.
    2. Select NodeAgent and OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On the MRS Manager, choose O&M > Log > Download.
    2. Select NodeAgent and OmmServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12038.html b/docs/mrs/umn/ALM-12038.html index e331a142..5eafc437 100644 --- a/docs/mrs/umn/ALM-12038.html +++ b/docs/mrs/umn/ALM-12038.html @@ -1,7 +1,7 @@

    ALM-12038 Monitoring Indicator Dumping Failure

    -

    Description

    After monitoring indicator dumping is configured on FusionInsight Manager, the system checks the monitoring indicator dumping result at the dumping interval (60 seconds by default). This alarm is generated when the dumping fails.

    +

    Description

    After monitoring indicator dumping is configured on MRS Manager, the system checks the monitoring indicator dumping result at the dumping interval (60 seconds by default). This alarm is generated when the dumping fails.

    This alarm is cleared when dumping is successful.

    Attribute

    @@ -55,12 +55,12 @@
    -

    Impact on the System

    The upper-layer management system cannot obtain monitoring indicators from the FusionInsight Manager system.

    +

    Impact on the System

    The upper-layer management system cannot obtain monitoring indicators from the MRS Manager system.

    Possible Causes

    • The server cannot be connected.
    • The save path on the server cannot be accessed.
    • The monitoring indicator file fails to be uploaded.

    Procedure

    Check whether the server connection is normal.

    -
    1. Check whether the network between the FusionInsight Manager system and the server is normal.

      • If yes, go to 3.
      • If no, go to 2.
      +
      1. Check whether the network between the MRS Manager system and the server is normal.

        • If yes, go to 3.
        • If no, go to 2.

      2. Contact the network administrator to recover the network and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 3.

      3. Choose System > Interconnection > Upload Performance Data and check whether the FTP username, password, port, dump mode, and public key configured on the upload performance data page are consistent with the configuration on the server.

        • If yes, go to 5.
        • If no, go to 4.

      4. Enter the correct configuration information, click OK, and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 5.
        @@ -76,7 +76,7 @@

      5. Delete unnecessary files or go to the monitoring indicator dumping configuration page to change the save path. Then, check whether the save path has sufficient disk space.

        • If yes, no further action is required.
        • If no, go to 11.

      Collect fault information.

      -
      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
      2. Select OMS from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager portal, choose O&M > Log > Download.
      2. Select OMS from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12039.html b/docs/mrs/umn/ALM-12039.html index 08e43b94..c043e235 100644 --- a/docs/mrs/umn/ALM-12039.html +++ b/docs/mrs/umn/ALM-12039.html @@ -75,7 +75,7 @@

    Possible Causes

    • The network between the active and standby nodes is unstable.
    • The standby OMS Database is abnormal.
    • The standby node disk space is full.

    Procedure

    Check whether the network between the active and standby nodes is normal.

    -
    1. Log in to FusionInsight Manager, click O&M > Alarm > Alarms, click in the row where the alarm is located, and query the standby OMS Database IP address.
    2. Log in to the active OMS Database node as user root.
    3. Run the ping Standby OMS Database heartbeat IP address command to check whether the standby OMS Database node is reachable.

      • If yes, go to 6.
      • If no, go to 4.
      +
      1. Log in to MRS Manager, click O&M > Alarm > Alarms, click in the row where the alarm is located, and query the standby OMS Database IP address.
      2. Log in to the active OMS Database node as user root.
      3. Run the ping Standby OMS Database heartbeat IP address command to check whether the standby OMS Database node is reachable.

        • If yes, go to 6.
        • If no, go to 4.

      4. Contact the network administrator to check whether the network is faulty.

        • If yes, go to 5.
        • If no, go to 6.

      5. Rectify the network fault and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 6.

      @@ -89,7 +89,7 @@

    4. Expand the disk capacity.
    5. After the disk capacity is expanded, wait 2 minutes and check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 16.

    Collect fault information.

    -
    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
    2. Select OMMServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On the MRS Manager portal, choose O&M > Log > Download.
    2. Select OMMServer from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12040.html b/docs/mrs/umn/ALM-12040.html index 6dc6019e..4b59841d 100644 --- a/docs/mrs/umn/ALM-12040.html +++ b/docs/mrs/umn/ALM-12040.html @@ -64,7 +64,7 @@

    Possible Causes

    • rng-tools or haveged has not been installed or started.
    • The entropy of the OS is smaller than 100 for multiple consecutive times.

    Procedure

    Check whether haveged or rng-tools has been installed or started.

    -
    1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms.
    2. Check the value of HostName in the Location area to obtain the name of the host for which the alarm is generated.
    3. Log in to the node for which the alarm is generated as user root.
    4. Run the /bin/rpm -qa | grep -w "haveged" command to check the haveged installation status and check whether the command output is empty.

      • If yes, go to 6.
      • If no, go to 5.
      +
      1. Log in to MRS Manager and choose O&M > Alarm > Alarms.
      2. Check the value of HostName in the Location area to obtain the name of the host for which the alarm is generated.
      3. Log in to the node for which the alarm is generated as user root.
      4. Run the /bin/rpm -qa | grep -w "haveged" command to check the haveged installation status and check whether the command output is empty.

        • If yes, go to 6.
        • If no, go to 5.

      5. Run the /sbin/service haveged status |grep "running" command and check the command output.

        • If the command is executed successfully, haveged has been installed and configured correctly and is running properly. Go to 8.
        • If the command fails to execute, haveged is not running properly. Run the following command to manually restart haveged and go to 9:

          systemctl restart haveged.service

      6. Run the /bin/rpm -qa | grep -w "rng-tools" command to check the rng-tools installation and check whether the command output is empty.

        • If yes, contact the OS vendor to install and start haveged or rng-tools. Then go to 9.
        • If no, go to 7.
        @@ -94,7 +94,7 @@ Restart=always

      7. Wait until the system to check the entropy at 00:00 on the following day and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 10.

      Collect fault information.

      -
      1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select NodeAgent for Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.
      +
      1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select NodeAgent for Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12041.html b/docs/mrs/umn/ALM-12041.html index f8b23e79..b899dcde 100644 --- a/docs/mrs/umn/ALM-12041.html +++ b/docs/mrs/umn/ALM-12041.html @@ -65,7 +65,7 @@

    Possible Causes

    The file permission is abnormal or the file is lost due to a user manually modified information such as the file permission, user, and user group, or the system is powered off unexpectedly.

    Procedure

    Check whether the abnormal file exists and whether the permission on the abnormal file is correct.

    -
    1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms.
    2. Check the value of HostName to obtain the host name involved in this alarm. Check the value of PathName to obtain the path or name of the abnormal file.
    3. Log in to the node for which the alarm is generated as user root.
    4. Run the ll pathName command, where pathName indicates the name of the abnormal file to obtain the user, permission, and user group information about the file or directory.
    5. Go to ${BIGDATA_HOME}/om-agent/nodeagent/etc/agent/autocheck directory. Then run the vi keyfile command and search for the name of the abnormal file and check the due permission of the file.

      To ensure proper configuration synchronization between the active and standby OMS servers, files, directories, and files and sub-directories in the directories configured in $OMS_RUN_PATH/workspace/ha/module/hasync/plugin/conf/filesync.xml will also be monitored except files and directories in keyfile. User omm must have read and write permissions of files and read and execute permissions of directories.

      +
      1. On the MRS Manager portal, choose O&M > Alarm > Alarms.
      2. Check the value of HostName to obtain the host name involved in this alarm. Check the value of PathName to obtain the path or name of the abnormal file.
      3. Log in to the node for which the alarm is generated as user root.
      4. Run the ll pathName command, where pathName indicates the name of the abnormal file to obtain the user, permission, and user group information about the file or directory.
      5. Go to ${BIGDATA_HOME}/om-agent/nodeagent/etc/agent/autocheck directory. Then run the vi keyfile command and search for the name of the abnormal file and check the due permission of the file.

        To ensure proper configuration synchronization between the active and standby OMS servers, files, directories, and files and sub-directories in the directories configured in $OMS_RUN_PATH/workspace/ha/module/hasync/plugin/conf/filesync.xml will also be monitored except files and directories in keyfile. User omm must have read and write permissions of files and read and execute permissions of directories.

      6. Compare the real-world permission of the file with the due permission obtained in 5 and correct the permission, user, and user group information for the file.
      7. Wait a hour and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 8.

        If the disk partition where the cluster installation directory resides is used up, some temporary files will be generated in the program installation directory when running the sed command fails. Users do not have the read, write, and execute permissions of these temporary files. The system reports an alarm indicating that permissions of temporary files are abnormal if these files are within the monitoring range of the alarm. Perform the preceding alarm handling processes to clear the alarm. Alternatively, you can directly delete the temporary files after confirming that files with abnormal permissions are temporary. The temporary file generated after a sed command execution failure is similar to the following.

        @@ -73,7 +73,7 @@

      Collect fault information.

      -
      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
      2. Select NodeAgent from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager portal, choose O&M > Log > Download.
      2. Select NodeAgent from the Service and click OK.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

      Alarm Clearing

      After the fault is rectified, the system automatically clears this alarm.

      diff --git a/docs/mrs/umn/ALM-12042.html b/docs/mrs/umn/ALM-12042.html index 02049c4f..270f9389 100644 --- a/docs/mrs/umn/ALM-12042.html +++ b/docs/mrs/umn/ALM-12042.html @@ -65,14 +65,14 @@

      Possible Causes

      The file configuration is modified manually or the system is powered off unexpectedly.

      Procedure

      Check abnormal file configuration.

      -
      1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms.
      2. Check the value of HostName to obtain the host name involved in this alarm. Check the value of PathName to obtain the path or name of the abnormal file.
      3. Log in to the node for which the alarm is generated as user root.
      4. View the $BIGDATA_LOG_HOME/nodeagent/scriptlog/checkfileconfig.log file and analyze the cause based on the error log. Locate the check standards of the file in the Related Information and manually check and modify the file based on the standards.

        Run the vi file name command to enter the editing mode, and then press Insert to start editing.

        +
        1. On the MRS Manager portal, choose O&M > Alarm > Alarms.
        2. Check the value of HostName to obtain the host name involved in this alarm. Check the value of PathName to obtain the path or name of the abnormal file.
        3. Log in to the node for which the alarm is generated as user root.
        4. View the $BIGDATA_LOG_HOME/nodeagent/scriptlog/checkfileconfig.log file and analyze the cause based on the error log. Locate the check standards of the file in the Related Information and manually check and modify the file based on the standards.

          Run the vi file name command to enter the editing mode, and then press Insert to start editing.

          After the modification is complete, press Esc to exit the editing mode and enter :wq to save the settings and exit.

          For example:

          vi /etc/ssh/sshd_config

        5. Wait a hour and check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 6.

        Collect fault information.

        -
        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
        2. Select NodeAgent from the Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected log information.
        +
        1. On the MRS Manager portal, choose O&M > Log > Download.
        2. Select NodeAgent from the Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected log information.

      Alarm Clearing

      After the fault is rectified, the system automatically clears this alarm.

      diff --git a/docs/mrs/umn/ALM-12045.html b/docs/mrs/umn/ALM-12045.html index 3c76f998..5ffe8cf4 100644 --- a/docs/mrs/umn/ALM-12045.html +++ b/docs/mrs/umn/ALM-12045.html @@ -73,8 +73,8 @@

      Possible Causes

      • An OS exception occurs.
      • The NICs are bonded in active/standby mode.
      • The alarm threshold is improperly configured.
      • The network quality is poor.

      Procedure

      View the network packet dropped rate.

      -
      1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and view the name of the host for which the alarm is generated and the NIC name.
      2. Log in to the alarm node as user omm, and run the /sbin/ifconfig NIC name command to check whether packet loss occurs on the network.

        -
        • IP address of the node for which the alarm is generated: Query the IP address of the node for which the alarm is generated on the Hosts page of FusionInsight Manager based on the value of HostName in the alarm location information. Check both the IP addresses of the management plane and service plane.
        • Packet loss rate = (Number of dropped packets/Total number of received packets) x 100%. If the packet loss rate is greater than the system threshold (0.5% by default), read packets are dropped.
        +
        1. On MRS Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and view the name of the host for which the alarm is generated and the NIC name.
        2. Log in to the alarm node as user omm, and run the /sbin/ifconfig NIC name command to check whether packet loss occurs on the network.

          +
          • IP address of the node for which the alarm is generated: Query the IP address of the node for which the alarm is generated on the Hosts page of MRS Manager based on the value of HostName in the alarm location information. Check both the IP addresses of the management plane and service plane.
          • Packet loss rate = (Number of dropped packets/Total number of received packets) x 100%. If the packet loss rate is greater than the system threshold (0.5% by default), read packets are dropped.
          • If yes, go to 11.
          • If no, go to 3.

        @@ -92,9 +92,9 @@ Red Hat Enterprise Linux Server release

      3. Run the cat /proc/version command to check whether the SUSE kernel version is 3.0 or later.

        # cat /proc/version
 Linux version 3.0.101-63-default (geeko@buildhost) (gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) ) #1 SMP Tue Jun 23 16:02:31 UTC 2015 (4b89d0c)
        • If yes, the alarm sending function cannot be enabled. Go to 7.
        • If no, go to 11.
        -

      4. Log in to FusionInsight Manager and choose O&M > Alarm > Threshold Configuration.
      1. In the navigation tree of the Thresholds page, choose Name of the desired cluster > Host > Network Reading > Read Packet Dropped Rate. In the area on the right, check whether the Switch is toggled on.

        • If yes, the alarm sending function is enabled. Go to 9.
        • If no, the alarm sending function is disabled. Go to 10.
        +

      2. Log in to MRS Manager and choose O&M > Alarm > Threshold Configuration.
      1. In the navigation tree of the Thresholds page, choose Name of the desired cluster > Host > Network Reading > Read Packet Dropped Rate. In the area on the right, check whether the Switch is toggled on.

        • If yes, the alarm sending function is enabled. Go to 9.
        • If no, the alarm sending function is disabled. Go to 10.

      2. In the area on the right, toggle Switch off to disable the checking of Network Read Packet Dropped Rate Exceeds the Threshold.

        -

      3. On the Alarm page of FusionInsight Manager, search for alarm 12045 and manually clear the alarm if it is not automatically cleared. No further action is required.

        +

      4. On the Alarm page of MRS Manager, search for alarm 12045 and manually clear the alarm if it is not automatically cleared. No further action is required.

        ID of the Network Read Packet Dropped Rate Exceeds the Threshold alarm is 12045.

      @@ -137,7 +137,7 @@ Slave queue ID: 0

    Check whether the threshold is set properly.

    -
    1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Packet Dropped Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

      • If yes, go to 17.
      • If no, go to 15.
      +
      1. Log in to MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Packet Dropped Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

        • If yes, go to 17.
        • If no, go to 15.

      1. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Packet Dropped Rate. Click Modify in the Operation column to change the threshold. See Figure 1.

        Figure 1 Configuring the alarm threshold

      2. After 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 17.

      @@ -146,7 +146,7 @@ Slave queue ID: 0

    2. After 5 minutes, check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 19.

    Collect the fault information.

    -
    1. On FusionInsight Manager of the active cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
    2. Select OMS for Service and click OK.
    3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
    4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
    5. Contact O&M personnel and provide the collected logs.
    +
    1. On MRS Manager of the active cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
    2. Select OMS for Service and click OK.
    3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
    4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
    5. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12046.html b/docs/mrs/umn/ALM-12046.html index 5574b452..c7acf9d3 100644 --- a/docs/mrs/umn/ALM-12046.html +++ b/docs/mrs/umn/ALM-12046.html @@ -71,7 +71,7 @@

    Possible Causes

    • The alarm threshold is improperly configured.
    • The network quality is poor.

    Procedure

    Check whether the threshold is set properly.

    -
    1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Packet Dropped Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

      • If yes, go to 4.
      • If no, go to 2.
      +
      1. Log in to MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Packet Dropped Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

        • If yes, go to 4.
        • If no, go to 2.

      2. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Packet Dropped Rate. Click Modify in the Operation column to change the threshold.

        See Figure 1.

        Figure 1 Configuring the alarm threshold

      3. After 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 4.
        @@ -81,7 +81,7 @@

      4. After 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 6.

      Collect the fault information.

      -
      1. On FusionInsight Manager of the active cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
      5. Contact O&M personnel and provide the collected logs.
      +
      1. On MRS Manager of the active cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
      5. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12047.html b/docs/mrs/umn/ALM-12047.html index 186e7a3d..0b6cd90b 100644 --- a/docs/mrs/umn/ALM-12047.html +++ b/docs/mrs/umn/ALM-12047.html @@ -71,7 +71,7 @@

    Possible Causes

    • The alarm threshold is improperly configured.
    • The network quality is poor.

    Procedure

    Check whether the threshold is set properly.

    -
    1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Packet Error Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

      • If yes, go to 4.
      • If no, go to 2.
      +
      1. Log in to MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Packet Error Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

        • If yes, go to 4.
        • If no, go to 2.

      2. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Packet Error Rate. Click Modify in the Operation column to change the threshold.

        See Figure 1.

        Figure 1 Configuring the alarm threshold

      3. After 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 4.
        @@ -81,7 +81,7 @@

      4. After 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 6.

      Collect the fault information.

      -
      1. On FusionInsight Manager of the active cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
      5. Contact O&M personnel and provide the collected logs.
      +
      1. On MRS Manager of the active cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Select OMS for Service and click OK.
      3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
      5. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12048.html b/docs/mrs/umn/ALM-12048.html index b65b8d8b..5925aa9c 100644 --- a/docs/mrs/umn/ALM-12048.html +++ b/docs/mrs/umn/ALM-12048.html @@ -71,7 +71,7 @@

    Possible Causes

    • The alarm threshold is improperly configured.
    • The network quality is poor.

    Procedure

    Check whether the threshold is set properly.

    -
    1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Packet Error Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

      • If yes, go to 4.
      • If no, go to 2.
      +
      1. Log in to MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Packet Error Rate, and check whether the alarm threshold is configured properly. The default value is 0.5%. You can adjust the threshold as needed.

        • If yes, go to 4.
        • If no, go to 2.

      2. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Packet Error Rate. Click Modify in the Operation column to change the threshold.

        See Figure 1.

        Figure 1 Configuring the alarm threshold

      3. After 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 4.
        @@ -81,7 +81,7 @@

      4. After 5 minutes, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 6.

      Collect the fault information.

      -
      1. On FusionInsight Manager of the active cluster, choose O&M > Log > Download.
      2. Select OMS for Service and click OK.
      3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
      5. Contact O&M personnel and provide the collected logs.
      +
      1. On MRS Manager of the active cluster, choose O&M > Log > Download.
      2. Select OMS for Service and click OK.
      3. Expand the Hosts dialog box and select the alarm node and the active OMS node.
      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
      5. Contact O&M personnel and provide the collected logs.

    Alarm Clearing

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12049.html b/docs/mrs/umn/ALM-12049.html index 46e557dc..31f0dda1 100644 --- a/docs/mrs/umn/ALM-12049.html +++ b/docs/mrs/umn/ALM-12049.html @@ -71,18 +71,18 @@

    Possible Causes

    • The alarm threshold is set improperly.
    • The network port rate cannot meet the current service requirements.

    Procedure

    Check whether the threshold is set properly.

    -
    1. On the FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Throughput Rate and check whether the alarm threshold is set properly. (By default, 80% is a proper value. However, users can configure the value as required.)

      • If yes, go to 2.
      • If no, go to 4.
      +
      1. On the MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Throughput Rate and check whether the alarm threshold is set properly. (By default, 80% is a proper value. However, users can configure the value as required.)

        • If yes, go to 2.
        • If no, go to 4.

      2. Based on actual usage condition, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Reading > Read Throughput Rate and click Modify in the Operation column to modify the alarm threshold.

        For details, see Figure 1.

        Figure 1 Setting alarm thresholds

      3. Wait for 5 minutes, and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 4.

      Check whether the network port rate can meet the service requirements.

      -
      1. On FusionInsight Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host and the network port name for which the alarm is generated.
      2. Log in to the host for which the alarm is generated as user root.
      3. Run the ethtool network port name command to check the maximum speed of the current network port.

        In the VM environment, you cannot run a command to query the network port rate. It is recommended that you contact the system administrator to confirm whether the network port rate meets the requirements.

        +
        1. On MRS Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host and the network port name for which the alarm is generated.
        2. Log in to the host for which the alarm is generated as user root.
        3. Run the ethtool network port name command to check the maximum speed of the current network port.

          In the VM environment, you cannot run a command to query the network port rate. It is recommended that you contact the system administrator to confirm whether the network port rate meets the requirements.

        4. If the network read throughput rate exceeds the threshold, contact the system administrator to increase the network port rate.
        5. Check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 9.

        Collect fault information.

        -
        1. On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
        2. Select OMS from the Service and click OK.
        3. Set Host to the node for which the alarm is generated and the active OMS node.
        4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        5. Contact the O&M personnel and send the collected log information.
        +
        1. On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
        2. Select OMS from the Service and click OK.
        3. Set Host to the node for which the alarm is generated and the active OMS node.
        4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        5. Contact the O&M personnel and send the collected log information.

        Alarm Clearing

        After the fault is rectified, the system automatically clears this alarm.

        diff --git a/docs/mrs/umn/ALM-12050.html b/docs/mrs/umn/ALM-12050.html index 7ec36975..3bc60c04 100644 --- a/docs/mrs/umn/ALM-12050.html +++ b/docs/mrs/umn/ALM-12050.html @@ -71,18 +71,18 @@

        Possible Causes

        • The alarm threshold is set improperly.
        • The network port rate cannot meet the current service requirements.

        Procedure

        Check whether the threshold is set properly.

        -
        1. On the FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Throughput Rate and check whether the alarm threshold is set properly. (By default, 80% is a proper value. However, users can configure the value as required.)

          • If yes, go to 4.
          • If no, go to 2.
          +
          1. On the MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Throughput Rate and check whether the alarm threshold is set properly. (By default, 80% is a proper value. However, users can configure the value as required.)

            • If yes, go to 4.
            • If no, go to 2.

          2. Based on actual usage condition, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Network Writing > Write Throughput Rate and click Modify in the Operation column to modify the alarm threshold.

            For details, see Figure 1.

            Figure 1 Setting alarm thresholds

          3. Wait for 5 minutes, and check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 4.

          Check whether the network port rate can meet the service requirements.

          -
          1. On FusionInsight Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host and the network port name for which the alarm is generated.
          2. Log in to the host for which the alarm is generated as user root.
          3. Run the ethtoolnetwork port name command to check the maximum speed of the current network port.

            In the VM environment, you cannot run a command to query the network port rate. It is recommended that you contact the system administrator to confirm whether the network port rate meets the requirements.

            +
            1. On MRS Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host and the network port name for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the ethtoolnetwork port name command to check the maximum speed of the current network port.

              In the VM environment, you cannot run a command to query the network port rate. It is recommended that you contact the system administrator to confirm whether the network port rate meets the requirements.

            4. If the network write throughput rate exceeds the threshold, contact the system administrator to increase the network port rate.
            5. Check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 9.

            Collect fault information.

            -
            1. On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
            2. Select OMS from the Service and click OK.
            3. Set Host to the node for which the alarm is generated and the active OMS node.
            4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            5. Contact the O&M personnel and send the collected log information.
            +
            1. On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
            2. Select OMS from the Service and click OK.
            3. Set Host to the node for which the alarm is generated and the active OMS node.
            4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            5. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-12051.html b/docs/mrs/umn/ALM-12051.html index 86962524..63812177 100644 --- a/docs/mrs/umn/ALM-12051.html +++ b/docs/mrs/umn/ALM-12051.html @@ -71,7 +71,7 @@

            Possible Causes

            Massive small files are stored in the disk.

            Procedure

            Massive small files are stored in the disk.

            -
            1. On FusionInsight Manager, choose O&M > Alarm > Alarms and click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host and the disk partition for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the df -i | grep -iE "partition name|Filesystem" command to check the current disk Inode usage.

              # df -i | grep -iE "xvda2|Filesystem"
+
              1. On MRS Manager, choose O&M > Alarm > Alarms and click  in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host and the disk partition for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root. 
              3. Run the df -i | grep -iE "partition name|Filesystem" command to check the current disk Inode usage.
                # df -i | grep -iE "xvda2|Filesystem"
 Filesystem            Inodes   IUsed   IFree IUse% Mounted on
 /dev/xvda2           2359296  207420 2151876    9% /
                
 
              4. If the Inode usage exceeds the threshold, manually check small files stored in the disk partition and confirm whether these small files can be deleted.
                 
                Run the for i in /*; do echo $i; find $i|wc -l; done command to query the number of files in a partition. Replace /* with the specified partition.
                
@@ -89,7 +89,7 @@ Filesystem            Inodes   IUsed   IFree IUse% Mounted on
 
              5. Wait for 5 minutes, and check whether the alarm is cleared.
                • If yes, no further action is required.
                • If no, go to 6.
                
 
              
 
              Collect fault information.
              
-
              1. On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
              2. Select OMS from the Service and click OK.
              3. Set Host to the node for which the alarm is generated and the active OMS node.
              4. Click  in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              5. Contact the O&M personnel and send the collected log information.
              
+
              1. On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
              2. Select OMS from the Service and click OK.
              3. Set Host to the node for which the alarm is generated and the active OMS node.
              4. Click  in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              5. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-12052.html b/docs/mrs/umn/ALM-12052.html index 8d6c105f..ade9f482 100644 --- a/docs/mrs/umn/ALM-12052.html +++ b/docs/mrs/umn/ALM-12052.html @@ -66,7 +66,7 @@

            Possible Causes

            • The temporary port cannot meet the current service requirements.
            • The system is abnormal.

            Procedure

            Expand the temporary port number range.

            -
            1. On FusionInsight Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user omm.
            3. Run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 1 command to obtain the value of the start port and run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 2 command to obtain the value of the end port. The total number of temporary ports is the value of the end port minus the value of the start port. If the total number of temporary ports is smaller than 28,232, the random port range of the OS is narrow. Contact the system administrator to increase the port range.
            4. Run the ss -ant 2>/dev/null | grep -v LISTEN | awk 'NR > 2 {print $4}'|cut -d ':' -f 2 | awk '$1 >"Value of the start port" {print $1}' | sort -u | wc -l command to calculate the number of used temporary ports.
            5. The formula for calculating the usage of the temporary ports is: Usage of the temporary ports = (Number of used temporary ports/Total number of temporary ports) x 100%. Check whether the temporary port usage exceeds the threshold.

              • If yes, go to 7.
              • If no, go to 6.
              +
              1. On MRS Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user omm.
              3. Run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 1 command to obtain the value of the start port and run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 2 command to obtain the value of the end port. The total number of temporary ports is the value of the end port minus the value of the start port. If the total number of temporary ports is smaller than 28,232, the random port range of the OS is narrow. Contact the system administrator to increase the port range.
              4. Run the ss -ant 2>/dev/null | grep -v LISTEN | awk 'NR > 2 {print $4}'|cut -d ':' -f 2 | awk '$1 >"Value of the start port" {print $1}' | sort -u | wc -l command to calculate the number of used temporary ports.
              5. The formula for calculating the usage of the temporary ports is: Usage of the temporary ports = (Number of used temporary ports/Total number of temporary ports) x 100%. Check whether the temporary port usage exceeds the threshold.

                • If yes, go to 7.
                • If no, go to 6.

              6. Wait for 5 minutes, and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 7.

              Check whether the system environment is abnormal.

              @@ -86,7 +86,7 @@ tcp 0 0 10-120-85-154:45435 10-120-85-154:9866 CLOSE_WAIT 94237/java

            6. After obtaining the administrator's approval, clear the processes that occupy a large number of ports. Wait for 5 minutes, and check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 10.

            Collect fault information.

            -
            1. On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
            2. Select OMS from the Service and click OK.
            3. Set Host to the node for which the alarm is generated and the active OMS node.
            4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            5. Contact the O&M personnel and send the collected log information and files port_result.txt and ps_result.txt. Then, delete the two residual temporary files from the environment.
            +
            1. On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
            2. Select OMS from the Service and click OK.
            3. Set Host to the node for which the alarm is generated and the active OMS node.
            4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            5. Contact the O&M personnel and send the collected log information and files port_result.txt and ps_result.txt. Then, delete the two residual temporary files from the environment.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-12053.html b/docs/mrs/umn/ALM-12053.html index f363ac07..3d8821d5 100644 --- a/docs/mrs/umn/ALM-12053.html +++ b/docs/mrs/umn/ALM-12053.html @@ -66,11 +66,11 @@

            Possible Causes

            • The application process is abnormal. For example, the opened file or socket is not closed.
            • The number of file handles cannot meet the current service requirements.
            • The system is abnormal.

            Procedure

            Check information about files opened in processes.

            -
            1. On FusionInsight Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the lsof -n|awk '{print $2}'|sort|uniq -c|sort -nr|more command to check the process that occupies excessive file handles.
            4. Check whether the processes in which a large number of files are opened are normal. For example, check whether there are files or sockets not closed.

              • If yes, go to 5.
              • If no, go to 7.
              +
              1. On MRS Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root.
              3. Run the lsof -n|awk '{print $2}'|sort|uniq -c|sort -nr|more command to check the process that occupies excessive file handles.
              4. Check whether the processes in which a large number of files are opened are normal. For example, check whether there are files or sockets not closed.

                • If yes, go to 5.
                • If no, go to 7.

              5. Release the abnormal processes that occupy too many file handles.
              6. Five minutes later, check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 7.

              Increase the number of file handles.

              -
              1. On FusionInsight Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root.
              3. Contact the system administrator to increase the number of system file handles.
              4. Run the cat /proc/sys/fs/file-nr command to view the used handles and the maximum number of file handles. The first value is the number of used handles, the third value is the maximum number. Please check whether the usage exceeds the threshold.

                • If yes, go to 9.
                • If no, go to 11.
                  # cat /proc/sys/fs/file-nr
+
                  1. On MRS Manager, click  in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
                  2. Log in to the host for which the alarm is generated as user root.
                  3. Contact the system administrator to increase the number of system file handles.
                  4. Run the cat /proc/sys/fs/file-nr command to view the used handles and the maximum number of file handles. The first value is the number of used handles, the third value is the maximum number. Please check whether the usage exceeds the threshold.
                    • If yes, go to 9.
                    • If no, go to 11.
                      # cat /proc/sys/fs/file-nr
 12704 0 640000
                      
 
                    
 
                  5. Wait for 5 minutes, and check whether the alarm is cleared.
                    • If yes, no further action is required.
                    • If no, go to 12.
                    
@@ -80,7 +80,7 @@
 
                  6. Wait for 5 minutes, and check whether the alarm is cleared.
                    • If yes, no further action is required.
                    • If no, go to 14.
                    
 
                  
 
                  Collect fault information.
                  
-
                  1. On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
                  2. Select OMS from the Service and click OK.
                  3. Set Host to the node for which the alarm is generated and the active OMS node.
                  4. Click  in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  5. Contact the O&M personnel and send the collected log information.
                  
+
                  1. On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
                  2. Select OMS from the Service and click OK.
                  3. Set Host to the node for which the alarm is generated and the active OMS node.
                  4. Click  in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  5. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-12054.html b/docs/mrs/umn/ALM-12054.html index 9abfe9e3..537cbac8 100644 --- a/docs/mrs/umn/ALM-12054.html +++ b/docs/mrs/umn/ALM-12054.html @@ -68,7 +68,7 @@

            Possible Causes

            No certificate (CA certificate, HA root certificate, HA user certificate, Gaussdb root certificate, or Gaussdb user certificate) is imported to the system, the certificate fails to be imported, or the certificate file is invalid.

            Procedure

            Check the alarm cause.

            -
            1. On FusionInsight Manager, locate the target alarm in the real-time alarm list and click .

              View Additional Information to obtain the additional information about the alarm.

              +
              1. On MRS Manager, locate the target alarm in the real-time alarm list and click .

                View Additional Information to obtain the additional information about the alarm.

                • If CA Certificate is displayed in the additional alarm information, log in to the active OMS management node as user omm and go to 2.
                • If HA root Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 3.
                • If HA server Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 4.
                • If Certificate has expired is displayed in the additional information, view Location to obtain the name of the host for which the alarm is generated. Then, log in to the host as user omm and perform 2 to 4 in sequence to check whether the certificates have expired. If these certificates have not expired, check whether other certificates have been imported. If yes, import the certificate files again.

              Check the validity period of the certificate files in the system.

              @@ -97,7 +97,7 @@
              • If yes, go to 7.
              • If no, no further action is required.

            Collect the fault information.

            -
            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.
            +
            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.

            Alarm Clearing

            This alarm is automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12055.html b/docs/mrs/umn/ALM-12055.html index d41f04d6..0c5e637e 100644 --- a/docs/mrs/umn/ALM-12055.html +++ b/docs/mrs/umn/ALM-12055.html @@ -68,7 +68,7 @@

            Possible Causes

            The remaining validity period of a system certificate (CA certificate, HA root certificate, HA user certificate, Gaussdb root certificate, or Gaussdb user certificate) is less than 30 days.

            Procedure

            Check the alarm cause.

            -
            1. On FusionInsight Manager, locate the target alarm in the real-time alarm list and click .

              View Additional Information to obtain the additional information about the alarm.

              +
              1. On MRS Manager, locate the target alarm in the real-time alarm list and click .

                View Additional Information to obtain the additional information about the alarm.

                • If CA Certificate is displayed in the additional alarm information, log in to the active OMS management node as user omm and go to 2.
                • If HA root Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 3.
                • If HA server Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 4.

              Check the validity period of the certificate files in the system.

              @@ -97,7 +97,7 @@
              • If yes, go to 7.
              • If no, no further action is required.

            Collect the fault information.

            -
            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.
            +
            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.

            Alarm Clearing

            This alarm is automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12057.html b/docs/mrs/umn/ALM-12057.html index 2af662f5..af01f559 100644 --- a/docs/mrs/umn/ALM-12057.html +++ b/docs/mrs/umn/ALM-12057.html @@ -59,10 +59,10 @@

            Possible Causes

            Metadata is not configured with the task to periodically back up data to a third-party server.

            -

            Procedure

            1. On the FusionInsight Manager portal choose O&M > Alarm > Alarms.
            2. In the alarm list, click in the row where the alarm is located and identify the data module from which the alarm is generated based on Additional Information.
            3. Choose O&M > Backup and Restoration > Backup Management > Create.
            4. Configure a backup task. The backup data to be configured is consistent with the data in Additional Information of the alarm.
            5. After the backup task is created successfully, wait for two minutes and check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 6.
              +

              Procedure

              1. On the MRS Manager portal choose O&M > Alarm > Alarms.
              2. In the alarm list, click in the row where the alarm is located and identify the data module from which the alarm is generated based on Additional Information.
              3. Choose O&M > Backup and Restoration > Backup Management > Create.
              4. Configure a backup task. The backup data to be configured is consistent with the data in Additional Information of the alarm.
              5. After the backup task is created successfully, wait for two minutes and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 6.

              Collect fault information

              -
              1. On FusionInsight Manager, choose O&M > Log > Download.
              2. In the Service area, select Controller and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.
              +
              1. On MRS Manager, choose O&M > Log > Download.
              2. In the Service area, select Controller and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-12061.html b/docs/mrs/umn/ALM-12061.html index 0d68beb6..b4170b04 100644 --- a/docs/mrs/umn/ALM-12061.html +++ b/docs/mrs/umn/ALM-12061.html @@ -65,7 +65,7 @@

              Possible Causes

              • The alarm threshold is improperly configured.
              • The maximum number of processes (including threads) that can be concurrently opened by user omm is inappropriate.
              • An excessive number of threads are opened at the same time.

              Procedure

              Check whether the alarm threshold or alarm hit number is properly configured.

              -
              1. On the FusionInsight Manager, change the alarm threshold and Trigger Count based on the actual CPU usage.

                Specifically, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host> Process > omm Process Usage to change Trigger Count.

                +
                1. On the MRS Manager, change the alarm threshold and Trigger Count based on the actual CPU usage.

                  Specifically, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host> Process > omm Process Usage to change Trigger Count.

                  The alarm is generated when the process usage exceeds the threshold for the times specified by Trigger Count.

                  Set the alarm threshold based on the actual process usage. To check the process usage, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host> Process > omm Process Usage, as shown in Figure 1.

                  @@ -73,14 +73,14 @@

                2. 2 minutes later, check whether the alarm is cleared.

                  • If it is, no further action is required.
                  • If it is not, go to 3.

                Check whether the maximum number of processes (including threads) opened by user omm is appropriate.

                -
                1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
                2. Log in to the host where the alarm is generated as user root.
                3. Run the su - omm command to switch to user omm.
                4. Run the ulimit -u command to obtain the maximum number of threads that can be concurrently opened by user omm and check whether the number is greater than or equal to 60000.

                  • If it is, go to 8.
                  • If it is not, go to 7.
                  +
                  1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
                  2. Log in to the host where the alarm is generated as user root.
                  3. Run the su - omm command to switch to user omm.
                  4. Run the ulimit -u command to obtain the maximum number of threads that can be concurrently opened by user omm and check whether the number is greater than or equal to 60000.

                    • If it is, go to 8.
                    • If it is not, go to 7.

                  5. Run the ulimit -u 60000 command to change the maximum number to 60000. Two minutes later, check whether the alarm is cleared.

                    • If it is, no further action is required.
                    • If it is not, go to 12.

                  Check whether an excessive number of processes are opened at the same time.

                  -
                  1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
                  2. Log in to the host where the alarm is generated as user root.
                  3. Run the ps -o nlwp, pid, lwp, args, -u omm|sort -n command to check the numbers of threads used by the system. The result is sorted based on the thread number. Analyze the top 5 thread numbers and check whether the threads are incorrectly used. If they are, contact maintenance personnel to rectify the fault. If they are not, run the ulimit -u command to change the maximum number to be greater than 60000.
                  4. Five minutes later, check whether the alarm is cleared.

                    • If it is, no further action is required.
                    • If it is not, go to 12.
                    +
                    1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
                    2. Log in to the host where the alarm is generated as user root.
                    3. Run the ps -o nlwp, pid, lwp, args, -u omm|sort -n command to check the numbers of threads used by the system. The result is sorted based on the thread number. Analyze the top 5 thread numbers and check whether the threads are incorrectly used. If they are, contact maintenance personnel to rectify the fault. If they are not, run the ulimit -u command to change the maximum number to be greater than 60000.
                    4. Five minutes later, check whether the alarm is cleared.

                      • If it is, no further action is required.
                      • If it is not, go to 12.

                    Collect fault information.

                    -
                    1. On the FusionInsight Manager home page of the active clusters, choose O&M > Log > Download.
                    2. Select OmmServer and NodeAgent from the Service and click OK.
                    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
                    4. Contact the O&M personnel and send the collected log information.
                    +
                    1. On the MRS Manager home page of the active clusters, choose O&M > Log > Download.
                    2. Select OmmServer and NodeAgent from the Service and click OK.
                    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
                    4. Contact the O&M personnel and send the collected log information.

              Alarm Clearing

              This alarm will be automatically cleared after the fault is rectified.

              diff --git a/docs/mrs/umn/ALM-12062.html b/docs/mrs/umn/ALM-12062.html index b93ec017..c363a183 100644 --- a/docs/mrs/umn/ALM-12062.html +++ b/docs/mrs/umn/ALM-12062.html @@ -59,10 +59,10 @@

              Possible Causes

              The OMS parameter configurations mismatch with the cluster scale.

              Procedure

              Check whether the OMS parameter configurations match with the cluster scale.

              -
              1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
              2. Log in to the host where the alarm is generated as user root.
              3. Run the su - omm command to switch to user omm.
              4. Run the vi $BIGDATA_LOG_HOME/controller/scriptlog/modify_manager_param.log command to open the log file and search for the log file containing the following information: Current oms configurations cannot support xx nodes. In the information, xx indicates the number of nodes in the cluster.
              5. Optimize the current cluster configuration by following the instructions in Optimizing Manager Configurations Based on the Number of Cluster Nodes.
              6. One hour later, check whether the alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 7.
                +
                1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
                2. Log in to the host where the alarm is generated as user root.
                3. Run the su - omm command to switch to user omm.
                4. Run the vi $BIGDATA_LOG_HOME/controller/scriptlog/modify_manager_param.log command to open the log file and search for the log file containing the following information: Current oms configurations cannot support xx nodes. In the information, xx indicates the number of nodes in the cluster.
                5. Optimize the current cluster configuration by following the instructions in Optimizing Manager Configurations Based on the Number of Cluster Nodes.
                6. One hour later, check whether the alarm is cleared.

                  • If it is, no further action is required.
                  • If it is not, go to 7.

                Collect fault information.

                -
                1. On FusionInsight Manager, choose O&M > Log > Download.
                2. Select Controller from the Service and click OK.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected log information.
                +
                1. On MRS Manager, choose O&M > Log > Download.
                2. Select Controller from the Service and click OK.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected log information.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-12063.html b/docs/mrs/umn/ALM-12063.html index f5845fde..2171b752 100644 --- a/docs/mrs/umn/ALM-12063.html +++ b/docs/mrs/umn/ALM-12063.html @@ -64,14 +64,14 @@

              Possible Causes

              • The permission of the disk mount directory is abnormal.
              • There are disk bad sectors.

              Procedure

              Check whether the permission of the disk mount directory is normal.

              -
              1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host and DiskName for the disk for which the alarm is generated.
              2. Log in to the host where the alarm is generated as user root.
              3. Run the df -h |grep DiskName command to obtain the mount point and check whether the permission of the mount directory is unwritable or unreadable.

                • If it is, go to 4.
                • If it is not, go to 8.

                  If the permission of the mount directory is 000 or the owner is root, the mount directory is unreadable and unwritable.

                  +
                  1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host and DiskName for the disk for which the alarm is generated.
                  2. Log in to the host where the alarm is generated as user root.
                  3. Run the df -h |grep DiskName command to obtain the mount point and check whether the permission of the mount directory is unwritable or unreadable.

                    • If it is, go to 4.
                    • If it is not, go to 8.

                      If the permission of the mount directory is 000 or the owner is root, the mount directory is unreadable and unwritable.

                  1. Modify the directory permission.
                  2. One hour later, check whether this alarm is cleared.

                    • If it is, no further action is required.
                    • If it is not, go to 6.

                  3. Contact hardware engineers to rectify the disk.
                  4. One hour later, check whether this alarm is cleared.

                    • If it is, no further action is required.
                    • If it is not, go to 8.

                  Collect fault information.

                  -
                  1. On FusionInsight Manager, choose O&M > Log > Download.
                  2. Select NodeAgent from the Service and click OK.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected log information.
                  +
                  1. On MRS Manager, choose O&M > Log > Download.
                  2. Select NodeAgent from the Service and click OK.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected log information.

                  Alarm Clearing

                  After the fault is rectified, the system automatically clears this alarm.

                  diff --git a/docs/mrs/umn/ALM-12064.html b/docs/mrs/umn/ALM-12064.html index ab97f4d0..4296e46a 100644 --- a/docs/mrs/umn/ALM-12064.html +++ b/docs/mrs/umn/ALM-12064.html @@ -59,11 +59,11 @@

                  Possible Causes

                  The random port range configuration is modified.

                  Procedure

                  Check the random port range of the system.

                  -
                  1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
                  2. Log in to the host where the alarm is generated as user root.
                  3. Run the cat /proc/sys/net/ipv4/ip_local_port_range command to obtain the random port range of the host and check whether the minimum value is smaller than 32768.

                    • If it is, go to 4.
                    • If it is not, goto 7.
                    +
                    1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
                    2. Log in to the host where the alarm is generated as user root.
                    3. Run the cat /proc/sys/net/ipv4/ip_local_port_range command to obtain the random port range of the host and check whether the minimum value is smaller than 32768.

                      • If it is, go to 4.
                      • If it is not, goto 7.

                    4. Run the vim /etc/sysctl.conf command to change the value of net.ipv4.ip_local_port_range to 32768 61000. If this parameter does not exist, add the following configuration: net.ipv4.ip_local_port_range = 32768 61000.
                    5. Run the sysctl -p /etc/sysctl.conf command for the modification to take effect.
                    6. One hour later, check whether the alarm is cleared.

                      • If it is, no further action is required.
                      • If it is not, go to 7.

                    Collect fault information.

                    -
                    1. On FusionInsight Manager, choose O&M > Log > Download.
                    2. Select NodeAgent for Service and click OK.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected log information.
                    +
                    1. On MRS Manager, choose O&M > Log > Download.
                    2. Select NodeAgent for Service and click OK.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected log information.

                  Alarm Clearing

                  After the fault is rectified, the system automatically clears this alarm.

                  diff --git a/docs/mrs/umn/ALM-12066.html b/docs/mrs/umn/ALM-12066.html index 5c660d68..08a59211 100644 --- a/docs/mrs/umn/ALM-12066.html +++ b/docs/mrs/umn/ALM-12066.html @@ -59,7 +59,7 @@

                  Possible Causes

                  • The /etc/ssh/sshd_config configuration file is damaged.
                  • The password of user omm has expired.

                  Procedure

                  Check the status of the /etc/ssh/sshd_config configuration file.

                  -
                  1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm and click to view the host list in the alarm details.
                  2. Log in to the active OMS node as user omm.
                  3. Run the ssh command, for example, ssh host2, on each node in the alarm details to check whether the connection fails. (host2 is a node other than the OMS node in the alarm details.)

                    • If yes, go to 4.
                    • If no, go to 6.
                    +
                    1. In the alarm list on MRS Manager, locate the row that contains the alarm and click to view the host list in the alarm details.
                    2. Log in to the active OMS node as user omm.
                    3. Run the ssh command, for example, ssh host2, on each node in the alarm details to check whether the connection fails. (host2 is a node other than the OMS node in the alarm details.)

                      • If yes, go to 4.
                      • If no, go to 6.

                    4. Open the /etc/ssh/sshd_config configuration file on host2 and check whether AllowUsers or DenyUsers is configured for other nodes.

                      • If yes, go to 5.
                      • If no, contact OS experts.

                    5. Modify the whitelist or blacklist to ensure that user omm is in the whitelist or not in the blacklist. Check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 6.

                    @@ -69,7 +69,7 @@

                  4. Add the public key of user omm of the peer host to the trust list of the local host. Run the ssh command, for example, ssh host2, on each node in the alarm details to check whether the connection fails. (host2 is a node other than the OMS node in the alarm details.)

                    • If yes, go to 9.
                    • If no, check whether the alarm is cleared. If the alarm is cleared, no further action is required; otherwise, go to 9.

                  Collect the fault information.

                  -
                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                  2. Select Controller for Service and click OK.
                  3. Click in the upper right corner to set the log collection time range. Generally, the time range is 10 minutes before and after the alarm generation time. Click Download.
                  4. Contact O&M personnel and provide the collected logs.
                  +
                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                  2. Select Controller for Service and click OK.
                  3. Click in the upper right corner to set the log collection time range. Generally, the time range is 10 minutes before and after the alarm generation time. Click Download.
                  4. Contact O&M personnel and provide the collected logs.

                  Alarm Clearing

                  This alarm is automatically cleared after the fault is rectified.

                  diff --git a/docs/mrs/umn/ALM-12067.html b/docs/mrs/umn/ALM-12067.html index 41e1b008..bc2ddb06 100644 --- a/docs/mrs/umn/ALM-12067.html +++ b/docs/mrs/umn/ALM-12067.html @@ -61,10 +61,10 @@

                  Possible Causes

                  • The Tomcat directory permission is abnormal, and the Tomcat process is abnormal.

                  Procedure

                  Check whether the permission on the Tomcat directory is normal.

                  -
                  1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the IP address of the host for which the alarm is generated.
                  2. Log in to the alarm host as user root.
                  3. Run the su - omm command to switch to user omm.
                  4. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/tomcat.log command to check whether the Tomcat resource log contains keyword Cannot find XXX and rectify the file permission based on the keyword.
                  5. After 5 minutes, check whether the alarm is automatically cleared.

                    • If yes, no further action is required.
                    • If no, go to 6.
                    +
                    1. In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the IP address of the host for which the alarm is generated.
                    2. Log in to the alarm host as user root.
                    3. Run the su - omm command to switch to user omm.
                    4. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/tomcat.log command to check whether the Tomcat resource log contains keyword Cannot find XXX and rectify the file permission based on the keyword.
                    5. After 5 minutes, check whether the alarm is automatically cleared.

                      • If yes, no further action is required.
                      • If no, go to 6.

                    Collect the fault information.

                    -
                    1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                    2. In the Services area, select OmmServer and Tomcat, and click OK.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact O&M personnel and provide the collected logs.
                    +
                    1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                    2. In the Services area, select OmmServer and Tomcat, and click OK.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact O&M personnel and provide the collected logs.

                  Alarm Clearing

                  This alarm is automatically cleared after the fault is rectified.

                  diff --git a/docs/mrs/umn/ALM-12068.html b/docs/mrs/umn/ALM-12068.html index cef06028..58abc0dc 100644 --- a/docs/mrs/umn/ALM-12068.html +++ b/docs/mrs/umn/ALM-12068.html @@ -56,16 +56,16 @@
              -

              Impact on the System

              • The active/standby Manager switchover occurs.
              • The ACS process repeatedly restarts, which may cause the FusionInsight Manager login failure.
              +

              Impact on the System

              • The active/standby Manager switchover occurs.
              • The ACS process repeatedly restarts, which may cause the MRS Manager login failure.

              Possible Causes

              The ACS process is abnormal.

              Procedure

              Check whether the ACS process is normal.

              -
              1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
              2. Log in to the alarm host as user root.
              3. Run the su - omm command and then sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh to check whether the status of the ACS resources managed by the HA is normal. In the single-node system, the ACS resource is in the normal state. In the dual-node system, the ACS resource is in the normal state on the active node and in the stopped state on the standby node.

                • If yes, go to 6.
                • If no, go to 4.
                +
                1. In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
                2. Log in to the alarm host as user root.
                3. Run the su - omm command and then sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh to check whether the status of the ACS resources managed by the HA is normal. In the single-node system, the ACS resource is in the normal state. In the dual-node system, the ACS resource is in the normal state on the active node and in the stopped state on the standby node.

                  • If yes, go to 6.
                  • If no, go to 4.

                4. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/acs.log command to check whether the ACS resource log of HA contains the keyword ERROR. If yes, analyze the logs to locate the resource exception cause and fix the exception.
                5. After 5 minutes, check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 6.

                Collect the fault information.

                -
                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                2. In the Services area, select Controller and OmmServer, and click OK.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact O&M personnel and provide the collected logs.
                +
                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                2. In the Services area, select Controller and OmmServer, and click OK.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact O&M personnel and provide the collected logs.

              Alarm Clearing

              This alarm is automatically cleared after the fault is rectified.

              diff --git a/docs/mrs/umn/ALM-12069.html b/docs/mrs/umn/ALM-12069.html index cea673d1..6c3bbc3c 100644 --- a/docs/mrs/umn/ALM-12069.html +++ b/docs/mrs/umn/ALM-12069.html @@ -56,16 +56,16 @@
            -

            Impact on the System

            • The active/standby Manager switchover occurs.
            • The AOS process repeatedly restarts, which may cause the FusionInsight Manager login failure.
            +

            Impact on the System

            • The active/standby Manager switchover occurs.
            • The AOS process repeatedly restarts, which may cause the MRS Manager login failure.

            Possible Causes

            The AOS process is abnormal.

            Procedure

            Check whether the AOS process is normal.

            -
            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
            2. Log in to the alarm host as user root.
            3. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the AOS resources managed by the HA is normal. In the single-node system, the AOS resource is in the normal state. In the dual-node system, the AOS resource is in the normal state on the active node and in the stopped state on the standby node.

              • If yes, go to 6.
              • If no, go to 4.
              +
              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
              2. Log in to the alarm host as user root.
              3. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the AOS resources managed by the HA is normal. In the single-node system, the AOS resource is in the normal state. In the dual-node system, the AOS resource is in the normal state on the active node and in the stopped state on the standby node.

                • If yes, go to 6.
                • If no, go to 4.

              4. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/aos.log command to check whether the AOS resource log of HA contains the keyword ERROR. If yes, analyze the logs to locate the resource exception cause and fix the exception.
              5. After 5 minutes, check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 6.

              Collect the fault information.

              -
              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. In the Services area, select Controller and OmmServer, and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.
              +
              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. In the Services area, select Controller and OmmServer, and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.

            Alarm Clearing

            This alarm is automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12070.html b/docs/mrs/umn/ALM-12070.html index c8a56a10..8e02cff7 100644 --- a/docs/mrs/umn/ALM-12070.html +++ b/docs/mrs/umn/ALM-12070.html @@ -3,7 +3,7 @@

            ALM-12070 Controller Resource Is Abnormal

            Alarm Description

            HA checks the controller resources of Manager every 80 seconds. This alarm is generated when HA detects that the controller resources are abnormal for 2 consecutive times.

            This alarm is cleared when the Controller resource is normal.

            -

            Resource Type of Controller is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new Controller resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            +

            Resource Type of Controller is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new Controller resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            Attribute

            Alarm ID

            @@ -56,16 +56,16 @@
            -

            Impact on the System

            • The active/standby FusionInsight Manager switchover occurs.
            • The Controller process repeatedly restarts, which may cause the FusionInsight Manager login failure.
            +

            Impact on the System

            • The active/standby MRS Manager switchover occurs.
            • The Controller process repeatedly restarts, which may cause the MRS Manager login failure.

            Possible Causes

            The Controller process is abnormal.

            Procedure

            Check whether the controller process is normal.

            -
            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the su - omm command to switch to user omm.Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the Controller resources managed by the HA is normal. In the single-node system, the Controller resource is in the normal state. In the dual-node system, the Controller resource is in the normal state on the active node and in the stopped state on the standby node.

              • If it is, go to 6.
              • If it is not, go to 4.
              +
              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root.
              3. Run the su - omm command to switch to user omm.Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the Controller resources managed by the HA is normal. In the single-node system, the Controller resource is in the normal state. In the dual-node system, the Controller resource is in the normal state on the active node and in the stopped state on the standby node.

                • If it is, go to 6.
                • If it is not, go to 4.

              4. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/controller.log command to view the Controller resource logs, and run the vi $BIGDATA_LOG_HOME/controller/controller.log command to view the Controller running logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
              5. Five minutes later, check whether this alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 6.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServe for Service and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour before and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.
              +
              1. On MRS Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServe for Service and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour before and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-12071.html b/docs/mrs/umn/ALM-12071.html index 3d96f959..a4f6e926 100644 --- a/docs/mrs/umn/ALM-12071.html +++ b/docs/mrs/umn/ALM-12071.html @@ -3,7 +3,7 @@

            ALM-12071 Httpd Resource Is Abnormal

            Description

            HA checks the httpd resources of Manager every 120 seconds. This alarm is generated when HA detects that the httpd resources are abnormal for 10 consecutive times.

            This alarm is cleared when the httpd resource is normal.

            -

            Resource Type of httpd is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new httpd resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            +

            Resource Type of httpd is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new httpd resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            Attribute

            Alarm ID

            @@ -56,16 +56,16 @@
            -

            Impact on the System

            • The active/standby FusionInsight Manager switchover occurs.
            • The httpd process is repeatedly restarts, which may lead to the failure to visit the native service UI.
            +

            Impact on the System

            • The active/standby MRS Manager switchover occurs.
            • The httpd process is repeatedly restarts, which may lead to the failure to visit the native service UI.

            Possible Causes

            The httpd process is abnormal.

            Procedure

            Check whether the httpd process is abnormal.

            -
            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the su - omm command to switch to user omm.
            4. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the httpd resources managed by the HA is normal. In the single-node system, the httpd resource is in the normal state. In the dual-node system, the httpd resource is in the normal state on the active node and in the stopped state on the standby node.

              • If it is, go to 7.
              • If it is not, go to 5.
              +
              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root.
              3. Run the su - omm command to switch to user omm.
              4. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the httpd resources managed by the HA is normal. In the single-node system, the httpd resource is in the normal state. In the dual-node system, the httpd resource is in the normal state on the active node and in the stopped state on the standby node.

                • If it is, go to 7.
                • If it is not, go to 5.

              5. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/httpd.log command to view the httpd resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
              6. Five minutes later, check whether this alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 7.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.
              +
              1. On MRS Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            This alarm will be automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12072.html b/docs/mrs/umn/ALM-12072.html index 64ccb756..68e16509 100644 --- a/docs/mrs/umn/ALM-12072.html +++ b/docs/mrs/umn/ALM-12072.html @@ -3,7 +3,7 @@

            ALM-12072 FloatIP Resource Is Abnormal

            Description

            HA checks the floatip resources of Manager every 9 seconds. This alarm is generated when HA detects that the floatip resources are abnormal for 3 consecutive times.

            This alarm is cleared when the FloatIP resource is normal.

            -

            Resource Type of FloatIP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FloatIP resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            +

            Resource Type of FloatIP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FloatIP resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            Attribute

            Alarm ID

            @@ -56,21 +56,21 @@
            -

            Impact on the System

            • The active/standby FusionInsight Manager switchover occurs.
            • The FloatIP process is repeatedly restarts, which may lead to the failure to visit the native service UI.
            +

            Impact on the System

            • The active/standby MRS Manager switchover occurs.
            • The FloatIP process is repeatedly restarts, which may lead to the failure to visit the native service UI.

            Possible Causes

            • The floating IP address is abnormal.

            Procedure

            Check the floating IP address status of the active management node.

            -
            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the address of the host for which the alarm is generated and the resource name.
            2. Log in to the active management node as user root.
            3. Run the following command, go to the ${BIGDATA_HOME}/om-server/om/sbin/ directory.

              su - omm

              +
              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the address of the host for which the alarm is generated and the resource name.
              2. Log in to the active management node as user root.
              3. Run the following command, go to the ${BIGDATA_HOME}/om-server/om/sbin/ directory.

                su - omm

                cd ${BIGDATA_HOME}/om-server/om/sbin/

                -

              4. Run the sh status-oms.sh command, and execute the status-oms.sh script to check whether the floating IP address of the active FusionInsight Manager is normal. View the command output, locate the row where ResName is floatip, and check whether the following information is displayed.

                For example:

                +

              5. Run the sh status-oms.sh command, and execute the status-oms.sh script to check whether the floating IP address of the active MRS Manager is normal. View the command output, locate the row where ResName is floatip, and check whether the following information is displayed.

                For example:

                10-10-10-160 floatip Normal Normal Single_active
                • If it is, go to 8.
                • If it is not, go to 5.

              6. Run the ifconfig command to check whether the NIC with the floating IP address exists.

                • If it does, go to 8.
                • If it does not, go to 6.

              7. Run the ifconfig NIC name Floating IPaddress netmask Subnet mask command to reconfigure the NIC with the floating IP address. (For example, ifconfig eth0 10.10.10.102 netmask 255.255.255.0).
              8. Five minutes later, check whether the alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 8.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.
              +
              1. On MRS Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            This alarm will be automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12073.html b/docs/mrs/umn/ALM-12073.html index 406d74f4..d96a9359 100644 --- a/docs/mrs/umn/ALM-12073.html +++ b/docs/mrs/umn/ALM-12073.html @@ -3,7 +3,7 @@

            ALM-12073 CEP Resource Is Abnormal

            Description

            HA checks the cep resources of Manager every 60 seconds. This alarm is generated when HA detects that the cep resources are abnormal for 2 consecutive times.

            This alarm is cleared when the CEP resource is normal.

            -

            Resource Type of CEP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new CEP resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            +

            Resource Type of CEP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new CEP resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            Attribute

            Alarm ID

            @@ -56,16 +56,16 @@
            -

            Impact on the System

            • The active/standby FusionInsight Manager switchover occurs.
            • The CEP process repeatedly restarts, causing monitoring data to be abnormal.
            +

            Impact on the System

            • The active/standby MRS Manager switchover occurs.
            • The CEP process repeatedly restarts, causing monitoring data to be abnormal.

            Possible Causes

            The CEP process is abnormal.

            Procedure

            Check whether the CEP process is abnormal.

            -
            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the CEP resources managed by the HA is normal. In the single-node system, the CEP resource is in the normal state. In the dual-node system, the CEP resource is in the normal state on the active node and in the stopped state on the standby node.

              • If it is, go to 6.
              • If it is not, go to 4.
              +
              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root.
              3. Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the CEP resources managed by the HA is normal. In the single-node system, the CEP resource is in the normal state. In the dual-node system, the CEP resource is in the normal state on the active node and in the stopped state on the standby node.

                • If it is, go to 6.
                • If it is not, go to 4.

              4. Run the vi $BIGDATA_LOG_HOME/omm/oms/cep/cep.log and vi $BIGDATA_LOG_HOME/omm/oms/cep/scriptlog/cep_ha.log commands to view the CEP resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
              5. Five minutes later, check whether this alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 6.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.
              +
              1. On MRS Manager, choose O&M > Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            This alarm will be automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12074.html b/docs/mrs/umn/ALM-12074.html index 661d29ed..1398b042 100644 --- a/docs/mrs/umn/ALM-12074.html +++ b/docs/mrs/umn/ALM-12074.html @@ -3,7 +3,7 @@

            ALM-12074 FMS Resource Is Abnormal

            Description

            HA checks the fms resources of Manager every 60 seconds. This alarm is generated when HA detects that the fms resources are abnormal for 2 consecutive times.

            This alarm is cleared when the FMS resource is normal.

            -

            Resource Type of FMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FMS resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            +

            Resource Type of FMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FMS resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            Attribute

            Alarm ID

            @@ -56,16 +56,16 @@
            -

            Impact on the System

            • The active/standby FusionInsight Manager switchover occurs.
            • The FMS process repeatedly restarts. As a result, alarm information may fail to be reported.
            +

            Impact on the System

            • The active/standby MRS Manager switchover occurs.
            • The FMS process repeatedly restarts. As a result, alarm information may fail to be reported.

            Possible Causes

            The FMS process is abnormal.

            Procedure

            Check whether the FMS process is abnormal.

            -
            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the FMS resources managed by the HA is normal. In the single-node system, the FMS resource is in the normal state. In the dual-node system, the FMS resource is in the normal state on the active node and in the stopped state on the standby node.

              • If it is, go to 6.
              • If it is not, go to 4.
              +
              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root.
              3. Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the FMS resources managed by the HA is normal. In the single-node system, the FMS resource is in the normal state. In the dual-node system, the FMS resource is in the normal state on the active node and in the stopped state on the standby node.

                • If it is, go to 6.
                • If it is not, go to 4.

              4. Run the vi $BIGDATA_LOG_HOME/omm/oms/fms/fms.log and vi $BIGDATA_LOG_HOME/omm/oms/fms/scriptlog/fms_ha.log commands to view the FMS resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
              5. 5 minutes later, check whether this alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 6.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M> Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.
              +
              1. On MRS Manager, choose O&M> Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            This alarm will be automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12075.html b/docs/mrs/umn/ALM-12075.html index 3d916ff6..5a11c05e 100644 --- a/docs/mrs/umn/ALM-12075.html +++ b/docs/mrs/umn/ALM-12075.html @@ -3,7 +3,7 @@

            ALM-12075 PMS Resource Is Abnormal

            Description

            HA checks the pms resources of Manager every 55 seconds. This alarm is generated when HA detects that the pms resources are abnormal for three consecutive times.

            This alarm is cleared when the PMS resource is normal.

            -

            Resource Type of PMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new PMS resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            +

            Resource Type of PMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new PMS resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.

            Attribute

            Alarm ID

            @@ -56,16 +56,16 @@
            -

            Impact on the System

            • The active/standby FusionInsight Manager switchover occurs.
            • The PMS process repeatedly restarts, causing monitoring information to be abnormal.
            +

            Impact on the System

            • The active/standby MRS Manager switchover occurs.
            • The PMS process repeatedly restarts, causing monitoring information to be abnormal.

            Possible Causes

            The PMS process is abnormal.

            Procedure

            Check whether the PMS process is abnormal.

            -
            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
            2. Log in to the host for which the alarm is generated as user root.
            3. Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the PMS resources managed by the HA is normal. In the single-node system, the PMS resource is in the normal state. In the dual-node system, the PMS resource is in the normal state on the active node and in the stopped state on the standby node.

              • If it is, go to 6.
              • If it is not, go to 4.
              +
              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
              2. Log in to the host for which the alarm is generated as user root.
              3. Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the PMS resources managed by the HA is normal. In the single-node system, the PMS resource is in the normal state. In the dual-node system, the PMS resource is in the normal state on the active node and in the stopped state on the standby node.

                • If it is, go to 6.
                • If it is not, go to 4.

              4. Run the vi $BIGDATA_LOG_HOME/omm/oms/pms/pms.log and vi $BIGDATA_LOG_HOME/omm/oms/pms/scriptlog/pms_ha.log commands to view the PMS resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
              5. Five minutes later, check whether this alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 6.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M> Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.
              +
              1. On MRS Manager, choose O&M> Log > Download.
              2. Select Controller and OmmServer for Service and click OK.
              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
              4. Contact the O&M personnel and send the collected log information.

            Alarm Clearing

            This alarm will be automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-12076.html b/docs/mrs/umn/ALM-12076.html index ad5bef2e..d1c47d93 100644 --- a/docs/mrs/umn/ALM-12076.html +++ b/docs/mrs/umn/ALM-12076.html @@ -83,11 +83,11 @@
            • If it is, go to 3.
            • If it is not, go to 2.

          4. Contact the network administrator to check whether the network is faulty.

            • If it is, go to 3.
            • If it is not, go to 5.

          5. Five minutes later, check whether the alarm is cleared.

            • If it is, no further action is required.
            • If it is not, go to 4.
            -

          6. Log in to the active and standby management nodes, run the su -omm command to switch to user omm, go to the ${BIGDATA_HOME} /om-server/om/sbin/ directory, and run the status-oms.sh script to check whether the floating IP addresses and GaussDB resources of the active and standby FusionInsight Managers are in the status shown in the following figure.

            +

          7. Log in to the active and standby management nodes, run the su -omm command to switch to user omm, go to the ${BIGDATA_HOME} /om-server/om/sbin/ directory, and run the status-oms.sh script to check whether the floating IP addresses and GaussDB resources of the active and standby MRS Managers are in the status shown in the following figure.

            • If they are, find the alarm in the alarm list and manually clear the alarm.
            • If they are not, go to 5.

          Collect fault information.

          -
          1. On FusionInsight Manager, choose O&M > Log > Download.
          2. Select OmmServer for Service and click OK.
          3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
          4. Contact the O&M personnel and send the collected log information.
          +
          1. On MRS Manager, choose O&M > Log > Download.
          2. Select OmmServer for Service and click OK.
          3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
          4. Contact the O&M personnel and send the collected log information.

        Alarm Clearing

        This alarm will be automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/ALM-12077.html b/docs/mrs/umn/ALM-12077.html index e5ecc3e7..cbb3f5e4 100644 --- a/docs/mrs/umn/ALM-12077.html +++ b/docs/mrs/umn/ALM-12077.html @@ -55,7 +55,7 @@
    -

    Impact on the System

    User omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.

    +

    Impact on the System

    User omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.

    Possible Causes

    User omm has expired.

    @@ -67,7 +67,7 @@

  • Run the chage -E 'yyyy-MM-dd' omm command to set the expiration time of user omm. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12078.html b/docs/mrs/umn/ALM-12078.html index ce4a479f..2925713e 100644 --- a/docs/mrs/umn/ALM-12078.html +++ b/docs/mrs/umn/ALM-12078.html @@ -55,7 +55,7 @@
    -

    Impact on the System

    The password of user omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.

    +

    Impact on the System

    The password of user omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.

    Possible Causes

    The password of user omm has expired.

    @@ -67,7 +67,7 @@

  • Run the chage -M 'days' omm command to set the validity period of the password for user omm. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M> Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M> Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12079.html b/docs/mrs/umn/ALM-12079.html index fcbc2fa4..94dd6b8b 100644 --- a/docs/mrs/umn/ALM-12079.html +++ b/docs/mrs/umn/ALM-12079.html @@ -55,7 +55,7 @@
    -

    Impact on the System

    User omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.

    +

    Impact on the System

    User omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.

    Possible Causes

    The account of user omm is about to expire.

    @@ -67,7 +67,7 @@

  • Run the chage -E 'yyyy-MM-dd' omm command to set the validity period of user omm. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12080.html b/docs/mrs/umn/ALM-12080.html index 13cf3908..d9cf6ac4 100644 --- a/docs/mrs/umn/ALM-12080.html +++ b/docs/mrs/umn/ALM-12080.html @@ -55,7 +55,7 @@
    -

    Impact on the System

    The password of user omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.

    +

    Impact on the System

    The password of user omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.

    Possible Causes

    The password of user omm is about to expire.

    @@ -67,7 +67,7 @@

  • Run the chage -M 'days' omm command to set the validity period of the password for user omm. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M> Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M> Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12081.html b/docs/mrs/umn/ALM-12081.html index a76170aa..f9631705 100644 --- a/docs/mrs/umn/ALM-12081.html +++ b/docs/mrs/umn/ALM-12081.html @@ -1,6 +1,6 @@ -

    ALM-12081 User ommdba Expired

    +

    ALM-12081 User ommdba Expired

    Description

    The system starts at 00:00 every day to check whether user ommdba has expired every 8 hours. This alarm is generated if the user account has expired.

    This alarm is cleared when the expiration time of user ommdba is reset and the user account status becomes normal.

    @@ -67,7 +67,7 @@

  • Run the chage -E 'yyyy-MM-dd' omm command to set the validity period of user ommdba. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12082.html b/docs/mrs/umn/ALM-12082.html index a02f0a50..edb89b53 100644 --- a/docs/mrs/umn/ALM-12082.html +++ b/docs/mrs/umn/ALM-12082.html @@ -67,7 +67,7 @@

  • Run the chage -E 'yyyy-MM-dd' ommdba command to set the validity period of user ommdba. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12083.html b/docs/mrs/umn/ALM-12083.html index 593f5edf..82dd7a2f 100644 --- a/docs/mrs/umn/ALM-12083.html +++ b/docs/mrs/umn/ALM-12083.html @@ -67,7 +67,7 @@

  • Run the chage -M 'days' ommdba command to set the validity period of the password for user ommdba. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12084.html b/docs/mrs/umn/ALM-12084.html index a66079f1..17cfe0f1 100644 --- a/docs/mrs/umn/ALM-12084.html +++ b/docs/mrs/umn/ALM-12084.html @@ -55,7 +55,7 @@ -

    Impact on the System

    The password of user ommdba has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.

    +

    Impact on the System

    The password of user ommdba has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.

    Possible Causes

    The password of user ommdba for the host has expired.

    @@ -67,7 +67,7 @@

  • Run the chage -M 'days' ommdba command to set the validity period of the password for user ommdba. Eight hours later, check whether the alarm is automatically cleared.

    • If it is, no further action is required.
    • If it is not, go to 4.

    • Collect fault information.

    -
    1. On FusionInsight Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On MRS Manager, choose O&M > Log > Download.
    2. Select NodeAgent for Service and click OK.
    3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12085.html b/docs/mrs/umn/ALM-12085.html index 22b1bf20..66835ec4 100644 --- a/docs/mrs/umn/ALM-12085.html +++ b/docs/mrs/umn/ALM-12085.html @@ -59,7 +59,7 @@

    Possible Causes

    • The service audit logs are oversized.
    • The OMS backup storage space is insufficient.
    • The storage space of a host where the service is located is insufficient.

    Procedure

    Check whether the service audit logs are oversized.

    -
    1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host and additional information for which the alarm is generated.
    2. Log in to the host where the alarm is generated as user root.
    3. Run the vi ${BIGDATA_LOG_HOME}/controller/scriptlog/getLogs.log command to check whether the keyword "LOG SIZE is more than 5000MB" can be searched.

      • If it can, go to 4.
      • If it cannot, go to 5.
      +
      1. In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host and additional information for which the alarm is generated.
      2. Log in to the host where the alarm is generated as user root.
      3. Run the vi ${BIGDATA_LOG_HOME}/controller/scriptlog/getLogs.log command to check whether the keyword "LOG SIZE is more than 5000MB" can be searched.

        • If it can, go to 4.
        • If it cannot, go to 5.

      4. Check whether the oversized service audit logs are caused by exceptions.

      The OMS backup storage space is insufficient.

      1. Run the vi ${BIGDATA_LOG_HOME}/controller/scriptlog/getLogs.log command to check whether the keyword "Collect log failed, too many logs on" can be searched.

        • If it can, obtain the host IP address following the keyword "Collect log failed, too many logs on", and go to 6.
        • If it cannot, go to 11.
        @@ -75,7 +75,7 @@

      2. Expand the capacity of the node
      3. In the next execution period, 03:00, check whether the alarm is cleared.

        • If it is, no further action is required.
        • If it is not, go to 15.

      Collect fault information.

      -
      1. On FusionInsight Manager, choose O&M> Log > Download.
      2. Select Controller for Service and click OK.
      3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On MRS Manager, choose O&M> Log > Download.
      2. Select Controller for Service and click OK.
      3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12087.html b/docs/mrs/umn/ALM-12087.html index ffe0d119..f3330965 100644 --- a/docs/mrs/umn/ALM-12087.html +++ b/docs/mrs/umn/ALM-12087.html @@ -71,7 +71,7 @@

    1. In the early morning of the next day, check whether this alarm is cleared.

      • If it is, no further action is required.
      • If it is not, go to 6.

    Collect fault information.

    -
    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
    2. Select Controller from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.
    +
    1. On the MRS Manager portal, choose O&M > Log > Download.
    2. Select Controller from the Service and click OK.
    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
    4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    This alarm will be automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-12089.html b/docs/mrs/umn/ALM-12089.html index 9962d25b..269503c6 100644 --- a/docs/mrs/umn/ALM-12089.html +++ b/docs/mrs/umn/ALM-12089.html @@ -59,15 +59,15 @@

    Possible Causes

    • The node breaks down.
    • The network is faulty.

    Procedure

    Check the network health status.

    -
    1. In the alarm list on FusionInsight Manager, click the drop-down button of the alarm and view Additional Information. Record the source IP address and destination IP address of the node for which the alarm is reported.
    2. Log in to the node for which the alarm is reported. On the node, ping the target node to check whether the network between the two nodes is normal.

      • If yes, go to 6.
      • If no, go to 3.
      +
      1. In the alarm list on MRS Manager, click the drop-down button of the alarm and view Additional Information. Record the source IP address and destination IP address of the node for which the alarm is reported.
      2. Log in to the node for which the alarm is reported. On the node, ping the target node to check whether the network between the two nodes is normal.

        • If yes, go to 6.
        • If no, go to 3.

      Check the node status.

      -
      1. On FusionInsight Manager, click Host and check whether the host list contains the faulty node to determine whether the faulty node has been removed from the cluster.

        • If yes, go to 5.
        • If no, go to 4.
        +
        1. On MRS Manager, click Host and check whether the host list contains the faulty node to determine whether the faulty node has been removed from the cluster.

          • If yes, go to 5.
          • If no, go to 4.

        2. Check whether the faulty node is powered off.

          • If yes, start the faulty node and go to 2.
          • If no, contact related personnel to find root cause, if need to remove the faulty nodes from the cluster and go to 5, otherwise go to 6.

        3. Remove the file $NODE_AGENT_HOME/etc/agent/hosts.ini of all nodes in the cluster, and clean up the file /var/log/Bigdata/unreachable/unreachable_ip_info.log, and then manually clear the alarm.
        4. Wait for 30 seconds and checking if the alarm was been cleared.

          • If yes, no further action is required.
          • If no, go to 7.

        Collect fault information.

        -
        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
        2. Select OmmAgent from the Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected log information.
        +
        1. On the MRS Manager portal, choose O&M > Log > Download.
        2. Select OmmAgent from the Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-12101.html b/docs/mrs/umn/ALM-12101.html index c4577f74..c18546cf 100644 --- a/docs/mrs/umn/ALM-12101.html +++ b/docs/mrs/umn/ALM-12101.html @@ -63,7 +63,7 @@

    Possible Causes

    • The computing resources (Yarn) are unhealthy.
    • The storage resources (HDFS) are unhealthy.
    • Some storage resources (HDFS) are unhealthy.
    • Key roles except Yarn and HDFS are unhealthy.

    Procedure

    Disable the DR drill.

    -
    1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Cross-AZ HA. The Cross-AZ HA page is displayed.
    2. In the AZ DR list, check whether Perform DR Drill in the Operation column of the AZ whose health status is Unhealthy is gray.

      • If yes, go to 4.
      • If no, go to 3.
      +
      1. On MRS Manager, choose Cluster > Name of the desired cluster > Cross-AZ HA. The Cross-AZ HA page is displayed.
      2. In the AZ DR list, check whether Perform DR Drill in the Operation column of the AZ whose health status is Unhealthy is gray.

        • If yes, go to 4.
        • If no, go to 3.

      3. Click Restore in the Operation column of the target AZ. Wait 2 minutes and refresh the page to view the health status of the AZ. Check whether the health status is normal.

        • If yes, no further action is required.
        • If no, go to 4.

      Collect the fault information.

      diff --git a/docs/mrs/umn/ALM-12102.html b/docs/mrs/umn/ALM-12102.html index 219cf47f..1551eb22 100644 --- a/docs/mrs/umn/ALM-12102.html +++ b/docs/mrs/umn/ALM-12102.html @@ -49,7 +49,7 @@

      Possible Causes

      The roles of the components that support DR are not deployed based on DR requirements.

      Procedure

      Obtain alarm information.

      -
      1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
      2. In the alarm list, click in the row that contains the alarm and view the roles that are not deployed based on DR requirements in Additional Information.
      +
      1. On MRS Manager, choose O&M > Alarm > Alarms.
      2. In the alarm list, click in the row that contains the alarm and view the roles that are not deployed based on DR requirements in Additional Information.

      Redeploy the role instance.

      1. Choose Cluster > Services > Name of the desired service > Instance. On the instance page, redeploy or adjust the role instance.
      2. Check whether the alarm is cleared 10 minutes later.

        • If yes, no further action is required.
        • If no, contact O&M personnel.

      diff --git a/docs/mrs/umn/ALM-12103.html b/docs/mrs/umn/ALM-12103.html index 8cf6e245..7efc392c 100644 --- a/docs/mrs/umn/ALM-12103.html +++ b/docs/mrs/umn/ALM-12103.html @@ -61,11 +61,11 @@

      Possible Causes

      The Executor process is abnormal.

      Procedure

      Check whether the Executor process is abnormal.

      -
      1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
      2. Log in to the host for which the alarm is generated as user root.
      3. Run the su - omm command to switch to user omm.
      4. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the Executor resources managed by the HA is normal. In the single-node system, the Executor resource is in the normal state. In the dual-node system, the Executor resource is in the normal state on the active node and in the stopped state on the standby node.

        • If yes, go to 7.
        • If no, go to 5.
        +
        1. In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
        2. Log in to the host for which the alarm is generated as user root.
        3. Run the su - omm command to switch to user omm.
        4. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the Executor resources managed by the HA is normal. In the single-node system, the Executor resource is in the normal state. In the dual-node system, the Executor resource is in the normal state on the active node and in the stopped state on the standby node.

          • If yes, go to 7.
          • If no, go to 5.

        5. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/executor.log command to check whether the Executor resource log of HA contains the keyword ERROR. If yes, analyze the log to locate the resource exception cause and fix the exception.
        6. After 5 minutes, check whether this alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 7.

        Collect the fault information.

        -
        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. In the Services area, select Controller and OmmServer, and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.
        +
        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. In the Services area, select Controller and OmmServer, and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.

      diff --git a/docs/mrs/umn/ALM-12104.html b/docs/mrs/umn/ALM-12104.html index 5fcf3cde..f561100c 100644 --- a/docs/mrs/umn/ALM-12104.html +++ b/docs/mrs/umn/ALM-12104.html @@ -60,11 +60,11 @@

      Possible Causes

      The Knox process is abnormal.

      Procedure

      Check whether the Knox process is normal.

      -
      1. Log in to FusionInsight Manager. In the alarm list, locate the row that contains the alarm and view the name of the host for which the alarm is generated.
      2. Use PuTTY to log in to the host for which the alarm is generated as user root.
      3. Run the su - omm command to switch to user omm.
      4. Run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check whether the status of the Knox resources managed by HA is normal. If the status is normal, the Knox resources are normal. Otherwise, the Knox resources are abnormal.

        • If yes, go to 7.
        • If no, go to 5.
        +
        1. Log in to MRS Manager. In the alarm list, locate the row that contains the alarm and view the name of the host for which the alarm is generated.
        2. Use PuTTY to log in to the host for which the alarm is generated as user root.
        3. Run the su - omm command to switch to user omm.
        4. Run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check whether the status of the Knox resources managed by HA is normal. If the status is normal, the Knox resources are normal. Otherwise, the Knox resources are abnormal.

          • If yes, go to 7.
          • If no, go to 5.

        5. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/knox.log command to check whether the Knox resource log of HA contains the keyword ERROR. If yes, analyze the log to locate the resource exception cause and fix the exception.
        6. After 5 minutes, check whether this alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 7.

        Collect the fault information.

        -
        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. In the Services area, select Controller and OmmServer, and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.
        +
        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. In the Services area, select Controller and OmmServer, and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.

    diff --git a/docs/mrs/umn/ALM-12110.html b/docs/mrs/umn/ALM-12110.html index 7e15d91f..e5439c58 100644 --- a/docs/mrs/umn/ALM-12110.html +++ b/docs/mrs/umn/ALM-12110.html @@ -59,7 +59,7 @@

    Possible Causes

    • The meta role of the MRS cluster is abnormal.
    • The cluster has been bound to an agency and accessed OBS but has been unbound from the agency. As a result, the cluster has not been bound to any agency.

    Procedure

    Check the status of the meta role.

    -
    1. On FusionInsight Manager of the cluster, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and determine the IP address of the host for which the alarm is generated.
    2. On FusionInsight Manager of the cluster, choose Cluster > Services > Meta. On the page that is displayed, click the Instance tab, and check whether the meta role corresponding to the host for which the alarm is generated is normal.

      • If yes, go to 4.
      • If no, go to 3.
      +
      1. On MRS Manager of the cluster, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm, and determine the IP address of the host for which the alarm is generated.
      2. On MRS Manager of the cluster, choose Cluster > Services > Meta. On the page that is displayed, click the Instance tab, and check whether the meta role corresponding to the host for which the alarm is generated is normal.

        • If yes, go to 4.
        • If no, go to 3.

      3. Select the abnormal role and choose More > Restart Instance to restart the abnormal meta role. After the restart is complete, check whether the alarm is cleared several minutes later.

        • If yes, no further action is required.
        • If no, go to 4.

      Rebind the cluster to an agency.

      diff --git a/docs/mrs/umn/ALM-12172.html b/docs/mrs/umn/ALM-12172.html index d4097225..8349f276 100644 --- a/docs/mrs/umn/ALM-12172.html +++ b/docs/mrs/umn/ALM-12172.html @@ -58,7 +58,7 @@

    Possible Causes

    • Failed to call Cloud Eye APIs due to insufficient permissions.
    • Failed to report data to Cloud Eye due to network problems.
    • Failed to report data to Cloud Eye due to internal errors.
    -

    Procedure

    1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm and view the additional information of the alarm.
    2. Rectify the fault based on the following scenarios:

      • If "Call CES to send metrics fail. Permission exception" is displayed in the additional information, the token of the resource tenant is invalid. Restart the Controller and obtain the token again.
      • If "Call CES to send metrics fail. Request CES error code xxx" is displayed in the additional information, an error occurs in the request to Cloud Eye. Check the network connectivity and authentication information.
      • If "Call CES to send metrics fail. CES internal error code xxx" is displayed in the additional information, the Cloud Eye service encounters an internal error and is unavailable. Contact O&M personnel and send collected fault logs.
      +

      Procedure

      1. On MRS Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click in the row containing the alarm and view the additional information of the alarm.
      2. Rectify the fault based on the following scenarios:

        • If "Call CES to send metrics fail. Permission exception" is displayed in the additional information, the token of the resource tenant is invalid. Restart the Controller and obtain the token again.
        • If "Call CES to send metrics fail. Request CES error code xxx" is displayed in the additional information, an error occurs in the request to Cloud Eye. Check the network connectivity and authentication information.
        • If "Call CES to send metrics fail. CES internal error code xxx" is displayed in the additional information, the Cloud Eye service encounters an internal error and is unavailable. Contact O&M personnel and send collected fault logs.

      Alarm Clearing

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-12180.html b/docs/mrs/umn/ALM-12180.html index b7725049..75b9dd44 100644 --- a/docs/mrs/umn/ALM-12180.html +++ b/docs/mrs/umn/ALM-12180.html @@ -88,10 +88,10 @@

      Possible Causes

      The disk is aged.

      Procedure

      Replace the disk.

      -
      1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms.
      2. View the detailed information about the alarm. Check the values of HostName and DiskName in the location information to obtain the information about the faulty disk for which the alarm is reported.
      3. Replace the hard disk.
      4. Check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 5.
        +
        1. Log in to MRS Manager and choose O&M > Alarm > Alarms.
        2. View the detailed information about the alarm. Check the values of HostName and DiskName in the location information to obtain the information about the faulty disk for which the alarm is reported.
        3. Replace the hard disk.
        4. Check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 5.

        Collect fault information.

        -
        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. Select OMS for Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.
        +
        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. Select OMS for Service and click OK.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.

      Alarm Clearing

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-13000.html b/docs/mrs/umn/ALM-13000.html index 2710fd33..b6783381 100644 --- a/docs/mrs/umn/ALM-13000.html +++ b/docs/mrs/umn/ALM-13000.html @@ -70,21 +70,21 @@

    3. On the O&M > Alarm > Alarms tab, check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, go to 9.

    Check the KrbServer service status (Skip this step if the normal mode is used).

    -
    1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services.
    2. Check whether the KrbServer service is normal.

      • If yes, go to 13.
      • If no, go to 11.
      +
      1. On MRS Manager, choose Cluster > Name of the desired cluster > Services.
      2. Check whether the KrbServer service is normal.

        • If yes, go to 13.
        • If no, go to 11.

      3. Perform operations based on "ALM-25500 KrbServer Service Unavailable" and check whether the KrbServer service is recovered.

        • If yes, go to 12.
        • If no, go to 23.

      4. On the O&M > Alarm > Alarms tab, check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 13.

      Check the ZooKeeper service instance status.

      -
      1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper > quorumpeer.
      2. Check whether the ZooKeeper instances are normal.

        • If yes, go to 18.
        • If no, go to 15.
        +
        1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper > quorumpeer.
        2. Check whether the ZooKeeper instances are normal.

          • If yes, go to 18.
          • If no, go to 15.

        3. Select instances whose status is not good, and choose More > Restart Instance.
        4. Check whether the instance status is good after restart.

          • If yes, go to 17.
          • If no, go to 18.

        5. On the O&M > Alarm > Alarms tab, check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 18.

        Check disk status.

        -
        1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > ZooKeeper > quorumpeer, and check the node host information of the ZooKeeper instance.
        2. On FusionInsight Manager, click Host.
        3. In the Disk column, check whether the disk space of each node where ZooKeeper instances are located is insufficient (disk usage exceeds 80%).

          • If yes, go to 21.
          • If no, go to 23.
          +
          1. On MRS Manager, choose Cluster > Name of the desired cluster > Service > ZooKeeper > quorumpeer, and check the node host information of the ZooKeeper instance.
          2. On MRS Manager, click Host.
          3. In the Disk column, check whether the disk space of each node where ZooKeeper instances are located is insufficient (disk usage exceeds 80%).

            • If yes, go to 21.
            • If no, go to 23.

          4. Expand disk capacity. For details, see "ALM-12017 Insufficient Disk Capacity".
          5. On the O&M > Alarm > Alarms tab, check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 23.

          Collect fault information.

          -
          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
          2. Select the following nodes in the required cluster from the Service: (KrbServer logs do not need to be downloaded in normal mode.)

            • ZooKeeper
            • KrbServer
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select the following nodes in the required cluster from the Service: (KrbServer logs do not need to be downloaded in normal mode.)

              • ZooKeeper
              • KrbServer

            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-13001.html b/docs/mrs/umn/ALM-13001.html index 54c9f2ea..95937b67 100644 --- a/docs/mrs/umn/ALM-13001.html +++ b/docs/mrs/umn/ALM-13001.html @@ -65,16 +65,16 @@

    Possible Causes

    The number of connections to the ZooKeeper node exceeds the threshold. Connection leakage occurs on some connection processes, or the maximum number of connections does not comply with the actual scenario.

    Procedure

    Check connection status.

    -
    1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of Available ZooKeeper Connections Are Insufficient and confirm the node IP address of the host for which the alarm is generated in the Location Information.
    2. Obtain the PID of the ZooKeeper process. Log in to the node involved in this alarm as user root and run the pgrep -f proc_zookeeper command.
    3. Check whether the PID can be correctly obtained.

      • If yes, go to 4.
      • If no, go to 15.
      +
      1. On the MRS Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of Available ZooKeeper Connections Are Insufficient and confirm the node IP address of the host for which the alarm is generated in the Location Information.
      2. Obtain the PID of the ZooKeeper process. Log in to the node involved in this alarm as user root and run the pgrep -f proc_zookeeper command.
      3. Check whether the PID can be correctly obtained.

        • If yes, go to 4.
        • If no, go to 15.

      4. Obtain all the IP addresses connected to the ZooKeeper instance and the number of connections and check 10 IP addresses with top connections. Run the following command based on the obtained PID: lsof -i|grep $pid | awk '{print $9}' | cut -d : -f 2 | cut -d \>-f 2 | awk '{a[$1]++} END {for(i in a){print i,a[i] | "sort -r -g -k 2"}}' | head -10. (The PID obtained in the preceding step is used.)
      5. Check whether node IP addresses and number of connections are successfully obtained.

        • If yes, go to 6.
        • If no, go to 15.

      6. Obtain the ID of the port connected to the process. Run the following command based on the obtained PID and IP address: lsof -i|grep $pid | awk '{print $9}'|cut -d \> -f 2 |grep $IP| cut -d : -f 2. (The PID and IP address obtained in the preceding step are used.)
      7. Check whether the port ID is successfully obtained.

        • If yes, go to 8.
        • If no, go to 15.

      8. Obtain the ID of the connected process. Log in to each IP address and run the following command based on the obtained port ID: lsof -i|grep $port. (The port ID obtained in the preceding step is used.)
      9. Check whether the process ID is successfully obtained.

        • If yes, go to 10.
        • If no, go to 15.

      10. Check whether connection leakage occurs on the process based on the obtained process ID.

        • If yes, go to 11.
        • If no, go to 12.

      11. Close the process where connection leakage occurs and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 12.
        -

      12. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer > Performance and increase the value of maxCnxns as required.
      13. Save the configuration and restart the ZooKeeper service.
      14. Check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 15.
        +

      15. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer > Performance and increase the value of maxCnxns as required.
      16. Save the configuration and restart the ZooKeeper service.
      17. Check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 15.

      Collect fault information.

      -
      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
      2. Select ZooKeeper in the required cluster from the Service:
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.
      +
      1. On the MRS Manager portal, choose O&M > Log > Download.
      2. Select ZooKeeper in the required cluster from the Service:
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected log information.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-13002.html b/docs/mrs/umn/ALM-13002.html index 7db4f4ee..78e958a3 100644 --- a/docs/mrs/umn/ALM-13002.html +++ b/docs/mrs/umn/ALM-13002.html @@ -65,13 +65,13 @@

    Possible Causes

    The direct memory of the ZooKeeper instance is overused or the direct memory is inappropriately allocated.

    Procedure

    Check the direct memory usage.

    -
    1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ZooKeeper Direct Memory Usage Exceeds the Threshold. Check the IP address of the instance that reports the alarm.
    2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Instance > quorumpeer(the IP address checked). Click the drop-down menu in the upper right corner of Chart, choose Customize > CPU and Memory, and select ZooKeeper Heap And Direct Buffer Resource Percentage, click OK.
    3. Check whether the used direct buffer memory of ZooKeeper reaches 80% of the maximum direct buffer memory specified for ZooKeeper.

      • If yes, go to 4.
      • If no, go to 8.
      -

    4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

      • If yes, in the GC_OPTS parameter, delete "-XX:MaxDirectMemorySize" and go to 5.
      • If no, go to 6.
      +
      1. On the MRS Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ZooKeeper Direct Memory Usage Exceeds the Threshold. Check the IP address of the instance that reports the alarm.
      2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Instance > quorumpeer(the IP address checked). Click the drop-down menu in the upper right corner of Chart, choose Customize > CPU and Memory, and select ZooKeeper Heap And Direct Buffer Resource Percentage, click OK.
      3. Check whether the used direct buffer memory of ZooKeeper reaches 80% of the maximum direct buffer memory specified for ZooKeeper.

        • If yes, go to 4.
        • If no, go to 8.
        +

      4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

        • If yes, in the GC_OPTS parameter, delete "-XX:MaxDirectMemorySize" and go to 5.
        • If no, go to 6.

      5. Save the configuration and restart the ZooKeeper service.
      6. Check whether the ALM-13004 ZooKeeper Heap Memory Usage Exceeds the Threshold exists.

        • If yes, handle the alarm by referring to ALM-13004 ZooKeeper Heap Memory Usage Exceeds the Threshold.
        • If no, go to 7.

      7. Check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 8.

      Collect fault information.

      -
      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
      2. Select ZooKeeper in the required cluster from the Service.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected logs.
      +
      1. On the MRS Manager portal, choose O&M > Log > Download.
      2. Select ZooKeeper in the required cluster from the Service.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact the O&M personnel and send the collected logs.

    Alarm Clearing

    After the fault is rectified, the system automatically clears this alarm.

    diff --git a/docs/mrs/umn/ALM-13003.html b/docs/mrs/umn/ALM-13003.html index ab82ece8..af6bdf1a 100644 --- a/docs/mrs/umn/ALM-13003.html +++ b/docs/mrs/umn/ALM-13003.html @@ -60,19 +60,19 @@
    -

    Impact on the System

    A long GC duration of the ZooKeeper process may interrupt the services.

    +

    Impact on the System

    A long GC duration of the ZooKeeper process may interrupt the services.

    Possible Causes

    The heap memory of the ZooKeeper process is overused or inappropriately allocated, causing frequent occurrence of the GC process.

    Procedure

    Check the GC duration.

    -
    1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the displayed page, click the drop-down list of GC Duration of the ZooKeeper Process Exceeds the Threshold. View the IP address of the instance for which the alarm is generated.
    2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Instance > quorumpeer. Click the drop-down list in the upper right corner of Chart, choose Customize > GC, select ZooKeeper GC Duration per Minute, and click OK to check the GC duration statistics of the ZooKeeper process collected every minute.
    3. Check whether the GC duration of the ZooKeeper process collected every minute exceeds the threshold (12 seconds by default).

      • If yes, go to 4.
      • If no, go to 8.
      -

    4. Check whether memory leakage occurs in the application.
    5. On the Home page of FusionInsight Manager, choose Cluster > Services > ZooKeeper. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, and select quorumpeer > System. Increase the value of the GC_OPTS parameter as required.

      Generally, -Xmx is twice of ZooKeeper data capacity. If the capacity of ZooKeeper reaches 2 GB, set GC_OPTS as follows:

      +
      1. On MRS Manager, choose O&M > Alarm > Alarms. On the displayed page, click the drop-down list of GC Duration of the ZooKeeper Process Exceeds the Threshold. View the IP address of the instance for which the alarm is generated.
      2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Instance > quorumpeer. Click the drop-down list in the upper right corner of Chart, choose Customize > GC, select ZooKeeper GC Duration per Minute, and click OK to check the GC duration statistics of the ZooKeeper process collected every minute.
      3. Check whether the GC duration of the ZooKeeper process collected every minute exceeds the threshold (12 seconds by default).

        • If yes, go to 4.
        • If no, go to 8.
        +

      4. Check whether memory leakage occurs in the application.
      5. On the Home page of MRS Manager, choose Cluster > Services > ZooKeeper. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, and select quorumpeer > System. Increase the value of the GC_OPTS parameter as required.

        Generally, -Xmx is twice of ZooKeeper data capacity. If the capacity of ZooKeeper reaches 2 GB, set GC_OPTS as follows:

        -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=512M -XX:MetaspaceSize=64M -XX:MaxMetaspaceSize=64M -XX:CMSFullGCsBeforeCompaction=1

      6. Save the configuration and restart the ZooKeeper service.
      7. Check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, go to 8.

      Collect the fault information.

      -
      1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select ZooKeeper for the target cluster.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.
      +
      1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select ZooKeeper for the target cluster.
      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
      4. Contact O&M personnel and provide the collected logs.

      Alarm Clearing

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-13004.html b/docs/mrs/umn/ALM-13004.html index de5c4887..58939774 100644 --- a/docs/mrs/umn/ALM-13004.html +++ b/docs/mrs/umn/ALM-13004.html @@ -65,12 +65,12 @@

      Possible Causes

      The heap memory of the ZooKeeper instance is overused or the heap memory is inappropriately allocated.

      Procedure

      Check heap memory usage.

      -
      1. On the FusionInsight Manager portal, On the displayed interface, click the drop-down button of ZooKeeper Heap Memory Usage Exceeds the Threshold and confirm the node IP address of the host for which the alarm is generated in the Location Information.
      2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Instance, click quorumpeer in the Role column of the corresponding IP address. Click the drop-down menu in the upper right corner of Chart, choose Customize > CPU and Memory, and select ZooKeeper Heap And Direct Buffer Resource Percentage, click OK. Check the heap memory usage.
      3. Check whether the used heap memory of ZooKeeper reaches 95% of the maximum heap memory specified for ZooKeeper.

        • If yes, go to 4.
        • If no, go to 7.
        -

      4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer > System. Increase the value of -Xmx in GC_OPTS as required. The details are as follows:

        1. On the Instance tab, click quorumpeer in the Role column of the corresponding IP address. Choose Customize > CPU and Memory in the upper right corner, and select ZooKeeper Heap And Direct Buffer Resource, click OK to check the heap memory used by ZooKeeper.
        2. Change the value of -Xmx in the GC_OPTS parameter based on the actual heap memory usage. Generally, the value is twice the size of the ZooKeeper data volume. For example, if 2 GB ZooKeeper heap memory is used, the following configurations are recommended: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=512M -XX:MetaspaceSize=64M -XX:MaxMetaspaceSize=64M -XX:CMSFullGCsBeforeCompaction=1
        +
        1. On the MRS Manager portal, On the displayed interface, click the drop-down button of ZooKeeper Heap Memory Usage Exceeds the Threshold and confirm the node IP address of the host for which the alarm is generated in the Location Information.
        2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Instance, click quorumpeer in the Role column of the corresponding IP address. Click the drop-down menu in the upper right corner of Chart, choose Customize > CPU and Memory, and select ZooKeeper Heap And Direct Buffer Resource Percentage, click OK. Check the heap memory usage.
        3. Check whether the used heap memory of ZooKeeper reaches 95% of the maximum heap memory specified for ZooKeeper.

          • If yes, go to 4.
          • If no, go to 7.
          +

        4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer > System. Increase the value of -Xmx in GC_OPTS as required. The details are as follows:

          1. On the Instance tab, click quorumpeer in the Role column of the corresponding IP address. Choose Customize > CPU and Memory in the upper right corner, and select ZooKeeper Heap And Direct Buffer Resource, click OK to check the heap memory used by ZooKeeper.
          2. Change the value of -Xmx in the GC_OPTS parameter based on the actual heap memory usage. Generally, the value is twice the size of the ZooKeeper data volume. For example, if 2 GB ZooKeeper heap memory is used, the following configurations are recommended: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=512M -XX:MetaspaceSize=64M -XX:MaxMetaspaceSize=64M -XX:CMSFullGCsBeforeCompaction=1

        5. Save the configuration and restart the ZooKeeper service.
        6. Check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 7.

        Collect fault information.

        -
        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
        2. Select ZooKeeper in the required cluster from the Service.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected logs.
        +
        1. On the MRS Manager portal, choose O&M > Log > Download.
        2. Select ZooKeeper in the required cluster from the Service.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        4. Contact the O&M personnel and send the collected logs.

      Alarm Clearing

      After the fault is rectified, the system automatically clears this alarm.

      diff --git a/docs/mrs/umn/ALM-13005.html b/docs/mrs/umn/ALM-13005.html index 6df02061..5f862a9a 100644 --- a/docs/mrs/umn/ALM-13005.html +++ b/docs/mrs/umn/ALM-13005.html @@ -60,7 +60,7 @@

      Possible Causes

      The quota for the alarm directory is inappropriate.

      Procedure

      Check whether the quota for the alarm directory is appropriate.

      -
      1. Log in to FusionInsight Manager, and choose Cluster > Name of the desired cluster > Services > ZooKeeper. On the displayed page, choose Configurations > All Configurations > Quota. Check whether the directory for which the alarm is reported and its quota exist in the customized.quota configuration item.

        • If yes, go to 5.
        • If no, go to 2.
        +
        1. Log in to MRS Manager, and choose Cluster > Name of the desired cluster > Services > ZooKeeper. On the displayed page, choose Configurations > All Configurations > Quota. Check whether the directory for which the alarm is reported and its quota exist in the customized.quota configuration item.

          • If yes, go to 5.
          • If no, go to 2.

        2. Check whether the alarm directory for which the alarm is reported is in the following alarm list.

          @@ -105,7 +105,7 @@

        3. View the component of the alarm directory in the table, open the corresponding service page, and choose Configurations > All Configurations. On the displayed page, search for zk.quota in the upper right corner. The search result is the quota of the alarm directory.
        4. Check whether the quota of the alarm directory for which the alarm is reported is appropriate. The quota must be greater than or equal to the actual value, which can be obtained in Trigger Condition.
        5. Modify the services.quota value as prompted and save the configuration.
        6. After the time specified by service.quotas.auto.check.cron.expression, check whether the alarm is cleared.

          • If it is, no further action is required.
          • If no, go to 7.

          7. Collect fault information.

          -
          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
          2. Select ZooKeeper in the required cluster from the Service.
          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
          4. Contact the O&M personnel and send the collected logs.
          +
          1. On the MRS Manager portal, choose O&M > Log > Download.
          2. Select ZooKeeper in the required cluster from the Service.
          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
          4. Contact the O&M personnel and send the collected logs.

          Alarm Clearing

          After the fault is rectified, the system automatically clears this alarm.

          diff --git a/docs/mrs/umn/ALM-13006.html b/docs/mrs/umn/ALM-13006.html index fc4a891f..52529477 100644 --- a/docs/mrs/umn/ALM-13006.html +++ b/docs/mrs/umn/ALM-13006.html @@ -59,11 +59,11 @@

          Possible Causes

          A large amount of data is written to the ZooKeeper data directory. The threshold is not appropriate.

          Procedure

          Check whether a large amount of data is written to the directory for which the alarm is generated.

          -
          1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of Znode Number or Capacity Exceeds the Threshold. Confirm the Znode for which the alarm is generated in Location Information.
          2. Log in to FusionInsight Manager, open the ZooKeeper service interface, and select Resource. In the table Used Resources (By Second-Level Znode), check whether a large amount of data is written to the top-level Znode for which the alarm is reported.

            • If it is, go to 3.
            • If it is not, go to 4.
            -

          3. Log in to the ZooKeeper client and delete the data in the top-level Znode.
          4. Log in to FusionInsight Manager and open the ZooKeeper service interface. On the Resource page, choose > By Znode quantity in Used Resources (By Second-Level Znode). Threshold Configuration of By Znode quantity is displayed. Click Modify under Operation. Increase the threshold by referringto the value of max.Znode.count by choosing Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > Quota.
          5. In the Used Resources (By Second-Level Znode), choose > By capacity. The Threshold Settings page of By Capacity is displayed. Click Modify under Operation. Increase the threshold by referring to the value of max.data.size by choosing Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > Quota.
          6. Check whether the alarm is cleared.

            • If it is, no further action is required.
            • If it is not, go to 7.
            +
            1. On MRS Manager, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of Znode Number or Capacity Exceeds the Threshold. Confirm the Znode for which the alarm is generated in Location Information.
            2. Log in to MRS Manager, open the ZooKeeper service interface, and select Resource. In the table Used Resources (By Second-Level Znode), check whether a large amount of data is written to the top-level Znode for which the alarm is reported.

              • If it is, go to 3.
              • If it is not, go to 4.
              +

            3. Log in to the ZooKeeper client and delete the data in the top-level Znode.
            4. Log in to MRS Manager and open the ZooKeeper service interface. On the Resource page, choose > By Znode quantity in Used Resources (By Second-Level Znode). Threshold Configuration of By Znode quantity is displayed. Click Modify under Operation. Increase the threshold by referringto the value of max.Znode.count by choosing Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > Quota.
            5. In the Used Resources (By Second-Level Znode), choose > By capacity. The Threshold Settings page of By Capacity is displayed. Click Modify under Operation. Increase the threshold by referring to the value of max.data.size by choosing Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > Quota.
            6. Check whether the alarm is cleared.

              • If it is, no further action is required.
              • If it is not, go to 7.

            Collect fault information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

          Alarm Clearing

          After the fault is rectified, the system automatically clears this alarm.

          diff --git a/docs/mrs/umn/ALM-13007.html b/docs/mrs/umn/ALM-13007.html index 2c10aa76..77804071 100644 --- a/docs/mrs/umn/ALM-13007.html +++ b/docs/mrs/umn/ALM-13007.html @@ -74,11 +74,11 @@

          Possible Causes

          A large number of client processes are connected to ZooKeeper. The thresholds are not appropriate.

          Procedure

          Check whether there are a large number of client processes connected to ZooKeeper.

          -
          1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of Available ZooKeeper Client Connections Are Insufficient. Confirm the node IP address of the host for which the alarm is generated in the Location Information.
          2. Open the ZooKeeper service interface, click Resource to enter the Resource page, and check whether the number of connections of the client with the IP address specified by Number of Connections (By Client IP Address) is large.

            • If it is, go to 3.
            • If it is not, go to 4.
            -

          3. Check whether connection leakage occurs on the client process.
          4. Click in the Number of Connections (by Client IP Address) to enter the Thresholds page, and click Modify under Operation. Increase the threshold by referring to the value of maxClientCnxns by choosing Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer.
          5. Check whether the alarm is cleared.

            • If it is, no further action is required.
            • If it is not, go to 6.
            +
            1. On MRS Manager, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of Available ZooKeeper Client Connections Are Insufficient. Confirm the node IP address of the host for which the alarm is generated in the Location Information.
            2. Open the ZooKeeper service interface, click Resource to enter the Resource page, and check whether the number of connections of the client with the IP address specified by Number of Connections (By Client IP Address) is large.

              • If it is, go to 3.
              • If it is not, go to 4.
              +

            3. Check whether connection leakage occurs on the client process.
            4. Click in the Number of Connections (by Client IP Address) to enter the Thresholds page, and click Modify under Operation. Increase the threshold by referring to the value of maxClientCnxns by choosing Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations > quorumpeer.
            5. Check whether the alarm is cleared.

              • If it is, no further action is required.
              • If it is not, go to 6.

            Collect fault information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

          Alarm Clearing

          After the fault is rectified, the system automatically clears this alarm.

          diff --git a/docs/mrs/umn/ALM-13008.html b/docs/mrs/umn/ALM-13008.html index 3cfb7667..f5dad602 100644 --- a/docs/mrs/umn/ALM-13008.html +++ b/docs/mrs/umn/ALM-13008.html @@ -64,11 +64,11 @@

          Possible Causes

          • A large amount of data is written to the ZooKeeper data directory.
          • The user-defined threshold is inappropriate.

          Procedure

          Check whether a large amount of data is written into the directory for which the alarm is generated.

          -
          1. Log in to FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper, and click Resource. Click By Znode quantity in Used Resources (By Second-Level Znode), and check whether a large amount of data is written to the top Znode.

            • If yes, go to 2.
            • If no, go to 4.
            -

          2. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, select Location from the drop-down list box next to ALM-13008 ZooKeeper Znode Quantity Usage Exceeds Threshold, and obtain the Znode path in ServiceDirectory.
          3. Log in to the ZooKeeper client as a cluster user and delete unnecessary data from the Znode corresponding to the alarm.
          4. Log in to FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations, and search for max.znode.count, which is the maximum number of ZooKeeper directories. The alarm threshold is 80% of this parameter. Increase the value of this parameter, click Save, and restart the service for the configuration to take effect.
          5. Check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 6.
            +
            1. Log in to MRS Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper, and click Resource. Click By Znode quantity in Used Resources (By Second-Level Znode), and check whether a large amount of data is written to the top Znode.

              • If yes, go to 2.
              • If no, go to 4.
              +

            2. Log in to MRS Manager, choose O&M > Alarm > Alarms, select Location from the drop-down list box next to ALM-13008 ZooKeeper Znode Quantity Usage Exceeds Threshold, and obtain the Znode path in ServiceDirectory.
            3. Log in to the ZooKeeper client as a cluster user and delete unnecessary data from the Znode corresponding to the alarm.
            4. Log in to MRS Manager, choose Cluster > Name of the desired cluster > Services > ZooKeeper > Configurations > All Configurations, and search for max.znode.count, which is the maximum number of ZooKeeper directories. The alarm threshold is 80% of this parameter. Increase the value of this parameter, click Save, and restart the service for the configuration to take effect.
            5. Check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 6.

            Collect fault information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

          Alarm Clearing

          After the fault is rectified, the system automatically clears this alarm.

          diff --git a/docs/mrs/umn/ALM-13009.html b/docs/mrs/umn/ALM-13009.html index e48c325c..2ddc425c 100644 --- a/docs/mrs/umn/ALM-13009.html +++ b/docs/mrs/umn/ALM-13009.html @@ -64,7 +64,7 @@

          Possible Causes

          • A large volume of data has been written to the ZooKeeper data directory.
          • The threshold is improperly defined.

          Procedure

          Check whether a large volume of data is written to the alarm directory.

          -
          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. Click the drop-down list in the row containing ALM-13009 ZooKeeper ZNode Capacity Usage Exceeds the Threshold, and find the ZNode for which the alarm is generated in the Location area.
          2. Choose Cluster > Services > ZooKeeper. On the page that is displayed, click the Resource tab. In the Used Resources (By Second-Level ZNode) area, click By capacity and check whether a large amount of data is written to the top-level ZNode directory.

            • If yes, record the directory to which a large amount of data is written and go to 3.
            • If no, go to 5.
            +
            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. Click the drop-down list in the row containing ALM-13009 ZooKeeper ZNode Capacity Usage Exceeds the Threshold, and find the ZNode for which the alarm is generated in the Location area.
            2. Choose Cluster > Services > ZooKeeper. On the page that is displayed, click the Resource tab. In the Used Resources (By Second-Level ZNode) area, click By capacity and check whether a large amount of data is written to the top-level ZNode directory.

              • If yes, record the directory to which a large amount of data is written and go to 3.
              • If no, go to 5.

            3. Check whether data in the directory can be deleted.

              Deleting data from ZooKeeper is a high-risk operation. Exercise caution when performing this operation.

              • If yes, go to 4.
              • If no, go to 5.
              @@ -74,10 +74,10 @@
            4. Run the following command to log in to the client tool:

              zkCli.sh -server <Service IP address of the node where any ZooKeeper instance resides>:<Client port>

            5. Run the following command to delete unnecessary data:

              delete Path of the file to be deleted

            -

          3. Log in to FusionInsight Manager and choose Cluster > Services > ZooKeeper. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, and search for max.data.size. The value of max.data.size is the maximum capacity quota of the ZooKeeper directory. The unit is byte. Search for the GC_OPTS configuration item and check the value of Xmx.
          4. Compare the values of max.data.size and Xmx*0.65. The threshold is the smaller value multiplied by 80%. You can change the values of max.data.size and Xmx*0.65 to increase the threshold.
          5. Check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 8.
            +

          6. Log in to MRS Manager and choose Cluster > Services > ZooKeeper. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, and search for max.data.size. The value of max.data.size is the maximum capacity quota of the ZooKeeper directory. The unit is byte. Search for the GC_OPTS configuration item and check the value of Xmx.
          7. Compare the values of max.data.size and Xmx*0.65. The threshold is the smaller value multiplied by 80%. You can change the values of max.data.size and Xmx*0.65 to increase the threshold.
          8. Check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 8.

          Collect the fault information.

          -
          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
          2. Expand the Service drop-down list, and select ZooKeeper for the target cluster.
          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
          4. Contact O&M personnel and provide the collected logs.
          +
          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
          2. Expand the Service drop-down list, and select ZooKeeper for the target cluster.
          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
          4. Contact O&M personnel and provide the collected logs.

          Alarm Clearing

          This alarm is automatically cleared after the fault is rectified.

          diff --git a/docs/mrs/umn/ALM-13010.html b/docs/mrs/umn/ALM-13010.html index 5fadf9f7..ef3e4ba3 100644 --- a/docs/mrs/umn/ALM-13010.html +++ b/docs/mrs/umn/ALM-13010.html @@ -64,13 +64,13 @@

          Possible Causes

          • A large amount of data is written to the ZooKeeper data directory.
          • The user-defined threshold is inappropriate.

          Procedure

          Check whether a large amount of data is written into the directory for which the alarm is generated.

          -
          1. On FusionInsight Manager, choose O&M > Alarm > Alarms. Confirm the Znode for which the alarm is generated in Location of this alarm.
          2. Choose Cluster > Name of the desired cluster > Services > ZooKeeper and click Resource. In Used Resources (By Second-Level Znode), check whether a large amount of data is written into the top Znode.

            • If yes, go to 3.
            • If no, go to 5.
            -

          3. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, select Location from the drop-down list box next to ALM-13010 Znode Usage of a Directory with Quota Configured Exceeds the Threshold, and obtain the Znode path in ServiceDirectory.
          4. Log in to the ZooKeeper client as a cluster user and delete unwanted data in the Znode for which the alarm is generated.
          5. Log in to FusionInsight Manager, and choose Cluster > Name of the desired cluster > Services > Component of the top Znode for which the alarm isgenerated. Choose Configurations > All Configurations, search for zk.quota.number, increase its value, click Save.

            If the Component of the top Znode for which the alarm isgenerated is ClickHouse, change the value of clickhouse.zookeeper.quota.node.count.

            +
            1. On MRS Manager, choose O&M > Alarm > Alarms. Confirm the Znode for which the alarm is generated in Location of this alarm.
            2. Choose Cluster > Name of the desired cluster > Services > ZooKeeper and click Resource. In Used Resources (By Second-Level Znode), check whether a large amount of data is written into the top Znode.

              • If yes, go to 3.
              • If no, go to 5.
              +

            3. Log in to MRS Manager, choose O&M > Alarm > Alarms, select Location from the drop-down list box next to ALM-13010 Znode Usage of a Directory with Quota Configured Exceeds the Threshold, and obtain the Znode path in ServiceDirectory.
            4. Log in to the ZooKeeper client as a cluster user and delete unwanted data in the Znode for which the alarm is generated.
            5. Log in to MRS Manager, and choose Cluster > Name of the desired cluster > Services > Component of the top Znode for which the alarm isgenerated. Choose Configurations > All Configurations, search for zk.quota.number, increase its value, click Save.

              If the Component of the top Znode for which the alarm isgenerated is ClickHouse, change the value of clickhouse.zookeeper.quota.node.count.

            6. Check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 7.

            Collect fault information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select ZooKeeper in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14000.html b/docs/mrs/umn/ALM-14000.html index 76b8dea1..b6319aa1 100644 --- a/docs/mrs/umn/ALM-14000.html +++ b/docs/mrs/umn/ALM-14000.html @@ -60,17 +60,17 @@

            Possible Causes

            • The ZooKeeper service is abnormal.
            • All NameService services are abnormal.

            Procedure

            Check the ZooKeeper service status.

            -
            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. On the Alarm page, check whether ALM-13000 ZooKeeper Service Unavailable is reported.

              • If yes, go to 2.
              • If no, go to 4.
              +
              1. On the MRS Manager portal, choose O&M > Alarm > Alarms. On the Alarm page, check whether ALM-13000 ZooKeeper Service Unavailable is reported.

                • If yes, go to 2.
                • If no, go to 4.

              2. See ALM-13000 ZooKeeper Service Unavailable to rectify the health status of ZooKeeper fault and check whether the Running Status of the ZooKeeper service restores to Normal.

                • If yes, go to 3.
                • If no, go to 7.

              3. On the O&M > Alarm > Alarms page, check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              Handle the NameService service exception alarm.

              -
              1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. On the Alarms page, check whether ALM-14010 NameService Service Unavailable is reported.

                • If yes, go to 5.
                • If no, go to 7.
                +
                1. On the MRS Manager portal, choose O&M > Alarm > Alarms. On the Alarms page, check whether ALM-14010 NameService Service Unavailable is reported.

                  • If yes, go to 5.
                  • If no, go to 7.

                2. See ALM-14010 NameService Service Unavailable to handle the abnormal NameService services and check whether each NameService service exception alarm is cleared.

                  • If yes, go to 6.
                  • If no, go to 7.

                3. On the O&M > Alarm > Alarms page, check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 7.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select the following nodes in the required cluster from the Service:

                  • ZooKeeper
                  • HDFS
                  +
                  1. On the MRS Manager portal, choose O&M > Log > Download.
                  2. Select the following nodes in the required cluster from the Service:

                    • ZooKeeper
                    • HDFS

                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14001.html b/docs/mrs/umn/ALM-14001.html index 6e3ed0d7..4c9246de 100644 --- a/docs/mrs/umn/ALM-14001.html +++ b/docs/mrs/umn/ALM-14001.html @@ -71,7 +71,7 @@

            Possible Causes

            The disk space configured for the HDFS cluster is insufficient.

            Procedure

            Check the disk capacity and delete unnecessary files.

            -
            1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
            2. Click the drop-down menu in the upper right corner of Chart, choose Customize > Disk, and select Percentage of HDFS Capacity to check whether the HDFS disk usage exceeds the threshold (80% by default).

              • If yes, go to 3.
              • If no, go to 11.
              +
              1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
              2. Click the drop-down menu in the upper right corner of Chart, choose Customize > Disk, and select Percentage of HDFS Capacity to check whether the HDFS disk usage exceeds the threshold (80% by default).

                • If yes, go to 3.
                • If no, go to 11.

              3. In the Basic Information area, click the NameNode(Active) of the failure NameService and the HDFS WebUI page is displayed.

                By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

              4. On the HDFS web user interface (WebUI), click Datanodes tab. In the Block pool used column, view the disk usage of all DataNodes to check whether the disk usage of any DataNode exceeds the threshold.

                • If yes, go to 6.
                • If no, go to 11.
                @@ -81,7 +81,7 @@
                1. Expand the disk capacity.
                2. Check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 11.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select the following nodes in the required cluster from the Service:

                  • ZooKeeper
                  • HDFS
                  +
                  1. On the MRS Manager portal, choose O&M > Log > Download.
                  2. Select the following nodes in the required cluster from the Service:

                    • ZooKeeper
                    • HDFS

                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14002.html b/docs/mrs/umn/ALM-14002.html index 9affcf15..a5e64af1 100644 --- a/docs/mrs/umn/ALM-14002.html +++ b/docs/mrs/umn/ALM-14002.html @@ -66,19 +66,19 @@

            Possible Causes

            • The disk space configured for the HDFS cluster is insufficient.
            • Data skew occurs among DataNodes.

            Procedure

            Check whether the cluster disk capacity is full.

            -
            1. On FusionInsight Manager, choose O&M > Alarm > Alarms, and check whether the ALM-14001 HDFS Disk Usage Exceeds the Threshold alarm exists.

              • If yes, go to 2.
              • If no, go to 4.
              +
              1. On MRS Manager, choose O&M > Alarm > Alarms, and check whether the ALM-14001 HDFS Disk Usage Exceeds the Threshold alarm exists.

                • If yes, go to 2.
                • If no, go to 4.

              2. Handle the alarm by following the instructions in ALM-14001 HDFS Disk Usage Exceeds the Threshold and check whether the alarm is cleared.

                • If yes, go to 3.
                • If no, go to 11.

              3. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              Check the balance status of DataNodes.

              -
              1. On FusionInsight Manager, choose Hosts. Check whether the number of DataNodes on each rack is almost the same. If the difference is large, adjust the racks to which DataNodes belong to ensure that the number of DataNodes on each rack is almost the same. Restart the HDFS service for the settings to take effect.
              2. Choose Cluster > Name of the desired cluster > Services > HDFS.
              3. In the Basic Information area, click NameNode(Active). The HDFS web UI is displayed.

                By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                +
                1. On MRS Manager, choose Hosts. Check whether the number of DataNodes on each rack is almost the same. If the difference is large, adjust the racks to which DataNodes belong to ensure that the number of DataNodes on each rack is almost the same. Restart the HDFS service for the settings to take effect.
                2. Choose Cluster > Name of the desired cluster > Services > HDFS.
                3. In the Basic Information area, click NameNode(Active). The HDFS web UI is displayed.

                  By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                4. In the Summary area of the HDFS web UI, check whether the value of Max is 10% greater than that of Median in DataNodes usages.

                  • If yes, go to 8.
                  • If no, go to 11.

                5. Balance skewed data in the cluster. Log in to the MRS client as user root. If the cluster is in normal mode, run the su - omm command to switch to user omm. Run the cd command to go to the client installation directory and run the source bigdata_env command. If the cluster uses the security mode, perform security authentication. Run kinit hdfs and enter the password as prompted. Obtain the password from the MRS cluster administrator.
                6. Run the following command to balance data distribution:

                  hdfs balancer -threshold 10

                7. Wait several minutes and check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 11.

                Collect the fault information.

                -
                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact O&M personnel and provide the collected logs.
                +
                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact O&M personnel and provide the collected logs.

                Alarm Clearing

                This alarm is automatically cleared after the fault is rectified.

                diff --git a/docs/mrs/umn/ALM-14003.html b/docs/mrs/umn/ALM-14003.html index e77b9c30..945941ae 100644 --- a/docs/mrs/umn/ALM-14003.html +++ b/docs/mrs/umn/ALM-14003.html @@ -71,12 +71,12 @@

                Possible Causes

                • The DataNode instance is abnormal.
                • Data is deleted.

                Procedure

                Check the DataNode instance.

                -
                1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HDFS > Instance.
                2. Check whether the Running Status of all DataNode instance is Normal.

                  • If yes, go to 11.
                  • If no, go to 3.
                  +
                  1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HDFS > Instance.
                  2. Check whether the Running Status of all DataNode instance is Normal.

                    • If yes, go to 11.
                    • If no, go to 3.

                  3. Restart the DataNode instance and check whether the DataNode instance restarts successfully.

                    • If yes, go to 4.
                    • If no, go to 5.

                  4. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                    • If yes, no further action is required.
                    • If no, go to 5.

                  Delete the damaged file.

                  -
                  1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HDFS > NameNode(Active). On the WebUI page of the HDFS, view the information about lost blocks.

                    • If a block is lost, a line in red is displayed on the WebUI.
                    • By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.
                    +
                    1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HDFS > NameNode(Active). On the WebUI page of the HDFS, view the information about lost blocks.

                      • If a block is lost, a line in red is displayed on the WebUI.
                      • By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                    2. The user checks whether the file containing the lost data block is useful.

                      Files generated in directories /mr-history, /tmp/hadoop-yarn, and /tmp/logs during MapReduce task execution are unnecessary.

                      @@ -94,7 +94,7 @@

                    3. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 11.

                    Collect the fault information.

                    -
                    1. On FusionInsight Manager, choose O&M > Log > Download.
                    2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact O&M personnel and provide the collected logs.
                    +
                    1. On MRS Manager, choose O&M > Log > Download.
                    2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact O&M personnel and provide the collected logs.

                    Alarm Clearing

                    This alarm is automatically cleared after the fault is rectified.

                    diff --git a/docs/mrs/umn/ALM-14006.html b/docs/mrs/umn/ALM-14006.html index edeccf0a..70bbe468 100644 --- a/docs/mrs/umn/ALM-14006.html +++ b/docs/mrs/umn/ALM-14006.html @@ -70,7 +70,7 @@

                    Possible Causes

                    The number of HDFS files exceeds the threshold.

                    Procedure

                    Check the number of files in the system.

                    -
                    1. On FusionInsight Manager, check the number of HDFS files. Specifically, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, choose Customize > File and Block, and select HDFS File and Total Blocks.
                    2. Choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations, and search for the GC_OPTS parameter under NameNode.
                    3. Configure the threshold of the number of configuration file objects. Specifically, change the value of Xmx (GB) in the GC_OPTS parameter. The threshold (specified by y) is calculated as follows: y = 0.2007 x Xmx - 0.6312, where x indicates the memory capacity Xmx (GB) and y indicates the number of files (unit: kW). Adjust the memory size as required.
                    4. Confirm that the value of GC_PROFILE is custom so that the GC_OPTS configuration takes effect. Click Save and choose More > Restart Instance to restart the service.
                    5. Check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 6.
                      +
                      1. On MRS Manager, check the number of HDFS files. Specifically, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, choose Customize > File and Block, and select HDFS File and Total Blocks.
                      2. Choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations, and search for the GC_OPTS parameter under NameNode.
                      3. Configure the threshold of the number of configuration file objects. Specifically, change the value of Xmx (GB) in the GC_OPTS parameter. The threshold (specified by y) is calculated as follows: y = 0.2007 x Xmx - 0.6312, where x indicates the memory capacity Xmx (GB) and y indicates the number of files (unit: kW). Adjust the memory size as required.
                      4. Confirm that the value of GC_PROFILE is custom so that the GC_OPTS configuration takes effect. Click Save and choose More > Restart Instance to restart the service.
                      5. Check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 6.

                      Check whether needless files exist in the system.

                      1. Log in to the HDFS client as user root. Run cd to switch to the client installation directory, and run source bigdata_env to configure the environment variables.

                        If the cluster uses the security mode, perform security authentication.

                        @@ -81,7 +81,7 @@
                        • If yes, no further action is required.
                        • If no, go to 9.

                      Collect the fault information.

                      -
                      1. On FusionInsight Manager, choose O&M > Log > Download.
                      2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact O&M personnel and provide the collected logs.
                      +
                      1. On MRS Manager, choose O&M > Log > Download.
                      2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact O&M personnel and provide the collected logs.

                    Alarm Clearing

                    This alarm is automatically cleared after the fault is rectified.

                    diff --git a/docs/mrs/umn/ALM-14007.html b/docs/mrs/umn/ALM-14007.html index 8e4fefc6..f15fdf94 100644 --- a/docs/mrs/umn/ALM-14007.html +++ b/docs/mrs/umn/ALM-14007.html @@ -71,9 +71,9 @@

                  2. Run the hdfs dfs -rm -r file or directory command to delete unnecessary files.
                  3. Check whether the alarm is cleared.

                    • If yes, no further action is required.
                    • If no, go to 4.

                  Check the NameNode JVM memory usage and configuration.

                  -
                  1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
                  2. In the Basic Information area, click NameNode(Active) to go to the HDFS WebUI.

                    By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                    +
                    1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
                    2. In the Basic Information area, click NameNode(Active) to go to the HDFS WebUI.

                      By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                      -

                    3. On the HDFS WebUI, click the Overview tab. In Summary, check the numbers of files, directories, and blocks in the HDFS.
                    4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS memory parameter of HDFS->NameNode.
                    +

                  3. On the HDFS WebUI, click the Overview tab. In Summary, check the numbers of files, directories, and blocks in the HDFS.
                  4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS memory parameter of HDFS->NameNode.

                  Adjust the configuration in the system.

                  1. Check whether the memory is configured properly based on the number of files in 6 and the NameNode Heap Memory parameters in 7.

                    • If yes, go to 9.
                    • If no, go to 11.

                    The recommended mapping between the number of HDFS file objects (filesystem objects = files + blocks) and the JVM parameters configured for NameNode is as follows:

                    @@ -82,7 +82,7 @@

                  2. Modify the heap memory parameters of the NameNode based on the mapping between the number of file objects and the memory. Click Save and choose Dashboard > More > Restart Service.
                  3. Check whether the alarm is cleared.

                    • If yes, no further action is required.
                    • If no, go to 11.

                  Collect fault information.

                  -
                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                  2. Select the following nodes in the required cluster from the Service:

                    • ZooKeeper
                    • HDFS
                    +
                    1. On the MRS Manager portal, choose O&M > Log > Download.
                    2. Select the following nodes in the required cluster from the Service:

                      • ZooKeeper
                      • HDFS

                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected logs.

                Alarm Clearing

                After the fault is rectified, the system automatically clears this alarm.

                diff --git a/docs/mrs/umn/ALM-14008.html b/docs/mrs/umn/ALM-14008.html index 2b13520a..84049086 100644 --- a/docs/mrs/umn/ALM-14008.html +++ b/docs/mrs/umn/ALM-14008.html @@ -71,9 +71,9 @@

              4. Run the hdfs dfs -rm -r file or directory command to delete unnecessary files.
              5. Check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              Check the DataNode JVM memory usage and configuration.

              -
              1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
              2. In the Basic Information area, click NameNode(Active) to go to the HDFS WebUI.

                By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                +
                1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
                2. In the Basic Information area, click NameNode(Active) to go to the HDFS WebUI.

                  By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                  -

                3. On the HDFS WebUI, click the DataNodes tab, and check the number of blocks of all DataNodes related to the alarm.
                4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS memory parameter of HDFS->DataNode.
                +

              3. On the HDFS WebUI, click the DataNodes tab, and check the number of blocks of all DataNodes related to the alarm.
              4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS memory parameter of HDFS->DataNode.

              Adjust the configuration in the system.

              1. Check whether the memory is configured properly based on the number of block in 6 and the DataNode Heap Memory parameters in 7.

                • If yes, go to 9.
                • If no, go to 11.

                The mapping between the average number of blocks of a DataNode instance and the DataNode memory is as follows:

                @@ -82,7 +82,7 @@

              2. Modify the heap memory parameters of the DataNode based on the mapping between the number of blocks and the memory. Click Save and choose Dashboard > More > Restart Service.
              3. Check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 11.

              Collect fault information.

              -
              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
              2. Select HDFS in the required cluster from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.
              +
              1. On the MRS Manager portal, choose O&M > Log > Download.
              2. Select HDFS in the required cluster from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14009.html b/docs/mrs/umn/ALM-14009.html index dd1e28e4..41e2520a 100644 --- a/docs/mrs/umn/ALM-14009.html +++ b/docs/mrs/umn/ALM-14009.html @@ -71,31 +71,31 @@

            Possible Causes

            • DataNodes are faulty or overloaded.
            • The network between the NameNode and the DataNode is disconnected or busy.
            • NameNodes are overloaded.
            • The NameNodes are not restarted after the DataNode is deleted.

            Procedure

            Check whether DataNodes are faulty.

            -
            1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. The HDFS Status page is displayed.
            2. In the Basic Information area, click NameNode(Active) to go to the HDFS WebUI.

              By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

              +
              1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. The HDFS Status page is displayed.
              2. In the Basic Information area, click NameNode(Active) to go to the HDFS WebUI.

                By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

              3. On the HDFS WebUI, click the Datanodes tab. In the In operation area, click Filter to check whether down is in the drop-down list.

                • If yes, select down, record the information about the filtered DataNodes, and go to 4.
                • If no, go to 8.
                -

              4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance to check whether recorded DataNodes exist in the instance list.

                • If all recorded DataNodes exist, go to 5.
                • If none of the recorded DataNodes exists, go to 6.
                • If some of the recorded DataNodes exist, go to 7.
                +

              5. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance to check whether recorded DataNodes exist in the instance list.

                • If all recorded DataNodes exist, go to 5.
                • If none of the recorded DataNodes exists, go to 6.
                • If some of the recorded DataNodes exist, go to 7.

              6. Locate the DataNode instance, click More > Restart Instance to restart it and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 8.

              7. Select all NameNode instances, choose More > Instance Rolling Restart to restart them and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 16.

              8. Select all NameNode instances, choose More > Instance Rolling Restart to restart them. Locate the DataNode instance, click More > Restart Instance to restart it and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 8.

              Check the status of the network between the NameNode and the DataNode.

              -
              1. Log in to the faulty DataNode on the management page as user root, and run the ping IP address of the NameNode command to check whether the network between the DataNode and the NameNode is abnormal.

                On the FusionInsight Manager page, choose Cluster > Name of the desired cluster > Services > HDFS > Instance. In the instance list, view the service plane IP address of the faulty DataNode.

                +
                1. Log in to the faulty DataNode on the management page as user root, and run the ping IP address of the NameNode command to check whether the network between the DataNode and the NameNode is abnormal.

                  On the MRS Manager page, choose Cluster > Name of the desired cluster > Services > HDFS > Instance. In the instance list, view the service plane IP address of the faulty DataNode.

                  • If yes, go to 9.
                  • If no, go to 10.

                2. Rectify the network fault, and check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 10.

                Check whether the DataNode is overloaded.

                -
                1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and check whether the alarm ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold exists.

                  • If yes, go to 11.
                  • If no, go to 13.
                  +
                  1. On the MRS Manager portal, choose O&M > Alarm > Alarms and check whether the alarm ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold exists.

                    • If yes, go to 11.
                    • If no, go to 13.

                  2. See ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold to handle the alarm and check whether the alarm is cleared.

                    • If yes, go to 12.
                    • If no, go to 13.

                  3. Check whether the alarm is cleared from the alarm list.

                    • If yes, no further action is required.
                    • If no, go to 13.

                  Check whether the NameNode is overloaded.

                  -
                  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and check whether the alarm ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold exists.

                    • If yes, go to 14.
                    • If no, go to 16.
                    +
                    1. On the MRS Manager portal, choose O&M > Alarm > Alarms and check whether the alarm ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold exists.

                      • If yes, go to 14.
                      • If no, go to 16.

                    2. See ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold to handle the alarm and check whether the alarm is cleared.

                      • If yes, go to 15.
                      • If no, go to 16.

                    3. Check whether the alarm is cleared from the alarm list.

                      • If yes, no further action is required.
                      • If no, go to 16.

                    Collect fault information.

                    -
                    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                    2. Select HDFS in the required cluster from the Service.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected logs.
                    +
                    1. On the MRS Manager portal, choose O&M > Log > Download.
                    2. Select HDFS in the required cluster from the Service.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-14010.html b/docs/mrs/umn/ALM-14010.html index b6da6063..906db84c 100644 --- a/docs/mrs/umn/ALM-14010.html +++ b/docs/mrs/umn/ALM-14010.html @@ -65,33 +65,33 @@

              Possible Causes

              • The KrbServer service is abnormal.
              • The JournalNode is faulty.
              • The DataNode is faulty.
              • The disk capacity is insufficient.
              • The NameNode enters safe mode.

              Procedure

              Check the KrbServer service status.

              -
              1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services.
              2. Check whether the KrbServer service exists.

                • If yes, go to 3.
                • If no, go to 6.
                +
                1. On MRS Manager, choose Cluster > Name of the desired cluster > Services.
                2. Check whether the KrbServer service exists.

                  • If yes, go to 3.
                  • If no, go to 6.

                3. Click KrbServer.
                4. Click Instances. On the KrbServer management page, select the faulty instance, and choose More > Restart Instance. Check whether the instance successfully restarts.

                  • If yes, go to 5.
                  • If no, go to 24.

                5. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 6.

                Check the JournalNode instance status.

                -
                1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services.
                2. Choose HDFS > Instances.
                3. Check whether the Running Status of the JournalNode is Normal.

                  • If yes, go to 11.
                  • If no, go to 9.
                  +
                  1. On MRS Manager, choose Cluster > Name of the desired cluster > Services.
                  2. Choose HDFS > Instances.
                  3. Check whether the Running Status of the JournalNode is Normal.

                    • If yes, go to 11.
                    • If no, go to 9.

                  4. Select the faulty JournalNode, and choose More > Restart Instance. Check whether the JournalNode successfully restarts.

                    • If yes, go to 10.
                    • If no, go to 24.

                  5. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                    • If yes, no further action is required.
                    • If no, go to 11.

                  Check the DataNode instance status.

                  -
                  1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HDFS.
                  2. Click Instances and check whether Running Status of all DataNodes is Normal.

                    • If yes, go to 15.
                    • If no, go to 13.
                    +
                    1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HDFS.
                    2. Click Instances and check whether Running Status of all DataNodes is Normal.

                      • If yes, go to 15.
                      • If no, go to 13.

                    3. Click Instances. On the DataNode management page, select the faulty instance, and choose More > Restart Instance. Check whether the DataNode successfully restarts.

                      • If yes, go to 14.
                      • If no, go to 15.

                    4. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 15.

                    Check disk status.

                    -
                    1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Host.
                    2. In the Disk column, check whether the disk space is insufficient.

                      • If yes, go to 17.
                      • If no, go to 19.
                      +
                      1. On MRS Manager, choose Cluster > Name of the desired cluster > Host.
                      2. In the Disk column, check whether the disk space is insufficient.

                        • If yes, go to 17.
                        • If no, go to 19.

                      3. Expand the disk capacity.
                      4. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 19.

                      Check whether NameNode is in the safe mode.

                      -
                      1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HDFS. Click NameNode(Active) of the abnormal NameService. The NameNode web UI is displayed.

                        By default, the admin user does not have the management rights of other components. If the page cannot be opened or the content is not completely displayed due to insufficient permission when you access the native page of a component, you can manually create a user with the management rights of the corresponding component to log in to the component.

                        +
                        1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HDFS. Click NameNode(Active) of the abnormal NameService. The NameNode web UI is displayed.

                          By default, the admin user does not have the management rights of other components. If the page cannot be opened or the content is not completely displayed due to insufficient permission when you access the native page of a component, you can manually create a user with the management rights of the corresponding component to log in to the component.

                        2. On the NameNode web UI, check whether "Safe mode is ON." is displayed.

                          Information behind Safe mode is ON is alarm information and is displayed based actual conditions.

                          • If yes, go to 21.
                          • If no, go to 24.

                        3. Log in to the client as user root. Run the cd command to go to the client installation directory and run the source bigdata_env command. If the cluster uses the security mode, perform security authentication. Run the kinit hdfs command and enter the password as prompted. The password can be obtained from the MRS cluster administrator. If the cluster uses the non-security mode, log in as user omm and run the command. Ensure that user omm has the client execution permission.
                        4. Run hdfs dfsadmin -safemode leave.
                        5. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 24.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. In the Service area, select the following nodes of the desired cluster.

                          • ZooKeeper
                          • HDFS
                          +
                          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                          2. In the Service area, select the following nodes of the desired cluster.

                            • ZooKeeper
                            • HDFS

                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact O&M personnel and provide the collected logs.

                        Alarm Clearing

                        This alarm is automatically cleared after the fault is rectified.

                        diff --git a/docs/mrs/umn/ALM-14011.html b/docs/mrs/umn/ALM-14011.html index 153fb431..11345a5f 100644 --- a/docs/mrs/umn/ALM-14011.html +++ b/docs/mrs/umn/ALM-14011.html @@ -61,7 +61,7 @@

                        Possible Causes

                        • The DataNode data directory fails to be created.
                        • The DataNode data directory uses the same disk with critical directories, such as / or /boot.
                        • Multiple directories in the DataNode data directory use the same disk.

                        Procedure

                        Check the alarm cause and information about the DataNode for which the alarm is generated.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
                        2. In HostName of Location, obtain the host name of the DataNode for which the alarm is generated.
                        +
                        1. On the MRS Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
                        2. In HostName of Location, obtain the host name of the DataNode for which the alarm is generated.

                        Delete directories that do not comply with the disk plan from the DataNode data directory.

                        1. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance. In the instance list, click the DataNode instance on the node for which the alarm is generated.
                        2. Click Instance Configurations and view the value of the DataNode parameter dfs.datanode.data.dir.
                        3. Check whether all DataNode data directories are consistent with the disk plan.

                          • If yes, go to 6.
                          • If no, go to 9.

                        4. Modify the DataNode parameter dfs.datanode.data.dir and delete the incorrect directories.
                        5. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance and restart the DataNode instance.
                        6. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 9.
                          @@ -70,7 +70,7 @@

                          Check whether the DataNode data directory fails to be created.

                          1. Run the su - omm command to switch to user omm.
                          2. Run the ls command to check whether the directories exist in the DataNode data directory.

                            • If yes, go to 26.
                            • If no, go to 12.

                          3. Run the mkdir data directory command to create the directory and check whether the directory can be successfully created.

                            • If yes, go to 24.
                            • If no, go to 13.
                            -

                          4. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms to check whether alarm ALM-12017 Insufficient Disk Capacity exists.

                            • If yes, go to 14.
                            • If no, go to 15.
                            +

                          5. On the MRS Manager portal, choose O&M > Alarm > Alarms to check whether alarm ALM-12017 Insufficient Disk Capacity exists.

                            • If yes, go to 14.
                            • If no, go to 15.

                          6. Adjust the disk capacity and check whether alarm ALM-12017 Insufficient Disk Capacity is cleared. For details, see ALM-12017 Insufficient Disk Capacity.

                            • If yes, go to 12.
                            • If no, go to 15.

                          7. Check whether user omm has the rwx or x permission of all the upper-layer directories of the directory. (For example, for /tmp/abc/, user omm has the x permission for directory tmp and the rwx permission for directory abc.)

                            • If yes, go to 24.
                            • If no, go to 16.

                          8. Run the chmod u+rwx path or chmod u+x path command as user root to assign the rwx or x permission of these directories to user omm. Then go to 12.
                          @@ -80,10 +80,10 @@

                          Check whether multiple directories in the DataNode data directory use the same disk.

                          1. Run the df command to obtain the disk mounting information of each directory in the DataNode data directory. Record the mounted directory in the command output.
                          2. Modify the DataNode node parameters dfs.datanode.data.dir to reserve only one directory among the directories that mounted to the same disk directory.
                          3. Go to 24.

                          Restart the DataNode and check whether the alarm is cleared.

                          -
                          1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance and restart the DataNode instance
                          2. Check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 26.
                            +
                            1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance and restart the DataNode instance
                            2. Check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 26.

                            Collect fault information.

                            -
                            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                            2. Select HDFS in the required cluster from the Service.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.
                            +
                            1. On the MRS Manager portal, choose O&M > Log > Download.
                            2. Select HDFS in the required cluster from the Service.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.

                        Alarm Clearing

                        After the fault is rectified, the system automatically clears this alarm.

                        diff --git a/docs/mrs/umn/ALM-14012.html b/docs/mrs/umn/ALM-14012.html index 7be9951e..e3e8be8b 100644 --- a/docs/mrs/umn/ALM-14012.html +++ b/docs/mrs/umn/ALM-14012.html @@ -65,7 +65,7 @@

                        Possible Causes

                        • The JournalNode instance does not exist (deleted or migrated).
                        • The JournalNode instance has not been started or has been stopped.
                        • The JournalNode instance is working incorrectly.
                        • The network of the JournalNode is unreachable.

                        Procedure

                        Check whether the JournalNode instance has been started up.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
                        2. Check Location and obtain the IP address of the JournalNode for which the alarm is generated.
                        3. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance. In the instance list, check whether the JournalNode instance exists on the node for which the alarm is generated.

                          • If yes, go to 5.
                          • If no, go to 4.
                          +
                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
                          2. Check Location and obtain the IP address of the JournalNode for which the alarm is generated.
                          3. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance. In the instance list, check whether the JournalNode instance exists on the node for which the alarm is generated.

                            • If yes, go to 5.
                            • If no, go to 4.

                          4. Choose O&M > Alarm > Alarms. In the alarm list, click Clear in the Operation column of the alarm. In the dialog box that is displayed, click OK. No further action is needed.
                          5. Click the JournalNode instance and check whether its Configuration Status is Synchronized.

                            • If yes, go to 8.
                            • If no, go to 6.

                          6. Select the JournalNode instance and choose Start Instance to start the instance.
                          7. After 5 minutes, check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 15.

                          @@ -74,12 +74,12 @@

                        4. Select the JournalNode instance and choose More > Restart Instance to start the instance.
                        5. After 5 minutes, check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 15.

                        Check whether the network of the JournalNode is reachable.

                        -
                        1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance to check the service IP address of the active NameNode.
                        2. Log in to the active NameNode as user root.
                        3. Run the ping command to check whether a timeout occurs or the network is unreachable between the active NameNode and the JournalNode.

                          ping service IP address of the JournalNode

                          +
                          1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance to check the service IP address of the active NameNode.
                          2. Log in to the active NameNode as user root.
                          3. Run the ping command to check whether a timeout occurs or the network is unreachable between the active NameNode and the JournalNode.

                            ping service IP address of the JournalNode

                            • If yes, go to 14.
                            • If no, go to 15.

                          4. Contact the network administrator to rectify the network fault and check whether the alarm is cleared 5 minutes later.

                            • If yes, no further action is required.
                            • If no, go to 15.

                          Collect fault information.

                          -
                          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                          2. Select HDFS in the required cluster from the Service.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected logs.
                          +
                          1. On the MRS Manager portal, choose O&M > Log > Download.
                          2. Select HDFS in the required cluster from the Service.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected logs.

                        Alarm Clearing

                        After the fault is rectified, the system automatically clears this alarm.

                        diff --git a/docs/mrs/umn/ALM-14013.html b/docs/mrs/umn/ALM-14013.html index 20ebe2b8..93e45fa1 100644 --- a/docs/mrs/umn/ALM-14013.html +++ b/docs/mrs/umn/ALM-14013.html @@ -66,7 +66,7 @@

                        Possible Causes

                        • The standby NameNode is stopped.
                        • The standby NameNode instance is working incorrectly.
                        • The standby NameNode fails to generate a new FsImage file.
                        • Space of the data directory on the standby NameNode is insufficient.
                        • The standby NameNode fails to push the FsImage file to the active NameNode.
                        • Space of the data directory on the active NameNode is insufficient.

                        Procedure

                        Check whether the standby NameNode is stopped.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
                        2. View Location and obtain the host name of the active NameNode for which the alarm is generated and name of the NameService where the active NameNode resides.
                        3. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance, find the standby NameNode instance of the NameService in the instance list, and check whether its Configuration Status is Synchronized.

                          • If yes, go to 6.
                          • If no, go to 4.
                          +
                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
                          2. View Location and obtain the host name of the active NameNode for which the alarm is generated and name of the NameService where the active NameNode resides.
                          3. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance, find the standby NameNode instance of the NameService in the instance list, and check whether its Configuration Status is Synchronized.

                            • If yes, go to 6.
                            • If no, go to 4.

                          4. Select the standby NameNode instance, choose Start Instance, and wait until the startup is complete.
                          5. Wait for a NameNode metadata combination period and check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 6.

                          Check whether the NameNode instance is working correctly.

                          @@ -74,7 +74,7 @@

                        4. Select the standby NameNode instance, choose More > Restart Instance, and wait until the startup is complete.
                        5. Wait for a NameNode metadata combination period and check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 30.

                        Check whether the standby NameNode fails to generate a new FsImage file.

                        -
                        1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations, and search and obtain the value of dfs.namenode.checkpoint.period. This value is the period of NameNode metadata combination.
                        2. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance and obtain the service IP addresses of the active and standby NameNodes of the NameService for which the alarm is generated.
                        3. Click the NameNode(xx,Standy) and Instance Configurations to obtain the value of dfs.namenode.name.dir. This value is the FsImage storage directory of the standby NameNode.
                        4. Log in to the standby NameNode as user root or omm.
                        5. Go to the FsImage storage directory and check the generation time of the newest FsImage file.

                          cd Storage directory of the standby NameNode/current

                          +
                          1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations, and search and obtain the value of dfs.namenode.checkpoint.period. This value is the period of NameNode metadata combination.
                          2. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance and obtain the service IP addresses of the active and standby NameNodes of the NameService for which the alarm is generated.
                          3. Click the NameNode(xx,Standy) and Instance Configurations to obtain the value of dfs.namenode.name.dir. This value is the FsImage storage directory of the standby NameNode.
                          4. Log in to the standby NameNode as user root or omm.
                          5. Go to the FsImage storage directory and check the generation time of the newest FsImage file.

                            cd Storage directory of the standby NameNode/current

                            stat -c %y $(ls -t | grep "fsimage_[0-9]*$" | head -1)

                          6. Run the date command to obtain the current system time.
                          7. Calculate the time difference between the generation time of the newest FsImage file and the current system time and check whether the time difference is greater than three times of the metadata combination period.

                            • If yes, go to 16.
                            • If no, go to 20.

                          8. The metadata combination function of the standby NameNode is faulty. Run the following command to check whether the fault is caused by insufficient storage space.

                            Go to the FsImage storage directory and check the size of the newest FsImage file (in MB).

                            @@ -92,14 +92,14 @@

                          9. When the standby NameNode fails to push data to the active NameNode as user omm, contact the system administrator to handle the fault. Wait for a NameNode metadata combination period and check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 24.

                          Check whether space on the data directory of the active NameNode is insufficient.

                          -
                          1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance, click the active NameNode of the NameService for which the alarm is generated, and then click Instance Configurations to obtain the value of dfs.namenode.name.dir. This value is the FsImage storage directory of the active NameNode.
                          2. Log in to the active NameNode as user root or omm.
                          3. Go to the FsImage storage directory and check the size of the newest FsImage file (in MB).

                            cd Storage directory of the active NameNode/current

                            +
                            1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance, click the active NameNode of the NameService for which the alarm is generated, and then click Instance Configurations to obtain the value of dfs.namenode.name.dir. This value is the FsImage storage directory of the active NameNode.
                            2. Log in to the active NameNode as user root or omm.
                            3. Go to the FsImage storage directory and check the size of the newest FsImage file (in MB).

                              cd Storage directory of the active NameNode/current

                              du -m $(ls -t | grep "fsimage_[0-9]*$" | head -1) | awk '{print $1}'

                            4. Run the following command to check the available disk space of the active NameNode (in MB).

                              df -m ./ | awk 'END{print $4}'

                            5. Compare the FsImage file size and the available disk space and determine whether another FsImage file can be stored on the disk.

                              • If yes, go to 30.
                              • If no, go to 29.

                            6. Clear the redundant files on the disk where the directory resides to reserve sufficient space for metadata. After the clearance, wait for a NameNode metadata combination period and check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 30.

                            Collect fault information.

                            -
                            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                            2. Select NameNode in the required cluster from the Service.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.
                            +
                            1. On the MRS Manager portal, choose O&M > Log > Download.
                            2. Select NameNode in the required cluster from the Service.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.

                        Alarm Clearing

                        After the fault is rectified, the system automatically clears this alarm.

                        diff --git a/docs/mrs/umn/ALM-14014.html b/docs/mrs/umn/ALM-14014.html index d4e366e7..32e9341d 100644 --- a/docs/mrs/umn/ALM-14014.html +++ b/docs/mrs/umn/ALM-14014.html @@ -65,14 +65,14 @@

                        Possible Causes

                        The heap memory of the NameNode instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                        Procedure

                        Check the GC duration.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ALM-14014 NameNode GC Time Exceeds the Threshold. Then check the role name in Location and confirm the IP adress of the instance.
                        2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance > NameNode (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection, and select NameNode Garbage Collection (GC) to check the GC duration statistics of the NameNode process collected every minute.
                        3. Check whether the GC duration of the NameNode process collected every minute exceeds the threshold (12 seconds by default).

                          • If yes, go to 4.
                          • If no, go to 7.
                          -

                        4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations > NameNode > System to increase the value of GC_OPTS parameter as required.

                          The recommended mapping between the number of HDFS file objects (filesystem objects = files + blocks) and the JVM parameters configured for NameNode is as follows:

                          +
                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ALM-14014 NameNode GC Time Exceeds the Threshold. Then check the role name in Location and confirm the IP adress of the instance.
                          2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance > NameNode (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection, and select NameNode Garbage Collection (GC) to check the GC duration statistics of the NameNode process collected every minute.
                          3. Check whether the GC duration of the NameNode process collected every minute exceeds the threshold (12 seconds by default).

                            • If yes, go to 4.
                            • If no, go to 7.
                            +

                          4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations > NameNode > System to increase the value of GC_OPTS parameter as required.

                            The recommended mapping between the number of HDFS file objects (filesystem objects = files + blocks) and the JVM parameters configured for NameNode is as follows:

                            • If the number of file objects reaches 10,000,000, you are advised to set the JVM parameters as follows: -Xms6G -Xmx6G -XX:NewSize=512M -XX:MaxNewSize=512M
                            • If the number of file objects reaches 20,000,000, you are advised to set the JVM parameters as follows: -Xms12G -Xmx12G -XX:NewSize=1G -XX:MaxNewSize=1G
                            • If the number of file objects reaches 50,000,000, you are advised to set the JVM parameters as follows: -Xms32G -Xmx32G -XX:NewSize=3G -XX:MaxNewSize=3G
                            • If the number of file objects reaches 100,000,000, you are advised to set the JVM parameters as follows: -Xms64G -Xmx64G -XX:NewSize=6G -XX:MaxNewSize=6G
                            • If the number of file objects reaches 200,000,000, you are advised to set the JVM parameters as follows: -Xms96G -Xmx96G -XX:NewSize=9G -XX:MaxNewSize=9G
                            • If the number of file objects reaches 300,000,000, you are advised to set the JVM parameters as follows: -Xms164G -Xmx164G -XX:NewSize=12G -XX:MaxNewSize=12G

                          5. Save the configuration and restart the NameNode instance.
                          6. Check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 7.

                          Collect fault information.

                          -
                          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                          2. Select NameNode in the required cluster from the Service.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected logs.
                          +
                          1. On the MRS Manager portal, choose O&M > Log > Download.
                          2. Select NameNode in the required cluster from the Service.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected logs.

                          Alarm Clearing

                          After the fault is rectified, the system automatically clears this alarm.

                          diff --git a/docs/mrs/umn/ALM-14015.html b/docs/mrs/umn/ALM-14015.html index eb3a147f..46453465 100644 --- a/docs/mrs/umn/ALM-14015.html +++ b/docs/mrs/umn/ALM-14015.html @@ -65,14 +65,14 @@

                          Possible Causes

                          The heap memory of the DataNode instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                          Procedure

                          Check the GC duration.

                          -
                          1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ALM-14015 DataNode GC Time Exceeds the Threshold. Then check the role name in Location and confirm the IP adress of the instance.
                          2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance > DataNode (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection, and select DataNode Garbage Collection (GC) to check the GC duration statistics of the DataNode process collected every minute.
                          3. Check whether the GC duration of the DataNode process collected every minute exceeds the threshold (12 seconds by default).

                            • If yes, go to 4.
                            • If no, go to 7.
                            -

                          4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations > DataNode > System to increase the value of GC_OPTS parameter as required.

                            The mapping between the average number of blocks of a DataNode instance and the DataNode memory is as follows:

                            +
                            1. On the MRS Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ALM-14015 DataNode GC Time Exceeds the Threshold. Then check the role name in Location and confirm the IP adress of the instance.
                            2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance > DataNode (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection, and select DataNode Garbage Collection (GC) to check the GC duration statistics of the DataNode process collected every minute.
                            3. Check whether the GC duration of the DataNode process collected every minute exceeds the threshold (12 seconds by default).

                              • If yes, go to 4.
                              • If no, go to 7.
                              +

                            4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations > DataNode > System to increase the value of GC_OPTS parameter as required.

                              The mapping between the average number of blocks of a DataNode instance and the DataNode memory is as follows:

                              • If the average number of blocks of a DataNode instance reaches 2,000,000, the reference values of the JVM parameters of the DataNode are as follows: -Xms6G -Xmx6G -XX:NewSize=512M -XX:MaxNewSize=512M
                              • If the average number of blocks of a DataNode instance reaches 5,000,000, the reference values of the JVM parameters of the DataNode are as follows: -Xms12G -Xmx12G -XX:NewSize=1G -XX:MaxNewSize=1G

                            5. Save the configuration and restart the DataNode instance.
                            6. Check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 7.

                            Collect fault information.

                            -
                            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                            2. Select DataNode in the required cluster from the Service.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.
                            +
                            1. On the MRS Manager portal, choose O&M > Log > Download.
                            2. Select DataNode in the required cluster from the Service.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.

                            Alarm Clearing

                            After the fault is rectified, the system automatically clears this alarm.

                            diff --git a/docs/mrs/umn/ALM-14016.html b/docs/mrs/umn/ALM-14016.html index 1b8bdbfb..b8c551ed 100644 --- a/docs/mrs/umn/ALM-14016.html +++ b/docs/mrs/umn/ALM-14016.html @@ -2,7 +2,7 @@

                            ALM-14016 DataNode Direct Memory Usage Exceeds the Threshold

                            Description

                            The system checks the direct memory usage of HDFS every 30 seconds. This alarm is generated when the direct memory usage of DataNode instances exceeds the threshold (90% of the maximum memory).

                            -

                            This alarm is automatically cleared when the direct memory usage is less than the threshold.

                            +

                            This alarm is automatically cleared when the direct memory usage is less than the threshold.

                            Attribute

          Table 1 Component alarm directory

          Component

          Alarm ID

          @@ -65,8 +65,8 @@

          Possible Causes

          The direct memory of DataNode instances is overused or the direct memory is inappropriately allocated.

          Procedure

          Check the direct memory usage.

          -
          1. On the Home page of FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click the drop-down list in the row containing ALM-14016 DataNode Direct Memory Usage Exceeds the Threshold, and view the role name and IP address of the instance for which the alarm is generated in the Location area.
          2. On the Home page of FusionInsight Manager, choose Cluster > Services > HDFS. On the page that is displayed, click the Instance tab. In the instance list, select DataNode (IP address of the instance for which this alarm is generated). Click the drop-down list in the upper right corner of the chart, choose Customize > Resource, and select DataNode Memory to check the direct memory usage.
          3. Check whether the used direct memory of a DataNode instance reaches 90% (default threshold) of the maximum direct memory allocated to it.

            • If yes, go to 4.
            • If no, go to 8.
            -

          4. On the Home page of FusionInsight Manager, choose Cluster > Services > HDFS. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, and select DataNode > System. Check whether -XX:MaxDirectMemorySize exists in the GC_OPTS parameter.

            • If yes, go to 5.
            • If no, go to 6.
            +
            1. On the Home page of MRS Manager, choose O&M > Alarm > Alarms. On the page that is displayed, click the drop-down list in the row containing ALM-14016 DataNode Direct Memory Usage Exceeds the Threshold, and view the role name and IP address of the instance for which the alarm is generated in the Location area.
            2. On the Home page of MRS Manager, choose Cluster > Services > HDFS. On the page that is displayed, click the Instance tab. In the instance list, select DataNode (IP address of the instance for which this alarm is generated). Click the drop-down list in the upper right corner of the chart, choose Customize > Resource, and select DataNode Memory to check the direct memory usage.
            3. Check whether the used direct memory of a DataNode instance reaches 90% (default threshold) of the maximum direct memory allocated to it.

              • If yes, go to 4.
              • If no, go to 8.
              +

            4. On the Home page of MRS Manager, choose Cluster > Services > HDFS. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, and select DataNode > System. Check whether -XX:MaxDirectMemorySize exists in the GC_OPTS parameter.

              • If yes, go to 5.
              • If no, go to 6.

            5. Adjust the value of -XX:MaxDirectMemorySize.

              1. In GC_OPTS, check the value of -Xmx and check whether the node memory is sufficient.

                You can determine whether the node memory is sufficient based on the actual environment. For example, you can use the following method:

                Use the IP address to log in to the instance for which the alarm is generated as user root and run the free -g command to check the value of Mem in the free column. The value indicates the available memory of the node. In the following example, the available memory of the node is 4 GB.
                              total        used        free      shared  buff/cache   available
 Mem:            112          48           4          10          58          46
@@ -80,7 +80,7 @@ Mem:            112          48
              2. Check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 8.

              Collect the fault information.

              -
              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the Service drop-down list, and select DataNode for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.
              +
              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the Service drop-down list, and select DataNode for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.

          Alarm Clearing

          This alarm is automatically cleared after the fault is rectified.

          diff --git a/docs/mrs/umn/ALM-14017.html b/docs/mrs/umn/ALM-14017.html index c709e773..02e45af6 100644 --- a/docs/mrs/umn/ALM-14017.html +++ b/docs/mrs/umn/ALM-14017.html @@ -65,13 +65,13 @@

          Possible Causes

          The direct memory of the NameNode instance is overused or the direct memory is inappropriately allocated.

          Procedure

          Check the direct memory usage.

          -
          1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ALM-14017 NameNode Direct Memory Usage Exceeds the Threshold. Then check the role name in Location and confirm the IP adress of the instance.
          2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance > NameNode (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource, and select NameNode Memory to check the direct memory usage.
          3. Check whether the used direct memory of NameNode reaches 90% of the maximum direct memory specified for NameNode by default.

            • If yes, go to 4.
            • If no, go to 8.
            -

          4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations > NameNode > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

            • If yes, go to 5.
            • If no, go to 6.
            +
            1. On the MRS Manager portal, choose O&M > Alarm > Alarms. On the displayed interface, click the drop-down button of ALM-14017 NameNode Direct Memory Usage Exceeds the Threshold. Then check the role name in Location and confirm the IP adress of the instance.
            2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance > NameNode (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource, and select NameNode Memory to check the direct memory usage.
            3. Check whether the used direct memory of NameNode reaches 90% of the maximum direct memory specified for NameNode by default.

              • If yes, go to 4.
              • If no, go to 8.
              +

            4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations > NameNode > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

              • If yes, go to 5.
              • If no, go to 6.

            5. In the GC_OPTS parameter, delete "-XX:MaxDirectMemorySize". Save the configuration and restart the NameNode instance.
            6. Check whether the ALM-14007 NameNode Heap Memory Usage Exceeds the Threshold exists.

              • If yes, handle the alarm by referring to ALM-14007 NameNode Heap Memory Usage Exceeds the Threshold.
              • If no, go to 7.

            7. Check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 8.

            Collect fault information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
            2. Select NameNode in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select NameNode in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

          Alarm Clearing

          After the fault is rectified, the system automatically clears this alarm.

          diff --git a/docs/mrs/umn/ALM-14018.html b/docs/mrs/umn/ALM-14018.html index 1d9372f0..6afa2fa3 100644 --- a/docs/mrs/umn/ALM-14018.html +++ b/docs/mrs/umn/ALM-14018.html @@ -71,9 +71,9 @@

        7. Run the hdfs dfs -rm -r file or directory path command to delete unnecessary files.
        8. Check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 4.

          9. Check the NameNode JVM non-heap memory usage and configuration.

          -
          1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. The HDFS status page is displayed.
          2. In the Basic Information area, click NameNode(Active). The HDFS WebUI is displayed.

            By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

            +
            1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. The HDFS status page is displayed.
            2. In the Basic Information area, click NameNode(Active). The HDFS WebUI is displayed.

              By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

              -

            3. On the HDFS WebUI, click the Overview tab. In Summary, check the numbers of files, directories, and blocks in HDFS.
            4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS non-heap memory parameter of HDFS->NameNode.
            +

          3. On the HDFS WebUI, click the Overview tab. In Summary, check the numbers of files, directories, and blocks in HDFS.
          4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS non-heap memory parameter of HDFS->NameNode.

          Adjust system configurations.

          1. Check whether the non-heap memory is properly configured based on the number of file objects in 6 and the non-heap parameters configured for NameNode in 7.

            • If yes, go to 9.
            • If no, go to 12.

            The recommended mapping between the number of HDFS file objects (filesystem objects = files + blocks) and the JVM parameters configured for NameNode is as follows:

            @@ -82,7 +82,7 @@

          2. Modify the GC_OPTS parameter of the NameNode based on the mapping between the number of file objects and non-heap memory.
          3. Save the configuration and click Dashboard > More > Restart Service.
          4. Check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 12.

          Collect fault information.

          -
          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
          2. Select the following services in the required cluster from the Service.

            • ZooKeeper
            • HDFS
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select the following services in the required cluster from the Service.

              • ZooKeeper
              • HDFS

            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14019.html b/docs/mrs/umn/ALM-14019.html index 278555a2..1303926d 100644 --- a/docs/mrs/umn/ALM-14019.html +++ b/docs/mrs/umn/ALM-14019.html @@ -71,9 +71,9 @@

          3. Run the hdfs dfs -rm -r file or directory path command to delete unnecessary files.
          4. Check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 4.

          Check the DataNode JVM non-heap memory usage and configuration.

          -
          1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
          2. In the Basic Information area, click NameNode(Active). The HDFS WebUI is displayed.

            By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

            +
            1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS.
            2. In the Basic Information area, click NameNode(Active). The HDFS WebUI is displayed.

              By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

              -

            3. On the HDFS WebUI, click the Datanodes tab to view the number of blocks of all DataNodes that report alarms.
            4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS non-heap memory parameter of HDFS->DataNode.
            +

          3. On the HDFS WebUI, click the Datanodes tab to view the number of blocks of all DataNodes that report alarms.
          4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS non-heap memory parameter of HDFS->DataNode.

          Adjust system configurations.

          1. Check whether the memory is properly configured based on the number of blocks in 6 and the memory parameters configured for DataNode in 7.

            • If yes, go to 9.
            • If no, go to 12.

            The mapping between the average number of blocks of a DataNode instance and the DataNode memory is as follows:

            @@ -82,7 +82,7 @@

          2. Modify the GC_OPTS parameter of the DataNode based on the mapping between the number of blocks and memory.
          3. Save the configuration and click Dashboard > More > Restart Service.
          4. Check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 12.

          Collect fault information.

          -
          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
          2. Select the following services in the required cluster from the Service.

            • ZooKeeper
            • HDFS
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select the following services in the required cluster from the Service.

              • ZooKeeper
              • HDFS

            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14020.html b/docs/mrs/umn/ALM-14020.html index 120a298e..e21dc594 100644 --- a/docs/mrs/umn/ALM-14020.html +++ b/docs/mrs/umn/ALM-14020.html @@ -82,11 +82,11 @@

          3. Wait 1 hour and check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 5.

          Check whether the threshold is correctly configured.

          -
          1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. Search for the dfs.namenode.fs-limits.max-directory-items parameter and check whether the parameter value is appropriate.

            • If yes, go to 9.
            • If no, go to 6.
            +
            1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. Search for the dfs.namenode.fs-limits.max-directory-items parameter and check whether the parameter value is appropriate.

              • If yes, go to 9.
              • If no, go to 6.

            2. Increase the parameter value.
            3. Save the configuration and click Dashboard > More > Restart Service.
            4. Wait 1 hour and check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 9.

            Collect fault information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
            2. Select HDFS in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select HDFS in the required cluster from the Service.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14021.html b/docs/mrs/umn/ALM-14021.html index 84d6d735..c272f9a9 100644 --- a/docs/mrs/umn/ALM-14021.html +++ b/docs/mrs/umn/ALM-14021.html @@ -72,24 +72,24 @@
            • NameNode parameters are not configured properly, so NameNode cannot make full use of system performance.

            Procedure

            Obtain alarm information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
            2. Check the alarm. Obtain the host name of the NameNode node involved in this alarm from the HostName information of Location. Then obtain the name of the NameService node involved in this alarm from the NameServiceName information of Location.
            +
            1. On the MRS Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
            2. Check the alarm. Obtain the host name of the NameNode node involved in this alarm from the HostName information of Location. Then obtain the name of the NameService node involved in this alarm from the NameServiceName information of Location.

            Check whether the threshold is too small.

            1. Check the status of the services that depend on HDFS. Check whether the services run slowly or task execution times out.

              • If yes, go to 8.
              • If no, go to 4.
              -

            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, choose Customize > RPC, and select Average Time of Active NameNode RPC Processing and click OK.
            3. On the Average Time of Active NameNode RPC Processing monitoring page, obtain the value of the NameService node involved in this alarm.
            4. On the FusionInsight Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HDFS. Locate Average Time of Active NameNode RPC Processing and click the Modify in the Operation column of the default rule. The Modify Rule page is displayed. Change Threshold to 150% of the peak value within one day before and after the alarm is generated. Click OK to save the new threshold.
            5. Wait for 5 minutes and then check whether the alarm is automatically cleared.

              • If yes, no further action is required.
              • If no, go to 8.
              +

            6. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, choose Customize > RPC, and select Average Time of Active NameNode RPC Processing and click OK.
            7. On the Average Time of Active NameNode RPC Processing monitoring page, obtain the value of the NameService node involved in this alarm.
            8. On the MRS Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HDFS. Locate Average Time of Active NameNode RPC Processing and click the Modify in the Operation column of the default rule. The Modify Rule page is displayed. Change Threshold to 150% of the peak value within one day before and after the alarm is generated. Click OK to save the new threshold.
            9. Wait for 5 minutes and then check whether the alarm is automatically cleared.

              • If yes, no further action is required.
              • If no, go to 8.

            Check whether the CPU performance of the NameNode node is sufficient.

            -
            1. On the FusionInsight Manager portal, click O&M > Alarm >Alarms and check whether ALM-12016 CPU Usage Exceeds the Threshold is generated for the NameNode node.

              • If yes, go to 9.
              • If no, go to 11.
              +
              1. On the MRS Manager portal, click O&M > Alarm >Alarms and check whether ALM-12016 CPU Usage Exceeds the Threshold is generated for the NameNode node.

                • If yes, go to 9.
                • If no, go to 11.

              2. Handle ALM-12016 CPU Usage Exceeds the Threshold by taking recommended actions.
              3. Wait for 10 minutes and check whether alarm 14021 is automatically cleared.

                • If yes, no further action is required.
                • If no, go to 11.

              Check whether the memory of the NameNode node is too small.

              -
              1. On the FusionInsight Manager portal, click O&M > Alarm >Alarms and check whether ALM-14007 HDFS NameNode Heap Memory Usage Exceeds the Threshold is generated for the NameNode node.

                • If yes, go to 12.
                • If no, go to 14.
                +
                1. On the MRS Manager portal, click O&M > Alarm >Alarms and check whether ALM-14007 HDFS NameNode Heap Memory Usage Exceeds the Threshold is generated for the NameNode node.

                  • If yes, go to 12.
                  • If no, go to 14.

                2. Handle ALM-14007 HDFS NameNode Heap Memory Usage Exceeds the Threshold by taking recommended actions.
                3. Wait for 10 minutes and check whether alarm 14021 is automatically cleared.

                  • If yes, no further action is required.
                  • If no, go to 14.

                Check whether NameNode parameters are configured properly.

                -
                1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. Search for parameter dfs.namenode.handler.count and view its value. If the value is less than or equal to 128, change it to 128. If the value is greater than 128 but less than 192, change it to 192.
                2. Search for parameter ipc.server.read.threadpool.size and view its value. If the value is less than 5, change it to 5.
                3. Click Save and click OK.
                4. On the Instance page of HDFS, select the standby NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the standby NameNode is started up.
                5. On the Instance page of HDFS, select the active NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the active NameNode is started up.
                6. Wait for 1 hour and then check whether the alarm is automatically cleared.

                  • If yes, no further action is required.
                  • If no, go to 20.
                  +
                  1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. Search for parameter dfs.namenode.handler.count and view its value. If the value is less than or equal to 128, change it to 128. If the value is greater than 128 but less than 192, change it to 192.
                  2. Search for parameter ipc.server.read.threadpool.size and view its value. If the value is less than 5, change it to 5.
                  3. Click Save and click OK.
                  4. On the Instance page of HDFS, select the standby NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the standby NameNode is started up.
                  5. On the Instance page of HDFS, select the active NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the active NameNode is started up.
                  6. Wait for 1 hour and then check whether the alarm is automatically cleared.

                    • If yes, no further action is required.
                    • If no, go to 20.

                  Collect fault information.

                  -
                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                  2. Select the following node in the required cluster from the Service.

                    • HDFS
                    +
                    1. On the MRS Manager portal, choose O&M > Log > Download.
                    2. Select the following node in the required cluster from the Service.

                      • HDFS

                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14022.html b/docs/mrs/umn/ALM-14022.html index 0af9b05b..f5e81238 100644 --- a/docs/mrs/umn/ALM-14022.html +++ b/docs/mrs/umn/ALM-14022.html @@ -71,27 +71,27 @@

            Possible Causes

            • The CPU performance of NameNode nodes is insufficient and therefore NameNode nodes cannot process messages in a timely manner.
            • The configured NameNode memory is too small and frame freezing occurs on the JVM due to frequent full garbage collection.
            • NameNode parameters are not configured properly, so NameNode cannot make full use of system performance.
            • The volume of services that access HDFS is too large and therefore NameNode is overloaded.

            Procedure

            Obtain alarm information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
            2. Check the alarm. Obtain the alarm generation time from Generated. Obtain the host name of the NameNode node involved in this alarm from the HostName information of Location. Then obtain the name of the NameService node involved in this alarm from the NameServiceName information of Location.
            +
            1. On the MRS Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
            2. Check the alarm. Obtain the alarm generation time from Generated. Obtain the host name of the NameNode node involved in this alarm from the HostName information of Location. Then obtain the name of the NameService node involved in this alarm from the NameServiceName information of Location.

            Check whether the threshold is too small.

            1. Check the status of the services that depend on HDFS. Check whether the services run slowly or task execution times out.

              • If yes, go to 8.
              • If no, go to 4.
              -

            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, choose Customize > RPC, and select Average Time of Active NameNode RPC Queuing and click OK.
            3. On the Average Time of Active NameNode RPC Queuing monitoring page, obtain the value of the NameService node involved in this alarm.
            4. On the FusionInsight Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HDFS. Locate Average Time of Active NameNode RPC Queuing and click the Modify in the Operation column of the default rule. The Modify Rule page is displayed. Change Threshold to 150% of the monitored value. Click OK to save the new threshold.
            5. Wait for 1 minute and then check whether the alarm is automatically cleared.

              • If yes, no further action is required.
              • If no, go to 8.
              +

            6. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, choose Customize > RPC, and select Average Time of Active NameNode RPC Queuing and click OK.
            7. On the Average Time of Active NameNode RPC Queuing monitoring page, obtain the value of the NameService node involved in this alarm.
            8. On the MRS Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HDFS. Locate Average Time of Active NameNode RPC Queuing and click the Modify in the Operation column of the default rule. The Modify Rule page is displayed. Change Threshold to 150% of the monitored value. Click OK to save the new threshold.
            9. Wait for 1 minute and then check whether the alarm is automatically cleared.

              • If yes, no further action is required.
              • If no, go to 8.

              Check whether the CPU performance of the NameNode node is sufficient.

              -

            10. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and check whether ALM-12016 HDFS NameNode Memory Usage Exceeds the Threshold is generated.

              • If yes, go to 9.
              • If no, go to 11.
              +

            11. On the MRS Manager portal, click O&M > Alarm > Alarms and check whether ALM-12016 HDFS NameNode Memory Usage Exceeds the Threshold is generated.

              • If yes, go to 9.
              • If no, go to 11.

            12. Handle ALM-12016 CPU Usage Exceeds the Threshold by taking recommended actions.
            13. Wait for 10 minutes and check whether alarm 14022 is automatically cleared.

              • If yes, no further action is required.
              • If no, go to 11.

            Check whether the memory of the NameNode node is too small.

            -
            1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and check whether ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold is generated.

              • If yes, go to 12.
              • If no, go to 14.
              +
              1. On the MRS Manager portal, click O&M > Alarm > Alarms and check whether ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold is generated.

                • If yes, go to 12.
                • If no, go to 14.

              2. Handle ALM-14007 CPU Usage Exceeds the Threshold by taking recommended actions.
              3. Wait for 10 minutes and check whether alarm 14022 is automatically cleared.

                • If yes, no further action is required.
                • If no, go to 14.

              Check whether NameNode parameters are configured properly.

              -
              1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. Search for parameter dfs.namenode.handler.count and view its value. If the value is less than or equal to 128, change it to 128. If the value is greater than 128 but less than 192, change it to 192.
              2. Search for parameter ipc.server.read.threadpool.size and view its value. If the value is less than 5, change it to 5.
              3. Click Save, and click OK.
              4. On the Instance page of HDFS, select the standby NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the standby NameNode is started up.
              5. On the Instance page of HDFS, select the active NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the active NameNode is started up.
              6. Wait for 1 hour and then check whether the alarm is automatically cleared.

                • If yes, no further action is required.
                • If no, go to 20.
                +
                1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Configurations > All Configurations. Search for parameter dfs.namenode.handler.count and view its value. If the value is less than or equal to 128, change it to 128. If the value is greater than 128 but less than 192, change it to 192.
                2. Search for parameter ipc.server.read.threadpool.size and view its value. If the value is less than 5, change it to 5.
                3. Click Save, and click OK.
                4. On the Instance page of HDFS, select the standby NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the standby NameNode is started up.
                5. On the Instance page of HDFS, select the active NameNode of NameService involved in this alarm and choose More > Restart Instance. Enter the password and click OK. Wait until the active NameNode is started up.
                6. Wait for 1 hour and then check whether the alarm is automatically cleared.

                  • If yes, no further action is required.
                  • If no, go to 20.

                Check whether the HDFS workload changes and reduce the workload properly.

                -
                1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, click Customize, select Average Time of Active NameNode RPC Queuing and click OK.
                2. Click . The Details page is displayed.
                3. Set the monitoring data display period, from 5 days before the alarm generation time to the alarm generation time. Click OK.
                4. On the Average RPC Queuing Time monitoring page, check whether the point in time when the queuing time increases abruptly exists.

                  • If yes, go to 24.
                  • If no, go to 27.
                  +
                  1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Click the drop-down menu in the upper right corner of Chart, click Customize, select Average Time of Active NameNode RPC Queuing and click OK.
                  2. Click . The Details page is displayed.
                  3. Set the monitoring data display period, from 5 days before the alarm generation time to the alarm generation time. Click OK.
                  4. On the Average RPC Queuing Time monitoring page, check whether the point in time when the queuing time increases abruptly exists.

                    • If yes, go to 24.
                    • If no, go to 27.

                  5. Confirm and check the point in time. Check whether a new task frequently accesses HDFS and whether the access frequency can be reduced.
                  6. If a Balancer task starts at the point in time, stop the task or specify a node for the task to reduce the HDFS workload.
                  7. Wait for 1 hour and then check whether the alarm is automatically cleared.

                    • If yes, no further action is required.
                    • If no, go to 27.

                  Collect fault information.

                  -
                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                  2. Select HDFS in the required cluster from the Service.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.
                  +
                  1. On the MRS Manager portal, choose O&M > Log > Download.
                  2. Select HDFS in the required cluster from the Service.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14023.html b/docs/mrs/umn/ALM-14023.html index c222e393..a34d12b3 100644 --- a/docs/mrs/umn/ALM-14023.html +++ b/docs/mrs/umn/ALM-14023.html @@ -65,11 +65,11 @@

            Possible Causes

            • The alarm threshold is improperly configured.
            • The disk space configured for the HDFS cluster is insufficient.
            • The volume of services that access HDFS is too large and therefore DataNode is overloaded.

            Procedure

            Check whether the alarm threshold is appropriate.

            -
            1. On the FusionInsight Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HDFS > Disk > Percentage of Reserved Space for Replicas of Unused Space to check whether the alarm threshold is appropriate. (The default threshold is 90%. Users can change it as required.)

              • If yes, go to 4.
              • If no, go to 2.
              +
              1. On the MRS Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HDFS > Disk > Percentage of Reserved Space for Replicas of Unused Space to check whether the alarm threshold is appropriate. (The default threshold is 90%. Users can change it as required.)

                • If yes, go to 4.
                • If no, go to 2.

              2. Choose O&M > Alarm > Thresholds > Name of the desired cluster > HDFS > Disk > Percentage of Reserved Space for Replicas of Unused Space and Click Modify, change the threshold based on the actual usage.
              3. Wait 5 minutes and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              Check whether an alarm indicating insufficient disk space is generated.

              -
              1. On the FusionInsight Manager portal, check whether ALM-14001 HDFS Disk Usage Exceeds the Threshold or ALM-14002 DataNode Disk Usage Exceeds the Threshold exists on the O&M > Alarm > Alarms page.

                • If yes, go to 5.
                • If no, go to 7.
                +
                1. On the MRS Manager portal, check whether ALM-14001 HDFS Disk Usage Exceeds the Threshold or ALM-14002 DataNode Disk Usage Exceeds the Threshold exists on the O&M > Alarm > Alarms page.

                  • If yes, go to 5.
                  • If no, go to 7.

                2. Handle the alarm by referring to instructions in ALM-14001 HDFS Disk Usage Exceeds the Threshold or ALM-14002 DataNode Disk Usage Exceeds the Threshold and check whether the alarm is cleared.

                  • If yes, go to 6.
                  • If no, go to 7.

                3. Wait 5 minutes and check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 7.

                @@ -77,7 +77,7 @@
                1. Expand the DataNode capacity.
                2. Wait 5 minutes and check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 9.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select HDFS in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.
                +
                1. On the MRS Manager portal, choose O&M > Log > Download.
                2. Select HDFS in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14024.html b/docs/mrs/umn/ALM-14024.html index 739dfc97..a3f6e5cf 100644 --- a/docs/mrs/umn/ALM-14024.html +++ b/docs/mrs/umn/ALM-14024.html @@ -75,15 +75,15 @@

            Possible Causes

            • The alarm threshold is improperly configured.
            • The space allocated to the tenant is improper.

            Procedure

            Check whether the alarm threshold is appropriate.

            -
            1. View the alarm location information to obtain the tenant name and tenant directory for which the alarm is generated.
            2. On the FusionInsight Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the storage space threshold configured for the tenant directory for which the alarm is generated is proper. (The default value 90% is a proper value. You can set it based on the site requirements.)

              • If yes, go to 5.
              • If no, go to 3.
              +
              1. View the alarm location information to obtain the tenant name and tenant directory for which the alarm is generated.
              2. On the MRS Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the storage space threshold configured for the tenant directory for which the alarm is generated is proper. (The default value 90% is a proper value. You can set it based on the site requirements.)

                • If yes, go to 5.
                • If no, go to 3.

              3. On the Resources page, click Modify to modify or delete the storage space threshold.
              4. About one minute later, check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 5.

              Check whether the space allocated to the tenant is appropriate.

              -
              1. On the FusionInsight Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the storage space quota of the tenant directory for which the alarm is generated is proper based on the actual service status of the tenant directory.

                • If yes, go to 8.
                • If no, go to 6.
                +
                1. On the MRS Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the storage space quota of the tenant directory for which the alarm is generated is proper based on the actual service status of the tenant directory.

                  • If yes, go to 8.
                  • If no, go to 6.

                2. On the Resources page, click Modify to modify the storage space quota.
                3. About one minute later, check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 8.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select HDFS in the required cluster and NodeAgent under Manager from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.
                +
                1. On the MRS Manager portal, choose O&M > Log > Download.
                2. Select HDFS in the required cluster and NodeAgent under Manager from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14025.html b/docs/mrs/umn/ALM-14025.html index 27875115..68b6bdf9 100644 --- a/docs/mrs/umn/ALM-14025.html +++ b/docs/mrs/umn/ALM-14025.html @@ -75,15 +75,15 @@

            Possible Causes

            • The alarm threshold is improperly configured.
            • The maximum number of file objects allocated to the tenant directory is inappropriate.

            Procedure

            Check whether the alarm threshold is appropriate.

            -
            1. View the alarm location information to obtain the tenant name and tenant directory for which the alarm is generated.
            2. On the FusionInsight Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the file object threshold configured for the tenant directory for which the alarm is generated is proper. (The default value 90% is a proper value. You can set it based on the site requirements.)

              • If yes, go to 5.
              • If no, go to 3.
              +
              1. View the alarm location information to obtain the tenant name and tenant directory for which the alarm is generated.
              2. On the MRS Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the file object threshold configured for the tenant directory for which the alarm is generated is proper. (The default value 90% is a proper value. You can set it based on the site requirements.)

                • If yes, go to 5.
                • If no, go to 3.

              3. On the Resources page, click Modify to modify or delete the file object threshold of the tenant directory for which the alarm is generated.
              4. About one minute later, check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 5.

              Check whether the maximum number of file objects allocated to the tenant is appropriate.

              -
              1. On the FusionInsight Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the maximum number of file objects configured for the tenant directory for which the alarm is generated is proper based on the actual service status of the tenant directory.

                • If yes, go to 8.
                • If no, go to 6.
                +
                1. On the MRS Manager portal, choose the Tenant Resources page, select the tenant for which the alarm is generated, and click Resources. Check whether the maximum number of file objects configured for the tenant directory for which the alarm is generated is proper based on the actual service status of the tenant directory.

                  • If yes, go to 8.
                  • If no, go to 6.

                2. On the Resources page, click Modify to modify or delete the maximum number of file objects configured for the tenant directory.
                3. About one minute later, check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 8.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select HDFS in the required cluster and NodeAgent under Manager from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.
                +
                1. On the MRS Manager portal, choose O&M > Log > Download.
                2. Select HDFS in the required cluster and NodeAgent under Manager from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-14026.html b/docs/mrs/umn/ALM-14026.html index a08d81ae..618a2a9e 100644 --- a/docs/mrs/umn/ALM-14026.html +++ b/docs/mrs/umn/ALM-14026.html @@ -66,25 +66,25 @@
            • Data skew occurs among DataNodes.
            • The disk space configured for the HDFS cluster is insufficient.

            Procedure

            Change the threshold.

            -
            1. On FusionInsight Manager, choose Cluster, click the name of the desired cluster, and choose HDFS. Then choose Configurations > All Configurations. On the displayed page, find the GC_OPTS parameter under HDFS->DataNode.
            2. Set the threshold of the DataNode blocks. Specifically, change the value of Xmx of the GC_OPTS parameter. Xmx specifies the memory, and each GB memory supports a maximum of 500,000 DataNode blocks. Set the memory as required. Confirm that GC_PROFILE is set to custom and save the configuration.
            3. Choose Cluster, click the name of the desired cluster, and choose HDFS > Instance. Select the DataNode instance whose status is Expired, click More, and select Restart Instance to make the GC_OPTS configuration take effect.
            4. Check whether the alarm is cleared 5 minutes later.

              • If yes, no further action is required.
              • If no, go to 5.
              +
              1. On MRS Manager, choose Cluster, click the name of the desired cluster, and choose HDFS. Then choose Configurations > All Configurations. On the displayed page, find the GC_OPTS parameter under HDFS->DataNode.
              2. Set the threshold of the DataNode blocks. Specifically, change the value of Xmx of the GC_OPTS parameter. Xmx specifies the memory, and each GB memory supports a maximum of 500,000 DataNode blocks. Set the memory as required. Confirm that GC_PROFILE is set to custom and save the configuration.
              3. Choose Cluster, click the name of the desired cluster, and choose HDFS > Instance. Select the DataNode instance whose status is Expired, click More, and select Restart Instance to make the GC_OPTS configuration take effect.
              4. Check whether the alarm is cleared 5 minutes later.

                • If yes, no further action is required.
                • If no, go to 5.

              Check whether associated alarms are reported.

              -
              1. On FusionInsight Manager, choose O&M > Alarm > Alarms, and check whether the ALM-14002 DataNode Disk Usage Exceeds the Threshold alarm exists.

                • If yes, go to 6.
                • If no, go to 8.
                +
                1. On MRS Manager, choose O&M > Alarm > Alarms, and check whether the ALM-14002 DataNode Disk Usage Exceeds the Threshold alarm exists.

                  • If yes, go to 6.
                  • If no, go to 8.

                2. Handle the alarm by following the instructions in ALM-14002 DataNode Disk Usage Exceeds the Threshold and check whether the alarm is cleared.

                  • If yes, go to 7.
                  • If no, go to 8.

                3. Check whether the alarm is cleared 5 minutes later.

                  • If yes, no further action is required.
                  • If no, go to 8.

                Expand the DataNode capacity.

                -
                1. Expand the DataNode capacity.
                2. On FusionInsight Manager, wait for 5 minutes and check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 10.
                  +
                  1. Expand the DataNode capacity.
                  2. On MRS Manager, wait for 5 minutes and check whether the alarm is cleared.

                    • If yes, no further action is required.
                    • If no, go to 10.

                  Collect the fault information.

                  -
                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                  2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact O&M personnel and provide the collected logs.
                  +
                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                  2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact O&M personnel and provide the collected logs.

            Alarm Clearing

            This alarm is automatically cleared after the fault is rectified.

            Related Information

            Configuration rules of the DataNode JVM parameter.

            -

            Default value of the DataNode JVM parameter GC_OPTS:

            +

            Default value of the DataNode JVM parameter GC_OPTS:

            -Xms2G -Xmx4G -XX:NewSize=128M -XX:MaxNewSize=256M -XX:MetaspaceSize=128M -XX:MaxMetaspaceSize=128M -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:CMSInitiatingOccupancyFraction=65 -XX:+PrintGCDetails -Dsun.rmi.dgc.client.gcInterval=0x7FFFFFFFFFFFFFE -Dsun.rmi.dgc.server.gcInterval=0x7FFFFFFFFFFFFFE -XX:-OmitStackTraceInFastThrow -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=1M -Djdk.tls.ephemeralDHKeySize=2048

            -

            The average number of blocks stored in each DataNode instance in the cluster is: Number of HDFS blocks x 3/Number of DataNodes. If the average number of blocks changes, you need to change -Xms2G -Xmx4G -XX:NewSize=128M -XX:MaxNewSize=256M in the default value. The following table lists the reference values.

            +

            The average number of blocks stored in each DataNode instance in the cluster is: Number of HDFS blocks x 3/Number of DataNodes. If the average number of blocks changes, you need to change -Xms2G -Xmx4G -XX:NewSize=128M -XX:MaxNewSize=256M in the default value. The following table lists the reference values.

            diff --git a/docs/mrs/umn/ALM-14027.html b/docs/mrs/umn/ALM-14027.html index af32ed36..d315521e 100644 --- a/docs/mrs/umn/ALM-14027.html +++ b/docs/mrs/umn/ALM-14027.html @@ -65,7 +65,7 @@

            Possible Causes

            • The hard disk is faulty.
            • The disk permissions are configured improperly.

            Procedure

            Check whether a disk alarm is generated.

            -
            1. On FusionInsight Manager, choose O&M > Alarm > Alarms and check whether ALM-12014 Partition Lost or ALM-12033 Slow Disk Fault exists.

              • If yes, go to 2.
              • If no, go to 4.
              +
              1. On MRS Manager, choose O&M > Alarm > Alarms and check whether ALM-12014 Partition Lost or ALM-12033 Slow Disk Fault exists.

                • If yes, go to 2.
                • If no, go to 4.

              2. Rectify the fault by referring to the handling procedure of ALM-12014 Partition Lost or ALM-12033 Slow Disk Fault. Then, check whether the alarm is cleared.

                • If yes, go to 3.
                • If no, go to 4.

              3. Wait 5 minutes and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              @@ -76,7 +76,7 @@

            2. In the alarm list on Manager, click Clear in the Operation column of the alarm to manually clear the alarm. Choose Cluster > Services > HDFS > Instance, select the DataNode, choose More > Restart Instance, wait for 5 minutes, and check whether a new alarm is reported.

              • If no, no further action is required.
              • If yes, go to 8.

            Collect the fault information.

            -
            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. Expand the Service drop-down list, and select HDFS and OMS for the target cluster.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.
            +
            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. Expand the Service drop-down list, and select HDFS and OMS for the target cluster.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 20 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.

            Alarm Clearing

            After the fault is rectified, the system does not automatically clear this alarm and you need to manually clear the alarm.

            diff --git a/docs/mrs/umn/ALM-14028.html b/docs/mrs/umn/ALM-14028.html index a819f294..1ef3a4d7 100644 --- a/docs/mrs/umn/ALM-14028.html +++ b/docs/mrs/umn/ALM-14028.html @@ -70,7 +70,7 @@

            Possible Causes

            • The DataNode instance is abnormal.
            • Data is deleted.
            • The number of replicas written into the file is greater than the number of DataNodes.
            -

            Procedure

            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, check whether alarm ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold is generated.

              • If yes, go to 2.
              • If no, go to 3.
              +

              Procedure

              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, check whether alarm ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold is generated.

                • If yes, go to 2.
                • If no, go to 3.

              2. Rectify the fault according to the handling procedure of ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold. Five minutes later, check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 3.

              1. Log in to the HDFS client as user root. The user password is defined by the user before the installation. Contact the MRS cluster administrator to obtain the password. Run the following commands:

                • Security mode:

                  cd Client installation directory

                  source bigdata_env

                  @@ -86,13 +86,13 @@

                • Check whether the percentage of N is greater than 50% (N/M > 50%).

                  • If yes, go to 8.
                  • If no, go to 9.

                • Run the following command to reconfigure the number of file replicas in the directory (set the number of file replicas to the number of DataNodes or the default number of file replicas):

                  hdfs dfs -setrep -w Number of file replicas/tmp/hadoop-yarn/staging/

                  To obtain the default number of file replicas:

                  -

                  Log in to FusionInsight Manager, choose Cluster > Services > HDFS > Configurations > All Configurations, and search for the dfs.replication parameter. The value of this parameter is the default number of file replicas.

                  +

                  Log in to MRS Manager, choose Cluster > Services > HDFS > Configurations > All Configurations, and search for the dfs.replication parameter. The value of this parameter is the default number of file replicas.

                  Check whether the alarm is cleared 5 minutes later.

                  • If yes, no further action is required.
                  • If no, go to 9.

              Collect the fault information.

              -
              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.
              +
              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.

              Alarm Clearing

              This alarm is automatically cleared after the fault is rectified.

              diff --git a/docs/mrs/umn/ALM-14029.html b/docs/mrs/umn/ALM-14029.html index dee09547..ad513c99 100644 --- a/docs/mrs/umn/ALM-14029.html +++ b/docs/mrs/umn/ALM-14029.html @@ -64,7 +64,7 @@

            Possible Causes

            • The DataNode is faulty.
            • The disk is faulty.
            • Files are written to a single replica.
            -

            Procedure

            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, check whether alarm ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold is generated.

              • If yes, go to 2.
              • If no, go to 3.
              +

              Procedure

              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, check whether alarm ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold is generated.

                • If yes, go to 2.
                • If no, go to 3.

              2. Rectify the fault according to the handling procedure of ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold. In the next detection period, check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 3.

              3. Check whether files of a single replica have been written into the service.

                • If yes, go to 4.
                • If no, go to 7.

              4. Log in to the HDFS client as user root. The user password is defined by the user before the installation. Contact the MRS cluster administrator to obtain the password. Run the following commands:

                • Security mode:

                  cd Client installation directory

                  @@ -78,7 +78,7 @@

                • In the next detection period, check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 7.

              Collect the fault information.

              -
              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.
              +
              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.

              Alarm Clearing

              This alarm is automatically cleared after the fault is rectified.

              diff --git a/docs/mrs/umn/ALM-14030.html b/docs/mrs/umn/ALM-14030.html index 00a07d1b..75ef10ba 100644 --- a/docs/mrs/umn/ALM-14030.html +++ b/docs/mrs/umn/ALM-14030.html @@ -54,10 +54,10 @@

            Possible Causes

            The HDFS configuration item dfs.single.replication.enable is set to true.

            -

            Procedure

            1. Log in to FusionInsight Manager and choose Cluster > Services > HDFS. On the page that is displayed, click the Configurations tab then the All Configurations sub-tab.
            2. Search for dfs.single.replication.enable in the search box, change the value of the configuration item to false, and click Save.
            3. Wait for about 10 minutes and check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 4.
              +

              Procedure

              1. Log in to MRS Manager and choose Cluster > Services > HDFS. On the page that is displayed, click the Configurations tab then the All Configurations sub-tab.
              2. Search for dfs.single.replication.enable in the search box, change the value of the configuration item to false, and click Save.
              3. Wait for about 10 minutes and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.
              +
              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
              2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HDFS for the target cluster.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact O&M personnel and provide the collected logs.

              Alarm Clearing

              This alarm is automatically cleared after the fault is rectified.

              diff --git a/docs/mrs/umn/ALM-16000.html b/docs/mrs/umn/ALM-16000.html index 4cade166..c2eb5512 100644 --- a/docs/mrs/umn/ALM-16000.html +++ b/docs/mrs/umn/ALM-16000.html @@ -66,10 +66,10 @@

              Possible Causes

              Too many clients are connected to HiveServer.

              Procedure

              Increase the maximum number of connections to Hive.

              -
              1. On the FusionInsight Manager portal, Choose Cluster > Name of the desired cluster > Services > Hive > Configurations >All Configurations.
              2. Search for hive.server.session.control.maxconnections and increase the value of this parameter. If the value of this parameter is A, the threshold is B, and the number of sessions connected to the HiveServer is C, adjust the value of this parameter according to A x B > C. To view the number of sessions connected to the HiveServer, check the value of Statistics for Sessions of the HiveServer on the Hive monitoring page.
              3. Check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 4.
                +
                1. On the MRS Manager portal, Choose Cluster > Name of the desired cluster > Services > Hive > Configurations >All Configurations.
                2. Search for hive.server.session.control.maxconnections and increase the value of this parameter. If the value of this parameter is A, the threshold is B, and the number of sessions connected to the HiveServer is C, adjust the value of this parameter according to A x B > C. To view the number of sessions connected to the HiveServer, check the value of Statistics for Sessions of the HiveServer on the Hive monitoring page.
                3. Check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 4.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select Hive in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.
                +
                1. On the MRS Manager portal, choose O&M > Log > Download.
                2. Select Hive in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-16001.html b/docs/mrs/umn/ALM-16001.html index 64d7a85e..4240f3cd 100644 --- a/docs/mrs/umn/ALM-16001.html +++ b/docs/mrs/umn/ALM-16001.html @@ -68,18 +68,18 @@

              Possible Causes

              • The upper limit of the HDFS capacity available for Hive is too small.
              • The HDFS space is insufficient.
              • Some data nodes break down.

              Procedure

              Expand the system configuration.

              -
              1. Analyze the cluster HDFS capacity usage and increase the upper limit of the HDFS capacity available for Hive.

                Log in to FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Hive > Configurations > All Configurations, find hive.metastore.warehouse.size.percent, and increase its value so that larger HDFS capacity will be available for Hive. Assume that the value of the configuration item is A, the total HDFS storage space is B, the threshold is C, and the HDFS space used by Hive is D. The adjustment policy is A x B x C > D. The total HDFS storage space can be viewed on the HDFS NameNode page. The HDFS space used by Hive can be viewed on the Hive monitoring page.

                +
                1. Analyze the cluster HDFS capacity usage and increase the upper limit of the HDFS capacity available for Hive.

                  Log in to MRS Manager, choose Cluster > Name of the desired cluster > Services > Hive > Configurations > All Configurations, find hive.metastore.warehouse.size.percent, and increase its value so that larger HDFS capacity will be available for Hive. Assume that the value of the configuration item is A, the total HDFS storage space is B, the threshold is C, and the HDFS space used by Hive is D. The adjustment policy is A x B x C > D. The total HDFS storage space can be viewed on the HDFS NameNode page. The HDFS space used by Hive can be viewed on the Hive monitoring page.

                2. Check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 3.

                Expand the system.

                1. Expand the system.
                2. Check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 5.

                Check whether the data node is normal.

                -
                1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms.
                2. Check whether "ALM-12006 Node Fault", "ALM-12007 Process Fault", or "ALM-14002 DataNode Disk Usage Exceeds the Threshold" exist.

                  • If yes, go to 7.
                  • If no, go to 9.
                  +
                  1. On the MRS Manager portal, click O&M > Alarm > Alarms.
                  2. Check whether "ALM-12006 Node Fault", "ALM-12007 Process Fault", or "ALM-14002 DataNode Disk Usage Exceeds the Threshold" exist.

                    • If yes, go to 7.
                    • If no, go to 9.

                  3. Clear the alarm by following the steps provided in "ALM-12006 Node Fault", "ALM-12007 Process Fault", and "ALM-14002 DataNode Disk Usage Exceeds the Threshold".
                  4. Check whether the alarm is cleared.
                  • If yes, no further action is required.
                  • If no, go to 9.

                  Collect fault information.

                  -
                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                  2. Select Hive in the required cluster from the Service.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.
                  +
                  1. On the MRS Manager portal, choose O&M > Log > Download.
                  2. Select Hive in the required cluster from the Service.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-16002.html b/docs/mrs/umn/ALM-16002.html index 276d8f88..b10ca632 100644 --- a/docs/mrs/umn/ALM-16002.html +++ b/docs/mrs/umn/ALM-16002.html @@ -66,23 +66,23 @@

              Possible Causes

              • A syntax error occurs in HQL statements.
              • The HBase service is abnormal when a Hive on HBase task is performed.
              • The Spark service is abnormal when a Hive on Spark task is performed.
              • The dependent basic services, such as HDFS, Yarn, and ZooKeeper, are abnormal.

              Procedure

              Check whether the HQL statements comply with syntax.

              -
              1. On the FusionInsight Manager page, choose O&M > Alarm to view the alarm details and obtain the node where the alarm is generated.
              2. Use the Hive client to log in to the HiveServer node where an alarm is reported. Query the HQL syntax provided by Apache, and check whether the HQL commands are correct.

                • If yes, go to 4.
                • If no, go to 3.
                +
                1. On the MRS Manager page, choose O&M > Alarm to view the alarm details and obtain the node where the alarm is generated.
                2. Use the Hive client to log in to the HiveServer node where an alarm is reported. Query the HQL syntax provided by Apache, and check whether the HQL commands are correct.

                  • If yes, go to 4.
                  • If no, go to 3.

                  To view the user who runs an incorrect statement, you can download the hiveserver audit log file of the HiveServer node where this alarm is generated. Start Data and End Data are 10 minutes before and after the alarm generation time respectively. Open the log file and search for the Result=FAIL keyword to filter the log information about the incorrect statement, and then view the user who runs the incorrect statement according to UserName in the log information.

                3. Enter the correct HQL statements, and check whether the command can be properly executed.

                  • If yes, go to 12.
                  • If no, go to 4.

                Check whether the HBase service is abnormal.

                1. Check whether an Hive on HBase task is performed with the user who runs the HQL command.

                  • If yes, go to 5.
                  • If no, go to 8.
                  -

                2. On the FusionInsight Manager page, click Cluster > Name of the desired cluster > Services, check whether the HBase service is normal in the service list.

                  • If yes, go to 8.
                  • If no, go to 6.
                  +

                3. On the MRS Manager page, click Cluster > Name of the desired cluster > Services, check whether the HBase service is normal in the service list.

                  • If yes, go to 8.
                  • If no, go to 6.

                4. Choose O&M > Alarm, check the related alarms displayed on the alarm page and clear them according to related alarm help.
                5. Enter the correct HQL statements, and check whether the command can be properly executed.

                  • If yes, go to 12.
                  • If no, go to 8.

                Check whether the HDFS, Yarn, and ZooKeeper are normal.

                -
                1. On the FusionInsight Manager portal, click Cluster > Name of the desired cluster > Services.
                2. In the service list, check whether the services, such as HDFS, Yarn, and ZooKeeper are normal.

                  • If yes, go to 12.
                  • If no, go to 10.
                  +
                  1. On the MRS Manager portal, click Cluster > Name of the desired cluster > Services.
                  2. In the service list, check whether the services, such as HDFS, Yarn, and ZooKeeper are normal.

                    • If yes, go to 12.
                    • If no, go to 10.

                  3. Check the related alarms displayed on the alarm page and clear them according to related alarm help.
                  4. Enter the correct HQL statements, and check whether the command can be properly executed.

                    • If yes, go to 12.
                    • If no, go to 13.

                  5. After 1 minute, check whether the alarm is cleared.

                    • If yes, no further action is required.
                    • If no, go to 13.

                  Collect fault information.

                  -
                  1. On the FusionInsight Manager home page, choose O&M > Log > Download.
                  2. Select the following nodes in the required cluster from the Service:

                    • MapReduce
                    • Hive
                    +
                    1. On the MRS Manager home page, choose O&M > Log > Download.
                    2. Select the following nodes in the required cluster from the Service:

                      • MapReduce
                      • Hive

                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-16003.html b/docs/mrs/umn/ALM-16003.html index 1663d62e..65a8f01d 100644 --- a/docs/mrs/umn/ALM-16003.html +++ b/docs/mrs/umn/ALM-16003.html @@ -65,14 +65,14 @@

            Procedure

            Check the number of tasks executed in the background thread pool of HiveServer.

            -
            1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive. On the displayed page, click HiveServer Instance and check values of Background Thread Count and Background Thread Usage.
            2. Check whether the number of background threads in the latest half an hour is excessively high. (By default, the queue number is 100, and the thread number is considered as high if it is 90 or larger.)

              • If it is, go to 3.
              • If it is not, go to 5.
              +
              1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive. On the displayed page, click HiveServer Instance and check values of Background Thread Count and Background Thread Usage.
              2. Check whether the number of background threads in the latest half an hour is excessively high. (By default, the queue number is 100, and the thread number is considered as high if it is 90 or larger.)

                • If it is, go to 3.
                • If it is not, go to 5.

              3. Adjust the number of tasks submitted to the background thread pool. (For example, cancel some time-consuming tasks with low performance.)
              4. Check whether the values of Background Thread Count and Background Thread Usage decrease.

                • If it is, go to 7.
                • If it is not, go to 5.

              Check the capacity of the HiveServer background thread pool.

              -
              1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive. On the displayed page, click HiveServer Instance and check values of Background Thread Count and Background Thread Usage.
              2. Increase the value of hive.server2.async.exec.threads in the ${BIGDATA_HOME}/FusionInsight_HD_8.1.0.1/1_23_HiveServer/etc/hive-site.xml file. For example, increase the value by 20%.
              3. Save the modification.
              4. Check whether the alarm is cleared.

                • If it is, no further action is required.
                • If it is not, go to 9.
                +
                1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive. On the displayed page, click HiveServer Instance and check values of Background Thread Count and Background Thread Usage.
                2. Increase the value of hive.server2.async.exec.threads in the ${BIGDATA_HOME}/FusionInsight_HD_8.1.0.1/1_23_HiveServer/etc/hive-site.xml file. For example, increase the value by 20%.
                3. Save the modification.
                4. Check whether the alarm is cleared.

                  • If it is, no further action is required.
                  • If it is not, go to 9.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select Hive in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.
                +
                1. On the MRS Manager portal, choose O&M > Log > Download.
                2. Select Hive in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-16004.html b/docs/mrs/umn/ALM-16004.html index 91824b35..4be579bf 100644 --- a/docs/mrs/umn/ALM-16004.html +++ b/docs/mrs/umn/ALM-16004.html @@ -61,34 +61,34 @@
          2. The network communication between the Hive and basic services is interrupted.

            3. Procedure

            Check the HiveServer/MetaStore process status.

            -
            1. On the FusionInsight Manager portal, click Cluster > Name of the desired cluster > Services > Hive > Instance. In the Hive instance list, check whether the HiveServer or MetaStore instances are in the Unknown state.

              • If yes, go to 2.
              • If no, go to 4.
              +
              1. On the MRS Manager portal, click Cluster > Name of the desired cluster > Services > Hive > Instance. In the Hive instance list, check whether the HiveServer or MetaStore instances are in the Unknown state.

                • If yes, go to 2.
                • If no, go to 4.

              2. In the Hive instance list, choose More > Restart Instance to restart the HiveServer/MetaStore process.
              3. In the alarm list, check whether Hive Service Unavailable is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              Check the ZooKeeper service status.

              -
              1. On the FusionInsight Manager, check whether the alarm list contains Process Fault.

                • If yes, go to 5.
                • If no, go to 8.
                +
                1. On the MRS Manager, check whether the alarm list contains Process Fault.

                  • If yes, go to 5.
                  • If no, go to 8.

                2. In the Process Fault, check whether ServiceName is ZooKeeper.

                  • If yes, go to 6.
                  • If no, go to 8.

                3. Rectify the fault by following the steps provided in "ALM-12007 Process Fault".
                4. In the alarm list, check whether Hive Service Unavailable is cleared.

                  • If yes, no further action is required.
                  • If no, go to 8.

                Check the HDFS service status.

                -
                1. On the FusionInsight Manager, check whether the alarm list contains HDFS Service Unavailable.

                  • If yes, go to 9.
                  • If no, go to 11.
                  +
                  1. On the MRS Manager, check whether the alarm list contains HDFS Service Unavailable.

                    • If yes, go to 9.
                    • If no, go to 11.

                  2. Rectify the fault by following the steps provided in "ALM-14000 HDFS Service Unavailable".
                  3. In the alarm list, check whether Hive Service Unavailable is cleared.

                    • If yes, no further action is required.
                    • If no, go to 11.

                  Check the Yarn service status.

                  -
                  1. In FusionInsight Manager alarm list, check whether Yarn Service Unavailable is generated.

                    • If yes, go to 12.
                    • If no, go to 14.
                    +
                    1. In MRS Manager alarm list, check whether Yarn Service Unavailable is generated.

                      • If yes, go to 12.
                      • If no, go to 14.

                    2. Rectify the fault. For details, see "ALM-18000 Yarn Service Unavailable".
                    3. In the alarm list, check whether Hive Service Unavailable is cleared.

                      • If yes, no further action is required.
                      • If no, go to 14.

                    Check the DBService service status.

                    -
                    1. In FusionInsight Manager alarm list, check whether DBService Service Unavailable is generated.

                      • If yes, go to 15.
                      • If no, go to 17.
                      +
                      1. In MRS Manager alarm list, check whether DBService Service Unavailable is generated.

                        • If yes, go to 15.
                        • If no, go to 17.

                      2. Rectify the fault. For details, see "ALM-27001 DBService Service Unavailable".
                      3. In the alarm list, check whether Hive Service Unavailable is cleared.

                        • If yes, no further action is required.
                        • If no, go to 17.

                      Check the network connection between the Hive and ZooKeeper, HDFS, Yarn, and DBService.

                      -
                      1. On the FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Hive.
                      2. Click Instance.

                        The HiveServer instance list is displayed.

                        +
                        1. On the MRS Manager, choose Cluster > Name of the desired cluster > Services > Hive.
                        2. Click Instance.

                          The HiveServer instance list is displayed.

                        3. Click Host Name in the row of HiveServer.

                          The active HiveServer host status page is displayed.

                        4. Record the IP address under Basic Information.
                        5. Use the IP address obtained in 20 to log in to the host where the active HiveServer runs as user omm.
                        1. Run the ping command to check whether communication between the host that runs the active HiveServer and the hosts that run the ZooKeeper, HDFS, Yarn, and DBService services is normal. (Obtain the IP addresses of the hosts that run the ZooKeeper, HDFS, Yarn, and DBService services in the same way as that for obtaining the IP address of the active HiveServer.)

                          • If yes, go to 25.
                          • If no, go to 23.

                        2. Contact the administrator to restore the network.
                        3. In the alarm list, check whether Hive Service Unavailable is cleared.

                          • If yes, no further action is required.
                          • If no, go to 25.

                        Collect fault information.

                        -
                        1. On the FusionInsight Manager, choose O&M > Log > Download.
                        2. Select the following nodes in the required cluster from the Service:

                          • ZooKeeper
                          • HDFS
                          • Yarn
                          • DBService
                          • Hive
                          +
                          1. On the MRS Manager, choose O&M > Log > Download.
                          2. Select the following nodes in the required cluster from the Service:

                            • ZooKeeper
                            • HDFS
                            • Yarn
                            • DBService
                            • Hive

                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-16005.html b/docs/mrs/umn/ALM-16005.html index 97204a36..4fc6ba5c 100644 --- a/docs/mrs/umn/ALM-16005.html +++ b/docs/mrs/umn/ALM-16005.html @@ -61,19 +61,19 @@

            Possible Causes

            The heap memory of the Hive instance on the node is overused or the heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

            Procedure

            Check heap memory usage.

            -
            1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16005. Then check the role name in Location and confirm the IP adress of the instance.

              • If the role for which the alarm is generated is HiveServer, go to 2.
              • If the role for which the alarm is generated is MetaStore, go to 3.
              -

            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select HiveServer Memory Usage Statistics and click OK, check whether the used heap memory of the HiveServer service reaches the threshold(default value: 95%) of the maximum heap memory specified for HiveServer.

              • If yes, go to 4.
              • If no, go to 7.
              -

            3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select MetaStore Memory Usage Statistics and click OK, check whether the used heap memory of the MetaStore service reaches the threshold(default value: 95%) of the maximum heap memory specified for MetaStore.

              • If yes, go to 4.
              • If no, go to 7.
              -

            4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -Xmx in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

              Suggestions for GC parameter settings for the HiveServer:
              • When the heap memory used by the HiveServer process reaches the threshold (default value: 95%) of the maximum heap memory set by the HiveServer process, change the value of -Xmx to twice the default value. For example, if -Xmx is set to 2GB by default, change the value of -Xmx to 4GB. You are advised to change the value of -Xms to set the ratio of -Xms and -Xmx to 1:2 to avoid performance problems when JVM dynamically. On the FusionInsight Manager home page, choose O&M> Alarm> Thresholds > Name of the desired cluster > Hive > CPU and Memory > HiveServer Heap Memory Usage Statistics (HiveServer) to view Threshold.
              +
              1. On the MRS Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16005. Then check the role name in Location and confirm the IP adress of the instance.

                • If the role for which the alarm is generated is HiveServer, go to 2.
                • If the role for which the alarm is generated is MetaStore, go to 3.
                +

              2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select HiveServer Memory Usage Statistics and click OK, check whether the used heap memory of the HiveServer service reaches the threshold(default value: 95%) of the maximum heap memory specified for HiveServer.

                • If yes, go to 4.
                • If no, go to 7.
                +

              3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select MetaStore Memory Usage Statistics and click OK, check whether the used heap memory of the MetaStore service reaches the threshold(default value: 95%) of the maximum heap memory specified for MetaStore.

                • If yes, go to 4.
                • If no, go to 7.
                +

              4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -Xmx in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

                Suggestions for GC parameter settings for the HiveServer:
                • When the heap memory used by the HiveServer process reaches the threshold (default value: 95%) of the maximum heap memory set by the HiveServer process, change the value of -Xmx to twice the default value. For example, if -Xmx is set to 2GB by default, change the value of -Xmx to 4GB. You are advised to change the value of -Xms to set the ratio of -Xms and -Xmx to 1:2 to avoid performance problems when JVM dynamically. On the MRS Manager home page, choose O&M> Alarm> Thresholds > Name of the desired cluster > Hive > CPU and Memory > HiveServer Heap Memory Usage Statistics (HiveServer) to view Threshold.
                -
                Suggestions for GC parameter settings for the MetaServer:
                • When the heap memory used by the MetaStore process reaches the threshold (default value: 95%) of the maximum heap memory set by the MetaStore process, change the value of -Xmx to twice the default value. For example, if -Xmx is set to 2GB by default, change the value of -Xmx to 4GB. On the FusionInsight Manager home page, choose O&M> Alarm> Thresholds > Name of the desired cluster > Hive > CPU and Memory > MetaStore Heap Memory Usage Statistics (MetaStore) to view Threshold.
                +
                Suggestions for GC parameter settings for the MetaServer:
                • When the heap memory used by the MetaStore process reaches the threshold (default value: 95%) of the maximum heap memory set by the MetaStore process, change the value of -Xmx to twice the default value. For example, if -Xmx is set to 2GB by default, change the value of -Xmx to 4GB. On the MRS Manager home page, choose O&M> Alarm> Thresholds > Name of the desired cluster > Hive > CPU and Memory > MetaStore Heap Memory Usage Statistics (MetaStore) to view Threshold.
                • You are advised to change the value of -Xms to set the ratio of -Xms and -Xmx to 1:2 to avoid performance problems when JVM dynamically.

              5. Click More > Restart Service to restart the service.
              6. Check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 7.

              Collect fault information.

              -
              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
              2. Select Hive in the required cluster from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.
              +
              1. On the MRS Manager portal, choose O&M > Log > Download.
              2. Select Hive in the required cluster from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-16006.html b/docs/mrs/umn/ALM-16006.html index 353179f9..ef9d71e7 100644 --- a/docs/mrs/umn/ALM-16006.html +++ b/docs/mrs/umn/ALM-16006.html @@ -66,10 +66,10 @@

              Possible Causes

              The direct memory of the Hive instance on the node is overused or the direct memory is inappropriately allocated. As a result, the usage exceeds the threshold.

              Procedure

              Check direct memory usage.

              -
              1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16006. Then check the role name in Location and confirm the IP adress of the instance.

                • If the role for which the alarm is generated is HiveServer, go to 2.
                • If the role for which the alarm is generated is MetaStore, go to 3.
                -

              2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select HiveServer Memory Usage Statistics and click OK, check whether the used direct memory of the HiveServer service reaches the threshold(default value: 95%) of the maximum direct memory specified for HiveServer.

                • If yes, go to 4.
                • If no, go to 7.
                -

              3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select MetaStore Memory Usage Statistics and click OK, check whether the used direct memory of the MetaStore service reaches the threshold(default value: 95%) of the maximum direct memory specified for MetaStore.

                • If yes, go to 4.
                • If no, go to 7.
                -

              4. On the FusionInsight Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -XX:MaxDirectMemorySize in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

                Suggestions for GC parameter settings for the HiveServer:
                • It is recommended that you set the value of -XX:MaxDirectMemorySize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 8 GB, -XX:MaxDirectMemorySize is set to 1024 MB. If -Xmx is set to 4 GB, -XX:MaxDirectMemorySize is set to 512 MB. It is recommended that the value of -XX:MaxDirectMemorySize be greater than or equal to 512 MB.
                +
                1. On the MRS Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16006. Then check the role name in Location and confirm the IP adress of the instance.

                  • If the role for which the alarm is generated is HiveServer, go to 2.
                  • If the role for which the alarm is generated is MetaStore, go to 3.
                  +

                2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select HiveServer Memory Usage Statistics and click OK, check whether the used direct memory of the HiveServer service reaches the threshold(default value: 95%) of the maximum direct memory specified for HiveServer.

                  • If yes, go to 4.
                  • If no, go to 7.
                  +

                3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select MetaStore Memory Usage Statistics and click OK, check whether the used direct memory of the MetaStore service reaches the threshold(default value: 95%) of the maximum direct memory specified for MetaStore.

                  • If yes, go to 4.
                  • If no, go to 7.
                  +

                4. On the MRS Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -XX:MaxDirectMemorySize in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

                  Suggestions for GC parameter settings for the HiveServer:
                  • It is recommended that you set the value of -XX:MaxDirectMemorySize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 8 GB, -XX:MaxDirectMemorySize is set to 1024 MB. If -Xmx is set to 4 GB, -XX:MaxDirectMemorySize is set to 512 MB. It is recommended that the value of -XX:MaxDirectMemorySize be greater than or equal to 512 MB.
                  Suggestions for GC parameter settings for the MetaServer:
                  • It is recommended that you set the value of -XX:MaxDirectMemorySize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 8 GB, -XX:MaxDirectMemorySize is set to 1024 MB. If -Xmx is set to 4 GB, -XX:MaxDirectMemorySize is set to 512 MB. It is recommended that the value of -XX:MaxDirectMemorySize be greater than or equal to 512 MB.
                  @@ -77,7 +77,7 @@

                5. Click More > Restart Service to restart the service.
                6. Check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 7.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select Hive in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected fault logs.
                +
                1. On the MRS Manager portal, choose O&M > Log > Download.
                2. Select Hive in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected fault logs.

                Alarm Clearing

                After the fault is rectified, the system automatically clears this alarm.

                diff --git a/docs/mrs/umn/ALM-16007.html b/docs/mrs/umn/ALM-16007.html index 51772d70..8c603e88 100644 --- a/docs/mrs/umn/ALM-16007.html +++ b/docs/mrs/umn/ALM-16007.html @@ -64,12 +64,12 @@

                Possible Causes

                The memory of Hive instances is overused, the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                Procedure

                Check the GC time.

                -
                1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16007. Then check the role name in Location and confirm the IP adress of the instance.

                  • If the role for which the alarm is generated is HiveServer, go to 2.
                  • If the role for which the alarm is generated is MetaStore, go to 3.
                  -

                2. On the FusionInsight Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC, and select Garbage Collection (GC) Time of HiveServer and click OK to check whether the GC time is longer than 12 seconds.

                  • If yes, go to 4.
                  • If no, go to 7.
                  -

                3. On the FusionInsight Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC, and select Garbage Collection (GC) Time of MetaStore and click OK to check whether the GC time is longer than 12 seconds.

                  • If yes, go to 4.
                  • If no, go to 7.
                  +
                  1. On the MRS Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16007. Then check the role name in Location and confirm the IP adress of the instance.

                    • If the role for which the alarm is generated is HiveServer, go to 2.
                    • If the role for which the alarm is generated is MetaStore, go to 3.
                    +

                  2. On the MRS Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC, and select Garbage Collection (GC) Time of HiveServer and click OK to check whether the GC time is longer than 12 seconds.

                    • If yes, go to 4.
                    • If no, go to 7.
                    +

                  3. On the MRS Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC, and select Garbage Collection (GC) Time of MetaStore and click OK to check whether the GC time is longer than 12 seconds.

                    • If yes, go to 4.
                    • If no, go to 7.

                  Check the current JVM configuration.

                  -
                  1. On the FusionInsight Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -Xmx in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

                    Suggestions for GC parameter settings for the HiveServer:
                    • When the Hive GC time exceeds the threshold, change the value of -Xmx to twice the default value. For example, if -Xmx is set to 2 GB by default, change the value of -Xmx to 4 GB.
                    +
                    1. On the MRS Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -Xmx in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

                      Suggestions for GC parameter settings for the HiveServer:
                      • When the Hive GC time exceeds the threshold, change the value of -Xmx to twice the default value. For example, if -Xmx is set to 2 GB by default, change the value of -Xmx to 4 GB.
                      • You are advised to change the value of -Xms to set the ratio of -Xms and -Xmx to 1:2 to avoid performance problems when JVM dynamically.
                      Suggestions for GC parameter settings for the MetaServer:
                      • When the Meta GC time exceeds the threshold, change the value of -Xmx to twice the default value. For example, if -Xmx is set to 2 GB by default, change the value of -Xmx to 4 GB.
                      @@ -79,7 +79,7 @@

                    2. Click More > Restart Service to restart the service.
                    3. Check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 7.

                    Collect fault information.

                    -
                    1. On the FusionInsight Manager portal of active and standby clusters, choose O&M > Log > Download.
                    2. In the Service, select Hive in the required cluster.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected logs.
                    +
                    1. On the MRS Manager portal of active and standby clusters, choose O&M > Log > Download.
                    2. In the Service, select Hive in the required cluster.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    diff --git a/docs/mrs/umn/ALM-16008.html b/docs/mrs/umn/ALM-16008.html index a5436293..50d72419 100644 --- a/docs/mrs/umn/ALM-16008.html +++ b/docs/mrs/umn/ALM-16008.html @@ -61,10 +61,10 @@

                    Possible Causes

                    The non-heap memory of the Hive instance on the node is overused or the non-heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

                    Procedure

                    Check non-heap memory usage.

                    -
                    1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16008. Then check the role name in Location and confirm the IP adress of the instance.

                      • If the role for which the alarm is generated is HiveServer, go to 2.
                      • If the role for which the alarm is generated is MetaStore, go to 3.
                      -

                    2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select HiveServer Memory Usage Statistics and click OK, check whether the used non-heap memory of the HiveServer service reaches the threshold(default value: 95%) of the maximum non-heap memory specified for HiveServer.

                      • If yes, go to 4.
                      • If no, go to 7.
                      -

                    3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select MetaStore Memory Usage Statistics and click OK, check whether the used non-heap memory of the MetaStore service reaches the threshold(default value: 95%) of the maximum non-heap memory specified for MetaStore.

                      • If yes, go to 4.
                      • If no, go to 7.
                      -

                    4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -XX:MaxMetaspaceSize in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

                      Suggestions for GC parameter settings for the HiveServer:
                      • It is recommended that you set the value of -XX:MaxMetaspaceSize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 2 GB, -XX:

                        MaxMetaspaceSize is set to 256 MB. If -Xmx is set to 4 GB, -XX:MaxMetaspaceSize is set to 512 MB.

                        +
                        1. On the MRS Manager portal, click O&M > Alarm > Alarms and select the alarm whose Alarm ID is 16008. Then check the role name in Location and confirm the IP adress of the instance.

                          • If the role for which the alarm is generated is HiveServer, go to 2.
                          • If the role for which the alarm is generated is MetaStore, go to 3.
                          +

                        2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the HiveServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select HiveServer Memory Usage Statistics and click OK, check whether the used non-heap memory of the HiveServer service reaches the threshold(default value: 95%) of the maximum non-heap memory specified for HiveServer.

                          • If yes, go to 4.
                          • If no, go to 7.
                          +

                        3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Instance and click the MetaStore for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory, and select MetaStore Memory Usage Statistics and click OK, check whether the used non-heap memory of the MetaStore service reaches the threshold(default value: 95%) of the maximum non-heap memory specified for MetaStore.

                          • If yes, go to 4.
                          • If no, go to 7.
                          +

                        4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Hive > Configurations > All Configurations. Choose HiveServer/MetaStore > JVM. Adjust the value of -XX:MaxMetaspaceSize in HIVE_GC_OPTS/METASTORE_GC_OPTS as the following rules. Click Save.

                          Suggestions for GC parameter settings for the HiveServer:
                          • It is recommended that you set the value of -XX:MaxMetaspaceSize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 2 GB, -XX:

                            MaxMetaspaceSize is set to 256 MB. If -Xmx is set to 4 GB, -XX:MaxMetaspaceSize is set to 512 MB.

                          Suggestions for GC parameter settings for the MetaServer:
                          • It is recommended that you set the value of -XX:MaxMetaspaceSize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 2 GB, -XX:

                            MaxMetaspaceSize is set to 256 MB. If -Xmx is set to 4 GB, -XX:MaxMetaspaceSize is set to 512 MB

                            @@ -74,7 +74,7 @@

                          • Click More > Restart Service to restart the service.
                          • Check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 7.

                        Collect fault information.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                        2. Select Hive in the required cluster from the Service.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected logs.
                        +
                        1. On the MRS Manager portal, choose O&M > Log > Download.
                        2. Select Hive in the required cluster from the Service.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected logs.

                      Alarm Clearing

                      After the fault is rectified, the system automatically clears this alarm.

                      diff --git a/docs/mrs/umn/ALM-16009.html b/docs/mrs/umn/ALM-16009.html index d7fffe70..1cc0ced2 100644 --- a/docs/mrs/umn/ALM-16009.html +++ b/docs/mrs/umn/ALM-16009.html @@ -64,10 +64,10 @@

                      Possible Causes

                      The HQL statements are not the optimal.

                      Procedure

                      Check the number of HQL maps.

                      -
                      1. On FusionInsight Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Resource. Check the HQL statements with the excessively large number (5000 or more) of maps in HQL Map Count.
                      1. Locate the corresponding HQL statements, optimize them and execute them again.
                      2. Check whether the alarm is cleared.

                        • If it is, no further action is required.
                        • If it is not, go to 4.
                        +
                        1. On MRS Manager portal, choose Cluster >Name of the desired cluster > Services > Hive > Resource. Check the HQL statements with the excessively large number (5000 or more) of maps in HQL Map Count.
                        1. Locate the corresponding HQL statements, optimize them and execute them again.
                        2. Check whether the alarm is cleared.

                          • If it is, no further action is required.
                          • If it is not, go to 4.

                        Collect fault information.

                        -
                        1. On the FusionInsight Manager, choose O&M > Log > Download.
                        2. Select Hive in the required cluster from the Service.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected logs.
                        +
                        1. On the MRS Manager, choose O&M > Log > Download.
                        2. Select Hive in the required cluster from the Service.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected logs.

                      Alarm Clearing

                      After the fault is rectified, the system automatically clears this alarm.

                      diff --git a/docs/mrs/umn/ALM-16047.html b/docs/mrs/umn/ALM-16047.html index 71bff408..6469b669 100644 --- a/docs/mrs/umn/ALM-16047.html +++ b/docs/mrs/umn/ALM-16047.html @@ -59,10 +59,10 @@

                      Possible Causes

                      • The network is disconnected.
                      • The ZooKeeper instance is abnormal.

                      Procedure

                      Restart related instances.

                      -
                      1. Log in to FusionInsight Manager. Choose O&M > Alarm > Alarms, click the drop-down list in the row that contains the alarm, and view role and the IP address of the node for which the alarm is generated in Location.
                      2. Choose Cluster > Name of the desired cluster > Services > Hive > Instance, select the instance at the IP address for which the alarm is generated, and choose More > Restart Instance.
                      3. Wait for 5 minutes and check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 4.
                        +
                        1. Log in to MRS Manager. Choose O&M > Alarm > Alarms, click the drop-down list in the row that contains the alarm, and view role and the IP address of the node for which the alarm is generated in Location.
                        2. Choose Cluster > Name of the desired cluster > Services > Hive > Instance, select the instance at the IP address for which the alarm is generated, and choose More > Restart Instance.
                        3. Wait for 5 minutes and check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 4.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select Hive for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select Hive for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-17003.html b/docs/mrs/umn/ALM-17003.html index 84cf05c3..ad5ff631 100644 --- a/docs/mrs/umn/ALM-17003.html +++ b/docs/mrs/umn/ALM-17003.html @@ -60,7 +60,7 @@

                      Possible Causes

                      • The DBService service is abnormal or the data of Oozie stored in DBService is damaged.
                      • The HDFS service is abnormal or the data of Oozie stored in HDFS is damaged.
                      • The Yarn service is abnormal.
                      • The Nodeagent process is abnormal.

                      Procedure

                      Query the Oozie service health status code.

                      -
                      1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster >Services > Oozie. Click oozie (any one is OK) on the oozie WebUI. to go to the Oozie WebUI.

                        By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                        +
                        1. On the MRS Manager portal, choose Cluster > Name of the desired cluster >Services > Oozie. Click oozie (any one is OK) on the oozie WebUI. to go to the Oozie WebUI.

                          By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                        2. Add /servicehealth to the URL in the address box of the browser and access again. The value of statusCode is the current Oozie service health status code.

                          For example, visit https://10.10.0.117:20026/Oozie/oozie/130/oozie/servicehealth. The result is as follows:

                          {"beans":[{"name":"serviceStatus","statusCode":0}]}
                          @@ -117,9 +117,9 @@

                      Check the DBService service.

                      -
                      1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services, and check whether the DBService service is running properly.

                        • If yes, go to 6.
                        • If no, go to 5.
                        +
                        1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services, and check whether the DBService service is running properly.

                          • If yes, go to 6.
                          • If no, go to 5.

                        2. Resolve the problem of DBService based on the alarm help and check whether the Oozie alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 18.
                          -

                        3. Log in to the Oozie database to check whether the data is complete.

                          1. Log in to the active DBService node as user root.

                            On the FusionInsight Manager page, choose Cluster > Name of the desired cluster > Services > DBService > Instance to view the IP address of the active DBservice node.

                            +

                          2. Log in to the Oozie database to check whether the data is complete.

                            1. Log in to the active DBService node as user root.

                              On the MRS Manager page, choose Cluster > Name of the desired cluster > Services > DBService > Instance to view the IP address of the active DBservice node.

                            2. Run the following command to log in to the Oozie database:

                              su - omm

                              source ${BIGDATA_HOME}/FusionInsight_BASE_8.1.0.1/install/FusionInsight-dbservice-2.7.0/.dbservice_profile

                              gsql -U Username -W Oozie database password -p 20051 -d Database name

                              @@ -127,7 +127,7 @@

                          Check the HDFS service.

                          -
                          1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services, and check whether the HDFS service is running properly.

                            • If yes, go to 9.
                            • If no, go to 8.
                            +
                            1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services, and check whether the HDFS service is running properly.

                              • If yes, go to 9.
                              • If no, go to 8.

                            2. Resolve the problem of HDFS based on the alarm help and check whether the Oozie alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 18.

                            3. Log in to HDFS to check whether the Oozie file directory structure is complete.

                              1. Download and install an HDFS client..
                              2. Log in to the client node as user root and run the following commands to check whether /user/oozie/share exists.

                                If the cluster uses the security mode, perform security authentication.

                                kinit admin

                                @@ -137,7 +137,7 @@

                              3. In the Oozie client installation directory, manually upload the share directory to /user/oozie in HDFS, and check whether the alarm is cleared.

                                • If yes, no further action is required.
                                • If no, go to 18.

                              Check the Yarn and MapReduce service.

                              -
                              1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services, and check whether the Yarn and MapReduce services are running properly.

                                • If yes, go to 18.
                                • If no, go to 12.
                                +
                                1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services, and check whether the Yarn and MapReduce services are running properly.

                                  • If yes, go to 18.
                                  • If no, go to 12.

                                2. Resolve the problem of Yarn and MapReduce based on the alarm help and check whether the Oozie alarm is cleared.

                                  • If yes, no further action is required.
                                  • If no, go to 18.

                                Check the Oozie process.

                                diff --git a/docs/mrs/umn/ALM-17004.html b/docs/mrs/umn/ALM-17004.html index b1da6efa..5635734c 100644 --- a/docs/mrs/umn/ALM-17004.html +++ b/docs/mrs/umn/ALM-17004.html @@ -64,14 +64,14 @@

                                Possible Causes

                                The heap memory of the Oozie instance is overused or the heap memory is inappropriately allocated.

                                Procedure

                                Check heap memory usage.

                                -
                                1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Oozie Heap Memory Usage Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
                                2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Oozie Heap Memory Resource Percentage. Click OK.
                                3. Check whether the used heap memory of Oozie reaches the threshold (the default value is 95% of the maximum heap memory) specified for Oozie.

                                  • If yes, go to 4.
                                  • If no, go to 6.
                                  -

                                4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations > All Configurations. Set Search GC_OPTS in the search box. Increase the value of -Xmx as required, and click Save > OK.

                                  Suggestions on GC parameter settings for Oozie:

                                  +
                                  1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Oozie Heap Memory Usage Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
                                  2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Oozie Heap Memory Resource Percentage. Click OK.
                                  3. Check whether the used heap memory of Oozie reaches the threshold (the default value is 95% of the maximum heap memory) specified for Oozie.

                                    • If yes, go to 4.
                                    • If no, go to 6.
                                    +

                                  4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations > All Configurations. Set Search GC_OPTS in the search box. Increase the value of -Xmx as required, and click Save > OK.

                                    Suggestions on GC parameter settings for Oozie:

                                    You are advised to set -Xms and -Xmx to the same value to prevent adverse impact on performance when JVM dynamically adjusts the heap memory size.

                                  5. Restart the affected services or instances and check whether the alarm is cleared.

                                    • If yes, no further action is required.
                                    • If no, go to 6.

                                  Collect fault information.

                                  -
                                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                  2. Select Oozie in the required cluster from the Service.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.
                                  +
                                  1. On the MRS Manager portal, choose O&M > Log > Download.
                                  2. Select Oozie in the required cluster from the Service.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.

                                  Alarm Clearing

                                  After the fault is rectified, the system automatically clears this alarm.

                                  diff --git a/docs/mrs/umn/ALM-17005.html b/docs/mrs/umn/ALM-17005.html index 278ba83b..a547a907 100644 --- a/docs/mrs/umn/ALM-17005.html +++ b/docs/mrs/umn/ALM-17005.html @@ -64,15 +64,15 @@

                                  Possible Causes

                                  The non-heap memory of the Oozie instance is overused or the non-heap memory is inappropriately allocated.

                                  Procedure

                                  Check non-heap memory usage.

                                  -
                                  1. On FusionInsight Manager, choose O&M > Alarm > Alarms > Oozie Non Heap Memory Usage Exceeds the Threshold. On the displayed page, check the location information of the alarm. Check the name of the instance host for which the alarm is generated.
                                  2. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Oozie and click the Instance tab. On the displayed page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Memory and select Oozie Non Heap Memory Resource Percentage. Click OK.
                                  3. Check whether the non-heap memory used by Oozie reaches the threshold (80% of the maximum non-heap memory by default).

                                    • If yes, go to 4.
                                    • If no, go to 6.
                                    -

                                  4. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Oozie and click the Configurations and then All Configurations. On the displayed page, search for the GC_OPTS parameter in the search box and check whether it contains -XX: MaxMetaspaceSize. If yes, increase the value of -XX: MaxMetaspaceSize based on the site requirements. If no, manually add -XX: MaxMetaspaceSize and set its value to 1/8 of the value of -Xmx. Click Save, and then click OK

                                    JDK1.8 does not support the MaxPermSize parameter.

                                    +
                                    1. On MRS Manager, choose O&M > Alarm > Alarms > Oozie Non Heap Memory Usage Exceeds the Threshold. On the displayed page, check the location information of the alarm. Check the name of the instance host for which the alarm is generated.
                                    2. On MRS Manager, choose Cluster > Name of the target cluster > Services > Oozie and click the Instance tab. On the displayed page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Memory and select Oozie Non Heap Memory Resource Percentage. Click OK.
                                    3. Check whether the non-heap memory used by Oozie reaches the threshold (80% of the maximum non-heap memory by default).

                                      • If yes, go to 4.
                                      • If no, go to 6.
                                      +

                                    4. On MRS Manager, choose Cluster > Name of the target cluster > Services > Oozie and click the Configurations and then All Configurations. On the displayed page, search for the GC_OPTS parameter in the search box and check whether it contains -XX: MaxMetaspaceSize. If yes, increase the value of -XX: MaxMetaspaceSize based on the site requirements. If no, manually add -XX: MaxMetaspaceSize and set its value to 1/8 of the value of -Xmx. Click Save, and then click OK

                                      JDK1.8 does not support the MaxPermSize parameter.

                                      Suggestions on GC parameter settings for Oozie:

                                      Set the value of -XX:MaxMetaspaceSize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 2 GB, -XX:MaxMetaspaceSize is set to 256 MB. If -Xmx is set to 4 GB, -XX:MaxMetaspaceSize is set to 512 MB.

                                    5. Restart the affected services or instances and check whether the alarm is cleared.

                                      • If yes, no further action is required.
                                      • If no, go to 6.

                                    Collect the fault information.

                                    -
                                    1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                    2. Expand the Service drop-down list, and select Oozie for the target cluster.
                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                    4. Contact O&M personnel and provide the collected logs.
                                    +
                                    1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                    2. Expand the Service drop-down list, and select Oozie for the target cluster.
                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                    4. Contact O&M personnel and provide the collected logs.

                                    Alarm Clearing

                                    This alarm is automatically cleared after the fault is rectified.

                                    diff --git a/docs/mrs/umn/ALM-17006.html b/docs/mrs/umn/ALM-17006.html index 616bc35c..d34c8bd6 100644 --- a/docs/mrs/umn/ALM-17006.html +++ b/docs/mrs/umn/ALM-17006.html @@ -64,14 +64,14 @@

                                    Possible Causes

                                    The direct memory of the Oozie instance is overused or the direct memory is inappropriately allocated.

                                    Procedure

                                    Check direct memory usage.

                                    -
                                    1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Oozie Direct Memory Usage Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
                                    2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Oozie Direct Buffer Resource Percentage. Click OK.
                                    3. Check whether the used direct memory of Oozie reaches the threshold (the default value is 80% of the maximum direct memory) specified for Oozie.

                                      • If yes, go to 4.
                                      • If no, go to 6.
                                      -

                                    4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations. Click All Configurations. Search GC_OPTS in the search box. Increase the value of -XX:MaxDirectMemorySize as required, and click Save. Click OK.

                                      Suggestions on GC parameter settings for Oozie:

                                      +
                                      1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Oozie Direct Memory Usage Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
                                      2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Oozie Direct Buffer Resource Percentage. Click OK.
                                      3. Check whether the used direct memory of Oozie reaches the threshold (the default value is 80% of the maximum direct memory) specified for Oozie.

                                        • If yes, go to 4.
                                        • If no, go to 6.
                                        +

                                      4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations. Click All Configurations. Search GC_OPTS in the search box. Increase the value of -XX:MaxDirectMemorySize as required, and click Save. Click OK.

                                        Suggestions on GC parameter settings for Oozie:

                                        You are advised to set the value of -XX:MaxDirectMemorySize to 1/4 of the value of -Xmx. For example, if -Xmx is set to 4 GB, -XX:MaxDirectMemorySize is set to 1024 MB. If -Xmx is set to 2 GB, -XX:MaxDirectMemorySize is set to 512 MB. It is recommended that the value of -XX:MaxDirectMemorySize be greater than or equal to 512 MB.

                                      5. Restart the affected services or instances and check whether the alarm is cleared.

                                        • If yes, no further action is required.
                                        • If no, go to 6.

                                      Collect fault information.

                                      -
                                      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                      2. Select Oozie in the required cluster from the Service drop-down list.
                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                      4. Contact the O&M personnel and send the collected logs.
                                      +
                                      1. On the MRS Manager portal, choose O&M > Log > Download.
                                      2. Select Oozie in the required cluster from the Service drop-down list.
                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                      4. Contact the O&M personnel and send the collected logs.

                                      Alarm Clearing

                                      After the fault is rectified, the system automatically clears this alarm.

                                      diff --git a/docs/mrs/umn/ALM-17007.html b/docs/mrs/umn/ALM-17007.html index fb9b20fe..b0da46e8 100644 --- a/docs/mrs/umn/ALM-17007.html +++ b/docs/mrs/umn/ALM-17007.html @@ -64,14 +64,14 @@

                                      Possible Causes

                                      The heap memory of the Oozie instance is overused or the heap memory is inappropriately allocated.

                                      Procedure

                                      Check GC time.

                                      -
                                      1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Garbage Collection (GC) Time of the Oozie Process Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
                                      2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > GC > Garbage Collection (GC) Time of Oozie. Click OK.
                                      3. Check whether GC time of the Oozie process every second exceeds the threshold (default value: 12 seconds).

                                        • If yes, go to 4.
                                        • If no, go to 6.
                                        -

                                      4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations. Click All Configurations. Search GC_OPTS in the search box. Increase the value of -Xmx as required, and click Save. Click OK.

                                        Suggestions on GC parameter settings for Oozie:

                                        +
                                        1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Garbage Collection (GC) Time of the Oozie Process Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
                                        2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > GC > Garbage Collection (GC) Time of Oozie. Click OK.
                                        3. Check whether GC time of the Oozie process every second exceeds the threshold (default value: 12 seconds).

                                          • If yes, go to 4.
                                          • If no, go to 6.
                                          +

                                        4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations. Click All Configurations. Search GC_OPTS in the search box. Increase the value of -Xmx as required, and click Save. Click OK.

                                          Suggestions on GC parameter settings for Oozie:

                                          You are advised to set -Xms and -Xmx to the same value to prevent adverse impact on performance when JVM dynamically adjusts the heap memory size.

                                        5. Restart the affected services or instances and check whether the alarm is cleared.

                                          • If yes, no further action is required.
                                          • If no, go to 6.

                                        Collect fault information.

                                        -
                                        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                        2. Select Oozie in the required cluster from the Service drop-down list.
                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                        4. Contact the O&M personnel and send the collected logs.
                                        +
                                        1. On the MRS Manager portal, choose O&M > Log > Download.
                                        2. Select Oozie in the required cluster from the Service drop-down list.
                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                        4. Contact the O&M personnel and send the collected logs.

                                        Alarm Clearing

                                        After the fault is rectified, the system automatically clears this alarm.

                                        diff --git a/docs/mrs/umn/ALM-18000.html b/docs/mrs/umn/ALM-18000.html index 3621f3a6..7fc246ff 100644 --- a/docs/mrs/umn/ALM-18000.html +++ b/docs/mrs/umn/ALM-18000.html @@ -60,22 +60,22 @@

                                        Possible Causes

                                        • The ZooKeeper service is abnormal.
                                        • The HDFS service is abnormal.
                                        • There is no active ResourceManager instance in the Yarn cluster.
                                        • All the NodeManagers in the Yarn cluster are abnormal.

                                        Procedure

                                        Check ZooKeeper service status.

                                        -
                                        1. On the FusionInsight Manager, check whether the alarm list contains ALM-13000 ZooKeeper Service Unavailable.

                                          • If yes, go to 2.
                                          • If no, go to 3.
                                          +
                                          1. On the MRS Manager, check whether the alarm list contains ALM-13000 ZooKeeper Service Unavailable.

                                            • If yes, go to 2.
                                            • If no, go to 3.

                                          2. Rectify the fault by following the steps provided in ALM-13000 ZooKeeper Service Unavailable, and check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 3.

                                          Check the HDFS service status.

                                          -
                                          1. On the FusionInsight Manager, check whether the alarm list contains the HDFS alarms.

                                            • If yes, go to 4.
                                            • If no, go to 5.
                                            +
                                            1. On the MRS Manager, check whether the alarm list contains the HDFS alarms.

                                              • If yes, go to 4.
                                              • If no, go to 5.

                                            2. Choose O&M > Alarm > Alarms, handle HDFS alarms based on the alarm help, and check whether the Yarn alarm is cleared.

                                              • If yes, no further action is required.
                                              • If no, go to 5.

                                            Check the ResourceManager status in the Yarn cluster.

                                            -
                                            1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn.
                                            2. In Dashboard, check whether there is an active ResourceManager instance in the Yarn cluster.

                                              • If yes, go to 7.
                                              • If no, go to 10.
                                              +
                                              1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn.
                                              2. In Dashboard, check whether there is an active ResourceManager instance in the Yarn cluster.

                                                • If yes, go to 7.
                                                • If no, go to 10.

                                              Check the NodeManager node status in the Yarn cluster.

                                              -
                                              1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance.
                                              2. Query NodeManager Running Status, and check whether there are unhealthy nodes.

                                                • If yes, go to 9.
                                                • If no, go to 10.
                                                +
                                                1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance.
                                                2. Query NodeManager Running Status, and check whether there are unhealthy nodes.

                                                  • If yes, go to 9.
                                                  • If no, go to 10.

                                                3. Rectify the fault by following the steps provided in ALM-18002 NodeManager Heartbeat Lost or ALM-18003 NodeManager Unhealthy. After the fault is rectified, check whether the Yarn alarm is cleared.

                                                  • If yes, no further action is required.
                                                  • If no, go to 10.

                                                Collect fault information.

                                                -
                                                1. On the FusionInsight Manager portal of the active cluster, choose O&M > Log > Download.
                                                2. Select Yarn in the required cluster from the Service.
                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                4. Contact the O&M personnel and send the collected logs.
                                                +
                                                1. On the MRS Manager portal of the active cluster, choose O&M > Log > Download.
                                                2. Select Yarn in the required cluster from the Service.
                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                4. Contact the O&M personnel and send the collected logs.

                                        Alarm Clearing

                                        After the fault is rectified, the system automatically clears this alarm.

                                        diff --git a/docs/mrs/umn/ALM-18002.html b/docs/mrs/umn/ALM-18002.html index 9f3a5211..5d60f2b8 100644 --- a/docs/mrs/umn/ALM-18002.html +++ b/docs/mrs/umn/ALM-18002.html @@ -2,7 +2,7 @@

                                        ALM-18002 NodeManager Heartbeat Lost

                                        Description

                                        The system checks the number of lost NodeManager nodes every 30 seconds, and compares the number with the threshold. The Number of Lost Nodes indicator has a default threshold. The alarm is generated when the value of Number of Lost Nodes exceeds the threshold.

                                        -

                                        To change the threshold, on FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Yarn. On the displayed page, choose Configurations > All Configurations, and change the value of yarn.nodemanager.lost.alarm.threshold. You do not need to restart Yarn to make the change take effect.

                                        +

                                        To change the threshold, on MRS Manager, choose Cluster > Name of the desired cluster > Services > Yarn. On the displayed page, choose Configurations > All Configurations, and change the value of yarn.nodemanager.lost.alarm.threshold. You do not need to restart Yarn to make the change take effect.

                                        The default threshold is 0. The alarm is generated when the number of lost nodes exceeds the threshold, and is cleared when the number of lost nodes is less than the threshold.

                                        @@ -67,13 +67,13 @@

                                        Possible Causes

                                        • NodeManager is forcibly deleted without decommission.
                                        • All the NodeManager instances are stopped or the NodeManager process is faulty.
                                        • The host where the NodeManager node resides is faulty.
                                        • The network between the NodeManager and ResourceManager is disconnected or busy.

                                        Procedure

                                        Check the NodeManager status.

                                        -
                                        1. On the FusionInsight Manager, and choose O&M > Alarm > Alarms. Click before the alarm and obtain lost nodes in Additional Information.
                                        2. Check whether the lost nodes are hosts that have been manually deleted without decommission.

                                          • If yes, go to 3.
                                          • If no, go to 5.
                                          +
                                          1. On the MRS Manager, and choose O&M > Alarm > Alarms. Click before the alarm and obtain lost nodes in Additional Information.
                                          2. Check whether the lost nodes are hosts that have been manually deleted without decommission.

                                            • If yes, go to 3.
                                            • If no, go to 5.

                                          3. After the setting, Choose Cluster > Name of the desired cluster > Services > Yarn. On the displayed page, choose Configurations > All Configurations. Search for yarn.nodemanager.lost.alarm.threshold and change its value to the number of hosts that are not out of service and proactively deleted. After the setting, check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 4.
                                            -

                                          4. Manually clear the alarm. Note that decommission must be performed before deleting hosts.
                                          5. On the FusionInsight Manager portal, choose Cluster > Hosts, and check whether the nodes obtained in 1 are healthy.

                                            • If yes, go to 7.
                                            • If no, go to 6.
                                            +

                                          6. Manually clear the alarm. Note that decommission must be performed before deleting hosts.
                                          7. On the MRS Manager portal, choose Cluster > Hosts, and check whether the nodes obtained in 1 are healthy.

                                            • If yes, go to 7.
                                            • If no, go to 6.

                                          8. Rectify the node fault based on ALM-12006 Node Fault and check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 7.

                                          Check the process status.

                                          -
                                          1. On the FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Yarn > Instance, and check whether there are NodeManager instances whose status is not Good.

                                            • If yes, go to 10.
                                            • If no, go to 8.
                                            +
                                            1. On the MRS Manager, choose Cluster > Name of the desired cluster > Services > Yarn > Instance, and check whether there are NodeManager instances whose status is not Good.

                                              • If yes, go to 10.
                                              • If no, go to 8.

                                            2. Check whether the NodeManager instance is deleted.

                                              • If yes, go to 9.
                                              • If no, go to 11.

                                            3. Restart the active and standby ResourceManager instances, and check whether the alarm is cleared.

                                              • If yes, no further action is required.
                                              • If no, go to 13.

                                            @@ -85,7 +85,7 @@

                                          2. Rectify the network, and check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 13.

                                          Collect fault information.

                                          -
                                          1. On the FusionInsight Manager in the active cluster, choose O&M > Log > Download.
                                          2. Select Yarn in the required cluster from the Service.
                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                          4. Contact the O&M personnel and send the collected logs.
                                          +
                                          1. On the MRS Manager in the active cluster, choose O&M > Log > Download.
                                          2. Select Yarn in the required cluster from the Service.
                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                          4. Contact the O&M personnel and send the collected logs.

                                        Alarm Clearing

                                        After the fault is rectified, the system automatically clears this alarm.

                                        diff --git a/docs/mrs/umn/ALM-18003.html b/docs/mrs/umn/ALM-18003.html index 513c5e82..34daba9a 100644 --- a/docs/mrs/umn/ALM-18003.html +++ b/docs/mrs/umn/ALM-18003.html @@ -2,7 +2,7 @@

                                        ALM-18003 NodeManager Unhealthy

                                        Description

                                        The system checks the number of unhealthy NodeManager nodes every 30 seconds, and compares the number with the threshold. The Unhealthy Nodes indicator has a default threshold. This alarm is generated when the value of the Unhealthy Nodes indicator exceeds the threshold.

                                        -

                                        To change the threshold, on FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Yarn. On the displayed page, choose Configurations > All Configurations, and change the value of yarn.nodemanager.unhealthy.alarm.threshold. You do not need to restart Yarn to make the change take effect.

                                        +

                                        To change the threshold, on MRS Manager, choose Cluster > Name of the desired cluster > Services > Yarn. On the displayed page, choose Configurations > All Configurations, and change the value of yarn.nodemanager.unhealthy.alarm.threshold. You do not need to restart Yarn to make the change take effect.

                                        The default threshold is 0. The alarm is generated when the number of unhealthy nodes exceeds the threshold, and is cleared when the number of unhealthy nodes is less than the threshold.

                                        Attribute

                                        @@ -66,7 +66,7 @@

                                        Possible Causes

                                        • The hard disk space of the host where the NodeManager node resides is insufficient.
                                        • User omm does not have the permission to access a local directory on the NodeManager node.

                                        Procedure

                                        Check the hard disk space of the host.

                                        -
                                        1. On the FusionInsight Manager, and choose O&M > Alarm > Alarms. Click before the alarm and obtain unhealthy nodes in Additional Information.
                                        2. Choose Cluster > Name of the desired cluster > Services > Yarn > Instance, select the NodeManager instance corresponding to the host, choose Instance Configurations > All Configurations and view disks corresponding to yarn.nodemanager.local-dirs and yarn.nodemanager.log-dirs.
                                        3. Choose O&M > Alarm > Alarms. In the alarm list, check whether the related disk has the alarm ALM-12017 Insufficient Disk Capacity.

                                          • If yes, go to 4.
                                          • If no, go to 5.
                                          +
                                          1. On the MRS Manager, and choose O&M > Alarm > Alarms. Click before the alarm and obtain unhealthy nodes in Additional Information.
                                          2. Choose Cluster > Name of the desired cluster > Services > Yarn > Instance, select the NodeManager instance corresponding to the host, choose Instance Configurations > All Configurations and view disks corresponding to yarn.nodemanager.local-dirs and yarn.nodemanager.log-dirs.
                                          3. Choose O&M > Alarm > Alarms. In the alarm list, check whether the related disk has the alarm ALM-12017 Insufficient Disk Capacity.

                                            • If yes, go to 4.
                                            • If no, go to 5.

                                          4. Rectify the disk fault based on ALM-12017 Insufficient Disk Capacit and check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 7.

                                          5. Choose Hosts > Name of the desired host . On the Dashboard page, check the disk usage of the corresponding partition. Check whether the percentage of the used space of the mounted disk exceeds the value of yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage

                                            • If yes, go to 6.
                                            • If no, go to 7.

                                          6. Reduce the disk usage to less than the value of yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage, wait for 10 to 20 minutes, and check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 7.
                                            @@ -78,7 +78,7 @@

                                          7. Wait for 10 to 20 minutes and check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 11.

                                          Collect fault information.

                                          -
                                          1. On the FusionInsight Manager in the active cluster, choose O&M > Log > Download.
                                          2. Select Yarn in the required cluster from the Service.
                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                          4. Contact the O&M personnel and send the collected logs.
                                          +
                                          1. On the MRS Manager in the active cluster, choose O&M > Log > Download.
                                          2. Select Yarn in the required cluster from the Service.
                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                          4. Contact the O&M personnel and send the collected logs.

                                        Alarm Clearing

                                        After the fault is rectified, the system automatically clears this alarm.

                                        diff --git a/docs/mrs/umn/ALM-18008.html b/docs/mrs/umn/ALM-18008.html index a1d3e791..e4169e38 100644 --- a/docs/mrs/umn/ALM-18008.html +++ b/docs/mrs/umn/ALM-18008.html @@ -66,14 +66,14 @@

                                        Possible Causes

                                        The heap memory of the Yarn ResourceManager instance on the node is overused or the heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

                                        Procedure

                                        Check the heap memory usage.

                                        -
                                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                        2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager (Indicates the host name of the instance for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > ResourceManager > Percentage of Used Memory of the ResourceManager. Check the heap memory usage.
                                        3. Check whether the used heap memory of ResourceManager reaches 95% of the maximum heap memory specified for ResourceManager.

                                          • If yes, go to 4.
                                          • If no, go to 6.
                                          -

                                        4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System. Increase the value of GC_OPTS parameter as required, click Save. Restart the role instance.

                                          The mapping between the number of NodeManager instances in a cluster and the memory size of ResourceManager is as follows:

                                          +
                                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                          2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager (Indicates the host name of the instance for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > ResourceManager > Percentage of Used Memory of the ResourceManager. Check the heap memory usage.
                                          3. Check whether the used heap memory of ResourceManager reaches 95% of the maximum heap memory specified for ResourceManager.

                                            • If yes, go to 4.
                                            • If no, go to 6.
                                            +

                                          4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System. Increase the value of GC_OPTS parameter as required, click Save. Restart the role instance.

                                            The mapping between the number of NodeManager instances in a cluster and the memory size of ResourceManager is as follows:

                                            • If the number of NodeManager instances in the cluster reaches 100, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                            • If the number of NodeManager instances in the cluster reaches 200, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms6G -Xmx6G -XX:NewSize=512M -XX:MaxNewSize=1G
                                            • If the number of NodeManager instances in the cluster reaches 500, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms10G -Xmx10G -XX:NewSize=1G -XX:MaxNewSize=2G
                                            • If the number of NodeManager instances in the cluster reaches 1000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms20G -Xmx20G -XX:NewSize=1G -XX:MaxNewSize=2G
                                            • If the number of NodeManager instances in the cluster reaches 2000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms40G -Xmx40G -XX:NewSize=2G -XX:MaxNewSize=4G
                                            • If the number of NodeManager instances in the cluster reaches 3000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms60G -Xmx60G -XX:NewSize=2G -XX:MaxNewSize=4G
                                            • If the number of NodeManager instances in the cluster reaches 4000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms80G -Xmx80G -XX:NewSize=2G -XX:MaxNewSize=4G
                                            • If the number of NodeManager instances in the cluster reaches 5000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms100G -Xmx100G -XX:NewSize=3G -XX:MaxNewSize=6G

                                          5. Check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 6.

                                          Collect fault information.

                                          -
                                          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                          2. Select the following node in the required cluster from the Service.

                                            • NodeAgent
                                            • Yarn
                                            +
                                            1. On the MRS Manager portal, choose O&M > Log > Download.
                                            2. Select the following node in the required cluster from the Service.

                                              • NodeAgent
                                              • Yarn

                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                            4. Contact the O&M personnel and send the collected logs.

                                          Alarm Clearing

                                          After the fault is rectified, the system automatically clears this alarm.

                                          diff --git a/docs/mrs/umn/ALM-18009.html b/docs/mrs/umn/ALM-18009.html index 9a04d76c..b2ebd74a 100644 --- a/docs/mrs/umn/ALM-18009.html +++ b/docs/mrs/umn/ALM-18009.html @@ -66,14 +66,14 @@

                                          Possible Causes

                                          The heap memory of the Mapreduce JobHistoryServer instance on the node is overused or the heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

                                          Procedure

                                          Check the memory usage.

                                          -
                                          1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18009 Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                          2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Mapreduce > Instance > JobHistoryServer. Click the drop-down menu in the upper right corner of Chart, choose Customize > JobHistoryServer heap memory usage statistics. JobHistoryServer indicates the corresponding HostName of the instance for which the alarm is generated. Check the heap memory usage.
                                          3. Check whether the used heap memory of JobHistoryServer reaches 95% of the maximum heap memory specified for JobHistoryServer.

                                            • If yes, go to 4.
                                            • If no, go to 6.
                                            -

                                          4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Mapreduce > Configurations > All Configurations > JobHistoryServer > System. Increase the value of GC_OPTS parameter as required, click Save. Click OK and restart the role instance.

                                            The mapping between the number of historical tasks (10000) and the memory of JobHistoryServer is as follows:

                                            +
                                            1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18009 Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                            2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Mapreduce > Instance > JobHistoryServer. Click the drop-down menu in the upper right corner of Chart, choose Customize > JobHistoryServer heap memory usage statistics. JobHistoryServer indicates the corresponding HostName of the instance for which the alarm is generated. Check the heap memory usage.
                                            3. Check whether the used heap memory of JobHistoryServer reaches 95% of the maximum heap memory specified for JobHistoryServer.

                                              • If yes, go to 4.
                                              • If no, go to 6.
                                              +

                                            4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Mapreduce > Configurations > All Configurations > JobHistoryServer > System. Increase the value of GC_OPTS parameter as required, click Save. Click OK and restart the role instance.

                                              The mapping between the number of historical tasks (10000) and the memory of JobHistoryServer is as follows:

                                              -Xms30G -Xmx30G -XX:NewSize=1G -XX:MaxNewSize=2G

                                            5. Check whether the alarm is cleared.

                                              • If yes, no further action is required.
                                              • If no, go to 6.

                                            Collect fault information.

                                            -
                                            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                            2. Select the following node in the required cluster from the Service.

                                              • NodeAgent
                                              • Mapreduce
                                              +
                                              1. On the MRS Manager portal, choose O&M > Log > Download.
                                              2. Select the following node in the required cluster from the Service.

                                                • NodeAgent
                                                • Mapreduce

                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                              4. Contact the O&M personnel and send the collected logs.

                                            Alarm Clearing

                                            After the fault is rectified, the system automatically clears this alarm.

                                            diff --git a/docs/mrs/umn/ALM-18010.html b/docs/mrs/umn/ALM-18010.html index 10070b3f..cc57a22b 100644 --- a/docs/mrs/umn/ALM-18010.html +++ b/docs/mrs/umn/ALM-18010.html @@ -65,14 +65,14 @@

                                            Possible Causes

                                            The heap memory of the ResourceManager instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                            Procedure

                                            Check the GC duration.

                                            -
                                            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18010 ResourceManager GC Time Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection (GC) Time of ResourceManager to check the GC duration statistics of the Broker process collected every minute.
                                            3. Check whether the GC duration of the ResourceManager process collected every minute exceeds the threshold (12 seconds by default).

                                              • If yes, go to 4.
                                              • If no, go to 7.
                                              -

                                            4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System to increase the value of GC_OPTS parameter as required.

                                              The mapping between the number of NodeManager instances in a cluster and the memory size of ResourceManager is as follows:

                                              +
                                              1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18010 ResourceManager GC Time Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                              2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection (GC) Time of ResourceManager to check the GC duration statistics of the Broker process collected every minute.
                                              3. Check whether the GC duration of the ResourceManager process collected every minute exceeds the threshold (12 seconds by default).

                                                • If yes, go to 4.
                                                • If no, go to 7.
                                                +

                                              4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System to increase the value of GC_OPTS parameter as required.

                                                The mapping between the number of NodeManager instances in a cluster and the memory size of ResourceManager is as follows:

                                                • If the number of NodeManager instances in the cluster reaches 100, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                • If the number of NodeManager instances in the cluster reaches 200, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms6G -Xmx6G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                • If the number of NodeManager instances in the cluster reaches 500, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms10G -Xmx10G -XX:NewSize=1G -XX:MaxNewSize=2G
                                                • If the number of NodeManager instances in the cluster reaches 1000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms20G -Xmx20G -XX:NewSize=1G -XX:MaxNewSize=2G
                                                • If the number of NodeManager instances in the cluster reaches 2000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms40G -Xmx40G -XX:NewSize=2G -XX:MaxNewSize=4G
                                                • If the number of NodeManager instances in the cluster reaches 3000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms60G -Xmx60G -XX:NewSize=2G -XX:MaxNewSize=4G
                                                • If the number of NodeManager instances in the cluster reaches 4000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms80G -Xmx80G -XX:NewSize=2G -XX:MaxNewSize=4G
                                                • If the number of NodeManager instances in the cluster reaches 5000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms100G -Xmx100G -XX:NewSize=3G -XX:MaxNewSize=6G

                                              5. Save the configuration and restart the ResourceManager instance.
                                              6. Check whether the alarm is cleared.

                                                • If yes, no further action is required.
                                                • If no, go to 7.

                                              Collect fault information.

                                              -
                                              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                              2. Select ResourceManager in the required cluster from the Service.
                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                              4. Contact the O&M personnel and send the collected logs.
                                              +
                                              1. On the MRS Manager portal, choose O&M > Log > Download.
                                              2. Select ResourceManager in the required cluster from the Service.
                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                              4. Contact the O&M personnel and send the collected logs.

                                              Alarm Clearing

                                              After the fault is rectified, the system automatically clears this alarm.

                                              diff --git a/docs/mrs/umn/ALM-18011.html b/docs/mrs/umn/ALM-18011.html index 832b3601..b911fbf5 100644 --- a/docs/mrs/umn/ALM-18011.html +++ b/docs/mrs/umn/ALM-18011.html @@ -65,14 +65,14 @@

                                              Possible Causes

                                              The heap memory of the NodeManager instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                              Procedure

                                              Check the GC duration.

                                              -
                                              1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18011 NodeManager GC Time Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                              2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection (GC) Time of NodeManager to check the GC duration statistics of the Broker process collected every minute.
                                              3. Check whether the GC duration of the NodeManager process collected every minute exceeds the threshold (12 seconds by default).

                                                • If yes, go to 4.
                                                • If no, go to 7.
                                                -

                                              4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > NodeManager > System to increase the value of GC_OPTS parameter as required.

                                                The mapping between the number of NodeManager instances in a cluster and the memory size of NodeManager is as follows:

                                                +
                                                1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18011 NodeManager GC Time Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection (GC) Time of NodeManager to check the GC duration statistics of the Broker process collected every minute.
                                                3. Check whether the GC duration of the NodeManager process collected every minute exceeds the threshold (12 seconds by default).

                                                  • If yes, go to 4.
                                                  • If no, go to 7.
                                                  +

                                                4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > NodeManager > System to increase the value of GC_OPTS parameter as required.

                                                  The mapping between the number of NodeManager instances in a cluster and the memory size of NodeManager is as follows:

                                                  • If the number of NodeManager instances in the cluster reaches 100, the recommended JVM parameters for NodeManager instances are as follows: -Xms2G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                  • If the number of NodeManager instances in the cluster reaches 200, the recommended JVM parameters for NodeManager instances are as follows: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                  • If the number of NodeManager instances in the cluster reaches 500, the recommended JVM parameters for NodeManager instances are as follows: -Xms8G -Xmx8G -XX:NewSize=1G -XX:MaxNewSize=2G

                                                5. Save the configuration and restart the NodeManager instance.
                                                6. Check whether the alarm is cleared.

                                                  • If yes, no further action is required.
                                                  • If no, go to 7.

                                                Collect fault information.

                                                -
                                                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                2. Select NodeManager in the required cluster from the Service.
                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                4. Contact the O&M personnel and send the collected logs.
                                                +
                                                1. On the MRS Manager portal, choose O&M > Log > Download.
                                                2. Select NodeManager in the required cluster from the Service.
                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                4. Contact the O&M personnel and send the collected logs.

                                                Alarm Clearing

                                                After the fault is rectified, the system automatically clears this alarm.

                                                diff --git a/docs/mrs/umn/ALM-18012.html b/docs/mrs/umn/ALM-18012.html index 38749f7d..8abafe04 100644 --- a/docs/mrs/umn/ALM-18012.html +++ b/docs/mrs/umn/ALM-18012.html @@ -65,14 +65,14 @@

                                                Possible Causes

                                                The heap memory of the JobHistoryServer instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                                Procedure

                                                Check the GC duration.

                                                -
                                                1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18012 JobHistoryServer GC Time Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance > JobHistoryServer (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection (GC) Time of the JobHistoryServer to check the GC duration statistics of the Broker process collected every minute.
                                                3. Check whether the GC duration of the JobHistoryServer process collected every minute exceeds the threshold (12 seconds by default).

                                                  • If yes, go to 4.
                                                  • If no, go to 7.
                                                  -

                                                4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Configurations > All Configurations > JobHistoryServer > System to increase the value of GC_OPTS parameter as required.

                                                  The mapping between the number of historical tasks (10000) and the memory of the JobHistoryServer is as follows:

                                                  +
                                                  1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18012 JobHistoryServer GC Time Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                  2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance > JobHistoryServer (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Garbage Collection (GC) Time of the JobHistoryServer to check the GC duration statistics of the Broker process collected every minute.
                                                  3. Check whether the GC duration of the JobHistoryServer process collected every minute exceeds the threshold (12 seconds by default).

                                                    • If yes, go to 4.
                                                    • If no, go to 7.
                                                    +

                                                  4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Configurations > All Configurations > JobHistoryServer > System to increase the value of GC_OPTS parameter as required.

                                                    The mapping between the number of historical tasks (10000) and the memory of the JobHistoryServer is as follows:

                                                    -Xms30G -Xmx30G -XX:NewSize=1G -XX:MaxNewSize=2G

                                                  5. Save the configuration and restart the JobHistoryServer instance.
                                                  6. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 7.

                                                  Collect fault information.

                                                  -
                                                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                  2. Select JobHistoryServer in the required cluster from the Service.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                  4. Contact the O&M personnel and send the collected logs.
                                                  +
                                                  1. On the MRS Manager portal, choose O&M > Log > Download.
                                                  2. Select JobHistoryServer in the required cluster from the Service.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                  4. Contact the O&M personnel and send the collected logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-18013.html b/docs/mrs/umn/ALM-18013.html index d4e5d23b..5ce9cc58 100644 --- a/docs/mrs/umn/ALM-18013.html +++ b/docs/mrs/umn/ALM-18013.html @@ -65,13 +65,13 @@

                                                  Possible Causes

                                                  The direct memory of the ResourceManager instance is overused or the direct memory is inappropriately allocated.

                                                  Procedure

                                                  Check the direct memory usage.

                                                  -
                                                  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18013 ResourceManager Direct Memory Usage Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Memory Usage Status of ResourceManager to check the direct memory usage.
                                                  3. Check whether the used direct memory of ResourceManager reaches 90% of the maximum direct memory specified for ResourceManager by default.

                                                    • If yes, go to 4.
                                                    • If no, go to 9.
                                                    -

                                                  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System to increase the value of check whether -XX:MaxDirectMemorySize exists in the GC_OPTS parameter.

                                                    • If yes, go to 5.
                                                    • If no, go to 7.
                                                    +
                                                    1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18013 ResourceManager Direct Memory Usage Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                    2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Memory Usage Status of ResourceManager to check the direct memory usage.
                                                    3. Check whether the used direct memory of ResourceManager reaches 90% of the maximum direct memory specified for ResourceManager by default.

                                                      • If yes, go to 4.
                                                      • If no, go to 9.
                                                      +

                                                    4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System to increase the value of check whether -XX:MaxDirectMemorySize exists in the GC_OPTS parameter.

                                                      • If yes, go to 5.
                                                      • If no, go to 7.

                                                    5. In the GC_OPTS parameter, delete -XX:MaxDirectMemorySize.
                                                    6. Save the configuration and restart the ResourceManager instance.
                                                    7. Check whether the ALM-18008 Heap Memory Usage of ResourceManager Exceeds the Threshold exists.

                                                      • If yes, handle the alarm by referring to ALM-18008 Heap Memory Usage of ResourceManager Exceeds the Threshold.
                                                      • If no, go to 8.

                                                    8. Check whether the alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 9.

                                                    Collect fault information.

                                                    -
                                                    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                    2. Select ResourceManager in the required cluster from the Service.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected logs.
                                                    +
                                                    1. On the MRS Manager portal, choose O&M > Log > Download.
                                                    2. Select ResourceManager in the required cluster from the Service.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-18014.html b/docs/mrs/umn/ALM-18014.html index 3d5e4fd6..72f1275c 100644 --- a/docs/mrs/umn/ALM-18014.html +++ b/docs/mrs/umn/ALM-18014.html @@ -65,13 +65,13 @@

                                                  Possible Causes

                                                  The direct memory of the NodeManager instance is overused or the direct memory is inappropriately allocated.

                                                  Procedure

                                                  Check the direct memory usage.

                                                  -
                                                  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18014 NodeManager Direct Memory Usage Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource > Percentage of Used Memory of the NodeManager to check the direct memory usage.
                                                  3. Check whether the used direct memory of NodeManager reaches 90% of the maximum direct memory specified for NodeManager by default.

                                                    • If yes, go to 4.
                                                    • If no, go to 9.
                                                    -

                                                  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations> NodeManager > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

                                                    • If yes, go to 5.
                                                    • If no, go to 7.
                                                    +
                                                    1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18014 NodeManager Direct Memory Usage Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                    2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource > Percentage of Used Memory of the NodeManager to check the direct memory usage.
                                                    3. Check whether the used direct memory of NodeManager reaches 90% of the maximum direct memory specified for NodeManager by default.

                                                      • If yes, go to 4.
                                                      • If no, go to 9.
                                                      +

                                                    4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations> NodeManager > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

                                                      • If yes, go to 5.
                                                      • If no, go to 7.

                                                    5. In the GC_OPTS parameter, delete "-XX:MaxDirectMemorySize".
                                                    6. Save the configuration and restart the NodeManager instance.
                                                    7. Check whether the ALM-18018 NodeManager Heap Memory Usage Exceeds the Threshold exists.

                                                      • If yes, handle the alarm by referring to ALM-18018 NodeManager Heap Memory Usage Exceeds the Threshold.
                                                      • If no, go to 8.

                                                    8. Check whether the alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 9.

                                                    Collect fault information.

                                                    -
                                                    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                    2. Select NodeManager in the required cluster from the Service.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected logs.
                                                    +
                                                    1. On the MRS Manager portal, choose O&M > Log > Download.
                                                    2. Select NodeManager in the required cluster from the Service.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-18015.html b/docs/mrs/umn/ALM-18015.html index 975303c8..09586ff5 100644 --- a/docs/mrs/umn/ALM-18015.html +++ b/docs/mrs/umn/ALM-18015.html @@ -65,13 +65,13 @@

                                                  Possible Causes

                                                  The direct memory of the JobHistoryServer instance is overused or the direct memory is inappropriately allocated.

                                                  Procedure

                                                  Check the direct memory usage.

                                                  -
                                                  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance > JobHistoryServer (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Memory Usage Status of JobHistoryServer to check the direct memory usage.
                                                  3. Check whether the used direct memory of JobHistoryServer reaches 90% of the maximum direct memory specified for JobHistoryServer by default.

                                                    • If yes, go to 4.
                                                    • If no, go to 9.
                                                    -

                                                  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Configurations > All Configurations > JobHistoryServer > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

                                                    • If yes, go to 5.
                                                    • If no, go to 7.
                                                    +
                                                    1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
                                                    2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance > JobHistoryServer (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Memory Usage Status of JobHistoryServer to check the direct memory usage.
                                                    3. Check whether the used direct memory of JobHistoryServer reaches 90% of the maximum direct memory specified for JobHistoryServer by default.

                                                      • If yes, go to 4.
                                                      • If no, go to 9.
                                                      +

                                                    4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Configurations > All Configurations > JobHistoryServer > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

                                                      • If yes, go to 5.
                                                      • If no, go to 7.

                                                    5. In the GC_OPTS parameter, delete "-XX:MaxDirectMemorySize".
                                                    6. Save the configuration and restart the JobHistoryServer instance.
                                                    7. Check whether the ALM-18009 Heap Memory Usage of JobHistoryServer Exceeds the Threshold exists.

                                                      • If yes, handle the alarm by referring to ALM-18009 Heap Memory Usage of JobHistoryServer Exceeds the Threshold.
                                                      • If no, go to 8.

                                                    8. Check whether the alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 9.

                                                    Collect fault information.

                                                    -
                                                    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                    2. Select JobHistoryServer in the required cluster from the Service.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected logs.
                                                    +
                                                    1. On the MRS Manager portal, choose O&M > Log > Download.
                                                    2. Select JobHistoryServer in the required cluster from the Service.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-18016.html b/docs/mrs/umn/ALM-18016.html index b000ebfc..4778782c 100644 --- a/docs/mrs/umn/ALM-18016.html +++ b/docs/mrs/umn/ALM-18016.html @@ -66,14 +66,14 @@

                                                  Possible Causes

                                                  The Non Heap memory of the Yarn ResourceManager instance on the node is overused or the Non Heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

                                                  Procedure

                                                  Check the Non Heap memory usage.

                                                  -
                                                  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18016 Non Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager. Click the drop-down menu in the upper right corner of Chart, choose Customize > Percentage of Used Memory of the ResourceManager. ResourceManager indicates the corresponding HostName of the instance for which the alarm is generated. Check the Non Heap memory usage.
                                                  3. Check whether the used Non Heap memory of ResourceManager reaches 90% of the maximum Non Heap memory specified for ResourceManager by default.

                                                    • If yes, go to 4.
                                                    • If no, go to 6.
                                                    -

                                                  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System. Adjust the GC_OPTS memory parameter of ResourceManager. Save the configuration and restart the ResourceManager instance.

                                                    The mapping between the number of NodeManager instances in a cluster and the memory size of ResourceManager is as follows:

                                                    +
                                                    1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18016 Non Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                    2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > ResourceManager. Click the drop-down menu in the upper right corner of Chart, choose Customize > Percentage of Used Memory of the ResourceManager. ResourceManager indicates the corresponding HostName of the instance for which the alarm is generated. Check the Non Heap memory usage.
                                                    3. Check whether the used Non Heap memory of ResourceManager reaches 90% of the maximum Non Heap memory specified for ResourceManager by default.

                                                      • If yes, go to 4.
                                                      • If no, go to 6.
                                                      +

                                                    4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > ResourceManager > System. Adjust the GC_OPTS memory parameter of ResourceManager. Save the configuration and restart the ResourceManager instance.

                                                      The mapping between the number of NodeManager instances in a cluster and the memory size of ResourceManager is as follows:

                                                      • If the number of NodeManager instances in the cluster reaches 100, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                      • If the number of NodeManager instances in the cluster reaches 200, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms6G -Xmx6G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                      • If the number of NodeManager instances in the cluster reaches 500, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms10G -Xmx10G -XX:NewSize=1G -XX:MaxNewSize=2G
                                                      • If the number of NodeManager instances in the cluster reaches 1000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms20G -Xmx20G -XX:NewSize=1G -XX:MaxNewSize=2G
                                                      • If the number of NodeManager instances in the cluster reaches 2000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms40G -Xmx40G -XX:NewSize=2G -XX:MaxNewSize=4G
                                                      • If the number of NodeManager instances in the cluster reaches 3000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms60G -Xmx60G -XX:NewSize=2G -XX:MaxNewSize=4G
                                                      • If the number of NodeManager instances in the cluster reaches 4000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms80G -Xmx80G -XX:NewSize=2G -XX:MaxNewSize=4G
                                                      • If the number of NodeManager instances in the cluster reaches 5000, the recommended JVM parameters of the ResourceManager instance are as follows: -Xms100G -Xmx100G -XX:NewSize=3G -XX:MaxNewSize=6G

                                                    5. Check whether the alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 6.

                                                    Collect fault information.

                                                    -
                                                    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                    2. Select the following node in the required cluster from the Service.

                                                      • NodeAgent
                                                      • Yarn
                                                      +
                                                      1. On the MRS Manager portal, choose O&M > Log > Download.
                                                      2. Select the following node in the required cluster from the Service.

                                                        • NodeAgent
                                                        • Yarn

                                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                      4. Contact the O&M personnel and send the collected logs.

                                                    Alarm Clearing

                                                    After the fault is rectified, the system automatically clears this alarm.

                                                    diff --git a/docs/mrs/umn/ALM-18017.html b/docs/mrs/umn/ALM-18017.html index fae66cc2..06c79690 100644 --- a/docs/mrs/umn/ALM-18017.html +++ b/docs/mrs/umn/ALM-18017.html @@ -66,14 +66,14 @@

                                                    Possible Causes

                                                    The Non Heap memory of the Yarn NodeManager instance on the node is overused or the Non Heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

                                                    Procedure

                                                    Check the Non Heap memory usage.

                                                    -
                                                    1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18017 Non Heap Memory Usage of Yarn NodeManager Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                    2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager. Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource > Percentage of Used Memory of the NodeManager. NodeManager indicates the corresponding HostName of the instance for which the alarm is generated. Check the Non Heap memory usage.
                                                    3. Check whether the used Non Heap memory of NodeManager reaches 90% of the maximum Non Heap memory specified for NodeManager by default.

                                                      • If yes, go to 4.
                                                      • If no, go to 6.
                                                      -

                                                    4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > NodeManager > System. Adjust the GC_OPTS memory parameter of NodeManager, click Save, and click OK, and restart the role instance.

                                                      The mapping between the number of NodeManager instances in a cluster and the memory size of NodeManager is as follows:

                                                      +
                                                      1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18017 Non Heap Memory Usage of Yarn NodeManager Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                      2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager. Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource > Percentage of Used Memory of the NodeManager. NodeManager indicates the corresponding HostName of the instance for which the alarm is generated. Check the Non Heap memory usage.
                                                      3. Check whether the used Non Heap memory of NodeManager reaches 90% of the maximum Non Heap memory specified for NodeManager by default.

                                                        • If yes, go to 4.
                                                        • If no, go to 6.
                                                        +

                                                      4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > NodeManager > System. Adjust the GC_OPTS memory parameter of NodeManager, click Save, and click OK, and restart the role instance.

                                                        The mapping between the number of NodeManager instances in a cluster and the memory size of NodeManager is as follows:

                                                        • If the number of NodeManager instances in the cluster reaches 100, the recommended JVM parameters for NodeManager instances are as follows: -Xms2G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                        • If the number of NodeManager instances in the cluster reaches 200, the recommended JVM parameters for NodeManager instances are as follows: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                        • If the number of NodeManager instances in the cluster reaches 500, the recommended JVM parameters for NodeManager instances are as follows: -Xms8G -Xmx8G -XX:NewSize=1G -XX:MaxNewSize=2G

                                                      5. Check whether the alarm is cleared.

                                                        • If yes, no further action is required.
                                                        • If no, go to 6.

                                                      Collect fault information.

                                                      -
                                                      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                      2. Select the following node in the required cluster from the Service.

                                                        • NodeAgent
                                                        • Yarn
                                                        +
                                                        1. On the MRS Manager portal, choose O&M > Log > Download.
                                                        2. Select the following node in the required cluster from the Service.

                                                          • NodeAgent
                                                          • Yarn

                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                        4. Contact the O&M personnel and send the collected logs.

                                                      Alarm Clearing

                                                      After the fault is rectified, the system automatically clears this alarm.

                                                      diff --git a/docs/mrs/umn/ALM-18018.html b/docs/mrs/umn/ALM-18018.html index f84d3c9c..4c67356e 100644 --- a/docs/mrs/umn/ALM-18018.html +++ b/docs/mrs/umn/ALM-18018.html @@ -65,14 +65,14 @@

                                                      Possible Causes

                                                      The heap memory of the Yarn NodeManager instance on the node is overused or the heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

                                                      Procedure

                                                      Check the heap memory usage.

                                                      -
                                                      1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18018 NodeManager Heap Memory Usage Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                      2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager. Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource > Percentage of Used Memory of the NodeManager to check the heap memory usage.
                                                      3. Check whether the used heap memory of NodeManager reaches 95% of the maximum heap memory specified for NodeManager.

                                                        • If yes, go to 4.
                                                        • If no, go to 6.
                                                        -

                                                      4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > NodeManager > System. Increase the value of GC_OPTS parameter as required, click Save, and click OK, and restart the role instance.

                                                        The mapping between the number of NodeManager instances in a cluster and the memory size of NodeManager is as follows:

                                                        +
                                                        1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18018 NodeManager Heap Memory Usage Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                        2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Instance > NodeManager. Click the drop-down menu in the upper right corner of Chart, choose Customize > Resource > Percentage of Used Memory of the NodeManager to check the heap memory usage.
                                                        3. Check whether the used heap memory of NodeManager reaches 95% of the maximum heap memory specified for NodeManager.

                                                          • If yes, go to 4.
                                                          • If no, go to 6.
                                                          +

                                                        4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations > NodeManager > System. Increase the value of GC_OPTS parameter as required, click Save, and click OK, and restart the role instance.

                                                          The mapping between the number of NodeManager instances in a cluster and the memory size of NodeManager is as follows:

                                                          • If the number of NodeManager instances in the cluster reaches 100, the recommended JVM parameters for NodeManager instances are as follows: -Xms2G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                          • If the number of NodeManager instances in the cluster reaches 200, the recommended JVM parameters for NodeManager instances are as follows: -Xms4G -Xmx4G -XX:NewSize=512M -XX:MaxNewSize=1G
                                                          • If the number of NodeManager instances in the cluster reaches 500, the recommended JVM parameters for NodeManager instances are as follows: -Xms8G -Xmx8G -XX:NewSize=1G -XX:MaxNewSize=2G

                                                        5. Check whether the alarm is cleared.

                                                          • If yes, no further action is required.
                                                          • If no, go to 6.

                                                        Collect fault information.

                                                        -
                                                        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                        2. Select the following node in the required cluster from the Service.

                                                          • NodeAgent
                                                          • Yarn
                                                          +
                                                          1. On the MRS Manager portal, choose O&M > Log > Download.
                                                          2. Select the following node in the required cluster from the Service.

                                                            • NodeAgent
                                                            • Yarn

                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          4. Contact the O&M personnel and send the collected logs.

                                                        Alarm Clearing

                                                        After the fault is rectified, the system automatically clears this alarm.

                                                        diff --git a/docs/mrs/umn/ALM-18019.html b/docs/mrs/umn/ALM-18019.html index 642b9219..a1b99356 100644 --- a/docs/mrs/umn/ALM-18019.html +++ b/docs/mrs/umn/ALM-18019.html @@ -66,14 +66,14 @@

                                                        Possible Causes

                                                        The Non Heap memory of the MapReduce JobHistoryServer instance on the node is overused or the Non Heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

                                                        Procedure

                                                        Check the Non Heap memory usage.

                                                        -
                                                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18019 Non Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                        2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance > JobHistoryServer. Click the drop-down menu in the upper right corner of Chart, choose Customize > JobHistoryServer Non Heap memory usage statistics. JobHistoryServer indicates the corresponding HostName of the instance for which the alarm is generated. Check the Non Heap memory usage.
                                                        3. Check whether the used Non Heap memory of JobHistoryServer reaches 90% of the maximum Non Heap memory specified for JobHistoryServer.

                                                          • If yes, go to 4.
                                                          • If no, go to 6.
                                                          -

                                                        4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Configurations > All Configurations > JobHistoryServer > System. Adjust the GC_OPTS memory parameter of the NodeManager, click Save, and click OK, and restart the role instance.

                                                          The mapping between the number of historical tasks (10000) and the memory of the JobHistoryServer is as follows:

                                                          +
                                                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms > ALM-18019 Non Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold > Location. Check the HostName of the instance for which the alarm is generated.
                                                          2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance > JobHistoryServer. Click the drop-down menu in the upper right corner of Chart, choose Customize > JobHistoryServer Non Heap memory usage statistics. JobHistoryServer indicates the corresponding HostName of the instance for which the alarm is generated. Check the Non Heap memory usage.
                                                          3. Check whether the used Non Heap memory of JobHistoryServer reaches 90% of the maximum Non Heap memory specified for JobHistoryServer.

                                                            • If yes, go to 4.
                                                            • If no, go to 6.
                                                            +

                                                          4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Configurations > All Configurations > JobHistoryServer > System. Adjust the GC_OPTS memory parameter of the NodeManager, click Save, and click OK, and restart the role instance.

                                                            The mapping between the number of historical tasks (10000) and the memory of the JobHistoryServer is as follows:

                                                            -Xms30G -Xmx30G -XX:NewSize=1G -XX:MaxNewSize=2G

                                                          5. Check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.

                                                          Collect fault information.

                                                          -
                                                          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                                          2. Select the following node in the required cluster from the Service.

                                                            • NodeAgent
                                                            • MapReduce
                                                            +
                                                            1. On the MRS Manager portal, choose O&M > Log > Download.
                                                            2. Select the following node in the required cluster from the Service.

                                                              • NodeAgent
                                                              • MapReduce

                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact the O&M personnel and send the collected logs.

                                                          Alarm Clearing

                                                          After the fault is rectified, the system automatically clears this alarm.

                                                          diff --git a/docs/mrs/umn/ALM-18020.html b/docs/mrs/umn/ALM-18020.html index 40801cd0..aeb36fad 100644 --- a/docs/mrs/umn/ALM-18020.html +++ b/docs/mrs/umn/ALM-18020.html @@ -65,19 +65,19 @@

                                                          Possible Causes

                                                          • The specified timeout duration is shorter than the required execution time.
                                                          • The queue resources for task running are insufficient.
                                                          • Task data skew occurs. As a result, some tasks process a large amount of data and take a long time to execute.

                                                          Procedure

                                                          Check whether the timeout interval is correctly set.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. The Alarms page is displayed.
                                                          2. Select the alarm whose ID is 18020. In the alarm details, view Location to obtain the timeout task name and timeout duration.
                                                          3. Based on the task name and timeout interval, choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager (Active) to log in to the native Yarn page. Then find the task on the native page, check its StartTime and calculate the task execution time based on the current system time. Check whether the task execution time exceeds the timeout duration.

                                                            • If yes, go to 4.
                                                            • If no, go to 10.
                                                            +
                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms. The Alarms page is displayed.
                                                            2. Select the alarm whose ID is 18020. In the alarm details, view Location to obtain the timeout task name and timeout duration.
                                                            3. Based on the task name and timeout interval, choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager (Active) to log in to the native Yarn page. Then find the task on the native page, check its StartTime and calculate the task execution time based on the current system time. Check whether the task execution time exceeds the timeout duration.

                                                              • If yes, go to 4.
                                                              • If no, go to 10.

                                                            4. Evaluate the expected task execution time based on the service and compare it with the task timeout interval. If the timeout interval is too short, set the timeout interval (mapreduce.application.timeout.alarm or spark.application.timeout.alarm) of the client to the task expected execution time. Run the task again and check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 5.

                                                            Check whether the queue resources are sufficient.

                                                            1. Find the task on the native page and view the queue name of the task. Click Scheduler on the left of the native page. On the Applications Queues page, find the corresponding queue name and expand the queue details, as shown in the following figure.

                                                              -

                                                            2. Check whether the value of Used Resources in the queue details is approximately equal to the value of Max Resources, which indicates that the resources in the queue submitted by the task have been used up. If the queue resources are insufficient, choose Tenant Resources > Dynamic Resource Plan > Resource Distribution Policy on FusionInsight Manager and increase the value of Max Resources for the queue. Run the task again and check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 7.
                                                              +

                                                            3. Check whether the value of Used Resources in the queue details is approximately equal to the value of Max Resources, which indicates that the resources in the queue submitted by the task have been used up. If the queue resources are insufficient, choose Tenant Resources > Dynamic Resource Plan > Resource Distribution Policy on MRS Manager and increase the value of Max Resources for the queue. Run the task again and check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 7.

                                                            Check whether data skew occurs.

                                                            1. On the native Yarn page, click task ID (for example, application_1565337919723_0002) > Tracking URL:ApplicationMaster > job_1565337919723_0002. The following page is displayed.

                                                            2. Choose Job > Map tasks or Job > Reduce tasks on the left and check whether the execution time of each Map or Reduce task differs greatly. If yes, task data skew occurs. In this case, you need to balance the task data.
                                                            3. Rectify the fault based on the preceding causes and perform the tasks again. Then, check whether the alarm persists.

                                                              • If yes, go to 10.
                                                              • If no, no further action is required.

                                                            Collect the fault information.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.
                                                            +
                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.

                                                          Alarm Clearing

                                                          This alarm is automatically cleared after the fault is rectified.

                                                          diff --git a/docs/mrs/umn/ALM-18021.html b/docs/mrs/umn/ALM-18021.html index 9a8c892e..7e56b64b 100644 --- a/docs/mrs/umn/ALM-18021.html +++ b/docs/mrs/umn/ALM-18021.html @@ -60,26 +60,26 @@

                                                          Possible Causes

                                                          • The JobHistoryServer instance is abnormal.
                                                          • The KrbServer service is abnormal.
                                                          • The ZooKeeper service abnormal.
                                                          • The HDFS service abnormal.
                                                          • The Yarn service is abnormal.

                                                          Procedure

                                                          Check MapReduce service JobHistoryServer instance status.

                                                          -
                                                          1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance.
                                                          2. Check whether the running status of JobHistoryServer is Normal.

                                                            • If yes, go to 11.
                                                            • If no, go to 3.
                                                            +
                                                            1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance.
                                                            2. Check whether the running status of JobHistoryServer is Normal.

                                                              • If yes, go to 11.
                                                              • If no, go to 3.

                                                            Check the KrbServer service status.

                                                            -
                                                            1. In the alarm list on FusionInsight Manager, check whether ALM-25500 KrbServer Service Unavailable exists.

                                                              • If yes, go to 4.
                                                              • If no, go to 5.
                                                              +
                                                              1. In the alarm list on MRS Manager, check whether ALM-25500 KrbServer Service Unavailable exists.

                                                                • If yes, go to 4.
                                                                • If no, go to 5.

                                                              2. Rectify the fault by following the steps provided in ALM-25500 KrbServer Service Unavailable, and check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 5.

                                                              Check the ZooKeeper service.

                                                              -
                                                              1. In the alarm list on FusionInsight Manager, check whether ALM-13000 ZooKeeper Service Unavailable exists.

                                                                • If yes, go to 6.
                                                                • If no, go to 7.
                                                                +
                                                                1. In the alarm list on MRS Manager, check whether ALM-13000 ZooKeeper Service Unavailable exists.

                                                                  • If yes, go to 6.
                                                                  • If no, go to 7.

                                                                2. Rectify the fault by following the steps provided in ALM-13000 ZooKeeper Service Unavailable, and check whether the alarm is cleared.

                                                                  • If yes, no further action is required.
                                                                  • If no, go to 7.

                                                                Check the HDFS service status.

                                                                -
                                                                1. In the alarm list on FusionInsight Manager, check whether ALM-14000 HDFS Service Unavailable exists.

                                                                  • If yes, go to 8.
                                                                  • If no, go to 9.
                                                                  +
                                                                  1. In the alarm list on MRS Manager, check whether ALM-14000 HDFS Service Unavailable exists.

                                                                    • If yes, go to 8.
                                                                    • If no, go to 9.

                                                                  2. Rectify the fault by following the steps provided in ALM-14000 HDFS Service Unavailable, and check whether the alarm is cleared.

                                                                    • If yes, no further action is required.
                                                                    • If no, go to 9.

                                                                  Check the Yarn service status.

                                                                  -
                                                                  1. In the alarm list on FusionInsight Manager, check whether ALM-18000 Yarn Service Unavailable exists.

                                                                    • If yes, go to 10
                                                                    • If no, go to 11.
                                                                    +
                                                                    1. In the alarm list on MRS Manager, check whether ALM-18000 Yarn Service Unavailable exists.

                                                                      • If yes, go to 10
                                                                      • If no, go to 11.

                                                                    2. Rectify the fault by following the steps provided in ALM-18000 Yarn Service Unavailable, and check whether the alarm is cleared.

                                                                      • If yes, no further action is required.
                                                                      • If no, go to 11.

                                                                    Collect fault information.

                                                                    -
                                                                    1. On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
                                                                    2. Select MapReduce in the required cluster from the Service.
                                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                    4. Contact the O&M personnel and send the collected logs.
                                                                    +
                                                                    1. On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
                                                                    2. Select MapReduce in the required cluster from the Service.
                                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                    4. Contact the O&M personnel and send the collected logs.

                                                          Alarm Clearing

                                                          After the fault is rectified, the system automatically clears this alarm.

                                                          diff --git a/docs/mrs/umn/ALM-18022.html b/docs/mrs/umn/ALM-18022.html index 5f43e515..92844818 100644 --- a/docs/mrs/umn/ALM-18022.html +++ b/docs/mrs/umn/ALM-18022.html @@ -60,8 +60,8 @@

                                                          Possible Causes

                                                          • NodeManager node resources are insufficient.
                                                          • The configured maximum resource capacity of the queue is excessively small.
                                                          • The configured maximum AM resource percentage is excessively small.

                                                          Procedure

                                                          View alarm details.

                                                          -
                                                          1. On the FusionInsight Manager, choose O&M > Alarm > Alarms.
                                                          2. View location information of this alarm and check whether QueueName is root and QueueMetric is Memory or QueueName is root and QueueMetric is vCores.

                                                            • If yes, go to 3.
                                                            • If no, go to 4.
                                                            -

                                                          1. The memory or CPU of the Yarn cluster is insufficient. In this case, log in to the node where NodeManager resides and run the free -g and cat /proc/cpuinfo commands to query the available memory and available CPU of the node, respectively. On FusionInsight Manager, increase the values of yarn.nodemanager.resource.memory-mb and yarn.nodemanager.resource.cpu-vcores for the Yarn NodeManager based on the query results. Then, restart the NodeManager instance. Check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 4.
                                                            +
                                                            1. On the MRS Manager, choose O&M > Alarm > Alarms.
                                                            2. View location information of this alarm and check whether QueueName is root and QueueMetric is Memory or QueueName is root and QueueMetric is vCores.

                                                              • If yes, go to 3.
                                                              • If no, go to 4.
                                                              +

                                                            1. The memory or CPU of the Yarn cluster is insufficient. In this case, log in to the node where NodeManager resides and run the free -g and cat /proc/cpuinfo commands to query the available memory and available CPU of the node, respectively. On MRS Manager, increase the values of yarn.nodemanager.resource.memory-mb and yarn.nodemanager.resource.cpu-vcores for the Yarn NodeManager based on the query results. Then, restart the NodeManager instance. Check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 4.

                                                            1. View location information of this alarm and check whether QueueName is <Tenant Queue> and QueueMetric is Memory, or QueueName is <Tenant Queue> and QueueMetric is vCores in Location, check whether available Memory = or available vCores = are included in Additional Information.

                                                              • If yes, go to 5.
                                                              • If no, go to 7.

                                                            1. The memory or CPU of the tenant queue is insufficient. In this case, choose Tenant Resources > Dynamic Resource Plan > Resource Distribution Policy and increase the value of Maximum Capacity. Then, check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 6.

                                                            1. Choose Cluster > Name of the desired cluster > Services > Yarn > Configurations > All Configurations. Enter the keyword "threshold" and click ResourceManager. Adjust the threshold values of the following parameters:

                                                              If Additional Information contains available Memory =, change the value of yarn.queue.memory.alarm.threshold to a value smaller than that of available Memory = in Additional Information.

                                                              @@ -75,7 +75,7 @@

                                                        Collect fault information.

                                                        -
                                                        1. Log in to FusionInsight Manager of the active cluster, and choose O&M > Log > Download.
                                                        2. Select Yarn in the required cluster from the Service.
                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                        4. Contact the O&M personnel and send the collected logs.
                                                        +
                                                        1. Log in to MRS Manager of the active cluster, and choose O&M > Log > Download.
                                                        2. Select Yarn in the required cluster from the Service.
                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                        4. Contact the O&M personnel and send the collected logs.

                                                        Alarm Clearing

                                                        After the fault is rectified, the system automatically clears this alarm.

                                                        diff --git a/docs/mrs/umn/ALM-18023.html b/docs/mrs/umn/ALM-18023.html index 4d2b22d2..4761a2b9 100644 --- a/docs/mrs/umn/ALM-18023.html +++ b/docs/mrs/umn/ALM-18023.html @@ -54,18 +54,18 @@

                                                        Possible Causes

                                                        • NodeManager node resources are insufficient.
                                                        • The maximum resource capacity of the queue and the maximum AM resource percentage are too small.
                                                        • The monitoring threshold is too small.

                                                        Procedure

                                                        Check NodeManager resources.

                                                        -
                                                        1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager (Active) to access the ResourceManager web UI.
                                                        2. Click Scheduler and check whether the root queue resources are used up in Application Queues.

                                                          • If yes, go to 3.
                                                          • If no, go to 4.
                                                          +
                                                          1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager (Active) to access the ResourceManager web UI.
                                                          2. Click Scheduler and check whether the root queue resources are used up in Application Queues.

                                                            • If yes, go to 3.
                                                            • If no, go to 4.

                                                          3. Expand the capacity of the NodeManager instance of the Yarn service. After the capacity expansion, check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.

                                                          Check the maximum queue resource capacity and the maximum AM resource percentage.

                                                          1. Check whether the resources of the queue corresponding to the pending task are used up.

                                                            • If yes, go to 5.
                                                            • If no, go to 6.
                                                            -

                                                          2. On FusionInsight Manager, choose Tenant Resources > Dynamic Resource Plan and add resources as required. Check whether the alarms are cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.
                                                            +

                                                          3. On MRS Manager, choose Tenant Resources > Dynamic Resource Plan and add resources as required. Check whether the alarms are cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.

                                                          Adjust the monitoring thresholds.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Yarn > Applications > Pending Applications, and increase the thresholds as required.
                                                          2. Check whether the alarm is cleared 5 minutes later.

                                                            • If yes, no further action is required.
                                                            • If no, go to 8.
                                                            +
                                                            1. On MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Yarn > Applications > Pending Applications, and increase the thresholds as required.
                                                            2. Check whether the alarm is cleared 5 minutes later.

                                                              • If yes, no further action is required.
                                                              • If no, go to 8.

                                                            Collect the fault information.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.
                                                            +
                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.

                                                        Alarm Clearing

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-18024.html b/docs/mrs/umn/ALM-18024.html index 09d68b73..11f9df2e 100644 --- a/docs/mrs/umn/ALM-18024.html +++ b/docs/mrs/umn/ALM-18024.html @@ -54,18 +54,18 @@

                                                        Possible Causes

                                                        • NodeManager node resources are insufficient.
                                                        • The maximum resource capacity of the queue and the maximum AM resource percentage are too small.
                                                        • The monitoring threshold is too small.

                                                        Procedure

                                                        Check NodeManager resources.

                                                        -
                                                        1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager (Active) to access the ResourceManager web UI.
                                                        2. Click Scheduler and check whether the root queue resources are used up in Application Queues.

                                                          • If yes, go to 3.
                                                          • If no, go to 4.
                                                          +
                                                          1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager (Active) to access the ResourceManager web UI.
                                                          2. Click Scheduler and check whether the root queue resources are used up in Application Queues.

                                                            • If yes, go to 3.
                                                            • If no, go to 4.

                                                          3. Expand the capacity of the NodeManager instance of the Yarn service. After the capacity expansion, check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.

                                                          Check the maximum queue resource capacity and the maximum AM resource percentage.

                                                          1. Check whether the resources of the queue corresponding to the pending task are used up.

                                                            • If yes, go to 5.
                                                            • If no, go to 6.
                                                            -

                                                          2. On FusionInsight Manager, choose Tenant Resources > Dynamic Resource Plan and add resources as required. Check whether the alarms are cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.
                                                            +

                                                          3. On MRS Manager, choose Tenant Resources > Dynamic Resource Plan and add resources as required. Check whether the alarms are cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.

                                                          Adjust the monitoring thresholds.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Yarn > CPU and Memory > Pending Memory, and increase the threshold as required.
                                                          2. Check whether the alarm is cleared 5 minutes later.

                                                            • If yes, no further action is required.
                                                            • If no, go to 8.
                                                            +
                                                            1. On MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Yarn > CPU and Memory > Pending Memory, and increase the threshold as required.
                                                            2. Check whether the alarm is cleared 5 minutes later.

                                                              • If yes, no further action is required.
                                                              • If no, go to 8.

                                                            Collect the fault information.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.
                                                            +
                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.

                                                        Alarm Clearing

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-18025.html b/docs/mrs/umn/ALM-18025.html index aad40a1f..9b9e4e8c 100644 --- a/docs/mrs/umn/ALM-18025.html +++ b/docs/mrs/umn/ALM-18025.html @@ -64,11 +64,11 @@

                                                        Possible Causes

                                                        • The user forcibly terminates a large number of tasks.
                                                        • The system terminates tasks due to some error.

                                                        Procedure

                                                        Check the alarm details.

                                                        -
                                                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms to go to the alarm page.
                                                        2. View Additional Information in the alarm details to check whether the alarm threshold is too small.

                                                          • If yes, go to 3.
                                                          • If no, go to 4.
                                                          +
                                                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms to go to the alarm page.
                                                          2. View Additional Information in the alarm details to check whether the alarm threshold is too small.

                                                            • If yes, go to 3.
                                                            • If no, go to 4.

                                                          3. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Yarn > Other > Terminated Applications of root queue to modify the threshold. Go to 6.
                                                          4. Choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager(Active) to access the ResourceManager web UI.
                                                          5. Click KILLED in Applications and click the task on the top. View the description of Diagnostics and rectify the fault based on the task termination details (for example, the task is terminated by a user).
                                                          6. Wait for 3 minutes and check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 7.

                                                          Collect the fault information.

                                                          -
                                                          1. On the FusionInsight Manager, choose O&M > Log > Download.
                                                          2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          4. Contact the O&M personnel and send the collected logs.
                                                          +
                                                          1. On the MRS Manager, choose O&M > Log > Download.
                                                          2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          4. Contact the O&M personnel and send the collected logs.

                                                        Alarm Clearing

                                                        After the fault is rectified, the system automatically clears this alarm.

                                                        diff --git a/docs/mrs/umn/ALM-18026.html b/docs/mrs/umn/ALM-18026.html index d40d7077..ae6030ac 100644 --- a/docs/mrs/umn/ALM-18026.html +++ b/docs/mrs/umn/ALM-18026.html @@ -64,11 +64,11 @@

                                                        Possible Causes

                                                        The task fails to be executed due to some error.

                                                        Procedure

                                                        Check the alarm details.

                                                        -
                                                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms to go to the alarm page.
                                                        2. View Additional Information in the alarm details to check whether the alarm threshold is too small.

                                                          • If yes, go to 3.
                                                          • If no, go to 4.
                                                          +
                                                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms to go to the alarm page.
                                                          2. View Additional Information in the alarm details to check whether the alarm threshold is too small.

                                                            • If yes, go to 3.
                                                            • If no, go to 4.

                                                          3. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Yarn > Other > Failed Applications of root queue to modify the threshold. Go to 6.
                                                          4. Choose Cluster > Name of the desired cluster > Services > Yarn > ResourceManager(Active) to access the ResourceManager web UI.
                                                          5. Click FAILED in Applications and click the task on the top. View the description of Diagnostics and rectify the fault based on the task failure causes.
                                                          6. Wait for 3 minutes and check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 7.

                                                          Collect the fault information.

                                                          -
                                                          1. On the FusionInsight Manager, choose O&M > Log > Download.
                                                          2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          4. Contact the O&M personnel and send the collected logs.
                                                          +
                                                          1. On the MRS Manager, choose O&M > Log > Download.
                                                          2. Expand the Service drop-down list, and select Yarn for the target cluster.
                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          4. Contact the O&M personnel and send the collected logs.

                                                        Alarm Clearing

                                                        After the fault is rectified, the system automatically clears this alarm.

                                                        diff --git a/docs/mrs/umn/ALM-19000.html b/docs/mrs/umn/ALM-19000.html index 5f57eb44..ede2477a 100644 --- a/docs/mrs/umn/ALM-19000.html +++ b/docs/mrs/umn/ALM-19000.html @@ -60,20 +60,20 @@

                                                        Possible Causes

                                                        • The ZooKeeper service is abnormal.
                                                        • The HDFS service is abnormal.
                                                        • The HBase service is abnormal.
                                                        • The network is abnormal.

                                                        Procedure

                                                        Check the ZooKeeper service status.

                                                        -
                                                        1. On the FusionInsight Manager, check whether the running status of ZooKeeper is Normal on service list.

                                                          • If yes, go to 5.
                                                          • If no, go to 2.
                                                          +
                                                          1. On the MRS Manager, check whether the running status of ZooKeeper is Normal on service list.

                                                            • If yes, go to 5.
                                                            • If no, go to 2.

                                                          2. In the alarm list, check whether ALM-13000 ZooKeeper Service Unavailable exists.

                                                            • If yes, go to 3.
                                                            • If no, go to 5.

                                                          3. Rectify the fault by following the steps provided in ALM-13000 ZooKeeper Service Unavailable.
                                                          4. Wait several minutes, and check whether alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 5.

                                                          Check the HDFS service status.

                                                          1. In the alarm list, check whether ALM-14000 HDFS Service Unavailable exists.

                                                            • If yes, go to 6.
                                                            • If no, go to 8.

                                                          2. Rectify the fault by following the steps provided in ALM-14000 HDFS Service Unavailable.
                                                          3. Wait several minutes, and check whether alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 8.
                                                            -

                                                          4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Check whether Safe Mode is ON.

                                                            • If yes, go to 9.
                                                            • If no, go to 12.
                                                            +

                                                          5. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS. Check whether Safe Mode is ON.

                                                            • If yes, go to 9.
                                                            • If no, go to 12.

                                                          6. Log in to the HDFS client as user root. Run cd to switch to the client installation directory, and run source bigdata_env.

                                                            If the cluster uses the security mode, perform security authentication. Obtain the password of user hdfs from the administrator, run the kinit hdfs command and enter the password as prompted.

                                                          7. Run the following command to manually exit the safe mode:

                                                            hdfs dfsadmin -safemode leave

                                                          8. Wait several minutes and check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 12.

                                                          Check the HBase service status.

                                                          -
                                                          1. On the FusionInsight Manager portal, click Cluster > Name of the desired cluster > Services > HBase.
                                                          2. Check whether there is one active HMaster and one standby HMaster.

                                                            • If yes, go to 15.
                                                            • If no, go to 14.
                                                            +
                                                            1. On the MRS Manager portal, click Cluster > Name of the desired cluster > Services > HBase.
                                                            2. Check whether there is one active HMaster and one standby HMaster.

                                                              • If yes, go to 15.
                                                              • If no, go to 14.

                                                            3. Click Instances, select the HMaster whose status is not Active, click More, and select Restart Instance to restart the HMaster. Check whether there is one active HMaster and one standby HMaster again.

                                                              • If yes, go to 15.
                                                              • If no, go to 21.

                                                            4. Choose Cluster >Name of the desired cluster > Services > HBase > HMaster(Active) to go to the HMaster WebUI.

                                                              By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                                                              @@ -91,15 +91,15 @@
                                                              • If yes, go to 20.
                                                              • If no, go to 21.

                                                            5. On the HMaster WebUI, check whether any hbase:meta is in the Region in Transition state for a long time.

                                                              Figure 4 Region in Transition
                                                              • If yes, go to 21.
                                                              • If no, go to 22.
                                                              -

                                                            6. In the precondition that services are not affected, log in to the FusionInsight Manager portal and choose Cluster > Name of the desired cluster > Services > HBase > More > Restart Service. Enter the administrator password and click OK.

                                                              • If yes, go to 22.
                                                              • If no, go to 23.
                                                              +

                                                            7. In the precondition that services are not affected, log in to the MRS Manager portal and choose Cluster > Name of the desired cluster > Services > HBase > More > Restart Service. Enter the administrator password and click OK.

                                                              • If yes, go to 22.
                                                              • If no, go to 23.

                                                            8. Wait several minutes and check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 23.

                                                            Check the network connection between HMaster and dependent components.

                                                            -
                                                            1. On the FusionInsight Manager, choose Cluster >Name of the desired cluster > Services > HBase.
                                                            2. Click Instance and the HMaster instance list is displayed. Record the management IP Address in the row of HMaster(Active).
                                                            3. Use the IP address obtained in 24 to log in to the host where the active HMaster runs as user omm .
                                                            4. Run the ping command to check whether communication between the host that runs the active HMaster and the hosts that run the dependent components. (The dependent components include ZooKeeper, HDFS and Yarn. Obtain the IP addresses of the hosts that run these services in the same way as that for obtaining the IP address of the active HMaster.)

                                                              • If yes, go to 29.
                                                              • If no, go to 27.
                                                              +
                                                              1. On the MRS Manager, choose Cluster >Name of the desired cluster > Services > HBase.
                                                              2. Click Instance and the HMaster instance list is displayed. Record the management IP Address in the row of HMaster(Active).
                                                              3. Use the IP address obtained in 24 to log in to the host where the active HMaster runs as user omm .
                                                              4. Run the ping command to check whether communication between the host that runs the active HMaster and the hosts that run the dependent components. (The dependent components include ZooKeeper, HDFS and Yarn. Obtain the IP addresses of the hosts that run these services in the same way as that for obtaining the IP address of the active HMaster.)

                                                                • If yes, go to 29.
                                                                • If no, go to 27.

                                                              5. Contact the administrator to restore the network.
                                                              6. In the alarm list, check whether HBase Service Unavailable is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 29.

                                                              Collect fault information.

                                                              -
                                                              1. On the FusionInsight Manager, choose O&M > Log > Download.
                                                              2. Select the following nodes in the required cluster from the Service drop-down list:

                                                                • ZooKeeper
                                                                • HDFS
                                                                • HBase
                                                                +
                                                                1. On the MRS Manager, choose O&M > Log > Download.
                                                                2. Select the following nodes in the required cluster from the Service drop-down list:

                                                                  • ZooKeeper
                                                                  • HDFS
                                                                  • HBase

                                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                4. Contact the O&M personnel and send the collected logs.

                                                        Alarm Clearing

                                                        After the fault is rectified, the system automatically clears this alarm.

                                                        diff --git a/docs/mrs/umn/ALM-19006.html b/docs/mrs/umn/ALM-19006.html index f634bee1..be694658 100644 --- a/docs/mrs/umn/ALM-19006.html +++ b/docs/mrs/umn/ALM-19006.html @@ -65,11 +65,11 @@

                                                        Possible Causes

                                                        • The HBase service on the standby cluster is abnormal.
                                                        • A network exception occurs.

                                                        Procedure

                                                        Observe whether the system automatically clears the alarm.

                                                        -
                                                        1. On the FusionInsight Manager portal of the active cluster, click O&M > Alarm > Alarms.
                                                        2. In the alarm list, click the alarm to obtain alarm generation time from Generated of the alarm. Check whether the alarm has existed for five minutes.

                                                          • If yes, go to 4.
                                                          • If no, go to 3.
                                                          +
                                                          1. On the MRS Manager portal of the active cluster, click O&M > Alarm > Alarms.
                                                          2. In the alarm list, click the alarm to obtain alarm generation time from Generated of the alarm. Check whether the alarm has existed for five minutes.

                                                            • If yes, go to 4.
                                                            • If no, go to 3.

                                                          3. Wait five minutes and check whether the system automatically clears the alarm.

                                                            • If yes, no further action is required.
                                                            • If no, go to 4.

                                                          Check the HBase service status of the standby cluster.

                                                          -
                                                          1. Log in to the FusionInsight Manager portal of the active cluster, and click O&M > Alarm > Alarms.
                                                          2. In the alarm list, click the alarm to obtain HostName from Location.
                                                          3. Access the node where the HBase client of the active cluster resides as user omm.

                                                            If the cluster uses a security mode, perform security authentication first and then access the hbase shell interface as user hbase.

                                                            +
                                                            1. Log in to the MRS Manager portal of the active cluster, and click O&M > Alarm > Alarms.
                                                            2. In the alarm list, click the alarm to obtain HostName from Location.
                                                            3. Access the node where the HBase client of the active cluster resides as user omm.

                                                              If the cluster uses a security mode, perform security authentication first and then access the hbase shell interface as user hbase.

                                                              cd /opt/client

                                                              source ./bigdata_env

                                                              kinit hbaseuser

                                                              @@ -82,16 +82,16 @@ SOURCE: PeerID=abc1, SizeOfLogQu abc1 10.10.10.110,10.10.10.119,10.10.10.133:2181:/hbase2 ENABLED abc 10.10.10.110,10.10.10.119,10.10.10.133:2181:/hbase ENABLED

                                                              In the preceding information, /hbase2 indicates that data is synchronized to the HBase2 instance of the standby cluster.

                                                              -

                                                            4. In the service list of FusionInsight Manager of the standby cluster, check whether the running status of the HBase instance obtained by using 9 is Normal.

                                                              • If yes, go to 14.
                                                              • If no, go to 11.
                                                              +

                                                            5. In the service list of MRS Manager of the standby cluster, check whether the running status of the HBase instance obtained by using 9 is Normal.

                                                              • If yes, go to 14.
                                                              • If no, go to 11.

                                                            6. In the alarm list, check whether the ALM-19000 HBase Service Unavailable alarm is generated.

                                                              • If yes, go to 12.
                                                              • If no, go to 14.

                                                            7. Follow troubleshooting procedures in ALM-19000 HBase Service Unavailable to rectify the fault.
                                                            8. Wait for a few minutes and check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 14.

                                                            Check network connections between RegionServers on active and standby clusters.

                                                            -
                                                            1. Log in to the FusionInsight Manager portal of the active cluster, and click O&M > Alarm > Alarms.
                                                            2. In the alarm list, click the alarm to obtain HostName from Location.
                                                            3. Use the IP address obtained in 15 to log in to a faulty RegionServer node as user omm.
                                                            4. Run the ping command to check whether network connections between the faulty RegionServer node and the host where RegionServer of the standby cluster resides are in the normal state.

                                                              • If yes, go to 20.
                                                              • If no, go to 18.
                                                              +
                                                              1. Log in to the MRS Manager portal of the active cluster, and click O&M > Alarm > Alarms.
                                                              2. In the alarm list, click the alarm to obtain HostName from Location.
                                                              3. Use the IP address obtained in 15 to log in to a faulty RegionServer node as user omm.
                                                              4. Run the ping command to check whether network connections between the faulty RegionServer node and the host where RegionServer of the standby cluster resides are in the normal state.

                                                                • If yes, go to 20.
                                                                • If no, go to 18.

                                                              5. Contact the network administrator to restore the network.
                                                              6. After the network is running properly, check whether the alarm is cleared in the alarm list.

                                                                • If yes, no further action is required.
                                                                • If no, go to 20.

                                                              Collect fault information.

                                                              -
                                                              1. On the FusionInsight Manager interface of active and standby clusters, choose O&M > Log > Download.
                                                              2. In the Service drop-down list box, select HBase in the required cluster.
                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              4. Contact the O&M personnel and send the collected fault logs.
                                                              +
                                                              1. On the MRS Manager interface of active and standby clusters, choose O&M > Log > Download.
                                                              2. In the Service drop-down list box, select HBase in the required cluster.
                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              4. Contact the O&M personnel and send the collected fault logs.

                                                        Alarm Clearing

                                                        After the fault is rectified, the system automatically clears this alarm.

                                                        diff --git a/docs/mrs/umn/ALM-19007.html b/docs/mrs/umn/ALM-19007.html index 93fac779..4e32e5de 100644 --- a/docs/mrs/umn/ALM-19007.html +++ b/docs/mrs/umn/ALM-19007.html @@ -1,7 +1,7 @@

                                                        ALM-19007 HBase GC Time Exceeds the Threshold

                                                        -

                                                        Description

                                                        The system checks the old generation garbage collection (GC) time of the HBase service every 60 seconds. This alarm is generated when the detected old generation GC time exceeds the threshold (exceeds 5 seconds for three consecutive checks by default). To change the threshold, on the FusionInsight Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HBase > GC > GC time for old generation. This alarm is cleared when the old generation GC time of the HBase service is shorter than or equal to the threshold.

                                                        +

                                                        Description

                                                        The system checks the old generation garbage collection (GC) time of the HBase service every 60 seconds. This alarm is generated when the detected old generation GC time exceeds the threshold (exceeds 5 seconds for three consecutive checks by default). To change the threshold, on the MRS Manager portal, choose O&M > Alarm > Thresholds > Name of the desired cluster > HBase > GC > GC time for old generation. This alarm is cleared when the old generation GC time of the HBase service is shorter than or equal to the threshold.

                                                        Attribute

            Table 1 DataNode JVM configuration

            Average Number of Blocks in a DataNode Instance

            Alarm ID

            @@ -59,19 +59,19 @@

            Possible Causes

            The memory of HBase instances is overused, the heap memory is inappropriately allocated, or a large number of I/O operations exist in HBase. As a result, GCs occur frequently.

            Procedure

            Check the GC time.

            -
            1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and select the alarm whose ID is 19007. Then check the role name in Location and confirm the IP adress of the instance.

              • If the role for which the alarm is generated is HMaster, go to 2.
              • If the role for which the alarm is generated is RegionServer, go to 3.
              -

            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the HMaster for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC > Garbage Collection (GC) Time of HMaster and click OK to check whether the value of GC time for old generation is greater than the threshold (exceeds 5 seconds for three consecutive checks periods by default).

              • If yes, go to 4.
              • If no, go to 6.
              -

            3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the RegionServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC > Garbage Collection (GC) Time of RegionServer and click OK to check whether the value of GC time for old generation is greater than the threshold (exceeds 5 seconds for three consecutive checks periods by default).

              • If yes, go to 4.
              • If no, go to 6.
              +
              1. On the MRS Manager portal, click O&M > Alarm > Alarms and select the alarm whose ID is 19007. Then check the role name in Location and confirm the IP adress of the instance.

                • If the role for which the alarm is generated is HMaster, go to 2.
                • If the role for which the alarm is generated is RegionServer, go to 3.
                +

              2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the HMaster for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC > Garbage Collection (GC) Time of HMaster and click OK to check whether the value of GC time for old generation is greater than the threshold (exceeds 5 seconds for three consecutive checks periods by default).

                • If yes, go to 4.
                • If no, go to 6.
                +

              3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the RegionServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC > Garbage Collection (GC) Time of RegionServer and click OK to check whether the value of GC time for old generation is greater than the threshold (exceeds 5 seconds for three consecutive checks periods by default).

                • If yes, go to 4.
                • If no, go to 6.

              Check the current JVM configuration.

              -
              1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Configurations, and click All Configurations. In Search, enter GC_OPTS to check the GC_OPTS memory parameter of role HMaster(HBase->HMaster), RegionServer(HBase->RegionServer). Adjust the values of -Xmx and -XX:CMSInitiatingOccupancyFraction of the GC_OPTS parameter by referring to the Note.

                1. Suggestions on GC parameter configurations for HMaster
                  • Set -Xms and -Xmx to the same value to prevent JVM from dynamically adjusting the heap memory size and affecting performance.
                  • Set -XX:NewSize to the value of -XX:MaxNewSize, which is one eighth of -Xmx.
                  • For large-scale HBase clusters with a large number of regions, increase values of GC_OPTS parameters for HMaster. Specifically, set -Xmx to 4 GB if the number of regions is less than 100,000. If the number of regions is more than 100,000, set -Xmx to be greater than or equal to 6 GB. For each increased 35,000 regions, increase the value of -Xmx by 2 GB. The maximum value of -Xmx is 32 GB.
                  +
                  1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Configurations, and click All Configurations. In Search, enter GC_OPTS to check the GC_OPTS memory parameter of role HMaster(HBase->HMaster), RegionServer(HBase->RegionServer). Adjust the values of -Xmx and -XX:CMSInitiatingOccupancyFraction of the GC_OPTS parameter by referring to the Note.

                    1. Suggestions on GC parameter configurations for HMaster
                      • Set -Xms and -Xmx to the same value to prevent JVM from dynamically adjusting the heap memory size and affecting performance.
                      • Set -XX:NewSize to the value of -XX:MaxNewSize, which is one eighth of -Xmx.
                      • For large-scale HBase clusters with a large number of regions, increase values of GC_OPTS parameters for HMaster. Specifically, set -Xmx to 4 GB if the number of regions is less than 100,000. If the number of regions is more than 100,000, set -Xmx to be greater than or equal to 6 GB. For each increased 35,000 regions, increase the value of -Xmx by 2 GB. The maximum value of -Xmx is 32 GB.
                    2. Suggestions on GC parameter configurations for RegionServer
                      • Set -Xms and -Xmx to the same value to prevent JVM from dynamically adjusting the heap memory size and affecting performance.
                      • Set -XX:NewSize to one eighth of -Xmx.
                      • Set the memory for RegionServer to be greater than that for HMaster. If sufficient memory is available, increase the heap memory.
                      • Set -Xmx based on the machine memory size. Specifically, set -Xmx to 32 GB if the machine memory is greater than 200 GB, to 16 GB if the machine memory is greater than 128 GB and less than 200 GB, and to 8 GB if the machine memory is less than 128 GB. When -Xmx is set to 32 GB, a RegionServer node supports 2000 regions and 200 hotspot regions.
                      • XX:CMSInitiatingOccupancyFraction to be less than and equal to 85, and it is calculated as follows: 100 x (hfile.block.cache.size + hbase.regionserver.global.memstore.size)

                  2. Check whether the alarm is cleared.

                    • If yes, no further action is required.
                    • If no, go to 6.

                  Collect fault information.

                  -
                  1. On the FusionInsight Manager interface of active and standby clusters, choose O&M > Log > Download.
                  2. In the Service drop-down list box, select HBase in the required cluster.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected fault logs.
                  +
                  1. On the MRS Manager interface of active and standby clusters, choose O&M > Log > Download.
                  2. In the Service drop-down list box, select HBase in the required cluster.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected fault logs.

                Alarm Clearing

                After the fault is rectified, the system automatically clears this alarm.

                diff --git a/docs/mrs/umn/ALM-19008.html b/docs/mrs/umn/ALM-19008.html index 18311246..67af799d 100644 --- a/docs/mrs/umn/ALM-19008.html +++ b/docs/mrs/umn/ALM-19008.html @@ -59,17 +59,17 @@

                Possible Causes

                The heap memory of the HBase service is overused or the heap memory is inappropriately allocated.

                Procedure

                Check heap memory usage.

                -
                1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and select the alarm whose ID is 19008. Then check the role name in Location and confirm the IP adress of the instance.

                  • If the role for which the alarm is generated is HMaster, go to 2.
                  • If the role for which the alarm is generated is RegionServer, go to 3.
                  -

                2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the HMaster for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > HMaster Heap Memory Usage and Direct Memory Usage Statistics and click OK, check whether the used heap memory of the HBase service reaches 90% of the maximum heap memory specified for HBase.

                  • If yes, go to 4.
                  • If no, go to 6.
                  -

                3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the RegionServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > RegionServer Heap Memory Usage and Direct Memory Usage Statistics and click OK, check whether the used heap memory of the HBase service reaches 90% of the maximum heap memory specified for HBase.

                  • If yes, go to 4.
                  • If no, go to 6.
                  -

                4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Configurations, and click All Configurations. Choose HMaster/RegionServer > System. Increase the value of -Xmx in GC_OPTS by referring to the Note.

                  1. Suggestions on GC parameter configurations for HMaster
                    • Set -Xms and -Xmx to the same value to prevent JVM from dynamically adjusting the heap memory size and affecting performance.
                    • Set -XX:NewSize to the value of -XX:MaxNewSize, which is one eighth of -Xmx.
                    • For large-scale HBase clusters with a large number of regions, increase values of GC_OPTS parameters for HMaster. Specifically, set -Xmx to 4 GB if the number of regions is less than 100,000. If the number of regions is more than 100,000, set -Xmx to be greater than or equal to 6 GB. For each increased 35,000 regions, increase the value of -Xmx by 2 GB. The maximum value of -Xmx is 32 GB.
                    +
                    1. On the MRS Manager portal, click O&M > Alarm > Alarms and select the alarm whose ID is 19008. Then check the role name in Location and confirm the IP adress of the instance.

                      • If the role for which the alarm is generated is HMaster, go to 2.
                      • If the role for which the alarm is generated is RegionServer, go to 3.
                      +

                    2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the HMaster for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > HMaster Heap Memory Usage and Direct Memory Usage Statistics and click OK, check whether the used heap memory of the HBase service reaches 90% of the maximum heap memory specified for HBase.

                      • If yes, go to 4.
                      • If no, go to 6.
                      +

                    3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the RegionServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > RegionServer Heap Memory Usage and Direct Memory Usage Statistics and click OK, check whether the used heap memory of the HBase service reaches 90% of the maximum heap memory specified for HBase.

                      • If yes, go to 4.
                      • If no, go to 6.
                      +

                    4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Configurations, and click All Configurations. Choose HMaster/RegionServer > System. Increase the value of -Xmx in GC_OPTS by referring to the Note.

                      1. Suggestions on GC parameter configurations for HMaster
                        • Set -Xms and -Xmx to the same value to prevent JVM from dynamically adjusting the heap memory size and affecting performance.
                        • Set -XX:NewSize to the value of -XX:MaxNewSize, which is one eighth of -Xmx.
                        • For large-scale HBase clusters with a large number of regions, increase values of GC_OPTS parameters for HMaster. Specifically, set -Xmx to 4 GB if the number of regions is less than 100,000. If the number of regions is more than 100,000, set -Xmx to be greater than or equal to 6 GB. For each increased 35,000 regions, increase the value of -Xmx by 2 GB. The maximum value of -Xmx is 32 GB.
                      2. Suggestions on GC parameter configurations for RegionServer
                        • Set -Xms and -Xmx to the same value to prevent JVM from dynamically adjusting the heap memory size and affecting performance.
                        • Set -XX:NewSize to one eighth of -Xmx.
                        • Set the memory for RegionServer to be greater than that for HMaster. If sufficient memory is available, increase the heap memory.
                        • Set -Xmx based on the machine memory size. Specifically, set -Xmx to 32 GB if the machine memory is greater than 200 GB, to 16 GB if the machine memory is greater than 128 GB and less than 200 GB, and to 8 GB if the machine memory is less than 128 GB. When -Xmx is set to 32 GB, a RegionServer node supports 2000 regions and 200 hotspot regions.

                    5. Check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 6.

                    Collect fault information.

                    -
                    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                    2. Select HBase in the required cluster from the Service drop-down list.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected fault logs.
                    +
                    1. On the MRS Manager portal, choose O&M > Log > Download.
                    2. Select HBase in the required cluster from the Service drop-down list.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected fault logs.

                  Alarm Clearing

                  After the fault is rectified, the system automatically clears this alarm.

                  diff --git a/docs/mrs/umn/ALM-19009.html b/docs/mrs/umn/ALM-19009.html index e2b6065f..bb8e1c7b 100644 --- a/docs/mrs/umn/ALM-19009.html +++ b/docs/mrs/umn/ALM-19009.html @@ -60,16 +60,16 @@

                  Possible Causes

                  The direct memory of the HBase service is overused or the direct memory is inappropriately allocated.

                  Procedure

                  Check direct memory usage.

                  -
                  1. On the FusionInsight Manager portal, click O&M > Alarm > Alarms and select the alarm whose ID is 19009. Check the RoleName in Location and confirm the IP address of HostName.

                    • If the role for which the alarm is generated is HMaster, go to 2.
                    • If the role for which the alarm is generated is RegionServer, go to 3.
                    -

                  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the HMaster for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > HMaster Heap Memory Usage and Direct Memory Usage Statistics and click OK to check whether the used direct memory of the HBase service reaches 90% of the maximum direct memory specified for HBase.

                    • If yes, go to 4.
                    • If no, go to 8.
                    -

                  3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the RegionServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > RegionServer Heap Memory Usage and Direct Memory Usage Statistics and click OK to check whether the used direct memory of the HBase service reaches 90% of the maximum direct memory specified for HBase.

                    • If yes, go to 4.
                    • If no, go to 8.
                    -

                  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Configurations, and click All Configurations. Choose HMaster/RegionServer > System and check whether XX:MaxDirectMemorySize exists in GC_OPTS.

                    • If yes, go to 5.
                    • If no, go to 6.
                    -

                  5. On the FusionInsight Manager portal, choose Cluster > Nameof the desired cluster > Services > HBase > Configurations, and click All Configurations. Choose HMaster/RegionServer > System and delete XX:MaxDirectMemorySize from GC_OPTS.
                  6. Check whether the ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold alarm is generated.

                    If yes, handle the alarm by referring to ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold.

                    +
                    1. On the MRS Manager portal, click O&M > Alarm > Alarms and select the alarm whose ID is 19009. Check the RoleName in Location and confirm the IP address of HostName.

                      • If the role for which the alarm is generated is HMaster, go to 2.
                      • If the role for which the alarm is generated is RegionServer, go to 3.
                      +

                    2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the HMaster for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > HMaster Heap Memory Usage and Direct Memory Usage Statistics and click OK to check whether the used direct memory of the HBase service reaches 90% of the maximum direct memory specified for HBase.

                      • If yes, go to 4.
                      • If no, go to 8.
                      +

                    3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Instance and click the RegionServer for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > CPU and Memory > RegionServer Heap Memory Usage and Direct Memory Usage Statistics and click OK to check whether the used direct memory of the HBase service reaches 90% of the maximum direct memory specified for HBase.

                      • If yes, go to 4.
                      • If no, go to 8.
                      +

                    4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > HBase > Configurations, and click All Configurations. Choose HMaster/RegionServer > System and check whether XX:MaxDirectMemorySize exists in GC_OPTS.

                      • If yes, go to 5.
                      • If no, go to 6.
                      +

                    5. On the MRS Manager portal, choose Cluster > Nameof the desired cluster > Services > HBase > Configurations, and click All Configurations. Choose HMaster/RegionServer > System and delete XX:MaxDirectMemorySize from GC_OPTS.
                    6. Check whether the ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold alarm is generated.

                      If yes, handle the alarm by referring to ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold.

                      If no, go to 8.

                    7. Check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 8.

                    Collect fault information.

                    -
                    1. On the FusionInsight Manager interface of active and standby clusters, choose O&M > Log > Download.
                    2. In the Service in the required cluster drop-down list box, select HBase.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected fault logs.
                    +
                    1. On the MRS Manager interface of active and standby clusters, choose O&M > Log > Download.
                    2. In the Service in the required cluster drop-down list box, select HBase.
                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    4. Contact the O&M personnel and send the collected fault logs.

                  Alarm Clearing

                  After the fault is rectified, the system automatically clears this alarm.

                  diff --git a/docs/mrs/umn/ALM-19011.html b/docs/mrs/umn/ALM-19011.html index 9cefc5bc..19823398 100644 --- a/docs/mrs/umn/ALM-19011.html +++ b/docs/mrs/umn/ALM-19011.html @@ -59,7 +59,7 @@

                  Possible Causes

                  • The RegionServer region distribution is unbalanced.
                  • The HBase cluster scale is too small.

                  Procedure

                  View alarm location information.

                  -
                  1. On the FusionInsight Manager home page, choose O&M > Alarm > Alarms, select this alarm, and view the service instance and host name in Location.
                  2. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services, click the HBase service instance for which the alarm is generated, and click HMaster(Active). On the displayed WebUI of the HBase instance, check whether the region distribution on the RegionServer is balanced.

                    By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                    +
                    1. On the MRS Manager home page, choose O&M > Alarm > Alarms, select this alarm, and view the service instance and host name in Location.
                    2. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services, click the HBase service instance for which the alarm is generated, and click HMaster(Active). On the displayed WebUI of the HBase instance, check whether the region distribution on the RegionServer is balanced.

                      By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                      • If yes, go to 9.
                      • If no, go to 3.
                      Figure 1 WebUI of HBase instance
                      @@ -75,29 +75,29 @@

                      balancer_enabled

                    3. On the HBase shell command window, run the balancer command to manually trigger the load balancing function.

                      You are advised to enable and manually trigger the load balancing function during off-peak hours.

                      -

                    4. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > HBase, and click HMaster(Active). On the displayed WebUI of the HBase instance, refresh the page and check whether the region distribution is balanced.

                      • If yes, go to 8.
                      • If no, go to 21.
                      +

                    5. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > HBase, and click HMaster(Active). On the displayed WebUI of the HBase instance, refresh the page and check whether the region distribution is balanced.

                      • If yes, go to 8.
                      • If no, go to 21.

                    6. Check whether the alarm is cleared.

                      • If yes, no further action is required.
                      • If no, go to 9.

                    Delete unwanted HBase tables.

                    Exercise caution when deleting data to ensure data is deleted correctly.

                    -
                    1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > HBase, and click HMaster(Active). On the displayed WebUI of the HBase instance, view tables stored in the HBase service instance and record unwanted tables that can be deleted.
                    2. On the HBase shell command window, run the disable command and drop command to delete the table to decrease the number of regions.

                      disable 'name of the table to be deleted'

                      +
                      1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > HBase, and click HMaster(Active). On the displayed WebUI of the HBase instance, view tables stored in the HBase service instance and record unwanted tables that can be deleted.
                      2. On the HBase shell command window, run the disable command and drop command to delete the table to decrease the number of regions.

                        disable 'name of the table to be deleted'

                        drop 'name of the table to be deleted'

                      3. On the HBase shell command window, run the following command to check whether the load balancing function is enabled.

                        balancer_enabled
                        • If yes, go to 13.
                        • If no, go to 12.

                      4. On the HBase shell command window, run the following commands to enable the load balancing function and confirm that the function is enabled.

                        balance_switch true

                        balancer_enabled

                        -

                      5. On the HBase shell command window, run the balancer command to manually trigger the load balancing function.
                      6. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > HBase, and click HMaster(Active). On the displayed WebUI of the HBase instance, refresh the page and check whether the region distribution is balanced.

                        • If yes, go to 15.
                        • If no, go to 21.
                        +

                      7. On the HBase shell command window, run the balancer command to manually trigger the load balancing function.
                      8. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > HBase, and click HMaster(Active). On the displayed WebUI of the HBase instance, refresh the page and check whether the region distribution is balanced.

                        • If yes, go to 15.
                        • If no, go to 21.

                      9. Check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 16.

                      Adjust the threshold.

                      -
                      1. On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > HBase > Regions(RegionServer), select the applied rule, and click Modify to check whether the threshold is proper.

                        • If it is excessively small, increase the threshold as required and go to 17.
                        • If it is proper, go to 18.
                        +
                        1. On the MRS Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > HBase > Regions(RegionServer), select the applied rule, and click Modify to check whether the threshold is proper.

                          • If it is excessively small, increase the threshold as required and go to 17.
                          • If it is proper, go to 18.

                        2. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 18.

                          Perform system capacity expansion.

                          -

                        3. Add nodes to the HBase cluster and add RegionServer instances to the nodes. Then enable and manually trigger the load balancing function.
                        4. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services, click the HBase service instance for which the alarm is generated, and click HMaster(Active). On the displayed WebUI of the HBase instance, refresh the page and check whether the region distribution is balanced.

                          • If yes, go to 20.
                          • If no, go to 21.
                          +

                        5. Add nodes to the HBase cluster and add RegionServer instances to the nodes. Then enable and manually trigger the load balancing function.
                        6. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services, click the HBase service instance for which the alarm is generated, and click HMaster(Active). On the displayed WebUI of the HBase instance, refresh the page and check whether the region distribution is balanced.

                          • If yes, go to 20.
                          • If no, go to 21.

                        7. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 21.

                          Collect fault information.

                          -

                        8. On the FusionInsight Manager home page of the active and standby clusters, choose O&M> Log > Download.
                        9. Select HBase in the required cluster from the Service.
                        10. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        11. Contact the O&M personnel and send the collected logs.
                        +

                      2. On the MRS Manager home page of the active and standby clusters, choose O&M> Log > Download.
                      3. Select HBase in the required cluster from the Service.
                      4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      5. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    diff --git a/docs/mrs/umn/ALM-19012.html b/docs/mrs/umn/ALM-19012.html index d0ce9e43..51385f91 100644 --- a/docs/mrs/umn/ALM-19012.html +++ b/docs/mrs/umn/ALM-19012.html @@ -61,11 +61,11 @@

                    Possible Causes

                    Files or directories on the HDFS are missing.

                    Procedure

                    Locate the alarm cause.

                    -
                    1. On the FusionInsight Manager, choose O&M > Alarm > Alarms. Click this alarm and check whether Alarm Cause indicates unknown errors.

                      • If yes, go to 4.
                      • If no, go to 2
                      -

                    2. On the FusionInsight Manager home page, choose O&M > Backup and Restoration > Backup Management. Check whether there are success records of the backup task named default or other HBase metadata backup tasks that have been successfully executed.

                      • If yes, go to 3.
                      • If no, go to 4.
                      +
                      1. On the MRS Manager, choose O&M > Alarm > Alarms. Click this alarm and check whether Alarm Cause indicates unknown errors.

                        • If yes, go to 4.
                        • If no, go to 2
                        +

                      2. On the MRS Manager home page, choose O&M > Backup and Restoration > Backup Management. Check whether there are success records of the backup task named default or other HBase metadata backup tasks that have been successfully executed.

                        • If yes, go to 3.
                        • If no, go to 4.

                      3. Use the latest backup metadata to restore the metadata of the HBase service.

                      Collect fault information.

                      -
                      1. On the FusionInsight Manager page of the active and standby clusters, choose O&M > Log > Download.
                      2. In the Service area, select faulty HBase services in the required cluster.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.
                      +
                      1. On the MRS Manager page of the active and standby clusters, choose O&M > Log > Download.
                      2. In the Service area, select faulty HBase services in the required cluster.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    diff --git a/docs/mrs/umn/ALM-19013.html b/docs/mrs/umn/ALM-19013.html index 31e7d6be..77c07006 100644 --- a/docs/mrs/umn/ALM-19013.html +++ b/docs/mrs/umn/ALM-19013.html @@ -59,7 +59,7 @@

                    Possible Causes

                    • Compaction is permanently blocked.
                    • The HDFS files are abnormal.

                    Procedure

                    Locate the alarm cause.

                    -
                    1. On the FusionInsight Manager, choose O&M > Alarm > Alarms, select this alarm, and view the HostName and RoleName in Location.
                    2. Choose Cluster > Name of the desired cluster > Services > HBase, Click the drop-down menu in the chartarea and choose Customize > Service >

                      Region in transaction count to view Region in transaction count over threshold. Check whether the monitoring item detects a value in three consecutive detection periods. (The default threshold is 60 seconds.)
                      • If yes, go to 3.
                      • If no, go to 7.
                      +
                      1. On the MRS Manager, choose O&M > Alarm > Alarms, select this alarm, and view the HostName and RoleName in Location.
                      2. Choose Cluster > Name of the desired cluster > Services > HBase, Click the drop-down menu in the chartarea and choose Customize > Service >

                        Region in transaction count to view Region in transaction count over threshold. Check whether the monitoring item detects a value in three consecutive detection periods. (The default threshold is 60 seconds.)
                        • If yes, go to 3.
                        • If no, go to 7.

                      3. Choose Cluster > Name of the desired cluster > Services > HBase > HMaster (Active) > Tables to check whether the regions of only one table transaction status time out.

                        • If yes, go to 4.
                        • If no, go to 7.

                      4. Run the hbase hbck command on the client and check whether the error message "No table descriptor file under hdfs://hacluster/hbase/data/default/table" is displayed.

                        • If yes, go to 5.
                        • If no, go to 7.
                        @@ -73,7 +73,7 @@

                      5. Repeat 4. Run the hbase hbck command on the client and check whether the error message "No table descriptor file under hdfs://hacluster/hbase/data/default/table" is displayed.

                        • If yes, go to 7.
                        • If no, no further action is required.

                      Collect fault information.

                      -
                      1. On the FusionInsight Manager page of the active and standby clusters, choose O&M > Log > Download.
                      2. In the Service area, select faulty HBase services in the required cluster.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.
                      +
                      1. On the MRS Manager page of the active and standby clusters, choose O&M > Log > Download.
                      2. In the Service area, select faulty HBase services in the required cluster.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.

                      Alarm Clearing

                      After the fault is rectified, the system automatically clears this alarm.

                      diff --git a/docs/mrs/umn/ALM-19014.html b/docs/mrs/umn/ALM-19014.html index 967bdf43..27f688a8 100644 --- a/docs/mrs/umn/ALM-19014.html +++ b/docs/mrs/umn/ALM-19014.html @@ -65,7 +65,7 @@

                      Possible Causes

                      • DR is configured for HBase, and data synchronization fails or is slow in DR.
                      • A large number of WAL files are being split in the HBase cluster.

                      Procedure

                      Check the capacity configuration and usage of ZNodes.

                      -
                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19014, and view the threshold in Additional Information.
                      2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                        cd Client installation directory

                        +
                        1. On MRS Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19014, and view the threshold in Additional Information.
                        2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                          cd Client installation directory

                          Run the following command to set environment variables:

                          source bigdata_env

                          If the cluster uses the security mode, run the following command to perform security authentication:

                          @@ -73,13 +73,13 @@

                          Enter the password as prompted (obtain the password from the MRS cluster administrator).

                        3. Run the hbase zkcli command to log in to the ZooKeeper client and run the listquota /hbase command to check the ZNode capacity quota of the HBase service. The ZNode root directory in the command is specified by the zookeeper.znode.parent parameter of the HBase service. The marked area in the following figure shows the capacity configuration of the root ZNode of the HBase service.

                        4. Run the getusage /hbase/splitWAL command to check the capacity usage of the ZNode. Check whether the ratio of Data size to the ZNode capacity quota is close to the alarm threshold.

                          • If yes, go to 5.
                          • If no, go to 6.
                          -

                        5. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 12007, 19000, or 19013 and the ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.
                          +

                        6. On MRS Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 12007, 19000, or 19013 and the ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.

                        7. Run the getusage /hbase/replication command to check the capacity usage of the ZNode. Check whether the ratio of Data size to the ZNode capacity quota is close to the alarm threshold.

                          • If yes, go to 7.
                          • If no, go to 9.
                          -

                        8. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.
                          +

                        9. On MRS Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.

                        10. Check whether the alarm is cleared five minutes later.

                          • If yes, no further action is required.
                          • If no, go to 9.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-19015.html b/docs/mrs/umn/ALM-19015.html index c7508e8f..3fd45d97 100644 --- a/docs/mrs/umn/ALM-19015.html +++ b/docs/mrs/umn/ALM-19015.html @@ -65,7 +65,7 @@

                      Possible Causes

                      • DR is configured for HBase, and data synchronization fails or is slow in DR.
                      • A large number of WAL files are being split in the HBase cluster.

                      Procedure

                      Check the quantity quota and usage of ZNodes.

                      -
                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19015, and view the threshold in Additional Information.
                      2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                        cd Client installation directory

                        +
                        1. On MRS Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19015, and view the threshold in Additional Information.
                        2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                          cd Client installation directory

                          Run the following command to set environment variables:

                          source bigdata_env

                          If the cluster uses the security mode, run the following command to perform security authentication:

                          @@ -73,13 +73,13 @@

                          Enter the password as prompted (obtain the password from the MRS cluster administrator).

                        3. Run the hbase zkcli command to log in to the ZooKeeper client and run the listquota /hbase command to check the ZNode quantity quota of the HBase service. The ZNode root directory in the command is specified by the zookeeper.znode.parent parameter of the HBase service. The marked area in the following figure shows the quantity quota configuration of the root ZNode of the HBase service.

                        4. Run the getusage /hbase/splitWAL command to check the ZNode quantity usage and check whether the ratio of Node count in the command output to the ZNode quantity quota is close to the alarm threshold.

                          • If yes, go to 5.
                          • If no, go to 6.
                          -

                        5. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 12007, 19000, or 19013 and the ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.
                          +

                        6. On MRS Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 12007, 19000, or 19013 and the ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.

                        7. Run the getusage /hbase/replication command to check the ZNode quantity usage and check whether the ratio of Node count in the command output to the ZNode quantity quota is close to the alarm threshold.

                          • If yes, go to 7.
                          • If no, go to 9.
                          -

                        8. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.
                          +

                        9. On MRS Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.

                        10. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 9.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-19016.html b/docs/mrs/umn/ALM-19016.html index 0116eaf4..3a7b0c65 100644 --- a/docs/mrs/umn/ALM-19016.html +++ b/docs/mrs/umn/ALM-19016.html @@ -65,7 +65,7 @@

                      Possible Causes

                      • DR is configured for HBase, and data synchronization fails or is slow in DR.
                      • A large number of WAL files are being split in the HBase cluster.

                      Procedure

                      Check the quantity quota and usage of ZNodes.

                      -
                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19016, and view the threshold in Additional Information.
                      2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                        cd Client installation directory

                        +
                        1. On MRS Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19016, and view the threshold in Additional Information.
                        2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                          cd Client installation directory

                          Run the following command to set environment variables:

                          source bigdata_env

                          If the cluster uses the security mode, run the following command to perform security authentication:

                          @@ -73,13 +73,13 @@

                          Enter the password as prompted (obtain the password from the MRS cluster administrator).

                        3. Run the hbase zkcli command to log in to the ZooKeeper client and run the listquota /hbase command to check the ZNode quantity quota of the HBase service. The ZNode root directory in the command is specified by the zookeeper.znode.parent parameter of the HBase service. The marked area in the following figure shows the quantity configuration of the root ZNode of the HBase service.

                        4. Run the getusage /hbase/splitWAL command to check the ZNode usage and check whether the ratio of Node count in the command output to the znode quantity quota is close to the alarm threshold.

                          • If yes, go to 5.
                          • If no, go to 6.
                          -

                        5. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 12007, 19000, or 19013 and the ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.
                          +

                        6. On MRS Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 12007, 19000, or 19013 and the ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.

                        7. Run the getusage /hbase/replication command to check the ZNode usage and check whether the ratio of Node count in the command output to the ZNode quantity quota is close to the alarm threshold.

                          • If yes, go to 7.
                          • If no, go to 9.
                          -

                        8. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.
                          +

                        9. On MRS Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.

                        10. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 9.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-19017.html b/docs/mrs/umn/ALM-19017.html index c83290ab..026d552d 100644 --- a/docs/mrs/umn/ALM-19017.html +++ b/docs/mrs/umn/ALM-19017.html @@ -65,7 +65,7 @@

                      Possible Causes

                      • DR is configured for HBase, and data synchronization fails or is slow in DR.
                      • A large number of WAL files are being split in the HBase cluster.

                      Procedure

                      Check the capacity configuration and usage of ZNodes.

                      -
                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19017, and view the threshold in Additional Information.
                      2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                        cd Client installation directory

                        +
                        1. On MRS Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19017, and view the threshold in Additional Information.
                        2. Log in to the HBase client as user root. Run the following command to go to the client installation directory:

                          cd Client installation directory

                          Run the following command to set environment variables:

                          source bigdata_env

                          If the cluster uses the security mode, run the following command to perform security authentication:

                          @@ -73,13 +73,13 @@

                          Enter the password as prompted (obtain the password from the MRS cluster administrator).

                        3. Run the hbase zkcli command to log in to the ZooKeeper client and run the listquota /hbase command to check the ZNode quantity quota of the HBase service. The ZNode root directory in the command is specified by the zookeeper.znode.parent parameter of the HBase service. The marked area in the following figure shows the quantity configuration of the root ZNode of the HBase service.

                        4. Run the getusage /hbase/splitWAL command to check the capacity usage of the ZNode. Check whether the ratio of Data size to the ZNode capacity quota is close to the alarm threshold.

                          • If yes, go to 5.
                          • If no, go to 6.
                          -

                        5. On FusionInsight Manager, check whether the alarm whose ID is 12007, 19000, or 19013 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 7.
                          +

                        6. On MRS Manager, check whether the alarm whose ID is 12007, 19000, or 19013 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 7.

                        7. Run the getusage /hbase/replication command to check the capacity usage of the ZNode. Check whether the ratio of Data size to the ZNode capacity quota is close to the alarm threshold.

                          • If yes, go to 7.
                          • If no, go to 9.
                          -

                        8. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.
                          +

                        9. On MRS Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
                          • If no, go to 9.

                        10. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 9.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-19018.html b/docs/mrs/umn/ALM-19018.html index 85c86b5e..54116309 100644 --- a/docs/mrs/umn/ALM-19018.html +++ b/docs/mrs/umn/ALM-19018.html @@ -59,11 +59,11 @@

                      Possible Causes

                      • The number of HBase RegionServers is too small.
                      • There are excessive regions on a single RegionServer of HBase.
                      • The HBase RegionServer heap size is small.
                      • Resources are insufficient.
                      • Related parameters are not configured properly.

                      Procedure

                      Check whether related parameters are properly configured.

                      -
                      1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. On the page that is displayed, check whether the alarm whose Alarm ID is 19008 or 19011 exists.

                        • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 3.
                        • If no, go to 2.
                        -

                      2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HBase. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, search for hbase.hstore.compaction.min, hbase.hstore.compaction.max, hbase.regionserver.thread.compaction.small, and hbase.regionserver.thread.compaction.throttle, and set them to larger values.
                      3. Check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 4.
                        +
                        1. Log in to MRS Manager and choose O&M > Alarm > Alarms. On the page that is displayed, check whether the alarm whose Alarm ID is 19008 or 19011 exists.

                          • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 3.
                          • If no, go to 2.
                          +

                        2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HBase. On the page that is displayed, click the Configuration tab then the All Configurations sub-tab, search for hbase.hstore.compaction.min, hbase.hstore.compaction.max, hbase.regionserver.thread.compaction.small, and hbase.regionserver.thread.compaction.throttle, and set them to larger values.
                        3. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 4.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-19019.html b/docs/mrs/umn/ALM-19019.html index 0a9dae73..6a1adff8 100644 --- a/docs/mrs/umn/ALM-19019.html +++ b/docs/mrs/umn/ALM-19019.html @@ -64,13 +64,13 @@

                      Possible Causes

                      • The network is abnormal.
                      • The RegionServer region distribution is unbalanced.
                      • The HBase service scale of the standby cluster is too small.

                      Procedure

                      View alarm location information.

                      -
                      1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 19019, and view the service instance and host name in Location.
                      +
                      1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 19019, and view the service instance and host name in Location.

                      Check the network connection between RegionServers on active and standby clusters.

                      1. Run the ping command to check whether the network connection between the faulty RegionServer node and the host where RegionServer of the standby cluster resides is normal.

                        • If yes, go to 5.
                        • If no, go to 3.
                        -

                      2. Contact the network administrator to restore the network.
                      3. After the network recovers, check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 5.
                        +

                      4. Contact the network administrator to restore the network.
                      5. After the network recovers, check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 5.

                      Check the RegionServer region distribution in the active cluster.

                      -
                      1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance and check whether regions are evenly distributed on the Region Server.
                      2. Log in to the faulty RegionServer node as user omm.
                      3. Run the following commands to go to the client installation directory and set the environment variable:

                        cd Client installation directory

                        +
                        1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance and check whether regions are evenly distributed on the Region Server.
                        2. Log in to the faulty RegionServer node as user omm.
                        3. Run the following commands to go to the client installation directory and set the environment variable:

                          cd Client installation directory

                          source bigdata_env

                          If the cluster uses the security mode, perform security authentication. Run the kinit hbase command and enter the password as prompted (obtain the password from the MRS cluster administrator).

                        4. Run the following commands to check whether the load balancing function is enabled.

                          hbase shell

                          @@ -83,11 +83,11 @@

                        5. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 12.

                        Check the HBase service scale of the standby cluster.

                        -
                        1. Expand the HBase cluster, add a node, and add a RegionServer instance on the node. Then, perform 6 to 10 to enable the load balancing function and manually trigger it.
                        2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance, refresh the page, and check whether regions are evenly distributed.

                          • If yes, go to 14.
                          • If no, go to 15.
                          +
                          1. Expand the HBase cluster, add a node, and add a RegionServer instance on the node. Then, perform 6 to 10 to enable the load balancing function and manually trigger it.
                          2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance, refresh the page, and check whether regions are evenly distributed.

                            • If yes, go to 14.
                            • If no, go to 15.

                          3. Check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 15.

                          Collect the fault information.

                          -
                          1. On FusionInsight Manager of the standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
                          2. Expand the Service drop-down list, and select HBase for the target cluster.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact O&M personnel and provide the collected logs.
                          +
                          1. On MRS Manager of the standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
                          2. Expand the Service drop-down list, and select HBase for the target cluster.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-19020.html b/docs/mrs/umn/ALM-19020.html index a4798b1f..8c3890e0 100644 --- a/docs/mrs/umn/ALM-19020.html +++ b/docs/mrs/umn/ALM-19020.html @@ -64,13 +64,13 @@

                      Possible Causes

                      • The network is abnormal.
                      • The RegionServer region distribution is unbalanced.
                      • The HBase service scale of the standby cluster is too small.

                      Procedure

                      View alarm location information.

                      -
                      1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 19020, and view the service instance and host name in Location.
                      +
                      1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 19020, and view the service instance and host name in Location.

                      Check the network connection between RegionServers on active and standby clusters.

                      1. Run the ping command to check whether the network connection between the faulty RegionServer node and the host where RegionServer of the standby cluster resides is normal.

                        • If yes, go to 5.
                        • If no, go to 3.
                        -

                      2. Contact the network administrator to restore the network.
                      3. After the network recovers, check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 5.
                        +

                      4. Contact the network administrator to restore the network.
                      5. After the network recovers, check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 5.

                      Check the RegionServer region distribution in the active cluster.

                      -
                      1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance and check whether regions are evenly distributed on the Region Server.
                      2. Log in to the faulty RegionServer node as user omm.
                      3. Run the following commands to go to the client installation directory and set the environment variable:

                        cd Client installation directory

                        +
                        1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance and check whether regions are evenly distributed on the Region Server.
                        2. Log in to the faulty RegionServer node as user omm.
                        3. Run the following commands to go to the client installation directory and set the environment variable:

                          cd Client installation directory

                          source bigdata_env

                          If the cluster uses the security mode, perform security authentication. Run the kinit hbase command and enter the password as prompted (obtain the password from the MRS cluster administrator).

                        4. Run the following commands to check whether the load balancing function is enabled.

                          hbase shell

                          @@ -83,11 +83,11 @@

                        5. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 12.

                        Check the HBase service scale of the standby cluster.

                        -
                        1. Expand the HBase cluster, add a node, and add a RegionServer instance on the node. Then, perform 6 to 10 to enable the load balancing function and manually trigger it.
                        2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance, refresh the page, and check whether regions are evenly distributed.

                          • If yes, go to 14.
                          • If no, go to 15.
                          +
                          1. Expand the HBase cluster, add a node, and add a RegionServer instance on the node. Then, perform 6 to 10 to enable the load balancing function and manually trigger it.
                          2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HBase. Click HMaster(Active) to go to the web UI of the HBase instance, refresh the page, and check whether regions are evenly distributed.

                            • If yes, go to 14.
                            • If no, go to 15.

                          3. Check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 15.

                          Collect the fault information.

                          -
                          1. On FusionInsight Manager of the standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
                          2. Expand the Service drop-down list, and select HBase for the target cluster.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact O&M personnel and provide the collected logs.
                          +
                          1. On MRS Manager of the standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
                          2. Expand the Service drop-down list, and select HBase for the target cluster.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-19021.html b/docs/mrs/umn/ALM-19021.html index 80373407..186678fd 100644 --- a/docs/mrs/umn/ALM-19021.html +++ b/docs/mrs/umn/ALM-19021.html @@ -66,15 +66,15 @@

                      Possible Causes

                      • The value of a handler is too small.
                      • Hotspotting occurs.

                      Procedure

                      View alarm location information.

                      -
                      1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms, locate the row that contains the alarm whose Alarm ID is 19021, and view the service instance and host name in Location.
                      +
                      1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms, locate the row that contains the alarm whose Alarm ID is 19021, and view the service instance and host name in Location.

                      Check the handler configuration.

                      1. Choose Cluster > Services > HBase and click the Configurations tab. In the upper right corner of the page, search for hbase.regionserver.handler.count and check whether its value is too small. The default value is 200.

                        • If yes, go to 3.
                        • If no, go to 5.

                      2. Change the value of this parameter to a greater value and save the configuration. Choose Cluster > Services > HBase, click the Instance tab, select the affected RegionServer instances, and choose More > Instance Rolling Restart. In the displayed dialog box, enter the username and password. In the Instance Rolling Restart dialog box, click OK and wait until the rolling restart is complete.
                      3. After the configuration takes effect, check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 5.

                      Check whether cluster hotspotting occurs.

                      -
                      1. On FusionInsight Manager, choose Cluster > Services > HBase and click HMaster(Active) following HMaster WebUI to go to the web UI of the HBase instance. In the Region Servers area of the Home page, click Requests and check whether the requests in the Filtered Read Request Count and Write Request Count columns are evenly distributed.

                        +
                        1. On MRS Manager, choose Cluster > Services > HBase and click HMaster(Active) following HMaster WebUI to go to the web UI of the HBase instance. In the Region Servers area of the Home page, click Requests and check whether the requests in the Filtered Read Request Count and Write Request Count columns are evenly distributed.

                          • If yes, go to 13.
                          • If no, go to 6.
                          -

                        2. Check whether regions are evenly distributed.

                          On FusionInsight Manager, choose Cluster > Services > HBase and click HMaster(Active) following HMaster WebUI to go to the web UI of the HBase instance. In the Region Servers area of the Home page, click Base Stats and check whether the regions in the Num.Regions column are evenly distributed.

                          +

                        3. Check whether regions are evenly distributed.

                          On MRS Manager, choose Cluster > Services > HBase and click HMaster(Active) following HMaster WebUI to go to the web UI of the HBase instance. In the Region Servers area of the Home page, click Base Stats and check whether the regions in the Num.Regions column are evenly distributed.

                          • If yes, go to 13.
                          • If no, go to 7.

                        4. Log in to the faulty RegionServer node as user omm.
                        5. Run the following commands to go to the client installation directory and set the environment variable:

                          cd Client installation directory

                          @@ -94,10 +94,10 @@ Took 0.0165 seconds

                          You are advised to enable and manually trigger the load balancing function during off-peak hours.

                        6. Run the following command to manually trigger' the load balancing function:

                          balancer

                          -

                        7. After the load balancing is complete, log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms and check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 13.
                          +

                        8. After the load balancing is complete, log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms and check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 13.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select HBase for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                      Alarm Clearing

                      This alarm is automatically cleared after the fault is rectified.

                      diff --git a/docs/mrs/umn/ALM-20002.html b/docs/mrs/umn/ALM-20002.html index 52d97240..2bf789cc 100644 --- a/docs/mrs/umn/ALM-20002.html +++ b/docs/mrs/umn/ALM-20002.html @@ -60,12 +60,12 @@

                      Possible Causes

                      • The internal KrbServer service on which the Hue service depends is abnormal.
                      • The internal DBService service on which the Hue service depends is abnormal.
                      • The network connection to the DBService is abnormal.

                      Procedure

                      Check whether the KrbServer is abnormal.

                      -
                      1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services. In the service list, check whether the KrbServer running status is Normal.

                        • If yes, go to 4.
                        • If no, go to 2.
                        +
                        1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services. In the service list, check whether the KrbServer running status is Normal.

                          • If yes, go to 4.
                          • If no, go to 2.

                        2. Restart the KrbServer service.
                        3. Wait several minutes, and check whether Hue Service Unavailable is cleared.

                          • If yes, no further action is required.
                          • If no, go to 4.

                        Check whether the DBService is abnormal.

                        -
                        1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services.
                        2. In the service list, check whether the DBService running status is Normal.

                          • If yes, go to 8.
                          • If no, go to 6.
                          -

                        3. Restart the DBService.

                          To restart the service, enter the FusionInsight Manager administrator password.

                          +
                          1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services.
                          2. In the service list, check whether the DBService running status is Normal.

                            • If yes, go to 8.
                            • If no, go to 6.
                            +

                          3. Restart the DBService.

                            To restart the service, enter the MRS Manager administrator password.

                          4. Wait several minutes, and check whether Hue Service Unavailable is cleared.

                            • If yes, no further action is required.
                            • If no, go to 8.

                          @@ -74,8 +74,8 @@

                        4. Contact the administrator to restore the network.
                        5. Wait several minutes, and check whether Hue Service Unavailable is cleared.

                          • If yes, no further action is required.
                          • If no, go to 13.

                        Collect fault information.

                        -
                        1. On FusionInsight Manager, choose O&M > Log > Download.
                        2. Select the following nodes in the required cluster from the Service drop-down list:

                          • Hue
                          • Controller
                          -

                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. On the FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Hue.
                        5. Choose More > Restart Service, and click OK.
                        1. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 19.
                          +
                          1. On MRS Manager, choose O&M > Log > Download.
                          2. Select the following nodes in the required cluster from the Service drop-down list:

                            • Hue
                            • Controller
                            +

                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. On the MRS Manager, choose Cluster > Name of the desired cluster > Services > Hue.
                          5. Choose More > Restart Service, and click OK.
                          1. Check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 19.

                          2. Contact the O&M personnel and send the collected logs.

                      Alarm Clearing

                      After the fault is rectified, the system automatically clears this alarm.

                      diff --git a/docs/mrs/umn/ALM-23001.html b/docs/mrs/umn/ALM-23001.html index 7715a6b1..d09f122d 100644 --- a/docs/mrs/umn/ALM-23001.html +++ b/docs/mrs/umn/ALM-23001.html @@ -60,37 +60,37 @@
                    3. Environment fault: The network is abnormal, which the Loader service cannot communicate with the depended internal services and cannot provide services.
                    4. Software fault: The Loader service cannot run properly.

                    Procedure

                    Check the ZooKeeper service status.

                    -
                    1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > ZooKeeper to check whether the ZooKeeper running status is Normal.

                      • If yes, go to 3.
                      • If no, go to 2.
                      +
                      1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > ZooKeeper to check whether the ZooKeeper running status is Normal.

                        • If yes, go to 3.
                        • If no, go to 2.

                      2. Choose More > Restart Service to restart the ZooKeeper service. In the alarm list, check whether LoaderService Unavailable is cleared.

                        • If yes, no further action is required.
                        • If no, go to 3.
                        -

                      3. On the FusionInsight Manager, check whether the alarm list contains Process Fault.

                        • If yes, go to 4.
                        • If no, go to 7.
                        +

                      4. On the MRS Manager, check whether the alarm list contains Process Fault.

                        • If yes, go to 4.
                        • If no, go to 7.

                      5. In the Location area of Process Fault, check whether ServiceName is ZooKeeper.

                        • If yes, go to 5.
                        • If no, go to 7.

                      6. Rectify the fault by following the steps provided in ALM-12007 Process Fault.
                      7. In the alarm list, check whether Loader Service Unavailable is cleared.

                        • If yes, no further action is required.
                        • If no, go to 7.

                      Check the HDFS service status.

                      -
                      1. On the FusionInsight Manager, check whether the alarm list contains HDFS Service Unavailable.

                        • If yes, go to 8.
                        • If no, go to 10.
                        +
                        1. On the MRS Manager, check whether the alarm list contains HDFS Service Unavailable.

                          • If yes, go to 8.
                          • If no, go to 10.

                        2. Rectify the fault by following the steps provided in ALM-14000 HDFS Service Unavailable.
                        3. In the alarm list, check whether Loader Service Unavailable is cleared.

                          • If yes, no further action is required.
                          • If no, go to 10.

                        Check the DBService status.

                        -
                        1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > DBService to check whether the DBService running status is Normal.

                          • If yes, go to 12.
                          • If no, go to 11.
                          +
                          1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > DBService to check whether the DBService running status is Normal.

                            • If yes, go to 12.
                            • If no, go to 11.

                          2. Choose More > Restart Service to restart the DBService service. In the alarm list, check whether LoaderService Unavailable is cleared.

                            • If yes, no further action is required.
                            • If no, go to 12.

                          Check the Mapreduce status.

                          -
                          1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Mapreduce to check whether the Mapreduce running status is Normal.

                            • If yes, go to 16.
                            • If no, go to 13.
                            +
                            1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Mapreduce to check whether the Mapreduce running status is Normal.

                              • If yes, go to 16.
                              • If no, go to 13.

                            2. Choose More > Restart Service to restart the Mapreduce service. In the alarm list, check whether LoaderService Unavailable is cleared.

                              • If yes, no further action is required.
                              • If no, go to 16.

                            Check the Yarn status.

                            -
                            1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Yarn to check whether the Yarn running status is Normal.

                              • If yes, go to 16.
                              • If no, go to 15.
                              +
                              1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Yarn to check whether the Yarn running status is Normal.

                                • If yes, go to 16.
                                • If no, go to 15.

                              2. Choose More > Restart Service to restart the Yarn service. In the alarm list, check whether LoaderService Unavailable is cleared.

                                • If yes, no further action is required.
                                • If no, go to 16.
                                -

                              3. On the FusionInsight Manager, check whether the alarm list contains Yarn Service Unavailable.

                                • If yes, go to 17.
                                • If no, go to 19.
                                +

                              4. On the MRS Manager, check whether the alarm list contains Yarn Service Unavailable.

                                • If yes, go to 17.
                                • If no, go to 19.

                              5. Rectify the fault by following the steps provided in ALM-18000 Yarn Service Unavailable.
                              6. In the alarm list, check whether Loader Service Unavailable is cleared.

                                • If yes, no further action is required.
                                • If no, go to 19.

                              Check the network connection between Loader and dependent components.

                              -
                              1. On the FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Loader.
                              2. Click Instance and the LoaderServer instance list is displayed.
                              3. Record the Management IP Address in the row of LoaderServer(Active).
                              4. Log in to the host where the active LoaderServer runs as omm user using the IP address obtained in 21.
                              1. Run the ping command to check whether communication between the host that runs the active LoaderServer and the hosts that run the dependent components. (The dependent components include ZooKeeper, DBService, HDFS, Mapreduce and Yarn. Obtain the IP addresses of the hosts that run these services in the same way as that for obtaining the IP address of the active LoaderServer.)

                                • If yes, go to 26.
                                • If no, go to 24.
                                +
                                1. On the MRS Manager, choose Cluster > Name of the desired cluster > Services > Loader.
                                2. Click Instance and the LoaderServer instance list is displayed.
                                3. Record the Management IP Address in the row of LoaderServer(Active).
                                4. Log in to the host where the active LoaderServer runs as omm user using the IP address obtained in 21.
                                1. Run the ping command to check whether communication between the host that runs the active LoaderServer and the hosts that run the dependent components. (The dependent components include ZooKeeper, DBService, HDFS, Mapreduce and Yarn. Obtain the IP addresses of the hosts that run these services in the same way as that for obtaining the IP address of the active LoaderServer.)

                                  • If yes, go to 26.
                                  • If no, go to 24.

                                2. Contact the administrator to restore the network.
                                3. In the alarm list, check whether Loader Service Unavailable is cleared.

                                  • If yes, no further action is required.
                                  • If no, go to 26.

                                Collect fault information.

                                -
                                1. On the FusionInsight Manager, choose O&M > Log > Download.
                                2. Select the following nodes in the required cluster from the Service drop-down list:

                                  • ZooKeeper
                                  • HDFS
                                  • DBService
                                  • Yarn
                                  • Mapreduce
                                  • Loader
                                  -

                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. On the FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Loader.
                                5. Choose More > Restart Service, and click OK.
                                1. Check whether the alarm is cleared.

                                  • If yes, no further action is required.
                                  • If no, go to 32.
                                  +
                                  1. On the MRS Manager, choose O&M > Log > Download.
                                  2. Select the following nodes in the required cluster from the Service drop-down list:

                                    • ZooKeeper
                                    • HDFS
                                    • DBService
                                    • Yarn
                                    • Mapreduce
                                    • Loader
                                    +

                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. On the MRS Manager, choose Cluster > Name of the desired cluster > Services > Loader.
                                  5. Choose More > Restart Service, and click OK.
                                  1. Check whether the alarm is cleared.

                                    • If yes, no further action is required.
                                    • If no, go to 32.

                                  2. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    diff --git a/docs/mrs/umn/ALM-23003.html b/docs/mrs/umn/ALM-23003.html index 2b6a8f38..8f9ebbc8 100644 --- a/docs/mrs/umn/ALM-23003.html +++ b/docs/mrs/umn/ALM-23003.html @@ -79,16 +79,16 @@

                    Possible Causes

                    • Task parameters are incorrectly configured.
                    • Exceptions occur when Yarn is executing a job.

                    Procedure

                    Check whether task parameters are incorrectly configured.

                    -
                    1. On FusionInsight Manager, choose O&M > Alarm > Alarms and click the alarm drop-down list from the alarm list, obtain the Alarm Cause.
                    2. If the alarm cause is "Failure to submit job", view error details in Additional Information, and go to the Loader WebUI to view the execution history of the job.

                      By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                      +
                      1. On MRS Manager, choose O&M > Alarm > Alarms and click the alarm drop-down list from the alarm list, obtain the Alarm Cause.
                      2. If the alarm cause is "Failure to submit job", view error details in Additional Information, and go to the Loader WebUI to view the execution history of the job.

                        By default, the admin user does not have the permissions to manage other components. If the page cannot be opened or the displayed content is incomplete when you access the native UI of a component due to insufficient permissions, you can manually create a user with the permissions to manage that component.

                      3. Submit the task again.
                      4. Check whether the task executed successfully.

                        • If yes, go to 9.
                        • If no, go to 5.

                      Check whether exceptions occur when Yarn is executing a job.

                      -
                      1. On FusionInsight Manager, click the alarm drop-down list from the alarm list, obtain the Alarm Cause.
                      2. Check whether the Yarn activity is executed properly in the Alarm Cause. If the alarm cause is "Yarn execution failed", the Yarn activity is abnormal.

                        • If yes, go to 7.
                        • If no, go to 10.
                        +
                        1. On MRS Manager, click the alarm drop-down list from the alarm list, obtain the Alarm Cause.
                        2. Check whether the Yarn activity is executed properly in the Alarm Cause. If the alarm cause is "Yarn execution failed", the Yarn activity is abnormal.

                          • If yes, go to 7.
                          • If no, go to 10.

                        3. Submit the task again.
                        4. Please check whether the task executed successfully.

                          • If yes, go to 9.
                          • If no, go to 10.

                        5. In the alarm list, click Clear from Operation to manually clear the alarm. No further action is required.

                        Collect fault information.

                        -
                        1. On FusionInsight Manager, choose O&M > Log > Download.
                        2. Select the following nodes in the required cluster from the Service drop-down list:

                          • DBService
                          • HDFS
                          • Loader
                          • Mapreduce
                          • Yarn
                          • ZooKeeper
                          +
                          1. On MRS Manager, choose O&M > Log > Download.
                          2. Select the following nodes in the required cluster from the Service drop-down list:

                            • DBService
                            • HDFS
                            • Loader
                            • Mapreduce
                            • Yarn
                            • ZooKeeper

                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected logs.

                      Alarm Clearing

                      After the fault is rectified, the system does not automatically clear this alarm, and you need to manually clear the alarm.

                      diff --git a/docs/mrs/umn/ALM-23004.html b/docs/mrs/umn/ALM-23004.html index 040acafa..e0d482d3 100644 --- a/docs/mrs/umn/ALM-23004.html +++ b/docs/mrs/umn/ALM-23004.html @@ -64,13 +64,13 @@

                      Possible Causes

                      The heap memory of the Loader instance is overused or the heap memory is inappropriately allocated.

                      Procedure

                      Check heap memory usage.

                      -
                      1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Loader Heap Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                      2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Loader Heap Memory Resource Percentage. Click OK.
                      3. Check whether the used heap memory of Loader reaches the threshold (the default value is 95% of the maximum heap memory) specified for Loader.

                        • If yes, go to 4.
                        • If no, go to 6.
                        -

                      4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations. Increase the value of -Xmx in GC_OPTS as required, and click Save. Click OK.

                        • If this alarm is generated, the heap memory configured for the current Loader instance is insufficient for data transmission. You are advised to open the instance monitoring page, display the Loader heap memory resource status monitoring chart, and observe the change trend of the heap memory used by Loader in the monitoring chart. Then change the value of -Xmx to twice the current heap memory usage or to another value to meet site requirements.
                        • When setting the heap memory, you can set -Xms and -Xmx to similar values to avoid performance deterioration caused by heap size adjustment after each GC.
                        • Ensure that the sum of -Xmx and XX:MaxPermSize is not greater than the physical memory of the node server.
                        +
                        1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Loader Heap Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                        2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Loader Heap Memory Resource Percentage. Click OK.
                        3. Check whether the used heap memory of Loader reaches the threshold (the default value is 95% of the maximum heap memory) specified for Loader.

                          • If yes, go to 4.
                          • If no, go to 6.
                          +

                        4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations. Increase the value of -Xmx in GC_OPTS as required, and click Save. Click OK.

                          • If this alarm is generated, the heap memory configured for the current Loader instance is insufficient for data transmission. You are advised to open the instance monitoring page, display the Loader heap memory resource status monitoring chart, and observe the change trend of the heap memory used by Loader in the monitoring chart. Then change the value of -Xmx to twice the current heap memory usage or to another value to meet site requirements.
                          • When setting the heap memory, you can set -Xms and -Xmx to similar values to avoid performance deterioration caused by heap size adjustment after each GC.
                          • Ensure that the sum of -Xmx and XX:MaxPermSize is not greater than the physical memory of the node server.

                        5. Restart the affected services or instances and check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 6.

                        Collect fault information.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                        2. Select Loader in the required cluster from the Service drop-down list.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected fault logs.
                        +
                        1. On the MRS Manager portal, choose O&M > Log > Download.
                        2. Select Loader in the required cluster from the Service drop-down list.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected fault logs.

                        Alarm Clearing

                        After the fault is rectified, the system automatically clears this alarm.

                        diff --git a/docs/mrs/umn/ALM-23005.html b/docs/mrs/umn/ALM-23005.html index 4dd2e27d..f4105cfa 100644 --- a/docs/mrs/umn/ALM-23005.html +++ b/docs/mrs/umn/ALM-23005.html @@ -64,13 +64,13 @@

                        Possible Causes

                        The non-heap memory of the Loader instance is overused or the non-heap memory is inappropriately allocated.

                        Procedure

                        Check non-heap memory usage.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Loader Non-Heap Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                        2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Loader Non Heap Memory Resource Percentage. Click OK.
                        3. Check whether the used non-heap memory of Loader reaches the threshold (the default value is 80% of the maximum non-heap memory) specified for Loader.

                          • If yes, go to 4.
                          • If no, go to 6.
                          -

                        4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations Search LOADER_GC_OPTS in the search box. If the -XX: MaxPermSize parameter is not configured, set the initial value to -XX: MaxPermSize=256M for the first time. (If the alarm persists after the first adjustment, perform the second adjustment by referring to the following note.) And click Save. Click OK.

                          If this alarm is generated, the non-heap memory configured for the current Loader instance is insufficient for the service scenario. You are advised to open the instance monitoring page, open the Loader non-heap memory resource status monitoring chart, and observe the change trend of the non-heap memory used by Loader in the monitoring chart. Then change the value of -XX:MaxPermSize to twice the current non-heap memory usage or to another value to meet site requirements.

                          +
                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Loader Non-Heap Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                          2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Loader Non Heap Memory Resource Percentage. Click OK.
                          3. Check whether the used non-heap memory of Loader reaches the threshold (the default value is 80% of the maximum non-heap memory) specified for Loader.

                            • If yes, go to 4.
                            • If no, go to 6.
                            +

                          4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations Search LOADER_GC_OPTS in the search box. If the -XX: MaxPermSize parameter is not configured, set the initial value to -XX: MaxPermSize=256M for the first time. (If the alarm persists after the first adjustment, perform the second adjustment by referring to the following note.) And click Save. Click OK.

                            If this alarm is generated, the non-heap memory configured for the current Loader instance is insufficient for the service scenario. You are advised to open the instance monitoring page, open the Loader non-heap memory resource status monitoring chart, and observe the change trend of the non-heap memory used by Loader in the monitoring chart. Then change the value of -XX:MaxPermSize to twice the current non-heap memory usage or to another value to meet site requirements.

                          5. Restart the affected services or instances and check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 6.

                          Collect fault information.

                          -
                          1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                          2. Select Loader in the required cluster from the Service drop-down list.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected fault logs.
                          +
                          1. On the MRS Manager portal, choose O&M > Log > Download.
                          2. Select Loader in the required cluster from the Service drop-down list.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact the O&M personnel and send the collected fault logs.

                          Alarm Clearing

                          After the fault is rectified, the system automatically clears this alarm.

                          diff --git a/docs/mrs/umn/ALM-23006.html b/docs/mrs/umn/ALM-23006.html index dfc2cfb0..f90484a0 100644 --- a/docs/mrs/umn/ALM-23006.html +++ b/docs/mrs/umn/ALM-23006.html @@ -64,13 +64,13 @@

                          Possible Causes

                          The direct memory of the Loader instance is overused or the direct memory is inappropriately allocated.

                          Procedure

                          Check direct memory usage.

                          -
                          1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Loader Direct Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                          2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Loader Memory Usage Statistics. Click OK.
                          3. Check whether the used direct memory of Loader reaches the threshold (the default value is 80% of the maximum direct memory) specified for Loader.

                            • If yes, go to 4.
                            • If no, go to 6.
                            -

                          4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations. Search LOADER_GC_OPTS in the search box. Increase the value of -XX:MaxDirectMemorySize as required, and click Save. Click OK.

                            If this alarm is generated, the direct memory configured for the current Loader instance is insufficient for the service scenario. You are advised to open the instance monitoring page, display the Loader direct memory resource status monitoring chart, and observe the change trend of the direct memory used by Loader in the monitoring chart. Then change the value of -XX:MaxDirectMemorySize to twice the current direct memory usage or to another value to meet site requirements.

                            +
                            1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Loader Direct Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                            2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Loader Memory Usage Statistics. Click OK.
                            3. Check whether the used direct memory of Loader reaches the threshold (the default value is 80% of the maximum direct memory) specified for Loader.

                              • If yes, go to 4.
                              • If no, go to 6.
                              +

                            4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations. Search LOADER_GC_OPTS in the search box. Increase the value of -XX:MaxDirectMemorySize as required, and click Save. Click OK.

                              If this alarm is generated, the direct memory configured for the current Loader instance is insufficient for the service scenario. You are advised to open the instance monitoring page, display the Loader direct memory resource status monitoring chart, and observe the change trend of the direct memory used by Loader in the monitoring chart. Then change the value of -XX:MaxDirectMemorySize to twice the current direct memory usage or to another value to meet site requirements.

                            5. Restart the affected services or instances and check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 6.

                            Collect fault information.

                            -
                            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                            2. Select Loader in the required cluster from the Service drop-down list.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected fault logs.
                            +
                            1. On the MRS Manager portal, choose O&M > Log > Download.
                            2. Select Loader in the required cluster from the Service drop-down list.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected fault logs.

                            Alarm Clearing

                            After the fault is rectified, the system automatically clears this alarm.

                            diff --git a/docs/mrs/umn/ALM-23007.html b/docs/mrs/umn/ALM-23007.html index 04680f4e..f945cad3 100644 --- a/docs/mrs/umn/ALM-23007.html +++ b/docs/mrs/umn/ALM-23007.html @@ -64,13 +64,13 @@

                            Possible Causes

                            The heap memory of the Loader instance is overused or the heap memory is inappropriately allocated.

                            Procedure

                            Check GC time.

                            -
                            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > GC > Garbage Collection (GC) Time of Loader. Click OK.
                            3. Check whether GC time of the Loader process every second exceeds the threshold (default value: 12 seconds).

                              • If yes, go to 4.
                              • If no, go to 6.
                              -

                            4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations. Search LOADER_GC_OPTS in the search box. Increase the value of -Xmx as required, and click Save. Click OK.

                              If this alarm is generated, the heap memory configured for the current Loader instance cannot meet the heap memory required for data transmission. You are advised to handle the problem by referring to 4 in section ALM-23004 Loader Heap Memory Usage Exceeds the Threshold.

                              +
                              1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                              2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > GC > Garbage Collection (GC) Time of Loader. Click OK.
                              3. Check whether GC time of the Loader process every second exceeds the threshold (default value: 12 seconds).

                                • If yes, go to 4.
                                • If no, go to 6.
                                +

                              4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Loader > Configurations. Click All Configurations. Search LOADER_GC_OPTS in the search box. Increase the value of -Xmx as required, and click Save. Click OK.

                                If this alarm is generated, the heap memory configured for the current Loader instance cannot meet the heap memory required for data transmission. You are advised to handle the problem by referring to 4 in section ALM-23004 Loader Heap Memory Usage Exceeds the Threshold.

                              5. Restart the affected services or instances and check whether the alarm is cleared.

                                • If yes, no further action is required.
                                • If no, go to 6.

                              Collect fault information.

                              -
                              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                              2. Select Loader in the required cluster from the Service drop-down list.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact the O&M personnel and send the collected fault logs.
                              +
                              1. On the MRS Manager portal, choose O&M > Log > Download.
                              2. Select Loader in the required cluster from the Service drop-down list.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact the O&M personnel and send the collected fault logs.

                              Alarm Clearing

                              After the fault is rectified, the system automatically clears this alarm.

                              diff --git a/docs/mrs/umn/ALM-24000.html b/docs/mrs/umn/ALM-24000.html index 81bfa367..1c7b8f6d 100644 --- a/docs/mrs/umn/ALM-24000.html +++ b/docs/mrs/umn/ALM-24000.html @@ -63,7 +63,7 @@

                            5. In the alarm list, check whether alarm "Flume Service Unavailable" is cleared.

                              • If yes, no further action is required.
                              • If no, go to 3.

                            Collect the fault information.

                            -
                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact O&M personnel and provide the collected logs.
                            +
                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact O&M personnel and provide the collected logs.

                            Alarm Clearing

                            This alarm is automatically cleared after the fault is rectified.

                            diff --git a/docs/mrs/umn/ALM-24001.html b/docs/mrs/umn/ALM-24001.html index cda4714e..478932e9 100644 --- a/docs/mrs/umn/ALM-24001.html +++ b/docs/mrs/umn/ALM-24001.html @@ -78,9 +78,7 @@

                            Check the Flume agent configuration.

                            1. Run the cat properties.properties | grep spooldir and cat properties.properties | grep TAILDIR commands to check whether the Flume source type is spoolDir or tailDir. If any command output is displayed, the Flume source type is spoolDir or tailDir.

                              • If yes, go to 13.
                              • If no, go to 17.

                            2. Check whether the data monitoring directory exists.

                              • If yes, go to 15.
                              • If no, go to 14.

                                Run the cat properties.properties | grep spoolDir command to view the spoolDir monitoring directory.

                                -

                                Run the cat properties.properties | grep parentDir command to view the tailDir monitoring directory.

                                -

                            3. Specify a correct data monitoring directory.
                            4. Check whether the Flume agent user has the read, write, and execute permissions on the monitoring directory specified in 13.

                              • If yes, go to 17.
                              • If no, go to 16.

                                Go to the monitoring directory as the Flume running user. If files can be created, the Flume running user has the read, write, and execute permissions on the monitoring directory.

                                @@ -91,14 +89,13 @@

                            5. Run the ll ketab path command to check whether the keytab authentication path specified by the *.kerberosKeytab parameter in the configuration file exists.

                              • If yes, go to 20.
                              • If no, go to 19.

                                To view the ketab path, run the cat properties.properties | grep keytab command.

                                -

                            6. Change the value of kerberosKeytab in 18 to the custom keytab path and go to 21.
                            7. Perform 18 to check whether the Flume agent running user has the permission to access the keytab authentication file. If the keytab path is returned, the user has the permission. Otherwise, the user does not have the permission.

                              • If yes, go to 22.
                              • If no, go to 21.

                            8. Run the chmod 755 ketab file command to grant the read permission on the keytab file specified in 19, and restart the Flume process.
                            9. Check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 23.

                            Collect the fault information.

                            -
                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact O&M personnel and provide the collected logs.
                            +
                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact O&M personnel and provide the collected logs.

                            Alarm Clearing

                            This alarm is automatically cleared after the fault is rectified.

                            diff --git a/docs/mrs/umn/ALM-24003.html b/docs/mrs/umn/ALM-24003.html index 97aa4826..a4f114bc 100644 --- a/docs/mrs/umn/ALM-24003.html +++ b/docs/mrs/umn/ALM-24003.html @@ -72,7 +72,7 @@
                            1. Check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 11.

                            Collect the fault information.

                            -
                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Collect logs in the /var/log/Bigdata/flume-client directory on the Flume client using a transmission tool.
                            5. Contact O&M personnel and provide the collected logs.
                            +
                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Collect logs in the /var/log/Bigdata/flume-client directory on the Flume client using a transmission tool.
                            5. Contact O&M personnel and provide the collected logs.

                          Alarm Clearing

                          This alarm is automatically cleared after the fault is rectified.

                          diff --git a/docs/mrs/umn/ALM-24004.html b/docs/mrs/umn/ALM-24004.html index df38cd1d..01294277 100644 --- a/docs/mrs/umn/ALM-24004.html +++ b/docs/mrs/umn/ALM-24004.html @@ -77,7 +77,7 @@

                        5. Open the properties.properties configuration file on the local PC, search for org.apache.flume.source.kafka.KafkaSource in the file, and check whether the Flume source type is Kafka.

                          • If yes, go to 4.
                          • If no, go to 7.

                        6. Check whether the topic data configured by Kafka Source has been used up.

                          • If yes, no further action is required.
                          • If no, go to 5.
                          -

                        7. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Flume > Instance.
                        8. Go to the Flume instance page of the faulty node to check whether the indicator Source Speed Metrics in the alarm is 0.

                          • If yes, go to 11.
                          • If no, go to 7.
                          +

                        9. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Flume > Instance.
                        10. Go to the Flume instance page of the faulty node to check whether the indicator Source Speed Metrics in the alarm is 0.

                          • If yes, go to 11.
                          • If no, go to 7.

                        Check the network connection between the faulty node and the node that corresponds to the Flume Source IP address.

                        1. Open the properties.properties configuration file on the local PC, search for type = avro in the file, and check whether the Flume source type is Avro.

                          • If yes, go to 8.
                          • If no, go to 11.
                          @@ -85,7 +85,7 @@

                        2. Contact the network administrator to restore the network.
                        3. In the alarm list, check whether the alarm is cleared after a period.

                          • If yes, no further action is required.
                          • If no, go to 11.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select Flume for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select Flume for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                        Alarm Clearing

                        This alarm is automatically cleared after the fault is rectified.

                        diff --git a/docs/mrs/umn/ALM-24005.html b/docs/mrs/umn/ALM-24005.html index cf088f96..68df9380 100644 --- a/docs/mrs/umn/ALM-24005.html +++ b/docs/mrs/umn/ALM-24005.html @@ -72,12 +72,12 @@

                        Procedure

                        Check whether Flume Sink is faulty.

                        1. Open the properties.properties configuration file on the local PC, search for type = hdfs in the file, and check whether the Flume sink type is HDFS.

                          • If yes, go to 2.
                          • If no, go to 3.
                          -

                        2. On FusionInsight Manager, check whether HDFS Service Unavailable alarm is generated in the alarm list and whether the HDFS service is stopped in the service list.

                          • If the alarm is reported, clear it according to the handling suggestions of ALM-14000 HDFS Service Unavailable; if the HDFS service is stopped, start it. Then, go to 7.
                          • If no, go to 7.
                          +

                        3. On MRS Manager, check whether HDFS Service Unavailable alarm is generated in the alarm list and whether the HDFS service is stopped in the service list.

                          • If the alarm is reported, clear it according to the handling suggestions of ALM-14000 HDFS Service Unavailable; if the HDFS service is stopped, start it. Then, go to 7.
                          • If no, go to 7.

                        4. Open the properties.properties configuration file on the local PC, search for type = hbase in the file, and check whether the Flume sink type is HBase.

                          • If yes, go to 4.
                          • If no, go to 5.
                          -

                        5. On FusionInsight Manager, check whether HBase Service Unavailable alarm is generated in the alarm list and whether the HBase service is stopped in the service list.

                          • If the alarm is reported, clear it according to the handling suggestions of ALM-19000 HBase Service Unavailable; if the HBase service is stopped, start it. Then, go to 7.
                          • If no, go to 7.
                          +

                        6. On MRS Manager, check whether HBase Service Unavailable alarm is generated in the alarm list and whether the HBase service is stopped in the service list.

                          • If the alarm is reported, clear it according to the handling suggestions of ALM-19000 HBase Service Unavailable; if the HBase service is stopped, start it. Then, go to 7.
                          • If no, go to 7.

                        7. Open the properties.properties configuration file on the local PC, search for org.apache.flume.sink.kafka.KafkaSink in the file, and check whether the Flume sink type is Kafka.

                          • If yes, go to 6.
                          • If no, go to 9.
                          -

                        8. On FusionInsight Manager, check whether Kafka Service Unavailable alarm is generated in the alarm list and whether the Kafka service is stopped in the service list.

                          • If the alarm is reported, clear it according to the handling suggestions of ALM-38000 Kafka Service Unavailable; if the Kafka service is stopped, start it. Then, go to 7.
                          • If no, go to 7.
                          -

                        9. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Flume > Instance.
                        10. Go to the Flume instance page of the faulty node to check whether the indicator Sink Speed Metrics is 0.

                          • If yes, go to 13.
                          • If no, go to 9.
                          +

                        11. On MRS Manager, check whether Kafka Service Unavailable alarm is generated in the alarm list and whether the Kafka service is stopped in the service list.

                          • If the alarm is reported, clear it according to the handling suggestions of ALM-38000 Kafka Service Unavailable; if the Kafka service is stopped, start it. Then, go to 7.
                          • If no, go to 7.
                          +

                        12. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Flume > Instance.
                        13. Go to the Flume instance page of the faulty node to check whether the indicator Sink Speed Metrics is 0.

                          • If yes, go to 13.
                          • If no, go to 9.

                        Check the network connection between the faulty node and the node that corresponds to the Flume Sink IP address.

                        1. Open the properties.properties configuration file on the local PC, search for type = avro in the file, and check whether the Flume sink type is Avro.

                          • If yes, go to 10.
                          • If no, go to 13.
                          @@ -85,7 +85,7 @@

                        2. Contact the network administrator to restore the network.
                        3. In the alarm list, check whether the alarm is cleared after a period.

                          • If yes, no further action is required.
                          • If no, go to 13.

                        Collect the fault information.

                        -
                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select Flume for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.
                        +
                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                        2. Expand the Service drop-down list, and select Flume for the target cluster.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact O&M personnel and provide the collected logs.

                        Alarm Clearing

                        This alarm is automatically cleared after the fault is rectified.

                        diff --git a/docs/mrs/umn/ALM-24006.html b/docs/mrs/umn/ALM-24006.html index 9477b823..c044c5a1 100644 --- a/docs/mrs/umn/ALM-24006.html +++ b/docs/mrs/umn/ALM-24006.html @@ -64,13 +64,13 @@

                        Possible Causes

                        The heap memory of the Flume instance is overused or the heap memory is inappropriately allocated.

                        Procedure

                        Check the heap memory usage.

                        -
                        1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing Flume Heap Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                        2. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Flume Heap Memory Resource Percentage. Then, click OK.
                        3. Check whether the heap memory used by Flume reaches the threshold (95% of the maximum heap memory by default).

                          • If yes, go to 4.
                          • If no, go to 6.
                          -

                        4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -Xmx in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                          If this alarm is generated, the heap memory configured for the Flume server is insufficient for data transmission. You are advised to change the heap memory to: Channel capacity x Maximum size of a single data record x Number of channels. Note that the value of xmx cannot exceed the remaining memory of the node.

                          +
                          1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing Flume Heap Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                          2. On MRS Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Flume Heap Memory Resource Percentage. Then, click OK.
                          3. Check whether the heap memory used by Flume reaches the threshold (95% of the maximum heap memory by default).

                            • If yes, go to 4.
                            • If no, go to 6.
                            +

                          4. On MRS Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -Xmx in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                            If this alarm is generated, the heap memory configured for the Flume server is insufficient for data transmission. You are advised to change the heap memory to: Channel capacity x Maximum size of a single data record x Number of channels. Note that the value of xmx cannot exceed the remaining memory of the node.

                          5. Restart the affected services or instances and check whether the alarm is cleared.

                            • If yes, no further action is required.
                            • If no, go to 6.

                          Collect the fault information.

                          -
                          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                          2. Expand the Service drop-down list, and select Flume for the target cluster.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact O&M personnel and provide the collected logs.
                          +
                          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                          2. Expand the Service drop-down list, and select Flume for the target cluster.
                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                          4. Contact O&M personnel and provide the collected logs.

                          Alarm Clearing

                          This alarm is automatically cleared after the fault is rectified.

                          diff --git a/docs/mrs/umn/ALM-24007.html b/docs/mrs/umn/ALM-24007.html index 32a27eff..acb747a1 100644 --- a/docs/mrs/umn/ALM-24007.html +++ b/docs/mrs/umn/ALM-24007.html @@ -64,13 +64,13 @@

                          Possible Causes

                          The direct memory of the Flume process is overused or the direct memory is inappropriately allocated.

                          Procedure

                          Check the direct memory usage.

                          -
                          1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing Flume Direct Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                          2. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Flume Direct Memory Resource Percentage. Then, click OK.
                          3. Check whether the direct memory used by Flume reaches the threshold (80% of the maximum direct memory by default).

                            • If yes, go to 4.
                            • If no, go to 6.
                            -

                          4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -XX:MaxDirectMemorySize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                            If this alarm is generated, the direct memory size configured for the Flume server instance cannot meet service requirements. You are advised to change the value of -XX:MaxDirectMemorySize to twice the current direct memory size or change the value based on site requirements.

                            +
                            1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing Flume Direct Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                            2. On MRS Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Flume Direct Memory Resource Percentage. Then, click OK.
                            3. Check whether the direct memory used by Flume reaches the threshold (80% of the maximum direct memory by default).

                              • If yes, go to 4.
                              • If no, go to 6.
                              +

                            4. On MRS Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -XX:MaxDirectMemorySize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                              If this alarm is generated, the direct memory size configured for the Flume server instance cannot meet service requirements. You are advised to change the value of -XX:MaxDirectMemorySize to twice the current direct memory size or change the value based on site requirements.

                            5. Restart the affected services or instances and check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 6.

                            Collect the fault information.

                            -
                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact O&M personnel and provide the collected logs.
                            +
                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                            2. Expand the Service drop-down list, and select Flume for the target cluster.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact O&M personnel and provide the collected logs.

                            Alarm Clearing

                            This alarm is automatically cleared after the fault is rectified.

                            diff --git a/docs/mrs/umn/ALM-24008.html b/docs/mrs/umn/ALM-24008.html index 2d57ec70..81adc38f 100644 --- a/docs/mrs/umn/ALM-24008.html +++ b/docs/mrs/umn/ALM-24008.html @@ -64,13 +64,13 @@

                            Possible Causes

                            The non-heap memory of the Flume instance is overused or the non-heap memory is inappropriately allocated.

                            Procedure

                            Check non-heap memory usage.

                            -
                            1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing Flume Non Heap Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                            2. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Flume Non Heap Memory Resource Percentage. Then, click OK.
                            3. Check whether the non-heap memory used by Flume reaches the threshold (80% of the maximum non-heap memory by default).

                              • If yes, go to 4.
                              • If no, go to 6.
                              -

                            4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                              If this alarm is generated, the non-heap memory size configured for the Flume server instance cannot meet service requirements. You are advised to change the value of -XX:MaxPermSize to twice the current non-heap memory size or change the value based on site requirements.

                              +
                              1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing Flume Non Heap Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                              2. On MRS Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Flume Non Heap Memory Resource Percentage. Then, click OK.
                              3. Check whether the non-heap memory used by Flume reaches the threshold (80% of the maximum non-heap memory by default).

                                • If yes, go to 4.
                                • If no, go to 6.
                                +

                              4. On MRS Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                                If this alarm is generated, the non-heap memory size configured for the Flume server instance cannot meet service requirements. You are advised to change the value of -XX:MaxPermSize to twice the current non-heap memory size or change the value based on site requirements.

                              5. Restart the affected services or instances and check whether the alarm is cleared.

                                • If yes, no further action is required.
                                • If no, go to 6.

                              Collect the fault information.

                              -
                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                              2. Expand the Service drop-down list, and select Flume for the target cluster.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact O&M personnel and provide the collected logs.
                              +
                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                              2. Expand the Service drop-down list, and select Flume for the target cluster.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact O&M personnel and provide the collected logs.

                              Alarm Clearing

                              This alarm is automatically cleared after the fault is rectified.

                              diff --git a/docs/mrs/umn/ALM-24009.html b/docs/mrs/umn/ALM-24009.html index 77e779fb..e05a0431 100644 --- a/docs/mrs/umn/ALM-24009.html +++ b/docs/mrs/umn/ALM-24009.html @@ -64,13 +64,13 @@

                              Possible Causes

                              The heap memory of the Flume process is overused or inappropriately allocated, causing frequent occurrence of the GC process.

                              Procedure

                              Check the GC duration.

                              -
                              1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing GC Duration Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                              2. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Garbage Collection (GC) Duration of Flume. Then, click OK.
                              3. Check whether the GC duration of the Flume process collected every minute exceeds the threshold (12 seconds by default).

                                • If yes, go to 4.
                                • If no, go to 6.
                                -

                              4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -Xmx in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                                If this alarm is generated, the heap memory configured for the Flume server is insufficient for data transmission. You are advised to change the heap memory to: Channel capacity x Maximum size of a single data record x Number of channels. Note that the value of xmx cannot exceed the remaining memory of the node.

                                +
                                1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing GC Duration Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
                                2. On MRS Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Garbage Collection (GC) Duration of Flume. Then, click OK.
                                3. Check whether the GC duration of the Flume process collected every minute exceeds the threshold (12 seconds by default).

                                  • If yes, go to 4.
                                  • If no, go to 6.
                                  +

                                4. On MRS Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -Xmx in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                                  If this alarm is generated, the heap memory configured for the Flume server is insufficient for data transmission. You are advised to change the heap memory to: Channel capacity x Maximum size of a single data record x Number of channels. Note that the value of xmx cannot exceed the remaining memory of the node.

                                5. Restart the affected services or instances and check whether the alarm is cleared.

                                  • If yes, no further action is required.
                                  • If no, go to 6.

                                Collect the fault information.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.
                                +
                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-24010.html b/docs/mrs/umn/ALM-24010.html index 153a6a34..c71a34f0 100644 --- a/docs/mrs/umn/ALM-24010.html +++ b/docs/mrs/umn/ALM-24010.html @@ -60,7 +60,7 @@

                                Possible Causes

                                The Flume certificate file is invalid or damaged.

                                Procedure

                                View alarm information.

                                -
                                1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24010 Flume Certificate File Is Invalid or Damaged, and view the Location information. View the IP address of the instance for which the alarm is generated.
                                +
                                1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24010 Flume Certificate File Is Invalid or Damaged, and view the Location information. View the IP address of the instance for which the alarm is generated.

                                Check whether the certificate file in the system is valid. If it is not, generate a new one.

                                1. Log in to the node for which the alarm is generated as user root and run the su - omm command to switch to user omm.
                                2. Run the following command to go to the Flume service certificate directory:

                                  cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/conf

                                3. Run the ls -l command to check whether the flume_sChat.crt file exists.

                                  • If yes, go to 5.
                                  • If no, go to 6.
                                  @@ -74,7 +74,7 @@

                                4. Check whether this alarm is generated again during periodic system check.

                                  • If yes, go to 9.
                                  • If no, no further action is required.

                                Collect the fault information.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.
                                +
                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-24011.html b/docs/mrs/umn/ALM-24011.html index 6022ce39..ccea923c 100644 --- a/docs/mrs/umn/ALM-24011.html +++ b/docs/mrs/umn/ALM-24011.html @@ -60,7 +60,7 @@

                                Possible Causes

                                The Flume certificate file is about to expire.

                                Procedure

                                View alarm information.

                                -
                                1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24011 Flume Certificate Is About to Expire, and view the Location information. View the IP address of the instance for which the alarm is generated.
                                +
                                1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24011 Flume Certificate Is About to Expire, and view the Location information. View the IP address of the instance for which the alarm is generated.

                                Check whether the certificate file in the system is valid. If it is not, generate a new one.

                                1. Log in to the node for which the alarm is generated as user root and run the su - omm command to switch to user omm.
                                2. Run the following command to go to the Flume service certificate directory:

                                  cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/conf

                                3. Run the following command to check the effective time and expiration time of the Flume user certificate:

                                  openssl x509 -noout -text -in flume_sChat.crt

                                  @@ -74,7 +74,7 @@

                                4. Check whether this alarm is generated again during periodic system check.

                                  • If yes, go to 10.
                                  • If no, no further action is required.

                                Collect the fault information.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.
                                +
                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-24012.html b/docs/mrs/umn/ALM-24012.html index 3f91f445..d5bda0be 100644 --- a/docs/mrs/umn/ALM-24012.html +++ b/docs/mrs/umn/ALM-24012.html @@ -60,7 +60,7 @@

                                Possible Causes

                                The Flume certificate file has expired.

                                Procedure

                                View alarm information.

                                -
                                1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24012 Flume Certificate Has Expired, and view the Location information. View the IP address of the instance for which the alarm is generated.
                                +
                                1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24012 Flume Certificate Has Expired, and view the Location information. View the IP address of the instance for which the alarm is generated.

                                Check whether the certificate file in the system is valid. If it is not, generate a new one.

                                1. Log in to the node for which the alarm is generated as user root and run the su - omm command to switch to user omm.
                                2. Run the following command to go to the Flume service certificate directory:

                                  cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/conf

                                3. Run the following command to check the effective time and expiration time of the HA user certificate to determine whether the certificate file is still in the validity period:

                                  openssl x509 -noout -text -in flume_sChat.crt
                                  • If yes, go to 9.
                                  • If no, go to 5.
                                  @@ -75,7 +75,7 @@

                                4. Check whether this alarm is generated again during periodic system check.

                                  • If yes, go to 9.
                                  • If no, no further action is required.

                                Collect the fault information.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.
                                +
                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Expand the Service drop-down list, and select Flume for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-24013.html b/docs/mrs/umn/ALM-24013.html index cce41714..817864bf 100644 --- a/docs/mrs/umn/ALM-24013.html +++ b/docs/mrs/umn/ALM-24013.html @@ -60,7 +60,7 @@

                                Possible Causes

                                The MonitorServer certificate file is invalid or damaged.

                                Procedure

                                View alarm information.

                                -
                                1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24013 MonitorServer Certificate File Is Invalid or Damaged, and view the Location information. View the IP address of the instance for which the alarm is generated.
                                +
                                1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24013 MonitorServer Certificate File Is Invalid or Damaged, and view the Location information. View the IP address of the instance for which the alarm is generated.

                                Check whether the certificate file in the system is valid. If it is not, generate a new one.

                                1. Log in to the node for which the alarm is generated as user root and run the su - omm command to switch to user omm.
                                2. Run the following command to go to the MonitorServer certificate file directory:

                                  cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/conf

                                3. Run the ls -l command to check whether the ms_sChat.crt file exists:

                                  • If yes, go to 5.
                                  • If no, go to 6.
                                  @@ -74,7 +74,7 @@

                                4. Check whether this alarm is generated again during periodic system check.

                                  • If yes, go to 9.
                                  • If no, no further action is required.

                                Collect the fault information.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Select MonitorServer in the required cluster for Service.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.
                                +
                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Select MonitorServer in the required cluster for Service.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-24014.html b/docs/mrs/umn/ALM-24014.html index 484cacbd..5d970916 100644 --- a/docs/mrs/umn/ALM-24014.html +++ b/docs/mrs/umn/ALM-24014.html @@ -60,7 +60,7 @@

                                Possible Causes

                                The MonitorServer certificate file is about to expire.

                                Procedure

                                View alarm information.

                                -
                                1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24014 MonitorServer Certificate Is About to Expire, and view the Location information. View the IP address of the instance for which the alarm is generated.
                                +
                                1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24014 MonitorServer Certificate Is About to Expire, and view the Location information. View the IP address of the instance for which the alarm is generated.

                                Check whether the certificate file in the system is valid. If it is not, generate a new one.

                                1. Log in to the node for which the alarm is generated as user root and run the su - omm command to switch to user omm.
                                2. Run the following command to go to the MonitorServer certificate file directory:

                                  cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/conf

                                3. Run the following command to check the effective time and expiration time of the MonitorServer user certificate:

                                  openssl x509 -noout -text -in ms_sChat.crt

                                  @@ -74,7 +74,7 @@

                                4. Check whether this alarm is generated again during periodic system check.

                                  • If yes, go to 10.
                                  • If no, no further action is required.

                                Collect the fault information.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Select MonitorServer in the required cluster for Service.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.
                                +
                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Select MonitorServer in the required cluster for Service.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-24015.html b/docs/mrs/umn/ALM-24015.html index 429c26fe..58983b77 100644 --- a/docs/mrs/umn/ALM-24015.html +++ b/docs/mrs/umn/ALM-24015.html @@ -60,7 +60,7 @@

                                Possible Causes

                                The MonitorServer certificate file has expired.

                                Procedure

                                View alarm information.

                                -
                                1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24015 MonitorServer Certificate Has Expired, and view the Location information. View the IP address of the instance for which the alarm is generated.
                                +
                                1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24015 MonitorServer Certificate Has Expired, and view the Location information. View the IP address of the instance for which the alarm is generated.

                                Check whether the certificate file in the system is valid. If it is not, generate a new one.

                                1. Log in to the node for which the alarm is generated as user root and run the su - omm command to switch to user omm.
                                2. Run the following command to go to the MonitorServer certificate file directory:

                                  cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/conf

                                3. Run the following command to check the effective time and expiration time of the user certificate to determine whether the certificate file is still in the validity period:

                                  openssl x509 -noout -text -in ms_sChat.crt
                                  • If yes, go to 9.
                                  • If no, go to 5.
                                  @@ -75,7 +75,7 @@

                                4. Check whether this alarm is generated again during periodic system check.

                                  • If yes, go to 9.
                                  • If no, no further action is required.

                                Collect the fault information.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Select MonitorServer in the required cluster for Service.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.
                                +
                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                2. Select MonitorServer in the required cluster for Service.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-25000.html b/docs/mrs/umn/ALM-25000.html index 2b6bee65..73e3e139 100644 --- a/docs/mrs/umn/ALM-25000.html +++ b/docs/mrs/umn/ALM-25000.html @@ -55,22 +55,22 @@
            -

            Impact on the System

            When this alarm is generated, no operation can be performed for the KrbServer users and LdapServer users in the cluster. For example, users, user groups, or roles cannot be added, deleted, or modified, and user passwords cannot be changed on the FusionInsight Manager portal. The authentication for existing users in the cluster is not affected.

            +

            Impact on the System

            When this alarm is generated, no operation can be performed for the KrbServer users and LdapServer users in the cluster. For example, users, user groups, or roles cannot be added, deleted, or modified, and user passwords cannot be changed on the MRS Manager portal. The authentication for existing users in the cluster is not affected.

            Possible Causes

            • The node where the LdapServer service locates is faulty.
            • The LdapServer process is abnormal.

            Procedure

            Check whether the nodes where the two SlapdServer instances of the LdapServer service are located are faulty.

            -
            1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > LdapServer > Instance to go to the LdapServer instance page to obtain the host name of the node where the two SlapdServer instances locates.
            2. Choose O&M > Alarm > Alarms. On the Alarm page of the FusionInsight Manager system, check whether any alarm of Node Fault exists.

              • If yes, go to 3.
              • If no, go to 6.
              +
              1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > LdapServer > Instance to go to the LdapServer instance page to obtain the host name of the node where the two SlapdServer instances locates.
              2. Choose O&M > Alarm > Alarms. On the Alarm page of the MRS Manager system, check whether any alarm of Node Fault exists.

                • If yes, go to 3.
                • If no, go to 6.

              3. Check whether the host name in the alarm is consistent with the 1 host name.

                • If yes, go to 4.
                • If no, go to 6.

              4. Handle the alarm according to "ALM-12006 Node Fault".
              5. Check whether LdapServer Service Unavailable is cleared in the alarm list.

                • If yes, no further action is required.
                • If no, go to 10.

              Check whether the LdapServer process is normal.

              -
              1. Choose O&M > Alarm > Alarms. On the Alarm page of the FusionInsight Manager system, check whether any alarm of Process Fault exists.

                • If yes, go to 7.
                • If no, go to 10.
                +
                1. Choose O&M > Alarm > Alarms. On the Alarm page of the MRS Manager system, check whether any alarm of Process Fault exists.

                  • If yes, go to 7.
                  • If no, go to 10.

                2. Check whether the service and host name in the alarm are consistent with the LdapServer service and host name.

                  • If yes, go to 8.
                  • If no, go to 10.

                3. Handle the alarm according to "ALM-12007 Process Fault".
                4. Check whether LdapServer Service Unavailable is cleared in the alarm list.

                  • If yes, no further action is required.
                  • If no, go to 10.

                Collect fault information.

                -
                1. On the FusionInsight Manager, choose O&M > Log > Download.
                2. Select LdapServer in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.
                +
                1. On the MRS Manager, choose O&M > Log > Download.
                2. Select LdapServer in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-25004.html b/docs/mrs/umn/ALM-25004.html index 58a809d1..cf98c02d 100644 --- a/docs/mrs/umn/ALM-25004.html +++ b/docs/mrs/umn/ALM-25004.html @@ -60,17 +60,17 @@

            Possible Causes

            • The network of the node where the LdapServer process locates is faulty.
            • The LdapServer process is abnormal.
            • The OS restart damages data on LdapServer.

            Procedure

            Check whether the network where the LdapServer nodes reside is faulty.

            -
            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. Record the IP address of HostName in the alarm locating information as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
            2. Contact O&M personnel and log in to the nodes corresponding to IP 1. Run the ping command to check whether the IP address of the management plane of the active OMS node can be pinged.

              • If yes, go to 4.
              • If no, go to 3.
              +
              1. On the MRS Manager portal, choose O&M > Alarm > Alarms. Record the IP address of HostName in the alarm locating information as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
              2. Contact O&M personnel and log in to the nodes corresponding to IP 1. Run the ping command to check whether the IP address of the management plane of the active OMS node can be pinged.

                • If yes, go to 4.
                • If no, go to 3.

              3. Contact the network administrator to recover the network and check whether Abnormal LdapServer Data Synchronization is cleared.

                • If yes, no further action is required.
                • If no, go to 4.

              Check whether the LdapServer processes are normal.

              -
              1. On the Alarm page of FusionInsight Manager, check whether the OLdap Resource Abnormal exists.

                • If yes, go to 5.
                • If no, go to 7.
                +
                1. On the Alarm page of MRS Manager, check whether the OLdap Resource Abnormal exists.

                  • If yes, go to 5.
                  • If no, go to 7.

                2. Clear the alarm by following the steps provided in "ALM-12004 OLdap Resource Abnormal".
                3. Check whether Abnormal LdapServer Data Synchronization is cleared in the alarm list.

                  • If yes, no further action is required.
                  • If no, go to 7.
                  -

                4. On the Alarm page of FusionInsight Manager, check whether Process Fault is generated for the LdapServer service.

                  • If yes, go to 8.
                  • If no, go to 10.
                  +

                5. On the Alarm page of MRS Manager, check whether Process Fault is generated for the LdapServer service.

                  • If yes, go to 8.
                  • If no, go to 10.

                6. Handle the alarm according to "ALM-12007 Process Fault".
                7. Check whether Abnormal LdapServer Data Synchronization is cleared.

                  • If yes, no further action is required.
                  • If no, go to 10.

                Check whether the LdapServer processes are normal.

                -
                1. On FusionInsight Manager, choose O&M > Alarm > Alarms. Record the IP address of HostName in the alarm locating information as "IP1" (if multiple alarms exist, record the IP addresses as "IP1", "IP2", and "IP3" respectively). Choose Cluster > Name of the desired cluster > Services > LdapServer > Configurations. Record the port number of LdapServer as "PORT". (If the IP address in the alarm locating information is the IP address of the standby management node, choose System > OMS > oldap > Modify Configuration and record the listening port number of LdapServer.)
                2. Log in to the nodes corresponding to IP1 as user omm.
                3. Run the following command to check whether errors are displayed in the queried information.

                  ldapsearch -H ldaps://IP1:PORT -LLL -x -D cn=root,dc=hadoop,dc=com -W -b ou=Peoples,dc=hadoop,dc=com

                  +
                  1. On MRS Manager, choose O&M > Alarm > Alarms. Record the IP address of HostName in the alarm locating information as "IP1" (if multiple alarms exist, record the IP addresses as "IP1", "IP2", and "IP3" respectively). Choose Cluster > Name of the desired cluster > Services > LdapServer > Configurations. Record the port number of LdapServer as "PORT". (If the IP address in the alarm locating information is the IP address of the standby management node, choose System > OMS > oldap > Modify Configuration and record the listening port number of LdapServer.)
                  2. Log in to the nodes corresponding to IP1 as user omm.
                  3. Run the following command to check whether errors are displayed in the queried information.

                    ldapsearch -H ldaps://IP1:PORT -LLL -x -D cn=root,dc=hadoop,dc=com -W -b ou=Peoples,dc=hadoop,dc=com

                    After running the command, enter the LDAP administrator password. Contact the system administrator to obtain the password.

                    • If yes, go to 13.
                    • If no, go to 15.

                  4. Recover the LdapServer and OMS nodes using data backed up before the alarm is generated.

                    Use the OMS data and LdapServer data backed up at the same point in time to recover the data. Otherwise, the service and operation may fail. To recover data when services run properly, you are advised to manually back up the latest management data and then recover the data. Otherwise, Manager data produced between the backup point in time and the recovery point in time will be lost.

                    @@ -78,7 +78,7 @@

                  5. Check whether alarm Abnormal LdapServer Data Synchronization is cleared.

                    • If yes, no further action is required.
                    • If no, go to 15.

                  Collect fault information.

                  -
                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                  2. Select LdapServer in the required cluster and OmsLdapServer from the Service.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.
                  +
                  1. On the MRS Manager portal, choose O&M > Log > Download.
                  2. Select LdapServer in the required cluster and OmsLdapServer from the Service.
                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-25005.html b/docs/mrs/umn/ALM-25005.html index 7f8ef6f4..d09fd755 100644 --- a/docs/mrs/umn/ALM-25005.html +++ b/docs/mrs/umn/ALM-25005.html @@ -55,7 +55,7 @@

            Possible Causes

            • The nscd service is not started.
            • The network is faulty, and cannot access the LDAP server.
            • NameService is abnormal.
            • Users cannot be queried because the OS executes commands too slowly.

            Procedure

            Check whether the nscd service is started.

            -
            1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. Record the IP address of HostName in Location of the alarm as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
            2. Contact the O&M personnel to access the node using IP1 as user root. Run the ps -ef | grep nscd command on the node and check whether the /usr/sbin/nscd process is started.

              • If yes, go to 5.
              • If no, go to 3.
              +
              1. Log in to MRS Manager and choose O&M > Alarm > Alarms. Record the IP address of HostName in Location of the alarm as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
              2. Contact the O&M personnel to access the node using IP1 as user root. Run the ps -ef | grep nscd command on the node and check whether the /usr/sbin/nscd process is started.

                • If yes, go to 5.
                • If no, go to 3.

              3. Run the service nscd restart command as user root to restart the nscd service. Then run the ps -ef | grep nscd command to check whether the nscd service is started.

                • If yes, go to 4.
                • If no, go to 15.

              4. Wait for 5 minutes and run the ps -ef | grep nscd command again as user root. Check whether the service exists.

                • If yes, go to 11.
                • If no, go to 15.

              @@ -72,7 +72,7 @@

            3. Run the /usr/sbin/nscd -i group and /usr/sbin/nscd -i passwd commands as user root. Wait for 2 minutes and run the id admin and id backup/manager commands to check whether results can be queried.

              • If yes, go to 11.
              • If no, go to 15.

            4. Run the vi /etc/nsswitch.conf command as user root. Correct the configurations in 6 and save the file. Run the service nscd restart command to restart the nscd service. Wait for 2 minutes and run the id admin and id backup/manager commands to check whether results can be queried.

              • If yes, go to 11.
              • If no, go to 15.

            5. Run the vi /etc/nscd.conf command as user root. Correct the configurations in 7 and save the file. Run the service nscd restart command to restart the nscd service. Wait for 2 minutes and run the id admin and id backup/manager commands to check whether results can be queried.

              • If yes, go to 11.
              • If no, go to 15.
              -

            6. Log in to the FusionInsight Manager portal. Wait for 5 minutes and check whether the nscd Service Exception alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 12.
              +

            7. Log in to the MRS Manager portal. Wait for 5 minutes and check whether the nscd Service Exception alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 12.

            Check whether frame freezing occurs when running a command in the operating system.

            1. Log in to the faulty node as user root, run the id admin command, and check whether the command execution takes a long time. If the command execution takes more than 3 seconds, the command execution is deemed to be slow.

              • If yes, go to 13.
              • If no, go to 15.
              @@ -87,7 +87,7 @@ Feb 11 11:44:44 10-120-205-33 ntpq: nss_ldap: failed to bind to LDAP server ldap
              • If yes, go to 15.
              • If no, log in to other faulty nodes and repeat 12 to 14 to check whether the first LdapServer node in the URI before modifying /etc/ldap.conf is faulty. For example, check whether the service IP address is unreachable, the network delay is too long, or other abnormal software is deployed.

            Collect the fault information.

            -
            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select LdapClient for the target cluster.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.
            +
            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
            2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select LdapClient for the target cluster.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact O&M personnel and provide the collected logs.

            Alarm Clearing

            This alarm is automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-25006.html b/docs/mrs/umn/ALM-25006.html index c7b294d2..60be5338 100644 --- a/docs/mrs/umn/ALM-25006.html +++ b/docs/mrs/umn/ALM-25006.html @@ -56,7 +56,7 @@
            • Users cannot be queried because the OS executes commands too slowly.

            Procedure

            Check whether the sssd service is correctly started.

            -
            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. Find the IP address of HostName in Location of the alarm and record it as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
            2. Contact the O&M personnel to access the node using IP1 as user root. Run the ps -ef | grep sssd command and check whether the /usr/sbin/sssd process is started.

              • If the process is started, go to 3.
              • If the process is not started, go to 4.
              +
              1. On the MRS Manager portal, choose O&M > Alarm > Alarms. Find the IP address of HostName in Location of the alarm and record it as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
              2. Contact the O&M personnel to access the node using IP1 as user root. Run the ps -ef | grep sssd command and check whether the /usr/sbin/sssd process is started.

                • If the process is started, go to 3.
                • If the process is not started, go to 4.

              3. Check whether the sssd process queried in 2 has three subprocesses.

                • If yes, go to 5.
                • If no, go to 4.

              4. Run the service sssd restart command as user root to restart the sssd service. Then run the ps -ef | grep sssd command to check whether the sssd process is normal.

                In the normal state, the /usr/sbin/sssd process has three subprocesses: /usr/libexec/sssd/sssd_be, /usr/libexec/sssd/sssd_nss, and /usr/libexec/sssd/sssd_pam.

                • If it exists, go to 9.
                • If it does not exist, go to 13.
                @@ -69,7 +69,7 @@
                • If the configurations are correct, go to 7.
                • If the configurations are incorrect, go to 8.

              5. Run the /usr/sbin/sss_cache -G and /usr/sbin/sss_cache -U commands as user root. Wait for 2 minutes and run the id admin and id backup/manager commands to check whether results can be queried.

                • If results are queried, go to 9.
                • If no result is queried, go to 13.

              6. Run the vi /etc/nsswitch.conf command as user root. Correct the configurations in 6 and save the file. Run the service sssd restart command to restart the sssd service. Wait for 2 minutes and run the id admin and id backup/manager commands to check whether results can be queried.

                • If results are queried, go to 9.
                • If no result is queried, go to 13.
                -

              7. Log in to the FusionInsight Manager portal. Wait for 5 minutes and check whether the sssd Service Exception alarm is cleared.

                • If the alarm is cleared, no further action is required.
                • If the alarm persists, go to 10.
                +

              8. Log in to the MRS Manager portal. Wait for 5 minutes and check whether the sssd Service Exception alarm is cleared.

                • If the alarm is cleared, no further action is required.
                • If the alarm persists, go to 10.

              Check whether frame freezing occurs when running a command in the operating system.

              1. Log in to the faulty node as user root, run the id admin command, and check whether the command execution takes a long time. If the command execution takes more than 3 seconds, the command execution is deemed to be slow.

                • If yes, go to 11.
                • If no, go to 13.
                @@ -89,7 +89,7 @@ Feb 7 11:38:16 10-132-190-105 sssd[pam]: Starting up
                • If yes, go to 13.
                • If no, log in to other faulty nodes and run 10 to 12. Collect logs and check whether the first ldapserver node in the ldap_uri before modifying /etc/sssd/sssd.conf is faulty. For example, check whether the service IP address is unreachable, the network latency is too long, or other abnormal software is deployed.

              Collect fault information.

              -
              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
              2. Select LdapClient in the required cluster from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected fault logs.
              +
              1. On the MRS Manager portal, choose O&M > Log > Download.
              2. Select LdapClient in the required cluster from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected fault logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-25500.html b/docs/mrs/umn/ALM-25500.html index 45b7a163..661fa557 100644 --- a/docs/mrs/umn/ALM-25500.html +++ b/docs/mrs/umn/ALM-25500.html @@ -60,16 +60,16 @@

            Possible Causes

            • The node where the KrbServer service locates is faulty.
            • The OLdap service is abnormal.

            Procedure

            Check whether the node where the KrbServer service locates is faulty.

            -
            1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > KrbServer > Instance to go to the KrbServer instance page to obtain the host name of the node where the KrbServer service locates.
            2. On the Alarm page of the FusionInsight Manager system, check whether any alarm of Node Fault exists.

              • If yes, go to 3.
              • If no, go to 6.
              +
              1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > KrbServer > Instance to go to the KrbServer instance page to obtain the host name of the node where the KrbServer service locates.
              2. On the Alarm page of the MRS Manager system, check whether any alarm of Node Fault exists.

                • If yes, go to 3.
                • If no, go to 6.

              3. Check whether the host name in the alarm is consistent with the 1 host name.

                • If yes, go to 4.
                • If no, go to 6.

              4. Handle the alarm according to "ALM-12006 Node Fault".
              5. Check whether KrbServer Service Unavailable is cleared in the alarm list.

                • If yes, no further action is required.
                • If no, go to 6.

              Check whether the OLdap service is normal.

              -
              1. On the Alarm page of the FusionInsight Manager system, check whether any alarm of OLdap Resource Abnormal exists.

                • If yes, go to 7.
                • If no, go to 9.
                +
                1. On the Alarm page of the MRS Manager system, check whether any alarm of OLdap Resource Abnormal exists.

                  • If yes, go to 7.
                  • If no, go to 9.

                2. Handle the alarm according to "ALM-12004 OLdap Resource Abnormal".
                3. Check whether KrbServer Service Unavailable is cleared in the alarm list.

                  • If yes, no further action is required.
                  • If no, go to 9.

                Collect fault information.

                -
                1. On the FusionInsight Manager, choose O&M > Log > Download.
                2. Select KrbServer in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.
                +
                1. On the MRS Manager, choose O&M > Log > Download.
                2. Select KrbServer in the required cluster from the Service.
                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-26051.html b/docs/mrs/umn/ALM-26051.html index ee4a1fa7..d4331eda 100644 --- a/docs/mrs/umn/ALM-26051.html +++ b/docs/mrs/umn/ALM-26051.html @@ -60,7 +60,7 @@

            Possible Causes

            • The Kerberos cluster is faulty.
            • The ZooKeeper cluster is faulty or suspended.
            • The active and standby Nimbus nodes in the Storm cluster are abnormal

            Procedure

            Check the status of the Kerberos cluster. (Skip this step if the normal mode is used.)

            -
            1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services.
            2. Check whether the running status of the Kerberos service is Normal.

              • If yes, go to 5.
              • If no, go to 3.
              +
              1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services.
              2. Check whether the running status of the Kerberos service is Normal.

                • If yes, go to 5.
                • If no, go to 3.

              3. See the related maintenance information of ALM-25500 KrbServer Service Unavailable.
              4. Check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 5.

              Check the status of the ZooKeeper cluster.

              @@ -70,11 +70,11 @@

              Check the status of the active and standby Nimbus nodes.

              1. Choose Cluster > Name of the desired cluster > Services > Storm > Nimbus to go to the Nimbus Instances page.
              2. Check whether only one Nimbus node that is in the Active state in Roles.

                • If yes, go to 13.
                • If no, go to 10.

              3. Select two Nimbus role instances, choose More > Restart Instance, and check whether the instances restart successfully.

                • If yes, go to 11.
                • If no, go to 13.
                -

              4. Log in to the FusionInsight Manager portal again, choose Cluster > Name of the desired cluster > Services > Storm > Nimbus to check whether the running status is Normal.

                • If yes, go to 12.
                • If no, go to 13.
                +

              5. Log in to the MRS Manager portal again, choose Cluster > Name of the desired cluster > Services > Storm > Nimbus to check whether the running status is Normal.

                • If yes, go to 12.
                • If no, go to 13.

              6. Wait for 30 seconds and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 13.

              Collecting Fault Information

              -
              1. On the FusionInsight Manager, choose O&M > Log > Download.
              2. Select the following nodes in the required cluster from the Service drop-down list:

                • KrbServer

                  KrbServer logs do not need to be downloaded in normal mode.

                  +
                  1. On the MRS Manager, choose O&M > Log > Download.
                  2. Select the following nodes in the required cluster from the Service drop-down list:

                    • KrbServer

                      KrbServer logs do not need to be downloaded in normal mode.

                    • ZooKeeper
                    • Storm

                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.
                  diff --git a/docs/mrs/umn/ALM-26052.html b/docs/mrs/umn/ALM-26052.html index a4e5e406..60b1ce1d 100644 --- a/docs/mrs/umn/ALM-26052.html +++ b/docs/mrs/umn/ALM-26052.html @@ -73,7 +73,7 @@

              Collect fault information.

              -
              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
              2. Select Storm and ZooKeeper in the required cluster from the Service drop-down list box.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.
              +
              1. On the MRS Manager portal, choose O&M > Log > Download.
              2. Select Storm and ZooKeeper in the required cluster from the Service drop-down list box.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-26053.html b/docs/mrs/umn/ALM-26053.html index 7332526d..1b10f55c 100644 --- a/docs/mrs/umn/ALM-26053.html +++ b/docs/mrs/umn/ALM-26053.html @@ -71,13 +71,13 @@

          3. Wait several minutes, and check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 5.

          Increase the number of slots in each Supervisor.

          -
          1. Log in to the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Storm > Configurations > All Configurations.
          2. Increase the number of ports in the supervisor.slots.ports parameter of each Supervisor role and restart the instance.
          3. Wait several minutes, and check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 8.
            +
            1. Log in to the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Storm > Configurations > All Configurations.
            2. Increase the number of ports in the supervisor.slots.ports parameter of each Supervisor role and restart the instance.
            3. Wait several minutes, and check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 8.

            1. Perform capacity expansion for Supervisor.
            2. Wait several minutes, and check whether the alarm is cleared.

              • If yes, no further action is required.
              • If no, go to 10.

                Services are interrupted when the Supervisor is being restarted. Then, services are restored after the restarting.

            Collect fault information.

            -
            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
            2. Select Storm and ZooKeeper in the required cluster from the Service drop-down list box.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.
            +
            1. On the MRS Manager portal, choose O&M > Log > Download.
            2. Select Storm and ZooKeeper in the required cluster from the Service drop-down list box.
            3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
            4. Contact the O&M personnel and send the collected logs.

            Alarm Clearing

            After the fault is rectified, the system automatically clears this alarm.

            diff --git a/docs/mrs/umn/ALM-26054.html b/docs/mrs/umn/ALM-26054.html index 64bf6aa2..93493c72 100644 --- a/docs/mrs/umn/ALM-26054.html +++ b/docs/mrs/umn/ALM-26054.html @@ -66,13 +66,13 @@

            Possible Causes

            The heap memory of the Storm Nimbus instance on the node is overused or the heap memory is inappropriately allocated. As a result, the usage exceeds the threshold.

            Procedure

            Check the heap memory usage.

            -
            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Heap Memory Usage of Storm Nimbus Exceeds the Threshold > Location. Check the host name of the instance for which the alarm is generated.
            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Storm > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Nimbus > Heap Memory Usage of Nimbus. Click OK.
            3. Check whether the used heap memory of Nimbus reaches the threshold (The default value is 80% of the maximum heap memory) specified for Nimbus.

              • If yes, go to 4.
              • If no, go to 6.
              -

            4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Storm > Configurations > All Configurations > Nimbus > System. Change the value of -Xmx in NIMBUS_GC_OPTS based on site requirements, and click Save. Click OK.

              • You are advised to set -Xms and -Xmx to the same value to prevent adverse impact on performance when JVM dynamically adjusts the heap memory size.
              • The number of Workers grows as the Storm cluster scale increases. You can increase the value of GC_OPTS for Nimbus. The recommended value is as follows: If the number of Workers is 20, set -Xmx to a value greater than or equal to 1 GB. If the number of Workers exceeds 100, set -Xmx to a value greater than or equal to 5 GB.
              +
              1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Heap Memory Usage of Storm Nimbus Exceeds the Threshold > Location. Check the host name of the instance for which the alarm is generated.
              2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Storm > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Nimbus > Heap Memory Usage of Nimbus. Click OK.
              3. Check whether the used heap memory of Nimbus reaches the threshold (The default value is 80% of the maximum heap memory) specified for Nimbus.

                • If yes, go to 4.
                • If no, go to 6.
                +

              4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Storm > Configurations > All Configurations > Nimbus > System. Change the value of -Xmx in NIMBUS_GC_OPTS based on site requirements, and click Save. Click OK.

                • You are advised to set -Xms and -Xmx to the same value to prevent adverse impact on performance when JVM dynamically adjusts the heap memory size.
                • The number of Workers grows as the Storm cluster scale increases. You can increase the value of GC_OPTS for Nimbus. The recommended value is as follows: If the number of Workers is 20, set -Xmx to a value greater than or equal to 1 GB. If the number of Workers exceeds 100, set -Xmx to a value greater than or equal to 5 GB.

              5. Restart the affected services or instances and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 6.

              Collect fault information.

              -
              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
              2. Select the following node in the required cluster from the Service drop-down list.

                • NodeAgent
                • Storm
                +
                1. On the MRS Manager portal, choose O&M > Log > Download.
                2. Select the following node in the required cluster from the Service drop-down list.

                  • NodeAgent
                  • Storm

                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-27001.html b/docs/mrs/umn/ALM-27001.html index 7772db4e..a8d8aea2 100644 --- a/docs/mrs/umn/ALM-27001.html +++ b/docs/mrs/umn/ALM-27001.html @@ -60,11 +60,11 @@

              Possible Causes

              • The floating IP address does not exist.
              • There is no active DBServer instance.
              • The active and standby DBServer processes are abnormal.

              Procedure

              Check whether the floating IP address exists in the cluster environment.

              -
              1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > DBService > Instance.
              2. Check whether the active instance exists.

                • If yes, go to 3.
                • If no, go to 9.
                +
                1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > DBService > Instance.
                2. Check whether the active instance exists.

                  • If yes, go to 3.
                  • If no, go to 9.

                3. Select the active DBServer instance and record the IP address.
                4. Log in to the host that corresponds to the preceding IP address as user root, and run the ifconfig command to check whether the DBService floating IP address exists on the node.

                  • If yes, go to 5.
                  • If no, go to 9.

                5. Run the ping floatip command to check whether the DBService floating IP address can be pinged successfully.

                  • If yes, go to 6.
                  • If no, go to 9.

                6. Log in to the host that corresponds to the DBService floating IP address as user root, and run the command to delete the floating IP address.

                  ifconfig interface down

                  -

                7. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > DBService > More > Restart Service to restart DBService, and check whether DBService is restarted successfully.

                  • If yes, go to 8.
                  • If no, go to 9.
                  +

                8. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > DBService > More > Restart Service to restart DBService, and check whether DBService is restarted successfully.

                  • If yes, go to 8.
                  • If no, go to 9.

                9. Wait for about 2 minutes and check whether the alarm is cleared in the alarm list.

                  • If yes, no further action is required.
                  • If no, go to 14.

                Check the status of the active DBServer instance.

                @@ -86,11 +86,11 @@ NodeName ResName ResStatus ResHAS 10_5_89_66 gaussDB Standby_normal Normal Active_standby
                • If yes, go to 16.
                • If no, go to 19.

              3. Check whether the active and standby HA processes are in the abnormal state.

                • If yes, go to 17.
                • If no, go to 19.
                -

              4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > DBService > More > Restart Service to restart DBService, and check whether the system displays a message indicating that the restart is successful.

                • If yes, go to 18.
                • If no, go to 19.
                +

              5. On MRS Manager, choose Cluster > Name of the desired cluster > Services > DBService > More > Restart Service to restart DBService, and check whether the system displays a message indicating that the restart is successful.

                • If yes, go to 18.
                • If no, go to 19.

              6. Wait for about 2 minutes and check whether the alarm is cleared in the alarm list.

                • If yes, no further action is required.
                • If no, go to 19.

              Collect fault information.

              -
              1. On FusionInsight Manager, choose O&M > Log > Download.
              2. Select DBService in the required cluster and NodeAgent from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.
              +
              1. On MRS Manager, choose O&M > Log > Download.
              2. Select DBService in the required cluster and NodeAgent from the Service.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-27003.html b/docs/mrs/umn/ALM-27003.html index 789db304..daaa8e84 100644 --- a/docs/mrs/umn/ALM-27003.html +++ b/docs/mrs/umn/ALM-27003.html @@ -70,12 +70,12 @@

              Possible Causes

              The link between the active and standby DBService nodes is abnormal.

              Procedure

              Check whether the network between the active DBService server and the standby DBService server is normal.

              -
              1. In the alarm list on FusionInsight Manager, click in the row where the alarm is located in the real-time alarm list and view the standby DBService server address.
              2. Log in to the active DBService server as user root.
              1. Run the ping standby DBService heartbeat IP address command to check whether the standby DBService server is reachable.

                • If yes, go to 6.
                • If no, go to 4.
                +
                1. In the alarm list on MRS Manager, click in the row where the alarm is located in the real-time alarm list and view the standby DBService server address.
                2. Log in to the active DBService server as user root.
                1. Run the ping standby DBService heartbeat IP address command to check whether the standby DBService server is reachable.

                  • If yes, go to 6.
                  • If no, go to 4.

                2. Contact the network administrator to check whether the network is faulty.

                  • If yes, go to 5.
                  • If no, go to 6.

                3. Rectify the network fault and check whether the alarm is cleared from the alarm list.

                  • If yes, no further action is required.
                  • If no, go to 6.

                Collect fault information.

                -
                1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                2. Select the following nodes in the required cluster from the Service:

                  • DBService
                  • Controller
                  • NodeAgent
                  +
                  1. On the MRS Manager portal, choose O&M > Log > Download.
                  2. Select the following nodes in the required cluster from the Service:

                    • DBService
                    • Controller
                    • NodeAgent

                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-27004.html b/docs/mrs/umn/ALM-27004.html index 8fd07453..e4193339 100644 --- a/docs/mrs/umn/ALM-27004.html +++ b/docs/mrs/umn/ALM-27004.html @@ -75,7 +75,7 @@

              Possible Causes

              • The network between the active and standby nodes is unstable.
              • The standby DBService is abnormal.
              • The standby node disk space is full.
              • The CPU usage of the GaussDB process on the active DBService node is high. You need to locate the failure cause based on logs.

              Procedure

              Check whether the network between the active and standby nodes is normal.

              -
              1. On FusionInsight Manager, choose Cluster > Services > DBService > Instance, check the service IP address of the standby DBServer instance.
              2. Log in to the active DBService node as user root.
              3. Run the ping Standby DBService heartbeat IP address command to check whether the standby DBService node is reachable.

                • If yes, go to 6.
                • If no, go to 4.
                +
                1. On MRS Manager, choose Cluster > Services > DBService > Instance, check the service IP address of the standby DBServer instance.
                2. Log in to the active DBService node as user root.
                3. Run the ping Standby DBService heartbeat IP address command to check whether the standby DBService node is reachable.

                  • If yes, go to 6.
                  • If no, go to 4.

                4. Contact the network administrator to check whether the network is faulty.

                  • If yes, go to 5.
                  • If no, go to 6.

                5. Rectify the network fault and check whether the alarm is cleared.

                  • If yes, no further action is required.
                  • If no, go to 6.

                @@ -92,7 +92,7 @@

              4. Expand the disk capacity.
              5. After the disk capacity is expanded, wait 2 minutes and check whether the alarm is cleared.

                • If yes, no further action is required.
                • If no, go to 16.

              Collect fault information.

              -
              1. On the FusionInsight Manager portal, choose O&M > Log > Download.
              2. In the Service area, select DBService of the target cluster and OS, OS Statistics, and OS Performance under OMS, and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.
              +
              1. On the MRS Manager portal, choose O&M > Log > Download.
              2. In the Service area, select DBService of the target cluster and OS, OS Statistics, and OS Performance under OMS, and click OK.
              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
              4. Contact the O&M personnel and send the collected logs.

              Alarm Clearing

              After the fault is rectified, the system automatically clears this alarm.

              diff --git a/docs/mrs/umn/ALM-27005.html b/docs/mrs/umn/ALM-27005.html index b977b561..e98e7a89 100644 --- a/docs/mrs/umn/ALM-27005.html +++ b/docs/mrs/umn/ALM-27005.html @@ -67,16 +67,16 @@

              Procedure

              Checking whether too many data connections are used

              -
              1. On FusionInsight Manager, click DBService in the service list on the left navigation pane. The DBService monitoring page is displayed.
              2. Observe the number of connections used by the database user, as shown in Figure 1. Based on the service scenario, reduce the number of database user connections.

                Figure 1 Number of connections used by database users
                +
                1. On MRS Manager, click DBService in the service list on the left navigation pane. The DBService monitoring page is displayed.
                2. Observe the number of connections used by the database user, as shown in Figure 1. Based on the service scenario, reduce the number of database user connections.

                  Figure 1 Number of connections used by database users

                3. Wait for 2 minutes and check whether the alarm is automatically cleared.

                  • If it is, no further action is required.
                  • If it is not, go to 4.

                Checking whether the maximum number of database connections is properly configured

                -
                1. Log in to FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > DBService > Configurations. On the displayed page, select the All Configurations tab, and increase the maximum number of database connections based on service requirements, as shown in Figure 2. Click Save. In the displayed Save configuration dialog box, click OK.

                  Figure 2 Setting the maximum number of database connections
                  -

                1. After the maximum number of database connections is changed, restart DBService (do not restart the upper-layer services).

                  Procedure: Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Services > DBService. On the displayed page, choose More > Restart Service. Enter the password of the current login user and click OK. Do not select Restart upper-layer services., click OK.

                  +
                  1. Log in to MRS Manager, choose Cluster > Name of the desired cluster > Services > DBService > Configurations. On the displayed page, select the All Configurations tab, and increase the maximum number of database connections based on service requirements, as shown in Figure 2. Click Save. In the displayed Save configuration dialog box, click OK.

                    Figure 2 Setting the maximum number of database connections
                    +

                  1. After the maximum number of database connections is changed, restart DBService (do not restart the upper-layer services).

                    Procedure: Log in to MRS Manager and choose Cluster > Name of the desired cluster > Services > DBService. On the displayed page, choose More > Restart Service. Enter the password of the current login user and click OK. Do not select Restart upper-layer services., click OK.

                  1. After the service is restarted, wait for 2 minutes and check whether the alarm is cleared.

                    • If it is, no further action is required.
                    • If it is not, go to 7.

                  Checking whether the alarm threshold or trigger count is properly configured

                  -
                  1. Log in to FusionInsight Manager and change the alarm threshold and alarm trigger count based on the actual database connection usage.

                    Choose O&M> Alarm > Thresholds > Name of the desired cluster > DBService > Database > Database Connections Usage (DBServer). In the Database Connections Usage (DBServer) area, click the pencil icon next to Trigger Count. In the displayed dialog box, change the trigger count, as shown in Figure 3.

                    +
                    1. Log in to MRS Manager and change the alarm threshold and alarm trigger count based on the actual database connection usage.

                      Choose O&M> Alarm > Thresholds > Name of the desired cluster > DBService > Database > Database Connections Usage (DBServer). In the Database Connections Usage (DBServer) area, click the pencil icon next to Trigger Count. In the displayed dialog box, change the trigger count, as shown in Figure 3.

                      Trigger Count: If the usage of the number of database connections exceeds the threshold consecutively for more than the value of this parameter, an alarm is generated.

                      Figure 3 Setting alarm trigger count
                      @@ -85,7 +85,7 @@

                    1. Wait for 2 minutes and check whether the alarm is automatically cleared.

                      • If it is, no further action is required.
                      • If it is not, go to 9.

                    Collect fault information

                    -
                    1. On FusionInsight Manager, choose O&M > Log > Download.
                    2. Select DBService in the required cluster from the Service.
                    3. Specify the host for collecting logs by setting the Host parameter that is optional. By default, all hosts are selected.
                    4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    5. Contact the O&M personnel and send the collected fault logs.
                    +
                    1. On MRS Manager, choose O&M > Log > Download.
                    2. Select DBService in the required cluster from the Service.
                    3. Specify the host for collecting logs by setting the Host parameter that is optional. By default, all hosts are selected.
                    4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    5. Contact the O&M personnel and send the collected fault logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    Related Information

                    None

                    diff --git a/docs/mrs/umn/ALM-27006.html b/docs/mrs/umn/ALM-27006.html index dd90fe81..01839e6b 100644 --- a/docs/mrs/umn/ALM-27006.html +++ b/docs/mrs/umn/ALM-27006.html @@ -70,7 +70,7 @@

                    Possible Causes

                    • The alarm threshold is improperly configured.
                    • The data volume of the database is too large or the disk configuration cannot meet service requirements, causing excessive disk usage.

                    Procedure

                    Check whether the threshold is set properly.

                    -
                    1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > DBService > Database > Disk Space Usage of the Data Directory to check whether the alarm threshold is proper (the default value 80% is a proper value).

                      • If yes, go to 3.
                      • If no, go to 2.
                      +
                      1. On MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > DBService > Database > Disk Space Usage of the Data Directory to check whether the alarm threshold is proper (the default value 80% is a proper value).

                        • If yes, go to 3.
                        • If no, go to 2.

                      2. Change the alarm threshold based on the actual service situation.
                      3. Choose Cluster > Name of the desired cluster > Services > DBService. On the Dashboard page, view the Disk Space Usage of the Data Directory chart and check whether the disk space usage of the data directory is lower than the threshold.

                        • If yes, go to 4.
                        • If no, go to 5.

                      4. Wait 2 minutes and check whether the alarm is automatically cleared.

                        • If yes, no further action is required.
                        • If no, go to 5.

                        Check whether large files are incorrectly written into the disk.

                        @@ -79,7 +79,7 @@
                        • If yes, go to 7.
                        • If no, go to 8.

                      5. Handle the large files based on the actual scenario and check whether the alarm is cleared 2 minutes later.

                        • If yes, no further action is required.
                        • If no, go to 8.

                        Collect fault information.

                        -

                      6. On FusionInsight Manager, choose O&M > Log > Download.
                      7. Expand the Service drop-down list, and select DBService for the target cluster.
                      8. Specify the host for collecting logs by setting the Host parameter which is optional. By default, all hosts are selected.
                      9. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      10. Contact the O&M personnel and send the collected logs.
                      +

                    2. On MRS Manager, choose O&M > Log > Download.
                    3. Expand the Service drop-down list, and select DBService for the target cluster.
                    4. Specify the host for collecting logs by setting the Host parameter which is optional. By default, all hosts are selected.
                    5. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                    6. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    diff --git a/docs/mrs/umn/ALM-27007.html b/docs/mrs/umn/ALM-27007.html index 8d242ab3..613679a3 100644 --- a/docs/mrs/umn/ALM-27007.html +++ b/docs/mrs/umn/ALM-27007.html @@ -60,7 +60,7 @@

                    Possible Causes

                    The disk configuration cannot meet service requirements. The disk usage reaches the upper limit.

                    Procedure

                    Check whether the disk space usage reaches the upper limit.

                    -
                    1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > DBService.
                    2. On the Dashboard page, view the Disk Space Usage of the Data Directory chart and check whether the disk space usage of the data directory exceeds 90%.

                      • If yes, go to 3.
                      • If no, go to 13.
                      +
                      1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > DBService.
                      2. On the Dashboard page, view the Disk Space Usage of the Data Directory chart and check whether the disk space usage of the data directory exceeds 90%.

                        • If yes, go to 3.
                        • If no, go to 13.

                      3. Log in to the active management node of the DBServer as user omm and run the following commands to check whether the database enters the read-only mode:

                        source $DBSERVER_HOME/.dbservice_profile

                        gsql -U omm -W password -d postgres -p 20051

                        show default_transaction_read_only;

                        @@ -77,13 +77,13 @@

                        vi ${DBSERVICE_SOFTWARE_DIR}/tools/dbservice.properties

                      4. Change the value of gaussdb_readonly_auto to OFF.
                      5. Run the following command to open the postgresql.conf file:

                        vi ${DBSERVICE_DATA_DIR}/postgresql.conf

                      6. Delete default_transaction_read_only = on.
                      7. Run the following command for the configuration to take effect:

                        gs_ctl reload -D ${DBSERVICE_DATA_DIR}

                        -

                      8. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. On the right of the alarm "Database Enters the Read-Only Mode", click Clear in the Operation column. In the dialog box that is displayed, click OK to manually clear the alarm.
                      9. Log in to the active management node of the DBServer as user omm and run the following commands to view the files whose size exceeds 500 MB in the data directory and check whether there are large files incorrectly written into the directory:

                        source $DBSERVER_HOME/.dbservice_profile

                        +

                      10. Log in to MRS Manager and choose O&M > Alarm > Alarms. On the right of the alarm "Database Enters the Read-Only Mode", click Clear in the Operation column. In the dialog box that is displayed, click OK to manually clear the alarm.
                      11. Log in to the active management node of the DBServer as user omm and run the following commands to view the files whose size exceeds 500 MB in the data directory and check whether there are large files incorrectly written into the directory:

                        source $DBSERVER_HOME/.dbservice_profile

                        find "$DBSERVICE_DATA_DIR"/../ -type f -size +500M

                        • If yes, go to 11.
                        • If no, go to 13.
                        -

                      12. Handle the files that are incorrectly written into the directory based on the actual scenario.
                      13. Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Services > DBService. On the Dashboard page, view the Disk Space Usage of the Data Directory chart and check whether the disk space usage is lower than 80%.

                        • If yes, no further action is required.
                        • If no, go to 13.
                        +

                      14. Handle the files that are incorrectly written into the directory based on the actual scenario.
                      15. Log in to MRS Manager and choose Cluster > Name of the desired cluster > Services > DBService. On the Dashboard page, view the Disk Space Usage of the Data Directory chart and check whether the disk space usage is lower than 80%.

                        • If yes, no further action is required.
                        • If no, go to 13.

                      Collect fault information.

                      -
                      1. On FusionInsight Manager, choose O&M > Log > Download.
                      2. Expand the Service drop-down list, and select DBService for the target cluster.
                      3. Specify the host for collecting logs by setting the Host parameter which is optional. By default, all hosts are selected.
                      4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      5. Contact the O&M personnel and send the collected logs.
                      +
                      1. On MRS Manager, choose O&M > Log > Download.
                      2. Expand the Service drop-down list, and select DBService for the target cluster.
                      3. Specify the host for collecting logs by setting the Host parameter which is optional. By default, all hosts are selected.
                      4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      5. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    diff --git a/docs/mrs/umn/ALM-38000.html b/docs/mrs/umn/ALM-38000.html index 0031aa26..2abaf6ce 100644 --- a/docs/mrs/umn/ALM-38000.html +++ b/docs/mrs/umn/ALM-38000.html @@ -60,7 +60,7 @@

                    Possible Causes

                    • The KrbServer service is abnormal.(Skip this step if the normal mode is used.)
                    • The ZooKeeper service is abnormal or does not respond.
                    • The Broker instance in the Kafka cluster are abnormal.

                    Procedure

                    Check the status of the KrbServer service. (Skip this step if the normal mode is used.)

                    -
                    1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > KrbServer.
                    2. Check whether the running status of the KrbServer service is Normal.

                      • If yes, go to 5.
                      • If no, go to 3.
                      +
                      1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > KrbServer.
                      2. Check whether the running status of the KrbServer service is Normal.

                        • If yes, go to 5.
                        • If no, go to 3.

                      3. Rectify the fault by following the steps provided in ALM-25500 KrbServer Service Unavailable.
                      4. Perform 2 again.

                      Check the status of the ZooKeeper cluster.

                      1. Check whether the running status of the ZooKeeper service is Normal.

                        • If yes, go to 8.
                        • If no, go to 6.
                        @@ -72,7 +72,7 @@

                      2. Wait for 30 seconds and check whether the alarm is cleared.

                        • If yes, no further action is required.
                        • If no, go to 13.

                      Collecting Fault Information

                      -
                      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                      2. Select Kafka in the required cluster from the Service drop-down list.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.
                      +
                      1. On the MRS Manager portal, choose O&M > Log > Download.
                      2. Select Kafka in the required cluster from the Service drop-down list.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    diff --git a/docs/mrs/umn/ALM-38001.html b/docs/mrs/umn/ALM-38001.html index c196f1f5..694a85c6 100644 --- a/docs/mrs/umn/ALM-38001.html +++ b/docs/mrs/umn/ALM-38001.html @@ -71,7 +71,7 @@

                    Possible Causes

                    • The configuration (such as number and size) of the disks for storing Kafka data cannot meet the requirement of the current service traffic, due to which the disk usage reaches the upper limit.
                    • Data retention time is too long, due to which the data disk usage reaches the upper limit.
                    • The service plan does not distribute data evenly, due to which the usage of some disks reaches the upper limit.

                    Procedure

                    Check the disk configuration of Kafka data.

                    -
                    1. On the FusionInsight Manager portal and click O&M > Alarm > Alarms.
                    2. In the alarm list, locate the alarm and obtain HostName from Location.
                    3. Click Cluster > Name of the desired cluster > Hosts.
                    4. In the host list, click the host name obtained in 2.
                    5. Check whether the Disk area contains the partition name in the alarm.

                      • If yes, go to 6.
                      • If no, manually clear the alarm and no further operation is required.
                      +
                      1. On the MRS Manager portal and click O&M > Alarm > Alarms.
                      2. In the alarm list, locate the alarm and obtain HostName from Location.
                      3. Click Cluster > Name of the desired cluster > Hosts.
                      4. In the host list, click the host name obtained in 2.
                      5. Check whether the Disk area contains the partition name in the alarm.

                        • If yes, go to 6.
                        • If no, manually clear the alarm and no further operation is required.

                      6. Check whether the disk partition usage contained in the alarm reaches 100% in the Disk area.

                      Check the Kafka data storage duration.

                      @@ -85,7 +85,7 @@
                      1. In the Instance area, click Broker. In the Real Time area of Broker, Click the drop-down menu in the Chart area and choose Customize to customize monitoring items.
                      2. In the dialog box, select Disk > Broker Disk Usage and click OK.

                        The Kafka disk usage information is displayed.

                      3. View the information in 12 to check whether there is only the disk parathion for which the alarm is generated in 2.

                        • If yes, go to 14.
                        • If no, go to 15.

                      4. Perform disk planning and mount a new disk again. Go to the Instance Configurations page of the node for which the alarm is generated, modify log.dirs, add other disk directories, and restart the Kafka instance.
                      5. Determine whether to shorten the data retention time configured on Kafka based on service requirements and service traffic.

                        • If yes, go to 16.
                        • If no, go to 17.
                        -

                      6. Log in to FusionInsight Manager, select Cluster > Name of the desired cluster > Services > Kafka > Configurations, and click All Configurations. In the search box on the right, enter log.retention.hours. The value of the parameter indicates the default data retention time of the topic. You can change the value to a smaller one.

                        • For a topic whose data retention time is configured alone, the modification of the data retention time on the Kafka Service Configuration page does not take effect.
                        • To modify the data retention time for a topic, use the Kafka client command-line interface (CLI) to configure the topic.

                          Example: kafka-topics.sh --zookeeper "ZooKeeper IP address:2181/kafka" --alter --topic "Topic bane" --config retention.ms= "retention time"

                          +

                        • Log in to MRS Manager, select Cluster > Name of the desired cluster > Services > Kafka > Configurations, and click All Configurations. In the search box on the right, enter log.retention.hours. The value of the parameter indicates the default data retention time of the topic. You can change the value to a smaller one.

                          • For a topic whose data retention time is configured alone, the modification of the data retention time on the Kafka Service Configuration page does not take effect.
                          • To modify the data retention time for a topic, use the Kafka client command-line interface (CLI) to configure the topic.

                            Example: kafka-topics.sh --zookeeper "ZooKeeper IP address:2181/kafka" --alter --topic "Topic bane" --config retention.ms= "retention time"

                        • Check whether the usage of some disks reaches the upper limit due to unreasonable configuration of the partitions of some topics. For example, the number of partitions configured for a topic with large data volume is smaller than the number of disks. In this case, the data is not evenly allocated to disks.

                          If you do not know which topic has large data volume, you can log in to an instance node based on the host node information obtained in 2, and go to the data directory (directory specified by log.dirs before the modification in 14) to check whether there is topic with partition that use large disk space.

                          @@ -101,14 +101,14 @@

                        • Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 22.

                      Collect fault information.

                      -
                      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                      2. Select Kafka in the required cluster from the Service drop-down list.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.
                      +
                      1. On the MRS Manager portal, choose O&M > Log > Download.
                      2. Select Kafka in the required cluster from the Service drop-down list.
                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                      4. Contact the O&M personnel and send the collected logs.

                    Alarm Clearing

                    After the fault is rectified, the system automatically clears this alarm.

                    -

                    Related Information

                    1. Log in to FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Kafka > Instance, stop the Broker instance whose status is Restoring, record the management IP address of the node where the Broker instance is located, and record broker.id. The value can be obtained by using the following method: Click the role name. On the Configurations page, select All Configurations, and search for the broker.id parameter.
                    2. Log in to the recorded management IP address as user root, and run the df -lh command to view the mounted directory whose disk usage is 100%, for example, ${BIGDATA_DATA_HOME}/kafka/data1.
                    3. Go to the directory, run the du -sh * command to view the size of each file in the directory,check whether files other than kafka-logs exist, and determine whether these files can be deleted or migrated.

                      • If yes, go to 8.
                      • If no, go to 4.
                      +

                      Related Information

                      1. Log in to MRS Manager, choose Cluster > Name of the desired cluster > Services > Kafka > Instance, stop the Broker instance whose status is Restoring, record the management IP address of the node where the Broker instance is located, and record broker.id. The value can be obtained by using the following method: Click the role name. On the Configurations page, select All Configurations, and search for the broker.id parameter.
                      2. Log in to the recorded management IP address as user root, and run the df -lh command to view the mounted directory whose disk usage is 100%, for example, ${BIGDATA_DATA_HOME}/kafka/data1.
                      3. Go to the directory, run the du -sh * command to view the size of each file in the directory,check whether files other than kafka-logs exist, and determine whether these files can be deleted or migrated.

                        • If yes, go to 8.
                        • If no, go to 4.

                      4. Go to the kafka-logs directory, run the du -sh * command, select a partition folder to be moved. The naming rule is Topic name-Partition ID. Record the topic and partition.
                      5. Modify the recovery-point-offset-checkpoint and replication-offset-checkpoint files in the kafka-logs directory in the same way.

                        1. Decrease the number in the second line in the file. (To remove multiple directories, the number deducted is equal to the number of files to be removed.)
                        2. Delete the line of the to-be-removed partition. (The line structure is "Topic name Partition ID Offset". Save the data before deletion. Subsequently, the content must be added to the file of the same name in the destination directory.)

                      6. Modify the recovery-point-offset-checkpoint and replication-offset-checkpoint files in the destination data directory. For example, ${BIGDATA_DATA_HOME}/kafka/data2/kafka-logs in the same way.

                        • Increase the number in the second line in the file. (To move multiple directories, the number added is equal to the number of files to be moved.)
                        • Add the to-be moved partition to the end of the file. (The line structure is "Topic name Partition ID Offset". You can copy the line data saved in 5.)
                        -

                      7. Move the partition to the destination directory. After the partition is moved, run the chown omm:wheel -R Partition directory command to modify the directory owner group for the partition.
                      8. Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Services > Kafka > Instance to start the Broker instance.
                      9. Wait for 5 to 10 minutes and check whether the health status of the Broker instance is Normal.

                        • If yes, resolve the disk capacity insufficiency problem according to the handling method of "ALM-38001 Insufficient Kafka Disk Space" after the alarm is cleared.
                        • If no, contact the O&M personnel.
                        +

                      10. Move the partition to the destination directory. After the partition is moved, run the chown omm:wheel -R Partition directory command to modify the directory owner group for the partition.
                      11. Log in to MRS Manager and choose Cluster > Name of the desired cluster > Services > Kafka > Instance to start the Broker instance.
                      12. Wait for 5 to 10 minutes and check whether the health status of the Broker instance is Normal.

                        • If yes, resolve the disk capacity insufficiency problem according to the handling method of "ALM-38001 Insufficient Kafka Disk Space" after the alarm is cleared.
                        • If no, contact the O&M personnel.

                    diff --git a/docs/mrs/umn/ALM-38002.html b/docs/mrs/umn/ALM-38002.html index 35096afb..b479c9d3 100644 --- a/docs/mrs/umn/ALM-38002.html +++ b/docs/mrs/umn/ALM-38002.html @@ -65,15 +65,15 @@

                    Possible Causes

                    The heap memory of the Kafka instance is overused or the heap memory is inappropriately allocated.

                    Procedure

                    Check heap memory usage.

                    -
                    1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Kafka Heap Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                    2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area, choose Customize > Process > Heap Memory Usage of Kafka, and click OK.
                    3. Check whether the used heap memory of Kafka reaches 95% of the maximum heap memory specified for Kafka.

                      • If yes, go to 4.
                      • If no, go to 6.
                      +
                      1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Kafka Heap Memory Usage Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                      2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area, choose Customize > Process > Heap Memory Usage of Kafka, and click OK.
                      3. Check whether the used heap memory of Kafka reaches 95% of the maximum heap memory specified for Kafka.

                        • If yes, go to 4.
                        • If no, go to 6.

                      Check the heap memory size configured for Kafka.

                      -
                      1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations> Broker(Role) > Environment. Increase the value of KAFKA_HEAP_OPTS by referring to the Note.

                        • It is recommended that -Xmx and -Xms be set to the same value.
                        • You are advised to view Heap Memory Usage of Kafka by referring to 2, and set the value of KAFKA_HEAP_OPTS to twice the value of Heap Memory Used by Kafka.
                        +
                        1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations> Broker(Role) > Environment. Increase the value of KAFKA_HEAP_OPTS by referring to the Note.

                          • It is recommended that -Xmx and -Xms be set to the same value.
                          • You are advised to view Heap Memory Usage of Kafka by referring to 2, and set the value of KAFKA_HEAP_OPTS to twice the value of Heap Memory Used by Kafka.

                        2. Check whether the alarm is cleared.

                          • If yes, no further action is required.
                          • If no, go to 6.

                        Collect fault information.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                        2. Select Kafka in the required cluster from the Service drop-down list.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected logs.
                        +
                        1. On the MRS Manager portal, choose O&M > Log > Download.
                        2. Select Kafka in the required cluster from the Service drop-down list.
                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                        4. Contact the O&M personnel and send the collected logs.

                        Alarm Clearing

                        After the fault is rectified, the system automatically clears this alarm.

                        diff --git a/docs/mrs/umn/ALM-38004.html b/docs/mrs/umn/ALM-38004.html index 03a4365d..97849c67 100644 --- a/docs/mrs/umn/ALM-38004.html +++ b/docs/mrs/umn/ALM-38004.html @@ -65,15 +65,15 @@

                        Possible Causes

                        The direct memory of the Kafka instance is overused or the direct memory is inappropriately allocated.

                        Procedure

                        Check the direct memory usage.

                        -
                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Kafka Direct Memory Usage Exceeds the Threshold > Location to check the host name of the instance for which the alarm is generated.
                        2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the Chart area and choose Customize > Process > Kafka Direct Memory Usage, and click OK.
                        3. Check whether the used direct memory of Kafka reaches 80% of the maximum direct memory specified for Kafka.

                          • If yes, go to 4.
                          • If no, go to 7.
                          +
                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Kafka Direct Memory Usage Exceeds the Threshold > Location to check the host name of the instance for which the alarm is generated.
                          2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the Chart area and choose Customize > Process > Kafka Direct Memory Usage, and click OK.
                          3. Check whether the used direct memory of Kafka reaches 80% of the maximum direct memory specified for Kafka.

                            • If yes, go to 4.
                            • If no, go to 7.

                          Check the direct memory size configured for the Kafka.

                          -
                          1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations > Broker(Role) > Environment to increase the value of -Xmx configured in the KAFKA_HEAP_OPTS parameter by referring to the Note.

                            • It is recommended that -Xmx and -Xms be set to the same value.
                            • You are advised to view Kafka Direct Memory Usage by referring to 2, and set the value of KAFKA_HEAP_OPTS to twice the value of Direct Memory Used by Kafka.
                            +
                            1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations > Broker(Role) > Environment to increase the value of -Xmx configured in the KAFKA_HEAP_OPTS parameter by referring to the Note.

                              • It is recommended that -Xmx and -Xms be set to the same value.
                              • You are advised to view Kafka Direct Memory Usage by referring to 2, and set the value of KAFKA_HEAP_OPTS to twice the value of Direct Memory Used by Kafka.

                            2. Save the configuration and restart the Kafka service.
                            3. Check whether the alarm is cleared.

                              • If yes, no further action is required.
                              • If no, go to 7.

                            Collect fault information.

                            -
                            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                            2. Select Kafka in the required cluster from the Service drop-down list.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.
                            +
                            1. On the MRS Manager portal, choose O&M > Log > Download.
                            2. Select Kafka in the required cluster from the Service drop-down list.
                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                            4. Contact the O&M personnel and send the collected logs.

                            Alarm Clearing

                            After the fault is rectified, the system automatically clears this alarm.

                            diff --git a/docs/mrs/umn/ALM-38005.html b/docs/mrs/umn/ALM-38005.html index 4666c188..b08786e1 100644 --- a/docs/mrs/umn/ALM-38005.html +++ b/docs/mrs/umn/ALM-38005.html @@ -65,16 +65,16 @@

                            Possible Causes

                            The Kafka GC duration of the node is too long or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                            Procedure

                            Check the GC duration.

                            -
                            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > GC Duration of the Broker Process Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area, choose Customize > Process > Broker GC Duration per Minute, and click OK.
                            3. Check whether the GC duration of the Broker process collected every minute exceeds the threshold (12 seconds by default).

                              • If yes, go to 4.
                              • If no, go to 7.
                              +
                              1. On the MRS Manager portal, choose O&M > Alarm > Alarms > GC Duration of the Broker Process Exceeds the Threshold > Location. Check the host name of the instance involved in this alarm.
                              2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area, choose Customize > Process > Broker GC Duration per Minute, and click OK.
                              3. Check whether the GC duration of the Broker process collected every minute exceeds the threshold (12 seconds by default).

                                • If yes, go to 4.
                                • If no, go to 7.

                              Check the direct memory size configured for the Kafka.

                              -
                              1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations > Broker(Role) > Environment to increase the value of -Xmx configured in the KAFKA_HEAP_OPTS parameter by referring to the Note.

                                • It is recommended that -Xmx and -Xms be set to the same value.
                                • You are advised to set the value of KAFKA_HEAP_OPTS to twice the value of Direct Memory Used by Kafka.

                                  On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area and choose Customize > Process > Kafka Direct Memory Resource Status to check the value of Direct Memory Used by Kafka.

                                  +
                                  1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations > Broker(Role) > Environment to increase the value of -Xmx configured in the KAFKA_HEAP_OPTS parameter by referring to the Note.

                                    • It is recommended that -Xmx and -Xms be set to the same value.
                                    • You are advised to set the value of KAFKA_HEAP_OPTS to twice the value of Direct Memory Used by Kafka.

                                      On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area and choose Customize > Process > Kafka Direct Memory Resource Status to check the value of Direct Memory Used by Kafka.

                                  2. Save the configuration and restart the Kafka service.
                                  3. Check whether the alarm is cleared.

                                    • If yes, no further action is required.
                                    • If no, go to 7.

                                  Collect fault information.

                                  -
                                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                  2. Select Kafka in the required cluster from the Service drop-down list.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.
                                  +
                                  1. On the MRS Manager portal, choose O&M > Log > Download.
                                  2. Select Kafka in the required cluster from the Service drop-down list.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.

                                Alarm Clearing

                                After the fault is rectified, the system automatically clears this alarm.

                                diff --git a/docs/mrs/umn/ALM-38006.html b/docs/mrs/umn/ALM-38006.html index 4e370203..6c0b6af7 100644 --- a/docs/mrs/umn/ALM-38006.html +++ b/docs/mrs/umn/ALM-38006.html @@ -60,12 +60,12 @@

                                Possible Causes

                                Some nodes where the Broker instance resides are abnormal or stop running. As a result, replicas of some partitions in Kafka are out of the in-sync replicas (ISR) set.

                                Procedure

                                Check Broker instances.

                                -
                                1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. The Kafka instances page is displayed.
                                2. Check whether faulty nodes exist among all Broker nodes.

                                  • If yes, record the host name of the node and go to 3.
                                  • If no, go to 5.
                                  -

                                3. On the FusionInsight Manager portal, click O&M > Alarm > Alarms to check whether the fault described in 2 exists in the alarm information and handle the alarm based on corresponding methods.
                                4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. The Kafka instances page is displayed.
                                5. Check whether stopped nodes exist among all Broker instance.

                                  • If yes, go to 6.
                                  • If no, go to 7.
                                  +
                                  1. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. The Kafka instances page is displayed.
                                  2. Check whether faulty nodes exist among all Broker nodes.

                                    • If yes, record the host name of the node and go to 3.
                                    • If no, go to 5.
                                    +

                                  3. On the MRS Manager portal, click O&M > Alarm > Alarms to check whether the fault described in 2 exists in the alarm information and handle the alarm based on corresponding methods.
                                  4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. The Kafka instances page is displayed.
                                  5. Check whether stopped nodes exist among all Broker instance.

                                    • If yes, go to 6.
                                    • If no, go to 7.

                                  6. Select all stopped Broker instances and click Start Instance.
                                  7. Check whether the alarm is cleared.

                                    • If yes, no further action is required.
                                    • If no, go to 8.

                                  Collect fault information.

                                  -
                                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                  2. Select Kafka in the required cluster from the Service drop-down list.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.
                                  +
                                  1. On the MRS Manager portal, choose O&M > Log > Download.
                                  2. Select Kafka in the required cluster from the Service drop-down list.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.

                                Alarm Clearing

                                After the fault is rectified, the system automatically clears this alarm.

                                diff --git a/docs/mrs/umn/ALM-38007.html b/docs/mrs/umn/ALM-38007.html index 771e175a..9ddc77f5 100644 --- a/docs/mrs/umn/ALM-38007.html +++ b/docs/mrs/umn/ALM-38007.html @@ -65,14 +65,14 @@

                                Possible Causes

                                • The Sssd service is abnormal.
                                • Some Broker instances stop running.

                                Procedure

                                Check whether the Sssd service is abnormal.

                                -
                                1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Status of Kafka Default User Is Abnormal > Location to check the host name of the instance for which the alarm is generated.
                                2. Find the host information in the alarm information and log in to the host.
                                3. Run the id -Gn kafka command and check whether "No such user" is displayed in the command output.

                                  • If yes, record the host name of the node and go to 4.
                                  • If no, go to 6.
                                  -

                                4. On the FusionInsight Manager home page, choose O&M > Alarm > Alarms. Check whether there is Sssd Service Exception in the alarm information. If there is, handle the alarm based on alarm information.
                                +
                                1. On the MRS Manager portal, choose O&M > Alarm > Alarms > Status of Kafka Default User Is Abnormal > Location to check the host name of the instance for which the alarm is generated.
                                2. Find the host information in the alarm information and log in to the host.
                                3. Run the id -Gn kafka command and check whether "No such user" is displayed in the command output.

                                  • If yes, record the host name of the node and go to 4.
                                  • If no, go to 6.
                                  +

                                4. On the MRS Manager home page, choose O&M > Alarm > Alarms. Check whether there is Sssd Service Exception in the alarm information. If there is, handle the alarm based on alarm information.

                                Check the running status of the Broker instance.

                                -
                                1. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. The Kafka instance page is displayed.
                                2. Check whether there are stopped nodes on all Broker instances.

                                  • If yes, go to 7.
                                  • If no, go to 8.
                                  +
                                  1. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. The Kafka instance page is displayed.
                                  2. Check whether there are stopped nodes on all Broker instances.

                                    • If yes, go to 7.
                                    • If no, go to 8.

                                  3. Select all stopped Broker instances and click Start Instance.
                                  4. Check whether the alarm is cleared.

                                    • If yes, no further action is required.
                                    • If no, go to 9.

                                  Collect fault information.

                                  -
                                  1. On FusionInsight Manager, choose O&M > Log > Download.
                                  2. In the Service area, select Kafka in the required cluster.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.
                                  +
                                  1. On MRS Manager, choose O&M > Log > Download.
                                  2. In the Service area, select Kafka in the required cluster.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.

                                Alarm Clearing

                                After the fault is rectified, the system automatically clears this alarm.

                                diff --git a/docs/mrs/umn/ALM-38008.html b/docs/mrs/umn/ALM-38008.html index eaab1aa0..6653d627 100644 --- a/docs/mrs/umn/ALM-38008.html +++ b/docs/mrs/umn/ALM-38008.html @@ -74,10 +74,10 @@

                              2. Restore the owner group of the data directory and its subdirectories to omm:wheel.

                                • If yes, go to 6.
                                • If no, go to 5.

                              Check whether the disk where the data directory is located is faulty.

                              -
                              1. In the upper-level directory of the data directory, create and delete files as user omm. Check whether data read/write on the disk is normal.
                              2. Replace or repair the disk where the data directory is located to ensure that data read/write on the disk is normal.
                              3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. On the Kafka instance page that is displayed, restart the Broker instance on the host recorded in 2.
                              4. After Broker is started, check whether the alarm is cleared.

                                • If yes, no further action is required.
                                • If no, go to 8.
                                +
                                1. In the upper-level directory of the data directory, create and delete files as user omm. Check whether data read/write on the disk is normal.
                                2. Replace or repair the disk where the data directory is located to ensure that data read/write on the disk is normal.
                                3. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. On the Kafka instance page that is displayed, restart the Broker instance on the host recorded in 2.
                                4. After Broker is started, check whether the alarm is cleared.

                                  • If yes, no further action is required.
                                  • If no, go to 8.

                                Collect fault information.

                                -
                                1. On FusionInsight Manager, choose O&M > Log > Download.
                                2. In the Service area, select Kafka in the required cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact the O&M personnel and send the collected logs.
                                +
                                1. On MRS Manager, choose O&M > Log > Download.
                                2. In the Service area, select Kafka in the required cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact the O&M personnel and send the collected logs.

                            Alarm Clearing

                            After the fault is rectified, the system automatically clears this alarm.

                            diff --git a/docs/mrs/umn/ALM-38009.html b/docs/mrs/umn/ALM-38009.html index 8e7a4454..11b68bbd 100644 --- a/docs/mrs/umn/ALM-38009.html +++ b/docs/mrs/umn/ALM-38009.html @@ -1,6 +1,6 @@ -

                            ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0)

                            +

                            (Applicable to Versions Later Than MRS 3.1.0)ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0)

                            This section applies to versions later than MRS 3.1.0.

                            Description

                            The system checks the I/O status of each Kafka disk every 60 seconds. This alarm is generated when the disk I/O of a Kafka data directory on a broker exceeds the threshold (80% by default).

                            @@ -67,7 +67,7 @@

                            Possible Causes

                            • There are many replicas configured for the topic.
                            • The parameter for batch writing producer's messages is inappropriately configured. The service traffic of this topic is too heavy, and the current partition configuration is inappropriate.

                            Procedure

                            Check the number of topic replicas.

                            -
                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms. Locate the row that contains this alarm, click , and view the host name in Location.
                            2. On FusionInsight Manager, choose Cluster, click the name of the desired cluster, choose Services > Kafka > KafkaTopic Monitor, search for the topic for which the alarm is generated, and check the number of replicas.
                            3. Reduce the replication factors of the topic (for example, reduce to 3) if the number of replicas is greater than 3.

                              Run the following command on the FusionInsight client to replan the replicas of Kafka topics:

                              +
                              1. On MRS Manager, choose O&M > Alarm > Alarms. Locate the row that contains this alarm, click , and view the host name in Location.
                              2. On MRS Manager, choose Cluster, click the name of the desired cluster, choose Services > Kafka > KafkaTopic Monitor, search for the topic for which the alarm is generated, and check the number of replicas.
                              3. Reduce the replication factors of the topic (for example, reduce to 3) if the number of replicas is greater than 3.

                                Run the following command on the MRS client to replan the replicas of Kafka topics:

                                kafka-reassign-partitions.sh --zookeeper {zk_host}:{port}/kafka --reassignment-json-file {manual assignment json file path} --execute

                                For example:

                                /opt/client/Kafka/kafka/bin/kafka-reassign-partitions.sh --zookeeper 10.149.0.90:2181,10.149.0.91:2181,10.149.0.92:2181/kafka --reassignment-json-file expand-cluster-reassignment.json --execute

                                @@ -85,7 +85,7 @@

                              4. Observe for a period of time and check whether the alarm is cleared.

                                • If yes, no further action is required.
                                • If no, go to 9.

                              Collect fault information.

                              -
                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                              2. Expand the Service drop-down list, and select Kafka for the target cluster.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact O&M personnel and provide the collected logs.
                              +
                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                              2. Expand the Service drop-down list, and select Kafka for the target cluster.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact O&M personnel and provide the collected logs.

                            Alarm Clearing

                            This alarm is automatically cleared after the fault is rectified.

                            diff --git a/docs/mrs/umn/ALM-38010.html b/docs/mrs/umn/ALM-38010.html index 1cd275d6..4584bc33 100644 --- a/docs/mrs/umn/ALM-38010.html +++ b/docs/mrs/umn/ALM-38010.html @@ -59,17 +59,17 @@

                            Possible Causes

                            • The number of replicas for the topic is incorrectly configured.

                            Procedure

                            Check the number of replicas for the topic.

                            -
                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms, click of this alarm, and view the TopicName list in Location.
                            2. Check whether replicas need to be added for the topic for which the alarm is generated.

                              • If yes, go to 3.
                              • If no, go to 5.
                              -

                            3. On the FusionInsight client, re-plan topic replicas and describe the partition distribution of the topic in the add-replicas-reassignment.json file in the following format: {"partitions":[{"topic": "topic name","partition": 1,"replicas": [1,2] }],"version":1}. Then, run the following command to add replicas:

                              kafka-reassign-partitions.sh --zookeeper {zk_host}:{port}/kafka --reassignment-json-file {manual assignment json file path} --execute

                              +
                              1. On MRS Manager, choose O&M > Alarm > Alarms, click of this alarm, and view the TopicName list in Location.
                              2. Check whether replicas need to be added for the topic for which the alarm is generated.

                                • If yes, go to 3.
                                • If no, go to 5.
                                +

                              3. On the MRS client, re-plan topic replicas and describe the partition distribution of the topic in the add-replicas-reassignment.json file in the following format: {"partitions":[{"topic": "topic name","partition": 1,"replicas": [1,2] }],"version":1}. Then, run the following command to add replicas:

                                kafka-reassign-partitions.sh --zookeeper {zk_host}:{port}/kafka --reassignment-json-file {manual assignment json file path} --execute

                                For example:

                                /opt/client/Kafka/kafka/bin/kafka-reassign-partitions.sh --zookeeper 192.168.0.90:2181,192.168.0.91:2181,192.168.0.92:2181/kafka --reassignment-json-file add-replicas-reassignment.json --execute

                              4. Run the following command to check the task execution progress:

                                kafka-reassign-partitions.sh --zookeeper {zk_host}:{port}/kafka --reassignment-json-file {manual assignment json file path} --verify

                                For example:

                                /opt/client/Kafka/kafka/bin/kafka-reassign-partitions.sh --zookeeper 192.168.0.90:2181,192.168.0.91:2181,192.168.0.92:2181/kafka --reassignment-json-file add-replicas-reassignment.json --verify

                                -

                              5. After completing the handling operations or confirming that the alarm has no impact, manually clear the alarm on FusionInsight Manager.
                              6. After a period of time, check whether the alarm is cleared.

                                • If it is, no further action is required.
                                • If it is not, go to 7.
                                +

                              7. After completing the handling operations or confirming that the alarm has no impact, manually clear the alarm on MRS Manager.
                              8. After a period of time, check whether the alarm is cleared.

                                • If it is, no further action is required.
                                • If it is not, go to 7.

                              Collect fault information.

                              -
                              1. On FusionInsight Manager, choose O&M > Log > Download.
                              2. In the Service area, select Kafka in the required cluster.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact the O&M personnel and send the collected logs.
                              +
                              1. On MRS Manager, choose O&M > Log > Download.
                              2. In the Service area, select Kafka in the required cluster.
                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                              4. Contact the O&M personnel and send the collected logs.

                            Alarm Clearing

                            If the alarm has no impact, manually clear the alarm.

                            diff --git a/docs/mrs/umn/ALM-38011.html b/docs/mrs/umn/ALM-38011.html index 897b89e1..bb1a6187 100644 --- a/docs/mrs/umn/ALM-38011.html +++ b/docs/mrs/umn/ALM-38011.html @@ -66,7 +66,7 @@

                            Possible Causes

                            • The number of connections (created by a user) used by the client exceeds the preset threshold.
                            • The threshold for the connection usage does not meet service requirements.

                            Procedure

                            Check the number of connections established by the same user on the client.

                            -
                            1. On the FusionInsight Manager home page, choose O&M > Alarm > Alarms > User Connection Usage on Broker Exceeds the Threshold. Check the host name and username of the Broker instance for which the alarm is generated in Location.
                            2. On FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area, choose Customize > Other, and select User Connection Usage on Broker, Maximum Number of User Connections on Broker, and Number of User Connections on Broker to view the number of the current user connections on the Broker.
                            3. Observe the number of real-time connections of the current alarm user and check whether the real-time monitoring data of the current user exists.

                              • If yes, go to 4.
                              • If no, the current user has disconnected all connections. You need to clear the alarm manually, and no further action is required.

                                After the alarm user disconnects all connections, the monitoring data of the user disappears. In this case, the alarm will not be automatically cleared. You need to manually clear it.

                                +
                                1. On the MRS Manager home page, choose O&M > Alarm > Alarms > User Connection Usage on Broker Exceeds the Threshold. Check the host name and username of the Broker instance for which the alarm is generated in Location.
                                2. On MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area, choose Customize > Other, and select User Connection Usage on Broker, Maximum Number of User Connections on Broker, and Number of User Connections on Broker to view the number of the current user connections on the Broker.
                                3. Observe the number of real-time connections of the current alarm user and check whether the real-time monitoring data of the current user exists.

                                  • If yes, go to 4.
                                  • If no, the current user has disconnected all connections. You need to clear the alarm manually, and no further action is required.

                                    After the alarm user disconnects all connections, the monitoring data of the user disappears. In this case, the alarm will not be automatically cleared. You need to manually clear it.

                                4. Check whether the user is authorized by the service side.

                                  If yes, go to 7.

                                  @@ -74,7 +74,7 @@

                                5. Run the following command on the client to limit the number of connections of the user. There are two configuration rules based on the following commands:

                                  1. For the specific Broker and user, run the following command:

                                    kafka-configs.sh --bootstrap-server <broker ip:port> --alter --add-config 'max.connections.per.user.overrides=[<username>:<connection.number>]' --entity-type brokers --entity-name <broker.id> --command-config Kafka/kafka/config/producer.properties

                                    For unauthorized users, confirm with the service side to reduce the maximum number of connections of an unauthorized user or set the maximum number of connections to 0.

                                    In the command, you need to specify the IP address and port number of Broker, set values of configuration items, and specify the brokerId and username. Here, the user refers to the authorized Kerberos user.

                                    -

                                    The configuration updated using the command line tool can take effect dynamically. The configuration becomes invalid after the service is restarted. To make the configuration take effect after the restart, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations> Broker > Server on the FusionInsight Manager home page and update the configuration to max.connections.per.user.overrides.

                                    +

                                    The configuration updated using the command line tool can take effect dynamically. The configuration becomes invalid after the service is restarted. To make the configuration take effect after the restart, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations> Broker > Server on the MRS Manager home page and update the configuration to max.connections.per.user.overrides.

                                  2. For the specific use and default Broker (that is, all Broker instances in the cluster), run the following command:

                                    kafka-configs.sh --bootstrap-server <broker ip:port> --alter --add-config 'max.connections.per.user.overrides=[<username>:<connection.number>]' --entity-type brokers ---entity-default --command-config Kafka/kafka/config/client.properties

                                    Example:

                                    @@ -95,9 +95,9 @@

                                  3. Determine whether to add the user to the whitelist based on service requirements on the service side.

                                    • If yes, go to 13.
                                    • If no, go to 15.

                                    To add a user to the whitelist, you need to restart the Kafka service. However, this operation will cause service interruption and affect service running. Therefore, you must confirm with the service side before performing this operation.

                                    -

                                  4. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations > Broker(Role) > Server to add the user to the max.connections.per.user.whitelist configuration item.
                                  5. Restart the service for the modification to take effect. In addition, you need to manually clear the alarm, and no further action is required.
                                  +

                                6. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Kafka > Configurations > All Configurations > Broker(Role) > Server to add the user to the max.connections.per.user.whitelist configuration item.
                                7. Restart the service for the modification to take effect. In addition, you need to manually clear the alarm, and no further action is required.

                                Collect the fault information.

                                -
                                1. On the FusionInsight Manager homepage, choose O&M > Log > Download.
                                2. Expand the Service drop-down list, and select Kafka for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact the O&M personnel and send the collected fault logs.
                                +
                                1. On the MRS Manager homepage, choose O&M > Log > Download.
                                2. Expand the Service drop-down list, and select Kafka for the target cluster.
                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                4. Contact the O&M personnel and send the collected fault logs.

                                Alarm Clearing

                                After the fault is rectified, the system automatically clears this alarm.

                                diff --git a/docs/mrs/umn/ALM-43001.html b/docs/mrs/umn/ALM-43001.html index fab41e95..0a163102 100644 --- a/docs/mrs/umn/ALM-43001.html +++ b/docs/mrs/umn/ALM-43001.html @@ -61,7 +61,7 @@

                                Procedure

                                If the alarm is abnormal Spark2x assembly packet, the Spark packet is abnormal. Wait for about 10 minutes. The alarm is automatically cleared.

                                Check whether service unavailability alarms exist in services that Spark2x depends on.

                                -
                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms.
                                2. Check whether the following alarms exist in the alarm list:

                                  • ALM-25500 KrbServer Service Unavailable
                                  • ALM-25000 LdapServer Service Unavailable
                                  • ALM-13000 ZooKeeper Service Unavailable
                                  • ALM-14000 HDFS Service Unavailable
                                  • ALM-18000 Yarn Service Unavailable
                                  • ALM-16004 Hive Service Unavailable
                                  +
                                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms.
                                  2. Check whether the following alarms exist in the alarm list:

                                    • ALM-25500 KrbServer Service Unavailable
                                    • ALM-25000 LdapServer Service Unavailable
                                    • ALM-13000 ZooKeeper Service Unavailable
                                    • ALM-14000 HDFS Service Unavailable
                                    • ALM-18000 Yarn Service Unavailable
                                    • ALM-16004 Hive Service Unavailable

                                    If the multi-instance function is enabled for the cluster and multiple Spark2x services are installed, check the Spark2x service for which the alarm is generated based on the value of ServiceName in location information and check whether the Hive service is faulty. Spark2x corresponds to Hive, spark2x1 corresponds to Hive1, and other services follow the same rule.

                                    • If yes, go to 3.
                                    • If no, go to 4.
                                    @@ -69,7 +69,7 @@
                                    • If yes, no further action is required.
                                    • If no, go to 4.

                                  Collect fault information.

                                  -
                                  1. On FusionInsight Manager, choose O&M > Log > Download.
                                  2. In the Service area, select the following nodes of the desired cluster. (Hive is the specific Hive service determined based on ServiceName in the alarm location information).

                                    • KrbServer
                                    • LdapServer
                                    • ZooKeeper
                                    • HDFS
                                    • Yarn
                                    • Hive
                                    +
                                    1. On MRS Manager, choose O&M > Log > Download.
                                    2. In the Service area, select the following nodes of the desired cluster. (Hive is the specific Hive service determined based on ServiceName in the alarm location information).

                                      • KrbServer
                                      • LdapServer
                                      • ZooKeeper
                                      • HDFS
                                      • Yarn
                                      • Hive

                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                    4. Contact O&M personnel and provide the collected logs.

                                Alarm Clearing

                                This alarm is automatically cleared after the fault is rectified.

                                diff --git a/docs/mrs/umn/ALM-43006.html b/docs/mrs/umn/ALM-43006.html index c722d047..670d5843 100644 --- a/docs/mrs/umn/ALM-43006.html +++ b/docs/mrs/umn/ALM-43006.html @@ -64,13 +64,13 @@

                                Possible Causes

                                The heap memory of the JobHistory2x Process is overused or the heap memory is inappropriately allocated.

                                Procedure

                                Check heap memory usage.

                                -
                                1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43006. Check the RoleName in Location and confirm the IP address of HostName.
                                2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JobHistory2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used heap memory of the JobHistory2x Process reaches the threshold(default value is 95%) of the maximum heap memory specified for JobHistory2x.

                                  • If yes, go to 3.
                                  • If no, go to 7.
                                  -

                                3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JobHistory2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the heap memory of the JobHistory2x Process, and click OK. Based on the alarm generation time, check the values of the used heap memory of the JobHistory2x process in the corresponding period and obtain the maximum value.
                                4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. The default value of SPARK_DAEMON_MEMORY is 4GB. You can change the value according to the following rules: Ratio of the maximum heap memory usage of the JobHistory2x to the Threshold of the JobHistory2x Heap Memory Usage Statistics (JobHistory2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time.

                                  On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JobHistory2x Heap Memory Usage Statistics (JobHistory2x) to view Threshold.

                                  +
                                  1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43006. Check the RoleName in Location and confirm the IP address of HostName.
                                  2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JobHistory2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used heap memory of the JobHistory2x Process reaches the threshold(default value is 95%) of the maximum heap memory specified for JobHistory2x.

                                    • If yes, go to 3.
                                    • If no, go to 7.
                                    +

                                  3. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JobHistory2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the heap memory of the JobHistory2x Process, and click OK. Based on the alarm generation time, check the values of the used heap memory of the JobHistory2x process in the corresponding period and obtain the maximum value.
                                  4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. The default value of SPARK_DAEMON_MEMORY is 4GB. You can change the value according to the following rules: Ratio of the maximum heap memory usage of the JobHistory2x to the Threshold of the JobHistory2x Heap Memory Usage Statistics (JobHistory2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time.

                                    On the MRS Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JobHistory2x Heap Memory Usage Statistics (JobHistory2x) to view Threshold.

                                  5. Restart all JobHistory2x instances.
                                  6. After 10 minutes, check whether the alarm is cleared.

                                    • If yes, no further action is required.
                                    • If no, go to 7.

                                  Collect fault information.

                                  -
                                  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                  2. Select Spark2x in the required cluster from the Service.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.
                                  +
                                  1. On the MRS Manager portal, choose O&M > Log > Download.
                                  2. Select Spark2x in the required cluster from the Service.
                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                  4. Contact the O&M personnel and send the collected logs.

                                  Alarm Clearing

                                  After the fault is rectified, the system automatically clears this alarm.

                                  diff --git a/docs/mrs/umn/ALM-43007.html b/docs/mrs/umn/ALM-43007.html index 1a3ba788..edaee91f 100644 --- a/docs/mrs/umn/ALM-43007.html +++ b/docs/mrs/umn/ALM-43007.html @@ -64,13 +64,13 @@

                                  Possible Causes

                                  The non-heap memory of the JobHistory2x Process is overused or the non-heap memory is inappropriately allocated.

                                  Procedure

                                  Check non-heap memory usage.

                                  -
                                  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43007. Check the RoleName in Location and confirm the IP address of HostName.
                                  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JobHistory2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK, Check whether the used non-heap memory of the JobHistory2x Process reaches the threshold(default value is 95%) of the maximum non-heap memory specified for JobHistory2x.

                                    • If yes, go to 3.
                                    • If no, go to 7.
                                    -

                                  3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JobHistory2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the non-heap memory of the JobHistory2x Process, and click OK. Based on the alarm generation time, check the values of the used non-heap memory of the JobHistory2x process in the corresponding period and obtain the maximum value.
                                  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. You can change the value of -XX:MaxMetaspaceSize in SPARK_DAEMON_JAVA_OPTS according to the following rules: Ratio of the JobHistory2x non-heap memory usage to the Threshold of JobHistory2x Non-Heap Memory Usage Statistics (JobHistory2x) in the alarm period.

                                    On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JobHistory2x Non-Heap Memory Usage Statistics (JobHistory2x) to view Threshold.

                                    +
                                    1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43007. Check the RoleName in Location and confirm the IP address of HostName.
                                    2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JobHistory2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK, Check whether the used non-heap memory of the JobHistory2x Process reaches the threshold(default value is 95%) of the maximum non-heap memory specified for JobHistory2x.

                                      • If yes, go to 3.
                                      • If no, go to 7.
                                      +

                                    3. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JobHistory2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the non-heap memory of the JobHistory2x Process, and click OK. Based on the alarm generation time, check the values of the used non-heap memory of the JobHistory2x process in the corresponding period and obtain the maximum value.
                                    4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. You can change the value of -XX:MaxMetaspaceSize in SPARK_DAEMON_JAVA_OPTS according to the following rules: Ratio of the JobHistory2x non-heap memory usage to the Threshold of JobHistory2x Non-Heap Memory Usage Statistics (JobHistory2x) in the alarm period.

                                      On the MRS Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JobHistory2x Non-Heap Memory Usage Statistics (JobHistory2x) to view Threshold.

                                    5. Restart all JobHistory2x instances.
                                    6. After 10 minutes, check whether the alarm is cleared.

                                      • If yes, no further action is required.
                                      • If no, go to 7.

                                    Collect fault information.

                                    -
                                    1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                    2. Select Spark2x in the required cluster from the Service.
                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                    4. Contact the O&M personnel and send the collected logs.
                                    +
                                    1. On the MRS Manager portal, choose O&M > Log > Download.
                                    2. Select Spark2x in the required cluster from the Service.
                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                    4. Contact the O&M personnel and send the collected logs.

                                    Alarm Clearing

                                    After the fault is rectified, the system automatically clears this alarm.

                                    diff --git a/docs/mrs/umn/ALM-43008.html b/docs/mrs/umn/ALM-43008.html index ad8d4338..d596545c 100644 --- a/docs/mrs/umn/ALM-43008.html +++ b/docs/mrs/umn/ALM-43008.html @@ -64,13 +64,13 @@

                                    Possible Causes

                                    The direct memory of the JobHistory2x Process is overused or the direct memory is inappropriately allocated.

                                    Procedure

                                    Check direct memory usage.

                                    -
                                    1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43008. Check the RoleName in Location and confirm the IP address of HostName.
                                    2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JobHistory2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used direct memory of the JobHistory2x Process reaches the threshold(default value is 95%) of the maximum direct memory specified for JobHistory2x.

                                      • If yes, go to 3.
                                      • If no, go to 7.
                                      -

                                    3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JobHistory2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Direct Memory of JobHistory2x, and click OK. Based on the alarm generation time, check the values of the used direc memory of the JobHistory2x process in the corresponding period and obtain the maximum value.
                                    4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. The default value of -XX:MaxDirectMemorySize in SPARK_DAEMON_JAVA_OPTS is 512 MB. You can change the value according to the following rules: Ratio of the maximum direct memory usage of the JobHistory2x to the Threshold of the JobHistory2x Direct Memory Usage Statistics (JobHistory2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time. It is recommended that the value be less than or equal to the value of SPARK_DAEMON_MEMORY.

                                      On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JobHistory2x Direct Memory Usage Statistics (JobHistory2x) to view Threshold.

                                      +
                                      1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43008. Check the RoleName in Location and confirm the IP address of HostName.
                                      2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JobHistory2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used direct memory of the JobHistory2x Process reaches the threshold(default value is 95%) of the maximum direct memory specified for JobHistory2x.

                                        • If yes, go to 3.
                                        • If no, go to 7.
                                        +

                                      3. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JobHistory2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Direct Memory of JobHistory2x, and click OK. Based on the alarm generation time, check the values of the used direc memory of the JobHistory2x process in the corresponding period and obtain the maximum value.
                                      4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. The default value of -XX:MaxDirectMemorySize in SPARK_DAEMON_JAVA_OPTS is 512 MB. You can change the value according to the following rules: Ratio of the maximum direct memory usage of the JobHistory2x to the Threshold of the JobHistory2x Direct Memory Usage Statistics (JobHistory2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time. It is recommended that the value be less than or equal to the value of SPARK_DAEMON_MEMORY.

                                        On the MRS Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JobHistory2x Direct Memory Usage Statistics (JobHistory2x) to view Threshold.

                                      5. Restart all JobHistory2x instances.
                                      6. After 10 minutes, check whether the alarm is cleared.

                                        • If yes, no further action is required.
                                        • If no, go to 7.

                                      Collect fault information.

                                      -
                                      1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                      2. Select Spark2x in the required cluster from the Service.
                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                      4. Contact the O&M personnel and send the collected logs.
                                      +
                                      1. On the MRS Manager portal, choose O&M > Log > Download.
                                      2. Select Spark2x in the required cluster from the Service.
                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                      4. Contact the O&M personnel and send the collected logs.

                                      Alarm Clearing

                                      After the fault is rectified, the system automatically clears this alarm.

                                      diff --git a/docs/mrs/umn/ALM-43009.html b/docs/mrs/umn/ALM-43009.html index 1941fd65..a4419a96 100644 --- a/docs/mrs/umn/ALM-43009.html +++ b/docs/mrs/umn/ALM-43009.html @@ -64,11 +64,11 @@

                                      Possible Causes

                                      The memory of JobHistory2x is overused, the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                      Procedure

                                      Check the GC time.

                                      -
                                      1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43009. Check the RoleName in Location and confirm the IP address of HostName.
                                      2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of JobHistory2x from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold(default value: 12 seconds).

                                        • If yes, go to 3.
                                        • If no, go to 6.
                                        -

                                      3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. The default value of SPARK_DAEMON_MEMORY is 4GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. If the alarm is frequently reported, increase the value by 1 time.
                                      4. Restart all JobHistory2x instances.
                                      5. After 10 minutes, check whether the alarm is cleared.

                                        • If yes, no further action is required.
                                        • If no, go to 6.
                                        +
                                        1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43009. Check the RoleName in Location and confirm the IP address of HostName.
                                        2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of JobHistory2x from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold(default value: 12 seconds).

                                          • If yes, go to 3.
                                          • If no, go to 6.
                                          +

                                        3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. The default value of SPARK_DAEMON_MEMORY is 4GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. If the alarm is frequently reported, increase the value by 1 time.
                                        4. Restart all JobHistory2x instances.
                                        5. After 10 minutes, check whether the alarm is cleared.

                                          • If yes, no further action is required.
                                          • If no, go to 6.

                                        Collect fault information.

                                        -
                                        1. On the FusionInsight Manager interface of active and standby clusters, choose O&M > Log > Download.
                                        2. Select Spark2x in the required cluster from the Service.
                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                        4. Contact the O&M personnel and send the collected logs.
                                        +
                                        1. On the MRS Manager interface of active and standby clusters, choose O&M > Log > Download.
                                        2. Select Spark2x in the required cluster from the Service.
                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                        4. Contact the O&M personnel and send the collected logs.

                                      Alarm Clearing

                                      After the fault is rectified, the system automatically clears this alarm.

                                      diff --git a/docs/mrs/umn/ALM-43010.html b/docs/mrs/umn/ALM-43010.html index a1e39516..782ab85e 100644 --- a/docs/mrs/umn/ALM-43010.html +++ b/docs/mrs/umn/ALM-43010.html @@ -64,13 +64,13 @@

                                      Possible Causes

                                      The heap memory of the JDBCServer2x Process is overused or the heap memory is inappropriately allocated.

                                      Procedure

                                      Check heap memory usage.

                                      -
                                      1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43010. Check the RoleName in Location and confirm the IP address of HostName.
                                      2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JDBCServer2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used heap memory of the JDBCServer2x Process reaches the threshold(default value is 95%) of the maximum heap memory specified for JDBCServer2x.

                                        • If yes, go to 3.
                                        • If no, go to 7.
                                        -

                                      3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JDBCServer2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the heap memory of the JDBCServer2x Process, and click OK. Based on the alarm generation time, check the values of the used heap memory of the JDBCServer2x process in the corresponding period and obtain the maximum value.
                                      4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Tuning. The default value of SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: Ratio of the maximum heap memory usage of the JobHistory2x to the Threshold of the JDBCServer2x Heap Memory Usage Statistics (JDBCServer2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time. In the case of large service volume and high concurrency, add instances.

                                        On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JDBCServer2x Heap Memory Usage Statistics (JDBCServer2x) to view Threshold.

                                        +
                                        1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43010. Check the RoleName in Location and confirm the IP address of HostName.
                                        2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JDBCServer2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used heap memory of the JDBCServer2x Process reaches the threshold(default value is 95%) of the maximum heap memory specified for JDBCServer2x.

                                          • If yes, go to 3.
                                          • If no, go to 7.
                                          +

                                        3. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JDBCServer2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the heap memory of the JDBCServer2x Process, and click OK. Based on the alarm generation time, check the values of the used heap memory of the JDBCServer2x process in the corresponding period and obtain the maximum value.
                                        4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Tuning. The default value of SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: Ratio of the maximum heap memory usage of the JobHistory2x to the Threshold of the JDBCServer2x Heap Memory Usage Statistics (JDBCServer2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time. In the case of large service volume and high concurrency, add instances.

                                          On the MRS Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JDBCServer2x Heap Memory Usage Statistics (JDBCServer2x) to view Threshold.

                                        5. Restart all JDBCServer2x instances.
                                        6. After 10 minutes, check whether the alarm is cleared.

                                          • If yes, no further action is required.
                                          • If no, go to 7.

                                        Collect fault information.

                                        -
                                        1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                        2. Select Spark2x in the required cluster from the Service.
                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                        4. Contact the O&M personnel and send the collected logs.
                                        +
                                        1. On the MRS Manager portal, choose O&M > Log > Download.
                                        2. Select Spark2x in the required cluster from the Service.
                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                        4. Contact the O&M personnel and send the collected logs.

                                        Alarm Clearing

                                        After the fault is rectified, the system automatically clears this alarm.

                                        diff --git a/docs/mrs/umn/ALM-43011.html b/docs/mrs/umn/ALM-43011.html index a69bddbc..4ec434cd 100644 --- a/docs/mrs/umn/ALM-43011.html +++ b/docs/mrs/umn/ALM-43011.html @@ -64,13 +64,13 @@

                                        Possible Causes

                                        The non-heap memory of the JDBCServer2x Process is overused or the non-heap memory is inappropriately allocated.

                                        Procedure

                                        Check non-heap memory usage.

                                        -
                                        1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43011. Check the RoleName in Location and confirm the IP address of HostName.
                                        2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JDBCServer2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK, Check whether the used non-heap memory of the JDBCServer2x Process reaches the threshold(default value is 95%) of the maximum non-heap memory specified for JDBCServer2x.

                                          • If yes, go to 3.
                                          • If no, go to 7.
                                          -

                                        3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JDBCServer2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the non-heap memory of the JDBCServer2x Process, and click OK. Based on the alarm generation time, check the values of the used non-heap memory of the JDBCServer2x process in the corresponding period and obtain the maximum value.
                                        4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Tuning. You can change the value of -XX: MaxMetaspaceSize in spark.driver.extraJavaOptions according to the following rules: Ratio of the JDBCServer2x non-heap memory usage to the Threshold of JDBCServer2x Non-Heap Memory Usage Statistics ( JDBCServer2x) in the alarm period.

                                          On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > JDBCServer2x Non-Heap Memory Usage Statistics (JDBCServer2x) to view Threshold.

                                          +
                                          1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43011. Check the RoleName in Location and confirm the IP address of HostName.
                                          2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JDBCServer2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK, Check whether the used non-heap memory of the JDBCServer2x Process reaches the threshold(default value is 95%) of the maximum non-heap memory specified for JDBCServer2x.

                                            • If yes, go to 3.
                                            • If no, go to 7.
                                            +

                                          3. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JDBCServer2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the non-heap memory of the JDBCServer2x Process, and click OK. Based on the alarm generation time, check the values of the used non-heap memory of the JDBCServer2x process in the corresponding period and obtain the maximum value.
                                          4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Tuning. You can change the value of -XX: MaxMetaspaceSize in spark.driver.extraJavaOptions according to the following rules: Ratio of the JDBCServer2x non-heap memory usage to the Threshold of JDBCServer2x Non-Heap Memory Usage Statistics ( JDBCServer2x) in the alarm period.

                                            On the MRS Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > JDBCServer2x Non-Heap Memory Usage Statistics (JDBCServer2x) to view Threshold.

                                          5. Restart all JDBCServer2x instances.
                                          6. After 10 minutes, check whether the alarm is cleared.

                                            • If yes, no further action is required.
                                            • If no, go to 7.

                                          Collect fault information.

                                          -
                                          1. On the FusionInsight Manager portal, choose O&M > Log >Download.
                                          2. Select Spark2x in the required cluster from the Service.
                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                          4. Contact the O&M personnel and send the collected logs.
                                          +
                                          1. On the MRS Manager portal, choose O&M > Log >Download.
                                          2. Select Spark2x in the required cluster from the Service.
                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                          4. Contact the O&M personnel and send the collected logs.

                                          Alarm Clearing

                                          After the fault is rectified, the system automatically clears this alarm.

                                          diff --git a/docs/mrs/umn/ALM-43012.html b/docs/mrs/umn/ALM-43012.html index af0d84e4..248f545c 100644 --- a/docs/mrs/umn/ALM-43012.html +++ b/docs/mrs/umn/ALM-43012.html @@ -64,13 +64,13 @@

                                          Possible Causes

                                          The direct heap memory of the JDBCServer2x Process is overused or the direct heap memory is inappropriately allocated.

                                          Procedure

                                          Check direct heap memory usage.

                                          -
                                          1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43012. Check the RoleName in Location and confirm the IP address of HostName.
                                          2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JDBCServer2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used direct heap memory of the JDBCServer2x Process reaches the threshold(default value is 95%) of the maximum direct heap memory specified for JDBCServer2x.

                                            • If yes, go to 3.
                                            • If no, go to 7.
                                            -

                                          3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JDBCServer2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Direct Memory of JDBCServer2x, and click OK. Based on the alarm generation time, check the values of the used direct memory of the JDBCServer2x process in the corresponding period and obtain the maximum value.
                                          4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Tuning. The default value of -XX:MaxDirectMemorySize in spark.driver.extraJavaOptions is 512 MB. You can change the value according to the following rules: Ratio of the maximum direct memory usage of the JDBCServer2x to the Threshold of the JDBCServer2x Direct Memory Usage Statistics (JDBCServer2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time. In the case of large service volume and high service concurrency, you are advised to add instances.

                                            On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JDBCServer2x Direct Memory Usage Statistics (JDBCServer2x) to view Threshold.

                                            +
                                            1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43012. Check the RoleName in Location and confirm the IP address of HostName.
                                            2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JDBCServer2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK. Check whether the used direct heap memory of the JDBCServer2x Process reaches the threshold(default value is 95%) of the maximum direct heap memory specified for JDBCServer2x.

                                              • If yes, go to 3.
                                              • If no, go to 7.
                                              +

                                            3. On the MRS Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JDBCServer2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Direct Memory of JDBCServer2x, and click OK. Based on the alarm generation time, check the values of the used direct memory of the JDBCServer2x process in the corresponding period and obtain the maximum value.
                                            4. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Tuning. The default value of -XX:MaxDirectMemorySize in spark.driver.extraJavaOptions is 512 MB. You can change the value according to the following rules: Ratio of the maximum direct memory usage of the JDBCServer2x to the Threshold of the JDBCServer2x Direct Memory Usage Statistics (JDBCServer2x) in the alarm period. If this alarm is generated occasionally after the parameter value is adjusted, increase the value by 0.5 times. If the alarm is frequently reported after the parameter value is adjusted, increase the value by 1 time. In the case of large service volume and high service concurrency, you are advised to add instances.

                                              On the MRS Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JDBCServer2x Direct Memory Usage Statistics (JDBCServer2x) to view Threshold.

                                            5. Restart all JDBCServer2x instances.
                                            6. After 10 minutes, check whether the alarm is cleared.

                                              • If yes, no further action is required.
                                              • If no, go to 7.

                                            Collect fault information.

                                            -
                                            1. On the FusionInsight Manager portal, choose O&M > Log > Download.
                                            2. Select Spark2x in the required cluster from the Service.
                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                            4. Contact the O&M personnel and send the collected logs.
                                            +
                                            1. On the MRS Manager portal, choose O&M > Log > Download.
                                            2. Select Spark2x in the required cluster from the Service.
                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                            4. Contact the O&M personnel and send the collected logs.

                                            Alarm Clearing

                                            After the fault is rectified, the system automatically clears this alarm.

                                            diff --git a/docs/mrs/umn/ALM-43013.html b/docs/mrs/umn/ALM-43013.html index 995e1897..555d78d8 100644 --- a/docs/mrs/umn/ALM-43013.html +++ b/docs/mrs/umn/ALM-43013.html @@ -64,11 +64,11 @@

                                            Possible Causes

                                            The memory of JDBCServer2x is overused, the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                            Procedure

                                            Check the GC time.

                                            -
                                            1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43013. Check the RoleName in Location and confirm the IP address of HostName.
                                            2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of JDBCServer2x from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold(default value: 12 seconds).

                                              • If yes, go to 3.
                                              • If no, go to 6.
                                              -

                                            3. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Default. The default value of SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. If the alarm is frequently reported, increase the value by 1 time. In the case of large service volume and high service concurrency, you are advised to add instances.
                                            4. Restart all JDBCServer2x instances.
                                            5. After 10 minutes, check whether the alarm is cleared.

                                              • If yes, no further action is required.
                                              • If no, go to 6.
                                              +
                                              1. On the MRS Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43013. Check the RoleName in Location and confirm the IP address of HostName.
                                              2. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JDBCServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of JDBCServer2x from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold(default value: 12 seconds).

                                                • If yes, go to 3.
                                                • If no, go to 6.
                                                +

                                              3. On the MRS Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JDBCServer2x > Default. The default value of SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. If the alarm is frequently reported, increase the value by 1 time. In the case of large service volume and high service concurrency, you are advised to add instances.
                                              4. Restart all JDBCServer2x instances.
                                              5. After 10 minutes, check whether the alarm is cleared.

                                                • If yes, no further action is required.
                                                • If no, go to 6.

                                              Collect fault information.

                                              -
                                              1. On the FusionInsight Manager interface of active and standby clusters, choose O&M > Log > Download.
                                              2. Select Spark2x in the required cluster from the Service.
                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                              4. Contact the O&M personnel and send the collected logs.
                                              +
                                              1. On the MRS Manager interface of active and standby clusters, choose O&M > Log > Download.
                                              2. Select Spark2x in the required cluster from the Service.
                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                              4. Contact the O&M personnel and send the collected logs.

                                            Alarm Clearing

                                            After the fault is rectified, the system automatically clears this alarm.

                                            diff --git a/docs/mrs/umn/ALM-43017.html b/docs/mrs/umn/ALM-43017.html index 7e40fe92..e0ff8a99 100644 --- a/docs/mrs/umn/ALM-43017.html +++ b/docs/mrs/umn/ALM-43017.html @@ -64,11 +64,11 @@

                                            Possible Causes

                                            The heap memory usage of the JDBCServer2x process is excessively large, or the heap memory is inappropriately allocated. As a result, Full GC occurs frequently.

                                            Procedure

                                            Check the number of Full GCs.

                                            -
                                            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, select this alarm, and check the RoleName in Location and confirm the IP address of HostName.
                                            2. Choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. On the displayed page, click the JDBCServer2x for which the alarm is reported. On the Dashboard page that is displayed, click the drop-down menu in the Chart area and choose Customize > GC Number > Full GC Number of JDBCServer2x in the upper right corner and click OK. Check whether the number of Full GCs of the JDBCServer2x process is greater than the threshold(default value: 12).

                                              • If it is, go to 3.
                                              • If it is not, go to 6.
                                              +
                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms, select this alarm, and check the RoleName in Location and confirm the IP address of HostName.
                                              2. Choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. On the displayed page, click the JDBCServer2x for which the alarm is reported. On the Dashboard page that is displayed, click the drop-down menu in the Chart area and choose Customize > GC Number > Full GC Number of JDBCServer2x in the upper right corner and click OK. Check whether the number of Full GCs of the JDBCServer2x process is greater than the threshold(default value: 12).

                                                • If it is, go to 3.
                                                • If it is not, go to 6.

                                              3. Choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations. On the displayed page, choose JDBCServer2x > Tuning. The default value of SPARK_DRIVER_MEMORY is 4GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. If the alarm is frequently reported, increase the value by 1 time. In the case of large service volume and high concurrency, add instances.
                                              4. Restart all JDBCServer2x instances.
                                              5. After 10 minutes, check whether the alarm is cleared.

                                                • If it is, no further action is required.
                                                • If it is not, go to 6.

                                              Collect fault information.

                                              -
                                              1. Log in to FusionInsight Manager, and choose O&M > Log > Download.
                                              2. Select Spark2x in the required cluster from the Service drop-down list.
                                              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
                                              4. Contact the O&M personnel and send the collected logs.
                                              +
                                              1. Log in to MRS Manager, and choose O&M > Log > Download.
                                              2. Select Spark2x in the required cluster from the Service drop-down list.
                                              3. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
                                              4. Contact the O&M personnel and send the collected logs.

                                            Alarm Clearing

                                            This alarm will be automatically cleared after the fault is rectified.

                                            diff --git a/docs/mrs/umn/ALM-43018.html b/docs/mrs/umn/ALM-43018.html index a3ec95b9..33782ab1 100644 --- a/docs/mrs/umn/ALM-43018.html +++ b/docs/mrs/umn/ALM-43018.html @@ -64,10 +64,10 @@

                                            Possible Causes

                                            The heap memory usage of the JobHistory2x process is excessively large, or the heap memory is inappropriately allocated. As a result, Full GC occurs frequently.

                                            Procedure

                                            Check the number of Full GCs.

                                            -
                                            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, select this alarm, and check the RoleName in Location and confirm the IP address of HostName.
                                            2. Choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. On the displayed page, click the JobHistory2x for which the alarm is reported. On the Dashboard page that is displayed, click the drop-down menu in the Chart area and choose Customize > GC Number > Full GC Number of JobHistory2x in the upper right corner and click OK. Check whether the number of Full GCs of the JobHistory2x process is greater than the threshold(default value: 12).

                                              • If it is, go to 3.
                                              • If it is not, go to 6.
                                              +
                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms, select this alarm, and check the RoleName in Location and confirm the IP address of HostName.
                                              2. Choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. On the displayed page, click the JobHistory2x for which the alarm is reported. On the Dashboard page that is displayed, click the drop-down menu in the Chart area and choose Customize > GC Number > Full GC Number of JobHistory2x in the upper right corner and click OK. Check whether the number of Full GCs of the JobHistory2x process is greater than the threshold(default value: 12).

                                                • If it is, go to 3.
                                                • If it is not, go to 6.

                                              3. Choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations. On the displayed page, choose JobHistory2x > Default. The default value of SPARK_DAEMON_MEMORY is 4GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. If the alarm is frequently reported, increase the value by 1 time.
                                              4. Restart all JobHistory2x instances.
                                              5. After 10 minutes, check whether the alarm is cleared.

                                                • If it is, no further action is required.
                                                • If it is not, go to 6.

                                                Collect fault information.

                                                -

                                              6. Log in to FusionInsight Manager, and choose O&M > Log > Download.
                                              7. Select Spark2x in the required cluster from the Service.
                                              8. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
                                              9. Contact the O&M personnel and send the collected logs.
                                              +

                                            3. Log in to MRS Manager, and choose O&M > Log > Download.
                                            4. Select Spark2x in the required cluster from the Service.
                                            5. Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
                                            6. Contact the O&M personnel and send the collected logs.

                                            Alarm Clearing

                                            This alarm will be automatically cleared after the fault is rectified.

                                            diff --git a/docs/mrs/umn/ALM-43019.html b/docs/mrs/umn/ALM-43019.html index d8978467..485bf25a 100644 --- a/docs/mrs/umn/ALM-43019.html +++ b/docs/mrs/umn/ALM-43019.html @@ -64,13 +64,13 @@

                                            Possible Causes

                                            The heap memory of the IndexServer2x process is overused or the heap memory is inappropriately allocated.

                                            Procedure

                                            Check the heap memory usage.

                                            -
                                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm for which the ID is 43019, and check the RoleName in Location and confirm the IP address of HostName.
                                            2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > IndexServer2x Memory Usage Statistics > OK. Check whether the heap memory used by the IndexServer2x process reaches the maximum heap memory threshold (95% by default).

                                              • If the threshold is reached, go to 3.
                                              • If the threshold is not reached, go to 7.
                                              -

                                            3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Statistics for the heap memory of the IndexServer2x Process > OK. Based on the alarm generation time, check the values of the used heap memory of the IndexServer2x process in the corresponding period and obtain the maximum value.
                                            4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configuration > IndexServer2x> Tuning. The default value of the SPARK_DRIVER_MEMORY parameter is 4 GB. You can change the value based on the ratio of the maximum heap memory used by the IndexServer2x process to the threshold specified by IndexServer2x Heap Memory Usage Statistics (IndexServer2x) in the alarm period. If the alarm persists after the parameter value is changed, increase the value by 0.5 times. If the alarm is generated frequently, double the rate.

                                              On FusionInsight Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > IndexServer2x Heap Memory Usage Statistics (IndexServer2x) to view the threshold.

                                              +
                                              1. On MRS Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm for which the ID is 43019, and check the RoleName in Location and confirm the IP address of HostName.
                                              2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > IndexServer2x Memory Usage Statistics > OK. Check whether the heap memory used by the IndexServer2x process reaches the maximum heap memory threshold (95% by default).

                                                • If the threshold is reached, go to 3.
                                                • If the threshold is not reached, go to 7.
                                                +

                                              3. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Statistics for the heap memory of the IndexServer2x Process > OK. Based on the alarm generation time, check the values of the used heap memory of the IndexServer2x process in the corresponding period and obtain the maximum value.
                                              4. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configuration > IndexServer2x> Tuning. The default value of the SPARK_DRIVER_MEMORY parameter is 4 GB. You can change the value based on the ratio of the maximum heap memory used by the IndexServer2x process to the threshold specified by IndexServer2x Heap Memory Usage Statistics (IndexServer2x) in the alarm period. If the alarm persists after the parameter value is changed, increase the value by 0.5 times. If the alarm is generated frequently, double the rate.

                                                On MRS Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > IndexServer2x Heap Memory Usage Statistics (IndexServer2x) to view the threshold.

                                              5. Restart all IndexServer2x instances.
                                              6. After 10 minutes, check whether the alarm is cleared.

                                                • If the alarm is cleared, no further action is required.
                                                • If the alarm is not cleared, go to 7.

                                              Collect fault information.

                                              -
                                              1. On FusionInsight Manager, choose O&M > Log > Download.
                                              2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                              4. Contact the O&M personnel and provide the collected logs.
                                              +
                                              1. On MRS Manager, choose O&M > Log > Download.
                                              2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                              4. Contact the O&M personnel and provide the collected logs.

                                              Alarm Clearing

                                              After the fault is rectified, the system automatically clears this alarm.

                                              diff --git a/docs/mrs/umn/ALM-43020.html b/docs/mrs/umn/ALM-43020.html index f0137894..2c6caf8c 100644 --- a/docs/mrs/umn/ALM-43020.html +++ b/docs/mrs/umn/ALM-43020.html @@ -64,13 +64,13 @@

                                              Possible Causes

                                              The non-heap memory of the IndexServer2x process is overused or the non-heap memory is inappropriately allocated.

                                              Procedure

                                              Check non-heap memory usage.

                                              -
                                              1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm for which the ID is 43020, and check the RoleName in Location and confirm the IP address of HostName.
                                              2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > IndexServer2x Memory Usage Statistics > OK. Check whether the non-heap memory used by the IndexServer2x process reaches the maximum non-heap memory threshold (95% by default).

                                                • If the threshold is reached, go to 3.
                                                • If the threshold is not reached, go to 7.
                                                -

                                              3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Statistics for the non-heap memory of the IndexServer2x Process > OK. Based on the alarm generation time, check the values of the used non-heap memory of the IndexServer2x process in the corresponding period and obtain the maximum value.
                                              4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x> Tuning. You can change the value of XX:MaxMetaspaceSize in the spark.driver.extraJavaOptions parameter based on the ratio of the maximum non-heap memory used by the IndexServer2x process to the threshold specified by IndexServer2x Non-Heap Memory Usage Statistics (IndexServer2x) in the alarm period.

                                                On FusionInsight Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > IndexServer2x Non-Heap Memory Usage Statistics (IndexServer2x) to view the threshold.

                                                +
                                                1. On MRS Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm for which the ID is 43020, and check the RoleName in Location and confirm the IP address of HostName.
                                                2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > IndexServer2x Memory Usage Statistics > OK. Check whether the non-heap memory used by the IndexServer2x process reaches the maximum non-heap memory threshold (95% by default).

                                                  • If the threshold is reached, go to 3.
                                                  • If the threshold is not reached, go to 7.
                                                  +

                                                3. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Statistics for the non-heap memory of the IndexServer2x Process > OK. Based on the alarm generation time, check the values of the used non-heap memory of the IndexServer2x process in the corresponding period and obtain the maximum value.
                                                4. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x> Tuning. You can change the value of XX:MaxMetaspaceSize in the spark.driver.extraJavaOptions parameter based on the ratio of the maximum non-heap memory used by the IndexServer2x process to the threshold specified by IndexServer2x Non-Heap Memory Usage Statistics (IndexServer2x) in the alarm period.

                                                  On MRS Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > IndexServer2x Non-Heap Memory Usage Statistics (IndexServer2x) to view the threshold.

                                                5. Restart all IndexServer2x instances.
                                                6. After 10 minutes, check whether the alarm is cleared.

                                                  • If the alarm is cleared, no further action is required.
                                                  • If the alarm is not cleared, go to 7.

                                                Collect fault information.

                                                -
                                                1. On FusionInsight Manager, choose O&M > Log > Download.
                                                2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                4. Contact the O&M personnel and provide the collected logs.
                                                +
                                                1. On MRS Manager, choose O&M > Log > Download.
                                                2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                4. Contact the O&M personnel and provide the collected logs.

                                                Alarm Clearing

                                                After the fault is rectified, the system automatically clears this alarm.

                                                diff --git a/docs/mrs/umn/ALM-43021.html b/docs/mrs/umn/ALM-43021.html index 422fc4b7..53e0fe34 100644 --- a/docs/mrs/umn/ALM-43021.html +++ b/docs/mrs/umn/ALM-43021.html @@ -64,13 +64,13 @@

                                                Possible Causes

                                                The direct heap memory of the IndexServer2x process is overused or the direct heap memory is inappropriately allocated.

                                                Procedure

                                                Check direct heap memory usage.

                                                -
                                                1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm for which the ID is 43021, and check the RoleName in Location and confirm the IP address of HostName.
                                                2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > IndexServer2x Memory Usage Statistics > OK. Check whether the direct memory used by the IndexServer2x process reaches the maximum direct memory threshold.

                                                  • If the threshold is reached, go to 3.
                                                  • If the threshold is not reached, go to 7.
                                                  -

                                                3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Direct Memory of IndexServer2x > OK. Based on the alarm generation time, check the values of the used direct memory of the IndexServer2x process in the corresponding period and obtain the maximum value.
                                                4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x> Tuning. You can change the value of XX:MaxDirectMemorySize (the default value is 512 MB) in the spark.driver.extraJavaOptions parameter based on the ratio of the maximum direct memory used by the IndexServer2x process to the threshold specified by IndexServer2x Direct Memory Usage Statistics (IndexServer2x) in the alarm period. If the alarm persists after the parameter value is changed, increase the value by 0.5 times. If the alarm is generated frequently, double the rate.

                                                  On FusionInsight Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > IndexServer2x Direct Memory Usage Statistics (IndexServer2x) to view the threshold.

                                                  +
                                                  1. On MRS Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm for which the ID is 43021, and check the RoleName in Location and confirm the IP address of HostName.
                                                  2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > IndexServer2x Memory Usage Statistics > OK. Check whether the direct memory used by the IndexServer2x process reaches the maximum direct memory threshold.

                                                    • If the threshold is reached, go to 3.
                                                    • If the threshold is not reached, go to 7.
                                                    +

                                                  3. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click the IndexServer2x that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Direct Memory of IndexServer2x > OK. Based on the alarm generation time, check the values of the used direct memory of the IndexServer2x process in the corresponding period and obtain the maximum value.
                                                  4. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x> Tuning. You can change the value of XX:MaxDirectMemorySize (the default value is 512 MB) in the spark.driver.extraJavaOptions parameter based on the ratio of the maximum direct memory used by the IndexServer2x process to the threshold specified by IndexServer2x Direct Memory Usage Statistics (IndexServer2x) in the alarm period. If the alarm persists after the parameter value is changed, increase the value by 0.5 times. If the alarm is generated frequently, double the rate.

                                                    On MRS Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory > IndexServer2x Direct Memory Usage Statistics (IndexServer2x) to view the threshold.

                                                  5. Restart all IndexServer2x instances.
                                                  6. After 10 minutes, check whether the alarm is cleared.

                                                    • If the alarm is cleared, no further action is required.
                                                    • If the alarm is not cleared, go to 7.

                                                  Collect fault information.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M > Log > Download.
                                                  2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact the O&M personnel and provide the collected logs.
                                                  +
                                                  1. On MRS Manager, choose O&M > Log > Download.
                                                  2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact the O&M personnel and provide the collected logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-43022.html b/docs/mrs/umn/ALM-43022.html index b16d4790..767f13c1 100644 --- a/docs/mrs/umn/ALM-43022.html +++ b/docs/mrs/umn/ALM-43022.html @@ -64,11 +64,11 @@

                                                  Possible Causes

                                                  The heap memory of the IndexServer2x process is overused or the heap memory is inappropriately allocated. As a result, GC occurs frequently.

                                                  Procedure

                                                  Check the GC time.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm with ID 43022, and check the RoleName in Location and confirm the IP address of HostName.
                                                  2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the IndexServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of IndexServer2x from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold (default value: 12 seconds).

                                                    • If the threshold is reached, go to 3.
                                                    • If the threshold is not reached, go to 6.
                                                    -

                                                  3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x > Default. The default value of the SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: Increase the value of the SPARK_DRIVER_MEMORY parameter 1.5 times to its default value. If this alarm is still generated occasionally after the adjustment, increase the value by 0.5 times. Double the value if the alarm is reported frequently.
                                                  4. Restart all IndexServer2x instances.
                                                  5. After 10 minutes, check whether the alarm is cleared.

                                                    • If the alarm is cleared, no further action is required.
                                                    • If the alarm is not cleared, go to 6.
                                                    +
                                                    1. On MRS Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm with ID 43022, and check the RoleName in Location and confirm the IP address of HostName.
                                                    2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the IndexServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of IndexServer2x from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold (default value: 12 seconds).

                                                      • If the threshold is reached, go to 3.
                                                      • If the threshold is not reached, go to 6.
                                                      +

                                                    3. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x > Default. The default value of the SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: Increase the value of the SPARK_DRIVER_MEMORY parameter 1.5 times to its default value. If this alarm is still generated occasionally after the adjustment, increase the value by 0.5 times. Double the value if the alarm is reported frequently.
                                                    4. Restart all IndexServer2x instances.
                                                    5. After 10 minutes, check whether the alarm is cleared.

                                                      • If the alarm is cleared, no further action is required.
                                                      • If the alarm is not cleared, go to 6.

                                                    Collect fault information.

                                                    -
                                                    1. On FusionInsight Manager, choose O&M > Log > Download.
                                                    2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                    4. Contact the O&M personnel and provide the collected logs.
                                                    +
                                                    1. On MRS Manager, choose O&M > Log > Download.
                                                    2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                    4. Contact the O&M personnel and provide the collected logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-43023.html b/docs/mrs/umn/ALM-43023.html index d608db29..09d899d7 100644 --- a/docs/mrs/umn/ALM-43023.html +++ b/docs/mrs/umn/ALM-43023.html @@ -64,11 +64,11 @@

                                                  Possible Causes

                                                  The heap memory of the IndexServer2x process is overused or the heap memory is inappropriately allocated. As a result, Full GC occurs frequently.

                                                  Procedure

                                                  Check the number of Full GCs.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm with the ID 43023, and check the RoleName in Location and confirm the IP address of HostName.
                                                  2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the IndexServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the chart area and choose Customize > GC Number > Full GC Number of IndexServer2x from the drop-down list box in the upper right corner and click OK to check whether the GC number is larger than the threshold (default value: 12).

                                                    • If the threshold is reached, go to 3.
                                                    • If the threshold is not reached, go to 6.
                                                    -

                                                  3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x > Tuning. The default value of the SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. Double the value if the alarm is reported frequently. In the case of large service volume and high service concurrency, you are advised to add instances.
                                                  4. Restart all IndexServer2x instances.
                                                  5. After 10 minutes, check whether the alarm is cleared.

                                                    • If the alarm is cleared, no further action is required.
                                                    • If the alarm is not cleared, go to 6.
                                                    +
                                                    1. On MRS Manager, choose O&M > Alarm > Alarms. In the displayed alarm list, choose the alarm with the ID 43023, and check the RoleName in Location and confirm the IP address of HostName.
                                                    2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the IndexServer2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the chart area and choose Customize > GC Number > Full GC Number of IndexServer2x from the drop-down list box in the upper right corner and click OK to check whether the GC number is larger than the threshold (default value: 12).

                                                      • If the threshold is reached, go to 3.
                                                      • If the threshold is not reached, go to 6.
                                                      +

                                                    3. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations > All Configurations > IndexServer2x > Tuning. The default value of the SPARK_DRIVER_MEMORY is 4 GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. Double the value if the alarm is reported frequently. In the case of large service volume and high service concurrency, you are advised to add instances.
                                                    4. Restart all IndexServer2x instances.
                                                    5. After 10 minutes, check whether the alarm is cleared.

                                                      • If the alarm is cleared, no further action is required.
                                                      • If the alarm is not cleared, go to 6.

                                                    Collect fault information.

                                                    -
                                                    1. On FusionInsight Manager, choose O&M > Log > Download.
                                                    2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected fault logs.
                                                    +
                                                    1. On MRS Manager, choose O&M > Log > Download.
                                                    2. Expand the Service drop-down list, and select Spark2x for the target cluster.
                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                    4. Contact the O&M personnel and send the collected fault logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-45000.html b/docs/mrs/umn/ALM-45000.html index 1163c8ea..ece8014b 100644 --- a/docs/mrs/umn/ALM-45000.html +++ b/docs/mrs/umn/ALM-45000.html @@ -60,7 +60,7 @@

                                                  Possible Causes

                                                  • The KrbServer service is abnormal.
                                                  • The ZooKeeper service is abnormal.
                                                  • The HDFS service is abnormal.
                                                  • The Yarn service is abnormal.
                                                  • The DBService service is abnormal.
                                                  • The Hive service is abnormal.
                                                  • Thre are no HSBroker instances in HetuEngine.

                                                  Procedure

                                                  Check the KrbServer service status.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M > Alarm > Alarm.
                                                  2. In the alarm list, check whether the "ALM-25500 KrbServer Service Unavailable" alarm is generated.

                                                    • If yes, go to 3.
                                                    • If no, go to 5.
                                                    +
                                                    1. On MRS Manager, choose O&M > Alarm > Alarm.
                                                    2. In the alarm list, check whether the "ALM-25500 KrbServer Service Unavailable" alarm is generated.

                                                      • If yes, go to 3.
                                                      • If no, go to 5.

                                                    3. Clear "ALM-25500 KrbServer Service Unavailable" according to the alarm help.
                                                    4. In the alarm list, check whether the alarm "ALM-45000 HetuEngine Service Unavailable" is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 5.

                                                    Check the ZooKeeper service status.

                                                    @@ -85,15 +85,15 @@

                                                  3. Clear "ALM-16004 Hive Service Unavailable" according to the alarm help.
                                                  4. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 20.

                                                  Check whether there are no HSBroker instances in HetuEngine.

                                                  -
                                                  1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HetuEngine. On the page that is displayed, click the Instance tab.
                                                  2. Check whether there are no HSBroker instances.

                                                    • If yes, click Add Instance to add one.
                                                    • If no, go to 23.
                                                    +
                                                    1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HetuEngine. On the page that is displayed, click the Instance tab.
                                                    2. Check whether there are no HSBroker instances.

                                                      • If yes, click Add Instance to add one.
                                                      • If no, go to 23.

                                                    3. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 23.

                                                    Check the network connection between HetuEngine and ZooKeeper, HDFS, YARN, DBService, and Hive.

                                                    -
                                                    1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > HetuEngine. On the page that is displayed, click the Instance tab.
                                                    2. Click the host name in the HSBroker row and record the management IP address in the Basic Information area.
                                                    3. Log in to the host where HSBroker resides as user omm using the IP address obtained in 25.
                                                    1. Run the ping command to check whether the network connection between the host where HSBroker resides and the hosts where ZooKeeper, HDFS, Yarn, DBService, and Hive reside is in the normal state.

                                                      • If yes, go to 30.
                                                      • If no, go to 28.
                                                      -

                                                    2. Contact the network administrator to restore the network.
                                                    3. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 30.
                                                      +
                                                      1. On MRS Manager, choose Cluster > Name of the desired cluster > Services > HetuEngine. On the page that is displayed, click the Instance tab.
                                                      2. Click the host name in the HSBroker row and record the management IP address in the Basic Information area.
                                                      3. Log in to the host where HSBroker resides as user omm using the IP address obtained in 25.
                                                      1. Run the ping command to check whether the network connection between the host where HSBroker resides and the hosts where ZooKeeper, HDFS, Yarn, DBService, and Hive reside is in the normal state.

                                                        • If yes, go to 30.
                                                        • If no, go to 28.
                                                        +

                                                      2. Contact the network administrator to restore the network.
                                                      3. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared.

                                                        • If yes, no further action is required.
                                                        • If no, go to 30.

                                                      Collect fault information.

                                                      -
                                                      1. On FusionInsight Manager, choose O&M > Log > Download.
                                                      2. Expand the Service drop-down list. In the Services dialog box that is displayed, select HetuEngine under the target cluster name, and click OK.
                                                      3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                      5. Contact O&M personnel and provide the collected logs.
                                                      +
                                                      1. On MRS Manager, choose O&M > Log > Download.
                                                      2. Expand the Service drop-down list. In the Services dialog box that is displayed, select HetuEngine under the target cluster name, and click OK.
                                                      3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                      5. Contact O&M personnel and provide the collected logs.

                                                  Alarm Clearing

                                                  After the fault is rectified, the system automatically clears this alarm.

                                                  diff --git a/docs/mrs/umn/ALM-45001.html b/docs/mrs/umn/ALM-45001.html index b305351f..48a489bd 100644 --- a/docs/mrs/umn/ALM-45001.html +++ b/docs/mrs/umn/ALM-45001.html @@ -73,11 +73,11 @@

                                                5. Clear "ALM-18022 Insufficient YARN Queue Resources" according to the alarm help.
                                                6. In the alarm list, check whether the "ALM-45001 Faulty HetuEngine Compute Instances" alarm is cleared.

                                                  • If yes, no further action is required.
                                                  • If no, go to 10.

                                                Check the HetuEngine compute instance status.

                                                -
                                                1. Log in to FusionInsight Manager as an administrator who can access the HetuEngine web UI and choose Cluster > Services > HetuEngine.
                                                2. In the Basic Information area on the Dashboard tab page, click the link next to HSConsole WebUI to access the HSConsole page.
                                                3. On the compute instance page, check whether any compute instances are in the FAULT state.

                                                  • If yes, go to 13.
                                                  • If no, go to 14.
                                                  +
                                                  1. Log in to MRS Manager as an administrator who can access the HetuEngine web UI and choose Cluster > Services > HetuEngine.
                                                  2. In the Basic Information area on the Dashboard tab page, click the link next to HSConsole WebUI to access the HSConsole page.
                                                  3. On the compute instance page, check whether any compute instances are in the FAULT state.

                                                    • If yes, go to 13.
                                                    • If no, go to 14.

                                                  1. In the Operation column of the target compute instance, click Start and wait until the instance is started.
                                                  2. In the alarm list, check whether the "ALM-45001 Faulty HetuEngine Compute Instances" alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 15.

                                                  Collect fault information.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M > Log > Download.
                                                  2. Expand the Service drop-down list. In the Services dialog box that is displayed, select HetuEngine under the target cluster name, and click OK.
                                                  3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                  4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  5. Contact O&M personnel and provide the collected logs.
                                                  +
                                                  1. On MRS Manager, choose O&M > Log > Download.
                                                  2. Expand the Service drop-down list. In the Services dialog box that is displayed, select HetuEngine under the target cluster name, and click OK.
                                                  3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                  4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  5. Contact O&M personnel and provide the collected logs.

                                                Alarm Clearing

                                                This alarm is automatically cleared after the fault is rectified.

                                                diff --git a/docs/mrs/umn/ALM-45175.html b/docs/mrs/umn/ALM-45175.html index c2c10d30..2c70fc61 100644 --- a/docs/mrs/umn/ALM-45175.html +++ b/docs/mrs/umn/ALM-45175.html @@ -65,11 +65,11 @@

                                                Possible Causes

                                                Frame freezing occurs on the OBS server, or the network between the OBS client and the OBS server is unstable.

                                                Procedure

                                                Check the heap memory usage.

                                                -
                                                1. On the FusionInsight Manager homepage, choose O&M > Alarm > Alarms > Average Time for Calling the OBS Metadata API Exceeds the Threshold, view the role name in Location, and check the instance IP address.
                                                2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Average time of OBS interface calls from OBS Meta data Operations, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                  • If yes, go to 3.
                                                  • If no, go to 5.
                                                  +
                                                  1. On the MRS Manager homepage, choose O&M > Alarm > Alarms > Average Time for Calling the OBS Metadata API Exceeds the Threshold, view the role name in Location, and check the instance IP address.
                                                  2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Average time of OBS interface calls from OBS Meta data Operations, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                    • If yes, go to 3.
                                                    • If no, go to 5.

                                                  3. Choose Cluster > Name of the desired cluster > O&M > Alarm > Thresholds > meta > Average Time for Calling the OBS Metadata API. Increase the threshold or smoothing times as required.
                                                  4. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 5.

                                                  Collect the fault information.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.
                                                  +
                                                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.

                                                Alarm Clearing

                                                This alarm is automatically cleared after the fault is rectified.

                                                diff --git a/docs/mrs/umn/ALM-45176.html b/docs/mrs/umn/ALM-45176.html index f19d8ae5..2f1f88f6 100644 --- a/docs/mrs/umn/ALM-45176.html +++ b/docs/mrs/umn/ALM-45176.html @@ -65,11 +65,11 @@

                                                Possible Causes

                                                An execution exception or severe timeout occurs on the OBS server.

                                                Procedure

                                                Check the heap memory usage.

                                                -
                                                1. On the FusionInsight Manager homepage, choose O&M > Alarm > Alarms > Success Rate for Calling the OBS Metadata API Is Lower Than the Threshold, view the role name in Location, and check the instance IP address.
                                                2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Success percent of OBS interface calls from OBS Meta data Operations, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                  • If yes, go to 3.
                                                  • If no, go to 5.
                                                  +
                                                  1. On the MRS Manager homepage, choose O&M > Alarm > Alarms > Success Rate for Calling the OBS Metadata API Is Lower Than the Threshold, view the role name in Location, and check the instance IP address.
                                                  2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Success percent of OBS interface calls from OBS Meta data Operations, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                    • If yes, go to 3.
                                                    • If no, go to 5.

                                                  3. Choose Cluster > Name of the desired cluster > O&M > Alarm > Thresholds > meta > Success Rate for Calling the OBS Metadata API. Increase the threshold or smoothing times as required.
                                                  4. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 5.

                                                  Collect the fault information.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.
                                                  +
                                                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.

                                                Alarm Clearing

                                                This alarm is automatically cleared after the fault is rectified.

                                                diff --git a/docs/mrs/umn/ALM-45177.html b/docs/mrs/umn/ALM-45177.html index bfb3affb..03b0ab7e 100644 --- a/docs/mrs/umn/ALM-45177.html +++ b/docs/mrs/umn/ALM-45177.html @@ -65,12 +65,12 @@

                                                Possible Causes

                                                An execution exception or severe timeout occurs on the OBS server.

                                                Procedure

                                                Check the heap memory usage.

                                                -
                                                1. On the FusionInsight Manager homepage, choose O&M > Alarm > Alarms > Success Rate for Calling the OBS Data Read API Is Lower Than the Threshold, view the role name in Location, and check the instance IP address.
                                                2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Success percent of OBS data read operation interface calls from OBS data read operation, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                  • If yes, go to 3.
                                                  • If no, go to 5.
                                                  +
                                                  1. On the MRS Manager homepage, choose O&M > Alarm > Alarms > Success Rate for Calling the OBS Data Read API Is Lower Than the Threshold, view the role name in Location, and check the instance IP address.
                                                  2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Success percent of OBS data read operation interface calls from OBS data read operation, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                    • If yes, go to 3.
                                                    • If no, go to 5.

                                                  3. Choose Cluster > Name of the desired cluster > O&M > Alarm > Thresholds > meta > Success Rate for Calling the OBS Data Read API. Increase the threshold or smoothing times as required.

                                                  4. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 5.

                                                  Collect the fault information.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.
                                                  +
                                                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.

                                                Alarm Clearing

                                                This alarm is automatically cleared after the fault is rectified.

                                                diff --git a/docs/mrs/umn/ALM-45178.html b/docs/mrs/umn/ALM-45178.html index 99bea99f..e5605164 100644 --- a/docs/mrs/umn/ALM-45178.html +++ b/docs/mrs/umn/ALM-45178.html @@ -65,12 +65,12 @@

                                                Possible Causes

                                                An execution exception or severe timeout occurs on the OBS server.

                                                Procedure

                                                Check the heap memory usage.

                                                -
                                                1. On the FusionInsight Manager homepage, choose O&M > Alarm > Alarms > Success Rate for Calling the OBS Data Write API Is Lower Than the Threshold, view the role name in Location, and check the instance IP address.
                                                2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Success percent of OBS data write operation interface calls from OBS data write operation, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                  • If yes, go to 3.
                                                  • If no, go to 5.
                                                  +
                                                  1. On the MRS Manager homepage, choose O&M > Alarm > Alarms > Success Rate for Calling the OBS Data Write API Is Lower Than the Threshold, view the role name in Location, and check the instance IP address.
                                                  2. Choose Cluster > Name of the desired cluster > Services > meta > Instance > meta (IP address of the instance for which the alarm is generated). Click the drop-down list in the upper right corner of the chart area and choose Customize. In the dialog box that is displayed, select Success percent of OBS data write operation interface calls from OBS data write operation, and click OK. Check whether the average time of OBS metadata API calls exceeds the threshold.

                                                    • If yes, go to 3.
                                                    • If no, go to 5.

                                                  3. Choose Cluster > Name of the desired cluster > O&M > Alarm > Thresholds > meta > Success Rate for Calling the OBS Data Write API. Increase the threshold or smoothing times as required.

                                                  4. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 5.

                                                  Collect the fault information.

                                                  -
                                                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.
                                                  +
                                                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                  2. In the Services area, select NodeAgent, NodeMetricAgent, OmmServer, and OmmAgent under OMS.
                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                  4. Contact O&M personnel and provide the collected logs.

                                                Alarm Clearing

                                                This alarm is automatically cleared after the fault is rectified.

                                                diff --git a/docs/mrs/umn/ALM-45179.html b/docs/mrs/umn/ALM-45179.html index e4fda575..2b84031c 100644 --- a/docs/mrs/umn/ALM-45179.html +++ b/docs/mrs/umn/ALM-45179.html @@ -64,11 +64,11 @@

                                                Possible Causes

                                                An execution exception or severe timeout occurs on the OBS server.

                                                -

                                                Procedure

                                                1. Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS readFully interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                2. Check whether the alarm is cleared.

                                                  • If yes, no further action is required.
                                                  • If no, go to 3.
                                                  +

                                                  Procedure

                                                  1. Log in to MRS Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS readFully interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                  2. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 3.

                                                  3. Contact OBS O&M personnel to check whether the OBS service is normal.

                                                    • If yes, go to 4.
                                                    • If no, contact OBS O&M personnel to restore the OBS service.

                                                  Collect fault information.

                                                  -
                                                  1. On FusionInsight Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data read operation in the Chart Category area. In the Number of failed calls to the OBS readFully interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS readFully API calls. For example, the host name is node-ana-corevpeO003.

                                                    +
                                                    1. On MRS Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data read operation in the Chart Category area. In the Number of failed calls to the OBS readFully interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS readFully API calls. For example, the host name is node-ana-corevpeO003.

                                                    2. Choose O&M > Log > Download and select meta and meta under it for Service.
                                                    3. Select the host obtained in 4 for Hosts.
                                                    4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                    5. Contact O&M personnel and provide the collected logs.

                                                  Alarm Clearing

                                                  This alarm is automatically cleared after the fault is rectified.

                                                  diff --git a/docs/mrs/umn/ALM-45180.html b/docs/mrs/umn/ALM-45180.html index dfef105b..b53be49f 100644 --- a/docs/mrs/umn/ALM-45180.html +++ b/docs/mrs/umn/ALM-45180.html @@ -64,11 +64,11 @@

                                                  Possible Causes

                                                  An execution exception or severe timeout occurs on the OBS server.

                                                  -

                                                  Procedure

                                                  1. Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS read interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                  2. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 3.
                                                    +

                                                    Procedure

                                                    1. Log in to MRS Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS read interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                    2. Check whether the alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 3.

                                                    3. Contact OBS O&M personnel to check whether the OBS service is normal.

                                                      • If yes, go to 4.
                                                      • If no, contact OBS O&M personnel to restore the OBS service.

                                                    Collect fault information.

                                                    -
                                                    1. On FusionInsight Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data read operation in the Chart Category area. In the Number of failed calls to the OBS read interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS read API calls. For example, the host name is node-ana-corevpeO003.

                                                      +
                                                      1. On MRS Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data read operation in the Chart Category area. In the Number of failed calls to the OBS read interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS read API calls. For example, the host name is node-ana-corevpeO003.

                                                      2. Choose O&M > Log > Download and select meta and meta under it for Service.
                                                      3. Select the host obtained in 4 for Hosts.
                                                      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                      5. Contact O&M personnel and provide the collected logs.

                                                    diff --git a/docs/mrs/umn/ALM-45181.html b/docs/mrs/umn/ALM-45181.html index b34c83d4..e51653f0 100644 --- a/docs/mrs/umn/ALM-45181.html +++ b/docs/mrs/umn/ALM-45181.html @@ -64,11 +64,11 @@

                                                  Possible Causes

                                                  An execution exception or severe timeout occurs on the OBS server.

                                                  -

                                                  Procedure

                                                  1. Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS write interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                  2. Check whether the alarm is cleared.

                                                    • If yes, no further action is required.
                                                    • If no, go to 3.
                                                    +

                                                    Procedure

                                                    1. Log in to MRS Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS write interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                    2. Check whether the alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 3.

                                                    3. Contact OBS O&M personnel to check whether the OBS service is normal.

                                                      • If yes, go to 4.
                                                      • If no, contact OBS O&M personnel to restore the OBS service.

                                                    Collect fault information.

                                                    -
                                                    1. On FusionInsight Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data write operation in the Chart Category area. In the Number of failed calls to the OBS write interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS write API calls. For example, the host name is node-ana-corevpeO003.

                                                      +
                                                      1. On MRS Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data write operation in the Chart Category area. In the Number of failed calls to the OBS write interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS write API calls. For example, the host name is node-ana-corevpeO003.

                                                      2. Choose O&M > Log > Download and select meta and meta under it for Service.
                                                      3. Select the host obtained in 4 for Hosts.
                                                      4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                      5. Contact O&M personnel and provide the collected logs.

                                                    Alarm Clearing

                                                    This alarm is automatically cleared after the fault is rectified.

                                                    diff --git a/docs/mrs/umn/ALM-45182.html b/docs/mrs/umn/ALM-45182.html index 856e7c04..a3a7ecfd 100644 --- a/docs/mrs/umn/ALM-45182.html +++ b/docs/mrs/umn/ALM-45182.html @@ -64,11 +64,11 @@

                                                    Possible Causes

                                                    The frequency of requesting OBS APIs is too high.

                                                    -

                                                    Procedure

                                                    1. Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of Throttled OBS Operations. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                    2. Check whether the alarm is cleared.

                                                      • If yes, no further action is required.
                                                      • If no, go to 3.
                                                      +

                                                      Procedure

                                                      1. Log in to MRS Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of Throttled OBS Operations. In the right pane, set Threshold or Trigger Count to a larger value as required.
                                                      2. Check whether the alarm is cleared.

                                                        • If yes, no further action is required.
                                                        • If no, go to 3.

                                                      3. Contact OBS O&M personnel to check whether the OBS service is normal.

                                                        • If yes, go to 4.
                                                        • If no, contact OBS O&M personnel to restore the OBS service.

                                                      Collect fault information.

                                                      -
                                                      1. On FusionInsight Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS Throttled in the Chart Category area. In the Number of Throttled OBS Operations-All Instances chart, view the host name of the instance that has the maximum number of throttled OBS API calls. For example, the host name is node-ana-coreUQqJ0002.

                                                        +
                                                        1. On MRS Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS Throttled in the Chart Category area. In the Number of Throttled OBS Operations-All Instances chart, view the host name of the instance that has the maximum number of throttled OBS API calls. For example, the host name is node-ana-coreUQqJ0002.

                                                        2. Choose O&M > Log > Download and select meta and meta under it for Service.
                                                        3. Select the host obtained in 4 for Hosts.
                                                        1. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                        2. Contact O&M personnel and provide the collected logs.

                                                      Alarm Clearing

                                                      This alarm is automatically cleared after the fault is rectified.

                                                      diff --git a/docs/mrs/umn/ALM-45275.html b/docs/mrs/umn/ALM-45275.html index cd462227..f1203def 100644 --- a/docs/mrs/umn/ALM-45275.html +++ b/docs/mrs/umn/ALM-45275.html @@ -60,7 +60,7 @@

                                                      Possible Causes

                                                      • The DBService service on which Ranger depends is abnormal.
                                                      • The RangerAdmin role instance is abnormal.

                                                      Procedure

                                                      Check the DBService process status.

                                                      -
                                                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the displayed page, check whether the ALM-27001 DBService Service Unavailable alarm is reported.

                                                        • If yes, go to 2.
                                                        • If no, go to 3.
                                                        +
                                                        1. On MRS Manager, choose O&M > Alarm > Alarms. On the displayed page, check whether the ALM-27001 DBService Service Unavailable alarm is reported.

                                                          • If yes, go to 2.
                                                          • If no, go to 3.

                                                        2. Rectify the DBService service fault by following the handling procedure of ALM-27001 DBService Service Unavailable. After the DBService alarm is cleared, check whether Ranger Service Unavailable alarm is cleared.

                                                          • If yes, no further action is required.
                                                          • If no, go to 3.

                                                        Check all RangerAdmin instances.

                                                        @@ -68,7 +68,7 @@

                                                      2. In the alarm list, check whether the alarm "Ranger Service Unavailable" is cleared.

                                                        • If yes, no further action is required.
                                                        • If no, go to 5.

                                                      Collect the fault information.

                                                      -
                                                      1. On FusionInsight Manager, choose O&M > Log > Download.
                                                      2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                      4. Contact O&M personnel and provide the collected logs.
                                                      +
                                                      1. On MRS Manager, choose O&M > Log > Download.
                                                      2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                      4. Contact O&M personnel and provide the collected logs.

                                                      Alarm Clearing

                                                      After the fault that triggers the alarm is rectified, the alarm is automatically cleared.

                                                      diff --git a/docs/mrs/umn/ALM-45276.html b/docs/mrs/umn/ALM-45276.html index ee54a905..a57be511 100644 --- a/docs/mrs/umn/ALM-45276.html +++ b/docs/mrs/umn/ALM-45276.html @@ -60,11 +60,11 @@

                                                      Possible Causes

                                                      The RangerAdmin port is not started.

                                                      Procedure

                                                      Check the port process.

                                                      -
                                                      1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
                                                      2. Log in to the node where the RangerAdmin instance is located as user omm. Run the ps -ef|grep "proc_rangeradmin" | grep -v grep | awk -F ' ' '{print $2}' command to obtain pid of the RangerAdmin process, and run the netstat -anp|grep pid | grep LISTEN command to check whether the RangerAdmin process listens to port 21401 in the security mode and port 21400 in standard mode.

                                                        • If yes, go to 4.
                                                        • If no, restart the faulty RangerAdmin instance or Ranger service and go to 3.
                                                        +
                                                        1. In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
                                                        2. Log in to the node where the RangerAdmin instance is located as user omm. Run the ps -ef|grep "proc_rangeradmin" | grep -v grep | awk -F ' ' '{print $2}' command to obtain pid of the RangerAdmin process, and run the netstat -anp|grep pid | grep LISTEN command to check whether the RangerAdmin process listens to port 21401 in the security mode and port 21400 in standard mode.

                                                          • If yes, go to 4.
                                                          • If no, restart the faulty RangerAdmin instance or Ranger service and go to 3.

                                                        3. In the alarm list, check whether the "Abnormal RangerAdmin Status" alarm is cleared.

                                                          • If yes, no further action is required.
                                                          • If no, go to 4.

                                                        Collect the fault information.

                                                        -
                                                        1. On FusionInsight Manager, choose O&M > Log > Download.
                                                        2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                        4. Contact O&M personnel and provide the collected logs.
                                                        +
                                                        1. On MRS Manager, choose O&M > Log > Download.
                                                        2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                        4. Contact O&M personnel and provide the collected logs.

                                                      Alarm Clearing

                                                      After the fault that triggers the alarm is rectified, the alarm is automatically cleared.

                                                      diff --git a/docs/mrs/umn/ALM-45277.html b/docs/mrs/umn/ALM-45277.html index 99b0be83..63f9a1f8 100644 --- a/docs/mrs/umn/ALM-45277.html +++ b/docs/mrs/umn/ALM-45277.html @@ -64,13 +64,13 @@

                                                      Possible Causes

                                                      The heap memory usage of the RangerAdmin instance is high or the heap memory is improperly allocated.

                                                      Procedure

                                                      Check the heap memory usage.

                                                      -
                                                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45277 RangerAdmin Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                      2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > RangerAdmin Heap Memory Usage. Click OK.
                                                      3. Check whether the heap memory used by RangerAdmin reaches the threshold (95% of the maximum heap memory by default).

                                                        • If yes, go to 4.
                                                        • If no, go to 6.
                                                        -

                                                      4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                        If this alarm is generated, the heap memory configured for RangerAdmin cannot meet the heap memory required by the RangerAdmin process. You are advised to check the heap memory usage of RangerAdmin and change the value of -Xmx in GC_OPTS to the twice of the heap memory used by RangerAdmin. The value can be changed based on the actual service scenario. For details, see 2.

                                                        +
                                                        1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45277 RangerAdmin Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                        2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > RangerAdmin Heap Memory Usage. Click OK.
                                                        3. Check whether the heap memory used by RangerAdmin reaches the threshold (95% of the maximum heap memory by default).

                                                          • If yes, go to 4.
                                                          • If no, go to 6.
                                                          +

                                                        4. On MRS Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                          If this alarm is generated, the heap memory configured for RangerAdmin cannot meet the heap memory required by the RangerAdmin process. You are advised to check the heap memory usage of RangerAdmin and change the value of -Xmx in GC_OPTS to the twice of the heap memory used by RangerAdmin. The value can be changed based on the actual service scenario. For details, see 2.

                                                        5. Restart the affected services or instances and check whether the alarm is cleared.

                                                          • If yes, no further action is required.
                                                          • If no, go to 6.

                                                        Collect the fault information.

                                                        -
                                                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                        2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                        4. Contact O&M personnel and provide the collected logs.
                                                        +
                                                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                        2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                        4. Contact O&M personnel and provide the collected logs.

                                                        Alarm Clearing

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-45278.html b/docs/mrs/umn/ALM-45278.html index 0c644f5a..36327e1c 100644 --- a/docs/mrs/umn/ALM-45278.html +++ b/docs/mrs/umn/ALM-45278.html @@ -61,16 +61,16 @@

                                                        Impact on the System

                                                        Direct memory overflow may cause service breakdown.

                                                        -

                                                        Possible Causes

                                                        The direct memory of the RangerAdmin instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.

                                                        +

                                                        Possible Causes

                                                        The direct memory of the RangerAdmin instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.

                                                        Procedure

                                                        Check the direct memory usage.

                                                        -
                                                        1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45278 RangerAdmin Direct Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                        2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > RangerAdmin Direct Memory Usage. Click OK.
                                                        3. Check whether the direct memory used by RangerAdmin reaches the threshold (80% of the maximum direct memory by default).

                                                          • If yes, go to 4.
                                                          • If no, go to 6.
                                                          -

                                                        4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                          If this alarm is generated, the direct memory configured for RangerAdmin cannot meet the direct memory required by the RangerAdmin process. You are advised to check the direct memory usage of RangerAdmin and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by RangerAdmin. You can change the value based on the actual service scenario. For details, see 2.

                                                          +
                                                          1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45278 RangerAdmin Direct Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                          2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > RangerAdmin Direct Memory Usage. Click OK.
                                                          3. Check whether the direct memory used by RangerAdmin reaches the threshold (80% of the maximum direct memory by default).

                                                            • If yes, go to 4.
                                                            • If no, go to 6.
                                                            +

                                                          4. On MRS Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                            If this alarm is generated, the direct memory configured for RangerAdmin cannot meet the direct memory required by the RangerAdmin process. You are advised to check the direct memory usage of RangerAdmin and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by RangerAdmin. You can change the value based on the actual service scenario. For details, see 2.

                                                          5. Restart the affected services or instances and check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 6.

                                                          Collect the fault information.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                          2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          4. Contact O&M personnel and provide the collected logs.
                                                          +
                                                          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                          2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          4. Contact O&M personnel and provide the collected logs.

                                                          Alarm Clearing

                                                          This alarm is automatically cleared after the fault is rectified.

                                                          diff --git a/docs/mrs/umn/ALM-45279.html b/docs/mrs/umn/ALM-45279.html index f6f0c7d8..fed30a0e 100644 --- a/docs/mrs/umn/ALM-45279.html +++ b/docs/mrs/umn/ALM-45279.html @@ -64,13 +64,13 @@

                                                          Possible Causes

                                                          The non-heap memory usage of the RangerAdmin instance is high or the non-heap memory is improperly allocated.

                                                          Procedure

                                                          Check non-heap memory usage.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45279 RangerAdmin Non Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                          2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > RangerAdmin Non Heap Memory Usage. Click OK.
                                                          3. Check whether the non-heap memory used by RangerAdmin reaches the threshold (80% of the maximum non-heap memory by default).

                                                            • If yes, go to 4.
                                                            • If no, go to 6.
                                                            -

                                                          4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                                                            If this alarm is generated, the non-heap memory size configured for the RangerAdmin instance cannot meet the non-heap memory required by the RangerAdmin process. You are advised to change the value of -XX:MaxPermSize in GC_OPTS to the twice of the current non-heap memory usage or change the value based on the site requirements.

                                                            +
                                                            1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45279 RangerAdmin Non Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                            2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > RangerAdmin Non Heap Memory Usage. Click OK.
                                                            3. Check whether the non-heap memory used by RangerAdmin reaches the threshold (80% of the maximum non-heap memory by default).

                                                              • If yes, go to 4.
                                                              • If no, go to 6.
                                                              +

                                                            4. On MRS Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                                                              If this alarm is generated, the non-heap memory size configured for the RangerAdmin instance cannot meet the non-heap memory required by the RangerAdmin process. You are advised to change the value of -XX:MaxPermSize in GC_OPTS to the twice of the current non-heap memory usage or change the value based on the site requirements.

                                                            5. Restart the affected services or instances and check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 6.

                                                            Collect the fault information.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.
                                                            +
                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45280.html b/docs/mrs/umn/ALM-45280.html index ffe72c79..6f5c393d 100644 --- a/docs/mrs/umn/ALM-45280.html +++ b/docs/mrs/umn/ALM-45280.html @@ -1,7 +1,7 @@

                                                            ALM-45280 RangerAdmin GC Duration Exceeds the Threshold

                                                            -

                                                            Description

                                                            The system checks the GC duration of the RangerAdmin process every 60 seconds. This alarm is generated when the GC duration of the RangerAdmin process exceeds the threshold (12 seconds by default) for five consecutive times. This alarm is cleared when the GC duration is less than the threshold.

                                                            +

                                                            Description

                                                            The system checks the GC duration of the RangerAdmin process every 60 seconds. This alarm is generated when the GC duration of the RangerAdmin process exceeds the threshold (12 seconds by default) for five consecutive times. This alarm is cleared when the GC duration is less than the threshold.

                                                            Attribute

                                                            Alarm ID

                                                            @@ -61,16 +61,16 @@

                                                            Impact on the System

                                                            The RangerAdmin responds slowly.

                                                            -

                                                            Possible Causes

                                                            The heap memory of the RangerAdmin instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                                            +

                                                            Possible Causes

                                                            The heap memory of the RangerAdmin instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                                            Procedure

                                                            Check the GC duration.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45280 RangerAdmin GC Duration Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                            2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated and click the drop-down list in the upper right corner of the chart area. Choose Customize > GC > RangerAdmin GC Duration. Click OK.
                                                            3. Check whether the GC duration of the RangerAdmin process collected every minute exceeds the threshold (12 seconds by default).

                                                              • If yes, go to 4.
                                                              • If no, go to 6.
                                                              -

                                                            4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                              If this alarm is generated, the heap memory configured for RangerAdmin cannot meet the heap memory required by the RangerAdmin process. You are advised to check the heap memory usage of RangerAdmin and change the value of -Xmx in GC_OPTS to the twice of the heap memory used by RangerAdmin. The value can be changed based on the actual service scenario. For details, see 2.

                                                              +
                                                              1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45280 RangerAdmin GC Duration Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                              2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated and click the drop-down list in the upper right corner of the chart area. Choose Customize > GC > RangerAdmin GC Duration. Click OK.
                                                              3. Check whether the GC duration of the RangerAdmin process collected every minute exceeds the threshold (12 seconds by default).

                                                                • If yes, go to 4.
                                                                • If no, go to 6.
                                                                +

                                                              4. On MRS Manager, choose Cluster > Services > Ranger > Instance > RangerAdmin > Instance Configuration. Click All Configurations, and choose RangerAdmin > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                If this alarm is generated, the heap memory configured for RangerAdmin cannot meet the heap memory required by the RangerAdmin process. You are advised to check the heap memory usage of RangerAdmin and change the value of -Xmx in GC_OPTS to the twice of the heap memory used by RangerAdmin. The value can be changed based on the actual service scenario. For details, see 2.

                                                              5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 6.

                                                              Collect the fault information.

                                                              -
                                                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              4. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              4. Contact O&M personnel and provide the collected logs.

                                                              Alarm Clearing

                                                              This alarm is automatically cleared after the fault is rectified.

                                                              diff --git a/docs/mrs/umn/ALM-45281.html b/docs/mrs/umn/ALM-45281.html index 69a68a60..83778fd0 100644 --- a/docs/mrs/umn/ALM-45281.html +++ b/docs/mrs/umn/ALM-45281.html @@ -63,13 +63,13 @@

                                                              Possible Causes

                                                              The heap memory usage of the UserSync instance is high or the heap memory is improperly allocated.

                                                              -

                                                              Procedure

                                                              1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45281 UserSync Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                              2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > UserSync Heap Memory Usage. Click OK.
                                                              3. Check whether the heap memory used by UserSync reaches the threshold (95% of the maximum heap memory by default).

                                                                • If yes, go to 4.
                                                                • If no, go to 6.
                                                                -

                                                              4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                If this alarm is generated, the heap memory configured for UserSync cannot meet the heap memory required by the UserSync process. You are advised to change the -Xmx value of GC_OPTS to twice that of the heap memory used by UserSync. You can change the value based on the actual service scenario. For details about how to check the UserSync heap memory usage, see 2.

                                                                +

                                                                Procedure

                                                                1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45281 UserSync Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > UserSync Heap Memory Usage. Click OK.
                                                                3. Check whether the heap memory used by UserSync reaches the threshold (95% of the maximum heap memory by default).

                                                                  • If yes, go to 4.
                                                                  • If no, go to 6.
                                                                  +

                                                                4. On MRS Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                  If this alarm is generated, the heap memory configured for UserSync cannot meet the heap memory required by the UserSync process. You are advised to change the -Xmx value of GC_OPTS to twice that of the heap memory used by UserSync. You can change the value based on the actual service scenario. For details about how to check the UserSync heap memory usage, see 2.

                                                                5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                  • If yes, no further action is required.
                                                                  • If no, go to 6.

                                                                Collect the fault information.

                                                                -
                                                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                4. Contact O&M personnel and provide the collected logs.
                                                                +
                                                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                4. Contact O&M personnel and provide the collected logs.

                                                                Alarm Clearing

                                                                This alarm is automatically cleared after the fault is rectified.

                                                                diff --git a/docs/mrs/umn/ALM-45282.html b/docs/mrs/umn/ALM-45282.html index 5abe15de..54476d31 100644 --- a/docs/mrs/umn/ALM-45282.html +++ b/docs/mrs/umn/ALM-45282.html @@ -61,16 +61,16 @@

                                                                Impact on the System

                                                                Direct memory overflow may cause service breakdown.

                                                                -

                                                                Possible Causes

                                                                The direct memory of the UserSync instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.

                                                                +

                                                                Possible Causes

                                                                The direct memory of the UserSync instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.

                                                                Procedure

                                                                Check the direct memory usage.

                                                                -
                                                                1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45282 UserSync Direct Memory Usage Exceeds the Threshold. Check the location information of the alarm. Check the name of the instance host for which the alarm is generated.
                                                                2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > UserSync Direct Memory Usage. Click OK.
                                                                3. Check whether the direct memory used by the UserSync reaches the threshold (80% of the maximum direct memory by default).

                                                                  • If yes, go to 4.
                                                                  • If no, go to 6.
                                                                  -

                                                                4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                  If this alarm is generated, the direct memory configured for UserSync cannot meet the direct memory required by the UserSync process. You are advised to check the direct memory usage of UserSync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by UserSync. You can change the value based on the actual service scenario. For details, see 2.

                                                                  +
                                                                  1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45282 UserSync Direct Memory Usage Exceeds the Threshold. Check the location information of the alarm. Check the name of the instance host for which the alarm is generated.
                                                                  2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > UserSync Direct Memory Usage. Click OK.
                                                                  3. Check whether the direct memory used by the UserSync reaches the threshold (80% of the maximum direct memory by default).

                                                                    • If yes, go to 4.
                                                                    • If no, go to 6.
                                                                    +

                                                                  4. On MRS Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                    If this alarm is generated, the direct memory configured for UserSync cannot meet the direct memory required by the UserSync process. You are advised to check the direct memory usage of UserSync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by UserSync. You can change the value based on the actual service scenario. For details, see 2.

                                                                  5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                    • If yes, no further action is required.
                                                                    • If no, go to 6.

                                                                  Collect the fault information.

                                                                  -
                                                                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                  2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                  4. Contact O&M personnel and provide the collected logs.
                                                                  +
                                                                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                  2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                  4. Contact O&M personnel and provide the collected logs.

                                                                  Alarm Clearing

                                                                  This alarm is automatically cleared after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-45283.html b/docs/mrs/umn/ALM-45283.html index 9bbaa2ba..e73ed627 100644 --- a/docs/mrs/umn/ALM-45283.html +++ b/docs/mrs/umn/ALM-45283.html @@ -64,13 +64,13 @@

                                                                  Possible Causes

                                                                  The non-heap memory of the UserSync process is overused or the non-heap memory is inappropriately allocated.

                                                                  Procedure

                                                                  Check non-heap memory usage.

                                                                  -
                                                                  1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45283 UserSync Non Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                  2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > UserSync Non Heap Memory Usage. Click OK.
                                                                  3. Check whether the non-heap memory used by UserSync reaches the threshold (80% of the maximum non-heap memory by default).

                                                                    • If yes, go to 4.
                                                                    • If no, go to 6.
                                                                    -

                                                                  4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and click Save to save the configuration.

                                                                    If this alarm is generated, the non-heap memory size configured for the UserSync instance cannot meet the non-heap memory required by the UserSync process. You are advised to change the -XX:MaxPermSize value of GC_OPTS to twice that of the current non-heap memory size or change the value based on the site requirements.

                                                                    +
                                                                    1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45283 UserSync Non Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                    2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > UserSync Non Heap Memory Usage. Click OK.
                                                                    3. Check whether the non-heap memory used by UserSync reaches the threshold (80% of the maximum non-heap memory by default).

                                                                      • If yes, go to 4.
                                                                      • If no, go to 6.
                                                                      +

                                                                    4. On MRS Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and click Save to save the configuration.

                                                                      If this alarm is generated, the non-heap memory size configured for the UserSync instance cannot meet the non-heap memory required by the UserSync process. You are advised to change the -XX:MaxPermSize value of GC_OPTS to twice that of the current non-heap memory size or change the value based on the site requirements.

                                                                    5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                      • If yes, no further action is required.
                                                                      • If no, go to 6.

                                                                    Collect the fault information.

                                                                    -
                                                                    1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                    2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                    4. Contact O&M personnel and provide the collected logs.
                                                                    +
                                                                    1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                    2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                    3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                    4. Contact O&M personnel and provide the collected logs.

                                                                    Alarm Clearing

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    diff --git a/docs/mrs/umn/ALM-45284.html b/docs/mrs/umn/ALM-45284.html index 0e515b90..83bf80f8 100644 --- a/docs/mrs/umn/ALM-45284.html +++ b/docs/mrs/umn/ALM-45284.html @@ -1,7 +1,7 @@

                                                                    ALM-45284 UserSync Garbage Collection (GC) Time Exceeds the Threshold

                                                                    -

                                                                    Description

                                                                    The system checks the GC duration of the UserSync process every 60 seconds. This alarm is generated when the GC duration of the UserSync process exceeds the threshold (12 seconds by default) for five consecutive times. This alarm is cleared when the GC duration is less than the threshold.

                                                                    +

                                                                    Description

                                                                    The system checks the GC duration of the UserSync process every 60 seconds. This alarm is generated when the GC duration of the UserSync process exceeds the threshold (12 seconds by default) for five consecutive times. This alarm is cleared when the GC duration is less than the threshold.

                                                                    Attributes

                                                                    Alarm ID

                                                                    @@ -61,16 +61,16 @@

                                                                    Impact on the System

                                                                    UserSync responds slowly.

                                                                    -

                                                                    Possible Causes

                                                                    The heap memory of the UserSync instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                                                    +

                                                                    Possible Causes

                                                                    The heap memory of the UserSync instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                                                    Procedure

                                                                    Check the GC time.

                                                                    -
                                                                    1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45284 UserSync Garbage Collection (GC) Time Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                    2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated and click the drop-down list in the upper right corner of the chart area. Choose Customize > GC > UserSync GC Duration. Click OK.
                                                                    3. Check whether the GC duration of the UserSync process collected every minute exceeds the threshold (12 seconds by default).

                                                                      • If yes, go to 4.
                                                                      • If no, go to 6.
                                                                      -

                                                                    4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                      If this alarm is generated, the heap memory configured for UserSync cannot meet the heap memory required by the UserSync process. You are advised to change the value of GC_OPTS to the twice that of the heap memory used by UserSync. You can change the value based on the actual service scenario. For details about how to check the UserSync heap memory usage, see 2.

                                                                      +
                                                                      1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45284 UserSync Garbage Collection (GC) Time Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                      2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated and click the drop-down list in the upper right corner of the chart area. Choose Customize > GC > UserSync GC Duration. Click OK.
                                                                      3. Check whether the GC duration of the UserSync process collected every minute exceeds the threshold (12 seconds by default).

                                                                        • If yes, go to 4.
                                                                        • If no, go to 6.
                                                                        +

                                                                      4. On MRS Manager, choose Cluster > Services > Ranger > Instance > UserSync > Instance Configuration. Click All Configurations, and choose UserSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                        If this alarm is generated, the heap memory configured for UserSync cannot meet the heap memory required by the UserSync process. You are advised to change the value of GC_OPTS to the twice that of the heap memory used by UserSync. You can change the value based on the actual service scenario. For details about how to check the UserSync heap memory usage, see 2.

                                                                      5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                        • If yes, no further action is required.
                                                                        • If no, go to 6.

                                                                      Collect the fault information.

                                                                      -
                                                                      1. On FusionInsight Manager, choose O&M > Log > Download.
                                                                      2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                      4. Contact O&M personnel and provide the collected logs.
                                                                      +
                                                                      1. On MRS Manager, choose O&M > Log > Download.
                                                                      2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                      3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                      4. Contact O&M personnel and provide the collected logs.

                                                                      Alarm Clearing

                                                                      After the fault that triggers the alarm is rectified, the alarm is automatically cleared.

                                                                      diff --git a/docs/mrs/umn/ALM-45285.html b/docs/mrs/umn/ALM-45285.html index b8355e01..2072d79f 100644 --- a/docs/mrs/umn/ALM-45285.html +++ b/docs/mrs/umn/ALM-45285.html @@ -63,13 +63,13 @@

                                                                      Possible Causes

                                                                      The heap memory usage of the TagSync instance is high or the heap memory is improperly allocated.

                                                                      -

                                                                      Procedure

                                                                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45285 TagSync Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                      2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > TagSync Heap Memory Usage. Click OK.
                                                                      3. Check whether the heap memory used by TagSync reaches the threshold (95% of the maximum heap memory by default).

                                                                        • If yes, go to 4.
                                                                        • If no, go to 6.
                                                                        -

                                                                      4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                        If this alarm is generated, the heap memory configured for TagSync cannot meet the heap memory required by the TagSync process. You are advised to change the -Xmx value of GC_OPTS to twice that of the heap memory used by TagSync. You can change the value based on the actual service scenario. For details about how to check the TagSync heap memory usage, see 2.

                                                                        +

                                                                        Procedure

                                                                        1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45285 TagSync Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                        2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > TagSync Heap Memory Usage. Click OK.
                                                                        3. Check whether the heap memory used by TagSync reaches the threshold (95% of the maximum heap memory by default).

                                                                          • If yes, go to 4.
                                                                          • If no, go to 6.
                                                                          +

                                                                        4. On MRS Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                          If this alarm is generated, the heap memory configured for TagSync cannot meet the heap memory required by the TagSync process. You are advised to change the -Xmx value of GC_OPTS to twice that of the heap memory used by TagSync. You can change the value based on the actual service scenario. For details about how to check the TagSync heap memory usage, see 2.

                                                                        5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                          • If yes, no further action is required.
                                                                          • If no, go to 6.

                                                                        Collect the fault information.

                                                                        -
                                                                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                        2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                        4. Contact O&M personnel and provide the collected logs.
                                                                        +
                                                                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                        2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                        3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                        4. Contact O&M personnel and provide the collected logs.

                                                                        Alarm Clearing

                                                                        This alarm is automatically cleared after the fault is rectified.

                                                                        diff --git a/docs/mrs/umn/ALM-45286.html b/docs/mrs/umn/ALM-45286.html index 7ea011ad..d6c9ca0f 100644 --- a/docs/mrs/umn/ALM-45286.html +++ b/docs/mrs/umn/ALM-45286.html @@ -61,16 +61,16 @@

                                                                        Impact on the System

                                                                        Direct memory overflow may cause service breakdown.

                                                                        -

                                                                        Possible Causes

                                                                        The direct memory of the TagSync instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.

                                                                        +

                                                                        Possible Causes

                                                                        The direct memory of the TagSync instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.

                                                                        Procedure

                                                                        Check the direct memory usage.

                                                                        -
                                                                        1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45286 TagSync Direct Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                        2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > TagSync Direct Memory Usage. Click OK.
                                                                        3. Check whether the direct memory used by the TagSync reaches the threshold (80% of the maximum direct memory by default).

                                                                          • If yes, go to 4.
                                                                          • If no, go to 6.
                                                                          -

                                                                        4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                          If this alarm is generated, the direct memory configured for TagSync cannot meet the direct memory required by the TagSync process. You are advised to check the direct memory usage of TagSync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by TagSync. You can change the value based on the actual service scenario. For details, see 2.

                                                                          +
                                                                          1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45286 TagSync Direct Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                          2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > TagSync Direct Memory Usage. Click OK.
                                                                          3. Check whether the direct memory used by the TagSync reaches the threshold (80% of the maximum direct memory by default).

                                                                            • If yes, go to 4.
                                                                            • If no, go to 6.
                                                                            +

                                                                          4. On MRS Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                            If this alarm is generated, the direct memory configured for TagSync cannot meet the direct memory required by the TagSync process. You are advised to check the direct memory usage of TagSync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by TagSync. You can change the value based on the actual service scenario. For details, see 2.

                                                                          5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                            • If yes, no further action is required.
                                                                            • If no, go to 6.

                                                                          Collect the fault information.

                                                                          -
                                                                          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                          2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                          4. Contact O&M personnel and provide the collected logs.
                                                                          +
                                                                          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                          2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                          3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                          4. Contact O&M personnel and provide the collected logs.

                                                                          Alarm Clearing

                                                                          This alarm is automatically cleared after the fault is rectified.

                                                                          diff --git a/docs/mrs/umn/ALM-45287.html b/docs/mrs/umn/ALM-45287.html index d795d6df..dbe55db4 100644 --- a/docs/mrs/umn/ALM-45287.html +++ b/docs/mrs/umn/ALM-45287.html @@ -64,13 +64,13 @@

                                                                          Possible Causes

                                                                          The non-heap memory of the TagSync process is overused or the non-heap memory is inappropriately allocated.

                                                                          Procedure

                                                                          Check non-heap memory usage.

                                                                          -
                                                                          1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45287 TagSync Non Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                          2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > TagSync Non Heap Memory Usage. Click OK.
                                                                          3. Check whether the non-heap memory used by TagSync reaches the threshold (80% of the maximum non-heap memory by default).

                                                                            • If yes, go to 4.
                                                                            • If no, go to 6.
                                                                            -

                                                                          4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                                                                            If this alarm is generated, the non-heap memory size configured for the TagSync instance cannot meet the non-heap memory required by the TagSync process. You are advised to change the -XX:MaxPermSize value of GC_OPTS to twice that of the current non-heap memory size or change the value based on the site requirements.

                                                                            +
                                                                            1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45287 TagSync Non Heap Memory Usage Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                            2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated. Click the drop-down list in the upper right corner of the chart area and choose Customize > CPU and Memory > TagSync Non Heap Memory Usage. Click OK.
                                                                            3. Check whether the non-heap memory used by TagSync reaches the threshold (80% of the maximum non-heap memory by default).

                                                                              • If yes, go to 4.
                                                                              • If no, go to 6.
                                                                              +

                                                                            4. On MRS Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.

                                                                              If this alarm is generated, the non-heap memory size configured for the TagSync instance cannot meet the non-heap memory required by the TagSync process. You are advised to change the -XX:MaxPermSize value of GC_OPTS to twice that of the current non-heap memory size or change the value based on the site requirements.

                                                                            5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                              • If yes, no further action is required.
                                                                              • If no, go to 6.

                                                                            Collect the fault information.

                                                                            -
                                                                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                            2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                            4. Contact O&M personnel and provide the collected logs.
                                                                            +
                                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                            2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                            4. Contact O&M personnel and provide the collected logs.

                                                                            Alarm Clearing

                                                                            This alarm is automatically cleared after the fault is rectified.

                                                                            diff --git a/docs/mrs/umn/ALM-45288.html b/docs/mrs/umn/ALM-45288.html index 61c79f46..cbca622f 100644 --- a/docs/mrs/umn/ALM-45288.html +++ b/docs/mrs/umn/ALM-45288.html @@ -1,7 +1,7 @@

                                                                            ALM-45288 TagSync Garbage Collection (GC) Time Exceeds the Threshold

                                                                            -

                                                                            Description

                                                                            The system checks the GC duration of the TagSync process every 60 seconds. This alarm is generated when the GC duration of the TagSync process exceeds the threshold (12 seconds by default) for five consecutive times. This alarm is cleared when the GC duration is less than the threshold.

                                                                            +

                                                                            Description

                                                                            The system checks the GC duration of the TagSync process every 60 seconds. This alarm is generated when the GC duration of the TagSync process exceeds the threshold (12 seconds by default) for five consecutive times. This alarm is cleared when the GC duration is less than the threshold.

                                                                            Attributes

                                                                            Alarm ID

                                                                            @@ -61,16 +61,16 @@

                                                                            Impact on the System

                                                                            TagSync responds slowly.

                                                                            -

                                                                            Possible Causes

                                                                            The heap memory of the TagSync instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                                                            +

                                                                            Possible Causes

                                                                            The heap memory of the TagSync instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.

                                                                            Procedure

                                                                            Check the GC duration.

                                                                            -
                                                                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45288 TagSync Garbage Collection (GC) Time Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                            2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated and click the drop-down list in the upper right corner of the chart area. Choose Customize > GC > TagSync GC Duration. Click OK.
                                                                            3. Check whether the GC duration of the TagSync process collected every minute exceeds the threshold (12 seconds by default).

                                                                              • If yes, go to 4.
                                                                              • If no, go to 6.
                                                                              -

                                                                            4. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                              If this alarm is generated, the heap memory configured for TagSync cannot meet the heap memory required by the TagSync process. You are advised to change the -Xmx value of GC_OPTS to twice that of the heap memory used by TagSync. You can change the value based on the actual service scenario. For details about how to check the TagSync heap memory usage, see 2.

                                                                              +
                                                                              1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45288 TagSync Garbage Collection (GC) Time Exceeds the Threshold. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
                                                                              2. On MRS Manager, choose Cluster > Services > Ranger > Instance. Select the role corresponding to the host name of the instance for which the alarm is generated and click the drop-down list in the upper right corner of the chart area. Choose Customize > GC > TagSync GC Duration. Click OK.
                                                                              3. Check whether the GC duration of the TagSync process collected every minute exceeds the threshold (12 seconds by default).

                                                                                • If yes, go to 4.
                                                                                • If no, go to 6.
                                                                                +

                                                                              4. On MRS Manager, choose Cluster > Services > Ranger > Instance > TagSync > Instance Configuration. Click All Configurations and choose TagSync > System. Increase the value of -Xmx in the GC_OPTS parameter based on the site requirements and save the configuration.

                                                                                If this alarm is generated, the heap memory configured for TagSync cannot meet the heap memory required by the TagSync process. You are advised to change the -Xmx value of GC_OPTS to twice that of the heap memory used by TagSync. You can change the value based on the actual service scenario. For details about how to check the TagSync heap memory usage, see 2.

                                                                              5. Restart the affected services or instances and check whether the alarm is cleared.

                                                                                • If yes, no further action is required.
                                                                                • If no, go to 6.

                                                                              Collect the fault information.

                                                                              -
                                                                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                              2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                              4. Contact O&M personnel and provide the collected logs.
                                                                              +
                                                                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                              2. Expand the Service drop-down list, and select Ranger for the target cluster.
                                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                              4. Contact O&M personnel and provide the collected logs.

                                                                              Alarm Clearing

                                                                              This alarm is automatically cleared after the fault is rectified.

                                                                              diff --git a/docs/mrs/umn/ALM-45425.html b/docs/mrs/umn/ALM-45425.html index 9a022780..67c8c584 100644 --- a/docs/mrs/umn/ALM-45425.html +++ b/docs/mrs/umn/ALM-45425.html @@ -55,12 +55,12 @@
                                                                            -

                                                                            Impact on the System

                                                                            The ClickHouse service is abnormal. You cannot use FusionInsight Manager to perform cluster operations on the ClickHouse service. The ClickHouse service function is unavailable.

                                                                            +

                                                                            Impact on the System

                                                                            The ClickHouse service is abnormal. You cannot use MRS Manager to perform cluster operations on the ClickHouse service. The ClickHouse service function is unavailable.

                                                                            Possible Causes

                                                                            The configuration information in the metrika.xml file in the component configuration directory of the faulty ClickHouse instance node is inconsistent with that of the corresponding ClickHouse instance in the ZooKeeper.

                                                                            Procedure

                                                                            Check whether the configuration in metrika.xml of the ClickHouse instance is correct.

                                                                            -
                                                                            1. Log in to FusionInsight Manager, choose Cluster > Services > ClickHouse > Instance, and locate the abnormal ClickHouse instance based on the alarm information.

                                                                              • If yes, go to 2.
                                                                              • If no, go to 9.
                                                                              +
                                                                              1. Log in to MRS Manager, choose Cluster > Services > ClickHouse > Instance, and locate the abnormal ClickHouse instance based on the alarm information.

                                                                                • If yes, go to 2.
                                                                                • If no, go to 9.

                                                                              2. Log in to the host where the ClickHouse service is abnormal and ping the IP address of another normal ClickHouse instance node to check whether the network connection is normal.

                                                                                • If yes, go to 3.
                                                                                • If no, contact the network administrator to repair the network.

                                                                              1. Choose Cluster > Services > ClickHouse > Instance, click the abnormal instance name in the Role column, click Configurations, search for macros.id in the search box, and find the value of macros.id of the current instance.
                                                                              2. Log in to the host where the ZooKeeper client is located and log in to the ZooKeeper client.

                                                                                Switch to the client installation directory.

                                                                                Example: cd /opt/client

                                                                                @@ -75,10 +75,10 @@

                                                                              1. Log in to the host where the ClickHouse instance is abnormal and go to the configuration directory of the ClickHouse instance.

                                                                                cd ${BIGDATA_HOME}/FusionInsight_ClickHouse_Version/x_x_ClickHouseServer/etc

                                                                                cat metrika.xml

                                                                              2. Check whether the cluster topology information on ZooKeeper obtained in 5 is the same as that in the metrika.xml file in the component configuration directory in 6.

                                                                                • If yes, check whether the alarm is cleared. If the alarm persists, go to 9.
                                                                                • If no, go to 8.
                                                                                -

                                                                              3. On FusionInsight Manager, choose Cluster > Services > ClickHouse, click More, and select Synchronize Configuration. Then, check whether the service status is normal and whether the alarm is cleared 5 minutes later.

                                                                                • If yes, no further action is required.
                                                                                • If no, go to 9.
                                                                                +

                                                                              4. On MRS Manager, choose Cluster > Services > ClickHouse, click More, and select Synchronize Configuration. Then, check whether the service status is normal and whether the alarm is cleared 5 minutes later.

                                                                                • If yes, no further action is required.
                                                                                • If no, go to 9.

                                                                              Collect the fault information.

                                                                              -
                                                                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                              2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                                              3. Choose the corresponding host form the host list.
                                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                              5. Contact O&M personnel and provide the collected logs.
                                                                              +
                                                                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                              2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                                              3. Choose the corresponding host form the host list.
                                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                              5. Contact O&M personnel and provide the collected logs.

                                                                            Alarm Clearing

                                                                            This alarm is automatically cleared after the fault is rectified.

                                                                            diff --git a/docs/mrs/umn/ALM-45426.html b/docs/mrs/umn/ALM-45426.html index 2bc11157..8a2398df 100644 --- a/docs/mrs/umn/ALM-45426.html +++ b/docs/mrs/umn/ALM-45426.html @@ -55,7 +55,7 @@
                                                                    -

                                                                    Impact on the System

                                                                    After the ZooKeeper quantity quota of the ClickHouse service exceeds the threshold, you cannot perform cluster operations on the ClickHouse service on FusionInsight Manager. As a result, the ClickHouse service cannot be used.

                                                                    +

                                                                    Impact on the System

                                                                    After the ZooKeeper quantity quota of the ClickHouse service exceeds the threshold, you cannot perform cluster operations on the ClickHouse service on MRS Manager. As a result, the ClickHouse service cannot be used.

                                                                    Possible Causes

                                                                    • When table data is created, inserted, or deleted, the ClickHouse creates znodes on ZooKeeper nodes. As the service volume increases, the number of znodes may exceed the configured threshold.
                                                                    • No quota limit is set for the metadata directory /clickhouse of ClickHouse in ZooKeeper.
                                                                    @@ -72,18 +72,18 @@ Quota for path /clickhouse does not exist.

                                                                    If the preceding information indicates that the quota configuration is incorrect, go to 3.

                                                                    -

                                                                    If no, go to 5.

                                                                    -

                                                                  5. Log in to FusionInsight Manager and choose Cluster > Services > ZooKeeper. On the displayed page, click Configurations and click All Configurations. On this sub-tab page, search for quotas.auto.check.enable to check whether its value is true.

                                                                    If the value is not true, change the value to true and click Save.

                                                                    -

                                                                  6. On FusionInsight Manager, choose Cluster > Services > ClickHouse, click More, and select Synchronize Configuration. After the synchronization is successful, go to 1.
                                                                  7. Run the following command and check whether the ratio of the count value of Output stat to the count value of Output quota in the command output is greater than 0.9:

                                                                    listquota /clickhouse
                                                                    absolute path is /zookeeper/quota/clickhouse
+
                                                                    If no, go to 5.
                                                                    
+
                                                                  8. Log in to MRS Manager and choose Cluster > Services > ZooKeeper. On the displayed page, click Configurations and click All Configurations. On this sub-tab page, search for quotas.auto.check.enable to check whether its value is true.

                                                                    If the value is not true, change the value to true and click Save.

                                                                    +

                                                                  9. On MRS Manager, choose Cluster > Services > ClickHouse, click More, and select Synchronize Configuration. After the synchronization is successful, go to 1.
                                                                  10. Run the following command and check whether the ratio of the count value of Output stat to the count value of Output quota in the command output is greater than 0.9:

                                                                    listquota /clickhouse
                                                                    absolute path is /zookeeper/quota/clickhouse
 Output quota for /clickhouse count=200000,bytes=1000000000
 Output stat for /clickhouse count=2667,bytes=60063
                                                                    In the preceding information, the count value of Output stat is 2667, and the count value of Output quota is 200000.
                                                                    • If yes, go to 6.
                                                                    • If no, check whether the alarm is cleared 5 minutes later. If the alarm persists, go to 8.
                                                                    -

                                                                  11. On FusionInsight Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, search for the clickhouse.zookeeper.quota.node.count parameter, and change the value of this parameter to twice the count value of Output stat in 5.
                                                                  12. Restart the ClickHouse instance for which the alarm is generated, and check whether the alarm is cleared 5 minutes later.

                                                                    • If yes, no further action is required.
                                                                    • If no, perform 6 again, and check whether the alarm is cleared 5 minutes later. If the alarm persists, go to 8.
                                                                    +

                                                                  13. On MRS Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, search for the clickhouse.zookeeper.quota.node.count parameter, and change the value of this parameter to twice the count value of Output stat in 5.
                                                                  14. Restart the ClickHouse instance for which the alarm is generated, and check whether the alarm is cleared 5 minutes later.

                                                                    • If yes, no further action is required.
                                                                    • If no, perform 6 again, and check whether the alarm is cleared 5 minutes later. If the alarm persists, go to 8.

                                                                  Collect the fault information.

                                                                  -
                                                                  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                  2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                                  3. Choose the corresponding host form the host list.
                                                                  4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                  5. Contact O&M personnel and provide the collected logs.
                                                                  +
                                                                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                  2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                                  3. Choose the corresponding host form the host list.
                                                                  4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                  5. Contact O&M personnel and provide the collected logs.

                                                                  Alarm Clearing

                                                                  This alarm is automatically cleared after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-45427.html b/docs/mrs/umn/ALM-45427.html index 838ff211..3fb1cd78 100644 --- a/docs/mrs/umn/ALM-45427.html +++ b/docs/mrs/umn/ALM-45427.html @@ -55,7 +55,7 @@
                                                            -

                                                            Impact on the System

                                                            After the ZooKeeper quantity quota of the ClickHouse service exceeds the threshold, you cannot perform cluster operations on the ClickHouse service on FusionInsight Manager. As a result, the ClickHouse service cannot be used.

                                                            +

                                                            Impact on the System

                                                            After the ZooKeeper quantity quota of the ClickHouse service exceeds the threshold, you cannot perform cluster operations on the ClickHouse service on MRS Manager. As a result, the ClickHouse service cannot be used.

                                                            Possible Causes

                                                            • When table data is created, inserted, or deleted, the ClickHouse creates znodes on ZooKeeper nodes. As the service volume increases, the capacity of znodes may exceed the configured threshold.
                                                            • No quota limit is set for the metadata directory /clickhouse of ClickHouse in ZooKeeper.
                                                            @@ -71,18 +71,18 @@

                                                          5. Run the following command to check the quota used by the ClickHouse in the ZooKeeper and check whether the quota information is correctly set:

                                                            listquota /clickhouse
                                                            absolute path is /zookeeper/quota/clickhouse
 Quota for path /clickhouse does not exist.
                                                            -
                                                            • If the preceding information indicates that the quota configuration is incorrect, go to 3.
                                                            • If not, go to 5.
                                                            -

                                                          6. Log in to FusionInsight Manager and choose Cluster > Services > ZooKeeper. On the displayed page, click Configurations and click All Configurations. On this sub-tab page, search for quotas.auto.check.enable to check whether its value is true.

                                                            If the value is not true, change the value to true and click Save.

                                                            -

                                                          7. On FusionInsight Manager, choose Cluster > Services > ClickHouse, click More, and select Synchronize Configuration. After the synchronization is successful, go to 1.
                                                          8. Run the following command and check whether the ratio of the bytes value of Output stat to the bytes value of Output quota in the command output is greater than 0.9:

                                                            listquota /clickhouse
                                                            absolute path is /zookeeper/quota/clickhouse
+
                                                            • If the preceding information indicates that the quota configuration is incorrect, go to 3.
                                                            • If not, go to 5.
                                                            
+
                                                          9. Log in to MRS Manager and choose Cluster > Services > ZooKeeper. On the displayed page, click Configurations and click All Configurations. On this sub-tab page, search for quotas.auto.check.enable to check whether its value is true.

                                                            If the value is not true, change the value to true and click Save.

                                                            +

                                                          10. On MRS Manager, choose Cluster > Services > ClickHouse, click More, and select Synchronize Configuration. After the synchronization is successful, go to 1.
                                                          11. Run the following command and check whether the ratio of the bytes value of Output stat to the bytes value of Output quota in the command output is greater than 0.9:

                                                            listquota /clickhouse
                                                            absolute path is /zookeeper/quota/clickhouse
 Output quota for /clickhouse count=200000,bytes=1000000000
 Output stat for /clickhouse count=2667,bytes=60063
                                                            In the preceding information, the bytes value of Output stat is 60063, and the bytes value of Output quota is 1000000000.
                                                            • If yes, go to 6.
                                                            • If no, check whether the alarm is cleared 5 minutes later. If the alarm persists, go to 8.
                                                            -

                                                          12. On FusionInsight Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, search for the clickhouse.zookeeper.quota.size parameter, and change the value of this parameter to twice the bytes value of Output stat in 5.
                                                          13. Restart the ClickHouse instance for which the alarm is generated, and check whether the alarm is cleared 5 minutes later.

                                                            • If yes, no further action is required.
                                                            • If no, perform 6 again, and check whether the alarm is cleared 5 minutes later. If the alarm persists, go to 8.
                                                            +

                                                          14. On MRS Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, search for the clickhouse.zookeeper.quota.size parameter, and change the value of this parameter to twice the bytes value of Output stat in 5.
                                                          15. Restart the ClickHouse instance for which the alarm is generated, and check whether the alarm is cleared 5 minutes later.

                                                            • If yes, no further action is required.
                                                            • If no, perform 6 again, and check whether the alarm is cleared 5 minutes later. If the alarm persists, go to 8.

                                                          Collect the fault information.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                          2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                          3. Choose the corresponding host form the host list.
                                                          4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          5. Contact O&M personnel and provide the collected logs.
                                                          +
                                                          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                          2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                          3. Choose the corresponding host form the host list.
                                                          4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                          5. Contact O&M personnel and provide the collected logs.

                                                          Alarm Clearing

                                                          This alarm is automatically cleared after the fault is rectified.

                                                          diff --git a/docs/mrs/umn/ALM-45428.html b/docs/mrs/umn/ALM-45428.html index 84592819..c4dda63c 100644 --- a/docs/mrs/umn/ALM-45428.html +++ b/docs/mrs/umn/ALM-45428.html @@ -58,13 +58,13 @@

                                                          Possible Causes

                                                          The disk is aged or has bad sectors.

                                                          -

                                                          Procedure

                                                          1. On FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45428 ClickHouse Disk I/O Exception. Check the role name and the IP address of the host where the alarm is generated in Location.
                                                          2. Use PuTTY to log in to the node for which the fault is generated as user root.
                                                          3. Run the df -h command to check the mount directory and find the disk mounted to the faulty directory.
                                                          4. Run the smartctl -a /dev/sd* command to check disks.

                                                            • If SMART Health Status: OK is displayed, as shown in the following figure, the disk is healthy. In this case, go to 6.

                                                              +

                                                              Procedure

                                                              1. On MRS Manager, choose O&M > Alarm > Alarms > ALM-45428 ClickHouse Disk I/O Exception. Check the role name and the IP address of the host where the alarm is generated in Location.
                                                              2. Use PuTTY to log in to the node for which the fault is generated as user root.
                                                              3. Run the df -h command to check the mount directory and find the disk mounted to the faulty directory.
                                                              4. Run the smartctl -a /dev/sd* command to check disks.

                                                                • If SMART Health Status: OK is displayed, as shown in the following figure, the disk is healthy. In this case, go to 6.

                                                                • If the number following Elements in grown defect list is not 0, as shown in the following figure, the disk may have bad sectors. If SMART Health Status: FAILURE is displayed, the disk is in the sub-health state. In this case, contact O&M personnel.

                                                                -

                                                              5. After the fault is rectified, manually clear the alarm on FusionInsight Manager and check whether the alarm is generated again during the periodic check.

                                                                • If yes, go to 6.
                                                                • If no, no further action is required.
                                                                +

                                                              6. After the fault is rectified, manually clear the alarm on MRS Manager and check whether the alarm is generated again during the periodic check.

                                                                • If yes, go to 6.
                                                                • If no, no further action is required.

                                                              Collect the fault information.

                                                              -
                                                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                              3. Choose the corresponding host form the host list.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                              3. Choose the corresponding host form the host list.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.

                                                              Alarm Clearing

                                                              If the alarm has no impact, manually clear the alarm.

                                                              diff --git a/docs/mrs/umn/ALM-45429.html b/docs/mrs/umn/ALM-45429.html index c709c074..85a66aef 100644 --- a/docs/mrs/umn/ALM-45429.html +++ b/docs/mrs/umn/ALM-45429.html @@ -60,16 +60,16 @@

                                                          Possible Causes

                                                          A node is stopped or faulty during capacity expansion.

                                                          -

                                                          Procedure

                                                          1. On FusionInsight Manager, choose Cluster > Services > ClickHouse > Instance.
                                                          2. Check whether an instance is stopped, decommissioned, or faulty.

                                                            • If yes, go to 3.
                                                            • If no, go to 4.
                                                            -

                                                          3. Start the instance or rectify the instance fault until all instances are running properly.
                                                          4. On FusionInsight Manager, choose O&M > Alarm > Alarms, locate this alarm and the faulty host based on the location information.
                                                          1. Log in to the faulty host as user omm.
                                                          2. Run the following commands to initialize environment variables:

                                                            source Cluster installation directory/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/ENV_VARS

                                                            +

                                                            Procedure

                                                            1. On MRS Manager, choose Cluster > Services > ClickHouse > Instance.
                                                            2. Check whether an instance is stopped, decommissioned, or faulty.

                                                              • If yes, go to 3.
                                                              • If no, go to 4.
                                                              +

                                                            3. Start the instance or rectify the instance fault until all instances are running properly.
                                                            4. On MRS Manager, choose O&M > Alarm > Alarms, locate this alarm and the faulty host based on the location information.
                                                            1. Log in to the faulty host as user omm.
                                                            2. Run the following commands to initialize environment variables:

                                                              source Cluster installation directory/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/ENV_VARS

                                                              source Cluster installation directory/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/clickhouse-env.sh

                                                              export CLICKHOUSE_CONF_DIR=${CLICKHOUSE_CONF_DIR}

                                                            3. Run the following command to run the metadata synchronization tool to synchronize metadata from the existing node to the faulty node:

                                                              sh Cluster installation directory/FusionInsight_ClickHouse_*/install/FusionInsight-ClickHouse-*/clickhouse/sbin/clickhouse-create-meta.sh true

                                                            4. Run the following command to view the log information and check whether the metadata has been synchronized:

                                                              vim /var/log/Bigdata/clickhouse/clickhouseServer/start.log
                                                              • If the synchronization is complete, go to 9.
                                                              • If the synchronization fails, go to 10.
                                                              -

                                                            5. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the Alarm ID column, locate the corresponding alarm and click Clear in the Operation column. In the displayed dialog box, click OK to manually clear the alarm.
                                                            +

                                                          3. On MRS Manager, choose O&M > Alarm > Alarms. In the Alarm ID column, locate the corresponding alarm and click Clear in the Operation column. In the displayed dialog box, click OK to manually clear the alarm.

                                                          Collect the fault information.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                          2. Expand the Service drop-down list, select ClickHouse for the target cluster, and click OK.
                                                          3. Choose the corresponding host form the host list.
                                                          4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                          5. Contact O&M personnel and provide the collected logs.
                                                          +
                                                          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                          2. Expand the Service drop-down list, select ClickHouse for the target cluster, and click OK.
                                                          3. Choose the corresponding host form the host list.
                                                          4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                          5. Contact O&M personnel and provide the collected logs.

                                                          Alarm Clearing

                                                          This alarm needs to be manually cleared after the fault is rectified.

                                                          diff --git a/docs/mrs/umn/ALM-45430.html b/docs/mrs/umn/ALM-45430.html index 82d6f809..2d2084c5 100644 --- a/docs/mrs/umn/ALM-45430.html +++ b/docs/mrs/umn/ALM-45430.html @@ -60,17 +60,17 @@

                                                        Possible Causes

                                                        A node is stopped or faulty during capacity expansion.

                                                        -

                                                        Procedure

                                                        1. On FusionInsight Manager, choose Cluster > Services > ClickHouse > Instance.
                                                        2. Check whether an instance is stopped, decommissioned, or faulty.

                                                          • If yes, go to 3.
                                                          • If no, go to 4.
                                                          -

                                                        3. Start the instance or rectify the instance fault until all instances are running properly.
                                                        4. On FusionInsight Manager, choose O&M > Alarm > Alarms, locate this alarm and the faulty host based on the location information.
                                                        1. Log in to the faulty host as user omm.
                                                        2. Run the following commands to initialize environment variables:

                                                          source Cluster installation directory/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/ENV_VARS

                                                          +

                                                          Procedure

                                                          1. On MRS Manager, choose Cluster > Services > ClickHouse > Instance.
                                                          2. Check whether an instance is stopped, decommissioned, or faulty.

                                                            • If yes, go to 3.
                                                            • If no, go to 4.
                                                            +

                                                          3. Start the instance or rectify the instance fault until all instances are running properly.
                                                          4. On MRS Manager, choose O&M > Alarm > Alarms, locate this alarm and the faulty host based on the location information.
                                                          1. Log in to the faulty host as user omm.
                                                          2. Run the following commands to initialize environment variables:

                                                            source Cluster installation directory/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/ENV_VARS

                                                            source Cluster installation directory/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/clickhouse-env.sh

                                                            export CLICKHOUSE_CONF_DIR=${CLICKHOUSE_CONF_DIR}

                                                          3. Run the following command to run the metadata synchronization tool to synchronize metadata from the existing node to the faulty node:

                                                            sh Cluster installation directory/FusionInsight_ClickHouse_*/install/FusionInsight-ClickHouse-*/clickhouse/sbin/clickhouse-create-meta.sh true

                                                          4. Run the following command to view the log information and check whether the metadata has been synchronized:

                                                            vim /var/log/Bigdata/clickhouse/clickhouseServer/start.log

                                                            If the synchronization is complete, go to 9.

                                                            If the synchronization fails, go to 10.

                                                            -

                                                          5. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the Alarm ID column, locate the corresponding alarm and click Clear in the Operation column. In the displayed dialog box, click OK to manually clear the alarm.
                                                          +

                                                        3. On MRS Manager, choose O&M > Alarm > Alarms. In the Alarm ID column, locate the corresponding alarm and click Clear in the Operation column. In the displayed dialog box, click OK to manually clear the alarm.

                                                        Collect the fault information.

                                                        -
                                                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                        2. Expand the Service drop-down list, select ClickHouse for the target cluster, and click OK.
                                                        3. Choose the corresponding host form the host list.
                                                        4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                        5. Contact O&M personnel and provide the collected logs.
                                                        +
                                                        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                        2. Expand the Service drop-down list, select ClickHouse for the target cluster, and click OK.
                                                        3. Choose the corresponding host form the host list.
                                                        4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                        5. Contact O&M personnel and provide the collected logs.

                                                        Alarm Clearing

                                                        This alarm needs to be manually cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-45431.html b/docs/mrs/umn/ALM-45431.html index b493b6ff..6a9b72c1 100644 --- a/docs/mrs/umn/ALM-45431.html +++ b/docs/mrs/umn/ALM-45431.html @@ -58,7 +58,7 @@

                                                        Possible Causes

                                                        During installation or capacity expansion, the number of instances or allocation mode does not meet the topology requirements.

                                                        -

                                                        Procedure

                                                        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms, locate the row that contains the alarm, and analyze the cause based on Location and Additional Information.
                                                        2. Handle the alarm based on the additional alarm information and handling method in the following table.

                                                          +

                                                          Procedure

                                                          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Alarm > Alarms, locate the row that contains the alarm, and analyze the cause based on Location and Additional Information.
                                                          2. Handle the alarm based on the additional alarm information and handling method in the following table.

                                                            - - diff --git a/docs/mrs/umn/ALM-45432.html b/docs/mrs/umn/ALM-45432.html index 47f56d43..74ddc730 100644 --- a/docs/mrs/umn/ALM-45432.html +++ b/docs/mrs/umn/ALM-45432.html @@ -60,7 +60,7 @@

                                                            Possible Causes

                                                            • The ClickHouse user role synchronization process is not started properly or exits abnormally.
                                                            • The ClickHouse user role synchronization process fails to synchronize user role information because the LdapServer service is faulty.

                                                            Procedure

                                                            Check whether the ClickHouse user role synchronization process is normal.

                                                            -
                                                            1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. On the page that is displayed, search for ALM-45432 ClickHouse User Synchronization Process Fails.
                                                            2. Check the host name and additional information in the alarm details.

                                                              • If the additional information is "Process clickhouse-ugsync is not exit.", go to 3.
                                                              • If the additional information is "Process clickhouse-ugsync sync user failed.", go to 6.
                                                              +
                                                              1. Log in to MRS Manager and choose O&M > Alarm > Alarms. On the page that is displayed, search for ALM-45432 ClickHouse User Synchronization Process Fails.
                                                              2. Check the host name and additional information in the alarm details.

                                                                • If the additional information is "Process clickhouse-ugsync is not exit.", go to 3.
                                                                • If the additional information is "Process clickhouse-ugsync sync user failed.", go to 6.

                                                              3. Log in to the faulty host as user omm and run the following command to check whether the ClickHouse user role synchronization process is normal:

                                                                ps -ef | grep 'clickhouse-ugsync'

                                                                Abnormal result of the synchronization process:

                                                                [omm@server-2110081635-0001 ~]$ ps -ef | grep 'clickhouse-ugsync'
@@ -70,15 +70,15 @@ omm      20104 13146  0 15:57 pts/7    00:00:00 Normal setting of the crontab daemon task:
                                                                
 
                                                                */5 * * * * bash /xxxxx/clickhouse_ugsync_check.sh >/dev/null 2>&1
                                                                
 
                                                                • If yes, check whether the alarm is cleared 5 minutes later. If the alarm is cleared, no further action is required. If the alarm persists, go to 8.
                                                                • If no, go to 5.
                                                                
-
                                                              4. Log in to FusionInsight Manager, choose Cluster > Services > ClickHouse. On the page that is displayed, click the Instance tab. On this tab page, find the abnormal ClickHouseServer instance based on the fault information, and restart it. Wait for 5 minutes and check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 6.
                                                                +

                                                              5. Log in to MRS Manager, choose Cluster > Services > ClickHouse. On the page that is displayed, click the Instance tab. On this tab page, find the abnormal ClickHouseServer instance based on the fault information, and restart it. Wait for 5 minutes and check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 6.

                                                              Check whether the LdapServer service is normal.

                                                              -
                                                              1. Log in to FusionInsight Manager, choose Cluster > Services, and check whether Running Status of LdapServer is Normal.

                                                                • If yes, go to 8.
                                                                • If no, go to 7.
                                                                +
                                                                1. Log in to MRS Manager, choose Cluster > Services, and check whether Running Status of LdapServer is Normal.

                                                                  • If yes, go to 8.
                                                                  • If no, go to 7.

                                                                2. Handle the LdapServer service unavailable alarm according to ALM-25000 LdapServer Service Unavailable.

                                                                  After Running Status of LdapServer becomes Normal, check whether this alarm is cleared.
                                                                  • If yes, no further action is required.
                                                                  • If no, go to 8.

                                                                Collect fault information.

                                                                -
                                                                1. On FusionInsight Manager, choose O&M > Log > Download.
                                                                2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select ClickHouseServer for the target cluster.
                                                                3. Expand the Hosts list. In the Select Host dialog box that is displayed, select the abnormal host, and click OK.
                                                                4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                5. Contact O&M personnel and provide the collected logs.
                                                                +
                                                                1. On MRS Manager, choose O&M > Log > Download.
                                                                2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select ClickHouseServer for the target cluster.
                                                                3. Expand the Hosts list. In the Select Host dialog box that is displayed, select the abnormal host, and click OK.
                                                                4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                                5. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45433.html b/docs/mrs/umn/ALM-45433.html index 204461a0..aca79759 100644 --- a/docs/mrs/umn/ALM-45433.html +++ b/docs/mrs/umn/ALM-45433.html @@ -83,10 +83,10 @@ </shard> </mcluster> </topo> -

                                                          3. Select a host from the desired shard and deploy the host in another AZ.
                                                          4. Log in to FusionInsight Manager, click Host, select the host you have deployed in 6 and choose More > Reinstall to reinstall the host.
                                                          5. Choose Cluster > Cross-AZ HA, click Configure AZ and Policy and change the AZ information of the reinstalled host to the AZ planned in the 6.
                                                          6. Wait for five minutes and check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 10.
                                                            +

                                                          7. Select a host from the desired shard and deploy the host in another AZ.
                                                          8. Log in to MRS Manager, click Host, select the host you have deployed in 6 and choose More > Reinstall to reinstall the host.
                                                          9. Choose Cluster > Cross-AZ HA, click Configure AZ and Policy and change the AZ information of the reinstalled host to the AZ planned in the 6.
                                                          10. Wait for five minutes and check whether the alarm is cleared.

                                                            • If yes, no further action is required.
                                                            • If no, go to 10.

                                                            11. Collect fault information.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M > Log > Download.
                                                            2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select ClickHouseServer for the target cluster.
                                                            3. Expand the Hosts list. In the Select Host dialog box that is displayed, select the abnormal host, and click OK.
                                                            4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            5. Contact O&M personnel and provide the collected logs.
                                                            +
                                                            1. On MRS Manager, choose O&M > Log > Download.
                                                            2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select ClickHouseServer for the target cluster.
                                                            3. Expand the Hosts list. In the Select Host dialog box that is displayed, select the abnormal host, and click OK.
                                                            4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            5. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45434.html b/docs/mrs/umn/ALM-45434.html index e070eaf8..6cc94c45 100644 --- a/docs/mrs/umn/ALM-45434.html +++ b/docs/mrs/umn/ALM-45434.html @@ -60,7 +60,7 @@

                                                            Possible Causes

                                                            The metrika.xml file in the ClickHouse configuration directory contains single-replica configuration.

                                                            Procedure

                                                            Check whether the configuration in metrika.xml of the ClickHouse instance is correct.

                                                            -
                                                            1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated. On the Hosts page, view the host IP address based on the host name.
                                                            2. Log in to the host where the ClickHouse instance is abnormal, go to the configuration directory of the ClickHouse instance, and run the following commands:

                                                              cd ${BIGDATA_HOME}/FusionInsight_ClickHouse_Version/x_x_ClickHouseServer/etc

                                                              +
                                                              1. In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated. On the Hosts page, view the host IP address based on the host name.
                                                              2. Log in to the host where the ClickHouse instance is abnormal, go to the configuration directory of the ClickHouse instance, and run the following commands:

                                                                cd ${BIGDATA_HOME}/FusionInsight_ClickHouse_Version/x_x_ClickHouseServer/etc

                                                                cat metrika.xml

                                                              3. View the number of shards in each custom logical cluster and check that a single replica exists. Then, go to 4.

                                                                If a shard contains only one node, a single replica exists in a logical cluster, as shown in the following:

                                                                <shard>
@@ -75,7 +75,7 @@

                                                              Collect fault information.

                                                              -
                                                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the abnormal host, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, and select ClickHouse for the target cluster.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the abnormal host, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45585.html b/docs/mrs/umn/ALM-45585.html index 6e5b1aa7..4c24a4cb 100644 --- a/docs/mrs/umn/ALM-45585.html +++ b/docs/mrs/umn/ALM-45585.html @@ -59,14 +59,14 @@

                                                            Possible Causes

                                                            • The KrbServer service is abnormal.
                                                            • More than 50% of IoTDBServer instances are faulty.

                                                            Procedure

                                                            Check whether the KrbServer service on which the IoTDB depends is abnormal.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                                            2. In the alarm list, check whether ALM-25500 KrbServer Service Unavailable exists.

                                                              • If yes, go to 3.
                                                              • If no, go to 5.
                                                              +
                                                              1. On MRS Manager, choose O&M > Alarm > Alarms.
                                                              2. In the alarm list, check whether ALM-25500 KrbServer Service Unavailable exists.

                                                                • If yes, go to 3.
                                                                • If no, go to 5.

                                                              3. Handle the alarm by referring to "ALM-25500 KrbServer Service Unavailable."
                                                              4. After ALM-25500 is cleared, wait a few minutes and check whether the alarm HetuServer Service Unavailable is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 5.

                                                              Check whether IoTDBServer instances are faulty.

                                                              -
                                                              1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > IoTDB > Instance.
                                                              2. Check whether the percentage of faulty IoTDBServer instances exceeds 50%. If yes, restart the faulty IoTDBServer instances and check whether the status is restored.

                                                                • If yes, no further action is required.
                                                                • If no, go to 7.
                                                                +
                                                                1. On MRS Manager, choose Cluster > Name of the desired cluster > Service > IoTDB > Instance.
                                                                2. Check whether the percentage of faulty IoTDBServer instances exceeds 50%. If yes, restart the faulty IoTDBServer instances and check whether the status is restored.

                                                                  • If yes, no further action is required.
                                                                  • If no, go to 7.

                                                                Collect the fault information.

                                                                -
                                                                1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                                4. Contact O&M personnel and provide the collected logs.
                                                                +
                                                                1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                                3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                                4. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45586.html b/docs/mrs/umn/ALM-45586.html index 41644f39..0e21d404 100644 --- a/docs/mrs/umn/ALM-45586.html +++ b/docs/mrs/umn/ALM-45586.html @@ -59,13 +59,13 @@

                                                            Possible Causes

                                                            The heap memory of the IoTDBServer process is overused or the heap memory is inappropriately allocated.

                                                            Procedure

                                                            Check the heap memory usage.

                                                            -
                                                            1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 45586, view the role name in Location, and check the instance IP address.
                                                            2. Choose Cluster > Name of the desired cluster > Service > IoTDB > Instance. Click the IoTDBServer for which the alarm is generated to go to Dashboard. Click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select IoTDBServer Heap Memory Resource Percentage, and click OK. Check whether the used non-heap memory of the IoTDBServer process reaches 90% (by default) of the maximum non-heap memory specified for IoTDBServer.

                                                              • If yes, go to 3.
                                                              • If no, go to 5.
                                                              +
                                                              1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 45586, view the role name in Location, and check the instance IP address.
                                                              2. Choose Cluster > Name of the desired cluster > Service > IoTDB > Instance. Click the IoTDBServer for which the alarm is generated to go to Dashboard. Click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select IoTDBServer Heap Memory Resource Percentage, and click OK. Check whether the used non-heap memory of the IoTDBServer process reaches 90% (by default) of the maximum non-heap memory specified for IoTDBServer.

                                                                • If yes, go to 3.
                                                                • If no, go to 5.

                                                              3. Choose Cluster > Name of the desired cluster > Service > IoTDB > Configuration, click All Configurations, choose IoTDBServer > System, and increase the value of -Xmx in the GC_OPTS parameter.

                                                                • The default value of -Xmx is 2G.
                                                                • If this alarm is occasionally generated, increase the value by 0.5 times. If this alarm is frequently generated, double the value.
                                                                • In the case of large service volume and high service concurrency, you are advised to add instances.

                                                              4. Check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 5.

                                                              Collect the fault information.

                                                              -
                                                              1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              4. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                              2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              4. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45587.html b/docs/mrs/umn/ALM-45587.html index 83297213..e3bc4837 100644 --- a/docs/mrs/umn/ALM-45587.html +++ b/docs/mrs/umn/ALM-45587.html @@ -1,7 +1,7 @@

                                                            ALM-45587 IoTDBServer GC Duration Exceeds the Threshold

                                                            -

                                                            Description

                                                            The system checks the GC duration of the IoTDBServer process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seconds by default) for three consecutive times. You can choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > IoTDB > GC > Total GC duration of IoTDBServer process (IoTDBServer) to change the threshold. This alarm is cleared when the GC duration is less than the threshold.

                                                            +

                                                            Description

                                                            The system checks the GC duration of the IoTDBServer process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seconds by default) for three consecutive times. You can choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > IoTDB > GC > Total GC duration of IoTDBServer process (IoTDBServer) to change the threshold. This alarm is cleared when the GC duration is less than the threshold.

                                                            Attribute

                                                            Additional Information

                                                            Remarks

                                                            @@ -71,14 +71,14 @@

                                                            This alarm is generated when a single cluster is deployed in cross-AZ DR mode. The ClickHouseServer instance deployment does not meet the cross-AZ DR topology allocation requirements. As a result, some instances cannot work properly.

                                                            1. On FusionInsight Manager, choose Cluster > Services > ClickHouse, click the Instance tab, locate the row that contains the alarm, view the host name in Location, and find the AZ for which the alarm is generated in the AZ column based on the host name.
                                                            2. On the Instance page, click Add Instance to add n ClickHouseServer instances to other AZs except the AZ where the alarm is generated.
                                                            +
                                                            1. On MRS Manager, choose Cluster > Services > ClickHouse, click the Instance tab, locate the row that contains the alarm, view the host name in Location, and find the AZ for which the alarm is generated in the AZ column based on the host name.
                                                            2. On the Instance page, click Add Instance to add n ClickHouseServer instances to other AZs except the AZ where the alarm is generated.

                                                            n ClickHouseServer instances should be added.

                                                            This alarm is generated when a non-single-cluster is deployed in the default deployment mode of cross-AZ DR. The number of ClickHouseServer instances in the cluster is less than an even number. As a result, some instances cannot work properly.

                                                            1. Determine the number (n) of ClickHouseServer instances to be added based on the alarm information.
                                                            2. On FusionInsight Manager, choose Cluster > Services > ClickHouse, click the Instance tab, and add n ClickHouseServer instances to the cluster.
                                                            +
                                                            1. Determine the number (n) of ClickHouseServer instances to be added based on the alarm information.
                                                            2. On MRS Manager, choose Cluster > Services > ClickHouse, click the Instance tab, and add n ClickHouseServer instances to the cluster.

                                                            Alarm ID

                                                            @@ -59,18 +59,18 @@
                                                          -

                                                          Impact on the System

                                                          A long GC duration of the IoTDBServer process may interrupt the services.

                                                          +

                                                          Impact on the System

                                                          A long GC duration of the IoTDBServer process may interrupt the services.

                                                          Possible Causes

                                                          The heap memory of the IoTDBServer process is overused or inappropriately allocated, causing frequent occurrence of the GC process.

                                                          Procedure

                                                          Check the GC duration.

                                                          -
                                                          1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 45587, view the role name in Location, and check the instance IP address.
                                                          2. Choose Cluster > Name of the desired cluster > Service > IoTDB > Instance. Click the IoTDBServer for which the alarm is generated to go to Dashboard. Click the drop-down list in the upper right corner of the chart area and choose Customize > GC. In the dialog box that is displayed, select Garbage Collection (GC) Time of IoTDBServer, and click OK. Check whether the GC time of the IoTDBServer process is greater than 12 seconds.

                                                            • If yes, go to 3.
                                                            • If no, go to 5.
                                                            +
                                                            1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 45587, view the role name in Location, and check the instance IP address.
                                                            2. Choose Cluster > Name of the desired cluster > Service > IoTDB > Instance. Click the IoTDBServer for which the alarm is generated to go to Dashboard. Click the drop-down list in the upper right corner of the chart area and choose Customize > GC. In the dialog box that is displayed, select Garbage Collection (GC) Time of IoTDBServer, and click OK. Check whether the GC time of the IoTDBServer process is greater than 12 seconds.

                                                              • If yes, go to 3.
                                                              • If no, go to 5.

                                                            3. Choose Cluster > Name of the desired cluster > Service > IoTDB > Configuration, click All Configurations, choose IoTDBServer > System, and increase the value of -Xmx in the GC_OPTS parameter.

                                                              • The default value of -Xmx is 2G.
                                                              • If this alarm is occasionally generated, increase the value by 0.5 times. If this alarm is frequently generated, double the value.
                                                              • In the case of large service volume and high service concurrency, you are advised to add instances.

                                                            4. Check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 5.

                                                            Collect the fault information.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.
                                                            +
                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.

                                                          Alarm Clearing

                                                          This alarm is automatically cleared after the fault is rectified.

                                                          diff --git a/docs/mrs/umn/ALM-45588.html b/docs/mrs/umn/ALM-45588.html index 09202f7c..773aad90 100644 --- a/docs/mrs/umn/ALM-45588.html +++ b/docs/mrs/umn/ALM-45588.html @@ -64,13 +64,13 @@

                                                          Possible Causes

                                                          The direct memory of the IoTDBServer process is overused or the direct memory is inappropriately allocated.

                                                          Procedure

                                                          Check the direct memory usage.

                                                          -
                                                          1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 45588, view the role name in Location, and check the instance IP address.
                                                          2. Choose Cluster > Name of the desired cluster > Service > IoTDB > Instance. Click the IoTDBServer for which the alarm is generated to go to Dashboard. Click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select IoTDBServer Direct Buffer Resource Percentage, and click OK.
                                                          3. Check whether the direct memory used by the IoTDBServer reaches the threshold (90% of the maximum direct memory by default).

                                                            • If yes, go to 4.
                                                            • If no, go to 6.
                                                            -

                                                          4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > IoTDB > Configuration, click All Configurations, choose IoTDBServer > System, increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter as required, and save the configuration.

                                                            • If this alarm is generated, the direct memory configured for the IoTDBServer process cannot meet the requirements of the IoTDBServer process.
                                                            • You are advised to set -XX:MaxDirectMemorySize in GC_OPTS to twice the direct memory used by the IoTDBServer process. (You can change the value based on the actual service scenario.)
                                                            • To obtain the size of the direct memory used by the IoTDBServer process, choose Customize > Memory > IoTDBServer Direct Memory Resource Status. If GC_OPTS does not contain the -XX:MaxDirectMemorySize parameter, add it manually.
                                                            +
                                                            1. Log in to MRS Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing the alarm whose Alarm ID is 45588, view the role name in Location, and check the instance IP address.
                                                            2. Choose Cluster > Name of the desired cluster > Service > IoTDB > Instance. Click the IoTDBServer for which the alarm is generated to go to Dashboard. Click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select IoTDBServer Direct Buffer Resource Percentage, and click OK.
                                                            3. Check whether the direct memory used by the IoTDBServer reaches the threshold (90% of the maximum direct memory by default).

                                                              • If yes, go to 4.
                                                              • If no, go to 6.
                                                              +

                                                            4. On MRS Manager, choose Cluster > Name of the desired cluster > Service > IoTDB > Configuration, click All Configurations, choose IoTDBServer > System, increase the value of -XX:MaxDirectMemorySize in the GC_OPTS parameter as required, and save the configuration.

                                                              • If this alarm is generated, the direct memory configured for the IoTDBServer process cannot meet the requirements of the IoTDBServer process.
                                                              • You are advised to set -XX:MaxDirectMemorySize in GC_OPTS to twice the direct memory used by the IoTDBServer process. (You can change the value based on the actual service scenario.)
                                                              • To obtain the size of the direct memory used by the IoTDBServer process, choose Customize > Memory > IoTDBServer Direct Memory Resource Status. If GC_OPTS does not contain the -XX:MaxDirectMemorySize parameter, add it manually.

                                                            5. Restart the affected services or instances and check whether the alarm is cleared.

                                                              • If yes, no further action is required.
                                                              • If no, go to 6.

                                                            Collect the fault information.

                                                            -
                                                            1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select IoTDBServer for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.
                                                            +
                                                            1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                            2. Expand the Service drop-down list, and select IoTDBServer for the target cluster.
                                                            3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                            4. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45589.html b/docs/mrs/umn/ALM-45589.html index c5d241ae..ad45ae56 100644 --- a/docs/mrs/umn/ALM-45589.html +++ b/docs/mrs/umn/ALM-45589.html @@ -59,7 +59,7 @@

                                                            Possible Causes

                                                            The heap memory configured for the node is improper. As a result, the usage exceeds the threshold.

                                                            Procedure

                                                            Check the heap memory configuration.

                                                            -
                                                            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                            2. Choose Cluster > Services > IoTDB. Click Instance, click the ConfigNode corresponding to the IP address obtained in 1, and check whether ConfigNode Heap Memory Usage on the Dashboard tab page reaches the threshold specified for the ConfigNode process.

                                                              If the chart is not displayed, click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select ConfigNode Heap Memory Usage and click OK.

                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose Cluster > Services > IoTDB. Click Instance, click the ConfigNode corresponding to the IP address obtained in 1, and check whether ConfigNode Heap Memory Usage on the Dashboard tab page reaches the threshold specified for the ConfigNode process.

                                                                If the chart is not displayed, click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select ConfigNode Heap Memory Usage and click OK.

                                                                You can choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > IoTDB > Memory > ConfigNode Heap Memory Usage (ConfigNode) to view the threshold.

                                                                • If yes, go to 3.
                                                                • If no, go to 6.
                                                                @@ -68,7 +68,7 @@

                                                              3. Click Dashboard. Click Restart Service to restart the IoTDB service for the configuration to take effect.
                                                              4. Wait for about 120 seconds and check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 6.

                                                              Collect fault information.

                                                              -
                                                              1. On FusionInsight Manager, choose O&M > Log > Download.
                                                              2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. On MRS Manager, choose O&M > Log > Download.
                                                              2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45590.html b/docs/mrs/umn/ALM-45590.html index 317a2e08..30a98b7f 100644 --- a/docs/mrs/umn/ALM-45590.html +++ b/docs/mrs/umn/ALM-45590.html @@ -66,7 +66,7 @@

                                                            Possible Causes

                                                            The heap memory configured on the node is improper. As a result, GC occurs frequently.

                                                            Procedure

                                                            Check the heap memory configuration.

                                                            -
                                                            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in the row containing this alarm and view the role name and instance IP address in Location.
                                                            2. Choose Cluster > Services > IoTDB. Click Instance, click the ConfigNode corresponding to the IP address obtained by 1. Switch to the Dashboard tab page, locate the Total GC Duration of ConfigNode chart, and check whether the GC duration of the ConfigNode process exceeds the threshold.

                                                              If the GC duration of ConfigNode is not displayed, click the drop-down list in the upper right corner of the chart area and choose Customize > GC. In the displayed dialog box, select Total GC Duration of ConfigNode and click OK.

                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in the row containing this alarm and view the role name and instance IP address in Location.
                                                              2. Choose Cluster > Services > IoTDB. Click Instance, click the ConfigNode corresponding to the IP address obtained by 1. Switch to the Dashboard tab page, locate the Total GC Duration of ConfigNode chart, and check whether the GC duration of the ConfigNode process exceeds the threshold.

                                                                If the GC duration of ConfigNode is not displayed, click the drop-down list in the upper right corner of the chart area and choose Customize > GC. In the displayed dialog box, select Total GC Duration of ConfigNode and click OK.

                                                                You can choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > IoTDB > GC > Total GC duration of ConfigNode process (ConfigNode) to view the threshold.

                                                                • If yes, go to 3.
                                                                • If no, go to 6.
                                                                @@ -75,7 +75,7 @@

                                                              3. Click Dashboard. Click Restart Service to restart the IoTDB service for the configuration to take effect.
                                                              4. Check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 6.

                                                              Collect fault information.

                                                              -
                                                              1. On FusionInsight Manager, choose O&M > Log > Download.
                                                              2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. On MRS Manager, choose O&M > Log > Download.
                                                              2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.

                                                            Alarm Clearing

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-45591.html b/docs/mrs/umn/ALM-45591.html index 89baec30..f7ebceec 100644 --- a/docs/mrs/umn/ALM-45591.html +++ b/docs/mrs/umn/ALM-45591.html @@ -64,14 +64,14 @@

                                                            Possible Causes

                                                            The direct memory configured for the node is improper. As a result, the usage exceeds the threshold.

                                                            Procedure

                                                            Check the direct memory configuration.

                                                            -
                                                            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                            2. Choose Cluster > Services > IoTDB. Click Instance, click the ConfigNode corresponding to the IP address obtained in 1, and check whether ConfigNode Direct Memory Usage on the Dashboard tab page reaches the threshold specified for the ConfigNode process (90% of the maximum direct memory by default).

                                                              If the chart is not displayed, click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select ConfigNode Direct Memory Usage and click OK.
                                                              • If yes, go to 3.
                                                              • If no, go to 5.
                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose Cluster > Services > IoTDB. Click Instance, click the ConfigNode corresponding to the IP address obtained in 1, and check whether ConfigNode Direct Memory Usage on the Dashboard tab page reaches the threshold specified for the ConfigNode process (90% of the maximum direct memory by default).

                                                                If the chart is not displayed, click the drop-down list in the upper right corner of the chart area and choose Customize > Memory. In the dialog box that is displayed, select ConfigNode Direct Memory Usage and click OK.
                                                                • If yes, go to 3.
                                                                • If no, go to 5.
                                                                -

                                                              3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > IoTDB. Click Configurations then All Configurations. Click ConfigNode and select System. Set -XX:MaxDirectMemorySize in GC_OPTS to a larger value as required and save the configuration.

                                                                • You are advised to set -XX:MaxDirectMemorySize in GC_OPTS to twice the direct memory used by the ConfigNode process. (You can change the value based on the actual service scenario.)
                                                                • To obtain the size of the direct memory used by the ConfigNode process, choose Customize > Memory > ConfigNode Direct Memory Resource Status.
                                                                • If GC_OPTS does not contain the -XX:MaxDirectMemorySize parameter, add it.
                                                                +

                                                              4. On MRS Manager, choose Cluster > Name of the desired cluster > Services > IoTDB. Click Configurations then All Configurations. Click ConfigNode and select System. Set -XX:MaxDirectMemorySize in GC_OPTS to a larger value as required and save the configuration.

                                                                • You are advised to set -XX:MaxDirectMemorySize in GC_OPTS to twice the direct memory used by the ConfigNode process. (You can change the value based on the actual service scenario.)
                                                                • To obtain the size of the direct memory used by the ConfigNode process, choose Customize > Memory > ConfigNode Direct Memory Resource Status.
                                                                • If GC_OPTS does not contain the -XX:MaxDirectMemorySize parameter, add it.

                                                              5. Restart the affected IoTDB service or instances and check whether the alarm is cleared.

                                                                • If yes, no further action is required.
                                                                • If no, go to 5.

                                                              Collect fault information.

                                                              -
                                                              1. On FusionInsight Manager, choose O&M > Log > Download.
                                                              2. Expand the Service drop-down list, and select ConfigNode for the destination cluster.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. On MRS Manager, choose O&M > Log > Download.
                                                              2. Expand the Service drop-down list, and select ConfigNode for the destination cluster.
                                                              3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
                                                              4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                                                              5. Contact O&M personnel and provide the collected logs.

                                                              Alarm Clearing

                                                              This alarm is automatically cleared after the fault is rectified.

                                                              diff --git a/docs/mrs/umn/ALM-45592.html b/docs/mrs/umn/ALM-45592.html index d132e905..ec9d8b62 100644 --- a/docs/mrs/umn/ALM-45592.html +++ b/docs/mrs/umn/ALM-45592.html @@ -59,7 +59,7 @@

                                                              Possible Causes

                                                              The processing duration of an IoTDBServer RPC request exceeds the threshold. Logs need to be further analyzed to locate the cause.

                                                              Procedure

                                                              Collect fault information.

                                                              -
                                                              1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.

                                                              Alarm Clearing

                                                              This alarm is automatically cleared after the fault is rectified.

                                                              diff --git a/docs/mrs/umn/ALM-45593.html b/docs/mrs/umn/ALM-45593.html index 24b03480..14247ad9 100644 --- a/docs/mrs/umn/ALM-45593.html +++ b/docs/mrs/umn/ALM-45593.html @@ -59,7 +59,7 @@

                                                              Possible Causes

                                                              The IoTDB flushing on the node is slow. You need to further analyze logs.

                                                              Procedure

                                                              Collect fault information.

                                                              -
                                                              1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.

                                                              Alarm Clearing

                                                              This alarm is automatically cleared after the fault is rectified.

                                                              diff --git a/docs/mrs/umn/ALM-45594.html b/docs/mrs/umn/ALM-45594.html index e6e8706a..ae355c85 100644 --- a/docs/mrs/umn/ALM-45594.html +++ b/docs/mrs/umn/ALM-45594.html @@ -59,7 +59,7 @@

                                                              Possible Causes

                                                              The merge task in the IoTDB space of the node is slow. You need to further analyze logs.

                                                              Procedure

                                                              Collect fault information.

                                                              -
                                                              1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.

                                                              Alarm Clearing

                                                              This alarm is automatically cleared after the fault is rectified.

                                                              diff --git a/docs/mrs/umn/ALM-45595.html b/docs/mrs/umn/ALM-45595.html index e0dc8f73..b9ff31fc 100644 --- a/docs/mrs/umn/ALM-45595.html +++ b/docs/mrs/umn/ALM-45595.html @@ -59,7 +59,7 @@

                                                              Possible Causes

                                                              The IoTDB cross-space merge task on the node is slow. You need to further analyze logs.

                                                              Procedure

                                                              Collect fault information.

                                                              -
                                                              1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.
                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Alarms. In the real-time alarm list, click in front of this alarm and view the role name and instance IP address in Location.
                                                              2. Choose O&M > Log > Download.
                                                              3. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
                                                              4. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the host queried in 1, and click OK.
                                                              5. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
                                                              6. Contact O&M personnel and provide the collected logs.

                                                              Alarm Clearing

                                                              This alarm is automatically cleared after the fault is rectified.

                                                              diff --git a/docs/mrs/umn/ALM-45615.html b/docs/mrs/umn/ALM-45615.html index cb548b16..ec65d345 100644 --- a/docs/mrs/umn/ALM-45615.html +++ b/docs/mrs/umn/ALM-45615.html @@ -54,19 +54,19 @@
      -

      Impact on the System

      The CDL service is abnormal. You cannot use FusionInsight Manager to perform cluster operations on the CDL service. The CDL service function is unavailable.

      +

      Impact on the System

      The CDL service is abnormal. You cannot use MRS Manager to perform cluster operations on the CDL service. The CDL service function is unavailable.

      Possible Causes

      All CDLService or CDLConnector instances of the CDL service are abnormal, and the Kafka service is unavailable.

      Procedure

      Check whether the Kafka service on which the CDL service depends is abnormal.

      -
      1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
      2. In the alarm list, check whether ALM-38000 Kafka Service Unavailable exists.

        • If yes, go to 3.
        • If no, go to 5.
        +
        1. On MRS Manager, choose O&M > Alarm > Alarms.
        2. In the alarm list, check whether ALM-38000 Kafka Service Unavailable exists.

          • If yes, go to 3.
          • If no, go to 5.

        3. Handle the alarm by referring to "ALM-38000 Kafka Service Unavailable".
        4. After the alarm is cleared, wait a few minutes and check whether the alarm HetuServer Service Unavailable is cleared.

          • If yes, no further action is required.
          • If no, go to 5.

        Check whether CDL instances are faulty.

        -
        1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > CDL > Instance.
        2. Check whether all CDLService and CDLConnector instances are faulty.

          • If yes, restart the CDL service and choose Cluster > Name of the desired cluster > Services > CDL > More > Restart Service. If the fault persists after the restart, go to 7 and contact O&M personnel to check CDL logs.
          • If no, go to 7.
          +
          1. On MRS Manager, choose Cluster > Name of the desired cluster > Service > CDL > Instance.
          2. Check whether all CDLService and CDLConnector instances are faulty.

            • If yes, restart the CDL service and choose Cluster > Name of the desired cluster > Services > CDL > More > Restart Service. If the fault persists after the restart, go to 7 and contact O&M personnel to check CDL logs.
            • If no, go to 7.

          Collect the fault information.

          -
          1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
          2. Expand the Service drop-down list, and select CDL for the target cluster.
          3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
          4. Contact O&M personnel and provide the collected logs.
          +
          1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
          2. Expand the Service drop-down list, and select CDL for the target cluster.
          3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
          4. Contact O&M personnel and provide the collected logs.

      Alarm Clearing

      After the service is restored, the system automatically clears the alarm.

      diff --git a/docs/mrs/umn/ALM-45616.html b/docs/mrs/umn/ALM-45616.html index 952c87fa..5c4026ab 100644 --- a/docs/mrs/umn/ALM-45616.html +++ b/docs/mrs/umn/ALM-45616.html @@ -58,13 +58,13 @@

      Possible Causes

      The CDL task fails to be executed due to incorrect parameter settings or other reasons. On the Job Management page of the CDL web UI, locate the row where the job is located and click Failed/Abnormal running in the Status column to view the failure cause, or view the failure cause in the logs.

      -

      Procedure

      1. Log in to FusionInsight Manager as a user who has the CDL job creation or administrator permission.
      2. Choose O&M. In the navigation pane on the left, choose Alarm > Alarms, click in the row where Alarm ID is 45616, and view the name of the job for which this alarm is generated in Location.
      3. Choose Cluster > Services > CDL and click the link next to CDLService UI to go to the CDL web UI.
      4. Locate the row where the failed job is located based on the job name obtained in 2, and click Abnormal running or Failed in the Status column.

        +

        Procedure

        1. Log in to MRS Manager as a user who has the CDL job creation or administrator permission.
        2. Choose O&M. In the navigation pane on the left, choose Alarm > Alarms, click in the row where Alarm ID is 45616, and view the name of the job for which this alarm is generated in Location.
        3. Choose Cluster > Services > CDL and click the link next to CDLService UI to go to the CDL web UI.
        4. Locate the row where the failed job is located based on the job name obtained in 2, and click Abnormal running or Failed in the Status column.

        5. On the page that is displayed, view the error information and rectify the fault. For example, Figure 1 shows that the task running on Yarn is manually killed. For details, see trace error information, as shown in Figure 2.

          Figure 1 CDL job exception
          Figure 2 Trace error information

        6. Rectify the fault based on the error information, execute the task again, and check whether the task can be executed successfully.

          • If yes, no further action is required.
          • If no, go to 7.

        Collect the fault information.

        -
        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. Select CDL in the required cluster for Service.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.
        +
        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. Select CDL in the required cluster for Service.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.

        Alarm Clearing

        After the job is successfully restored or stopped, the alarm is cleared if it has been reported.

        diff --git a/docs/mrs/umn/ALM-45617.html b/docs/mrs/umn/ALM-45617.html index 2a276c2b..33f0bb03 100644 --- a/docs/mrs/umn/ALM-45617.html +++ b/docs/mrs/umn/ALM-45617.html @@ -68,13 +68,13 @@

      Possible Causes

      The CDL job is abnormal, and data processing stops; the source database is updated quickly, and CDL data processing is slow.

      -

      Procedure

      1. Log in to FusionInsight Manager as a user who has the CDL job creation or administrator permission.
      2. Choose O&M. In the navigation pane on the left, choose Alarm > Alarms, click in the row where Alarm ID is 45617, and view the name of the job for which this alarm is generated in Location.
      3. Check whether ALM-45616 CDL Job Execution Exception is displayed in the alarm list.

        • If yes, handle the alarm by performing operations provided for ALM-45616 CDL Job Execution Exception.
        • If no, go to 4.
        +

        Procedure

        1. Log in to MRS Manager as a user who has the CDL job creation or administrator permission.
        2. Choose O&M. In the navigation pane on the left, choose Alarm > Alarms, click in the row where Alarm ID is 45617, and view the name of the job for which this alarm is generated in Location.
        3. Check whether ALM-45616 CDL Job Execution Exception is displayed in the alarm list.

          • If yes, handle the alarm by performing operations provided for ALM-45616 CDL Job Execution Exception.
          • If no, go to 4.

        4. Choose Cluster > Services > CDL. Click the link next to CDLService UI to go to the CDL web UI and check whether the job is displayed in the job list based on its name obtained in 2.

          • If yes, check whether the job is abnormal.
            • If it is abnormal, go to 5.
            • If it is not, data processing is slow. Contact O&M personnel.
          • If no, go to 7.

        5. Click Abnormal or Failed in the row where the job is located and rectify the fault based on the error information displayed on the page.
        6. After rectifying the fault, run the job again and check whether the job can be executed successfully.

          • If yes, no further action is required.
          • If no, go to 7.

        Collect the fault information.

        -
        1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. Select CDL in the required cluster for Service.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.
        +
        1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
        2. Select CDL in the required cluster for Service.
        3. Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time respectively. Then, click Download.
        4. Contact O&M personnel and provide the collected logs.

        Alarm Clearing

        This alarm is cleared when the amount of data queued in the replication slot is less than the threshold. You do not need to manually clear the alarm.

        diff --git a/docs/mrs/umn/ALM-45640.html b/docs/mrs/umn/ALM-45640.html index 2dac7ed0..1db26538 100644 --- a/docs/mrs/umn/ALM-45640.html +++ b/docs/mrs/umn/ALM-45640.html @@ -61,7 +61,7 @@

        Possible Causes

        • The active or standby FlinkServer instance is in the stopped state.
        • The NIC of the floating IP address of the HA system used by the FlinkServer node is incorrectly configured. FlinkServer fails to be started.
        • The link between the active and standby FlinkServer nodes is abnormal.

        Procedure

        Check the status of the active and standby FlinkServer instances.

        -
        1. Log in to FusionInsight Manager, choose Cluster > Services > Flink > Instance, and check the state of FlinkServer is normal.

          • If yes, go to 3.
          • If no, go to 2.
          +
          1. Log in to MRS Manager, choose Cluster > Services > Flink > Instance, and check the state of FlinkServer is normal.

            • If yes, go to 3.
            • If no, go to 2.

          2. Select the abnormal FlinkServer instance and start the instance. After the instance is started, check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 3.

          Check whether the link between the standby FlinkServer nodes is normal.

          @@ -71,12 +71,12 @@

        Check whether the logs of the node where the abnormal FlinkServer instance locates contains error information.

        1. Log in to the server where the abnormal FlinkServer instance locates as the root user.
        2. Open the log file in the default directory /var/log/Bigdata/flink/flinkserver/prestart.log and check whether there is error message Float ip x.x.x.x is invalid.

          • If yes, go to 10.
          • If no, go to 12.
          -

        3. On FusionInsight Manager, choose Cluster > Services > Flink > Configurations > All Configurations and search for flink.ha.floatip. Change the parameter value to the correct floating IP address, save the configuration, and restart the Flink service.

          Contact the network engineer to obtain the new floating IP address.

          +

        4. On MRS Manager, choose Cluster > Services > Flink > Configurations > All Configurations and search for flink.ha.floatip. Change the parameter value to the correct floating IP address, save the configuration, and restart the Flink service.

          Contact the network engineer to obtain the new floating IP address.

        5. Check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 12.

        Collect the fault information.

        -
        1. On FusionInsight Manager, choose O&M > Log > Download.
        2. Select the Flink service in the required cluster for Service.
        3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
        4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        5. Contact O&M personnel and provide the collected logs.
        +
        1. On MRS Manager, choose O&M > Log > Download.
        2. Select the Flink service in the required cluster for Service.
        3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
        4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        5. Contact O&M personnel and provide the collected logs.

        Alarm Clearing

        This alarm is automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/ALM-45641.html b/docs/mrs/umn/ALM-45641.html index 387d74c4..789b124d 100644 --- a/docs/mrs/umn/ALM-45641.html +++ b/docs/mrs/umn/ALM-45641.html @@ -61,7 +61,7 @@

        Possible Causes

        • The link between the active and standby FlinkServer nodes is interrupted.
        • The synchronization file does not exist or the file permission is required.

        Procedure

        Check whether the network between the active and standby FlinkServer is in normal state.

        -
        1. On FusionInsight Manager, choose Cluster > Services > ClickHouse > Instance. View and record the IP addresses of active and standby FlinkServer.
        2. Log in to the active FlinkServer node as the root user.
        3. Run the following command to check whether the standby FlinkServer is reachable:

          ping IP address of the standby FlinkServer

          +
          1. On MRS Manager, choose Cluster > Services > ClickHouse > Instance. View and record the IP addresses of active and standby FlinkServer.
          2. Log in to the active FlinkServer node as the root user.
          3. Run the following command to check whether the standby FlinkServer is reachable:

            ping IP address of the standby FlinkServer

            • If yes, go to 6.
            • If no, go to 4.

          4. Contact the network administrator to check whether the network is faulty.

            • If yes, go to 5.
            • If no, go to 6.

          5. Rectify the network fault and check whether the alarm is cleared from the alarm list.

            • If yes, no further action is required.
            • If no, go to 6.
            @@ -72,7 +72,7 @@

          6. Run the following command to clear unnecessary backup files:

            rm -rf Directory to be cleared

            The following are two examples:

            rm -rf /srv/BigData/LocalBackup/0/default-oms_20191211143443

            -

          7. On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management.

            In the Operation column of the backup task, click Configure and change the value of Maximum Number of Backup Copies to reduce the number of backup file sets.

            +

          8. On MRS Manager, choose O&M > Backup and Restoration > Backup Management.

            In the Operation column of the backup task, click Configure and change the value of Maximum Number of Backup Copies to reduce the number of backup file sets.

          9. Wait for 1 minute and check whether the alarm is cleared.

            • If yes, no further action is required.
            • If no, go to 10.

          Check whether the synchronization file exists and whether the file permission is valid.

          @@ -95,7 +95,7 @@

        4. Wait for about 10 minutes and check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, go to 14.

        Collect fault information.

        -
        1. On FusionInsight Manager, choose O&M > Log > Download.
        2. Select FlinkServer information from Services and click OK.
        3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
        4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        5. Contact O&M personnel and provide the collected logs.
        +
        1. On MRS Manager, choose O&M > Log > Download.
        2. Select FlinkServer information from Services and click OK.
        3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
        4. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
        5. Contact O&M personnel and provide the collected logs.

        Alarm Clearing

        This alarm is automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/CLASS.TXT.json b/docs/mrs/umn/CLASS.TXT.json index b5eded16..0e8f07ae 100644 --- a/docs/mrs/umn/CLASS.TXT.json +++ b/docs/mrs/umn/CLASS.TXT.json @@ -1682,6 +1682,33 @@ "p_code":"185", "code":"187" }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"", + "title":"Removing ClickHouseServer Instance Nodes", + "uri":"mrs_01_248971.html", + "doc_type":"", + "p_code":"185", + "code":"188" + }, + { + "desc":"If a cluster has only one shard, the instance nodes cannot be removed from the cluster.Multiple instance nodes in the same shard must be decommissioned or recommissioned ", + "product_code":"", + "title":"Constraints on ClickHouseServer Scale-in", + "uri":"mrs_01_248972.html", + "doc_type":"", + "p_code":"188", + "code":"189" + }, + { + "desc":"Before removing ClickHouseServer instance nodes, you need to decommission them. Multiple node replicas of the same shard must be decommissioned at the same time. If there", + "product_code":"", + "title":"Scaling In ClickHouseServer Nodes", + "uri":"mrs_01_248973.html", + "doc_type":"", + "p_code":"188", + "code":"190" + }, { "desc":"To check an abnormal or faulty host (node), you need to stop all host roles on MRS. To recover host services after the host fault is rectified, restart all roles.You have", "product_code":"mrs", @@ -1689,7 +1716,7 @@ "uri":"mrs_01_0211.html", "doc_type":"usermanual", "p_code":"185", - "code":"188" + "code":"191" }, { "desc":"If a host is found to be abnormal or faulty, affecting cluster performance or preventing services from being provided, you can temporarily exclude that host from the avai", @@ -1698,7 +1725,7 @@ "uri":"mrs_01_0212.html", "doc_type":"usermanual", "p_code":"185", - "code":"189" + "code":"192" }, { "desc":"After the exception or fault of a host is handled, you must cancel the isolation of the host for proper usage.You can cancel the isolation of a host on MRS.The host is in", @@ -1707,7 +1734,7 @@ "uri":"mrs_01_0213.html", "doc_type":"usermanual", "p_code":"185", - "code":"190" + "code":"193" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1716,7 +1743,7 @@ "uri":"mrs_01_0522.html", "doc_type":"usermanual", "p_code":"160", - "code":"191" + "code":"194" }, { "desc":"An MRS job is the program execution platform of MRS. It is used to process and analyze user data. After a job is created, all job information is displayed on the Jobs tab", @@ -1724,8 +1751,8 @@ "title":"Introduction to MRS Jobs", "uri":"mrs_01_0051.html", "doc_type":"usermanual", - "p_code":"191", - "code":"192" + "p_code":"194", + "code":"195" }, { "desc":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a MapReduce job on the MRS management c", @@ -1733,8 +1760,8 @@ "title":"Running a MapReduce Job", "uri":"mrs_01_0052.html", "doc_type":"usermanual", - "p_code":"191", - "code":"193" + "p_code":"194", + "code":"196" }, { "desc":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a Spark job on the MRS console.You have", @@ -1742,8 +1769,8 @@ "title":"Running a SparkSubmit Job", "uri":"mrs_01_0524.html", "doc_type":"usermanual", - "p_code":"191", - "code":"194" + "p_code":"194", + "code":"197" }, { "desc":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a HiveSQL job on the MRS management con", @@ -1751,8 +1778,8 @@ "title":"Running a HiveSQL Job", "uri":"mrs_01_0525.html", "doc_type":"usermanual", - "p_code":"191", - "code":"195" + "p_code":"194", + "code":"198" }, { "desc":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a SparkSQL job on the MRS console. Spar", @@ -1760,8 +1787,8 @@ "title":"Running a SparkSql Job", "uri":"mrs_01_0526.html", "doc_type":"usermanual", - "p_code":"191", - "code":"196" + "p_code":"194", + "code":"199" }, { "desc":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This section describes how to submit a Flink job on the MRS management conso", @@ -1769,8 +1796,8 @@ "title":"Running a Flink Job", "uri":"mrs_01_0527.html", "doc_type":"usermanual", - "p_code":"191", - "code":"197" + "p_code":"194", + "code":"200" }, { "desc":"You can submit programs developed by yourself to MRS to execute them, and obtain the results. This topic describes how to generate and consume messages in a Kafka topic.C", @@ -1778,8 +1805,8 @@ "title":"Running a Kafka Job", "uri":"mrs_01_0494.html", "doc_type":"usermanual", - "p_code":"191", - "code":"198" + "p_code":"194", + "code":"201" }, { "desc":"This section describes how to view job configuration and logs.You can view configuration information of all jobs.You can only view logs of running jobs.Because logs of Sp", @@ -1787,8 +1814,8 @@ "title":"Viewing Job Configuration and Logs", "uri":"mrs_01_0055.html", "doc_type":"usermanual", - "p_code":"191", - "code":"199" + "p_code":"194", + "code":"202" }, { "desc":"This section describes how to stop running MRS jobs.You cannot stop Spark SQL jobs. After a job is stopped, its status changes to Terminated and the job cannot be execute", @@ -1796,8 +1823,8 @@ "title":"Stopping a Job", "uri":"mrs_01_0056.html", "doc_type":"usermanual", - "p_code":"191", - "code":"200" + "p_code":"194", + "code":"203" }, { "desc":"This section describes how to copy new MRS jobs. Only clusters whose version is MRS 1.7.2 or earlier support job replication.Currently, all types of jobs except for Spark", @@ -1805,8 +1832,8 @@ "title":"Copying Jobs", "uri":"mrs_01_0057.html", "doc_type":"usermanual", - "p_code":"191", - "code":"201" + "p_code":"194", + "code":"204" }, { "desc":"This section describes how to delete an MRS job. After a job is executed, you can delete it if you do not need to view its information.Jobs can be deleted one after anoth", @@ -1814,8 +1841,8 @@ "title":"Deleting a Job", "uri":"mrs_01_0058.html", "doc_type":"usermanual", - "p_code":"191", - "code":"202" + "p_code":"194", + "code":"205" }, { "desc":"MRS uses SMN to offer a publish/subscribe model to achieve one-to-multiple message subscriptions and notifications in a variety of message types (SMSs and emails). You ca", @@ -1823,8 +1850,8 @@ "title":"Configuring Job Notification Rules", "uri":"mrs_01_0762.html", "doc_type":"usermanual", - "p_code":"191", - "code":"203" + "p_code":"194", + "code":"206" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1833,7 +1860,7 @@ "uri":"mrs_01_0200.html", "doc_type":"usermanual", "p_code":"160", - "code":"204" + "code":"207" }, { "desc":"MRS contains different types of basic objects. Table 1 describes these objects.", @@ -1841,8 +1868,8 @@ "title":"Object Management", "uri":"mrs_01_0201.html", "doc_type":"usermanual", - "p_code":"204", - "code":"205" + "p_code":"207", + "code":"208" }, { "desc":"On MRS, you can view the configuration of services (including roles) and role instances.You have synchronized IAM users. (On the Dashboard page, click Synchronize on the ", @@ -1850,8 +1877,8 @@ "title":"Viewing Configuration", "uri":"mrs_01_0202.html", "doc_type":"usermanual", - "p_code":"204", - "code":"206" + "p_code":"207", + "code":"209" }, { "desc":"You can perform the following operations on MRS:Start the service in the Stopped, Stop Failed, or Failed to Start state to use the service.Stop the services or stop abnor", @@ -1859,8 +1886,8 @@ "title":"Managing Services", "uri":"mrs_01_0203.html", "doc_type":"usermanual", - "p_code":"204", - "code":"207" + "p_code":"207", + "code":"210" }, { "desc":"On the MRS console, you can view and modify the default service configurations based on site requirements and export or import the configurations.You need to download and", @@ -1868,8 +1895,8 @@ "title":"Configuring Service Parameters", "uri":"mrs_01_0204.html", "doc_type":"usermanual", - "p_code":"204", - "code":"208" + "p_code":"207", + "code":"211" }, { "desc":"Each component of MRS supports all open-source parameters. MRS supports the modification of some parameters for key application scenarios. Some component clients may not ", @@ -1877,8 +1904,8 @@ "title":"Configuring Customized Service Parameters", "uri":"mrs_01_0205.html", "doc_type":"usermanual", - "p_code":"204", - "code":"209" + "p_code":"207", + "code":"212" }, { "desc":"If Configuration Status of some services is Configuration expired or Configuration failed, synchronize configuration for the cluster or service to restore its configurati", @@ -1886,8 +1913,8 @@ "title":"Synchronizing Service Configuration", "uri":"mrs_01_0206.html", "doc_type":"usermanual", - "p_code":"204", - "code":"210" + "p_code":"207", + "code":"213" }, { "desc":"You can start a role instance that is in the Stopped, Failed to stop or Failed to start status, stop an unused or abnormal role instance or restart an abnormal role insta", @@ -1895,8 +1922,8 @@ "title":"Managing Role Instances", "uri":"mrs_01_0207.html", "doc_type":"usermanual", - "p_code":"204", - "code":"211" + "p_code":"207", + "code":"214" }, { "desc":"You can view and modify default role instance configuration on MRS based on site requirements. The configurations can be imported and exported.You need to download and up", @@ -1904,8 +1931,8 @@ "title":"Configuring Role Instance Parameters", "uri":"mrs_01_0208.html", "doc_type":"usermanual", - "p_code":"204", - "code":"212" + "p_code":"207", + "code":"215" }, { "desc":"When Configuration Status of a role instance is Configuration expired or Configuration failed, you can synchronize the configuration data of the role instance with the ba", @@ -1913,8 +1940,8 @@ "title":"Synchronizing Role Instance Configuration", "uri":"mrs_01_0209.html", "doc_type":"usermanual", - "p_code":"204", - "code":"213" + "p_code":"207", + "code":"216" }, { "desc":"If a Core or Task node is faulty, the cluster status may be displayed as Abnormal. In an MRS cluster, data can be stored on different Core nodes. You can decommission the", @@ -1922,8 +1949,8 @@ "title":"Decommissioning and Recommissioning a Role Instance", "uri":"mrs_01_0210.html", "doc_type":"usermanual", - "p_code":"204", - "code":"214" + "p_code":"207", + "code":"217" }, { "desc":"A cluster is a collection of service components. You can start or stop all services in a cluster.You have synchronized IAM users. (On the Dashboard page, click Synchroniz", @@ -1931,8 +1958,8 @@ "title":"Starting and Stopping a Cluster", "uri":"mrs_01_0214.html", "doc_type":"usermanual", - "p_code":"204", - "code":"215" + "p_code":"207", + "code":"218" }, { "desc":"If Configuration Status of all services or some services is Configuration expired or Configuration failed, synchronize configuration for the cluster or service to restore", @@ -1940,8 +1967,8 @@ "title":"Synchronizing Cluster Configuration", "uri":"mrs_01_0215.html", "doc_type":"usermanual", - "p_code":"204", - "code":"216" + "p_code":"207", + "code":"219" }, { "desc":"You can export all configuration data of a cluster using MRS to meet site requirements. The exported configuration data is used to rapidly update service configuration.In", @@ -1949,8 +1976,8 @@ "title":"Exporting Cluster Configuration", "uri":"mrs_01_0216.html", "doc_type":"usermanual", - "p_code":"204", - "code":"217" + "p_code":"207", + "code":"220" }, { "desc":"After modifying the configuration items of a big data component, you need to restart the corresponding service to make new configurations take effect. If you use a normal", @@ -1958,8 +1985,8 @@ "title":"Performing Rolling Restart", "uri":"mrs_01_0628.html", "doc_type":"usermanual", - "p_code":"204", - "code":"218" + "p_code":"207", + "code":"221" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1968,7 +1995,7 @@ "uri":"mrs_01_0112.html", "doc_type":"usermanual", "p_code":"160", - "code":"219" + "code":"222" }, { "desc":"The alarm list displays all alarms in the MRS cluster. The MRS page displays the alarms that need to be handled in a timely manner and the events.On the MRS management co", @@ -1976,8 +2003,8 @@ "title":"Viewing the Alarm List", "uri":"en-us_topic_0040980162.html", "doc_type":"usermanual", - "p_code":"219", - "code":"220" + "p_code":"222", + "code":"223" }, { "desc":"The event list displays information about all events in a cluster, such as service restart and service termination.Events are listed in chronological order by default in ", @@ -1985,8 +2012,8 @@ "title":"Viewing the Event List", "uri":"mrs_01_0602.html", "doc_type":"usermanual", - "p_code":"219", - "code":"221" + "p_code":"222", + "code":"224" }, { "desc":"You can view and clear alarms on MRS.Generally, the system automatically clears an alarm when the fault is rectified. If the fault has been rectified and the alarm cannot", @@ -1994,8 +2021,8 @@ "title":"Viewing and Manually Clearing an Alarm", "uri":"mrs_01_0113.html", "doc_type":"usermanual", - "p_code":"219", - "code":"222" + "p_code":"222", + "code":"225" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2004,7 +2031,7 @@ "uri":"mrs_01_0409.html", "doc_type":"usermanual", "p_code":"160", - "code":"223" + "code":"226" }, { "desc":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", @@ -2012,8 +2039,8 @@ "title":"Patch Operation Guide for Versions Earlier than MRS 1.7.0", "uri":"mrs_01_0410.html", "doc_type":"usermanual", - "p_code":"223", - "code":"224" + "p_code":"226", + "code":"227" }, { "desc":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", @@ -2021,8 +2048,8 @@ "title":"Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0", "uri":"mrs_01_0411.html", "doc_type":"usermanual", - "p_code":"223", - "code":"225" + "p_code":"226", + "code":"228" }, { "desc":"The rolling patch function indicates that patches are installed or uninstalled for one or more services in a cluster by performing a rolling service restart (restarting s", @@ -2030,8 +2057,8 @@ "title":"Rolling Patches", "uri":"mrs_01_0431.html", "doc_type":"usermanual", - "p_code":"223", - "code":"226" + "p_code":"226", + "code":"229" }, { "desc":"If some hosts are isolated in a cluster, perform the following operations to restore patches for these isolated hosts after patch installation on other hosts in the clust", @@ -2039,8 +2066,8 @@ "title":"Restoring Patches for the Isolated Hosts", "uri":"mrs_01_0412.html", "doc_type":"usermanual", - "p_code":"223", - "code":"227" + "p_code":"226", + "code":"230" }, { "desc":"When a new patch is available in the cluster, the system pushes the patch online. You can install the patch in a few clicks.This section applies only to MRS 2.x and earli", @@ -2048,8 +2075,17 @@ "title":"Patch Update", "uri":"mrs_01_248926.html", "doc_type":"usermanual", - "p_code":"223", - "code":"228" + "p_code":"226", + "code":"231" + }, + { + "desc":"After the MRS 3.1.2-LTS.2.14 patch is installed, a message may be displayed indicating that the client patch package fails to be generated. To solve this problem, perform", + "product_code":"", + "title":"MRS 3.1.2-LTS.2 Patch Description", + "uri":"mrs_01_9043.html", + "doc_type":"", + "p_code":"226", + "code":"232" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2058,7 +2094,7 @@ "uri":"mrs_01_0303.html", "doc_type":"usermanual", "p_code":"160", - "code":"229" + "code":"233" }, { "desc":"This section describes how to manage tenants on the MRS console.Tenant management operations on the console apply only to clusters of versions earlier than MRS 3.x.Tenant", @@ -2066,8 +2102,8 @@ "title":"Before You Start", "uri":"mrs_01_0604.html", "doc_type":"usermanual", - "p_code":"229", - "code":"230" + "p_code":"233", + "code":"234" }, { "desc":"An MRS cluster provides various resources and services for multiple organizations, departments, or applications to share. The cluster provides tenants as a logical entity", @@ -2075,8 +2111,8 @@ "title":"Overview", "uri":"mrs_01_0304.html", "doc_type":"usermanual", - "p_code":"229", - "code":"231" + "p_code":"233", + "code":"235" }, { "desc":"You can create a tenant on MRS Manager to specify the resource usage.A tenant name has been planned. The name must not be the same as that of a role or Yarn queue that ex", @@ -2084,8 +2120,8 @@ "title":"Creating a Tenant", "uri":"mrs_01_0305.html", "doc_type":"usermanual", - "p_code":"229", - "code":"232" + "p_code":"233", + "code":"236" }, { "desc":"You can create a sub-tenant on MRS if the resources of the current tenant need to be further allocated.A parent tenant has been added.A tenant name has been planned. The ", @@ -2093,8 +2129,8 @@ "title":"Creating a Sub-tenant", "uri":"mrs_01_0306.html", "doc_type":"usermanual", - "p_code":"229", - "code":"233" + "p_code":"233", + "code":"237" }, { "desc":"You can delete a tenant that is not required on MRS.A tenant has been added.You have checked whether the tenant to be deleted has sub-tenants. If the tenant has sub-tenan", @@ -2102,8 +2138,8 @@ "title":"Deleting a Tenant", "uri":"mrs_01_0307.html", "doc_type":"usermanual", - "p_code":"229", - "code":"234" + "p_code":"233", + "code":"238" }, { "desc":"You can manage the HDFS storage directory used by a specific tenant on MRS. The management operations include adding a tenant directory, modifying the directory file quot", @@ -2111,8 +2147,8 @@ "title":"Managing a Tenant Directory", "uri":"mrs_01_0308.html", "doc_type":"usermanual", - "p_code":"229", - "code":"235" + "p_code":"233", + "code":"239" }, { "desc":"Tenant data is stored on Manager and in cluster components by default. When components are restored from faults or reinstalled, some tenant configuration data may be abno", @@ -2120,8 +2156,8 @@ "title":"Restoring Tenant Data", "uri":"mrs_01_0309.html", "doc_type":"usermanual", - "p_code":"229", - "code":"236" + "p_code":"233", + "code":"240" }, { "desc":"In an MRS cluster, users can logically divide Yarn cluster nodes to combine multiple NodeManagers into a Yarn resource pool. Each NodeManager belongs to one resource pool", @@ -2129,8 +2165,8 @@ "title":"Creating a Resource Pool", "uri":"mrs_01_0310.html", "doc_type":"usermanual", - "p_code":"229", - "code":"237" + "p_code":"233", + "code":"241" }, { "desc":"You can modify members of an existing resource pool on MRS.You have synchronized IAM users. (On the Dashboard page, click Synchronize on the right side of IAM User Sync t", @@ -2138,8 +2174,8 @@ "title":"Modifying a Resource Pool", "uri":"mrs_01_0311.html", "doc_type":"usermanual", - "p_code":"229", - "code":"238" + "p_code":"233", + "code":"242" }, { "desc":"You can delete an existing resource pool on MRS.Any queue in a cluster cannot use the resource pool to be deleted as the default resource pool. Before deleting the resour", @@ -2147,8 +2183,8 @@ "title":"Deleting a Resource Pool", "uri":"mrs_01_0312.html", "doc_type":"usermanual", - "p_code":"229", - "code":"239" + "p_code":"233", + "code":"243" }, { "desc":"You can modify the queue configuration of a specified tenant on MRS based on service requirements.A tenant associated with Yarn and allocated dynamic resources has been a", @@ -2156,8 +2192,8 @@ "title":"Configuring a Queue", "uri":"mrs_01_0313.html", "doc_type":"usermanual", - "p_code":"229", - "code":"240" + "p_code":"233", + "code":"244" }, { "desc":"After a resource pool is added, the capacity policies of available resources need to be configured for Yarn task queues. This ensures that tasks in the resource pool are ", @@ -2165,8 +2201,8 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"mrs_01_0314.html", "doc_type":"usermanual", - "p_code":"229", - "code":"241" + "p_code":"233", + "code":"245" }, { "desc":"Users can clear the configuration of a queue on MRS Manager when the queue does not need resources from a resource pool or if a resource pool needs to be disassociated fr", @@ -2174,8 +2210,8 @@ "title":"Clearing Configuration of a Queue", "uri":"mrs_01_0315.html", "doc_type":"usermanual", - "p_code":"229", - "code":"242" + "p_code":"233", + "code":"246" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2184,7 +2220,7 @@ "uri":"mrs_01_24565.html", "doc_type":"usermanual", "p_code":"160", - "code":"243" + "code":"247" }, { "desc":"Bootstrap actions indicate that you can run your scripts on a specified cluster node before or after starting big data components. You can run bootstrap actions to instal", @@ -2192,8 +2228,8 @@ "title":"Introduction to Bootstrap Actions", "uri":"mrs_01_0414.html", "doc_type":"usermanual", - "p_code":"243", - "code":"244" + "p_code":"247", + "code":"248" }, { "desc":"Currently, bootstrap actions support Linux shell scripts only. Script files must end with .sh.Before compiling a script, you need to upload all required installation pack", @@ -2201,8 +2237,8 @@ "title":"Preparing the Bootstrap Action Script", "uri":"mrs_01_0417.html", "doc_type":"usermanual", - "p_code":"243", - "code":"245" + "p_code":"247", + "code":"249" }, { "desc":"You can view the execution result of the bootstrap operation on the Bootstrap Action page.Log in to the MRS console.In the left navigation pane, choose Clusters > Active ", @@ -2210,8 +2246,8 @@ "title":"View Execution Records", "uri":"mrs_01_0415.html", "doc_type":"usermanual", - "p_code":"243", - "code":"246" + "p_code":"247", + "code":"250" }, { "desc":"Add a bootstrap action.This operation applies to clusters earlier than MRS 3.x.", @@ -2219,8 +2255,8 @@ "title":"Adding a Bootstrap Action", "uri":"mrs_01_0416.html", "doc_type":"usermanual", - "p_code":"243", - "code":"247" + "p_code":"247", + "code":"251" }, { "desc":"Modify an existing bootstrap action on an MRS cluster.", @@ -2228,8 +2264,8 @@ "title":"Modifying a Bootstrap Action", "uri":"mrs_01_24566.html", "doc_type":"usermanual", - "p_code":"243", - "code":"248" + "p_code":"247", + "code":"252" }, { "desc":"Delete a bootstrap action on an MRS cluster.", @@ -2237,8 +2273,8 @@ "title":"Deleting a Bootstrap Action", "uri":"mrs_01_24567.html", "doc_type":"usermanual", - "p_code":"243", - "code":"249" + "p_code":"247", + "code":"253" }, { "desc":"Zeppelin is a web-based notebook that supports interactive data analysis. For more information, visit the Zeppelin official website at http://zeppelin.apache.org/.This sa", @@ -2246,8 +2282,8 @@ "title":"Sample Scripts", "uri":"mrs_01_0418.html", "doc_type":"usermanual", - "p_code":"243", - "code":"250" + "p_code":"247", + "code":"254" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2256,7 +2292,7 @@ "uri":"mrs_01_0088.html", "doc_type":"usermanual", "p_code":"", - "code":"251" + "code":"255" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2264,8 +2300,8 @@ "title":"Installing a Client", "uri":"mrs_01_24212.html", "doc_type":"usermanual", - "p_code":"251", - "code":"252" + "p_code":"255", + "code":"256" }, { "desc":"This section describes how to install clients of all services (excluding Flume) in an MRS cluster. For details about how to install the Flume client, see Installing the F", @@ -2273,8 +2309,8 @@ "title":"Installing a Client (Version 3.x or Later)", "uri":"mrs_01_0090.html", "doc_type":"usermanual", - "p_code":"252", - "code":"253" + "p_code":"256", + "code":"257" }, { "desc":"An MRS client is required. The MRS cluster client can be installed on the Master or Core node in the cluster or on a node outside the cluster.After a cluster of versions ", @@ -2282,8 +2318,8 @@ "title":"Installing a Client (Versions Earlier Than 3.x)", "uri":"mrs_01_0091.html", "doc_type":"usermanual", - "p_code":"252", - "code":"254" + "p_code":"256", + "code":"258" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2291,8 +2327,8 @@ "title":"Updating a Client", "uri":"mrs_01_24213.html", "doc_type":"usermanual", - "p_code":"251", - "code":"255" + "p_code":"255", + "code":"259" }, { "desc":"A cluster provides a client for you to connect to a server, view task results, or manage data. If you modify service configuration parameters on Manager and restart the s", @@ -2300,8 +2336,8 @@ "title":"Updating a Client (Version 3.x or Later)", "uri":"mrs_01_24209.html", "doc_type":"usermanual", - "p_code":"255", - "code":"256" + "p_code":"259", + "code":"260" }, { "desc":"This section applies to clusters of versions earlier than MRS 3.x. For MRS 3.x or later, see Updating a Client (Version 3.x or Later).ScenarioAn MRS cluster provides a cl", @@ -2309,8 +2345,8 @@ "title":"Updating a Client (Versions Earlier Than 3.x)", "uri":"mrs_01_0089.html", "doc_type":"usermanual", - "p_code":"255", - "code":"257" + "p_code":"259", + "code":"261" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2318,8 +2354,8 @@ "title":"Using the Client of Each Component", "uri":"mrs_01_24183.html", "doc_type":"usermanual", - "p_code":"251", - "code":"258" + "p_code":"255", + "code":"262" }, { "desc":"ClickHouse is a column-based database oriented to online analysis and processing. It supports SQL query and provides good query performance. The aggregation analysis and ", @@ -2327,8 +2363,8 @@ "title":"Using a ClickHouse Client", "uri":"mrs_01_24184.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"259" + "p_code":"262", + "code":"263" }, { "desc":"This section describes how to use Flink to run wordcount jobs.Flink has been installed in an MRS cluster.The cluster runs properly and the client has been correctly insta", @@ -2336,8 +2372,8 @@ "title":"Using a Flink Client", "uri":"mrs_01_24185.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"260" + "p_code":"262", + "code":"264" }, { "desc":"You can use Flume to import collected log information to Kafka.A streaming cluster that contains components such as Flume and Kafka and has Kerberos authentication enable", @@ -2345,8 +2381,8 @@ "title":"Using a Flume Client", "uri":"mrs_01_24186.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"261" + "p_code":"262", + "code":"265" }, { "desc":"This section describes how to use the HBase client in an O&M scenario or a service scenario.The client has been installed. For example, the installation directory is /opt", @@ -2354,8 +2390,8 @@ "title":"Using an HBase Client", "uri":"mrs_01_24187.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"262" + "p_code":"262", + "code":"266" }, { "desc":"This section describes how to use the HDFS client in an O&M scenario or service scenario.The client has been installed.For example, the installation directory is /opt/had", @@ -2363,8 +2399,8 @@ "title":"Using an HDFS Client", "uri":"mrs_01_24188.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"263" + "p_code":"262", + "code":"267" }, { "desc":"This section guides users to use a Hive client in an O&M or service scenario.The client has been installed. For example, the client is installed in the /opt/hadoopclient ", @@ -2372,8 +2408,8 @@ "title":"Using a Hive Client", "uri":"mrs_01_24189.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"264" + "p_code":"262", + "code":"268" }, { "desc":"You can create, query, and delete topics on a cluster client.The client has been installed. For example, the client is installed in the /opt/hadoopclient directory. The c", @@ -2381,8 +2417,8 @@ "title":"Using a Kafka Client", "uri":"mrs_01_24191.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"265" + "p_code":"262", + "code":"269" }, { "desc":"This section describes how to use the Oozie client in an O&M scenario or service scenario.The client has been installed. For example, the installation directory is /opt/c", @@ -2390,8 +2426,8 @@ "title":"Using the Oozie Client", "uri":"mrs_01_24193.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"266" + "p_code":"262", + "code":"270" }, { "desc":"This section describes how to use the Storm client in an O&M scenario or service scenario.You have installed the client. For example, the installation directory is /opt/h", @@ -2399,8 +2435,8 @@ "title":"Using a Storm Client", "uri":"mrs_01_24194.html", "doc_type":"usermanual", - "p_code":"258", - "code":"267" + "p_code":"262", + "code":"271" }, { "desc":"This section guides users to use a Yarn client in an O&M or service scenario.The client has been installed.For example, the installation directory is /opt/hadoopclient. T", @@ -2408,8 +2444,8 @@ "title":"Using a Yarn Client", "uri":"mrs_01_24196.html", "doc_type":"cmpntguide", - "p_code":"258", - "code":"268" + "p_code":"262", + "code":"272" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2418,7 +2454,7 @@ "uri":"mrs_01_0440.html", "doc_type":"usermanual", "p_code":"", - "code":"269" + "code":"273" }, { "desc":"In scenarios that require large storage capacity and elastic compute resources, MRS enables you to store data in OBS and use an MRS cluster for data computing only. In th", @@ -2426,8 +2462,8 @@ "title":"Introduction to Storage-Compute Decoupling", "uri":"mrs_01_0467.html", "doc_type":"usermanual", - "p_code":"269", - "code":"270" + "p_code":"273", + "code":"274" }, { "desc":"MRS allows you to store data in OBS and use an MRS cluster for data computing only. In this way, storage and compute are separated. You can create an IAM agency, which en", @@ -2435,8 +2471,8 @@ "title":"Configuring a Storage-Compute Decoupled Cluster (Agency)", "uri":"mrs_01_0768.html", "doc_type":"usermanual", - "p_code":"269", - "code":"271" + "p_code":"273", + "code":"275" }, { "desc":"In MRS 1.9.2 or later, OBS can be interconnected with MRS using obs://. Currently, Hadoop, Hive, Spark, Presto, and Flink are supported. HBase cannot use obs:// to interc", @@ -2444,8 +2480,8 @@ "title":"Configuring a Storage-Compute Decoupled Cluster (AK/SK)", "uri":"mrs_01_0468.html", "doc_type":"usermanual", - "p_code":"269", - "code":"272" + "p_code":"273", + "code":"276" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2453,8 +2489,8 @@ "title":"Using a Storage-Compute Decoupled Cluster", "uri":"mrs_01_0643.html", "doc_type":"usermanual", - "p_code":"269", - "code":"273" + "p_code":"273", + "code":"277" }, { "desc":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", @@ -2462,8 +2498,8 @@ "title":"Interconnecting Flink with OBS", "uri":"mrs_01_1288.html", "doc_type":"usermanual", - "p_code":"273", - "code":"274" + "p_code":"277", + "code":"278" }, { "desc":"This section applies to MRS 3.x or later.Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to C", @@ -2471,8 +2507,8 @@ "title":"Interconnecting Flume with OBS", "uri":"en-us_topic_0000001349137409.html", "doc_type":"usermanual", - "p_code":"273", - "code":"275" + "p_code":"277", + "code":"279" }, { "desc":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", @@ -2480,8 +2516,8 @@ "title":"Interconnecting HDFS with OBS", "uri":"mrs_01_1292.html", "doc_type":"usermanual", - "p_code":"273", - "code":"276" + "p_code":"277", + "code":"280" }, { "desc":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", @@ -2489,8 +2525,8 @@ "title":"Interconnecting Hive with OBS", "uri":"mrs_01_1286.html", "doc_type":"usermanual", - "p_code":"273", - "code":"277" + "p_code":"277", + "code":"281" }, { "desc":"Before performing the following operations, ensure that you have configured a storage-compute decoupled cluster by referring to Configuring a Storage-Compute Decoupled Cl", @@ -2498,8 +2534,8 @@ "title":"Interconnecting MapReduce with OBS", "uri":"mrs_01_0617.html", "doc_type":"usermanual", - "p_code":"273", - "code":"278" + "p_code":"277", + "code":"282" }, { "desc":"The OBS file system can be interconnected with Spark2x after an MRS cluster is installed.Before performing the following operations, ensure that you have configured a sto", @@ -2507,8 +2543,8 @@ "title":"Interconnecting Spark2x with OBS", "uri":"mrs_01_1289.html", "doc_type":"usermanual", - "p_code":"273", - "code":"279" + "p_code":"277", + "code":"283" }, { "desc":"source /opt/client/bigdata_envsqoop export --connect jdbc:mysql://10.100.231.134:3306/test --username root --password xxxxxx --table component13 -export-dir hdfs://haclu", @@ -2516,8 +2552,8 @@ "title":"Interconnecting Sqoop with External Storage Systems", "uri":"mrs_01_24294.html", "doc_type":"usermanual", - "p_code":"273", - "code":"280" + "p_code":"277", + "code":"284" }, { "desc":"source ${client_home}/bigdata_envsource ${client_home}/Hudi/component_envvim ${client_home}/Hudi/hudi/conf/hdfs-site.xmlkinit Usernameimport org.apache.hudi.QuickstartUti", @@ -2525,8 +2561,8 @@ "title":"Interconnecting Hudi with OBS", "uri":"mrs_01_24171.html", "doc_type":"usermanual", - "p_code":"273", - "code":"281" + "p_code":"277", + "code":"285" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2535,7 +2571,7 @@ "uri":"mrs_01_0644.html", "doc_type":"usermanual", "p_code":"", - "code":"282" + "code":"286" }, { "desc":"Web UIs of different components are created and hosted on the Master or Core nodes in the MRS cluster by default. You can view information about the components on these w", @@ -2543,8 +2579,8 @@ "title":"Web UIs of Open Source Components", "uri":"mrs_01_0362.html", "doc_type":"usermanual", - "p_code":"282", - "code":"283" + "p_code":"286", + "code":"287" }, { "desc":"The protocol type of all ports in the table is TCP (for MRS 1.6.3 or later).The protocol type of all ports in the table is TCP (for MRS 1.7.0 or later).The protocol type ", @@ -2552,8 +2588,8 @@ "title":"List of Open Source Component Ports", "uri":"mrs_01_0504.html", "doc_type":"usermanual", - "p_code":"282", - "code":"284" + "p_code":"286", + "code":"288" }, { "desc":"MRS allows you to access MRS clusters using Direct Connect. Direct Connect is a high-speed, low-latency, stable, and secure dedicated network connection that connects you", @@ -2561,8 +2597,8 @@ "title":"Access Through Direct Connect", "uri":"mrs_01_0645.html", "doc_type":"usermanual", - "p_code":"282", - "code":"285" + "p_code":"286", + "code":"289" }, { "desc":"You can bind an EIP to a cluster to access the web UIs of the open-source components managed in the MRS cluster. This method is simple and easy to use and is recommended ", @@ -2570,8 +2606,8 @@ "title":"EIP-based Access", "uri":"mrs_01_0646.html", "doc_type":"usermanual", - "p_code":"282", - "code":"286" + "p_code":"286", + "code":"290" }, { "desc":"MRS allows you to access the web UIs of open-source components through a Windows ECS. This method is complex and is recommended for MRS clusters that do not support the E", @@ -2579,8 +2615,8 @@ "title":"Access Using a Windows ECS", "uri":"mrs_01_0647.html", "doc_type":"usermanual", - "p_code":"282", - "code":"287" + "p_code":"286", + "code":"291" }, { "desc":"Users and an MRS cluster are in different networks. As a result, an SSH channel needs to be created to send users' requests for accessing websites to the MRS cluster and ", @@ -2588,8 +2624,8 @@ "title":"Creating an SSH Channel for Connecting to an MRS Cluster and Configuring the Browser", "uri":"mrs_01_0363.html", "doc_type":"usermanual", - "p_code":"282", - "code":"288" + "p_code":"286", + "code":"292" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2598,34 +2634,34 @@ "uri":"mrs_01_0128.html", "doc_type":"usermanual", "p_code":"", - "code":"289" + "code":"293" }, { - "desc":"In MRS 3.x or later, FusionInsight Manager is used to monitor, configure, and manage clusters. After the cluster is installed, you can use the account to log in to Fusion", + "desc":"In an MRS cluster of version 3.x, MRS Manager is used to monitor, configure, and manage clusters. After the cluster is installed, you can use the account to log in to MRS", "product_code":"mrs", - "title":"Accessing FusionInsight Manager (MRS 3.x or Later)", + "title":"Accessing MRS Manager", "uri":"mrs_01_0129.html", "doc_type":"usermanual", - "p_code":"289", - "code":"290" + "p_code":"293", + "code":"294" }, { - "desc":"MRS uses FusionInsight Manager to monitor, configure, and manage clusters. You can access FusionInsight Manager by clicking Access Manager on the Dashboard tab page of yo", + "desc":"In an MRS cluster of version 2.x and earlier, MRS uses MRS Manager to monitor, configure, and manage clusters. You can access MRS Manager by clicking Access Manager on th", "product_code":"mrs", - "title":"Accessing MRS Manager MRS 2.1.0 or Earlier)", + "title":"Accessing MRS Manager (MRS 2.x or Earlier)", "uri":"mrs_01_0102.html", "doc_type":"usermanual", - "p_code":"289", - "code":"291" + "p_code":"293", + "code":"295" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"mrs", - "title":"FusionInsight Manager Operation Guide (Applicable to 3.x)", + "title":"MRS Manager Operation Guide (Applicable to 3.x)", "uri":"mrs_01_0606.html", "doc_type":"usermanual", "p_code":"", - "code":"292" + "code":"296" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2633,35 +2669,35 @@ "title":"Getting Started", "uri":"admin_guide_000001.html", "doc_type":"usermanual", - "p_code":"292", - "code":"293" + "p_code":"296", + "code":"297" }, { "desc":"MRS allows you to manage and analyze massive amounts of structured and unstructured data for rapid data mining. Open source components have complex structures and therefo", "product_code":"mrs", - "title":"FusionInsight Manager Introduction", + "title":"MRS Manager Introduction", "uri":"admin_guide_000002.html", "doc_type":"usermanual", - "p_code":"293", - "code":"294" + "p_code":"297", + "code":"298" }, { - "desc":"By viewing the FusionInsight Manager version, you can prepare for system upgrade and routine maintenance.Using the GUI:Log in to FusionInsight Manager. On the home page, ", + "desc":"By viewing the MRS Manager version, you can prepare for system upgrade and routine maintenance.Using the GUI:Log in to MRS Manager. On the home page, click in the upper ", "product_code":"mrs", - "title":"Querying the FusionInsight Manager Version", + "title":"Querying the MRS Manager Version", "uri":"admin_guide_000003.html", "doc_type":"usermanual", - "p_code":"293", - "code":"295" + "p_code":"297", + "code":"299" }, { - "desc":"Log in to FusionInsight Manager using an account.The password must:Contain 8 to 64 characters.Contain at least four types of the following characters: uppercase letters, ", + "desc":"Log in to MRS Manager using an account.The password must:Contain 8 to 64 characters.Contain at least four types of the following characters: uppercase letters, lowercase ", "product_code":"mrs", - "title":"Logging In to FusionInsight Manager", + "title":"Logging In to MRS Manager", "uri":"admin_guide_000004.html", "doc_type":"usermanual", - "p_code":"293", - "code":"296" + "p_code":"297", + "code":"300" }, { "desc":"Some O&M operation scripts and commands need to be run or can be run only on the active management node. You can identify and log in to the active or standby management n", @@ -2669,8 +2705,8 @@ "title":"Logging In to the Management Node", "uri":"admin_guide_000005.html", "doc_type":"usermanual", - "p_code":"293", - "code":"297" + "p_code":"297", + "code":"301" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2678,26 +2714,26 @@ "title":"Home Page", "uri":"admin_guide_000006.html", "doc_type":"usermanual", - "p_code":"292", - "code":"298" + "p_code":"296", + "code":"302" }, { - "desc":"After you log in to FusionInsight Manager, Homepage is displayed by default. On this page, the Summary tab displays the service statuses and monitoring status reports of ", + "desc":"After you log in to MRS Manager, Homepage is displayed by default. On this page, the Summary tab displays the service statuses and monitoring status reports of each clust", "product_code":"mrs", "title":"Overview", "uri":"admin_guide_000007.html", "doc_type":"usermanual", - "p_code":"298", - "code":"299" + "p_code":"302", + "code":"303" }, { - "desc":"On FusionInsight Manager, you can customize monitoring items to display on the homepage and export monitoring data.The interval on the horizontal axis of the chart varies", + "desc":"On MRS Manager, you can customize monitoring items to display on the homepage and export monitoring data.The interval on the horizontal axis of the chart varies depending", "product_code":"mrs", "title":"Managing Monitoring Metric Reports", "uri":"admin_guide_000008.html", "doc_type":"usermanual", - "p_code":"298", - "code":"300" + "p_code":"302", + "code":"304" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2705,8 +2741,8 @@ "title":"Cluster", "uri":"admin_guide_000009.html", "doc_type":"usermanual", - "p_code":"292", - "code":"301" + "p_code":"296", + "code":"305" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2714,17 +2750,17 @@ "title":"Cluster Management", "uri":"admin_guide_000010.html", "doc_type":"usermanual", - "p_code":"301", - "code":"302" + "p_code":"305", + "code":"306" }, { - "desc":"Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Dashboard to view the status of the current cluster.On the Dashboard tab page, you can ", + "desc":"Log in to MRS Manager and choose Cluster > Name of the desired cluster > Dashboard to view the status of the current cluster.On the Dashboard tab page, you can start, sto", "product_code":"mrs", "title":"Overview", "uri":"admin_guide_000011.html", "doc_type":"usermanual", - "p_code":"302", - "code":"303" + "p_code":"306", + "code":"307" }, { "desc":"A rolling restart is batch restarting all services in a cluster after they are modified or upgraded without interrupting workloads.You can perform a rolling restart of a ", @@ -2732,8 +2768,8 @@ "title":"Performing a Rolling Restart of a Cluster", "uri":"admin_guide_000012.html", "doc_type":"usermanual", - "p_code":"302", - "code":"304" + "p_code":"306", + "code":"308" }, { "desc":"If a new configuration needs to be delivered to all services in the cluster, or Configuration Status of multiple services changes to Expired or Failed after a configurati", @@ -2741,8 +2777,8 @@ "title":"Managing Expired Configurations", "uri":"admin_guide_000013.html", "doc_type":"usermanual", - "p_code":"302", - "code":"305" + "p_code":"306", + "code":"309" }, { "desc":"Use the default client provided by MRS clusters to manage the cluster, run services, and perform secondary development. Before you use this client, you need to download i", @@ -2750,26 +2786,26 @@ "title":"Downloading the Client", "uri":"admin_guide_000014.html", "doc_type":"usermanual", - "p_code":"302", - "code":"306" + "p_code":"306", + "code":"310" }, { - "desc":"View basic cluster attributes on FusionInsight Manager.By default, you can view the cluster name, cluster description, product type, cluster ID, authentication mode, crea", + "desc":"View basic cluster attributes on MRS Manager.By default, you can view the cluster name, cluster description, product type, cluster ID, authentication mode, creation time,", "product_code":"mrs", "title":"Modifying Cluster Attributes", "uri":"admin_guide_000015.html", "doc_type":"usermanual", - "p_code":"302", - "code":"307" + "p_code":"306", + "code":"311" }, { - "desc":"FusionInsight Manager allows you to view the changes of service configuration parameters in a cluster with one click, helping you quickly locate faults and improve config", + "desc":"MRS Manager allows you to view the changes of service configuration parameters in a cluster with one click, helping you quickly locate faults and improve configuration ma", "product_code":"mrs", "title":"Managing Cluster Configurations", "uri":"admin_guide_000016.html", "doc_type":"usermanual", - "p_code":"302", - "code":"308" + "p_code":"306", + "code":"312" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2777,8 +2813,8 @@ "title":"Managing Static Service Pools", "uri":"admin_guide_000017.html", "doc_type":"usermanual", - "p_code":"302", - "code":"309" + "p_code":"306", + "code":"313" }, { "desc":"A cluster allocates static service resources to services Flume, HBase, HDFS, and YARN. The total volume of computing resources allocated to each service is fixed, and the", @@ -2786,17 +2822,17 @@ "title":"Static Service Resources", "uri":"admin_guide_000018.html", "doc_type":"usermanual", - "p_code":"309", - "code":"310" + "p_code":"313", + "code":"314" }, { - "desc":"You can adjust resource base on FusionInsight Manager and customize resource configuration groups if you need to control service resources used on each node in a cluster ", + "desc":"You can adjust resource base on MRS Manager and customize resource configuration groups if you need to control service resources used on each node in a cluster or the ava", "product_code":"mrs", "title":"Configuring Cluster Static Resources", "uri":"admin_guide_000019.html", "doc_type":"usermanual", - "p_code":"309", - "code":"311" + "p_code":"313", + "code":"315" }, { "desc":"The big data management platform can manage and isolate service resources that are not running on YARN using static service resource pools. The system supports time-based", @@ -2804,8 +2840,8 @@ "title":"Viewing Cluster Static Resources", "uri":"admin_guide_000020.html", "doc_type":"usermanual", - "p_code":"309", - "code":"312" + "p_code":"313", + "code":"316" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2813,35 +2849,35 @@ "title":"Managing Clients", "uri":"admin_guide_000021.html", "doc_type":"usermanual", - "p_code":"302", - "code":"313" + "p_code":"306", + "code":"317" }, { - "desc":"FusionInsight Manager supports unified management of cluster client installation information. After a user downloads and installs a client, FusionInsight Manager automati", + "desc":"MRS Manager supports unified management of cluster client installation information. After a user downloads and installs a client, MRS Manager automatically records inform", "product_code":"mrs", "title":"Managing a Client", "uri":"admin_guide_000022.html", "doc_type":"usermanual", - "p_code":"313", - "code":"314" + "p_code":"317", + "code":"318" }, { - "desc":"The client package downloaded from FusionInsight Manager contains the client batch upgrade tool. When multiple clients need to be upgraded after the cluster upgrade or sc", + "desc":"The client package downloaded from MRS Manager contains the client batch upgrade tool. When multiple clients need to be upgraded after the cluster upgrade or scale-out, y", "product_code":"mrs", "title":"Batch Upgrading Clients", "uri":"admin_guide_000023.html", "doc_type":"usermanual", - "p_code":"313", - "code":"315" + "p_code":"317", + "code":"319" }, { - "desc":"The client package downloaded from FusionInsight Manager contains the client batch upgrade tool. This tool provides the function of upgrading clients in batches and the l", + "desc":"The client package downloaded from MRS Manager contains the client batch upgrade tool. This tool provides the function of upgrading clients in batches and the lightweight", "product_code":"mrs", "title":"Updating the hosts File in Batches", "uri":"admin_guide_000024.html", "doc_type":"usermanual", - "p_code":"313", - "code":"316" + "p_code":"317", + "code":"320" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2849,17 +2885,17 @@ "title":"Managing a Service", "uri":"admin_guide_000026.html", "doc_type":"usermanual", - "p_code":"301", - "code":"317" + "p_code":"305", + "code":"321" }, { - "desc":"Log in to FusionInsight Manager. Choose Cluster, click the name of the desired cluster, and choose Services. The service management page is displayed, including the funct", + "desc":"Log in to MRS Manager. Choose Cluster, click the name of the desired cluster, and choose Services. The service management page is displayed, including the functional area", "product_code":"mrs", "title":"Overview", "uri":"admin_guide_000027.html", "doc_type":"usermanual", - "p_code":"317", - "code":"318" + "p_code":"321", + "code":"322" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2867,17 +2903,17 @@ "title":"Other Service Management Operations", "uri":"admin_guide_000029.html", "doc_type":"usermanual", - "p_code":"317", - "code":"319" + "p_code":"321", + "code":"323" }, { - "desc":"Log in to FusionInsight Manager and choose Cluster >Name of the desired cluster > Services. In the service list, click the specified service name to go to the service det", + "desc":"Log in to MRS Manager and choose Cluster >Name of the desired cluster > Services. In the service list, click the specified service name to go to the service details page,", "product_code":"mrs", "title":"Service Details Page", "uri":"admin_guide_000030.html", "doc_type":"usermanual", - "p_code":"319", - "code":"320" + "p_code":"323", + "code":"324" }, { "desc":"Some service roles are deployed in active/standby mode. If the active instance needs to be maintained and cannot provide services, or other maintenance is required, you c", @@ -2885,26 +2921,26 @@ "title":"Performing Active/Standby Switchover of a Role Instance", "uri":"admin_guide_000031.html", "doc_type":"usermanual", - "p_code":"319", - "code":"321" + "p_code":"323", + "code":"325" }, { - "desc":"Log in to FusionInsight Manager, choose Cluster >Name of the desired cluster > Services, and click Resource. The resource monitoring page is displayed.Some services in th", + "desc":"Log in to MRS Manager, choose Cluster >Name of the desired cluster > Services, and click Resource. The resource monitoring page is displayed.Some services in the cluster ", "product_code":"mrs", "title":"Resource Monitoring", "uri":"admin_guide_000032.html", "doc_type":"usermanual", - "p_code":"319", - "code":"322" + "p_code":"323", + "code":"326" }, { - "desc":"To meet actual service requirements, the cluster administrator can collect stack information about a specified role or instance on FusionInsight Manager, save the informa", + "desc":"To meet actual service requirements, the cluster administrator can collect stack information about a specified role or instance on MRS Manager, save the information to a ", "product_code":"mrs", "title":"Collecting Stack Information", "uri":"admin_guide_000033.html", "doc_type":"usermanual", - "p_code":"319", - "code":"323" + "p_code":"323", + "code":"327" }, { "desc":"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 ", @@ -2912,8 +2948,8 @@ "title":"Switching Ranger Authentication", "uri":"admin_guide_000415.html", "doc_type":"usermanual", - "p_code":"319", - "code":"324" + "p_code":"323", + "code":"328" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2921,26 +2957,26 @@ "title":"Service Configuration", "uri":"admin_guide_000034.html", "doc_type":"usermanual", - "p_code":"317", - "code":"325" + "p_code":"321", + "code":"329" }, { - "desc":"To meet actual service requirements, cluster administrators can quickly view and modify default service configurations on FusionInsight Manager. Configure parameters base", + "desc":"To meet actual service requirements, cluster administrators can quickly view and modify default service configurations on MRS Manager. Configure parameters based on the i", "product_code":"mrs", "title":"Modifying Service Configuration Parameters", "uri":"admin_guide_000035.html", "doc_type":"usermanual", - "p_code":"325", - "code":"326" + "p_code":"329", + "code":"330" }, { - "desc":"All open source parameters can be configured for all MRS cluster components. Parameters used in some key application scenarios can be modified on FusionInsight Manager, a", + "desc":"All open source parameters can be configured for all MRS cluster components. Parameters used in some key application scenarios can be modified on MRS Manager, and some pa", "product_code":"mrs", "title":"Modifying Custom Configuration Parameters of a Service", "uri":"admin_guide_000036.html", "doc_type":"usermanual", - "p_code":"325", - "code":"327" + "p_code":"329", + "code":"331" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2948,17 +2984,17 @@ "title":"Instance Management", "uri":"admin_guide_000037.html", "doc_type":"usermanual", - "p_code":"301", - "code":"328" + "p_code":"305", + "code":"332" }, { - "desc":"Log in to FusionInsight Manager, click Cluster, click the name of the desired cluster, and choose Service > KrbServer. On the displayed page, click Instance. The displaye", + "desc":"Log in to MRS Manager, click Cluster, click the name of the desired cluster, and choose Service > KrbServer. On the displayed page, click Instance. The displayed instance", "product_code":"mrs", "title":"Overview", "uri":"admin_guide_000038.html", "doc_type":"usermanual", - "p_code":"328", - "code":"329" + "p_code":"332", + "code":"333" }, { "desc":"Some role instances provide services for external services in distributed and parallel mode. Services independently store information about whether each instance can be u", @@ -2966,8 +3002,8 @@ "title":"Decommissioning and Recommissioning an Instance", "uri":"admin_guide_000040.html", "doc_type":"usermanual", - "p_code":"328", - "code":"330" + "p_code":"332", + "code":"334" }, { "desc":"Configuration parameters of each role instance can be modified. In the scenario where instances are migrated to a new cluster or the service is redeployed, the cluster ad", @@ -2975,17 +3011,17 @@ "title":"Managing Instance Configurations", "uri":"admin_guide_000043.html", "doc_type":"usermanual", - "p_code":"328", - "code":"331" + "p_code":"332", + "code":"335" }, { - "desc":"FusionInsight Manager allows O&M personnel to view the content configuration files such as environment variables and role configurations of the instance node on the manag", + "desc":"MRS Manager allows O&M personnel to view the content configuration files such as environment variables and role configurations of the instance node on the management page", "product_code":"mrs", "title":"Viewing the Instance Configuration File", "uri":"admin_guide_000044.html", "doc_type":"usermanual", - "p_code":"328", - "code":"332" + "p_code":"332", + "code":"336" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2993,35 +3029,35 @@ "title":"Instance Group", "uri":"admin_guide_000045.html", "doc_type":"usermanual", - "p_code":"328", - "code":"333" + "p_code":"332", + "code":"337" }, { - "desc":"Instance groups can be managed on FusionInsight Manager. That is, you can group multiple instances in the same role based on a specified principle, such as the nodes with", + "desc":"Instance groups can be managed on MRS Manager. That is, you can group multiple instances in the same role based on a specified principle, such as the nodes with the same ", "product_code":"mrs", "title":"Managing Instance Groups", "uri":"admin_guide_000046.html", "doc_type":"usermanual", - "p_code":"333", - "code":"334" + "p_code":"337", + "code":"338" }, { - "desc":"The cluster administrator can view the instance group of a specified service on FusionInsight Manager.To move an instance from an instance group to another, perform the f", + "desc":"The cluster administrator can view the instance group of a specified service on MRS Manager.To move an instance from an instance group to another, perform the following o", "product_code":"mrs", "title":"Viewing Information About an Instance Group", "uri":"admin_guide_000047.html", "doc_type":"usermanual", - "p_code":"333", - "code":"335" + "p_code":"337", + "code":"339" }, { - "desc":"In a large cluster, users can configure parameters for multiple instances in batches by configuring the related instance groups on FusionInsight Manager, reducing redunda", + "desc":"In a large cluster, users can configure parameters for multiple instances in batches by configuring the related instance groups on MRS Manager, reducing redundant instanc", "product_code":"mrs", "title":"Configuring Instantiation Group Parameters", "uri":"admin_guide_000048.html", "doc_type":"usermanual", - "p_code":"333", - "code":"336" + "p_code":"337", + "code":"340" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3029,8 +3065,8 @@ "title":"Hosts", "uri":"admin_guide_000049.html", "doc_type":"usermanual", - "p_code":"292", - "code":"337" + "p_code":"296", + "code":"341" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3038,35 +3074,35 @@ "title":"Host Management Page", "uri":"admin_guide_000050.html", "doc_type":"usermanual", - "p_code":"337", - "code":"338" + "p_code":"341", + "code":"342" }, { - "desc":"Log in to FusionInsight Manager, click Hosts, and the host list is displayed on the host management page. You can view the host list and basic information of each host.Yo", + "desc":"Log in to MRS Manager, click Hosts, and the host list is displayed on the host management page. You can view the host list and basic information of each host.You can swit", "product_code":"mrs", "title":"Viewing the Host List", "uri":"admin_guide_000051.html", "doc_type":"usermanual", - "p_code":"338", - "code":"339" + "p_code":"342", + "code":"343" }, { - "desc":"Log in to FusionInsight Manager, click Hosts, and click a host name in the host list. The host details page contains the basic information area, disk status area, role li", + "desc":"Log in to MRS Manager, click Hosts, and click a host name in the host list. The host details page contains the basic information area, disk status area, role list area, a", "product_code":"mrs", "title":"Viewing the Host Dashboard", "uri":"admin_guide_000052.html", "doc_type":"usermanual", - "p_code":"338", - "code":"340" + "p_code":"342", + "code":"344" }, { - "desc":"Log in to FusionInsight Manager, click Hosts, and click the specified host name in the host list. On the host details page, click the Process and Resource tabs.On the Pro", + "desc":"Log in to MRS Manager, click Hosts, and click the specified host name in the host list. On the host details page, click the Process and Resource tabs.On the Process tab p", "product_code":"mrs", "title":"Checking Host Processes and Resources", "uri":"admin_guide_000053.html", "doc_type":"usermanual", - "p_code":"338", - "code":"341" + "p_code":"342", + "code":"345" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3074,8 +3110,8 @@ "title":"Host Maintenance Operations", "uri":"admin_guide_000054.html", "doc_type":"usermanual", - "p_code":"337", - "code":"342" + "p_code":"341", + "code":"346" }, { "desc":"If a host is faulty, you may need to stop all the roles on the host and perform maintenance check on the host. After the host fault is rectified, start all roles running ", @@ -3083,8 +3119,8 @@ "title":"Starting and Stopping All Instances on a Host", "uri":"admin_guide_000056.html", "doc_type":"usermanual", - "p_code":"342", - "code":"343" + "p_code":"346", + "code":"347" }, { "desc":"If the running status of a host is not Normal, you can perform health checks on the host to check whether some basic functions are abnormal. During routine O&M, you can p", @@ -3092,8 +3128,8 @@ "title":"Performing a Host Health Check", "uri":"admin_guide_000057.html", "doc_type":"usermanual", - "p_code":"342", - "code":"344" + "p_code":"346", + "code":"348" }, { "desc":"All hosts in a large cluster are usually deployed on multiple racks. Hosts on different racks communicate with each other through switches. The network bandwidth between ", @@ -3101,8 +3137,8 @@ "title":"Configuring Racks for Hosts", "uri":"admin_guide_000058.html", "doc_type":"usermanual", - "p_code":"342", - "code":"345" + "p_code":"346", + "code":"349" }, { "desc":"If a host is abnormal or faulty and cannot provide services or affects the cluster performance, you can remove the host from the available node in the cluster temporarily", @@ -3110,17 +3146,17 @@ "title":"Isolating a Host", "uri":"admin_guide_000059.html", "doc_type":"usermanual", - "p_code":"342", - "code":"346" + "p_code":"346", + "code":"350" }, { - "desc":"Administrators can export information about all hosts on FusionInsight Manager.", + "desc":"Administrators can export information about all hosts on MRS Manager.", "product_code":"mrs", "title":"Exporting Host Information", "uri":"admin_guide_000062.html", "doc_type":"usermanual", - "p_code":"342", - "code":"347" + "p_code":"346", + "code":"351" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3128,44 +3164,44 @@ "title":"Resource Overview", "uri":"admin_guide_000063.html", "doc_type":"usermanual", - "p_code":"337", - "code":"348" + "p_code":"341", + "code":"352" }, { - "desc":"Log in to FusionInsight Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Distribution tab to view resource distrib", + "desc":"Log in to MRS Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Distribution tab to view resource distribution of e", "product_code":"mrs", "title":"Distribution", "uri":"admin_guide_000064.html", "doc_type":"usermanual", - "p_code":"348", - "code":"349" + "p_code":"352", + "code":"353" }, { - "desc":"Log in to FusionInsight and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Trend tab to view resource trends of all clusters", + "desc":"Log in to MRS and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Trend tab to view resource trends of all clusters or a sing", "product_code":"mrs", "title":"Trend", "uri":"admin_guide_000065.html", "doc_type":"usermanual", - "p_code":"348", - "code":"350" + "p_code":"352", + "code":"354" }, { - "desc":"Log in to FusionInsight Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Cluster tab to view resource monitoring o", + "desc":"Log in to MRS Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Cluster tab to view resource monitoring of all clus", "product_code":"mrs", "title":"Cluster", "uri":"admin_guide_000066.html", "doc_type":"usermanual", - "p_code":"348", - "code":"351" + "p_code":"352", + "code":"355" }, { - "desc":"Log in to FusionInsight Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Host tab to view host resource overview, ", + "desc":"Log in to MRS Manager and choose Hosts > Resource Overview. On the Resource Overview page that is displayed, click the Host tab to view host resource overview, including ", "product_code":"mrs", "title":"Host", "uri":"admin_guide_000067.html", "doc_type":"usermanual", - "p_code":"348", - "code":"352" + "p_code":"352", + "code":"356" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3173,8 +3209,8 @@ "title":"O&M", "uri":"admin_guide_000068.html", "doc_type":"usermanual", - "p_code":"292", - "code":"353" + "p_code":"296", + "code":"357" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3182,35 +3218,35 @@ "title":"Alarms", "uri":"admin_guide_000069.html", "doc_type":"usermanual", - "p_code":"353", - "code":"354" + "p_code":"357", + "code":"358" }, { - "desc":"Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. You can view information about alarms reported by all clusters, including the alarm name, ID, severity, a", + "desc":"Log in to MRS Manager and choose O&M > Alarm > Alarms. You can view information about alarms reported by all clusters, including the alarm name, ID, severity, and generat", "product_code":"mrs", "title":"Overview of Alarms and Events", "uri":"admin_guide_000070.html", "doc_type":"usermanual", - "p_code":"354", - "code":"355" + "p_code":"358", + "code":"359" }, { - "desc":"You can configure monitoring indicator thresholds to monitor the health status of indicators on FusionInsight Manager. If abnormal data occurs and the preset conditions a", + "desc":"You can configure monitoring indicator thresholds to monitor the health status of indicators on MRS Manager. If abnormal data occurs and the preset conditions are met, th", "product_code":"mrs", "title":"Configuring the Threshold", "uri":"admin_guide_000071.html", "doc_type":"usermanual", - "p_code":"354", - "code":"356" + "p_code":"358", + "code":"360" }, { - "desc":"If you do not want FusionInsight Manager to report specified alarms in the following scenarios, you can manually mask the alarms.Some unimportant alarms and minor alarms ", + "desc":"If you do not want MRS Manager to report specified alarms in the following scenarios, you can manually mask the alarms.Some unimportant alarms and minor alarms need to be", "product_code":"mrs", "title":"Configuring the Alarm Masking Status", "uri":"admin_guide_000072.html", "doc_type":"usermanual", - "p_code":"354", - "code":"357" + "p_code":"358", + "code":"361" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3218,26 +3254,26 @@ "title":"Log", "uri":"admin_guide_000073.html", "doc_type":"usermanual", - "p_code":"353", - "code":"358" + "p_code":"357", + "code":"362" }, { - "desc":"FusionInsight Manager allows you to search for logs online and view the log content of components to locate faults.You can click Stop to forcibly stop the search. You can", + "desc":"MRS Manager allows you to search for logs online and view the log content of components to locate faults.You can click Stop to forcibly stop the search. You can view the ", "product_code":"mrs", "title":"Log Online Search", "uri":"admin_guide_000074.html", "doc_type":"usermanual", - "p_code":"358", - "code":"359" + "p_code":"362", + "code":"363" }, { - "desc":"FusionInsight Manager allows you to batch export logs generated on all instances of each service.Service: Click and select a service.Host: Enter the IP address of the ho", + "desc":"MRS Manager allows you to batch export logs generated on all instances of each service.Service: Click and select a service.Host: Enter the IP address of the host where t", "product_code":"mrs", "title":"Log Download", "uri":"admin_guide_000075.html", "doc_type":"usermanual", - "p_code":"358", - "code":"360" + "p_code":"362", + "code":"364" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3245,8 +3281,8 @@ "title":"Perform a Health Check", "uri":"admin_guide_000076.html", "doc_type":"usermanual", - "p_code":"353", - "code":"361" + "p_code":"357", + "code":"365" }, { "desc":"Administrators can view all health check tasks in the health check management center to check whether the cluster is affected after the modification.By default, all saved", @@ -3254,17 +3290,17 @@ "title":"Viewing a Health Check Task", "uri":"admin_guide_000077.html", "doc_type":"usermanual", - "p_code":"361", - "code":"362" + "p_code":"365", + "code":"366" }, { - "desc":"FusionInsight Manager allows you to download and delete health check reports.", + "desc":"MRS Manager allows you to download and delete health check reports.", "product_code":"mrs", "title":"Managing Health Check Reports", "uri":"admin_guide_000078.html", "doc_type":"usermanual", - "p_code":"361", - "code":"363" + "p_code":"365", + "code":"367" }, { "desc":"Administrators can enable automatic health check to reduce manual operation time. By default, the automatic health check checks the entire cluster.Periodic Health Check i", @@ -3272,8 +3308,8 @@ "title":"Modifying Health Check Configuration", "uri":"admin_guide_000079.html", "doc_type":"usermanual", - "p_code":"361", - "code":"364" + "p_code":"365", + "code":"368" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3281,35 +3317,35 @@ "title":"Configuring Backup and Backup Restoration", "uri":"admin_guide_000080.html", "doc_type":"usermanual", - "p_code":"353", - "code":"365" + "p_code":"357", + "code":"369" }, { - "desc":"You can create backup tasks on FusionInsight Manager. Executing backup tasks backs up related data.Metadata and service data can be backed up.For details about how to bac", + "desc":"You can create backup tasks on MRS Manager. Executing backup tasks backs up related data.Metadata and service data can be backed up.For details about how to back up data ", "product_code":"mrs", "title":"Creating a Backup Task", "uri":"admin_guide_000081.html", "doc_type":"usermanual", - "p_code":"365", - "code":"366" + "p_code":"369", + "code":"370" }, { - "desc":"You can create a backup restoration task on FusionInsight Manager. After the restoration task is executed, the specified backup data is restored to the cluster.Metadata a", + "desc":"You can create a backup restoration task on MRS Manager. After the restoration task is executed, the specified backup data is restored to the cluster.Metadata and service", "product_code":"mrs", "title":"Creating a Backup Restoration Task", "uri":"admin_guide_000082.html", "doc_type":"usermanual", - "p_code":"365", - "code":"367" + "p_code":"369", + "code":"371" }, { - "desc":"You can also maintain and manage backup restoration tasks on FusionInsight Manager.", + "desc":"You can also maintain and manage backup restoration tasks on MRS Manager.", "product_code":"mrs", "title":"Managing Backup and Backup Restoration Tasks", "uri":"admin_guide_000083.html", "doc_type":"usermanual", - "p_code":"365", - "code":"368" + "p_code":"369", + "code":"372" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3317,8 +3353,8 @@ "title":"Audit", "uri":"admin_guide_000084.html", "doc_type":"usermanual", - "p_code":"292", - "code":"369" + "p_code":"296", + "code":"373" }, { "desc":"The Audit page displays the user operations on Manager. On this page, administrators can view historical user operations on Manager. For details about the audit informati", @@ -3326,17 +3362,17 @@ "title":"Overview", "uri":"admin_guide_000085.html", "doc_type":"usermanual", - "p_code":"369", - "code":"370" + "p_code":"373", + "code":"374" }, { - "desc":"The audit logs of FusionInsight Manager are stored in the database by default. If the audit logs are retained for a long time, the disk space of the data directory may be", + "desc":"The audit logs of MRS Manager are stored in the database by default. If the audit logs are retained for a long time, the disk space of the data directory may be insuffici", "product_code":"mrs", "title":"Configuring Audit Log Dumping", "uri":"admin_guide_000086.html", "doc_type":"usermanual", - "p_code":"369", - "code":"371" + "p_code":"373", + "code":"375" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3344,8 +3380,8 @@ "title":"Tenant Resources", "uri":"admin_guide_000087.html", "doc_type":"usermanual", - "p_code":"292", - "code":"372" + "p_code":"296", + "code":"376" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3353,8 +3389,8 @@ "title":"Multi-Tenancy", "uri":"admin_guide_000088.html", "doc_type":"usermanual", - "p_code":"372", - "code":"373" + "p_code":"376", + "code":"377" }, { "desc":"Multi-tenancy refers to multiple resource sets (a resource set is a tenant) in the MRS big data cluster and is able to allocate and schedule resources. The resources incl", @@ -3362,8 +3398,8 @@ "title":"Overview", "uri":"admin_guide_000089.html", "doc_type":"usermanual", - "p_code":"373", - "code":"374" + "p_code":"377", + "code":"378" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3371,17 +3407,17 @@ "title":"Technical Principles", "uri":"admin_guide_000090.html", "doc_type":"usermanual", - "p_code":"373", - "code":"375" + "p_code":"377", + "code":"379" }, { - "desc":"Log in to FusionInsight Manager and choose Tenant Resources > Tenant Resources Management. On the page that is displayed, you can find that FusionInsight Manager is a uni", + "desc":"Log in to MRS Manager and choose Tenant Resources > Tenant Resources Management. On the page that is displayed, you can find that MRS Manager is a unified multi-tenant ma", "product_code":"mrs", "title":"Multi-Tenant Management", "uri":"admin_guide_000091.html", "doc_type":"usermanual", - "p_code":"375", - "code":"376" + "p_code":"379", + "code":"380" }, { "desc":"The following figure shows a multi-tenant model.Table 1 describes the concepts involved in Figure 1.If a user wants to use a tenant's resources or add or delete a sub-ten", @@ -3389,8 +3425,8 @@ "title":"Multi-Tenant Model", "uri":"admin_guide_000092.html", "doc_type":"usermanual", - "p_code":"375", - "code":"377" + "p_code":"379", + "code":"381" }, { "desc":"MRS cluster resources are classified into computing resources and storage resources. The multi-tenant architecture implements resource isolation.Computing resourcesComput", @@ -3398,8 +3434,8 @@ "title":"Resource Overview", "uri":"admin_guide_000093.html", "doc_type":"usermanual", - "p_code":"375", - "code":"378" + "p_code":"379", + "code":"382" }, { "desc":"Yarn provides distributed resource management for a big data cluster. The total volume of resources allocated to Yarn can be configured. Then Yarn allocates and schedules", @@ -3407,8 +3443,8 @@ "title":"Dynamic Resources", "uri":"admin_guide_000094.html", "doc_type":"usermanual", - "p_code":"375", - "code":"379" + "p_code":"379", + "code":"383" }, { "desc":"As a distributed file storage service in a big data cluster, HDFS stores all the user data of the upper-layer applications in the big data cluster, including the data wri", @@ -3416,8 +3452,8 @@ "title":"Storage Resources", "uri":"admin_guide_000095.html", "doc_type":"usermanual", - "p_code":"375", - "code":"380" + "p_code":"379", + "code":"384" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3425,8 +3461,8 @@ "title":"Multi-Tenancy Usage", "uri":"admin_guide_000096.html", "doc_type":"usermanual", - "p_code":"373", - "code":"381" + "p_code":"377", + "code":"385" }, { "desc":"Tenants are used in resource control and service isolation scenarios. Administrators need to determine the service scenarios of cluster resources and then plan tenants.Ya", @@ -3434,8 +3470,8 @@ "title":"Overview", "uri":"admin_guide_000097.html", "doc_type":"usermanual", - "p_code":"381", - "code":"382" + "p_code":"385", + "code":"386" }, { "desc":"Administrators need to determine the service scenarios of cluster resources and then plan tenants. After that, administrators add tenants and configure dynamic resources,", @@ -3443,8 +3479,8 @@ "title":"Process Overview", "uri":"admin_guide_000098.html", "doc_type":"usermanual", - "p_code":"381", - "code":"383" + "p_code":"385", + "code":"387" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3452,8 +3488,8 @@ "title":"Using the Superior Scheduler", "uri":"admin_guide_000099.html", "doc_type":"usermanual", - "p_code":"372", - "code":"384" + "p_code":"376", + "code":"388" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3461,80 +3497,80 @@ "title":"Creating Tenants", "uri":"admin_guide_000100.html", "doc_type":"usermanual", - "p_code":"384", - "code":"385" - }, - { - "desc":"You can create tenants on FusionInsight Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based", - "product_code":"mrs", - "title":"Adding a Tenant", - "uri":"admin_guide_000101.html", - "doc_type":"usermanual", - "p_code":"385", - "code":"386" - }, - { - "desc":"You can create sub-tenants on FusionInsight Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planni", - "product_code":"mrs", - "title":"Adding a Sub-Tenant", - "uri":"admin_guide_000102.html", - "doc_type":"usermanual", - "p_code":"385", - "code":"387" - }, - { - "desc":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on FusionInsight Manager and bind the user to the ", - "product_code":"mrs", - "title":"Adding a User and Binding the User to a Tenant Role", - "uri":"admin_guide_000103.html", - "doc_type":"usermanual", - "p_code":"385", - "code":"388" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"mrs", - "title":"Managing Tenants", - "uri":"admin_guide_000104.html", - "doc_type":"usermanual", - "p_code":"384", + "p_code":"388", "code":"389" }, { - "desc":"You can manage the HDFS storage directories used by specified tenants based on service requirements on FusionInsight Manager, such as adding tenant directories, changing ", + "desc":"You can create tenants on MRS Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based on servic", "product_code":"mrs", - "title":"Managing Tenant Directories", - "uri":"admin_guide_000105.html", + "title":"Adding a Tenant", + "uri":"admin_guide_000101.html", "doc_type":"usermanual", "p_code":"389", "code":"390" }, { - "desc":"Tenant data is stored on FusionInsight Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants ", + "desc":"You can create sub-tenants on MRS Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planning and req", "product_code":"mrs", - "title":"Restoring Tenant Data", - "uri":"admin_guide_000106.html", + "title":"Adding a Sub-Tenant", + "uri":"admin_guide_000102.html", "doc_type":"usermanual", "p_code":"389", "code":"391" }, { - "desc":"You can delete tenants that are no longer used on FusionInsight Manager based on service requirements to release resources occupied by the tenants.A tenant has been added", + "desc":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on MRS Manager and bind the user to the role of th", "product_code":"mrs", - "title":"Deleting a Tenant", - "uri":"admin_guide_000107.html", + "title":"Adding a User and Binding the User to a Tenant Role", + "uri":"admin_guide_000103.html", "doc_type":"usermanual", "p_code":"389", "code":"392" }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"mrs", + "title":"Managing Tenants", + "uri":"admin_guide_000104.html", + "doc_type":"usermanual", + "p_code":"388", + "code":"393" + }, + { + "desc":"You can manage the HDFS storage directories used by specified tenants based on service requirements on MRS Manager, such as adding tenant directories, changing the quotas", + "product_code":"mrs", + "title":"Managing Tenant Directories", + "uri":"admin_guide_000105.html", + "doc_type":"usermanual", + "p_code":"393", + "code":"394" + }, + { + "desc":"Tenant data is stored on MRS Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants may become", + "product_code":"mrs", + "title":"Restoring Tenant Data", + "uri":"admin_guide_000106.html", + "doc_type":"usermanual", + "p_code":"393", + "code":"395" + }, + { + "desc":"You can delete tenants that are no longer used on MRS Manager based on service requirements to release resources occupied by the tenants.A tenant has been added.The tenan", + "product_code":"mrs", + "title":"Deleting a Tenant", + "uri":"admin_guide_000107.html", + "doc_type":"usermanual", + "p_code":"393", + "code":"396" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"mrs", "title":"Managing Resources", "uri":"admin_guide_000108.html", "doc_type":"usermanual", - "p_code":"384", - "code":"393" + "p_code":"388", + "code":"397" }, { "desc":"In a cluster, you can logically group Yarn NodeManagers into Yarn resource pools. Each NodeManager belongs to only one resource pool. You can create a custom resource poo", @@ -3542,35 +3578,35 @@ "title":"Adding a Resource Pool", "uri":"admin_guide_000109.html", "doc_type":"usermanual", - "p_code":"393", - "code":"394" + "p_code":"397", + "code":"398" }, { - "desc":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on FusionInsight Manager.Adding hosts: Select", + "desc":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on MRS Manager.Adding hosts: Select desired h", "product_code":"mrs", "title":"Modifying a Resource Pool", "uri":"admin_guide_000110.html", "doc_type":"usermanual", - "p_code":"393", - "code":"395" + "p_code":"397", + "code":"399" }, { - "desc":"If a resource pool is no longer used based on service requirements, you can delete it on FusionInsight Manager.Any queue in the cluster does not use the resource pool to ", + "desc":"If a resource pool is no longer used based on service requirements, you can delete it on MRS Manager.Any queue in the cluster does not use the resource pool to be deleted", "product_code":"mrs", "title":"Deleting a Resource Pool", "uri":"admin_guide_000111.html", "doc_type":"usermanual", - "p_code":"393", - "code":"396" + "p_code":"397", + "code":"400" }, { - "desc":"You can modify the queue configurations for a specified tenant on FusionInsight Manager.A tenant who uses the Superior scheduler has been added.You can also access the Mo", + "desc":"You can modify the queue configurations for a specified tenant on MRS Manager.A tenant who uses the Superior scheduler has been added.You can also access the Modify Queue", "product_code":"mrs", "title":"Configuring a Queue", "uri":"admin_guide_000112.html", "doc_type":"usermanual", - "p_code":"393", - "code":"397" + "p_code":"397", + "code":"401" }, { "desc":"After a resource pool is added, you can configure the capacity policy of available resources for Yarn queues so that jobs in the queues can be properly executed in the re", @@ -3578,17 +3614,17 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"admin_guide_000113.html", "doc_type":"usermanual", - "p_code":"393", - "code":"398" + "p_code":"397", + "code":"402" }, { - "desc":"You can clear the configurations of a queue on FusionInsight MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disass", + "desc":"You can clear the configurations of a queue on MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disassociated from t", "product_code":"mrs", "title":"Clearing Queue Configurations", "uri":"admin_guide_000114.html", "doc_type":"usermanual", - "p_code":"393", - "code":"399" + "p_code":"397", + "code":"403" }, { "desc":"If a tenant uses a Superior scheduler, you can configure the global policy for users to use the resource scheduler, including:Maximum running appsMaximum pending appsDefa", @@ -3596,8 +3632,8 @@ "title":"Managing Global User Policies", "uri":"admin_guide_000115.html", "doc_type":"usermanual", - "p_code":"384", - "code":"400" + "p_code":"388", + "code":"404" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3605,8 +3641,8 @@ "title":"Using the Capacity Scheduler", "uri":"admin_guide_000116.html", "doc_type":"usermanual", - "p_code":"372", - "code":"401" + "p_code":"376", + "code":"405" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3614,35 +3650,35 @@ "title":"Creating Tenants", "uri":"admin_guide_000117.html", "doc_type":"usermanual", - "p_code":"401", - "code":"402" + "p_code":"405", + "code":"406" }, { - "desc":"You can create tenants on FusionInsight Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based", + "desc":"You can create tenants on MRS Manager based on the resource consumption and isolation planning and requirements of services.A tenant name has been planned based on servic", "product_code":"mrs", "title":"Adding a Tenant", "uri":"admin_guide_000118.html", "doc_type":"usermanual", - "p_code":"402", - "code":"403" + "p_code":"406", + "code":"407" }, { - "desc":"You can create sub-tenants on FusionInsight Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planni", + "desc":"You can create sub-tenants on MRS Manager and allocate resources of the current tenant to the sub-tenants based on the resource consumption and isolation planning and req", "product_code":"mrs", "title":"Adding a Sub-Tenant", "uri":"admin_guide_000119.html", "doc_type":"usermanual", - "p_code":"402", - "code":"404" + "p_code":"406", + "code":"408" }, { - "desc":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on FusionInsight Manager and bind the user to the ", + "desc":"A newly created tenant cannot directly log in to the cluster to access resources. You need to add a user for the tenant on MRS Manager and bind the user to the role of th", "product_code":"mrs", "title":"Adding a User and Binding the User to a Tenant Role", "uri":"admin_guide_000120.html", "doc_type":"usermanual", - "p_code":"402", - "code":"405" + "p_code":"406", + "code":"409" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3650,35 +3686,35 @@ "title":"Managing Tenants", "uri":"admin_guide_000121.html", "doc_type":"usermanual", - "p_code":"401", - "code":"406" + "p_code":"405", + "code":"410" }, { - "desc":"You can manage the HDFS storage directories used by specified tenants based on service requirements on FusionInsight Manager, such as adding tenant directories, changing ", + "desc":"You can manage the HDFS storage directories used by specified tenants based on service requirements on MRS Manager, such as adding tenant directories, changing the quotas", "product_code":"mrs", "title":"Managing Tenant Directories", "uri":"admin_guide_000122.html", "doc_type":"usermanual", - "p_code":"406", - "code":"407" + "p_code":"410", + "code":"411" }, { - "desc":"Tenant data is stored on FusionInsight Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants ", + "desc":"Tenant data is stored on MRS Manager and cluster components. When components are recovered from failures or reinstalled, some configuration data of all tenants may become", "product_code":"mrs", "title":"Restoring Tenant Data", "uri":"admin_guide_000123.html", "doc_type":"usermanual", - "p_code":"406", - "code":"408" + "p_code":"410", + "code":"412" }, { - "desc":"You can delete tenants that are no longer used on FusionInsight Manager based on service requirements to release resources occupied by the tenants.A tenant has been added", + "desc":"You can delete tenants that are no longer used on MRS Manager based on service requirements to release resources occupied by the tenants.A tenant has been added.The tenan", "product_code":"mrs", "title":"Deleting a Tenant", "uri":"admin_guide_000124.html", "doc_type":"usermanual", - "p_code":"406", - "code":"409" + "p_code":"410", + "code":"413" }, { "desc":"If Yarn uses the Capacity scheduler, deleting a tenant only sets the queue capacity of the tenant to 0 and the tenant status to STOPPED but does not clear the queues of t", @@ -3686,8 +3722,8 @@ "title":"Clearing Non-associated Queues of a Tenant", "uri":"admin_guide_000125.html", "doc_type":"usermanual", - "p_code":"406", - "code":"410" + "p_code":"410", + "code":"414" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3695,8 +3731,8 @@ "title":"Managing Resources", "uri":"admin_guide_000126.html", "doc_type":"usermanual", - "p_code":"401", - "code":"411" + "p_code":"405", + "code":"415" }, { "desc":"In a cluster, you can logically group Yarn NodeManagers into Yarn resource pools. Each NodeManager belongs to only one resource pool. You can create a custom resource poo", @@ -3704,35 +3740,35 @@ "title":"Adding a Resource Pool", "uri":"admin_guide_000127.html", "doc_type":"usermanual", - "p_code":"411", - "code":"412" + "p_code":"415", + "code":"416" }, { - "desc":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on FusionInsight Manager.Adding hosts: Select", + "desc":"When hosts in a resource pool need to be adjusted based on service requirements, you can modify members in the resource pool on MRS Manager.Adding hosts: Select desired h", "product_code":"mrs", "title":"Modifying a Resource Pool", "uri":"admin_guide_000128.html", "doc_type":"usermanual", - "p_code":"411", - "code":"413" + "p_code":"415", + "code":"417" }, { - "desc":"If a resource pool is no longer used based on service requirements, you can delete it on FusionInsight Manager.Any queue in the cluster does not use the resource pool to ", + "desc":"If a resource pool is no longer used based on service requirements, you can delete it on MRS Manager.Any queue in the cluster does not use the resource pool to be deleted", "product_code":"mrs", "title":"Deleting a Resource Pool", "uri":"admin_guide_000129.html", "doc_type":"usermanual", - "p_code":"411", - "code":"414" + "p_code":"415", + "code":"418" }, { - "desc":"You can modify the queue configurations for a specified tenant on FusionInsight Manager.A tenant who uses the Capacity scheduler has been added.The Resource Distribution ", + "desc":"You can modify the queue configurations for a specified tenant on MRS Manager.A tenant who uses the Capacity scheduler has been added.The Resource Distribution Policy pag", "product_code":"mrs", "title":"Configuring a Queue", "uri":"admin_guide_000130.html", "doc_type":"usermanual", - "p_code":"411", - "code":"415" + "p_code":"415", + "code":"419" }, { "desc":"After a resource pool is added, you can configure the capacity policy of available resources for Yarn queues so that jobs in the queues can be properly executed in the re", @@ -3740,17 +3776,17 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"admin_guide_000131.html", "doc_type":"usermanual", - "p_code":"411", - "code":"416" + "p_code":"415", + "code":"420" }, { - "desc":"You can clear the configurations of a queue on FusionInsight MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disass", + "desc":"You can clear the configurations of a queue on MRS Manager when the queue does not need resources of a resource pool or the resource pool needs to be disassociated from t", "product_code":"mrs", "title":"Clearing Queue Configurations", "uri":"admin_guide_000132.html", "doc_type":"usermanual", - "p_code":"411", - "code":"417" + "p_code":"415", + "code":"421" }, { "desc":"The newly installed MRS cluster uses the Superior scheduler by default. If the cluster is upgraded from an earlier version, you can switch the YARN scheduler from the Cap", @@ -3758,8 +3794,8 @@ "title":"Switching the Scheduler", "uri":"admin_guide_000133.html", "doc_type":"usermanual", - "p_code":"372", - "code":"418" + "p_code":"376", + "code":"422" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3767,8 +3803,8 @@ "title":"System Configuration", "uri":"admin_guide_000134.html", "doc_type":"usermanual", - "p_code":"292", - "code":"419" + "p_code":"296", + "code":"423" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3776,8 +3812,8 @@ "title":"Configuring Permissions", "uri":"admin_guide_000135.html", "doc_type":"usermanual", - "p_code":"419", - "code":"420" + "p_code":"423", + "code":"424" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3785,35 +3821,35 @@ "title":"Managing Users", "uri":"admin_guide_000136.html", "doc_type":"usermanual", - "p_code":"420", - "code":"421" + "p_code":"424", + "code":"425" }, { - "desc":"FusionInsight Manager supports a maximum of 50,000 users (including built-in users). By default, only user admin has the highest operation permissions of FusionInsight Ma", + "desc":"MRS Manager supports a maximum of 50,000 users (including built-in users). By default, only user admin has the highest operation permissions of MRS Manager. You need to c", "product_code":"mrs", "title":"Creating a User", "uri":"admin_guide_000137.html", "doc_type":"usermanual", - "p_code":"421", - "code":"422" + "p_code":"425", + "code":"426" }, { - "desc":"You can modify user information on FusionInsight Manager, including the user group, primary group, role permission assignment, and user description.Modify the parameters ", + "desc":"You can modify user information on MRS Manager, including the user group, primary group, role permission assignment, and user description.Modify the parameters based on s", "product_code":"mrs", "title":"Modifying User Information", "uri":"admin_guide_000138.html", "doc_type":"usermanual", - "p_code":"421", - "code":"423" + "p_code":"425", + "code":"427" }, { - "desc":"You can export information about all created users on FusionInsight Manager.The exported user information contains the username, creation time, description, user type (0 ", + "desc":"You can export information about all created users on MRS Manager.The exported user information contains the username, creation time, description, user type (0 indicates ", "product_code":"mrs", "title":"Exporting User Information", "uri":"admin_guide_000139.html", "doc_type":"usermanual", - "p_code":"421", - "code":"424" + "p_code":"425", + "code":"428" }, { "desc":"A user may be suspended for a long period of time due to service changes. For security purposes, you can lock such a user.You can lock a user in using either of the follo", @@ -3821,44 +3857,44 @@ "title":"Locking a User", "uri":"admin_guide_000140.html", "doc_type":"usermanual", - "p_code":"421", - "code":"425" + "p_code":"425", + "code":"429" }, { - "desc":"You can unlock a user on FusionInsight Manager if the user has been locked because the number of login attempts exceeds the threshold. Only users created on FusionInsight", + "desc":"You can unlock a user on MRS Manager if the user has been locked because the number of login attempts exceeds the threshold. Only users created on MRS Manager can be unlo", "product_code":"mrs", "title":"Unlocking a User", "uri":"admin_guide_000141.html", "doc_type":"usermanual", - "p_code":"421", - "code":"426" + "p_code":"425", + "code":"430" }, { - "desc":"Based on service requirements, you can delete system users that are no longer used on FusionInsight Manager.After a user is deleted, the provisioned ticket granting ticke", + "desc":"Based on service requirements, you can delete system users that are no longer used on MRS Manager.After a user is deleted, the provisioned ticket granting ticket (TGT) is", "product_code":"mrs", "title":"Deleting a User", "uri":"admin_guide_000142.html", "doc_type":"usermanual", - "p_code":"421", - "code":"427" + "p_code":"425", + "code":"431" }, { - "desc":"For security purposes, the password of a human-machine user must be changed periodically.If users have the permission to use FusionInsight Manager, they can change their ", + "desc":"For security purposes, the password of a human-machine user must be changed periodically.If users have the permission to use MRS Manager, they can change their passwords ", "product_code":"mrs", "title":"Changing a User Password", "uri":"admin_guide_000143.html", "doc_type":"usermanual", - "p_code":"421", - "code":"428" + "p_code":"425", + "code":"432" }, { - "desc":"If a user forgets the password or the public account password needs to be changed periodically, you can initialize the password on FusionInsight Manager. After the passwo", + "desc":"If a user forgets the password or the public account password needs to be changed periodically, you can initialize the password on MRS Manager. After the password is init", "product_code":"mrs", "title":"Initializing a Password", "uri":"admin_guide_000144.html", "doc_type":"usermanual", - "p_code":"421", - "code":"429" + "p_code":"425", + "code":"433" }, { "desc":"If a user uses a security mode cluster to develop applications, the keytab file of the user needs to be obtained for security authentication. You can export keytab files ", @@ -3866,26 +3902,26 @@ "title":"Exporting an Authentication Credential File", "uri":"admin_guide_000145.html", "doc_type":"usermanual", - "p_code":"421", - "code":"430" + "p_code":"425", + "code":"434" }, { - "desc":"FusionInsight Manager supports a maximum of 5000 user groups (including built-in user groups). You can create and manage different user groups based on service scenarios ", + "desc":"MRS Manager supports a maximum of 5000 user groups (including built-in user groups). You can create and manage different user groups based on service scenarios on MRS Man", "product_code":"mrs", "title":"Managing User Groups", "uri":"admin_guide_000147.html", "doc_type":"usermanual", - "p_code":"420", - "code":"431" + "p_code":"424", + "code":"435" }, { - "desc":"FusionInsight Manager supports a maximum of 5000 roles (including system built-in roles but excluding roles automatically created by tenants). Based on different service ", + "desc":"MRS Manager supports a maximum of 5000 roles (including system built-in roles but excluding roles automatically created by tenants). Based on different service requiremen", "product_code":"mrs", "title":"Managing Roles", "uri":"admin_guide_000148.html", "doc_type":"usermanual", - "p_code":"420", - "code":"432" + "p_code":"424", + "code":"436" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3893,26 +3929,26 @@ "title":"Security Policies", "uri":"admin_guide_000149.html", "doc_type":"usermanual", - "p_code":"420", - "code":"433" + "p_code":"424", + "code":"437" }, { - "desc":"To keep up with service security requirements, you can set password security rules, user login security rules, and user locking rules on FusionInsight Manager.Modify pass", + "desc":"To keep up with service security requirements, you can set password security rules, user login security rules, and user locking rules on MRS Manager.Modify password polic", "product_code":"mrs", "title":"Configuring Password Policies", "uri":"admin_guide_000150.html", "doc_type":"usermanual", - "p_code":"433", - "code":"434" + "p_code":"437", + "code":"438" }, { - "desc":"User admin or administrators who are bound to the Manager_administrator role can configure the independent attribute on FusionInsight Manager so that common users (all se", + "desc":"User admin or administrators who are bound to the Manager_administrator role can configure the independent attribute on MRS Manager so that common users (all service user", "product_code":"mrs", "title":"Configuring the Independent Attribute", "uri":"admin_guide_000151.html", "doc_type":"usermanual", - "p_code":"433", - "code":"435" + "p_code":"437", + "code":"439" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3920,26 +3956,26 @@ "title":"Configuring Interconnections", "uri":"admin_guide_000153.html", "doc_type":"usermanual", - "p_code":"419", - "code":"436" + "p_code":"423", + "code":"440" }, { - "desc":"If users need to view alarms and monitoring data of a cluster on the O&M platform, you can use Simple Network Management Protocol (SNMP) on FusionInsight Manager to repor", + "desc":"If users need to view alarms and monitoring data of a cluster on the O&M platform, you can use Simple Network Management Protocol (SNMP) on MRS Manager to report related ", "product_code":"mrs", "title":"Configuring SNMP Northbound Parameters", "uri":"admin_guide_000154.html", "doc_type":"usermanual", - "p_code":"436", - "code":"437" + "p_code":"440", + "code":"441" }, { - "desc":"If users need to view alarms and events of a cluster on the unified alarm reporting platform, you can use the Syslog protocol on FusionInsight Manager to report related d", + "desc":"If users need to view alarms and events of a cluster on the unified alarm reporting platform, you can use the Syslog protocol on MRS Manager to report related data to the", "product_code":"mrs", "title":"Configuring Syslog Northbound Parameters", "uri":"admin_guide_000155.html", "doc_type":"usermanual", - "p_code":"436", - "code":"438" + "p_code":"440", + "code":"442" }, { "desc":"The monitoring data reporting function writes the monitoring data collected in the system into a text file and uploads the file to a specified server in FTP or SFTP mode.", @@ -3947,17 +3983,17 @@ "title":"Configuring Monitoring Metric Dumping", "uri":"admin_guide_000156.html", "doc_type":"usermanual", - "p_code":"436", - "code":"439" + "p_code":"440", + "code":"443" }, { - "desc":"CA certificates are used to encrypt data during communication between FusionInsight Manager modules and between cluster component clients and servers to ensure security. ", + "desc":"CA certificates are used to encrypt data during communication between MRS Manager modules and between cluster component clients and servers to ensure security. CA certifi", "product_code":"mrs", "title":"Importing a Certificate", "uri":"admin_guide_000157.html", "doc_type":"usermanual", - "p_code":"419", - "code":"440" + "p_code":"423", + "code":"444" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3965,26 +4001,26 @@ "title":"OMS Management", "uri":"admin_guide_000159.html", "doc_type":"usermanual", - "p_code":"419", - "code":"441" + "p_code":"423", + "code":"445" }, { - "desc":"Log in to FusionInsight Manager and choose System > OMS. You can perform maintenance operations on the OMS page, including viewing basic information, viewing the service ", + "desc":"Log in to MRS Manager and choose System > OMS. You can perform maintenance operations on the OMS page, including viewing basic information, viewing the service status of ", "product_code":"mrs", "title":"Overview of the OMS Page", "uri":"admin_guide_000160.html", "doc_type":"usermanual", - "p_code":"441", - "code":"442" + "p_code":"445", + "code":"446" }, { - "desc":"Based on the security requirements of the user environment, you can modify the Kerberos and LDAP configurations in the OMS on FusionInsight Manager.After the OMS service ", + "desc":"Based on the security requirements of the user environment, you can modify the Kerberos and LDAP configurations in the OMS on MRS Manager.After the OMS service configurat", "product_code":"mrs", "title":"Modifying OMS Service Configuration Parameters", "uri":"admin_guide_000162.html", "doc_type":"usermanual", - "p_code":"441", - "code":"443" + "p_code":"445", + "code":"447" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3992,17 +4028,17 @@ "title":"Component Management", "uri":"admin_guide_000164.html", "doc_type":"usermanual", - "p_code":"419", - "code":"444" + "p_code":"423", + "code":"448" }, { - "desc":"A complete MRS cluster consists of multiple component packages. Before installing some services on FusionInsight Manager, check whether the component packages of those se", + "desc":"A complete MRS cluster consists of multiple component packages. Before installing some services on MRS Manager, check whether the component packages of those services hav", "product_code":"mrs", "title":"Viewing Component Packages", "uri":"admin_guide_000165.html", "doc_type":"usermanual", - "p_code":"444", - "code":"445" + "p_code":"448", + "code":"449" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4010,8 +4046,8 @@ "title":"Cluster Management", "uri":"admin_guide_000166.html", "doc_type":"usermanual", - "p_code":"292", - "code":"446" + "p_code":"296", + "code":"450" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4019,8 +4055,8 @@ "title":"Configuring Client", "uri":"admin_guide_000170.html", "doc_type":"usermanual", - "p_code":"446", - "code":"447" + "p_code":"450", + "code":"451" }, { "desc":"This section describes how to install the clients of all services, except Flume, in the MRS cluster. MRS provides shell scripts for different services so that maintenance", @@ -4028,8 +4064,8 @@ "title":"Installing a Client", "uri":"admin_guide_000171.html", "doc_type":"usermanual", - "p_code":"447", - "code":"448" + "p_code":"451", + "code":"452" }, { "desc":"After the client is installed, you can use the shell command on the client in O&M or service scenarios, or use the sample project on the client during application develop", @@ -4037,17 +4073,17 @@ "title":"Using a Client", "uri":"admin_guide_000172.html", "doc_type":"usermanual", - "p_code":"447", - "code":"449" + "p_code":"451", + "code":"453" }, { - "desc":"The cluster provides a client for you to connect to a server, view task results, or manage data. If you modify service configuration parameters on FusionInsight Manager a", + "desc":"The cluster provides a client for you to connect to a server, view task results, or manage data. If you modify service configuration parameters on MRS Manager and restart", "product_code":"mrs", "title":"Updating the Configuration of an Installed Client", "uri":"admin_guide_000173.html", "doc_type":"usermanual", - "p_code":"447", - "code":"450" + "p_code":"451", + "code":"454" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4055,8 +4091,8 @@ "title":"Cluster Mutual Trust Management", "uri":"admin_guide_000174.html", "doc_type":"usermanual", - "p_code":"446", - "code":"451" + "p_code":"450", + "code":"455" }, { "desc":"By default, users of a big data cluster in security mode can only access resources in the cluster but cannot perform identity authentication or access resources in other ", @@ -4064,62 +4100,62 @@ "title":"Overview of Mutual Trust Between Clusters", "uri":"admin_guide_000175.html", "doc_type":"usermanual", - "p_code":"451", - "code":"452" + "p_code":"455", + "code":"456" }, { - "desc":"The secure usage scope of users in each system is called a domain. Each system must have a unique domain name. The domain name of FusionInsight Manager is generated durin", + "desc":"The secure usage scope of users in each system is called a domain. Each system must have a unique domain name. The domain name of MRS Manager is generated during installa", "product_code":"mrs", "title":"Changing Manager's Domain Name", "uri":"admin_guide_000176.html", "doc_type":"usermanual", - "p_code":"451", - "code":"453" + "p_code":"455", + "code":"457" }, { - "desc":"When two security-mode clusters managed by different FusionInsight Managers need to access each other's resources, the system administrator can configure cross-Manager mu", + "desc":"When two security-mode clusters managed by different MRS Managers need to access each other's resources, the system administrator can configure cross-Manager mutual trust", "product_code":"mrs", "title":"Configuring Cross-Manager Mutual Trust Between Clusters", "uri":"admin_guide_000177.html", "doc_type":"usermanual", - "p_code":"451", - "code":"454" + "p_code":"455", + "code":"458" }, { - "desc":"After cross-Manager cluster mutual trust is configured, assign user access permissions on FusionInsight Managers so that these users can perform service operations in the", + "desc":"After cross-Manager cluster mutual trust is configured, assign user access permissions on MRS Managers so that these users can perform service operations in the mutually ", "product_code":"mrs", "title":"Assigning User Permissions After Cross-Cluster Mutual Trust Is Configured", "uri":"admin_guide_000178.html", "doc_type":"usermanual", - "p_code":"451", - "code":"455" + "p_code":"455", + "code":"459" }, { - "desc":"You can modify the configuration file to periodically back up FusionInsight Manager alarm information, FusionInsight Manager audit information, and audit information of a", + "desc":"You can modify the configuration file to periodically back up MRS Manager alarm information, MRS Manager audit information, and audit information of all services to the s", "product_code":"mrs", "title":"Configuring Scheduled Backup of Alarm and Audit Information", "uri":"admin_guide_000182.html", "doc_type":"usermanual", - "p_code":"446", - "code":"456" + "p_code":"450", + "code":"460" }, { - "desc":"When FusionInsight Manager is installed, two pieces of routing information are automatically created on the active management node. You can run the ip rule list command t", + "desc":"When MRS Manager is installed, two pieces of routing information are automatically created on the active management node. You can run the ip rule list command to view the", "product_code":"mrs", - "title":"Modifying the FusionInsight Manager Routing Table", + "title":"Modifying the MRS Manager Routing Table", "uri":"admin_guide_000183.html", "doc_type":"usermanual", - "p_code":"446", - "code":"457" + "p_code":"450", + "code":"461" }, { - "desc":"FusionInsight Manager allows you to set clusters, services, hosts, or OMSs to the maintenance mode. Objects in maintenance mode do not report alarms. This prevents the sy", + "desc":"MRS Manager allows you to set clusters, services, hosts, or OMSs to the maintenance mode. Objects in maintenance mode do not report alarms. This prevents the system from ", "product_code":"mrs", "title":"Switching to the Maintenance Mode", "uri":"admin_guide_000189.html", "doc_type":"usermanual", - "p_code":"446", - "code":"458" + "p_code":"450", + "code":"462" }, { "desc":"To ensure long-term and stable running of the system, administrators or maintenance engineers need to periodically check items listed in Table 1 and rectify the detected ", @@ -4127,8 +4163,8 @@ "title":"Routine Maintenance", "uri":"admin_guide_000191.html", "doc_type":"usermanual", - "p_code":"446", - "code":"459" + "p_code":"450", + "code":"463" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4136,8 +4172,8 @@ "title":"Log Management", "uri":"admin_guide_000192.html", "doc_type":"usermanual", - "p_code":"292", - "code":"460" + "p_code":"296", + "code":"464" }, { "desc":"MRS cluster logs are stored in the /var/log/Bigdata directory. The following table lists the log types.The following table lists the MRS log directories.After the multi-i", @@ -4145,8 +4181,8 @@ "title":"About Logs", "uri":"admin_guide_000193.html", "doc_type":"usermanual", - "p_code":"460", - "code":"461" + "p_code":"464", + "code":"465" }, { "desc":"Log path: The default storage path of Manager log files is /var/log/Bigdata/Manager component.ControllerService: /var/log/Bigdata/controller/ (OMS installation and run lo", @@ -4154,17 +4190,17 @@ "title":"Manager Log List", "uri":"admin_guide_000194.html", "doc_type":"usermanual", - "p_code":"460", - "code":"462" + "p_code":"464", + "code":"466" }, { - "desc":"You can change the log levels of FusionInsight Manager. For a specific service, you can change the log level and the log file size to prevent the failure in saving logs d", + "desc":"You can change the log levels of MRS Manager. For a specific service, you can change the log level and the log file size to prevent the failure in saving logs due to insu", "product_code":"mrs", "title":"Configuring the Log Level and Log File Size", "uri":"admin_guide_000195.html", "doc_type":"usermanual", - "p_code":"460", - "code":"463" + "p_code":"464", + "code":"467" }, { "desc":"Audit logs of cluster components are classified by name and stored in the /var/log/Bigdata/audit directory on each cluster node. The OMS automatically backs up the audit ", @@ -4172,17 +4208,17 @@ "title":"Configuring the Number of Local Audit Log Backups", "uri":"admin_guide_000196.html", "doc_type":"usermanual", - "p_code":"460", - "code":"464" + "p_code":"464", + "code":"468" }, { - "desc":"FusionInsight Manager allows users to view logs of each role instance.On the Hosts page, click a host name. In the instance list of the host, you can view the log files o", + "desc":"MRS Manager allows users to view logs of each role instance.On the Hosts page, click a host name. In the instance list of the host, you can view the log files of all role", "product_code":"mrs", "title":"Viewing Role Instance Logs", "uri":"admin_guide_000197.html", "doc_type":"usermanual", - "p_code":"460", - "code":"465" + "p_code":"464", + "code":"469" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4190,17 +4226,17 @@ "title":"Backup and Recovery Management", "uri":"admin_guide_000198.html", "doc_type":"usermanual", - "p_code":"292", - "code":"466" + "p_code":"296", + "code":"470" }, { - "desc":"FusionInsight Manager provides the backup and restoration of system data and user data by component. The system can back up Manager data, component metadata, and service ", + "desc":"MRS Manager provides the backup and restoration of system data and user data by component. The system can back up Manager data, component metadata, and service data.Data ", "product_code":"mrs", "title":"Introduction", "uri":"admin_guide_000399.html", "doc_type":"usermanual", - "p_code":"466", - "code":"467" + "p_code":"470", + "code":"471" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4208,17 +4244,17 @@ "title":"Backing Up Data", "uri":"admin_guide_000201.html", "doc_type":"usermanual", - "p_code":"466", - "code":"468" + "p_code":"470", + "code":"472" }, { - "desc":"To ensure data security of FusionInsight Manager routinely or before and after a critical operation (such as capacity expansion and reduction) on FusionInsight Manager, y", + "desc":"To ensure data security of MRS Manager routinely or before and after a critical operation (such as capacity expansion and reduction) on MRS Manager, you need to back up M", "product_code":"mrs", "title":"Backing Up Manager Data", "uri":"admin_guide_000202.html", "doc_type":"usermanual", - "p_code":"468", - "code":"469" + "p_code":"472", + "code":"473" }, { "desc":"To ensure CDL service data security routinely or before a major operation on CDL (such as upgrade or migration), you need to back up CDL data. The backup data can be used", @@ -4226,8 +4262,8 @@ "title":"Backing Up CDL Data", "uri":"admin_guide_000343.html", "doc_type":"usermanual", - "p_code":"468", - "code":"470" + "p_code":"472", + "code":"474" }, { "desc":"To ensure ClickHouse metadata security or before a major operation on ZooKeeper (such as upgrade or migration), you need to back up ClickHouse metadata. The backup data c", @@ -4235,8 +4271,8 @@ "title":"Backing Up ClickHouse Metadata", "uri":"admin_guide_000348.html", "doc_type":"usermanual", - "p_code":"468", - "code":"471" + "p_code":"472", + "code":"475" }, { "desc":"To ensure ClickHouse service data security routinely or before a major operation on ClickHouse (such as upgrade or migration), you need to back up ClickHouse service data", @@ -4244,8 +4280,8 @@ "title":"Backing Up ClickHouse Service Data", "uri":"admin_guide_000349.html", "doc_type":"usermanual", - "p_code":"468", - "code":"472" + "p_code":"472", + "code":"476" }, { "desc":"To ensure DBService service data security routinely or before a major operation on DBService (such as upgrade or migration), you need to back up DBService data. The backu", @@ -4253,8 +4289,8 @@ "title":"Backing Up DBService Data", "uri":"admin_guide_000203.html", "doc_type":"usermanual", - "p_code":"468", - "code":"473" + "p_code":"472", + "code":"477" }, { "desc":"To ensure HBase metadata security (including tableinfo files and HFiles) or before a major operation on HBase system tables (such as upgrade or migration), you need to ba", @@ -4262,8 +4298,8 @@ "title":"Backing Up HBase Metadata", "uri":"admin_guide_000204.html", "doc_type":"usermanual", - "p_code":"468", - "code":"474" + "p_code":"472", + "code":"478" }, { "desc":"To ensure HBase service data security routinely or before a major operation on HBase (such as upgrade or migration), you need to back up HBase service data. The backup da", @@ -4271,8 +4307,8 @@ "title":"Backing Up HBase Service Data", "uri":"admin_guide_000205.html", "doc_type":"usermanual", - "p_code":"468", - "code":"475" + "p_code":"472", + "code":"479" }, { "desc":"To ensure NameNode service data security routinely or before a major operation on NameNode (such as upgrade or migration), you need to back up NameNode data. The backup d", @@ -4280,8 +4316,8 @@ "title":"Backing Up NameNode Data", "uri":"admin_guide_000208.html", "doc_type":"usermanual", - "p_code":"468", - "code":"476" + "p_code":"472", + "code":"480" }, { "desc":"To ensure HDFS service data security routinely or before a major operation on HDFS (such as upgrade or migration), you need to back up HDFS service data. The backup data ", @@ -4289,8 +4325,8 @@ "title":"Backing Up HDFS Service Data", "uri":"admin_guide_000209.html", "doc_type":"usermanual", - "p_code":"468", - "code":"477" + "p_code":"472", + "code":"481" }, { "desc":"To ensure Hive service data security routinely or before a major operation on Hive (such as upgrade or migration), you need to back up Hive service data. The backup data ", @@ -4298,8 +4334,8 @@ "title":"Backing Up Hive Service Data", "uri":"admin_guide_000210.html", "doc_type":"usermanual", - "p_code":"468", - "code":"478" + "p_code":"472", + "code":"482" }, { "desc":"To ensure IoTDB metadata security and prevent the IoTDB service from being unavailable due to IoTDB metadata file damages, you need to back up IoTDB metadata. The backup ", @@ -4307,8 +4343,8 @@ "title":"Backing Up IoTDB Metadata", "uri":"admin_guide_000350.html", "doc_type":"usermanual", - "p_code":"468", - "code":"479" + "p_code":"472", + "code":"483" }, { "desc":"To ensure IoTDB service data security routinely or before a major operation on IoTDB (such as upgrade or migration), you need to back up IoTDB service data. The backup da", @@ -4316,8 +4352,8 @@ "title":"Backing Up IoTDB Service Data", "uri":"admin_guide_000360.html", "doc_type":"usermanual", - "p_code":"468", - "code":"480" + "p_code":"472", + "code":"484" }, { "desc":"To ensure Kafka metadata security or before a major operation on ZooKeeper (such as upgrade or migration), you need to back up Kafka metadata. The backup data can be used", @@ -4325,8 +4361,8 @@ "title":"Backing Up Kafka Metadata", "uri":"admin_guide_000211.html", "doc_type":"usermanual", - "p_code":"468", - "code":"481" + "p_code":"472", + "code":"485" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4334,8 +4370,8 @@ "title":"Recovering Data", "uri":"admin_guide_000215.html", "doc_type":"usermanual", - "p_code":"466", - "code":"482" + "p_code":"470", + "code":"486" }, { "desc":"Manager data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical", @@ -4343,8 +4379,8 @@ "title":"Restoring Manager Data", "uri":"admin_guide_000216.html", "doc_type":"usermanual", - "p_code":"482", - "code":"483" + "p_code":"486", + "code":"487" }, { "desc":"CDL data needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After an administrator performs major operati", @@ -4352,8 +4388,8 @@ "title":"Restoring CDL Data", "uri":"admin_guide_000345.html", "doc_type":"usermanual", - "p_code":"482", - "code":"484" + "p_code":"486", + "code":"488" }, { "desc":"ClickHouse metadata needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After a user performs major operat", @@ -4361,8 +4397,8 @@ "title":"Restoring ClickHouse Metadata", "uri":"admin_guide_000358.html", "doc_type":"usermanual", - "p_code":"482", - "code":"485" + "p_code":"486", + "code":"489" }, { "desc":"ClickHouse data needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After a user performs major operations", @@ -4370,8 +4406,8 @@ "title":"Restoring ClickHouse Service Data", "uri":"admin_guide_000359.html", "doc_type":"usermanual", - "p_code":"482", - "code":"486" + "p_code":"486", + "code":"490" }, { "desc":"DBService data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critic", @@ -4379,8 +4415,8 @@ "title":"Restoring DBService data", "uri":"admin_guide_000217.html", "doc_type":"usermanual", - "p_code":"482", - "code":"487" + "p_code":"486", + "code":"491" }, { "desc":"To ensure HBase metadata security (including tableinfo files and HFiles) or before a major operation on HBase system tables (such as upgrade or migration), you need to ba", @@ -4388,8 +4424,8 @@ "title":"Restoring HBase Metadata", "uri":"admin_guide_000218.html", "doc_type":"usermanual", - "p_code":"482", - "code":"488" + "p_code":"486", + "code":"492" }, { "desc":"HBase data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical d", @@ -4397,8 +4433,8 @@ "title":"Restoring HBase Service Data", "uri":"admin_guide_000219.html", "doc_type":"usermanual", - "p_code":"482", - "code":"489" + "p_code":"486", + "code":"493" }, { "desc":"NameNode data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critica", @@ -4406,8 +4442,8 @@ "title":"Restoring NameNode Data", "uri":"admin_guide_000222.html", "doc_type":"usermanual", - "p_code":"482", - "code":"490" + "p_code":"486", + "code":"494" }, { "desc":"HDFS data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical da", @@ -4415,8 +4451,8 @@ "title":"Restoring HDFS Service Data", "uri":"admin_guide_000223.html", "doc_type":"usermanual", - "p_code":"482", - "code":"491" + "p_code":"486", + "code":"495" }, { "desc":"Hive data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical da", @@ -4424,8 +4460,8 @@ "title":"Restoring Hive Service Data", "uri":"admin_guide_000224.html", "doc_type":"usermanual", - "p_code":"482", - "code":"492" + "p_code":"486", + "code":"496" }, { "desc":"To ensure IoTDB metadata security and prevent the IoTDB service from being unavailable due to IoTDB file damage, IoTDB metadata needs to be backed up. In this way, the sy", @@ -4433,8 +4469,8 @@ "title":"Restoring IoTDB Metadata", "uri":"admin_guide_000351.html", "doc_type":"usermanual", - "p_code":"482", - "code":"493" + "p_code":"486", + "code":"497" }, { "desc":"IoTDB service data needs to be restored in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored. After an administrator performs maj", @@ -4442,8 +4478,8 @@ "title":"Restoring IoTDB Service Data", "uri":"admin_guide_000361.html", "doc_type":"usermanual", - "p_code":"482", - "code":"494" + "p_code":"486", + "code":"498" }, { "desc":"Kafka data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical d", @@ -4451,8 +4487,8 @@ "title":"Restoring Kafka Metadata", "uri":"admin_guide_000225.html", "doc_type":"usermanual", - "p_code":"482", - "code":"495" + "p_code":"486", + "code":"499" }, { "desc":"DistCp is used to replicate the data stored in HDFS from a cluster to another cluster. DistCp depends on the cross-cluster replication function, which is disabled by defa", @@ -4460,44 +4496,44 @@ "title":"Enabling Cross-Cluster Replication", "uri":"admin_guide_000200.html", "doc_type":"usermanual", - "p_code":"466", - "code":"496" + "p_code":"470", + "code":"500" }, { - "desc":"When DistCp is used to back up data, the backup snapshot is saved to HDFS of the active cluster. FusionInsight Manager supports using the local snapshot for quick data re", + "desc":"When DistCp is used to back up data, the backup snapshot is saved to HDFS of the active cluster. MRS Manager supports using the local snapshot for quick data restoration,", "product_code":"mrs", "title":"Managing Local Quick Restoration Tasks", "uri":"admin_guide_000229.html", "doc_type":"usermanual", - "p_code":"466", - "code":"497" + "p_code":"470", + "code":"501" }, { - "desc":"This section describes how to modify the parameters of a created backup task on FusionInsight Manager to meet changing service requirements. The parameters of restoration", + "desc":"This section describes how to modify the parameters of a created backup task on MRS Manager to meet changing service requirements. The parameters of restoration tasks can", "product_code":"mrs", "title":"Modifying a Backup Task", "uri":"admin_guide_000230.html", "doc_type":"usermanual", - "p_code":"466", - "code":"498" + "p_code":"470", + "code":"502" }, { - "desc":"This section describes how to view created backup and recovery tasks and check their running status on FusionInsight Manager.You have logged in to FusionInsight Manager. ", + "desc":"This section describes how to view created backup and recovery tasks and check their running status on MRS Manager.You have logged in to MRS Manager. For details, see Log", "product_code":"mrs", "title":"Viewing Backup and Restoration Tasks", "uri":"admin_guide_000231.html", "doc_type":"usermanual", - "p_code":"466", - "code":"499" + "p_code":"470", + "code":"503" }, { - "desc":"This section applies only to MRS 3.1.0.How do I configure the environment when I create a ClickHouse backup task on FusionInsight Manager and set the path type to RemoteH", + "desc":"This section applies only to MRS 3.1.0.How do I configure the environment when I create a ClickHouse backup task on MRS Manager and set the path type to RemoteHDFS?For ex", "product_code":"mrs", - "title":"How Do I Configure the Environment When I Create a ClickHouse Backup Task on FusionInsight Manager and Set the Path Type to RemoteHDFS?", + "title":"How Do I Configure the Environment When I Create a ClickHouse Backup Task on MRS Manager and Set the Path Type to RemoteHDFS?", "uri":"admin_guide_000357.html", "doc_type":"usermanual", - "p_code":"466", - "code":"500" + "p_code":"470", + "code":"504" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4505,8 +4541,8 @@ "title":"Security Management", "uri":"admin_guide_000233.html", "doc_type":"usermanual", - "p_code":"292", - "code":"501" + "p_code":"296", + "code":"505" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4514,26 +4550,26 @@ "title":"Security Overview", "uri":"admin_guide_000234.html", "doc_type":"usermanual", - "p_code":"501", - "code":"502" + "p_code":"505", + "code":"506" }, { - "desc":"FusionInsight adopts the role-based access control (RBAC) mode to manage rights on the big data system. It integrates the right management functions of the components to ", + "desc":"MRS adopts the role-based access control (RBAC) mode to manage rights on the big data system. It integrates the right management functions of the components to centrally ", "product_code":"mrs", "title":"Right Model", "uri":"admin_guide_000235.html", "doc_type":"usermanual", - "p_code":"502", - "code":"503" + "p_code":"506", + "code":"507" }, { - "desc":"FusionInsight adopts the Lightweight Directory Access Protocol (LDAP) to store data of users and user groups. Information about role definitions is stored in the relation", + "desc":"MRS adopts the Lightweight Directory Access Protocol (LDAP) to store data of users and user groups. Information about role definitions is stored in the relational databas", "product_code":"mrs", "title":"Right Mechanism", "uri":"admin_guide_000236.html", "doc_type":"usermanual", - "p_code":"502", - "code":"504" + "p_code":"506", + "code":"508" }, { "desc":"The big data platform performs user identity authentication to prevent invalid users from accessing the cluster. The cluster provides authentication capabilities in both ", @@ -4541,8 +4577,8 @@ "title":"Authentication Policies", "uri":"admin_guide_000237.html", "doc_type":"usermanual", - "p_code":"502", - "code":"505" + "p_code":"506", + "code":"509" }, { "desc":"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 configurat", @@ -4550,35 +4586,35 @@ "title":"Permission Verification Policies", "uri":"admin_guide_000238.html", "doc_type":"usermanual", - "p_code":"502", - "code":"506" + "p_code":"506", + "code":"510" }, { "desc":"The MRS cluster provides the following three types of users. The system administrator needs to periodically change the passwords. It is not recommended to use the default", "product_code":"mrs", - "title":"User Account List", + "title":"User Account ListUser Account ListSystem User Description", "uri":"admin_guide_000239.html", "doc_type":"usermanual", - "p_code":"502", - "code":"507" + "p_code":"506", + "code":"511" }, { - "desc":"If the current cluster is not the cluster that is installed for the first time in FusionInsight Manager, the default user group name of all components except Manager in t", + "desc":"If the current cluster is not the cluster that is installed for the first time in MRS Manager, the default user group name of all components except Manager in the cluster", "product_code":"mrs", "title":"Default Permission Information", "uri":"admin_guide_000240.html", "doc_type":"usermanual", - "p_code":"502", - "code":"508" + "p_code":"506", + "code":"512" }, { - "desc":"You can query and set user rights data through the following FusionInsight Manager modules:User management: Users can be added, deleted, modified, queried, bound to user ", + "desc":"You can query and set user rights data through the following MRS Manager modules:User management: Users can be added, deleted, modified, queried, bound to user groups, an", "product_code":"mrs", - "title":"FusionInsight Manager Security Functions", + "title":"MRS Manager Security Functions", "uri":"admin_guide_000241.html", "doc_type":"usermanual", - "p_code":"502", - "code":"509" + "p_code":"506", + "code":"513" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4586,8 +4622,8 @@ "title":"Account Management", "uri":"admin_guide_000242.html", "doc_type":"usermanual", - "p_code":"501", - "code":"510" + "p_code":"505", + "code":"514" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4595,8 +4631,8 @@ "title":"Account Security Settings", "uri":"admin_guide_000243.html", "doc_type":"usermanual", - "p_code":"510", - "code":"511" + "p_code":"514", + "code":"515" }, { "desc":"If the LDAP user cn=pg_search_dn,ou=Users,dc=hadoop,dc=com and LDAP management accounts cn=krbkdc,ou=Users,dc=hadoop,dc=com and cn=krbadmin,ou=Users,dc=hadoop,dc=com are ", @@ -4604,8 +4640,8 @@ "title":"Unlocking LDAP Users and Management Accounts", "uri":"admin_guide_000245.html", "doc_type":"usermanual", - "p_code":"511", - "code":"512" + "p_code":"515", + "code":"516" }, { "desc":"If the service is abnormal, the internal user of the system may be locked. Unlock the user promptly, or the cluster cannot run properly. For the list of system internal u", @@ -4613,8 +4649,8 @@ "title":"Internal an Internal System User", "uri":"admin_guide_000246.html", "doc_type":"usermanual", - "p_code":"511", - "code":"513" + "p_code":"515", + "code":"517" }, { "desc":"HDFS and ZooKeeper verify the permission of users who attempt to access the services in both security and normal clusters by default. Users without related permission can", @@ -4622,8 +4658,8 @@ "title":"Enabling and Disabling Permission Verification on Cluster Components", "uri":"admin_guide_000247.html", "doc_type":"usermanual", - "p_code":"511", - "code":"514" + "p_code":"515", + "code":"518" }, { "desc":"When the cluster is installed in normal mode, the component clients do not support security authentication and cannot use the kinit command. Therefore, nodes outside the ", @@ -4631,8 +4667,8 @@ "title":"Logging In to a Non-Cluster Node Using a Cluster User in Normal Mode", "uri":"admin_guide_000248.html", "doc_type":"usermanual", - "p_code":"511", - "code":"515" + "p_code":"515", + "code":"519" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4640,26 +4676,26 @@ "title":"Changing the Password for a System User", "uri":"admin_guide_000249.html", "doc_type":"usermanual", - "p_code":"510", - "code":"516" + "p_code":"514", + "code":"520" }, { - "desc":"User admin is the system administrator account of FusionInsight Manager. You are advised to periodically change the password on FusionInsight Manager to improve system se", + "desc":"User admin is the system administrator account of MRS Manager. You are advised to periodically change the password on MRS Manager to improve system security.User admin is", "product_code":"mrs", "title":"Changing the Password for User admin", "uri":"admin_guide_000250.html", "doc_type":"usermanual", - "p_code":"516", - "code":"517" + "p_code":"520", + "code":"521" }, { - "desc":"During FusionInsight Manager installation, the system automatically creates user omm and ommdba on each node in the cluster. Periodically change the login passwords of th", + "desc":"During MRS Manager installation, the system automatically creates user omm and ommdba on each node in the cluster. Periodically change the login passwords of the OS users", "product_code":"mrs", "title":"Changing the Password for an OS User", "uri":"admin_guide_000251.html", "doc_type":"usermanual", - "p_code":"516", - "code":"518" + "p_code":"520", + "code":"522" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4667,8 +4703,8 @@ "title":"Changing the Password for a System Internal User", "uri":"admin_guide_000252.html", "doc_type":"usermanual", - "p_code":"510", - "code":"519" + "p_code":"514", + "code":"523" }, { "desc":"It is recommended that the administrator periodically change the password of Kerberos administrator kadmin to improve the system O&M security.If the user password is chan", @@ -4676,8 +4712,8 @@ "title":"Changing the Password for the Kerberos Administrator", "uri":"admin_guide_000253.html", "doc_type":"usermanual", - "p_code":"519", - "code":"520" + "p_code":"523", + "code":"524" }, { "desc":"It is recommended that the administrator periodically change the password of OMS Kerberos administrator kadmin to improve the system O&M security.If the user password is ", @@ -4685,8 +4721,8 @@ "title":"Changing the Password for the OMS Kerberos Administrator", "uri":"admin_guide_000254.html", "doc_type":"usermanual", - "p_code":"519", - "code":"521" + "p_code":"523", + "code":"525" }, { "desc":"It is recommended that the administrator periodically changes the passwords of LDAP administrator cn=root,dc=hadoop,dc=com and LDAP user cn=pg_search_dn,ou=Users,dc=hadoo", @@ -4694,8 +4730,8 @@ "title":"Changing the Passwords of the LDAP Administrator and the LDAP User (Including OMS LDAP)", "uri":"admin_guide_000255.html", "doc_type":"usermanual", - "p_code":"519", - "code":"522" + "p_code":"523", + "code":"526" }, { "desc":"It is recommended that the administrator periodically changes the passwords of LDAP administrator accounts cn=krbkdc,ou=Users,dc=hadoop,dc=com and cn=krbadmin,ou=Users,dc", @@ -4703,8 +4739,8 @@ "title":"Changing the Password for the LDAP Administrator", "uri":"admin_guide_000256.html", "doc_type":"usermanual", - "p_code":"519", - "code":"523" + "p_code":"523", + "code":"527" }, { "desc":"It is recommended that the administrator periodically change the password for each component running user to improve the system O&M security.Component running users can b", @@ -4712,8 +4748,8 @@ "title":"Changing the Password for a Component Running User", "uri":"admin_guide_000257.html", "doc_type":"usermanual", - "p_code":"519", - "code":"524" + "p_code":"523", + "code":"528" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4721,8 +4757,8 @@ "title":"Changing the Password for a Database User", "uri":"admin_guide_000258.html", "doc_type":"usermanual", - "p_code":"510", - "code":"525" + "p_code":"514", + "code":"529" }, { "desc":"It is recommended that the administrator periodically change the password of the OMS database administrator to improve the system O&M security.The password of user ommdba", @@ -4730,8 +4766,8 @@ "title":"Changing the Password of the OMS Database Administrator", "uri":"admin_guide_000259.html", "doc_type":"usermanual", - "p_code":"525", - "code":"526" + "p_code":"529", + "code":"530" }, { "desc":"It is recommended that the administrator periodically change the password of the user accessing the OMS database to improve the system O&M security.The OMS service needs ", @@ -4739,8 +4775,8 @@ "title":"Changing the Password for the Data Access User of the OMS Database", "uri":"admin_guide_000260.html", "doc_type":"usermanual", - "p_code":"525", - "code":"527" + "p_code":"529", + "code":"531" }, { "desc":"It is recommended that the administrator periodically change the password for each component database user to improve the system O&M security.This section applies only to", @@ -4748,8 +4784,8 @@ "title":"Changing the Password for a Component Database User", "uri":"admin_guide_000261.html", "doc_type":"usermanual", - "p_code":"525", - "code":"528" + "p_code":"529", + "code":"532" }, { "desc":"Default passwords for components in the MRS cluster to connect to the DBService database are random. You are advised to periodically reset the passwords of component data", @@ -4757,8 +4793,8 @@ "title":"Resetting the Component Database User Password", "uri":"admin_guide_000363.html", "doc_type":"usermanual", - "p_code":"525", - "code":"529" + "p_code":"529", + "code":"533" }, { "desc":"The password of user omm for the DBService database cannot be changed on the standby DBService node. Change the password on the active DBService node only.su - ommsource ", @@ -4766,8 +4802,8 @@ "title":"Changing the Password for User omm in DBService", "uri":"admin_guide_000354.html", "doc_type":"usermanual", - "p_code":"525", - "code":"530" + "p_code":"529", + "code":"534" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4775,17 +4811,17 @@ "title":"Security Hardening", "uri":"admin_guide_000271.html", "doc_type":"usermanual", - "p_code":"501", - "code":"531" + "p_code":"505", + "code":"535" }, { - "desc":"Tomcat is hardened as follows based on open-source software during FusionInsight Manager software installation and use:The Tomcat version is upgraded to the official vers", + "desc":"Tomcat is hardened as follows based on open-source software during MRS Manager software installation and use:The Tomcat version is upgraded to the official version.Permis", "product_code":"mrs", "title":"Hardening Policies", "uri":"admin_guide_000272.html", "doc_type":"usermanual", - "p_code":"531", - "code":"532" + "p_code":"535", + "code":"536" }, { "desc":"By default, the LDAP service deployed in the OMS and cluster can be accessed by any IP address. To enable the LDAP service to be accessed by only trusted IP addresses, yo", @@ -4793,8 +4829,8 @@ "title":"Configuring a Trusted IP Address to Access LDAP", "uri":"admin_guide_000274.html", "doc_type":"usermanual", - "p_code":"531", - "code":"533" + "p_code":"535", + "code":"537" }, { "desc":"Setting the HFile and WAL encryption mode to SMS4 or AES has a great impact on the system and will cause data loss in case of any misoperation. Therefore, this operation ", @@ -4802,8 +4838,8 @@ "title":"HFile and WAL Encryption", "uri":"admin_guide_000276.html", "doc_type":"usermanual", - "p_code":"531", - "code":"534" + "p_code":"535", + "code":"538" }, { "desc":"The channels between components are not encrypted by default. You can set the following parameters to configure security channel encryption.Page access for setting parame", @@ -4811,8 +4847,8 @@ "title":"Configuring Hadoop Security Parameters", "uri":"admin_guide_000277.html", "doc_type":"usermanual", - "p_code":"531", - "code":"535" + "p_code":"535", + "code":"539" }, { "desc":"If the Replication function is enabled for HBase clusters, a protection mechanism for data modification is added on the standby HBase cluster to ensure data consistency b", @@ -4820,8 +4856,8 @@ "title":"Configuring an IP Address Whitelist for Modification Allowed by HBase", "uri":"admin_guide_000278.html", "doc_type":"usermanual", - "p_code":"531", - "code":"536" + "p_code":"535", + "code":"540" }, { "desc":"When a cluster is installed, an encryption key is generated automatically by the system so that the security information in the cluster (such as all database user passwor", @@ -4829,8 +4865,8 @@ "title":"Updating a Key for a Cluster", "uri":"admin_guide_000279.html", "doc_type":"usermanual", - "p_code":"531", - "code":"537" + "p_code":"535", + "code":"541" }, { "desc":"In the cluster adopting the dual-plane networking, the LDAP is deployed on the service plane. To ensure the LDAP data security, you are advised to configure the firewall ", @@ -4838,8 +4874,8 @@ "title":"Hardening the LDAP", "uri":"admin_guide_000280.html", "doc_type":"usermanual", - "p_code":"531", - "code":"538" + "p_code":"535", + "code":"542" }, { "desc":"Data between the Kafka client and the broker is transmitted in plain text. The Kafka client may be deployed in an untrusted network, exposing the transmitting data to lea", @@ -4847,17 +4883,17 @@ "title":"Configuring Kafka Data Encryption During Transmission", "uri":"admin_guide_000281.html", "doc_type":"usermanual", - "p_code":"531", - "code":"539" + "p_code":"535", + "code":"543" }, { - "desc":"The channel between components is not encrypted by default. You can set parameters to enable security channel encryption.Navigation path for setting parameters: On Fusion", + "desc":"The channel between components is not encrypted by default. You can set parameters to enable security channel encryption.Navigation path for setting parameters: On MRS Ma", "product_code":"mrs", "title":"Configuring HDFS Data Encryption During Transmission", "uri":"admin_guide_000282.html", "doc_type":"usermanual", - "p_code":"531", - "code":"540" + "p_code":"535", + "code":"544" }, { "desc":"After a cluster is installed, Controller and Agent need to communicate with each other. The Kerberos authentication is used during the communication. By default, the comm", @@ -4865,8 +4901,8 @@ "title":"Encrypting the Communication Between the Controller and the Agent", "uri":"admin_guide_000284.html", "doc_type":"usermanual", - "p_code":"531", - "code":"541" + "p_code":"535", + "code":"545" }, { "desc":"During cluster installation, the system automatically generate the SSH public key and private key for user omm to establish the trust relationship between nodes. After th", @@ -4874,8 +4910,8 @@ "title":"Updating SSH Keys for User omm", "uri":"admin_guide_000285.html", "doc_type":"usermanual", - "p_code":"531", - "code":"542" + "p_code":"535", + "code":"546" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4883,17 +4919,17 @@ "title":"Security Maintenance", "uri":"admin_guide_000287.html", "doc_type":"usermanual", - "p_code":"501", - "code":"543" + "p_code":"505", + "code":"547" }, { - "desc":"It is recommended that the administrator conduct routine checks on the accounts. The check covers the following items:Check whether the accounts of the OS, FusionInsight ", + "desc":"It is recommended that the administrator conduct routine checks on the accounts. The check covers the following items:Check whether the accounts of the OS, MRS Manager, a", "product_code":"mrs", "title":"Account Maintenance Suggestions", "uri":"admin_guide_000289.html", "doc_type":"usermanual", - "p_code":"543", - "code":"544" + "p_code":"547", + "code":"548" }, { "desc":"User identity authentication is a must for accessing the application system. The complexity and validity period of user accounts and passwords must meet customers' securi", @@ -4901,8 +4937,8 @@ "title":"Password Maintenance Suggestions", "uri":"admin_guide_000290.html", "doc_type":"usermanual", - "p_code":"543", - "code":"545" + "p_code":"547", + "code":"549" }, { "desc":"Operation logs help discover exceptions such as illegal operations and login by unauthorized users. The system records important operations in logs. You can use operation", @@ -4910,8 +4946,8 @@ "title":"Log Maintenance Suggestions", "uri":"admin_guide_000291.html", "doc_type":"usermanual", - "p_code":"543", - "code":"546" + "p_code":"547", + "code":"550" }, { "desc":"MRS MRS cluster is a big data cluster that provides users with distributed data analysis and computing capabilities. The built-in JDK of MRS MRS is OpenJDK, which is used", @@ -4919,8 +4955,8 @@ "title":"Security Statement", "uri":"admin_guide_000315.html", "doc_type":"usermanual", - "p_code":"501", - "code":"547" + "p_code":"505", + "code":"551" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -4928,8 +4964,8 @@ "title":"Alarm Reference (Applicable to MRS 3.x)", "uri":"mrs_01_1298.html", "doc_type":"usermanual", - "p_code":"292", - "code":"548" + "p_code":"296", + "code":"552" }, { "desc":"Cluster audit logs need to be dumped on a third-party server due to the local historical data backup policy. The system starts to check the dump server at 3 a.m. every da", @@ -4937,8 +4973,8 @@ "title":"ALM-12001 Audit Log Dumping Failure", "uri":"ALM-12001.html", "doc_type":"alarm", - "p_code":"548", - "code":"549" + "p_code":"552", + "code":"553" }, { "desc":"The system checks LDAP resources every 60 seconds. This alarm is generated when the system detects that the LDAP resources in Manager are abnormal for six consecutive tim", @@ -4946,8 +4982,8 @@ "title":"ALM-12004 OLdap Resource Abnormal", "uri":"ALM-12004.html", "doc_type":"alarm", - "p_code":"548", - "code":"550" + "p_code":"552", + "code":"554" }, { "desc":"The alarm module checks the status of the Kerberos resource in Manager every 80 seconds. This alarm is generated when the alarm module detects that the Kerberos resources", @@ -4955,8 +4991,8 @@ "title":"ALM-12005 OKerberos Resource Abnormal", "uri":"ALM-12005.html", "doc_type":"alarm", - "p_code":"548", - "code":"551" + "p_code":"552", + "code":"555" }, { "desc":"Controller checks the NodeAgent heartbeat every 30 seconds. If Controller does not receive heartbeat messages from a NodeAgent, it attempts to restart the NodeAgent proce", @@ -4964,8 +5000,8 @@ "title":"ALM-12006 Node Fault", "uri":"ALM-12006.html", "doc_type":"alarm", - "p_code":"548", - "code":"552" + "p_code":"552", + "code":"556" }, { "desc":"This alarm is generated when the process health check module detects that the process connection status is Bad for three consecutive times. The process health check modul", @@ -4973,8 +5009,8 @@ "title":"ALM-12007 Process Fault", "uri":"ALM-12007.html", "doc_type":"alarm", - "p_code":"548", - "code":"553" + "p_code":"552", + "code":"557" }, { "desc":"This alarm is generated when the active Mager does not receive the heartbeat signal from the standby Manager within 7 seconds.This alarm is cleared when the active Manage", @@ -4982,8 +5018,8 @@ "title":"ALM-12010 Manager Heartbeat Interruption Between the Active and Standby Nodes", "uri":"ALM-12010.html", "doc_type":"alarm", - "p_code":"548", - "code":"554" + "p_code":"552", + "code":"558" }, { "desc":"The system checks data synchronization between the active and standby Manager nodes every 60 seconds. This alarm is generated when the standby Manager fails to synchroniz", @@ -4991,8 +5027,8 @@ "title":"ALM-12011 Manager Data Synchronization Exception Between the Active and Standby Nodes", "uri":"ALM-12011.html", "doc_type":"alarm", - "p_code":"548", - "code":"555" + "p_code":"552", + "code":"559" }, { "desc":"The system checks whether the NTP service on a node synchronizes time with the NTP service on the active OMS node every 60 seconds. This alarm is generated when the NTP s", @@ -5000,8 +5036,8 @@ "title":"ALM-12012 NTP Service Is Abnormal", "uri":"ALM-12012.html", "doc_type":"alarm", - "p_code":"548", - "code":"556" + "p_code":"552", + "code":"560" }, { "desc":"The system checks the partition status every 60 seconds. This alarm is generated when the system detects that a partition to which service directories are mounted is lost", @@ -5009,8 +5045,8 @@ "title":"ALM-12014 Partition Lost", "uri":"ALM-12014.html", "doc_type":"alarm", - "p_code":"548", - "code":"557" + "p_code":"552", + "code":"561" }, { "desc":"The system checks the partition status every 60 seconds. This alarm is generated when the system detects that a partition to which service directories are mounted enters ", @@ -5018,8 +5054,8 @@ "title":"ALM-12015 Partition Filesystem Readonly", "uri":"ALM-12015.html", "doc_type":"alarm", - "p_code":"548", - "code":"558" + "p_code":"552", + "code":"562" }, { "desc":"The system checks the CPU usage every 30 seconds and compares the actual CPU usage with the threshold. The CPU usage has a default threshold. This alarm is generated when", @@ -5027,8 +5063,8 @@ "title":"ALM-12016 CPU Usage Exceeds the Threshold", "uri":"ALM-12016.html", "doc_type":"alarm", - "p_code":"548", - "code":"559" + "p_code":"552", + "code":"563" }, { "desc":"The system checks the host disk usage of the system every 30 seconds and compares the actual disk usage with the threshold. The disk usage has a default threshold, this a", @@ -5036,8 +5072,8 @@ "title":"ALM-12017 Insufficient Disk Capacity", "uri":"ALM-12017.html", "doc_type":"alarm", - "p_code":"548", - "code":"560" + "p_code":"552", + "code":"564" }, { "desc":"The system checks the memory usage of the system every 30 seconds and compares the actual memory usage with the threshold. The memory usage has a default threshold, this ", @@ -5045,8 +5081,8 @@ "title":"ALM-12018 Memory Usage Exceeds the Threshold", "uri":"ALM-12018.html", "doc_type":"alarm", - "p_code":"548", - "code":"561" + "p_code":"552", + "code":"565" }, { "desc":"The system checks the PID usage every 30 seconds and compares the actual PID usage with the default PID usage threshold. This alarm is generated when the system detects t", @@ -5054,17 +5090,17 @@ "title":"ALM-12027 Host PID Usage Exceeds the Threshold", "uri":"ALM-12027.html", "doc_type":"alarm", - "p_code":"548", - "code":"562" + "p_code":"552", + "code":"566" }, { "desc":"The system checks the number of processes in the D stateand Z state of user omm on the host every 30 seconds and compares the actual number with the threshold. The number", "product_code":"mrs", - "title":"ALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold", + "title":"and Z StateALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold", "uri":"ALM-12028.html", "doc_type":"alarm", - "p_code":"548", - "code":"563" + "p_code":"552", + "code":"567" }, { "desc":"For HDDs, the alarm is triggered when any of the following conditions is met:The system runs the iostat command every 3 seconds, and detects that the svctm value exceeds ", @@ -5072,8 +5108,8 @@ "title":"ALM-12033 Slow Disk Fault", "uri":"ALM-12033.html", "doc_type":"alarm", - "p_code":"548", - "code":"564" + "p_code":"552", + "code":"568" }, { "desc":"The system executes the periodic backup task every 60 minutes. This alarm is generated when a periodical backup task fails to be executed. This alarm is cleared when the ", @@ -5081,8 +5117,8 @@ "title":"ALM-12034 Periodical Backup Failure", "uri":"ALM-12034.html", "doc_type":"alarm", - "p_code":"548", - "code":"565" + "p_code":"552", + "code":"569" }, { "desc":"After the recovery task fails, the system automatically rolls back every 60 minutes. If the rollback fails, data may be lost. If this occurs, an alarm is reported. This a", @@ -5090,8 +5126,8 @@ "title":"ALM-12035 Unknown Data Status After Recovery Task Failure", "uri":"ALM-12035.html", "doc_type":"alarm", - "p_code":"548", - "code":"566" + "p_code":"552", + "code":"570" }, { "desc":"The system checks the NTP server status every 60 seconds. This alarm is generated when the system detects that the NTP server is abnormal for 10 consecutive times.This al", @@ -5099,17 +5135,17 @@ "title":"ALM-12037 NTP Server Abnormal", "uri":"ALM-12037.html", "doc_type":"alarm", - "p_code":"548", - "code":"567" + "p_code":"552", + "code":"571" }, { - "desc":"After monitoring indicator dumping is configured on FusionInsight Manager, the system checks the monitoring indicator dumping result at the dumping interval (60 seconds b", + "desc":"After monitoring indicator dumping is configured on MRS Manager, the system checks the monitoring indicator dumping result at the dumping interval (60 seconds by default)", "product_code":"mrs", "title":"ALM-12038 Monitoring Indicator Dumping Failure", "uri":"ALM-12038.html", "doc_type":"alarm", - "p_code":"548", - "code":"568" + "p_code":"552", + "code":"572" }, { "desc":"The system checks the data synchronization status between the active and standby OMS Databases every 10 seconds. This alarm is generated when the synchronization status c", @@ -5117,8 +5153,8 @@ "title":"ALM-12039 Active/Standby OMS Databases Not Synchronized", "uri":"ALM-12039.html", "doc_type":"alarm", - "p_code":"548", - "code":"569" + "p_code":"552", + "code":"573" }, { "desc":"MRS 3.2.0-LTS.2 or later:The system checks whether the rng-tools or haveged tool has been enabled and correctly configured every 5 minutes. If neither tool is configured,", @@ -5126,8 +5162,8 @@ "title":"ALM-12040 Insufficient System Entropy", "uri":"ALM-12040.html", "doc_type":"alarm", - "p_code":"548", - "code":"570" + "p_code":"552", + "code":"574" }, { "desc":"The system checks whether the permission, user, and user group information about critical directories or files is normal every 5 minutes. This alarm is generated when the", @@ -5135,8 +5171,8 @@ "title":"ALM-12041 Incorrect Permission on Key Files", "uri":"ALM-12041.html", "doc_type":"alarm", - "p_code":"548", - "code":"571" + "p_code":"552", + "code":"575" }, { "desc":"The system checks whether critical configurations are correct every 5 minutes. This alarm is generated when the configurations are abnormal.This alarm is cleared when the", @@ -5144,8 +5180,8 @@ "title":"ALM-12042 Incorrect Configuration of Key Files", "uri":"ALM-12042.html", "doc_type":"alarm", - "p_code":"548", - "code":"572" + "p_code":"552", + "code":"576" }, { "desc":"The system checks the read packet dropped rate every 30 seconds. This alarm is generated when the read packet dropped rate exceeds the threshold (the default threshold is", @@ -5153,8 +5189,8 @@ "title":"ALM-12045 Read Packet Dropped Rate Exceeds the Threshold", "uri":"ALM-12045.html", "doc_type":"alarm", - "p_code":"548", - "code":"573" + "p_code":"552", + "code":"577" }, { "desc":"The system checks the write packet dropped rate every 30 seconds. This alarm is generated when the write packet dropped rate exceeds the threshold (the default threshold ", @@ -5162,8 +5198,8 @@ "title":"ALM-12046 Write Packet Dropped Rate Exceeds the Threshold", "uri":"ALM-12046.html", "doc_type":"alarm", - "p_code":"548", - "code":"574" + "p_code":"552", + "code":"578" }, { "desc":"The system checks the read packet error rate every 30 seconds. This alarm is generated when the read packet error rate exceeds the threshold (the default threshold is 0.5", @@ -5171,8 +5207,8 @@ "title":"ALM-12047 Read Packet Error Rate Exceeds the Threshold", "uri":"ALM-12047.html", "doc_type":"alarm", - "p_code":"548", - "code":"575" + "p_code":"552", + "code":"579" }, { "desc":"The system checks the write packet error rate every 30 seconds. This alarm is generated when the write packet error rate exceeds the threshold (the default threshold is 0", @@ -5180,8 +5216,8 @@ "title":"ALM-12048 Write Packet Error Rate Exceeds the Threshold", "uri":"ALM-12048.html", "doc_type":"alarm", - "p_code":"548", - "code":"576" + "p_code":"552", + "code":"580" }, { "desc":"The system checks the network read throughput rate every 30 seconds and compares the actual throughput rate with the threshold (the default threshold is 80%). This alarm ", @@ -5189,8 +5225,8 @@ "title":"ALM-12049 Network Read Throughput Rate Exceeds the Threshold", "uri":"ALM-12049.html", "doc_type":"alarm", - "p_code":"548", - "code":"577" + "p_code":"552", + "code":"581" }, { "desc":"The system checks the network write throughput rate every 30 seconds and compares the actual throughput rate with the threshold (the default threshold is 80%). This alarm", @@ -5198,8 +5234,8 @@ "title":"ALM-12050 Network Write Throughput Rate Exceeds the Threshold", "uri":"ALM-12050.html", "doc_type":"alarm", - "p_code":"548", - "code":"578" + "p_code":"552", + "code":"582" }, { "desc":"The system checks the disk Inode usage every 30 seconds and compares the actual Inode usage with the threshold (the default threshold is 80%). This alarm is generated whe", @@ -5207,8 +5243,8 @@ "title":"ALM-12051 Disk Inode Usage Exceeds the Threshold", "uri":"ALM-12051.html", "doc_type":"alarm", - "p_code":"548", - "code":"579" + "p_code":"552", + "code":"583" }, { "desc":"The system checks the TCP temporary port usage every 30 seconds and compares the actual usage with the threshold (the default threshold is 80%). This alarm is generated w", @@ -5216,8 +5252,8 @@ "title":"ALM-12052 TCP Temporary Port Usage Exceeds the Threshold", "uri":"ALM-12052.html", "doc_type":"alarm", - "p_code":"548", - "code":"580" + "p_code":"552", + "code":"584" }, { "desc":"The system checks the file handle usage every 30 seconds and compares the actual usage with the threshold (the default threshold is 80%). This alarm is generated when the", @@ -5225,8 +5261,8 @@ "title":"ALM-12053 Host File Handle Usage Exceeds the Threshold", "uri":"ALM-12053.html", "doc_type":"alarm", - "p_code":"548", - "code":"581" + "p_code":"552", + "code":"585" }, { "desc":"The system checks whether the certificate file is invalid (has expired or is not valid yet) on 23:00 every day. This alarm is generated when the certificate file is inval", @@ -5234,8 +5270,8 @@ "title":"ALM-12054 Invalid Certificate File", "uri":"ALM-12054.html", "doc_type":"alarm", - "p_code":"548", - "code":"582" + "p_code":"552", + "code":"586" }, { "desc":"The system checks the certificate file on 23:00 every day. This alarm is generated if the certificate file is about to expire within 30 days.This alarm is cleared when a ", @@ -5243,8 +5279,8 @@ "title":"ALM-12055 The Certificate File Is About to Expire", "uri":"ALM-12055.html", "doc_type":"alarm", - "p_code":"548", - "code":"583" + "p_code":"552", + "code":"587" }, { "desc":"After the system is installed, it checks whether the task for periodically backing up metadata to the third-party server, and then performs the check hourly. If the task ", @@ -5252,8 +5288,8 @@ "title":"ALM-12057 Metadata Not Configured with the Task to Periodically Back Up Data to a Third-Party Server", "uri":"ALM-12057.html", "doc_type":"alarm", - "p_code":"548", - "code":"584" + "p_code":"552", + "code":"588" }, { "desc":"The system checks the usage of the omm process every 30 seconds. Users can run the ps -o nlwp, pid, args, -u omm | awk '{sum+=$1} END {print \"\", sum}' command to obtain t", @@ -5261,8 +5297,8 @@ "title":"ALM-12061 Process Usage Exceeds the Threshold", "uri":"ALM-12061.html", "doc_type":"alarm", - "p_code":"548", - "code":"585" + "p_code":"552", + "code":"589" }, { "desc":"The system checks whether the OMS parameter configurations match with the cluster scale at each top hour. If the OMS parameter configurations do not meet the cluster scal", @@ -5270,8 +5306,8 @@ "title":"ALM-12062 OMS Parameter Configurations Mismatch with the Cluster Scale", "uri":"ALM-12062.html", "doc_type":"alarm", - "p_code":"548", - "code":"586" + "p_code":"552", + "code":"590" }, { "desc":"The system checks whether the data disk of the current host is available at the top of each hour. The system creates files, writes files, and deletes files in the mount d", @@ -5279,8 +5315,8 @@ "title":"ALM-12063 Unavailable Disk", "uri":"ALM-12063.html", "doc_type":"alarm", - "p_code":"548", - "code":"587" + "p_code":"552", + "code":"591" }, { "desc":"The system checks whether the random port range of the host conflicts with the range of ports used by the Cluster system every hour. The alarm is generated if they confli", @@ -5288,8 +5324,8 @@ "title":"ALM-12064 Host Random Port Range Conflicts with Cluster Used Port", "uri":"ALM-12064.html", "doc_type":"alarm", - "p_code":"548", - "code":"588" + "p_code":"552", + "code":"592" }, { "desc":"The system checks whether the trust relationship between the active OMS node and other Agent nodes is normal every hour. The alarm is generated if the mutual trust fails.", @@ -5297,8 +5333,8 @@ "title":"ALM-12066 Trust Relationships Between Nodes Become Invalid", "uri":"ALM-12066.html", "doc_type":"alarm", - "p_code":"548", - "code":"589" + "p_code":"552", + "code":"593" }, { "desc":"HA checks the Tomcat resources of Manager every 85 seconds. This alarm is generated when HA detects that the Tomcat resources are abnormal for two consecutive times.This ", @@ -5306,8 +5342,8 @@ "title":"ALM-12067 Tomcat Resource Is Abnormal", "uri":"ALM-12067.html", "doc_type":"alarm", - "p_code":"548", - "code":"590" + "p_code":"552", + "code":"594" }, { "desc":"HA checks the ACS resources of Manager every 80 seconds. This alarm is generated when HA detects that the ACS resources are abnormal for two consecutive times.This alarm ", @@ -5315,8 +5351,8 @@ "title":"ALM-12068 ACS Resource Exception", "uri":"ALM-12068.html", "doc_type":"alarm", - "p_code":"548", - "code":"591" + "p_code":"552", + "code":"595" }, { "desc":"HA checks the AOS resources of Manager every 81 seconds. This alarm is generated when HA detects that the AOS resources are abnormal for two consecutive times.This alarm ", @@ -5324,8 +5360,8 @@ "title":"ALM-12069 AOS Resource Exception", "uri":"ALM-12069.html", "doc_type":"alarm", - "p_code":"548", - "code":"592" + "p_code":"552", + "code":"596" }, { "desc":"HA checks the controller resources of Manager every 80 seconds. This alarm is generated when HA detects that the controller resources are abnormal for 2 consecutive times", @@ -5333,8 +5369,8 @@ "title":"ALM-12070 Controller Resource Is Abnormal", "uri":"ALM-12070.html", "doc_type":"alarm", - "p_code":"548", - "code":"593" + "p_code":"552", + "code":"597" }, { "desc":"HA checks the httpd resources of Manager every 120 seconds. This alarm is generated when HA detects that the httpd resources are abnormal for 10 consecutive times.This al", @@ -5342,8 +5378,8 @@ "title":"ALM-12071 Httpd Resource Is Abnormal", "uri":"ALM-12071.html", "doc_type":"alarm", - "p_code":"548", - "code":"594" + "p_code":"552", + "code":"598" }, { "desc":"HA checks the floatip resources of Manager every 9 seconds. This alarm is generated when HA detects that the floatip resources are abnormal for 3 consecutive times.This a", @@ -5351,8 +5387,8 @@ "title":"ALM-12072 FloatIP Resource Is Abnormal", "uri":"ALM-12072.html", "doc_type":"alarm", - "p_code":"548", - "code":"595" + "p_code":"552", + "code":"599" }, { "desc":"HA checks the cep resources of Manager every 60 seconds. This alarm is generated when HA detects that the cep resources are abnormal for 2 consecutive times.This alarm is", @@ -5360,8 +5396,8 @@ "title":"ALM-12073 CEP Resource Is Abnormal", "uri":"ALM-12073.html", "doc_type":"alarm", - "p_code":"548", - "code":"596" + "p_code":"552", + "code":"600" }, { "desc":"HA checks the fms resources of Manager every 60 seconds. This alarm is generated when HA detects that the fms resources are abnormal for 2 consecutive times.This alarm is", @@ -5369,8 +5405,8 @@ "title":"ALM-12074 FMS Resource Is Abnormal", "uri":"ALM-12074.html", "doc_type":"alarm", - "p_code":"548", - "code":"597" + "p_code":"552", + "code":"601" }, { "desc":"HA checks the pms resources of Manager every 55 seconds. This alarm is generated when HA detects that the pms resources are abnormal for three consecutive times.This alar", @@ -5378,8 +5414,8 @@ "title":"ALM-12075 PMS Resource Is Abnormal", "uri":"ALM-12075.html", "doc_type":"alarm", - "p_code":"548", - "code":"598" + "p_code":"552", + "code":"602" }, { "desc":"HA checks the Manager database every 10 seconds. This alarm is generated when HA detects that the database is abnormal for 3 consecutive times.This alarm is cleared when ", @@ -5387,8 +5423,8 @@ "title":"ALM-12076 GaussDB Resource Is Abnormal", "uri":"ALM-12076.html", "doc_type":"alarm", - "p_code":"548", - "code":"599" + "p_code":"552", + "code":"603" }, { "desc":"The system starts at 00:00 every day to check whether user omm has expired every eight hours. This alarm is generated if the user account has expired.This alarm is cleare", @@ -5396,8 +5432,8 @@ "title":"ALM-12077 User omm Expired", "uri":"ALM-12077.html", "doc_type":"alarm", - "p_code":"548", - "code":"600" + "p_code":"552", + "code":"604" }, { "desc":"The system starts at 00:00 every day to check whether the password of user omm has expired every 8 hours. This alarm is generated if the password has expired.This alarm i", @@ -5405,8 +5441,8 @@ "title":"ALM-12078 Password of User omm Expired", "uri":"ALM-12078.html", "doc_type":"alarm", - "p_code":"548", - "code":"601" + "p_code":"552", + "code":"605" }, { "desc":"The system starts at 00:00 every day to check whether user omm is about to expire every 8 hours. This alarm is generated if the user account will expire no less than 15 d", @@ -5414,8 +5450,8 @@ "title":"ALM-12079 User omm Is About to Expire", "uri":"ALM-12079.html", "doc_type":"alarm", - "p_code":"548", - "code":"602" + "p_code":"552", + "code":"606" }, { "desc":"The system starts at 00:00 every day to check whether the password of user omm is about to expire every 8 hours. This alarm is generated if the password will expire no le", @@ -5423,17 +5459,17 @@ "title":"ALM-12080 Password of User omm Is About to Expire", "uri":"ALM-12080.html", "doc_type":"alarm", - "p_code":"548", - "code":"603" + "p_code":"552", + "code":"607" }, { "desc":"The system starts at 00:00 every day to check whether user ommdba has expired every 8 hours. This alarm is generated if the user account has expired.This alarm is cleared", "product_code":"mrs", - "title":"ALM-12081User ommdba Expired", + "title":"ALM-12081 User ommdba Expired", "uri":"ALM-12081.html", "doc_type":"alarm", - "p_code":"548", - "code":"604" + "p_code":"552", + "code":"608" }, { "desc":"The system starts at 00:00 every day to check whether user ommdba is about to expire every 8 hours. This alarm is generated if the user account will expire no less than 1", @@ -5441,8 +5477,8 @@ "title":"ALM-12082 User ommdba Is About to Expire", "uri":"ALM-12082.html", "doc_type":"alarm", - "p_code":"548", - "code":"605" + "p_code":"552", + "code":"609" }, { "desc":"The system starts at 00:00 every day to check whether the password of user ommdba is about to expire every 8 hours. This alarm is generated if the password is about to ex", @@ -5450,8 +5486,8 @@ "title":"ALM-12083 Password of User ommdba Is About to Expire", "uri":"ALM-12083.html", "doc_type":"alarm", - "p_code":"548", - "code":"606" + "p_code":"552", + "code":"610" }, { "desc":"The system starts at 00:00 every day to check whether the password of user ommdba has expired every 8 hours. This alarm is generated if the password has expired.This alar", @@ -5459,8 +5495,8 @@ "title":"ALM-12084 Password of User ommdba Expired", "uri":"ALM-12084.html", "doc_type":"alarm", - "p_code":"548", - "code":"607" + "p_code":"552", + "code":"611" }, { "desc":"The system dumps service audit logs at 03:00 every day and stores them on the OMS node. This alarm is generated when the dump fails. This alarm is cleared when the next d", @@ -5468,8 +5504,8 @@ "title":"ALM-12085 Service Audit Log Dump Failure", "uri":"ALM-12085.html", "doc_type":"alarm", - "p_code":"548", - "code":"608" + "p_code":"552", + "code":"612" }, { "desc":"The system checks whether it is in the upgrade observation period at 00:00 every day and checks whether the duration that it has been in the upgrade observation state exc", @@ -5477,8 +5513,8 @@ "title":"ALM-12087 System Is in the Upgrade Observation Period", "uri":"ALM-12087.html", "doc_type":"alarm", - "p_code":"548", - "code":"609" + "p_code":"552", + "code":"613" }, { "desc":"The alarm module checks the network health status of nodes in the cluster every 10 seconds. This alarm is generated when the network between two nodes is unreachable or t", @@ -5486,8 +5522,8 @@ "title":"ALM-12089 Inter-Node Network Is Abnormal", "uri":"ALM-12089.html", "doc_type":"alarm", - "p_code":"548", - "code":"610" + "p_code":"552", + "code":"614" }, { "desc":"After the AZ DR function is enabled, the system checks the AZ health status every 5 minutes. This alarm is generated when the system detects that the AZ is subhealthy or ", @@ -5495,8 +5531,8 @@ "title":"ALM-12101 AZ Unhealthy", "uri":"ALM-12101.html", "doc_type":"alarm", - "p_code":"548", - "code":"611" + "p_code":"552", + "code":"615" }, { "desc":"The alarm module checks the deployment status of AZ HA components every 5 minutes. This alarm is generated when the components that support DR are not deployed based on D", @@ -5504,8 +5540,8 @@ "title":"ALM-12102 AZ HA Component Is Not Deployed Based on DR Requirements", "uri":"ALM-12102.html", "doc_type":"alarm", - "p_code":"548", - "code":"612" + "p_code":"552", + "code":"616" }, { "desc":"HA checks the Executor resources of Manager every 30 seconds. This alarm is generated when HA detects that the Executor resources are abnormal for two consecutive times.T", @@ -5513,8 +5549,8 @@ "title":"ALM-12103 Executor Resource Exception", "uri":"ALM-12103.html", "doc_type":"alarm", - "p_code":"548", - "code":"613" + "p_code":"552", + "code":"617" }, { "desc":"HA checks the Knox resources of Manager every 70 seconds. This alarm is generated when HA detects that the Knox resources are abnormal for three consecutive times.This al", @@ -5522,8 +5558,8 @@ "title":"ALM-12104 Abnormal Knox Resources", "uri":"ALM-12104.html", "doc_type":"alarm", - "p_code":"548", - "code":"614" + "p_code":"552", + "code":"618" }, { "desc":"The meta service periodically obtains the temporary AK/SK of the ECS. This alarm is generated when the meta service fails to obtain the temporary AK/SK.In storage-compute", @@ -5531,8 +5567,8 @@ "title":"ALM-12110 Failed to get ECS temporary AK/SK", "uri":"ALM-12110.html", "doc_type":"alarm", - "p_code":"548", - "code":"615" + "p_code":"552", + "code":"619" }, { "desc":"After metric sharing is enabled for a cluster, the Controller periodically collects cluster metrics and reports them to Cloud Eye.MRS monitoring metrics are unavailable o", @@ -5540,8 +5576,8 @@ "title":"ALM-12172 Failed to Report Metrics to Cloud Eye", "uri":"ALM-12172.html", "doc_type":"usermanual", - "p_code":"548", - "code":"616" + "p_code":"552", + "code":"620" }, { "desc":"For HDDs, the alarm is triggered when any of the following conditions is met:The system collects data every 3 seconds, and detects that the svctm value exceeds 6s for 10 ", @@ -5549,8 +5585,8 @@ "title":"ALM-12180 Suspended Disk I/O", "uri":"ALM-12180.html", "doc_type":"usermanual", - "p_code":"548", - "code":"617" + "p_code":"552", + "code":"621" }, { "desc":"The system periodically checks the number of connections to all Knox topologies. This alarm is generated when the number of connections to a topology exceeds the threshol", @@ -5558,8 +5594,8 @@ "title":"ALM-12190 Number of Knox Connections Exceeds the Threshold", "uri":"ALM-12190.html", "doc_type":"usermanual", - "p_code":"548", - "code":"618" + "p_code":"552", + "code":"622" }, { "desc":"The system checks the ZooKeeper service status every 60 seconds. This alarm is generated when the ZooKeeper service is unavailable.This alarm is cleared when the ZooKeepe", @@ -5567,8 +5603,8 @@ "title":"ALM-13000 ZooKeeper Service Unavailable", "uri":"ALM-13000.html", "doc_type":"alarm", - "p_code":"548", - "code":"619" + "p_code":"552", + "code":"623" }, { "desc":"The system checks ZooKeeper connections every 60 seconds. This alarm is generated when the system detects that the number of used ZooKeeper instance connections exceeds t", @@ -5576,8 +5612,8 @@ "title":"ALM-13001 Available ZooKeeper Connections Are Insufficient", "uri":"ALM-13001.html", "doc_type":"alarm", - "p_code":"548", - "code":"620" + "p_code":"552", + "code":"624" }, { "desc":"The system checks the direct memory usage of the ZooKeeper service every 30 seconds. The alarm is generated when the direct memory usage of a ZooKeeper instance exceeds t", @@ -5585,8 +5621,8 @@ "title":"ALM-13002 ZooKeeper Direct Memory Usage Exceeds the Threshold", "uri":"ALM-13002.html", "doc_type":"alarm", - "p_code":"548", - "code":"621" + "p_code":"552", + "code":"625" }, { "desc":"The system checks the garbage collection (GC) duration of the ZooKeeper process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 s", @@ -5594,8 +5630,8 @@ "title":"ALM-13003 GC Duration of the ZooKeeper Process Exceeds the Threshold", "uri":"ALM-13003.html", "doc_type":"alarm", - "p_code":"548", - "code":"622" + "p_code":"552", + "code":"626" }, { "desc":"The system checks the heap memory usage of the ZooKeeper service every 60 seconds. The alarm is generated when the heap memory usage of a ZooKeeper instance exceeds the t", @@ -5603,8 +5639,8 @@ "title":"ALM-13004 ZooKeeper Heap Memory Usage Exceeds the Threshold", "uri":"ALM-13004.html", "doc_type":"alarm", - "p_code":"548", - "code":"623" + "p_code":"552", + "code":"627" }, { "desc":"The system sets quotas for each ZooKeeper top-level directory in the customized.quota configuration item and components every 5 hours. This alarm is generated when the sy", @@ -5612,8 +5648,8 @@ "title":"ALM-13005 Failed to Set the Quota of Top Directories of ZooKeeper Components", "uri":"ALM-13005.html", "doc_type":"alarm", - "p_code":"548", - "code":"624" + "p_code":"552", + "code":"628" }, { "desc":"The system periodically detects the status of secondary Znode in the ZooKeeper service data directory every four hours. This alarm is generated when the number or capacit", @@ -5621,8 +5657,8 @@ "title":"ALM-13006 Znode Number or Capacity Exceeds the Threshold", "uri":"ALM-13006.html", "doc_type":"alarm", - "p_code":"548", - "code":"625" + "p_code":"552", + "code":"629" }, { "desc":"The system periodically detects the number of active processes between the ZooKeeper client and the ZooKeeper server every 60 seconds. This alarm is generated when the nu", @@ -5630,8 +5666,8 @@ "title":"ALM-13007 Available ZooKeeper Client Connections Are Insufficient", "uri":"ALM-13007.html", "doc_type":"alarm", - "p_code":"548", - "code":"626" + "p_code":"552", + "code":"630" }, { "desc":"The system checks the level-2 Znode status in the ZooKeeper data directory every hour. This alarm is generated when the system detects that the level-2 Znode usage exceed", @@ -5639,8 +5675,8 @@ "title":"ALM-13008 ZooKeeper Znode Usage Exceeds the Threshold", "uri":"ALM-13008.html", "doc_type":"alarm", - "p_code":"548", - "code":"627" + "p_code":"552", + "code":"631" }, { "desc":"The system checks the level-2 ZNode status in the ZooKeeper data directory every hour. This alarm is generated when the system detects that the capacity usage exceeds the", @@ -5648,8 +5684,8 @@ "title":"ALM-13009 ZooKeeper Znode Capacity Usage Exceeds the Threshold", "uri":"ALM-13009.html", "doc_type":"alarm", - "p_code":"548", - "code":"628" + "p_code":"552", + "code":"632" }, { "desc":"The system checks the Znode usage of all service directories with quota configured every hour. This alarm is generated when the system detects that the level-2 Znode usag", @@ -5657,8 +5693,8 @@ "title":"ALM-13010 Znode Usage of a Directory with Quota Configured Exceeds the Threshold", "uri":"ALM-13010.html", "doc_type":"alarm", - "p_code":"548", - "code":"629" + "p_code":"552", + "code":"633" }, { "desc":"The system checks the NameService service status every 60 seconds. This alarm is generated when all the NameService services are abnormal and the system considers that th", @@ -5666,8 +5702,8 @@ "title":"ALM-14000 HDFS Service Unavailable", "uri":"ALM-14000.html", "doc_type":"alarm", - "p_code":"548", - "code":"630" + "p_code":"552", + "code":"634" }, { "desc":"The system checks the HDFS disk usage every 30 seconds and compares the actual HDFS disk usage with the threshold. The HDFS disk usage indicator has a default threshold, ", @@ -5675,8 +5711,8 @@ "title":"ALM-14001 HDFS Disk Usage Exceeds the Threshold", "uri":"ALM-14001.html", "doc_type":"alarm", - "p_code":"548", - "code":"631" + "p_code":"552", + "code":"635" }, { "desc":"The system checks the DataNode disk usage every 30 seconds and compares the actual disk usage with the threshold. A default threshold range is provided for the DataNode d", @@ -5684,8 +5720,8 @@ "title":"ALM-14002 DataNode Disk Usage Exceeds the Threshold", "uri":"ALM-14002.html", "doc_type":"alarm", - "p_code":"548", - "code":"632" + "p_code":"552", + "code":"636" }, { "desc":"The system checks the lost blocks every 30 seconds and compares the actual lost blocks with the threshold. The lost blocks indicator has a default threshold. This alarm i", @@ -5693,8 +5729,8 @@ "title":"ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold", "uri":"ALM-14003.html", "doc_type":"alarm", - "p_code":"548", - "code":"633" + "p_code":"552", + "code":"637" }, { "desc":"The system periodically checks the number of HDFS files every 30 seconds and compares the number of HDFS files with the threshold. This alarm is generated when the system", @@ -5702,8 +5738,8 @@ "title":"ALM-14006 Number of HDFS Files Exceeds the Threshold", "uri":"ALM-14006.html", "doc_type":"alarm", - "p_code":"548", - "code":"634" + "p_code":"552", + "code":"638" }, { "desc":"The system checks the HDFS NameNode Heap Memory usage every 30 seconds and compares the actual Heap memory usage with the threshold. The HDFS NameNode Heap Memory usage h", @@ -5711,8 +5747,8 @@ "title":"ALM-14007 NameNode Heap Memory Usage Exceeds the Threshold", "uri":"ALM-14007.html", "doc_type":"alarm", - "p_code":"548", - "code":"635" + "p_code":"552", + "code":"639" }, { "desc":"The system checks the HDFS DataNode Heap Memory usage every 30 seconds and compares the actual Heap Memory usage with the threshold. The HDFS DataNode Heap Memory usage h", @@ -5720,8 +5756,8 @@ "title":"ALM-14008 DataNode Heap Memory Usage Exceeds the Threshold", "uri":"ALM-14008.html", "doc_type":"alarm", - "p_code":"548", - "code":"636" + "p_code":"552", + "code":"640" }, { "desc":"The system periodically detects the number of dead DataNodes in the HDFS cluster every 30 seconds, and compares the number with the threshold. The number of DataNodes in ", @@ -5729,8 +5765,8 @@ "title":"ALM-14009 Number of Dead DataNodes Exceeds the Threshold", "uri":"ALM-14009.html", "doc_type":"alarm", - "p_code":"548", - "code":"637" + "p_code":"552", + "code":"641" }, { "desc":"The system checks the NameService service status every 180 seconds. This alarm is generated when the NameService service is unavailable.This alarm is cleared when the Nam", @@ -5738,8 +5774,8 @@ "title":"ALM-14010 NameService Service Is Abnormal", "uri":"ALM-14010.html", "doc_type":"alarm", - "p_code":"548", - "code":"638" + "p_code":"552", + "code":"642" }, { "desc":"The DataNode parameter dfs.datanode.data.dir specifies DataNode data directories. This alarm is generated when a configured data directory cannot be created, a data direc", @@ -5747,8 +5783,8 @@ "title":"ALM-14011 DataNode Data Directory Is Not Configured Properly", "uri":"ALM-14011.html", "doc_type":"alarm", - "p_code":"548", - "code":"639" + "p_code":"552", + "code":"643" }, { "desc":"On the active NameNode, the system checks the data consistency of all JournalNodes in the cluster every 5 minutes. This alarm is generated when the data on a JournalNode ", @@ -5756,8 +5792,8 @@ "title":"ALM-14012 JournalNode Is Out of Synchronization", "uri":"ALM-14012.html", "doc_type":"alarm", - "p_code":"548", - "code":"640" + "p_code":"552", + "code":"644" }, { "desc":"HDFS metadata is stored in the FsImage file of the NameNode data directory, which is specified by the dfs.namenode.name.dir configuration item. The standby NameNode perio", @@ -5765,8 +5801,8 @@ "title":"ALM-14013 Failed to Update the NameNode FsImage File", "uri":"ALM-14013.html", "doc_type":"alarm", - "p_code":"548", - "code":"641" + "p_code":"552", + "code":"645" }, { "desc":"The system checks the garbage collection (GC) duration of the NameNode process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 se", @@ -5774,8 +5810,8 @@ "title":"ALM-14014 NameNode GC Time Exceeds the Threshold", "uri":"ALM-14014.html", "doc_type":"alarm", - "p_code":"548", - "code":"642" + "p_code":"552", + "code":"646" }, { "desc":"The system checks the garbage collection (GC) duration of the DataNode process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 se", @@ -5783,8 +5819,8 @@ "title":"ALM-14015 DataNode GC Time Exceeds the Threshold", "uri":"ALM-14015.html", "doc_type":"alarm", - "p_code":"548", - "code":"643" + "p_code":"552", + "code":"647" }, { "desc":"The system checks the direct memory usage of HDFS every 30 seconds. This alarm is generated when the direct memory usage of DataNode instances exceeds the threshold (90% ", @@ -5792,8 +5828,8 @@ "title":"ALM-14016 DataNode Direct Memory Usage Exceeds the Threshold", "uri":"ALM-14016.html", "doc_type":"alarm", - "p_code":"548", - "code":"644" + "p_code":"552", + "code":"648" }, { "desc":"The system checks the direct memory usage of the HDFS service every 30 seconds. This alarm is generated when the direct memory usage of a NameNode instance exceeds the th", @@ -5801,8 +5837,8 @@ "title":"ALM-14017 NameNode Direct Memory Usage Exceeds the Threshold", "uri":"ALM-14017.html", "doc_type":"alarm", - "p_code":"548", - "code":"645" + "p_code":"552", + "code":"649" }, { "desc":"The system checks the non-heap memory usage of the HDFS NameNode every 30 seconds and compares the actual usage with the threshold. The non-heap memory usage of the HDFS ", @@ -5810,8 +5846,8 @@ "title":"ALM-14018 NameNode Non-heap Memory Usage Exceeds the Threshold", "uri":"ALM-14018.html", "doc_type":"alarm", - "p_code":"548", - "code":"646" + "p_code":"552", + "code":"650" }, { "desc":"The system checks the non-heap memory usage of the HDFS DataNode every 30 seconds and compares the actual usage with the threshold. The non-heap memory usage of the HDFS ", @@ -5819,8 +5855,8 @@ "title":"ALM-14019 DataNode Non-heap Memory Usage Exceeds the Threshold", "uri":"ALM-14019.html", "doc_type":"alarm", - "p_code":"548", - "code":"647" + "p_code":"552", + "code":"651" }, { "desc":"The system obtains the number of subfiles and subdirectories in a specified directory every hour and checks whether it reaches the percentage of the threshold (the maximu", @@ -5828,8 +5864,8 @@ "title":"ALM-14020 Number of Entries in the HDFS Directory Exceeds the Threshold", "uri":"ALM-14020.html", "doc_type":"alarm", - "p_code":"548", - "code":"648" + "p_code":"552", + "code":"652" }, { "desc":"The system checks the average RPC processing time of NameNode every 30 seconds, and compares the actual average RPC processing time with the threshold (default value: 100", @@ -5837,8 +5873,8 @@ "title":"ALM-14021 NameNode Average RPC Processing Time Exceeds the Threshold", "uri":"ALM-14021.html", "doc_type":"alarm", - "p_code":"548", - "code":"649" + "p_code":"552", + "code":"653" }, { "desc":"The system checks the average RPC queuing time of NameNode every 30 seconds, and compares the actual average RPC queuing time with the threshold (default value: 200 ms). ", @@ -5846,8 +5882,8 @@ "title":"ALM-14022 NameNode Average RPC Queuing Time Exceeds the Threshold", "uri":"ALM-14022.html", "doc_type":"alarm", - "p_code":"548", - "code":"650" + "p_code":"552", + "code":"654" }, { "desc":"The system checks the percentage of total reserved disk space for replicas (Total reserved disk space for replicas/(Total reserved disk space for replicas + Total remaini", @@ -5855,8 +5891,8 @@ "title":"ALM-14023 Percentage of Total Reserved Disk Space for Replicas Exceeds the Threshold", "uri":"ALM-14023.html", "doc_type":"alarm", - "p_code":"548", - "code":"651" + "p_code":"552", + "code":"655" }, { "desc":"The system checks the space usage (used space of each directory/space allocated to each directory) of each directory associated with a tenant every hour and compares the ", @@ -5864,8 +5900,8 @@ "title":"ALM-14024 Tenant Space Usage Exceeds the Threshold", "uri":"ALM-14024.html", "doc_type":"alarm", - "p_code":"548", - "code":"652" + "p_code":"552", + "code":"656" }, { "desc":"The system checks the file object usage (used file objects of each directory/number of file objects allocated to each directory) of each directory associated with a tenan", @@ -5873,8 +5909,8 @@ "title":"ALM-14025 Tenant File Object Usage Exceeds the Threshold", "uri":"ALM-14025.html", "doc_type":"alarm", - "p_code":"548", - "code":"653" + "p_code":"552", + "code":"657" }, { "desc":"The system checks the number of blocks on each DataNode every 30 seconds. This alarm is generated when the number of blocks on the DataNode exceeds the threshold.If Trigg", @@ -5882,8 +5918,8 @@ "title":"ALM-14026 Blocks on DataNode Exceed the Threshold", "uri":"ALM-14026.html", "doc_type":"alarm", - "p_code":"548", - "code":"654" + "p_code":"552", + "code":"658" }, { "desc":"The system checks the disk status on DataNodes every 60 seconds. This alarm is generated when a disk is faulty.After all faulty disks on the DataNode are recovered, you n", @@ -5891,8 +5927,8 @@ "title":"ALM-14027 DataNode Disk Fault", "uri":"ALM-14027.html", "doc_type":"alarm", - "p_code":"548", - "code":"655" + "p_code":"552", + "code":"659" }, { "desc":"The system checks the number of blocks to be supplemented every 30 seconds and compares the number with the threshold. The number of blocks to be supplemented has a defau", @@ -5900,8 +5936,8 @@ "title":"ALM-14028 Number of Blocks to Be Supplemented Exceeds the Threshold", "uri":"ALM-14028.html", "doc_type":"alarm", - "p_code":"548", - "code":"656" + "p_code":"552", + "code":"660" }, { "desc":"The system checks the number of blocks in a single replica every four hours and compares the number with the threshold. There is a threshold for the number of blocks in a", @@ -5909,8 +5945,8 @@ "title":"ALM-14029 Number of Blocks in a Replica Exceeds the Threshold", "uri":"ALM-14029.html", "doc_type":"alarm", - "p_code":"548", - "code":"657" + "p_code":"552", + "code":"661" }, { "desc":"This alarm is generated when dfs.single.replication.enable is set to true, indicating that HDFS is configured to allow write of single-replica data.This alarm is cleared ", @@ -5918,8 +5954,8 @@ "title":"ALM-14030 HDFS Allows Write of Single-Replica Data", "uri":"ALM-14030.html", "doc_type":"usermanual", - "p_code":"548", - "code":"658" + "p_code":"552", + "code":"662" }, { "desc":"The system detects the percentage of sessions connected to the HiveServer to the maximum number of allowed sessions every 30 seconds. This indicator can be viewed on the ", @@ -5927,8 +5963,8 @@ "title":"ALM-16000 Percentage of Sessions Connected to the HiveServer to Maximum Number Allowed Exceeds the Threshold", "uri":"ALM-16000.html", "doc_type":"alarm", - "p_code":"548", - "code":"659" + "p_code":"552", + "code":"663" }, { "desc":"This alarm is generated when the Hive warehouse space usage exceeds the specified threshold (85% by default). The system checks the Hive data warehouse space usage every ", @@ -5936,8 +5972,8 @@ "title":"ALM-16001 Hive Warehouse Space Usage Exceeds the Threshold", "uri":"ALM-16001.html", "doc_type":"alarm", - "p_code":"548", - "code":"660" + "p_code":"552", + "code":"664" }, { "desc":"The system checks the percentage of the HQL statements that are executed successfully in every 30 seconds. The formula is: Percentage of HQL statements that are executed ", @@ -5945,8 +5981,8 @@ "title":"ALM-16002 Hive SQL Execution Success Rate Is Lower Than the Threshold", "uri":"ALM-16002.html", "doc_type":"alarm", - "p_code":"548", - "code":"661" + "p_code":"552", + "code":"665" }, { "desc":"The system checks the background thread usage in every 30 seconds. This alarm is generated when the usage of the background thread pool of Hive exceeds the threshold, 90%", @@ -5954,8 +5990,8 @@ "title":"ALM-16003 Background Thread Usage Exceeds the Threshold", "uri":"ALM-16003.html", "doc_type":"alarm", - "p_code":"548", - "code":"662" + "p_code":"552", + "code":"666" }, { "desc":"This alarm is generated when the HiveServer service is unavailable. The system checks the HiveServer service status every 60 seconds.This alarm is cleared when the HiveSe", @@ -5963,8 +5999,8 @@ "title":"ALM-16004 Hive Service Unavailable", "uri":"ALM-16004.html", "doc_type":"alarm", - "p_code":"548", - "code":"663" + "p_code":"552", + "code":"667" }, { "desc":"The system checks the Hive service status every 30 seconds. The alarm is generated when the heap memory usage of an Hive service exceeds the threshold (95% of the maximum", @@ -5972,8 +6008,8 @@ "title":"ALM-16005 The Heap Memory Usage of the Hive Process Exceeds the Threshold", "uri":"ALM-16005.html", "doc_type":"alarm", - "p_code":"548", - "code":"664" + "p_code":"552", + "code":"668" }, { "desc":"The system checks the Hive service status every 30 seconds. The alarm is generated when the direct memory usage of an Hive service exceeds the threshold (95% of the maxim", @@ -5981,8 +6017,8 @@ "title":"ALM-16006 The Direct Memory Usage of the Hive Process Exceeds the Threshold", "uri":"ALM-16006.html", "doc_type":"alarm", - "p_code":"548", - "code":"665" + "p_code":"552", + "code":"669" }, { "desc":"The system checks the garbage collection (GC) time of the Hive service every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (exceeds ", @@ -5990,8 +6026,8 @@ "title":"ALM-16007 Hive GC Time Exceeds the Threshold", "uri":"ALM-16007.html", "doc_type":"alarm", - "p_code":"548", - "code":"666" + "p_code":"552", + "code":"670" }, { "desc":"The system checks the Hive service status every 30 seconds. The alarm is generated when the non-heap memory usage of an Hive service exceeds the threshold (95% of the max", @@ -5999,8 +6035,8 @@ "title":"ALM-16008 Non-Heap Memory Usage of the Hive Process Exceeds the Threshold", "uri":"ALM-16008.html", "doc_type":"alarm", - "p_code":"548", - "code":"667" + "p_code":"552", + "code":"671" }, { "desc":"The system checks the number of HQL maps in every 30 seconds. This alarm is generated if the number exceeds the threshold. By default, Trigger Count is set to 3, and the ", @@ -6008,8 +6044,8 @@ "title":"ALM-16009 Map Number Exceeds the Threshold", "uri":"ALM-16009.html", "doc_type":"alarm", - "p_code":"548", - "code":"668" + "p_code":"552", + "code":"672" }, { "desc":"The system checks the Hive data warehouse in every 60 seconds.This alarm is generated when the Hive data warehouse is deleted.The default Hive data warehouse is deleted. ", @@ -6017,8 +6053,8 @@ "title":"ALM-16045 Hive Data Warehouse Is Deleted", "uri":"ALM-16045.html", "doc_type":"alarm", - "p_code":"548", - "code":"669" + "p_code":"552", + "code":"673" }, { "desc":"The system checks the Hive data warehouse permission in every 60 seconds. This alarm is generated if the permission is modified.If the permission on the Hive default data", @@ -6026,8 +6062,8 @@ "title":"ALM-16046 Hive Data Warehouse Permission Is Modified", "uri":"ALM-16046.html", "doc_type":"alarm", - "p_code":"548", - "code":"670" + "p_code":"552", + "code":"674" }, { "desc":"The system checks the Hive service every 60 seconds. This alarm is generated when Hive registration information on ZooKeeper is lost or Hive cannot connect to ZooKeeper.I", @@ -6035,8 +6071,8 @@ "title":"ALM-16047 HiveServer Has Been Deregistered from ZooKeeper", "uri":"ALM-16047.html", "doc_type":"alarm", - "p_code":"548", - "code":"671" + "p_code":"552", + "code":"675" }, { "desc":"The system checks the Tez and Spark library paths every 180 seconds. This alarm is generated when the Tez or Spark library path does not exist.The Hive on Tez and Hive on", @@ -6044,8 +6080,8 @@ "title":"ALM-16048 Tez or Spark Library Path Does Not Exist", "uri":"ALM-16048.html", "doc_type":"usermanual", - "p_code":"548", - "code":"672" + "p_code":"552", + "code":"676" }, { "desc":"The system checks the Oozie service status in every 5 seconds. This alarm is generated when Oozie or a component on which Oozie depends cannot provide services properly.", @@ -6053,8 +6089,8 @@ "title":"ALM-17003 Oozie Service Unavailable", "uri":"ALM-17003.html", "doc_type":"alarm", - "p_code":"548", - "code":"673" + "p_code":"552", + "code":"677" }, { "desc":"The system checks the heap memory usage of the Oozie service every 60 seconds. The alarm is generated when the heap memory usage of a Metadata instance exceeds the thresh", @@ -6062,8 +6098,8 @@ "title":"ALM-17004 Oozie Heap Memory Usage Exceeds the Threshold", "uri":"ALM-17004.html", "doc_type":"alarm", - "p_code":"548", - "code":"674" + "p_code":"552", + "code":"678" }, { "desc":"The system checks the non heap memory usage of Oozie every 30 seconds. This alarm is reported if the non heap memory usage of Oozie exceeds the threshold (80%). This alar", @@ -6071,8 +6107,8 @@ "title":"ALM-17005 Oozie Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-17005.html", "doc_type":"alarm", - "p_code":"548", - "code":"675" + "p_code":"552", + "code":"679" }, { "desc":"The system checks the direct memory usage of the Oozie service every 30 seconds. The alarm is generated when the direct memory usage of an Oozie instance exceeds the thre", @@ -6080,8 +6116,8 @@ "title":"ALM-17006 Oozie Direct Memory Usage Exceeds the Threshold", "uri":"ALM-17006.html", "doc_type":"alarm", - "p_code":"548", - "code":"676" + "p_code":"552", + "code":"680" }, { "desc":"The system checks GC time of the Oozie process every 60 seconds. The alarm is generated when GC time of the Oozie process exceeds the threshold (default value: 12 seconds", @@ -6089,8 +6125,8 @@ "title":"ALM-17007 Garbage Collection (GC) Time of the Oozie Process Exceeds the Threshold", "uri":"ALM-17007.html", "doc_type":"alarm", - "p_code":"548", - "code":"677" + "p_code":"552", + "code":"681" }, { "desc":"This alarm is generated when the Yarn service is unavailable. The alarm module checks the Yarn service status every 60 seconds.The alarm is cleared when the Yarn service ", @@ -6098,8 +6134,8 @@ "title":"ALM-18000 Yarn Service Unavailable", "uri":"ALM-18000.html", "doc_type":"alarm", - "p_code":"548", - "code":"678" + "p_code":"552", + "code":"682" }, { "desc":"The system checks the number of lost NodeManager nodes every 30 seconds, and compares the number with the threshold. The Number of Lost Nodes indicator has a default thre", @@ -6107,8 +6143,8 @@ "title":"ALM-18002 NodeManager Heartbeat Lost", "uri":"ALM-18002.html", "doc_type":"alarm", - "p_code":"548", - "code":"679" + "p_code":"552", + "code":"683" }, { "desc":"The system checks the number of unhealthy NodeManager nodes every 30 seconds, and compares the number with the threshold. The Unhealthy Nodes indicator has a default thre", @@ -6116,8 +6152,8 @@ "title":"ALM-18003 NodeManager Unhealthy", "uri":"ALM-18003.html", "doc_type":"alarm", - "p_code":"548", - "code":"680" + "p_code":"552", + "code":"684" }, { "desc":"The system checks the heap memory usage of Yarn ResourceManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap me", @@ -6125,8 +6161,8 @@ "title":"ALM-18008 Heap Memory Usage of ResourceManager Exceeds the Threshold", "uri":"ALM-18008.html", "doc_type":"alarm", - "p_code":"548", - "code":"681" + "p_code":"552", + "code":"685" }, { "desc":"The system checks the heap memory usage of Mapreduce JobHistoryServer every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the h", @@ -6134,8 +6170,8 @@ "title":"ALM-18009 Heap Memory Usage of JobHistoryServer Exceeds the Threshold", "uri":"ALM-18009.html", "doc_type":"alarm", - "p_code":"548", - "code":"682" + "p_code":"552", + "code":"686" }, { "desc":"The system checks the garbage collection (GC) duration of the ResourceManager process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold", @@ -6143,8 +6179,8 @@ "title":"ALM-18010 ResourceManager GC Time Exceeds the Threshold", "uri":"ALM-18010.html", "doc_type":"alarm", - "p_code":"548", - "code":"683" + "p_code":"552", + "code":"687" }, { "desc":"The system checks the garbage collection (GC) duration of the NodeManager process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12", @@ -6152,8 +6188,8 @@ "title":"ALM-18011 NodeManager GC Time Exceeds the Threshold", "uri":"ALM-18011.html", "doc_type":"alarm", - "p_code":"548", - "code":"684" + "p_code":"552", + "code":"688" }, { "desc":"The system checks the garbage collection (GC) duration of the JobHistoryServer process every 60 seconds. This alarm is generated when the GC duration exceeds the threshol", @@ -6161,8 +6197,8 @@ "title":"ALM-18012 JobHistoryServer GC Time Exceeds the Threshold", "uri":"ALM-18012.html", "doc_type":"alarm", - "p_code":"548", - "code":"685" + "p_code":"552", + "code":"689" }, { "desc":"The system checks the direct memory usage of the Yarn service every 30 seconds. This alarm is generated when the direct memory usage of a ResourceManager instance exceeds", @@ -6170,8 +6206,8 @@ "title":"ALM-18013 ResourceManager Direct Memory Usage Exceeds the Threshold", "uri":"ALM-18013.html", "doc_type":"alarm", - "p_code":"548", - "code":"686" + "p_code":"552", + "code":"690" }, { "desc":"The system checks the direct memory usage of the Yarn service every 30 seconds. This alarm is generated when the direct memory usage of a NodeManager instance exceeds the", @@ -6179,8 +6215,8 @@ "title":"ALM-18014 NodeManager Direct Memory Usage Exceeds the Threshold", "uri":"ALM-18014.html", "doc_type":"alarm", - "p_code":"548", - "code":"687" + "p_code":"552", + "code":"691" }, { "desc":"The system checks the direct memory usage of the MapReduce service every 30 seconds. This alarm is generated when the direct memory usage of a JobHistoryServer instance e", @@ -6188,8 +6224,8 @@ "title":"ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold", "uri":"ALM-18015.html", "doc_type":"alarm", - "p_code":"548", - "code":"688" + "p_code":"552", + "code":"692" }, { "desc":"The system checks the Non Heap memory usage of Yarn ResourceManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the Non", @@ -6197,8 +6233,8 @@ "title":"ALM-18016 Non Heap Memory Usage of ResourceManager Exceeds the Threshold", "uri":"ALM-18016.html", "doc_type":"alarm", - "p_code":"548", - "code":"689" + "p_code":"552", + "code":"693" }, { "desc":"The system checks the Non Heap memory usage of Yarn NodeManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the Non Hea", @@ -6206,8 +6242,8 @@ "title":"ALM-18017 Non Heap Memory Usage of NodeManager Exceeds the Threshold", "uri":"ALM-18017.html", "doc_type":"alarm", - "p_code":"548", - "code":"690" + "p_code":"552", + "code":"694" }, { "desc":"The system checks the heap memory usage of Yarn NodeManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap memory", @@ -6215,8 +6251,8 @@ "title":"ALM-18018 NodeManager Heap Memory Usage Exceeds the Threshold", "uri":"ALM-18018.html", "doc_type":"alarm", - "p_code":"548", - "code":"691" + "p_code":"552", + "code":"695" }, { "desc":"The system checks the Non Heap memory usage of MapReduce JobHistoryServer every 30 seconds and compares the actual usage with the threshold. The alarm is generated when t", @@ -6224,8 +6260,8 @@ "title":"ALM-18019 Non Heap Memory Usage of JobHistoryServer Exceeds the Threshold", "uri":"ALM-18019.html", "doc_type":"alarm", - "p_code":"548", - "code":"692" + "p_code":"552", + "code":"696" }, { "desc":"The system checks MapReduce and Spark tasks (except for permanent JDBC tasks) submitted to Yarn every 15 minutes. This alarm is generated when the task execution time exc", @@ -6233,8 +6269,8 @@ "title":"ALM-18020 Yarn Task Execution Timeout", "uri":"ALM-18020.html", "doc_type":"alarm", - "p_code":"548", - "code":"693" + "p_code":"552", + "code":"697" }, { "desc":"The alarm module checks the MapReduce service status every 60 seconds. This alarm is generated when the system detects that the MapReduce service is unavailable.The alarm", @@ -6242,8 +6278,8 @@ "title":"ALM-18021 Mapreduce Service Unavailable", "uri":"ALM-18021.html", "doc_type":"alarm", - "p_code":"548", - "code":"694" + "p_code":"552", + "code":"698" }, { "desc":"The alarm module checks Yarn queue resources every 60 seconds. This alarm is generated when available resources or ApplicationMaster (AM) resources of a queue are insuffi", @@ -6251,8 +6287,8 @@ "title":"ALM-18022 Insufficient Yarn Queue Resources", "uri":"ALM-18022.html", "doc_type":"alarm", - "p_code":"548", - "code":"695" + "p_code":"552", + "code":"699" }, { "desc":"The alarm module checks the number of pending applications in the Yarn root queue every 60 seconds. The alarm is generated when the number exceeds 60.It takes long time t", @@ -6260,8 +6296,8 @@ "title":"ALM-18023 Number of Pending Yarn Tasks Exceeds the Threshold", "uri":"ALM-18023.html", "doc_type":"alarm", - "p_code":"548", - "code":"696" + "p_code":"552", + "code":"700" }, { "desc":"The alarm module checks the pending memory of Yarn every 60 seconds. The alarm is generated when the pending memory exceeds the threshold. Pending memory indicates the to", @@ -6269,8 +6305,8 @@ "title":"ALM-18024 Pending Yarn Memory Usage Exceeds the Threshold", "uri":"ALM-18024.html", "doc_type":"alarm", - "p_code":"548", - "code":"697" + "p_code":"552", + "code":"701" }, { "desc":"The alarm module checks the number of terminated applications in the Yarn root queue every 60 seconds. The alarm is generated when the number exceeds 50 for three consecu", @@ -6278,8 +6314,8 @@ "title":"ALM-18025 Number of Terminated Yarn Tasks Exceeds the Threshold", "uri":"ALM-18025.html", "doc_type":"alarm", - "p_code":"548", - "code":"698" + "p_code":"552", + "code":"702" }, { "desc":"The alarm module checks the number of failed applications in the Yarn root queue every 60 seconds. The alarm is generated when the number exceeds 50 for three consecutive", @@ -6287,8 +6323,8 @@ "title":"ALM-18026 Number of Failed Yarn Tasks Exceeds the Threshold", "uri":"ALM-18026.html", "doc_type":"alarm", - "p_code":"548", - "code":"699" + "p_code":"552", + "code":"703" }, { "desc":"This alarm is generated when the HBase service is unavailable. The alarm module checks the HBase service status every 120 seconds.This alarm is cleared when the HBase ser", @@ -6296,8 +6332,8 @@ "title":"ALM-19000 HBase Service Unavailable", "uri":"ALM-19000.html", "doc_type":"alarm", - "p_code":"548", - "code":"700" + "p_code":"552", + "code":"704" }, { "desc":"The alarm module checks the HBase DR data synchronization status every 30 seconds. When disaster recovery (DR) data fails to be synchronized to a standby cluster, the ala", @@ -6305,8 +6341,8 @@ "title":"ALM-19006 HBase Replication Sync Failed", "uri":"ALM-19006.html", "doc_type":"alarm", - "p_code":"548", - "code":"701" + "p_code":"552", + "code":"705" }, { "desc":"The system checks the old generation garbage collection (GC) time of the HBase service every 60 seconds. This alarm is generated when the detected old generation GC time ", @@ -6314,8 +6350,8 @@ "title":"ALM-19007 HBase GC Time Exceeds the Threshold", "uri":"ALM-19007.html", "doc_type":"alarm", - "p_code":"548", - "code":"702" + "p_code":"552", + "code":"706" }, { "desc":"The system checks the HBase service status every 30 seconds. The alarm is generated when the heap memory usage of an HBase service exceeds the threshold (90% of the maxim", @@ -6323,8 +6359,8 @@ "title":"ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold", "uri":"ALM-19008.html", "doc_type":"alarm", - "p_code":"548", - "code":"703" + "p_code":"552", + "code":"707" }, { "desc":"The system checks the HBase service status every 30 seconds. The alarm is generated when the direct memory usage of an HBase service exceeds the threshold (90% of the max", @@ -6332,8 +6368,8 @@ "title":"ALM-19009 Direct Memory Usage of the HBase Process Exceeds the Threshold", "uri":"ALM-19009.html", "doc_type":"alarm", - "p_code":"548", - "code":"704" + "p_code":"552", + "code":"708" }, { "desc":"The system checks the number of regions on each RegionServer in each HBase service instance every 30 seconds. The region number is displayed on the HBase service monitori", @@ -6341,8 +6377,8 @@ "title":"ALM-19011 RegionServer Region Number Exceeds the Threshold", "uri":"ALM-19011.html", "doc_type":"alarm", - "p_code":"548", - "code":"705" + "p_code":"552", + "code":"709" }, { "desc":"The system checks whether HBase directories and files exist on the HDFS every 120 seconds. This alarm is generated when the system detects that the files or directories d", @@ -6350,8 +6386,8 @@ "title":"ALM-19012 HBase System Table Directory or File Lost", "uri":"ALM-19012.html", "doc_type":"alarm", - "p_code":"548", - "code":"706" + "p_code":"552", + "code":"710" }, { "desc":"The system checks the number of regions in transaction state on HBase every 300 seconds. This alarm is generated when the system detects that the duration of regions in t", @@ -6359,8 +6395,8 @@ "title":"ALM-19013 Duration of Regions in transaction State Exceeds the Threshold", "uri":"ALM-19013.html", "doc_type":"alarm", - "p_code":"548", - "code":"707" + "p_code":"552", + "code":"711" }, { "desc":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the ZNode capacity usage of the HBase service exceeds the critical ", @@ -6368,8 +6404,8 @@ "title":"ALM-19014 Capacity Quota Usage on ZooKeeper Exceeds the Threshold Severely", "uri":"ALM-19014.html", "doc_type":"alarm", - "p_code":"548", - "code":"708" + "p_code":"552", + "code":"712" }, { "desc":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the system detects that the ZNode quantity usage of the HBase servi", @@ -6377,8 +6413,8 @@ "title":"ALM-19015 Quantity Quota Usage on ZooKeeper Exceeds the Threshold", "uri":"ALM-19015.html", "doc_type":"alarm", - "p_code":"548", - "code":"709" + "p_code":"552", + "code":"713" }, { "desc":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the znode usage of the HBase service exceeds the critical alarm thr", @@ -6386,8 +6422,8 @@ "title":"ALM-19016 Quantity Quota Usage on ZooKeeper Exceeds the Threshold Severely", "uri":"ALM-19016.html", "doc_type":"alarm", - "p_code":"548", - "code":"710" + "p_code":"552", + "code":"714" }, { "desc":"The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the system detects that the ZNodes capacity usage of the HBase serv", @@ -6395,8 +6431,8 @@ "title":"ALM-19017 Capacity Quota Usage on ZooKeeper Exceeds the Threshold", "uri":"ALM-19017.html", "doc_type":"alarm", - "p_code":"548", - "code":"711" + "p_code":"552", + "code":"715" }, { "desc":"The system checks the HBase compaction queue size every 300 seconds. This alarm is generated when the compaction queue size exceeds the alarm threshold (100 by default). ", @@ -6404,8 +6440,8 @@ "title":"ALM-19018 HBase Compaction Queue Size Exceeds the Threshold", "uri":"ALM-19018.html", "doc_type":"alarm", - "p_code":"548", - "code":"712" + "p_code":"552", + "code":"716" }, { "desc":"The system checks the number of HFiles to be synchronized by the RegionServer of each HBase service instance every 30 seconds. This indicator can be viewed on the RegionS", @@ -6413,8 +6449,8 @@ "title":"ALM-19019 Number of HBase HFiles to Be Synchronized Exceeds the Threshold", "uri":"ALM-19019.html", "doc_type":"alarm", - "p_code":"548", - "code":"713" + "p_code":"552", + "code":"717" }, { "desc":"The system checks the number of WAL files to be synchronized by the RegionServer of each HBase service instance every 30 seconds. This indicator can be viewed on the Regi", @@ -6422,8 +6458,8 @@ "title":"ALM-19020 Number of HBase WAL Files to Be Synchronized Exceeds the Threshold", "uri":"ALM-19020.html", "doc_type":"alarm", - "p_code":"548", - "code":"714" + "p_code":"552", + "code":"718" }, { "desc":"The system checks the RegionServer handler usage of each HBase service instance every 30 seconds. This alarm is generated when the handler usage of a RegionServer exceeds", @@ -6431,8 +6467,8 @@ "title":"ALM-19021 Handler Usage of RegionServer Exceeds the Threshold", "uri":"ALM-19021.html", "doc_type":"usermanual", - "p_code":"548", - "code":"715" + "p_code":"552", + "code":"719" }, { "desc":"This alarm is generated when the Hue service is unavailable. The system checks the Hue service status every 60 seconds.This alarm is cleared when the Hue service is norma", @@ -6440,8 +6476,8 @@ "title":"ALM-20002 Hue Service Unavailable", "uri":"ALM-20002.html", "doc_type":"alarm", - "p_code":"548", - "code":"716" + "p_code":"552", + "code":"720" }, { "desc":"The system checks the Loader service availability every 60 seconds. This alarm is generated when the system detects that the Loader service is unavailable. This alarm is ", @@ -6449,8 +6485,8 @@ "title":"ALM-23001 Loader Service Unavailable", "uri":"ALM-23001.html", "doc_type":"alarm", - "p_code":"548", - "code":"717" + "p_code":"552", + "code":"721" }, { "desc":"This alarm is generated immediately when the system detects that the Loader job fails. This alarm is cleared when the failed job is manually handled by a user. This alarm", @@ -6458,8 +6494,8 @@ "title":"ALM-23003 Loader Task Execution Failure", "uri":"ALM-23003.html", "doc_type":"alarm", - "p_code":"548", - "code":"718" + "p_code":"552", + "code":"722" }, { "desc":"The system checks the heap memory usage of the Loader service every 60 seconds. The alarm is generated when the heap memory usage of a Loader instance exceeds the thresho", @@ -6467,8 +6503,8 @@ "title":"ALM-23004 Loader Heap Memory Usage Exceeds the Threshold", "uri":"ALM-23004.html", "doc_type":"alarm", - "p_code":"548", - "code":"719" + "p_code":"552", + "code":"723" }, { "desc":"The system checks the non-heap memory usage of the Loader service every 30 seconds. The alarm is generated when the non-heap memory usage of a Loader instance exceeds the", @@ -6476,8 +6512,8 @@ "title":"ALM-23005 Loader Non-Heap Memory Usage Exceeds the Threshold", "uri":"ALM-23005.html", "doc_type":"alarm", - "p_code":"548", - "code":"720" + "p_code":"552", + "code":"724" }, { "desc":"The system checks the direct memory usage of the Loader service every 30 seconds. The alarm is generated when the direct memory usage of a Loader instance exceeds the thr", @@ -6485,8 +6521,8 @@ "title":"ALM-23006 Loader Direct Memory Usage Exceeds the Threshold", "uri":"ALM-23006.html", "doc_type":"alarm", - "p_code":"548", - "code":"721" + "p_code":"552", + "code":"725" }, { "desc":"The system checks GC time of the Loader process every 60 seconds. The alarm is generated when GC time of the Loader process exceeds the threshold (default value: 12 secon", @@ -6494,8 +6530,8 @@ "title":"ALM-23007 Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold", "uri":"ALM-23007.html", "doc_type":"alarm", - "p_code":"548", - "code":"722" + "p_code":"552", + "code":"726" }, { "desc":"The alarm module checks the Flume service status every 180 seconds. This alarm is generated if the Flume service is abnormal.This alarm is automatically cleared after the", @@ -6503,8 +6539,8 @@ "title":"ALM-24000 Flume Service Unavailable", "uri":"ALM-24000.html", "doc_type":"alarm", - "p_code":"548", - "code":"723" + "p_code":"552", + "code":"727" }, { "desc":"The Flume agent instance for which the alarm is generated cannot be started. This alarm is generated when the Flume agent process is faulty (The system checks in every 5 ", @@ -6512,8 +6548,8 @@ "title":"ALM-24001 Flume Agent Exception", "uri":"ALM-24001.html", "doc_type":"alarm", - "p_code":"548", - "code":"724" + "p_code":"552", + "code":"728" }, { "desc":"The alarm module monitors the port connection status on the Flume server. This alarm is generated if the Flume server fails to receive a connection message from the Flume", @@ -6521,8 +6557,8 @@ "title":"ALM-24003 Flume Client Connection Interrupted", "uri":"ALM-24003.html", "doc_type":"alarm", - "p_code":"548", - "code":"725" + "p_code":"552", + "code":"729" }, { "desc":"The alarm module monitors the status of Flume Source. This alarm is generated immediately when the duration in which Source fails to read the data exceeds the threshold.T", @@ -6530,8 +6566,8 @@ "title":"ALM-24004 Exception Occurs When Flume Reads Data", "uri":"ALM-24004.html", "doc_type":"alarm", - "p_code":"548", - "code":"726" + "p_code":"552", + "code":"730" }, { "desc":"The alarm module monitors the capacity status of Flume Channel. The alarm is generated immediately when the duration that Channel is fully occupied exceeds the threshold ", @@ -6539,8 +6575,8 @@ "title":"ALM-24005 Exception Occurs When Flume Transmits Data", "uri":"ALM-24005.html", "doc_type":"alarm", - "p_code":"548", - "code":"727" + "p_code":"552", + "code":"731" }, { "desc":"The system checks the heap memory usage of the Flume service every 60 seconds. This alarm is generated when the heap memory usage of the Flume instance exceeds the thresh", @@ -6548,8 +6584,8 @@ "title":"ALM-24006 Heap Memory Usage of Flume Server Exceeds the Threshold", "uri":"ALM-24006.html", "doc_type":"alarm", - "p_code":"548", - "code":"728" + "p_code":"552", + "code":"732" }, { "desc":"The system checks the direct memory usage of the Flume service every 60 seconds. This alarm is generated when the direct memory usage of the Flume instance exceeds the th", @@ -6557,8 +6593,8 @@ "title":"ALM-24007 Flume Server Direct Memory Usage Exceeds the Threshold", "uri":"ALM-24007.html", "doc_type":"alarm", - "p_code":"548", - "code":"729" + "p_code":"552", + "code":"733" }, { "desc":"The system checks the non-heap memory usage of the Flume service every 60 seconds. This alarm is generated when the non-heap memory usage of the Flume instance exceeds th", @@ -6566,8 +6602,8 @@ "title":"ALM-24008 Flume Server Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-24008.html", "doc_type":"alarm", - "p_code":"548", - "code":"730" + "p_code":"552", + "code":"734" }, { "desc":"The system checks the GC duration of the Flume process every 60 seconds. This alarm is generated when the GC duration of the Flume process exceeds the threshold (12 secon", @@ -6575,8 +6611,8 @@ "title":"ALM-24009 Flume Server Garbage Collection (GC) Time Exceeds the Threshold", "uri":"ALM-24009.html", "doc_type":"alarm", - "p_code":"548", - "code":"731" + "p_code":"552", + "code":"735" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.Flume checks whether the Flume certificate file is valid (whether the certificate exists and whether the certificate form", @@ -6584,8 +6620,8 @@ "title":"ALM-24010 Flume Certificate File Is Invalid or Damaged", "uri":"ALM-24010.html", "doc_type":"usermanual", - "p_code":"548", - "code":"732" + "p_code":"552", + "code":"736" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.Flume checks whether the Flume certificate file is about to expire every hour. This alarm is generated when the remaining", @@ -6593,8 +6629,8 @@ "title":"ALM-24011 Flume Certificate File Is About to Expire", "uri":"ALM-24011.html", "doc_type":"usermanual", - "p_code":"548", - "code":"733" + "p_code":"552", + "code":"737" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.Flume checks whether its certificate file in the system has expired every hour. This alarm is generated when the server c", @@ -6602,8 +6638,8 @@ "title":"ALM-24012 Flume Certificate File Has Expired", "uri":"ALM-24012.html", "doc_type":"usermanual", - "p_code":"548", - "code":"734" + "p_code":"552", + "code":"738" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.MonitorServer checks whether its certificate file is valid (whether the certificate exists and whether the certificate fo", @@ -6611,8 +6647,8 @@ "title":"ALM-24013 Flume MonitorServer Certificate File Is Invalid or Damaged", "uri":"ALM-24013.html", "doc_type":"usermanual", - "p_code":"548", - "code":"735" + "p_code":"552", + "code":"739" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.MonitorServer checks whether its certificate file is about to expire every hour. This alarm is generated when the remaini", @@ -6620,8 +6656,8 @@ "title":"ALM-24014 Flume MonitorServer Certificate Is About to Expire", "uri":"ALM-24014.html", "doc_type":"usermanual", - "p_code":"548", - "code":"736" + "p_code":"552", + "code":"740" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.MonitorServer checks whether its certificate file in the system has expired every hour. This alarm is generated when the ", @@ -6629,8 +6665,8 @@ "title":"ALM-24015 Flume MonitorServer Certificate File Has Expired", "uri":"ALM-24015.html", "doc_type":"usermanual", - "p_code":"548", - "code":"737" + "p_code":"552", + "code":"741" }, { "desc":"The system checks the LdapServer service status every 30 seconds. This alarm is generated when the system detects that both the active and standby LdapServer services are", @@ -6638,8 +6674,8 @@ "title":"ALM-25000 LdapServer Service Unavailable", "uri":"ALM-25000.html", "doc_type":"alarm", - "p_code":"548", - "code":"738" + "p_code":"552", + "code":"742" }, { "desc":"The system checks the LdapServer data every 30 seconds. This alarm is generated when the data on the active and standby LdapServers of Manager is inconsistent for 12 cons", @@ -6647,8 +6683,8 @@ "title":"ALM-25004 Abnormal LdapServer Data Synchronization", "uri":"ALM-25004.html", "doc_type":"alarm", - "p_code":"548", - "code":"739" + "p_code":"552", + "code":"743" }, { "desc":"The system checks the status of the nscd service every 60 seconds. This alarm is generated when the nscd process fails to be queried for four consecutive times (three min", @@ -6656,8 +6692,8 @@ "title":"ALM-25005 nscd Service Exception", "uri":"ALM-25005.html", "doc_type":"alarm", - "p_code":"548", - "code":"740" + "p_code":"552", + "code":"744" }, { "desc":"The system checks the status of the sssd service every 60 seconds. This alarm is generated when the sssd process fails to be queried for four consecutive times (three min", @@ -6665,8 +6701,8 @@ "title":"ALM-25006 Sssd Service Exception", "uri":"ALM-25006.html", "doc_type":"alarm", - "p_code":"548", - "code":"741" + "p_code":"552", + "code":"745" }, { "desc":"The system checks the KrbServer service status every 30 seconds. This alarm is generated when the system detects that the KrbServer service is abnormal.This alarm is clea", @@ -6674,8 +6710,8 @@ "title":"ALM-25500 KrbServer Service Unavailable", "uri":"ALM-25500.html", "doc_type":"alarm", - "p_code":"548", - "code":"742" + "p_code":"552", + "code":"746" }, { "desc":"The system checks the Storm service status every 30 seconds. This alarm is generated when all Nimbus nodes in the cluster are abnormal and the Storm service is unavailabl", @@ -6683,8 +6719,8 @@ "title":"ALM-26051 Storm Service Unavailable", "uri":"ALM-26051.html", "doc_type":"alarm", - "p_code":"548", - "code":"743" + "p_code":"552", + "code":"747" }, { "desc":"The system periodically checks the number of available Supervisors every 60 seconds and compares the number of available Supervisors with the threshold. This alarm is gen", @@ -6692,8 +6728,8 @@ "title":"ALM-26052 Number of Available Supervisors of the Storm Service Is Less Than the Threshold", "uri":"ALM-26052.html", "doc_type":"alarm", - "p_code":"548", - "code":"744" + "p_code":"552", + "code":"748" }, { "desc":"The system checks the slot usage every 60 seconds and compares the actual slot usage with the threshold. This alarm is generated when the slot usage is greater than the t", @@ -6701,8 +6737,8 @@ "title":"ALM-26053 Storm Slot Usage Exceeds the Threshold", "uri":"ALM-26053.html", "doc_type":"alarm", - "p_code":"548", - "code":"745" + "p_code":"552", + "code":"749" }, { "desc":"The system checks the heap memory usage of Storm Nimbus every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap memory usa", @@ -6710,8 +6746,8 @@ "title":"ALM-26054 Nimbus Heap Memory Usage Exceeds the Threshold", "uri":"ALM-26054.html", "doc_type":"alarm", - "p_code":"548", - "code":"746" + "p_code":"552", + "code":"750" }, { "desc":"The alarm module checks the DBService service status every 30 seconds. This alarm is generated when the system detects that DBService service is unavailable.This alarm is", @@ -6719,8 +6755,8 @@ "title":"ALM-27001 DBService Service Unavailable", "uri":"ALM-27001.html", "doc_type":"alarm", - "p_code":"548", - "code":"747" + "p_code":"552", + "code":"751" }, { "desc":"This alarm is generated when the active or standby DBService node does not receive heartbeat messages from the peer node for 7 seconds.This alarm is cleared when the hear", @@ -6728,8 +6764,8 @@ "title":"ALM-27003 DBService Heartbeat Interruption Between the Active and Standby Nodes", "uri":"ALM-27003.html", "doc_type":"alarm", - "p_code":"548", - "code":"748" + "p_code":"552", + "code":"752" }, { "desc":"The system checks the data synchronization status between the active and standby DBService every 10 seconds. This alarm is generated when the synchronization status canno", @@ -6737,8 +6773,8 @@ "title":"ALM-27004 Data Inconsistency Between Active and Standby DBServices", "uri":"ALM-27004.html", "doc_type":"alarm", - "p_code":"548", - "code":"749" + "p_code":"552", + "code":"753" }, { "desc":"The system checks the usage of the number of database connections of the nodes where DBServer instances are located every 30 seconds and compares the usage with the thres", @@ -6746,8 +6782,8 @@ "title":"ALM-27005 Database Connections Usage Exceeds the Threshold", "uri":"ALM-27005.html", "doc_type":"alarm", - "p_code":"548", - "code":"750" + "p_code":"552", + "code":"754" }, { "desc":"The system checks the disk space usage of the data directory on the active DBServer node every 30 seconds and compares the disk usage with the threshold. The alarm is gen", @@ -6755,8 +6791,8 @@ "title":"ALM-27006 Disk Space Usage of the Data Directory Exceeds the Threshold", "uri":"ALM-27006.html", "doc_type":"alarm", - "p_code":"548", - "code":"751" + "p_code":"552", + "code":"755" }, { "desc":"The system checks the disk space usage of the data directory on the active DBServer node every 30 seconds. The alarm is generated when the disk space usage exceeds 90%.Th", @@ -6764,8 +6800,8 @@ "title":"ALM-27007 Database Enters the Read-Only Mode", "uri":"ALM-27007.html", "doc_type":"alarm", - "p_code":"548", - "code":"752" + "p_code":"552", + "code":"756" }, { "desc":"The system checks the Kafka service status every 30 seconds. This alarm is generated when the Kafka service is unavailable.This alarm is cleared when the Kafka service re", @@ -6773,8 +6809,8 @@ "title":"ALM-38000 Kafka Service Unavailable", "uri":"ALM-38000.html", "doc_type":"alarm", - "p_code":"548", - "code":"753" + "p_code":"552", + "code":"757" }, { "desc":"The system checks the Kafka disk usage every 60 seconds and compares the actual disk usage with the threshold. The disk usage has a default threshold. This alarm is gener", @@ -6782,8 +6818,8 @@ "title":"ALM-38001 Insufficient Kafka Disk Capacity", "uri":"ALM-38001.html", "doc_type":"alarm", - "p_code":"548", - "code":"754" + "p_code":"552", + "code":"758" }, { "desc":"The system checks the Kafka service status every 30 seconds. The alarm is generated when the heap memory usage of a Kafka instance exceeds the threshold (95% of the maxim", @@ -6791,8 +6827,8 @@ "title":"ALM-38002 Kafka Heap Memory Usage Exceeds the Threshold", "uri":"ALM-38002.html", "doc_type":"alarm", - "p_code":"548", - "code":"755" + "p_code":"552", + "code":"759" }, { "desc":"The system checks the direct memory usage of the Kafka service every 30 seconds. This alarm is generated when the direct memory usage of a Kafka instance exceeds the thre", @@ -6800,8 +6836,8 @@ "title":"ALM-38004 Kafka Direct Memory Usage Exceeds the Threshold", "uri":"ALM-38004.html", "doc_type":"alarm", - "p_code":"548", - "code":"756" + "p_code":"552", + "code":"760" }, { "desc":"The system checks the garbage collection (GC) duration of the Broker process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seco", @@ -6809,8 +6845,8 @@ "title":"ALM-38005 GC Duration of the Broker Process Exceeds the Threshold", "uri":"ALM-38005.html", "doc_type":"alarm", - "p_code":"548", - "code":"757" + "p_code":"552", + "code":"761" }, { "desc":"The system checks the percentage of Kafka partitions that are not completely synchronized to the total number of partitions every 60 seconds. This alarm is generated when", @@ -6818,8 +6854,8 @@ "title":"ALM-38006 Percentage of Kafka Partitions That Are Not Completely Synchronized Exceeds the Threshold", "uri":"ALM-38006.html", "doc_type":"alarm", - "p_code":"548", - "code":"758" + "p_code":"552", + "code":"762" }, { "desc":"The system checks the default user of Kafka every 60 seconds. This alarm is generated when the system detects that the user status is abnormal.Trigger Count is set to 1. ", @@ -6827,8 +6863,8 @@ "title":"ALM-38007 Status of Kafka Default User Is Abnormal", "uri":"ALM-38007.html", "doc_type":"alarm", - "p_code":"548", - "code":"759" + "p_code":"552", + "code":"763" }, { "desc":"The system checks the Kafka data directory status every 60 seconds. This alarm is generated when the system detects that the status of a data directory is abnormal.Trigge", @@ -6836,17 +6872,17 @@ "title":"ALM-38008 Abnormal Kafka Data Directory Status", "uri":"ALM-38008.html", "doc_type":"alarm", - "p_code":"548", - "code":"760" + "p_code":"552", + "code":"764" }, { "desc":"This section applies to versions later than MRS 3.1.0.The system checks the I/O status of each Kafka disk every 60 seconds. This alarm is generated when the disk I/O of a", "product_code":"mrs", - "title":"ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0)", + "title":"(Applicable to Versions Later Than MRS 3.1.0)ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0)", "uri":"ALM-38009.html", "doc_type":"alarm", - "p_code":"548", - "code":"761" + "p_code":"552", + "code":"765" }, { "desc":"The system checks the number of replicas of each topic every 60 seconds on the node where the Kafka Controller resides. This alarm is generated when there is one replica ", @@ -6854,8 +6890,8 @@ "title":"ALM-38010 Topics with Single Replica", "uri":"ALM-38010.html", "doc_type":"alarm", - "p_code":"548", - "code":"762" + "p_code":"552", + "code":"766" }, { "desc":"The system checks the number of connections of each user on Broker every 30 seconds. This alarm is generated when the connection usage of a user on the Broker exceeds the", @@ -6863,8 +6899,8 @@ "title":"ALM-38011 User Connection Usage on Broker Exceeds the Threshold", "uri":"ALM-38011.html", "doc_type":"alarm", - "p_code":"548", - "code":"763" + "p_code":"552", + "code":"767" }, { "desc":"The system checks the Spark2x service status every 300 seconds. This alarm is generated when the Spark2x service is unavailable.This alarm is cleared when the Spark2x ser", @@ -6872,8 +6908,8 @@ "title":"ALM-43001 Spark2x Service Unavailable", "uri":"ALM-43001.html", "doc_type":"alarm", - "p_code":"548", - "code":"764" + "p_code":"552", + "code":"768" }, { "desc":"The system checks the JobHistory2x Process status every 30 seconds. The alarm is generated when the heap memory usage of a JobHistory2x Process exceeds the threshold (95%", @@ -6881,8 +6917,8 @@ "title":"ALM-43006 Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold", "uri":"ALM-43006.html", "doc_type":"alarm", - "p_code":"548", - "code":"765" + "p_code":"552", + "code":"769" }, { "desc":"The system checks the JobHistory2x Process status every 30 seconds. The alarm is generated when the non-heap memory usage of a JobHistory2x Process exceeds the threshold ", @@ -6890,8 +6926,8 @@ "title":"ALM-43007 Non-Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold", "uri":"ALM-43007.html", "doc_type":"alarm", - "p_code":"548", - "code":"766" + "p_code":"552", + "code":"770" }, { "desc":"The system checks the JobHistory2x Process status every 30 seconds. The alarm is generated when the direct memory usage of a JobHistory2x Process exceeds the threshold (9", @@ -6899,8 +6935,8 @@ "title":"ALM-43008 The Direct Memory Usage of the JobHistory2x Process Exceeds the Threshold", "uri":"ALM-43008.html", "doc_type":"alarm", - "p_code":"548", - "code":"767" + "p_code":"552", + "code":"771" }, { "desc":"The system checks the garbage collection (GC) time of the JobHistory2x Process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (", @@ -6908,8 +6944,8 @@ "title":"ALM-43009 JobHistory2x Process GC Time Exceeds the Threshold", "uri":"ALM-43009.html", "doc_type":"alarm", - "p_code":"548", - "code":"768" + "p_code":"552", + "code":"772" }, { "desc":"The system checks the JDBCServer2x Process status every 30 seconds. The alarm is generated when the heap memory usage of a JDBCServer2x Process exceeds the threshold (95%", @@ -6917,8 +6953,8 @@ "title":"ALM-43010 Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold", "uri":"ALM-43010.html", "doc_type":"alarm", - "p_code":"548", - "code":"769" + "p_code":"552", + "code":"773" }, { "desc":"The system checks the JDBCServer2x Process status every 30 seconds. The alarm is generated when the non-heap memory usage of an JDBCServer2x Process exceeds the threshold", @@ -6926,8 +6962,8 @@ "title":"ALM-43011 Non-Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold", "uri":"ALM-43011.html", "doc_type":"alarm", - "p_code":"548", - "code":"770" + "p_code":"552", + "code":"774" }, { "desc":"The system checks the JDBCServer2x Process status every 30 seconds. The alarm is generated when the direct heap memory usage of a JDBCServer2x Process exceeds the thresho", @@ -6935,8 +6971,8 @@ "title":"ALM-43012 Direct Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold", "uri":"ALM-43012.html", "doc_type":"alarm", - "p_code":"548", - "code":"771" + "p_code":"552", + "code":"775" }, { "desc":"The system checks the garbage collection (GC) time of the JDBCServer2x Process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (", @@ -6944,8 +6980,8 @@ "title":"ALM-43013 JDBCServer2x Process GC Time Exceeds the Threshold", "uri":"ALM-43013.html", "doc_type":"alarm", - "p_code":"548", - "code":"772" + "p_code":"552", + "code":"776" }, { "desc":"The system checks the number of Full garbage collection (GC) times of the JDBCServer2x process every 60 seconds. This alarm is generated when the detected Full GC number ", @@ -6953,8 +6989,8 @@ "title":"ALM-43017 JDBCServer2x Process Full GC Number Exceeds the Threshold", "uri":"ALM-43017.html", "doc_type":"alarm", - "p_code":"548", - "code":"773" + "p_code":"552", + "code":"777" }, { "desc":"The system checks the number of Full garbage collection (GC) times of the JobHistory2x process every 60 seconds. This alarm is generated when the detected Full GC number ", @@ -6962,8 +6998,8 @@ "title":"ALM-43018 JobHistory2x Process Full GC Number Exceeds the Threshold", "uri":"ALM-43018.html", "doc_type":"alarm", - "p_code":"548", - "code":"774" + "p_code":"552", + "code":"778" }, { "desc":"The system checks the IndexServer2x process status every 30 seconds. The alarm is generated when the heap memory usage of a IndexServer2x process exceeds the threshold (9", @@ -6971,8 +7007,8 @@ "title":"ALM-43019 Heap Memory Usage of the IndexServer2x Process Exceeds the Threshold", "uri":"ALM-43019.html", "doc_type":"alarm", - "p_code":"548", - "code":"775" + "p_code":"552", + "code":"779" }, { "desc":"The system checks the IndexServer2x process status every 30 seconds. The alarm is generated when the non-heap memory usage of the IndexServer2x process exceeds the thresh", @@ -6980,8 +7016,8 @@ "title":"ALM-43020 Non-Heap Memory Usage of the IndexServer2x Process Exceeds the Threshold", "uri":"ALM-43020.html", "doc_type":"alarm", - "p_code":"548", - "code":"776" + "p_code":"552", + "code":"780" }, { "desc":"The system checks the IndexServer2x process status every 30 seconds. The alarm is generated when the direct heap memory usage of a IndexServer2x process exceeds the thres", @@ -6989,8 +7025,8 @@ "title":"ALM-43021 Direct Memory Usage of the IndexServer2x Process Exceeds the Threshold", "uri":"ALM-43021.html", "doc_type":"alarm", - "p_code":"548", - "code":"777" + "p_code":"552", + "code":"781" }, { "desc":"The system checks the GC time of the IndexServer2x process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (12 seconds) for thre", @@ -6998,8 +7034,8 @@ "title":"ALM-43022 IndexServer2x Process GC Time Exceeds the Threshold", "uri":"ALM-43022.html", "doc_type":"alarm", - "p_code":"548", - "code":"778" + "p_code":"552", + "code":"782" }, { "desc":"The system checks the Full GC number of the IndexServer2x process every 60 seconds. This alarm is generated when the detected Full GC number exceeds the threshold (12) fo", @@ -7007,8 +7043,8 @@ "title":"ALM-43023 IndexServer2x Process Full GC Number Exceeds the Threshold", "uri":"ALM-43023.html", "doc_type":"alarm", - "p_code":"548", - "code":"779" + "p_code":"552", + "code":"783" }, { "desc":"This alarm is generated when the system detects that the number of queuing tasks in a resource group exceeds the threshold. The system queries the number of queuing tasks", @@ -7016,8 +7052,8 @@ "title":"ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold", "uri":"ALM-44004.html", "doc_type":"alarm", - "p_code":"548", - "code":"780" + "p_code":"552", + "code":"784" }, { "desc":"The system collects GC time of the Presto Coordinator process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for thre", @@ -7025,8 +7061,8 @@ "title":"ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold", "uri":"ALM-44005.html", "doc_type":"alarm", - "p_code":"548", - "code":"781" + "p_code":"552", + "code":"785" }, { "desc":"The system collects GC time of the Presto Worker process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for three con", @@ -7034,8 +7070,8 @@ "title":"ALM-44006 Presto Worker Process GC Time Exceeds the Threshold", "uri":"ALM-44006.html", "doc_type":"alarm", - "p_code":"548", - "code":"782" + "p_code":"552", + "code":"786" }, { "desc":"The system checks the HetuEngine service status every 300 seconds. This alarm is generated when the HetuEngine service is unavailable.This alarm is cleared when the HetuE", @@ -7043,8 +7079,8 @@ "title":"ALM-45000 HetuEngine Service Unavailable", "uri":"ALM-45000.html", "doc_type":"alarm", - "p_code":"548", - "code":"783" + "p_code":"552", + "code":"787" }, { "desc":"This alarm applies only to MRS 3.2.0-LTS.2 or later.The system checks the HetuEngine compute instance status every 60 seconds. This alarm is generated when a HetuEngine c", @@ -7052,8 +7088,8 @@ "title":"ALM-45001 Faulty HetuEngine Compute Instances", "uri":"ALM-45001.html", "doc_type":"alarm", - "p_code":"548", - "code":"784" + "p_code":"552", + "code":"788" }, { "desc":"The system checks whether the average duration for calling OBS metadata APIs is greater than the threshold every 30 seconds. This alarm is generated when the number of co", @@ -7061,8 +7097,8 @@ "title":"ALM-45175 Average Time for Calling OBS Metadata APIs Is Greater than the Threshold", "uri":"ALM-45175.html", "doc_type":"alarm", - "p_code":"548", - "code":"785" + "p_code":"552", + "code":"789" }, { "desc":"The system checks whether the success rate of calling OBS metadata APIs is lower than the threshold every 30 seconds. This alarm is generated when the success rate is low", @@ -7070,8 +7106,8 @@ "title":"ALM-45176 Success Rate of Calling OBS Metadata APIs Is Lower than the Threshold", "uri":"ALM-45176.html", "doc_type":"alarm", - "p_code":"548", - "code":"786" + "p_code":"552", + "code":"790" }, { "desc":"The system checks whether the success rate of calling APIs for reading OBS data is lower than the threshold every 30 seconds. This alarm is generated when the success rat", @@ -7079,8 +7115,8 @@ "title":"ALM-45177 Success Rate of Calling OBS Data Read APIs Is Lower than the Threshold", "uri":"ALM-45177.html", "doc_type":"alarm", - "p_code":"548", - "code":"787" + "p_code":"552", + "code":"791" }, { "desc":"The system checks whether the success rate of calling APIs for writing OBS data is lower than the threshold every 30 seconds. This alarm is generated when the success rat", @@ -7088,8 +7124,8 @@ "title":"ALM-45178 Success Rate of Calling OBS Data Write APIs Is Lower Than the Threshold", "uri":"ALM-45178.html", "doc_type":"alarm", - "p_code":"548", - "code":"788" + "p_code":"552", + "code":"792" }, { "desc":"The system checks whether the number of failed OBS readFully API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of failed API calls", @@ -7097,8 +7133,8 @@ "title":"ALM-45179 Number of Failed OBS readFully API Calls Exceeds the Threshold", "uri":"ALM-45179.html", "doc_type":"usermanual", - "p_code":"548", - "code":"789" + "p_code":"552", + "code":"793" }, { "desc":"The system checks whether the number of failed OBS read API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of failed API calls exce", @@ -7106,8 +7142,8 @@ "title":"ALM-45180 Number of Failed OBS read API Calls Exceeds the Threshold", "uri":"ALM-45180.html", "doc_type":"usermanual", - "p_code":"548", - "code":"790" + "p_code":"552", + "code":"794" }, { "desc":"The system checks whether the number of failed OBS write API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of failed API calls exc", @@ -7115,8 +7151,8 @@ "title":"ALM-45181 Number of Failed OBS write API Calls Exceeds the Threshold", "uri":"ALM-45181.html", "doc_type":"usermanual", - "p_code":"548", - "code":"791" + "p_code":"552", + "code":"795" }, { "desc":"The system checks whether the number of throttled OBS operations exceeds the threshold every 30 seconds. This alarm is generated when the number of throttled OBS operatio", @@ -7124,8 +7160,8 @@ "title":"ALM-45182 Number of Throttled OBS Operations Exceeds the Threshold", "uri":"ALM-45182.html", "doc_type":"usermanual", - "p_code":"548", - "code":"792" + "p_code":"552", + "code":"796" }, { "desc":"The alarm module checks the Ranger service status every 180 seconds. This alarm is generated if the Ranger service is abnormal.This alarm is cleared after the Ranger serv", @@ -7133,8 +7169,8 @@ "title":"ALM-45275 Ranger Service Unavailable", "uri":"ALM-45275.html", "doc_type":"alarm", - "p_code":"548", - "code":"793" + "p_code":"552", + "code":"797" }, { "desc":"The alarm module checks the RangerAdmin service status every 60 seconds. This alarm is generated if RangerAdmin is unavailable.This alarm is automatically cleared after t", @@ -7142,8 +7178,8 @@ "title":"ALM-45276 Abnormal RangerAdmin Status", "uri":"ALM-45276.html", "doc_type":"alarm", - "p_code":"548", - "code":"794" + "p_code":"552", + "code":"798" }, { "desc":"The system checks the heap memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the system detects that the heap memory usage of the Ran", @@ -7151,8 +7187,8 @@ "title":"ALM-45277 RangerAdmin Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45277.html", "doc_type":"alarm", - "p_code":"548", - "code":"795" + "p_code":"552", + "code":"799" }, { "desc":"The system checks the direct memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the direct memory usage of the RangerAdmin instance ex", @@ -7160,8 +7196,8 @@ "title":"ALM-45278 RangerAdmin Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45278.html", "doc_type":"alarm", - "p_code":"548", - "code":"796" + "p_code":"552", + "code":"800" }, { "desc":"The system checks the non-heap memory usage of the RangerAdmin service every 60 seconds. This alarm is generated when the non-heap memory usage of the RangerAdmin instanc", @@ -7169,8 +7205,8 @@ "title":"ALM-45279 RangerAdmin Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45279.html", "doc_type":"alarm", - "p_code":"548", - "code":"797" + "p_code":"552", + "code":"801" }, { "desc":"The system checks the GC duration of the RangerAdmin process every 60 seconds. This alarm is generated when the GC duration of the RangerAdmin process exceeds the thresho", @@ -7178,8 +7214,8 @@ "title":"ALM-45280 RangerAdmin GC Duration Exceeds the Threshold", "uri":"ALM-45280.html", "doc_type":"alarm", - "p_code":"548", - "code":"798" + "p_code":"552", + "code":"802" }, { "desc":"The system checks the heap memory usage of the UserSync service every 60 seconds. This alarm is generated when the system detects that the heap memory usage of the UserSy", @@ -7187,8 +7223,8 @@ "title":"ALM-45281 UserSync Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45281.html", "doc_type":"alarm", - "p_code":"548", - "code":"799" + "p_code":"552", + "code":"803" }, { "desc":"The system checks the direct memory usage of the UserSync service every 60 seconds. This alarm is generated when the direct memory usage of the UserSync instance exceeds ", @@ -7196,8 +7232,8 @@ "title":"ALM-45282 UserSync Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45282.html", "doc_type":"alarm", - "p_code":"548", - "code":"800" + "p_code":"552", + "code":"804" }, { "desc":"The system checks the non-heap memory usage of the UserSync service every 60 seconds. This alarm is generated when the non-heap memory usage of the UserSync instance exce", @@ -7205,8 +7241,8 @@ "title":"ALM-45283 UserSync Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45283.html", "doc_type":"alarm", - "p_code":"548", - "code":"801" + "p_code":"552", + "code":"805" }, { "desc":"The system checks the GC duration of the UserSync process every 60 seconds. This alarm is generated when the GC duration of the UserSync process exceeds the threshold (12", @@ -7214,8 +7250,8 @@ "title":"ALM-45284 UserSync Garbage Collection (GC) Time Exceeds the Threshold", "uri":"ALM-45284.html", "doc_type":"alarm", - "p_code":"548", - "code":"802" + "p_code":"552", + "code":"806" }, { "desc":"The system checks the heap memory usage of the TagSync service every 60 seconds. This alarm is generated when the heap memory usage of the TagSync instance exceeds the th", @@ -7223,8 +7259,8 @@ "title":"ALM-45285 TagSync Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45285.html", "doc_type":"alarm", - "p_code":"548", - "code":"803" + "p_code":"552", + "code":"807" }, { "desc":"The system checks the direct memory usage of the TagSync service every 60 seconds. This alarm is generated when the direct memory usage of the TagSync instance exceeds th", @@ -7232,8 +7268,8 @@ "title":"ALM-45286 TagSync Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45286.html", "doc_type":"alarm", - "p_code":"548", - "code":"804" + "p_code":"552", + "code":"808" }, { "desc":"The system checks the non-heap memory usage of the TagSync service every 60 seconds. This alarm is generated when the non-heap memory usage of the TagSync instance exceed", @@ -7241,8 +7277,8 @@ "title":"ALM-45287 TagSync Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45287.html", "doc_type":"alarm", - "p_code":"548", - "code":"805" + "p_code":"552", + "code":"809" }, { "desc":"The system checks the GC duration of the TagSync process every 60 seconds. This alarm is generated when the GC duration of the TagSync process exceeds the threshold (12 s", @@ -7250,8 +7286,8 @@ "title":"ALM-45288 TagSync Garbage Collection (GC) Time Exceeds the Threshold", "uri":"ALM-45288.html", "doc_type":"alarm", - "p_code":"548", - "code":"806" + "p_code":"552", + "code":"810" }, { "desc":"The alarm module checks the ClickHouse instance status every 60 seconds. This alarm is generated when the alarm module detects that all ClickHouse instances are abnormal.", @@ -7259,8 +7295,8 @@ "title":"ALM-45425 ClickHouse Service Unavailable", "uri":"ALM-45425.html", "doc_type":"alarm", - "p_code":"548", - "code":"807" + "p_code":"552", + "code":"811" }, { "desc":"The alarm module checks the quota usage of the ClickHouse service in the ZooKeeper every 60 seconds. This alarm is generated when the alarm module detects that the usage ", @@ -7268,8 +7304,8 @@ "title":"ALM-45426 ClickHouse Service Quantity Quota Usage in ZooKeeper Exceeds the Threshold", "uri":"ALM-45426.html", "doc_type":"alarm", - "p_code":"548", - "code":"808" + "p_code":"552", + "code":"812" }, { "desc":"The alarm module checks the quota usage of the ClickHouse service in the ZooKeeper every 60 seconds. This alarm is generated when the alarm module detects that the usage ", @@ -7277,8 +7313,8 @@ "title":"ALM-45427 ClickHouse Service Capacity Quota Usage in ZooKeeper Exceeds the Threshold", "uri":"ALM-45427.html", "doc_type":"alarm", - "p_code":"548", - "code":"809" + "p_code":"552", + "code":"813" }, { "desc":"This alarm is generated when the alarm module detects EIO or EROFS errors during ClickHouse read and write every 60 seconds.ClickHouse fails to read and write data. The I", @@ -7286,8 +7322,8 @@ "title":"ALM-45428 ClickHouse Disk I/O Exception", "uri":"ALM-45428.html", "doc_type":"alarm", - "p_code":"548", - "code":"810" + "p_code":"552", + "code":"814" }, { "desc":"This section applies only to MRS 3.1.2-LTS.6 or later.This alarm is generated when the local table corresponding to the distributed table fails to be created during Click", @@ -7295,8 +7331,8 @@ "title":"ALM-45429 Table Metadata Synchronization Failed on the Added ClickHouse Node", "uri":"ALM-45429.html", "doc_type":"alarm", - "p_code":"548", - "code":"811" + "p_code":"552", + "code":"815" }, { "desc":"This section applies only to MRS 3.1.2-LTS.6 or later.This alarm is generated when user and permission information fails to be synchronized during ClickHouse capacity exp", @@ -7304,8 +7340,8 @@ "title":"ALM-45430 Permission Metadata Synchronization Failed on the Added ClickHouse Node", "uri":"ALM-45430.html", "doc_type":"alarm", - "p_code":"548", - "code":"812" + "p_code":"552", + "code":"816" }, { "desc":"The ClickHouseServer instance distribution does not meet the topology allocation requirements.Some ClickHouseServer instances are unavailable.During installation or capac", @@ -7313,8 +7349,8 @@ "title":"ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation", "uri":"ALM-45431.html", "doc_type":"usermanual", - "p_code":"548", - "code":"813" + "p_code":"552", + "code":"817" }, { "desc":"The system checks the status of the ClickHouse user role synchronization process every 5 minutes. This alarm is generated when the system detects that the ClickHouse user", @@ -7322,8 +7358,8 @@ "title":"ALM-45432 ClickHouse User Synchronization Process Fails", "uri":"ALM-45432.html", "doc_type":"usermanual", - "p_code":"548", - "code":"814" + "p_code":"552", + "code":"818" }, { "desc":"If the cross-AZ HA function is enabled for a cluster where ClickHouse has been deployed, the ClickHouse topology remains unchanged. This alarm is generated when the cross", @@ -7331,8 +7367,8 @@ "title":"ALM-45433 ClickHouse AZ Topology Exception", "uri":"ALM-45433.html", "doc_type":"usermanual", - "p_code":"548", - "code":"815" + "p_code":"552", + "code":"819" }, { "desc":"This alarm is generated when a single replica is detected in a custom logical cluster after the custom logical cluster is enabled for ClickHouse.This alarm is automatical", @@ -7340,8 +7376,8 @@ "title":"ALM-45434 A Single Replica Exists in the ClickHouse Data Table", "uri":"ALM-45434.html", "doc_type":"usermanual", - "p_code":"548", - "code":"816" + "p_code":"552", + "code":"820" }, { "desc":"The system checks the IoTDB service status every 300 seconds. This alarm is generated when the IoTDB service is unavailable. This alarm is cleared when the IoTDB service ", @@ -7349,8 +7385,8 @@ "title":"ALM-45585 IoTDB Service Unavailable", "uri":"ALM-45585.html", "doc_type":"alarm", - "p_code":"548", - "code":"817" + "p_code":"552", + "code":"821" }, { "desc":"The system checks the IoTDBServer process status every 60 seconds. The alarm is generated when the heap memory usage of the IoTDBServer process exceeds the threshold (90%", @@ -7358,8 +7394,8 @@ "title":"ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45586.html", "doc_type":"alarm", - "p_code":"548", - "code":"818" + "p_code":"552", + "code":"822" }, { "desc":"The system checks the GC duration of the IoTDBServer process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seconds by default) ", @@ -7367,8 +7403,8 @@ "title":"ALM-45587 IoTDBServer GC Duration Exceeds the Threshold", "uri":"ALM-45587.html", "doc_type":"alarm", - "p_code":"548", - "code":"819" + "p_code":"552", + "code":"823" }, { "desc":"The system checks the direct memory usage of the IoTDBServer service every 60 seconds. This alarm is generated when the direct memory usage of the IoTDBServer instance ex", @@ -7376,8 +7412,8 @@ "title":"ALM-45588 IoTDBServer Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45588.html", "doc_type":"alarm", - "p_code":"548", - "code":"820" + "p_code":"552", + "code":"824" }, { "desc":"The system checks the heap memory usage of the ConfigNode process every 60 seconds. This alarm is generated when the heap memory usage of the ConfigNode process exceeds t", @@ -7385,8 +7421,8 @@ "title":"ALM-45589 ConfigNode Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45589.html", "doc_type":"alarm", - "p_code":"548", - "code":"821" + "p_code":"552", + "code":"825" }, { "desc":"The system checks the GC duration of the ConfigNode process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seconds by default) f", @@ -7394,8 +7430,8 @@ "title":"ALM-45590 ConfigNode GC Duration Exceeds the Threshold", "uri":"ALM-45590.html", "doc_type":"usermanual", - "p_code":"548", - "code":"822" + "p_code":"552", + "code":"826" }, { "desc":"The system checks the direct memory usage of the ConfigNode process every 60 seconds. This alarm is generated when the direct memory usage of the ConfigNode exceeds the t", @@ -7403,8 +7439,8 @@ "title":"ALM-45591 ConfigNode Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45591.html", "doc_type":"usermanual", - "p_code":"548", - "code":"823" + "p_code":"552", + "code":"827" }, { "desc":"The system checks the RPC execution duration of the IoTDBServer process every 60 seconds. This alarm is generated when the execution duration exceeds the threshold. This ", @@ -7412,8 +7448,8 @@ "title":"ALM-45592 IoTDBServer RPC Execution Duration Exceeds the Threshold", "uri":"ALM-45592.html", "doc_type":"usermanual", - "p_code":"548", - "code":"824" + "p_code":"552", + "code":"828" }, { "desc":"This alarm is generated when the data flush duration exceeds the threshold. This alarm is cleared when the flush duration is less than the threshold.Data write is blocked", @@ -7421,8 +7457,8 @@ "title":"ALM-45593 IoTDBServer Flush Execution Duration Exceeds the Threshold", "uri":"ALM-45593.html", "doc_type":"usermanual", - "p_code":"548", - "code":"825" + "p_code":"552", + "code":"829" }, { "desc":"This alarm is generated when the merge duration in the space exceeds the threshold. This alarm is cleared when the merge duration in the space is less than the threshold.", @@ -7430,8 +7466,8 @@ "title":"ALM-45594 IoTDBServer Intra-Space Merge Duration Exceeds the Threshold", "uri":"ALM-45594.html", "doc_type":"usermanual", - "p_code":"548", - "code":"826" + "p_code":"552", + "code":"830" }, { "desc":"This alarm is generated when the cross-space merge duration exceeds the threshold. This alarm is cleared when the cross-space merge duration is less than the threshold.Da", @@ -7439,8 +7475,8 @@ "title":"ALM-45595 IoTDBServer Cross-Space Merge Duration Exceeds the Threshold", "uri":"ALM-45595.html", "doc_type":"usermanual", - "p_code":"548", - "code":"827" + "p_code":"552", + "code":"831" }, { "desc":"The system checks the CDL health status every 60 seconds. This alarm is generated when the CDL health status is DOWN. This alarm is cleared when the system detects that t", @@ -7448,8 +7484,8 @@ "title":"ALM-45615 CDL Service Unavailable", "uri":"ALM-45615.html", "doc_type":"alarm", - "p_code":"548", - "code":"828" + "p_code":"552", + "code":"832" }, { "desc":"The system checks whether a CDL job is normal every 60 seconds. This alarm is reported when the CDL job is abnormal. This alarm is cleared when the job is restored or sto", @@ -7457,8 +7493,8 @@ "title":"ALM-45616 CDL Job Execution Exception", "uri":"ALM-45616.html", "doc_type":"usermanual", - "p_code":"548", - "code":"829" + "p_code":"552", + "code":"833" }, { "desc":"If a large number of write-ahead logs (WALs) are stacked in the PostgreSQL database, the PostgreSQL disk space may be used up. The system checks whether the amount of dat", @@ -7466,8 +7502,8 @@ "title":"ALM-45617 Data Queued in the CDL Replication Slot Exceeds the Threshold", "uri":"ALM-45617.html", "doc_type":"usermanual", - "p_code":"548", - "code":"830" + "p_code":"552", + "code":"834" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks whether FlinkServer jobs fail to be executed every 10 seconds. This alarm is generated when a FlinkServ", @@ -7475,8 +7511,8 @@ "title":"ALM-45635 FlinkServer Job Execution Failure", "uri":"ALM-45635.html", "doc_type":"alarm", - "p_code":"548", - "code":"831" + "p_code":"552", + "code":"835" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks the number of consecutive checkpoint failures based on the configured alarm checking interval. This ala", @@ -7484,8 +7520,8 @@ "title":"ALM-45636 FlinkServer Job Checkpoints Keep Failing", "uri":"ALM-45636.html", "doc_type":"alarm", - "p_code":"548", - "code":"832" + "p_code":"552", + "code":"836" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks the number of consecutive checkpoint failures based on the configured alarm checking interval. This ala", @@ -7493,8 +7529,8 @@ "title":"ALM-45636 Flink Job Checkpoints Keep Failing", "uri":"ALM-45636-1.html", "doc_type":"alarm", - "p_code":"548", - "code":"833" + "p_code":"552", + "code":"837" }, { "desc":"This section applies to MRS 3.1.2-LTS.6 or later.The system checks the back pressure duration of FlinkServer tasks based on the configured alarm checking interval. This a", @@ -7502,8 +7538,8 @@ "title":"ALM-45637 FlinkServer Task Is Continuously Under Back Pressure", "uri":"ALM-45637.html", "doc_type":"alarm", - "p_code":"548", - "code":"834" + "p_code":"552", + "code":"838" }, { "desc":"This section applies to MRS 3.1.2-LTS.6 or later.The system checks the number of FlinkServer job restarts based on the alarm checking interval. This alarm is generated wh", @@ -7511,8 +7547,8 @@ "title":"ALM-45638 Number of Restarts After FlinkServer Job Failures Exceeds the Threshold", "uri":"ALM-45638.html", "doc_type":"alarm", - "p_code":"548", - "code":"835" + "p_code":"552", + "code":"839" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks the number of Flink job restarts based on the alarm checking interval. This alarm is generated when the", @@ -7520,8 +7556,8 @@ "title":"ALM-45638 Number of Restarts After Flink Job Failures Exceeds the Threshold", "uri":"ALM-45638-1.html", "doc_type":"alarm", - "p_code":"548", - "code":"836" + "p_code":"552", + "code":"840" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.This alarm is generated when the FlinkServer active node or standby node does not receive heartbeat messages from the pee", @@ -7529,8 +7565,8 @@ "title":"ALM-45640 FlinkServer Heartbeat Interruption Between the Active and Standby Nodes", "uri":"ALM-45640.html", "doc_type":"alarm", - "p_code":"548", - "code":"837" + "p_code":"552", + "code":"841" }, { "desc":"This section applies to MRS 3.2.0-LTS.2 or later.The system checks data synchronization between the active and standby FlinkServer nodes every 60 seconds. This alarm is g", @@ -7538,8 +7574,8 @@ "title":"ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes", "uri":"ALM-45641.html", "doc_type":"alarm", - "p_code":"548", - "code":"838" + "p_code":"552", + "code":"842" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -7548,7 +7584,7 @@ "uri":"mrs_01_0648.html", "doc_type":"usermanual", "p_code":"", - "code":"839" + "code":"843" }, { "desc":"MRS manages and analyzes massive data and helps you rapidly obtain desired data from structured and unstructured data. The structure of open-source components is complex.", @@ -7556,8 +7592,8 @@ "title":"Introduction to MRS Manager", "uri":"mrs_01_0101.html", "doc_type":"usermanual", - "p_code":"839", - "code":"840" + "p_code":"843", + "code":"844" }, { "desc":"When you perform operations on MRS Manager to trigger a task, the task execution process and progress are displayed. After the task window is closed, you need to open the", @@ -7565,8 +7601,8 @@ "title":"Checking Running Tasks", "uri":"mrs_01_0105.html", "doc_type":"usermanual", - "p_code":"839", - "code":"841" + "p_code":"843", + "code":"845" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -7574,8 +7610,8 @@ "title":"Monitoring Management", "uri":"mrs_01_0106.html", "doc_type":"usermanual", - "p_code":"839", - "code":"842" + "p_code":"843", + "code":"846" }, { "desc":"On MRS Manager, nodes in a cluster can be classified into management nodes, control nodes, and data nodes. The change trends of key host monitoring metrics on each type o", @@ -7583,8 +7619,8 @@ "title":"Dashboard", "uri":"mrs_01_0107.html", "doc_type":"usermanual", - "p_code":"842", - "code":"843" + "p_code":"846", + "code":"847" }, { "desc":"You can manage the following status and indicators of all services (including role instances) and hosts on the MRS Manager:Status information: includes operation, health,", @@ -7592,8 +7628,8 @@ "title":"Managing Services and Monitoring Hosts", "uri":"mrs_01_0232.html", "doc_type":"usermanual", - "p_code":"842", - "code":"844" + "p_code":"846", + "code":"848" }, { "desc":"On MRS Manager, you can query the top value curves, bottom value curves, or average data curves of key service and host monitoring metrics, that is, the resource distribu", @@ -7601,8 +7637,8 @@ "title":"Managing Resource Distribution", "uri":"mrs_01_0233.html", "doc_type":"usermanual", - "p_code":"842", - "code":"845" + "p_code":"846", + "code":"849" }, { "desc":"You can configure interconnection parameters on MRS Manager to save monitoring metric data to a specified FTP server using the FTP or SFTP protocol. In this way, MRS clus", @@ -7610,8 +7646,8 @@ "title":"Configuring Monitoring Metric Dumping", "uri":"mrs_01_0235.html", "doc_type":"usermanual", - "p_code":"842", - "code":"846" + "p_code":"846", + "code":"850" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -7619,8 +7655,8 @@ "title":"Alarm Management", "uri":"mrs_01_0236.html", "doc_type":"usermanual", - "p_code":"839", - "code":"847" + "p_code":"843", + "code":"851" }, { "desc":"You can view and clear alarms on MRS Manager.Generally, the system automatically clears an alarm when the fault is rectified. If the fault has been rectified and the alar", @@ -7628,8 +7664,8 @@ "title":"Viewing and Manually Clearing an Alarm", "uri":"mrs_01_0237.html", "doc_type":"usermanual", - "p_code":"847", - "code":"848" + "p_code":"851", + "code":"852" }, { "desc":"You can configure an alarm threshold to learn the metric health status. After Send Alarm is selected, the system sends an alarm message when the monitored data reaches th", @@ -7637,8 +7673,8 @@ "title":"Configuring an Alarm Threshold", "uri":"mrs_01_0238.html", "doc_type":"usermanual", - "p_code":"847", - "code":"849" + "p_code":"851", + "code":"853" }, { "desc":"You can configure the northbound interface so that alarms generated on MRS Manager can be reported to your monitoring O&M system using Syslog.If the Syslog protocol is no", @@ -7646,8 +7682,8 @@ "title":"Configuring Syslog Northbound Interface Parameters", "uri":"mrs_01_0239.html", "doc_type":"usermanual", - "p_code":"847", - "code":"850" + "p_code":"851", + "code":"854" }, { "desc":"You can configure the northbound interface so that alarms and monitoring metrics on MRS Manager can be integrated to the network management platform using SNMP.The ECS co", @@ -7655,8 +7691,8 @@ "title":"Configuring SNMP Northbound Interface Parameters", "uri":"mrs_01_0240.html", "doc_type":"usermanual", - "p_code":"847", - "code":"851" + "p_code":"851", + "code":"855" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -7664,8 +7700,8 @@ "title":"Alarm Reference (Applicable to Versions Earlier Than MRS 3.x)", "uri":"mrs_01_0241.html", "doc_type":"usermanual", - "p_code":"839", - "code":"852" + "p_code":"843", + "code":"856" }, { "desc":"Cluster audit logs need to be dumped on a third-party server due to the local historical data backup policy. Audit logs can be successfully dumped if the dump server meet", @@ -7673,8 +7709,8 @@ "title":"ALM-12001 Audit Log Dump Failure", "uri":"alm_12001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"853" + "p_code":"856", + "code":"857" }, { "desc":"The high availability (HA) software periodically checks the WebService floating IP addresses and databases of Manager. This alarm is generated when the HA software detect", @@ -7682,8 +7718,8 @@ "title":"ALM-12002 HA Resource Is Abnormal", "uri":"alm_12002.html", "doc_type":"usermanual", - "p_code":"852", - "code":"854" + "p_code":"856", + "code":"858" }, { "desc":"This alarm is generated when the Ldap resource in Manager is abnormal.This alarm is cleared when the Ldap resource in Manager recovers and the alarm handling is complete.", @@ -7691,8 +7727,8 @@ "title":"ALM-12004 OLdap Resource Is Abnormal", "uri":"alm_12004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"855" + "p_code":"856", + "code":"859" }, { "desc":"The alarm module monitors the status of the Kerberos resource in Manager. This alarm is generated when the Kerberos resource is abnormal.This alarm is cleared when the al", @@ -7700,8 +7736,8 @@ "title":"ALM-12005 OKerberos Resource Is Abnormal", "uri":"alm_12005.html", "doc_type":"usermanual", - "p_code":"852", - "code":"856" + "p_code":"856", + "code":"860" }, { "desc":"Controller checks the NodeAgent status every 30 seconds. This alarm is generated when Controller fails to receive the status report of a NodeAgent for three consecutive t", @@ -7709,8 +7745,8 @@ "title":"ALM-12006 Node Fault", "uri":"alm_12006.html", "doc_type":"usermanual", - "p_code":"852", - "code":"857" + "p_code":"856", + "code":"861" }, { "desc":"The process health check module checks the process status every 5 seconds. This alarm is generated when the process health check module detects that the process connectio", @@ -7718,8 +7754,8 @@ "title":"ALM-12007 Process Fault", "uri":"alm_12007.html", "doc_type":"usermanual", - "p_code":"852", - "code":"858" + "p_code":"856", + "code":"862" }, { "desc":"This alarm is generated when the active Manager does not receive any heartbeat signal from the standby Manager within 7 seconds.This alarm is cleared when the active Mana", @@ -7727,8 +7763,8 @@ "title":"ALM-12010 Manager Heartbeat Interruption Between the Active and Standby Nodes", "uri":"alm_12010.html", "doc_type":"usermanual", - "p_code":"852", - "code":"859" + "p_code":"856", + "code":"863" }, { "desc":"This alarm is generated when the standby Manager fails to synchronize files with the active Manager.This alarm is cleared when the standby Manager synchronizes files with", @@ -7736,8 +7772,8 @@ "title":"ALM-12011 Data Synchronization Exception Between the Active and Standby Manager Nodes", "uri":"alm_12011.html", "doc_type":"usermanual", - "p_code":"852", - "code":"860" + "p_code":"856", + "code":"864" }, { "desc":"This alarm is generated when the NTP service on the current node fails to synchronize time with the NTP service on the active OMS node.This alarm is cleared when the NTP ", @@ -7745,8 +7781,8 @@ "title":"ALM-12012 NTP Service Is Abnormal", "uri":"alm_12012.html", "doc_type":"usermanual", - "p_code":"852", - "code":"861" + "p_code":"856", + "code":"865" }, { "desc":"The system checks the CPU usage every 30 seconds and compares the check result with the default threshold. The CPU usage has a default threshold. This alarm is generated ", @@ -7754,8 +7790,8 @@ "title":"ALM-12016 CPU Usage Exceeds the Threshold", "uri":"alm_12016.html", "doc_type":"usermanual", - "p_code":"852", - "code":"862" + "p_code":"856", + "code":"866" }, { "desc":"The system checks the host disk usage every 30 seconds and compares the actual disk usage with the threshold. The disk usage has a default threshold. This alarm is genera", @@ -7763,8 +7799,8 @@ "title":"ALM-12017 Insufficient Disk Capacity", "uri":"alm_12017.html", "doc_type":"usermanual", - "p_code":"852", - "code":"863" + "p_code":"856", + "code":"867" }, { "desc":"The system checks the memory usage every 30 seconds and compares the actual memory usage with the threshold. The memory usage has a default threshold. This alarm is gener", @@ -7772,8 +7808,8 @@ "title":"ALM-12018 Memory Usage Exceeds the Threshold", "uri":"alm_12018.html", "doc_type":"usermanual", - "p_code":"852", - "code":"864" + "p_code":"856", + "code":"868" }, { "desc":"The system checks the PID usage every 30 seconds and compares the actual PID usage with the default threshold. This alarm is generated when the PID usage exceeds the thre", @@ -7781,8 +7817,8 @@ "title":"ALM-12027 Host PID Usage Exceeds the Threshold", "uri":"alm_12027.html", "doc_type":"usermanual", - "p_code":"852", - "code":"865" + "p_code":"856", + "code":"869" }, { "desc":"The system periodically checks the number of D state processes of user omm on the host every 30 seconds and compares the number with the threshold. The number of processe", @@ -7790,8 +7826,8 @@ "title":"ALM-12028 Number of Processes in the D State on the Host Exceeds the Threshold", "uri":"alm_12028.html", "doc_type":"usermanual", - "p_code":"852", - "code":"866" + "p_code":"856", + "code":"870" }, { "desc":"The system starts at 00:00 every day to check whether user omm and the password are about to expire every eight hours. This alarm is generated if the user or password is ", @@ -7799,8 +7835,8 @@ "title":"ALM-12031 User omm or Password Is About to Expire", "uri":"alm_12031.html", "doc_type":"usermanual", - "p_code":"852", - "code":"867" + "p_code":"856", + "code":"871" }, { "desc":"The system starts at 00:00 every day to check whether user ommdba and the password are about to expire every eight hours. This alarm is generated if the user or password ", @@ -7808,8 +7844,8 @@ "title":"ALM-12032 User ommdba or Password Is About to Expire", "uri":"alm_12032.html", "doc_type":"usermanual", - "p_code":"852", - "code":"868" + "p_code":"856", + "code":"872" }, { "desc":"The system runs the iostat command every second to monitor the disk I/O indicator. If there are more than 30 times that the svctm value is greater than 100 ms in 60 secon", @@ -7817,8 +7853,8 @@ "title":"ALM-12033 Slow Disk Fault", "uri":"alm_12033.html", "doc_type":"usermanual", - "p_code":"852", - "code":"869" + "p_code":"856", + "code":"873" }, { "desc":"This alarm is generated when a periodic backup task fails to be executed. This alarm is cleared when the next backup task is executed successfully.No backup package is av", @@ -7826,8 +7862,8 @@ "title":"ALM-12034 Periodic Backup Failure", "uri":"alm_12034.html", "doc_type":"usermanual", - "p_code":"852", - "code":"870" + "p_code":"856", + "code":"874" }, { "desc":"If a recovery task fails, the system attempts to automatically roll back. If the rollback fails, data may be lost. If this occurs, an alarm is reported. This alarm is cle", @@ -7835,8 +7871,8 @@ "title":"ALM-12035 Unknown Data Status After Recovery Task Failure", "uri":"alm_12035.html", "doc_type":"usermanual", - "p_code":"852", - "code":"871" + "p_code":"856", + "code":"875" }, { "desc":"This alarm is generated when the NTP server is abnormal.This alarm is cleared when the NTP server recovers.The NTP server configured on the active OMS node is abnormal. I", @@ -7844,8 +7880,8 @@ "title":"ALM-12037 NTP Server Is Abnormal", "uri":"alm_12037.html", "doc_type":"usermanual", - "p_code":"852", - "code":"872" + "p_code":"856", + "code":"876" }, { "desc":"This alarm is generated when dumping fails after monitoring indicator dumping is configured on MRS Manager.This alarm is cleared when dumping is successful.The upper-laye", @@ -7853,8 +7889,8 @@ "title":"ALM-12038 Monitoring Indicator Dump Failure", "uri":"alm_12038.html", "doc_type":"usermanual", - "p_code":"852", - "code":"873" + "p_code":"856", + "code":"877" }, { "desc":"The system checks the data synchronization status between the active and standby GaussDB nodes every 10 seconds. This alarm is generated when the synchronization status c", @@ -7862,8 +7898,8 @@ "title":"ALM-12039 GaussDB Data Is Not Synchronized", "uri":"alm_12039.html", "doc_type":"usermanual", - "p_code":"852", - "code":"874" + "p_code":"856", + "code":"878" }, { "desc":"The system checks the entropy at 00:00:00 every day and performs five consecutive checks each time. First, the system checks whether the rng-tools tool is enabled and cor", @@ -7871,8 +7907,8 @@ "title":"ALM-12040 Insufficient System Entropy", "uri":"alm_12040.html", "doc_type":"usermanual", - "p_code":"852", - "code":"875" + "p_code":"856", + "code":"879" }, { "desc":"The system checks the ZooKeeper service status every 30 seconds. This alarm is generated when the ZooKeeper service is unavailable.This alarm is cleared when the ZooKeepe", @@ -7880,8 +7916,8 @@ "title":"ALM-13000 ZooKeeper Service Unavailable", "uri":"alm_13000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"876" + "p_code":"856", + "code":"880" }, { "desc":"The system checks ZooKeeper connections every 30 seconds. This alarm is generated when the system detects that the number of used ZooKeeper instance connections exceeds t", @@ -7889,8 +7925,8 @@ "title":"ALM-13001 Available ZooKeeper Connections Are Insufficient", "uri":"alm_13001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"877" + "p_code":"856", + "code":"881" }, { "desc":"The system checks the ZooKeeper service status every 30 seconds. The alarm is generated when the memory usage of a ZooKeeper instance exceeds the threshold (80% of the ma", @@ -7898,8 +7934,8 @@ "title":"ALM-13002 ZooKeeper Memory Usage Exceeds the Threshold", "uri":"alm_13002.html", "doc_type":"usermanual", - "p_code":"852", - "code":"878" + "p_code":"856", + "code":"882" }, { "desc":"The system checks the service status of NameService every 30 seconds. This alarm is generated when the system considers that the HDFS service is unavailable because all t", @@ -7907,8 +7943,8 @@ "title":"ALM-14000 HDFS Service Unavailable", "uri":"alm_14000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"879" + "p_code":"856", + "code":"883" }, { "desc":"The system checks the disk usage of the HDFS cluster every 30 seconds and compares the actual disk usage with the threshold. The HDFS cluster disk usage indicator has a d", @@ -7916,8 +7952,8 @@ "title":"ALM-14001 HDFS Disk Usage Exceeds the Threshold", "uri":"alm_14001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"880" + "p_code":"856", + "code":"884" }, { "desc":"The system checks the DataNode disk usage every 30 seconds and compares the actual disk usage with the threshold. The Percentage of DataNode Capacity indicator has a defa", @@ -7925,8 +7961,8 @@ "title":"ALM-14002 DataNode Disk Usage Exceeds the Threshold", "uri":"alm_14002.html", "doc_type":"usermanual", - "p_code":"852", - "code":"881" + "p_code":"856", + "code":"885" }, { "desc":"The system checks the number of lost blocks every 30 seconds and compares the number of lost blocks with the threshold. The lost blocks indicator has a default threshold.", @@ -7934,8 +7970,8 @@ "title":"ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold", "uri":"alm_14003.html", "doc_type":"usermanual", - "p_code":"852", - "code":"882" + "p_code":"856", + "code":"886" }, { "desc":"The system checks the number of damaged blocks every 30 seconds and compares the number of damaged blocks with the threshold. The damaged blocks indicator has a default t", @@ -7943,8 +7979,8 @@ "title":"ALM-14004 Number of Damaged HDFS Blocks Exceeds the Threshold", "uri":"alm_14004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"883" + "p_code":"856", + "code":"887" }, { "desc":"The system periodically checks the number of HDFS files every 30 seconds and compares the number of HDFS files with the threshold. This alarm is generated when the system", @@ -7952,8 +7988,8 @@ "title":"ALM-14006 Number of HDFS Files Exceeds the Threshold", "uri":"alm_14006.html", "doc_type":"usermanual", - "p_code":"852", - "code":"884" + "p_code":"856", + "code":"888" }, { "desc":"The system checks the HDFS NameNode memory usage every 30 seconds and compares the actual memory usage with the threshold. The HDFS NameNode memory usage has a default th", @@ -7961,8 +7997,8 @@ "title":"ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold", "uri":"alm_14007.html", "doc_type":"usermanual", - "p_code":"852", - "code":"885" + "p_code":"856", + "code":"889" }, { "desc":"The system checks the HDFS DataNode memory usage every 30 seconds and compares the actual memory usage with the threshold. The HDFS DataNode memory usage has a default th", @@ -7970,8 +8006,8 @@ "title":"ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold", "uri":"alm_14008.html", "doc_type":"usermanual", - "p_code":"852", - "code":"886" + "p_code":"856", + "code":"890" }, { "desc":"The system periodically checks the number of faulty DataNodes in the HDFS cluster every 30 seconds, and compares the number with the threshold. The number of faulty DataN", @@ -7979,8 +8015,8 @@ "title":"ALM-14009 Number of Faulty DataNodes Exceeds the Threshold", "uri":"alm_14009.html", "doc_type":"usermanual", - "p_code":"852", - "code":"887" + "p_code":"856", + "code":"891" }, { "desc":"The system checks the NameService service status every 180 seconds. This alarm is generated when the NameService service is unavailable.This alarm is cleared when the Nam", @@ -7988,8 +8024,8 @@ "title":"ALM-14010 NameService Service Is Abnormal", "uri":"alm_14010.html", "doc_type":"usermanual", - "p_code":"852", - "code":"888" + "p_code":"856", + "code":"892" }, { "desc":"The DataNode parameter dfs.datanode.data.dir specifies the DataNode data directory. This alarm is generated in any of the following scenarios:A configured data directory ", @@ -7997,8 +8033,8 @@ "title":"ALM-14011 HDFS DataNode Data Directory Is Not Configured Properly", "uri":"alm_14011.html", "doc_type":"usermanual", - "p_code":"852", - "code":"889" + "p_code":"856", + "code":"893" }, { "desc":"On the active NameNode, the system checks data synchronization on all JournalNodes in the cluster every 5 minutes. This alarm is generated when data on a JournalNode is n", @@ -8006,8 +8042,8 @@ "title":"ALM-14012 HDFS JournalNode Data Is Not Synchronized", "uri":"alm_14012.html", "doc_type":"usermanual", - "p_code":"852", - "code":"890" + "p_code":"856", + "code":"894" }, { "desc":"The system checks the percentage of sessions connected to the HiveServer to the maximum number allowed every 30 seconds. This indicator can be viewed on the Hive service ", @@ -8015,8 +8051,8 @@ "title":"ALM-16000 Percentage of Sessions Connected to the HiveServer to the Maximum Number Allowed Exceeds the Threshold", "uri":"alm_16000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"891" + "p_code":"856", + "code":"895" }, { "desc":"The system checks the Hive warehouse space usage every 30 seconds. The indicator Percentage of HDFS Space Used by Hive to the Available Space can be viewed on the Hive se", @@ -8024,8 +8060,8 @@ "title":"ALM-16001 Hive Warehouse Space Usage Exceeds the Threshold", "uri":"alm_16001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"892" + "p_code":"856", + "code":"896" }, { "desc":"The system checks the percentage of the HiveQL statements that are executed successfully every 30 seconds. Percentage of HiveQL statements that are executed successfully ", @@ -8033,8 +8069,8 @@ "title":"ALM-16002 Hive SQL Execution Success Rate Is Lower Than the Threshold", "uri":"alm_16002.html", "doc_type":"usermanual", - "p_code":"852", - "code":"893" + "p_code":"856", + "code":"897" }, { "desc":"The system checks the Hive service status every 30 seconds. This alarm is generated when the Hive service is unavailable.This alarm is cleared when the Hive service recov", @@ -8042,8 +8078,8 @@ "title":"ALM-16004 Hive Service Unavailable", "uri":"alm_16004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"894" + "p_code":"856", + "code":"898" }, { "desc":"The alarm module checks the Yarn service status every 30 seconds. This alarm is generated when the Yarn service is unavailable.This alarm is cleared when the Yarn service", @@ -8051,8 +8087,8 @@ "title":"ALM-18000 Yarn Service Unavailable", "uri":"alm_18000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"895" + "p_code":"856", + "code":"899" }, { "desc":"The system checks the number of lost NodeManager nodes every 30 seconds, and compares the number of lost nodes with the threshold. The Lost Nodes indicator has a default ", @@ -8060,8 +8096,8 @@ "title":"ALM-18002 NodeManager Heartbeat Lost", "uri":"alm_18002.html", "doc_type":"usermanual", - "p_code":"852", - "code":"896" + "p_code":"856", + "code":"900" }, { "desc":"The system checks the number of abnormal NodeManager nodes every 30 seconds, and compares the number of abnormal nodes with the threshold. The Unhealthy Nodes indicator h", @@ -8069,8 +8105,8 @@ "title":"ALM-18003 NodeManager Unhealthy", "uri":"alm_18003.html", "doc_type":"usermanual", - "p_code":"852", - "code":"897" + "p_code":"856", + "code":"901" }, { "desc":"The system checks the available disk space of each NodeManager node every 30 seconds and compares the disk availability rate with the threshold. A default threshold range", @@ -8078,8 +8114,8 @@ "title":"ALM-18004 NodeManager Disk Usability Ratio Is Lower Than the Threshold", "uri":"alm_18004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"898" + "p_code":"856", + "code":"902" }, { "desc":"The alarm module checks the MapReduce job execution every 30 seconds. This alarm is generated when the execution of a submitted MapReduce job times out.This alarm must be", @@ -8087,8 +8123,8 @@ "title":"ALM-18006 MapReduce Job Execution Timeout", "uri":"alm_18006.html", "doc_type":"usermanual", - "p_code":"852", - "code":"899" + "p_code":"856", + "code":"903" }, { "desc":"The alarm module checks the HBase service status every 30 seconds. This alarm is generated when the HBase service is unavailable.This alarm is cleared when the HBase serv", @@ -8096,8 +8132,8 @@ "title":"ALM-19000 HBase Service Unavailable", "uri":"alm_19000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"900" + "p_code":"856", + "code":"904" }, { "desc":"This alarm is generated when disaster recovery (DR) data fails to be synchronized to a standby cluster.This alarm is cleared when DR data synchronization succeeds.HBase d", @@ -8105,8 +8141,8 @@ "title":"ALM-19006 HBase Replication Sync Failed", "uri":"alm_19006.html", "doc_type":"usermanual", - "p_code":"852", - "code":"901" + "p_code":"856", + "code":"905" }, { "desc":"The system checks the LdapServer service status every 30 seconds. This alarm is generated when the active and standby LdapServer services are abnormal.This alarm is clear", @@ -8114,8 +8150,8 @@ "title":"ALM-25000 LdapServer Service Unavailable", "uri":"alm_25000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"902" + "p_code":"856", + "code":"906" }, { "desc":"This alarm is generated when LdapServer data on Manager is inconsistent. This alarm is cleared when the data becomes consistent.This alarm is generated when LdapServer da", @@ -8123,8 +8159,8 @@ "title":"ALM-25004 Abnormal LdapServer Data Synchronization", "uri":"alm_25004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"903" + "p_code":"856", + "code":"907" }, { "desc":"The system checks the KrbServer service status every 30 seconds. This alarm is generated when the KrbServer service is abnormal.This alarm is cleared when the KrbServer s", @@ -8132,8 +8168,8 @@ "title":"ALM-25500 KrbServer Service Unavailable", "uri":"alm_25500.html", "doc_type":"usermanual", - "p_code":"852", - "code":"904" + "p_code":"856", + "code":"908" }, { "desc":"The alarm module checks the DBService status every 30 seconds. This alarm is generated when the system detects that DBService is unavailable.This alarm is cleared when DB", @@ -8141,8 +8177,8 @@ "title":"ALM-27001 DBService Is Unavailable", "uri":"alm_27001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"905" + "p_code":"856", + "code":"909" }, { "desc":"This alarm is generated when the active or standby DBService node does not receive heartbeat messages from the peer node.This alarm is cleared when the heartbeat recovers", @@ -8150,8 +8186,8 @@ "title":"ALM-27003 DBService Heartbeat Interruption Between the Active and Standby Nodes", "uri":"alm_27003.html", "doc_type":"usermanual", - "p_code":"852", - "code":"906" + "p_code":"856", + "code":"910" }, { "desc":"The system checks the data synchronization status between the active and standby DBServices every 10 seconds. This alarm is generated when the synchronization status cann", @@ -8159,8 +8195,8 @@ "title":"ALM-27004 Data Inconsistency Between Active and Standby DBServices", "uri":"alm_27004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"907" + "p_code":"856", + "code":"911" }, { "desc":"The system checks the Spark service status every 30 seconds. This alarm is generated when the Spark service is unavailable.This alarm is cleared when the Spark service re", @@ -8168,8 +8204,8 @@ "title":"ALM-28001 Spark Service Unavailable", "uri":"alm_28001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"908" + "p_code":"856", + "code":"912" }, { "desc":"The system checks the Storm service availability every 30 seconds. This alarm is generated if the Storm service becomes unavailable after all Nimbus nodes in a cluster be", @@ -8177,8 +8213,8 @@ "title":"ALM-26051 Storm Service Unavailable", "uri":"alm_26051.html", "doc_type":"usermanual", - "p_code":"852", - "code":"909" + "p_code":"856", + "code":"913" }, { "desc":"The system checks the number of supervisors every 60 seconds and compares it with the threshold. This alarm is generated if the number of supervisors is lower than the th", @@ -8186,8 +8222,8 @@ "title":"ALM-26052 Number of Available Supervisors in Storm Is Lower Than the Threshold", "uri":"alm_26052.html", "doc_type":"usermanual", - "p_code":"852", - "code":"910" + "p_code":"856", + "code":"914" }, { "desc":"The system checks the slot usage of Storm every 60 seconds and compares it with the threshold. This alarm is generated if the slot usage exceeds the threshold.To modify t", @@ -8195,8 +8231,8 @@ "title":"ALM-26053 Slot Usage of Storm Exceeds the Threshold", "uri":"alm_26053.html", "doc_type":"usermanual", - "p_code":"852", - "code":"911" + "p_code":"856", + "code":"915" }, { "desc":"The system checks the heap memory usage of Storm Nimbus every 30 seconds and compares it with the threshold. This alarm is generated if the heap memory usage exceeds the ", @@ -8204,8 +8240,8 @@ "title":"ALM-26054 Heap Memory Usage of Storm Nimbus Exceeds the Threshold", "uri":"alm_26054.html", "doc_type":"usermanual", - "p_code":"852", - "code":"912" + "p_code":"856", + "code":"916" }, { "desc":"The system checks the Kafka service availability every 30 seconds. This alarm is generated if the Kafka service becomes unavailable.This alarm is cleared after the Kafka ", @@ -8213,8 +8249,8 @@ "title":"ALM-38000 Kafka Service Unavailable", "uri":"alm_38000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"913" + "p_code":"856", + "code":"917" }, { "desc":"The system checks the Kafka disk usage every 60 seconds and compares it with the threshold. This alarm is generated if the disk usage exceeds the threshold.To modify the ", @@ -8222,8 +8258,8 @@ "title":"ALM-38001 Insufficient Kafka Disk Space", "uri":"alm_38001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"914" + "p_code":"856", + "code":"918" }, { "desc":"The system checks the heap memory usage of Kafka every 30 seconds. This alarm is generated if the heap memory usage of Kafka exceeds the threshold (80%).This alarm is cle", @@ -8231,8 +8267,8 @@ "title":"ALM-38002 Heap Memory Usage of Kafka Exceeds the Threshold", "uri":"alm_38002.html", "doc_type":"usermanual", - "p_code":"852", - "code":"915" + "p_code":"856", + "code":"919" }, { "desc":"The alarm module checks the Flume service status every 180 seconds. This alarm is generated if the Flume service is abnormal.This alarm is cleared after the Flume service", @@ -8240,8 +8276,8 @@ "title":"ALM-24000 Flume Service Unavailable", "uri":"alm_24000.html", "doc_type":"usermanual", - "p_code":"852", - "code":"916" + "p_code":"856", + "code":"920" }, { "desc":"This alarm is generated if the Flume agent monitoring module detects that the Flume agent process is abnormal.This alarm is cleared after the Flume agent process recovers", @@ -8249,8 +8285,8 @@ "title":"ALM-24001 Flume Agent Is Abnormal", "uri":"alm_24001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"917" + "p_code":"856", + "code":"921" }, { "desc":"The alarm module monitors the port connection status on the Flume server. This alarm is generated if the Flume server fails to receive a connection message from the Flume", @@ -8258,8 +8294,8 @@ "title":"ALM-24003 Flume Client Connection Failure", "uri":"alm_24003.html", "doc_type":"usermanual", - "p_code":"852", - "code":"918" + "p_code":"856", + "code":"922" }, { "desc":"The alarm module monitors the Flume source status. This alarm is generated if the duration that Flume source fails to read data exceeds the threshold.Users can modify the", @@ -8267,8 +8303,8 @@ "title":"ALM-24004 Flume Fails to Read Data", "uri":"alm_24004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"919" + "p_code":"856", + "code":"923" }, { "desc":"The alarm module monitors the capacity of Flume channels. This alarm is generated if the duration that a channel is full or the number of times that a source fails to sen", @@ -8276,8 +8312,8 @@ "title":"ALM-24005 Data Transmission by Flume Is Abnormal", "uri":"alm_24005.html", "doc_type":"usermanual", - "p_code":"852", - "code":"920" + "p_code":"856", + "code":"924" }, { "desc":"The system checks the permission, users, and user groups of key directories or files every hour. This alarm is generated if any of these is abnormal.This alarm is cleared", @@ -8285,8 +8321,8 @@ "title":"ALM-12041 Permission of Key Files Is Abnormal", "uri":"alm_12041.html", "doc_type":"usermanual", - "p_code":"852", - "code":"921" + "p_code":"856", + "code":"925" }, { "desc":"The system checks key file configurations every hour. This alarm is generated if any key configuration is abnormal.This alarm is cleared after the configuration becomes n", @@ -8294,8 +8330,8 @@ "title":"ALM-12042 Key File Configurations Are Abnormal", "uri":"alm_12042.html", "doc_type":"usermanual", - "p_code":"852", - "code":"922" + "p_code":"856", + "code":"926" }, { "desc":"The system checks the Loader service availability every 60 seconds. This alarm is generated if the Loader service is unavailable and is cleared after the Loader service r", @@ -8303,8 +8339,8 @@ "title":"ALM-23001 Loader Service Unavailable", "uri":"alm_23001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"923" + "p_code":"856", + "code":"927" }, { "desc":"If the user has configured audit log export to the OBS on MRS Manager, the system regularly exports audit logs to the OBS. This alarm is reported if the system fails to a", @@ -8312,8 +8348,8 @@ "title":"ALM-12357 Failed to Export Audit Logs to OBS", "uri":"alm_12357.html", "doc_type":"usermanual", - "p_code":"852", - "code":"924" + "p_code":"856", + "code":"928" }, { "desc":"This alarm is generated when the system detects that a partition to which service directories are mounted is lost (because the device is removed or goes offline, or the p", @@ -8321,8 +8357,8 @@ "title":"ALM-12014 Device Partition Lost", "uri":"alm_12014.html", "doc_type":"usermanual", - "p_code":"852", - "code":"925" + "p_code":"856", + "code":"929" }, { "desc":"This alarm is generated when the system detects that a partition to which service directories are mounted enters the read-only mode (due to a bad sector or a faulty file ", @@ -8330,8 +8366,8 @@ "title":"ALM-12015 Device Partition File System Read-Only", "uri":"alm_12015.html", "doc_type":"usermanual", - "p_code":"852", - "code":"926" + "p_code":"856", + "code":"930" }, { "desc":"The system checks the DNS parsing duration every 30 seconds. This alarm is generated when the DNS parsing duration exceeds the threshold (the default threshold is 20,000 ", @@ -8339,8 +8375,8 @@ "title":"ALM-12043 DNS Parsing Duration Exceeds the Threshold", "uri":"alm_12043.html", "doc_type":"usermanual", - "p_code":"852", - "code":"927" + "p_code":"856", + "code":"931" }, { "desc":"The system checks the read packet dropped rate every 30 seconds. This alarm is generated when the read packet dropped rate exceeds the threshold (the default threshold is", @@ -8348,8 +8384,8 @@ "title":"ALM-12045 Read Packet Dropped Rate Exceeds the Threshold", "uri":"alm_12045.html", "doc_type":"usermanual", - "p_code":"852", - "code":"928" + "p_code":"856", + "code":"932" }, { "desc":"The system checks the write packet dropped rate every 30 seconds. This alarm is generated when the write packet dropped rate exceeds the threshold (the default threshold ", @@ -8357,8 +8393,8 @@ "title":"ALM-12046 Write Packet Dropped Rate Exceeds the Threshold", "uri":"alm_12046.html", "doc_type":"usermanual", - "p_code":"852", - "code":"929" + "p_code":"856", + "code":"933" }, { "desc":"The system checks the read packet error rate every 30 seconds. This alarm is generated when the read packet error rate exceeds the threshold (the default threshold is 0.5", @@ -8366,8 +8402,8 @@ "title":"ALM-12047 Read Packet Error Rate Exceeds the Threshold", "uri":"alm_12047.html", "doc_type":"usermanual", - "p_code":"852", - "code":"930" + "p_code":"856", + "code":"934" }, { "desc":"The system checks the write packet error rate every 30 seconds. This alarm is generated when the write packet error rate exceeds the threshold (the default threshold is 0", @@ -8375,8 +8411,8 @@ "title":"ALM-12048 Write Packet Error Rate Exceeds the Threshold", "uri":"alm_12048.html", "doc_type":"usermanual", - "p_code":"852", - "code":"931" + "p_code":"856", + "code":"935" }, { "desc":"The system checks the read throughput rate every 30 seconds. This alarm is generated when the read throughput rate exceeds the threshold (the default threshold is 80%) fo", @@ -8384,8 +8420,8 @@ "title":"ALM-12049 Read Throughput Rate Exceeds the Threshold", "uri":"alm_12049.html", "doc_type":"usermanual", - "p_code":"852", - "code":"932" + "p_code":"856", + "code":"936" }, { "desc":"The system checks the write throughput rate every 30 seconds. This alarm is generated when the write throughput rate exceeds the threshold (the default threshold is 80%) ", @@ -8393,8 +8429,8 @@ "title":"ALM-12050 Write Throughput Rate Exceeds the Threshold", "uri":"alm_12050.html", "doc_type":"usermanual", - "p_code":"852", - "code":"933" + "p_code":"856", + "code":"937" }, { "desc":"The system checks the disk inode usage every 30 seconds. This alarm is generated when the disk inode usage exceeds the threshold (the default threshold is 80%) for multip", @@ -8402,8 +8438,8 @@ "title":"ALM-12051 Disk Inode Usage Exceeds the Threshold", "uri":"alm_12051.html", "doc_type":"usermanual", - "p_code":"852", - "code":"934" + "p_code":"856", + "code":"938" }, { "desc":"The system checks the usage of temporary TCP ports every 30 seconds. This alarm is generated when the usage of temporary TCP ports exceeds the threshold (the default thre", @@ -8411,8 +8447,8 @@ "title":"ALM-12052 Usage of Temporary TCP Ports Exceeds the Threshold", "uri":"alm_12052.html", "doc_type":"usermanual", - "p_code":"852", - "code":"935" + "p_code":"856", + "code":"939" }, { "desc":"The system checks the handler usage every 30 seconds. This alarm is generated when the handle usage exceeds the threshold (the default threshold is 80%) for multiple time", @@ -8420,8 +8456,8 @@ "title":"ALM-12053 File Handle Usage Exceeds the Threshold", "uri":"alm_12053.html", "doc_type":"usermanual", - "p_code":"852", - "code":"936" + "p_code":"856", + "code":"940" }, { "desc":"The system checks whether the certificate file is invalid (has expired or is not yet valid) on 23:00 every day. This alarm is generated when the certificate file is inval", @@ -8429,8 +8465,8 @@ "title":"ALM-12054 The Certificate File Is Invalid", "uri":"alm_12054.html", "doc_type":"usermanual", - "p_code":"852", - "code":"937" + "p_code":"856", + "code":"941" }, { "desc":"The system checks the certificate file on 23:00 every day. This alarm is generated if the certificate file is about to expire with a validity period less than days set in", @@ -8438,8 +8474,8 @@ "title":"ALM-12055 The Certificate File Is About to Expire", "uri":"alm_12055.html", "doc_type":"usermanual", - "p_code":"852", - "code":"938" + "p_code":"856", + "code":"942" }, { "desc":"The system checks the heap memory usage of Yarn ResourceManager every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the heap me", @@ -8447,8 +8483,8 @@ "title":"ALM-18008 Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold", "uri":"alm_18008.html", "doc_type":"usermanual", - "p_code":"852", - "code":"939" + "p_code":"856", + "code":"943" }, { "desc":"The system checks the heap memory usage of MapReduce JobHistoryServer every 30 seconds and compares the actual usage with the threshold. The alarm is generated when the h", @@ -8456,8 +8492,8 @@ "title":"ALM-18009 Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold", "uri":"alm_18009.html", "doc_type":"usermanual", - "p_code":"852", - "code":"940" + "p_code":"856", + "code":"944" }, { "desc":"The system checks the Hue service status every 60 seconds. This alarm is generated if the Hue service is unavailable.This alarm is cleared when the Hue service is normal.", @@ -8465,8 +8501,8 @@ "title":"ALM-20002 Hue Service Unavailable", "uri":"alm_20002.html", "doc_type":"usermanual", - "p_code":"852", - "code":"941" + "p_code":"856", + "code":"945" }, { "desc":"The system checks the Spark service status every 60 seconds. This alarm is generated when the Spark service is unavailable.This alarm is cleared when the Spark service re", @@ -8474,8 +8510,8 @@ "title":"ALM-43001 Spark Service Unavailable", "uri":"alm_43001.html", "doc_type":"usermanual", - "p_code":"852", - "code":"942" + "p_code":"856", + "code":"946" }, { "desc":"The system checks the JobHistory process status every 30 seconds. The alarm is generated when the heap memory usage of the JobHistory process exceeds the threshold (90% o", @@ -8483,8 +8519,8 @@ "title":"ALM-43006 Heap Memory Usage of the JobHistory Process Exceeds the Threshold", "uri":"alm_43006.html", "doc_type":"usermanual", - "p_code":"852", - "code":"943" + "p_code":"856", + "code":"947" }, { "desc":"The system checks the JobHistory process status every 30 seconds. The alarm is generated when the non-heap memory usage of the JobHistory process exceeds the threshold (9", @@ -8492,8 +8528,8 @@ "title":"ALM-43007 Non-Heap Memory Usage of the JobHistory Process Exceeds the Threshold", "uri":"alm_43007.html", "doc_type":"usermanual", - "p_code":"852", - "code":"944" + "p_code":"856", + "code":"948" }, { "desc":"The system checks the JobHistory process status every 30 seconds. The alarm is generated when the direct memory usage of the JobHistory process exceeds the threshold (90%", @@ -8501,8 +8537,8 @@ "title":"ALM-43008 Direct Memory Usage of the JobHistory Process Exceeds the Threshold", "uri":"alm_43008.html", "doc_type":"usermanual", - "p_code":"852", - "code":"945" + "p_code":"856", + "code":"949" }, { "desc":"The system checks the GC time of the JobHistory process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (12 seconds) for three c", @@ -8510,8 +8546,8 @@ "title":"ALM-43009 JobHistory GC Time Exceeds the Threshold", "uri":"alm_43009.html", "doc_type":"usermanual", - "p_code":"852", - "code":"946" + "p_code":"856", + "code":"950" }, { "desc":"The system checks the JDBCServer process status every 30 seconds. The alarm is generated when the heap memory usage of the JDBCServer process exceeds the threshold (90% o", @@ -8519,8 +8555,8 @@ "title":"ALM-43010 Heap Memory Usage of the JDBCServer Process Exceeds the Threshold", "uri":"alm_43010.html", "doc_type":"usermanual", - "p_code":"852", - "code":"947" + "p_code":"856", + "code":"951" }, { "desc":"The system checks the JDBCServer process status every 30 seconds. The alarm is generated when the non-heap memory usage of the JDBCServer process exceeds the threshold (9", @@ -8528,8 +8564,8 @@ "title":"ALM-43011 Non-Heap Memory Usage of the JDBCServer Process Exceeds the Threshold", "uri":"alm_43011.html", "doc_type":"usermanual", - "p_code":"852", - "code":"948" + "p_code":"856", + "code":"952" }, { "desc":"The system checks the JDBCServer process status every 30 seconds. The alarm is generated when the direct memory usage of the JDBCServer process exceeds the threshold (90%", @@ -8537,8 +8573,8 @@ "title":"ALM-43012 Direct Memory Usage of the JDBCServer Process Exceeds the Threshold", "uri":"alm_43012.html", "doc_type":"usermanual", - "p_code":"852", - "code":"949" + "p_code":"856", + "code":"953" }, { "desc":"The system checks the GC time of the JDBCServer process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (12 seconds) for three c", @@ -8546,8 +8582,8 @@ "title":"ALM-43013 JDBCServer GC Time Exceeds the Threshold", "uri":"alm_43013.html", "doc_type":"usermanual", - "p_code":"852", - "code":"950" + "p_code":"856", + "code":"954" }, { "desc":"This alarm is generated when the system detects that the number of queuing tasks in a resource group exceeds the threshold. The system queries the number of queuing tasks", @@ -8555,8 +8591,8 @@ "title":"ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold", "uri":"alm_44004.html", "doc_type":"usermanual", - "p_code":"852", - "code":"951" + "p_code":"856", + "code":"955" }, { "desc":"The system collects GC time of the Presto Coordinator process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for thre", @@ -8564,8 +8600,8 @@ "title":"ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold", "uri":"alm_44005.html", "doc_type":"usermanual", - "p_code":"852", - "code":"952" + "p_code":"856", + "code":"956" }, { "desc":"The system collects GC time of the Presto Worker process every 30 seconds. This alarm is generated when the GC time exceeds the threshold (exceeds 5 seconds for three con", @@ -8573,8 +8609,8 @@ "title":"ALM-44006 Presto Worker Process GC Time Exceeds the Threshold", "uri":"alm_44006.html", "doc_type":"usermanual", - "p_code":"852", - "code":"953" + "p_code":"856", + "code":"957" }, { "desc":"The system checks the number of pending Yarn tasks every 30 seconds and compares the number of tasks with the threshold. This alarm is generated when the number of pendin", @@ -8582,8 +8618,8 @@ "title":"ALM-18010 Number of Pending Yarn Tasks Exceeds the Threshold", "uri":"alm_18010.html", "doc_type":"usermanual", - "p_code":"852", - "code":"954" + "p_code":"856", + "code":"958" }, { "desc":"The system checks the memory of pending Yarn tasks every 30 seconds and compares the memory with the threshold. This alarm is generated when the memory of pending tasks e", @@ -8591,8 +8627,8 @@ "title":"ALM-18011 Memory of Pending Yarn Tasks Exceeds the Threshold", "uri":"alm_18011.html", "doc_type":"usermanual", - "p_code":"852", - "code":"955" + "p_code":"856", + "code":"959" }, { "desc":"The system checks the number of terminated Yarn tasks every 10 minutes. This alarm is generated when the number of terminated Yarn tasks in the last 10 minutes is greater", @@ -8600,8 +8636,8 @@ "title":"ALM-18012 Number of Terminated Yarn Tasks in the Last Period Exceeds the Threshold", "uri":"alm_18012.html", "doc_type":"usermanual", - "p_code":"852", - "code":"956" + "p_code":"856", + "code":"960" }, { "desc":"The system checks the number of failed Yarn tasks every 10 minutes. This alarm is generated when the number of failed Yarn tasks in the last 10 minutes is greater than th", @@ -8609,8 +8645,8 @@ "title":"ALM-18013 Number of Failed Yarn Tasks in the Last Period Exceeds the Threshold", "uri":"alm_18013.html", "doc_type":"usermanual", - "p_code":"852", - "code":"957" + "p_code":"856", + "code":"961" }, { "desc":"The system checks whether the number of Hive SQL statements that fail to be executed has exceeded the threshold in the last 10-minute period. This alarm is generated when", @@ -8618,8 +8654,8 @@ "title":"ALM-16005 Number of Failed Hive SQL Executions in the Last Period Exceeds the Threshold", "uri":"alm_16005.html", "doc_type":"usermanual", - "p_code":"852", - "code":"958" + "p_code":"856", + "code":"962" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -8627,8 +8663,8 @@ "title":"Object Management", "uri":"mrs_01_0242.html", "doc_type":"usermanual", - "p_code":"839", - "code":"959" + "p_code":"843", + "code":"963" }, { "desc":"MRS contains different types of basic objects as described in Table 1.", @@ -8636,8 +8672,8 @@ "title":"Managing Objects", "uri":"mrs_01_0243.html", "doc_type":"usermanual", - "p_code":"959", - "code":"960" + "p_code":"963", + "code":"964" }, { "desc":"On MRS Manager, users can view the configurations of services (including roles) and role instances.Query service configurations.On MRS Manager page, click Services.Select", @@ -8645,8 +8681,8 @@ "title":"Viewing Configurations", "uri":"mrs_01_0244.html", "doc_type":"usermanual", - "p_code":"959", - "code":"961" + "p_code":"963", + "code":"965" }, { "desc":"You can perform the following operations on MRS Manager:Start the service in the Stopped, Stop Failed, or Start Failed state to use the service.Stop the services or stop ", @@ -8654,8 +8690,8 @@ "title":"Managing Services", "uri":"mrs_01_0245.html", "doc_type":"usermanual", - "p_code":"959", - "code":"962" + "p_code":"963", + "code":"966" }, { "desc":"On MRS Manager, you can view and modify the default service configurations based on site requirements and export or import the configurations.You need to download and upd", @@ -8663,8 +8699,8 @@ "title":"Configuring Service Parameters", "uri":"mrs_01_0246.html", "doc_type":"usermanual", - "p_code":"959", - "code":"963" + "p_code":"963", + "code":"967" }, { "desc":"Each component of MRS supports all open-source parameters. You can modify some parameters for key application scenarios on MRS Manager. Some component clients may not inc", @@ -8672,8 +8708,8 @@ "title":"Configuring Customized Service Parameters", "uri":"mrs_01_0247.html", "doc_type":"usermanual", - "p_code":"959", - "code":"964" + "p_code":"963", + "code":"968" }, { "desc":"If Configuration Status of a service is Expired or Failed, synchronize configurations for the cluster or service to restore its configuration status. If all services in t", @@ -8681,8 +8717,8 @@ "title":"Synchronizing Service Configurations", "uri":"mrs_01_0248.html", "doc_type":"usermanual", - "p_code":"959", - "code":"965" + "p_code":"963", + "code":"969" }, { "desc":"You can start a role instance that is in the Stopped, Failed to stop or Failed to start status, stop an unused or abnormal role instance or restart an abnormal role insta", @@ -8690,8 +8726,8 @@ "title":"Managing Role Instances", "uri":"mrs_01_0249.html", "doc_type":"usermanual", - "p_code":"959", - "code":"966" + "p_code":"963", + "code":"970" }, { "desc":"You can view and modify default role instance configurations on MRS Manager based on site requirements. The configurations can be imported and exported.You need to downlo", @@ -8699,8 +8735,8 @@ "title":"Configuring Role Instance Parameters", "uri":"mrs_01_0250.html", "doc_type":"usermanual", - "p_code":"959", - "code":"967" + "p_code":"963", + "code":"971" }, { "desc":"When Configuration Status of a role instance is Expired or Failed, you can synchronize the configuration data of the role instance with the background configuration.After", @@ -8708,8 +8744,8 @@ "title":"Synchronizing Role Instance Configuration", "uri":"mrs_01_0251.html", "doc_type":"usermanual", - "p_code":"959", - "code":"968" + "p_code":"963", + "code":"972" }, { "desc":"If a Core or Task node is faulty, the cluster status may be displayed as Abnormal. In an MRS cluster, data can be stored on different Core nodes. Users can decommission t", @@ -8717,8 +8753,8 @@ "title":"Decommissioning and Recommissioning a Role Instance", "uri":"mrs_01_0252.html", "doc_type":"usermanual", - "p_code":"959", - "code":"969" + "p_code":"963", + "code":"973" }, { "desc":"When a host is abnormal or faulty, you need to stop all roles of the host on MRS Manager to check the host. After the host fault is rectified, start all roles running on ", @@ -8726,8 +8762,8 @@ "title":"Managing a Host", "uri":"mrs_01_0254.html", "doc_type":"usermanual", - "p_code":"959", - "code":"970" + "p_code":"963", + "code":"974" }, { "desc":"If a host is found to be abnormal or faulty, affecting cluster performance or preventing services from being provided, you can temporarily exclude that host from the avai", @@ -8735,8 +8771,8 @@ "title":"Isolating a Host", "uri":"mrs_01_0255.html", "doc_type":"usermanual", - "p_code":"959", - "code":"971" + "p_code":"963", + "code":"975" }, { "desc":"After the exception or fault of a host is handled, you must cancel the isolation of the host for proper usage.Users can cancel the isolation of a host on MRS Manager.The ", @@ -8744,8 +8780,8 @@ "title":"Canceling Host Isolation", "uri":"mrs_01_0256.html", "doc_type":"usermanual", - "p_code":"959", - "code":"972" + "p_code":"963", + "code":"976" }, { "desc":"A cluster is a collection of service components. You can start or stop all services in a cluster.", @@ -8753,8 +8789,8 @@ "title":"Starting or Stopping a Cluster", "uri":"mrs_01_0258.html", "doc_type":"usermanual", - "p_code":"959", - "code":"973" + "p_code":"963", + "code":"977" }, { "desc":"If Configuration Status of all services or some services is Expired or Failed, synchronize configuration for the cluster or service to restore its configuration status.If", @@ -8762,8 +8798,8 @@ "title":"Synchronizing Cluster Configurations", "uri":"mrs_01_0259.html", "doc_type":"usermanual", - "p_code":"959", - "code":"974" + "p_code":"963", + "code":"978" }, { "desc":"You can export all configuration data of a cluster on MRS Manager to meet site requirements. The exported configuration data is used to rapidly update service configurati", @@ -8771,8 +8807,8 @@ "title":"Exporting Configuration Data of a Cluster", "uri":"mrs_01_0260.html", "doc_type":"usermanual", - "p_code":"959", - "code":"975" + "p_code":"963", + "code":"979" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -8780,8 +8816,8 @@ "title":"Log Management", "uri":"mrs_01_0264.html", "doc_type":"usermanual", - "p_code":"839", - "code":"976" + "p_code":"843", + "code":"980" }, { "desc":"MRS cluster logs are stored in the /var/log/Bigdata directory. The following table lists the log types.The following table lists the MRS log directories.Table 3 describes", @@ -8789,8 +8825,8 @@ "title":"About Logs", "uri":"mrs_01_1226.html", "doc_type":"usermanual", - "p_code":"976", - "code":"977" + "p_code":"980", + "code":"981" }, { "desc":"Log path: The default storage path of Manager log files is /var/log/Bigdata/Manager component.ControllerService: /var/log/Bigdata/controller/ (operation & maintenance sys", @@ -8798,8 +8834,8 @@ "title":"Manager Log List", "uri":"mrs_01_1227.html", "doc_type":"usermanual", - "p_code":"976", - "code":"978" + "p_code":"980", + "code":"982" }, { "desc":"This section describes how to view and export audit logs on MRS Manager. The audit logs can be used to trace security events, locate fault causes, and determine responsib", @@ -8807,8 +8843,8 @@ "title":"Viewing and Exporting Audit Logs", "uri":"mrs_01_0265.html", "doc_type":"usermanual", - "p_code":"976", - "code":"979" + "p_code":"980", + "code":"983" }, { "desc":"This section describes how to export logs generated by each service role from MRS Manager.You have obtained the access key ID (AK) and secret access key (SK) of the accou", @@ -8816,8 +8852,8 @@ "title":"Exporting Service Logs", "uri":"mrs_01_0267.html", "doc_type":"usermanual", - "p_code":"976", - "code":"980" + "p_code":"980", + "code":"984" }, { "desc":"If MRS audit logs are stored in the system for a long time, the disk space of the data directory may be insufficient. Therefore, you can set export parameters to automati", @@ -8825,8 +8861,8 @@ "title":"Configuring Audit Log Exporting Parameters", "uri":"mrs_01_0270.html", "doc_type":"usermanual", - "p_code":"976", - "code":"981" + "p_code":"980", + "code":"985" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -8834,8 +8870,8 @@ "title":"Health Check Management", "uri":"mrs_01_0271.html", "doc_type":"usermanual", - "p_code":"839", - "code":"982" + "p_code":"843", + "code":"986" }, { "desc":"To ensure that cluster parameters, configurations, and monitoring are correct and that the cluster can run stably for a long time, you can perform a health check during r", @@ -8843,8 +8879,8 @@ "title":"Performing a Health Check", "uri":"mrs_01_0274.html", "doc_type":"usermanual", - "p_code":"982", - "code":"983" + "p_code":"986", + "code":"987" }, { "desc":"You can view the health check result in MRS Manager and export the health check results for further analysis.A system health check includes MRS Manager, service-level, an", @@ -8852,8 +8888,8 @@ "title":"Viewing and Exporting a Health Check Report", "uri":"mrs_01_0275.html", "doc_type":"usermanual", - "p_code":"982", - "code":"984" + "p_code":"986", + "code":"988" }, { "desc":"Health check reports of MRS clusters, services, and hosts may vary with the time and scenario. You can modify the number of health check reports to be reserved on MRS Man", @@ -8861,8 +8897,8 @@ "title":"Configuring the Number of Health Check Reports to Be Reserved", "uri":"mrs_01_0277.html", "doc_type":"usermanual", - "p_code":"982", - "code":"985" + "p_code":"986", + "code":"989" }, { "desc":"On MRS Manager, users can manage historical health check reports, for example, viewing, downloading, and deleting historical health check reports.Download a specified hea", @@ -8870,8 +8906,8 @@ "title":"Managing Health Check Reports", "uri":"mrs_01_0278.html", "doc_type":"usermanual", - "p_code":"982", - "code":"986" + "p_code":"986", + "code":"990" }, { "desc":"Indicator: Service StatusDescription: This indicator is used to check whether the DBService service status is normal. If the status is abnormal, the service is unhealthy.", @@ -8879,8 +8915,8 @@ "title":"DBService Health Check Indicators", "uri":"mrs_01_0279.html", "doc_type":"usermanual", - "p_code":"982", - "code":"987" + "p_code":"986", + "code":"991" }, { "desc":"Indicator: Service StatusDescription: This indicator is used to check whether the Flume service status is normal. If the status is abnormal, the service is unhealthy.Reco", @@ -8888,8 +8924,8 @@ "title":"Flume Health Check Indicators", "uri":"mrs_01_0280.html", "doc_type":"usermanual", - "p_code":"982", - "code":"988" + "p_code":"986", + "code":"992" }, { "desc":"Indicator: Normal RegionServer CountDescription: This indicator is used to check the number of RegionServers that are running properly in an HBase cluster.Recovery Guide:", @@ -8897,8 +8933,8 @@ "title":"HBase Health Check Indicators", "uri":"mrs_01_0281.html", "doc_type":"usermanual", - "p_code":"982", - "code":"989" + "p_code":"986", + "code":"993" }, { "desc":"Indicator: Swap UsageDescription: Swap usage of the system. The value is calculated using the following formula: Swap usage = Used swap size/Total swap size. Assume that ", @@ -8906,8 +8942,8 @@ "title":"Host Health Check Indicators", "uri":"mrs_01_0282.html", "doc_type":"usermanual", - "p_code":"982", - "code":"990" + "p_code":"986", + "code":"994" }, { "desc":"Indicator: Average Packet Sending TimeDescription: This indicator is used to collect statistics on the average time for the DataNode in the HDFS to execute SendPacket eac", @@ -8915,8 +8951,8 @@ "title":"HDFS Health Check Indicators", "uri":"mrs_01_0284.html", "doc_type":"usermanual", - "p_code":"982", - "code":"991" + "p_code":"986", + "code":"995" }, { "desc":"Indicator: Maximum Number of Sessions Allowed by HiveServerDescription: This indicator is used to check the maximum number of sessions that can be connected to Hive.Recov", @@ -8924,8 +8960,8 @@ "title":"Hive Health Check Indicators", "uri":"mrs_01_0285.html", "doc_type":"usermanual", - "p_code":"982", - "code":"992" + "p_code":"986", + "code":"996" }, { "desc":"Indicator: Number of BrokersDescription: This indicator is used to check the number of available Broker nodes in a cluster. If the number of available Broker nodes in a c", @@ -8933,8 +8969,8 @@ "title":"Kafka Health Check Indicators", "uri":"mrs_01_0288.html", "doc_type":"usermanual", - "p_code":"982", - "code":"993" + "p_code":"986", + "code":"997" }, { "desc":"Indicator: KerberosAdmin Service AvailabilityDescription: The system checks the KerberosAdmin service status. If the check result is abnormal, the KerberosAdmin service i", @@ -8942,8 +8978,8 @@ "title":"KrbServer Health Check Indicators", "uri":"mrs_01_0289.html", "doc_type":"usermanual", - "p_code":"982", - "code":"994" + "p_code":"986", + "code":"998" }, { "desc":"Indicator: SlapdServer Service AvailabilityDescription: The system checks the SlapdServer service status. If the status is abnormal, the SlapdServer service is unavailabl", @@ -8951,8 +8987,8 @@ "title":"LdapServer Health Check Indicators", "uri":"mrs_01_0291.html", "doc_type":"usermanual", - "p_code":"982", - "code":"995" + "p_code":"986", + "code":"999" }, { "desc":"Indicator: ZooKeeper health statusDescription: This indicator is used to check whether the ZooKeeper health status is normal. If the status is abnormal, the ZooKeeper ser", @@ -8960,8 +8996,8 @@ "title":"Loader Health Check Indicators", "uri":"mrs_01_0292.html", "doc_type":"usermanual", - "p_code":"982", - "code":"996" + "p_code":"986", + "code":"1000" }, { "desc":"Indicator: Service StatusDescription: This indicator is used to check whether the MapReduce service status is normal. If the status is abnormal, the service is unhealthy.", @@ -8969,8 +9005,8 @@ "title":"MapReduce Health Check Indicators", "uri":"mrs_01_0293.html", "doc_type":"usermanual", - "p_code":"982", - "code":"997" + "p_code":"986", + "code":"1001" }, { "desc":"Indicator: OMS Status CheckDescription: The OMS status check includes the HA status check and resource status check. The HA status includes active, standby, and NULL, ind", @@ -8978,8 +9014,8 @@ "title":"OMS Health Check Indicators", "uri":"mrs_01_0294.html", "doc_type":"usermanual", - "p_code":"982", - "code":"998" + "p_code":"986", + "code":"1002" }, { "desc":"Indicator: Service StatusDescription: This indicator is used to check whether the Spark service status is normal. If the status is abnormal, the service is unhealthy.Reco", @@ -8987,8 +9023,8 @@ "title":"Spark Health Check Indicators", "uri":"mrs_01_0530.html", "doc_type":"usermanual", - "p_code":"982", - "code":"999" + "p_code":"986", + "code":"1003" }, { "desc":"Indicator: Number of SupervisorsDescription: This indicator is used to check the number of available Supervisors in a cluster. If the number of available Supervisors in a", @@ -8996,8 +9032,8 @@ "title":"Storm Health Check Indicators", "uri":"mrs_01_0531.html", "doc_type":"usermanual", - "p_code":"982", - "code":"1000" + "p_code":"986", + "code":"1004" }, { "desc":"Indicator: Service StatusDescription: This indicator is used to check whether the Yarn service status is normal. If the number of NodeManager nodes cannot be obtained, th", @@ -9005,8 +9041,8 @@ "title":"Yarn Health Check Indicators", "uri":"mrs_01_0532.html", "doc_type":"usermanual", - "p_code":"982", - "code":"1001" + "p_code":"986", + "code":"1005" }, { "desc":"Indicator: Average ZooKeeper Service Request Processing LatencyDescription: This indicator is used to check the average delay for the ZooKeeper service to process request", @@ -9014,8 +9050,8 @@ "title":"ZooKeeper Health Check Indicators", "uri":"mrs_01_0533.html", "doc_type":"usermanual", - "p_code":"982", - "code":"1002" + "p_code":"986", + "code":"1006" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9023,8 +9059,8 @@ "title":"Static Service Pool Management", "uri":"mrs_01_0534.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1003" + "p_code":"843", + "code":"1007" }, { "desc":"MRS Manager manages and isolates service resources that are not running on YARN through the static service resource pool. It dynamically manages the total CPU, I/O, and m", @@ -9032,8 +9068,8 @@ "title":"Viewing the Status of a Static Service Pool", "uri":"mrs_01_0535.html", "doc_type":"usermanual", - "p_code":"1003", - "code":"1004" + "p_code":"1007", + "code":"1008" }, { "desc":"If you need to control the node resources that can be used by the cluster service or the CPU usage of the node used by the cluster in different time periods, you can adju", @@ -9041,8 +9077,8 @@ "title":"Configuring a Static Service Pool", "uri":"mrs_01_0536.html", "doc_type":"usermanual", - "p_code":"1003", - "code":"1005" + "p_code":"1007", + "code":"1009" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9050,8 +9086,8 @@ "title":"Tenant Management", "uri":"mrs_01_0537.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1006" + "p_code":"843", + "code":"1010" }, { "desc":"An MRS cluster provides various resources and services for multiple organizations, departments, or applications to share. The cluster provides tenants as a logical entity", @@ -9059,8 +9095,8 @@ "title":"Overview", "uri":"mrs_01_0538.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1007" + "p_code":"1010", + "code":"1011" }, { "desc":"You can create a tenant on MRS Manager to specify the resource usage.A tenant name has been planned. The name must not be the same as that of a role or Yarn queue that ex", @@ -9068,8 +9104,8 @@ "title":"Creating a Tenant", "uri":"mrs_01_0539.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1008" + "p_code":"1010", + "code":"1012" }, { "desc":"You can create a sub-tenant on MRS Manager if the resources of the current tenant need to be further allocated.A parent tenant has been added.A tenant name has been plann", @@ -9077,8 +9113,8 @@ "title":"Creating a Sub-tenant", "uri":"mrs_01_0540.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1009" + "p_code":"1010", + "code":"1013" }, { "desc":"You can delete a tenant that is not required on MRS Manager.A tenant has been added.You have checked whether the tenant to be deleted has sub-tenants. If the tenant has s", @@ -9086,8 +9122,8 @@ "title":"Deleting a tenant", "uri":"mrs_01_0541.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1010" + "p_code":"1010", + "code":"1014" }, { "desc":"You can manage the HDFS storage directory used by a specific tenant on MRS Manager. The management operations include adding a tenant directory, modifying the directory f", @@ -9095,8 +9131,8 @@ "title":"Managing a Tenant Directory", "uri":"mrs_01_0542.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1011" + "p_code":"1010", + "code":"1015" }, { "desc":"Tenant data is stored on Manager and in cluster components by default. When components are restored from faults or reinstalled, some tenant configuration data may be abno", @@ -9104,8 +9140,8 @@ "title":"Restoring Tenant Data", "uri":"mrs_01_0543.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1012" + "p_code":"1010", + "code":"1016" }, { "desc":"In an MRS cluster, users can logically divide Yarn cluster nodes to combine multiple NodeManagers into a Yarn resource pool. Each NodeManager belongs to one resource pool", @@ -9113,8 +9149,8 @@ "title":"Creating a Resource Pool", "uri":"mrs_01_0544.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1013" + "p_code":"1010", + "code":"1017" }, { "desc":"You can modify members of an existing resource pool on MRS Manager.Adding a host: Select the name of a specified host in host list on the left and click to add the selec", @@ -9122,8 +9158,8 @@ "title":"Modifying a Resource Pool", "uri":"mrs_01_0545.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1014" + "p_code":"1010", + "code":"1018" }, { "desc":"You can delete an existing resource pool on MRS Manager.Any queue in a cluster cannot use the resource pool to be deleted as the default resource pool. Before deleting th", @@ -9131,8 +9167,8 @@ "title":"Deleting a Resource Pool", "uri":"mrs_01_0546.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1015" + "p_code":"1010", + "code":"1019" }, { "desc":"This section describes how to modify the queue configuration for a specified tenant on MRS Manager.A tenant associated with Yarn and allocated dynamic resources has been ", @@ -9140,8 +9176,8 @@ "title":"Configuring a Queue", "uri":"mrs_01_0547.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1016" + "p_code":"1010", + "code":"1020" }, { "desc":"After a resource pool is added, the capacity policies of available resources need to be configured for Yarn task queues. This ensures that tasks in the resource pool are ", @@ -9149,8 +9185,8 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"mrs_01_0548.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1017" + "p_code":"1010", + "code":"1021" }, { "desc":"Users can clear the configuration of a queue on MRS Manager when the queue does not need resources from a resource pool or if a resource pool needs to be disassociated fr", @@ -9158,8 +9194,8 @@ "title":"Clearing Configuration of a Queue", "uri":"mrs_01_0549.html", "doc_type":"usermanual", - "p_code":"1006", - "code":"1018" + "p_code":"1010", + "code":"1022" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9167,8 +9203,8 @@ "title":"Backup and Restoration", "uri":"mrs_01_0550.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1019" + "p_code":"843", + "code":"1023" }, { "desc":"MRS Manager provides backup and restoration for user data and system data. The backup function is provided based on components to back up Manager data (including OMS data", @@ -9176,8 +9212,8 @@ "title":"Introduction", "uri":"mrs_01_0551.html", "doc_type":"usermanual", - "p_code":"1019", - "code":"1020" + "p_code":"1023", + "code":"1024" }, { "desc":"To ensure the security of metadata either on a routine basis or before and after performing critical metadata operations (such as scale-out, scale-in, patch installation,", @@ -9185,8 +9221,8 @@ "title":"Backing Up Metadata", "uri":"mrs_01_0553.html", "doc_type":"usermanual", - "p_code":"1019", - "code":"1021" + "p_code":"1023", + "code":"1025" }, { "desc":"You need to restore metadata in the following scenarios: A user modifies or deletes data unexpectedly, data needs to be retrieved, system data becomes abnormal or does no", @@ -9194,8 +9230,8 @@ "title":"Restoring Metadata", "uri":"mrs_01_0555.html", "doc_type":"usermanual", - "p_code":"1019", - "code":"1022" + "p_code":"1023", + "code":"1026" }, { "desc":"This section describes how to modify the parameters of a created backup task on MRS Manager to meet changing service requirements. The parameters of restoration tasks can", @@ -9203,8 +9239,8 @@ "title":"Modifying a Backup Task", "uri":"mrs_01_0558.html", "doc_type":"usermanual", - "p_code":"1019", - "code":"1023" + "p_code":"1023", + "code":"1027" }, { "desc":"This section describes how to view created backup and restoration tasks and check their running status on MRS Manager.In the displayed window, click View in the Details c", @@ -9212,8 +9248,8 @@ "title":"Viewing Backup and Restoration Tasks", "uri":"mrs_01_0559.html", "doc_type":"usermanual", - "p_code":"1019", - "code":"1024" + "p_code":"1023", + "code":"1028" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9221,8 +9257,8 @@ "title":"Security Management", "uri":"mrs_01_0560.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1025" + "p_code":"843", + "code":"1029" }, { "desc":"The MRS cluster provides the following two types of users. Users are advised to periodically change the passwords. It is not recommended to use the default passwords.User", @@ -9230,8 +9266,8 @@ "title":"Default Users of Clusters with Kerberos Authentication Disabled", "uri":"mrs_01_0561.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1026" + "p_code":"1029", + "code":"1030" }, { "desc":"The MRS cluster provides the following three types of users. Users are advised to periodically change the passwords. It is not recommended to use the default passwords.Us", @@ -9239,8 +9275,8 @@ "title":"Default Users of Clusters with Kerberos Authentication Enabled", "uri":"mrs_01_24044.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1027" + "p_code":"1029", + "code":"1031" }, { "desc":"This section describes how to periodically change the login passwords of the OS users omm, ommdba, and root on MRS cluster nodes to improve the system O&M security.Passwo", @@ -9248,8 +9284,8 @@ "title":"Changing the Password of an OS User", "uri":"mrs_01_0562.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1028" + "p_code":"1029", + "code":"1032" }, { "desc":"This section describes how to periodically change the password of cluster user admin to improve the system O&M security.If the password is changed, the downloaded user cr", @@ -9257,8 +9293,8 @@ "title":"Changing the password of user admin", "uri":"mrs_01_0563.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1029" + "p_code":"1029", + "code":"1033" }, { "desc":"This section describes how to periodically change the password of the Kerberos administrator kadmin of the MRS cluster to improve the system O&M security.If the password ", @@ -9266,8 +9302,8 @@ "title":"Changing the Password of the Kerberos Administrator", "uri":"mrs_01_0564.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1030" + "p_code":"1029", + "code":"1034" }, { "desc":"This section describes how to periodically change the passwords of the LDAP administrator rootdn:cn=root,dc=hadoop,dc=com and the LDAP user pg_search_dn:cn=pg_search_dn,o", @@ -9275,8 +9311,8 @@ "title":"Changing the Passwords of the LDAP Administrator and the LDAP User", "uri":"mrs_01_0565.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1031" + "p_code":"1029", + "code":"1035" }, { "desc":"This section describes how to periodically change the password of the component running user of the MRS cluster to improve the system O&M security.If the initial password", @@ -9284,8 +9320,8 @@ "title":"Changing the Password of a Component Running User", "uri":"mrs_01_0566.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1032" + "p_code":"1029", + "code":"1036" }, { "desc":"This section describes how to periodically change the password of the OMS database administrator to improve the system O&M security.The password of user ommdba cannot be ", @@ -9293,8 +9329,8 @@ "title":"Changing the Password of the OMS Database Administrator", "uri":"mrs_01_0567.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1033" + "p_code":"1029", + "code":"1037" }, { "desc":"This section describes how to periodically change the password of the data access user of the OMS database to improve the system O&M security.The OMS service needs to be ", @@ -9302,8 +9338,8 @@ "title":"Changing the Password of the Data Access User of the OMS Database", "uri":"mrs_01_0568.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1034" + "p_code":"1029", + "code":"1038" }, { "desc":"This section describes how to periodically change the password of the component database user to improve the system O&M security.The services need to be restarted for the", @@ -9311,8 +9347,8 @@ "title":"Changing the Password of a Component Database User", "uri":"mrs_01_0569.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1035" + "p_code":"1029", + "code":"1039" }, { "desc":"HA certificates are used to encrypt the communication between active/standby processes and HA processes to ensure the communication security. This section describes how t", @@ -9320,8 +9356,8 @@ "title":"Replacing the HA Certificate", "uri":"mrs_01_0571.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1036" + "p_code":"1029", + "code":"1040" }, { "desc":"When a cluster is installed, an encryption key is generated automatically to store the security information in the cluster (such as all database user passwords and key fi", @@ -9329,8 +9365,8 @@ "title":"Updating Cluster Keys", "uri":"mrs_01_0572.html", "doc_type":"usermanual", - "p_code":"1025", - "code":"1037" + "p_code":"1029", + "code":"1041" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9338,8 +9374,8 @@ "title":"Permissions Management", "uri":"mrs_01_0573.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1038" + "p_code":"843", + "code":"1042" }, { "desc":"This section describes how to create a role on MRS Manager and authorize and manage Manager and components.Up to 1,000 roles can be created on MRS Manager.You have learne", @@ -9347,8 +9383,8 @@ "title":"Creating a Role", "uri":"mrs_01_0420.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1039" + "p_code":"1042", + "code":"1043" }, { "desc":"This section describes how to create user groups and specify their operation permissions on MRS Manager. Management of single or multiple users can be unified in the user", @@ -9356,8 +9392,8 @@ "title":"Creating a User Group", "uri":"mrs_01_0421.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1040" + "p_code":"1042", + "code":"1044" }, { "desc":"This section describes how to create users on MRS Manager based on site requirements and specify their operation permissions to meet service requirements.Up to 1,000 user", @@ -9365,8 +9401,8 @@ "title":"Creating a User", "uri":"mrs_01_0422.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1041" + "p_code":"1042", + "code":"1045" }, { "desc":"This section describes how to modify user information on MRS Manager, including information about the user group, primary group, role, and description.If you change user ", @@ -9374,8 +9410,8 @@ "title":"Modifying User Information", "uri":"mrs_01_0423.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1042" + "p_code":"1042", + "code":"1046" }, { "desc":"This section describes how to lock users in MRS clusters. A locked user cannot log in to MRS Manager or perform security authentication in the cluster.A locked user can b", @@ -9383,8 +9419,8 @@ "title":"Locking a User", "uri":"mrs_01_0424.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1043" + "p_code":"1042", + "code":"1047" }, { "desc":"If a user is locked because the number of login attempts exceeds the value of Number of Password Retries, or the user is manually locked by the administrator, the adminis", @@ -9392,8 +9428,8 @@ "title":"Unlocking a User", "uri":"mrs_01_0425.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1044" + "p_code":"1042", + "code":"1048" }, { "desc":"If an MRS cluster user is not required, the administrator can delete the user on MRS Manager.", @@ -9401,8 +9437,8 @@ "title":"Deleting a User", "uri":"mrs_01_0426.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1045" + "p_code":"1042", + "code":"1049" }, { "desc":"Passwords of Human-Machine system users must be regularly changed to ensure MRS cluster security. This section describes how to change your passwords on MRS Manager.If a ", @@ -9410,8 +9446,8 @@ "title":"Changing the Password of an Operation User", "uri":"mrs_01_0427.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1046" + "p_code":"1042", + "code":"1050" }, { "desc":"This section describes how to initialize a password on MRS Manager if a user forgets the password or the password of a public account needs to be changed regularly. After", @@ -9419,8 +9455,8 @@ "title":"Initializing the Password of a System User", "uri":"mrs_01_0428.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1047" + "p_code":"1042", + "code":"1051" }, { "desc":"When a user develops big data applications and runs them in an MRS cluster that supports Kerberos authentication, the user needs to prepare a user authentication file for", @@ -9428,8 +9464,8 @@ "title":"Downloading a User Authentication File", "uri":"mrs_01_0429.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1048" + "p_code":"1042", + "code":"1052" }, { "desc":"This section describes how to set password and user login security rules as well as user lock rules. Password policies set on MRS Manager take effect for Human-machine us", @@ -9437,8 +9473,8 @@ "title":"Modifying a Password Policy", "uri":"mrs_01_0430.html", "doc_type":"usermanual", - "p_code":"1038", - "code":"1049" + "p_code":"1042", + "code":"1053" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9446,8 +9482,8 @@ "title":"MRS Multi-User Permission Management", "uri":"mrs_01_0340.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1050" + "p_code":"843", + "code":"1054" }, { "desc":"MRS Cluster UsersIndicate the security accounts of Manager, including usernames and passwords. These accounts are used to access resources in MRS clusters. Each MRS clust", @@ -9455,8 +9491,8 @@ "title":"Users and Permissions of MRS Clusters", "uri":"mrs_01_0341.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1051" + "p_code":"1054", + "code":"1055" }, { "desc":"The MRS cluster provides the following three types of users. Users are advised to periodically change the passwords. It is not recommended to use the default passwords.Us", @@ -9464,8 +9500,8 @@ "title":"Default Users of Clusters with Kerberos Authentication Enabled", "uri":"mrs_01_0342.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1052" + "p_code":"1054", + "code":"1056" }, { "desc":"This section describes how to create a role on Manager and authorize and manage Manager and components.Up to 1000 roles can be created on Manager.The operations described", @@ -9473,8 +9509,8 @@ "title":"Creating a Role", "uri":"mrs_01_0343.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1053" + "p_code":"1054", + "code":"1057" }, { "desc":"This section describes how to create user groups and specify their operation permissions on Manager. Management of single or multiple users can be unified in the user gro", @@ -9482,8 +9518,8 @@ "title":"Creating a User Group", "uri":"mrs_01_0344.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1054" + "p_code":"1054", + "code":"1058" }, { "desc":"This section describes how to create users on Manager based on site requirements and specify their operation permissions to meet service requirements.Up to 1000 users can", @@ -9491,8 +9527,8 @@ "title":"Creating a User", "uri":"mrs_01_0345.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1055" + "p_code":"1054", + "code":"1059" }, { "desc":"This section describes how to modify user information on Manager, including information about the user group, primary group, role, and description.This operation is suppo", @@ -9500,8 +9536,8 @@ "title":"Modifying User Information", "uri":"mrs_01_0346.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1056" + "p_code":"1054", + "code":"1060" }, { "desc":"This section describes how to lock users in MRS clusters. A locked user cannot log in to Manager or perform security authentication in the cluster. This operation is supp", @@ -9509,8 +9545,8 @@ "title":"Locking a User", "uri":"mrs_01_0347.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1057" + "p_code":"1054", + "code":"1061" }, { "desc":"If a user is locked because the number of login attempts exceeds the value of Number of Password Retries, or the user is manually locked by the administrator, the adminis", @@ -9518,8 +9554,8 @@ "title":"Unlocking a User", "uri":"mrs_01_0348.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1058" + "p_code":"1054", + "code":"1062" }, { "desc":"The administrator can delete an MRS cluster user that is not required on MRS Manager. Deleting a user is allowed only in clusters with Kerberos authentication enabled or ", @@ -9527,8 +9563,8 @@ "title":"Deleting a User", "uri":"mrs_01_0349.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1059" + "p_code":"1054", + "code":"1063" }, { "desc":"Passwords of Human-machine system users must be regularly changed to ensure MRS cluster security. This section describes how to change passwords on MRS Manager.If a new p", @@ -9536,8 +9572,8 @@ "title":"Changing the Password of an Operation User", "uri":"mrs_01_0350.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1060" + "p_code":"1054", + "code":"1064" }, { "desc":"This section describes how to initialize a password on Manager if a user forgets the password or the password of a public account needs to be changed regularly. After pas", @@ -9545,8 +9581,8 @@ "title":"Initializing the Password of a System User", "uri":"mrs_01_0351.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1061" + "p_code":"1054", + "code":"1065" }, { "desc":"When a user develops big data applications and runs them in an MRS cluster that supports Kerberos authentication, the user needs to prepare a Machine-machine user authent", @@ -9554,8 +9590,8 @@ "title":"Downloading a User Authentication File", "uri":"mrs_01_0352.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1062" + "p_code":"1054", + "code":"1066" }, { "desc":"Because password policies are critical to the user management security, modify them based on service security requirements. Otherwise, security risks may be incurred.This", @@ -9563,8 +9599,8 @@ "title":"Modifying a Password Policy", "uri":"mrs_01_0353.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1063" + "p_code":"1054", + "code":"1067" }, { "desc":"If cluster A needs to access the resources of cluster B, the mutual trust relationship must be configured between these two clusters.If no trust relationship is configure", @@ -9572,8 +9608,8 @@ "title":"Configuring Cross-Cluster Mutual Trust Relationships", "uri":"mrs_01_0354.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1064" + "p_code":"1054", + "code":"1068" }, { "desc":"After cross-cluster mutual trust is configured, permission must be configured for users in the local cluster, so that the users can access the same resources in the peer ", @@ -9581,8 +9617,8 @@ "title":"Configuring Users to Access Resources of a Trusted Cluster", "uri":"mrs_01_0355.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1065" + "p_code":"1054", + "code":"1069" }, { "desc":"When fine-grained permission control is enabled, you can configure OBS access permissions to implement access control on directories in OBS file systems.This section appl", @@ -9590,8 +9626,8 @@ "title":"Configuring Fine-Grained Permissions for MRS Multi-User Access to OBS", "uri":"mrs_01_0632.html", "doc_type":"usermanual", - "p_code":"1050", - "code":"1066" + "p_code":"1054", + "code":"1070" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9599,8 +9635,8 @@ "title":"Patch Operation Guide", "uri":"mrs_01_0574.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1067" + "p_code":"843", + "code":"1071" }, { "desc":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", @@ -9608,17 +9644,17 @@ "title":"Patch Operation Guide for Versions Earlier than MRS 1.7.0", "uri":"mrs_01_0575.html", "doc_type":"usermanual", - "p_code":"1067", - "code":"1068" + "p_code":"1071", + "code":"1072" }, { "desc":"If you obtain patch information from the following sources, upgrade the patch according to actual requirements.You obtain information about the patch released by MRS from", "product_code":"mrs", - "title":"Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0", + "title":"from MRS 1.7.0 to MRS 2.1.0Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0Earlier Than MRS 3.x", "uri":"mrs_01_0576.html", "doc_type":"usermanual", - "p_code":"1067", - "code":"1069" + "p_code":"1071", + "code":"1073" }, { "desc":"The rolling patch function indicates that patches are installed or uninstalled for one or more services in a cluster by performing a rolling service restart (restarting s", @@ -9626,8 +9662,8 @@ "title":"Supporting Rolling Patches", "uri":"mrs_01_0577.html", "doc_type":"usermanual", - "p_code":"1067", - "code":"1070" + "p_code":"1071", + "code":"1074" }, { "desc":"If some hosts are isolated in a cluster, perform the following operations to restore patches for these isolated hosts after patch installation on other hosts in the clust", @@ -9635,8 +9671,8 @@ "title":"Restoring Patches for the Isolated Hosts", "uri":"mrs_01_0578.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1071" + "p_code":"843", + "code":"1075" }, { "desc":"After modifying the configuration items of a big data component, you need to restart the corresponding service to make new configurations take effect. If you use a normal", @@ -9644,8 +9680,8 @@ "title":"Rolling Restart", "uri":"mrs_01_0579.html", "doc_type":"usermanual", - "p_code":"839", - "code":"1072" + "p_code":"843", + "code":"1076" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9654,7 +9690,7 @@ "uri":"mrs_01_0528.html", "doc_type":"usermanual", "p_code":"", - "code":"1073" + "code":"1077" }, { "desc":"The Hadoop community version provides two authentication modes: Kerberos authentication (security mode) and Simple authentication (normal mode). When creating a cluster, ", @@ -9662,8 +9698,8 @@ "title":"Security Configuration Suggestions for Clusters with Kerberos Authentication Disabled", "uri":"mrs_01_0419.html", "doc_type":"usermanual", - "p_code":"1073", - "code":"1074" + "p_code":"1077", + "code":"1078" }, { "desc":"For clusters in security mode with Kerberos authentication enabled, security authentication is required during application development.Kerberos, is now used to a concept ", @@ -9671,8 +9707,8 @@ "title":"Security Authentication Principles and Mechanisms", "uri":"mrs_07_020001.html", "doc_type":"usermanual", - "p_code":"1073", - "code":"1075" + "p_code":"1077", + "code":"1079" }, { "desc":"Table 1 lists forbidden operations during the routine cluster operation and maintenance process.The following tables list the high-risk operations during the operation an", @@ -9681,7 +9717,7 @@ "uri":"mrs_01_0785.html", "doc_type":"usermanual", "p_code":"", - "code":"1076" + "code":"1080" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9690,7 +9726,7 @@ "uri":"mrs_01_0316.html", "doc_type":"usermanual", "p_code":"", - "code":"1077" + "code":"1081" }, { "desc":"This section describes how to back up and restore data on the MRS console.Backup and restoration operations on the console apply only to clusters of MRS 3.x or earlier.Ba", @@ -9698,8 +9734,8 @@ "title":"Before You Start", "uri":"mrs_01_0605.html", "doc_type":"usermanual", - "p_code":"1077", - "code":"1078" + "p_code":"1081", + "code":"1082" }, { "desc":"MRS provides backup and restoration for user data and system data. The backup function is provided based on components to back up Manager data (including OMS data and Lda", @@ -9707,8 +9743,8 @@ "title":"Introduction", "uri":"mrs_01_0317.html", "doc_type":"usermanual", - "p_code":"1077", - "code":"1079" + "p_code":"1081", + "code":"1083" }, { "desc":"To ensure metadata security or before and after a critical operation (such as scale-out/scale-in, patch installation, upgrade, or migration) on the metadata, you need to ", @@ -9716,8 +9752,8 @@ "title":"Backing Up Metadata", "uri":"mrs_01_0319.html", "doc_type":"usermanual", - "p_code":"1077", - "code":"1080" + "p_code":"1081", + "code":"1084" }, { "desc":"Metadata needs to be recovered in the following scenarios:Data is modified or deleted unexpectedly and needs to be restored.After a critical operation (such as an upgrade", @@ -9725,8 +9761,8 @@ "title":"Restoring Metadata", "uri":"mrs_01_0321.html", "doc_type":"usermanual", - "p_code":"1077", - "code":"1081" + "p_code":"1081", + "code":"1085" }, { "desc":"You can modify the parameters of a created backup task on MRS to meet changing service requirements. The parameters of restoration tasks can only be viewed but cannot be ", @@ -9734,8 +9770,8 @@ "title":"Modifying Backup Tasks", "uri":"mrs_01_0324.html", "doc_type":"usermanual", - "p_code":"1077", - "code":"1082" + "p_code":"1081", + "code":"1086" }, { "desc":"You can view created backup and restoration tasks and check their running status on the MRS console.You have synchronized IAM users. (On the Dashboard page, click Synchro", @@ -9743,8 +9779,8 @@ "title":"Viewing Backup and Restoration Tasks", "uri":"mrs_01_0325.html", "doc_type":"usermanual", - "p_code":"1077", - "code":"1083" + "p_code":"1081", + "code":"1087" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9753,7 +9789,7 @@ "uri":"mrs_01_0444.html", "doc_type":"usermanual", "p_code":"", - "code":"1084" + "code":"1088" }, { "desc":"If the source cluster and destination cluster are deployed in different VPCs in the same region, create a network connection between the two VPCs to establish a data tran", @@ -9761,8 +9797,8 @@ "title":"HDFS Data", "uri":"mrs_01_0445.html", "doc_type":"usermanual", - "p_code":"1084", - "code":"1085" + "p_code":"1088", + "code":"1089" }, { "desc":"Hive table data is stored in HDFS. Table data and the metadata of the table data is centrally migrated in directories by HDFS in a unified manner. Metadata of Hive tables", @@ -9770,8 +9806,8 @@ "title":"Hive Metadata", "uri":"mrs_01_0446.html", "doc_type":"usermanual", - "p_code":"1084", - "code":"1086" + "p_code":"1088", + "code":"1090" }, { "desc":"Hive data is not backed up independently. For details, see HDFS Data.", @@ -9779,8 +9815,8 @@ "title":"Hive Data", "uri":"mrs_01_0447.html", "doc_type":"usermanual", - "p_code":"1084", - "code":"1087" + "p_code":"1088", + "code":"1091" }, { "desc":"Currently, HBase data can be backed up in the following modes:SnapshotsReplicationExportCopyTableHTable APIOffline backup of HDFS dataTable 1 compares the impact of opera", @@ -9788,8 +9824,8 @@ "title":"HBase Data", "uri":"mrs_01_0448.html", "doc_type":"usermanual", - "p_code":"1084", - "code":"1088" + "p_code":"1088", + "code":"1092" }, { "desc":"MirrorMaker is a powerful tool for Kafka data synchronization. It is used when data needs to be synchronized between two Kafka clusters or when data in the original Kafka", @@ -9797,8 +9833,8 @@ "title":"Kafka Data", "uri":"mrs_01_0449.html", "doc_type":"usermanual", - "p_code":"1084", - "code":"1089" + "p_code":"1088", + "code":"1093" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9807,7 +9843,7 @@ "uri":"mrs_01_9002.html", "doc_type":"usermanual", "p_code":"", - "code":"1090" + "code":"1094" }, { "desc":"Custers of versions earlier than MRS 3.x use MRS Manager to manage and monitor MRS clusters. On the Cluster Management page of the MRS management console, you can view cl", @@ -9815,8 +9851,8 @@ "title":"Precautions for MRS 3.x", "uri":"mrs_01_0614.html", "doc_type":"usermanual", - "p_code":"1090", - "code":"1091" + "p_code":"1094", + "code":"1095" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9824,8 +9860,8 @@ "title":"Installing the Flume Client", "uri":"mrs_01_0392.html", "doc_type":"cmpntguide", - "p_code":"1090", - "code":"1092" + "p_code":"1094", + "code":"1096" }, { "desc":"To use Flume to collect logs, you must install the Flume client on a log host. You can create an ECS and install the Flume client on it.This section applies to MRS 3.x or", @@ -9833,8 +9869,8 @@ "title":"Installing the Flume Client on Clusters of Versions Earlier Than MRS 3.x", "uri":"mrs_01_1594.html", "doc_type":"cmpntguide", - "p_code":"1092", - "code":"1093" + "p_code":"1096", + "code":"1097" }, { "desc":"To use Flume to collect logs, you must install the Flume client on a log host. You can create an ECS and install the Flume client on it.This section applies to MRS 3.x or", @@ -9842,8 +9878,8 @@ "title":"Installing the Flume Client on MRS 3.x or Later Clusters", "uri":"mrs_01_1595.html", "doc_type":"cmpntguide", - "p_code":"1092", - "code":"1094" + "p_code":"1096", + "code":"1098" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9852,7 +9888,7 @@ "uri":"en-us_topic_0000001349287889.html", "doc_type":"usermanual", "p_code":"", - "code":"1095" + "code":"1099" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -9860,8 +9896,8 @@ "title":"MRS Overview", "uri":"mrs_03_0002.html", "doc_type":"faq", - "p_code":"1095", - "code":"1096" + "p_code":"1099", + "code":"1100" }, { "desc":"MapReduce Service (MRS) is an enterprise-grade big data platform that allows you to quickly build and operate economical, secure, full-stack, cloud-native big data enviro", @@ -9869,8 +9905,8 @@ "title":"What Is MRS Used For?", "uri":"mrs_03_0001.html", "doc_type":"faq", - "p_code":"1096", - "code":"1097" + "p_code":"1100", + "code":"1101" }, { "desc":"MRS supports Hadoop 3.1.x and will soon support other mainstream Hadoop versions released by the community. Table 1 lists the component versions supported by MRS.", @@ -9878,8 +9914,8 @@ "title":"What Types of Distributed Storage Does MRS Support?", "uri":"mrs_03_1005.html", "doc_type":"faq", - "p_code":"1096", - "code":"1098" + "p_code":"1100", + "code":"1102" }, { "desc":"If you want to use a self-defined security group when buying a cluster, you need to enable port 9022 or select Auto create in Security Group on the MRS console.", @@ -9887,8 +9923,8 @@ "title":"How Do I Create an MRS Cluster Using a Custom Security Group?", "uri":"mrs_03_1012.html", "doc_type":"faq", - "p_code":"1096", - "code":"1099" + "p_code":"1100", + "code":"1103" }, { "desc":"MapReduce Service (MRS) is a service you can use to deploy and manage Hadoop-based components on the Cloud. It enables you to deploy Hadoop clusters with a few clicks. MR", @@ -9896,8 +9932,8 @@ "title":"How Do I Use MRS?", "uri":"mrs_03_1013.html", "doc_type":"faq", - "p_code":"1096", - "code":"1100" + "p_code":"1100", + "code":"1104" }, { "desc":"Phoenix does not support connection pool configuration. You are advised to write code to implement a tool class for managing connections and simulate a connection pool.", @@ -9905,8 +9941,8 @@ "title":"Can I Configure a Phoenix Connection Pool?", "uri":"mrs_03_1105.html", "doc_type":"faq", - "p_code":"1096", - "code":"1101" + "p_code":"1100", + "code":"1105" }, { "desc":"You can change the network segment. On the cluster Dashboard page of MRS console, click Change Subnet to the right of Default Subnet, and select a subnet in the VPC of th", @@ -9914,8 +9950,8 @@ "title":"Does MRS Support Change of the Network Segment?", "uri":"mrs_03_1019.html", "doc_type":"faq", - "p_code":"1096", - "code":"1102" + "p_code":"1100", + "code":"1106" }, { "desc":"You cannot downgrade the specifications of an MRS cluster node by using the console. If you want to downgrade an MRS cluster node's specifications, contact technical supp", @@ -9923,8 +9959,8 @@ "title":"Can I Downgrade the Specifications of an MRS Cluster Node?", "uri":"mrs_03_1125.html", "doc_type":"faq", - "p_code":"1096", - "code":"1103" + "p_code":"1100", + "code":"1107" }, { "desc":"Hive and HDFSHive is an Apache Hadoop project. Hive uses Hadoop Distributed File System (HDFS) as its file storage system. Hive parses and processes structured data store", @@ -9932,8 +9968,8 @@ "title":"What Is the Relationship Between Hive and Other Components?", "uri":"mrs_03_1046.html", "doc_type":"faq", - "p_code":"1096", - "code":"1104" + "p_code":"1100", + "code":"1108" }, { "desc":"Clusters of MRS 1.9.x support Hive on Spark.Clusters of MRS 3.x or later support Hive on Spark.You can use Hive on Tez for the clusters of other versions.", @@ -9941,8 +9977,8 @@ "title":"Does an MRS Cluster Support Hive on Spark?", "uri":"mrs_03_1048.html", "doc_type":"faq", - "p_code":"1096", - "code":"1105" + "p_code":"1100", + "code":"1109" }, { "desc":"Hive 3.1 has the following differences when compared with Hive 1.2:String cannot be converted to int.The user-defined functions (UDFs) of the Date type are changed to Hiv", @@ -9950,8 +9986,8 @@ "title":"What Are the Differences Between Hive Versions?", "uri":"mrs_03_1081.html", "doc_type":"faq", - "p_code":"1096", - "code":"1106" + "p_code":"1100", + "code":"1110" }, { "desc":"MRS cluster 2.0.5 or later supports Hive connections on DataLake Governance Center (DGC) and provides the IAM user synchronization function.", @@ -9959,8 +9995,8 @@ "title":"Which MRS Cluster Version Supports Hive Connection and User Synchronization?", "uri":"mrs_03_1095.html", "doc_type":"faq", - "p_code":"1096", - "code":"1107" + "p_code":"1100", + "code":"1111" }, { "desc":"The data processed by MRS is from OBS or HDFS. OBS is an object-based storage service that provides secure, reliable, and cost-effective storage of huge amounts of data. ", @@ -9968,8 +10004,8 @@ "title":"What Are the Differences Between OBS and HDFS in Data Storage?", "uri":"mrs_03_1062.html", "doc_type":"faq", - "p_code":"1096", - "code":"1108" + "p_code":"1100", + "code":"1112" }, { "desc":"Download it from https://github.com/Intel-bigdata/HiBench.", @@ -9977,8 +10013,8 @@ "title":"How Do I Obtain the Hadoop Pressure Test Tool?", "uri":"mrs_03_1092.html", "doc_type":"faq", - "p_code":"1096", - "code":"1109" + "p_code":"1100", + "code":"1113" }, { "desc":"Impala and HDFSImpala uses HDFS as its file storage system. Impala parses and processes structured data, while HDFS provides reliable underlying storage. Impala provides ", @@ -9986,8 +10022,8 @@ "title":"What Is the Relationship Between Impala and Other Components?", "uri":"mrs_03_1065.html", "doc_type":"faq", - "p_code":"1096", - "code":"1110" + "p_code":"1100", + "code":"1114" }, { "desc":"The open-source third-party packages on which the open-source components integrated by MRS depend contain SDK usage examples. Public IP addresses such as 12.1.2.3, 54.123", @@ -9995,8 +10031,8 @@ "title":"Statement About the Public IP Addresses in the Open-Source Third-Party SDK Integrated by MRS", "uri":"mrs_03_2022.html", "doc_type":"faq", - "p_code":"1096", - "code":"1111" + "p_code":"1100", + "code":"1115" }, { "desc":"Kudu is designed based on the HBase structure and can implement fast random read/write and update functions that HBase is good at. Kudu and HBase are similar in architect", @@ -10004,8 +10040,8 @@ "title":"What Is the Relationship Between Kudu and HBase?", "uri":"mrs_03_1066.html", "doc_type":"faq", - "p_code":"1096", - "code":"1112" + "p_code":"1100", + "code":"1116" }, { "desc":"MRS does not support Hive on Kudu.Currently, MRS supports only the following two methods to access Kudu:Access Kudu through Impala tables.Access and operate Kudu tables u", @@ -10013,8 +10049,8 @@ "title":"Does MRS Support Running Hive on Kudu?", "uri":"mrs_03_1068.html", "doc_type":"faq", - "p_code":"1096", - "code":"1113" + "p_code":"1100", + "code":"1117" }, { "desc":"GaussDB (for MySQL) is recommended for scenarios, such as data updates, online transaction processing (OLTP), and complex analysis of 1 billion data records.Impala and Ku", @@ -10022,8 +10058,8 @@ "title":"What Are the Solutions for processing 1 Billion Data Records?", "uri":"mrs_03_1133.html", "doc_type":"faq", - "p_code":"1096", - "code":"1114" + "p_code":"1100", + "code":"1118" }, { "desc":"MRS does not support the change of the DBService IP address.", @@ -10031,8 +10067,8 @@ "title":"Can I Change the IP address of DBService?", "uri":"mrs_03_1137.html", "doc_type":"faq", - "p_code":"1096", - "code":"1115" + "p_code":"1100", + "code":"1119" }, { "desc":"MRS sudo log files record operations performed by user omm and are helpful for fault locating. You can delete the logs of the earliest date to release storage space.If th", @@ -10040,8 +10076,8 @@ "title":"Can I Clear MRS sudo Logs?", "uri":"mrs_03_1155.html", "doc_type":"faq", - "p_code":"1096", - "code":"1116" + "p_code":"1100", + "code":"1120" }, { "desc":"In MRS cluster 2.1.0, the Storm log cannot exceed 20 GB. If the Storm log exceeds 20 GB, the log files will be deleted cyclically. Logs are stored on the system disk, the", @@ -10049,8 +10085,8 @@ "title":"Is the Storm Log also limited to 20 GB in MRS cluster 2.1.0?", "uri":"en-us_topic_0000001442653893.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1117" + "p_code":"1100", + "code":"1121" }, { "desc":"ThriftServer is a JDBC API. You can use JDBC to connect to ThriftServer to access SparkSQL data. Therefore, you can see JDBCServer in Spark components, but not ThriftServ", @@ -10058,8 +10094,8 @@ "title":"What Is Spark ThriftServer?", "uri":"en-us_topic_0000001442773925.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1118" + "p_code":"1100", + "code":"1122" }, { "desc":"Kafka supports PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL.", @@ -10067,8 +10103,8 @@ "title":"What Access Protocols Are Supported by Kafka?", "uri":"en-us_topic_0000001442494337.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1119" + "p_code":"1100", + "code":"1123" }, { "desc":"Zstandard (zstd) is an open-source fast lossless compression algorithm. The compression ratio of zstd is twice that of orc. For details, see https://github.com/L-Angel/co", @@ -10076,26 +10112,26 @@ "title":"What Is the Compression Ratio of zstd?", "uri":"en-us_topic_0000001392255170.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1120" + "p_code":"1100", + "code":"1124" }, { "desc":"The HDFS, YARN, and MapReduce components are integrated in Hadoop. If the three components are unavailable when are MRS cluster is created, select Hadoop instead. After a", "product_code":"mrs", - "title":"Why Are the HDFS, YARN, and MapReduce Components Unavailable When an MRS Cluster Is Created?", + "title":"CreatedWhy Are the HDFS, YARN, and MapReduce Components Unavailable When an MRS Cluster Is BoughtCreated?", "uri":"mrs_03_1202.html", "doc_type":"faq", - "p_code":"1096", - "code":"1121" + "p_code":"1100", + "code":"1125" }, { "desc":"If you create a cluster of a version earlier than MRS 3.x, ZooKeeper is installed by default and is not displayed on the GUI.If you create a cluster of MRS 3.x or later, ", "product_code":"mrs", - "title":"Why Is the ZooKeeper Component Unavailable When an MRS Cluster Is Created?", + "title":"CreatedWhy Is the ZooKeeper Component Unavailable When an MRS Cluster Is BoughtCreated?", "uri":"mrs_03_1204.html", "doc_type":"faq", - "p_code":"1096", - "code":"1122" + "p_code":"1100", + "code":"1126" }, { "desc":"For MRS 3.1.0 clusters, Python 2.7 or 3.x is recommended for Spark tasks.", @@ -10103,8 +10139,8 @@ "title":"Which Python Versions Are Supported by Spark Tasks in an MRS 3.1.0 Cluster?", "uri":"mrs_03_1216.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1123" + "p_code":"1100", + "code":"1127" }, { "desc":"Create a tenant on Manager.Roles, computing resources, and storage resources are automatically created when tenants are created.The new role has permissions on the comput", @@ -10112,17 +10148,17 @@ "title":"How Do I Enable Different Service Programs to Use Different YARN Queues?", "uri":"mrs_03_1221.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1124" + "p_code":"1100", + "code":"1128" }, { - "desc":"You can access Manager from the MRS management console.Manager is classified as MRS Manager and FusionInsight Manager.MRS Manager is the manager page of MRS 2.x or earlie", + "desc":"You can access Manager from the MRS management console.The following table lists the differences and relationships between the management console and MRS Manager.", "product_code":"mrs", "title":"Differences and Relationships Between the MRS Management Console and Cluster Manager", "uri":"mrs_03_1233.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1125" + "p_code":"1100", + "code":"1129" }, { "desc":"After an EIP is bound on the console, the EIP cannot be unbound in the EIP module of the VPC service.A dialog box is displayed, indicating that the operation cannot be pe", @@ -10130,8 +10166,8 @@ "title":"How Do I Unbind an EIP from an MRS Cluster Node?", "uri":"mrs_03_1246.html", "doc_type":"usermanual", - "p_code":"1096", - "code":"1126" + "p_code":"1100", + "code":"1130" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10139,8 +10175,8 @@ "title":"Account and Password", "uri":"mrs_03_2003.html", "doc_type":"faq", - "p_code":"1095", - "code":"1127" + "p_code":"1099", + "code":"1131" }, { "desc":"The default account for logging in to Manager is admin, and the password is the one you set when you created the cluster.", @@ -10148,8 +10184,8 @@ "title":"What Is the Account for Logging In to Manager?", "uri":"mrs_03_1027.html", "doc_type":"faq", - "p_code":"1127", - "code":"1128" + "p_code":"1131", + "code":"1132" }, { "desc":"Querying the password validity period of a component running user (human-machine user or machine-machine user):cd /opt/Bigdata/clientsource bigdata_envkadmin -p kadmin/ad", @@ -10157,8 +10193,8 @@ "title":"How Do I Query and Change the Password Validity Period of an Account?", "uri":"mrs_03_1249.html", "doc_type":"usermanual", - "p_code":"1127", - "code":"1129" + "p_code":"1131", + "code":"1133" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10166,17 +10202,17 @@ "title":"Accounts and Permissions", "uri":"mrs_03_2004.html", "doc_type":"faq", - "p_code":"1095", - "code":"1130" + "p_code":"1099", + "code":"1134" }, { - "desc":"For MRS cluster 2.1.0 or earlier, choose System > Configuration > Permission on MRS Manager.For MRS cluster 3.x or later, choose System > Permission on FusionInsight Mana", + "desc":"For MRS cluster 2.1.0 or earlier, choose System > Configuration > Permission on MRS Manager.For MRS cluster 3.x or later, choose System > Permission on MRS Manager.", "product_code":"mrs", "title":"Does an MRS Cluster Support Access Permission Control If Kerberos Authentication Is not Enabled?", "uri":"mrs_03_1020.html", "doc_type":"faq", - "p_code":"1130", - "code":"1131" + "p_code":"1134", + "code":"1135" }, { "desc":"You can assign tenant management permission only in analysis or hybrid clusters, but not in streaming clusters.The operations vary depending on the MRS cluster version:Pr", @@ -10184,8 +10220,8 @@ "title":"How Do I Assign Tenant Management Permission to a New Account?", "uri":"mrs_03_1035.html", "doc_type":"faq", - "p_code":"1130", - "code":"1132" + "p_code":"1134", + "code":"1136" }, { "desc":"On the IAM console, choose Permissions in the navigation pane, and click Create Custom Policy.Set a policy name in Policy Name.Set Scope to Project-level service for MRS.", @@ -10193,8 +10229,8 @@ "title":"How Do I Customize an MRS Policy?", "uri":"mrs_03_1118.html", "doc_type":"faq", - "p_code":"1130", - "code":"1133" + "p_code":"1134", + "code":"1137" }, { "desc":"Check whether you have the Manager_administrator permission. If you do not have this permission, Manage User will not be available on the System page of MRS Manager.", @@ -10202,8 +10238,8 @@ "title":"Why Is the Manage User Function Unavailable on the System Page on MRS Manager?", "uri":"mrs_03_1037.html", "doc_type":"faq", - "p_code":"1130", - "code":"1134" + "p_code":"1134", + "code":"1138" }, { "desc":"Hue does not provide an entry for configuring account permissions on its web UI. However, you can configure user roles and user groups for Hue accounts on the System tab ", @@ -10211,8 +10247,8 @@ "title":"Does Hue Support Account Permission Configuration?", "uri":"mrs_03_1121.html", "doc_type":"faq", - "p_code":"1130", - "code":"1135" + "p_code":"1134", + "code":"1139" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10220,8 +10256,8 @@ "title":"Client Usage", "uri":"mrs_03_2005.html", "doc_type":"faq", - "p_code":"1095", - "code":"1136" + "p_code":"1099", + "code":"1140" }, { "desc":"Log in to any Master node as user root.Run the su - omm command to switch to user omm.Run the cdclient installation directory command to switch to the client.Run the sour", @@ -10229,17 +10265,17 @@ "title":"How Do I Configure Environment Variables and Run Commands on a Component Client?", "uri":"mrs_03_1031.html", "doc_type":"faq", - "p_code":"1136", - "code":"1137" + "p_code":"1140", + "code":"1141" }, { - "desc":"Log in to FusionInsight Manager, choose Cluster > Services > ZooKeeper, click the Configurations tab and then All Configurations. In the navigation pane on the left, choo", + "desc":"Log in to MRS Manager, choose Cluster > Services > ZooKeeper, click the Configurations tab and then All Configurations. In the navigation pane on the left, choose quorump", "product_code":"mrs", "title":"How Do I Disable ZooKeeper SASL Authentication?", "uri":"mrs_03_1219.html", "doc_type":"usermanual", - "p_code":"1136", - "code":"1138" + "p_code":"1140", + "code":"1142" }, { "desc":"After the client is installed on a node outside an MRS cluster and the kinit command is executed, the following error information is displayed:The following error informa", @@ -10247,8 +10283,8 @@ "title":"An Error Is Reported When the kinit Command Is Executed on a Client Node Outside an MRS Cluster", "uri":"mrs_03_1251.html", "doc_type":"usermanual", - "p_code":"1136", - "code":"1139" + "p_code":"1140", + "code":"1143" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10256,8 +10292,8 @@ "title":"Web Page Access", "uri":"mrs_03_2006.html", "doc_type":"faq", - "p_code":"1095", - "code":"1140" + "p_code":"1099", + "code":"1144" }, { "desc":"You need to set a proper web session timeout duration for security purposes. To change the session timeout duration, do as follows:For MRS cluster versions earlier than 3", @@ -10265,8 +10301,8 @@ "title":"How Do I Change the Session Timeout Duration for an Open Source Component Web UI?", "uri":"mrs_03_1151.html", "doc_type":"faq", - "p_code":"1140", - "code":"1141" + "p_code":"1144", + "code":"1145" }, { "desc":"You can run the ps -ef |grep aos command to check whether the AOS process restarts successfully. If the process exists, the restart is successful and the Dynamic Resource", @@ -10274,8 +10310,8 @@ "title":"Why Cannot I Refresh the Dynamic Resource Plan Page on MRS Tenant Tab?", "uri":"mrs_03_1156.html", "doc_type":"faq", - "p_code":"1140", - "code":"1142" + "p_code":"1144", + "code":"1146" }, { "desc":"sh /opt/Bigdata/apache-tomcat-7.0.78/bin/shutdown.sh", @@ -10283,8 +10319,8 @@ "title":"What Do I Do If the Kafka Topic Monitoring Tab Is Unavailable on Manager?", "uri":"mrs_03_1166.html", "doc_type":"faq", - "p_code":"1140", - "code":"1143" + "p_code":"1144", + "code":"1147" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10292,8 +10328,8 @@ "title":"Alarm Monitoring", "uri":"mrs_03_2007.html", "doc_type":"faq", - "p_code":"1095", - "code":"1144" + "p_code":"1099", + "code":"1148" }, { "desc":"The Kafka topic monitoring function cannot send alarms by email or SMS message. However, you can view alarm information on Manager.", @@ -10301,26 +10337,26 @@ "title":"In an MRS Streaming Cluster, Can the Kafka Topic Monitoring Function Send Alarm Notifications?", "uri":"mrs_03_1055.html", "doc_type":"faq", - "p_code":"1144", - "code":"1145" + "p_code":"1148", + "code":"1149" }, { - "desc":"Log in to FusionInsight Manager and choose Cluster > Services > Yarn. In the navigation pane on the left, choose ResourceManager(Active) and log in to the native Yarn pag", + "desc":"Log in to MRS Manager and choose Cluster > Services > Yarn. In the navigation pane on the left, choose ResourceManager(Active) and log in to the native Yarn page.For deta", "product_code":"mrs", "title":"Where Can I View the Running Resource Queues When the Alarm \"ALM-18022 Insufficient Yarn Queue Resources\" Is Reported?", "uri":"mrs_03_1222.html", "doc_type":"usermanual", - "p_code":"1144", - "code":"1146" + "p_code":"1148", + "code":"1150" }, { - "desc":"The following uses the Operation Requests on RegionServers monitoring item as an example:Log in to FusionInsight Manager and choose Cluster > Services > HBase > Resource.", + "desc":"The following uses the Operation Requests on RegionServers monitoring item as an example:Log in to MRS Manager and choose Cluster > Services > HBase > Resource. On the di", "product_code":"mrs", "title":"How Do I Understand the Multi-Level Chart Statistics in the HBase Operation Requests Metric?", "uri":"mrs_03_1243.html", "doc_type":"usermanual", - "p_code":"1144", - "code":"1147" + "p_code":"1148", + "code":"1151" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10328,8 +10364,8 @@ "title":"Performance Tuning", "uri":"mrs_03_2008.html", "doc_type":"faq", - "p_code":"1095", - "code":"1148" + "p_code":"1099", + "code":"1152" }, { "desc":"An MRS cluster does not support system reinstallation.", @@ -10337,8 +10373,8 @@ "title":"Does an MRS Cluster Support System Reinstallation?", "uri":"mrs_03_1017.html", "doc_type":"faq", - "p_code":"1148", - "code":"1149" + "p_code":"1152", + "code":"1153" }, { "desc":"The OS of an MRS cluster cannot be changed.", @@ -10346,17 +10382,17 @@ "title":"Can I Change the OS of an MRS Cluster?", "uri":"mrs_03_1203.html", "doc_type":"faq", - "p_code":"1148", - "code":"1150" + "p_code":"1152", + "code":"1154" }, { - "desc":"Go to the Yarn service configuration page.For versions earlier than 1.9.2, log in to MRS Manager, choose Services > Yarn > Service Configuration, and select All from the ", + "desc":"Go to the Yarn service configuration page.For versions earlier than 1.9.2,log in to MRS Manager, choose Services > Yarn > Service Configuration, and select All from the B", "product_code":"mrs", "title":"How Do I Improve the Resource Utilization of Core Nodes in a Cluster?", "uri":"mrs_03_1090.html", "doc_type":"faq", - "p_code":"1148", - "code":"1151" + "p_code":"1152", + "code":"1155" }, { "desc":"For example, to check the firewall status on EulerOS, run the systemctl status firewalld.service command.For example, to stop the firewall service on EulerOS, run the sys", @@ -10364,8 +10400,8 @@ "title":"How Do I Stop the Firewall Service?", "uri":"mrs_03_1072.html", "doc_type":"faq", - "p_code":"1148", - "code":"1152" + "p_code":"1152", + "code":"1156" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10373,8 +10409,8 @@ "title":"Job Development", "uri":"mrs_03_2009.html", "doc_type":"faq", - "p_code":"1095", - "code":"1153" + "p_code":"1099", + "code":"1157" }, { "desc":"MRS can process data in OBS and HDFS. You can get your data into OBS or HDFS as follows:Upload local data to OBS.Log in to the OBS console.Create a parallel file system n", @@ -10382,8 +10418,8 @@ "title":"How Do I Get My Data into OBS or HDFS?", "uri":"mrs_03_1015.html", "doc_type":"faq", - "p_code":"1153", - "code":"1154" + "p_code":"1157", + "code":"1158" }, { "desc":"MRS clusters support Spark jobs submitted in Spark, Spark Script, or Spark SQL mode.", @@ -10391,8 +10427,8 @@ "title":"What Types of Spark Jobs Can Be Submitted in a Cluster?", "uri":"mrs_03_1050.html", "doc_type":"faq", - "p_code":"1153", - "code":"1155" + "p_code":"1157", + "code":"1159" }, { "desc":"You can run only one Spark task at a time after the minimum tenant resources of an MRS cluster is changed to 0.", @@ -10400,8 +10436,8 @@ "title":"Can I Run Multiple Spark Tasks at the Same Time After the Minimum Tenant Resources of an MRS Cluster Is Changed to 0?", "uri":"mrs_03_1052.html", "doc_type":"faq", - "p_code":"1153", - "code":"1156" + "p_code":"1157", + "code":"1160" }, { "desc":"You need to understand the concept ApplicationMaster before understanding the essential differences between Yarn-client and Yarn-cluster.In Yarn, each application instanc", @@ -10409,8 +10445,8 @@ "title":"What Are the Differences Between the Client Mode and Cluster Mode of Spark Jobs?", "uri":"en-us_topic_0000001392574214.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1157" + "p_code":"1157", + "code":"1161" }, { "desc":"If IAM synchronization is not performed when a job is submitted in a security cluster, the error message \"The current user does not exist on MRS Manager. Grant the user s", @@ -10418,8 +10454,8 @@ "title":"How Do I Do If the Message \"The current user does not exist on MRS Manager. Grant the user sufficient permissions on IAM and then perform IAM user synchronization on the Dashboard tab page.\" Is Displayed?", "uri":"mrs_03_1173.html", "doc_type":"faq", - "p_code":"1153", - "code":"1158" + "p_code":"1157", + "code":"1162" }, { "desc":"The cause of the launcherJob failure is that the user who submits the job does not have the write permission on the hdfs /mrs/job-properties directory.This problem is fi", @@ -10427,8 +10463,8 @@ "title":"LauncherJob Job Execution Is Failed And the Error Message \"jobPropertiesMap is null.\" Is Displayed", "uri":"mrs_03_1174.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1159" + "p_code":"1157", + "code":"1163" }, { "desc":"To save storage space, the Yarn configuration item yarn.resourcemanager.max-completed-applications is modified to reduce the number of historical job records stored on Ya", @@ -10436,8 +10472,8 @@ "title":"How Do I Do If the Flink Job Status on the MRS Console Is Inconsistent with That on Yarn?", "uri":"mrs_03_1175.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1160" + "p_code":"1157", + "code":"1164" }, { "desc":"When a user submits a job that needs to read and write OBS, the job submission program adds the temporary access key (AK) and secret key (SK) for accessing OBS by default", @@ -10445,8 +10481,8 @@ "title":"How Do I Do If a SparkStreaming Job Fails After Being Executed Dozens of Hours and the OBS Access 403 Error is Reported?", "uri":"mrs_03_1176.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1161" + "p_code":"1157", + "code":"1165" }, { "desc":"The ClickHouse client restricts the memory used by GROUP BY statements. When a SQL statement is executed on the ClickHouse client, the following error information is disp", @@ -10454,8 +10490,8 @@ "title":"How Do I Do If an Alarm Is Reported Indicating that the Memory Is Insufficient When I Execute a SQL Statement on the ClickHouse Client?", "uri":"mrs_03_1201.html", "doc_type":"faq", - "p_code":"1153", - "code":"1162" + "p_code":"1157", + "code":"1166" }, { "desc":"The Spark job keeps running and error message \"java.io.IOException: Connection reset by peer\" is displayed.Add the executor.memory Overhead parameter to the parameters fo", @@ -10463,8 +10499,8 @@ "title":"How Do I Do If Error Message \"java.io.IOException: Connection reset by peer\" Is Displayed During the Execution of a Spark Job?", "uri":"mrs_03_1205.html", "doc_type":"faq", - "p_code":"1153", - "code":"1163" + "p_code":"1157", + "code":"1167" }, { "desc":"Error message \"requestId=4971883851071737250\" is displayed when a Spark job accesses OBS.Log in to the node where the Spark client is located, go to the conf directory, a", @@ -10472,8 +10508,8 @@ "title":"How Do I Do If Error Message \"requestId=4971883851071737250\" Is Displayed When a Spark Job Accesses OBS?", "uri":"mrs_03_1207.html", "doc_type":"faq", - "p_code":"1153", - "code":"1164" + "p_code":"1157", + "code":"1168" }, { "desc":"DataArtsStudio occasionally fails to schedule Spark jobs and the rescheduling also fails. The following error information is displayed:Log in to the node where the Spark ", @@ -10481,8 +10517,8 @@ "title":"Why DataArtsStudio Occasionally Fail to Schedule Spark Jobs and the Rescheduling also Fails?", "uri":"mrs_03_1208.html", "doc_type":"faq", - "p_code":"1153", - "code":"1165" + "p_code":"1157", + "code":"1169" }, { "desc":"A Flink job fails to be executed and the following error message is displayed:The third-party dependency package in the customer code conflicts with the cluster package. ", @@ -10490,8 +10526,8 @@ "title":"How Do I Do If a Flink Job Fails to Execute and the Error Message \"java.lang.NoSuchFieldError: SECURITY_SSL_ENCRYPT_ENABLED\" Is Displayed?", "uri":"mrs_03_1215.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1166" + "p_code":"1157", + "code":"1170" }, { "desc":"After a Yarn job is created, it cannot be viewed if you log in to the web UI as the admin user.The admin user is a user on the cluster management page. Check whether the ", @@ -10499,8 +10535,8 @@ "title":"Why Submitted Yarn Job Cannot Be Viewed on the Web UI?", "uri":"mrs_03_1223.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1167" + "p_code":"1157", + "code":"1171" }, { "desc":"You can modify or add the HDFS NameSpace (fs.defaultFS) of the cluster by modifying the core-site.xml and hdfs-site.xml files on the client. However, you are not advised ", @@ -10508,8 +10544,8 @@ "title":"How Do I Modify the HDFS NameSpace (fs.defaultFS) of an Existing Cluster?", "uri":"mrs_03_1224.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1168" + "p_code":"1157", + "code":"1172" }, { "desc":"The launcher-job queue is stopped by YARN when a Flink job is submitted on the management plane.Increase the heap size of the launcher-job queue.Log in to the active OMS ", @@ -10517,8 +10553,8 @@ "title":"How Do I Do If the launcher-job Queue Is Stopped by YARN due to Insufficient Heap Size When I Submit a Flink Job on the Management Plane?", "uri":"mrs_03_1229.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1169" + "p_code":"1157", + "code":"1173" }, { "desc":"When a Flink job is submitted, JobManager is started successfully. However, TaskManager remains in the starting state until timeout. The following error information is di", @@ -10526,8 +10562,8 @@ "title":"How Do I Do If the Error Message \"slot request timeout\" Is Displayed When I Submit a Flink Job?", "uri":"mrs_03_1237.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1170" + "p_code":"1157", + "code":"1174" }, { "desc":"Does a DistCP job compare data consistency during data import and export?No. DistCP jobs only copy data but do not modify it.No. DistCP jobs only copy data but do not mod", @@ -10535,8 +10571,8 @@ "title":"Data Import and Export of DistCP Jobs", "uri":"mrs_03_1238.html", "doc_type":"usermanual", - "p_code":"1153", - "code":"1171" + "p_code":"1157", + "code":"1175" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10544,8 +10580,8 @@ "title":"Cluster Upgrade/Patching", "uri":"mrs_03_2010.html", "doc_type":"faq", - "p_code":"1095", - "code":"1172" + "p_code":"1099", + "code":"1176" }, { "desc":"You cannot upgrade an MRS cluster. However, you can create a cluster of the target version and migrate data from the old cluster to the new cluster.", @@ -10553,8 +10589,8 @@ "title":"Can I Upgrade an MRS Cluster?", "uri":"mrs_03_1089.html", "doc_type":"usermanual", - "p_code":"1172", - "code":"1173" + "p_code":"1176", + "code":"1177" }, { "desc":"You cannot change the version of an MRS cluster. However, you can terminate the current cluster and create an MRS cluster of the version you require.", @@ -10562,8 +10598,8 @@ "title":"Can I Change the MRS Cluster Version?", "uri":"mrs_03_1021.html", "doc_type":"usermanual", - "p_code":"1172", - "code":"1174" + "p_code":"1176", + "code":"1178" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10571,8 +10607,8 @@ "title":"Cluster Access", "uri":"mrs_03_2013.html", "doc_type":"faq", - "p_code":"1095", - "code":"1175" + "p_code":"1099", + "code":"1179" }, { "desc":"No. You can select the login mode when creating the cluster. You cannot change the login mode after you created the cluster.", @@ -10580,17 +10616,17 @@ "title":"Can I Switch Between the Two Login Modes of MRS?", "uri":"mrs_03_1029.html", "doc_type":"usermanual", - "p_code":"1175", - "code":"1176" + "p_code":"1179", + "code":"1180" }, { - "desc":"You can obtain the IP address and port number of a ZooKeeper instance through the MRS console or FusionInsight Manager.Method 1: Obtaining the IP address and port number ", + "desc":"You can obtain the IP address and port number of a ZooKeeper instance through the MRS console or MRS Manager.Method 1: Obtaining the IP address and port number of a ZooKe", "product_code":"mrs", "title":"How Can I Obtain the IP Address and Port Number of a ZooKeeper Instance?", "uri":"mrs_03_1071.html", "doc_type":"faq", - "p_code":"1175", - "code":"1177" + "p_code":"1179", + "code":"1181" }, { "desc":"If you can log in to an existing node as the Linux user but fail to log in to the newly added node, log in to the newly added node as the root user.", @@ -10598,8 +10634,8 @@ "title":"How Do I Do If a New Node Cannot Be logged In to as a Linux User?", "uri":"mrs_03_1185.html", "doc_type":"faq", - "p_code":"1175", - "code":"1178" + "p_code":"1179", + "code":"1182" }, { "desc":"Set AZ, VPC, and Security Group of the ECS to the same values as those of the cluster to be accessed.On the Dashboard tab page, click Add Security Group Rule. In the Add ", @@ -10607,8 +10643,8 @@ "title":"How Do I Access an MRS Cluster from a Node Outside the Cluster?", "uri":"mrs_03_1234.html", "doc_type":"usermanual", - "p_code":"1175", - "code":"1179" + "p_code":"1179", + "code":"1183" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10616,8 +10652,8 @@ "title":"Big Data Service Development", "uri":"mrs_03_2014.html", "doc_type":"faq", - "p_code":"1095", - "code":"1180" + "p_code":"1099", + "code":"1184" }, { "desc":"The Flume client supports multiple independent data flows. You can configure and link multiple sources, channels, and sinks in the properties.properties configuration fil", @@ -10625,8 +10661,8 @@ "title":"Can MRS Run Multiple Flume Tasks at a Time?", "uri":"mrs_03_1059.html", "doc_type":"faq", - "p_code":"1180", - "code":"1181" + "p_code":"1184", + "code":"1185" }, { "desc":"Log in to the node where FlumeClient is running.Go to the FlumeClient installation directory. For example, if the FlumeClient installation directory is /opt/FlumeClient, ", @@ -10634,8 +10670,8 @@ "title":"How Do I Change FlumeClient Logs to Standard Logs?", "uri":"mrs_03_1058.html", "doc_type":"faq", - "p_code":"1180", - "code":"1182" + "p_code":"1184", + "code":"1186" }, { "desc":"hadoopstreaming.jar: /opt/share/hadoop-streaming-* (* indicates the Hadoop version.)JDK environment variables: /opt/client/JDK/component_envHadoop environment variables: ", @@ -10643,8 +10679,8 @@ "title":"Where Are the JAR Files and Environment Variables of Hadoop Stored?", "uri":"mrs_03_1064.html", "doc_type":"faq", - "p_code":"1180", - "code":"1183" + "p_code":"1184", + "code":"1187" }, { "desc":"HBase supports the Snappy, LZ4, and gzip compression algorithms.", @@ -10652,8 +10688,8 @@ "title":"What Compression Algorithms Does HBase Support?", "uri":"mrs_03_1042.html", "doc_type":"faq", - "p_code":"1180", - "code":"1184" + "p_code":"1184", + "code":"1188" }, { "desc":"No. Hive on HBase supports only data query.", @@ -10661,8 +10697,8 @@ "title":"Can MRS Write Data to HBase Through the HBase External Table of Hive?", "uri":"mrs_03_1044.html", "doc_type":"faq", - "p_code":"1180", - "code":"1185" + "p_code":"1184", + "code":"1189" }, { "desc":"Log in to the Master node in the cluster as user root.Run the su - omm command to switch to user omm.Run the cd /var/log/Bigdata/hbase/ command to go to the /var/log/Bigd", @@ -10670,8 +10706,8 @@ "title":"How Do I View HBase Logs?", "uri":"mrs_03_1045.html", "doc_type":"faq", - "p_code":"1180", - "code":"1186" + "p_code":"1184", + "code":"1190" }, { "desc":"Set the time to live (TTL) when creating a table:Create the t_task_log table, set the column family to f, and set the TTL to 86400 seconds.create 't_task_log',{NAME => 'f", @@ -10679,8 +10715,8 @@ "title":"How Do I Set the TTL for an HBase Table?", "uri":"mrs_03_1140.html", "doc_type":"faq", - "p_code":"1180", - "code":"1187" + "p_code":"1184", + "code":"1191" }, { "desc":"Log in to the master node of the cluster and run the corresponding command to configure environment variables. /opt/client indicates the client installation directory. Re", @@ -10688,8 +10724,8 @@ "title":"How Do I Balance HDFS Data?", "uri":"mrs_03_1113.html", "doc_type":"faq", - "p_code":"1180", - "code":"1188" + "p_code":"1184", + "code":"1192" }, { "desc":"Go to the HDFS service configuration page.For MRS cluster versions earlier than 1.9.2:Log in to MRS Manager, choose Services > HDFS > Service Configuration, and select Al", @@ -10697,8 +10733,8 @@ "title":"How Do I Change the Number of HDFS Replicas?", "uri":"mrs_03_1061.html", "doc_type":"faq", - "p_code":"1180", - "code":"1189" + "p_code":"1184", + "code":"1193" }, { "desc":"The default port of open source HDFS is 50070 for versions earlier than MRS 3.0.0, and 9870 for MRS 3.0.0 or later. Common HDFS Ports describes the common ports of HDFS.T", @@ -10706,8 +10742,8 @@ "title":"What Is the Port for Accessing HDFS Using Python?", "uri":"mrs_03_1060.html", "doc_type":"faq", - "p_code":"1180", - "code":"1190" + "p_code":"1184", + "code":"1194" }, { "desc":"If the org.apache.hadoop.hdfs.server.namenode.ha.AdaptiveFailoverProxyProvider class is unavailable when a cluster of MRS 3.x connects to NameNodes using HDFS, the cause ", @@ -10715,8 +10751,8 @@ "title":"How Do I Modify the HDFS Active/Standby Switchover Class?", "uri":"mrs_03_1196.html", "doc_type":"faq", - "p_code":"1180", - "code":"1191" + "p_code":"1184", + "code":"1195" }, { "desc":"smallint is recommended.", @@ -10724,8 +10760,8 @@ "title":"What Is the Recommended Number Type of DynamoDB in Hive Tables?", "uri":"mrs_03_1047.html", "doc_type":"faq", - "p_code":"1180", - "code":"1192" + "p_code":"1184", + "code":"1196" }, { "desc":"The Hive driver cannot be interconnected with the DBCP2 database connection pool. The DBCP2 database connection pool invokes the isValid method to check whether a connect", @@ -10733,8 +10769,8 @@ "title":"Can the Hive Driver Be Interconnected with DBCP2?", "uri":"mrs_03_1049.html", "doc_type":"faq", - "p_code":"1180", - "code":"1193" + "p_code":"1184", + "code":"1197" }, { "desc":"Versions earlier than MRS 3.x:Log in to MRS Manager and choose System > Permission > Manage Role.Click Create Role, and set Role Name and Description.In the Permission ta", @@ -10742,8 +10778,8 @@ "title":"How Do I View the Hive Table Created by Another User?", "uri":"mrs_03_1082.html", "doc_type":"faq", - "p_code":"1180", - "code":"1194" + "p_code":"1184", + "code":"1198" }, { "desc":"Run the following statement to export the query result of Hive data:", @@ -10751,17 +10787,17 @@ "title":"Can I Export the Query Result of Hive Data?", "uri":"mrs_03_1149.html", "doc_type":"faq", - "p_code":"1180", - "code":"1195" + "p_code":"1184", + "code":"1199" }, { "desc":"When Hive of MRS 3.x runs the beeline -e \" use default;show tables;\" command, the following error message is displayed: Error while compiling statement: FAILED: ParseExce", "product_code":"mrs", - "title":"How Do I Do If an Error Occurs When Hive Runs the beeline -e Command to Execute Multiple Statements?", + "title":"beeline -eHow Do I Do If an Error Occurs When Hive Runs the beeline -e Command to Execute Multiple Statements?", "uri":"mrs_03_1194.html", "doc_type":"faq", - "p_code":"1180", - "code":"1196" + "p_code":"1184", + "code":"1200" }, { "desc":"This issue occurs because the MRS CommonOperations permission bound to the user group to which the user who submits the job belongs does not include the Hive permission a", @@ -10769,8 +10805,8 @@ "title":"How Do I Do If a \"hivesql/hivescript\" Job Fails to Submit After Hive Is Added?", "uri":"mrs_03_1200.html", "doc_type":"faq", - "p_code":"1180", - "code":"1197" + "p_code":"1184", + "code":"1201" }, { "desc":"This section applies only to versions earlier than MRS 3.x.Log in to a Master node as user root and switch to user omm.su - ommsu - ommCheck whether the current node is t", @@ -10778,8 +10814,8 @@ "title":"What If an Excel File Downloaded on Hue Failed to Open?", "uri":"mrs_03_1160.html", "doc_type":"faq", - "p_code":"1180", - "code":"1198" + "p_code":"1184", + "code":"1202" }, { "desc":"Applicable versions: MRS 3.1.0 and earlierModify the following file on the two Hue nodes:/opt/Bigdata/FusionInsight_Porter_8.*/install/FusionInsight-Hue-*/hue/apps/beeswa", @@ -10787,8 +10823,8 @@ "title":"How Do I Do If Sessions Are Not Released After Hue Connects to HiveServer and the Error Message \"over max user connections\" Is Displayed?", "uri":"mrs_03_1214.html", "doc_type":"usermanual", - "p_code":"1180", - "code":"1199" + "p_code":"1184", + "code":"1203" }, { "desc":"You can reset Kafka data by deleting Kafka topics.Delete a topic: kafka-topics.sh --delete --zookeeperZooKeeper Cluster service IP address:2181/kafka --topic topicnameQue", @@ -10796,8 +10832,8 @@ "title":"How Do I Reset Kafka Data?", "uri":"mrs_03_1106.html", "doc_type":"faq", - "p_code":"1180", - "code":"1200" + "p_code":"1184", + "code":"1204" }, { "desc":"Run the --bootstrap-server command to query the information about the client.", @@ -10805,8 +10841,8 @@ "title":"How Do I Obtain the Client Version of MRS Kafka?", "uri":"mrs_03_1145.html", "doc_type":"faq", - "p_code":"1180", - "code":"1201" + "p_code":"1184", + "code":"1205" }, { "desc":"Kafka supports PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL.", @@ -10814,8 +10850,8 @@ "title":"What Access Protocols Are Supported by Kafka?", "uri":"mrs_03_1146.html", "doc_type":"faq", - "p_code":"1180", - "code":"1202" + "p_code":"1184", + "code":"1206" }, { "desc":"This issue is caused by the conflict between the Ranger authentication and ACL authentication of a cluster. If a Kafka cluster uses ACL for permission access control and ", @@ -10823,8 +10859,8 @@ "title":"How Do I Do If Error Message \"Not Authorized to access group xxx\" Is Displayed When a Kafka Topic Is Consumed?", "uri":"mrs_03_1197.html", "doc_type":"faq", - "p_code":"1180", - "code":"1203" + "p_code":"1184", + "code":"1207" }, { "desc":"Kudu supports Snappy, LZ4, and zlib. LZ4 is used by default.", @@ -10832,8 +10868,8 @@ "title":"What Compression Algorithms Does Kudu Support?", "uri":"mrs_03_1067.html", "doc_type":"faq", - "p_code":"1180", - "code":"1204" + "p_code":"1184", + "code":"1208" }, { "desc":"Log in to the Master node in the cluster.Run the su - omm command to switch to user omm.Run the cd /var/log/Bigdata/kudu/ command to go to the /var/log/Bigdata/kudu/ dire", @@ -10841,8 +10877,8 @@ "title":"How Do I View Kudu Logs?", "uri":"mrs_03_1069.html", "doc_type":"faq", - "p_code":"1180", - "code":"1205" + "p_code":"1184", + "code":"1209" }, { "desc":"Log in to the MRS console.Click the name of the cluster.On the page displayed, choose Components > Kudu > Instances and locate the IP address of the abnormal instance.If ", @@ -10850,8 +10886,8 @@ "title":"How Do I Handle the Kudu Service Exceptions Generated During Cluster Creation?", "uri":"mrs_03_1169.html", "doc_type":"faq", - "p_code":"1180", - "code":"1206" + "p_code":"1184", + "code":"1210" }, { "desc":"OpenTSDB supports Python APIs. OpenTSDB provides HTTP-based RESTful APIs that are language-independent. Any language that supports HTTP requests can interconnect to OpenT", @@ -10859,8 +10895,8 @@ "title":"Does OpenTSDB Support Python APIs?", "uri":"mrs_03_1070.html", "doc_type":"faq", - "p_code":"1180", - "code":"1207" + "p_code":"1184", + "code":"1211" }, { "desc":"In this section, MySQL is used as an example.For MRS 1.x and 3.x clusters, do the following:Log in to the MRS management console.Click the name of the cluster to go to it", @@ -10868,8 +10904,8 @@ "title":"How Do I Configure Other Data Sources on Presto?", "uri":"mrs_03_1147.html", "doc_type":"faq", - "p_code":"1180", - "code":"1208" + "p_code":"1184", + "code":"1212" }, { "desc":"Log in to the Master node in the cluster as user root.Run the following command to configure environment variables:source Client installation directory/bigdata_envsource ", @@ -10877,8 +10913,8 @@ "title":"How Do I Connect to Spark Shell from MRS?", "uri":"mrs_03_1157.html", "doc_type":"faq", - "p_code":"1180", - "code":"1209" + "p_code":"1184", + "code":"1213" }, { "desc":"Log in to the master node in the cluster as user root.Run the following command to configure environment variables:source Client installation directory/bigdata_envsource ", @@ -10886,8 +10922,8 @@ "title":"How Do I Connect to Spark Beeline from MRS?", "uri":"mrs_03_1158.html", "doc_type":"faq", - "p_code":"1180", - "code":"1210" + "p_code":"1184", + "code":"1214" }, { "desc":"Logs of unfinished Spark jobs are stored in the /srv/BigData/hadoop/data1/nm/containerlogs/ directory on the Core node.Logs of finished Spark jobs are stored in the /tmp/", @@ -10895,8 +10931,8 @@ "title":"Where Are the Execution Logs of Spark Jobs Stored?", "uri":"mrs_03_1159.html", "doc_type":"faq", - "p_code":"1180", - "code":"1211" + "p_code":"1184", + "code":"1215" }, { "desc":"You can modify the /opt/Bigdata/MRS_XXX/1_XX _Supervisor/etc/worker.xml file on the streaming Core node of MRS, set the value of filename to the path, and restart the cor", @@ -10904,8 +10940,8 @@ "title":"How Do I Specify a Log Path When Submitting a Task in an MRS Storm Cluster?", "uri":"mrs_03_1127.html", "doc_type":"faq", - "p_code":"1180", - "code":"1212" + "p_code":"1184", + "code":"1216" }, { "desc":"root-default is hidden on the Manager page.If the sum is 100, the configuration is correct.If the sum is not 100, the configuration is incorrect. Perform the following st", @@ -10913,8 +10949,8 @@ "title":"How Do I Check Whether the ResourceManager Configuration of Yarn Is Correct?", "uri":"mrs_03_1163.html", "doc_type":"faq", - "p_code":"1180", - "code":"1213" + "p_code":"1184", + "code":"1217" }, { "desc":"cd /opt/Client installation directorysourcebigdata_envkinit MRS cluster userThe user must have the ClickHouse administrator permissions.set allow_drop_detached=1;SELECT *", @@ -10922,8 +10958,8 @@ "title":"How Do I Modify the allow_drop_detached Parameter of ClickHouse?", "uri":"mrs_03_1210.html", "doc_type":"faq", - "p_code":"1180", - "code":"1214" + "p_code":"1184", + "code":"1218" }, { "desc":"When a Spark task is executed, an alarm indicating insufficient memory is reported. The alarm ID is 18022. As a result, no available memory can be used.Set the executor p", @@ -10931,8 +10967,8 @@ "title":"How Do I Do If an Alarm Indicating Insufficient Memory Is Reported During Spark Task Execution?", "uri":"mrs_03_1206.html", "doc_type":"faq", - "p_code":"1180", - "code":"1215" + "p_code":"1184", + "code":"1219" }, { "desc":"A user performs a large number of update operations using ClickHouse. This operation on a ClickHouse consumes a large number of resources. In addition, the operation will", @@ -10940,8 +10976,8 @@ "title":"How Do I Do If ClickHouse Consumes Excessive CPU Resources?", "uri":"mrs_03_1209.html", "doc_type":"faq", - "p_code":"1180", - "code":"1216" + "p_code":"1184", + "code":"1220" }, { "desc":"vim /opt/Bigdata/components/current/ClickHouse/configurations.xmlChange hidden to advanced, as shown in the following information in bold. Then save the configuration and", @@ -10949,8 +10985,8 @@ "title":"How Do I Enable the Map Type on ClickHouse?", "uri":"mrs_03_1217.html", "doc_type":"usermanual", - "p_code":"1180", - "code":"1217" + "p_code":"1184", + "code":"1221" }, { "desc":"When Spark SQL is used to access Hive partitioned tables stored in OBS, the acces speed is slow and a large number of OBS query APIs are called.Example SQL:According to t", @@ -10958,8 +10994,8 @@ "title":"A Large Number of OBS APIs Are Called When Spark SQL Accesses Hive Partitioned Tables", "uri":"mrs_03_1248.html", "doc_type":"usermanual", - "p_code":"1180", - "code":"1218" + "p_code":"1184", + "code":"1222" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10967,8 +11003,8 @@ "title":"API", "uri":"mrs_03_2015.html", "doc_type":"faq", - "p_code":"1095", - "code":"1219" + "p_code":"1099", + "code":"1223" }, { "desc":"When you use the API for adjusting cluster nodes, the value of node_id is fixed to node_orderadd.", @@ -10976,8 +11012,8 @@ "title":"How Do I Configure the node_id Parameter When Using the API for Adjusting Cluster Nodes?", "uri":"mrs_03_1139.html", "doc_type":"faq", - "p_code":"1219", - "code":"1220" + "p_code":"1223", + "code":"1224" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -10985,8 +11021,8 @@ "title":"Cluster Management", "uri":"mrs_03_2016.html", "doc_type":"faq", - "p_code":"1095", - "code":"1221" + "p_code":"1099", + "code":"1225" }, { "desc":"You can view all MRS clusters on the Clusters page. You can view clusters in different status.Active Clusters: all clusters except clusters in Failed and Terminated state", @@ -10994,8 +11030,8 @@ "title":"How Do I View All Clusters?", "uri":"mrs_03_1002.html", "doc_type":"faq", - "p_code":"1221", - "code":"1222" + "p_code":"1225", + "code":"1226" }, { "desc":"You can view operation logs of clusters and jobs on the Operation Logs page. The MRS operation logs record the following operations:Cluster operationsCreate, terminate, a", @@ -11003,8 +11039,8 @@ "title":"How Do I View Log Information?", "uri":"mrs_03_1003.html", "doc_type":"faq", - "p_code":"1221", - "code":"1223" + "p_code":"1225", + "code":"1227" }, { "desc":"After a cluster is created, click the cluster name on the MRS console. On the page displayed, you can view basic configuration information about the cluster. The instance", @@ -11012,8 +11048,8 @@ "title":"How Do I View Cluster Configuration Information?", "uri":"mrs_03_1004.html", "doc_type":"faq", - "p_code":"1221", - "code":"1224" + "p_code":"1225", + "code":"1228" }, { "desc":"You cannot install the Kafka and Flume components for a created cluster of MRS 3.1.0 or earlier. Kafka and Flume are components for a streaming cluster. To install Kafka ", @@ -11021,8 +11057,8 @@ "title":"How Do I Install Kafka and Flume in an MRS Cluster?", "uri":"mrs_03_1054.html", "doc_type":"faq", - "p_code":"1221", - "code":"1225" + "p_code":"1225", + "code":"1229" }, { "desc":"To stop an MRS cluster, stop each node in the cluster on the ECS. Click the name of each node on the Nodes tab page to go to the Elastic Cloud Server page and click Stop.", @@ -11030,8 +11066,8 @@ "title":"How Do I Stop an MRS Cluster?", "uri":"mrs_03_1016.html", "doc_type":"faq", - "p_code":"1221", - "code":"1226" + "p_code":"1225", + "code":"1230" }, { "desc":"You can expand data disk capacity for MRS during off-peak hours.Expand the EVS disk capacity, and then log in to the ECS and expand the partitions and file system. MRS no", @@ -11039,8 +11075,8 @@ "title":"Can I Expand Data Disk Capacity for MRS?", "uri":"mrs_03_1018.html", "doc_type":"faq", - "p_code":"1221", - "code":"1227" + "p_code":"1225", + "code":"1231" }, { "desc":"You cannot add or remove any component to and from a created cluster of MRS 3.1.0. However, you can create an MRS cluster that contains the required components.", @@ -11048,8 +11084,8 @@ "title":"Can I Add Components to an Existing Cluster?", "uri":"mrs_03_1024.html", "doc_type":"faq", - "p_code":"1221", - "code":"1228" + "p_code":"1225", + "code":"1232" }, { "desc":"You cannot delete any component from a created MRS cluster of MRS 3.1.0. If a component is not required, log in to MRS Manager and stop the component on the Services page", @@ -11057,8 +11093,8 @@ "title":"Can I Delete Components Installed in an MRS Cluster?", "uri":"mrs_03_1028.html", "doc_type":"faq", - "p_code":"1221", - "code":"1229" + "p_code":"1225", + "code":"1233" }, { "desc":"You cannot change MRS cluster nodes on the MRS console. You are also advised not to change MRS cluster nodes on the ECS console. Manually stopping or deleting an ECS, mod", @@ -11066,8 +11102,8 @@ "title":"Can I Change MRS Cluster Nodes on the MRS Console?", "uri":"mrs_03_1034.html", "doc_type":"faq", - "p_code":"1221", - "code":"1230" + "p_code":"1225", + "code":"1234" }, { "desc":"Log in to the MRS console.Click the name of the cluster.On the page displayed, choose Alarms > Notification Rules.Locate the row that contains the rule you want to modify", @@ -11075,8 +11111,8 @@ "title":"How Do I Shield Cluster Alarm/Event Notifications?", "uri":"mrs_03_1130.html", "doc_type":"faq", - "p_code":"1221", - "code":"1231" + "p_code":"1225", + "code":"1235" }, { "desc":"In an MRS cluster, MRS allocates 50% of the cluster memory to Yarn by default. You manage Yarn nodes logically by resource pool. Therefore, the total memory of the resour", @@ -11084,8 +11120,8 @@ "title":"Why Is the Resource Pool Memory Displayed in the MRS Cluster Smaller Than the Actual Cluster Memory?", "uri":"mrs_03_1161.html", "doc_type":"faq", - "p_code":"1221", - "code":"1232" + "p_code":"1225", + "code":"1236" }, { "desc":"su ommvim /opt/knox/bin/gateway.shsh /opt/knox/bin/gateway.sh stopsh /opt/knox/bin/gateway.sh start", @@ -11093,8 +11129,8 @@ "title":"How Do I Configure the knox Memory?", "uri":"mrs_03_1162.html", "doc_type":"faq", - "p_code":"1221", - "code":"1233" + "p_code":"1225", + "code":"1237" }, { "desc":"Log in to a Master node as user root and run the Python3 command to query the Python version.", @@ -11102,8 +11138,8 @@ "title":"What Is the Python Version Installed for an MRS Cluster?", "uri":"mrs_03_1171.html", "doc_type":"faq", - "p_code":"1221", - "code":"1234" + "p_code":"1225", + "code":"1238" }, { "desc":"The configuration file paths of commonly used components are as follows:", @@ -11111,8 +11147,8 @@ "title":"How Do I View the Configuration File Directory of Each Component?", "uri":"mrs_03_1198.html", "doc_type":"faq", - "p_code":"1221", - "code":"1235" + "p_code":"1225", + "code":"1239" }, { "desc":"If the time on a node inside the cluster is incorrect, log in to the node and rectify the fault from 2.If the time on a node inside the cluster is different from that on ", @@ -11120,8 +11156,8 @@ "title":"How Do I Do If the Time on MRS Nodes Is Incorrect?", "uri":"mrs_03_1211.html", "doc_type":"faq", - "p_code":"1221", - "code":"1236" + "p_code":"1225", + "code":"1240" }, { "desc":"Log in to the target node and run the following command to query the startup time:date -d \"$(awk -F. '{print $1}' /proc/uptime) second ago\" +\"%Y-%m-%d %H:%M:%S\"", @@ -11129,8 +11165,8 @@ "title":"How Do I Query the Startup Time of an MRS Node?", "uri":"mrs_03_1250.html", "doc_type":"usermanual", - "p_code":"1221", - "code":"1237" + "p_code":"1225", + "code":"1241" }, { "desc":"If \"ALM-12066 Inter-Node Mutual Trust Fails\" is reported on Manager or there is no SSH trust relationship between nodes, rectify the fault by performing the following ope", @@ -11138,8 +11174,8 @@ "title":"How Do I Do If Trust Relationships Between Nodes Are Abnormal?", "uri":"mrs_03_1212.html", "doc_type":"faq", - "p_code":"1221", - "code":"1238" + "p_code":"1225", + "code":"1242" }, { "desc":"The manager-executor process runs either on the Master1 or Master2 node in the MRS cluster in active/standby mode. This process is used to encapsulate the MRS management ", @@ -11147,8 +11183,8 @@ "title":"How Do I Adjust the Memory Size of the manager-executor Process?", "uri":"mrs_03_1228.html", "doc_type":"usermanual", - "p_code":"1221", - "code":"1239" + "p_code":"1225", + "code":"1243" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -11156,8 +11192,8 @@ "title":"Kerberos Usage", "uri":"mrs_03_2018.html", "doc_type":"faq", - "p_code":"1095", - "code":"1240" + "p_code":"1099", + "code":"1244" }, { "desc":"You cannot change the Kerberos service after an MRS cluster is created.", @@ -11165,8 +11201,8 @@ "title":"How Do I Change the Kerberos Authentication Status of a Created MRS Cluster?", "uri":"mrs_03_1038.html", "doc_type":"faq", - "p_code":"1240", - "code":"1241" + "p_code":"1244", + "code":"1245" }, { "desc":"The Kerberos authentication service uses ports 21730 (TCP), 21731 (TCP/UDP), and 21732 (TCP/UDP).", @@ -11174,8 +11210,8 @@ "title":"What Are the Ports of the Kerberos Authentication Service?", "uri":"mrs_03_1131.html", "doc_type":"faq", - "p_code":"1240", - "code":"1242" + "p_code":"1244", + "code":"1246" }, { "desc":"The MRS cluster does not support customized Kerberos installation and deployment, and the Kerberos authentication cannot be set up between components. To enable Kerberos ", @@ -11183,8 +11219,8 @@ "title":"How Do I Deploy the Kerberos Service in a Running Cluster?", "uri":"mrs_03_1148.html", "doc_type":"usermanual", - "p_code":"1240", - "code":"1243" + "p_code":"1244", + "code":"1247" }, { "desc":"Log in to the master node in the cluster as user root.Run the following command to configure environment variables:source /opt/client/bigdata_envsource /opt/client/bigdat", @@ -11192,8 +11228,8 @@ "title":"How Do I Access Hive in a Cluster with Kerberos Authentication Enabled?", "uri":"mrs_03_1152.html", "doc_type":"faq", - "p_code":"1240", - "code":"1244" + "p_code":"1244", + "code":"1248" }, { "desc":"Log in to the Master node in the cluster as user root.Run the following command to configure environment variables:source /opt/client/bigdata_envsource /opt/client/bigdat", @@ -11201,8 +11237,8 @@ "title":"How Do I Access Presto in a Cluster with Kerberos Authentication Enabled?", "uri":"mrs_03_1153.html", "doc_type":"faq", - "p_code":"1240", - "code":"1245" + "p_code":"1244", + "code":"1249" }, { "desc":"Log in to the master node in the cluster as user root.Run the following command to configure environment variables:source /opt/client/bigdata_envsource /opt/client/bigdat", @@ -11210,8 +11246,8 @@ "title":"How Do I Access Spark in a Cluster with Kerberos Authentication Enabled?", "uri":"en-us_topic_0000001442653993.html", "doc_type":"faq", - "p_code":"1240", - "code":"1246" + "p_code":"1244", + "code":"1250" }, { "desc":"Java applications:Before connecting to HBase, HDFS, or other big data components, call loginUserFromKeytab() to create a UGI. Then, start a scheduled thread to periodical", @@ -11219,8 +11255,8 @@ "title":"How Do I Prevent Kerberos Authentication Expiration?", "uri":"mrs_03_1167.html", "doc_type":"usermanual", - "p_code":"1240", - "code":"1247" + "p_code":"1244", + "code":"1251" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -11228,8 +11264,8 @@ "title":"Metadata Management", "uri":"mrs_03_2019.html", "doc_type":"faq", - "p_code":"1095", - "code":"1248" + "p_code":"1099", + "code":"1252" }, { "desc":"If Hive metadata is stored in GaussDB of an MRS cluster, log in to the master DBServer node of the cluster, switch to user omm, and run the gsql -p 20051 -U {USER} -W {PA", @@ -11237,8 +11273,8 @@ "title":"Where Can I View Hive Metadata?", "uri":"mrs_03_1119.html", "doc_type":"faq", - "p_code":"1248", - "code":"1249" + "p_code":"1252", + "code":"1253" }, { "desc":"For details about the terms involved in this document, see Glossary.", @@ -11247,7 +11283,7 @@ "uri":"en-us_topic_0000001296775220.html", "doc_type":"usermanual", "p_code":"", - "code":"1250" + "code":"1254" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -11256,6 +11292,6 @@ "uri":"mrs_01_9003.html", "doc_type":"usermanual", "p_code":"", - "code":"1251" + "code":"1255" } ] \ No newline at end of file diff --git a/docs/mrs/umn/admin_guide_000001.html b/docs/mrs/umn/admin_guide_000001.html index 659fd394..568e93e2 100644 --- a/docs/mrs/umn/admin_guide_000001.html +++ b/docs/mrs/umn/admin_guide_000001.html @@ -4,18 +4,18 @@
        diff --git a/docs/mrs/umn/admin_guide_000002.html b/docs/mrs/umn/admin_guide_000002.html index a99cef2e..d75ee2ba 100644 --- a/docs/mrs/umn/admin_guide_000002.html +++ b/docs/mrs/umn/admin_guide_000002.html @@ -1,10 +1,10 @@ -

        FusionInsight Manager Introduction

        -

        Overview

        MRS allows you to manage and analyze massive amounts of structured and unstructured data for rapid data mining. Open source components have complex structures and therefore they are difficult to install, configure, and manage. FusionInsight Manager is a unified enterprise-level cluster management platform that provides:

        +

        MRS Manager Introduction

        +

        Overview

        MRS allows you to manage and analyze massive amounts of structured and unstructured data for rapid data mining. Open source components have complex structures and therefore they are difficult to install, configure, and manage. MRS Manager is a unified enterprise-level cluster management platform that provides:

        • Cluster monitoring: enables you to quickly learn the running status of hosts and services.
        • Graphical metric monitoring and customization: enable you to obtain key system information in a timely manner.
        • Service property configuration: allows you to configure service properties based on the performance requirements of your services.
        • Cluster, service, and role instance operations: allow you to start or stop services and clusters with just a few clicks.
        • Rights management and audit: allow you to configure the access control and manage operation logs.
        -

        Introduction to the FusionInsight Manager GUI

        FusionInsight Manager provides a unified cluster management platform, facilitating rapid and easy O&M for clusters.

        +

        Introduction to the MRS Manager GUI

        MRS Manager provides a unified cluster management platform, facilitating rapid and easy O&M for clusters.

        The upper part of the page is the operation bar, the middle part is the display area, and the bottom part is the taskbar.

        Table 1 describes the functions of each portal on the operation bar. @@ -46,7 +46,7 @@

        System

        -

        Provides system management settings of FusionInsight Manager, such as user permission settings. For details, see System Configuration.

        +

        Provides system management settings of MRS Manager, such as user permission settings. For details, see System Configuration.

        diff --git a/docs/mrs/umn/admin_guide_000003.html b/docs/mrs/umn/admin_guide_000003.html index 07bf0da4..65c51772 100644 --- a/docs/mrs/umn/admin_guide_000003.html +++ b/docs/mrs/umn/admin_guide_000003.html @@ -1,9 +1,9 @@ -

        Querying the FusionInsight Manager Version

        -

        By viewing the FusionInsight Manager version, you can prepare for system upgrade and routine maintenance.

        -
        • Using the GUI:

          Log in to FusionInsight Manager. On the home page, click in the upper right corner and choose About from the drop-down list. In the dialog box that is displayed, view the FusionInsight Manager version.

          -
        • Using the CLI
          1. Log in to the FusionInsight Manager active management node as user root.
          2. Run the following commands to check the version and platform information of FusionInsight Manager:

            su - omm

            +

            Querying the MRS Manager Version

            +

            By viewing the MRS Manager version, you can prepare for system upgrade and routine maintenance.

            +
            • Using the GUI:

              Log in to MRS Manager. On the home page, click in the upper right corner and choose About from the drop-down list. In the dialog box that is displayed, view the MRS Manager version.

              +
            • Using the CLI
              1. Log in to the MRS Manager active management node as user root.
              2. Run the following commands to check the version and platform information of MRS Manager:

                su - omm

                cd ${BIGDATA_HOME}/om-server/om/sbin/pack

                ./queryManager.sh

                The following information is displayed:

                diff --git a/docs/mrs/umn/admin_guide_000004.html b/docs/mrs/umn/admin_guide_000004.html index 003bf67b..39df6240 100644 --- a/docs/mrs/umn/admin_guide_000004.html +++ b/docs/mrs/umn/admin_guide_000004.html @@ -1,9 +1,9 @@ -

                Logging In to FusionInsight Manager

                -

                Scenario

                Log in to FusionInsight Manager using an account.

                +

                Logging In to MRS Manager

                +

                Scenario

                Log in to MRS Manager using an account.

                -

                Procedure

                1. Obtain the URL for logging in to FusionInsight Manager.
                2. On login page, enter the username and password.
                3. Change the password upon your first login.

                  The password must:

                  +

                  Procedure

                  1. Obtain the URL for logging in to MRS Manager.
                  2. On login page, enter the username and password.
                  3. Change the password upon your first login.

                    The password must:

                    • Contain 8 to 64 characters.
                    • Contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (`~!@#$%^&*()-_=+|[{}];',<.>/\?).
                    • Be different from the username or the username spelled backwards.
                    • Be different from the current password.

                  4. Move the cursor over in the upper right corner of home page, and choose Logout from the drop-down list. In the dialog box that is displayed, click OK to log out of the current user.
                  diff --git a/docs/mrs/umn/admin_guide_000005.html b/docs/mrs/umn/admin_guide_000005.html index a08162ce..6af57450 100644 --- a/docs/mrs/umn/admin_guide_000005.html +++ b/docs/mrs/umn/admin_guide_000005.html @@ -3,11 +3,11 @@

                  Logging In to the Management Node

                  Scenario

                  Some O&M operation scripts and commands need to be run or can be run only on the active management node. You can identify and log in to the active or standby management node based on the following operations.

                  -

                  Checking and Logging In to the Active and Standby Management Nodes

                  1. Log in to FusionInsight Manager.
                  2. Choose System > OMS.

                    In the Basic Information area, Current Active indicates the host name of the active management node, and Current Standby indicates the host name of the standby management node.

                    +

                    Checking and Logging In to the Active and Standby Management Nodes

                    1. Log in to MRS Manager.
                    2. Choose System > OMS.

                      In the Basic Information area, Current Active indicates the host name of the active management node, and Current Standby indicates the host name of the standby management node.

                      Click a host name to go to the host details page. On the host details page, record the IP address of the host.

                    3. Log in to the active or standby management node as user root.
                    -

                    Identifying the Active and Standby Management Nodes by Running Scripts and Logging In to Them

                    1. Log in to any node where FusionInsight Manager is installed as user root.
                    2. Run the following command to identify the active and standby management nodes:

                      su - omm

                      +

                      Identifying the Active and Standby Management Nodes by Running Scripts and Logging In to Them

                      1. Log in to any node where MRS Manager is installed as user root.
                      2. Run the following command to identify the active and standby management nodes:

                        su - omm

                        sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh

                        In the command output, the node whose HAActive is active is the active management node (Master1), and the node whose HAActive is standby is the standby node (Master2).

                        HAMode 
diff --git a/docs/mrs/umn/admin_guide_000006.html b/docs/mrs/umn/admin_guide_000006.html
index 1ff5af47..3ff04f6e 100644
--- a/docs/mrs/umn/admin_guide_000006.html
+++ b/docs/mrs/umn/admin_guide_000006.html
@@ -11,7 +11,7 @@
            -
            Parent topic: FusionInsight Manager Operation Guide (Applicable to 3.x)
            +
            Parent topic: MRS Manager Operation Guide (Applicable to 3.x)
            diff --git a/docs/mrs/umn/admin_guide_000007.html b/docs/mrs/umn/admin_guide_000007.html index 7ca162e2..4440e7eb 100644 --- a/docs/mrs/umn/admin_guide_000007.html +++ b/docs/mrs/umn/admin_guide_000007.html @@ -1,7 +1,7 @@

            Overview

            -

            After you log in to FusionInsight Manager, Homepage is displayed by default. On this page, the Summary tab displays the service statuses and monitoring status reports of each cluster, and the Alarm Analysis tab displays the statistics and analysis of top alarms.

            +

            After you log in to MRS Manager, Homepage is displayed by default. On this page, the Summary tab displays the service statuses and monitoring status reports of each cluster, and the Alarm Analysis tab displays the statistics and analysis of top alarms.

            • On the right of the home page, you can view the number of alarms of different severities, number of running tasks, current user, and help information.
              • Click to view the task name, cluster, status, progress, start time, and end time of the last 100 operation tasks in Task Management Center.

                For a start, stop, restart, or rolling restart task, you can abort it by clicking the task name in the task list, clicking Abort, and then entering the system administrator password in the dialog box that is displayed. An aborted task is no longer executed.

              • Click to obtain help information. @@ -13,14 +13,14 @@

                About

                -

                Provides the FusionInsight Manager version information.

                +

                Provides the MRS Manager version information.

        -
      4. The taskbar at the bottom of the home page displays the language options of FusionInsight Manager and the current cluster time and time zone information. You can switch the system language as needed.
        5. +
      5. The taskbar at the bottom of the home page displays the language options of MRS Manager and the current cluster time and time zone information. You can switch the system language as needed.

        6. Service Status Preview Area

        The number of hosts available in and the number of services installed in each cluster are displayed on the left of the homepage. You can click to expand all service information of the cluster and view the status and alarms of each service.

        Click to perform basic O&M management operations on the current cluster. For details, see Table 1.

        The icon on the left of each service name indicates that the service is running properly; the icon indicates that the current service fails to start; and the icon indicates that the current service is not started.

        diff --git a/docs/mrs/umn/admin_guide_000008.html b/docs/mrs/umn/admin_guide_000008.html index 8a26d835..a25239e5 100644 --- a/docs/mrs/umn/admin_guide_000008.html +++ b/docs/mrs/umn/admin_guide_000008.html @@ -1,19 +1,19 @@

        Managing Monitoring Metric Reports

        -

        Scenario

        On FusionInsight Manager, you can customize monitoring items to display on the homepage and export monitoring data.

        +

        Scenario

        On MRS Manager, you can customize monitoring items to display on the homepage and export monitoring data.

        The interval on the horizontal axis of the chart varies depending on the time period you specify. Data monitoring rules are as follows:

        • 0 to 25 hours: The interval is 5 minutes. The cluster must have been installed for at least 10 minutes, and monitoring data of a maximum of 15 days is saved.
        • 25 to 150 hours: The interval is 30 minutes. The cluster must have been installed for at least 30 minutes, and monitoring data of a maximum of 3 months is saved.
        • 150 to 300 hours: The interval is 1 hour. The cluster must have been installed for at least 1 hour, and monitoring data of a maximum of 3 months is saved.
        • 300 hours to 300 days: The interval is 1 day. The cluster must have been installed for at least 1 day, and monitoring data of a maximum of 6 months is saved.
        • Over 300 days: The interval is 7 days. The cluster must have been installed for more than 7 days, and monitoring data of a maximum of 1 year is saved.
        • If the disk usage of the partition where GaussDB resides exceeds 80%, real-time monitoring data and monitoring data whose interval is 5 minutes will be deleted.
        • Storage resources (HDFS) in Tenant Resources (0 to 300 hours): The interval is 1 hour. The cluster must have been installed for at least 1 hour, and monitoring data of a maximum of 3 months is saved.
        -

        Customizing a Monitoring Metric Report

        1. Log in to FusionInsight Manager.
        2. Choose Homepage.
        3. In the upper right corner of the chart area, click and choose Customize from the displayed menu.

          Monitoring data of the past 1 hour is displayed at an interval of 5 minutes. After you enter the Real-time Monitoring page, you can view that real-time monitoring data is displayed on the right of the monitoring chart at an interval of 5 minutes.

          +

          Customizing a Monitoring Metric Report

          1. Log in to MRS Manager.
          2. Choose Homepage.
          3. In the upper right corner of the chart area, click and choose Customize from the displayed menu.

            Monitoring data of the past 1 hour is displayed at an interval of 5 minutes. After you enter the Real-time Monitoring page, you can view that real-time monitoring data is displayed on the right of the monitoring chart at an interval of 5 minutes.

          4. In the left pane of the Customize Statistics dialog box, select a resource to monitor.
          5. Select one or multiple monitoring metrics in the right pane.
          6. Click OK.
          -

          Exporting All Monitoring Data

          1. Log in to FusionInsight Manager.
          2. Choose Homepage.
          3. In the upper right corner of the chart area, select a time range to obtain monitoring data, for example, 1w.

            Real-time data is displayed by default, which cannot be exported. You can click to customize a time range.

            +

            Exporting All Monitoring Data

            1. Log in to MRS Manager.
            2. Choose Homepage.
            3. In the upper right corner of the chart area, select a time range to obtain monitoring data, for example, 1w.

              Real-time data is displayed by default, which cannot be exported. You can click to customize a time range.

            4. In the upper right corner of the chart area, click and choose Export from the displayed menu.
            -

            Exporting Monitoring Data of a Specified Monitoring Item

            1. Log in to FusionInsight Manager.
            2. Choose Homepage.
            3. Click in the upper right corner of any monitoring report pane in the chart area of the target cluster.
            4. Select a time range to obtain monitoring data, for example, 1w.

              Real-time data is displayed by default, which cannot be exported. You can click to customize a time range.

              +

              Exporting Monitoring Data of a Specified Monitoring Item

              1. Log in to MRS Manager.
              2. Choose Homepage.
              3. Click in the upper right corner of any monitoring report pane in the chart area of the target cluster.
              4. Select a time range to obtain monitoring data, for example, 1w.

                Real-time data is displayed by default, which cannot be exported. You can click to customize a time range.

              5. Click Export.
            diff --git a/docs/mrs/umn/admin_guide_000009.html b/docs/mrs/umn/admin_guide_000009.html index 677d08b0..68aaf6df 100644 --- a/docs/mrs/umn/admin_guide_000009.html +++ b/docs/mrs/umn/admin_guide_000009.html @@ -13,7 +13,7 @@
            -
            Parent topic: FusionInsight Manager Operation Guide (Applicable to 3.x)
            +
            Parent topic: MRS Manager Operation Guide (Applicable to 3.x)
          diff --git a/docs/mrs/umn/admin_guide_000011.html b/docs/mrs/umn/admin_guide_000011.html index 502ace22..228fdb59 100644 --- a/docs/mrs/umn/admin_guide_000011.html +++ b/docs/mrs/umn/admin_guide_000011.html @@ -1,7 +1,7 @@

          Overview

          -

          Dashboard

          Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Dashboard to view the status of the current cluster.

          +

          Dashboard

          Log in to MRS Manager and choose Cluster > Name of the desired cluster > Dashboard to view the status of the current cluster.

          On the Dashboard tab page, you can start, stop, perform a rolling restart of, synchronize configurations to, and perform other basic operations on the current cluster.

          diff --git a/docs/mrs/umn/admin_guide_000012.html b/docs/mrs/umn/admin_guide_000012.html index ddb86f5c..0ea64f37 100644 --- a/docs/mrs/umn/admin_guide_000012.html +++ b/docs/mrs/umn/admin_guide_000012.html @@ -8,7 +8,7 @@

          Impact on the System

          A rolling restart takes a longer time and may affect service throughput and performance.

          -

          Procedure

          1. Log in to FusionInsight Manager.
          2. Choose Cluster > Name of the target cluster > Dashboard. On this tab page, choose More > Rolling-restart Service.
          3. In the dialog box that is displayed, enter the password of the current login user and click OK.
          4. Configure the parameters based on site requirements.

            +

            Procedure

            1. Log in to MRS Manager.
            2. Choose Cluster > Name of the target cluster > Dashboard. On this tab page, choose More > Rolling-restart Service.
            3. In the dialog box that is displayed, enter the password of the current login user and click OK.
            4. Configure the parameters based on site requirements.

              Table 1 Rolling restart parameters

              Parameter

              Description

              diff --git a/docs/mrs/umn/admin_guide_000013.html b/docs/mrs/umn/admin_guide_000013.html index 13c5148a..29b78a56 100644 --- a/docs/mrs/umn/admin_guide_000013.html +++ b/docs/mrs/umn/admin_guide_000013.html @@ -7,7 +7,7 @@

              Impact on the System

              • After synchronizing the cluster configuration, you need to restart the services whose configuration has expired. These services are unavailable during restart.
              • The instances whose configuration has expired are unavailable during restart.

              Procedure

              Synchronize the configuration.

              -
              1. Log in to FusionInsight Manager.
              2. Choose Cluster > Name of the desired cluster > Dashboard.
              3. On this page, choose More > Synchronize Configuration.
              4. In the dialog box that is displayed, click OK.
              +
              1. Log in to MRS Manager.
              2. Choose Cluster > Name of the desired cluster > Dashboard.
              3. On this page, choose More > Synchronize Configuration.
              4. In the dialog box that is displayed, click OK.

              Restart configuration-expired instances.

              1. Choose More > Restart Configuration-Expired Instances.
              2. In the dialog box that is displayed, enter the password of the current login user and click OK.
              3. In the displayed dialog box, click OK.

                You can click View Instance to open the list of all expired instances and confirm that the instances have been restarted.

              diff --git a/docs/mrs/umn/admin_guide_000014.html b/docs/mrs/umn/admin_guide_000014.html index 046a6633..6de75dba 100644 --- a/docs/mrs/umn/admin_guide_000014.html +++ b/docs/mrs/umn/admin_guide_000014.html @@ -3,8 +3,8 @@

              Downloading the Client

              Scenario

              Use the default client provided by MRS clusters to manage the cluster, run services, and perform secondary development. Before you use this client, you need to download its software package.

              -

              Procedure

              1. Log in to FusionInsight Manager.
              2. Choose Cluster > Name of the desired cluster > Dashboard. On the page that is displayed, choose More > Download Client.

                The Download Cluster Client dialog box is displayed.

                -

              3. Select a client type for Select Client Type.