From c285e88a17b826bfd96f894ee59ced12881a3135 Mon Sep 17 00:00:00 2001 From: yangtong Date: Tue, 2 Sep 2025 10:43:57 +0000 Subject: [PATCH] MRS UMN 20250806 version Reviewed-by: Pruthi, Vineet Co-authored-by: yangtong Co-committed-by: yangtong --- docs/mrs/umn/.placeholder | 0 docs/mrs/umn/ALL_META.TXT.json | 4087 +++++--- docs/mrs/umn/ALM-12091.html | 4 +- docs/mrs/umn/ALM-12186.html | 4 +- docs/mrs/umn/ALM-12187.html | 6 +- docs/mrs/umn/ALM-12188.html | 4 +- docs/mrs/umn/ALM-12191.html | 98 + docs/mrs/umn/ALM-12192.html | 98 + docs/mrs/umn/ALM-12200.html | 81 + docs/mrs/umn/ALM-12201.html | 98 + docs/mrs/umn/ALM-12202.html | 93 + docs/mrs/umn/ALM-12203.html | 93 + docs/mrs/umn/ALM-12204.html | 98 + docs/mrs/umn/ALM-12205.html | 98 + docs/mrs/umn/ALM-12206.html | 81 + docs/mrs/umn/ALM-12207.html | 112 + docs/mrs/umn/ALM-14031.html | 4 +- docs/mrs/umn/ALM-14032.html | 4 +- docs/mrs/umn/ALM-14033.html | 4 +- docs/mrs/umn/ALM-14034.html | 4 +- docs/mrs/umn/ALM-14035.html | 4 +- docs/mrs/umn/ALM-14036.html | 103 + docs/mrs/umn/ALM-14037.html | 86 + docs/mrs/umn/ALM-14038.html | 92 + docs/mrs/umn/ALM-14039.html | 103 + docs/mrs/umn/ALM-16051.html | 95 + docs/mrs/umn/ALM-16052.html | 97 + docs/mrs/umn/ALM-16053.html | 97 + docs/mrs/umn/ALM-17008.html | 89 + docs/mrs/umn/ALM-17009.html | 89 + docs/mrs/umn/ALM-17010.html | 89 + docs/mrs/umn/ALM-17011.html | 89 + docs/mrs/umn/ALM-19022.html | 8 +- docs/mrs/umn/ALM-19023.html | 4 +- docs/mrs/umn/ALM-19024.html | 10 +- docs/mrs/umn/ALM-19025.html | 6 +- docs/mrs/umn/ALM-19026.html | 6 +- docs/mrs/umn/ALM-19030.html | 102 + docs/mrs/umn/ALM-19031.html | 98 + docs/mrs/umn/ALM-19032.html | 124 + docs/mrs/umn/ALM-19033.html | 132 + docs/mrs/umn/ALM-19034.html | 106 + docs/mrs/umn/ALM-19035.html | 124 + docs/mrs/umn/ALM-19036.html | 133 + docs/mrs/umn/ALM-25007.html | 6 +- docs/mrs/umn/ALM-25008.html | 6 +- docs/mrs/umn/ALM-29007.html | 4 +- docs/mrs/umn/ALM-29008.html | 6 +- docs/mrs/umn/ALM-29010.html | 4 +- docs/mrs/umn/ALM-29011.html | 4 +- docs/mrs/umn/ALM-29012.html | 4 +- docs/mrs/umn/ALM-29013.html | 6 +- docs/mrs/umn/ALM-29014.html | 6 +- docs/mrs/umn/ALM-29015.html | 4 +- docs/mrs/umn/ALM-29016.html | 6 +- docs/mrs/umn/ALM-38009.html | 4 +- docs/mrs/umn/ALM-38012.html | 93 + docs/mrs/umn/ALM-38013.html | 100 + docs/mrs/umn/ALM-38014.html | 100 + docs/mrs/umn/ALM-38015.html | 100 + docs/mrs/umn/ALM-38016.html | 100 + docs/mrs/umn/ALM-38017.html | 95 + docs/mrs/umn/ALM-38018.html | 106 + docs/mrs/umn/ALM-43028.html | 90 + docs/mrs/umn/ALM-43029.html | 95 + docs/mrs/umn/ALM-45003.html | 4 +- docs/mrs/umn/ALM-45004.html | 97 + docs/mrs/umn/ALM-45005.html | 98 + docs/mrs/umn/ALM-45006.html | 99 + docs/mrs/umn/ALM-45007.html | 96 + docs/mrs/umn/ALM-45008.html | 99 + docs/mrs/umn/ALM-45009.html | 99 + docs/mrs/umn/ALM-45289.html | 6 +- docs/mrs/umn/ALM-45290.html | 6 +- docs/mrs/umn/ALM-45291.html | 6 +- docs/mrs/umn/ALM-45292.html | 6 +- docs/mrs/umn/ALM-45293.html | 132 + docs/mrs/umn/ALM-45294.html | 124 + docs/mrs/umn/ALM-45435.html | 4 +- docs/mrs/umn/ALM-45436.html | 4 +- docs/mrs/umn/ALM-45437.html | 4 +- docs/mrs/umn/ALM-45438.html | 4 +- docs/mrs/umn/ALM-45439.html | 6 +- docs/mrs/umn/ALM-45440.html | 8 +- docs/mrs/umn/ALM-45441.html | 6 +- docs/mrs/umn/ALM-45442.html | 6 +- docs/mrs/umn/ALM-45443.html | 6 +- docs/mrs/umn/ALM-45444.html | 4 +- docs/mrs/umn/ALM-45445.html | 131 + docs/mrs/umn/ALM-45446.html | 105 + docs/mrs/umn/ALM-45447.html | 108 + docs/mrs/umn/ALM-45448.html | 93 + docs/mrs/umn/ALM-45449.html | 94 + docs/mrs/umn/ALM-45450.html | 91 + docs/mrs/umn/ALM-45451.html | 91 + docs/mrs/umn/ALM-45452.html | 91 + docs/mrs/umn/ALM-45475.html | 80 + docs/mrs/umn/ALM-45476.html | 86 + docs/mrs/umn/ALM-45477.html | 84 + docs/mrs/umn/ALM-45478.html | 83 + docs/mrs/umn/ALM-45479.html | 88 + docs/mrs/umn/ALM-45480.html | 95 + docs/mrs/umn/ALM-45481.html | 92 + docs/mrs/umn/ALM-45642.html | 6 +- docs/mrs/umn/ALM-45643.html | 2 +- docs/mrs/umn/ALM-45644.html | 4 +- docs/mrs/umn/ALM-45645.html | 2 +- docs/mrs/umn/ALM-45646.html | 2 +- docs/mrs/umn/ALM-45647.html | 2 +- docs/mrs/umn/ALM-45648.html | 4 +- docs/mrs/umn/ALM-45649.html | 4 +- docs/mrs/umn/ALM-45650.html | 6 +- docs/mrs/umn/ALM-45652.html | 12 +- docs/mrs/umn/ALM-45653.html | 4 +- docs/mrs/umn/ALM-45654.html | 4 +- docs/mrs/umn/ALM-45655.html | 4 +- docs/mrs/umn/ALM-45736.html | 4 +- docs/mrs/umn/ALM-45737.html | 6 +- docs/mrs/umn/ALM-45738.html | 6 +- docs/mrs/umn/ALM-45739.html | 6 +- docs/mrs/umn/ALM-45740.html | 6 +- docs/mrs/umn/ALM-45741.html | 2 +- docs/mrs/umn/ALM-45742.html | 2 +- docs/mrs/umn/ALM-45743.html | 2 +- docs/mrs/umn/ALM-45744.html | 96 + docs/mrs/umn/ALM-45745.html | 96 + docs/mrs/umn/ALM-47001.html | 93 + docs/mrs/umn/ALM-47002.html | 83 + docs/mrs/umn/ALM-47003.html | 84 + docs/mrs/umn/ALM-47004.html | 85 + docs/mrs/umn/ALM-50201.html | 8 +- docs/mrs/umn/ALM-50202.html | 4 +- docs/mrs/umn/ALM-50203.html | 4 +- docs/mrs/umn/ALM-50205.html | 4 +- docs/mrs/umn/ALM-50206.html | 4 +- docs/mrs/umn/ALM-50207.html | 4 +- docs/mrs/umn/ALM-50208.html | 4 +- docs/mrs/umn/ALM-50209.html | 4 +- docs/mrs/umn/ALM-50210.html | 4 +- docs/mrs/umn/ALM-50211.html | 6 +- docs/mrs/umn/ALM-50212.html | 4 +- docs/mrs/umn/ALM-50213.html | 4 +- docs/mrs/umn/ALM-50214.html | 6 +- docs/mrs/umn/ALM-50215.html | 4 +- docs/mrs/umn/ALM-50216.html | 4 +- docs/mrs/umn/ALM-50217.html | 6 +- docs/mrs/umn/ALM-50219.html | 6 +- docs/mrs/umn/ALM-50220.html | 2 +- docs/mrs/umn/ALM-50221.html | 4 +- docs/mrs/umn/ALM-50222.html | 4 +- docs/mrs/umn/ALM-50223.html | 6 +- docs/mrs/umn/ALM-50224.html | 4 +- docs/mrs/umn/ALM-50225.html | 4 +- docs/mrs/umn/ALM-50226.html | 4 +- docs/mrs/umn/ALM-50227.html | 92 + docs/mrs/umn/ALM-50228.html | 95 + docs/mrs/umn/ALM-50229.html | 97 + docs/mrs/umn/ALM-50230.html | 97 + docs/mrs/umn/ALM-50231.html | 99 + docs/mrs/umn/ALM-50232.html | 112 + docs/mrs/umn/ALM-50401.html | 4 +- docs/mrs/umn/ALM-50402.html | 4 +- docs/mrs/umn/ALM-50406.html | 82 + docs/mrs/umn/ALM-50407.html | 82 + docs/mrs/umn/ALM-50408.html | 82 + docs/mrs/umn/CLASS.TXT.json | 8368 +++++++++-------- docs/mrs/umn/admin_guide_000002.html | 33 +- docs/mrs/umn/admin_guide_000003.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 | 95 +- docs/mrs/umn/admin_guide_000022.html | 57 +- docs/mrs/umn/admin_guide_000040.html | 7 +- docs/mrs/umn/admin_guide_000071.html | 2 +- docs/mrs/umn/admin_guide_000072.html | 29 +- docs/mrs/umn/admin_guide_000101.html | 6 +- docs/mrs/umn/admin_guide_000109.html | 2 +- docs/mrs/umn/admin_guide_000110.html | 2 +- docs/mrs/umn/admin_guide_000113.html | 2 +- docs/mrs/umn/admin_guide_000115.html | 2 +- docs/mrs/umn/admin_guide_000118.html | 4 +- docs/mrs/umn/admin_guide_000127.html | 2 +- docs/mrs/umn/admin_guide_000128.html | 2 +- docs/mrs/umn/admin_guide_000133.html | 30 +- docs/mrs/umn/admin_guide_000145.html | 68 +- docs/mrs/umn/admin_guide_000148.html | 6 +- docs/mrs/umn/admin_guide_000150.html | 8 +- docs/mrs/umn/admin_guide_000162.html | 2 +- docs/mrs/umn/admin_guide_000171.html | 95 +- docs/mrs/umn/admin_guide_000173.html | 92 +- docs/mrs/umn/admin_guide_000176.html | 2 +- docs/mrs/umn/admin_guide_000177.html | 2 +- docs/mrs/umn/admin_guide_000201.html | 2 + docs/mrs/umn/admin_guide_000209.html | 4 +- docs/mrs/umn/admin_guide_000210.html | 4 +- docs/mrs/umn/admin_guide_000215.html | 2 + docs/mrs/umn/admin_guide_000223.html | 2 + docs/mrs/umn/admin_guide_000224.html | 2 + docs/mrs/umn/admin_guide_000240.html | 2 +- docs/mrs/umn/admin_guide_000249.html | 2 + docs/mrs/umn/admin_guide_000363.html | 2 +- docs/mrs/umn/admin_guide_000399.html | 23 +- docs/mrs/umn/admin_guide_000407.html | 2 + docs/mrs/umn/admin_guide_000408.html | 2 +- docs/mrs/umn/admin_guide_000409.html | 344 +- docs/mrs/umn/admin_guide_000410.html | 6 +- docs/mrs/umn/admin_guide_000412.html | 4 +- docs/mrs/umn/admin_guide_000413.html | 4 +- docs/mrs/umn/admin_guide_000414.html | 6 +- docs/mrs/umn/admin_guide_000416.html | 4 +- docs/mrs/umn/admin_guide_000420.html | 22 + docs/mrs/umn/admin_guide_000423.html | 80 + docs/mrs/umn/admin_guide_000424.html | 52 + docs/mrs/umn/admin_guide_000427.html | 66 + docs/mrs/umn/en-us_image_0000001392574002.png | Bin 90492 -> 0 bytes docs/mrs/umn/en-us_image_0000001532607778.png | Bin 74715 -> 0 bytes docs/mrs/umn/en-us_image_0000001583087429.png | Bin 42441 -> 0 bytes docs/mrs/umn/en-us_image_0000002379936846.png | Bin 0 -> 71058 bytes docs/mrs/umn/en-us_image_0000002380008412.png | Bin 0 -> 264 bytes docs/mrs/umn/en-us_image_0000002380310204.png | Bin 0 -> 82117 bytes docs/mrs/umn/en-us_image_0000002380470068.png | Bin 0 -> 236277 bytes docs/mrs/umn/en-us_image_0000002380470088.png | Bin 0 -> 53838 bytes docs/mrs/umn/en-us_image_0000002381596168.png | Bin 0 -> 29332 bytes docs/mrs/umn/en-us_image_0000002381622762.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002381622794.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002381782666.png | Bin 0 -> 14597 bytes docs/mrs/umn/en-us_image_0000002381782678.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002382274158.png | Bin 0 -> 57424 bytes docs/mrs/umn/en-us_image_0000002382293908.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002382434022.png | Bin 0 -> 37340 bytes docs/mrs/umn/en-us_image_0000002382453800.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002413536053.png | Bin 0 -> 15160 bytes docs/mrs/umn/en-us_image_0000002413647801.png | Bin 0 -> 174 bytes docs/mrs/umn/en-us_image_0000002413688652.png | Bin 0 -> 58446 bytes docs/mrs/umn/en-us_image_0000002413843108.png | Bin 0 -> 82117 bytes docs/mrs/umn/en-us_image_0000002413848564.png | Bin 0 -> 13881 bytes docs/mrs/umn/en-us_image_0000002413949605.png | Bin 0 -> 82117 bytes docs/mrs/umn/en-us_image_0000002414069433.png | Bin 0 -> 60840 bytes docs/mrs/umn/en-us_image_0000002414069445.png | Bin 0 -> 9300 bytes docs/mrs/umn/en-us_image_0000002415261981.png | Bin 0 -> 14597 bytes docs/mrs/umn/en-us_image_0000002415262005.png | Bin 0 -> 50918 bytes docs/mrs/umn/en-us_image_0000002415342137.png | Bin 0 -> 35588 bytes docs/mrs/umn/en-us_image_0000002415342161.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002415833501.png | Bin 0 -> 57424 bytes docs/mrs/umn/en-us_image_0000002415853277.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002415993313.png | Bin 0 -> 57424 bytes docs/mrs/umn/en-us_image_0000002416013105.png | Bin 0 -> 366 bytes docs/mrs/umn/en-us_image_0000002447362249.png | Bin 0 -> 82117 bytes docs/mrs/umn/en-us_image_0000002447402305.png | Bin 0 -> 82117 bytes docs/mrs/umn/mrs_01_0025.html | 2 +- docs/mrs/umn/mrs_01_0496.html | 2 +- docs/mrs/umn/mrs_01_0512.html | 2 +- docs/mrs/umn/mrs_01_0513.html | 2 +- docs/mrs/umn/mrs_01_1298.html | 150 + docs/mrs/umn/mrs_01_248978.html | 6 +- docs/mrs/umn/mrs_01_248989.html | 4 +- docs/mrs/umn/mrs_01_248991.html | 2 +- docs/mrs/umn/mrs_01_248992.html | 6 +- docs/mrs/umn/mrs_01_248993.html | 2 +- docs/mrs/umn/mrs_01_248995.html | 4 +- docs/mrs/umn/mrs_01_248996.html | 2 +- docs/mrs/umn/mrs_01_248997.html | 2 +- docs/mrs/umn/mrs_01_248998.html | 2 +- docs/mrs/umn/mrs_01_249283.html | 4 +- docs/mrs/umn/mrs_01_9003.html | 21 +- docs/mrs/umn/mrs_03_1058.html | 4 +- docs/mrs/umn/mrs_03_1133.html | 2 +- docs/mrs/umn/mrs_03_1167.html | 4 +- docs/mrs/umn/mrs_03_1169.html | 2 +- docs/mrs/umn/mrs_03_1198.html | 2 +- docs/mrs/umn/mrs_03_1214.html | 2 +- docs/mrs/umn/mrs_07_020001.html | 2 +- docs/mrs/umn/mrs_08_0001.html | 2 +- docs/mrs/umn/mrs_08_0005.html | 404 +- docs/mrs/umn/mrs_08_00132.html | 2 +- docs/mrs/umn/mrs_08_0038.html | 27 + docs/mrs/umn/mrs_08_0039.html | 21 + docs/mrs/umn/mrs_08_0052.html | 6 + docs/mrs/umn/mrs_08_0116.html | 17 + docs/mrs/umn/mrs_08_0117.html | 44 + docs/mrs/umn/mrs_08_0118.html | 22 + 282 files changed, 16390 insertions(+), 5762 deletions(-) delete mode 100644 docs/mrs/umn/.placeholder create mode 100644 docs/mrs/umn/ALM-12191.html create mode 100644 docs/mrs/umn/ALM-12192.html create mode 100644 docs/mrs/umn/ALM-12200.html create mode 100644 docs/mrs/umn/ALM-12201.html create mode 100644 docs/mrs/umn/ALM-12202.html create mode 100644 docs/mrs/umn/ALM-12203.html create mode 100644 docs/mrs/umn/ALM-12204.html create mode 100644 docs/mrs/umn/ALM-12205.html create mode 100644 docs/mrs/umn/ALM-12206.html create mode 100644 docs/mrs/umn/ALM-12207.html create mode 100644 docs/mrs/umn/ALM-14036.html create mode 100644 docs/mrs/umn/ALM-14037.html create mode 100644 docs/mrs/umn/ALM-14038.html create mode 100644 docs/mrs/umn/ALM-14039.html create mode 100644 docs/mrs/umn/ALM-16051.html create mode 100644 docs/mrs/umn/ALM-16052.html create mode 100644 docs/mrs/umn/ALM-16053.html create mode 100644 docs/mrs/umn/ALM-17008.html create mode 100644 docs/mrs/umn/ALM-17009.html create mode 100644 docs/mrs/umn/ALM-17010.html create mode 100644 docs/mrs/umn/ALM-17011.html create mode 100644 docs/mrs/umn/ALM-19030.html create mode 100644 docs/mrs/umn/ALM-19031.html create mode 100644 docs/mrs/umn/ALM-19032.html create mode 100644 docs/mrs/umn/ALM-19033.html create mode 100644 docs/mrs/umn/ALM-19034.html create mode 100644 docs/mrs/umn/ALM-19035.html create mode 100644 docs/mrs/umn/ALM-19036.html create mode 100644 docs/mrs/umn/ALM-38012.html create mode 100644 docs/mrs/umn/ALM-38013.html create mode 100644 docs/mrs/umn/ALM-38014.html create mode 100644 docs/mrs/umn/ALM-38015.html create mode 100644 docs/mrs/umn/ALM-38016.html create mode 100644 docs/mrs/umn/ALM-38017.html create mode 100644 docs/mrs/umn/ALM-38018.html create mode 100644 docs/mrs/umn/ALM-43028.html create mode 100644 docs/mrs/umn/ALM-43029.html create mode 100644 docs/mrs/umn/ALM-45004.html create mode 100644 docs/mrs/umn/ALM-45005.html create mode 100644 docs/mrs/umn/ALM-45006.html create mode 100644 docs/mrs/umn/ALM-45007.html create mode 100644 docs/mrs/umn/ALM-45008.html create mode 100644 docs/mrs/umn/ALM-45009.html create mode 100644 docs/mrs/umn/ALM-45293.html create mode 100644 docs/mrs/umn/ALM-45294.html create mode 100644 docs/mrs/umn/ALM-45445.html create mode 100644 docs/mrs/umn/ALM-45446.html create mode 100644 docs/mrs/umn/ALM-45447.html create mode 100644 docs/mrs/umn/ALM-45448.html create mode 100644 docs/mrs/umn/ALM-45449.html create mode 100644 docs/mrs/umn/ALM-45450.html create mode 100644 docs/mrs/umn/ALM-45451.html create mode 100644 docs/mrs/umn/ALM-45452.html create mode 100644 docs/mrs/umn/ALM-45475.html create mode 100644 docs/mrs/umn/ALM-45476.html create mode 100644 docs/mrs/umn/ALM-45477.html create mode 100644 docs/mrs/umn/ALM-45478.html create mode 100644 docs/mrs/umn/ALM-45479.html create mode 100644 docs/mrs/umn/ALM-45480.html create mode 100644 docs/mrs/umn/ALM-45481.html create mode 100644 docs/mrs/umn/ALM-45744.html create mode 100644 docs/mrs/umn/ALM-45745.html create mode 100644 docs/mrs/umn/ALM-47001.html create mode 100644 docs/mrs/umn/ALM-47002.html create mode 100644 docs/mrs/umn/ALM-47003.html create mode 100644 docs/mrs/umn/ALM-47004.html create mode 100644 docs/mrs/umn/ALM-50227.html create mode 100644 docs/mrs/umn/ALM-50228.html create mode 100644 docs/mrs/umn/ALM-50229.html create mode 100644 docs/mrs/umn/ALM-50230.html create mode 100644 docs/mrs/umn/ALM-50231.html create mode 100644 docs/mrs/umn/ALM-50232.html create mode 100644 docs/mrs/umn/ALM-50406.html create mode 100644 docs/mrs/umn/ALM-50407.html create mode 100644 docs/mrs/umn/ALM-50408.html create mode 100644 docs/mrs/umn/admin_guide_000420.html create mode 100644 docs/mrs/umn/admin_guide_000423.html create mode 100644 docs/mrs/umn/admin_guide_000424.html create mode 100644 docs/mrs/umn/admin_guide_000427.html delete mode 100644 docs/mrs/umn/en-us_image_0000001392574002.png delete mode 100644 docs/mrs/umn/en-us_image_0000001532607778.png delete mode 100644 docs/mrs/umn/en-us_image_0000001583087429.png create mode 100644 docs/mrs/umn/en-us_image_0000002379936846.png create mode 100644 docs/mrs/umn/en-us_image_0000002380008412.png create mode 100644 docs/mrs/umn/en-us_image_0000002380310204.png create mode 100644 docs/mrs/umn/en-us_image_0000002380470068.png create mode 100644 docs/mrs/umn/en-us_image_0000002380470088.png create mode 100644 docs/mrs/umn/en-us_image_0000002381596168.png create mode 100644 docs/mrs/umn/en-us_image_0000002381622762.png create mode 100644 docs/mrs/umn/en-us_image_0000002381622794.png create mode 100644 docs/mrs/umn/en-us_image_0000002381782666.png create mode 100644 docs/mrs/umn/en-us_image_0000002381782678.png create mode 100644 docs/mrs/umn/en-us_image_0000002382274158.png create mode 100644 docs/mrs/umn/en-us_image_0000002382293908.png create mode 100644 docs/mrs/umn/en-us_image_0000002382434022.png create mode 100644 docs/mrs/umn/en-us_image_0000002382453800.png create mode 100644 docs/mrs/umn/en-us_image_0000002413536053.png create mode 100644 docs/mrs/umn/en-us_image_0000002413647801.png create mode 100644 docs/mrs/umn/en-us_image_0000002413688652.png create mode 100644 docs/mrs/umn/en-us_image_0000002413843108.png create mode 100644 docs/mrs/umn/en-us_image_0000002413848564.png create mode 100644 docs/mrs/umn/en-us_image_0000002413949605.png create mode 100644 docs/mrs/umn/en-us_image_0000002414069433.png create mode 100644 docs/mrs/umn/en-us_image_0000002414069445.png create mode 100644 docs/mrs/umn/en-us_image_0000002415261981.png create mode 100644 docs/mrs/umn/en-us_image_0000002415262005.png create mode 100644 docs/mrs/umn/en-us_image_0000002415342137.png create mode 100644 docs/mrs/umn/en-us_image_0000002415342161.png create mode 100644 docs/mrs/umn/en-us_image_0000002415833501.png create mode 100644 docs/mrs/umn/en-us_image_0000002415853277.png create mode 100644 docs/mrs/umn/en-us_image_0000002415993313.png create mode 100644 docs/mrs/umn/en-us_image_0000002416013105.png create mode 100644 docs/mrs/umn/en-us_image_0000002447362249.png create mode 100644 docs/mrs/umn/en-us_image_0000002447402305.png create mode 100644 docs/mrs/umn/mrs_08_0038.html create mode 100644 docs/mrs/umn/mrs_08_0039.html create mode 100644 docs/mrs/umn/mrs_08_0116.html create mode 100644 docs/mrs/umn/mrs_08_0117.html create mode 100644 docs/mrs/umn/mrs_08_0118.html diff --git a/docs/mrs/umn/.placeholder b/docs/mrs/umn/.placeholder deleted file mode 100644 index e69de29bb..000000000 diff --git a/docs/mrs/umn/ALL_META.TXT.json b/docs/mrs/umn/ALL_META.TXT.json index 41c28f265..057ce8218 100644 --- a/docs/mrs/umn/ALL_META.TXT.json +++ b/docs/mrs/umn/ALL_META.TXT.json @@ -973,11 +973,29 @@ "title":"Hue Enhanced Open Source Features", "githuburl":"" }, + { + "uri":"mrs_08_0038.html", + "node_id":"mrs_08_0038.xml", + "product_code":"mrs", + "code":"55", + "des":"Impala provides fast, interactive SQL queries directly on your Apache Hadoop data stored in HDFS, HBase, or the Object Storage Service (OBS). In addition to using the sam", + "doc_type":"usermanual", + "kw":"Impala,Components,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"mrs", + "documenttype":"usermanual" + } + ], + "title":"Impala", + "githuburl":"" + }, { "uri":"mrs_08_0093.html", "node_id":"mrs_08_0093.xml", "product_code":"mrs", - "code":"55", + "code":"56", "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":"IoTDB", @@ -995,7 +1013,7 @@ "uri":"mrs_08_0094.html", "node_id":"mrs_08_0094.xml", "product_code":"mrs", - "code":"56", + "code":"57", "des":"Database for Internet of Things (IoTDB) is a software system that collects, stores, manages, and analyzes IoT time series data. Apache IoTDB uses a lightweight architectu", "doc_type":"usermanual", "kw":"IoTDB Basic Principles,IoTDB,User Guide", @@ -1013,7 +1031,7 @@ "uri":"mrs_08_0095.html", "node_id":"mrs_08_0095.xml", "product_code":"mrs", - "code":"57", + "code":"58", "des":"The IoTDB stores data locally, so it does not depend on any other component for storage. However, in a security cluster environment, IoTDB depends on the KrbServer compon", "doc_type":"usermanual", "kw":"Relationship Between IoTDB and Other Components,IoTDB,User Guide", @@ -1031,7 +1049,7 @@ "uri":"mrs_08_0096.html", "node_id":"mrs_08_0096.xml", "product_code":"mrs", - "code":"58", + "code":"59", "des":"Visualized O&M covers installation, uninstallation, one-click start and stop, configurations, clients, monitoring, alarms, health checks, and logs.Visualized permission m", "doc_type":"usermanual", "kw":"IoTDB Enhanced Open Source Features,IoTDB,User Guide", @@ -1049,7 +1067,7 @@ "uri":"mrs_08_0149.html", "node_id":"mrs_08_0149.xml", "product_code":"", - "code":"59", + "code":"60", "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":"JobGateway", @@ -1066,7 +1084,7 @@ "uri":"mrs_08_0150.html", "node_id":"mrs_08_0150.xml", "product_code":"", - "code":"60", + "code":"61", "des":"JobGateway allows you to submit jobs through REST APIs.As a gateway component for submitting big data jobs, JobGateway provides fully controllable enterprise-level big da", "doc_type":"", "kw":"JobGateway Basic Principles,JobGateway,User Guide", @@ -1083,7 +1101,7 @@ "uri":"mrs_08_0152.html", "node_id":"mrs_08_0152.xml", "product_code":"", - "code":"61", + "code":"62", "des":"JobGateway is a service that allows you to submit Spark, Hive, MapReduce, and Flink jobs through REST APIs.", "doc_type":"", "kw":"Relationships Between JobGateway and Other Components,JobGateway,User Guide", @@ -1100,7 +1118,7 @@ "uri":"mrs_08_0013.html", "node_id":"mrs_08_0013.xml", "product_code":"mrs", - "code":"62", + "code":"63", "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":"Kafka", @@ -1118,7 +1136,7 @@ "uri":"mrs_08_00131.html", "node_id":"mrs_08_00131.xml", "product_code":"mrs", - "code":"63", + "code":"64", "des":"Kafka is an open source, distributed, partitioned, and replicated commit log service. Kafka is publish-subscribe messaging, rethought as a distributed commit log. It prov", "doc_type":"usermanual", "kw":"Kafka Basic Principles,Kafka,User Guide", @@ -1136,8 +1154,8 @@ "uri":"mrs_08_00132.html", "node_id":"mrs_08_00132.xml", "product_code":"mrs", - "code":"64", - "des":"As a message publishing and subscription system, Kafka provides high-speed data transmission methods for data transmission between different subsystems of the FusionInsig", + "code":"65", + "des":"As a message publishing and subscription system, Kafka provides high-speed data transmission methods for data transmission between different subsystems of the platform. I", "doc_type":"usermanual", "kw":"Relationship Between Kafka and Other Components,Kafka,User Guide", "search_title":"", @@ -1154,7 +1172,7 @@ "uri":"mrs_08_00133.html", "node_id":"mrs_08_00133.xml", "product_code":"mrs", - "code":"65", + "code":"66", "des":"Monitors the following topic-level metrics:Topic Input TrafficTopic Output TrafficTopic Rejected TrafficNumber of Failed Fetch Requests Per SecondNumber of Failed Produce", "doc_type":"usermanual", "kw":"Kafka Enhanced Open Source Features,Kafka,User Guide", @@ -1172,7 +1190,7 @@ "uri":"mrs_08_0032.html", "node_id":"mrs_08_0032.xml", "product_code":"mrs", - "code":"66", + "code":"67", "des":"KafkaManager is a tool for managing Apache Kafka and provides GUI-based metric monitoring and management of Kafka clusters.KafkaManager supports the following operations:", "doc_type":"usermanual", "kw":"KafkaManager,Components,User Guide", @@ -1190,7 +1208,7 @@ "uri":"mrs_08_0064.html", "node_id":"mrs_08_0064.xml", "product_code":"mrs", - "code":"67", + "code":"68", "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":"KrbServer and LdapServer", @@ -1208,7 +1226,7 @@ "uri":"mrs_08_00641.html", "node_id":"mrs_08_00641.xml", "product_code":"mrs", - "code":"68", + "code":"69", "des":"To manage the access control permissions on data and resources in a cluster, it is recommended that the cluster be installed in security mode. In security mode, a client ", "doc_type":"usermanual", "kw":"KrbServer and LdapServer Principles,KrbServer and LdapServer,User Guide", @@ -1226,7 +1244,7 @@ "uri":"mrs_08_00642.html", "node_id":"mrs_08_00642.xml", "product_code":"mrs", - "code":"69", + "code":"70", "des":"In an MRS cluster that uses the security mode, mutual access between services is implemented based on the Kerberos security architecture. When a service (such as HDFS) in", "doc_type":"usermanual", "kw":"KrbServer and LdapServer Enhanced Open Source Features,KrbServer and LdapServer,User Guide", @@ -1240,11 +1258,29 @@ "title":"KrbServer and LdapServer Enhanced Open Source Features", "githuburl":"" }, + { + "uri":"mrs_08_0039.html", + "node_id":"mrs_08_0039.xml", + "product_code":"mrs", + "code":"71", + "des":"Kudu is a column-store manager developed for the Apache Hadoop platform. Kudu shares the common technical properties of Hadoop ecosystem applications, that is, it runs on", + "doc_type":"usermanual", + "kw":"Kudu,Components,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"mrs", + "documenttype":"usermanual" + } + ], + "title":"Kudu", + "githuburl":"" + }, { "uri":"mrs_08_0017.html", "node_id":"mrs_08_0017.xml", "product_code":"mrs", - "code":"70", + "code":"72", "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":"Loader", @@ -1262,7 +1298,7 @@ "uri":"mrs_08_00171.html", "node_id":"mrs_08_00171.xml", "product_code":"mrs", - "code":"71", + "code":"73", "des":"Loader is developed based on the open source Sqoop component. It is used to exchange data and files between MRS and relational databases and file systems. Loader can impo", "doc_type":"usermanual", "kw":"Loader Basic Principles,Loader,User Guide", @@ -1280,7 +1316,7 @@ "uri":"mrs_08_00172.html", "node_id":"mrs_08_00172.xml", "product_code":"mrs", - "code":"72", + "code":"74", "des":"The components that interact with Loader include HDFS, HBase, MapReduce, and ZooKeeper. Loader works as a client to use certain functions of these components, such as sto", "doc_type":"usermanual", "kw":"Relationship Between Loader and Other Components,Loader,User Guide", @@ -1298,7 +1334,7 @@ "uri":"mrs_08_00173.html", "node_id":"mrs_08_00173.xml", "product_code":"mrs", - "code":"73", + "code":"75", "des":"Loader is developed based on Sqoop. In addition to the Sqoop functions, Loader has the following enhanced features:Provides data conversion functions.Supports GUI-based c", "doc_type":"usermanual", "kw":"Loader Enhanced Open Source Features,Loader,User Guide", @@ -1316,7 +1352,7 @@ "uri":"mrs_08_0066.html", "node_id":"mrs_08_0066.xml", "product_code":"mrs", - "code":"74", + "code":"76", "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":"Manager", @@ -1334,7 +1370,7 @@ "uri":"mrs_08_00661.html", "node_id":"mrs_08_00661.xml", "product_code":"mrs", - "code":"75", + "code":"77", "des":"Manager is the O&M management system of MRS and provides unified cluster management capabilities for services deployed in clusters.Manager provides functions such as perf", "doc_type":"usermanual", "kw":"Manager Basic Principles,Manager,User Guide", @@ -1352,7 +1388,7 @@ "uri":"mrs_08_00662.html", "node_id":"mrs_08_00662.xml", "product_code":"mrs", - "code":"76", + "code":"78", "des":"Manager provides the visualized and convenient alarm monitoring function. Users can quickly obtain key cluster performance indicators, evaluate cluster health status, cus", "doc_type":"usermanual", "kw":"Manager Key Features,Manager,User Guide", @@ -1370,7 +1406,7 @@ "uri":"mrs_08_0050.html", "node_id":"mrs_08_0050.xml", "product_code":"mrs", - "code":"77", + "code":"79", "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":"MapReduce", @@ -1388,7 +1424,7 @@ "uri":"mrs_08_00501.html", "node_id":"mrs_08_00501.xml", "product_code":"mrs", - "code":"78", + "code":"80", "des":"MapReduce is the core of Hadoop. As a software architecture proposed by Google, MapReduce is used for parallel computing of large-scale datasets (larger than 1 TB). The c", "doc_type":"usermanual", "kw":"MapReduce Basic Principles,MapReduce,User Guide", @@ -1406,7 +1442,7 @@ "uri":"mrs_08_00502.html", "node_id":"mrs_08_00502.xml", "product_code":"mrs", - "code":"79", + "code":"81", "des":"HDFS features high fault tolerance and high throughput, and can be deployed on low-cost hardware for storing data of applications with massive data sets.MapReduce is a pr", "doc_type":"usermanual", "kw":"Relationship Between MapReduce and Other Components,MapReduce,User Guide", @@ -1424,7 +1460,7 @@ "uri":"mrs_08_00503.html", "node_id":"mrs_08_00503.xml", "product_code":"mrs", - "code":"80", + "code":"82", "des":"JobHistoryServer (JHS) is the server used to view historical MapReduce task information. Currently, the open source JHS supports only single-instance services. JHS HA can", "doc_type":"usermanual", "kw":"MapReduce Enhanced Open Source Features,MapReduce,User Guide", @@ -1438,11 +1474,62 @@ "title":"MapReduce Enhanced Open Source Features", "githuburl":"" }, + { + "uri":"mrs_08_0116.html", + "node_id":"mrs_08_0116.xml", + "product_code":"", + "code":"83", + "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":"MemArtsCC", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"MemArtsCC", + "githuburl":"" + }, + { + "uri":"mrs_08_0117.html", + "node_id":"mrs_08_0117.xml", + "product_code":"", + "code":"84", + "des":"MemArtsCC is a distributed lightweight caching system deployed on the compute side in the storage-compute decoupled architecture. It prefetches data from remote object st", + "doc_type":"", + "kw":"MemArtsCC Basic Principles,MemArtsCC,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"MemArtsCC Basic Principles", + "githuburl":"" + }, + { + "uri":"mrs_08_0118.html", + "node_id":"mrs_08_0118.xml", + "product_code":"", + "code":"85", + "des":"OBS provides a new InputStream: OBSMemArtsCCInputStream. This InputStream reads data from the MemArtsCC cluster deployed on the compute side to reduce OBS server pressure", + "doc_type":"", + "kw":"Relationships Between MemArtsCC and Other Components,MemArtsCC,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Relationships Between MemArtsCC and Other Components", + "githuburl":"" + }, { "uri":"mrs_08_0067.html", "node_id":"mrs_08_0067.xml", "product_code":"mrs", - "code":"81", + "code":"86", "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":"Oozie", @@ -1460,7 +1547,7 @@ "uri":"mrs_08_00671.html", "node_id":"mrs_08_00671.xml", "product_code":"mrs", - "code":"82", + "code":"87", "des":"Oozie is an open-source workflow engine that is used to schedule and coordinate Hadoop jobs.The Oozie engine is a web application integrated into Tomcat by default. Oozie", "doc_type":"usermanual", "kw":"Oozie Basic Principles,Oozie,User Guide", @@ -1478,7 +1565,7 @@ "uri":"mrs_08_00672.html", "node_id":"mrs_08_00672.xml", "product_code":"mrs", - "code":"83", + "code":"88", "des":"Provides roles of administrator and common users to support Oozie permission management.Supports single sign-on and sign-out, HTTPS access, and audit logs.", "doc_type":"usermanual", "kw":"Oozie Enhanced Open Source Features,Oozie,User Guide", @@ -1496,7 +1583,7 @@ "uri":"mrs_08_0035.html", "node_id":"mrs_08_0035.xml", "product_code":"mrs", - "code":"84", + "code":"89", "des":"OpenTSDB is a distributed, scalable time series database based on HBase. OpenTSDB is designed to collect monitoring information of a large-scale cluster and implement sec", "doc_type":"usermanual", "kw":"OpenTSDB,Components,User Guide", @@ -1514,7 +1601,7 @@ "uri":"mrs_08_0031.html", "node_id":"mrs_08_0031.xml", "product_code":"mrs", - "code":"85", + "code":"90", "des":"Presto is an open source SQL query engine for running interactive analytic queries against data sources of all sizes. It applies to massive structured/semi-structured dat", "doc_type":"usermanual", "kw":"Presto,Components,User Guide", @@ -1532,7 +1619,7 @@ "uri":"mrs_08_0041.html", "node_id":"mrs_08_0041.xml", "product_code":"mrs", - "code":"86", + "code":"91", "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":"Ranger", @@ -1550,7 +1637,7 @@ "uri":"mrs_08_00411.html", "node_id":"mrs_08_00411.xml", "product_code":"mrs", - "code":"87", + "code":"92", "des":"Apache Ranger offers a centralized security management framework and supports unified authorization and auditing. It manages fine grained access control over Hadoop and r", "doc_type":"usermanual", "kw":"Ranger Basic Principles,Ranger,User Guide", @@ -1568,7 +1655,7 @@ "uri":"mrs_08_004102.html", "node_id":"mrs_08_004102.xml", "product_code":"mrs", - "code":"88", + "code":"93", "des":"Ranger provides PABC-based authentication plug-ins for components to run on their servers. Ranger currently supports authentication for the following components like HDFS", "doc_type":"usermanual", "kw":"Relationship Between Ranger and Other Components,Ranger,User Guide", @@ -1586,7 +1673,7 @@ "uri":"mrs_08_0008.html", "node_id":"mrs_08_0008.xml", "product_code":"mrs", - "code":"89", + "code":"94", "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":"Spark", @@ -1604,7 +1691,7 @@ "uri":"mrs_08_00081.html", "node_id":"mrs_08_00081.xml", "product_code":"mrs", - "code":"90", + "code":"95", "des":"The Spark component applies to versions earlier than MRS 3.x.Spark is an open source parallel data processing framework. It helps you easily develop unified big data appl", "doc_type":"usermanual", "kw":"Basic Principles of Spark,Spark,User Guide", @@ -1622,7 +1709,7 @@ "uri":"mrs_08_00082.html", "node_id":"mrs_08_00082.xml", "product_code":"mrs", - "code":"91", + "code":"96", "des":"Based on existing JDBCServer in the community, multi-active-instance mode is used to achieve HA. In this mode, multiple JDBCServers coexist in the cluster and the client ", "doc_type":"usermanual", "kw":"Spark HA Solution,Spark,User Guide", @@ -1640,7 +1727,7 @@ "uri":"mrs_08_00083.html", "node_id":"mrs_08_00083.xml", "product_code":"mrs", - "code":"92", + "code":"97", "des":"Data computed by Spark comes from multiple data sources, such as local files and HDFS. Most data computed by Spark comes from the HDFS. The HDFS can read data in large sc", "doc_type":"usermanual", "kw":"Relationship Among Spark, HDFS, and Yarn,Spark,User Guide", @@ -1658,7 +1745,7 @@ "uri":"mrs_08_00084.html", "node_id":"mrs_08_00084.xml", "product_code":"mrs", - "code":"93", + "code":"98", "des":"Enterprises usually store massive data, such as from various databases and warehouses, for management and information collection. However, diversified data sources, hybri", "doc_type":"usermanual", "kw":"Spark Enhanced Open Source Feature: Optimized SQL Query of Cross-Source Data,Spark,User Guide", @@ -1676,7 +1763,7 @@ "uri":"mrs_08_0071.html", "node_id":"mrs_08_0071.xml", "product_code":"mrs", - "code":"94", + "code":"99", "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":"Spark2x", @@ -1694,7 +1781,7 @@ "uri":"mrs_08_007101.html", "node_id":"mrs_08_007101.xml", "product_code":"mrs", - "code":"95", + "code":"100", "des":"The Spark2x component applies to MRS 3.x and later versions.Spark is a memory-based distributed computing framework. In iterative computation scenarios, the computing cap", "doc_type":"usermanual", "kw":"Basic Principles of Spark2x,Spark2x,User Guide", @@ -1712,7 +1799,7 @@ "uri":"mrs_08_007102.html", "node_id":"mrs_08_007102.xml", "product_code":"mrs", - "code":"96", + "code":"101", "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":"Spark2x HA Solution", @@ -1730,7 +1817,7 @@ "uri":"mrs_08_007103.html", "node_id":"mrs_08_007103.xml", "product_code":"mrs", - "code":"97", + "code":"102", "des":"Based on existing JDBCServers in the community, multi-active-instance HA is used to achieve the high availability. In this mode, multiple JDBCServers coexist in the clust", "doc_type":"usermanual", "kw":"Spark2x Multi-active Instance,Spark2x HA Solution,User Guide", @@ -1748,7 +1835,7 @@ "uri":"mrs_08_007104.html", "node_id":"mrs_08_007104.xml", "product_code":"mrs", - "code":"98", + "code":"103", "des":"In the JDBCServer multi-active instance mode, JDBCServer implements the Yarn-client mode but only one Yarn resource queue is available. To solve the resource limitation p", "doc_type":"usermanual", "kw":"Spark2x Multi-tenant,Spark2x HA Solution,User Guide", @@ -1766,7 +1853,7 @@ "uri":"mrs_08_007105.html", "node_id":"mrs_08_007105.xml", "product_code":"mrs", - "code":"99", + "code":"104", "des":"Data computed by Spark comes from multiple data sources, such as local files and HDFS. Most data comes from HDFS which can read data in large scale for parallel computing", "doc_type":"usermanual", "kw":"Relationship Between Spark2x and Other Components,Spark2x,User Guide", @@ -1784,7 +1871,7 @@ "uri":"mrs_08_007106.html", "node_id":"mrs_08_007106.xml", "product_code":"mrs", - "code":"100", + "code":"105", "des":"Compared with Spark 1.5, Spark2x has some new open-source features. The specific features or concepts are as follows:DataSet: For details, see SparkSQL and DataSet Princi", "doc_type":"usermanual", "kw":"Spark2x Open Source New Features,Spark2x,User Guide", @@ -1802,7 +1889,7 @@ "uri":"mrs_08_007107.html", "node_id":"mrs_08_007107.xml", "product_code":"mrs", - "code":"101", + "code":"106", "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":"Spark2x Enhanced Open Source Features", @@ -1820,7 +1907,7 @@ "uri":"mrs_08_007108.html", "node_id":"mrs_08_007108.xml", "product_code":"mrs", - "code":"102", + "code":"107", "des":"CarbonData is a new Apache Hadoop native data-store format. CarbonData allows faster interactive queries over PetaBytes of data using advanced columnar storage, index, co", "doc_type":"usermanual", "kw":"CarbonData Overview,Spark2x Enhanced Open Source Features,User Guide", @@ -1838,7 +1925,7 @@ "uri":"mrs_08_007109.html", "node_id":"mrs_08_007109.xml", "product_code":"mrs", - "code":"103", + "code":"108", "des":"Enterprises usually store massive data, such as from various databases and warehouses, for management and information collection. However, diversified data sources, hybri", "doc_type":"usermanual", "kw":"Optimizing SQL Query of Data of Multiple Sources,Spark2x Enhanced Open Source Features,User Guide", @@ -1856,7 +1943,7 @@ "uri":"mrs_08_0014.html", "node_id":"mrs_08_0014.xml", "product_code":"mrs", - "code":"104", + "code":"109", "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":"Storm", @@ -1874,7 +1961,7 @@ "uri":"mrs_08_00141.html", "node_id":"mrs_08_00141.xml", "product_code":"mrs", - "code":"105", + "code":"110", "des":"Apache Storm is a distributed, reliable, and fault-tolerant real-time stream data processing system. In Storm, a graph-shaped data structure called topology needs to be d", "doc_type":"usermanual", "kw":"Storm Basic Principles,Storm,User Guide", @@ -1892,7 +1979,7 @@ "uri":"mrs_08_00142.html", "node_id":"mrs_08_00142.xml", "product_code":"mrs", - "code":"106", + "code":"111", "des":"Storm provides a real-time distributed computing framework. It can obtain real-time messages from data sources (such as Kafka and TCP connection), perform high-throughput", "doc_type":"usermanual", "kw":"Relationship Between Storm and Other Components,Storm,User Guide", @@ -1910,7 +1997,7 @@ "uri":"mrs_08_00143.html", "node_id":"mrs_08_00143.xml", "product_code":"mrs", - "code":"107", + "code":"112", "des":"CQLContinuous Query Language (CQL) is an SQL-like language used for real-time stream processing. Compared with SQL, CQL has introduced the concept of (time-sequencing) wi", "doc_type":"usermanual", "kw":"Storm Enhanced Open Source Features,Storm,User Guide", @@ -1928,7 +2015,7 @@ "uri":"mrs_08_0030.html", "node_id":"mrs_08_0030.xml", "product_code":"mrs", - "code":"108", + "code":"113", "des":"Tez is Apache's latest open source computing framework that supports Directed Acyclic Graph (DAG) jobs. It can convert multiple dependent jobs into one job, greatly impro", "doc_type":"usermanual", "kw":"Tez,Components,User Guide", @@ -1946,7 +2033,7 @@ "uri":"mrs_08_0051.html", "node_id":"mrs_08_0051.xml", "product_code":"mrs", - "code":"109", + "code":"114", "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":"Yarn", @@ -1964,7 +2051,7 @@ "uri":"mrs_08_00511.html", "node_id":"mrs_08_00511.xml", "product_code":"mrs", - "code":"110", + "code":"115", "des":"The Apache open source community introduces the unified resource management framework Yarn to share Hadoop clusters, improve their scalability and reliability, and elimin", "doc_type":"usermanual", "kw":"Yarn Basic Principles,Yarn,User Guide", @@ -1982,7 +2069,7 @@ "uri":"mrs_08_00512.html", "node_id":"mrs_08_00512.xml", "product_code":"mrs", - "code":"111", + "code":"116", "des":"ResourceManager in Yarn manages resources and schedules tasks in the cluster. In versions earlier than Hadoop 2.4, SPOFs may occur on ResourceManager in the Yarn cluster.", "doc_type":"usermanual", "kw":"Yarn HA Solution,Yarn,User Guide", @@ -2000,7 +2087,7 @@ "uri":"mrs_08_00513.html", "node_id":"mrs_08_00513.xml", "product_code":"mrs", - "code":"112", + "code":"117", "des":"The Spark computing and scheduling can be implemented using YARN mode. Spark enjoys the compute resources provided by YARN clusters and runs tasks in a distributed way. S", "doc_type":"usermanual", "kw":"Relationship Between YARN and Other Components,Yarn,User Guide", @@ -2018,7 +2105,7 @@ "uri":"mrs_08_00514.html", "node_id":"mrs_08_00514.xml", "product_code":"mrs", - "code":"113", + "code":"118", "des":"In the native Yarn resource scheduling mechanism, if the whole Hadoop cluster resources are occupied by those MapReduce jobs submitted earlier, jobs submitted later will ", "doc_type":"usermanual", "kw":"Yarn Enhanced Open Source Features,Yarn,User Guide", @@ -2036,7 +2123,7 @@ "uri":"mrs_08_0070.html", "node_id":"mrs_08_0070.xml", "product_code":"mrs", - "code":"114", + "code":"119", "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":"ZooKeeper", @@ -2054,7 +2141,7 @@ "uri":"mrs_08_00701.html", "node_id":"mrs_08_00701.xml", "product_code":"mrs", - "code":"115", + "code":"120", "des":"ZooKeeper is a distributed, highly available coordination service. ZooKeeper provides two functions:Prevents the system from single point of failures (SPOFs) and provides", "doc_type":"usermanual", "kw":"ZooKeeper Basic Principle,ZooKeeper,User Guide", @@ -2072,7 +2159,7 @@ "uri":"mrs_08_00702.html", "node_id":"mrs_08_00702.xml", "product_code":"mrs", - "code":"116", + "code":"121", "des":"Figure 1 shows the relationship between ZooKeeper and HDFS.As the client of a ZooKeeper cluster, ZKFailoverController (ZKFC) monitors the status of NameNode. ZKFC is depl", "doc_type":"usermanual", "kw":"Relationship Between ZooKeeper and Other Components,ZooKeeper,User Guide", @@ -2090,7 +2177,7 @@ "uri":"mrs_08_00703.html", "node_id":"mrs_08_00703.xml", "product_code":"mrs", - "code":"117", + "code":"122", "des":"In security mode, an ephemeral node is deleted as long as the session that created the node expires. Ephemeral node deletion is recorded in audit logs so that ephemeral n", "doc_type":"usermanual", "kw":"ZooKeeper Enhanced Open Source Features,ZooKeeper,User Guide", @@ -2108,7 +2195,7 @@ "uri":"mrs_08_0006.html", "node_id":"mrs_08_0006.xml", "product_code":"mrs", - "code":"118", + "code":"123", "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":"Functions", @@ -2126,7 +2213,7 @@ "uri":"mrs_08_0042.html", "node_id":"mrs_08_0042.xml", "product_code":"mrs", - "code":"119", + "code":"124", "des":"Modern enterprises' data clusters are developing towards centralization and cloudification. Enterprise-class big data clusters must meet the following requirements:Carry ", "doc_type":"usermanual", "kw":"Multi-tenant,Functions,User Guide", @@ -2144,7 +2231,7 @@ "uri":"mrs_08_0043.html", "node_id":"mrs_08_0043.xml", "product_code":"mrs", - "code":"120", + "code":"125", "des":"MRS is a platform for massive data management and analysis and has high security. MRS protects user data and service running from the following aspects:Network isolationT", "doc_type":"usermanual", "kw":"Security Hardening,Functions,User Guide", @@ -2162,7 +2249,7 @@ "uri":"mrs_08_0044.html", "node_id":"mrs_08_0044.xml", "product_code":"mrs", - "code":"121", + "code":"126", "des":"Big data components have their own web UIs to manage their own systems. However, you cannot easily access the web UIs due to network isolation. For example, to access the", "doc_type":"usermanual", "kw":"Easy Access to Web UIs of Components,Functions,User Guide", @@ -2180,7 +2267,7 @@ "uri":"mrs_08_0045.html", "node_id":"mrs_08_0045.xml", "product_code":"mrs", - "code":"122", + "code":"127", "des":"Based on Apache Hadoop open source software, MRS optimizes and improves the reliability and performance of main service components.HA for all management nodesIn the Hadoo", "doc_type":"usermanual", "kw":"Reliability Enhancement,Functions,User Guide", @@ -2198,7 +2285,7 @@ "uri":"mrs_08_0046.html", "node_id":"mrs_08_0046.xml", "product_code":"mrs", - "code":"123", + "code":"128", "des":"The job management function provides an entry for you to submit jobs in a cluster, including MapReduce, Spark, HiveQL, and SparkSQL jobs. MRS works with Data Lake Governa", "doc_type":"usermanual", "kw":"Job Management,Functions,User Guide", @@ -2216,7 +2303,7 @@ "uri":"mrs_08_0025.html", "node_id":"mrs_08_0025.xml", "product_code":"mrs", - "code":"124", + "code":"129", "des":"MRS provides standard elastic big data clusters on the cloud. Nine big data components, such as Hadoop and Spark, can be installed and deployed. Currently, standard cloud", "doc_type":"usermanual", "kw":"Bootstrap Actions,Functions,User Guide", @@ -2234,7 +2321,7 @@ "uri":"mrs_08_0075.html", "node_id":"mrs_08_0075.xml", "product_code":"mrs", - "code":"125", + "code":"130", "des":"MRS provides multiple metadata storage methods. When deploying Hive and Ranger during MRS cluster creation, select one of the following storage modes as required:Local: M", "doc_type":"usermanual", "kw":"Metadata,Functions,User Guide", @@ -2252,7 +2339,7 @@ "uri":"mrs_08_0048.html", "node_id":"mrs_08_0048.xml", "product_code":"mrs", - "code":"126", + "code":"131", "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", @@ -2270,7 +2357,7 @@ "uri":"mrs_08_0053.html", "node_id":"mrs_08_0053.xml", "product_code":"mrs", - "code":"127", + "code":"132", "des":"MRS supports cluster lifecycle management, including creating and terminating clusters.Creating a cluster: After you specify a cluster type, components, number of nodes o", "doc_type":"usermanual", "kw":"Cluster Lifecycle Management,Cluster Management,User Guide", @@ -2288,7 +2375,7 @@ "uri":"mrs_08_0054.html", "node_id":"mrs_08_0054.xml", "product_code":"mrs", - "code":"128", + "code":"133", "des":"The processing capability of a big data cluster can be horizontally expanded by adding nodes. If the cluster scale does not meet service requirements, you can manually sc", "doc_type":"usermanual", "kw":"Manually Scale Out/In a Cluster,Cluster Management,User Guide", @@ -2306,7 +2393,7 @@ "uri":"mrs_08_0022.html", "node_id":"mrs_08_0022.xml", "product_code":"mrs", - "code":"129", + "code":"134", "des":"More and more enterprises use technologies such as Spark and Hive to analyze data. Processing a large amount of data consumes huge resources and costs much. Typically, en", "doc_type":"usermanual", "kw":"Auto Scaling,Cluster Management,User Guide", @@ -2324,7 +2411,7 @@ "uri":"mrs_08_0023.html", "node_id":"mrs_08_0023.xml", "product_code":"mrs", - "code":"130", + "code":"135", "des":"Task nodes can be created and used for computing only. They do not store persistent data and are the basis for implementing auto scaling.When MRS is used only as a comput", "doc_type":"usermanual", "kw":"Task Node Creation,Cluster Management,User Guide", @@ -2342,7 +2429,7 @@ "uri":"mrs_08_0056.html", "node_id":"mrs_08_0056.xml", "product_code":"mrs", - "code":"131", + "code":"136", "des":"When detecting that a host is abnormal or faulty and cannot provide services or affects cluster performance, you can exclude the host from the available nodes in the clus", "doc_type":"usermanual", "kw":"Isolating a Host,Cluster Management,User Guide", @@ -2360,7 +2447,7 @@ "uri":"mrs_08_0057.html", "node_id":"mrs_08_0057.xml", "product_code":"mrs", - "code":"132", + "code":"137", "des":"Tags are cluster identifiers. Adding tags to clusters can help you identify and manage your cluster resources. By associating with Tag Management Service (TMS), MRS allow", "doc_type":"usermanual", "kw":"Managing Tags,Cluster Management,User Guide", @@ -2378,7 +2465,7 @@ "uri":"mrs_08_0049.html", "node_id":"mrs_08_0049.xml", "product_code":"mrs", - "code":"133", + "code":"138", "des":"MRS can monitor big data clusters in real time and identify system health status based on alarms and events. In addition, MRS allows you to customize monitoring and alarm", "doc_type":"usermanual", "kw":"Cluster O&M,Functions,User Guide", @@ -2396,7 +2483,7 @@ "uri":"mrs_08_0024.html", "node_id":"mrs_08_0024.xml", "product_code":"mrs", - "code":"134", + "code":"139", "des":"The following operations are often performed during the running of a big data cluster:Big data clusters often change, for example, cluster scale-out and scale-in.When a s", "doc_type":"usermanual", "kw":"Message Notification,Functions,User Guide", @@ -2414,7 +2501,7 @@ "uri":"mrs_08_0027.html", "node_id":"mrs_08_0027.xml", "product_code":"mrs", - "code":"135", + "code":"140", "des":"Before using MRS, ensure that you have read and understand the following restrictions.MRS clusters must be created in VPC subnets.You are advised to use any of the follow", "doc_type":"usermanual", "kw":"Constraints,Overview,User Guide", @@ -2432,7 +2519,7 @@ "uri":"mrs_08_0026.html", "node_id":"mrs_08_0026.xml", "product_code":"mrs", - "code":"136", + "code":"141", "des":"After you enable CTS, the system starts recording operations on cloud resources. You can view operation records of the last 7 days on the CTS management console. For deta", "doc_type":"usermanual", "kw":"Related Services,Overview,User Guide", @@ -2450,7 +2537,7 @@ "uri":"mrs_01_0452.html", "node_id":"mrs_01_0452.xml", "product_code":"mrs", - "code":"137", + "code":"142", "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":"Preparing a User", @@ -2470,7 +2557,7 @@ "uri":"mrs_01_0453.html", "node_id":"mrs_01_0453.xml", "product_code":"mrs", - "code":"138", + "code":"143", "des":"Use IAM to implement fine-grained permission control over your MRS. With IAM, you can:Create IAM users under your cloud account for employees based on your enterprise's o", "doc_type":"usermanual", "kw":"Creating an MRS User,Preparing a User,User Guide", @@ -2490,7 +2577,7 @@ "uri":"mrs_01_0455.html", "node_id":"mrs_01_0455.xml", "product_code":"mrs", - "code":"139", + "code":"144", "des":"Custom policies can be created to supplement the system-defined policies of MRS. For the actions that can be added to custom policies, see Permissions Policies and Suppor", "doc_type":"usermanual", "kw":"Creating a Custom Policy,Preparing a User,User Guide", @@ -2510,7 +2597,7 @@ "uri":"mrs_01_0495.html", "node_id":"mrs_01_0495.xml", "product_code":"mrs", - "code":"140", + "code":"145", "des":"IAM user synchronization is to synchronize IAM users bound with MRS policies to the MRS system and create accounts with the same usernames but different passwords as the ", "doc_type":"usermanual", "kw":"Synchronizing IAM Users to MRS,Preparing a User,User Guide", @@ -2530,7 +2617,7 @@ "uri":"mrs_01_0024.html", "node_id":"mrs_01_0024.xml", "product_code":"mrs", - "code":"141", + "code":"146", "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 Quick Start", @@ -2548,7 +2635,7 @@ "uri":"mrs_01_0511.html", "node_id":"mrs_01_0511.xml", "product_code":"mrs", - "code":"142", + "code":"147", "des":"MapReduce Service (MRS) is a cloud service that is used to deploy and manage the Hadoop system and enables one-click Hadoop cluster deployment. MRS provides enterprise-le", "doc_type":"usermanual", "kw":"How to Use MRS,MRS Quick Start,User Guide", @@ -2568,7 +2655,7 @@ "uri":"mrs_01_0027.html", "node_id":"mrs_01_0027.xml", "product_code":"mrs", - "code":"143", + "code":"148", "des":"The first step of using MRS is to create a cluster. This section describes how to create a cluster on the MRS management console.When creating a cluster, pay attention to", "doc_type":"usermanual", "kw":"Creating a Cluster,MRS Quick Start,User Guide", @@ -2588,7 +2675,7 @@ "uri":"mrs_01_0028.html", "node_id":"mrs_01_0028.xml", "product_code":"mrs", - "code":"144", + "code":"149", "des":"Through the Files tab page, you can create, delete, import, export, delete files in the analysis cluster.MRS clusters process data from OBS or HDFS. OBS provides customer", "doc_type":"usermanual", "kw":"Uploading Data and Programs,MRS Quick Start,User Guide", @@ -2608,7 +2695,7 @@ "uri":"mrs_01_0029.html", "node_id":"mrs_01_0029.xml", "product_code":"mrs", - "code":"145", + "code":"150", "des":"You can submit programs developed by yourself to MRS to execute them, and obtain the results.This section describes how to submit a job (take a MapReduce job as an exampl", "doc_type":"usermanual", "kw":"Creating a Job,MRS Quick Start,User Guide", @@ -2627,7 +2714,7 @@ "uri":"mrs_09_0003.html", "node_id":"mrs_09_0003.xml", "product_code":"mrs", - "code":"146", + "code":"151", "des":"This section instructs you to use security clusters and run MapReduce, Spark, and Hive programs.The Presto component of MRS 3.x does not support Kerberos authentication.Y", "doc_type":"qs", "kw":"Using Clusters with Kerberos Authentication Enabled,MRS Quick Start,User Guide", @@ -2645,7 +2732,7 @@ "uri":"mrs_01_0469.html", "node_id":"mrs_01_0469.xml", "product_code":"mrs", - "code":"147", + "code":"152", "des":"You can terminate an MRS cluster that is no longer use after job execution is complete.You can manually terminate a cluster after data analysis is complete or when the cl", "doc_type":"usermanual", "kw":"Terminating a Cluster,MRS Quick Start,User Guide", @@ -2663,7 +2750,7 @@ "uri":"mrs_01_0030.html", "node_id":"mrs_01_0030.xml", "product_code":"mrs", - "code":"148", + "code":"153", "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", @@ -2682,8 +2769,8 @@ "uri":"mrs_01_0025.html", "node_id":"mrs_01_0025.xml", "product_code":"mrs", - "code":"149", - "des":"This section describes how to create MRS clusters.Quick Creation of a Hadoop Analysis Cluster: On the Quick Config tab page, you can quickly configure parameters to creat", + "code":"154", + "des":"This section describes how to create MRS clusters.Quickly Creating a Doris Cluster: On the Quick Config tab page, you can quickly configure parameters to create Doris clu", "doc_type":"usermanual", "kw":"Methods of Creating MRS Clusters,Configuring a Cluster,User Guide", "search_title":"", @@ -2702,7 +2789,7 @@ "uri":"mrs_01_24297.html", "node_id":"mrs_01_24297.xml", "product_code":"mrs", - "code":"150", + "code":"155", "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":"Quick Creation of a Cluster", @@ -2722,7 +2809,7 @@ "uri":"mrs_01_249283.html", "node_id":"mrs_01_249283.xml", "product_code":"", - "code":"151", + "code":"156", "des":"This section describes how to quickly create a Doris cluster. Doris is a high-performance, real-time analytical database, suitable for report analysis, ad hoc query, and ", "doc_type":"", "kw":"Quickly Creating a Doris Cluster,Quick Creation of a Cluster,User Guide", @@ -2739,7 +2826,7 @@ "uri":"mrs_01_0512.html", "node_id":"mrs_01_0512.xml", "product_code":"mrs", - "code":"152", + "code":"157", "des":"This section describes how to quickly create a Hadoop analysis cluster for analyzing and querying vast amounts of data. In the open-source Hadoop ecosystem, Hadoop uses Y", "doc_type":"usermanual", "kw":"Quick Creation of a Hadoop Analysis Cluster,Quick Creation of a Cluster,User Guide", @@ -2759,7 +2846,7 @@ "uri":"mrs_01_0496.html", "node_id":"mrs_01_0496.xml", "product_code":"mrs", - "code":"153", + "code":"158", "des":"This section describes how to quickly create an HBase query cluster. The HBase cluster uses Hadoop and HBase components to provide a column-oriented distributed cloud sto", "doc_type":"usermanual", "kw":"Quick Creation of an HBase Analysis Cluster,Quick Creation of a Cluster,User Guide", @@ -2779,7 +2866,7 @@ "uri":"mrs_01_2354.html", "node_id":"mrs_01_2354.xml", "product_code":"mrs", - "code":"154", + "code":"159", "des":"This section describes how to quickly create a ClickHouse cluster. ClickHouse is a columnar database management system used for online analysis. It features the ultimate ", "doc_type":"usermanual", "kw":"Quick Creation of a ClickHouse Cluster,Quick Creation of a Cluster,User Guide", @@ -2799,7 +2886,7 @@ "uri":"mrs_01_2355.html", "node_id":"mrs_01_2355.xml", "product_code":"mrs", - "code":"155", + "code":"160", "des":"This section describes how to quickly create a real-time analysis cluster. The real-time analysis cluster uses Hadoop, Kafka, Flink, and ClickHouse to collect, analyze, a", "doc_type":"usermanual", "kw":"Quick Creation of a Real-time Analysis Cluster,Quick Creation of a Cluster,User Guide", @@ -2819,7 +2906,7 @@ "uri":"mrs_01_0513.html", "node_id":"mrs_01_0513.xml", "product_code":"mrs", - "code":"156", + "code":"161", "des":"The first step of using MRS is to create a cluster. This section describes how to create a cluster on the Custom Config tab of the MRS management console.You can create a", "doc_type":"usermanual", "kw":"Creating a Custom Cluster,Configuring a Cluster,User Guide", @@ -2839,7 +2926,7 @@ "uri":"mrs_01_0121.html", "node_id":"mrs_01_0121.xml", "product_code":"mrs", - "code":"157", + "code":"162", "des":"The analysis cluster, streaming cluster, and hybrid cluster provided by MRS use fixed templates to deploy cluster processes. Therefore, you cannot customize service proce", "doc_type":"usermanual", "kw":"Creating a Custom Topology Cluster,Configuring a Cluster,User Guide", @@ -2859,7 +2946,7 @@ "uri":"mrs_01_0048.html", "node_id":"mrs_01_0048.xml", "product_code":"mrs", - "code":"158", + "code":"163", "des":"Tags are used to identify clusters/nodes. Adding tags to clusters can help you identify and manage your cluster resources.Cluster tags: You can add up to 10 tags to a clu", "doc_type":"usermanual", "kw":"Adding a Tag to a Cluster/Node,Configuring a Cluster,User Guide", @@ -2879,7 +2966,7 @@ "uri":"mrs_01_0786.html", "node_id":"mrs_01_0786.xml", "product_code":"mrs", - "code":"159", + "code":"164", "des":"MRS clusters provision, manage, and use big data components through the management console. Big data components are deployed in a user's VPC. If the MRS management consol", "doc_type":"usermanual", "kw":"Communication Security Authorization,Configuring a Cluster,User Guide", @@ -2899,7 +2986,7 @@ "uri":"mrs_01_0061.html", "node_id":"mrs_01_0061.xml", "product_code":"mrs", - "code":"160", + "code":"165", "des":"In big data application scenarios, especially real-time data analysis and processing, the number of cluster nodes needs to be dynamically adjusted according to data volum", "doc_type":"usermanual", "kw":"Configuring an Auto Scaling Rule,Configuring a Cluster,User Guide", @@ -2919,7 +3006,7 @@ "uri":"mrs_01_24050.html", "node_id":"mrs_01_24050.xml", "product_code":"mrs", - "code":"161", + "code":"166", "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 Data Connections", @@ -2939,7 +3026,7 @@ "uri":"mrs_01_0633.html", "node_id":"mrs_01_0633.xml", "product_code":"mrs", - "code":"162", + "code":"167", "des":"MRS data connections are used to manage external source connections used by components in a cluster. For example, if Hive metadata uses an external relational database, a", "doc_type":"usermanual", "kw":"Configuring Data Connections,Managing Data Connections,User Guide", @@ -2959,7 +3046,7 @@ "uri":"mrs_01_24051.html", "node_id":"mrs_01_24051.xml", "product_code":"mrs", - "code":"163", + "code":"168", "des":"Switch the Ranger metadata of the existing cluster to the metadata stored in the RDS database. This operation enables multiple MRS clusters to share the same metadata, an", "doc_type":"usermanual", "kw":"Configuring Ranger Data Connections,Managing Data Connections,User Guide", @@ -2979,7 +3066,7 @@ "uri":"mrs_01_24487.html", "node_id":"mrs_01_24487.xml", "product_code":"mrs", - "code":"164", + "code":"169", "des":"This section describes how to switch the Hive metadata of an active cluster to the metadata stored in a local database or RDS database after you create a cluster. This op", "doc_type":"usermanual", "kw":"Configuring a Hive Data Connection,Managing Data Connections,User Guide", @@ -2999,7 +3086,7 @@ "uri":"mrs_01_0413.html", "node_id":"mrs_01_0413.xml", "product_code":"mrs", - "code":"165", + "code":"170", "des":"This operation applies to clusters earlier than MRS 3.x.The bootstrap action script has been prepared by referring to Preparing the Bootstrap Action Script.After the boot", "doc_type":"usermanual", "kw":"Installing Third-Party Software Using Bootstrap Actions,Configuring a Cluster,User Guide", @@ -3019,7 +3106,7 @@ "uri":"mrs_01_0043.html", "node_id":"mrs_01_0043.xml", "product_code":"mrs", - "code":"166", + "code":"171", "des":"This section describes how to view and delete a failed MRS task.If a cluster fails to be created, terminated, scaled out, or scaled in, the Manage Failed Tasks page is di", "doc_type":"usermanual", "kw":"Viewing Failed MRS Tasks,Configuring a Cluster,User Guide", @@ -3039,7 +3126,7 @@ "uri":"en-us_topic_0057514383.html", "node_id":"en-us_topic_0057514383.xml", "product_code":"mrs", - "code":"167", + "code":"172", "des":"Choose Clusters > Cluster History and click the name of a target cluster. You can view the cluster configuration and deployed node information.The following table describ", "doc_type":"usermanual", "kw":"Viewing Information of a Historical Cluster,Configuring a Cluster,User Guide", @@ -3059,7 +3146,7 @@ "uri":"mrs_01_0034.html", "node_id":"mrs_01_0034.xml", "product_code":"mrs", - "code":"168", + "code":"173", "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 Clusters", @@ -3079,7 +3166,7 @@ "uri":"mrs_01_0082.html", "node_id":"mrs_01_0082.xml", "product_code":"mrs", - "code":"169", + "code":"174", "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":"Logging In to a Cluster", @@ -3097,7 +3184,7 @@ "uri":"mrs_01_0081.html", "node_id":"mrs_01_0081.xml", "product_code":"mrs", - "code":"170", + "code":"175", "des":"This section describes remote login, MRS cluster node types, and node functions.MRS cluster nodes support remote login. The following remote login methods are available:G", "doc_type":"usermanual", "kw":"MRS Cluster Node Overview,Logging In to a Cluster,User Guide", @@ -3117,7 +3204,7 @@ "uri":"mrs_01_0083.html", "node_id":"mrs_01_0083.xml", "product_code":"mrs", - "code":"171", + "code":"176", "des":"This section describes how to remotely log in to an ECS in an MRS cluster using the remote login (VNC mode) function provided on the ECS management console or a key or pa", "doc_type":"usermanual", "kw":"Logging In to an ECS,Logging In to a Cluster,User Guide", @@ -3137,7 +3224,7 @@ "uri":"mrs_01_0086.html", "node_id":"mrs_01_0086.xml", "product_code":"mrs", - "code":"172", + "code":"177", "des":"This section describes how to determine the active and standby management nodes of Manager on the Master1 node.You can log in to other nodes in the cluster from the Maste", "doc_type":"usermanual", "kw":"Determining Active and Standby Management Nodes of Manager,Logging In to a Cluster,User Guide", @@ -3157,7 +3244,7 @@ "uri":"mrs_01_0514.html", "node_id":"mrs_01_0514.xml", "product_code":"mrs", - "code":"173", + "code":"178", "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 Overview", @@ -3177,7 +3264,7 @@ "uri":"en-us_topic_0012799688.html", "node_id":"en-us_topic_0012799688.xml", "product_code":"mrs", - "code":"174", + "code":"179", "des":"You can quickly view the status of all clusters and jobs by viewing the dashboard information, and obtain relevant MRS documents from Overview in the left navigation pane", "doc_type":"usermanual", "kw":"Cluster List,Cluster Overview,User Guide", @@ -3197,7 +3284,7 @@ "uri":"en-us_topic_0012808230.html", "node_id":"en-us_topic_0012808230.xml", "product_code":"mrs", - "code":"175", + "code":"180", "des":"The cluster list contains all clusters in MRS. You can view clusters in various states. If a large number of clusters are involved, navigate through multiple pages to vie", "doc_type":"usermanual", "kw":"Checking the Cluster Status,Cluster Overview,User Guide", @@ -3217,7 +3304,7 @@ "uri":"en-us_topic_0012808231.html", "node_id":"en-us_topic_0012808231.xml", "product_code":"mrs", - "code":"176", + "code":"181", "des":"You can monitor and manage the clusters you have created. Choose Clusters > Active Clusters. Select a cluster and click its name to go to the cluster details page. On the", "doc_type":"usermanual", "kw":"Viewing Basic Cluster Information,Cluster Overview,User Guide", @@ -3237,7 +3324,7 @@ "uri":"mrs_01_0036.html", "node_id":"mrs_01_0036.xml", "product_code":"mrs", - "code":"177", + "code":"182", "des":"To view patch information about cluster components, you can download the required patch if the cluster component, such as Hadoop or Spark, is faulty. On the MRS console, ", "doc_type":"usermanual", "kw":"Viewing Cluster Patch Information,Cluster Overview,User Guide", @@ -3257,7 +3344,7 @@ "uri":"mrs_01_0515.html", "node_id":"mrs_01_0515.xml", "product_code":"mrs", - "code":"178", + "code":"183", "des":"MRS cluster nodes are classified into management nodes, control nodes, and data nodes. The change trends of key host monitoring metrics on each type of node can be calcul", "doc_type":"usermanual", "kw":"Viewing and Customizing Cluster Monitoring Metrics,Cluster Overview,User Guide", @@ -3277,7 +3364,7 @@ "uri":"mrs_01_0517.html", "node_id":"mrs_01_0517.xml", "product_code":"mrs", - "code":"179", + "code":"184", "des":"You can manage the following status and metrics of all components (including role instances) and hosts on the MRS console:Status information: includes operation, health, ", "doc_type":"usermanual", "kw":"Managing Components and Monitoring Hosts,Cluster Overview,User Guide", @@ -3297,7 +3384,7 @@ "uri":"mrs_01_24295.html", "node_id":"mrs_01_24295.xml", "product_code":"mrs", - "code":"180", + "code":"185", "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 O&M", @@ -3317,7 +3404,7 @@ "uri":"en-us_topic_0019489057.html", "node_id":"en-us_topic_0019489057.xml", "product_code":"mrs", - "code":"181", + "code":"186", "des":"Through the Files tab page, you can create, delete, import, export, delete files in the analysis cluster. Currently, file creation is not supported. Streaming clusters do", "doc_type":"usermanual", "kw":"Importing and Exporting Data,Cluster O&M,User Guide", @@ -3337,7 +3424,7 @@ "uri":"mrs_01_24259.html", "node_id":"mrs_01_24259.xml", "product_code":"mrs", - "code":"182", + "code":"187", "des":"If the current subnet does not have sufficient IP addresses, you can change to another subnet in the same VPC of the current cluster to obtain more available subnet IP ad", "doc_type":"usermanual", "kw":"Changing the Subnet of a Cluster,Cluster O&M,User Guide", @@ -3357,7 +3444,7 @@ "uri":"mrs_01_0062.html", "node_id":"mrs_01_0062.xml", "product_code":"mrs", - "code":"183", + "code":"188", "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).On the ", "doc_type":"usermanual", "kw":"Configuring Message Notification,Cluster O&M,User Guide", @@ -3377,7 +3464,7 @@ "uri":"mrs_01_0223.html", "node_id":"mrs_01_0223.xml", "product_code":"mrs", - "code":"184", + "code":"189", "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":"Checking Health Status", @@ -3397,7 +3484,7 @@ "uri":"mrs_01_0603.html", "node_id":"mrs_01_0603.xml", "product_code":"mrs", - "code":"185", + "code":"190", "des":"This section describes how to manage health checks on the MRS console.Health check management operations on the MRS console apply only to clusters of MRS 1.9.2 to MRS 2.1", "doc_type":"usermanual", "kw":"Before You Start,Checking Health Status,User Guide", @@ -3417,7 +3504,7 @@ "uri":"mrs_01_0224.html", "node_id":"mrs_01_0224.xml", "product_code":"mrs", - "code":"186", + "code":"191", "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,Checking Health Status,User Guide", @@ -3437,7 +3524,7 @@ "uri":"mrs_01_0225.html", "node_id":"mrs_01_0225.xml", "product_code":"mrs", - "code":"187", + "code":"192", "des":"You can view the health check result on MRS and export it for further analysis.A system health check includes MRS Manager, service-level, and host-level health checks:MRS", "doc_type":"usermanual", "kw":"Viewing and Exporting a Health Check Report,Checking Health Status,User Guide", @@ -3457,7 +3544,7 @@ "uri":"mrs_01_0520.html", "node_id":"mrs_01_0520.xml", "product_code":"mrs", - "code":"188", + "code":"193", "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":"Remote O&M", @@ -3477,7 +3564,7 @@ "uri":"mrs_01_0641.html", "node_id":"mrs_01_0641.xml", "product_code":"mrs", - "code":"189", + "code":"194", "des":"If you need technical support personnel to help you with troubleshooting, you can use the O&M authorization function to authorize technical support personnel to access yo", "doc_type":"usermanual", "kw":"Authorizing O&M,Remote O&M,User Guide", @@ -3496,7 +3583,7 @@ "uri":"mrs_01_0642.html", "node_id":"mrs_01_0642.xml", "product_code":"mrs", - "code":"190", + "code":"195", "des":"If you need technical support personnel to help you with troubleshooting, you can use the log sharing function to provide logs in a specific time to technical support per", "doc_type":"usermanual", "kw":"Sharing Logs,Remote O&M,User Guide", @@ -3515,7 +3602,7 @@ "uri":"en-us_topic_0012808265.html", "node_id":"en-us_topic_0012808265.xml", "product_code":"mrs", - "code":"191", + "code":"196", "des":"You can view operation logs of clusters and jobs on the Operation Logs page. Log information is typically used for quickly locating faults in case of cluster exceptions, ", "doc_type":"usermanual", "kw":"Viewing MRS Operation Logs,Cluster O&M,User Guide", @@ -3535,7 +3622,7 @@ "uri":"mrs_01_0042.html", "node_id":"mrs_01_0042.xml", "product_code":"mrs", - "code":"192", + "code":"197", "des":"You can terminate an MRS cluster after job execution is complete.You can manually terminate a cluster after data analysis is complete or when the cluster encounters an ex", "doc_type":"usermanual", "kw":"Terminating a Cluster,Cluster O&M,User Guide", @@ -3554,7 +3641,7 @@ "uri":"mrs_01_24296.html", "node_id":"mrs_01_24296.xml", "product_code":"mrs", - "code":"193", + "code":"198", "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 Nodes", @@ -3574,7 +3661,7 @@ "uri":"mrs_01_0041.html", "node_id":"mrs_01_0041.xml", "product_code":"mrs", - "code":"194", + "code":"199", "des":"The storage and computing capabilities of MRS can be improved by simply adding Core nodes or Task nodes instead of modifying system architecture, reducing O&M costs. Core", "doc_type":"usermanual", "kw":"Manually Scaling Out a Cluster,Managing Nodes,User Guide", @@ -3594,7 +3681,7 @@ "uri":"mrs_01_0060.html", "node_id":"mrs_01_0060.xml", "product_code":"mrs", - "code":"195", + "code":"200", "des":"You can reduce the number of core or task nodes to scale in a cluster based on service requirements so that MRS delivers better storage and computing capabilities at lowe", "doc_type":"usermanual", "kw":"Manually Scaling In a Cluster,Managing Nodes,User Guide", @@ -3614,7 +3701,7 @@ "uri":"mrs_01_248971.html", "node_id":"mrs_01_248971.xml", "product_code":"", - "code":"196", + "code":"201", "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", @@ -3631,7 +3718,7 @@ "uri":"mrs_01_248972.html", "node_id":"mrs_01_248972.xml", "product_code":"", - "code":"197", + "code":"202", "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", @@ -3648,7 +3735,7 @@ "uri":"mrs_01_248973.html", "node_id":"mrs_01_248973.xml", "product_code":"", - "code":"198", + "code":"203", "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", @@ -3665,7 +3752,7 @@ "uri":"mrs_01_0211.html", "node_id":"mrs_01_0211.xml", "product_code":"mrs", - "code":"199", + "code":"204", "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", @@ -3685,7 +3772,7 @@ "uri":"mrs_01_0212.html", "node_id":"mrs_01_0212.xml", "product_code":"mrs", - "code":"200", + "code":"205", "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", @@ -3705,7 +3792,7 @@ "uri":"mrs_01_0213.html", "node_id":"mrs_01_0213.xml", "product_code":"mrs", - "code":"201", + "code":"206", "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", @@ -3725,7 +3812,7 @@ "uri":"mrs_01_0522.html", "node_id":"mrs_01_0522.xml", "product_code":"mrs", - "code":"202", + "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":"Job Management", @@ -3744,7 +3831,7 @@ "uri":"mrs_01_0051.html", "node_id":"mrs_01_0051.xml", "product_code":"mrs", - "code":"203", + "code":"208", "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", @@ -3764,7 +3851,7 @@ "uri":"mrs_01_0052.html", "node_id":"mrs_01_0052.xml", "product_code":"mrs", - "code":"204", + "code":"209", "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", @@ -3784,7 +3871,7 @@ "uri":"mrs_01_0524.html", "node_id":"mrs_01_0524.xml", "product_code":"mrs", - "code":"205", + "code":"210", "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", @@ -3804,7 +3891,7 @@ "uri":"mrs_01_0525.html", "node_id":"mrs_01_0525.xml", "product_code":"mrs", - "code":"206", + "code":"211", "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", @@ -3824,7 +3911,7 @@ "uri":"mrs_01_0526.html", "node_id":"mrs_01_0526.xml", "product_code":"mrs", - "code":"207", + "code":"212", "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", @@ -3844,7 +3931,7 @@ "uri":"mrs_01_0527.html", "node_id":"mrs_01_0527.xml", "product_code":"mrs", - "code":"208", + "code":"213", "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", @@ -3864,7 +3951,7 @@ "uri":"mrs_01_0494.html", "node_id":"mrs_01_0494.xml", "product_code":"mrs", - "code":"209", + "code":"214", "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", @@ -3884,7 +3971,7 @@ "uri":"mrs_01_0055.html", "node_id":"mrs_01_0055.xml", "product_code":"mrs", - "code":"210", + "code":"215", "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", @@ -3903,7 +3990,7 @@ "uri":"mrs_01_0056.html", "node_id":"mrs_01_0056.xml", "product_code":"mrs", - "code":"211", + "code":"216", "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", @@ -3922,7 +4009,7 @@ "uri":"mrs_01_0057.html", "node_id":"mrs_01_0057.xml", "product_code":"mrs", - "code":"212", + "code":"217", "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", @@ -3942,7 +4029,7 @@ "uri":"mrs_01_0058.html", "node_id":"mrs_01_0058.xml", "product_code":"mrs", - "code":"213", + "code":"218", "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", @@ -3960,7 +4047,7 @@ "uri":"mrs_01_0762.html", "node_id":"mrs_01_0762.xml", "product_code":"mrs", - "code":"214", + "code":"219", "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", @@ -3980,7 +4067,7 @@ "uri":"mrs_01_0200.html", "node_id":"mrs_01_0200.xml", "product_code":"mrs", - "code":"215", + "code":"220", "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", @@ -3999,7 +4086,7 @@ "uri":"mrs_01_0201.html", "node_id":"mrs_01_0201.xml", "product_code":"mrs", - "code":"216", + "code":"221", "des":"MRS contains different types of basic objects. Table 1 describes these objects.", "doc_type":"usermanual", "kw":"Object Management,Component Management,User Guide", @@ -4018,7 +4105,7 @@ "uri":"mrs_01_0202.html", "node_id":"mrs_01_0202.xml", "product_code":"mrs", - "code":"217", + "code":"222", "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", @@ -4038,7 +4125,7 @@ "uri":"mrs_01_0203.html", "node_id":"mrs_01_0203.xml", "product_code":"mrs", - "code":"218", + "code":"223", "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", @@ -4058,7 +4145,7 @@ "uri":"mrs_01_0204.html", "node_id":"mrs_01_0204.xml", "product_code":"mrs", - "code":"219", + "code":"224", "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", @@ -4078,7 +4165,7 @@ "uri":"mrs_01_0205.html", "node_id":"mrs_01_0205.xml", "product_code":"mrs", - "code":"220", + "code":"225", "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", @@ -4098,7 +4185,7 @@ "uri":"mrs_01_0206.html", "node_id":"mrs_01_0206.xml", "product_code":"mrs", - "code":"221", + "code":"226", "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", @@ -4118,7 +4205,7 @@ "uri":"mrs_01_0207.html", "node_id":"mrs_01_0207.xml", "product_code":"mrs", - "code":"222", + "code":"227", "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", @@ -4138,7 +4225,7 @@ "uri":"mrs_01_0208.html", "node_id":"mrs_01_0208.xml", "product_code":"mrs", - "code":"223", + "code":"228", "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", @@ -4158,7 +4245,7 @@ "uri":"mrs_01_0209.html", "node_id":"mrs_01_0209.xml", "product_code":"mrs", - "code":"224", + "code":"229", "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", @@ -4178,7 +4265,7 @@ "uri":"mrs_01_0210.html", "node_id":"mrs_01_0210.xml", "product_code":"mrs", - "code":"225", + "code":"230", "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", @@ -4198,7 +4285,7 @@ "uri":"mrs_01_0214.html", "node_id":"mrs_01_0214.xml", "product_code":"mrs", - "code":"226", + "code":"231", "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", @@ -4218,7 +4305,7 @@ "uri":"mrs_01_0215.html", "node_id":"mrs_01_0215.xml", "product_code":"mrs", - "code":"227", + "code":"232", "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", @@ -4238,7 +4325,7 @@ "uri":"mrs_01_0216.html", "node_id":"mrs_01_0216.xml", "product_code":"mrs", - "code":"228", + "code":"233", "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", @@ -4258,7 +4345,7 @@ "uri":"mrs_01_0628.html", "node_id":"mrs_01_0628.xml", "product_code":"mrs", - "code":"229", + "code":"234", "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", @@ -4277,7 +4364,7 @@ "uri":"mrs_01_0112.html", "node_id":"mrs_01_0112.xml", "product_code":"mrs", - "code":"230", + "code":"235", "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", @@ -4296,7 +4383,7 @@ "uri":"en-us_topic_0040980162.html", "node_id":"en-us_topic_0040980162.xml", "product_code":"mrs", - "code":"231", + "code":"236", "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", @@ -4315,7 +4402,7 @@ "uri":"mrs_01_0602.html", "node_id":"mrs_01_0602.xml", "product_code":"mrs", - "code":"232", + "code":"237", "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", @@ -4335,7 +4422,7 @@ "uri":"mrs_01_0113.html", "node_id":"mrs_01_0113.xml", "product_code":"mrs", - "code":"233", + "code":"238", "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", @@ -4354,7 +4441,7 @@ "uri":"mrs_01_0409.html", "node_id":"mrs_01_0409.xml", "product_code":"mrs", - "code":"234", + "code":"239", "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", @@ -4373,7 +4460,7 @@ "uri":"mrs_01_0410.html", "node_id":"mrs_01_0410.xml", "product_code":"mrs", - "code":"235", + "code":"240", "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", @@ -4393,7 +4480,7 @@ "uri":"mrs_01_0411.html", "node_id":"mrs_01_0411.xml", "product_code":"mrs", - "code":"236", + "code":"241", "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", @@ -4413,7 +4500,7 @@ "uri":"mrs_01_0431.html", "node_id":"mrs_01_0431.xml", "product_code":"mrs", - "code":"237", + "code":"242", "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", @@ -4433,7 +4520,7 @@ "uri":"mrs_01_0412.html", "node_id":"mrs_01_0412.xml", "product_code":"mrs", - "code":"238", + "code":"243", "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", @@ -4453,7 +4540,7 @@ "uri":"mrs_01_248926.html", "node_id":"mrs_01_248926.xml", "product_code":"mrs", - "code":"239", + "code":"244", "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", @@ -4471,7 +4558,7 @@ "uri":"mrs_01_9043.html", "node_id":"mrs_01_9043.xml", "product_code":"", - "code":"240", + "code":"245", "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", @@ -4488,7 +4575,7 @@ "uri":"mrs_01_0303.html", "node_id":"mrs_01_0303.xml", "product_code":"mrs", - "code":"241", + "code":"246", "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", @@ -4508,7 +4595,7 @@ "uri":"mrs_01_0604.html", "node_id":"mrs_01_0604.xml", "product_code":"mrs", - "code":"242", + "code":"247", "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", @@ -4528,7 +4615,7 @@ "uri":"mrs_01_0304.html", "node_id":"mrs_01_0304.xml", "product_code":"mrs", - "code":"243", + "code":"248", "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", @@ -4548,7 +4635,7 @@ "uri":"mrs_01_0305.html", "node_id":"mrs_01_0305.xml", "product_code":"mrs", - "code":"244", + "code":"249", "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", @@ -4568,7 +4655,7 @@ "uri":"mrs_01_0306.html", "node_id":"mrs_01_0306.xml", "product_code":"mrs", - "code":"245", + "code":"250", "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", @@ -4588,7 +4675,7 @@ "uri":"mrs_01_0307.html", "node_id":"mrs_01_0307.xml", "product_code":"mrs", - "code":"246", + "code":"251", "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", @@ -4608,7 +4695,7 @@ "uri":"mrs_01_0308.html", "node_id":"mrs_01_0308.xml", "product_code":"mrs", - "code":"247", + "code":"252", "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", @@ -4628,7 +4715,7 @@ "uri":"mrs_01_0309.html", "node_id":"mrs_01_0309.xml", "product_code":"mrs", - "code":"248", + "code":"253", "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", @@ -4648,7 +4735,7 @@ "uri":"mrs_01_0310.html", "node_id":"mrs_01_0310.xml", "product_code":"mrs", - "code":"249", + "code":"254", "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", @@ -4668,7 +4755,7 @@ "uri":"mrs_01_0311.html", "node_id":"mrs_01_0311.xml", "product_code":"mrs", - "code":"250", + "code":"255", "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", @@ -4688,7 +4775,7 @@ "uri":"mrs_01_0312.html", "node_id":"mrs_01_0312.xml", "product_code":"mrs", - "code":"251", + "code":"256", "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", @@ -4708,7 +4795,7 @@ "uri":"mrs_01_0313.html", "node_id":"mrs_01_0313.xml", "product_code":"mrs", - "code":"252", + "code":"257", "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", @@ -4728,7 +4815,7 @@ "uri":"mrs_01_0314.html", "node_id":"mrs_01_0314.xml", "product_code":"mrs", - "code":"253", + "code":"258", "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", @@ -4748,7 +4835,7 @@ "uri":"mrs_01_0315.html", "node_id":"mrs_01_0315.xml", "product_code":"mrs", - "code":"254", + "code":"259", "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", @@ -4768,7 +4855,7 @@ "uri":"mrs_01_24565.html", "node_id":"mrs_01_24565.xml", "product_code":"mrs", - "code":"255", + "code":"260", "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", @@ -4786,7 +4873,7 @@ "uri":"mrs_01_0414.html", "node_id":"mrs_01_0414.xml", "product_code":"mrs", - "code":"256", + "code":"261", "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", @@ -4806,7 +4893,7 @@ "uri":"mrs_01_0417.html", "node_id":"mrs_01_0417.xml", "product_code":"mrs", - "code":"257", + "code":"262", "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", @@ -4826,7 +4913,7 @@ "uri":"mrs_01_0415.html", "node_id":"mrs_01_0415.xml", "product_code":"mrs", - "code":"258", + "code":"263", "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", @@ -4846,7 +4933,7 @@ "uri":"mrs_01_0416.html", "node_id":"mrs_01_0416.xml", "product_code":"mrs", - "code":"259", + "code":"264", "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", @@ -4866,7 +4953,7 @@ "uri":"mrs_01_24566.html", "node_id":"mrs_01_24566.xml", "product_code":"mrs", - "code":"260", + "code":"265", "des":"Modify an existing bootstrap action on an MRS cluster.", "doc_type":"usermanual", "kw":"Modifying a Bootstrap Action,Bootstrap Actions,User Guide", @@ -4886,7 +4973,7 @@ "uri":"mrs_01_24567.html", "node_id":"mrs_01_24567.xml", "product_code":"mrs", - "code":"261", + "code":"266", "des":"Delete a bootstrap action on an MRS cluster.", "doc_type":"usermanual", "kw":"Deleting a Bootstrap Action,Bootstrap Actions,User Guide", @@ -4906,7 +4993,7 @@ "uri":"mrs_01_0418.html", "node_id":"mrs_01_0418.xml", "product_code":"mrs", - "code":"262", + "code":"267", "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", @@ -4926,7 +5013,7 @@ "uri":"mrs_01_0088.html", "node_id":"mrs_01_0088.xml", "product_code":"mrs", - "code":"263", + "code":"268", "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", @@ -4945,7 +5032,7 @@ "uri":"mrs_01_24212.html", "node_id":"mrs_01_24212.xml", "product_code":"mrs", - "code":"264", + "code":"269", "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", @@ -4963,7 +5050,7 @@ "uri":"mrs_01_0090.html", "node_id":"mrs_01_0090.xml", "product_code":"mrs", - "code":"265", + "code":"270", "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", @@ -4983,7 +5070,7 @@ "uri":"mrs_01_0091.html", "node_id":"mrs_01_0091.xml", "product_code":"mrs", - "code":"266", + "code":"271", "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", @@ -5003,7 +5090,7 @@ "uri":"mrs_01_24213.html", "node_id":"mrs_01_24213.xml", "product_code":"mrs", - "code":"267", + "code":"272", "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", @@ -5021,7 +5108,7 @@ "uri":"mrs_01_24209.html", "node_id":"mrs_01_24209.xml", "product_code":"mrs", - "code":"268", + "code":"273", "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", @@ -5041,7 +5128,7 @@ "uri":"mrs_01_0089.html", "node_id":"mrs_01_0089.xml", "product_code":"mrs", - "code":"269", + "code":"274", "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", @@ -5061,7 +5148,7 @@ "uri":"mrs_01_24183.html", "node_id":"mrs_01_24183.xml", "product_code":"mrs", - "code":"270", + "code":"275", "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", @@ -5079,7 +5166,7 @@ "uri":"mrs_01_24184.html", "node_id":"mrs_01_24184.xml", "product_code":"mrs", - "code":"271", + "code":"276", "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", @@ -5097,7 +5184,7 @@ "uri":"mrs_01_24185.html", "node_id":"mrs_01_24185.xml", "product_code":"mrs", - "code":"272", + "code":"277", "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", @@ -5115,7 +5202,7 @@ "uri":"mrs_01_24186.html", "node_id":"mrs_01_24186.xml", "product_code":"mrs", - "code":"273", + "code":"278", "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", @@ -5133,7 +5220,7 @@ "uri":"mrs_01_24187.html", "node_id":"mrs_01_24187.xml", "product_code":"mrs", - "code":"274", + "code":"279", "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", @@ -5151,7 +5238,7 @@ "uri":"mrs_01_24188.html", "node_id":"mrs_01_24188.xml", "product_code":"mrs", - "code":"275", + "code":"280", "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", @@ -5169,7 +5256,7 @@ "uri":"mrs_01_24189.html", "node_id":"mrs_01_24189.xml", "product_code":"mrs", - "code":"276", + "code":"281", "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", @@ -5187,7 +5274,7 @@ "uri":"mrs_01_24191.html", "node_id":"mrs_01_24191.xml", "product_code":"mrs", - "code":"277", + "code":"282", "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", @@ -5205,7 +5292,7 @@ "uri":"mrs_01_24193.html", "node_id":"mrs_01_24193.xml", "product_code":"mrs", - "code":"278", + "code":"283", "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", @@ -5223,7 +5310,7 @@ "uri":"mrs_01_24194.html", "node_id":"mrs_01_24194.xml", "product_code":"mrs", - "code":"279", + "code":"284", "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", @@ -5243,7 +5330,7 @@ "uri":"mrs_01_24196.html", "node_id":"mrs_01_24196.xml", "product_code":"mrs", - "code":"280", + "code":"285", "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", @@ -5261,7 +5348,7 @@ "uri":"mrs_01_0440.html", "node_id":"mrs_01_0440.xml", "product_code":"mrs", - "code":"281", + "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":"Configuring a Cluster with Storage and Compute Decoupled", @@ -5281,7 +5368,7 @@ "uri":"mrs_01_0467.html", "node_id":"mrs_01_0467.xml", "product_code":"mrs", - "code":"282", + "code":"287", "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":"MRS Storage-Compute Decoupling,Configuring a Cluster with Storage and Compute Decoupled,User Guide", @@ -5301,7 +5388,7 @@ "uri":"mrs_01_249279.html", "node_id":"mrs_01_249279.xml", "product_code":"", - "code":"283", + "code":"288", "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":"Interconnecting with OBS Using the Cluster Agency Mechanism", @@ -5318,7 +5405,7 @@ "uri":"mrs_01_0768.html", "node_id":"mrs_01_0768.xml", "product_code":"mrs", - "code":"284", + "code":"289", "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),Interconnecting with OBS Using the Cluster ", @@ -5338,7 +5425,7 @@ "uri":"mrs_01_0468.html", "node_id":"mrs_01_0468.xml", "product_code":"mrs", - "code":"285", + "code":"290", "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),Interconnecting with OBS Using the Cluster A", @@ -5358,7 +5445,7 @@ "uri":"mrs_01_249150.html", "node_id":"mrs_01_249150.xml", "product_code":"", - "code":"286", + "code":"291", "des":"By default, components in an MRS 3.2.0-LTS.1 or later cluster support prevention against accidental data deletion. Native HDFS garbage collection can be used in the Hadoo", "doc_type":"", "kw":"Configuring the Policy for Clearing Component Data in the Recycle Bin,Interconnecting with OBS Using", @@ -5375,7 +5462,7 @@ "uri":"mrs_01_0643.html", "node_id":"mrs_01_0643.xml", "product_code":"mrs", - "code":"287", + "code":"292", "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":"Interconnecting MRS with OBS Using an Agency", @@ -5393,7 +5480,7 @@ "uri":"mrs_01_1288.html", "node_id":"mrs_01_1288.xml", "product_code":"mrs", - "code":"288", + "code":"293", "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,Interconnecting MRS with OBS Using an Agency,User Guide", @@ -5413,7 +5500,7 @@ "uri":"mrs_01_24279.html", "node_id":"mrs_01_24279.xml", "product_code":"mrs", - "code":"289", + "code":"294", "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,Interconnecting MRS with OBS Using an Agency,User Guide", @@ -5433,7 +5520,7 @@ "uri":"mrs_01_1292.html", "node_id":"mrs_01_1292.xml", "product_code":"mrs", - "code":"290", + "code":"295", "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,Interconnecting MRS with OBS Using an Agency,User Guide", @@ -5453,7 +5540,7 @@ "uri":"mrs_01_1286.html", "node_id":"mrs_01_1286.xml", "product_code":"mrs", - "code":"291", + "code":"296", "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,Interconnecting MRS with OBS Using an Agency,User Guide", @@ -5473,7 +5560,7 @@ "uri":"mrs_01_0617.html", "node_id":"mrs_01_0617.xml", "product_code":"mrs", - "code":"292", + "code":"297", "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,Interconnecting MRS with OBS Using an Agency,User Guide", @@ -5493,7 +5580,7 @@ "uri":"mrs_01_1289.html", "node_id":"mrs_01_1289.xml", "product_code":"mrs", - "code":"293", + "code":"298", "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,Interconnecting MRS with OBS Using an Agency,User Guide", @@ -5513,7 +5600,7 @@ "uri":"mrs_01_24294.html", "node_id":"mrs_01_24294.xml", "product_code":"mrs", - "code":"294", + "code":"299", "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,Interconnecting MRS with OBS Using an Agency,Use", @@ -5533,7 +5620,7 @@ "uri":"mrs_01_24171.html", "node_id":"mrs_01_24171.xml", "product_code":"mrs", - "code":"295", + "code":"300", "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,Interconnecting MRS with OBS Using an Agency,User Guide", @@ -5553,7 +5640,7 @@ "uri":"mrs_01_0632.html", "node_id":"mrs_01_0632.xml", "product_code":"mrs", - "code":"296", + "code":"301", "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,Interconnecting with OBS Using", @@ -5573,7 +5660,7 @@ "uri":"mrs_01_248986.html", "node_id":"mrs_01_248986.xml", "product_code":"", - "code":"297", + "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":"", "kw":"Interconnecting with OBS Using the Guardian Service", @@ -5590,7 +5677,7 @@ "uri":"mrs_01_248987.html", "node_id":"mrs_01_248987.xml", "product_code":"", - "code":"298", + "code":"303", "des":"Create an MRS cluster.The MRS cluster must contain basic components such as Guardian, Ranger, and Hadoop.Currently, only MRS 3.3.0-LTS and later versions support intercon", "doc_type":"", "kw":"Scenarios,Interconnecting with OBS Using the Guardian Service,User Guide", @@ -5607,7 +5694,7 @@ "uri":"mrs_01_248978.html", "node_id":"mrs_01_248978.xml", "product_code":"", - "code":"299", + "code":"304", "des":"This section describes how to enable storage and compute decoupling for the Guardian component. After this feature is enabled, Guardian can provide temporary authenticati", "doc_type":"", "kw":"Interconnecting the Guardian Service with OBS,Interconnecting with OBS Using the Guardian Service,Us", @@ -5624,7 +5711,7 @@ "uri":"mrs_01_248988.html", "node_id":"mrs_01_248988.xml", "product_code":"", - "code":"300", + "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":"", "kw":"Interconnecting Components with OBS Using Guardian", @@ -5641,7 +5728,7 @@ "uri":"mrs_01_248989.html", "node_id":"mrs_01_248989.xml", "product_code":"", - "code":"301", + "code":"306", "des":"MRS clusters allow Hive to connect to OBS through Metastore.Interconnecting Hive with OBS through MetastoreLog in to the node where the Hive client is located and run the", "doc_type":"", "kw":"Interconnecting Hive with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5658,7 +5745,7 @@ "uri":"mrs_01_248991.html", "node_id":"mrs_01_248991.xml", "product_code":"", - "code":"302", + "code":"307", "des":"source Client installation directory/bigdata_envNormal cluster (Kerberos authentication disabled)yarn-session.sh -nm \"session-name\" -dyarn-session.sh -nm \"session-name\" -", "doc_type":"", "kw":"Interconnecting Flink with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5675,7 +5762,7 @@ "uri":"mrs_01_248992.html", "node_id":"mrs_01_248992.xml", "product_code":"", - "code":"303", + "code":"308", "des":"In an MRS cluster, Location can be set to an OBS file system path during Spark table creation and Spark can connect to OBS through Hive Metastore.Setting the location to ", "doc_type":"", "kw":"Interconnecting Spark with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5692,7 +5779,7 @@ "uri":"mrs_01_248993.html", "node_id":"mrs_01_248993.xml", "product_code":"", - "code":"304", + "code":"309", "des":"sourceClient installation directory/bigdata_envsourceClient installation directory/Hudi/component_envvimClient installation directory/Hudi/hudi/conf/hdfs-site.xmlkinit Us", "doc_type":"", "kw":"Interconnecting Hudi with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5709,7 +5796,7 @@ "uri":"mrs_01_248995.html", "node_id":"mrs_01_248995.xml", "product_code":"", - "code":"305", + "code":"310", "des":"In an MRS cluster, Location can be set to an OBS file system path during HetuEngine table creation and HetuEngine can connect to OBS through Hive Metastore.Setting Locati", "doc_type":"", "kw":"Interconnecting HetuEngine with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5726,7 +5813,7 @@ "uri":"mrs_01_248996.html", "node_id":"mrs_01_248996.xml", "product_code":"", - "code":"306", + "code":"311", "des":"cd Client installation directorysource bigdata_envkinitUser performing HDFS operationsThe following commands are examples.Access the OBS file system.hdfs dfs -ls obs://OB", "doc_type":"", "kw":"Interconnecting HDFS with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5743,7 +5830,7 @@ "uri":"mrs_01_248997.html", "node_id":"mrs_01_248997.xml", "product_code":"", - "code":"307", + "code":"312", "des":"cd Client installation directorysource bigdata_envkinitUser performing HDFS operationsAccess the OBS file system.hdfs dfs -ls obs://OBS parallel file system name/Pathhdfs", "doc_type":"", "kw":"Interconnecting Yarn with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5760,7 +5847,7 @@ "uri":"mrs_01_248998.html", "node_id":"mrs_01_248998.xml", "product_code":"", - "code":"308", + "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":"", "kw":"Interconnecting MapReduce with OBS,Interconnecting Components with OBS Using Guardian,User Guide", @@ -5777,7 +5864,7 @@ "uri":"mrs_01_0644.html", "node_id":"mrs_01_0644.xml", "product_code":"mrs", - "code":"309", + "code":"314", "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", @@ -5797,7 +5884,7 @@ "uri":"mrs_01_0362.html", "node_id":"mrs_01_0362.xml", "product_code":"mrs", - "code":"310", + "code":"315", "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", @@ -5817,7 +5904,7 @@ "uri":"mrs_01_0504.html", "node_id":"mrs_01_0504.xml", "product_code":"mrs", - "code":"311", + "code":"316", "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", @@ -5837,7 +5924,7 @@ "uri":"mrs_01_0645.html", "node_id":"mrs_01_0645.xml", "product_code":"mrs", - "code":"312", + "code":"317", "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,", @@ -5856,7 +5943,7 @@ "uri":"mrs_01_0646.html", "node_id":"mrs_01_0646.xml", "product_code":"mrs", - "code":"313", + "code":"318", "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", @@ -5876,7 +5963,7 @@ "uri":"mrs_01_0647.html", "node_id":"mrs_01_0647.xml", "product_code":"mrs", - "code":"314", + "code":"319", "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", @@ -5896,7 +5983,7 @@ "uri":"mrs_01_0363.html", "node_id":"mrs_01_0363.xml", "product_code":"mrs", - "code":"315", + "code":"320", "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", @@ -5916,7 +6003,7 @@ "uri":"mrs_01_0128.html", "node_id":"mrs_01_0128.xml", "product_code":"mrs", - "code":"316", + "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":"Accessing Manager", @@ -5936,7 +6023,7 @@ "uri":"mrs_01_0129.html", "node_id":"mrs_01_0129.xml", "product_code":"mrs", - "code":"317", + "code":"322", "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 MRS Manager,Accessing Manager,User Guide", @@ -5956,7 +6043,7 @@ "uri":"mrs_01_0102.html", "node_id":"mrs_01_0102.xml", "product_code":"mrs", - "code":"318", + "code":"323", "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.x or Earlier),Accessing Manager,User Guide", @@ -5976,7 +6063,7 @@ "uri":"mrs_01_0606.html", "node_id":"mrs_01_0606.xml", "product_code":"mrs", - "code":"319", + "code":"324", "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 3.x)", @@ -5994,7 +6081,7 @@ "uri":"admin_guide_000001.html", "node_id":"admin_guide_000001.xml", "product_code":"mrs", - "code":"320", + "code":"325", "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", @@ -6013,7 +6100,7 @@ "uri":"admin_guide_000002.html", "node_id":"admin_guide_000002.xml", "product_code":"mrs", - "code":"321", + "code":"326", "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":"MRS Manager Introduction,Getting Started,User Guide", @@ -6031,7 +6118,7 @@ "uri":"admin_guide_000003.html", "node_id":"admin_guide_000003.xml", "product_code":"mrs", - "code":"322", + "code":"327", "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 MRS Manager Version,Getting Started,User Guide", @@ -6049,7 +6136,7 @@ "uri":"admin_guide_000004.html", "node_id":"admin_guide_000004.xml", "product_code":"mrs", - "code":"323", + "code":"328", "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 MRS Manager,Getting Started,User Guide", @@ -6067,7 +6154,7 @@ "uri":"admin_guide_000005.html", "node_id":"admin_guide_000005.xml", "product_code":"mrs", - "code":"324", + "code":"329", "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", @@ -6085,7 +6172,7 @@ "uri":"admin_guide_000006.html", "node_id":"admin_guide_000006.xml", "product_code":"mrs", - "code":"325", + "code":"330", "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", @@ -6104,7 +6191,7 @@ "uri":"admin_guide_000007.html", "node_id":"admin_guide_000007.xml", "product_code":"mrs", - "code":"326", + "code":"331", "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", @@ -6122,7 +6209,7 @@ "uri":"admin_guide_000008.html", "node_id":"admin_guide_000008.xml", "product_code":"mrs", - "code":"327", + "code":"332", "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", @@ -6140,7 +6227,7 @@ "uri":"admin_guide_000009.html", "node_id":"admin_guide_000009.xml", "product_code":"mrs", - "code":"328", + "code":"333", "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", @@ -6158,7 +6245,7 @@ "uri":"admin_guide_000010.html", "node_id":"admin_guide_000010.xml", "product_code":"mrs", - "code":"329", + "code":"334", "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", @@ -6177,7 +6264,7 @@ "uri":"admin_guide_000011.html", "node_id":"admin_guide_000011.xml", "product_code":"mrs", - "code":"330", + "code":"335", "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", @@ -6195,7 +6282,7 @@ "uri":"admin_guide_000012.html", "node_id":"admin_guide_000012.xml", "product_code":"mrs", - "code":"331", + "code":"336", "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", @@ -6213,7 +6300,7 @@ "uri":"admin_guide_000013.html", "node_id":"admin_guide_000013.xml", "product_code":"mrs", - "code":"332", + "code":"337", "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", @@ -6231,7 +6318,7 @@ "uri":"admin_guide_000014.html", "node_id":"admin_guide_000014.xml", "product_code":"mrs", - "code":"333", + "code":"338", "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", @@ -6249,7 +6336,7 @@ "uri":"admin_guide_000015.html", "node_id":"admin_guide_000015.xml", "product_code":"mrs", - "code":"334", + "code":"339", "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", @@ -6267,7 +6354,7 @@ "uri":"admin_guide_000016.html", "node_id":"admin_guide_000016.xml", "product_code":"mrs", - "code":"335", + "code":"340", "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", @@ -6285,7 +6372,7 @@ "uri":"admin_guide_000017.html", "node_id":"admin_guide_000017.xml", "product_code":"mrs", - "code":"336", + "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":"Managing Static Service Pools", @@ -6304,7 +6391,7 @@ "uri":"admin_guide_000018.html", "node_id":"admin_guide_000018.xml", "product_code":"mrs", - "code":"337", + "code":"342", "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", @@ -6322,7 +6409,7 @@ "uri":"admin_guide_000019.html", "node_id":"admin_guide_000019.xml", "product_code":"mrs", - "code":"338", + "code":"343", "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", @@ -6340,7 +6427,7 @@ "uri":"admin_guide_000020.html", "node_id":"admin_guide_000020.xml", "product_code":"mrs", - "code":"339", + "code":"344", "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", @@ -6358,7 +6445,7 @@ "uri":"admin_guide_000021.html", "node_id":"admin_guide_000021.xml", "product_code":"mrs", - "code":"340", + "code":"345", "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", @@ -6377,7 +6464,7 @@ "uri":"admin_guide_000022.html", "node_id":"admin_guide_000022.xml", "product_code":"mrs", - "code":"341", + "code":"346", "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", @@ -6395,7 +6482,7 @@ "uri":"admin_guide_000023.html", "node_id":"admin_guide_000023.xml", "product_code":"mrs", - "code":"342", + "code":"347", "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", @@ -6413,7 +6500,7 @@ "uri":"admin_guide_000024.html", "node_id":"admin_guide_000024.xml", "product_code":"mrs", - "code":"343", + "code":"348", "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", @@ -6431,7 +6518,7 @@ "uri":"admin_guide_000026.html", "node_id":"admin_guide_000026.xml", "product_code":"mrs", - "code":"344", + "code":"349", "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", @@ -6449,7 +6536,7 @@ "uri":"admin_guide_000027.html", "node_id":"admin_guide_000027.xml", "product_code":"mrs", - "code":"345", + "code":"350", "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", @@ -6467,7 +6554,7 @@ "uri":"admin_guide_000029.html", "node_id":"admin_guide_000029.xml", "product_code":"mrs", - "code":"346", + "code":"351", "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", @@ -6485,7 +6572,7 @@ "uri":"admin_guide_000030.html", "node_id":"admin_guide_000030.xml", "product_code":"mrs", - "code":"347", + "code":"352", "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", @@ -6503,7 +6590,7 @@ "uri":"admin_guide_000031.html", "node_id":"admin_guide_000031.xml", "product_code":"mrs", - "code":"348", + "code":"353", "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", @@ -6521,7 +6608,7 @@ "uri":"admin_guide_000032.html", "node_id":"admin_guide_000032.xml", "product_code":"mrs", - "code":"349", + "code":"354", "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", @@ -6539,7 +6626,7 @@ "uri":"admin_guide_000033.html", "node_id":"admin_guide_000033.xml", "product_code":"mrs", - "code":"350", + "code":"355", "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", @@ -6557,7 +6644,7 @@ "uri":"admin_guide_000415.html", "node_id":"admin_guide_000415.xml", "product_code":"mrs", - "code":"351", + "code":"356", "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", @@ -6575,7 +6662,7 @@ "uri":"admin_guide_000034.html", "node_id":"admin_guide_000034.xml", "product_code":"mrs", - "code":"352", + "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":"Service Configuration", @@ -6593,7 +6680,7 @@ "uri":"admin_guide_000035.html", "node_id":"admin_guide_000035.xml", "product_code":"mrs", - "code":"353", + "code":"358", "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", @@ -6611,7 +6698,7 @@ "uri":"admin_guide_000036.html", "node_id":"admin_guide_000036.xml", "product_code":"mrs", - "code":"354", + "code":"359", "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", @@ -6629,7 +6716,7 @@ "uri":"admin_guide_000037.html", "node_id":"admin_guide_000037.xml", "product_code":"mrs", - "code":"355", + "code":"360", "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", @@ -6648,7 +6735,7 @@ "uri":"admin_guide_000038.html", "node_id":"admin_guide_000038.xml", "product_code":"mrs", - "code":"356", + "code":"361", "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", @@ -6666,7 +6753,7 @@ "uri":"admin_guide_000040.html", "node_id":"admin_guide_000040.xml", "product_code":"mrs", - "code":"357", + "code":"362", "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", @@ -6684,7 +6771,7 @@ "uri":"admin_guide_000043.html", "node_id":"admin_guide_000043.xml", "product_code":"mrs", - "code":"358", + "code":"363", "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", @@ -6702,7 +6789,7 @@ "uri":"admin_guide_000044.html", "node_id":"admin_guide_000044.xml", "product_code":"mrs", - "code":"359", + "code":"364", "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", @@ -6720,7 +6807,7 @@ "uri":"admin_guide_000045.html", "node_id":"admin_guide_000045.xml", "product_code":"mrs", - "code":"360", + "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":"Instance Group", @@ -6739,7 +6826,7 @@ "uri":"admin_guide_000046.html", "node_id":"admin_guide_000046.xml", "product_code":"mrs", - "code":"361", + "code":"366", "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", @@ -6757,7 +6844,7 @@ "uri":"admin_guide_000047.html", "node_id":"admin_guide_000047.xml", "product_code":"mrs", - "code":"362", + "code":"367", "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", @@ -6775,7 +6862,7 @@ "uri":"admin_guide_000048.html", "node_id":"admin_guide_000048.xml", "product_code":"mrs", - "code":"363", + "code":"368", "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", @@ -6793,7 +6880,7 @@ "uri":"admin_guide_000049.html", "node_id":"admin_guide_000049.xml", "product_code":"mrs", - "code":"364", + "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":"Hosts", @@ -6812,7 +6899,7 @@ "uri":"admin_guide_000050.html", "node_id":"admin_guide_000050.xml", "product_code":"mrs", - "code":"365", + "code":"370", "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", @@ -6831,7 +6918,7 @@ "uri":"admin_guide_000051.html", "node_id":"admin_guide_000051.xml", "product_code":"mrs", - "code":"366", + "code":"371", "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", @@ -6849,7 +6936,7 @@ "uri":"admin_guide_000052.html", "node_id":"admin_guide_000052.xml", "product_code":"mrs", - "code":"367", + "code":"372", "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", @@ -6867,7 +6954,7 @@ "uri":"admin_guide_000053.html", "node_id":"admin_guide_000053.xml", "product_code":"mrs", - "code":"368", + "code":"373", "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", @@ -6885,7 +6972,7 @@ "uri":"admin_guide_000054.html", "node_id":"admin_guide_000054.xml", "product_code":"mrs", - "code":"369", + "code":"374", "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", @@ -6904,7 +6991,7 @@ "uri":"admin_guide_000056.html", "node_id":"admin_guide_000056.xml", "product_code":"mrs", - "code":"370", + "code":"375", "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", @@ -6922,7 +7009,7 @@ "uri":"admin_guide_000057.html", "node_id":"admin_guide_000057.xml", "product_code":"mrs", - "code":"371", + "code":"376", "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", @@ -6940,7 +7027,7 @@ "uri":"admin_guide_000058.html", "node_id":"admin_guide_000058.xml", "product_code":"mrs", - "code":"372", + "code":"377", "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", @@ -6958,7 +7045,7 @@ "uri":"admin_guide_000059.html", "node_id":"admin_guide_000059.xml", "product_code":"mrs", - "code":"373", + "code":"378", "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", @@ -6976,7 +7063,7 @@ "uri":"admin_guide_000062.html", "node_id":"admin_guide_000062.xml", "product_code":"mrs", - "code":"374", + "code":"379", "des":"Administrators can export information about all hosts on MRS Manager.", "doc_type":"usermanual", "kw":"Exporting Host Information,Host Maintenance Operations,User Guide", @@ -6994,7 +7081,7 @@ "uri":"admin_guide_000063.html", "node_id":"admin_guide_000063.xml", "product_code":"mrs", - "code":"375", + "code":"380", "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", @@ -7013,7 +7100,7 @@ "uri":"admin_guide_000064.html", "node_id":"admin_guide_000064.xml", "product_code":"mrs", - "code":"376", + "code":"381", "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", @@ -7031,7 +7118,7 @@ "uri":"admin_guide_000065.html", "node_id":"admin_guide_000065.xml", "product_code":"mrs", - "code":"377", + "code":"382", "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", @@ -7049,7 +7136,7 @@ "uri":"admin_guide_000066.html", "node_id":"admin_guide_000066.xml", "product_code":"mrs", - "code":"378", + "code":"383", "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", @@ -7067,7 +7154,7 @@ "uri":"admin_guide_000067.html", "node_id":"admin_guide_000067.xml", "product_code":"mrs", - "code":"379", + "code":"384", "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", @@ -7085,7 +7172,7 @@ "uri":"admin_guide_000068.html", "node_id":"admin_guide_000068.xml", "product_code":"mrs", - "code":"380", + "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":"O&M", @@ -7104,7 +7191,7 @@ "uri":"admin_guide_000069.html", "node_id":"admin_guide_000069.xml", "product_code":"mrs", - "code":"381", + "code":"386", "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", @@ -7123,7 +7210,7 @@ "uri":"admin_guide_000070.html", "node_id":"admin_guide_000070.xml", "product_code":"mrs", - "code":"382", + "code":"387", "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", @@ -7141,7 +7228,7 @@ "uri":"admin_guide_000071.html", "node_id":"admin_guide_000071.xml", "product_code":"mrs", - "code":"383", + "code":"388", "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", @@ -7159,7 +7246,7 @@ "uri":"admin_guide_000072.html", "node_id":"admin_guide_000072.xml", "product_code":"mrs", - "code":"384", + "code":"389", "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", @@ -7177,7 +7264,7 @@ "uri":"admin_guide_000073.html", "node_id":"admin_guide_000073.xml", "product_code":"mrs", - "code":"385", + "code":"390", "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", @@ -7196,7 +7283,7 @@ "uri":"admin_guide_000074.html", "node_id":"admin_guide_000074.xml", "product_code":"mrs", - "code":"386", + "code":"391", "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", @@ -7214,7 +7301,7 @@ "uri":"admin_guide_000075.html", "node_id":"admin_guide_000075.xml", "product_code":"mrs", - "code":"387", + "code":"392", "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", @@ -7232,7 +7319,7 @@ "uri":"admin_guide_000076.html", "node_id":"admin_guide_000076.xml", "product_code":"mrs", - "code":"388", + "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":"Perform a Health Check", @@ -7250,7 +7337,7 @@ "uri":"admin_guide_000077.html", "node_id":"admin_guide_000077.xml", "product_code":"mrs", - "code":"389", + "code":"394", "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", @@ -7268,7 +7355,7 @@ "uri":"admin_guide_000078.html", "node_id":"admin_guide_000078.xml", "product_code":"mrs", - "code":"390", + "code":"395", "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", @@ -7286,7 +7373,7 @@ "uri":"admin_guide_000079.html", "node_id":"admin_guide_000079.xml", "product_code":"mrs", - "code":"391", + "code":"396", "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", @@ -7304,7 +7391,7 @@ "uri":"admin_guide_000080.html", "node_id":"admin_guide_000080.xml", "product_code":"mrs", - "code":"392", + "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":"Configuring Backup and Backup Restoration", @@ -7322,7 +7409,7 @@ "uri":"admin_guide_000081.html", "node_id":"admin_guide_000081.xml", "product_code":"mrs", - "code":"393", + "code":"398", "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", @@ -7340,7 +7427,7 @@ "uri":"admin_guide_000082.html", "node_id":"admin_guide_000082.xml", "product_code":"mrs", - "code":"394", + "code":"399", "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", @@ -7358,7 +7445,7 @@ "uri":"admin_guide_000083.html", "node_id":"admin_guide_000083.xml", "product_code":"mrs", - "code":"395", + "code":"400", "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", @@ -7376,7 +7463,7 @@ "uri":"admin_guide_000084.html", "node_id":"admin_guide_000084.xml", "product_code":"mrs", - "code":"396", + "code":"401", "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", @@ -7394,7 +7481,7 @@ "uri":"admin_guide_000085.html", "node_id":"admin_guide_000085.xml", "product_code":"mrs", - "code":"397", + "code":"402", "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", @@ -7412,7 +7499,7 @@ "uri":"admin_guide_000086.html", "node_id":"admin_guide_000086.xml", "product_code":"mrs", - "code":"398", + "code":"403", "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", @@ -7430,7 +7517,7 @@ "uri":"admin_guide_000087.html", "node_id":"admin_guide_000087.xml", "product_code":"mrs", - "code":"399", + "code":"404", "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", @@ -7449,7 +7536,7 @@ "uri":"admin_guide_000088.html", "node_id":"admin_guide_000088.xml", "product_code":"mrs", - "code":"400", + "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":"Multi-Tenancy", @@ -7468,7 +7555,7 @@ "uri":"admin_guide_000089.html", "node_id":"admin_guide_000089.xml", "product_code":"mrs", - "code":"401", + "code":"406", "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", @@ -7486,7 +7573,7 @@ "uri":"admin_guide_000090.html", "node_id":"admin_guide_000090.xml", "product_code":"mrs", - "code":"402", + "code":"407", "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", @@ -7505,7 +7592,7 @@ "uri":"admin_guide_000091.html", "node_id":"admin_guide_000091.xml", "product_code":"mrs", - "code":"403", + "code":"408", "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", @@ -7523,7 +7610,7 @@ "uri":"admin_guide_000092.html", "node_id":"admin_guide_000092.xml", "product_code":"mrs", - "code":"404", + "code":"409", "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", @@ -7541,7 +7628,7 @@ "uri":"admin_guide_000093.html", "node_id":"admin_guide_000093.xml", "product_code":"mrs", - "code":"405", + "code":"410", "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", @@ -7559,7 +7646,7 @@ "uri":"admin_guide_000094.html", "node_id":"admin_guide_000094.xml", "product_code":"mrs", - "code":"406", + "code":"411", "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", @@ -7577,7 +7664,7 @@ "uri":"admin_guide_000095.html", "node_id":"admin_guide_000095.xml", "product_code":"mrs", - "code":"407", + "code":"412", "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", @@ -7595,7 +7682,7 @@ "uri":"admin_guide_000096.html", "node_id":"admin_guide_000096.xml", "product_code":"mrs", - "code":"408", + "code":"413", "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", @@ -7614,7 +7701,7 @@ "uri":"admin_guide_000097.html", "node_id":"admin_guide_000097.xml", "product_code":"mrs", - "code":"409", + "code":"414", "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", @@ -7632,7 +7719,7 @@ "uri":"admin_guide_000098.html", "node_id":"admin_guide_000098.xml", "product_code":"mrs", - "code":"410", + "code":"415", "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", @@ -7650,7 +7737,7 @@ "uri":"admin_guide_000099.html", "node_id":"admin_guide_000099.xml", "product_code":"mrs", - "code":"411", + "code":"416", "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", @@ -7669,7 +7756,7 @@ "uri":"admin_guide_000100.html", "node_id":"admin_guide_000100.xml", "product_code":"mrs", - "code":"412", + "code":"417", "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", @@ -7688,7 +7775,7 @@ "uri":"admin_guide_000101.html", "node_id":"admin_guide_000101.xml", "product_code":"mrs", - "code":"413", + "code":"418", "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", @@ -7706,7 +7793,7 @@ "uri":"admin_guide_000102.html", "node_id":"admin_guide_000102.xml", "product_code":"mrs", - "code":"414", + "code":"419", "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", @@ -7724,7 +7811,7 @@ "uri":"admin_guide_000103.html", "node_id":"admin_guide_000103.xml", "product_code":"mrs", - "code":"415", + "code":"420", "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", @@ -7742,7 +7829,7 @@ "uri":"admin_guide_000104.html", "node_id":"admin_guide_000104.xml", "product_code":"mrs", - "code":"416", + "code":"421", "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", @@ -7761,7 +7848,7 @@ "uri":"admin_guide_000105.html", "node_id":"admin_guide_000105.xml", "product_code":"mrs", - "code":"417", + "code":"422", "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", @@ -7779,7 +7866,7 @@ "uri":"admin_guide_000106.html", "node_id":"admin_guide_000106.xml", "product_code":"mrs", - "code":"418", + "code":"423", "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", @@ -7797,7 +7884,7 @@ "uri":"admin_guide_000107.html", "node_id":"admin_guide_000107.xml", "product_code":"mrs", - "code":"419", + "code":"424", "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", @@ -7815,7 +7902,7 @@ "uri":"admin_guide_000108.html", "node_id":"admin_guide_000108.xml", "product_code":"mrs", - "code":"420", + "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 Resources", @@ -7834,7 +7921,7 @@ "uri":"admin_guide_000109.html", "node_id":"admin_guide_000109.xml", "product_code":"mrs", - "code":"421", + "code":"426", "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", @@ -7852,7 +7939,7 @@ "uri":"admin_guide_000110.html", "node_id":"admin_guide_000110.xml", "product_code":"mrs", - "code":"422", + "code":"427", "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", @@ -7870,7 +7957,7 @@ "uri":"admin_guide_000111.html", "node_id":"admin_guide_000111.xml", "product_code":"mrs", - "code":"423", + "code":"428", "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", @@ -7888,7 +7975,7 @@ "uri":"admin_guide_000112.html", "node_id":"admin_guide_000112.xml", "product_code":"mrs", - "code":"424", + "code":"429", "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", @@ -7906,7 +7993,7 @@ "uri":"admin_guide_000113.html", "node_id":"admin_guide_000113.xml", "product_code":"mrs", - "code":"425", + "code":"430", "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", @@ -7924,7 +8011,7 @@ "uri":"admin_guide_000114.html", "node_id":"admin_guide_000114.xml", "product_code":"mrs", - "code":"426", + "code":"431", "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", @@ -7942,7 +8029,7 @@ "uri":"admin_guide_000115.html", "node_id":"admin_guide_000115.xml", "product_code":"mrs", - "code":"427", + "code":"432", "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", @@ -7960,7 +8047,7 @@ "uri":"admin_guide_000116.html", "node_id":"admin_guide_000116.xml", "product_code":"mrs", - "code":"428", + "code":"433", "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", @@ -7979,7 +8066,7 @@ "uri":"admin_guide_000117.html", "node_id":"admin_guide_000117.xml", "product_code":"mrs", - "code":"429", + "code":"434", "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", @@ -7998,7 +8085,7 @@ "uri":"admin_guide_000118.html", "node_id":"admin_guide_000118.xml", "product_code":"mrs", - "code":"430", + "code":"435", "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", @@ -8016,7 +8103,7 @@ "uri":"admin_guide_000119.html", "node_id":"admin_guide_000119.xml", "product_code":"mrs", - "code":"431", + "code":"436", "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", @@ -8034,7 +8121,7 @@ "uri":"admin_guide_000120.html", "node_id":"admin_guide_000120.xml", "product_code":"mrs", - "code":"432", + "code":"437", "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", @@ -8052,7 +8139,7 @@ "uri":"admin_guide_000121.html", "node_id":"admin_guide_000121.xml", "product_code":"mrs", - "code":"433", + "code":"438", "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", @@ -8071,7 +8158,7 @@ "uri":"admin_guide_000122.html", "node_id":"admin_guide_000122.xml", "product_code":"mrs", - "code":"434", + "code":"439", "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", @@ -8089,7 +8176,7 @@ "uri":"admin_guide_000123.html", "node_id":"admin_guide_000123.xml", "product_code":"mrs", - "code":"435", + "code":"440", "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", @@ -8107,7 +8194,7 @@ "uri":"admin_guide_000124.html", "node_id":"admin_guide_000124.xml", "product_code":"mrs", - "code":"436", + "code":"441", "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", @@ -8125,7 +8212,7 @@ "uri":"admin_guide_000125.html", "node_id":"admin_guide_000125.xml", "product_code":"mrs", - "code":"437", + "code":"442", "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", @@ -8143,7 +8230,7 @@ "uri":"admin_guide_000126.html", "node_id":"admin_guide_000126.xml", "product_code":"mrs", - "code":"438", + "code":"443", "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", @@ -8162,7 +8249,7 @@ "uri":"admin_guide_000127.html", "node_id":"admin_guide_000127.xml", "product_code":"mrs", - "code":"439", + "code":"444", "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", @@ -8180,7 +8267,7 @@ "uri":"admin_guide_000128.html", "node_id":"admin_guide_000128.xml", "product_code":"mrs", - "code":"440", + "code":"445", "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", @@ -8198,7 +8285,7 @@ "uri":"admin_guide_000129.html", "node_id":"admin_guide_000129.xml", "product_code":"mrs", - "code":"441", + "code":"446", "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", @@ -8216,7 +8303,7 @@ "uri":"admin_guide_000130.html", "node_id":"admin_guide_000130.xml", "product_code":"mrs", - "code":"442", + "code":"447", "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", @@ -8234,7 +8321,7 @@ "uri":"admin_guide_000131.html", "node_id":"admin_guide_000131.xml", "product_code":"mrs", - "code":"443", + "code":"448", "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", @@ -8252,7 +8339,7 @@ "uri":"admin_guide_000132.html", "node_id":"admin_guide_000132.xml", "product_code":"mrs", - "code":"444", + "code":"449", "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", @@ -8270,7 +8357,7 @@ "uri":"admin_guide_000133.html", "node_id":"admin_guide_000133.xml", "product_code":"mrs", - "code":"445", + "code":"450", "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", @@ -8288,7 +8375,7 @@ "uri":"admin_guide_000134.html", "node_id":"admin_guide_000134.xml", "product_code":"mrs", - "code":"446", + "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":"System Configuration", @@ -8307,7 +8394,7 @@ "uri":"admin_guide_000135.html", "node_id":"admin_guide_000135.xml", "product_code":"mrs", - "code":"447", + "code":"452", "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", @@ -8326,7 +8413,7 @@ "uri":"admin_guide_000136.html", "node_id":"admin_guide_000136.xml", "product_code":"mrs", - "code":"448", + "code":"453", "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", @@ -8345,7 +8432,7 @@ "uri":"admin_guide_000137.html", "node_id":"admin_guide_000137.xml", "product_code":"mrs", - "code":"449", + "code":"454", "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", @@ -8363,7 +8450,7 @@ "uri":"admin_guide_000138.html", "node_id":"admin_guide_000138.xml", "product_code":"mrs", - "code":"450", + "code":"455", "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", @@ -8381,7 +8468,7 @@ "uri":"admin_guide_000139.html", "node_id":"admin_guide_000139.xml", "product_code":"mrs", - "code":"451", + "code":"456", "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", @@ -8399,7 +8486,7 @@ "uri":"admin_guide_000140.html", "node_id":"admin_guide_000140.xml", "product_code":"mrs", - "code":"452", + "code":"457", "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", @@ -8417,7 +8504,7 @@ "uri":"admin_guide_000141.html", "node_id":"admin_guide_000141.xml", "product_code":"mrs", - "code":"453", + "code":"458", "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", @@ -8435,7 +8522,7 @@ "uri":"admin_guide_000142.html", "node_id":"admin_guide_000142.xml", "product_code":"mrs", - "code":"454", + "code":"459", "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", @@ -8453,7 +8540,7 @@ "uri":"admin_guide_000143.html", "node_id":"admin_guide_000143.xml", "product_code":"mrs", - "code":"455", + "code":"460", "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", @@ -8471,7 +8558,7 @@ "uri":"admin_guide_000144.html", "node_id":"admin_guide_000144.xml", "product_code":"mrs", - "code":"456", + "code":"461", "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", @@ -8489,7 +8576,7 @@ "uri":"admin_guide_000145.html", "node_id":"admin_guide_000145.xml", "product_code":"mrs", - "code":"457", + "code":"462", "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", @@ -8507,7 +8594,7 @@ "uri":"admin_guide_000147.html", "node_id":"admin_guide_000147.xml", "product_code":"mrs", - "code":"458", + "code":"463", "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", @@ -8525,7 +8612,7 @@ "uri":"admin_guide_000148.html", "node_id":"admin_guide_000148.xml", "product_code":"mrs", - "code":"459", + "code":"464", "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", @@ -8543,7 +8630,7 @@ "uri":"admin_guide_000149.html", "node_id":"admin_guide_000149.xml", "product_code":"mrs", - "code":"460", + "code":"465", "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", @@ -8562,7 +8649,7 @@ "uri":"admin_guide_000150.html", "node_id":"admin_guide_000150.xml", "product_code":"mrs", - "code":"461", + "code":"466", "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", @@ -8580,7 +8667,7 @@ "uri":"admin_guide_000151.html", "node_id":"admin_guide_000151.xml", "product_code":"mrs", - "code":"462", + "code":"467", "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", @@ -8598,7 +8685,7 @@ "uri":"admin_guide_000153.html", "node_id":"admin_guide_000153.xml", "product_code":"mrs", - "code":"463", + "code":"468", "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", @@ -8617,7 +8704,7 @@ "uri":"admin_guide_000154.html", "node_id":"admin_guide_000154.xml", "product_code":"mrs", - "code":"464", + "code":"469", "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", @@ -8635,7 +8722,7 @@ "uri":"admin_guide_000155.html", "node_id":"admin_guide_000155.xml", "product_code":"mrs", - "code":"465", + "code":"470", "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", @@ -8653,7 +8740,7 @@ "uri":"admin_guide_000156.html", "node_id":"admin_guide_000156.xml", "product_code":"mrs", - "code":"466", + "code":"471", "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", @@ -8671,7 +8758,7 @@ "uri":"admin_guide_000157.html", "node_id":"admin_guide_000157.xml", "product_code":"mrs", - "code":"467", + "code":"472", "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", @@ -8689,7 +8776,7 @@ "uri":"admin_guide_000159.html", "node_id":"admin_guide_000159.xml", "product_code":"mrs", - "code":"468", + "code":"473", "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", @@ -8707,7 +8794,7 @@ "uri":"admin_guide_000160.html", "node_id":"admin_guide_000160.xml", "product_code":"mrs", - "code":"469", + "code":"474", "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", @@ -8725,7 +8812,7 @@ "uri":"admin_guide_000162.html", "node_id":"admin_guide_000162.xml", "product_code":"mrs", - "code":"470", + "code":"475", "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", @@ -8743,7 +8830,7 @@ "uri":"admin_guide_000164.html", "node_id":"admin_guide_000164.xml", "product_code":"mrs", - "code":"471", + "code":"476", "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", @@ -8762,7 +8849,7 @@ "uri":"admin_guide_000165.html", "node_id":"admin_guide_000165.xml", "product_code":"mrs", - "code":"472", + "code":"477", "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", @@ -8780,7 +8867,7 @@ "uri":"admin_guide_000166.html", "node_id":"admin_guide_000166.xml", "product_code":"mrs", - "code":"473", + "code":"478", "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", @@ -8799,7 +8886,7 @@ "uri":"admin_guide_000170.html", "node_id":"admin_guide_000170.xml", "product_code":"mrs", - "code":"474", + "code":"479", "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", @@ -8817,7 +8904,7 @@ "uri":"admin_guide_000171.html", "node_id":"admin_guide_000171.xml", "product_code":"mrs", - "code":"475", + "code":"480", "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", @@ -8835,7 +8922,7 @@ "uri":"admin_guide_000172.html", "node_id":"admin_guide_000172.xml", "product_code":"mrs", - "code":"476", + "code":"481", "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", @@ -8853,7 +8940,7 @@ "uri":"admin_guide_000173.html", "node_id":"admin_guide_000173.xml", "product_code":"mrs", - "code":"477", + "code":"482", "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", @@ -8871,7 +8958,7 @@ "uri":"admin_guide_000174.html", "node_id":"admin_guide_000174.xml", "product_code":"mrs", - "code":"478", + "code":"483", "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", @@ -8890,7 +8977,7 @@ "uri":"admin_guide_000175.html", "node_id":"admin_guide_000175.xml", "product_code":"mrs", - "code":"479", + "code":"484", "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", @@ -8908,7 +8995,7 @@ "uri":"admin_guide_000176.html", "node_id":"admin_guide_000176.xml", "product_code":"mrs", - "code":"480", + "code":"485", "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", @@ -8926,7 +9013,7 @@ "uri":"admin_guide_000177.html", "node_id":"admin_guide_000177.xml", "product_code":"mrs", - "code":"481", + "code":"486", "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", @@ -8944,7 +9031,7 @@ "uri":"admin_guide_000178.html", "node_id":"admin_guide_000178.xml", "product_code":"mrs", - "code":"482", + "code":"487", "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", @@ -8962,7 +9049,7 @@ "uri":"admin_guide_000182.html", "node_id":"admin_guide_000182.xml", "product_code":"mrs", - "code":"483", + "code":"488", "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", @@ -8980,7 +9067,7 @@ "uri":"admin_guide_000183.html", "node_id":"admin_guide_000183.xml", "product_code":"mrs", - "code":"484", + "code":"489", "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 MRS Manager Routing Table,Cluster Management,User Guide", @@ -8998,7 +9085,7 @@ "uri":"admin_guide_000189.html", "node_id":"admin_guide_000189.xml", "product_code":"mrs", - "code":"485", + "code":"490", "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", @@ -9016,7 +9103,7 @@ "uri":"admin_guide_000191.html", "node_id":"admin_guide_000191.xml", "product_code":"mrs", - "code":"486", + "code":"491", "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", @@ -9034,7 +9121,7 @@ "uri":"admin_guide_000192.html", "node_id":"admin_guide_000192.xml", "product_code":"mrs", - "code":"487", + "code":"492", "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", @@ -9053,7 +9140,7 @@ "uri":"admin_guide_000193.html", "node_id":"admin_guide_000193.xml", "product_code":"mrs", - "code":"488", + "code":"493", "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", @@ -9071,7 +9158,7 @@ "uri":"admin_guide_000194.html", "node_id":"admin_guide_000194.xml", "product_code":"mrs", - "code":"489", + "code":"494", "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", @@ -9089,7 +9176,7 @@ "uri":"admin_guide_000195.html", "node_id":"admin_guide_000195.xml", "product_code":"mrs", - "code":"490", + "code":"495", "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", @@ -9107,7 +9194,7 @@ "uri":"admin_guide_000196.html", "node_id":"admin_guide_000196.xml", "product_code":"mrs", - "code":"491", + "code":"496", "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", @@ -9125,7 +9212,7 @@ "uri":"admin_guide_000197.html", "node_id":"admin_guide_000197.xml", "product_code":"mrs", - "code":"492", + "code":"497", "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", @@ -9143,7 +9230,7 @@ "uri":"admin_guide_000198.html", "node_id":"admin_guide_000198.xml", "product_code":"mrs", - "code":"493", + "code":"498", "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", @@ -9161,7 +9248,7 @@ "uri":"admin_guide_000399.html", "node_id":"admin_guide_000399.xml", "product_code":"mrs", - "code":"494", + "code":"499", "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", @@ -9179,7 +9266,7 @@ "uri":"admin_guide_000201.html", "node_id":"admin_guide_000201.xml", "product_code":"mrs", - "code":"495", + "code":"500", "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", @@ -9197,7 +9284,7 @@ "uri":"admin_guide_000202.html", "node_id":"admin_guide_000202.xml", "product_code":"mrs", - "code":"496", + "code":"501", "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", @@ -9215,7 +9302,7 @@ "uri":"admin_guide_000343.html", "node_id":"admin_guide_000343.xml", "product_code":"mrs", - "code":"497", + "code":"502", "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", @@ -9233,7 +9320,7 @@ "uri":"admin_guide_000348.html", "node_id":"admin_guide_000348.xml", "product_code":"mrs", - "code":"498", + "code":"503", "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", @@ -9251,7 +9338,7 @@ "uri":"admin_guide_000349.html", "node_id":"admin_guide_000349.xml", "product_code":"mrs", - "code":"499", + "code":"504", "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", @@ -9269,7 +9356,7 @@ "uri":"admin_guide_000203.html", "node_id":"admin_guide_000203.xml", "product_code":"mrs", - "code":"500", + "code":"505", "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", @@ -9283,11 +9370,28 @@ "title":"Backing Up DBService Data", "githuburl":"" }, + { + "uri":"admin_guide_000423.html", + "node_id":"admin_guide_000423.xml", + "product_code":"", + "code":"506", + "des":"To ensure Doris service data security, you need to back up Doris service data especially before you perform a major operation on Doris (such as upgrade or migration). The", + "doc_type":"", + "kw":"Backing Up Doris Data,Backing Up Data,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Backing Up Doris Data", + "githuburl":"" + }, { "uri":"admin_guide_000204.html", "node_id":"admin_guide_000204.xml", "product_code":"mrs", - "code":"501", + "code":"507", "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", @@ -9305,7 +9409,7 @@ "uri":"admin_guide_000205.html", "node_id":"admin_guide_000205.xml", "product_code":"mrs", - "code":"502", + "code":"508", "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", @@ -9323,7 +9427,7 @@ "uri":"admin_guide_000208.html", "node_id":"admin_guide_000208.xml", "product_code":"mrs", - "code":"503", + "code":"509", "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", @@ -9341,7 +9445,7 @@ "uri":"admin_guide_000209.html", "node_id":"admin_guide_000209.xml", "product_code":"mrs", - "code":"504", + "code":"510", "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", @@ -9359,7 +9463,7 @@ "uri":"admin_guide_000210.html", "node_id":"admin_guide_000210.xml", "product_code":"mrs", - "code":"505", + "code":"511", "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", @@ -9377,7 +9481,7 @@ "uri":"admin_guide_000350.html", "node_id":"admin_guide_000350.xml", "product_code":"mrs", - "code":"506", + "code":"512", "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", @@ -9395,7 +9499,7 @@ "uri":"admin_guide_000360.html", "node_id":"admin_guide_000360.xml", "product_code":"mrs", - "code":"507", + "code":"513", "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", @@ -9413,7 +9517,7 @@ "uri":"admin_guide_000211.html", "node_id":"admin_guide_000211.xml", "product_code":"mrs", - "code":"508", + "code":"514", "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", @@ -9431,7 +9535,7 @@ "uri":"admin_guide_000215.html", "node_id":"admin_guide_000215.xml", "product_code":"mrs", - "code":"509", + "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":"Recovering Data", @@ -9449,7 +9553,7 @@ "uri":"admin_guide_000216.html", "node_id":"admin_guide_000216.xml", "product_code":"mrs", - "code":"510", + "code":"516", "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", @@ -9467,7 +9571,7 @@ "uri":"admin_guide_000345.html", "node_id":"admin_guide_000345.xml", "product_code":"mrs", - "code":"511", + "code":"517", "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", @@ -9485,7 +9589,7 @@ "uri":"admin_guide_000358.html", "node_id":"admin_guide_000358.xml", "product_code":"mrs", - "code":"512", + "code":"518", "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", @@ -9503,7 +9607,7 @@ "uri":"admin_guide_000359.html", "node_id":"admin_guide_000359.xml", "product_code":"mrs", - "code":"513", + "code":"519", "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", @@ -9521,7 +9625,7 @@ "uri":"admin_guide_000217.html", "node_id":"admin_guide_000217.xml", "product_code":"mrs", - "code":"514", + "code":"520", "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", @@ -9535,11 +9639,28 @@ "title":"Restoring DBService data", "githuburl":"" }, + { + "uri":"admin_guide_000424.html", + "node_id":"admin_guide_000424.xml", + "product_code":"", + "code":"521", + "des":"Doris 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":"", + "kw":"Restoring Doris Service Data,Recovering Data,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Restoring Doris Service Data", + "githuburl":"" + }, { "uri":"admin_guide_000218.html", "node_id":"admin_guide_000218.xml", "product_code":"mrs", - "code":"515", + "code":"522", "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", @@ -9557,7 +9678,7 @@ "uri":"admin_guide_000219.html", "node_id":"admin_guide_000219.xml", "product_code":"mrs", - "code":"516", + "code":"523", "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", @@ -9575,7 +9696,7 @@ "uri":"admin_guide_000222.html", "node_id":"admin_guide_000222.xml", "product_code":"mrs", - "code":"517", + "code":"524", "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", @@ -9593,7 +9714,7 @@ "uri":"admin_guide_000223.html", "node_id":"admin_guide_000223.xml", "product_code":"mrs", - "code":"518", + "code":"525", "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", @@ -9611,7 +9732,7 @@ "uri":"admin_guide_000224.html", "node_id":"admin_guide_000224.xml", "product_code":"mrs", - "code":"519", + "code":"526", "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", @@ -9629,7 +9750,7 @@ "uri":"admin_guide_000351.html", "node_id":"admin_guide_000351.xml", "product_code":"mrs", - "code":"520", + "code":"527", "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", @@ -9647,7 +9768,7 @@ "uri":"admin_guide_000361.html", "node_id":"admin_guide_000361.xml", "product_code":"mrs", - "code":"521", + "code":"528", "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", @@ -9665,7 +9786,7 @@ "uri":"admin_guide_000225.html", "node_id":"admin_guide_000225.xml", "product_code":"mrs", - "code":"522", + "code":"529", "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", @@ -9683,7 +9804,7 @@ "uri":"admin_guide_000200.html", "node_id":"admin_guide_000200.xml", "product_code":"mrs", - "code":"523", + "code":"530", "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", @@ -9701,7 +9822,7 @@ "uri":"admin_guide_000229.html", "node_id":"admin_guide_000229.xml", "product_code":"mrs", - "code":"524", + "code":"531", "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", @@ -9719,7 +9840,7 @@ "uri":"admin_guide_000230.html", "node_id":"admin_guide_000230.xml", "product_code":"mrs", - "code":"525", + "code":"532", "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", @@ -9737,7 +9858,7 @@ "uri":"admin_guide_000231.html", "node_id":"admin_guide_000231.xml", "product_code":"mrs", - "code":"526", + "code":"533", "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", @@ -9755,7 +9876,7 @@ "uri":"admin_guide_000357.html", "node_id":"admin_guide_000357.xml", "product_code":"mrs", - "code":"527", + "code":"534", "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 MRS Manager and Set the", @@ -9773,7 +9894,7 @@ "uri":"admin_guide_000407.html", "node_id":"admin_guide_000407.xml", "product_code":"", - "code":"528", + "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":"", "kw":"SQL Inspector", @@ -9790,7 +9911,7 @@ "uri":"admin_guide_000408.html", "node_id":"admin_guide_000408.xml", "product_code":"", - "code":"529", + "code":"536", "des":"SQL engines in the big data field are emerging one after another. In addition to a wide range of solutions, some problems are exposed. For example, the quality of SQL inp", "doc_type":"", "kw":"Overview,SQL Inspector,User Guide", @@ -9807,8 +9928,8 @@ "uri":"admin_guide_000409.html", "node_id":"admin_guide_000409.xml", "product_code":"", - "code":"530", - "des":"You can add rules for specified tenants and SQL engines on FusionInsight Manager. The system will display hints on, intercept, or block SQL requests matched by the rules.", + "code":"537", + "des":"You can add rules for specified tenants and SQL engines on MRS Manager. The system will display hints on, intercept, or block SQL requests matched by the rules.Exercise c", "doc_type":"", "kw":"Adding an SQL Inspection,SQL Inspector,User Guide", "search_title":"", @@ -9824,8 +9945,8 @@ "uri":"admin_guide_000412.html", "node_id":"admin_guide_000412.xml", "product_code":"", - "code":"531", - "des":"You can configure rules for Hive SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the Hive service has b", + "code":"538", + "des":"You can configure rules for Hive SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the Hive service has been instal", "doc_type":"", "kw":"Configuring Hive SQL Inspection,SQL Inspector,User Guide", "search_title":"", @@ -9841,8 +9962,8 @@ "uri":"admin_guide_000413.html", "node_id":"admin_guide_000413.xml", "product_code":"", - "code":"532", - "des":"You can configure rules for ClickHouse SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the ClickHouse s", + "code":"539", + "des":"You can configure rules for ClickHouse SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the ClickHouse service has", "doc_type":"", "kw":"Configuring ClickHouse SQL Inspection,SQL Inspector,User Guide", "search_title":"", @@ -9858,8 +9979,8 @@ "uri":"admin_guide_000416.html", "node_id":"admin_guide_000416.xml", "product_code":"", - "code":"533", - "des":"You can configure rules for HetuEngine SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the HetuEngine s", + "code":"540", + "des":"You can configure rules for HetuEngine SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the HetuEngine service has", "doc_type":"", "kw":"Configuring HetuEngine SQL Inspection,SQL Inspector,User Guide", "search_title":"", @@ -9875,8 +9996,8 @@ "uri":"admin_guide_000414.html", "node_id":"admin_guide_000414.xml", "product_code":"", - "code":"534", - "des":"You can configure rules for Spark SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the Spark service has", + "code":"541", + "des":"You can configure rules for Spark SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the Spark service has been inst", "doc_type":"", "kw":"Configuring Spark SQL Inspection,SQL Inspector,User Guide", "search_title":"", @@ -9888,11 +10009,28 @@ "title":"Configuring Spark SQL Inspection", "githuburl":"" }, + { + "uri":"admin_guide_000427.html", + "node_id":"admin_guide_000427.xml", + "product_code":"", + "code":"542", + "des":"This function applies only to clusters of MRS 3.5.0 and later versions.You can configure inspection rules for Doris SQL statements on MRS Manager and set rule parameters ", + "doc_type":"", + "kw":"Configuring Doris SQL Inspection,SQL Inspector,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Configuring Doris SQL Inspection", + "githuburl":"" + }, { "uri":"admin_guide_000233.html", "node_id":"admin_guide_000233.xml", "product_code":"mrs", - "code":"535", + "code":"543", "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", @@ -9910,7 +10048,7 @@ "uri":"admin_guide_000234.html", "node_id":"admin_guide_000234.xml", "product_code":"mrs", - "code":"536", + "code":"544", "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", @@ -9928,7 +10066,7 @@ "uri":"admin_guide_000235.html", "node_id":"admin_guide_000235.xml", "product_code":"mrs", - "code":"537", + "code":"545", "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", @@ -9946,7 +10084,7 @@ "uri":"admin_guide_000236.html", "node_id":"admin_guide_000236.xml", "product_code":"mrs", - "code":"538", + "code":"546", "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", @@ -9964,7 +10102,7 @@ "uri":"admin_guide_000237.html", "node_id":"admin_guide_000237.xml", "product_code":"mrs", - "code":"539", + "code":"547", "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", @@ -9982,7 +10120,7 @@ "uri":"admin_guide_000238.html", "node_id":"admin_guide_000238.xml", "product_code":"mrs", - "code":"540", + "code":"548", "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", @@ -10000,7 +10138,7 @@ "uri":"admin_guide_000239.html", "node_id":"admin_guide_000239.xml", "product_code":"mrs", - "code":"541", + "code":"549", "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", @@ -10018,7 +10156,7 @@ "uri":"admin_guide_000240.html", "node_id":"admin_guide_000240.xml", "product_code":"mrs", - "code":"542", + "code":"550", "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", @@ -10036,7 +10174,7 @@ "uri":"admin_guide_000241.html", "node_id":"admin_guide_000241.xml", "product_code":"mrs", - "code":"543", + "code":"551", "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":"MRS Manager Security Functions,Security Overview,User Guide", @@ -10054,7 +10192,7 @@ "uri":"admin_guide_000242.html", "node_id":"admin_guide_000242.xml", "product_code":"mrs", - "code":"544", + "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":"Account Management", @@ -10073,7 +10211,7 @@ "uri":"admin_guide_000243.html", "node_id":"admin_guide_000243.xml", "product_code":"mrs", - "code":"545", + "code":"553", "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", @@ -10092,7 +10230,7 @@ "uri":"admin_guide_000245.html", "node_id":"admin_guide_000245.xml", "product_code":"mrs", - "code":"546", + "code":"554", "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", @@ -10110,7 +10248,7 @@ "uri":"admin_guide_000246.html", "node_id":"admin_guide_000246.xml", "product_code":"mrs", - "code":"547", + "code":"555", "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", @@ -10128,7 +10266,7 @@ "uri":"admin_guide_000247.html", "node_id":"admin_guide_000247.xml", "product_code":"mrs", - "code":"548", + "code":"556", "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 ", @@ -10146,7 +10284,7 @@ "uri":"admin_guide_000248.html", "node_id":"admin_guide_000248.xml", "product_code":"mrs", - "code":"549", + "code":"557", "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 ", @@ -10164,7 +10302,7 @@ "uri":"admin_guide_000249.html", "node_id":"admin_guide_000249.xml", "product_code":"mrs", - "code":"550", + "code":"558", "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", @@ -10183,7 +10321,7 @@ "uri":"admin_guide_000250.html", "node_id":"admin_guide_000250.xml", "product_code":"mrs", - "code":"551", + "code":"559", "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", @@ -10201,7 +10339,7 @@ "uri":"admin_guide_000251.html", "node_id":"admin_guide_000251.xml", "product_code":"mrs", - "code":"552", + "code":"560", "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", @@ -10215,11 +10353,28 @@ "title":"Changing the Password for an OS User", "githuburl":"" }, + { + "uri":"admin_guide_000420.html", + "node_id":"admin_guide_000420.xml", + "product_code":"", + "code":"561", + "des":"By default, the password validity period of an OS user is 90 days. This topic describes how to change the validity period.You are advised to periodically change a user's ", + "doc_type":"", + "kw":"Changing the OS User Password Validity Period,Changing the Password for a System User,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Changing the OS User Password Validity Period", + "githuburl":"" + }, { "uri":"admin_guide_000252.html", "node_id":"admin_guide_000252.xml", "product_code":"mrs", - "code":"553", + "code":"562", "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", @@ -10238,7 +10393,7 @@ "uri":"admin_guide_000253.html", "node_id":"admin_guide_000253.xml", "product_code":"mrs", - "code":"554", + "code":"563", "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", @@ -10256,7 +10411,7 @@ "uri":"admin_guide_000254.html", "node_id":"admin_guide_000254.xml", "product_code":"mrs", - "code":"555", + "code":"564", "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", @@ -10274,7 +10429,7 @@ "uri":"admin_guide_000255.html", "node_id":"admin_guide_000255.xml", "product_code":"mrs", - "code":"556", + "code":"565", "des":"This section applies only to MRS 3.1.0. For later versions, see Modifying OMS Service Configuration Parameters.It is recommended that the administrator periodically chang", "doc_type":"usermanual", "kw":"Changing the Passwords of the LDAP Administrator and the LDAP User (Including OMS LDAP),Changing the", @@ -10292,7 +10447,7 @@ "uri":"admin_guide_000256.html", "node_id":"admin_guide_000256.xml", "product_code":"mrs", - "code":"557", + "code":"566", "des":"This section applies only to MRS 3.1.0. For later versions, see Modifying OMS Service Configuration Parameters.It is recommended that the administrator periodically chang", "doc_type":"usermanual", "kw":"Changing the Password for the LDAP Administrator,Changing the Password for a System Internal User,Us", @@ -10310,7 +10465,7 @@ "uri":"admin_guide_000257.html", "node_id":"admin_guide_000257.xml", "product_code":"mrs", - "code":"558", + "code":"567", "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,", @@ -10328,7 +10483,7 @@ "uri":"admin_guide_000258.html", "node_id":"admin_guide_000258.xml", "product_code":"mrs", - "code":"559", + "code":"568", "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", @@ -10347,7 +10502,7 @@ "uri":"admin_guide_000259.html", "node_id":"admin_guide_000259.xml", "product_code":"mrs", - "code":"560", + "code":"569", "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", @@ -10365,7 +10520,7 @@ "uri":"admin_guide_000260.html", "node_id":"admin_guide_000260.xml", "product_code":"mrs", - "code":"561", + "code":"570", "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", @@ -10383,7 +10538,7 @@ "uri":"admin_guide_000261.html", "node_id":"admin_guide_000261.xml", "product_code":"mrs", - "code":"562", + "code":"571", "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", @@ -10401,7 +10556,7 @@ "uri":"admin_guide_000363.html", "node_id":"admin_guide_000363.xml", "product_code":"mrs", - "code":"563", + "code":"572", "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", @@ -10419,7 +10574,7 @@ "uri":"admin_guide_000354.html", "node_id":"admin_guide_000354.xml", "product_code":"mrs", - "code":"564", + "code":"573", "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", @@ -10437,7 +10592,7 @@ "uri":"admin_guide_000271.html", "node_id":"admin_guide_000271.xml", "product_code":"mrs", - "code":"565", + "code":"574", "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", @@ -10455,7 +10610,7 @@ "uri":"admin_guide_000272.html", "node_id":"admin_guide_000272.xml", "product_code":"mrs", - "code":"566", + "code":"575", "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", @@ -10473,7 +10628,7 @@ "uri":"admin_guide_000274.html", "node_id":"admin_guide_000274.xml", "product_code":"mrs", - "code":"567", + "code":"576", "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", @@ -10491,7 +10646,7 @@ "uri":"admin_guide_000276.html", "node_id":"admin_guide_000276.xml", "product_code":"mrs", - "code":"568", + "code":"577", "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", @@ -10509,7 +10664,7 @@ "uri":"admin_guide_000277.html", "node_id":"admin_guide_000277.xml", "product_code":"mrs", - "code":"569", + "code":"578", "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", @@ -10527,7 +10682,7 @@ "uri":"admin_guide_000278.html", "node_id":"admin_guide_000278.xml", "product_code":"mrs", - "code":"570", + "code":"579", "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", @@ -10545,7 +10700,7 @@ "uri":"admin_guide_000279.html", "node_id":"admin_guide_000279.xml", "product_code":"mrs", - "code":"571", + "code":"580", "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", @@ -10563,7 +10718,7 @@ "uri":"admin_guide_000280.html", "node_id":"admin_guide_000280.xml", "product_code":"mrs", - "code":"572", + "code":"581", "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", @@ -10581,7 +10736,7 @@ "uri":"admin_guide_000281.html", "node_id":"admin_guide_000281.xml", "product_code":"mrs", - "code":"573", + "code":"582", "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", @@ -10599,7 +10754,7 @@ "uri":"admin_guide_000282.html", "node_id":"admin_guide_000282.xml", "product_code":"mrs", - "code":"574", + "code":"583", "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", @@ -10617,7 +10772,7 @@ "uri":"admin_guide_000284.html", "node_id":"admin_guide_000284.xml", "product_code":"mrs", - "code":"575", + "code":"584", "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", @@ -10635,7 +10790,7 @@ "uri":"admin_guide_000285.html", "node_id":"admin_guide_000285.xml", "product_code":"mrs", - "code":"576", + "code":"585", "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", @@ -10653,8 +10808,8 @@ "uri":"admin_guide_000410.html", "node_id":"admin_guide_000410.xml", "product_code":"", - "code":"577", - "des":"FusionInsight Manager allows you to configure the timeout duration of the Manager page based on service requirements. You must properly set the timeout duration to preven", + "code":"586", + "des":"MRS Manager allows you to configure the timeout duration of the Manager page based on service requirements. You must properly set the timeout duration to prevent informat", "doc_type":"", "kw":"Changing the Timeout Duration of the Manager Page,Security Hardening,User Guide", "search_title":"", @@ -10670,7 +10825,7 @@ "uri":"admin_guide_000287.html", "node_id":"admin_guide_000287.xml", "product_code":"mrs", - "code":"578", + "code":"587", "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", @@ -10688,7 +10843,7 @@ "uri":"admin_guide_000289.html", "node_id":"admin_guide_000289.xml", "product_code":"mrs", - "code":"579", + "code":"588", "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", @@ -10706,7 +10861,7 @@ "uri":"admin_guide_000290.html", "node_id":"admin_guide_000290.xml", "product_code":"mrs", - "code":"580", + "code":"589", "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", @@ -10724,7 +10879,7 @@ "uri":"admin_guide_000291.html", "node_id":"admin_guide_000291.xml", "product_code":"mrs", - "code":"581", + "code":"590", "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", @@ -10742,7 +10897,7 @@ "uri":"admin_guide_000315.html", "node_id":"admin_guide_000315.xml", "product_code":"mrs", - "code":"582", + "code":"591", "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", @@ -10760,7 +10915,7 @@ "uri":"mrs_01_1298.html", "node_id":"mrs_01_1298.xml", "product_code":"mrs", - "code":"583", + "code":"592", "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)", @@ -10779,7 +10934,7 @@ "uri":"ALM-12001.html", "node_id":"alm-12001.xml", "product_code":"mrs", - "code":"584", + "code":"593", "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", @@ -10797,7 +10952,7 @@ "uri":"ALM-12004.html", "node_id":"alm-12004.xml", "product_code":"mrs", - "code":"585", + "code":"594", "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", @@ -10815,7 +10970,7 @@ "uri":"ALM-12005.html", "node_id":"alm-12005.xml", "product_code":"mrs", - "code":"586", + "code":"595", "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", @@ -10833,7 +10988,7 @@ "uri":"ALM-12006.html", "node_id":"alm-12006.xml", "product_code":"mrs", - "code":"587", + "code":"596", "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", @@ -10851,7 +11006,7 @@ "uri":"ALM-12007.html", "node_id":"alm-12007.xml", "product_code":"mrs", - "code":"588", + "code":"597", "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", @@ -10869,7 +11024,7 @@ "uri":"ALM-12010.html", "node_id":"alm-12010.xml", "product_code":"mrs", - "code":"589", + "code":"598", "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", @@ -10887,7 +11042,7 @@ "uri":"ALM-12011.html", "node_id":"alm-12011.xml", "product_code":"mrs", - "code":"590", + "code":"599", "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", @@ -10905,7 +11060,7 @@ "uri":"ALM-12012.html", "node_id":"alm-12012.xml", "product_code":"mrs", - "code":"591", + "code":"600", "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", @@ -10923,7 +11078,7 @@ "uri":"ALM-12014.html", "node_id":"alm-12014.xml", "product_code":"mrs", - "code":"592", + "code":"601", "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", @@ -10941,7 +11096,7 @@ "uri":"ALM-12015.html", "node_id":"alm-12015.xml", "product_code":"mrs", - "code":"593", + "code":"602", "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", @@ -10959,7 +11114,7 @@ "uri":"ALM-12016.html", "node_id":"alm-12016.xml", "product_code":"mrs", - "code":"594", + "code":"603", "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", @@ -10977,7 +11132,7 @@ "uri":"ALM-12017.html", "node_id":"alm-12017.xml", "product_code":"mrs", - "code":"595", + "code":"604", "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", @@ -10995,7 +11150,7 @@ "uri":"ALM-12018.html", "node_id":"alm-12018.xml", "product_code":"mrs", - "code":"596", + "code":"605", "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", @@ -11013,7 +11168,7 @@ "uri":"ALM-12027.html", "node_id":"alm-12027.xml", "product_code":"mrs", - "code":"597", + "code":"606", "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", @@ -11031,7 +11186,7 @@ "uri":"ALM-12028.html", "node_id":"alm-12028.xml", "product_code":"mrs", - "code":"598", + "code":"607", "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":"and Z StateALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold,", @@ -11049,7 +11204,7 @@ "uri":"ALM-12033.html", "node_id":"alm-12033.xml", "product_code":"mrs", - "code":"599", + "code":"608", "des":"For MRS 3.3.0 and its later versions:For HDDs, the alarm is triggered when any of the following conditions is met:By default, the system collects data every 3 seconds. Th", "doc_type":"alarm", "kw":"ALM-12033 Slow Disk Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11067,7 +11222,7 @@ "uri":"ALM-12034.html", "node_id":"alm-12034.xml", "product_code":"mrs", - "code":"600", + "code":"609", "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", @@ -11085,7 +11240,7 @@ "uri":"ALM-12035.html", "node_id":"alm-12035.xml", "product_code":"mrs", - "code":"601", + "code":"610", "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", @@ -11103,7 +11258,7 @@ "uri":"ALM-12037.html", "node_id":"alm-12037.xml", "product_code":"mrs", - "code":"602", + "code":"611", "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", @@ -11121,7 +11276,7 @@ "uri":"ALM-12038.html", "node_id":"alm-12038.xml", "product_code":"mrs", - "code":"603", + "code":"612", "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", @@ -11139,7 +11294,7 @@ "uri":"ALM-12039.html", "node_id":"alm-12039.xml", "product_code":"mrs", - "code":"604", + "code":"613", "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", @@ -11157,7 +11312,7 @@ "uri":"ALM-12040.html", "node_id":"alm-12040.xml", "product_code":"mrs", - "code":"605", + "code":"614", "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", @@ -11175,7 +11330,7 @@ "uri":"ALM-12041.html", "node_id":"alm-12041.xml", "product_code":"mrs", - "code":"606", + "code":"615", "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", @@ -11193,7 +11348,7 @@ "uri":"ALM-12042.html", "node_id":"alm-12042.xml", "product_code":"mrs", - "code":"607", + "code":"616", "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", @@ -11211,7 +11366,7 @@ "uri":"ALM-12045.html", "node_id":"alm-12045.xml", "product_code":"mrs", - "code":"608", + "code":"617", "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", @@ -11229,7 +11384,7 @@ "uri":"ALM-12046.html", "node_id":"alm-12046.xml", "product_code":"mrs", - "code":"609", + "code":"618", "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", @@ -11247,7 +11402,7 @@ "uri":"ALM-12047.html", "node_id":"alm-12047.xml", "product_code":"mrs", - "code":"610", + "code":"619", "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 ", @@ -11265,7 +11420,7 @@ "uri":"ALM-12048.html", "node_id":"alm-12048.xml", "product_code":"mrs", - "code":"611", + "code":"620", "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", @@ -11283,7 +11438,7 @@ "uri":"ALM-12049.html", "node_id":"alm-12049.xml", "product_code":"mrs", - "code":"612", + "code":"621", "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)", @@ -11301,7 +11456,7 @@ "uri":"ALM-12050.html", "node_id":"alm-12050.xml", "product_code":"mrs", - "code":"613", + "code":"622", "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", @@ -11319,7 +11474,7 @@ "uri":"ALM-12051.html", "node_id":"alm-12051.xml", "product_code":"mrs", - "code":"614", + "code":"623", "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", @@ -11337,7 +11492,7 @@ "uri":"ALM-12052.html", "node_id":"alm-12052.xml", "product_code":"mrs", - "code":"615", + "code":"624", "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", @@ -11355,7 +11510,7 @@ "uri":"ALM-12053.html", "node_id":"alm-12053.xml", "product_code":"mrs", - "code":"616", + "code":"625", "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 ", @@ -11373,7 +11528,7 @@ "uri":"ALM-12054.html", "node_id":"alm-12054.xml", "product_code":"mrs", - "code":"617", + "code":"626", "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", @@ -11391,7 +11546,7 @@ "uri":"ALM-12055.html", "node_id":"alm-12055.xml", "product_code":"mrs", - "code":"618", + "code":"627", "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", @@ -11409,7 +11564,7 @@ "uri":"ALM-12057.html", "node_id":"alm-12057.xml", "product_code":"mrs", - "code":"619", + "code":"628", "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", @@ -11427,7 +11582,7 @@ "uri":"ALM-12061.html", "node_id":"alm-12061.xml", "product_code":"mrs", - "code":"620", + "code":"629", "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", @@ -11445,7 +11600,7 @@ "uri":"ALM-12062.html", "node_id":"alm-12062.xml", "product_code":"mrs", - "code":"621", + "code":"630", "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", @@ -11463,7 +11618,7 @@ "uri":"ALM-12063.html", "node_id":"alm-12063.xml", "product_code":"mrs", - "code":"622", + "code":"631", "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", @@ -11481,7 +11636,7 @@ "uri":"ALM-12064.html", "node_id":"alm-12064.xml", "product_code":"mrs", - "code":"623", + "code":"632", "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", @@ -11499,7 +11654,7 @@ "uri":"ALM-12066.html", "node_id":"alm-12066.xml", "product_code":"mrs", - "code":"624", + "code":"633", "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", @@ -11517,7 +11672,7 @@ "uri":"ALM-12067.html", "node_id":"alm-12067.xml", "product_code":"mrs", - "code":"625", + "code":"634", "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", @@ -11535,7 +11690,7 @@ "uri":"ALM-12068.html", "node_id":"alm-12068.xml", "product_code":"mrs", - "code":"626", + "code":"635", "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", @@ -11553,7 +11708,7 @@ "uri":"ALM-12069.html", "node_id":"alm-12069.xml", "product_code":"mrs", - "code":"627", + "code":"636", "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", @@ -11571,7 +11726,7 @@ "uri":"ALM-12070.html", "node_id":"alm-12070.xml", "product_code":"mrs", - "code":"628", + "code":"637", "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", @@ -11589,7 +11744,7 @@ "uri":"ALM-12071.html", "node_id":"alm-12071.xml", "product_code":"mrs", - "code":"629", + "code":"638", "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", @@ -11607,7 +11762,7 @@ "uri":"ALM-12072.html", "node_id":"alm-12072.xml", "product_code":"mrs", - "code":"630", + "code":"639", "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", @@ -11625,7 +11780,7 @@ "uri":"ALM-12073.html", "node_id":"alm-12073.xml", "product_code":"mrs", - "code":"631", + "code":"640", "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", @@ -11643,7 +11798,7 @@ "uri":"ALM-12074.html", "node_id":"alm-12074.xml", "product_code":"mrs", - "code":"632", + "code":"641", "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", @@ -11661,7 +11816,7 @@ "uri":"ALM-12075.html", "node_id":"alm-12075.xml", "product_code":"mrs", - "code":"633", + "code":"642", "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", @@ -11679,7 +11834,7 @@ "uri":"ALM-12076.html", "node_id":"alm-12076.xml", "product_code":"mrs", - "code":"634", + "code":"643", "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", @@ -11697,7 +11852,7 @@ "uri":"ALM-12077.html", "node_id":"alm-12077.xml", "product_code":"mrs", - "code":"635", + "code":"644", "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", @@ -11715,7 +11870,7 @@ "uri":"ALM-12078.html", "node_id":"alm-12078.xml", "product_code":"mrs", - "code":"636", + "code":"645", "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", @@ -11733,7 +11888,7 @@ "uri":"ALM-12079.html", "node_id":"alm-12079.xml", "product_code":"mrs", - "code":"637", + "code":"646", "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", @@ -11751,7 +11906,7 @@ "uri":"ALM-12080.html", "node_id":"alm-12080.xml", "product_code":"mrs", - "code":"638", + "code":"647", "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", @@ -11769,7 +11924,7 @@ "uri":"ALM-12081.html", "node_id":"alm-12081.xml", "product_code":"mrs", - "code":"639", + "code":"648", "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-12081 User ommdba Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11787,7 +11942,7 @@ "uri":"ALM-12082.html", "node_id":"alm-12082.xml", "product_code":"mrs", - "code":"640", + "code":"649", "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", @@ -11805,7 +11960,7 @@ "uri":"ALM-12083.html", "node_id":"alm-12083.xml", "product_code":"mrs", - "code":"641", + "code":"650", "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", @@ -11823,7 +11978,7 @@ "uri":"ALM-12084.html", "node_id":"alm-12084.xml", "product_code":"mrs", - "code":"642", + "code":"651", "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", @@ -11841,7 +11996,7 @@ "uri":"ALM-12085.html", "node_id":"alm-12085.xml", "product_code":"mrs", - "code":"643", + "code":"652", "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", @@ -11859,7 +12014,7 @@ "uri":"ALM-12087.html", "node_id":"alm-12087.xml", "product_code":"mrs", - "code":"644", + "code":"653", "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", @@ -11877,7 +12032,7 @@ "uri":"ALM-12089.html", "node_id":"alm-12089.xml", "product_code":"mrs", - "code":"645", + "code":"654", "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", @@ -11895,7 +12050,7 @@ "uri":"ALM-12091.html", "node_id":"alm-12091.xml", "product_code":"", - "code":"646", + "code":"655", "des":"HA checks the disaster resources of Manager every 86 seconds. This alarm is generated when HA detects that the disaster resources have been abnormal for 10 consecutive ti", "doc_type":"", "kw":"ALM-12091 Abnormal disaster Resources,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -11912,7 +12067,7 @@ "uri":"ALM-12101.html", "node_id":"alm-12101.xml", "product_code":"mrs", - "code":"647", + "code":"656", "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", @@ -11930,7 +12085,7 @@ "uri":"ALM-12102.html", "node_id":"alm-12102.xml", "product_code":"mrs", - "code":"648", + "code":"657", "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", @@ -11948,7 +12103,7 @@ "uri":"ALM-12103.html", "node_id":"alm-12103.xml", "product_code":"mrs", - "code":"649", + "code":"658", "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", @@ -11966,7 +12121,7 @@ "uri":"ALM-12104.html", "node_id":"alm-12104.xml", "product_code":"mrs", - "code":"650", + "code":"659", "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", @@ -11984,7 +12139,7 @@ "uri":"ALM-12110.html", "node_id":"alm-12110.xml", "product_code":"mrs", - "code":"651", + "code":"660", "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", @@ -12002,7 +12157,7 @@ "uri":"ALM-12172.html", "node_id":"alm-12172.xml", "product_code":"mrs", - "code":"652", + "code":"661", "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", @@ -12020,7 +12175,7 @@ "uri":"ALM-12180.html", "node_id":"alm-12180.xml", "product_code":"mrs", - "code":"653", + "code":"662", "des":"For MRS 3.3.0 and its later versions:For HDDs, the alarm is triggered when any of the following conditions is met:By default, the system collects data every 3 seconds. Th", "doc_type":"usermanual", "kw":"ALM-12180 Suspended Disk I/O,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12038,7 +12193,7 @@ "uri":"ALM-12186.html", "node_id":"alm-12186.xml", "product_code":"", - "code":"654", + "code":"663", "des":"The system checks the CGroup task usage of user omm every 5 minutes. This alarm is generated when the CGroup task usage exceeds 90%. This alarm is cleared when the CGroup", "doc_type":"", "kw":"ALM-12186 CGroup Task Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12055,7 +12210,7 @@ "uri":"ALM-12187.html", "node_id":"alm-12187.xml", "product_code":"", - "code":"655", + "code":"664", "des":"The system checks the disk space every 60 seconds. When detecting that the disk space is expanded, the system expands disk partition. This alarm is generated when the dis", "doc_type":"", "kw":"ALM-12187 Failed to Expand Disk Partition Capacity,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -12072,7 +12227,7 @@ "uri":"ALM-12188.html", "node_id":"alm-12188.xml", "product_code":"", - "code":"656", + "code":"665", "des":"NodeAgent checks the status of the diskmgt disk monitoring service every 5 minutes. This alarm is generated when diskmgt disk monitoring is unavailable.This alarm is clea", "doc_type":"", "kw":"ALM-12188 diskmgt Disk Monitoring Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12089,7 +12244,7 @@ "uri":"ALM-12190.html", "node_id":"alm-12190.xml", "product_code":"mrs", - "code":"657", + "code":"666", "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", @@ -12103,11 +12258,181 @@ "title":"ALM-12190 Number of Knox Connections Exceeds the Threshold", "githuburl":"" }, + { + "uri":"ALM-12191.html", + "node_id":"alm-12191.xml", + "product_code":"", + "code":"667", + "des":"The system checks the disk I/O usage every 30 seconds and compares the actual disk I/O usage with the threshold. This alarm is generated when the disk I/O usage exceeds t", + "doc_type":"", + "kw":"ALM-12191 Disk I/O Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12191 Disk I/O Usage Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-12192.html", + "node_id":"alm-12192.xml", + "product_code":"", + "code":"668", + "des":"The system checks the average load every 30 seconds and compares the actual average load with the threshold. This alarm is generated when the average load exceeds the thr", + "doc_type":"", + "kw":"ALM-12192 Host Load Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12192 Host Load Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-12200.html", + "node_id":"alm-12200.xml", + "product_code":"", + "code":"669", + "des":"The system checks whether a user password is about to expire at 1:00 a.m. every day. This alarm is generated when a user password is about to expire in less than 5 days b", + "doc_type":"", + "kw":"ALM-12200 Password Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12200 Password Is About to Expire", + "githuburl":"" + }, + { + "uri":"ALM-12201.html", + "node_id":"alm-12201.xml", + "product_code":"", + "code":"670", + "des":"The system checks the CPU usage every 30 seconds and compares the check result with the default threshold. This alarm is generated when the CPU usage exceeds the threshol", + "doc_type":"", + "kw":"ALM-12201 Process CPU Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12201 Process CPU Usage Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-12202.html", + "node_id":"alm-12202.xml", + "product_code":"", + "code":"671", + "des":"The system checks the memory usage of main OMS processes every 30 seconds. This alarm is generated when the memory usage of main OMS processes is greater than 90% (defaul", + "doc_type":"", + "kw":"ALM-12202 Process Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Gu", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12202 Process Memory Usage Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-12203.html", + "node_id":"alm-12203.xml", + "product_code":"", + "code":"672", + "des":"The system checks the GC duration of main OMS processes every 30 seconds. If the GC duration of an OMS process exceeds the threshold for three consecutive times, this ala", + "doc_type":"", + "kw":"ALM-12203 Process Full GC Duration Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12203 Process Full GC Duration Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-12204.html", + "node_id":"alm-12204.xml", + "product_code":"", + "code":"673", + "des":"The system checks the wait duration of a disk read every 30 seconds and compares the actual wait duration with the threshold. This alarm is generated when the wait durati", + "doc_type":"", + "kw":"ALM-12204 Wait Duration of a Disk Read Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12204 Wait Duration of a Disk Read Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-12205.html", + "node_id":"alm-12205.xml", + "product_code":"", + "code":"674", + "des":"The system checks the wait duration of a disk write every 30 seconds and compares the actual wait duration with the threshold. This alarm is generated when the wait durat", + "doc_type":"", + "kw":"ALM-12205 Wait Duration of a Disk Write Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12205 Wait Duration of a Disk Write Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-12206.html", + "node_id":"alm-12206.xml", + "product_code":"", + "code":"675", + "des":"The system checks whether a user password has expired at 1:00 a.m. every day. This alarm is generated when a user password has expired.This alarm is cleared when the user", + "doc_type":"", + "kw":"ALM-12206 Password Has Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12206 Password Has Expired", + "githuburl":"" + }, + { + "uri":"ALM-12207.html", + "node_id":"alm-12207.xml", + "product_code":"", + "code":"676", + "des":"When slow disk detection is enabled, the system checks the slow disk processing status every 10 minutes by default. This alarm is generated when the following disk or nod", + "doc_type":"", + "kw":"ALM-12207 Slow Disk Processing Timeout,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-12207 Slow Disk Processing Timeout", + "githuburl":"" + }, { "uri":"ALM-13000.html", "node_id":"alm-13000.xml", "product_code":"mrs", - "code":"658", + "code":"677", "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", @@ -12125,7 +12450,7 @@ "uri":"ALM-13001.html", "node_id":"alm-13001.xml", "product_code":"mrs", - "code":"659", + "code":"678", "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", @@ -12143,7 +12468,7 @@ "uri":"ALM-13002.html", "node_id":"alm-13002.xml", "product_code":"mrs", - "code":"660", + "code":"679", "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", @@ -12161,7 +12486,7 @@ "uri":"ALM-13003.html", "node_id":"alm-13003.xml", "product_code":"mrs", - "code":"661", + "code":"680", "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 ", @@ -12179,7 +12504,7 @@ "uri":"ALM-13004.html", "node_id":"alm-13004.xml", "product_code":"mrs", - "code":"662", + "code":"681", "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),", @@ -12197,7 +12522,7 @@ "uri":"ALM-13005.html", "node_id":"alm-13005.xml", "product_code":"mrs", - "code":"663", + "code":"682", "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", @@ -12215,7 +12540,7 @@ "uri":"ALM-13006.html", "node_id":"alm-13006.xml", "product_code":"mrs", - "code":"664", + "code":"683", "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", @@ -12233,7 +12558,7 @@ "uri":"ALM-13007.html", "node_id":"alm-13007.xml", "product_code":"mrs", - "code":"665", + "code":"684", "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", @@ -12251,7 +12576,7 @@ "uri":"ALM-13008.html", "node_id":"alm-13008.xml", "product_code":"mrs", - "code":"666", + "code":"685", "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", @@ -12269,7 +12594,7 @@ "uri":"ALM-13009.html", "node_id":"alm-13009.xml", "product_code":"mrs", - "code":"667", + "code":"686", "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.", @@ -12287,7 +12612,7 @@ "uri":"ALM-13010.html", "node_id":"alm-13010.xml", "product_code":"mrs", - "code":"668", + "code":"687", "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", @@ -12305,7 +12630,7 @@ "uri":"ALM-14000.html", "node_id":"alm-14000.xml", "product_code":"mrs", - "code":"669", + "code":"688", "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", @@ -12323,7 +12648,7 @@ "uri":"ALM-14001.html", "node_id":"alm-14001.xml", "product_code":"mrs", - "code":"670", + "code":"689", "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", @@ -12341,7 +12666,7 @@ "uri":"ALM-14002.html", "node_id":"alm-14002.xml", "product_code":"mrs", - "code":"671", + "code":"690", "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", @@ -12359,7 +12684,7 @@ "uri":"ALM-14003.html", "node_id":"alm-14003.xml", "product_code":"mrs", - "code":"672", + "code":"691", "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", @@ -12377,7 +12702,7 @@ "uri":"ALM-14006.html", "node_id":"alm-14006.xml", "product_code":"mrs", - "code":"673", + "code":"692", "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", @@ -12395,7 +12720,7 @@ "uri":"ALM-14007.html", "node_id":"alm-14007.xml", "product_code":"mrs", - "code":"674", + "code":"693", "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", @@ -12413,7 +12738,7 @@ "uri":"ALM-14008.html", "node_id":"alm-14008.xml", "product_code":"mrs", - "code":"675", + "code":"694", "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", @@ -12431,7 +12756,7 @@ "uri":"ALM-14009.html", "node_id":"alm-14009.xml", "product_code":"mrs", - "code":"676", + "code":"695", "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", @@ -12449,7 +12774,7 @@ "uri":"ALM-14010.html", "node_id":"alm-14010.xml", "product_code":"mrs", - "code":"677", + "code":"696", "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", @@ -12467,7 +12792,7 @@ "uri":"ALM-14011.html", "node_id":"alm-14011.xml", "product_code":"mrs", - "code":"678", + "code":"697", "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)", @@ -12485,7 +12810,7 @@ "uri":"ALM-14012.html", "node_id":"alm-14012.xml", "product_code":"mrs", - "code":"679", + "code":"698", "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", @@ -12503,7 +12828,7 @@ "uri":"ALM-14013.html", "node_id":"alm-14013.xml", "product_code":"mrs", - "code":"680", + "code":"699", "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", @@ -12521,7 +12846,7 @@ "uri":"ALM-14014.html", "node_id":"alm-14014.xml", "product_code":"mrs", - "code":"681", + "code":"700", "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", @@ -12539,7 +12864,7 @@ "uri":"ALM-14015.html", "node_id":"alm-14015.xml", "product_code":"mrs", - "code":"682", + "code":"701", "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", @@ -12557,7 +12882,7 @@ "uri":"ALM-14016.html", "node_id":"alm-14016.xml", "product_code":"mrs", - "code":"683", + "code":"702", "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)", @@ -12575,7 +12900,7 @@ "uri":"ALM-14017.html", "node_id":"alm-14017.xml", "product_code":"mrs", - "code":"684", + "code":"703", "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)", @@ -12593,7 +12918,7 @@ "uri":"ALM-14018.html", "node_id":"alm-14018.xml", "product_code":"mrs", - "code":"685", + "code":"704", "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.", @@ -12611,7 +12936,7 @@ "uri":"ALM-14019.html", "node_id":"alm-14019.xml", "product_code":"mrs", - "code":"686", + "code":"705", "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.", @@ -12629,7 +12954,7 @@ "uri":"ALM-14020.html", "node_id":"alm-14020.xml", "product_code":"mrs", - "code":"687", + "code":"706", "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 ", @@ -12647,7 +12972,7 @@ "uri":"ALM-14021.html", "node_id":"alm-14021.xml", "product_code":"mrs", - "code":"688", + "code":"707", "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 ", @@ -12665,7 +12990,7 @@ "uri":"ALM-14022.html", "node_id":"alm-14022.xml", "product_code":"mrs", - "code":"689", + "code":"708", "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", @@ -12683,7 +13008,7 @@ "uri":"ALM-14023.html", "node_id":"alm-14023.xml", "product_code":"mrs", - "code":"690", + "code":"709", "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", @@ -12701,7 +13026,7 @@ "uri":"ALM-14024.html", "node_id":"alm-14024.xml", "product_code":"mrs", - "code":"691", + "code":"710", "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", @@ -12719,7 +13044,7 @@ "uri":"ALM-14025.html", "node_id":"alm-14025.xml", "product_code":"mrs", - "code":"692", + "code":"711", "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", @@ -12737,7 +13062,7 @@ "uri":"ALM-14026.html", "node_id":"alm-14026.xml", "product_code":"mrs", - "code":"693", + "code":"712", "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", @@ -12755,7 +13080,7 @@ "uri":"ALM-14027.html", "node_id":"alm-14027.xml", "product_code":"mrs", - "code":"694", + "code":"713", "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", @@ -12773,7 +13098,7 @@ "uri":"ALM-14028.html", "node_id":"alm-14028.xml", "product_code":"mrs", - "code":"695", + "code":"714", "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", @@ -12791,7 +13116,7 @@ "uri":"ALM-14029.html", "node_id":"alm-14029.xml", "product_code":"mrs", - "code":"696", + "code":"715", "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", @@ -12809,7 +13134,7 @@ "uri":"ALM-14030.html", "node_id":"alm-14030.xml", "product_code":"mrs", - "code":"697", + "code":"716", "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", @@ -12827,7 +13152,7 @@ "uri":"ALM-14031.html", "node_id":"alm-14031.xml", "product_code":"", - "code":"698", + "code":"717", "des":"The DataNode process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This ala", "doc_type":"", "kw":"ALM-14031 DataNode Process Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12844,7 +13169,7 @@ "uri":"ALM-14032.html", "node_id":"alm-14032.xml", "product_code":"", - "code":"699", + "code":"718", "des":"The JournalNode process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This ", "doc_type":"", "kw":"ALM-14032 JournalNode Process Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12861,7 +13186,7 @@ "uri":"ALM-14033.html", "node_id":"alm-14033.xml", "product_code":"", - "code":"700", + "code":"719", "des":"The ZKFC process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This alarm i", "doc_type":"", "kw":"ALM-14033 ZKFC Process Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12878,7 +13203,7 @@ "uri":"ALM-14034.html", "node_id":"alm-14034.xml", "product_code":"", - "code":"701", + "code":"720", "des":"The Router process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This alarm", "doc_type":"", "kw":"ALM-14034 Router Process Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12895,7 +13220,7 @@ "uri":"ALM-14035.html", "node_id":"alm-14035.xml", "product_code":"", - "code":"702", + "code":"721", "des":"The HttpFS process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This alarm", "doc_type":"", "kw":"ALM-14035 HttpFS Process Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -12908,11 +13233,79 @@ "title":"ALM-14035 HttpFS Process Is Abnormal", "githuburl":"" }, + { + "uri":"ALM-14036.html", + "node_id":"alm-14036.xml", + "product_code":"", + "code":"722", + "des":"This alarm applies only to MRS 3.3.1 or later.The system checks the NameNode process status every 30 seconds. This alarm is generated when the NameNode is in the safe mod", + "doc_type":"", + "kw":"ALM-14036 NameNode Is In Safe Mode,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-14036 NameNode Is In Safe Mode", + "githuburl":"" + }, + { + "uri":"ALM-14037.html", + "node_id":"alm-14037.xml", + "product_code":"", + "code":"723", + "des":"This alarm applies only to MRS 3.3.1 or later.The NameNode checks whether there are DataNodes that are not managed in the cluster every 8 hours. This alarm is generated w", + "doc_type":"", + "kw":"ALM-14037 DataNodes Outside the Cluster,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-14037 DataNodes Outside the Cluster", + "githuburl":"" + }, + { + "uri":"ALM-14038.html", + "node_id":"alm-14038.xml", + "product_code":"", + "code":"724", + "des":"The system checks the size of the used HDFS Router heap memory and the maximum size of the heap memory that can be allocated every 30 seconds, calculates the ratio of the", + "doc_type":"", + "kw":"ALM-14038 Router Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),Use", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-14038 Router Heap Memory Usage Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-14039.html", + "node_id":"alm-14039.xml", + "product_code":"", + "code":"725", + "des":"The system checks the number of slow operations per second on HDFS DataNode instances every 60 seconds and compares the number with the threshold. This alarm is generated", + "doc_type":"", + "kw":"ALM-14039 Slow DataNodes Exist in the Cluster,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-14039 Slow DataNodes Exist in the Cluster", + "githuburl":"" + }, { "uri":"ALM-16000.html", "node_id":"alm-16000.xml", "product_code":"mrs", - "code":"703", + "code":"726", "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", @@ -12930,7 +13323,7 @@ "uri":"ALM-16001.html", "node_id":"alm-16001.xml", "product_code":"mrs", - "code":"704", + "code":"727", "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", @@ -12948,7 +13341,7 @@ "uri":"ALM-16002.html", "node_id":"alm-16002.xml", "product_code":"mrs", - "code":"705", + "code":"728", "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", @@ -12966,7 +13359,7 @@ "uri":"ALM-16003.html", "node_id":"alm-16003.xml", "product_code":"mrs", - "code":"706", + "code":"729", "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", @@ -12984,7 +13377,7 @@ "uri":"ALM-16004.html", "node_id":"alm-16004.xml", "product_code":"mrs", - "code":"707", + "code":"730", "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", @@ -13002,7 +13395,7 @@ "uri":"ALM-16005.html", "node_id":"alm-16005.xml", "product_code":"mrs", - "code":"708", + "code":"731", "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", @@ -13020,7 +13413,7 @@ "uri":"ALM-16006.html", "node_id":"alm-16006.xml", "product_code":"mrs", - "code":"709", + "code":"732", "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", @@ -13038,7 +13431,7 @@ "uri":"ALM-16007.html", "node_id":"alm-16007.xml", "product_code":"mrs", - "code":"710", + "code":"733", "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", @@ -13056,7 +13449,7 @@ "uri":"ALM-16008.html", "node_id":"alm-16008.xml", "product_code":"mrs", - "code":"711", + "code":"734", "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", @@ -13074,7 +13467,7 @@ "uri":"ALM-16009.html", "node_id":"alm-16009.xml", "product_code":"mrs", - "code":"712", + "code":"735", "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", @@ -13092,7 +13485,7 @@ "uri":"ALM-16045.html", "node_id":"alm-16045.xml", "product_code":"mrs", - "code":"713", + "code":"736", "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", @@ -13110,7 +13503,7 @@ "uri":"ALM-16046.html", "node_id":"alm-16046.xml", "product_code":"mrs", - "code":"714", + "code":"737", "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", @@ -13128,7 +13521,7 @@ "uri":"ALM-16047.html", "node_id":"alm-16047.xml", "product_code":"mrs", - "code":"715", + "code":"738", "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", @@ -13146,7 +13539,7 @@ "uri":"ALM-16048.html", "node_id":"alm-16048.xml", "product_code":"mrs", - "code":"716", + "code":"739", "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", @@ -13160,11 +13553,62 @@ "title":"ALM-16048 Tez or Spark Library Path Does Not Exist", "githuburl":"" }, + { + "uri":"ALM-16051.html", + "node_id":"alm-16051.xml", + "product_code":"", + "code":"740", + "des":"The system checks the percentage of sessions connected to MetaStore to the maximum number of sessions allowed by MetaStore every 30 seconds. This alarm is generated when ", + "doc_type":"", + "kw":"ALM-16051 Percentage of Sessions Connected to MetaStore Exceeds the Threshold,Alarm Reference (Appli", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-16051 Percentage of Sessions Connected to MetaStore Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-16052.html", + "node_id":"alm-16052.xml", + "product_code":"", + "code":"741", + "des":"The system periodically checks the latency for MetaStore to access the meta database during table creation. This alarm is generated when the average latency in the last 5", + "doc_type":"", + "kw":"ALM-16052 Latency for MetaStore to Access the Meta Database During Table Creation Exceeds the Thresh", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-16052 Latency for MetaStore to Access the Meta Database During Table Creation Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-16053.html", + "node_id":"alm-16053.xml", + "product_code":"", + "code":"742", + "des":"The system periodically checks the average HQL submission time, which is the time for calling the MapReduce/Spark/Tez APIs to submit Yarn jobs, including the time for upl", + "doc_type":"", + "kw":"ALM-16053 Average HQL Submission Time of Hive in the Last 5 Minutes Exceeds the Threshold,Alarm Refe", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-16053 Average HQL Submission Time of Hive in the Last 5 Minutes Exceeds the Threshold", + "githuburl":"" + }, { "uri":"ALM-17003.html", "node_id":"alm-17003.xml", "product_code":"mrs", - "code":"717", + "code":"743", "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", @@ -13182,7 +13626,7 @@ "uri":"ALM-17004.html", "node_id":"alm-17004.xml", "product_code":"mrs", - "code":"718", + "code":"744", "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", @@ -13200,7 +13644,7 @@ "uri":"ALM-17005.html", "node_id":"alm-17005.xml", "product_code":"mrs", - "code":"719", + "code":"745", "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),", @@ -13218,7 +13662,7 @@ "uri":"ALM-17006.html", "node_id":"alm-17006.xml", "product_code":"mrs", - "code":"720", + "code":"746", "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", @@ -13236,7 +13680,7 @@ "uri":"ALM-17007.html", "node_id":"alm-17007.xml", "product_code":"mrs", - "code":"721", + "code":"747", "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", @@ -13250,11 +13694,79 @@ "title":"ALM-17007 Garbage Collection (GC) Time of the Oozie Process Exceeds the Threshold", "githuburl":"" }, + { + "uri":"ALM-17008.html", + "node_id":"alm-17008.xml", + "product_code":"", + "code":"748", + "des":"In HA mode, Oozie depends on ZooKeeper. This alarm is generated when the connection between Oozie and ZooKeeper is abnormal for three consecutive times.This alarm is clea", + "doc_type":"", + "kw":"ALM-17008 Abnormal Connection Between Oozie and ZooKeeper,Alarm Reference (Applicable to MRS 3.x),Us", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-17008 Abnormal Connection Between Oozie and ZooKeeper", + "githuburl":"" + }, + { + "uri":"ALM-17009.html", + "node_id":"alm-17009.xml", + "product_code":"", + "code":"749", + "des":"Oozie depends on DBService. After a task is submitted, the system checks DBService connectivity. This alarm is generated when the service fails the check for 10 consecuti", + "doc_type":"", + "kw":"ALM-17009 Abnormal Connection Between Oozie and DBService,Alarm Reference (Applicable to MRS 3.x),Us", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-17009 Abnormal Connection Between Oozie and DBService", + "githuburl":"" + }, + { + "uri":"ALM-17010.html", + "node_id":"alm-17010.xml", + "product_code":"", + "code":"750", + "des":"Oozie depends on HDFS. After a task is submitted, the system checks HDFS connectivity. This alarm is generated when the service fails the check for 3 consecutive times.Th", + "doc_type":"", + "kw":"ALM-17010 Abnormal Connection Between Oozie and HDFS,Alarm Reference (Applicable to MRS 3.x),User Gu", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-17010 Abnormal Connection Between Oozie and HDFS", + "githuburl":"" + }, + { + "uri":"ALM-17011.html", + "node_id":"alm-17011.xml", + "product_code":"", + "code":"751", + "des":"Oozie depends on YARN. After a task is submitted, the system checks YARN connectivity. This alarm is generated when the service fails the check for 5 consecutive times.Th", + "doc_type":"", + "kw":"ALM-17011 Abnormal Connection Between Oozie and YARN,Alarm Reference (Applicable to MRS 3.x),User Gu", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-17011 Abnormal Connection Between Oozie and YARN", + "githuburl":"" + }, { "uri":"ALM-18000.html", "node_id":"alm-18000.xml", "product_code":"mrs", - "code":"722", + "code":"752", "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", @@ -13272,7 +13784,7 @@ "uri":"ALM-18002.html", "node_id":"alm-18002.xml", "product_code":"mrs", - "code":"723", + "code":"753", "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", @@ -13290,7 +13802,7 @@ "uri":"ALM-18003.html", "node_id":"alm-18003.xml", "product_code":"mrs", - "code":"724", + "code":"754", "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", @@ -13308,7 +13820,7 @@ "uri":"ALM-18008.html", "node_id":"alm-18008.xml", "product_code":"mrs", - "code":"725", + "code":"755", "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 ", @@ -13326,7 +13838,7 @@ "uri":"ALM-18009.html", "node_id":"alm-18009.xml", "product_code":"mrs", - "code":"726", + "code":"756", "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", @@ -13344,7 +13856,7 @@ "uri":"ALM-18010.html", "node_id":"alm-18010.xml", "product_code":"mrs", - "code":"727", + "code":"757", "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", @@ -13362,7 +13874,7 @@ "uri":"ALM-18011.html", "node_id":"alm-18011.xml", "product_code":"mrs", - "code":"728", + "code":"758", "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", @@ -13380,7 +13892,7 @@ "uri":"ALM-18012.html", "node_id":"alm-18012.xml", "product_code":"mrs", - "code":"729", + "code":"759", "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", @@ -13398,7 +13910,7 @@ "uri":"ALM-18013.html", "node_id":"alm-18013.xml", "product_code":"mrs", - "code":"730", + "code":"760", "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", @@ -13416,7 +13928,7 @@ "uri":"ALM-18014.html", "node_id":"alm-18014.xml", "product_code":"mrs", - "code":"731", + "code":"761", "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", @@ -13434,7 +13946,7 @@ "uri":"ALM-18015.html", "node_id":"alm-18015.xml", "product_code":"mrs", - "code":"732", + "code":"762", "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 ", @@ -13452,7 +13964,7 @@ "uri":"ALM-18016.html", "node_id":"alm-18016.xml", "product_code":"mrs", - "code":"733", + "code":"763", "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", @@ -13470,7 +13982,7 @@ "uri":"ALM-18017.html", "node_id":"alm-18017.xml", "product_code":"mrs", - "code":"734", + "code":"764", "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 ", @@ -13488,7 +14000,7 @@ "uri":"ALM-18018.html", "node_id":"alm-18018.xml", "product_code":"mrs", - "code":"735", + "code":"765", "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", @@ -13506,7 +14018,7 @@ "uri":"ALM-18019.html", "node_id":"alm-18019.xml", "product_code":"mrs", - "code":"736", + "code":"766", "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", @@ -13524,7 +14036,7 @@ "uri":"ALM-18020.html", "node_id":"alm-18020.xml", "product_code":"mrs", - "code":"737", + "code":"767", "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", @@ -13542,7 +14054,7 @@ "uri":"ALM-18021.html", "node_id":"alm-18021.xml", "product_code":"mrs", - "code":"738", + "code":"768", "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", @@ -13560,7 +14072,7 @@ "uri":"ALM-18022.html", "node_id":"alm-18022.xml", "product_code":"mrs", - "code":"739", + "code":"769", "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", @@ -13578,7 +14090,7 @@ "uri":"ALM-18023.html", "node_id":"alm-18023.xml", "product_code":"mrs", - "code":"740", + "code":"770", "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)", @@ -13596,7 +14108,7 @@ "uri":"ALM-18024.html", "node_id":"alm-18024.xml", "product_code":"mrs", - "code":"741", + "code":"771", "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", @@ -13614,7 +14126,7 @@ "uri":"ALM-18025.html", "node_id":"alm-18025.xml", "product_code":"mrs", - "code":"742", + "code":"772", "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", @@ -13632,7 +14144,7 @@ "uri":"ALM-18026.html", "node_id":"alm-18026.xml", "product_code":"mrs", - "code":"743", + "code":"773", "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),", @@ -13650,7 +14162,7 @@ "uri":"ALM-19000.html", "node_id":"alm-19000.xml", "product_code":"mrs", - "code":"744", + "code":"774", "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", @@ -13668,7 +14180,7 @@ "uri":"ALM-19006.html", "node_id":"alm-19006.xml", "product_code":"mrs", - "code":"745", + "code":"775", "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", @@ -13686,7 +14198,7 @@ "uri":"ALM-19007.html", "node_id":"alm-19007.xml", "product_code":"mrs", - "code":"746", + "code":"776", "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", @@ -13704,7 +14216,7 @@ "uri":"ALM-19008.html", "node_id":"alm-19008.xml", "product_code":"mrs", - "code":"747", + "code":"777", "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", @@ -13722,7 +14234,7 @@ "uri":"ALM-19009.html", "node_id":"alm-19009.xml", "product_code":"mrs", - "code":"748", + "code":"778", "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", @@ -13740,7 +14252,7 @@ "uri":"ALM-19011.html", "node_id":"alm-19011.xml", "product_code":"mrs", - "code":"749", + "code":"779", "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", @@ -13758,7 +14270,7 @@ "uri":"ALM-19012.html", "node_id":"alm-19012.xml", "product_code":"mrs", - "code":"750", + "code":"780", "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", @@ -13776,7 +14288,7 @@ "uri":"ALM-19013.html", "node_id":"alm-19013.xml", "product_code":"mrs", - "code":"751", + "code":"781", "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", @@ -13794,7 +14306,7 @@ "uri":"ALM-19014.html", "node_id":"alm-19014.xml", "product_code":"mrs", - "code":"752", + "code":"782", "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", @@ -13812,7 +14324,7 @@ "uri":"ALM-19015.html", "node_id":"alm-19015.xml", "product_code":"mrs", - "code":"753", + "code":"783", "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", @@ -13830,7 +14342,7 @@ "uri":"ALM-19016.html", "node_id":"alm-19016.xml", "product_code":"mrs", - "code":"754", + "code":"784", "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", @@ -13848,7 +14360,7 @@ "uri":"ALM-19017.html", "node_id":"alm-19017.xml", "product_code":"mrs", - "code":"755", + "code":"785", "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", @@ -13866,7 +14378,7 @@ "uri":"ALM-19018.html", "node_id":"alm-19018.xml", "product_code":"mrs", - "code":"756", + "code":"786", "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),", @@ -13884,7 +14396,7 @@ "uri":"ALM-19019.html", "node_id":"alm-19019.xml", "product_code":"mrs", - "code":"757", + "code":"787", "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", @@ -13902,7 +14414,7 @@ "uri":"ALM-19020.html", "node_id":"alm-19020.xml", "product_code":"mrs", - "code":"758", + "code":"788", "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", @@ -13920,7 +14432,7 @@ "uri":"ALM-19021.html", "node_id":"alm-19021.xml", "product_code":"mrs", - "code":"759", + "code":"789", "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", @@ -13938,7 +14450,7 @@ "uri":"ALM-19022.html", "node_id":"alm-19022.xml", "product_code":"", - "code":"760", + "code":"790", "des":"When the MetricController instance is installed for HBase, the alarm module checks the health status of the active HBase MetricController instance every 120 seconds. This", "doc_type":"", "kw":"ALM-19022 HBase Hotspot Detection Is Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13955,7 +14467,7 @@ "uri":"ALM-19023.html", "node_id":"alm-19023.xml", "product_code":"", - "code":"761", + "code":"791", "des":"When the MetricController instance is installed for the HBase service, self-healing from hotspotting is automatically enabled. The alarm module checks whether there are r", "doc_type":"", "kw":"ALM-19023 Region Traffic Restriction for HBase,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -13972,7 +14484,7 @@ "uri":"ALM-19024.html", "node_id":"alm-19024.xml", "product_code":"", - "code":"762", + "code":"792", "des":"The system checks P99 latency for RPC requests on each RegionServer instance of the HBase service every 30 seconds. This alarm is generated when P99 latency for RPC reque", "doc_type":"", "kw":"ALM-19024 RPC Requests P99 Latency on RegionServer Exceeds the Threshold,Alarm Reference (Applicable", @@ -13989,7 +14501,7 @@ "uri":"ALM-19025.html", "node_id":"alm-19025.xml", "product_code":"", - "code":"763", + "code":"793", "des":"The system checks the hdfs://hacluster/hbase/autocorrupt and hdfs://hacluster/hbase/MasterData/autocorrupt directories on HDFS of each HBase service every 120 seconds. Th", "doc_type":"", "kw":"ALM-19025 Damaged StoreFile in HBase,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14006,7 +14518,7 @@ "uri":"ALM-19026.html", "node_id":"alm-19026.xml", "product_code":"", - "code":"764", + "code":"794", "des":"The system checks the hdfs://hacluster/hbase/corrupt directory on the HDFS of each HBase service every 120 seconds. This alarm is generated when there are WAL files in th", "doc_type":"", "kw":"ALM-19026 Damaged WAL Files in HBase,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14019,11 +14531,130 @@ "title":"ALM-19026 Damaged WAL Files in HBase", "githuburl":"" }, + { + "uri":"ALM-19030.html", + "node_id":"alm-19030.xml", + "product_code":"", + "code":"795", + "des":"The system checks the P99 latency for responding to RPC requests on each RegionServer instance of the HBase service every 30 seconds. This alarm is generated when P99 lat", + "doc_type":"", + "kw":"ALM-19030 P99 Latency of RegionServer RPC Request Exceeds the Threshold,Alarm Reference (Applicable ", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-19030 P99 Latency of RegionServer RPC Request Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-19031.html", + "node_id":"alm-19031.xml", + "product_code":"", + "code":"796", + "des":"The system checks the number of RegionServer RPC connections in each HBase service every 30 seconds. This alarm is generated when the number of RPC connections of a Regio", + "doc_type":"", + "kw":"ALM-19031 Number of RegionServer RPC Connections Exceeds the Threshold,Alarm Reference (Applicable t", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-19031 Number of RegionServer RPC Connections Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-19032.html", + "node_id":"alm-19032.xml", + "product_code":"", + "code":"797", + "des":"The system checks the number of tasks waiting in the RPC write queue for the RegionServer instances of the HBase service every 30 seconds. This alarm is generated when th", + "doc_type":"", + "kw":"ALM-19032 Number of Tasks in the RegionServer RPC Write Queue Exceeds the Threshold,Alarm Reference ", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-19032 Number of Tasks in the RegionServer RPC Write Queue Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-19033.html", + "node_id":"alm-19033.xml", + "product_code":"", + "code":"798", + "des":"The system checks the number of tasks waiting in the RPC read queue for the RegionServer instances of the HBase service every 30 seconds. This alarm is generated when the", + "doc_type":"", + "kw":"ALM-19033 Number of Tasks in the RegionServer RPC Read Queue Exceeds the Threshold,Alarm Reference (", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-19033 Number of Tasks in the RegionServer RPC Read Queue Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-19034.html", + "node_id":"alm-19034.xml", + "product_code":"", + "code":"799", + "des":"The system checks the number of RegionServer WAL write timeouts in each HBase service every 30 seconds. This alarm is generated when the number of WAL write timeouts on a", + "doc_type":"", + "kw":"ALM-19034 Number of RegionServer WAL Write Timeouts Exceeds the Threshold,Alarm Reference (Applicabl", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-19034 Number of RegionServer WAL Write Timeouts Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-19035.html", + "node_id":"alm-19035.xml", + "product_code":"", + "code":"800", + "des":"The system checks the size of the RegionServer call queue for each HBase service every 30 seconds. This alarm is generated when the call queue of a RegionServer instance ", + "doc_type":"", + "kw":"ALM-19035 Size of the RegionServer Call Queue Exceeds the Threshold,Alarm Reference (Applicable to M", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-19035 Size of the RegionServer Call Queue Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-19036.html", + "node_id":"alm-19036.xml", + "product_code":"", + "code":"801", + "des":"The system checks for bad blocks in HBase key directories every 5 minutes, including the hbase.version file and the hbase:meta and master:store table directories. This al", + "doc_type":"", + "kw":"ALM-19036 Bad Blocks Exist in HBase Key Directory Data,Alarm Reference (Applicable to MRS 3.x),User ", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-19036 Bad Blocks Exist in HBase Key Directory Data", + "githuburl":"" + }, { "uri":"ALM-20002.html", "node_id":"alm-20002.xml", "product_code":"mrs", - "code":"765", + "code":"802", "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", @@ -14041,7 +14672,7 @@ "uri":"ALM-23001.html", "node_id":"alm-23001.xml", "product_code":"mrs", - "code":"766", + "code":"803", "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", @@ -14059,7 +14690,7 @@ "uri":"ALM-23003.html", "node_id":"alm-23003.xml", "product_code":"mrs", - "code":"767", + "code":"804", "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", @@ -14077,7 +14708,7 @@ "uri":"ALM-23004.html", "node_id":"alm-23004.xml", "product_code":"mrs", - "code":"768", + "code":"805", "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", @@ -14095,7 +14726,7 @@ "uri":"ALM-23005.html", "node_id":"alm-23005.xml", "product_code":"mrs", - "code":"769", + "code":"806", "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)", @@ -14113,7 +14744,7 @@ "uri":"ALM-23006.html", "node_id":"alm-23006.xml", "product_code":"mrs", - "code":"770", + "code":"807", "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", @@ -14131,7 +14762,7 @@ "uri":"ALM-23007.html", "node_id":"alm-23007.xml", "product_code":"mrs", - "code":"771", + "code":"808", "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 (", @@ -14149,7 +14780,7 @@ "uri":"ALM-24000.html", "node_id":"alm-24000.xml", "product_code":"mrs", - "code":"772", + "code":"809", "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", @@ -14167,7 +14798,7 @@ "uri":"ALM-24001.html", "node_id":"alm-24001.xml", "product_code":"mrs", - "code":"773", + "code":"810", "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", @@ -14185,7 +14816,7 @@ "uri":"ALM-24003.html", "node_id":"alm-24003.xml", "product_code":"mrs", - "code":"774", + "code":"811", "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", @@ -14203,7 +14834,7 @@ "uri":"ALM-24004.html", "node_id":"alm-24004.xml", "product_code":"mrs", - "code":"775", + "code":"812", "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", @@ -14221,7 +14852,7 @@ "uri":"ALM-24005.html", "node_id":"alm-24005.xml", "product_code":"mrs", - "code":"776", + "code":"813", "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", @@ -14239,7 +14870,7 @@ "uri":"ALM-24006.html", "node_id":"alm-24006.xml", "product_code":"mrs", - "code":"777", + "code":"814", "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", @@ -14257,7 +14888,7 @@ "uri":"ALM-24007.html", "node_id":"alm-24007.xml", "product_code":"mrs", - "code":"778", + "code":"815", "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 ", @@ -14275,7 +14906,7 @@ "uri":"ALM-24008.html", "node_id":"alm-24008.xml", "product_code":"mrs", - "code":"779", + "code":"816", "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", @@ -14293,7 +14924,7 @@ "uri":"ALM-24009.html", "node_id":"alm-24009.xml", "product_code":"mrs", - "code":"780", + "code":"817", "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", @@ -14311,7 +14942,7 @@ "uri":"ALM-24010.html", "node_id":"alm-24010.xml", "product_code":"mrs", - "code":"781", + "code":"818", "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 ", @@ -14329,7 +14960,7 @@ "uri":"ALM-24011.html", "node_id":"alm-24011.xml", "product_code":"mrs", - "code":"782", + "code":"819", "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", @@ -14347,7 +14978,7 @@ "uri":"ALM-24012.html", "node_id":"alm-24012.xml", "product_code":"mrs", - "code":"783", + "code":"820", "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", @@ -14365,7 +14996,7 @@ "uri":"ALM-24013.html", "node_id":"alm-24013.xml", "product_code":"mrs", - "code":"784", + "code":"821", "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 ", @@ -14383,7 +15014,7 @@ "uri":"ALM-24014.html", "node_id":"alm-24014.xml", "product_code":"mrs", - "code":"785", + "code":"822", "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)", @@ -14401,7 +15032,7 @@ "uri":"ALM-24015.html", "node_id":"alm-24015.xml", "product_code":"mrs", - "code":"786", + "code":"823", "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", @@ -14419,7 +15050,7 @@ "uri":"ALM-25000.html", "node_id":"alm-25000.xml", "product_code":"mrs", - "code":"787", + "code":"824", "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", @@ -14437,7 +15068,7 @@ "uri":"ALM-25004.html", "node_id":"alm-25004.xml", "product_code":"mrs", - "code":"788", + "code":"825", "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", @@ -14455,7 +15086,7 @@ "uri":"ALM-25005.html", "node_id":"alm-25005.xml", "product_code":"mrs", - "code":"789", + "code":"826", "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", @@ -14473,7 +15104,7 @@ "uri":"ALM-25006.html", "node_id":"alm-25006.xml", "product_code":"mrs", - "code":"790", + "code":"827", "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", @@ -14491,7 +15122,7 @@ "uri":"ALM-25007.html", "node_id":"alm-25007.xml", "product_code":"", - "code":"791", + "code":"828", "des":"The system checks the number of process connections on the SlapdServer node every 30 seconds and compares the actual number with the threshold. This alarm is generated wh", "doc_type":"", "kw":"ALM-25007 Number of SlapdServer Connections Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -14508,7 +15139,7 @@ "uri":"ALM-25008.html", "node_id":"alm-25008.xml", "product_code":"", - "code":"792", + "code":"829", "des":"The system checks the CPU usage of the SlapdServer node every 30 seconds and compares the actual usage with the threshold. This alarm is generated when the SlapdServer CP", "doc_type":"", "kw":"ALM-25008 SlapdServer CPU Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User G", @@ -14525,7 +15156,7 @@ "uri":"ALM-25500.html", "node_id":"alm-25500.xml", "product_code":"mrs", - "code":"793", + "code":"830", "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", @@ -14543,7 +15174,7 @@ "uri":"ALM-26051.html", "node_id":"alm-26051.xml", "product_code":"mrs", - "code":"794", + "code":"831", "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", @@ -14561,7 +15192,7 @@ "uri":"ALM-26052.html", "node_id":"alm-26052.xml", "product_code":"mrs", - "code":"795", + "code":"832", "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", @@ -14579,7 +15210,7 @@ "uri":"ALM-26053.html", "node_id":"alm-26053.xml", "product_code":"mrs", - "code":"796", + "code":"833", "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", @@ -14597,7 +15228,7 @@ "uri":"ALM-26054.html", "node_id":"alm-26054.xml", "product_code":"mrs", - "code":"797", + "code":"834", "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", @@ -14615,7 +15246,7 @@ "uri":"ALM-27001.html", "node_id":"alm-27001.xml", "product_code":"mrs", - "code":"798", + "code":"835", "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", @@ -14633,7 +15264,7 @@ "uri":"ALM-27003.html", "node_id":"alm-27003.xml", "product_code":"mrs", - "code":"799", + "code":"836", "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", @@ -14651,7 +15282,7 @@ "uri":"ALM-27004.html", "node_id":"alm-27004.xml", "product_code":"mrs", - "code":"800", + "code":"837", "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", @@ -14669,7 +15300,7 @@ "uri":"ALM-27005.html", "node_id":"alm-27005.xml", "product_code":"mrs", - "code":"801", + "code":"838", "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", @@ -14687,7 +15318,7 @@ "uri":"ALM-27006.html", "node_id":"alm-27006.xml", "product_code":"mrs", - "code":"802", + "code":"839", "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", @@ -14705,7 +15336,7 @@ "uri":"ALM-27007.html", "node_id":"alm-27007.xml", "product_code":"mrs", - "code":"803", + "code":"840", "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", @@ -14723,7 +15354,7 @@ "uri":"ALM-29007.html", "node_id":"alm-29007.xml", "product_code":"", - "code":"804", + "code":"841", "des":"The system checks the memory usage of the Impalad process every 30 seconds. This alarm is generated when the system detects that the memory usage exceeds the default thre", "doc_type":"", "kw":"ALM-29007 Impalad Process Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -14740,7 +15371,7 @@ "uri":"ALM-29008.html", "node_id":"alm-29008.xml", "product_code":"", - "code":"805", + "code":"842", "des":"The system checks the number of client connections to the Impalad node every 30 seconds. This alarm is generated when the number of client connections exceeds the customi", "doc_type":"", "kw":"ALM-29008 Number of ODBC Connections to Impalad Exceeds the Threshold,Alarm Reference (Applicable to", @@ -14757,7 +15388,7 @@ "uri":"ALM-29010.html", "node_id":"alm-29010.xml", "product_code":"", - "code":"806", + "code":"843", "des":"The system checks the total number of queries being submitted by the Impalad node every 60 seconds. This alarm is generated when the number of queries exceeds the customi", "doc_type":"", "kw":"ALM-29010 Number of Queries Being Submitted by Impalad Exceeds the Threshold,Alarm Reference (Applic", @@ -14774,7 +15405,7 @@ "uri":"ALM-29011.html", "node_id":"alm-29011.xml", "product_code":"", - "code":"807", + "code":"844", "des":"The system checks the total number of queries being executed by the Impalad node every 60 seconds. This alarm is generated when the number of queries exceeds the customiz", "doc_type":"", "kw":"ALM-29011 Number of Queries Being Executed by Impalad Exceeds the Threshold,Alarm Reference (Applica", @@ -14791,7 +15422,7 @@ "uri":"ALM-29012.html", "node_id":"alm-29012.xml", "product_code":"", - "code":"808", + "code":"845", "des":"The system checks the total number of queries being waited by the Impalad node every 60 seconds. This alarm is generated when the number of queries exceeds the customized", "doc_type":"", "kw":"ALM-29012 Number of Queries Being Waited by Impalad Exceeds the Threshold,Alarm Reference (Applicabl", @@ -14808,7 +15439,7 @@ "uri":"ALM-29013.html", "node_id":"alm-29013.xml", "product_code":"", - "code":"809", + "code":"846", "des":"The system checks the FGC time of the Impalad service every 60 seconds. This alarm is generated when the FGC time exceeds the threshold (12 seconds) for five consecutive ", "doc_type":"", "kw":"ALM-29013 Impalad FGC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14825,7 +15456,7 @@ "uri":"ALM-29014.html", "node_id":"alm-29014.xml", "product_code":"", - "code":"810", + "code":"847", "des":"The system checks the FGC time of the Catalog service every 60 seconds. This alarm is generated when the FGC time exceeds the threshold (12 seconds) for five consecutive ", "doc_type":"", "kw":"ALM-29014 Catalog FGC Time Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -14842,7 +15473,7 @@ "uri":"ALM-29015.html", "node_id":"alm-29015.xml", "product_code":"", - "code":"811", + "code":"848", "des":"The system checks the memory usage of the Catalog process every 30 seconds. This alarm is generated when the system detects that the memory usage exceeds the default thre", "doc_type":"", "kw":"ALM-29015 Catalog Process Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -14859,7 +15490,7 @@ "uri":"ALM-29016.html", "node_id":"alm-29016.xml", "product_code":"", - "code":"812", + "code":"849", "des":"In MRS 3.1.5, the system checks every 60 seconds whether the Hive Server2 HTTP port (28000) of Impalad responds to cURL requests. This alarm is generated when the returne", "doc_type":"", "kw":"ALM-29016 Impalad Instance in the Sub-healthy State,Alarm Reference (Applicable to MRS 3.x),User Gui", @@ -14876,7 +15507,7 @@ "uri":"ALM-38000.html", "node_id":"alm-38000.xml", "product_code":"mrs", - "code":"813", + "code":"850", "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", @@ -14894,7 +15525,7 @@ "uri":"ALM-38001.html", "node_id":"alm-38001.xml", "product_code":"mrs", - "code":"814", + "code":"851", "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", @@ -14912,7 +15543,7 @@ "uri":"ALM-38002.html", "node_id":"alm-38002.xml", "product_code":"mrs", - "code":"815", + "code":"852", "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", @@ -14930,7 +15561,7 @@ "uri":"ALM-38004.html", "node_id":"alm-38004.xml", "product_code":"mrs", - "code":"816", + "code":"853", "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", @@ -14948,7 +15579,7 @@ "uri":"ALM-38005.html", "node_id":"alm-38005.xml", "product_code":"mrs", - "code":"817", + "code":"854", "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", @@ -14966,7 +15597,7 @@ "uri":"ALM-38006.html", "node_id":"alm-38006.xml", "product_code":"mrs", - "code":"818", + "code":"855", "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,", @@ -14984,7 +15615,7 @@ "uri":"ALM-38007.html", "node_id":"alm-38007.xml", "product_code":"mrs", - "code":"819", + "code":"856", "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", @@ -15002,7 +15633,7 @@ "uri":"ALM-38008.html", "node_id":"alm-38008.xml", "product_code":"mrs", - "code":"820", + "code":"857", "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", @@ -15020,7 +15651,7 @@ "uri":"ALM-38009.html", "node_id":"alm-38009.xml", "product_code":"mrs", - "code":"821", + "code":"858", "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":"(Applicable to Versions Later Than MRS 3.1.0)ALM-38009 Busy Broker Disk I/Os (Applicable to Versions", @@ -15038,7 +15669,7 @@ "uri":"ALM-38010.html", "node_id":"alm-38010.xml", "product_code":"mrs", - "code":"822", + "code":"859", "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", @@ -15056,7 +15687,7 @@ "uri":"ALM-38011.html", "node_id":"alm-38011.xml", "product_code":"mrs", - "code":"823", + "code":"860", "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", @@ -15070,11 +15701,130 @@ "title":"ALM-38011 User Connection Usage on Broker Exceeds the Threshold", "githuburl":"" }, + { + "uri":"ALM-38012.html", + "node_id":"alm-38012.xml", + "product_code":"", + "code":"861", + "des":"The system checks the number of partitions on each Broker instance of the Kafka service every 30 seconds. You can view the number of partitions on the Broker instance das", + "doc_type":"", + "kw":"ALM-38012 Number of Broker Partitions Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-38012 Number of Broker Partitions Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-38013.html", + "node_id":"alm-38013.xml", + "product_code":"", + "code":"862", + "des":"The system checks the latency of Produce requests on Broker instances in the request queue every 30 seconds. This alarm is generated when the latency of Produce requests ", + "doc_type":"", + "kw":"ALM-38013 Produce Request Latency in the Request Queue Exceeds the Threshold,Alarm Reference (Applic", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-38013 Produce Request Latency in the Request Queue Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-38014.html", + "node_id":"alm-38014.xml", + "product_code":"", + "code":"863", + "des":"The system checks the total latency of Produce requests on Broker instances every 30 seconds. This alarm is generated when the total latency of Produce requests on a Brok", + "doc_type":"", + "kw":"ALM-38014 Total Produce Request Latency Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-38014 Total Produce Request Latency Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-38015.html", + "node_id":"alm-38015.xml", + "product_code":"", + "code":"864", + "des":"The system checks the latency of Fetch requests on Broker instances in the request queue every 30 seconds. This alarm is generated when the latency of Fetch requests on a", + "doc_type":"", + "kw":"ALM-38015 Fetch Request Latency in the Request Queue Exceeds the Threshold,Alarm Reference (Applicab", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-38015 Fetch Request Latency in the Request Queue Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-38016.html", + "node_id":"alm-38016.xml", + "product_code":"", + "code":"865", + "des":"The system checks the total latency of Fetch requests on Broker instances every 30 seconds. This alarm is generated when the total latency of Fetch requests on a Broker i", + "doc_type":"", + "kw":"ALM-38016 Total Fetch Request Latency Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-38016 Total Fetch Request Latency Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-38017.html", + "node_id":"alm-38017.xml", + "product_code":"", + "code":"866", + "des":"The system checks the partition reassignment time every 10 minutes. The check interval can be modified by the Kafka configuration auto.reassign.check.interval.ms. This al", + "doc_type":"", + "kw":"ALM-38017 Partition Reassignment Duration Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-38017 Partition Reassignment Duration Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-38018.html", + "node_id":"alm-38018.xml", + "product_code":"", + "code":"867", + "des":"If you have configured a threshold to report Kafka consumer lag on the Alarms page of Kafka UI (there is no such rule by default), the system reports the alarm based on t", + "doc_type":"", + "kw":"ALM-38018 Kafka Consumer Lag,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-38018 Kafka Consumer Lag", + "githuburl":"" + }, { "uri":"ALM-43001.html", "node_id":"alm-43001.xml", "product_code":"mrs", - "code":"824", + "code":"868", "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", @@ -15092,7 +15842,7 @@ "uri":"ALM-43006.html", "node_id":"alm-43006.xml", "product_code":"mrs", - "code":"825", + "code":"869", "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", @@ -15110,7 +15860,7 @@ "uri":"ALM-43007.html", "node_id":"alm-43007.xml", "product_code":"mrs", - "code":"826", + "code":"870", "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", @@ -15128,7 +15878,7 @@ "uri":"ALM-43008.html", "node_id":"alm-43008.xml", "product_code":"mrs", - "code":"827", + "code":"871", "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 ", @@ -15146,7 +15896,7 @@ "uri":"ALM-43009.html", "node_id":"alm-43009.xml", "product_code":"mrs", - "code":"828", + "code":"872", "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)", @@ -15164,7 +15914,7 @@ "uri":"ALM-43010.html", "node_id":"alm-43010.xml", "product_code":"mrs", - "code":"829", + "code":"873", "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", @@ -15182,7 +15932,7 @@ "uri":"ALM-43011.html", "node_id":"alm-43011.xml", "product_code":"mrs", - "code":"830", + "code":"874", "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", @@ -15200,7 +15950,7 @@ "uri":"ALM-43012.html", "node_id":"alm-43012.xml", "product_code":"mrs", - "code":"831", + "code":"875", "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", @@ -15218,7 +15968,7 @@ "uri":"ALM-43013.html", "node_id":"alm-43013.xml", "product_code":"mrs", - "code":"832", + "code":"876", "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)", @@ -15236,7 +15986,7 @@ "uri":"ALM-43017.html", "node_id":"alm-43017.xml", "product_code":"mrs", - "code":"833", + "code":"877", "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", @@ -15254,7 +16004,7 @@ "uri":"ALM-43018.html", "node_id":"alm-43018.xml", "product_code":"mrs", - "code":"834", + "code":"878", "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", @@ -15272,7 +16022,7 @@ "uri":"ALM-43019.html", "node_id":"alm-43019.xml", "product_code":"mrs", - "code":"835", + "code":"879", "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", @@ -15290,7 +16040,7 @@ "uri":"ALM-43020.html", "node_id":"alm-43020.xml", "product_code":"mrs", - "code":"836", + "code":"880", "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 (", @@ -15308,7 +16058,7 @@ "uri":"ALM-43021.html", "node_id":"alm-43021.xml", "product_code":"mrs", - "code":"837", + "code":"881", "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", @@ -15326,7 +16076,7 @@ "uri":"ALM-43022.html", "node_id":"alm-43022.xml", "product_code":"mrs", - "code":"838", + "code":"882", "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", @@ -15344,7 +16094,7 @@ "uri":"ALM-43023.html", "node_id":"alm-43023.xml", "product_code":"mrs", - "code":"839", + "code":"883", "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 ", @@ -15358,11 +16108,46 @@ "title":"ALM-43023 IndexServer2x Process Full GC Number Exceeds the Threshold", "githuburl":"" }, + { + "uri":"ALM-43028.html", + "node_id":"alm-43028.xml", + "product_code":"mrs", + "code":"884", + "des":"This section applies only to MRS 3.3.1-LTS or later.This alarm is generated when the JDBCServer process forwards requests and triffic control is triggered due to insuffic", + "doc_type":"alarm", + "kw":"ALM-43028 JDBCServer Session Overflow,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"alarm;usermanual", + "prodname":"mrs" + } + ], + "title":"ALM-43028 JDBCServer Session Overflow", + "githuburl":"" + }, + { + "uri":"ALM-43029.html", + "node_id":"alm-43029.xml", + "product_code":"", + "code":"885", + "des":"This section applies only to MRS 3.5.0-LTS or later.After a user submits a JDBC job, the system attempts to create a JDBCServer process and establish a session connection", + "doc_type":"", + "kw":"ALM-43029 JDBCServer Job Submission Timed Out,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-43029 JDBCServer Job Submission Timed Out", + "githuburl":"" + }, { "uri":"ALM-44004.html", "node_id":"alm-44004.xml", "product_code":"mrs", - "code":"840", + "code":"886", "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", @@ -15380,7 +16165,7 @@ "uri":"ALM-44005.html", "node_id":"alm-44005.xml", "product_code":"mrs", - "code":"841", + "code":"887", "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", @@ -15398,7 +16183,7 @@ "uri":"ALM-44006.html", "node_id":"alm-44006.xml", "product_code":"mrs", - "code":"842", + "code":"888", "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", @@ -15416,7 +16201,7 @@ "uri":"ALM-45000.html", "node_id":"alm-45000.xml", "product_code":"mrs", - "code":"843", + "code":"889", "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", @@ -15434,7 +16219,7 @@ "uri":"ALM-45001.html", "node_id":"alm-45001.xml", "product_code":"mrs", - "code":"844", + "code":"890", "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", @@ -15452,7 +16237,7 @@ "uri":"ALM-45003.html", "node_id":"alm-45003.xml", "product_code":"mrs", - "code":"845", + "code":"891", "des":"This section applies to MRS 3.3.0 or later.The system checks the HetuEngine QAS disk usage every 60 seconds and compares the actual disk usage with the threshold. The dis", "doc_type":"alarm", "kw":"ALM-45003 HetuEngine QAS Disk Capacity Is Insufficient,Alarm Reference (Applicable to MRS 3.x),User ", @@ -15466,11 +16251,113 @@ "title":"ALM-45003 HetuEngine QAS Disk Capacity Is Insufficient", "githuburl":"" }, + { + "uri":"ALM-45004.html", + "node_id":"alm-45004.xml", + "product_code":"", + "code":"892", + "des":"This section applies to MRS 3.3.1 or later.The system checks the number of running tasks on a HetuEngine compute instance every 30 seconds. This alarm is generated when t", + "doc_type":"", + "kw":"ALM-45004 Tasks Stacked on HetuEngine Compute Instance,Alarm Reference (Applicable to MRS 3.x),User ", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45004 Tasks Stacked on HetuEngine Compute Instance", + "githuburl":"" + }, + { + "uri":"ALM-45005.html", + "node_id":"alm-45005.xml", + "product_code":"", + "code":"893", + "des":"This section applies to MRS 3.3.1 or later.The system checks the average CPU usage of HetuEngine compute instances every 30 seconds. This alarm is generated when the aver", + "doc_type":"", + "kw":"ALM-45005 CPU Usage of HetuEngine Compute Instance Exceeded the Threshold,Alarm Reference (Applicabl", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45005 CPU Usage of HetuEngine Compute Instance Exceeded the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45006.html", + "node_id":"alm-45006.xml", + "product_code":"", + "code":"894", + "des":"This section applies to MRS 3.3.1 or later.The system checks the memory usage of HetuEngine compute instances every 30 seconds. This alarm is generated when the memory us", + "doc_type":"", + "kw":"ALM-45006 Memory Usage of a HetuEngine Compute Instance Exceeded the Threshold,Alarm Reference (Appl", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45006 Memory Usage of a HetuEngine Compute Instance Exceeded the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45007.html", + "node_id":"alm-45007.xml", + "product_code":"", + "code":"895", + "des":"This section applies to MRS 3.3.1 or later.The system checks the number of Workers of a HetuEngine compute instance every 60 seconds. This alarm is generated when the num", + "doc_type":"", + "kw":"ALM-45007 Number of Workers of a HetuEngine Compute Instance Is Less Than the Threshold,Alarm Refere", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45007 Number of Workers of a HetuEngine Compute Instance Is Less Than the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45008.html", + "node_id":"alm-45008.xml", + "product_code":"", + "code":"896", + "des":"This section applies to MRS 3.5.0 or later.The system checks the query latency of HetuEngine compute instances every 30 seconds. This alarm is generated when the query la", + "doc_type":"", + "kw":"ALM-45008 Query Latency of HetuEngine Compute Instances Exceeds the Threshold,Alarm Reference (Appli", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45008 Query Latency of HetuEngine Compute Instances Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45009.html", + "node_id":"alm-45009.xml", + "product_code":"", + "code":"897", + "des":"This section applies to MRS 3.5.0 or later.The system checks the task failure rate of HetuEngine compute instances every 30 seconds. This alarm is generated when the task", + "doc_type":"", + "kw":"ALM-45009 Task Failure Rate of HetuEngine Compute Instances Exceeds the Threshold,Alarm Reference (A", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45009 Task Failure Rate of HetuEngine Compute Instances Exceeds the Threshold", + "githuburl":"" + }, { "uri":"ALM-45175.html", "node_id":"alm-45175.xml", "product_code":"mrs", - "code":"846", + "code":"898", "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 (", @@ -15488,7 +16375,7 @@ "uri":"ALM-45176.html", "node_id":"alm-45176.xml", "product_code":"mrs", - "code":"847", + "code":"899", "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", @@ -15506,7 +16393,7 @@ "uri":"ALM-45177.html", "node_id":"alm-45177.xml", "product_code":"mrs", - "code":"848", + "code":"900", "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", @@ -15524,7 +16411,7 @@ "uri":"ALM-45178.html", "node_id":"alm-45178.xml", "product_code":"mrs", - "code":"849", + "code":"901", "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", @@ -15542,7 +16429,7 @@ "uri":"ALM-45179.html", "node_id":"alm-45179.xml", "product_code":"mrs", - "code":"850", + "code":"902", "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", @@ -15560,7 +16447,7 @@ "uri":"ALM-45180.html", "node_id":"alm-45180.xml", "product_code":"mrs", - "code":"851", + "code":"903", "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", @@ -15578,7 +16465,7 @@ "uri":"ALM-45181.html", "node_id":"alm-45181.xml", "product_code":"mrs", - "code":"852", + "code":"904", "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 ", @@ -15596,7 +16483,7 @@ "uri":"ALM-45182.html", "node_id":"alm-45182.xml", "product_code":"mrs", - "code":"853", + "code":"905", "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", @@ -15614,7 +16501,7 @@ "uri":"ALM-45275.html", "node_id":"alm-45275.xml", "product_code":"mrs", - "code":"854", + "code":"906", "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", @@ -15632,7 +16519,7 @@ "uri":"ALM-45276.html", "node_id":"alm-45276.xml", "product_code":"mrs", - "code":"855", + "code":"907", "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", @@ -15650,7 +16537,7 @@ "uri":"ALM-45277.html", "node_id":"alm-45277.xml", "product_code":"mrs", - "code":"856", + "code":"908", "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", @@ -15668,7 +16555,7 @@ "uri":"ALM-45278.html", "node_id":"alm-45278.xml", "product_code":"mrs", - "code":"857", + "code":"909", "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", @@ -15686,7 +16573,7 @@ "uri":"ALM-45279.html", "node_id":"alm-45279.xml", "product_code":"mrs", - "code":"858", + "code":"910", "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", @@ -15704,7 +16591,7 @@ "uri":"ALM-45280.html", "node_id":"alm-45280.xml", "product_code":"mrs", - "code":"859", + "code":"911", "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", @@ -15722,7 +16609,7 @@ "uri":"ALM-45281.html", "node_id":"alm-45281.xml", "product_code":"mrs", - "code":"860", + "code":"912", "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", @@ -15740,7 +16627,7 @@ "uri":"ALM-45282.html", "node_id":"alm-45282.xml", "product_code":"mrs", - "code":"861", + "code":"913", "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)", @@ -15758,7 +16645,7 @@ "uri":"ALM-45283.html", "node_id":"alm-45283.xml", "product_code":"mrs", - "code":"862", + "code":"914", "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.", @@ -15776,7 +16663,7 @@ "uri":"ALM-45284.html", "node_id":"alm-45284.xml", "product_code":"mrs", - "code":"863", + "code":"915", "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", @@ -15794,7 +16681,7 @@ "uri":"ALM-45285.html", "node_id":"alm-45285.xml", "product_code":"mrs", - "code":"864", + "code":"916", "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", @@ -15812,7 +16699,7 @@ "uri":"ALM-45286.html", "node_id":"alm-45286.xml", "product_code":"mrs", - "code":"865", + "code":"917", "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),", @@ -15830,7 +16717,7 @@ "uri":"ALM-45287.html", "node_id":"alm-45287.xml", "product_code":"mrs", - "code":"866", + "code":"918", "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", @@ -15848,7 +16735,7 @@ "uri":"ALM-45288.html", "node_id":"alm-45288.xml", "product_code":"mrs", - "code":"867", + "code":"919", "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 ", @@ -15866,7 +16753,7 @@ "uri":"ALM-45289.html", "node_id":"alm-45289.xml", "product_code":"", - "code":"868", + "code":"920", "des":"This section applies only to MRS 3.3.0 or later.The system checks the heap memory usage of the PolicySync service every 60 seconds. This alarm is generated when the heap ", "doc_type":"", "kw":"ALM-45289 PolicySync Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x)", @@ -15883,7 +16770,7 @@ "uri":"ALM-45290.html", "node_id":"alm-45290.xml", "product_code":"", - "code":"869", + "code":"921", "des":"This section applies only to MRS 3.3.0 or later.The system checks the direct memory usage of the PolicySync service every 60 seconds. This alarm is generated when the dir", "doc_type":"", "kw":"ALM-45290 PolicySync Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.", @@ -15900,7 +16787,7 @@ "uri":"ALM-45291.html", "node_id":"alm-45291.xml", "product_code":"", - "code":"870", + "code":"922", "des":"This section applies only to MRS 3.3.0 or later.The system checks the non-heap memory usage of the PolicySync service every 60 seconds. This alarm is generated when the n", "doc_type":"", "kw":"ALM-45291 PolicySync Non-Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS ", @@ -15917,7 +16804,7 @@ "uri":"ALM-45292.html", "node_id":"alm-45292.xml", "product_code":"", - "code":"871", + "code":"923", "des":"This section applies only to MRS 3.3.0 or later.The system checks the GC duration of the PolicySync process every 60 seconds. This alarm is generated when the GC duration", "doc_type":"", "kw":"ALM-45292 PolicySync GC Duration Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User ", @@ -15930,11 +16817,45 @@ "title":"ALM-45292 PolicySync GC Duration Exceeds the Threshold", "githuburl":"" }, + { + "uri":"ALM-45293.html", + "node_id":"alm-45293.xml", + "product_code":"", + "code":"924", + "des":"The system checks synchronization status of the UserSync process every 5 minutes. This alarm is generated when a synchronization exception occurs. This alarm is cleared w", + "doc_type":"", + "kw":"ALM-45293 Ranger User Synchronization Exception,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45293 Ranger User Synchronization Exception", + "githuburl":"" + }, + { + "uri":"ALM-45294.html", + "node_id":"alm-45294.xml", + "product_code":"", + "code":"925", + "des":"The RangerKMS process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This al", + "doc_type":"", + "kw":"ALM-45294 RangerKMS Process Is Abnormal,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45294 RangerKMS Process Is Abnormal", + "githuburl":"" + }, { "uri":"ALM-45425.html", "node_id":"alm-45425.xml", "product_code":"mrs", - "code":"872", + "code":"926", "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", @@ -15952,7 +16873,7 @@ "uri":"ALM-45426.html", "node_id":"alm-45426.xml", "product_code":"mrs", - "code":"873", + "code":"927", "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", @@ -15970,7 +16891,7 @@ "uri":"ALM-45427.html", "node_id":"alm-45427.xml", "product_code":"mrs", - "code":"874", + "code":"928", "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", @@ -15988,7 +16909,7 @@ "uri":"ALM-45428.html", "node_id":"alm-45428.xml", "product_code":"mrs", - "code":"875", + "code":"929", "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", @@ -16006,7 +16927,7 @@ "uri":"ALM-45429.html", "node_id":"alm-45429.xml", "product_code":"mrs", - "code":"876", + "code":"930", "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", @@ -16024,7 +16945,7 @@ "uri":"ALM-45430.html", "node_id":"alm-45430.xml", "product_code":"mrs", - "code":"877", + "code":"931", "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", @@ -16042,7 +16963,7 @@ "uri":"ALM-45431.html", "node_id":"alm-45431.xml", "product_code":"mrs", - "code":"878", + "code":"932", "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", @@ -16060,7 +16981,7 @@ "uri":"ALM-45432.html", "node_id":"alm-45432.xml", "product_code":"mrs", - "code":"879", + "code":"933", "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", @@ -16078,7 +16999,7 @@ "uri":"ALM-45433.html", "node_id":"alm-45433.xml", "product_code":"mrs", - "code":"880", + "code":"934", "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", @@ -16096,7 +17017,7 @@ "uri":"ALM-45434.html", "node_id":"alm-45434.xml", "product_code":"mrs", - "code":"881", + "code":"935", "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.", @@ -16114,7 +17035,7 @@ "uri":"ALM-45435.html", "node_id":"alm-45435.xml", "product_code":"", - "code":"882", + "code":"936", "des":"This section applies only to MRS 3.3.0 or later.This alarm is generated when the metadata in a distributed table or in the local table of the distributed table has been i", "doc_type":"", "kw":"ALM-45435 Inconsistent Metadata of ClickHouse Tables,Alarm Reference (Applicable to MRS 3.x),User Gu", @@ -16131,7 +17052,7 @@ "uri":"ALM-45436.html", "node_id":"alm-45436.xml", "product_code":"", - "code":"883", + "code":"937", "des":"This section applies only to MRS 3.3.0 or later.This alarm is generated when data skew occurs in the local table of a distributed table between ClickHouse nodes. This ala", "doc_type":"", "kw":"ALM-45436 Skew ClickHouse Table Data,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16148,7 +17069,7 @@ "uri":"ALM-45437.html", "node_id":"alm-45437.xml", "product_code":"", - "code":"884", + "code":"938", "des":"This section applies only to MRS 3.3.0 or later.This alarm is generated when the number of parts exceeds the threshold specified by part_num_threshold.This alarm is autom", "doc_type":"", "kw":"ALM-45437 Excessive Parts in the ClickHouse Table,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16165,7 +17086,7 @@ "uri":"ALM-45438.html", "node_id":"alm-45438.xml", "product_code":"", - "code":"885", + "code":"939", "des":"This section applies only to MRS 3.3.0 or later.The system checks the disk capacity of the ClickHouseServer node every 1 minute. This alarm is generated when the usage of", "doc_type":"", "kw":"ALM-45438 ClickHouse Disk Usage Exceeds 80%,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16182,7 +17103,7 @@ "uri":"ALM-45439.html", "node_id":"alm-45439.xml", "product_code":"", - "code":"886", + "code":"940", "des":"This section applies only to MRS 3.3.0 or later.The system checks the disk capacity of the ClickHouseServer node every 1 minute. This alarm is generated when the system d", "doc_type":"", "kw":"ALM-45439 ClickHouse Node Enters the Read-Only Mode,Alarm Reference (Applicable to MRS 3.x),User Gui", @@ -16199,7 +17120,7 @@ "uri":"ALM-45440.html", "node_id":"alm-45440.xml", "product_code":"", - "code":"887", + "code":"941", "des":"This section applies only to MRS 3.3.0 or later.When the number of ClickHouse replicas is greater than 1, the system periodically checks the replicated table. This alarm ", "doc_type":"", "kw":"ALM-45440 Inconsistency Between ClickHouse Replicas,Alarm Reference (Applicable to MRS 3.x),User Gui", @@ -16216,7 +17137,7 @@ "uri":"ALM-45441.html", "node_id":"alm-45441.xml", "product_code":"", - "code":"888", + "code":"942", "des":"This section applies only to MRS 3.3.0 or later.The system checks the connection between ClickHouse and ZooKeeper every minute. This alarm is generated when the connectio", "doc_type":"", "kw":"ALM-45441 Zookeeper Disconnected,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16233,7 +17154,7 @@ "uri":"ALM-45442.html", "node_id":"alm-45442.xml", "product_code":"", - "code":"889", + "code":"943", "des":"This section applies only to MRS 3.3.0 or later.The alarm module checks the number of concurrent ClickHouse requests every 30 seconds. This alarm is generated when the nu", "doc_type":"", "kw":"ALM-45442 Too Many Concurrent SQL Statements,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16250,7 +17171,7 @@ "uri":"ALM-45443.html", "node_id":"alm-45443.xml", "product_code":"", - "code":"890", + "code":"944", "des":"This section applies only to MRS 3.3.0 or later.The system checks slow SQL queries for ClickHouse every 1 minute. This alarm is generated when the execution time of a SQL", "doc_type":"", "kw":"ALM-45443 Slow SQL Queries in the Cluster,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16267,7 +17188,7 @@ "uri":"ALM-45444.html", "node_id":"alm-45444.xml", "product_code":"", - "code":"891", + "code":"945", "des":"This section applies only to MRS 3.3.0 or later.The health check module checks ClickHouse instances every 30 seconds. If the number of consecutive failures exceeds the th", "doc_type":"", "kw":"ALM-45444 Abnormal ClickHouse Process,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16280,11 +17201,266 @@ "title":"ALM-45444 Abnormal ClickHouse Process", "githuburl":"" }, + { + "uri":"ALM-45445.html", + "node_id":"alm-45445.xml", + "product_code":"", + "code":"946", + "des":"This section is available for MRS 3.3.1-LTS or later version only.The ClickHouse instance checks the distributed table every 300 seconds. If the number of consecutive fai", + "doc_type":"", + "kw":"ALM-45445 Failed to Send Data Files to Remote Shards When ClickHouse Writes Data to a Distributed Ta", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45445 Failed to Send Data Files to Remote Shards When ClickHouse Writes Data to a Distributed Table", + "githuburl":"" + }, + { + "uri":"ALM-45446.html", + "node_id":"alm-45446.xml", + "product_code":"", + "code":"947", + "des":"This section is available for MRS 3.3.1-LTS or later version only.The system checks mutation tasks every 5 minutes. This alarm is generated when the system detects that a", + "doc_type":"", + "kw":"ALM-45446 Mutation Task of ClickHouse Is Not Complete for a Long Time,Alarm Reference (Applicable to", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45446 Mutation Task of ClickHouse Is Not Complete for a Long Time", + "githuburl":"" + }, + { + "uri":"ALM-45447.html", + "node_id":"alm-45447.xml", + "product_code":"", + "code":"948", + "des":"This section is available for MRS 3.3.1-LTS or later version only.The system checks the table status every minute. This alarm is generated when the system detects that a ", + "doc_type":"", + "kw":"ALM-45447 ClickHouse Table Read-Only,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45447 ClickHouse Table Read-Only", + "githuburl":"" + }, + { + "uri":"ALM-45448.html", + "node_id":"alm-45448.xml", + "product_code":"", + "code":"949", + "des":"This section is available for MRS 3.3.1-LTS or later version only.Metadata in ClickHouse is stored on ZooKeeper Znodes. The number of occupied Znodes may increase sharply", + "doc_type":"", + "kw":"ALM-45448 Rapid Increase of Znodes Used by ClickHouse,Alarm Reference (Applicable to MRS 3.x),User G", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45448 Rapid Increase of Znodes Used by ClickHouse", + "githuburl":"" + }, + { + "uri":"ALM-45449.html", + "node_id":"alm-45449.xml", + "product_code":"", + "code":"950", + "des":"This section is available for MRS 3.3.1-LTS or later version only.ClickHouse uses ZooKeeper Transaction ID (zxid) to manage transactions. The zxid is a 64-bit number used", + "doc_type":"", + "kw":"ALM-45449 The Counter Number of zxid Used by ClickHouse Exceeds the Threshold,Alarm Reference (Appli", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45449 The Counter Number of zxid Used by ClickHouse Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45450.html", + "node_id":"alm-45450.xml", + "product_code":"", + "code":"951", + "des":"This section is available for MRS 3.3.1-LTS or later version only.After the cold-hot separation function and an agency are configured, the system checks the status of the", + "doc_type":"", + "kw":"ALM-45450 ClickHouse Failed to Obtain a Temporary Agency Credential,Alarm Reference (Applicable to M", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45450 ClickHouse Failed to Obtain a Temporary Agency Credential", + "githuburl":"" + }, + { + "uri":"ALM-45451.html", + "node_id":"alm-45451.xml", + "product_code":"", + "code":"952", + "des":"This section is available for MRS 3.3.1-LTS or later version only.When cold-hot separation is enabled, the system checks the OBS access every minute. This alarm is genera", + "doc_type":"", + "kw":"ALM-45451 ClickHouse Failed to Access OBS,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45451 ClickHouse Failed to Access OBS", + "githuburl":"" + }, + { + "uri":"ALM-45452.html", + "node_id":"alm-45452.xml", + "product_code":"", + "code":"953", + "des":"This section is available for MRS 3.3.1-LTS or later version only.When cold-hot separation is enabled, the system checks the remaining space of the local disk specified i", + "doc_type":"", + "kw":"ALM-45452 ClickHouse's Local Disk Space Is Below the Cold-Hot Separation Threshold,Alarm Reference (", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45452 ClickHouse's Local Disk Space Is Below the Cold-Hot Separation Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45475.html", + "node_id":"alm-45475.xml", + "product_code":"", + "code":"954", + "des":"The system checks the replica status of the Kudu data table. This alarm is generated when a single replica is detected in the Kudu data table.This alarm is cleared when a", + "doc_type":"", + "kw":"ALM-45475 A Single Replica Exists in the Kudu Data Table,Alarm Reference (Applicable to MRS 3.x),Use", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45475 A Single Replica Exists in the Kudu Data Table", + "githuburl":"" + }, + { + "uri":"ALM-45476.html", + "node_id":"alm-45476.xml", + "product_code":"", + "code":"955", + "des":"Kudu will enter the maintenance mode during disk replacement. This alarm is generated when Kudu fails to enter the maintenance mode.This alarm is cleared when Kudu succes", + "doc_type":"", + "kw":"ALM-45476 Kudu Failed to Enter the Maintenance Mode,Alarm Reference (Applicable to MRS 3.x),User Gui", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45476 Kudu Failed to Enter the Maintenance Mode", + "githuburl":"" + }, + { + "uri":"ALM-45477.html", + "node_id":"alm-45477.xml", + "product_code":"", + "code":"956", + "des":"This alarm is generated when Kudu fails to restore data by invoking the script in SetupTool after a disk is replaced.This alarm is cleared when the data is successfully r", + "doc_type":"", + "kw":"ALM-45477 Failed to Restore Data After a Disk of Kudu Is Replaced,Alarm Reference (Applicable to MRS", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45477 Failed to Restore Data After a Disk of Kudu Is Replaced", + "githuburl":"" + }, + { + "uri":"ALM-45478.html", + "node_id":"alm-45478.xml", + "product_code":"", + "code":"957", + "des":"The system periodically balances data among Kudu data tables. This alarm is generated when the system detects that the data balancing API returns a failure response.This ", + "doc_type":"", + "kw":"ALM-45478 Kudu Failed Data Balancing,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45478 Kudu Failed Data Balancing", + "githuburl":"" + }, + { + "uri":"ALM-45479.html", + "node_id":"alm-45479.xml", + "product_code":"", + "code":"958", + "des":"The system checks the Kudu service status every 60 seconds. This alarm is generated when the number of tablets of the Tserver process exceeds the threshold.This alarm is ", + "doc_type":"", + "kw":"ALM-45479 Number of Tablets of the Tserver Process Exceeds the Threshold,Alarm Reference (Applicable", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45479 Number of Tablets of the Tserver Process Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45480.html", + "node_id":"alm-45480.xml", + "product_code":"", + "code":"959", + "des":"The system checks the Kudu service status every 60 seconds. This alarm is generated when the ratio of tablet leaders of a Tserver process to total tablet leaders in the c", + "doc_type":"", + "kw":"ALM-45480 Tablet Leaders of a Tserver Process Are Unevenly Distributed,Alarm Reference (Applicable t", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45480 Tablet Leaders of a Tserver Process Are Unevenly Distributed", + "githuburl":"" + }, + { + "uri":"ALM-45481.html", + "node_id":"alm-45481.xml", + "product_code":"", + "code":"960", + "des":"The system checks Kudu disk metrics every 60 seconds. This alarm is generated when the number of fully occupied disks for a Tserver is not 0.This alarm is automatically c", + "doc_type":"", + "kw":"ALM-45481 KuduTserver Has Full Disks,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45481 KuduTserver Has Full Disks", + "githuburl":"" + }, { "uri":"ALM-45585.html", "node_id":"alm-45585.xml", "product_code":"mrs", - "code":"892", + "code":"961", "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", @@ -16302,7 +17478,7 @@ "uri":"ALM-45586.html", "node_id":"alm-45586.xml", "product_code":"mrs", - "code":"893", + "code":"962", "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", @@ -16320,7 +17496,7 @@ "uri":"ALM-45587.html", "node_id":"alm-45587.xml", "product_code":"mrs", - "code":"894", + "code":"963", "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", @@ -16338,7 +17514,7 @@ "uri":"ALM-45588.html", "node_id":"alm-45588.xml", "product_code":"mrs", - "code":"895", + "code":"964", "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", @@ -16356,7 +17532,7 @@ "uri":"ALM-45589.html", "node_id":"alm-45589.xml", "product_code":"mrs", - "code":"896", + "code":"965", "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)", @@ -16374,7 +17550,7 @@ "uri":"ALM-45590.html", "node_id":"alm-45590.xml", "product_code":"mrs", - "code":"897", + "code":"966", "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 ", @@ -16392,7 +17568,7 @@ "uri":"ALM-45591.html", "node_id":"alm-45591.xml", "product_code":"mrs", - "code":"898", + "code":"967", "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.", @@ -16410,7 +17586,7 @@ "uri":"ALM-45592.html", "node_id":"alm-45592.xml", "product_code":"mrs", - "code":"899", + "code":"968", "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", @@ -16428,7 +17604,7 @@ "uri":"ALM-45593.html", "node_id":"alm-45593.xml", "product_code":"mrs", - "code":"900", + "code":"969", "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 ", @@ -16446,7 +17622,7 @@ "uri":"ALM-45594.html", "node_id":"alm-45594.xml", "product_code":"mrs", - "code":"901", + "code":"970", "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", @@ -16464,7 +17640,7 @@ "uri":"ALM-45595.html", "node_id":"alm-45595.xml", "product_code":"mrs", - "code":"902", + "code":"971", "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", @@ -16482,7 +17658,7 @@ "uri":"ALM-45615.html", "node_id":"alm-45615.xml", "product_code":"mrs", - "code":"903", + "code":"972", "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", @@ -16500,7 +17676,7 @@ "uri":"ALM-45616.html", "node_id":"alm-45616.xml", "product_code":"mrs", - "code":"904", + "code":"973", "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", @@ -16518,7 +17694,7 @@ "uri":"ALM-45617.html", "node_id":"alm-45617.xml", "product_code":"mrs", - "code":"905", + "code":"974", "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 ", @@ -16536,7 +17712,7 @@ "uri":"ALM-45635.html", "node_id":"alm-45635.xml", "product_code":"mrs", - "code":"906", + "code":"975", "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", @@ -16554,7 +17730,7 @@ "uri":"ALM-45636.html", "node_id":"alm-45636.xml", "product_code":"mrs", - "code":"907", + "code":"976", "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", @@ -16572,7 +17748,7 @@ "uri":"ALM-45636-1.html", "node_id":"alm-45636-1.xml", "product_code":"mrs", - "code":"908", + "code":"977", "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", @@ -16590,7 +17766,7 @@ "uri":"ALM-45637.html", "node_id":"alm-45637.xml", "product_code":"mrs", - "code":"909", + "code":"978", "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.", @@ -16608,7 +17784,7 @@ "uri":"ALM-45638.html", "node_id":"alm-45638.xml", "product_code":"mrs", - "code":"910", + "code":"979", "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", @@ -16626,7 +17802,7 @@ "uri":"ALM-45638-1.html", "node_id":"alm-45638-1.xml", "product_code":"mrs", - "code":"911", + "code":"980", "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", @@ -16644,7 +17820,7 @@ "uri":"ALM-45639.html", "node_id":"alm-45639.xml", "product_code":"mrs", - "code":"912", + "code":"981", "des":"The system checks the checkpointing timeout of Flink jobs every 30 seconds. This alarm is generated if the checkpointing timeout of a Flink job is longer than the thresho", "doc_type":"alarm", "kw":"ALM-45639 Checkpointing of a Flink Job Times Out,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16662,7 +17838,7 @@ "uri":"ALM-45640.html", "node_id":"alm-45640.xml", "product_code":"mrs", - "code":"913", + "code":"982", "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", @@ -16680,7 +17856,7 @@ "uri":"ALM-45641.html", "node_id":"alm-45641.xml", "product_code":"mrs", - "code":"914", + "code":"983", "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", @@ -16698,7 +17874,7 @@ "uri":"ALM-45642.html", "node_id":"alm-45642.xml", "product_code":"", - "code":"915", + "code":"984", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45642 RocksDB Continuously Triggers Write Traffic Limiting,Alarm Reference (Applicable to MRS 3.", @@ -16715,7 +17891,7 @@ "uri":"ALM-45643.html", "node_id":"alm-45643.xml", "product_code":"", - "code":"916", + "code":"985", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold,Alarm Reference (Applicable to", @@ -16732,7 +17908,7 @@ "uri":"ALM-45644.html", "node_id":"alm-45644.xml", "product_code":"", - "code":"917", + "code":"986", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold,Alarm Referen", @@ -16749,7 +17925,7 @@ "uri":"ALM-45645.html", "node_id":"alm-45645.xml", "product_code":"", - "code":"918", + "code":"987", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45645 Pending Flush Size of RocksDB Continuously Exceeds the Threshold,Alarm Reference (Applicab", @@ -16766,7 +17942,7 @@ "uri":"ALM-45646.html", "node_id":"alm-45646.xml", "product_code":"", - "code":"919", + "code":"988", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold,Alarm Reference (App", @@ -16783,7 +17959,7 @@ "uri":"ALM-45647.html", "node_id":"alm-45647.xml", "product_code":"", - "code":"920", + "code":"989", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold,Alarm Refe", @@ -16800,7 +17976,7 @@ "uri":"ALM-45648.html", "node_id":"alm-45648.xml", "product_code":"", - "code":"921", + "code":"990", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45648 RocksDB Frequently Encounters Write-Stopped,Alarm Reference (Applicable to MRS 3.x),User G", @@ -16817,7 +17993,7 @@ "uri":"ALM-45649.html", "node_id":"alm-45649.xml", "product_code":"", - "code":"922", + "code":"991", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45649 P95 Latency of RocksDB Get Requests Continuously Exceeds the Threshold,Alarm Reference (Ap", @@ -16834,7 +18010,7 @@ "uri":"ALM-45650.html", "node_id":"alm-45650.xml", "product_code":"", - "code":"923", + "code":"992", "des":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", "doc_type":"", "kw":"ALM-45650 P95 Latency of RocksDB Write Requests Continuously Exceeds the Threshold,Alarm Reference (", @@ -16851,7 +18027,7 @@ "uri":"ALM-45652.html", "node_id":"alm-45652.xml", "product_code":"", - "code":"924", + "code":"993", "des":"This section applies to MRS 3.3.0 or later.The alarm module checks the Flink status every 60 seconds. This alarm is generated when the Flink service is unavailable. This ", "doc_type":"", "kw":"ALM-45652 Flink Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16868,7 +18044,7 @@ "uri":"ALM-45653.html", "node_id":"alm-45653.xml", "product_code":"", - "code":"925", + "code":"994", "des":"This section applies to MRS 3.3.0 or later.Flink checks whether the HA certificate file is valid (whether the certificate exists and whether its format is correct) in the", "doc_type":"", "kw":"ALM-45653 Invalid Flink HA Certificate File,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16885,7 +18061,7 @@ "uri":"ALM-45654.html", "node_id":"alm-45654.xml", "product_code":"", - "code":"926", + "code":"995", "des":"This section applies to MRS 3.3.0 or later.Flink checks whether the HA certificate file is about to expire in the first health check or at 01:00:00 every day. This alarm ", "doc_type":"", "kw":"ALM-45654 Flink HA Certificate Is About to Expire,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16902,7 +18078,7 @@ "uri":"ALM-45655.html", "node_id":"alm-45655.xml", "product_code":"", - "code":"927", + "code":"996", "des":"This section applies to MRS 3.3.0 or later.Flink checks whether the HA certificate file has expired in the first health check or at 01:00:00 every day. This alarm is gene", "doc_type":"", "kw":"ALM-45655 Flink HA Certificate File Has Expired,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16919,7 +18095,7 @@ "uri":"ALM-45736.html", "node_id":"alm-45736.xml", "product_code":"mrs", - "code":"928", + "code":"997", "des":"The alarm module checks the Guardian service status every 60 seconds. This alarm is generated if Guardian is unavailable.This alarm is cleared after Guardian recovers.Gua", "doc_type":"alarm", "kw":"ALM-45736 Guardian Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -16937,7 +18113,7 @@ "uri":"ALM-45737.html", "node_id":"alm-45737.xml", "product_code":"", - "code":"929", + "code":"998", "des":"The system checks the heap memory usage of the TokenServer service every 60 seconds. This alarm is generated when the heap memory usage of the TokenServer instance exceed", "doc_type":"", "kw":"ALM-45737 TokenServer Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x", @@ -16954,7 +18130,7 @@ "uri":"ALM-45738.html", "node_id":"alm-45738.xml", "product_code":"", - "code":"930", + "code":"999", "des":"The system checks the direct memory usage of the TokenServer service every 60 seconds. This alarm is generated when the direct memory usage of the TokenServer instance ex", "doc_type":"", "kw":"ALM-45738 TokenServer Direct Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", @@ -16971,7 +18147,7 @@ "uri":"ALM-45739.html", "node_id":"alm-45739.xml", "product_code":"", - "code":"931", + "code":"1000", "des":"The system checks the heap memory usage of the TokenServer service every 60 seconds. This alarm is generated when the non-heap memory usage of the TokenServer instance ex", "doc_type":"", "kw":"ALM-45739 TokenServer Non-Heap Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS", @@ -16988,7 +18164,7 @@ "uri":"ALM-45740.html", "node_id":"alm-45740.xml", "product_code":"", - "code":"932", + "code":"1001", "des":"The system checks the GC duration of the TokenServer process every 60 seconds. This alarm is generated when the GC duration of the TokenServer process exceeds the thresho", "doc_type":"", "kw":"ALM-45740 TokenServer GC Duration Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User", @@ -17005,7 +18181,7 @@ "uri":"ALM-45741.html", "node_id":"alm-45741.xml", "product_code":"mrs", - "code":"933", + "code":"1002", "des":"Guardian caches the temporary AK/SK of the ECS agency. When the cache does not exist or is about to expire, Guardian calls the securitykey API of ECS to update the AK/SK.", "doc_type":"alarm", "kw":"ALM-45741 Failed to Call the ECS securitykey API,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17023,7 +18199,7 @@ "uri":"ALM-45742.html", "node_id":"alm-45742.xml", "product_code":"mrs", - "code":"934", + "code":"1003", "des":"When Guardian calls an IAM API to obtain the temporary AK/SK, it needs to first obtain related metadata via the ECS Metadata API. This alarm is generated when Guardian fa", "doc_type":"alarm", "kw":"ALM-45742 Failed to Call the ECS Metadata API,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17041,7 +18217,7 @@ "uri":"ALM-45743.html", "node_id":"alm-45743.xml", "product_code":"mrs", - "code":"935", + "code":"1004", "des":"This alarm is generated when Guardian fails to call the IAM API to obtain a temporary AK/SK.The task may fail to obtain the temporary AK/SK for accessing OBS. As a result", "doc_type":"alarm", "kw":"ALM-45743 Failed to Call the IAM API,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17055,11 +18231,113 @@ "title":"ALM-45743 Failed to Call the IAM API", "githuburl":"" }, + { + "uri":"ALM-45744.html", + "node_id":"alm-45744.xml", + "product_code":"", + "code":"1005", + "des":"The system checks the average RPC processing time of the TokenServer service every 30 seconds. This alarm is generated when the average RPC processing time of the TokenSe", + "doc_type":"", + "kw":"ALM-45744 Average RPC Processing Time of the Guardian TokenServer Exceeds the Threshold,Alarm Refere", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45744 Average RPC Processing Time of the Guardian TokenServer Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-45745.html", + "node_id":"alm-45745.xml", + "product_code":"", + "code":"1006", + "des":"The system checks the average RPC queuing time of the TokenServer service every 30 seconds. This alarm is generated when the average RPC queuing time of the TokenServer i", + "doc_type":"", + "kw":"ALM-45745 Average RPC Queuing Time of the Guardian TokenServer Exceeds the Threshold,Alarm Reference", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-45745 Average RPC Queuing Time of the Guardian TokenServer Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-47001.html", + "node_id":"alm-47001.xml", + "product_code":"", + "code":"1007", + "des":"This section is available for MRS 3.3.1-LTS or later version only.The system checks the status of the ZooKeeper service on which the MemArtsCC depends every 60 seconds. T", + "doc_type":"", + "kw":"ALM-47001 MemArtsCC Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-47001 MemArtsCC Service Unavailable", + "githuburl":"" + }, + { + "uri":"ALM-47002.html", + "node_id":"alm-47002.xml", + "product_code":"", + "code":"1008", + "des":"This section is available for MRS 3.3.1-LTS or later version only.The alarm module checks the status of the local disk used by MemArtsCC every 60 seconds. This alarm is g", + "doc_type":"", + "kw":"ALM-47002 MemArtsCC Disk Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-47002 MemArtsCC Disk Fault", + "githuburl":"" + }, + { + "uri":"ALM-47003.html", + "node_id":"alm-47003.xml", + "product_code":"", + "code":"1009", + "des":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the memory usage of the CCWorker process of the MemArtsCC component every 30 seconds. ", + "doc_type":"", + "kw":"ALM-47003 Memory Usage of the MemArtsCC Worker Process Exceeds the Threshold,Alarm Reference (Applic", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-47003 Memory Usage of the MemArtsCC Worker Process Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-47004.html", + "node_id":"alm-47004.xml", + "product_code":"", + "code":"1010", + "des":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the average latency of all read requests to the MemArtsCC Worker process component eve", + "doc_type":"", + "kw":"ALM-47004 Average Latency of MemArtsCC Worker Read Requests Exceeds the Threshold,Alarm Reference (A", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-47004 Average Latency of MemArtsCC Worker Read Requests Exceeds the Threshold", + "githuburl":"" + }, { "uri":"ALM-50201.html", "node_id":"alm-50201.xml", "product_code":"", - "code":"936", + "code":"1011", "des":"The alarm module checks the Doris service status every 60 seconds. This alarm is generated when the alarm module detects that all FE and BE instances are abnormal.This al", "doc_type":"", "kw":"ALM-50201 Doris Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17076,7 +18354,7 @@ "uri":"ALM-50202.html", "node_id":"alm-50202.xml", "product_code":"", - "code":"937", + "code":"1012", "des":"The system checks the CPU usage of the FE instance every 30 seconds. The CPU usage has a default threshold. This alarm is generated when the CPU usage exceeds the thresho", "doc_type":"", "kw":"ALM-50202 FE CPU Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17093,7 +18371,7 @@ "uri":"ALM-50203.html", "node_id":"alm-50203.xml", "product_code":"", - "code":"938", + "code":"1013", "des":"The system checks the memory usage of the FE instance every 30 seconds. This alarm is generated when the memory usage exceeds the threshold (95% by default) for multiple ", "doc_type":"", "kw":"ALM-50203 FE Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17110,7 +18388,7 @@ "uri":"ALM-50205.html", "node_id":"alm-50205.xml", "product_code":"", - "code":"939", + "code":"1014", "des":"The system checks the CPU usage of the BE instance every 30 seconds. This alarm is generated when the CPU usage exceeds the threshold (95% by default) for multiple consec", "doc_type":"", "kw":"ALM-50205 BE CPU Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17127,7 +18405,7 @@ "uri":"ALM-50206.html", "node_id":"alm-50206.xml", "product_code":"", - "code":"940", + "code":"1015", "des":"The system checks the memory usage of the BE instance every 30 seconds. This alarm is generated when the memory usage exceeds the threshold for multiple consecutive times", "doc_type":"", "kw":"ALM-50206 BE Memory Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17144,7 +18422,7 @@ "uri":"ALM-50207.html", "node_id":"alm-50207.xml", "product_code":"", - "code":"941", + "code":"1016", "des":"The system checks the number of MySQL port connections every 30 seconds. This alarm is generated when the ratio of the number of current connections to the maximum number", "doc_type":"", "kw":"ALM-50207 Ratio of Connections to the FE MySQL Port to the Maximum Connections Allowed Exceeds the T", @@ -17161,7 +18439,7 @@ "uri":"ALM-50208.html", "node_id":"alm-50208.xml", "product_code":"", - "code":"942", + "code":"1017", "des":"The system checks the number of failures to clear historical metadata image files on the FE node every 30 seconds. This alarm is generated when the number of failures exc", "doc_type":"", "kw":"ALM-50208 Failures to Clear Historical Metadata Image Files Exceed the Threshold,Alarm Reference (Ap", @@ -17178,7 +18456,7 @@ "uri":"ALM-50209.html", "node_id":"alm-50209.xml", "product_code":"", - "code":"943", + "code":"1018", "des":"The system checks the number of failures to generate metadata image files on the FE node every 30 seconds. This alarm is generated when the number of failures exceeds the", "doc_type":"", "kw":"ALM-50209 Failures to Generate Metadata Image Files Exceed the Threshold,Alarm Reference (Applicable", @@ -17195,7 +18473,7 @@ "uri":"ALM-50210.html", "node_id":"alm-50210.xml", "product_code":"", - "code":"944", + "code":"1019", "des":"The system checks the maximum compaction score of all BE nodes every 30 seconds. This alarm is generated when the maximum compaction score exceeds the threshold (10 by de", "doc_type":"", "kw":"ALM-50210 Maximum Compaction Score of All BE Nodes Exceeds the Threshold,Alarm Reference (Applicable", @@ -17212,7 +18490,7 @@ "uri":"ALM-50211.html", "node_id":"alm-50211.xml", "product_code":"", - "code":"945", + "code":"1020", "des":"The system checks the queue length of each BE periodic report task on FE every 30 seconds. This alarm is generated when the queue length exceeds the threshold (10 by defa", "doc_type":"", "kw":"ALM-50211 FE Queue Length of BE Periodic Report Tasks Exceeds the Threshold,Alarm Reference (Applica", @@ -17229,7 +18507,7 @@ "uri":"ALM-50212.html", "node_id":"alm-50212.xml", "product_code":"", - "code":"946", + "code":"1021", "des":"The system checks the accumulated old-generation GC duration of the FE process every 30 seconds. This alarm is generated when the accumulated GC duration exceeds the thre", "doc_type":"", "kw":"ALM-50212 Accumulated Old-Generation GC Duration of the FE Process Exceeds the Threshold,Alarm Refer", @@ -17246,7 +18524,7 @@ "uri":"ALM-50213.html", "node_id":"alm-50213.xml", "product_code":"", - "code":"947", + "code":"1022", "des":"The system checks the number of queuing tasks in the FE thread pool for interacting with BE every 30 seconds. This alarm is generated when the number of queuing tasks exc", "doc_type":"", "kw":"ALM-50213 Number of Tasks Queuing in the FE Thread Pool for Interacting with BE Exceeds the Threshol", @@ -17263,7 +18541,7 @@ "uri":"ALM-50214.html", "node_id":"alm-50214.xml", "product_code":"", - "code":"948", + "code":"1023", "des":"The system checks the number of queuing tasks in the FE thread pool for processing tasks every 30 seconds. This alarm is generated when the number of queuing tasks exceed", "doc_type":"", "kw":"ALM-50214 Number of Tasks Queuing in the FE Thread Pool for Task Processing Exceeds the Threshold,Al", @@ -17280,7 +18558,7 @@ "uri":"ALM-50215.html", "node_id":"alm-50215.xml", "product_code":"", - "code":"949", + "code":"1024", "des":"The system checks the longest duration of RPC requests received by each FE Thrift method every 30 seconds. This alarm is generated when the longest duration exceeds the t", "doc_type":"", "kw":"ALM-50215 Longest Duration of RPC Requests Received by Each FE Thrift Method Exceeds the Threshold,A", @@ -17297,7 +18575,7 @@ "uri":"ALM-50216.html", "node_id":"alm-50216.xml", "product_code":"", - "code":"950", + "code":"1025", "des":"The system checks the memory usage of the FE node every 30 seconds. This alarm is generated when the memory usage exceeds the threshold (95% by default).This alarm is cle", "doc_type":"", "kw":"ALM-50216 Memory Usage of the FE Node Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),", @@ -17314,7 +18592,7 @@ "uri":"ALM-50217.html", "node_id":"alm-50217.xml", "product_code":"", - "code":"951", + "code":"1026", "des":"The system checks the heap memory usage of the FE node every 30 seconds. This alarm is generated when the heap memory usage exceeds the threshold (95% by default).This al", "doc_type":"", "kw":"ALM-50217 Heap Memory Usage of the FE Node Exceeds the Threshold,Alarm Reference (Applicable to MRS ", @@ -17331,7 +18609,7 @@ "uri":"ALM-50219.html", "node_id":"alm-50219.xml", "product_code":"", - "code":"952", + "code":"1027", "des":"The system checks the length of the waiting queue in the query execution thread pool every 30 seconds. This alarm is generated when the length exceeds the threshold (20 b", "doc_type":"", "kw":"ALM-50219 Length of the Queue in the Thread Pool for Query Execution Exceeds the Threshold,Alarm Ref", @@ -17348,7 +18626,7 @@ "uri":"ALM-50220.html", "node_id":"alm-50220.xml", "product_code":"", - "code":"953", + "code":"1028", "des":"The system checks the rate of TCP packet receiving errors every 30 seconds. This alarm is generated when the error rate exceeds the threshold (5% by default).This alarm i", "doc_type":"", "kw":"ALM-50220 Error Rate of TCP Packet Receiving Exceeds the Threshold,Alarm Reference (Applicable to MR", @@ -17365,7 +18643,7 @@ "uri":"ALM-50221.html", "node_id":"alm-50221.xml", "product_code":"", - "code":"954", + "code":"1029", "des":"The system checks the usage of BE data disks every 30 seconds. This alarm is generated when the disk usage exceeds the threshold (95% by default).This alarm is cleared wh", "doc_type":"", "kw":"ALM-50221 BE Data Disk Usage Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.x),User Guid", @@ -17382,7 +18660,7 @@ "uri":"ALM-50222.html", "node_id":"alm-50222.xml", "product_code":"", - "code":"955", + "code":"1030", "des":"The system checks the disk status of a specified data directory on BE every 30 seconds. This alarm is generated when the disk status is not 1 (1 indicates the normal stat", "doc_type":"", "kw":"ALM-50222 Disk Status of a Specified Data Directory on BE Is Abnormal,Alarm Reference (Applicable to", @@ -17399,7 +18677,7 @@ "uri":"ALM-50223.html", "node_id":"alm-50223.xml", "product_code":"", - "code":"956", + "code":"1031", "des":"The system checks whether the maximum memory required by BE is greater than the available memory every 30 seconds. This alarm is generated when the value is not 1 (1 indi", "doc_type":"", "kw":"ALM-50223 Maximum Memory Required by BE Is Greater Than the Remaining Memory of the Machine,Alarm Re", @@ -17416,7 +18694,7 @@ "uri":"ALM-50224.html", "node_id":"alm-50224.xml", "product_code":"", - "code":"957", + "code":"1032", "des":"The system checks whether the number of failed tasks of a certain type on BE is increasing every 30 seconds. This alarm is generated when the system detects that the valu", "doc_type":"", "kw":"ALM-50224 Failures a Certain Task Type on BE Are Increasing,Alarm Reference (Applicable to MRS 3.x),", @@ -17433,7 +18711,7 @@ "uri":"ALM-50225.html", "node_id":"alm-50225.xml", "product_code":"", - "code":"958", + "code":"1033", "des":"The system checks the FE process status every 30 seconds. This alarm is generated when the value is greater than 0 (0 indicates that the FE process is normal and 1 indica", "doc_type":"", "kw":"ALM-50225 FE Instance Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17450,7 +18728,7 @@ "uri":"ALM-50226.html", "node_id":"alm-50226.xml", "product_code":"", - "code":"959", + "code":"1034", "des":"The system checks the BE process status every 30 seconds. This alarm is generated when the value is greater than 0 (0 indicates that the BE process is normal and 1 indica", "doc_type":"", "kw":"ALM-50226 BE Instance Fault,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17463,11 +18741,113 @@ "title":"ALM-50226 BE Instance Fault", "githuburl":"" }, + { + "uri":"ALM-50227.html", + "node_id":"alm-50227.xml", + "product_code":"", + "code":"1035", + "des":"The system checks concurrent tenant queries on FE nodes every 30 seconds. This alarm is generated when the number exceeds the threshold (90% by default).This alarm is cle", + "doc_type":"", + "kw":"ALM-50227 Concurrent Doris Tenant Queries Exceeds the Threshold,Alarm Reference (Applicable to MRS 3", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50227 Concurrent Doris Tenant Queries Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-50228.html", + "node_id":"alm-50228.xml", + "product_code":"", + "code":"1036", + "des":"The system checks the memory usage of BE nodes every 30 seconds. This alarm is generated when the memory usage of a tenant exceeds the threshold.This alarm is cleared whe", + "doc_type":"", + "kw":"ALM-50228 Memory Usage of a Doris Tenant Exceeds the Threshold,Alarm Reference (Applicable to MRS 3.", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50228 Memory Usage of a Doris Tenant Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-50229.html", + "node_id":"alm-50229.xml", + "product_code":"", + "code":"1037", + "des":"The system checks whether the connection between the Doris FE nodes and OBS is available every 30 seconds. This alarm is generated when the connection status code is not ", + "doc_type":"", + "kw":"ALM-50229 Doris FE Failed to Connect to OBS,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50229 Doris FE Failed to Connect to OBS", + "githuburl":"" + }, + { + "uri":"ALM-50230.html", + "node_id":"alm-50230.xml", + "product_code":"", + "code":"1038", + "des":"The system checks whether the connection between the Doris BE nodes and OBS is available every 30 seconds. This alarm is generated when the connection status code is not ", + "doc_type":"", + "kw":"ALM-50230 Doris BE Cannot Connect to OBS,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50230 Doris BE Cannot Connect to OBS", + "githuburl":"" + }, + { + "uri":"ALM-50231.html", + "node_id":"alm-50231.xml", + "product_code":"", + "code":"1039", + "des":"The alarm module checks for abnormal tablets in the Doris cluster every 5 minutes. This alarm is generated when an abnormal tablet is detected.This alarm is cleared when ", + "doc_type":"", + "kw":"ALM-50231 Abnormal Tablets Exist in Doris,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50231 Abnormal Tablets Exist in Doris", + "githuburl":"" + }, + { + "uri":"ALM-50232.html", + "node_id":"alm-50232.xml", + "product_code":"", + "code":"1040", + "des":"The alarm module checks whether a tablet greater than 3 GB (specified by the alarm_tablet_max_size parameter) exists in the Doris cluster every 5 minutes. This alarm is g", + "doc_type":"", + "kw":"ALM-50232 Large Tablets in Doris,Alarm Reference (Applicable to MRS 3.x),User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50232 Large Tablets in Doris", + "githuburl":"" + }, { "uri":"ALM-50401.html", "node_id":"alm-50401.xml", "product_code":"", - "code":"960", + "code":"1041", "des":"This section applies only to MRS 3.3.0 or later.The system checks the number of jobs submitted to JobServer every 30 seconds. This alarm is generated when the number of j", "doc_type":"", "kw":"ALM-50401 Number of JobServer Jobs Waiting to Be Executed Exceeds the Threshold,Alarm Reference (App", @@ -17484,7 +18864,7 @@ "uri":"ALM-50402.html", "node_id":"alm-50402.xml", "product_code":"", - "code":"961", + "code":"1042", "des":"This section applies only to MRS 3.3.0 or later.The system checks the JobGateway service status every 60 seconds. This alarm is generated when the JobGateway service is a", "doc_type":"", "kw":"ALM-50402 JobGateway Service Unavailable,Alarm Reference (Applicable to MRS 3.x),User Guide", @@ -17497,11 +18877,62 @@ "title":"ALM-50402 JobGateway Service Unavailable", "githuburl":"" }, + { + "uri":"ALM-50406.html", + "node_id":"alm-50406.xml", + "product_code":"", + "code":"1043", + "des":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the failure rate of the JobServer job submission API every 30 seconds. This alarm is g", + "doc_type":"", + "kw":"ALM-50406 Failure Rate of the JobServer Job Submission API Exceeds the Threshold,Alarm Reference (Ap", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50406 Failure Rate of the JobServer Job Submission API Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-50407.html", + "node_id":"alm-50407.xml", + "product_code":"", + "code":"1044", + "des":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the failure rate of the JobServer job query API every 30 seconds. This alarm is genera", + "doc_type":"", + "kw":"ALM-50407 Failure Rate of the JobServer Job Query API Exceeds the Threshold,Alarm Reference (Applica", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50407 Failure Rate of the JobServer Job Query API Exceeds the Threshold", + "githuburl":"" + }, + { + "uri":"ALM-50408.html", + "node_id":"alm-50408.xml", + "product_code":"", + "code":"1045", + "des":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the failure rate of the JobServer job termination API every 30 seconds. This alarm is ", + "doc_type":"", + "kw":"ALM-50408 Failure Rate of the JobServer Job Termination API Exceeds the Threshold,Alarm Reference (A", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"ALM-50408 Failure Rate of the JobServer Job Termination API Exceeds the Threshold", + "githuburl":"" + }, { "uri":"mrs_01_0648.html", "node_id":"mrs_01_0648.xml", "product_code":"mrs", - "code":"962", + "code":"1046", "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)", @@ -17520,7 +18951,7 @@ "uri":"mrs_01_0101.html", "node_id":"mrs_01_0101.xml", "product_code":"mrs", - "code":"963", + "code":"1047", "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", @@ -17540,7 +18971,7 @@ "uri":"mrs_01_0105.html", "node_id":"mrs_01_0105.xml", "product_code":"mrs", - "code":"964", + "code":"1048", "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", @@ -17559,7 +18990,7 @@ "uri":"mrs_01_0106.html", "node_id":"mrs_01_0106.xml", "product_code":"mrs", - "code":"965", + "code":"1049", "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", @@ -17578,7 +19009,7 @@ "uri":"mrs_01_0107.html", "node_id":"mrs_01_0107.xml", "product_code":"mrs", - "code":"966", + "code":"1050", "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", @@ -17597,7 +19028,7 @@ "uri":"mrs_01_0232.html", "node_id":"mrs_01_0232.xml", "product_code":"mrs", - "code":"967", + "code":"1051", "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", @@ -17616,7 +19047,7 @@ "uri":"mrs_01_0233.html", "node_id":"mrs_01_0233.xml", "product_code":"mrs", - "code":"968", + "code":"1052", "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", @@ -17634,7 +19065,7 @@ "uri":"mrs_01_0235.html", "node_id":"mrs_01_0235.xml", "product_code":"mrs", - "code":"969", + "code":"1053", "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", @@ -17654,7 +19085,7 @@ "uri":"mrs_01_0236.html", "node_id":"mrs_01_0236.xml", "product_code":"mrs", - "code":"970", + "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":"Alarm Management", @@ -17673,7 +19104,7 @@ "uri":"mrs_01_0237.html", "node_id":"mrs_01_0237.xml", "product_code":"mrs", - "code":"971", + "code":"1055", "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", @@ -17692,7 +19123,7 @@ "uri":"mrs_01_0238.html", "node_id":"mrs_01_0238.xml", "product_code":"mrs", - "code":"972", + "code":"1056", "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", @@ -17711,7 +19142,7 @@ "uri":"mrs_01_0239.html", "node_id":"mrs_01_0239.xml", "product_code":"mrs", - "code":"973", + "code":"1057", "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", @@ -17730,7 +19161,7 @@ "uri":"mrs_01_0240.html", "node_id":"mrs_01_0240.xml", "product_code":"mrs", - "code":"974", + "code":"1058", "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", @@ -17749,7 +19180,7 @@ "uri":"mrs_01_0241.html", "node_id":"mrs_01_0241.xml", "product_code":"mrs", - "code":"975", + "code":"1059", "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)", @@ -17768,7 +19199,7 @@ "uri":"alm_12001.html", "node_id":"alm_12001.xml", "product_code":"mrs", - "code":"976", + "code":"1060", "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 ", @@ -17788,7 +19219,7 @@ "uri":"alm_12002.html", "node_id":"alm_12002.xml", "product_code":"mrs", - "code":"977", + "code":"1061", "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", @@ -17807,7 +19238,7 @@ "uri":"alm_12004.html", "node_id":"alm_12004.xml", "product_code":"mrs", - "code":"978", + "code":"1062", "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", @@ -17826,7 +19257,7 @@ "uri":"alm_12005.html", "node_id":"alm_12005.xml", "product_code":"mrs", - "code":"979", + "code":"1063", "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.", @@ -17845,7 +19276,7 @@ "uri":"alm_12006.html", "node_id":"alm_12006.xml", "product_code":"mrs", - "code":"980", + "code":"1064", "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", @@ -17864,7 +19295,7 @@ "uri":"alm_12007.html", "node_id":"alm_12007.xml", "product_code":"mrs", - "code":"981", + "code":"1065", "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", @@ -17883,7 +19314,7 @@ "uri":"alm_12010.html", "node_id":"alm_12010.xml", "product_code":"mrs", - "code":"982", + "code":"1066", "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", @@ -17903,7 +19334,7 @@ "uri":"alm_12011.html", "node_id":"alm_12011.xml", "product_code":"mrs", - "code":"983", + "code":"1067", "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", @@ -17922,7 +19353,7 @@ "uri":"alm_12012.html", "node_id":"alm_12012.xml", "product_code":"mrs", - "code":"984", + "code":"1068", "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", @@ -17942,7 +19373,7 @@ "uri":"alm_12016.html", "node_id":"alm_12016.xml", "product_code":"mrs", - "code":"985", + "code":"1069", "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", @@ -17961,7 +19392,7 @@ "uri":"alm_12017.html", "node_id":"alm_12017.xml", "product_code":"mrs", - "code":"986", + "code":"1070", "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", @@ -17980,7 +19411,7 @@ "uri":"alm_12018.html", "node_id":"alm_12018.xml", "product_code":"mrs", - "code":"987", + "code":"1071", "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", @@ -17999,7 +19430,7 @@ "uri":"alm_12027.html", "node_id":"alm_12027.xml", "product_code":"mrs", - "code":"988", + "code":"1072", "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 ", @@ -18019,7 +19450,7 @@ "uri":"alm_12028.html", "node_id":"alm_12028.xml", "product_code":"mrs", - "code":"989", + "code":"1073", "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", @@ -18038,7 +19469,7 @@ "uri":"alm_12031.html", "node_id":"alm_12031.xml", "product_code":"mrs", - "code":"990", + "code":"1074", "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", @@ -18057,7 +19488,7 @@ "uri":"alm_12032.html", "node_id":"alm_12032.xml", "product_code":"mrs", - "code":"991", + "code":"1075", "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", @@ -18076,7 +19507,7 @@ "uri":"alm_12033.html", "node_id":"alm_12033.xml", "product_code":"mrs", - "code":"992", + "code":"1076", "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", @@ -18095,7 +19526,7 @@ "uri":"alm_12034.html", "node_id":"alm_12034.xml", "product_code":"mrs", - "code":"993", + "code":"1077", "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", @@ -18115,7 +19546,7 @@ "uri":"alm_12035.html", "node_id":"alm_12035.xml", "product_code":"mrs", - "code":"994", + "code":"1078", "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", @@ -18135,7 +19566,7 @@ "uri":"alm_12037.html", "node_id":"alm_12037.xml", "product_code":"mrs", - "code":"995", + "code":"1079", "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 ", @@ -18154,7 +19585,7 @@ "uri":"alm_12038.html", "node_id":"alm_12038.xml", "product_code":"mrs", - "code":"996", + "code":"1080", "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", @@ -18173,7 +19604,7 @@ "uri":"alm_12039.html", "node_id":"alm_12039.xml", "product_code":"mrs", - "code":"997", + "code":"1081", "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 ", @@ -18192,7 +19623,7 @@ "uri":"alm_12040.html", "node_id":"alm_12040.xml", "product_code":"mrs", - "code":"998", + "code":"1082", "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),", @@ -18211,7 +19642,7 @@ "uri":"alm_13000.html", "node_id":"alm_13000.xml", "product_code":"mrs", - "code":"999", + "code":"1083", "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", @@ -18230,7 +19661,7 @@ "uri":"alm_13001.html", "node_id":"alm_13001.xml", "product_code":"mrs", - "code":"1000", + "code":"1084", "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", @@ -18249,7 +19680,7 @@ "uri":"alm_13002.html", "node_id":"alm_13002.xml", "product_code":"mrs", - "code":"1001", + "code":"1085", "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", @@ -18269,7 +19700,7 @@ "uri":"alm_14000.html", "node_id":"alm_14000.xml", "product_code":"mrs", - "code":"1002", + "code":"1086", "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", @@ -18288,7 +19719,7 @@ "uri":"alm_14001.html", "node_id":"alm_14001.xml", "product_code":"mrs", - "code":"1003", + "code":"1087", "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", @@ -18307,7 +19738,7 @@ "uri":"alm_14002.html", "node_id":"alm_14002.xml", "product_code":"mrs", - "code":"1004", + "code":"1088", "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 ", @@ -18326,7 +19757,7 @@ "uri":"alm_14003.html", "node_id":"alm_14003.xml", "product_code":"mrs", - "code":"1005", + "code":"1089", "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", @@ -18345,7 +19776,7 @@ "uri":"alm_14004.html", "node_id":"alm_14004.xml", "product_code":"mrs", - "code":"1006", + "code":"1090", "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", @@ -18364,7 +19795,7 @@ "uri":"alm_14006.html", "node_id":"alm_14006.xml", "product_code":"mrs", - "code":"1007", + "code":"1091", "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", @@ -18383,7 +19814,7 @@ "uri":"alm_14007.html", "node_id":"alm_14007.xml", "product_code":"mrs", - "code":"1008", + "code":"1092", "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", @@ -18402,7 +19833,7 @@ "uri":"alm_14008.html", "node_id":"alm_14008.xml", "product_code":"mrs", - "code":"1009", + "code":"1093", "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", @@ -18421,7 +19852,7 @@ "uri":"alm_14009.html", "node_id":"alm_14009.xml", "product_code":"mrs", - "code":"1010", + "code":"1094", "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", @@ -18440,7 +19871,7 @@ "uri":"alm_14010.html", "node_id":"alm_14010.xml", "product_code":"mrs", - "code":"1011", + "code":"1095", "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", @@ -18459,7 +19890,7 @@ "uri":"alm_14011.html", "node_id":"alm_14011.xml", "product_code":"mrs", - "code":"1012", + "code":"1096", "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", @@ -18478,7 +19909,7 @@ "uri":"alm_14012.html", "node_id":"alm_14012.xml", "product_code":"mrs", - "code":"1013", + "code":"1097", "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 ", @@ -18497,7 +19928,7 @@ "uri":"alm_16000.html", "node_id":"alm_16000.xml", "product_code":"mrs", - "code":"1014", + "code":"1098", "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", @@ -18516,7 +19947,7 @@ "uri":"alm_16001.html", "node_id":"alm_16001.xml", "product_code":"mrs", - "code":"1015", + "code":"1099", "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", @@ -18535,7 +19966,7 @@ "uri":"alm_16002.html", "node_id":"alm_16002.xml", "product_code":"mrs", - "code":"1016", + "code":"1100", "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", @@ -18554,7 +19985,7 @@ "uri":"alm_16004.html", "node_id":"alm_16004.xml", "product_code":"mrs", - "code":"1017", + "code":"1101", "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", @@ -18573,7 +20004,7 @@ "uri":"alm_18000.html", "node_id":"alm_18000.xml", "product_code":"mrs", - "code":"1018", + "code":"1102", "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", @@ -18592,7 +20023,7 @@ "uri":"alm_18002.html", "node_id":"alm_18002.xml", "product_code":"mrs", - "code":"1019", + "code":"1103", "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", @@ -18611,7 +20042,7 @@ "uri":"alm_18003.html", "node_id":"alm_18003.xml", "product_code":"mrs", - "code":"1020", + "code":"1104", "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", @@ -18630,7 +20061,7 @@ "uri":"alm_18004.html", "node_id":"alm_18004.xml", "product_code":"mrs", - "code":"1021", + "code":"1105", "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", @@ -18649,7 +20080,7 @@ "uri":"alm_18006.html", "node_id":"alm_18006.xml", "product_code":"mrs", - "code":"1022", + "code":"1106", "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", @@ -18668,7 +20099,7 @@ "uri":"alm_19000.html", "node_id":"alm_19000.xml", "product_code":"mrs", - "code":"1023", + "code":"1107", "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", @@ -18687,7 +20118,7 @@ "uri":"alm_19006.html", "node_id":"alm_19006.xml", "product_code":"mrs", - "code":"1024", + "code":"1108", "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", @@ -18706,7 +20137,7 @@ "uri":"alm_25000.html", "node_id":"alm_25000.xml", "product_code":"mrs", - "code":"1025", + "code":"1109", "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.", @@ -18725,7 +20156,7 @@ "uri":"alm_25004.html", "node_id":"alm_25004.xml", "product_code":"mrs", - "code":"1026", + "code":"1110", "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", @@ -18744,7 +20175,7 @@ "uri":"alm_25500.html", "node_id":"alm_25500.xml", "product_code":"mrs", - "code":"1027", + "code":"1111", "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", @@ -18763,7 +20194,7 @@ "uri":"alm_27001.html", "node_id":"alm_27001.xml", "product_code":"mrs", - "code":"1028", + "code":"1112", "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", @@ -18782,7 +20213,7 @@ "uri":"alm_27003.html", "node_id":"alm_27003.xml", "product_code":"mrs", - "code":"1029", + "code":"1113", "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", @@ -18801,7 +20232,7 @@ "uri":"alm_27004.html", "node_id":"alm_27004.xml", "product_code":"mrs", - "code":"1030", + "code":"1114", "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", @@ -18820,7 +20251,7 @@ "uri":"alm_28001.html", "node_id":"alm_28001.xml", "product_code":"mrs", - "code":"1031", + "code":"1115", "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", @@ -18839,7 +20270,7 @@ "uri":"alm_26051.html", "node_id":"alm_26051.xml", "product_code":"mrs", - "code":"1032", + "code":"1116", "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", @@ -18858,7 +20289,7 @@ "uri":"alm_26052.html", "node_id":"alm_26052.xml", "product_code":"mrs", - "code":"1033", + "code":"1117", "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", @@ -18877,7 +20308,7 @@ "uri":"alm_26053.html", "node_id":"alm_26053.xml", "product_code":"mrs", - "code":"1034", + "code":"1118", "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 ", @@ -18896,7 +20327,7 @@ "uri":"alm_26054.html", "node_id":"alm_26054.xml", "product_code":"mrs", - "code":"1035", + "code":"1119", "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", @@ -18915,7 +20346,7 @@ "uri":"alm_38000.html", "node_id":"alm_38000.xml", "product_code":"mrs", - "code":"1036", + "code":"1120", "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", @@ -18934,7 +20365,7 @@ "uri":"alm_38001.html", "node_id":"alm_38001.xml", "product_code":"mrs", - "code":"1037", + "code":"1121", "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", @@ -18954,7 +20385,7 @@ "uri":"alm_38002.html", "node_id":"alm_38002.xml", "product_code":"mrs", - "code":"1038", + "code":"1122", "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", @@ -18973,7 +20404,7 @@ "uri":"alm_24000.html", "node_id":"alm_24000.xml", "product_code":"mrs", - "code":"1039", + "code":"1123", "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", @@ -18992,7 +20423,7 @@ "uri":"alm_24001.html", "node_id":"alm_24001.xml", "product_code":"mrs", - "code":"1040", + "code":"1124", "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", @@ -19011,7 +20442,7 @@ "uri":"alm_24003.html", "node_id":"alm_24003.xml", "product_code":"mrs", - "code":"1041", + "code":"1125", "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", @@ -19030,7 +20461,7 @@ "uri":"alm_24004.html", "node_id":"alm_24004.xml", "product_code":"mrs", - "code":"1042", + "code":"1126", "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", @@ -19049,7 +20480,7 @@ "uri":"alm_24005.html", "node_id":"alm_24005.xml", "product_code":"mrs", - "code":"1043", + "code":"1127", "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", @@ -19068,7 +20499,7 @@ "uri":"alm_12041.html", "node_id":"alm_12041.xml", "product_code":"mrs", - "code":"1044", + "code":"1128", "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", @@ -19087,7 +20518,7 @@ "uri":"alm_12042.html", "node_id":"alm_12042.xml", "product_code":"mrs", - "code":"1045", + "code":"1129", "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 ", @@ -19106,7 +20537,7 @@ "uri":"alm_23001.html", "node_id":"alm_23001.xml", "product_code":"mrs", - "code":"1046", + "code":"1130", "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", @@ -19125,7 +20556,7 @@ "uri":"alm_12357.html", "node_id":"alm_12357.xml", "product_code":"mrs", - "code":"1047", + "code":"1131", "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", @@ -19144,7 +20575,7 @@ "uri":"alm_12014.html", "node_id":"alm_12014.xml", "product_code":"mrs", - "code":"1048", + "code":"1132", "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", @@ -19163,7 +20594,7 @@ "uri":"alm_12015.html", "node_id":"alm_12015.xml", "product_code":"mrs", - "code":"1049", + "code":"1133", "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", @@ -19182,7 +20613,7 @@ "uri":"alm_12043.html", "node_id":"alm_12043.xml", "product_code":"mrs", - "code":"1050", + "code":"1134", "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", @@ -19201,7 +20632,7 @@ "uri":"alm_12045.html", "node_id":"alm_12045.xml", "product_code":"mrs", - "code":"1051", + "code":"1135", "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", @@ -19220,7 +20651,7 @@ "uri":"alm_12046.html", "node_id":"alm_12046.xml", "product_code":"mrs", - "code":"1052", + "code":"1136", "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", @@ -19239,7 +20670,7 @@ "uri":"alm_12047.html", "node_id":"alm_12047.xml", "product_code":"mrs", - "code":"1053", + "code":"1137", "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", @@ -19258,7 +20689,7 @@ "uri":"alm_12048.html", "node_id":"alm_12048.xml", "product_code":"mrs", - "code":"1054", + "code":"1138", "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", @@ -19277,7 +20708,7 @@ "uri":"alm_12049.html", "node_id":"alm_12049.xml", "product_code":"mrs", - "code":"1055", + "code":"1139", "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", @@ -19296,7 +20727,7 @@ "uri":"alm_12050.html", "node_id":"alm_12050.xml", "product_code":"mrs", - "code":"1056", + "code":"1140", "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", @@ -19315,7 +20746,7 @@ "uri":"alm_12051.html", "node_id":"alm_12051.xml", "product_code":"mrs", - "code":"1057", + "code":"1141", "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", @@ -19334,7 +20765,7 @@ "uri":"alm_12052.html", "node_id":"alm_12052.xml", "product_code":"mrs", - "code":"1058", + "code":"1142", "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", @@ -19353,7 +20784,7 @@ "uri":"alm_12053.html", "node_id":"alm_12053.xml", "product_code":"mrs", - "code":"1059", + "code":"1143", "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", @@ -19372,7 +20803,7 @@ "uri":"alm_12054.html", "node_id":"alm_12054.xml", "product_code":"mrs", - "code":"1060", + "code":"1144", "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", @@ -19392,7 +20823,7 @@ "uri":"alm_12055.html", "node_id":"alm_12055.xml", "product_code":"mrs", - "code":"1061", + "code":"1145", "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", @@ -19412,7 +20843,7 @@ "uri":"alm_18008.html", "node_id":"alm_18008.xml", "product_code":"mrs", - "code":"1062", + "code":"1146", "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", @@ -19431,7 +20862,7 @@ "uri":"alm_18009.html", "node_id":"alm_18009.xml", "product_code":"mrs", - "code":"1063", + "code":"1147", "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", @@ -19450,7 +20881,7 @@ "uri":"alm_20002.html", "node_id":"alm_20002.xml", "product_code":"mrs", - "code":"1064", + "code":"1148", "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", @@ -19469,7 +20900,7 @@ "uri":"alm_43001.html", "node_id":"alm_43001.xml", "product_code":"mrs", - "code":"1065", + "code":"1149", "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", @@ -19488,7 +20919,7 @@ "uri":"alm_43006.html", "node_id":"alm_43006.xml", "product_code":"mrs", - "code":"1066", + "code":"1150", "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", @@ -19507,7 +20938,7 @@ "uri":"alm_43007.html", "node_id":"alm_43007.xml", "product_code":"mrs", - "code":"1067", + "code":"1151", "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", @@ -19526,7 +20957,7 @@ "uri":"alm_43008.html", "node_id":"alm_43008.xml", "product_code":"mrs", - "code":"1068", + "code":"1152", "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", @@ -19545,7 +20976,7 @@ "uri":"alm_43009.html", "node_id":"alm_43009.xml", "product_code":"mrs", - "code":"1069", + "code":"1153", "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", @@ -19564,7 +20995,7 @@ "uri":"alm_43010.html", "node_id":"alm_43010.xml", "product_code":"mrs", - "code":"1070", + "code":"1154", "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", @@ -19583,7 +21014,7 @@ "uri":"alm_43011.html", "node_id":"alm_43011.xml", "product_code":"mrs", - "code":"1071", + "code":"1155", "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", @@ -19602,7 +21033,7 @@ "uri":"alm_43012.html", "node_id":"alm_43012.xml", "product_code":"mrs", - "code":"1072", + "code":"1156", "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", @@ -19621,7 +21052,7 @@ "uri":"alm_43013.html", "node_id":"alm_43013.xml", "product_code":"mrs", - "code":"1073", + "code":"1157", "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", @@ -19640,7 +21071,7 @@ "uri":"alm_44004.html", "node_id":"alm_44004.xml", "product_code":"mrs", - "code":"1074", + "code":"1158", "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", @@ -19659,7 +21090,7 @@ "uri":"alm_44005.html", "node_id":"alm_44005.xml", "product_code":"mrs", - "code":"1075", + "code":"1159", "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", @@ -19678,7 +21109,7 @@ "uri":"alm_44006.html", "node_id":"alm_44006.xml", "product_code":"mrs", - "code":"1076", + "code":"1160", "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", @@ -19697,7 +21128,7 @@ "uri":"alm_18010.html", "node_id":"alm_18010.xml", "product_code":"mrs", - "code":"1077", + "code":"1161", "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", @@ -19717,7 +21148,7 @@ "uri":"alm_18011.html", "node_id":"alm_18011.xml", "product_code":"mrs", - "code":"1078", + "code":"1162", "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", @@ -19737,7 +21168,7 @@ "uri":"alm_18012.html", "node_id":"alm_18012.xml", "product_code":"mrs", - "code":"1079", + "code":"1163", "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 (", @@ -19756,7 +21187,7 @@ "uri":"alm_18013.html", "node_id":"alm_18013.xml", "product_code":"mrs", - "code":"1080", + "code":"1164", "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", @@ -19775,7 +21206,7 @@ "uri":"alm_16005.html", "node_id":"alm_16005.xml", "product_code":"mrs", - "code":"1081", + "code":"1165", "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", @@ -19794,7 +21225,7 @@ "uri":"mrs_01_0242.html", "node_id":"mrs_01_0242.xml", "product_code":"mrs", - "code":"1082", + "code":"1166", "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", @@ -19813,7 +21244,7 @@ "uri":"mrs_01_0243.html", "node_id":"mrs_01_0243.xml", "product_code":"mrs", - "code":"1083", + "code":"1167", "des":"MRS contains different types of basic objects as described in Table 1.", "doc_type":"usermanual", "kw":"Managing Objects,Object Management,User Guide", @@ -19832,7 +21263,7 @@ "uri":"mrs_01_0244.html", "node_id":"mrs_01_0244.xml", "product_code":"mrs", - "code":"1084", + "code":"1168", "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", @@ -19851,7 +21282,7 @@ "uri":"mrs_01_0245.html", "node_id":"mrs_01_0245.xml", "product_code":"mrs", - "code":"1085", + "code":"1169", "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", @@ -19870,7 +21301,7 @@ "uri":"mrs_01_0246.html", "node_id":"mrs_01_0246.xml", "product_code":"mrs", - "code":"1086", + "code":"1170", "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", @@ -19889,7 +21320,7 @@ "uri":"mrs_01_0247.html", "node_id":"mrs_01_0247.xml", "product_code":"mrs", - "code":"1087", + "code":"1171", "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", @@ -19908,7 +21339,7 @@ "uri":"mrs_01_0248.html", "node_id":"mrs_01_0248.xml", "product_code":"mrs", - "code":"1088", + "code":"1172", "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", @@ -19928,7 +21359,7 @@ "uri":"mrs_01_0249.html", "node_id":"mrs_01_0249.xml", "product_code":"mrs", - "code":"1089", + "code":"1173", "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", @@ -19948,7 +21379,7 @@ "uri":"mrs_01_0250.html", "node_id":"mrs_01_0250.xml", "product_code":"mrs", - "code":"1090", + "code":"1174", "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", @@ -19967,7 +21398,7 @@ "uri":"mrs_01_0251.html", "node_id":"mrs_01_0251.xml", "product_code":"mrs", - "code":"1091", + "code":"1175", "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", @@ -19987,7 +21418,7 @@ "uri":"mrs_01_0252.html", "node_id":"mrs_01_0252.xml", "product_code":"mrs", - "code":"1092", + "code":"1176", "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", @@ -20006,7 +21437,7 @@ "uri":"mrs_01_0254.html", "node_id":"mrs_01_0254.xml", "product_code":"mrs", - "code":"1093", + "code":"1177", "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", @@ -20025,7 +21456,7 @@ "uri":"mrs_01_0255.html", "node_id":"mrs_01_0255.xml", "product_code":"mrs", - "code":"1094", + "code":"1178", "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", @@ -20044,7 +21475,7 @@ "uri":"mrs_01_0256.html", "node_id":"mrs_01_0256.xml", "product_code":"mrs", - "code":"1095", + "code":"1179", "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", @@ -20063,7 +21494,7 @@ "uri":"mrs_01_0258.html", "node_id":"mrs_01_0258.xml", "product_code":"mrs", - "code":"1096", + "code":"1180", "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", @@ -20082,7 +21513,7 @@ "uri":"mrs_01_0259.html", "node_id":"mrs_01_0259.xml", "product_code":"mrs", - "code":"1097", + "code":"1181", "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", @@ -20101,7 +21532,7 @@ "uri":"mrs_01_0260.html", "node_id":"mrs_01_0260.xml", "product_code":"mrs", - "code":"1098", + "code":"1182", "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", @@ -20120,7 +21551,7 @@ "uri":"mrs_01_0264.html", "node_id":"mrs_01_0264.xml", "product_code":"mrs", - "code":"1099", + "code":"1183", "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", @@ -20139,7 +21570,7 @@ "uri":"mrs_01_1226.html", "node_id":"mrs_01_1226.xml", "product_code":"mrs", - "code":"1100", + "code":"1184", "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", @@ -20159,7 +21590,7 @@ "uri":"mrs_01_1227.html", "node_id":"mrs_01_1227.xml", "product_code":"mrs", - "code":"1101", + "code":"1185", "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", @@ -20177,7 +21608,7 @@ "uri":"mrs_01_0265.html", "node_id":"mrs_01_0265.xml", "product_code":"mrs", - "code":"1102", + "code":"1186", "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", @@ -20197,7 +21628,7 @@ "uri":"mrs_01_0267.html", "node_id":"mrs_01_0267.xml", "product_code":"mrs", - "code":"1103", + "code":"1187", "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", @@ -20216,7 +21647,7 @@ "uri":"mrs_01_0270.html", "node_id":"mrs_01_0270.xml", "product_code":"mrs", - "code":"1104", + "code":"1188", "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", @@ -20236,7 +21667,7 @@ "uri":"mrs_01_0271.html", "node_id":"mrs_01_0271.xml", "product_code":"mrs", - "code":"1105", + "code":"1189", "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", @@ -20255,7 +21686,7 @@ "uri":"mrs_01_0274.html", "node_id":"mrs_01_0274.xml", "product_code":"mrs", - "code":"1106", + "code":"1190", "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", @@ -20275,7 +21706,7 @@ "uri":"mrs_01_0275.html", "node_id":"mrs_01_0275.xml", "product_code":"mrs", - "code":"1107", + "code":"1191", "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", @@ -20294,7 +21725,7 @@ "uri":"mrs_01_0277.html", "node_id":"mrs_01_0277.xml", "product_code":"mrs", - "code":"1108", + "code":"1192", "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", @@ -20313,7 +21744,7 @@ "uri":"mrs_01_0278.html", "node_id":"mrs_01_0278.xml", "product_code":"mrs", - "code":"1109", + "code":"1193", "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", @@ -20332,7 +21763,7 @@ "uri":"mrs_01_0279.html", "node_id":"mrs_01_0279.xml", "product_code":"mrs", - "code":"1110", + "code":"1194", "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", @@ -20351,7 +21782,7 @@ "uri":"mrs_01_0280.html", "node_id":"mrs_01_0280.xml", "product_code":"mrs", - "code":"1111", + "code":"1195", "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", @@ -20370,7 +21801,7 @@ "uri":"mrs_01_0281.html", "node_id":"mrs_01_0281.xml", "product_code":"mrs", - "code":"1112", + "code":"1196", "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", @@ -20389,7 +21820,7 @@ "uri":"mrs_01_0282.html", "node_id":"mrs_01_0282.xml", "product_code":"mrs", - "code":"1113", + "code":"1197", "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", @@ -20408,7 +21839,7 @@ "uri":"mrs_01_0284.html", "node_id":"mrs_01_0284.xml", "product_code":"mrs", - "code":"1114", + "code":"1198", "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", @@ -20427,7 +21858,7 @@ "uri":"mrs_01_0285.html", "node_id":"mrs_01_0285.xml", "product_code":"mrs", - "code":"1115", + "code":"1199", "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", @@ -20446,7 +21877,7 @@ "uri":"mrs_01_0288.html", "node_id":"mrs_01_0288.xml", "product_code":"mrs", - "code":"1116", + "code":"1200", "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", @@ -20465,7 +21896,7 @@ "uri":"mrs_01_0289.html", "node_id":"mrs_01_0289.xml", "product_code":"mrs", - "code":"1117", + "code":"1201", "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", @@ -20484,7 +21915,7 @@ "uri":"mrs_01_0291.html", "node_id":"mrs_01_0291.xml", "product_code":"mrs", - "code":"1118", + "code":"1202", "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", @@ -20503,7 +21934,7 @@ "uri":"mrs_01_0292.html", "node_id":"mrs_01_0292.xml", "product_code":"mrs", - "code":"1119", + "code":"1203", "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", @@ -20522,7 +21953,7 @@ "uri":"mrs_01_0293.html", "node_id":"mrs_01_0293.xml", "product_code":"mrs", - "code":"1120", + "code":"1204", "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", @@ -20541,7 +21972,7 @@ "uri":"mrs_01_0294.html", "node_id":"mrs_01_0294.xml", "product_code":"mrs", - "code":"1121", + "code":"1205", "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", @@ -20561,7 +21992,7 @@ "uri":"mrs_01_0530.html", "node_id":"mrs_01_0530.xml", "product_code":"mrs", - "code":"1122", + "code":"1206", "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", @@ -20580,7 +22011,7 @@ "uri":"mrs_01_0531.html", "node_id":"mrs_01_0531.xml", "product_code":"mrs", - "code":"1123", + "code":"1207", "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", @@ -20599,7 +22030,7 @@ "uri":"mrs_01_0532.html", "node_id":"mrs_01_0532.xml", "product_code":"mrs", - "code":"1124", + "code":"1208", "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", @@ -20618,7 +22049,7 @@ "uri":"mrs_01_0533.html", "node_id":"mrs_01_0533.xml", "product_code":"mrs", - "code":"1125", + "code":"1209", "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", @@ -20637,7 +22068,7 @@ "uri":"mrs_01_0534.html", "node_id":"mrs_01_0534.xml", "product_code":"mrs", - "code":"1126", + "code":"1210", "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", @@ -20656,7 +22087,7 @@ "uri":"mrs_01_0535.html", "node_id":"mrs_01_0535.xml", "product_code":"mrs", - "code":"1127", + "code":"1211", "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", @@ -20674,7 +22105,7 @@ "uri":"mrs_01_0536.html", "node_id":"mrs_01_0536.xml", "product_code":"mrs", - "code":"1128", + "code":"1212", "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", @@ -20694,7 +22125,7 @@ "uri":"mrs_01_0537.html", "node_id":"mrs_01_0537.xml", "product_code":"mrs", - "code":"1129", + "code":"1213", "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", @@ -20713,7 +22144,7 @@ "uri":"mrs_01_0538.html", "node_id":"mrs_01_0538.xml", "product_code":"mrs", - "code":"1130", + "code":"1214", "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", @@ -20732,7 +22163,7 @@ "uri":"mrs_01_0539.html", "node_id":"mrs_01_0539.xml", "product_code":"mrs", - "code":"1131", + "code":"1215", "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", @@ -20751,7 +22182,7 @@ "uri":"mrs_01_0540.html", "node_id":"mrs_01_0540.xml", "product_code":"mrs", - "code":"1132", + "code":"1216", "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", @@ -20770,7 +22201,7 @@ "uri":"mrs_01_0541.html", "node_id":"mrs_01_0541.xml", "product_code":"mrs", - "code":"1133", + "code":"1217", "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", @@ -20789,7 +22220,7 @@ "uri":"mrs_01_0542.html", "node_id":"mrs_01_0542.xml", "product_code":"mrs", - "code":"1134", + "code":"1218", "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", @@ -20808,7 +22239,7 @@ "uri":"mrs_01_0543.html", "node_id":"mrs_01_0543.xml", "product_code":"mrs", - "code":"1135", + "code":"1219", "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", @@ -20827,7 +22258,7 @@ "uri":"mrs_01_0544.html", "node_id":"mrs_01_0544.xml", "product_code":"mrs", - "code":"1136", + "code":"1220", "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", @@ -20846,7 +22277,7 @@ "uri":"mrs_01_0545.html", "node_id":"mrs_01_0545.xml", "product_code":"mrs", - "code":"1137", + "code":"1221", "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", @@ -20865,7 +22296,7 @@ "uri":"mrs_01_0546.html", "node_id":"mrs_01_0546.xml", "product_code":"mrs", - "code":"1138", + "code":"1222", "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", @@ -20884,7 +22315,7 @@ "uri":"mrs_01_0547.html", "node_id":"mrs_01_0547.xml", "product_code":"mrs", - "code":"1139", + "code":"1223", "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", @@ -20903,7 +22334,7 @@ "uri":"mrs_01_0548.html", "node_id":"mrs_01_0548.xml", "product_code":"mrs", - "code":"1140", + "code":"1224", "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", @@ -20922,7 +22353,7 @@ "uri":"mrs_01_0549.html", "node_id":"mrs_01_0549.xml", "product_code":"mrs", - "code":"1141", + "code":"1225", "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", @@ -20941,7 +22372,7 @@ "uri":"mrs_01_0550.html", "node_id":"mrs_01_0550.xml", "product_code":"mrs", - "code":"1142", + "code":"1226", "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", @@ -20960,7 +22391,7 @@ "uri":"mrs_01_0551.html", "node_id":"mrs_01_0551.xml", "product_code":"mrs", - "code":"1143", + "code":"1227", "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", @@ -20979,7 +22410,7 @@ "uri":"mrs_01_0553.html", "node_id":"mrs_01_0553.xml", "product_code":"mrs", - "code":"1144", + "code":"1228", "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", @@ -20998,7 +22429,7 @@ "uri":"mrs_01_0555.html", "node_id":"mrs_01_0555.xml", "product_code":"mrs", - "code":"1145", + "code":"1229", "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", @@ -21017,7 +22448,7 @@ "uri":"mrs_01_0558.html", "node_id":"mrs_01_0558.xml", "product_code":"mrs", - "code":"1146", + "code":"1230", "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", @@ -21036,7 +22467,7 @@ "uri":"mrs_01_0559.html", "node_id":"mrs_01_0559.xml", "product_code":"mrs", - "code":"1147", + "code":"1231", "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", @@ -21055,7 +22486,7 @@ "uri":"mrs_01_0560.html", "node_id":"mrs_01_0560.xml", "product_code":"mrs", - "code":"1148", + "code":"1232", "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", @@ -21074,7 +22505,7 @@ "uri":"mrs_01_0561.html", "node_id":"mrs_01_0561.xml", "product_code":"mrs", - "code":"1149", + "code":"1233", "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", @@ -21094,7 +22525,7 @@ "uri":"mrs_01_24044.html", "node_id":"mrs_01_24044.xml", "product_code":"mrs", - "code":"1150", + "code":"1234", "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", @@ -21113,7 +22544,7 @@ "uri":"mrs_01_0562.html", "node_id":"mrs_01_0562.xml", "product_code":"mrs", - "code":"1151", + "code":"1235", "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", @@ -21132,7 +22563,7 @@ "uri":"mrs_01_0563.html", "node_id":"mrs_01_0563.xml", "product_code":"mrs", - "code":"1152", + "code":"1236", "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", @@ -21152,7 +22583,7 @@ "uri":"mrs_01_0564.html", "node_id":"mrs_01_0564.xml", "product_code":"mrs", - "code":"1153", + "code":"1237", "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", @@ -21172,7 +22603,7 @@ "uri":"mrs_01_0565.html", "node_id":"mrs_01_0565.xml", "product_code":"mrs", - "code":"1154", + "code":"1238", "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", @@ -21191,7 +22622,7 @@ "uri":"mrs_01_0566.html", "node_id":"mrs_01_0566.xml", "product_code":"mrs", - "code":"1155", + "code":"1239", "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", @@ -21211,7 +22642,7 @@ "uri":"mrs_01_0567.html", "node_id":"mrs_01_0567.xml", "product_code":"mrs", - "code":"1156", + "code":"1240", "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", @@ -21230,7 +22661,7 @@ "uri":"mrs_01_0568.html", "node_id":"mrs_01_0568.xml", "product_code":"mrs", - "code":"1157", + "code":"1241", "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", @@ -21249,7 +22680,7 @@ "uri":"mrs_01_0569.html", "node_id":"mrs_01_0569.xml", "product_code":"mrs", - "code":"1158", + "code":"1242", "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", @@ -21269,7 +22700,7 @@ "uri":"mrs_01_0571.html", "node_id":"mrs_01_0571.xml", "product_code":"mrs", - "code":"1159", + "code":"1243", "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", @@ -21289,7 +22720,7 @@ "uri":"mrs_01_0572.html", "node_id":"mrs_01_0572.xml", "product_code":"mrs", - "code":"1160", + "code":"1244", "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", @@ -21308,7 +22739,7 @@ "uri":"mrs_01_0573.html", "node_id":"mrs_01_0573.xml", "product_code":"mrs", - "code":"1161", + "code":"1245", "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", @@ -21327,7 +22758,7 @@ "uri":"mrs_01_0420.html", "node_id":"mrs_01_0420.xml", "product_code":"mrs", - "code":"1162", + "code":"1246", "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", @@ -21346,7 +22777,7 @@ "uri":"mrs_01_0421.html", "node_id":"mrs_01_0421.xml", "product_code":"mrs", - "code":"1163", + "code":"1247", "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", @@ -21365,7 +22796,7 @@ "uri":"mrs_01_0422.html", "node_id":"mrs_01_0422.xml", "product_code":"mrs", - "code":"1164", + "code":"1248", "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", @@ -21384,7 +22815,7 @@ "uri":"mrs_01_0423.html", "node_id":"mrs_01_0423.xml", "product_code":"mrs", - "code":"1165", + "code":"1249", "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", @@ -21403,7 +22834,7 @@ "uri":"mrs_01_0424.html", "node_id":"mrs_01_0424.xml", "product_code":"mrs", - "code":"1166", + "code":"1250", "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", @@ -21422,7 +22853,7 @@ "uri":"mrs_01_0425.html", "node_id":"mrs_01_0425.xml", "product_code":"mrs", - "code":"1167", + "code":"1251", "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", @@ -21441,7 +22872,7 @@ "uri":"mrs_01_0426.html", "node_id":"mrs_01_0426.xml", "product_code":"mrs", - "code":"1168", + "code":"1252", "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", @@ -21460,7 +22891,7 @@ "uri":"mrs_01_0427.html", "node_id":"mrs_01_0427.xml", "product_code":"mrs", - "code":"1169", + "code":"1253", "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", @@ -21480,7 +22911,7 @@ "uri":"mrs_01_0428.html", "node_id":"mrs_01_0428.xml", "product_code":"mrs", - "code":"1170", + "code":"1254", "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", @@ -21500,7 +22931,7 @@ "uri":"mrs_01_0429.html", "node_id":"mrs_01_0429.xml", "product_code":"mrs", - "code":"1171", + "code":"1255", "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", @@ -21519,7 +22950,7 @@ "uri":"mrs_01_0430.html", "node_id":"mrs_01_0430.xml", "product_code":"mrs", - "code":"1172", + "code":"1256", "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", @@ -21538,7 +22969,7 @@ "uri":"mrs_01_0340.html", "node_id":"mrs_01_0340.xml", "product_code":"mrs", - "code":"1173", + "code":"1257", "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", @@ -21557,7 +22988,7 @@ "uri":"mrs_01_0341.html", "node_id":"mrs_01_0341.xml", "product_code":"mrs", - "code":"1174", + "code":"1258", "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", @@ -21577,7 +23008,7 @@ "uri":"mrs_01_0342.html", "node_id":"mrs_01_0342.xml", "product_code":"mrs", - "code":"1175", + "code":"1259", "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,", @@ -21596,7 +23027,7 @@ "uri":"mrs_01_0343.html", "node_id":"mrs_01_0343.xml", "product_code":"mrs", - "code":"1176", + "code":"1260", "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", @@ -21616,7 +23047,7 @@ "uri":"mrs_01_0344.html", "node_id":"mrs_01_0344.xml", "product_code":"mrs", - "code":"1177", + "code":"1261", "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", @@ -21636,7 +23067,7 @@ "uri":"mrs_01_0345.html", "node_id":"mrs_01_0345.xml", "product_code":"mrs", - "code":"1178", + "code":"1262", "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", @@ -21656,7 +23087,7 @@ "uri":"mrs_01_0346.html", "node_id":"mrs_01_0346.xml", "product_code":"mrs", - "code":"1179", + "code":"1263", "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", @@ -21676,7 +23107,7 @@ "uri":"mrs_01_0347.html", "node_id":"mrs_01_0347.xml", "product_code":"mrs", - "code":"1180", + "code":"1264", "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", @@ -21696,7 +23127,7 @@ "uri":"mrs_01_0348.html", "node_id":"mrs_01_0348.xml", "product_code":"mrs", - "code":"1181", + "code":"1265", "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", @@ -21716,7 +23147,7 @@ "uri":"mrs_01_0349.html", "node_id":"mrs_01_0349.xml", "product_code":"mrs", - "code":"1182", + "code":"1266", "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", @@ -21736,7 +23167,7 @@ "uri":"mrs_01_0350.html", "node_id":"mrs_01_0350.xml", "product_code":"mrs", - "code":"1183", + "code":"1267", "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", @@ -21756,7 +23187,7 @@ "uri":"mrs_01_0351.html", "node_id":"mrs_01_0351.xml", "product_code":"mrs", - "code":"1184", + "code":"1268", "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", @@ -21776,7 +23207,7 @@ "uri":"mrs_01_0352.html", "node_id":"mrs_01_0352.xml", "product_code":"mrs", - "code":"1185", + "code":"1269", "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", @@ -21796,7 +23227,7 @@ "uri":"mrs_01_0353.html", "node_id":"mrs_01_0353.xml", "product_code":"mrs", - "code":"1186", + "code":"1270", "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", @@ -21816,7 +23247,7 @@ "uri":"mrs_01_0354.html", "node_id":"mrs_01_0354.xml", "product_code":"mrs", - "code":"1187", + "code":"1271", "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", @@ -21836,7 +23267,7 @@ "uri":"mrs_01_0355.html", "node_id":"mrs_01_0355.xml", "product_code":"mrs", - "code":"1188", + "code":"1272", "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", @@ -21856,7 +23287,7 @@ "uri":"mrs_01_0574.html", "node_id":"mrs_01_0574.xml", "product_code":"mrs", - "code":"1189", + "code":"1273", "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", @@ -21875,7 +23306,7 @@ "uri":"mrs_01_0575.html", "node_id":"mrs_01_0575.xml", "product_code":"mrs", - "code":"1190", + "code":"1274", "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", @@ -21895,7 +23326,7 @@ "uri":"mrs_01_0576.html", "node_id":"mrs_01_0576.xml", "product_code":"mrs", - "code":"1191", + "code":"1275", "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":"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", @@ -21914,7 +23345,7 @@ "uri":"mrs_01_0577.html", "node_id":"mrs_01_0577.xml", "product_code":"mrs", - "code":"1192", + "code":"1276", "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", @@ -21933,7 +23364,7 @@ "uri":"mrs_01_0578.html", "node_id":"mrs_01_0578.xml", "product_code":"mrs", - "code":"1193", + "code":"1277", "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 ", @@ -21952,7 +23383,7 @@ "uri":"mrs_01_0579.html", "node_id":"mrs_01_0579.xml", "product_code":"mrs", - "code":"1194", + "code":"1278", "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", @@ -21971,7 +23402,7 @@ "uri":"mrs_01_0528.html", "node_id":"mrs_01_0528.xml", "product_code":"mrs", - "code":"1195", + "code":"1279", "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", @@ -21991,7 +23422,7 @@ "uri":"mrs_01_0419.html", "node_id":"mrs_01_0419.xml", "product_code":"mrs", - "code":"1196", + "code":"1280", "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", @@ -22010,7 +23441,7 @@ "uri":"mrs_07_020001.html", "node_id":"mrs_07_020001.xml", "product_code":"mrs", - "code":"1197", + "code":"1281", "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", @@ -22028,7 +23459,7 @@ "uri":"mrs_01_0785.html", "node_id":"mrs_01_0785.xml", "product_code":"mrs", - "code":"1198", + "code":"1282", "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", @@ -22046,7 +23477,7 @@ "uri":"mrs_01_0316.html", "node_id":"mrs_01_0316.xml", "product_code":"mrs", - "code":"1199", + "code":"1283", "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", @@ -22065,7 +23496,7 @@ "uri":"mrs_01_0605.html", "node_id":"mrs_01_0605.xml", "product_code":"mrs", - "code":"1200", + "code":"1284", "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", @@ -22085,7 +23516,7 @@ "uri":"mrs_01_0317.html", "node_id":"mrs_01_0317.xml", "product_code":"mrs", - "code":"1201", + "code":"1285", "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", @@ -22104,7 +23535,7 @@ "uri":"mrs_01_0319.html", "node_id":"mrs_01_0319.xml", "product_code":"mrs", - "code":"1202", + "code":"1286", "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", @@ -22124,7 +23555,7 @@ "uri":"mrs_01_0321.html", "node_id":"mrs_01_0321.xml", "product_code":"mrs", - "code":"1203", + "code":"1287", "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", @@ -22144,7 +23575,7 @@ "uri":"mrs_01_0324.html", "node_id":"mrs_01_0324.xml", "product_code":"mrs", - "code":"1204", + "code":"1288", "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", @@ -22164,7 +23595,7 @@ "uri":"mrs_01_0325.html", "node_id":"mrs_01_0325.xml", "product_code":"mrs", - "code":"1205", + "code":"1289", "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", @@ -22184,7 +23615,7 @@ "uri":"mrs_01_0444.html", "node_id":"mrs_01_0444.xml", "product_code":"mrs", - "code":"1206", + "code":"1290", "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", @@ -22202,7 +23633,7 @@ "uri":"mrs_01_0445.html", "node_id":"mrs_01_0445.xml", "product_code":"mrs", - "code":"1207", + "code":"1291", "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", @@ -22222,7 +23653,7 @@ "uri":"mrs_01_0446.html", "node_id":"mrs_01_0446.xml", "product_code":"mrs", - "code":"1208", + "code":"1292", "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", @@ -22241,7 +23672,7 @@ "uri":"mrs_01_0447.html", "node_id":"mrs_01_0447.xml", "product_code":"mrs", - "code":"1209", + "code":"1293", "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", @@ -22260,7 +23691,7 @@ "uri":"mrs_01_0448.html", "node_id":"mrs_01_0448.xml", "product_code":"mrs", - "code":"1210", + "code":"1294", "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", @@ -22280,7 +23711,7 @@ "uri":"mrs_01_0449.html", "node_id":"mrs_01_0449.xml", "product_code":"mrs", - "code":"1211", + "code":"1295", "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", @@ -22300,7 +23731,7 @@ "uri":"mrs_01_9002.html", "node_id":"mrs_01_9002.xml", "product_code":"mrs", - "code":"1212", + "code":"1296", "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", @@ -22318,7 +23749,7 @@ "uri":"mrs_01_0614.html", "node_id":"mrs_01_0614.xml", "product_code":"mrs", - "code":"1213", + "code":"1297", "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", @@ -22336,7 +23767,7 @@ "uri":"mrs_01_0392.html", "node_id":"mrs_01_0392.xml", "product_code":"mrs", - "code":"1214", + "code":"1298", "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", @@ -22354,7 +23785,7 @@ "uri":"mrs_01_1594.html", "node_id":"mrs_01_1594.xml", "product_code":"mrs", - "code":"1215", + "code":"1299", "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", @@ -22372,7 +23803,7 @@ "uri":"mrs_01_1595.html", "node_id":"mrs_01_1595.xml", "product_code":"mrs", - "code":"1216", + "code":"1300", "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", @@ -22390,7 +23821,7 @@ "uri":"en-us_topic_0000001349287889.html", "node_id":"en-us_topic_0000001349287889.xml", "product_code":"mrs", - "code":"1217", + "code":"1301", "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", @@ -22408,7 +23839,7 @@ "uri":"mrs_03_0002.html", "node_id":"mrs_03_0002.xml", "product_code":"mrs", - "code":"1218", + "code":"1302", "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", @@ -22426,7 +23857,7 @@ "uri":"mrs_03_0001.html", "node_id":"mrs_03_0001.xml", "product_code":"mrs", - "code":"1219", + "code":"1303", "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", @@ -22445,7 +23876,7 @@ "uri":"mrs_03_1012.html", "node_id":"mrs_03_1012.xml", "product_code":"mrs", - "code":"1220", + "code":"1304", "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", @@ -22463,7 +23894,7 @@ "uri":"mrs_03_1013.html", "node_id":"mrs_03_1013.xml", "product_code":"mrs", - "code":"1221", + "code":"1305", "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", @@ -22482,7 +23913,7 @@ "uri":"mrs_03_1105.html", "node_id":"mrs_03_1105.xml", "product_code":"mrs", - "code":"1222", + "code":"1306", "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", @@ -22501,7 +23932,7 @@ "uri":"mrs_03_1019.html", "node_id":"mrs_03_1019.xml", "product_code":"mrs", - "code":"1223", + "code":"1307", "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", @@ -22519,7 +23950,7 @@ "uri":"mrs_03_1125.html", "node_id":"mrs_03_1125.xml", "product_code":"mrs", - "code":"1224", + "code":"1308", "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", @@ -22537,7 +23968,7 @@ "uri":"mrs_03_1046.html", "node_id":"mrs_03_1046.xml", "product_code":"mrs", - "code":"1225", + "code":"1309", "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", @@ -22555,7 +23986,7 @@ "uri":"mrs_03_1048.html", "node_id":"mrs_03_1048.xml", "product_code":"mrs", - "code":"1226", + "code":"1310", "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", @@ -22574,7 +24005,7 @@ "uri":"mrs_03_1081.html", "node_id":"mrs_03_1081.xml", "product_code":"mrs", - "code":"1227", + "code":"1311", "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", @@ -22592,7 +24023,7 @@ "uri":"mrs_03_1095.html", "node_id":"mrs_03_1095.xml", "product_code":"mrs", - "code":"1228", + "code":"1312", "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", @@ -22610,7 +24041,7 @@ "uri":"mrs_03_1062.html", "node_id":"mrs_03_1062.xml", "product_code":"mrs", - "code":"1229", + "code":"1313", "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", @@ -22628,7 +24059,7 @@ "uri":"mrs_03_1092.html", "node_id":"mrs_03_1092.xml", "product_code":"mrs", - "code":"1230", + "code":"1314", "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", @@ -22646,7 +24077,7 @@ "uri":"mrs_03_1065.html", "node_id":"mrs_03_1065.xml", "product_code":"mrs", - "code":"1231", + "code":"1315", "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", @@ -22664,7 +24095,7 @@ "uri":"mrs_03_2022.html", "node_id":"mrs_03_2022.xml", "product_code":"mrs", - "code":"1232", + "code":"1316", "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", @@ -22683,7 +24114,7 @@ "uri":"mrs_03_1066.html", "node_id":"mrs_03_1066.xml", "product_code":"mrs", - "code":"1233", + "code":"1317", "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", @@ -22701,7 +24132,7 @@ "uri":"mrs_03_1068.html", "node_id":"mrs_03_1068.xml", "product_code":"mrs", - "code":"1234", + "code":"1318", "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", @@ -22719,7 +24150,7 @@ "uri":"mrs_03_1133.html", "node_id":"mrs_03_1133.xml", "product_code":"mrs", - "code":"1235", + "code":"1319", "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", @@ -22737,7 +24168,7 @@ "uri":"mrs_03_1137.html", "node_id":"mrs_03_1137.xml", "product_code":"mrs", - "code":"1236", + "code":"1320", "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", @@ -22755,7 +24186,7 @@ "uri":"mrs_03_1155.html", "node_id":"mrs_03_1155.xml", "product_code":"mrs", - "code":"1237", + "code":"1321", "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", @@ -22773,7 +24204,7 @@ "uri":"en-us_topic_0000001442653893.html", "node_id":"en-us_topic_0000001442653893.xml", "product_code":"mrs", - "code":"1238", + "code":"1322", "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", @@ -22791,7 +24222,7 @@ "uri":"en-us_topic_0000001442773925.html", "node_id":"en-us_topic_0000001442773925.xml", "product_code":"mrs", - "code":"1239", + "code":"1323", "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", @@ -22809,7 +24240,7 @@ "uri":"en-us_topic_0000001442494337.html", "node_id":"en-us_topic_0000001442494337.xml", "product_code":"mrs", - "code":"1240", + "code":"1324", "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", @@ -22827,7 +24258,7 @@ "uri":"en-us_topic_0000001392255170.html", "node_id":"en-us_topic_0000001392255170.xml", "product_code":"mrs", - "code":"1241", + "code":"1325", "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", @@ -22845,7 +24276,7 @@ "uri":"mrs_03_1202.html", "node_id":"mrs_03_1202.xml", "product_code":"mrs", - "code":"1242", + "code":"1326", "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", @@ -22864,7 +24295,7 @@ "uri":"mrs_03_1204.html", "node_id":"mrs_03_1204.xml", "product_code":"mrs", - "code":"1243", + "code":"1327", "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", @@ -22883,7 +24314,7 @@ "uri":"mrs_03_1216.html", "node_id":"mrs_03_1216.xml", "product_code":"mrs", - "code":"1244", + "code":"1328", "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", @@ -22901,7 +24332,7 @@ "uri":"mrs_03_1221.html", "node_id":"mrs_03_1221.xml", "product_code":"mrs", - "code":"1245", + "code":"1329", "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", @@ -22919,7 +24350,7 @@ "uri":"mrs_03_1233.html", "node_id":"mrs_03_1233.xml", "product_code":"mrs", - "code":"1246", + "code":"1330", "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", @@ -22937,7 +24368,7 @@ "uri":"mrs_03_1246.html", "node_id":"mrs_03_1246.xml", "product_code":"mrs", - "code":"1247", + "code":"1331", "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", @@ -22955,7 +24386,7 @@ "uri":"mrs_03_2003.html", "node_id":"mrs_03_2003.xml", "product_code":"mrs", - "code":"1248", + "code":"1332", "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", @@ -22973,7 +24404,7 @@ "uri":"mrs_03_1027.html", "node_id":"mrs_03_1027.xml", "product_code":"mrs", - "code":"1249", + "code":"1333", "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", @@ -22991,7 +24422,7 @@ "uri":"mrs_03_1249.html", "node_id":"mrs_03_1249.xml", "product_code":"mrs", - "code":"1250", + "code":"1334", "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", @@ -23009,7 +24440,7 @@ "uri":"mrs_03_2004.html", "node_id":"mrs_03_2004.xml", "product_code":"mrs", - "code":"1251", + "code":"1335", "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", @@ -23027,7 +24458,7 @@ "uri":"mrs_03_1020.html", "node_id":"mrs_03_1020.xml", "product_code":"mrs", - "code":"1252", + "code":"1336", "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", @@ -23046,7 +24477,7 @@ "uri":"mrs_03_1035.html", "node_id":"mrs_03_1035.xml", "product_code":"mrs", - "code":"1253", + "code":"1337", "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", @@ -23064,7 +24495,7 @@ "uri":"mrs_03_1118.html", "node_id":"mrs_03_1118.xml", "product_code":"mrs", - "code":"1254", + "code":"1338", "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", @@ -23083,7 +24514,7 @@ "uri":"mrs_03_1037.html", "node_id":"mrs_03_1037.xml", "product_code":"mrs", - "code":"1255", + "code":"1339", "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", @@ -23101,7 +24532,7 @@ "uri":"mrs_03_1121.html", "node_id":"mrs_03_1121.xml", "product_code":"mrs", - "code":"1256", + "code":"1340", "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", @@ -23119,7 +24550,7 @@ "uri":"mrs_03_2005.html", "node_id":"mrs_03_2005.xml", "product_code":"mrs", - "code":"1257", + "code":"1341", "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", @@ -23137,7 +24568,7 @@ "uri":"mrs_03_1031.html", "node_id":"mrs_03_1031.xml", "product_code":"mrs", - "code":"1258", + "code":"1342", "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", @@ -23155,7 +24586,7 @@ "uri":"mrs_03_1219.html", "node_id":"mrs_03_1219.xml", "product_code":"mrs", - "code":"1259", + "code":"1343", "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", @@ -23173,7 +24604,7 @@ "uri":"mrs_03_1251.html", "node_id":"mrs_03_1251.xml", "product_code":"mrs", - "code":"1260", + "code":"1344", "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", @@ -23191,7 +24622,7 @@ "uri":"mrs_03_2006.html", "node_id":"mrs_03_2006.xml", "product_code":"mrs", - "code":"1261", + "code":"1345", "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", @@ -23209,7 +24640,7 @@ "uri":"mrs_03_1151.html", "node_id":"mrs_03_1151.xml", "product_code":"mrs", - "code":"1262", + "code":"1346", "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", @@ -23228,7 +24659,7 @@ "uri":"mrs_03_1156.html", "node_id":"mrs_03_1156.xml", "product_code":"mrs", - "code":"1263", + "code":"1347", "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", @@ -23246,7 +24677,7 @@ "uri":"mrs_03_1166.html", "node_id":"mrs_03_1166.xml", "product_code":"mrs", - "code":"1264", + "code":"1348", "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", @@ -23264,7 +24695,7 @@ "uri":"mrs_03_2007.html", "node_id":"mrs_03_2007.xml", "product_code":"mrs", - "code":"1265", + "code":"1349", "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", @@ -23282,7 +24713,7 @@ "uri":"mrs_03_1055.html", "node_id":"mrs_03_1055.xml", "product_code":"mrs", - "code":"1266", + "code":"1350", "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", @@ -23300,7 +24731,7 @@ "uri":"mrs_03_1222.html", "node_id":"mrs_03_1222.xml", "product_code":"mrs", - "code":"1267", + "code":"1351", "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", @@ -23318,7 +24749,7 @@ "uri":"mrs_03_1243.html", "node_id":"mrs_03_1243.xml", "product_code":"mrs", - "code":"1268", + "code":"1352", "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", @@ -23336,7 +24767,7 @@ "uri":"mrs_03_2008.html", "node_id":"mrs_03_2008.xml", "product_code":"mrs", - "code":"1269", + "code":"1353", "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", @@ -23354,7 +24785,7 @@ "uri":"mrs_03_1017.html", "node_id":"mrs_03_1017.xml", "product_code":"mrs", - "code":"1270", + "code":"1354", "des":"An MRS cluster does not support system reinstallation.", "doc_type":"faq", "kw":"Does an MRS Cluster Support System Reinstallation?,Performance Tuning,User Guide", @@ -23372,7 +24803,7 @@ "uri":"mrs_03_1203.html", "node_id":"mrs_03_1203.xml", "product_code":"mrs", - "code":"1271", + "code":"1355", "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", @@ -23391,7 +24822,7 @@ "uri":"mrs_03_1090.html", "node_id":"mrs_03_1090.xml", "product_code":"mrs", - "code":"1272", + "code":"1356", "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", @@ -23410,7 +24841,7 @@ "uri":"mrs_03_1072.html", "node_id":"mrs_03_1072.xml", "product_code":"mrs", - "code":"1273", + "code":"1357", "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", @@ -23428,7 +24859,7 @@ "uri":"mrs_03_2009.html", "node_id":"mrs_03_2009.xml", "product_code":"mrs", - "code":"1274", + "code":"1358", "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", @@ -23446,7 +24877,7 @@ "uri":"mrs_03_1015.html", "node_id":"mrs_03_1015.xml", "product_code":"mrs", - "code":"1275", + "code":"1359", "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", @@ -23464,7 +24895,7 @@ "uri":"mrs_03_1050.html", "node_id":"mrs_03_1050.xml", "product_code":"mrs", - "code":"1276", + "code":"1360", "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", @@ -23482,7 +24913,7 @@ "uri":"mrs_03_1052.html", "node_id":"mrs_03_1052.xml", "product_code":"mrs", - "code":"1277", + "code":"1361", "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", @@ -23500,7 +24931,7 @@ "uri":"en-us_topic_0000001392574214.html", "node_id":"en-us_topic_0000001392574214.xml", "product_code":"mrs", - "code":"1278", + "code":"1362", "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", @@ -23518,7 +24949,7 @@ "uri":"mrs_03_1173.html", "node_id":"mrs_03_1173.xml", "product_code":"mrs", - "code":"1279", + "code":"1363", "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", @@ -23537,7 +24968,7 @@ "uri":"mrs_03_1174.html", "node_id":"mrs_03_1174.xml", "product_code":"mrs", - "code":"1280", + "code":"1364", "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", @@ -23555,7 +24986,7 @@ "uri":"mrs_03_1175.html", "node_id":"mrs_03_1175.xml", "product_code":"mrs", - "code":"1281", + "code":"1365", "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", @@ -23573,7 +25004,7 @@ "uri":"mrs_03_1176.html", "node_id":"mrs_03_1176.xml", "product_code":"mrs", - "code":"1282", + "code":"1366", "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", @@ -23591,7 +25022,7 @@ "uri":"mrs_03_1201.html", "node_id":"mrs_03_1201.xml", "product_code":"mrs", - "code":"1283", + "code":"1367", "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 ", @@ -23610,7 +25041,7 @@ "uri":"mrs_03_1205.html", "node_id":"mrs_03_1205.xml", "product_code":"mrs", - "code":"1284", + "code":"1368", "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", @@ -23629,7 +25060,7 @@ "uri":"mrs_03_1207.html", "node_id":"mrs_03_1207.xml", "product_code":"mrs", - "code":"1285", + "code":"1369", "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 ", @@ -23648,7 +25079,7 @@ "uri":"mrs_03_1208.html", "node_id":"mrs_03_1208.xml", "product_code":"mrs", - "code":"1286", + "code":"1370", "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", @@ -23667,7 +25098,7 @@ "uri":"mrs_03_1215.html", "node_id":"mrs_03_1215.xml", "product_code":"mrs", - "code":"1287", + "code":"1371", "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", @@ -23685,7 +25116,7 @@ "uri":"mrs_03_1223.html", "node_id":"mrs_03_1223.xml", "product_code":"mrs", - "code":"1288", + "code":"1372", "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", @@ -23703,7 +25134,7 @@ "uri":"mrs_03_1224.html", "node_id":"mrs_03_1224.xml", "product_code":"mrs", - "code":"1289", + "code":"1373", "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", @@ -23721,7 +25152,7 @@ "uri":"mrs_03_1229.html", "node_id":"mrs_03_1229.xml", "product_code":"mrs", - "code":"1290", + "code":"1374", "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", @@ -23739,7 +25170,7 @@ "uri":"mrs_03_1237.html", "node_id":"mrs_03_1237.xml", "product_code":"mrs", - "code":"1291", + "code":"1375", "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 ", @@ -23757,7 +25188,7 @@ "uri":"mrs_03_1238.html", "node_id":"mrs_03_1238.xml", "product_code":"mrs", - "code":"1292", + "code":"1376", "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", @@ -23775,7 +25206,7 @@ "uri":"mrs_03_2010.html", "node_id":"mrs_03_2010.xml", "product_code":"mrs", - "code":"1293", + "code":"1377", "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", @@ -23793,7 +25224,7 @@ "uri":"mrs_03_1089.html", "node_id":"mrs_03_1089.xml", "product_code":"mrs", - "code":"1294", + "code":"1378", "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", @@ -23812,7 +25243,7 @@ "uri":"mrs_03_1021.html", "node_id":"mrs_03_1021.xml", "product_code":"mrs", - "code":"1295", + "code":"1379", "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", @@ -23831,7 +25262,7 @@ "uri":"mrs_03_2013.html", "node_id":"mrs_03_2013.xml", "product_code":"mrs", - "code":"1296", + "code":"1380", "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", @@ -23849,7 +25280,7 @@ "uri":"mrs_03_1029.html", "node_id":"mrs_03_1029.xml", "product_code":"mrs", - "code":"1297", + "code":"1381", "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", @@ -23868,7 +25299,7 @@ "uri":"mrs_03_1071.html", "node_id":"mrs_03_1071.xml", "product_code":"mrs", - "code":"1298", + "code":"1382", "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", @@ -23887,7 +25318,7 @@ "uri":"mrs_03_1185.html", "node_id":"mrs_03_1185.xml", "product_code":"mrs", - "code":"1299", + "code":"1383", "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", @@ -23906,7 +25337,7 @@ "uri":"mrs_03_1234.html", "node_id":"mrs_03_1234.xml", "product_code":"mrs", - "code":"1300", + "code":"1384", "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", @@ -23924,7 +25355,7 @@ "uri":"mrs_03_1244.html", "node_id":"mrs_03_1244.xml", "product_code":"", - "code":"1301", + "code":"1385", "des":"You have obtained the account AK and SK. For details, see How Do I Manage Access Keys?Install ICAgent on the MRS node. For details, see Installing ICAgent.For the first i", "doc_type":"", "kw":"How Do I Interconnect MRS with LTS?,Cluster Access,User Guide", @@ -23941,7 +25372,7 @@ "uri":"mrs_03_2014.html", "node_id":"mrs_03_2014.xml", "product_code":"mrs", - "code":"1302", + "code":"1386", "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", @@ -23959,7 +25390,7 @@ "uri":"mrs_03_1059.html", "node_id":"mrs_03_1059.xml", "product_code":"mrs", - "code":"1303", + "code":"1387", "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", @@ -23977,8 +25408,8 @@ "uri":"mrs_03_1058.html", "node_id":"mrs_03_1058.xml", "product_code":"mrs", - "code":"1304", - "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, ", + "code":"1388", + "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, r", "doc_type":"faq", "kw":"How Do I Change FlumeClient Logs to Standard Logs?,Big Data Service Development,User Guide", "search_title":"", @@ -23995,7 +25426,7 @@ "uri":"mrs_03_1064.html", "node_id":"mrs_03_1064.xml", "product_code":"mrs", - "code":"1305", + "code":"1389", "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", @@ -24014,7 +25445,7 @@ "uri":"mrs_03_1042.html", "node_id":"mrs_03_1042.xml", "product_code":"mrs", - "code":"1306", + "code":"1390", "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", @@ -24032,7 +25463,7 @@ "uri":"mrs_03_1044.html", "node_id":"mrs_03_1044.xml", "product_code":"mrs", - "code":"1307", + "code":"1391", "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", @@ -24050,7 +25481,7 @@ "uri":"mrs_03_1045.html", "node_id":"mrs_03_1045.xml", "product_code":"mrs", - "code":"1308", + "code":"1392", "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", @@ -24069,7 +25500,7 @@ "uri":"mrs_03_1140.html", "node_id":"mrs_03_1140.xml", "product_code":"mrs", - "code":"1309", + "code":"1393", "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", @@ -24087,7 +25518,7 @@ "uri":"mrs_03_1113.html", "node_id":"mrs_03_1113.xml", "product_code":"mrs", - "code":"1310", + "code":"1394", "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", @@ -24106,7 +25537,7 @@ "uri":"mrs_03_1061.html", "node_id":"mrs_03_1061.xml", "product_code":"mrs", - "code":"1311", + "code":"1395", "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", @@ -24125,7 +25556,7 @@ "uri":"mrs_03_1060.html", "node_id":"mrs_03_1060.xml", "product_code":"mrs", - "code":"1312", + "code":"1396", "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", @@ -24144,7 +25575,7 @@ "uri":"mrs_03_1196.html", "node_id":"mrs_03_1196.xml", "product_code":"mrs", - "code":"1313", + "code":"1397", "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", @@ -24163,7 +25594,7 @@ "uri":"mrs_03_1047.html", "node_id":"mrs_03_1047.xml", "product_code":"mrs", - "code":"1314", + "code":"1398", "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", @@ -24181,7 +25612,7 @@ "uri":"mrs_03_1049.html", "node_id":"mrs_03_1049.xml", "product_code":"mrs", - "code":"1315", + "code":"1399", "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", @@ -24199,7 +25630,7 @@ "uri":"mrs_03_1082.html", "node_id":"mrs_03_1082.xml", "product_code":"mrs", - "code":"1316", + "code":"1400", "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", @@ -24218,7 +25649,7 @@ "uri":"mrs_03_1149.html", "node_id":"mrs_03_1149.xml", "product_code":"mrs", - "code":"1317", + "code":"1401", "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", @@ -24236,7 +25667,7 @@ "uri":"mrs_03_1194.html", "node_id":"mrs_03_1194.xml", "product_code":"mrs", - "code":"1318", + "code":"1402", "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?", @@ -24255,7 +25686,7 @@ "uri":"mrs_03_1200.html", "node_id":"mrs_03_1200.xml", "product_code":"mrs", - "code":"1319", + "code":"1403", "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", @@ -24274,7 +25705,7 @@ "uri":"mrs_03_1160.html", "node_id":"mrs_03_1160.xml", "product_code":"mrs", - "code":"1320", + "code":"1404", "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", @@ -24293,8 +25724,8 @@ "uri":"mrs_03_1214.html", "node_id":"mrs_03_1214.xml", "product_code":"mrs", - "code":"1321", - "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", + "code":"1405", + "des":"Applicable versions: MRS 3.1.0 and earlierModify the following file on the two Hue nodes:/opt/Bigdata/*_Porter_8.*/install/*-Hue-*/hue/apps/beeswax/src/beeswax/models.py/", "doc_type":"usermanual", "kw":"How Do I Do If Sessions Are Not Released After Hue Connects to HiveServer and the Error Message \"ove", "search_title":"", @@ -24311,7 +25742,7 @@ "uri":"mrs_03_1106.html", "node_id":"mrs_03_1106.xml", "product_code":"mrs", - "code":"1322", + "code":"1406", "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", @@ -24329,7 +25760,7 @@ "uri":"mrs_03_1145.html", "node_id":"mrs_03_1145.xml", "product_code":"mrs", - "code":"1323", + "code":"1407", "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", @@ -24347,7 +25778,7 @@ "uri":"mrs_03_1146.html", "node_id":"mrs_03_1146.xml", "product_code":"mrs", - "code":"1324", + "code":"1408", "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", @@ -24365,7 +25796,7 @@ "uri":"mrs_03_1197.html", "node_id":"mrs_03_1197.xml", "product_code":"mrs", - "code":"1325", + "code":"1409", "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", @@ -24384,7 +25815,7 @@ "uri":"mrs_03_1067.html", "node_id":"mrs_03_1067.xml", "product_code":"mrs", - "code":"1326", + "code":"1410", "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", @@ -24402,7 +25833,7 @@ "uri":"mrs_03_1069.html", "node_id":"mrs_03_1069.xml", "product_code":"mrs", - "code":"1327", + "code":"1411", "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", @@ -24420,7 +25851,7 @@ "uri":"mrs_03_1169.html", "node_id":"mrs_03_1169.xml", "product_code":"mrs", - "code":"1328", + "code":"1412", "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", @@ -24439,7 +25870,7 @@ "uri":"mrs_03_1070.html", "node_id":"mrs_03_1070.xml", "product_code":"mrs", - "code":"1329", + "code":"1413", "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", @@ -24457,7 +25888,7 @@ "uri":"mrs_03_1147.html", "node_id":"mrs_03_1147.xml", "product_code":"mrs", - "code":"1330", + "code":"1414", "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", @@ -24476,7 +25907,7 @@ "uri":"mrs_03_1157.html", "node_id":"mrs_03_1157.xml", "product_code":"mrs", - "code":"1331", + "code":"1415", "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", @@ -24495,7 +25926,7 @@ "uri":"mrs_03_1158.html", "node_id":"mrs_03_1158.xml", "product_code":"mrs", - "code":"1332", + "code":"1416", "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", @@ -24514,7 +25945,7 @@ "uri":"mrs_03_1159.html", "node_id":"mrs_03_1159.xml", "product_code":"mrs", - "code":"1333", + "code":"1417", "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", @@ -24532,7 +25963,7 @@ "uri":"mrs_03_1127.html", "node_id":"mrs_03_1127.xml", "product_code":"mrs", - "code":"1334", + "code":"1418", "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", @@ -24550,7 +25981,7 @@ "uri":"mrs_03_1163.html", "node_id":"mrs_03_1163.xml", "product_code":"mrs", - "code":"1335", + "code":"1419", "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", @@ -24569,7 +26000,7 @@ "uri":"mrs_03_1210.html", "node_id":"mrs_03_1210.xml", "product_code":"mrs", - "code":"1336", + "code":"1420", "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", @@ -24588,7 +26019,7 @@ "uri":"mrs_03_1206.html", "node_id":"mrs_03_1206.xml", "product_code":"mrs", - "code":"1337", + "code":"1421", "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 ", @@ -24607,7 +26038,7 @@ "uri":"mrs_03_1209.html", "node_id":"mrs_03_1209.xml", "product_code":"mrs", - "code":"1338", + "code":"1422", "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", @@ -24626,7 +26057,7 @@ "uri":"mrs_03_1217.html", "node_id":"mrs_03_1217.xml", "product_code":"mrs", - "code":"1339", + "code":"1423", "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", @@ -24644,7 +26075,7 @@ "uri":"mrs_03_1248.html", "node_id":"mrs_03_1248.xml", "product_code":"mrs", - "code":"1340", + "code":"1424", "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", @@ -24662,7 +26093,7 @@ "uri":"mrs_03_2015.html", "node_id":"mrs_03_2015.xml", "product_code":"mrs", - "code":"1341", + "code":"1425", "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", @@ -24680,7 +26111,7 @@ "uri":"mrs_03_1139.html", "node_id":"mrs_03_1139.xml", "product_code":"mrs", - "code":"1342", + "code":"1426", "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", @@ -24698,7 +26129,7 @@ "uri":"mrs_03_2016.html", "node_id":"mrs_03_2016.xml", "product_code":"mrs", - "code":"1343", + "code":"1427", "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", @@ -24716,7 +26147,7 @@ "uri":"mrs_03_1002.html", "node_id":"mrs_03_1002.xml", "product_code":"mrs", - "code":"1344", + "code":"1428", "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", @@ -24735,7 +26166,7 @@ "uri":"mrs_03_1003.html", "node_id":"mrs_03_1003.xml", "product_code":"mrs", - "code":"1345", + "code":"1429", "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", @@ -24754,7 +26185,7 @@ "uri":"mrs_03_1004.html", "node_id":"mrs_03_1004.xml", "product_code":"mrs", - "code":"1346", + "code":"1430", "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", @@ -24773,7 +26204,7 @@ "uri":"mrs_03_1054.html", "node_id":"mrs_03_1054.xml", "product_code":"mrs", - "code":"1347", + "code":"1431", "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", @@ -24792,7 +26223,7 @@ "uri":"mrs_03_1016.html", "node_id":"mrs_03_1016.xml", "product_code":"mrs", - "code":"1348", + "code":"1432", "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", @@ -24810,7 +26241,7 @@ "uri":"mrs_03_1018.html", "node_id":"mrs_03_1018.xml", "product_code":"mrs", - "code":"1349", + "code":"1433", "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", @@ -24829,7 +26260,7 @@ "uri":"mrs_03_1024.html", "node_id":"mrs_03_1024.xml", "product_code":"mrs", - "code":"1350", + "code":"1434", "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", @@ -24848,7 +26279,7 @@ "uri":"mrs_03_1028.html", "node_id":"mrs_03_1028.xml", "product_code":"mrs", - "code":"1351", + "code":"1435", "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", @@ -24867,7 +26298,7 @@ "uri":"mrs_03_1034.html", "node_id":"mrs_03_1034.xml", "product_code":"mrs", - "code":"1352", + "code":"1436", "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", @@ -24885,7 +26316,7 @@ "uri":"mrs_03_1130.html", "node_id":"mrs_03_1130.xml", "product_code":"mrs", - "code":"1353", + "code":"1437", "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", @@ -24903,7 +26334,7 @@ "uri":"mrs_03_1161.html", "node_id":"mrs_03_1161.xml", "product_code":"mrs", - "code":"1354", + "code":"1438", "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?", @@ -24921,7 +26352,7 @@ "uri":"mrs_03_1162.html", "node_id":"mrs_03_1162.xml", "product_code":"mrs", - "code":"1355", + "code":"1439", "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", @@ -24939,7 +26370,7 @@ "uri":"mrs_03_1171.html", "node_id":"mrs_03_1171.xml", "product_code":"mrs", - "code":"1356", + "code":"1440", "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", @@ -24958,7 +26389,7 @@ "uri":"mrs_03_1198.html", "node_id":"mrs_03_1198.xml", "product_code":"mrs", - "code":"1357", + "code":"1441", "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", @@ -24977,7 +26408,7 @@ "uri":"mrs_03_1211.html", "node_id":"mrs_03_1211.xml", "product_code":"mrs", - "code":"1358", + "code":"1442", "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", @@ -24996,7 +26427,7 @@ "uri":"mrs_03_1250.html", "node_id":"mrs_03_1250.xml", "product_code":"mrs", - "code":"1359", + "code":"1443", "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", @@ -25014,7 +26445,7 @@ "uri":"mrs_03_1212.html", "node_id":"mrs_03_1212.xml", "product_code":"mrs", - "code":"1360", + "code":"1444", "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", @@ -25033,7 +26464,7 @@ "uri":"mrs_03_1228.html", "node_id":"mrs_03_1228.xml", "product_code":"mrs", - "code":"1361", + "code":"1445", "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", @@ -25051,7 +26482,7 @@ "uri":"mrs_03_2018.html", "node_id":"mrs_03_2018.xml", "product_code":"mrs", - "code":"1362", + "code":"1446", "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", @@ -25069,7 +26500,7 @@ "uri":"mrs_03_1038.html", "node_id":"mrs_03_1038.xml", "product_code":"mrs", - "code":"1363", + "code":"1447", "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", @@ -25088,7 +26519,7 @@ "uri":"mrs_03_1131.html", "node_id":"mrs_03_1131.xml", "product_code":"mrs", - "code":"1364", + "code":"1448", "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", @@ -25106,7 +26537,7 @@ "uri":"mrs_03_1148.html", "node_id":"mrs_03_1148.xml", "product_code":"mrs", - "code":"1365", + "code":"1449", "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", @@ -25125,7 +26556,7 @@ "uri":"mrs_03_1152.html", "node_id":"mrs_03_1152.xml", "product_code":"mrs", - "code":"1366", + "code":"1450", "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", @@ -25144,7 +26575,7 @@ "uri":"mrs_03_1153.html", "node_id":"mrs_03_1153.xml", "product_code":"mrs", - "code":"1367", + "code":"1451", "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", @@ -25163,7 +26594,7 @@ "uri":"en-us_topic_0000001442653993.html", "node_id":"en-us_topic_0000001442653993.xml", "product_code":"mrs", - "code":"1368", + "code":"1452", "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", @@ -25182,7 +26613,7 @@ "uri":"mrs_03_1167.html", "node_id":"mrs_03_1167.xml", "product_code":"mrs", - "code":"1369", + "code":"1453", "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", @@ -25201,7 +26632,7 @@ "uri":"mrs_03_2019.html", "node_id":"mrs_03_2019.xml", "product_code":"mrs", - "code":"1370", + "code":"1454", "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", @@ -25219,7 +26650,7 @@ "uri":"mrs_03_1119.html", "node_id":"mrs_03_1119.xml", "product_code":"mrs", - "code":"1371", + "code":"1455", "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", @@ -25238,7 +26669,7 @@ "uri":"mrs_01_9003.html", "node_id":"mrs_01_9003.xml", "product_code":"mrs", - "code":"1372", + "code":"1456", "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-12091.html b/docs/mrs/umn/ALM-12091.html index 38437c040..26fc996b6 100644 --- a/docs/mrs/umn/ALM-12091.html +++ b/docs/mrs/umn/ALM-12091.html @@ -61,11 +61,11 @@

Possible Causes

The disaster process is abnormal.

Handling Procedure

Check whether the disaster 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 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 disaster resources managed by the HA is normal. In the single-node system, the disaster resource is in the normal state. In the dual-node system, the disaster 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 disaster resources managed by the HA is normal. In the single-node system, the disaster resource is in the normal state. In the dual-node system, the disaster 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}/disaster/disaster.log command to check whether the disaster resource log of HA contains the keyword ERROR. If yes, analyze the logs to locate the resource exception cause and fix the exception.
    6. Wait 5 minutes and check whether the alarm is automatically cleared.

      • If yes, no further action is required.
      • If no, go to 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, select Disaster 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 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, select Disaster 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 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-12186.html b/docs/mrs/umn/ALM-12186.html index a4b4a3755..6a8bfe8bc 100644 --- a/docs/mrs/umn/ALM-12186.html +++ b/docs/mrs/umn/ALM-12186.html @@ -62,13 +62,13 @@

Possible Causes

The CGroup task usage exceeds 90%.

Handling Procedure

Check the maximum number of threads that can be concurrently opened by user omm is properly set.

-
  1. Log in to FusionInsight Manager and 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. Click the host name to view its IP address.
  2. Log in to the host for which the alarm is generated as user omm.
  3. Run the following command to obtain the maximum number of threads that can be concurrently opened by user omm and check whether this number is greater than or equal to 60000:

    systemctl status user-$(id -u).slice | grep limit

    +
    1. Log in to MRS Manager and 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. Click the host name to view its IP address.
    2. Log in to the host for which the alarm is generated as user omm.
    3. Run the following command to obtain the maximum number of threads that can be concurrently opened by user omm and check whether this number is greater than or equal to 60000:

      systemctl status user-$(id -u).slice | grep limit

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

    4. Switch to user root and run the following command to change the value for user omm to 60000:

      systemctl set-property user-2000.slice TasksMax=60000

    5. Change the value of UserTasksMax in the /etc/systemd/logind.conf file to 60000. (If the parameter is commented out, uncomment it.) Save the file, wait 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 FusionInsight Manager of the cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
    2. Expand the Service drop-down list, select OmmServer and NodeAgent 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 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 cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
    2. Expand the Service drop-down list, select OmmServer and NodeAgent 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 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-12187.html b/docs/mrs/umn/ALM-12187.html index 9b052fe16..0c99d0e54 100644 --- a/docs/mrs/umn/ALM-12187.html +++ b/docs/mrs/umn/ALM-12187.html @@ -65,11 +65,11 @@

Possible Causes

  • The growpart scale-out tool is not installed.
  • The system fails to execute the command for expanding disk partition.

Handling Procedure

Check whether growpart is installed.

-
  1. Log in to FusionInsight Manager, click O&M, and choose Alarm > Alarms to view the alarm details. In the Location column, check the name of the host and mount directory for which the alarm is generated. Click the host name to view its IP address.
  2. Log in to the node for which the alarm is generated as user root.
  3. Run the following command to check whether growpart is installed:

    which growpart

    +
    1. Log in to MRS Manager, click O&M, and choose Alarm > Alarms to view the alarm details. In the Location column, check the name of the host and mount directory for which the alarm is generated. Click the host name to view its IP address.
    2. Log in to the node for which the alarm is generated as user root.
    3. Run the following command to check whether growpart is installed:

      which growpart

      If information similar to the following is displayed, the growpart tool is installed. Otherwise, contact O&M personnel to install the growpart tool.
      [root@xxx ~]#which growpart
 /usr/bin/growpart
      -

    1. Wait for 5 minutes, then choose O&M, and choose Alarm > Alarms on FusionInsight Manager. Check whether the alarm is cleared.

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

    1. Wait for 5 minutes, then choose O&M, and choose Alarm > Alarms on MRS Manager. Check whether the alarm is cleared.

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

    Run the disk partition expansion command.

    1. Run the following command to view the disk and partition information:

      lsblk

      @@ -86,7 +86,7 @@

      resize2fs /dev/vdb1

      If information similar to the following is displayed, the execution is successful:

      -

    2. Wait for 5 minutes, click O&M, and choose Alarm > Alarms on FusionInsight Manager. Check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, contact O&M personnel.
      +

    3. Wait for 5 minutes, click O&M, and choose Alarm > Alarms on MRS Manager. Check whether the alarm is cleared.

      • If yes, no further action is required.
      • If no, contact O&M personnel.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-12188.html b/docs/mrs/umn/ALM-12188.html index 91c7277db..2561ece42 100644 --- a/docs/mrs/umn/ALM-12188.html +++ b/docs/mrs/umn/ALM-12188.html @@ -60,7 +60,7 @@

Possible Causes

  • The diskmgt disk monitoring service does not exist.
  • The diskmgt disk monitoring service is not started.

Handling Procedure

Check whether the diskmgt disk monitoring service exists.

-
  1. Log in to FusionInsight Manager, click O&M, and choose Alarm > Alarms to view the alarm details. In the Location column, check the name of the host for which the alarm is generated. Click the host name to view its IP address.
  2. Log in to the node for which the alarm is generated as user root.
  3. Run the following command to check whether the core service file exists:

    stat /usr/local/diskmgt/inner/diskmgtd

    +
    1. Log in to MRS Manager, click O&M, and choose Alarm > Alarms to view the alarm details. In the Location column, check the name of the host for which the alarm is generated. Click the host name to view its IP address.
    2. Log in to the node for which the alarm is generated as user root.
    3. Run the following command to check whether the core service file exists:

      stat /usr/local/diskmgt/inner/diskmgtd

      If the file does not exist, contact O&M personnel.

    Start the diskmgt disk monitoring service.

    @@ -69,7 +69,7 @@
    • If information similar to the following is displayed, the service is started successfully. Go to 6.

    • If no, contact O&M personnel.
    -

  4. Wait for 5 minutes, click O&M, and choose Alarm > Alarms on FusionInsight Manager. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, contact O&M personnel.
    +

  5. Wait for 5 minutes, click O&M, and choose Alarm > Alarms on MRS Manager. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, contact O&M personnel.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-12191.html b/docs/mrs/umn/ALM-12191.html new file mode 100644 index 000000000..9835457ab --- /dev/null +++ b/docs/mrs/umn/ALM-12191.html @@ -0,0 +1,98 @@ + + +

ALM-12191 Disk I/O Usage Exceeds the Threshold

+

Alarm Description

The system checks the disk I/O usage every 30 seconds and compares the actual disk I/O usage with the threshold. This alarm is generated when the disk I/O usage exceeds the threshold for multiple consecutive times (3 by default).

+

If the hit number is 1, this alarm is cleared when the disk I/O usage is less than or equal to the threshold. If the hit number is greater than 1, this alarm is cleared when the disk I/O usage is less than or equal to 90% of the threshold.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12191

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

  • Latency: Service processes may run slowly and there is a latency.
  • Service failure: Service processing may be slow, time out, or fail. As a result, jobs may fail to run.
+
+

Possible Causes

  • The alarm threshold or alarm trigger count is improperly configured.
  • The disk configuration cannot meet service requirements. The disk I/O usage reaches the upper limit. Alternatively, services are in peak hours. The disk I/O usage reaches the upper limit in a short period.
+
+

Handling Procedure

Check whether the alarm threshold or alarm trigger count is properly configured.

+
  1. Modify the alarm threshold and alarm trigger count based on the actual disk I/O usage.

    1. Log in to MRS Manager and choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Host > Disk > Disk IO Utilization.
    2. Click the edit button next to Trigger Count to change it to a proper value based on the actual service usage.

      Trigger Count indicates how many consecutive times the threshold is reached when the alarm is triggered.

      +
      +
    3. Click Modify in the Operation column of the row that contains the rule and change the alarm threshold.
    +

  2. Wait 2 minutes and check whether the alarm is automatically cleared.

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

+

Check whether the disk I/O usage reaches the upper limit.

+
  1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details and click the name of the host for which the alarm is generated in Location area.
  2. On the overview page of the host, observe the real-time data of the disk I/O usage for about 5 minutes. If the disk I/O usage exceeds the threshold for multiple times, contact the MRS cluster administrator to improve the disk specification.

    If Disk IO Utilization chart is not displayed, click the drop-down arrow on the right, select Customize, select the desired item, and click OK.

    +

  3. Check whether it was the peak hour. If this alarm was generated during peak hours, expand the node capacity or contact the MRS cluster administrator to improve the disk specification.
  4. Check whether the alarm is cleared.

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

+

Collect fault information.

+
  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 NodeAgent for the target cluster, and click OK.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12192.html b/docs/mrs/umn/ALM-12192.html new file mode 100644 index 000000000..64eb0fa41 --- /dev/null +++ b/docs/mrs/umn/ALM-12192.html @@ -0,0 +1,98 @@ + + +

ALM-12192 Host Load Exceeds the Threshold

+

Alarm Description

The system checks the average load every 30 seconds and compares the actual average load with the threshold. This alarm is generated when the average load exceeds the threshold for multiple consecutive times (10 by default).

+

This alarm is cleared when Trigger Count is 1 and the average load is less than or equal to the threshold. This alarm is cleared when Trigger Count is greater than 1 and the average load is less than or equal to 90% of the threshold.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12192

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

  • Latency: Service processes may run slowly and there is a latency.
  • Service failure: Service processing may be slow, time out, or fail. As a result, jobs may fail to run.
+
+

Possible Causes

  • The alarm threshold or alarm trigger count is improperly configured.
  • The host cannot meet service requirements. The average load reaches the upper limit. Alternatively, requirements surged during peak hours, and the average load reaches the upper limit in a short period.
+
+

Handling Procedure

Check whether the alarm threshold or alarm trigger count is properly configured.

+
  1. Modify the alarm threshold and alarm trigger count based on the actual CPU usage.

    1. To change the threshold, log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Host > Host Status > Average Host Load Information.
    2. Click the edit button next to Trigger Count to set it a proper value based on the actual service usage.

      Trigger Count indicates how many consecutive times the threshold is reached when the alarm is triggered.

      +
      +
    3. Click Modify in the Operation column of the row that contains the rule and change the alarm threshold.
    +

  2. Wait 2 minutes and check whether the alarm is automatically cleared.

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

+

Check whether the average load reaches the upper limit.

+
  1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details and click the name of the host for which the alarm is generated in Location area.
  2. On the overview page of the host, observe the real-time data of average host load for about 5 minutes. If the average load exceeds the threshold for multiple times, contact the MRS cluster administrator to improve the host specification.

    If Average Host Load Information chart is not displayed, click the drop-down arrow on the right, select Customize, select the desired item, and click OK.

    +

  3. Check whether it was the peak hour. If this alarm was generated during peak hours, expand the node capacity or contact the MRS cluster administrator to improve the host specification.
  4. Check whether the alarm is cleared.

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

+

Collect fault information.

+
  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 NodeAgent for the target cluster, and click OK.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12200.html b/docs/mrs/umn/ALM-12200.html new file mode 100644 index 000000000..368c39253 --- /dev/null +++ b/docs/mrs/umn/ALM-12200.html @@ -0,0 +1,81 @@ + + +

ALM-12200 Password Is About to Expire

+

Alarm Description

The system checks whether a user password is about to expire at 1:00 a.m. every day. This alarm is generated when a user password is about to expire in less than 5 days by default.

+

This alarm is cleared when the password is about to expire in at least five days by default.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12200

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

Additional Information

+

Details

+

Specifies that the username of password that is about to expire.

+
+
+
+

Impact on the System

The account cannot be used.

+
+

Possible Causes

The password is about to expire.

+
+

Handling Procedure

Change the user password.

+
  1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details, and view and record the name of the user whose password is about to expire in additional information.
  2. Change the password.
  3. If the DataArts Studio service is interconnected, check whether DataArts Studio jobs uses a password that is about to expire. If yes, go to the DataArts Studio management center to change the password. Otherwise, a large number of jobs may fail.
  4. Check whether the alarm is automatically cleared after 1:00 a.m. the next day.

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

+

Collect fault information.

+
  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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12201.html b/docs/mrs/umn/ALM-12201.html new file mode 100644 index 000000000..de2883bf3 --- /dev/null +++ b/docs/mrs/umn/ALM-12201.html @@ -0,0 +1,98 @@ + + +

ALM-12201 Process CPU Usage Exceeds the Threshold

+

Alarm Description

The system checks the CPU usage every 30 seconds and compares the check result with the default threshold. This alarm is generated when the CPU usage exceeds the threshold for multiple consecutive times (10 by default).

+

This alarm is cleared when Trigger Count is 1 and the CPU usage is less than or equal to the threshold. This alarm is cleared when Trigger Count is greater than 1 and the CPU usage is less than or equal to 90% of the threshold.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12201

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

  • Latency: Service processes may run slowly and there is a latency.
  • Service failure: Service processing may be slow, time out, or fail. As a result, jobs may fail to run.
+
+

Possible Causes

  • The alarm threshold or alarm trigger count is improperly configured.
  • The CPU configuration cannot meet service requirements, and the CPU usage reaches the upper limit. Alternatively, services are in peak hours. The CPU usage reaches the upper limit in a short period.
+
+

Handling Procedure

Check whether the alarm threshold or alarm trigger count is properly configured.

+
  1. Modify the alarm threshold and alarm trigger count based on the actual CPU usage.

    1. Log in to MRS Manager and choose O&M > Alarm > Thresholds > OMS > OMSServices > CPU > Process Used CPU (OMS).
    2. Click the edit button next to Trigger Count to set it a proper value based on the actual service usage.

      Trigger Count indicates how many consecutive times the threshold is reached when the alarm is triggered.

      +
      +
    3. Click Modify in the Operation column of the row that contains the rule and change the alarm threshold.
    +

  2. Wait 2 minutes and check whether the alarm is automatically cleared.

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

+

Check whether the CPU usage reaches the upper limit.

+
  1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details and click the name of the host for which the alarm is generated in Location area.
  2. On the overview page of the host, observe the real-time data of the host CPU usage for about 5 minutes. If the CPU usage exceeds the threshold for multiple times, contact the MRS cluster administrator to increase the CPU.

    If no chart is available, click the drop-down arrow on the right, select Customize, select the desired item, and click OK.

    +

  3. Check whether it was the peak hour. If this alarm was generated during peak hours, expand the node capacity or contact the MRS cluster administrator to improve the CPU specification.
  4. Check whether the alarm is cleared.

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

+

Collect fault information.

+
  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 OmmServer for the target cluster, and click OK.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12202.html b/docs/mrs/umn/ALM-12202.html new file mode 100644 index 000000000..2b1e2dd33 --- /dev/null +++ b/docs/mrs/umn/ALM-12202.html @@ -0,0 +1,93 @@ + + +

ALM-12202 Process Memory Usage Exceeds the Threshold

+

Alarm Description

The system checks the memory usage of main OMS processes every 30 seconds. This alarm is generated when the memory usage of main OMS processes is greater than 90% (default value) of the maximum memory.

+

This alarm is cleared when the memory usage of main OMS processes is less than or equal to 90% of the maximum memory.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12202

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

If the memory usage of main OMS processes is too high, the performance of these processes deteriorates, and even memory overflow occurs. As a result, main OMS processes are unavailable, and OMS tasks are slow or fail to run.

+
+

Possible Causes

The memory usage of main OMS processes is too high or the memory is inappropriately allocated.

+
+

Handling Procedure

Check the memory usage of main OMS processes.

+
  1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details, record the process name in Location, click the reported host name, and record the service IP address of the host.
  2. Choose System > OMS to view the OMS Process Memory Usage Ratio chart. Check whether the memory usage of the processes reaches the threshold (90% by default) at the time when the alarm is generated.

    If no chart is available, click the drop-down arrow on the right, select Customize, select the desired item, and click OK.
    • If yes, go to 3.
    • If the threshold is not reached, go to 6.
    +
    +

  3. Contact O&M personnel to modify the memory configurations of the processes.
  4. Restart the processes for which the alarm is generated.
  5. Check whether the alarm is cleared in 10 minutes.

    • If yes, no further action is required.
    • If the threshold is not reached, go to 6.
    +

+

Collect fault information.

+
  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 OmmServer for the target cluster.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12203.html b/docs/mrs/umn/ALM-12203.html new file mode 100644 index 000000000..83d7f0338 --- /dev/null +++ b/docs/mrs/umn/ALM-12203.html @@ -0,0 +1,93 @@ + + +

ALM-12203 Process Full GC Duration Exceeds the Threshold

+

Alarm Description

The system checks the GC duration of main OMS processes every 30 seconds. If the GC duration of an OMS process exceeds the threshold for three consecutive times, this alarm is generated. You can choose O&M > Alarm > Thresholds > OMS > OMSServices to change the threshold.

+

This alarm is cleared when the GC duration of the OMS process is shorter than or equal to the threshold.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12203

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

Read and write performance deteriorates. As a result, the task execution may slow down and even the service may restart unexpectedly.

+
+

Possible Causes

The memory of main OMS processes is too high or inappropriately allocated, causing frequent occurrence of the full GC.

+
+

Handling Procedure

Check the GC duration.

+
  1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details, record the process name in Location, click the reported host name, and record the service IP address of the host.
  2. Choose System > OMS, view the Full GC Times of OMS Process chart, and check whether the GC time is longer than 12 seconds (default value).

    If no chart is available, click the drop-down arrow on the right, select Customize, select the desired item, and click OK.
    • If yes, go to 3.
    • If no, go to 6.
    +
    +

  1. Contact O&M personnel to modify the memory configurations of the processes.
  2. Restart the process.
  3. Check whether the alarm is cleared.

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

+

Collect fault information.

+
  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 OmmServer for the target cluster.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12204.html b/docs/mrs/umn/ALM-12204.html new file mode 100644 index 000000000..99bc166b6 --- /dev/null +++ b/docs/mrs/umn/ALM-12204.html @@ -0,0 +1,98 @@ + + +

ALM-12204 Wait Duration of a Disk Read Exceeds the Threshold

+

Alarm Description

The system checks the wait duration of a disk read every 30 seconds and compares the actual wait duration with the threshold. This alarm is generated when the wait duration exceeds the threshold (10s by default) for multiple consecutive times.

+

This alarm is cleared when the wait duration is less than or equal to the threshold.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12204

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

  • Latency: Service processes may run slowly and there is a latency.
  • Service failure: Service processing may be slow, time out, or fail. As a result, jobs may fail to run.
+
+

Possible Causes

  • The alarm threshold or alarm trigger count is improperly configured.
  • The disk configuration cannot meet service requirements. The disk I/O performance reaches the upper limit. Alternatively, services are in peak hours. The wait duration of a disk read reaches the upper limit in a short period.
+
+

Handling Procedure

Check whether the alarm threshold or alarm trigger count is properly configured.

+
  1. Modify the alarm threshold and alarm trigger count based on the actual disk I/O usage.

    1. Log in to MRS Manager and choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Disk > Average Time Required for Each Read operation.
    2. Click the edit button next to Trigger Count to set it a proper value based on the actual service usage.

      Trigger Count indicates how many consecutive times the threshold is reached when the alarm is triggered.

      +
      +
    3. Click Modify in the Operation column of the row that contains the rule and change the alarm threshold.
    +

  2. Wait 2 minutes and check whether the alarm is automatically cleared.

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

+

Check whether the average time required for each read operation reaches the upper limit.

+
  1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details and click the name of the host for which the alarm is generated in Location area.
  2. On the overview page of the host, observe the real-time data of average time required for each read operation for about 5 minutes. If the wait duration exceeds the threshold for multiple times, contact the MRS cluster administrator to improve the disk specification.

    If the Average Time Required for Each Read Operation chart is unavailable, click the drop-down arrow on the right, select Customize, select the corresponding item, and click OK.

    +

  3. Check whether it was the peak hour. If this alarm was generated during peak hours, expand the node capacity or contact the MRS cluster administrator to improve the disk specification.
  4. Check whether the alarm is cleared.

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

+

Collect fault information.

+
  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 NodeAgent for the target cluster, and click OK.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12205.html b/docs/mrs/umn/ALM-12205.html new file mode 100644 index 000000000..ec96ad090 --- /dev/null +++ b/docs/mrs/umn/ALM-12205.html @@ -0,0 +1,98 @@ + + +

ALM-12205 Wait Duration of a Disk Write Exceeds the Threshold

+

Alarm Description

The system checks the wait duration of a disk write every 30 seconds and compares the actual wait duration with the threshold. This alarm is generated when the wait duration exceeds the threshold (10s by default) for multiple consecutive times.

+

This alarm is cleared when the wait duration is less than or equal to the threshold.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12205

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

  • Latency: Service processes may run slowly and there is a latency.
  • Service failure: Service processing may be slow, time out, or fail. As a result, jobs may fail to run.
+
+

Possible Causes

  • The alarm threshold or alarm trigger count is improperly configured.
  • The disk configuration cannot meet service requirements. The disk I/O performance reaches the upper limit. Alternatively, services are in peak hours. The wait duration of a disk write reaches the upper limit in a short period.
+
+

Handling Procedure

Check whether the alarm threshold or alarm trigger count is properly configured.

+
  1. Modify the alarm threshold and alarm trigger count based on the actual disk I/O usage.

    1. Log in to MRS Manager and choose O&M > Alarm > Thresholds > Name of the desired cluster > Host > Disk > Average Time Required for Each Write Operation.
    2. Click the edit button next to Trigger Count to set it a proper value based on the actual service usage.

      Trigger Count indicates how many consecutive times the threshold is reached when the alarm is triggered.

      +
      +
    3. Click Modify in the Operation column of the row that contains the rule and change the alarm threshold.
    +

  2. Wait 2 minutes and check whether the alarm is automatically cleared.

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

+

Check whether the average time required for each write operation reaches the upper limit.

+
  1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details and click the name of the host for which the alarm is generated in Location area.
  2. On the overview page of the host, observe the real-time data of average time required for each write operation for about 5 minutes. If the wait duration exceeds the threshold for multiple times, contact the MRS cluster administrator to improve the disk specification.

    If the Average Time Required for Each Write Operation chart is not displayed, click the drop-down arrow on the right, select Customize, select the desired item, and click OK.

    +

  3. Check whether it was the peak hour. If this alarm was generated during peak hours, expand the node capacity or contact the MRS cluster administrator to improve the disk specification.
  4. Check whether the alarm is cleared.

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

+

Collect fault information.

+
  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 NodeAgent for the target cluster, and click OK.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12206.html b/docs/mrs/umn/ALM-12206.html new file mode 100644 index 000000000..e62322f4c --- /dev/null +++ b/docs/mrs/umn/ALM-12206.html @@ -0,0 +1,81 @@ + + +

ALM-12206 Password Has Expired

+

Alarm Description

The system checks whether a user password has expired at 1:00 a.m. every day. This alarm is generated when a user password has expired.

+

This alarm is cleared when the user password in the system is within the validity period.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12206

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

Additional Information

+

Details

+

Specifies that the username of password that has expired.

+
+
+
+

Impact on the System

The account cannot be used.

+
+

Possible Causes

The user password has expired.

+
+

Handling Procedure

Change the user password.

+
  1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details, and view and record the name of the user whose password has expired in additional information.
  2. Change the user password that has expired.
  3. If the DataArts Studio service is interconnected, check whether DataArts Studio jobs uses an expired user password. If yes, go to the DataArts Studio management center to change the password and execute the affected jobs again.
  4. Check whether the alarm is automatically cleared after 1:00 a.m. the next day.

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

+

Collect fault information.

+
  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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-12207.html b/docs/mrs/umn/ALM-12207.html new file mode 100644 index 000000000..cef232f5f --- /dev/null +++ b/docs/mrs/umn/ALM-12207.html @@ -0,0 +1,112 @@ + + +

ALM-12207 Slow Disk Processing Timeout

+

Alarm Description

When slow disk detection is enabled, the system checks the slow disk processing status every 10 minutes by default. This alarm is generated when the following disk or node status does not change within 10 hours.

+

Disk: Automatic isolation aborted, isolated, isolation failed, and de-isolation failed.

+

Node: Isolated, Isolation failed, Isolation cancellation failed, Node startup failed, and De-isolated.

+

This alarm is automatically cleared when the status of the node or disk that is in the processing timeout state changes.

+

This alarm applies only to MRS 3.3.1 or later.

+
+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

12207

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster or system for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

DiskName

+

Specifies the disk for which the alarm was generated.

+

Additional Information

+

HostName

+

Specifies the host for which the alarm was generated.

+

DiskName

+

Specifies the disk for which the alarm was generated.

+

Details

+

Specifies that the description of slow disk isolation.

+
+
+
+

Impact on the System

If an isolated disk or node cannot be restored in a timely manner, the running of components may be affected, which further affects user services.

+
+

Possible Causes

The isolation status of the disk or node exceeds the configured timeout period for processing slow disks.

+
+

Handling Procedure

Check the cause of the slow disk processing timeout.

+
  1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details, and view and record the host or disk for which the alarm is generated.
  2. Log in to the active OMS node as user root and run the following command to check the cause of slow disk processing timeout in the controller log and check whether there is obvious error information:

    vi /var/log/Bigdata/controller/controller.log

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

  3. Log in to the node for which the alarm is generated as user root and run the following command to check the cause of slow disk processing timeout in the agent log and check whether any error information is displayed:

    vi /var/log/Bigdata/nodeagent/agentlog/agent.log

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

  4. Contact O&M personnel to rectify the fault and manually run the command for the slow disk or node. After the command is executed, observe for 5 minutes and check whether the alarm is cleared.

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

+

Collect fault information.

+
  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Select Controller and NodeAgent for Service, select the active/standby OMS node and the node for which the alarm is generated in the Host area, and click OK.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-14031.html b/docs/mrs/umn/ALM-14031.html index 67fbab6fd..782632eb1 100644 --- a/docs/mrs/umn/ALM-14031.html +++ b/docs/mrs/umn/ALM-14031.html @@ -60,13 +60,13 @@

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. The process may also be suspended and enter the T state.

Handling Procedure

Check whether the process is in the D, Z, or T state.

-
  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

    • If the alarm is not in the list, no further action is required.
    • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.
    +
    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

      • If the alarm is not in the list, no further action is required.
      • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.

    2. Log in to the host where the alarm is generated as the root user and run the su - omm command to switch to the omm user.
    3. Run the following command to check the process state:

      ps ww -eo stat,cmd| grep -w org.apache.hadoop.hdfs.server.datanode.DataNode | grep -v grep | awk '{print$1}'

    4. Check whether the command output contains any abnormal state (D, Z, or T).

      • If the output contains any abnormal state, go to 5.
      • If the output does not contain abnormal states, go to 7.

    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. Wait 5 minutes and check whether the alarm is cleared.

      • If the alarm is cleared, no further action is required.
      • If the alarm fails to be cleared, go to 7.

    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 the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-14032.html b/docs/mrs/umn/ALM-14032.html index 6d714ee6f..6361f5e31 100644 --- a/docs/mrs/umn/ALM-14032.html +++ b/docs/mrs/umn/ALM-14032.html @@ -60,13 +60,13 @@

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. The process may also be suspended and enter the T state.

Handling Procedure

Check whether the process is in the D, Z, or T state.

-
  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

    • If the alarm is not in the list, no further action is required.
    • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.
    +
    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

      • If the alarm is not in the list, no further action is required.
      • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.

    2. Log in to the host where the alarm is generated as the root user and run the su - omm command to switch to the omm user.
    3. Run the following command to check the process state:

      ps ww -eo stat,cmd| grep -w org.apache.hadoop.hdfs.qjournal.server.JournalNode | grep -v grep | awk '{print$1}'

    4. Check whether the command output contains any abnormal state (D, Z, or T).

      • If the output contains any abnormal state, go to 5.
      • If the output does not contain abnormal states, go to 7.

    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. Wait 5 minutes and check whether the alarm is cleared.

      • If the alarm is cleared, no further action is required.
      • If the alarm fails to be cleared, go to 7.

    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 the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-14033.html b/docs/mrs/umn/ALM-14033.html index 4a948ed36..456b1fec7 100644 --- a/docs/mrs/umn/ALM-14033.html +++ b/docs/mrs/umn/ALM-14033.html @@ -60,13 +60,13 @@

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. The process may also be suspended and enter the T state.

Handling Procedure

Check whether the process is in the D, Z, or T state.

-
  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

    • If the alarm is not in the list, no further action is required.
    • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.
    +
    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

      • If the alarm is not in the list, no further action is required.
      • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.

    2. Log in to the host where the alarm is generated as the root user and run the su - omm command to switch to the omm user.
    3. Run the following command to check whether the process state is abnormal:

      ps ww -eo stat,cmd| grep -w org.apache.hadoop.hdfs.tools.DFSZKFailoverController | grep -v grep | awk '{print$1}'

    4. Check whether the command output contains any abnormal state (D, Z, or T).

      • If the output contains any abnormal state, go to 5.
      • If the output does not contain abnormal states, go to 7.

    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. Wait 5 minutes and check whether the alarm is cleared.

      • If the alarm is cleared, no further action is required.
      • If the alarm fails to be cleared, go to 7.

    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 the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-14034.html b/docs/mrs/umn/ALM-14034.html index 7e3716ce2..bbb962ea8 100644 --- a/docs/mrs/umn/ALM-14034.html +++ b/docs/mrs/umn/ALM-14034.html @@ -60,13 +60,13 @@

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. The process may also be suspended and enter the T state.

Handling Procedure

Check whether the process is in the D, Z, or T state.

-
  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

    • If the alarm is not in the list, no further action is required.
    • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.
    +
    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

      • If the alarm is not in the list, no further action is required.
      • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.

    2. Log in to the host where the alarm is generated as the root user and run the su - omm command to switch to the omm user.
    3. Run the following command to check whether the process state is abnormal:

      ps ww -eo stat,cmd| grep -w org.apache.hadoop.hdfs.server.federation.router.DFSRouter | grep -v grep | awk '{print$1}'

    4. Check whether the command output contains any abnormal state (D, Z, or T).

      • If the output contains any abnormal state, go to 5.
      • If the output does not contain abnormal states, go to 7.

    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. Wait 5 minutes and check whether the alarm is cleared.

      • If the alarm is cleared, no further action is required.
      • If the alarm fails to be cleared, go to 7.

    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 the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-14035.html b/docs/mrs/umn/ALM-14035.html index f16f02b64..c6879d8f9 100644 --- a/docs/mrs/umn/ALM-14035.html +++ b/docs/mrs/umn/ALM-14035.html @@ -60,13 +60,13 @@

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. The process may also be suspended and enter the T state.

Handling Procedure

Check whether the process is in the D, Z, or T state.

-
  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

    • If the alarm is not in the list, no further action is required.
    • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.
    +
    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

      • If the alarm is not in the list, no further action is required.
      • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.

    2. Log in to the host where the alarm is generated as the root user and run the su - omm command to switch to the omm user.
    3. Run the following command to check whether the process state is abnormal:

      ps ww -eo stat,cmd| grep -w org.apache.hadoop.fs.http.server.HttpFSServerWebServer | grep -v grep | awk '{print$1}'

    4. Check whether the command output contains any abnormal state (D, Z, or T).

      • If the output contains any abnormal state, go to 5.
      • If the output does not contain abnormal states, go to 7.

    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. Wait 5 minutes and check whether the alarm is cleared.

      • If the alarm is cleared, no further action is required.
      • If the alarm fails to be cleared, go to 7.

    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 the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-14036.html b/docs/mrs/umn/ALM-14036.html new file mode 100644 index 000000000..8f69d9bda --- /dev/null +++ b/docs/mrs/umn/ALM-14036.html @@ -0,0 +1,103 @@ + + +

ALM-14036 NameNode Is In Safe Mode

+

This alarm applies only to MRS 3.3.1 or later.

+

Alarm Description

The system checks the NameNode process status every 30 seconds. This alarm is generated when the NameNode is in the safe mode.

+

This alarm is cleared when the process status recovers.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

14036

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

After a NameNode enters the safe mode, data cannot be written to the NameNode.

+
+

Possible Causes

Block loss occurs when a user manually enters the safe mode or restarts the NameNode.

+
+

Handling Procedure

Check whether NameNode is in the security mode.

+
  1. Log in to MRS Manager, click O&M, and choose Alarm > Alarms to view the alarm details. In the Location column, check the name of the host for which the alarm is generated.
  2. Choose Cluster > Services > HDFS, and click NameNode(host name recorded in 1,x) next to NameNode Web UI.

    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. In the Basic Information area on the Dashboard page of HDFS (or in the NameService Summary area on the Dashboard page of HDFS), check whether the value of Safe Mode is ON.

    ON indicates that the safe mode is enabled.

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

  4. Log in to the HDFS client.

    1. Log in to the node where the HDFS client is installed.
      • If Kerberos authentication is enabled for the cluster (the cluster is in security mode), log in as the root user.
      • If Kerberos authentication is disabled for the cluster (the cluster is in normal mode), log in as user omm and ensure that user omm has the execute permission on the client.
      +

      (Note that you need to decide with cluster security/normal mode, not the HDFS safe/common mode.)

      +
    2. Run the following commands to go to the client installation directory and configure environment variables:

      cd HDFS client installation directory

      +

      source bigdata_env

      +
    3. If Kerberos authentication is enabled for the cluster (the cluster is in security mode), run the following command to authenticate the user. If Kerberos authentication is disabled for the cluster (the cluster is in normal mode), skip this step.

      kinit hdfs

      +

      Enter the password as prompted. You can obtain the password from the MRS cluster administrator. Change the password upon the first authentication.

      +
    4. Run the following command to exit from the safe mode:

      hdfs dfsadmin -safemode leave

      +
    +

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

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

  6. In the Basic Information area on the Dashboard page of HDFS (or in the NameService Summary area on the Dashboard page of HDFS), check whether the value of Missing Blocks is 0.

    • If yes, no further action is required.
    • If no, check whether "ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold" is reported and rectify the fault according to the alarm help.
    +

+

Collect fault information.

+
  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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-14037.html b/docs/mrs/umn/ALM-14037.html new file mode 100644 index 000000000..ced786374 --- /dev/null +++ b/docs/mrs/umn/ALM-14037.html @@ -0,0 +1,86 @@ + + +

ALM-14037 DataNodes Outside the Cluster

+

This alarm applies only to MRS 3.3.1 or later.

+

Alarm Description

The NameNode checks whether there are DataNodes that are not managed in the cluster every 8 hours. This alarm is generated when there is a DataNode outside the cluster. This alarm is cleared when no DataNode is outside the cluster.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

14037

+

Major

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

NameServiceName

+

Specifies the NameService for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition, that is, the IP address and port of a DataNode outside the cluster is detected.

+
+
+
+

Impact on the System

Data may be lost.

+
+

Possible Causes

After a host is forcibly deleted, the host is powered on again, and the process is restarted.

+
+

Handling Procedure

  1. Log in to MRS Manager, click O&M, and choose Alarm > Alarms to view the alarm details. In the additional information area, check the IP address of the host for which the alarm is generated.
  2. Stop the DataNode process on the host for which the alarm is reported.

    If there are multiple IP addresses of the host, you can stop only one DataNode process at a time and stop the next DataNode process only after Number of Blocks to Be Replicated changes to 0.

    +
    +
    1. Log in to the host for which the alarm is generated as the root user and change the permission on the hadoop directory in the installation directory ${BIGDATA_HOME}/FusionInsight_HD_*/install.

      chmod 000 ${BIGDATA_HOME}/FusionInsight_HD_8.1.0.1/install/FusionInsight-Hadoop-3.3.1

      +
    2. Run the following commands to obtain the PID of the DataNode process and stop it on the host:

      ps -ef | grep Dproc_datanode

      +

      kill -15 PID

      +
    3. Choose Cluster > Services > HDFS. Check the Basic Information area in the Dashboard tab (or the NameService Summary area in the Dashboard tab of HDFS), and wait until the value of Blocks to be Replicated changes to 0.
    +

  3. Wait for 8 hours and check whether the alarm is cleared and whether the number of blocks to be replicated is 0.

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

+

Collect fault information.

+
  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 the edit icon in the upper right corner, and set Start 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.
+
+

+
+ + diff --git a/docs/mrs/umn/ALM-14038.html b/docs/mrs/umn/ALM-14038.html new file mode 100644 index 000000000..ea0cd0c03 --- /dev/null +++ b/docs/mrs/umn/ALM-14038.html @@ -0,0 +1,92 @@ + + +

ALM-14038 Router Heap Memory Usage Exceeds the Threshold

+

Alarm Description

The system checks the size of the used HDFS Router heap memory and the maximum size of the heap memory that can be allocated every 30 seconds, calculates the ratio of the used heap memory to the maximum size of the heap memory that can be allocated to obtain the heap memory usage, and compares the actual heap memory usage of the HDFS Router with the threshold. The HDFS Router Heap Memory usage has a default threshold. This alarm is generated when the HDFS Router Heap Memory usage exceeds the threshold.

+

You can change the threshold in O&M > Alarm > Thresholds > Name of the desired cluster > HDFS.

+

The alarm is cleared when the heap memory usage is less than or equal to the threshold.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

14038

+

Critical (default threshold: 95%)

+

Major (default threshold: 90%)

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm is generated.

+

ServiceName

+

Specifies the service for which the alarm is generated.

+

RoleName

+

Specifies the role for which the alarm is generated.

+

HostName

+

Specifies the host for which the alarm is generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

The HDFS Router Heap Memory usage is too high, which affects the data read/write performance of the HDFS.

+
+

Possible Causes

The HDFS Router Heap Memory is insufficient.

+
+

Handling Procedure

  1. On MRS Manager, choose Cluster > Services > Ranger > Instance > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > System.
  2. On the MRS Manager portal, choose Cluster > Services > HDFS > Configurations > All Configurations. In Search, enter GC_OPTS to check the GC_OPTS memory parameter of HDFS->Router.
  3. Increase the values of -Xms and -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 Router cannot meet the requirements of the current process. You are advised to change the values of -Xms and -Xmx in the GC_OPTS parameter to twice the size of the used heap memory or change the values based on the site requirements.

    +
    +

  4. Restart the affected services 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 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 for the target cluster.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-14039.html b/docs/mrs/umn/ALM-14039.html new file mode 100644 index 000000000..47d423366 --- /dev/null +++ b/docs/mrs/umn/ALM-14039.html @@ -0,0 +1,103 @@ + + +

ALM-14039 Slow DataNodes Exist in the Cluster

+

Alarm Description

The system checks the number of slow operations per second on HDFS DataNode instances every 60 seconds and compares the number with the threshold. This alarm is generated when the number of slow operations per second of an HDFS DataNode instance has exceeded the threshold for three minutes.

+

This alarm is cleared when the number of slow operations per second of the HDFS DataNode instance is less than or equal to the threshold.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

14039

+

Major (default threshold: 100)

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

Slow DataNodes on HDFS affect the data read and write performance of HDFS.

+
+

Possible Causes

  • The disk I/O rate of the HDFS DataNode instance is low, and the HDFS DataNode processing capability reaches the bottleneck.
  • The network transmission rate between HDFS DataNode instances is low.
+
+

Handling Procedure

Check whether the disk I/O rate of the DataNode instance is low.

+
  1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the host name of the DataNode instance for which this alarm is generated.
  2. Choose Cluster > Services > HDFS, click the Instances tab, and click the DataNode role based on the host name obtained in 1.
  3. Click the Chart tab and select Performance from the Chart Category area. Check whether any data in Slow Flush or Sync Occurrences Per Second, Slow SyncWriterOsCache Occurrences Per Second, and Slow WriteDataToDisk Occurrences Per Second charts is high.

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

  4. On MRS Manager, choose O&M > Alarm > Alarms and check whether ALM-12033 Slow Disk Fault exists.

    • If yes, record the disk information in the alarm details and go to 6.
    • If no, go to 5.
    +

  5. Obtain information about the disk where slow operations occur.

    1. Log in to the DataNode using the IP address obtained in 1 as user omm and run the following commands to view the run log:

      cd /var/log/Bigdata/hdfs/dn/

      +

      vim hadoop-omm-datanode-Hostname.log

      +
    2. Search for keyword slow in the log to identify the disk where slow operations occur.

      +
    +

  6. Rectify the fault based on the obtained disk information by following the handling procedure of ALM-12033 Slow Disk Fault.
  7. Wait 5 minutes and check whether the alarm is cleared.

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

+

Check whether the network transmission rate between HDFS DataNode instances is low.

+
  1. On MRS Manager, choose Cluster > Services > HDFS, click the Chart tab, select Performance in the Chart Category area, and check whether any data in the Slow Write Packet To DownStream Count Per Second and Slow Ack To Upstream Count Per Second charts is high.

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

  2. Log in to the DataNode using the IP address obtained in 1 as user omm and run the following commands to view the run log:

    cd /var/log/Bigdata/hdfs/dn/

    +

    vim hadoop-omm-datanode-Hostname.log

    +

  3. Search for keyword slow in the log to identify the upstream and downstream nodes where slow operations occur.

    +

  4. Check whether the network communication between the current node and the nodes obtained in 10 is normal.

    • If yes, go to 13.
    • If no, contact the network administrator to repair the network.
    +

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

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

+

Collect fault information.

+
  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 for the target cluster.
  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-16051.html b/docs/mrs/umn/ALM-16051.html new file mode 100644 index 000000000..13c2b2a2e --- /dev/null +++ b/docs/mrs/umn/ALM-16051.html @@ -0,0 +1,95 @@ + + +

ALM-16051 Percentage of Sessions Connected to MetaStore Exceeds the Threshold

+

Alarm Description

The system checks the percentage of sessions connected to MetaStore to the maximum number of sessions allowed by MetaStore every 30 seconds. This alarm is generated when the percentage exceeds the threshold.

+

This alarm is cleared when the percentage of MetaStore sessions is less than or equal to the threshold.

+

This alarm applies to MRS 3.3.1 or later.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

16051

+

Critical (default threshold: 90%)

+

Major (default threshold: 80%)

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

If this alarm is generated, sessions connected to MetaStore are too many. As a result, new connections cannot be set up.

+
+

Possible Causes

Too many clients are connected to MetaStore.

+
+

Handling Procedure

Change the maximum number of MetaStore connections.

+
  1. On MRS Manager, choose Cluster > Services > Hive, click Configuration and then All Configurations.
  2. In the All Configurations tab, search for hive.metastore.server.max.threads and check whether the value is the maximum 10000.

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

  3. Change the value of hive.metastore.server.max.threads to 10000 and click Save.
  4. Click Instances, select all MetaStore instances, and choose More > Restart Instance.

    During MetaStore instance restart, the instance cannot provide services for external systems. SQL tasks that are being executed on the instance may fail.

    +
    +

  5. Check whether this alarm is cleared.

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

+

Collect fault information.

+
  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 the edit icon in the upper right corner, and set 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 MRS Manager, choose Cluster > Services > Hive. On the displayed Dashboard page, click More and select Collect Stack Information. On the displayed page, set the following parameters:

    • Select MetaStore for the role where you want to collect data.
    • Select jstack and Enable continuous collection of jstack and jmap -histo information.
    • Set the collection interval to 10 seconds and the duration to 2 minutes.
    +

  5. Click OK. After the collection is complete, click Download.
  6. Contact O&M personnel and provide the collected logs.
+
+

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-16052.html b/docs/mrs/umn/ALM-16052.html new file mode 100644 index 000000000..232e1f436 --- /dev/null +++ b/docs/mrs/umn/ALM-16052.html @@ -0,0 +1,97 @@ + + +

ALM-16052 Latency for MetaStore to Access the Meta Database During Table Creation Exceeds the Threshold

+

Alarm Description

The system periodically checks the latency for MetaStore to access the meta database during table creation. This alarm is generated when the average latency in the last 5 minutes exceeds the threshold.

+

This alarm is cleared when the average latency falls below the threshold.

+

This alarm applies to MRS 3.5.0 or later.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

16052

+

Critical (default threshold: 60 seconds)

+

Major (default threshold: 10 seconds)

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

If this alarm is generated, the latency for inserting related table information to the meta database is high during table creation in MetaStore. As a result, calling to MetaStore APIs becomes slow or an error occurs.

+
+

Possible Causes

The MetaStore GC takes a long time or the meta database is abnormal (for example, the disk I/O usage is too high or there are too many long transactions).

+
+

Handling Procedure

Check whether the GC time of MetaStore is too long.

+
  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and check whether alarm Heap Memory Usage of the Hive Process Exceeds the Threshold exists in the alarm list.

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

  2. Rectify the fault by following the handling procedure of ALM-16005 Heap Memory Usage of the Hive Process Exceeds the Threshold.
  3. Check whether the alarm is cleared in the alarm list.

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

+

Check whether the meta database is normal.

+
  1. Contact the administrator of the cluster meta database to check whether the database is normal.

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

  2. Contact the meta database O&M personnel to rectify the fault. After the meta database is restored, check whether the alarm is cleared in the alarm list.

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

+

Collect fault information.

+
  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 the edit icon in the upper right corner, and set 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 MRS Manager, choose Cluster > Services > Hive. On the displayed Dashboard page, click More and select Collect Stack Information. On the displayed page, set the following parameters:

    • Select MetaStore for the role where you want to collect data.
    • Select jstack and Enable continuous collection of jstack and jmap -histo information.
    • Set the collection interval to 10 seconds and the duration to 2 minutes.
    +

  5. Click OK. After the collection is complete, click Download.
  6. Contact O&M personnel and provide the collected logs and stack information.
+
+

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-16053.html b/docs/mrs/umn/ALM-16053.html new file mode 100644 index 000000000..a2fe878c6 --- /dev/null +++ b/docs/mrs/umn/ALM-16053.html @@ -0,0 +1,97 @@ + + +

ALM-16053 Average HQL Submission Time of Hive in the Last 5 Minutes Exceeds the Threshold

+

Alarm Description

The system periodically checks the average HQL submission time, which is the time for calling the MapReduce/Spark/Tez APIs to submit Yarn jobs, including the time for uploading dependent temporary JAR packages and splitting files. This alarm is generated when the average HQL submission time exceeds the threshold.

+

This alarm is cleared when the HQL submission time falls below the threshold.

+

This alarm applies to MRS 3.5.0 or later.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

16053

+

Critical (default threshold: 240 seconds)

+

Major (default threshold: 120 seconds)

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + + + + +

Type

+

Parameter

+

Description

+

Location Information

+

Source

+

Specifies the cluster for which the alarm was generated.

+

ServiceName

+

Specifies the service for which the alarm was generated.

+

RoleName

+

Specifies the role for which the alarm was generated.

+

HostName

+

Specifies the host for which the alarm was generated.

+

Additional Information

+

Trigger Condition

+

Specifies the alarm triggering condition.

+
+
+
+

Impact on the System

If this alarm is generated, the average HQL submission time in the last 5 minutes exceeds the threshold. As a result, the HQL running time is prolonged. Errors may occur in Hive On Spark jobs.

+
+

Possible Causes

The HiveServer GC time is too long or the HDFS NameNode/Router RPC latency is too long.

+
+

Handling Procedure

Check whether the GC time of HiveServer is too long.

+
  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and check whether alarm Heap Memory Usage of the Hive Process Exceeds the Threshold exists in the alarm list.

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

  2. Rectify the fault by following the handling procedure of ALM-16005 Heap Memory Usage of the Hive Process Exceeds the Threshold.
  3. Check whether the alarm is cleared in the alarm list.

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

+

Check whether the HDFS RPC latency is too long.

+
  1. Check whether alarm Average NameNode RPC Processing Time Exceeds the Threshold exists in the alarm list.

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

  2. Rectify the fault by following the handling procedure of ALM-14021 Average NameNode RPC Processing Time Exceeds the Threshold.
  3. Check whether the alarm is cleared in the alarm list.

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

+

Collect fault information.

+
  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 the edit icon in the upper right corner, and set 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 MRS Manager, choose Cluster > Services > Hive. On the displayed Dashboard page, click More and select Collect Stack Information. On the displayed page, set the following parameters:

    • Select HiveServer for the role where you want to collect data.
    • Select jstack and Enable continuous collection of jstack and jmap -histo information.
    • Set the collection interval to 10 seconds and the duration to 2 minutes.
    +

  5. Click OK. After the collection is complete, click Download.
  6. Contact O&M personnel and provide the collected logs and stack information.
+
+

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-17008.html b/docs/mrs/umn/ALM-17008.html new file mode 100644 index 000000000..4e4420b3f --- /dev/null +++ b/docs/mrs/umn/ALM-17008.html @@ -0,0 +1,89 @@ + + +

ALM-17008 Abnormal Connection Between Oozie and ZooKeeper

+

Alarm Description

In HA mode, Oozie depends on ZooKeeper. This alarm is generated when the connection between Oozie and ZooKeeper is abnormal for three consecutive times.

+

This alarm is cleared when the connection between Oozie and ZooKeeper becomes normal.

+

This alarm applies to MRS 3.3.0 or later.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

17008

+

Minor

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + +

Parameter

+

Description

+

Source

+

Specifies the cluster for which the alarm is generated.

+

ServiceName

+

Specifies the service for which the alarm is generated.

+

RoleName

+

Specifies the role for which the alarm is generated.

+

HostName

+

Specifies the host for which the alarm is generated.

+

Trigger Condition

+

Specifies the threshold for triggering the alarm.

+
+
+
+

Impact on the System

Running scheduling tasks are blocked and new scheduling tasks cannot be submitted. In HA mode, the Oozie service will restart if this alarm is reported.

+
+

Possible Causes

  • The ZooKeeper service is abnormal.
  • Oozie fails to connect to ZooKeeper.
+
+

Handling Procedure

Check the ZooKeeper service status.

+
  1. In the service list on MRS Manager, check whether Running Status of ZooKeeper is Normal.

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

  2. In the alarm list, check whether ALM-13000 ZooKeeper Service Unavailable is reported.

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

  3. Rectify the fault by performing the operations provided for ALM-13000 ZooKeeper Service Unavailable.
  4. Wait for several minutes and check whether the alarm Abnormal Connection Between Oozie and ZooKeeper is cleared.

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

+

Check the connectivity between Oozie and ZooKeeper.

+
  1. Log in to MRS Manager, choose O&M > Log > Online Search, select the Oozie service, and search for the keyword [Oozie Alarm Enhancement][ZooKeeper] in the log. View the cause in the log, and rectify the fault. In the alarm list, check whether the alarm Abnormal Connection Between Oozie and ZooKeeper is cleared.

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

+

Collect fault information.

+
  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Select Oozie 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-17009.html b/docs/mrs/umn/ALM-17009.html new file mode 100644 index 000000000..0c6923650 --- /dev/null +++ b/docs/mrs/umn/ALM-17009.html @@ -0,0 +1,89 @@ + + +

ALM-17009 Abnormal Connection Between Oozie and DBService

+

Alarm Description

Oozie depends on DBService. After a task is submitted, the system checks DBService connectivity. This alarm is generated when the service fails the check for 10 consecutive times.

+

This alarm is cleared when the connection between Oozie and DBService becomes normal.

+

This alarm applies to MRS 3.3.0 or later.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

17009

+

Minor

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + +

Parameter

+

Description

+

Source

+

Specifies the cluster for which the alarm is generated.

+

ServiceName

+

Specifies the service for which the alarm is generated.

+

RoleName

+

Specifies the role for which the alarm is generated.

+

HostName

+

Specifies the host for which the alarm is generated.

+

Trigger Condition

+

Specifies the threshold for triggering the alarm.

+
+
+
+

Impact on the System

Running scheduling tasks are blocked and new scheduling tasks cannot be submitted.

+
+

Possible Causes

  • The DBService service is abnormal.
  • Oozie fails to connect to DBService.
+
+

Handling Procedure

Check the DBService status.

+
  1. In the service list on MRS Manager, check whether Running Status of DBService is Normal.

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

  2. In the alarm list, check whether ALM-27001 DBService Service Unavailable is reported.

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

  3. Rectify the fault by performing the operations provided for ALM-27001 DBService Service Unavailable.
  4. Wait for several minutes and check whether the alarm Abnormal Connection Between Oozie and DBService is cleared.

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

+

Check the connectivity between Oozie and DBService.

+
  1. Log in to MRS Manager, choose O&M > Log > Online Search, select the Oozie service, and search for the keyword [Oozie Alarm Enhancement][DB Service] in the log. View the cause in the log, and rectify the fault. In the alarm list, check whether the alarm Abnormal Connection Between Oozie and DBService is cleared.

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

+

Collect fault information.

+
  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Select Oozie 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-17010.html b/docs/mrs/umn/ALM-17010.html new file mode 100644 index 000000000..3db950cd1 --- /dev/null +++ b/docs/mrs/umn/ALM-17010.html @@ -0,0 +1,89 @@ + + +

ALM-17010 Abnormal Connection Between Oozie and HDFS

+

Alarm Description

Oozie depends on HDFS. After a task is submitted, the system checks HDFS connectivity. This alarm is generated when the service fails the check for 3 consecutive times.

+

This alarm is cleared when the connection between Oozie and HDFS becomes normal.

+

This alarm applies to MRS 3.3.0 or later.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

17010

+

Minor

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + +

Parameter

+

Description

+

Source

+

Specifies the cluster for which the alarm is generated.

+

ServiceName

+

Specifies the service for which the alarm is generated.

+

RoleName

+

Specifies the role for which the alarm is generated.

+

HostName

+

Specifies the host for which the alarm is generated.

+

Trigger Condition

+

Specifies the threshold for triggering the alarm.

+
+
+
+

Impact on the System

Running scheduling tasks are blocked and new scheduling tasks cannot be submitted.

+
+

Possible Causes

The HDFS service restarts, there is a fault, or the network connectivity is abnormal.

+
+

Handling Procedure

Check the HDFS service status.

+
  1. In the service list on MRS Manager, check whether Running Status of HDFS is Normal.

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

  2. In the alarm list, check whether the "ALM-14000 HDFS Service Unavailable" alarm is generated.

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

  3. Rectify the fault by performing the operations provided for ALM-14000 HDFS Service Unavailable.
  4. Wait for several minutes and check whether the alarm Abnormal Connection Between Oozie and HDFS is cleared.

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

+

Check the connectivity between Oozie and HDFS.

+
  1. Log in to MRS Manager, choose O&M > Log > Online Search, select the Oozie service, and search for the keyword [Oozie Alarm Enhancement][HDFS] in the log. View the cause in the log, and rectify the fault. In the alarm list, check whether the alarm Abnormal Connection Between Oozie and HDFS is cleared.

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

+

Collect fault information.

+
  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Select Oozie 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-17011.html b/docs/mrs/umn/ALM-17011.html new file mode 100644 index 000000000..44823f485 --- /dev/null +++ b/docs/mrs/umn/ALM-17011.html @@ -0,0 +1,89 @@ + + +

ALM-17011 Abnormal Connection Between Oozie and YARN

+

Alarm Description

Oozie depends on YARN. After a task is submitted, the system checks YARN connectivity. This alarm is generated when the service fails the check for 5 consecutive times.

+

This alarm is cleared when the connection between Oozie and YARN becomes normal.

+

This alarm applies to MRS 3.3.0 or later.

+
+

Alarm Attributes

+
+ + + + + + + + + +

Alarm ID

+

Alarm Severity

+

Auto Cleared

+

17011

+

Minor

+

Yes

+
+
+
+

Alarm Parameters

+
+ + + + + + + + + + + + + + + + + + + +

Parameter

+

Description

+

Source

+

Specifies the cluster for which the alarm is generated.

+

ServiceName

+

Specifies the service for which the alarm is generated.

+

RoleName

+

Specifies the role for which the alarm is generated.

+

HostName

+

Specifies the host for which the alarm is generated.

+

Trigger Condition

+

Specifies the threshold for triggering the alarm.

+
+
+
+

Impact on the System

Running scheduling tasks are blocked and new scheduling tasks cannot be submitted.

+
+

Possible Causes

  • The Yarn service is abnormal.
  • The connection between Oozie and Yarn is abnormal.
+
+

Handling Procedure

Check the YARN service status.

+
  1. In the service list on MRS Manager, check whether Running Status of Yarn is Normal.

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

  2. In the alarm list, check whether ALM-18000 YARN Service Unavailable is generated.

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

  3. Rectify the fault by performing the operations provided for ALM-18000 YARN Service Unavailable.
  4. Wait for several minutes and check whether the alarm Abnormal Connection Between Oozie and Yarn is cleared.

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

+

Check the connectivity between Oozie and Yarn.

+
  1. Log in to MRS Manager, choose O&M > Log > Online Search, select the Oozie service, and search for the keyword [Oozie Alarm Enhancement][Yarn] in the log. View the cause in the log, and rectify the fault. In the alarm list, check whether the alarm Abnormal Connection Between Oozie and Yarn is cleared.

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

+

Collect fault information.

+
  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Select Oozie 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 Clearance

This alarm is automatically cleared after the fault is rectified.

+
+

Related Information

None.

+
+
+ + diff --git a/docs/mrs/umn/ALM-19022.html b/docs/mrs/umn/ALM-19022.html index 6887f62c1..1f273aef1 100644 --- a/docs/mrs/umn/ALM-19022.html +++ b/docs/mrs/umn/ALM-19022.html @@ -62,17 +62,17 @@

Possible Causes

  • The ZooKeeper service is abnormal.
  • The HBase service is abnormal.
  • In the current HBase service, the MetricController instance on the same node as the active HMaster instance is not started.
  • The network is abnormal.

Handling Procedure

Check the ZooKeeper service status.

-
  1. In the service list on FusionInsight Manager, check whether Running Status of ZooKeeper is Normal.

    • If yes, go to 5.
    • If no, go to 2.
    +
    1. In the service list on MRS Manager, check whether Running Status of ZooKeeper is Normal.

      • 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 performing the operations provided for ALM-13000 ZooKeeper Service Unavailable.
    4. Wait for several minutes and check whether the alarm HBase Hotspot Detection Is Unavailable is cleared.

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

    Check the HBase service status.

    -
    1. In the service list on FusionInsight Manager, check whether Running Status of HBase is Normal.

      • If yes, go to 9.
      • If no, go to 6.
      +
      1. In the service list on MRS Manager, check whether Running Status of HBase is Normal.

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

      2. In the alarm list, check whether the alarm ALM-19000 HBase Service Unavailable exists.

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

      3. Rectify the fault by following the steps provided for ALM-19000 HBase Service Unavailable.
      4. Wait for several minutes and check whether the alarm HBase Hotspot Detection Is Unavailable is cleared.

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

      Check whether the MetricController instance deployed on the same node as the active HMaster instance is started.

      -
      1. On FusionInsight Manager, choose Cluster > Service > HBase, and click Instances to check whether the MetricController(Active) instance exists.

        • If yes, go to 12.
        • If no, go to 10.
        +
        1. On MRS Manager, choose Cluster > Service > HBase, and click Instances to check whether the MetricController(Active) instance exists.

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

        2. Select the MetricController instance whose management IP address is the same as that of the active HMaster instance, and click Start Instance.
        3. After the MetricController instance is restarted, check whether the alarm HBase Hotspot Detection Is Unavailable is cleared.

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

        Check the network connectivity between the started MetricController instances and the active HMaster node.

        @@ -80,7 +80,7 @@

      2. Contact the network administrator to restore the network.
      3. After the network recovers, check whether the alarm HBase Hotspot Detection Is Unavailable is cleared.

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

      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 HBase for the target cluster.
      3. In the Host area, select the host where the HMaster instance is deployed.
      4. Click the edit icon in the upper right corner, and 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. 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. In the Host area, select the host where the HMaster instance is deployed.
      4. Click the edit icon in the upper right corner, and 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-19023.html b/docs/mrs/umn/ALM-19023.html index 7b4e40062..f9a81e30d 100644 --- a/docs/mrs/umn/ALM-19023.html +++ b/docs/mrs/umn/ALM-19023.html @@ -61,10 +61,10 @@

Possible Causes

Too many requests are directed to a single region when the HBase service is accessed.

Handling Procedure

Check whether there are too many requests in a single region of HBase.

-
  1. Log in to FusionInsight Manager, and Choose O&M > Alarm > Alarms.
  2. In Additional Information of Region Traffic Restriction for HBase, view the reported table name and region information.
  3. On FusionInsight Manager, choose Cluster > Service > HBase and click the hyperlink on the right of HMaster web UI.
  4. Click Table Details and adjust service configurations in the region where the table in 2 is deployed.
  5. Wait a moment and then check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 6.
    +
    1. Log in to MRS Manager, and Choose O&M > Alarm > Alarms.
    2. In Additional Information of Region Traffic Restriction for HBase, view the reported table name and region information.
    3. On MRS Manager, choose Cluster > Service > HBase and click the hyperlink on the right of HMaster web UI.
    4. Click Table Details and adjust service configurations in the region where the table in 2 is deployed.
    5. Wait a moment and then 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. 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. In the Host area, select the host where the HMaster instance is deployed.
    4. Click the edit icon in the upper right corner, and 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. 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. In the Host area, select the host where the HMaster instance is deployed.
    4. Click the edit icon in the upper right corner, and 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 Clearance

This alarm will be automatically cleared.

diff --git a/docs/mrs/umn/ALM-19024.html b/docs/mrs/umn/ALM-19024.html index 4d48d9f17..17f8c4997 100644 --- a/docs/mrs/umn/ALM-19024.html +++ b/docs/mrs/umn/ALM-19024.html @@ -65,21 +65,21 @@

Possible Causes

  • RegionServer GC duration is too long.
  • The HDFS RPC response is too slow.
  • RegionServer request concurrency is too high.
-

Handling Procedure

  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 19024, and view the service instance and host name in Location.
+

Handling Procedure

  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 19024, and view the service instance and host name in Location.

Check the GC duration of RegionServer.

-
  1. In the alarm list on FusionInsight Manager, check whether the "HBase GC Duration Exceeds the Threshold" alarm is generated for the service instance in 1.

    • If yes, go to 3.
    • If no, go to 5.
    +
    1. In the alarm list on MRS Manager, check whether the "HBase GC Duration Exceeds the Threshold" alarm is generated for the service instance in 1.

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

    2. Rectify the fault by following the handling procedure of "ALM-19007 HBase GC Duration Exceeds the Threshold".
    3. Wait several minutes and check whether the alarm is cleared.

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

    Check HDFS RPC response time.

    -
    1. In the alarm list on FusionInsight Manager, check whether alarm "Average NameNode RPC Processing Time Exceeds the Threshold" is generated for the HDFS service on which the HBase service depends.

      • If yes, go to 6.
      • If no, go to 8.
      +
      1. In the alarm list on MRS Manager, check whether alarm "Average NameNode RPC Processing Time Exceeds the Threshold" is generated for the HDFS service on which the HBase service depends.

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

      2. Rectify the fault by following the handling procedure of "ALM-14021 Average NameNode RPC Processing Time Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      Check the number of concurrent processes on a RegionServer.

      -
      1. In the alarm list on FusionInsight Manager, check whether the "Handler Usage of RegionServer Exceeds the Threshold" alarm is generated for the service instance in 1.

        • If yes, go to 9.
        • If no, go to 11.
        +
        1. In the alarm list on MRS Manager, check whether the "Handler Usage of RegionServer Exceeds the Threshold" alarm is generated for the service instance in 1.

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

        2. Rectify the fault by following the handling procedure of "ALM-19021 Handler Usage of RegionServer Exceeds the Threshold".
        3. Wait several 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 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 the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

This alarm is automatically cleared after the fault is rectified.

diff --git a/docs/mrs/umn/ALM-19025.html b/docs/mrs/umn/ALM-19025.html index 009acdb32..3c9cfba1e 100644 --- a/docs/mrs/umn/ALM-19025.html +++ b/docs/mrs/umn/ALM-19025.html @@ -4,7 +4,7 @@

Alarm Description

The system checks the hdfs://hacluster/hbase/autocorrupt and hdfs://hacluster/hbase/MasterData/autocorrupt directories on HDFS of each HBase service every 120 seconds. This alarm is generated when there are files in the directories.

This alarm is cleared when the hdfs://hacluster/hbase/autocorrupt and hdfs://hacluster/hbase/MasterData/autocorrupt directories do not exist or are empty.

This alarm applies only to MRS 3.3.0 or later.

-

hdfs://hacluster indicates the name of the file system used by HBase, and /hbase indicates the root directory of HBase in the file system. You can log in to FusionInsight Manager, choose Cluster > Services > HBase and click Configuration. Search for fs.defaultFS and hbase.data.rootdir.

+

hdfs://hacluster indicates the name of the file system used by HBase, and /hbase indicates the root directory of HBase in the file system. You can log in to MRS Manager, choose Cluster > Services > HBase and click Configuration. Search for fs.defaultFS and hbase.data.rootdir.

Alarm Attributes

@@ -62,7 +62,7 @@

Possible Causes

The StoreFile files are damaged.

-

Handling Procedure

  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 19025, and view the service in Location.
  2. Log in to the node where the HDFS and HBase clients are installed as the client installation user and run the following commands:

    cd Client installation directory

    +

    Handling Procedure

    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 19025, and view the service in Location.
    2. Log in to the node where the HDFS and HBase clients are installed as the client installation user and run the following commands:

      cd Client installation directory

      source bigdata_env

      kinit Component service user (If Kerberos authentication is disabled for the cluster (the cluster is in normal mode), skip this step.)

    3. Check the damaged StoreFile file.

      • Run the following command to check whether the /hbase/autocorrupt directory of HDFS is empty. If it is not, go to 4.

        hdfs dfs -ls -R hdfs://hacluster/hbase/autocorrupt

        @@ -79,7 +79,7 @@

      • Wait several 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 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 the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

    This alarm is automatically cleared after the fault is rectified.

    diff --git a/docs/mrs/umn/ALM-19026.html b/docs/mrs/umn/ALM-19026.html index ba02af62b..8e9b555db 100644 --- a/docs/mrs/umn/ALM-19026.html +++ b/docs/mrs/umn/ALM-19026.html @@ -4,7 +4,7 @@

    Alarm Description

    The system checks the hdfs://hacluster/hbase/corrupt directory on the HDFS of each HBase service every 120 seconds. This alarm is generated when there are WAL files in the /hbase/corrupt directory.

    This alarm is cleared when the /hbase/corrupt directory does not exist or does not contain WAL files.

    This alarm applies only to MRS 3.3.0 or later.

    -

    hdfs://hacluster indicates the name of the file system used by HBase, and /hbase indicates the root directory of HBase in the file system. You can log in to FusionInsight Manager, choose Cluster > Services > HBase and click Configuration. Search for fs.defaultFS and hbase.data.rootdir.

    +

    hdfs://hacluster indicates the name of the file system used by HBase, and /hbase indicates the root directory of HBase in the file system. You can log in to MRS Manager, choose Cluster > Services > HBase and click Configuration. Search for fs.defaultFS and hbase.data.rootdir.

    Alarm Attributes

    @@ -62,13 +62,13 @@

    Possible Causes

    The WAL files are damaged.

    -

    Handling Procedure

    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 19026, and view the service in Location.
    2. Log in to the node where the HDFS clients are installed as the client installation user and run the following commands:

      cd Client installation directory

      +

      Handling Procedure

      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 19026, and view the service in Location.
      2. Log in to the node where the HDFS clients are installed as the client installation user and run the following commands:

        cd Client installation directory

        source bigdata_env

        kinit Component service user (If Kerberos authentication is disabled for the cluster (the cluster is in normal mode), skip this step.)

      3. Run the following command to check the damaged WAL files and go to 4:

        hdfs dfs -ls hdfs://hacluster/hbase/corrupt/*%2C*

      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 HBase for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-19030.html b/docs/mrs/umn/ALM-19030.html new file mode 100644 index 000000000..8014495bf --- /dev/null +++ b/docs/mrs/umn/ALM-19030.html @@ -0,0 +1,102 @@ + + +

      ALM-19030 P99 Latency of RegionServer RPC Request Exceeds the Threshold

      +

      Alarm Description

      The system checks the P99 latency for responding to RPC requests on each RegionServer instance of the HBase service every 30 seconds. This alarm is generated when P99 latency on a RegionServer instance exceeds the threshold for 10 consecutive times.

      +

      This alarm is cleared when the P99 latency on a RegionServer instance is less than or equal to the threshold.

      +

      This alarm is generated only for MRS 3.3.1 or later.

      +
      +

      Alarm Attributes

      +
      + + + + + + + + + +

      Alarm ID

      +

      Alarm Severity

      +

      Auto Cleared

      +

      19030

      +
      • Critical: The default threshold is 10 seconds.
      • Major: The default threshold is 5 seconds.
      +

      Yes

      +
      +
      +
      +

      Alarm Parameters

      +
      + + + + + + + + + + + + + + + + + + + + + + +

      Type

      +

      Parameter

      +

      Description

      +

      Location Information

      +

      Source

      +

      Specifies the cluster for which the alarm was generated.

      +

      ServiceName

      +

      Specifies the service for which the alarm was generated.

      +

      RoleName

      +

      Specifies the role for which the alarm was generated.

      +

      HostName

      +

      Specifies the host for which the alarm was generated.

      +

      Additional Information

      +

      Threshold

      +

      Specifies the threshold for generating the alarm.

      +
      +
      +
      +

      Impact on the System

      The RegionServer's capability of providing services for external systems is affected. For latency-sensitive services, a large number of service read and write requests may time out.

      +
      +

      Possible Causes

      • RegionServer GC duration is too long.
      • The HDFS RPC response is too slow.
      • The client requests are at scale with high concurrency.
      +
      +

      Handling Procedure

      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 19030, and view the service instance and host name in Location. Click the host name and record the service IP address of the host.
      +

      Check the GC duration of the RegionServer.

      +
      1. In the alarm list on MRS Manager, check whether the "HBase GC Duration Exceeds the Threshold" alarm is generated for the service instance in 1.

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

      2. Rectify the fault by following the handling procedure of "ALM-19007 HBase GC Duration Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check HDFS RPC response time.

      +
      1. In the alarm list on MRS Manager, check whether an alarm is generated for the DataNode instance of the HDFS service on which HBase depends, or whether the alarm "Slow Disk Fault", "Disk Unavailable", or "Average NameNode RPC Processing Time Exceeds the Threshold" is generated on the node where the alarm is generated.

        • If yes, go to 6.
        • If no, go to 8.
        +

      2. Rectify the fault by following the handling procedure of the DataNode alarms: "ALM-12033 Slow Disk Fault", "ALM-12063 Disk Unavailable", or "ALM-14021 Average NameNode RPC Processing Time Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      4. Log in to the node for which the alarm is generated, run the iostat -x 2 command to check the disk I/O. In the command output, check whether the value in the util column of each disk is greater than 90%.

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

      5. Choose Cluster > Services > HDFS > Instances, select the DataNode instance of the node for which the alarm is generated, choose More > Stop Instance, enter the password of the current user, and click OK to stop the DataNode instance.
      6. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the number of concurrent processes on a RegionServer.

      +
      1. In the alarm list on MRS Manager, check whether the "Handler Usage of RegionServer Exceeds the Threshold" alarm is generated for the service instance in 1.

        • If yes, go to 12.
        • If no, go to 14.
        +

      2. Rectify the fault by following the handling procedure of "ALM-19021 Handler Usage of RegionServer Exceeds the Threshold".
      3. Wait several 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 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 the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      +
      +

      Related Information

      None.

      +
      +
      + + diff --git a/docs/mrs/umn/ALM-19031.html b/docs/mrs/umn/ALM-19031.html new file mode 100644 index 000000000..2a48101a8 --- /dev/null +++ b/docs/mrs/umn/ALM-19031.html @@ -0,0 +1,98 @@ + + +

      ALM-19031 Number of RegionServer RPC Connections Exceeds the Threshold

      +

      Alarm Description

      The system checks the number of RegionServer RPC connections in each HBase service every 30 seconds. This alarm is generated when the number of RPC connections of a RegionServer instance exceeds the threshold for 10 consecutive times.

      +

      This alarm is cleared when the number of RPC connections of a RegionServer instance is less than or equal to the threshold.

      +

      This alarm is generated only for MRS 3.3.1 or later.

      +
      +

      Alarm Attributes

      +
      + + + + + + + + + +

      Alarm ID

      +

      Alarm Severity

      +

      Auto Cleared

      +

      19031

      +
      • Critical (default threshold: 2000)
      • Major (default threshold: 1000)
      +

      Yes

      +
      +
      +
      +

      Alarm Parameters

      +
      + + + + + + + + + + + + + + + + + + + + + + +

      Type

      +

      Parameter

      +

      Description

      +

      Location Information

      +

      Source

      +

      Specifies the cluster for which the alarm was generated.

      +

      ServiceName

      +

      Specifies the service for which the alarm was generated.

      +

      RoleName

      +

      Specifies the role for which the alarm was generated.

      +

      HostName

      +

      Specifies the host for which the alarm was generated.

      +

      Additional Information

      +

      Threshold

      +

      Specifies the threshold for generating the alarm.

      +
      +
      +
      +

      Impact on the System

      There are a large amount of concurrent access requests on the RegionServer node, which imposes great pressure and causes slow response. For latency-sensitive services, a large number of service read and write requests may time out.

      +
      +

      Possible Causes

      Too many concurrent requests are sent from applications to access HBase.

      +
      +

      Handling Procedure

      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 19031, and view the service instance and host name in Location.
      +

      Check the number of concurrent requests accessing HBase.

      +
      1. Log in to the node where the HBase client is installed and check whether hbase.client.ipc.pool.size in the Client installation directory/HBase/hbase/conf/hbase-site.xml file is set to a value greater than 5.

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

      2. Decrease the value of hbase.client.ipc.pool.size and save the change.
      3. Wait several minutes and check whether the alarm is cleared.

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

      4. Check whether the number of concurrent requests accessing the HBase service is too large.

        • If yes, go to 6.
        • If no, go to 8.
        +

        The number of concurrent HBase API calls by all applications must be less than or equal to the following value:

        +

        Number of RegionServer instances x Maximum number of handlers of a single RegionServer

        +

        To obtain the number of RegionServer instances, log in to Manager and choose Cluster > Services > HBase > Instances. To obtain the maximum number of handlers of a single RegionServer, click Configurations and search for the hbase.regionserver.handler.count parameter.

        +
        +

      1. Contact the upper-layer service support personnel to decrease the concurrent requests based on actual service requirements.
      2. Wait several minutes and check whether the alarm is cleared.

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

      +

      Collect fault information.

      +
      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 the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      +
      +

      Related Information

      None.

      +
      +
      + + diff --git a/docs/mrs/umn/ALM-19032.html b/docs/mrs/umn/ALM-19032.html new file mode 100644 index 000000000..09d5cf8b4 --- /dev/null +++ b/docs/mrs/umn/ALM-19032.html @@ -0,0 +1,124 @@ + + +

      ALM-19032 Number of Tasks in the RegionServer RPC Write Queue Exceeds the Threshold

      +

      Alarm Description

      The system checks the number of tasks waiting in the RPC write queue for the RegionServer instances of the HBase service every 30 seconds. This alarm is generated when the number of waiting tasks exceeds the threshold for 10 consecutive times.

      +

      This alarm is cleared when the number of waiting tasks is less than or equal to the threshold.

      +

      This alarm is generated only for MRS 3.3.1 or later.

      +
      +

      Alarm Attributes

      +
      + + + + + + + + + +

      Alarm ID

      +

      Alarm Severity

      +

      Auto Cleared

      +

      19032

      +
      • Critical (default threshold: 2000)
      • Major (default threshold: 1600)
      +

      Yes

      +
      +
      +
      +

      Alarm Parameters

      +
      + + + + + + + + + + + + + + + + + + + + + + +

      Type

      +

      Parameter

      +

      Description

      +

      Location Information

      +

      Source

      +

      Specifies the cluster for which the alarm was generated.

      +

      ServiceName

      +

      Specifies the service for which the alarm was generated.

      +

      RoleName

      +

      Specifies the role for which the alarm was generated.

      +

      HostName

      +

      Specifies the host for which the alarm was generated.

      +

      Additional Information

      +

      Threshold

      +

      Specifies the threshold for generating the alarm.

      +
      +
      +
      +

      Impact on the System

      Request queues are stacked, and the RegionServer memory GC pressure increases. As a result, the response time of write requests increases. For latency-sensitive services, a large number of service write requests may time out.

      +
      +

      Possible Causes

      • The RegionServer heap memory configuration is improper.
      • A slow disk fault occurred.
      • The RegionServer configuration is improper.
      • Regions of RegionServers are not evenly distributed and hotspotting occurred.
      • The latency of WAL Sync operations is high.
      +
      +

      Handling Procedure

      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 19032, and view the service instance and host name in Location.
      +

      Check RegionServer heap memory.

      +
      1. In the alarm list on MRS Manager, check whether the "Heap Memory Usage of the HBase Process Exceeds the Threshold" alarm is generated for the service instance in 1.

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

      2. Rectify the fault by following the handling procedure of "ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      4. On MRS Manager, choose Cluster > Services > HBase > Chart, select GC from the chart category, and check whether the GC times and GC monitoring period are normal.

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

      5. Click Configurations, search for GC_OPTS, and increase the value of Xmx of the RegionServer within the allowed memory range. Set the value to a number less than or equal to 31 GB. Click Save.
      6. Click Dashboard and click More > Restart Service to restart the HBase service.
      7. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check for slow disk fault.

      +
      1. Check whether alarm "Slow Disk Fault" or "Disk Unavailable" are generated on the node you checked in 1.

        • If yes, go to 10.
        • If no, go to 12.
        +

      1. Rectify the fault by following the handling procedure of "ALM-12033 Slow Disk Fault" or "ALM-12063 Disk Unavailable".
      2. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the RegionServer configuration.

      +
      1. On MRS Manager, choose Cluster > Service > HBase, click Configurations > All Configurations, and check whether the values of hbase.wal.hsync and hbase.hfile.hsync are true.

        • If yes, go to 13.
        • If no, go to 15.
        +

      2. Set both hbase.wal.hsync and hbase.hfile.hsync to false and click Save. Click Dashboard and click More > Restart Service to restart the HBase service.

        During HBase service restart, the service is unavailable. For example, data cannot be read or written, table operations cannot be performed, and the HBase web UI is inaccessible.

        +
        +

      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check whether RegionServer regions are evenly distributed.

      +
      1. On MRS Manager, choose Cluster > Services > HBase. Click HMaster(Active) on the right of HMaster Web UI to go to the web UI of the HBase instance. View the Base Stats tab in the Region Servers area. Check whether the number of regions in the Num.Regions column is even.

        • If yes, go to 20.
        • If no, go to 16.
        +

        +

      2. Log in to the node where the HBase client is deployed as the omm user.
      3. Run the following commands to go to the client installation directory and set the environment variable:

        cd Client installation directory

        +

        source bigdata_env

        +

        kinit the supergroup user group or a user with the Global Admin permission (If Kerberos authentication is disabled for the cluster, skip this operation.)

        +

      1. Run the following commands to enable HBase load balancing and check whether the function is successfully enabled:

        hbase shell

        +

        balance_switch true

        +

        balancer_enabled

        +

        If the command output is true, load balancing is enabled.

        +
        Run the balancer command to manually trigger the load balancing function.

        You are advised to enable and trigger load balancing during off-peak hours.

        +
        +
        +

      2. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the WAL sync latency.

      +
      1. On MRS Manager, choose Cluster > Services > HBase > Chart. In the Chart Category area, select Operations. Check whether the value of "P99.9th Percentile of WAL Sync Operation Delay-All Instances" exceeds 500 ms.

        • If yes, go to 21.
        • If no, go to 22.
        +

      1. Click Instances, select the RegionServer instance for which the alarm is generated, and choose More > Restart Instance. You also need to perform 22 and provide the logs to O&M personnel for fault locating.

        During RegionServer restart, client requests will be retried for multiple times. Read and write operations are affected for a short period of time.

        +
        +

      +

      Collect fault information.

      +
      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 the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      +
      +

      Related Information

      None.

      +
      +
      + + diff --git a/docs/mrs/umn/ALM-19033.html b/docs/mrs/umn/ALM-19033.html new file mode 100644 index 000000000..6f1b0eb33 --- /dev/null +++ b/docs/mrs/umn/ALM-19033.html @@ -0,0 +1,132 @@ + + +

      ALM-19033 Number of Tasks in the RegionServer RPC Read Queue Exceeds the Threshold

      +

      Alarm Description

      The system checks the number of tasks waiting in the RPC read queue for the RegionServer instances of the HBase service every 30 seconds. This alarm is generated when the number of waiting tasks exceeds the threshold for 10 consecutive times.

      +

      This alarm is cleared when the number of waiting tasks is less than or equal to the threshold.

      +

      This alarm applies only to MRS 3.3.1 or later.

      +
      +

      Alarm Attributes

      +
      + + + + + + + + + +

      Alarm ID

      +

      Alarm Severity

      +

      Auto Cleared

      +

      19033

      +
      • Critical (default threshold: 2000)
      • Major (default threshold: 1600)
      +

      Yes

      +
      +
      +
      +

      Alarm Parameters

      +
      + + + + + + + + + + + + + + + + + + + + + + +

      Type

      +

      Parameter

      +

      Description

      +

      Location Information

      +

      Source

      +

      Specifies the cluster for which the alarm was generated.

      +

      ServiceName

      +

      Specifies the service for which the alarm was generated.

      +

      RoleName

      +

      Specifies the role for which the alarm was generated.

      +

      HostName

      +

      Specifies the host for which the alarm was generated.

      +

      Additional Information

      +

      Threshold

      +

      Specifies the threshold for generating the alarm.

      +
      +
      +
      +

      Impact on the System

      Request queues are stacked, and the response time of read requests increases. For latency-sensitive services, a large number of service read requests may time out.

      +
      +

      Possible Causes

      • The RegionServer heap memory configuration is improper.
      • The RegionServer configuration is improper.
      • Regions of RegionServers are unevenly distributed, and read hotspotting occurred.
      • A slow disk fault occurred.
      +
      +

      Handling Procedure

      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 19033, and view the service instance and host name in Location.
      +

      Check the heap memory configuration.

      +
      1. In the alarm list on MRS Manager, check whether the "Heap Memory Usage of the HBase Process Exceeds the Threshold" alarm is generated for the service instance in 1.

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

      2. Rectify the fault by following the handling procedure of "ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      4. On MRS Manager, choose Cluster > Services > HBase > Chart, select GC from the chart category, and check whether the GC times and GC monitoring period are normal.

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

      1. Click Configurations, search for GC_OPTS, and increase the value of Xmx of the RegionServer within the allowed memory range. Set the value to a number less than or equal to 31 GB. Click Save.

        On MRS Manager, choose Cluster > Services > HBase > Instances and obtain the hostnames of all nodes where RegionServer resides. Go back to the MRS Manager homepage and choose Hosts. In the host list, view the Memory(GB) values of all nodes where RegionServer resides and check the remaining memory of each host. Increase the value of Xmx based on the minimum remaining memory, and ensure that the used memory of each node does not exceed 80% after the adjustment.

        +
        +

      2. Click Dashboard and click More > Restart Service to restart the HBase service.

        During HBase service restart, the service is unavailable. For example, data cannot be read or written, table operations cannot be performed, and the HBase web UI is inaccessible.

        +
        +

      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the RegionServer configuration.

      +
      1. On MRS Manager, choose Cluster > Services > HBase, click Configurations > All Configurations, and check whether hbase.bucketcache.size is properly set. A larger value indicates a larger read cache and higher read performance. Increase the value based on the remaining memory of the node and click Save. Click Dashboard and click More > Restart Service to restart the HBase service.
      2. Wait several minutes and check whether the alarm is cleared.

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

      1. On the HBase dashboard, click the hyperlink on the right of HMaster Web UI. In the User Tables tab in the Tables area, click the name of the table hit by a large number of user read requests. In the Table Schema area of the Table tab, check whether the value of BLOCKCACHE is false.

        • If yes, go to 12.
        • If no, go to 14.
        +

        +

      2. Log in to the node where the HBase client is installed as user omm. Run the following commands to change the value of BLOCKCACHE of the 11 table column family to true:

        cd Client installation directory

        +

        source bigdata_env

        +

        kinit the supergroup user group or a user with the Global Admin permission (If Kerberos authentication is disabled for the cluster, skip this operation.)

        +

        hbase shell

        +

        alter'Table name', {NAME =>'Column family name', BLOCKCACHE => true}

        +

        Run the following command to check whether the value of BLOCKCACHE of the column family is changed to true:

        +

        describe'Table name'

        +

      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check whether regions of RegionServers are evenly distributed.

      +
      1. On MRS Manager, choose Cluster > Services > HBase and click HMaster(Active). On the HBase web UI, check whether regions are evenly distributed in the Num.Regions column in the Base Stats tab in the Region Servers area.

        • If yes, go to 20.
        • If no, go to 15.
        +

        +

      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

        +

        kinit the supergroup user group or a user with the Global Admin permission (If Kerberos authentication is disabled for the cluster, skip this operation.)

        +

      4. Run the following commands to check whether the load balancing function is enabled:

        hbase shell

        +

        balancer_enabled

        +
        If the command output is true, load balancing is enabled.
        • If yes, go to 20.
        • If no, go to 18.
        +
        +

      5. Run the following commands to enable load balancing and check whether the function is successfully enabled:

        balance_switch true

        +

        balancer_enabled

        +
        Run the balancer command to manually trigger the load balancing function.

        You are advised to enable and trigger load balancing during off-peak hours.

        +
        +
        +

      1. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check for slow disk fault.

      +
      1. Check whether alarm "Slow Disk Fault" or "Disk Unavailable" are generated on the node in 1.

        • If yes, go to 21.
        • If no, go to 23.
        +

      1. Rectify the fault by following the handling procedure of "ALM-12033 Slow Disk Fault" or "ALM-12063 Disk Unavailable".
      2. Wait several minutes and check whether the alarm is cleared.

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

      +

      Collect fault information.

      +
      1. On MRS Manager, choose Cluster > Services > HBase > Chart, select IO from the Chart Category area, and view the values of Maximum Pread Latency-All Instances and Maximum Read Latency-All Instances. Normal values do not exceed 100 ms.
      2. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
      3. Expand the Service drop-down list, and select HBase for the target cluster.
      4. Click the edit icon in the upper right corner, and 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      +
      +

      Related Information

      None.

      +
      +
      + + diff --git a/docs/mrs/umn/ALM-19034.html b/docs/mrs/umn/ALM-19034.html new file mode 100644 index 000000000..2506cbcc9 --- /dev/null +++ b/docs/mrs/umn/ALM-19034.html @@ -0,0 +1,106 @@ + + +

      ALM-19034 Number of RegionServer WAL Write Timeouts Exceeds the Threshold

      +

      Alarm Description

      The system checks the number of RegionServer WAL write timeouts in each HBase service every 30 seconds. This alarm is generated when the number of WAL write timeouts on a RegionServer instance exceeds the threshold for 10 consecutive times.

      +

      This alarm is cleared when the number of WAL write timeouts on a RegionServer instance is less than or equal to the threshold.

      +

      This alarm applies only to MRS 3.3.1 or later.

      +
      +

      Alarm Attributes

      +
      + + + + + + + + + +

      Alarm ID

      +

      Alarm Severity

      +

      Auto Cleared

      +

      19034

      +
      • Critical (default threshold: 500)
      • Major (default threshold: 300)
      +

      Yes

      +
      +
      +
      +

      Alarm Parameters

      +
      + + + + + + + + + + + + + + + + + + + + + + +

      Type

      +

      Parameter

      +

      Description

      +

      Location Information

      +

      Source

      +

      Specifies the cluster for which the alarm was generated.

      +

      ServiceName

      +

      Specifies the service for which the alarm was generated.

      +

      RoleName

      +

      Specifies the role for which the alarm was generated.

      +

      HostName

      +

      Specifies the host for which the alarm was generated.

      +

      Additional Information

      +

      Threshold

      +

      Specifies the threshold for generating the alarm.

      +
      +
      +
      +

      Impact on the System

      The write operation latency increases. Too many WAL write timeouts may severely deteriorate the data write performance.

      +
      +

      Possible Causes

      • A slow disk fault occurred.
      • RegionServer GC is abnormal.
      • HBase is overloaded.
      • The WAL configuration is improper.
      +
      +

      Handling Procedure

      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 19034, and view the service instance and host name in Location.
      +

      Check whether a slow disk fault occurred.

      +
      1. In the alarm list on MRS Manager, check whether the "Slow Disk Fault" or "Disk Unavailable" is displayed for the instance you checked in 1.

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

      2. Rectify the fault by following the handling procedure of "ALM-12033 Slow Disk Fault" or "ALM-12063 Disk Unavailable".
      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check whether RegionServer GC is abnormal.

      +
      1. In the alarm list on MRS Manager, check whether "ALM-19007 HBase GC Duration Exceeds the Threshold" is displayed.

        • If yes, go to 6.
        • If no, go to 8.
        +

      2. Rectify the fault by following the handling procedure of "ALM-19007 HBase GC Duration Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the HBase load.

      +
      1. In the alarm list on MRS Manager, check whether "ALM-19018 HBase Compaction Queue Size Exceeds the Threshold" is displayed.

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

      2. Rectify the fault by following the handling procedure of "ALM-19018 HBase Compaction Queue Size Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the WAL configuration.

      +
      1. On MRS Manager, choose Cluster > Service > HBase, click Configurations > All Configurations, and check whether the values of hbase.wal.hsync and hbase.hfile.hsync are true.

        • If yes, go to 12.
        • If no, go to 14.
        +

      2. Set both hbase.wal.hsync and hbase.hfile.hsync to false and click Save. Click Dashboard and click More > Restart Service to restart the HBase service.

        During HBase service restart, the service is unavailable. For example, data cannot be read or written, table operations cannot be performed, and the HBase web UI is inaccessible.

        +
        +

      3. Wait several 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 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 the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      +
      +

      Related Information

      None.

      +
      +
      + + diff --git a/docs/mrs/umn/ALM-19035.html b/docs/mrs/umn/ALM-19035.html new file mode 100644 index 000000000..11d2c2c7a --- /dev/null +++ b/docs/mrs/umn/ALM-19035.html @@ -0,0 +1,124 @@ + + +

      ALM-19035 Size of the RegionServer Call Queue Exceeds the Threshold

      +

      Alarm Description

      The system checks the size of the RegionServer call queue for each HBase service every 30 seconds. This alarm is generated when the call queue of a RegionServer instance is bigger than the threshold for 10 consecutive times.

      +

      This alarm is cleared when the call queue of a RegionServer instance is no bigger than the threshold.

      +

      This alarm applies only to MRS 3.3.1 or later.

      +
      +

      Alarm Attributes

      +
      + + + + + + + + + +

      Alarm ID

      +

      Alarm Severity

      +

      Auto Cleared

      +

      19035

      +
      • Critical (default threshold: 800 MB)
      • Major (default threshold: 600 MB)
      +

      Yes

      +
      +
      +
      +

      Alarm Parameters

      +
      + + + + + + + + + + + + + + + + + + + + + + +

      Type

      +

      Parameter

      +

      Description

      +

      Location Information

      +

      Source

      +

      Specifies the cluster for which the alarm was generated.

      +

      ServiceName

      +

      Specifies the service for which the alarm was generated.

      +

      RoleName

      +

      Specifies the role for which the alarm was generated.

      +

      HostName

      +

      Specifies the host for which the alarm was generated.

      +

      Additional Information

      +

      Threshold

      +

      Specifies the threshold for generating the alarm.

      +
      +
      +
      +

      Impact on the System

      Request queues are stacked, and the RegionServer memory GC pressure increases. As a result, the response time of read requests increases. For latency-sensitive services, a large number of service read requests may time out.

      +
      +

      Possible Causes

      • The RegionServer heap memory configuration is improper.
      • A slow disk fault occurred.
      • The RegionServer configuration is improper.
      • Regions of RegionServers are not evenly distributed and hotspotting occurred.
      • The latency of WAL Sync operations is high.
      +
      +

      Handling Procedure

      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 19035, and view the service instance and host name in Location.
      +

      Check the heap memory configuration.

      +
      1. In the alarm list on MRS Manager, check whether the "Heap Memory Usage of the HBase Process Exceeds the Threshold" alarm is generated for the service instance in 1.

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

      2. Rectify the fault by following the handling procedure of "ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold".
      3. Wait several minutes and check whether the alarm is cleared.

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

      4. On MRS Manager, choose Cluster > Services > HBase > Chart, select GC from the chart category, and check whether the GC times and GC monitoring period are normal.

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

      5. Click Configurations, search for GC_OPTS, and increase the value of Xmx of the RegionServer within the allowed memory range. Set the value to a number less than or equal to 31 GB. Click Save.
      6. Click Dashboard and click More > Restart Service to restart the HBase service.

        During HBase service restart, the service is unavailable. For example, data cannot be read or written, table operations cannot be performed, and the HBase web UI is inaccessible.

        +
        +

      7. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check for slow disk fault.

      +
      1. Check whether alarm Slow Disk Fault or Disk Unavailable are generated for the same node in 1.

        • If yes, go to 10.
        • If no, go to 12.
        +

      1. Rectify the fault by following the handling procedure of "ALM-12033 Slow Disk Fault" or "ALM-12063 Disk Unavailable".
      2. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the RegionServer configuration.

      +
      1. On MRS Manager, choose Cluster > Service > HBase, click Configurations > All Configurations, and check whether the values of hbase.wal.hsync and hbase.hfile.hsync are true.

        • If yes, go to 13.
        • If no, go to 15.
        +

      2. Set both hbase.wal.hsync and hbase.hfile.hsync to false and click Save. Click Dashboard and click More > Restart Service to restart the HBase service.
      3. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check whether RegionServer regions are evenly distributed.

      +
      1. On MRS Manager, choose Cluster > Services > HBase. Click HMaster(Active) on the right of HMaster Web UI to go to the web UI of the HBase instance. View the Base Stats tab in the Region Servers area. Check whether the number of regions in the Num.Regions column is even.

        • If yes, go to 20.
        • If no, go to 16.
        +

        +

      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

        +

        kinit supergroup user group or a user with the Global Admin permission (If Kerberos authentication is disabled for the cluster, skip this operation.)

        +

      1. Run the following commands to enable load balancing and check whether the function is successfully enabled:

        hbase shell

        +

        balance_switch true

        +

        balancer_enabled

        +

        If the command output is true, load balancing is enabled.

        +
        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.

        +
        +
        +

      2. Wait several minutes and check whether the alarm is cleared.

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

      +

      Check the WAL sync latency.

      +
      1. On MRS Manager, choose Cluster > Services > HBase > Chart. In the Chart Category area, select Operations. Check whether the value of "P99.9th Percentile of WAL Sync Operation Delay-All Instances" exceeds 500 ms.

        • If yes, go to 21.
        • If no, go to 22.
        +

      1. Click Instances, select the RegionServer instance for which the alarm is generated, and choose More > Restart Instance. You also need to perform 22 and provide the logs to O&M personnel for fault locating.

        During RegionServer restart, client requests will be retried for multiple times. Read and write operations are affected for a short period of time.

        +
        +

      +

      Collect fault information.

      +
      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 the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      +
      +

      Related Information

      None.

      +
      +
      + + diff --git a/docs/mrs/umn/ALM-19036.html b/docs/mrs/umn/ALM-19036.html new file mode 100644 index 000000000..856dae542 --- /dev/null +++ b/docs/mrs/umn/ALM-19036.html @@ -0,0 +1,133 @@ + + +

      ALM-19036 Bad Blocks Exist in HBase Key Directory Data

      +

      Alarm Description

      The system checks for bad blocks in HBase key directories every 5 minutes, including the hbase.version file and the hbase:meta and master:store table directories. This alarm is generated when a bad block is detected.

      +

      This alarm is cleared when the system detects that no bad blocks exist in the HBase key directories.

      +

      This alarm applies only to MRS 3.5.0 or later.

      +
      +

      Alarm Attributes

      +
      + + + + + + + + + +

      Alarm ID

      +

      Alarm Severity

      +

      Auto Cleared

      +

      19036

      +

      Critical

      +

      Yes

      +
      +
      +
      +

      Alarm Parameters

      +
      + + + + + + + + + + + + + + + + + + +

      Type

      +

      Parameter

      +

      Description

      +

      Location Information

      +

      Source

      +

      Specifies the cluster for which the alarm was generated.

      +

      ServiceName

      +

      Specifies the service for which the alarm was generated.

      +

      RoleName

      +

      Specifies the role for which the alarm was generated.

      +

      HostName

      +

      Specifies the host for which the alarm was generated.

      +
      +
      +
      +

      Impact on the System

      If block loss occurs in HBase key directories, the HBase service becomes unavailable, causing service request stacking or interruptions.

      +
      +

      Possible Causes

      HDFS is faulty.

      +
      +

      Handling Procedure

      Handling bad blocks in key directory data involves operations that quickly restore the HBase service, such as stopping the HBase service. Be mindful that these operations will interrupt services. Also, be aware of any data stacking on the services.

      +
      +

      Check whether the HDFS service is normal.

      +
      1. Log in to MRS Manager, choose Cluster > Services > HDFS, and check whether the HDFS running status is Normal.

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

      2. Restore the HDFS running status to Normal by following the instructions provided in the alarm help, and go to 3.
      +

      Rebuild key directory data.

      +
      1. Log in to MRS Manager, choose O&M > Alarm > Alarms, check the cause of the alarm whose Alarm ID is 19036, and identify the directory with block loss.
      2. Perform the restoration operations based on the directory where block loss has occurred.

        • If Alarm Cause indicates that bad blocks exist in the hbase.version file, go to 5 to restore the hbase.version file.
        • If Alarm Cause indicates that bad blocks exist in the hbase:meta table directory, go to 6 to restore the hbase meta table directory files.
        • If Alarm Cause indicates that bad blocks exist in the master:store table directory, go to 7 to restore the master store table directory files.
        +

      3. Restore the hbase.version file.

        1. Log in to the node where the client is installed as the client installation user.
        2. Run the following command to go to the client installation directory:

          cd Client installation directory

          +
        3. Run the following commands to configure environment variables:

          source bigdata_env

          +

          source HBase/component_env

          +
        4. Kerberos authentication is enabled for the cluster (the cluster is in security mode): Run the following command to authenticate as the HBase built-in user. If this is your first-time authentication, enter the default password and change it.

          kinit hbase

          +

          Kerberos authentication is disabled for the cluster (the cluster is in normal mode): Run the following command to set the Hadoop username:

          +

          export HADOOP_USER_NAME=hbase

          +
        5. Run the following command to create a backup directory that does not exist in HDFS, for example, /tmp/hbase_bak:

          hdfs dfs -mkdir /tmp/hbase_bak

          +
        6. Run the following command to back up the old file:

          hdfs dfs -mv /hbase/hbase.version /tmp/hbase_bak

          +
        7. Run the following command to restore the hbase.version file:

          hbase hbck -j ${HBASE_HOME}/tools/hbase-hbck2-*.jar filesystem -fixVersionFile

          +
          • After the command is executed successfully, run the following command to view the restored hbase.version file:

            hdfs dfs -ls /hbase

            +
          • If the command fails to be executed, go to 8.
          +
        8. Log in to MRS Manager, choose Cluster > Services > HBase > Instances, select all HMaster instances, click More, and select Instance Rolling Restart. In the dialog box that is displayed, enter the password of the current user, and click OK to perform a rolling restart of all HMaster instances.
        9. After the HMaster instances are restarted, check whether the alarm is cleared in the alarm list.
          • If yes, no further action is required.
          • If no, go to 8.
          +
        +

      4. Restore the hbase meta table directory files.

        1. Log in to MRS Manager, choose Cluster > Services > HBase, and click Stop Service in the upper right corner of the Dashboard page. In the dialog box that is displayed, enter the password of the current user and click OK to stop the HBase service.
        2. Log in to the node where the client is installed as the client installation user.
        3. Run the following command to go to the client installation directory:

          cd Client installation directory

          +
        4. Run the following commands to configure environment variables:

          source bigdata_env

          +

          source HBase/component_env

          +
        5. Kerberos authentication is enabled for the cluster (the cluster is in security mode): Run the following command to authenticate as the HBase built-in user. If this is your first-time authentication, enter the default password and change it.

          kinit hbase

          +

          Kerberos authentication is disabled for the cluster (the cluster is in normal mode): Run the following command to set the Hadoop username:

          +

          export HADOOP_USER_NAME=hbase

          +
        6. Run the following commands to regenerate the meta table data:

          export HBASE_CLASSPATH=${HBASE_CLASSPATH}:${HBASE_HOME}/tools/*

          +

          hbase org.apache.hbase.hbck1.OfflineMetaRepair -details

          +

          If Success is displayed, the command is successfully executed. In this case, go to 6.g. If the command fails to be executed, go to 8.

          +
        7. Run the following command to create a backup directory that does not exist in HDFS, for example, /tmp/hbase_bak:

          hdfs dfs -mkdir /tmp/hbase_bak

          +
        8. Run the following command to back up and clear HMaster data:

          hdfs dfs -mv /hbase/MasterData/* /tmp/hbase_bak

          +
        9. Run the following commands to clear the location information of the meta table:

          hbase zkcli

          +

          deleteall /hbase/meta-region-server

          +

          quit

          +
        10. Log in to MRS Manager, choose Cluster > Services > HBase, and click Start Service in the upper right corner of the Dashboard page to start the HBase service.
        11. After the HBase service is started, check whether the alarm is cleared in the alarm list.
          • If yes, no further action is required.
          • If no, go to 8.
          +
        +

      5. Restore the master store table directory files.

        1. Log in to MRS Manager, choose Cluster > Services > HBase, and click Stop Service in the upper right corner of the Dashboard page. In the dialog box that is displayed, enter the password of the current user and click OK to stop the HBase service.
        2. Log in to the node where the client is installed as the client installation user.
        3. Run the following command to go to the client installation directory:

          cd Client installation directory

          +
        4. Run the following commands to configure environment variables:

          source bigdata_env

          +

          source HBase/component_env

          +
        5. Kerberos authentication is enabled for the cluster (the cluster is in security mode): Run the following command to authenticate as the HBase built-in user. If this is your first-time authentication, enter the default password and change it.

          kinit hbase

          +

          Kerberos authentication is disabled for the cluster (the cluster is in normal mode): Run the following command to set the Hadoop username:

          +

          export HADOOP_USER_NAME=hbase

          +
        6. Run the following command to create a backup directory that does not exist in HDFS, for example, /tmp/hbase_bak:

          hdfs dfs -mkdir /tmp/hbase_bak

          +
        7. Run the following command to back up and clear HMaster data:

          hdfs dfs -mv /hbase/MasterData/* /tmp/hbase_bak

          +
        8. Run the following commands to clear the location information of the meta table:

          hbase zkcli

          +

          deleteall /hbase/meta-region-server

          +

          quit

          +
        9. Log in to MRS Manager, choose Cluster > Services > HBase, and click Start Service in the upper right corner of the Dashboard page to start the HBase service.
        10. After the HBase service is started, check whether the alarm is cleared in the alarm list.
          • If yes, no further action is required.
          • If no, go to 8.
          +
        +

      +

      After the HBase service is restored, observe the service for a period of time. After confirming that HBase and related services are normal, you are advised to run the following command to delete the backup directory to prevent residual useless files:

      +

      hdfs dfs -rm -r /tmp/hbase_bak

      +
      +

      Collect fault information.

      +
      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 the edit icon 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      +
      +

      Related Information

      None.

      +
      +
      + + diff --git a/docs/mrs/umn/ALM-25007.html b/docs/mrs/umn/ALM-25007.html index b2bb32be2..2c799b235 100644 --- a/docs/mrs/umn/ALM-25007.html +++ b/docs/mrs/umn/ALM-25007.html @@ -65,15 +65,15 @@

      Possible Causes

      • There are too many SlapdServer connections.
      • The alarm threshold or alarm trigger count is improperly configured.

      Handling Procedure

      Check whether there are too many SlapdServer process connections.

      -
      1. Log in to FusionInsight Manager and choose Cluster > Services > LdapServer.
      2. On the LdapServer dashboard page, observe the SlapdServer process connections and decrease the connections based on service requirements.

        Figure 1 SlapdServer process connections
        +
        1. Log in to MRS Manager and choose Cluster > Services > LdapServer.
        2. On the LdapServer dashboard page, observe the SlapdServer process connections and decrease the connections based on service requirements.

          Figure 1 SlapdServer process connections

        3. Wait about 2 minutes and check whether the alarm is cleared.

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

        Check whether the alarm threshold or alarm trigger count is properly configured.

        -
        1. On FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose LdapServer > Other > SlapdServer Service Connections, and check whether the alarm trigger count and alarm threshold are set properly.

          • If yes, go to 7.
          • If no, go to 5.
          +
          1. On MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose LdapServer > Other > SlapdServer Service Connections, and check whether the alarm trigger count and alarm threshold are set properly.

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

          2. Change the trigger count and alarm threshold based on the actual number of process connections, and apply the changes.
          3. Wait 2 minutes and check whether the alarm is automatically cleared.

            • If yes, no further action is required.
            • If no, go to 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 LdapServer for the target cluster.
          3. Specify Hosts for collecting logs, 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 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 LdapServer for the target cluster.
          3. Specify Hosts for collecting logs, 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 O&M personnel and provide the collected logs.

      Alarm Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-25008.html b/docs/mrs/umn/ALM-25008.html index eeb5a69d2..3ec24294b 100644 --- a/docs/mrs/umn/ALM-25008.html +++ b/docs/mrs/umn/ALM-25008.html @@ -66,16 +66,16 @@

      Possible Causes

      • The alarm threshold or alarm trigger count is improperly configured.
      • The CPU configuration cannot meet service requirements, and the CPU usage reaches the upper limit.

      Handling Procedure

      Check whether the alarm threshold or alarm trigger count is properly configured.

      -
      1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose LdapServer > Other > SlapdServer Service Total CPU Percentage, and check whether the alarm trigger count and alarm threshold are set properly.

        • If yes, go to 4.
        • If no, go to 2.
        +
        1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose LdapServer > Other > SlapdServer Service Total CPU Percentage, and check whether the alarm trigger count and alarm threshold are set properly.

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

        2. Change the trigger count and alarm threshold based on the actual CPU usage, and apply the changes.
        3. Wait 2 minutes and check whether the alarm is automatically cleared.

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

        Check whether the CPU usage reaches the upper limit.

        -
        1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the right pane, click this alarm and obtain the host name in Location.
        2. Choose Cluster > Services > LdapServer, click the Instance tab, and click the SlapdServer instance corresponding to the host name in 4.
        3. On the dashboard of the instance, observe the real-time data of the CPU Usage of a Single SlapdServer Instance chart for about 5 minutes and check whether the CPU usage exceeds the threshold (75% by default) for multiple times.

          • If yes, go to 7.
          • If no, go to 9.
          +
          1. On MRS Manager, choose O&M > Alarm > Alarms. In the right pane, click this alarm and obtain the host name in Location.
          2. Choose Cluster > Services > LdapServer, click the Instance tab, and click the SlapdServer instance corresponding to the host name in 4.
          3. On the dashboard of the instance, observe the real-time data of the CPU Usage of a Single SlapdServer Instance chart for about 5 minutes and check whether the CPU usage exceeds the threshold (75% by default) for multiple times.

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

          4. Check whether the status of other SlapdServer instances is normal. For details, see 5 to 6.

            • If yes, contact the MRS cluster administrator to evaluate whether to expand the capacity of SlapdServer instances. Then, go to 8.
            • If no, repair the faulty SlapdServer instance and go to 8.

          5. 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 LdapServer 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 LdapServer 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-29007.html b/docs/mrs/umn/ALM-29007.html index a709192a0..fb608d3d2 100644 --- a/docs/mrs/umn/ALM-29007.html +++ b/docs/mrs/umn/ALM-29007.html @@ -70,13 +70,13 @@

    Possible Causes

    The Impalad process is executing a large number of query tasks.

    -

    Handling Procedure

    1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Impala > CPU and Memory > Impalad Process Memory Usage (Impalad) and check the threshold.
    2. If the alarm threshold is smaller than 80%, increase the alarm threshold as required and check whether the alarm is cleared.

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

      Handling Procedure

      1. On MRS Manager, choose O&M > Alarm > Thresholds > Impala > CPU and Memory > Impalad Process Memory Usage (Impalad) and check the threshold.
      2. If the alarm threshold is smaller than 80%, increase the alarm threshold as required and check whether the alarm is cleared.

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

      3. If the threshold is greater than 80%, check whether a large number of concurrent query tasks exist when the alarm is generated. A large number of concurrent query tasks will cause the memory usage to increase sharply. After the tasks are complete, check whether the alarm is automatically cleared. During this period, some tasks may fail to be executed or may be canceled due to insufficient memory. In this case, try again.

        If the memory usage always exceeds the threshold, the cluster capacity needs to be expanded.

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

      Collect fault information.

      -
      1. On FusionInsight Manager of the active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 Clearance

      The alarm is automatically cleared after the burst concurrent tasks are complete.

      diff --git a/docs/mrs/umn/ALM-29008.html b/docs/mrs/umn/ALM-29008.html index 0bab1e17a..28f820e4f 100644 --- a/docs/mrs/umn/ALM-29008.html +++ b/docs/mrs/umn/ALM-29008.html @@ -70,13 +70,13 @@

    Possible Causes

    The number of client connections maintained by the Impalad service is too large or the threshold is too small.

    -

    Handling Procedure

    1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Impala > Connections > Number of ODBC Connections to Impalad Process (Impalad) to check the threshold.
    2. Check the number of ODBC applications connected to Impalad and stop idle applications. Check whether the alarm is automatically cleared.

      • If yes, no further action is required.
      • If no, go to 3 to change the number of concurrent connections supported by Impalad.
      -

    3. On FusionInsight Manager, choose Cluster > Impala > Configurations > All Configurations > Impalad > Customization. Add the custom parameter --fe_service_threads. The default value of this parameter is 64. Change the value as required and click Save.
    4. After the query tasks on all clients are complete, click the Instances tab. Select all Impalad instances, and restart them.

      The service will become unavailable when all instances are restarted. If a single instance is restarted, the tasks that are being executed on that instance will fail and the service will become available.

      +

      Handling Procedure

      1. On MRS Manager, choose O&M > Alarm > Thresholds > Impala > Connections > Number of ODBC Connections to Impalad Process (Impalad) to check the threshold.
      2. Check the number of ODBC applications connected to Impalad and stop idle applications. Check whether the alarm is automatically cleared.

        • If yes, no further action is required.
        • If no, go to 3 to change the number of concurrent connections supported by Impalad.
        +

      3. On MRS Manager, choose Cluster > Impala > Configurations > All Configurations > Impalad > Customization. Add the custom parameter --fe_service_threads. The default value of this parameter is 64. Change the value as required and click Save.
      4. After the query tasks on all clients are complete, click the Instances tab. Select all Impalad instances, and restart them.

        The service will become unavailable when all instances are restarted. If a single instance is restarted, the tasks that are being executed on that instance will fail and the service will become available.

      5. After the restart is complete, check whether the alarm is cleared.

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

      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 Impala for the target cluster.
      3. Click the edit icon 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 Impala for the target cluster.
      3. Click the edit icon 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-29010.html b/docs/mrs/umn/ALM-29010.html index b59abae2c..993441e96 100644 --- a/docs/mrs/umn/ALM-29010.html +++ b/docs/mrs/umn/ALM-29010.html @@ -70,7 +70,7 @@

      Possible Causes

      The Impalad service has maintained a large number of queries, or the threshold is too small.

      -

      Handling Procedure

      1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Impala > Query Task Sum Statistics > Total number of Queries Being Submitted (Impalad) and check the threshold.

        +

        Handling Procedure

        1. On MRS Manager, choose O&M > Alarm > Thresholds > Impala > Query Task Sum Statistics > Total number of Queries Being Submitted (Impalad) and check the threshold.

        2. Change the threshold.

        3. Click the Instances tab, select all Impalad instances, and restart them.

          The service will become unavailable when all instances are restarted. If a single instance is restarted, the tasks that are being executed on that instance will fail and the service will become available.

          @@ -78,7 +78,7 @@

        4. After the restart is complete, 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. Expand the Service drop-down list, and select Impala for the target cluster.
        3. Click the edit icon 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 Impala for the target cluster.
        3. Click the edit icon 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/ALM-29011.html b/docs/mrs/umn/ALM-29011.html index 79e9b2441..9f686184b 100644 --- a/docs/mrs/umn/ALM-29011.html +++ b/docs/mrs/umn/ALM-29011.html @@ -70,7 +70,7 @@

      Possible Causes

      The Impalad service has maintained a large number of queries, or the threshold is too small.

      -

      Handling Procedure

      1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Impala > Query Task Sum Statistics > Total number of Queries Being Executed (Impalad) and check the threshold.

        +

        Handling Procedure

        1. On MRS Manager, choose O&M > Alarm > Thresholds > Impala > Query Task Sum Statistics > Total number of Queries Being Executed (Impalad) and check the threshold.

        2. Change the threshold.

        3. Click the Instances tab, select all Impalad instances, and restart them.

          The service will become unavailable when all instances are restarted. If a single instance is restarted, the tasks that are being executed on that instance will fail and the service will become available.

          @@ -78,7 +78,7 @@

        4. After the restart is complete, 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. Expand the Service drop-down list, and select Impala for the target cluster.
        3. Click the edit icon 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 Impala for the target cluster.
        3. Click the edit icon 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/ALM-29012.html b/docs/mrs/umn/ALM-29012.html index 9c86cf92f..93bf04b9f 100644 --- a/docs/mrs/umn/ALM-29012.html +++ b/docs/mrs/umn/ALM-29012.html @@ -70,7 +70,7 @@

      Possible Causes

      The Impalad service has maintained a large number of queries, or the threshold is too small.

      -

      Handling Procedure

      1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Impala > Query Task Sum Statistics > Total number of Waiting Queries (Impalad) and check the threshold.

        +

        Handling Procedure

        1. On MRS Manager, choose O&M > Alarm > Thresholds > Impala > Query Task Sum Statistics > Total number of Waiting Queries (Impalad) and check the threshold.

        2. Change the threshold.

        3. Click the Instances tab, select all Impalad instances, and restart them.

          The service will become unavailable when all instances are restarted. If a single instance is restarted, the tasks that are being executed on that instance will fail and the service will become available.

          @@ -78,7 +78,7 @@

        1. After the restart is complete, 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. Expand the Service drop-down list, and select Impala for the target cluster.
        3. Click the edit icon 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 Impala for the target cluster.
        3. Click the edit icon 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/ALM-29013.html b/docs/mrs/umn/ALM-29013.html index 166d88709..ed685ee2b 100644 --- a/docs/mrs/umn/ALM-29013.html +++ b/docs/mrs/umn/ALM-29013.html @@ -71,12 +71,12 @@

      Handling Procedure

      Check the GC time.

      1. Choose O&M > Alarm > Thresholds > Impala > Process FGCT > Process FGCT of Impalad (Impalad), and check the threshold (12s by default).

        -

      2. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and check whether the alarm whose Alarm ID is 29013 exists in the alarm list.

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

      3. On FusionInsight Manager, choose Cluster > Impala, click the Instances tab, select the Impalad instance for which the alarm is generated, then click the Chart tab, locate the Process FGCT chart, and check whether the FGC time is greater than the threshold in 1.

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

      4. Log in to MRS Manager, choose O&M > Alarm > Alarms, and check whether the alarm whose Alarm ID is 29013 exists in the alarm list.

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

      5. On MRS Manager, choose Cluster > Impala, click the Instances tab, select the Impalad instance for which the alarm is generated, then click the Chart tab, locate the Process FGCT chart, and check whether the FGC time is greater than the threshold in 1.

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

      6. Choose O&M > Alarm > Thresholds > Impala > Process FGCT > Process FGCT of Impalad (Impalad), and change the threshold to a value less than the time obtained in 3. Then, 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 of the active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-29014.html b/docs/mrs/umn/ALM-29014.html index 253023693..2313845eb 100644 --- a/docs/mrs/umn/ALM-29014.html +++ b/docs/mrs/umn/ALM-29014.html @@ -71,12 +71,12 @@

      Handling Procedure

      Check the GC time.

      1. Choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose Impala > Process FGCT > Process FGCT of Catalog (Catalog), and check the threshold (12s by default).

        -

      2. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and check whether the alarm whose Alarm ID is 29014 exists in the alarm list.

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

      3. On FusionInsight Manager, choose Cluster > Impala, click the Instance tab, select the Catalog instance for which the alarm is generated, then click the Chart tab, locate the Process FGCT chart, and check whether the FGC time is greater than the threshold in 1.

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

      4. Log in to MRS Manager, choose O&M > Alarm > Alarms, and check whether the alarm whose Alarm ID is 29014 exists in the alarm list.

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

      5. On MRS Manager, choose Cluster > Impala, click the Instance tab, select the Catalog instance for which the alarm is generated, then click the Chart tab, locate the Process FGCT chart, and check whether the FGC time is greater than the threshold in 1.

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

      6. Choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose Impala > Process FGCT > Process FGCT of Catalog (Catalog), and change the threshold to a value less than the time obtained in 3. Then, 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 of the active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-29015.html b/docs/mrs/umn/ALM-29015.html index 065c9edc0..4badbb2df 100644 --- a/docs/mrs/umn/ALM-29015.html +++ b/docs/mrs/umn/ALM-29015.html @@ -70,13 +70,13 @@

    Possible Causes

    The memory of the node instance is overused or the memory is inappropriately configured.

    -

    Handling Procedure

    1. On FusionInsight Manager, choose O&M > Alarm > Thresholds > Impala > CPU and Memory > Catalog Process Memory Usage (Impalad) and check the threshold.
    2. If the alarm threshold is smaller than 80%, increase the alarm threshold as required and check whether the alarm is cleared.

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

      Handling Procedure

      1. On MRS Manager, choose O&M > Alarm > Thresholds > Impala > CPU and Memory > Catalog Process Memory Usage (Impalad) and check the threshold.
      2. If the alarm threshold is smaller than 80%, increase the alarm threshold as required and check whether the alarm is cleared.

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

      3. If the threshold is greater than 80%, check whether a large number of concurrent query tasks exist when the alarm is generated. A large number of concurrent query tasks will cause the memory usage to increase sharply. After the tasks are complete, check whether the alarm is automatically cleared. During this period, some tasks may fail to be executed or may be canceled due to insufficient memory. In this case, try again.

        If the memory usage always exceeds the threshold, the cluster capacity needs to be expanded.

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

      Collect fault information.

      -
      1. On FusionInsight Manager of the active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-29016.html b/docs/mrs/umn/ALM-29016.html index a55622f81..ab529e12b 100644 --- a/docs/mrs/umn/ALM-29016.html +++ b/docs/mrs/umn/ALM-29016.html @@ -63,14 +63,14 @@

    Possible Causes

    The Impalad service maintains too many queries.

    -

    Handling Procedure

    1. Log in to FusionInsight Manager and choose Cluster > Services > Impala > Impalad Web UI. On the displayed page, click any node to go to the web UI.
    2. On the web UI, click /backends to view the Impala instance list. Locate the instance for which the alarm is generated and click Web UI. After the web UI of the subhealthy node is displayed, click /queries to check the task execution status and check whether any task is executed slowly.

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

      Handling Procedure

      1. Log in to MRS Manager and choose Cluster > Services > Impala > Impalad Web UI. On the displayed page, click any node to go to the web UI.
      2. On the web UI, click /backends to view the Impala instance list. Locate the instance for which the alarm is generated and click Web UI. After the web UI of the subhealthy node is displayed, click /queries to check the task execution status and check whether any task is executed slowly.

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

      3. After the task is complete, check whether the alarm is cleared.

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

      4. On FusionInsight Manager, choose Cluster > Services > Impala > Instances, select the Impala instance for which the alarm is generated, click More, and select Restart Instance. Then, check whether the alarm is cleared.

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

          The service will become unavailable when all instances are restarted. If a single instance is restarted, the tasks that are being executed on that instance will fail and the service will become available.

          +

        • On MRS Manager, choose Cluster > Services > Impala > Instances, select the Impala instance for which the alarm is generated, click More, and select Restart Instance. Then, check whether the alarm is cleared.

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

            The service will become unavailable when all instances are restarted. If a single instance is restarted, the tasks that are being executed on that instance will fail and the service will become available.

      Collect fault information.

      -
      1. On FusionInsight Manager of the active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala 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 active or standby cluster, choose O&M. In the navigation pane on the left, choose Log > Download.
      2. Expand the Service drop-down list, and select Impala 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-38009.html b/docs/mrs/umn/ALM-38009.html index 11b68bbd8..3955413a5 100644 --- a/docs/mrs/umn/ALM-38009.html +++ b/docs/mrs/umn/ALM-38009.html @@ -75,10 +75,10 @@

  3. Observe for a period of time and check whether the alarm is cleared. If the alarm persists, go to 5.

Check the partition planning of the topic.

-
  1. On the KafkaTopic Monitor page, view Topic Input Traffic in the Topic Traffic area of each topic, obtain the topic with the largest value, and check the partitions of this topic as well as information about the host of these partitions.
  2. Log in to the host queried in 5 and run the iostat -d -x command to check the %util value of each disk.

    • If the %util value of each disk exceeds the threshold (80% by default), expand the Kafka disk capacity. After the capacity expansion, replan the topic partitions by referring to 3.
    • If the %util values of the disks vary greatly, check the disk partition configuration of Kafka. For example, check the value of log.dirs in the ${BIGDATA_HOME}/FusionInsight_HD_8.1.0.1/1_14_Broker/etc/server.properties file.

      Run the following command to view the Filesystem information:

      +
      1. On the KafkaTopic Monitor page, view Topic Input Traffic in the Topic Traffic area of each topic, obtain the topic with the largest value, and check the partitions of this topic as well as information about the host of these partitions.
      2. Log in to the host queried in 5 and run the iostat -d -x command to check the %util value of each disk.

        • If the %util value of each disk exceeds the threshold (80% by default), expand the Kafka disk capacity. After the capacity expansion, replan the topic partitions by referring to 3.
        • If the %util values of the disks vary greatly, check the disk partition configuration of Kafka. For example, check the value of log.dirs in the ${BIGDATA_HOME}/FusionInsight_HD_8.1.0.1/1_14_Broker/etc/server.properties file.

          Run the following command to view the Filesystem information:

          df -h log.dirs value

          The command output is as follows.

          -

          +

        • If the partition where Filesystem is located matches the partition with a high %util value, plan Kafka partitions on idle disks, configure log.dirs as an idle disk directory, and replan topic partitions by referring to 3. Ensure that the partitions of the topic are evenly distributed to each disk.

      3. Observe for a period of time and check whether the alarm is cleared.

        • If yes, no further action is required.
        • If no, repeat 5 to 6 three times. Then, go to 8.
        diff --git a/docs/mrs/umn/ALM-38012.html b/docs/mrs/umn/ALM-38012.html new file mode 100644 index 000000000..7efc592a7 --- /dev/null +++ b/docs/mrs/umn/ALM-38012.html @@ -0,0 +1,93 @@ + + +

        ALM-38012 Number of Broker Partitions Exceeds the Threshold

        +

        Alarm Description

        The system checks the number of partitions on each Broker instance of the Kafka service every 30 seconds. You can view the number of partitions on the Broker instance dashboard page. This alarm is generated when the number of partitions on a Broker instance exceeds the threshold. You can choose O&M > Alarm > Thresholds > Kafka and change the threshold. This alarm is cleared when the number of partitions is less than or equal to the threshold.

        +

        This alarm applies only to MRS 3.5.0 or later.

        +
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        38012

        +

        Critical (default threshold: 6000)

        +

        Major (default threshold: 3000)

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +
        +
        +
        +

        Impact on the System

        The number of Broker partitions exceeds the threshold. Too many partitions increase the Broker load and cause bottlenecks in memory, disk I/O, and CPU resources. As a result, the request response becomes slow or even times out.

        +
        +

        Possible Causes

        • Broker partitions are unevenly distributed, or the Kafka cluster usage exceeds the specifications.
        • There are many useless topics.
        +
        +

        Handling Procedure

        Check whether partitions are evenly distributed on Broker.

        +
        1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the service instance and host for which the alarm is generated.
        2. Choose Cluster > Services > Kafka > Chart, select Partition from the Chart Category area, zoom in Number of Partitions-All Instances in the upper right corner, and click Distribution to check whether partitions are evenly distributed on Broker.

          Figure 1 Example of uneven partition distribution on Broker
          +
          • If yes, go to 3.
          • If no, go to 4.
          +

        3. If the partitions on Broker are balanced, the Kafka cluster exceeds the specifications. In this case, add Broker instances. Then, go to 5.

          On MRS Manager, choose Cluster > Services > Kafka > Instances, click Add Instance, and add Broker instances as prompted.

          +

        4. Click the uneven distribution bar on the rightmost. If the number of partitions on only the Broker node for which the alarm is generated is too large, perform data balancing.
        5. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether there are many useless topics.

        +
        1. Check whether useless topics exist in the cluster.

          • If yes, perform the following steps to delete useless topics: Deleting topics is a high-risk operation. Before deleting topics, ensure that the topics are not used.
            1. Log in to Manager as a user who has the permission to access the Kafka web UI.
            2. Choose Cluster > Services > Kafka. On the right of KafkaManager Web UI, click the URL to access the Kafka web UI.
            3. Choose Topics.
            4. In the Operation column of the target topic, click Action and select Delete.
            5. In the dialog box that is displayed, click OK.

              The default built-in topics cannot be deleted.

              +
            +
          • If no, go to 8.
          +

        2. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Collect fault information.

        +
        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 the edit icon in the upper right corner, and set Start 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-38013.html b/docs/mrs/umn/ALM-38013.html new file mode 100644 index 000000000..1b6044fa4 --- /dev/null +++ b/docs/mrs/umn/ALM-38013.html @@ -0,0 +1,100 @@ + + +

        ALM-38013 Produce Request Latency in the Request Queue Exceeds the Threshold

        +

        Alarm Description

        The system checks the latency of Produce requests on Broker instances in the request queue every 30 seconds. This alarm is generated when the latency of Produce requests on a Broker instance in the request queue has exceeded the threshold for 10 consecutive times.

        +

        This alarm is cleared when the latency of Produce requests in the request queue is less than or equal to the threshold.

        +

        This alarm applies only to MRS 3.5.0 or later.

        +
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        38013

        +

        Critical (default threshold: 60000)

        +

        Major (default threshold: 30000)

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +
        +
        +
        +

        Impact on the System

        The latency of Produce requests on the Broker instance in the request queue exceeds the threshold. As a result, the request queue is congested, and the response time of write requests increases. For latency-sensitive services, a large number of write requests may time out.

        +
        +

        Possible Causes

        • The number of threads used by the Broker instance to process requests is incorrectly configured.
        • A slow disk fault has occurred.
        • The Broker disk I/O is busy.
        • Broker partitions are unevenly distributed, and hotspotting has occurred.
        +
        +

        Handling Procedure

        Check whether the number of threads used by the Broker instance to process requests is appropriate.

        +
        1. Log in to MRS Manager and choose Cluster > Services > Kafka. On the page that is displayed, click Configurations and then All Configurations.
        2. Search for and check the value of num.io.threads. If the value is too small, increase it. You are advised to change the value to twice the number of CPU cores. The maximum value is 64. Save the configuration.
        3. Click the Instances tab, select all Broker instances, click More, and select Instance Rolling Restart.

          Services may be affected or interrupted during the restart. Restart the instances during off-peak hours.

          +
          +

        4. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether a slow disk fault has occurred.

        +
        1. On MRS Manager, choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the host name for which this alarm is generated.
        2. Check whether alarm Slow Disk Fault or Disk Unavailable is generated for the same node in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-12033 Slow Disk Fault or ALM-12063 Disk Unavailable.
          • If no, go to 8.
          +

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

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

        +

        Check whether the Broker disk I/O is busy.

        +
        1. Check whether alarm Busy Broker Disk I/Os exists on the node for which this alarm is generated in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-38009 Busy Broker Disk I/Os and then go to 9.
          • If no, go to 10.
          +

        2. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether Broker partitions are evenly distributed and hotspotting has occurred.

        +
        1. Choose Cluster > Services > Kafka > Chart, select Partition from the Chart Category area, zoom in Number of Partitions-All Instances in the upper right corner, and click Distribution to check whether partitions are evenly distributed on Broker.

          Figure 1 Example of uneven partition distribution on Broker
          +
          • If yes, go to 13.
          • If no, go to 11.
          +

        2. Click the uneven distribution bar on the rightmost, and check whether the node obtained in 5 is included in the unevenly distributed instances. If it is, perform data balancing.
        3. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Collect fault information.

        +
        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 the edit icon in the upper right corner, and set Start 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-38014.html b/docs/mrs/umn/ALM-38014.html new file mode 100644 index 000000000..8fdfb97e3 --- /dev/null +++ b/docs/mrs/umn/ALM-38014.html @@ -0,0 +1,100 @@ + + +

        ALM-38014 Total Produce Request Latency Exceeds the Threshold

        +

        Alarm Description

        The system checks the total latency of Produce requests on Broker instances every 30 seconds. This alarm is generated when the total latency of Produce requests on a Broker instance has exceeded the threshold for 10 consecutive times.

        +

        This alarm is cleared when the total latency of Produce requests is less than or equal to the threshold.

        +

        This alarm applies only to MRS 3.5.0 or later.

        +
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        38014

        +

        Critical (default threshold: 120000)

        +

        Major (default threshold: 60000)

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +
        +
        +
        +

        Impact on the System

        The total latency of Produce requests on the Broker instance exceeds the threshold. For latency-sensitive services, a large number of service query requests may time out.

        +
        +

        Possible Causes

        • The number of threads used by the Broker instance to process requests is incorrectly configured.
        • A slow disk fault has occurred.
        • The Broker disk I/O is busy.
        • Broker partitions are unevenly distributed, and hotspotting has occurred.
        +
        +

        Handling Procedure

        Check whether the number of threads used by the Broker instance to process requests is appropriate.

        +
        1. Log in to MRS Manager and choose Cluster > Services > Kafka. On the page that is displayed, click Configurations and then All Configurations.
        2. Search for and check the value of num.io.threads. If the value is too small, increase it. You are advised to change the value to twice the number of CPU cores. The maximum value is 64. Save the configuration.
        3. Click the Instances tab, select all Broker instances, click More, and select Instance Rolling Restart.

          Services may be affected or interrupted during the restart. Restart the instances during off-peak hours.

          +
          +

        4. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether a slow disk fault has occurred.

        +
        1. On MRS Manager, choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the host name for which this alarm is generated.
        2. Check whether alarm Slow Disk Fault or Disk Unavailable is generated for the same node in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-12033 Slow Disk Fault or ALM-12063 Disk Unavailable.
          • If no, go to 8.
          +

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

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

        +

        Check whether the Broker disk I/O is busy.

        +
        1. Check whether alarm Busy Broker Disk I/Os exists on the node for which this alarm is generated in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-38009 Busy Broker Disk I/Os and then go to 9.
          • If no, go to 10.
          +

        2. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether Broker partitions are evenly distributed and hotspotting has occurred.

        +
        1. Choose Cluster > Services > Kafka > Chart, select Partition from the Chart Category area, zoom in Number of Partitions-All Instances in the upper right corner, and click Distribution to check whether partitions are evenly distributed on Broker.

          Figure 1 Example of uneven partition distribution on Broker
          +
          • If yes, go to 13.
          • If no, go to 11.
          +

        2. Click the uneven distribution bar on the rightmost, and check whether the node obtained in 5 is included in the unevenly distributed instances. If it is, perform data balancing.
        3. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Collect fault information.

        +
        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 the edit icon in the upper right corner, and set Start 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 engineers and provide the collected logs.
        +
        +

        Alarm Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-38015.html b/docs/mrs/umn/ALM-38015.html new file mode 100644 index 000000000..3817022b3 --- /dev/null +++ b/docs/mrs/umn/ALM-38015.html @@ -0,0 +1,100 @@ + + +

        ALM-38015 Fetch Request Latency in the Request Queue Exceeds the Threshold

        +

        Alarm Description

        The system checks the latency of Fetch requests on Broker instances in the request queue every 30 seconds. This alarm is generated when the latency of Fetch requests on a Broker instance in the request queue has exceeded the threshold for 10 consecutive times.

        +

        This alarm is cleared when the latency of Fetch requests in the request queue is less than or equal to the threshold.

        +

        This alarm applies only to MRS 3.5.0 or later.

        +
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        38015

        +

        Critical (default threshold: 30000)

        +

        Major (default threshold: 10000)

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +
        +
        +
        +

        Impact on the System

        The latency of Fetch requests on the Broker instance in the request queue exceeds the threshold. For latency-sensitive services, a large number of service query requests may time out.

        +
        +

        Possible Causes

        • The number of threads used by the Broker instance to process requests is incorrectly configured.
        • A slow disk fault has occurred.
        • The Broker disk I/O is busy.
        • Broker partitions are unevenly distributed, and hotspotting has occurred.
        +
        +

        Handling Procedure

        Check whether the number of threads used by the Broker instance to process requests is appropriate.

        +
        1. Log in to MRS Manager and choose Cluster > Services > Kafka. On the page that is displayed, click Configurations and then All Configurations.
        2. Search for and check the value of num.io.threads. If the value is too small, increase it. You are advised to change the value to twice the number of CPU cores. The maximum value is 64. Save the configuration.
        3. Click the Instances tab, select all Broker instances, click More, and select Instance Rolling Restart.

          Services may be affected or interrupted during the restart. Restart the instances during off-peak hours.

          +
          +

        4. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether a slow disk fault has occurred.

        +
        1. On MRS Manager, choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the host name for which this alarm is generated.
        2. Check whether alarm Slow Disk Fault or Disk Unavailable is generated for the same node in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-12033 Slow Disk Fault or ALM-12063 Disk Unavailable.
          • If no, go to 8.
          +

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

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

        +

        Check whether the Broker disk I/O is busy.

        +
        1. Check whether alarm Busy Broker Disk I/Os exists on the node for which this alarm is generated in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-38009 Busy Broker Disk I/Os and then go to 9.
          • If no, go to 10.
          +

        2. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether Broker partitions are evenly distributed and hotspotting has occurred.

        +
        1. Choose Cluster > Services > Kafka > Chart, select Partition from the Chart Category area, zoom in Number of Partitions-All Instances in the upper right corner, and click Distribution to check whether partitions are evenly distributed on Broker.

          Figure 1 Example of uneven partition distribution on Broker
          +
          • If yes, go to 13.
          • If no, go to 11.
          +

        2. Click the uneven distribution bar on the rightmost, and check whether the node obtained in 5 is included in the unevenly distributed instances. If it is, perform data balancing.
        3. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Collect fault information.

        +
        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 the edit icon in the upper right corner, and set Start 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 engineers and provide the collected logs.
        +
        +

        Alarm Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-38016.html b/docs/mrs/umn/ALM-38016.html new file mode 100644 index 000000000..ab40fca1f --- /dev/null +++ b/docs/mrs/umn/ALM-38016.html @@ -0,0 +1,100 @@ + + +

        ALM-38016 Total Fetch Request Latency Exceeds the Threshold

        +

        Alarm Description

        The system checks the total latency of Fetch requests on Broker instances every 30 seconds. This alarm is generated when the total latency of Fetch requests on a Broker instance has exceeded the threshold for 10 consecutive times.

        +

        This alarm is cleared when the total latency of Fetch requests on the Broker instance is less than or equal to the threshold.

        +

        This alarm applies only to MRS 3.5.0 or later.

        +
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        38016

        +

        Critical (default threshold: 60000)

        +

        Major (default threshold: 30000)

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +
        +
        +
        +

        Impact on the System

        The total latency of Fetch requests on the Broker instance exceeds the threshold. For latency-sensitive services, a large number of service query requests may time out.

        +
        +

        Possible Causes

        • The number of threads used by the Broker instance to process requests is incorrectly configured.
        • A slow disk fault has occurred.
        • The Broker disk I/O is busy.
        • Broker partitions are unevenly distributed, and hotspotting has occurred.
        +
        +

        Handling Procedure

        Check whether the number of threads used by the Broker instance to process requests is appropriate.

        +
        1. Log in to MRS Manager and choose Cluster > Services > Kafka. On the page that is displayed, click Configurations and then All Configurations.
        2. Search for and check the value of num.io.threads. If the value is too small, increase it. You are advised to change the value to twice the number of CPU cores. The maximum value is 64. Save the configuration.
        3. Click the Instances tab, select all Broker instances, click More, and select Instance Rolling Restart.

          Services may be affected or interrupted during the restart. Restart the instances during off-peak hours.

          +
          +

        4. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether a slow disk fault has occurred.

        +
        1. On MRS Manager, choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the host name for which this alarm is generated.
        2. Check whether alarm Slow Disk Fault or Disk Unavailable is generated for the same node in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-12033 Slow Disk Fault or ALM-12063 Disk Unavailable.
          • If no, go to 8.
          +

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

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

        +

        Check whether the Broker disk I/O is busy.

        +
        1. Check whether alarm Busy Broker Disk I/Os exists on the node for which this alarm is generated in 5.

          • If yes, rectify the fault by following the handling procedure of ALM-38009 Busy Broker Disk I/Os and then go to 9.
          • If no, go to 10.
          +

        2. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether Broker partitions are evenly distributed and hotspotting has occurred.

        +
        1. Choose Cluster > Services > Kafka > Chart, select Partition from the Chart Category area, zoom in Number of Partitions-All Instances in the upper right corner, and click Distribution to check whether partitions are evenly distributed on Broker.

          Figure 1 Example of uneven partition distribution on Broker
          +
          • If yes, go to 13.
          • If no, go to 11.
          +

        2. Click the uneven distribution bar on the rightmost, and check whether the node obtained in 5 is included in the unevenly distributed instances. If it is, perform data balancing.
        3. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Collect fault information.

        +
        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 the edit icon in the upper right corner, and set Start 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 engineers and provide the collected logs.
        +
        +

        Alarm Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-38017.html b/docs/mrs/umn/ALM-38017.html new file mode 100644 index 000000000..968035e47 --- /dev/null +++ b/docs/mrs/umn/ALM-38017.html @@ -0,0 +1,95 @@ + + +

        ALM-38017 Partition Reassignment Duration Exceeds the Threshold

        +

        Alarm Description

        The system checks the partition reassignment time every 10 minutes. The check interval can be modified by the Kafka configuration auto.reassign.check.interval.ms. This alarm is generated when the partition reassignment triggered by a Broker scale-out takes more time than the threshold (1440 minutes by default, which can be modified by the Kafka configuration reassignment.total.time.threshold).

        +

        This alarm is cleared when the partition workload balancing is complete.

        +

        This alarm applies only to MRS 3.5.0 or later.

        +
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        38017

        +

        Major

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the cluster service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Trigger Condition

        +

        Specifies the alarm triggering condition.

        +
        +
        +
        +

        Impact on the System

        The Kafka service has unbalanced load for a long time, which may deteriorate the read and write performance.

        +
        +

        Possible Causes

        The amount of data in a partition to be migrated is too large, and the allowed triffic is low.

        +
        +

        Handling Procedure

        1. Log in to the Kafka web UI.

          1. Log in to MRS Manager as a user who has the permission to access the Kafka web UI.
          2. Choose Cluster > Services > Kafka.
          3. On the right of KafkaManager Web UI, click the URL to access the Kafka web UI.
          +

        2. Click Current Reassign Status to view the partition reassignment tasks.

          +

        3. Check the status of the partitions that are being migrated. If the progress remains unchanged for a long time, click Modify Reassignment Throttle to check whether the value of the Throttle parameter is too small.

          +
          • If yes, adjust the Throttle parameter during off-peak hours and click OK to accelerate the migration. Run the command in 4.
          • If no, go to 5.
          +

        4. Wait for 10 minutes and check whether the partition migration progress changes significantly.

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

        +

        Collect fault information.

        +
        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 the edit icon in the upper right corner, and set Start 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +

        +
        + + diff --git a/docs/mrs/umn/ALM-38018.html b/docs/mrs/umn/ALM-38018.html new file mode 100644 index 000000000..cf439d0e9 --- /dev/null +++ b/docs/mrs/umn/ALM-38018.html @@ -0,0 +1,106 @@ + + +

        ALM-38018 Kafka Consumer Lag

        +

        Alarm Description

        If you have configured a threshold to report Kafka consumer lag on the Alarms page of Kafka UI (there is no such rule by default), the system reports the alarm based on the following rules:

        +

        The system checks the topics subscribed to by all consumer groups every 60 seconds. This alarm is generated when the system detects that the difference (lag) between the consumption progress (offset) and the log end offset of the latest message generated in the partition is too large for five consecutive times, and the consumer log exceeds the threshold configured in the alarm rule.

        +

        This alarm is cleared when the system detects that the difference (lag) between the offsets is lower than the configured threshold for five consecutive times.

        +

        This alarm applies only to MRS 3.5.0 or later.

        +
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        38018

        +

        Major (manually configured threshold)

        +

        Major (manually configured threshold)

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        ServiceName

        +

        Specifies the cluster service for which the alarm was generated.

        +

        ConsumerGroup

        +

        Name of the Kafka consumer group for which the alarm is generated.

        +

        Additional Information

        +

        +

        TopicName

        +

        Specifies the Kafka topic for which the alarm is generated.

        +

        ConsumerLag

        +

        Specifies the number of messages yet to be consumed by the consumers in the Kafka topic for which the alarm is generated.

        +
        +
        +
        +

        Impact on the System

        Messages in Kafka topics are retained for a limited period (seven days by default). If messages are not consumed in time, data will be lost.

        +
        +

        Possible Causes

        • The new consumer group starts consuming messages from the beginning topic, leading to consumer lag.
        • The threshold of the consumer lag alarm rule configured by the user is too small.
        • The Kafka topic traffic increases sharply, and a large number of messages are generated in a short period of time.
        • It takes a long time for the downstream system to process the Kafka messages in the topic.
        +
        +

        Handling Procedure

        Check whether the consumer group is new.

        +
        1. Log in to MRS Manager and choose O&M > Alarm > Alarms. View the alarm details. In the Location information area, view the name of the Kafka consumer group for which the alarm is generated. In the Additional Information area, view the topic name.
        2. Check whether the consumer group is new.

          • If yes, go to 3.

            In a new consumer group, the new consumer starts consuming messages from the beginning topic, which can cause a consumer lag alarm. This alarm is automatically cleared once the downstream consumer finishes processing the topic messages.

            +
            +
          • If no, go to 4.
          +

        3. Wait a moment and then check whether the alarm is cleared.

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

        +

        Check whether the alarm rule configuration is improper.

        +
        1. On MRS Manager, choose Cluster > Services > Kafka. On the right of KafkaManager web UI, click the URL link to access the Kafka UI. Click Alarms and check whether the configured threshold of the consumer lag alarm is proper.

          • If yes, go to 6.
          • If no, reconfigure the threshold, save the configuration, and go to 5.
          +

        2. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Check whether the topic traffic increases sharply.

        +
        1. On the Kafka UI, click Topics and check whether a large number of messages are generated in a short period of time.

          • If yes, go to 7.

            If the alarm is caused by a soaring increase in topic traffic, the alarm is automatically cleared after the downstream system consumes topic messages.

            +
            +
          • If no, go to 8.
          +

        2. Wait a moment and then check whether the alarm is cleared.

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

        +

        Check whether it takes a long time for the downstream system to process messages in the Kafka topic.

        +
        1. Check whether the downstream system is consuming messages from the topic at a slow pace.

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

        2. Analyze the reason why downstream jobs cannot quickly consume the topic messages and rectify the fault to accelerate the consumption. Wait 5 minutes and check whether the alarm is automatically cleared.

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

        +

        Collect fault information.

        +
        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 the edit icon in the upper right corner, and set Start 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-43028.html b/docs/mrs/umn/ALM-43028.html new file mode 100644 index 000000000..45571adb4 --- /dev/null +++ b/docs/mrs/umn/ALM-43028.html @@ -0,0 +1,90 @@ + + +

        ALM-43028 JDBCServer Session Overflow

        +

        This section applies only to MRS 3.3.1-LTS or later.

        +
        +

        Alarm Description

        This alarm is generated when the JDBCServer process forwards requests and triffic control is triggered due to insufficient session resources. In this case, too many requests are sent to the JDBCServer process, exceeding the processing capability of the JDBCServer process.

        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        43028

        +

        Minor (default threshold: 9 for three consecutive times)

        +

        Critical (default threshold: 12 for three consecutive times)

        +

        No

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Trigger Condition

        +

        Specifies the alarm triggering condition.

        +
        +
        +
        +

        Impact on the System

        Requests that cannot be processed are responded with a failure message.

        +
        +

        Possible Causes

        The JDBCServer process on the node is overloaded.

        +
        +

        Handling Procedure

        Check the source of the requests for connecting to the JDBCServer service.

        +
        1. On MRS Manager, choose O&M > Alarm > Alarms and select the alarm whose ID is 43028. Check the role name and the IP address of the host where the alarm is generated in Location.
        2. On MRS Manager, choose Cluster > Name of the desired cluster > Services > Spark > Instances, click the JDBCServer for which this alarm is generated, and click jdbcserver-audit in the Log column on the left.
        3. Click the download button in the lower left corner to download the logs to the local PC.
        4. Search for UserIP in the logs, collect statistics on the IP addresses of the clients that submit a large number of requests, and limit the traffic of these clients to reserve resources for other clients.
        +

        Collect fault information.

        +
        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 Spark 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 Clearance

        This alarm needs to be cleared manually.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-43029.html b/docs/mrs/umn/ALM-43029.html new file mode 100644 index 000000000..51b41dad2 --- /dev/null +++ b/docs/mrs/umn/ALM-43029.html @@ -0,0 +1,95 @@ + + +

        ALM-43029 JDBCServer Job Submission Timed Out

        +

        This section applies only to MRS 3.5.0-LTS or later.

        +
        +

        Alarm Description

        After a user submits a JDBC job, the system attempts to create a JDBCServer process and establish a session connection. This alarm is generated if the preset thresholds are exceeded before the connection is established. There are two configuration parameters affecting alarm triggering:

        +
        • spark.thriftserver.proxy.create.session.monitor.enabled: whether to enable the alarm function. The default value is true for the cluster.
        • spark.thriftserver.proxy.create.session.timeout.threshold: Maximum time allowed for submitting a JDBC job. This alarm is reported when the system detects that the job does not start after the threshold is exceeded. The unit is second. The default value is 180s.
        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        43029

        +

        Major

        +

        No

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        User_Queue

        +

        Name of the user who submits the alarm and the queue for which the alarm is generated.

        +
        +
        +
        +

        Impact on the System

        The JDBC job submission time increases due to high system load, which may also affect the job execution efficiency. The job can start properly after this alarm is reported because the detection is asynchronous.

        +
        +

        Possible Causes

        The JDBCServer on the node is overloaded. The cluster health reflected by the system metrics and job execution status is not good.

        +
        +

        Handling Procedure

        Check the JDBCServer instance for which the alarm is generated.

        +
        1. On MRS Manager, choose O&M > Alarm > Alarms and select the alarm whose ID is 43029. Check the role name and the IP address of the host where the alarm is generated in Location. Check the username and queue in Additional Information.
        +

        Re-executing Affected JDBCServer Jobs

        +
        1. Choose Cluster > Services > Yarn > ResourceManager (Active) to log in to the YARN web UI. Find the corresponding application based on the username and queue name in Additional Information and check whether the job submission is affected based on the driver log and Spark UI. Confirm and record the affected job to execute it again.
        2. On MRS Manager, choose Cluster > Services > Spark > Instances, click the JDBCServer for which this alarm is generated, and choose More > Restart Instance.
        3. Choose O&M > Alarm > Alarms, search for the reported alarm, and click Clear in the Operation column.
        4. Execute the affected job and check whether the alarm is triggered again for the job.

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

        +

        Collect fault information.

        +
        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 Spark for the target cluster.
        3. Click the edit icon in the upper right corner, and set Start 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 Clearance

        This alarm needs to be cleared manually.

        +
        +

        Related Information

        None.

        +
        +

        +
        + + diff --git a/docs/mrs/umn/ALM-45003.html b/docs/mrs/umn/ALM-45003.html index 293f05896..a3f3a14e1 100644 --- a/docs/mrs/umn/ALM-45003.html +++ b/docs/mrs/umn/ALM-45003.html @@ -72,7 +72,7 @@

        Possible Causes

        • The alarm threshold is improperly configured.
        • The configuration of the HetuEngine QAS disk cannot meet service requirements. The disk usage reaches the upper limit.

        Handling Procedure

        Check whether the threshold is set properly.

        -
        1. Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. In the service list, choose HetuEngine > Disk > QAS Disk Usage (QAS). Check whether the alarm threshold is set properly. The default threshold is 80% of the disk capacity. You can change the threshold as required.

          • If the threshold is set properly, go to 4.
          • If the threshold is not set properly, go to 2.
          +
          1. Log in to MRS Manager and choose O&M > Alarm > Thresholds. In the service list, choose HetuEngine > Disk > QAS Disk Usage (QAS). Check whether the alarm threshold is set properly. The default threshold is 80% of the disk capacity. You can change the threshold as required.

            • If the threshold is set properly, go to 4.
            • If the threshold is not set properly, go to 2.

          2. Click Modify in the Operation column to modify and save the alarm threshold as required.
          3. Wait 2 minutes and check whether the alarm is cleared.

            • If the alarm is cleared, no further action is required.
            • If the alarm is not cleared, go to 4.

          Check whether the disk usage reaches the upper limit.

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

        2. Wait 2 minutes and check whether the alarm is cleared.

          • If the alarm is cleared, no further action is required.
          • If the alarm fails to be cleared, 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, select HetuEngine 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 the edit icon in the upper right corner, and 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. In the navigation pane on the left, choose Log > Download.
        2. Expand the Service drop-down list, select HetuEngine 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 the edit icon in the upper right corner, and 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/ALM-45004.html b/docs/mrs/umn/ALM-45004.html new file mode 100644 index 000000000..b69f0f9b3 --- /dev/null +++ b/docs/mrs/umn/ALM-45004.html @@ -0,0 +1,97 @@ + + +

        ALM-45004 Tasks Stacked on HetuEngine Compute Instance

        +

        This section applies to MRS 3.3.1 or later.

        +

        Alarm Description

        The system checks the number of running tasks on a HetuEngine compute instance every 30 seconds. This alarm is generated when the number of running tasks is greater than 50.

        +

        This alarm is cleared when the number of tasks running on the HetuEngine compute instance is no more than 50.

        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        45004

        +

        Major

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Running Queries Backlog

        +

        Specifies the tenant name of the compute instance for which the alarm is generated and how much the threshold is exceeded.

        +
        +
        +
        +

        Impact on the System

        The performance of the compute instance deteriorates and the SQL response becomes slow.

        +
        +

        Possible Causes

        • The compute instance specification is too small.
        • Large SQL tasks occupy too many compute resources. No resource is available for other tasks, and the compute instance cannot respond quickly. As a result, tasks are stacked.
        +
        +

        Handling Procedure

        Check whether compute instance resources are properly configured.

        +
        1. Log in to MRS Manager as an administrator who can access the HetuEngine web UI.
        2. Choose O&M > Alarm > Alarms > Tasks Stacked on HetuEngine Compute Instance, check the Additional Information of the alarm, and view and record the tenant name for which the alarm is generated.
        3. Choose Cluster > Services > HetuEngine. In the Basic Information area in the Dashboard tab, click the link next to HSConsole Web UI. The HSConsole page is displayed.
        4. On the Compute Instance page, click Configure in the Operation column of the tenant to which the compute instance belongs. Check whether the resource configured for the compute instance is proper. (The the minimum resources are used by default. You can adjust the configuration based on the site requirements.)

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

        5. Return to the compute instance list, click Stop Instances in the Operation column, and stop instances as prompted.

          Tasks submitted to the stopped compute instances will be interrupted.

          +
          +

        6. Click Configure, add resources to the target compute instance based on the site requirements, and click OK. Click Start Instances and start instances as prompted.
        7. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Check whether there are large SQL tasks.

        +
        1. On the Compute Instances page, expand the instances of the tenant and click LINK in the WebUI column of a compute instance to view the status of all tasks.
        2. In the Sort column, select Execution Time to sort the running tasks and check whether there are tasks that have been running for hours.

          • If yes, go to 10.
          • If no, go to 12.
          +

        3. End the tasks that have been running for a long time based on service requirement and optimize the service SQL statements.
        4. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Collect fault information.

        +
        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 HetuEngine 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 the edit icon in the upper right corner, and 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-45005.html b/docs/mrs/umn/ALM-45005.html new file mode 100644 index 000000000..c7d80cdb4 --- /dev/null +++ b/docs/mrs/umn/ALM-45005.html @@ -0,0 +1,98 @@ + + +

        ALM-45005 CPU Usage of HetuEngine Compute Instance Exceeded the Threshold

        +

        +

        This section applies to MRS 3.3.1 or later.

        +

        Alarm Description

        The system checks the average CPU usage of HetuEngine compute instances every 30 seconds. This alarm is generated when the average CPU usage of the instances is greater than 90%.

        +

        This alarm is cleared when the CPU usage of the HetuEngine compute instances is no more than 90%.

        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        45005

        +

        Major

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Cpu Usage Exceeds The Threshold

        +

        Specifies the tenant name of the compute instance for which the alarm is generated and how much the threshold is exceeded.

        +
        +
        +
        +

        Impact on the System

        The performance of the compute instances deteriorates and the response to SQL statements becomes slow.

        +
        +

        Possible Causes

        • The compute instance specification is too small.
        • Large SQL tasks occupy too many compute resources. No resource is available for other tasks, and the compute instance cannot respond quickly. As a result, tasks are stacked.
        +
        +

        Handling Procedure

        Check whether compute instance resources are properly configured.

        +
        1. Log in to MRS Manager as an administrator who can access the HetuEngine web UI.
        2. Choose O&M > Alarm > Alarms > Tasks Stacked on HetuEngine Compute Instance, check the Additional Information of the alarm, and view and record the tenant name for which the alarm is generated.
        3. Choose Cluster > Services > HetuEngine. In the Basic Information area in the Dashboard tab, click the link next to HSConsole Web UI. The HSConsole page is displayed.
        4. On the Compute Instance page, click Configure in the Operation column of the tenant to which the compute instance belongs. Check whether the resource configured for the compute instance is proper. (The the minimum resources are used by default. You can adjust the configuration based on the site requirements.)

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

        5. Return to the compute instance list, click Stop Instances in the Operation column, and stop instances as prompted.

          Tasks submitted to the stopped compute instances will be interrupted.

          +
          +

        6. Click Configure, add resources to the target compute instance based on the site requirements, and click OK. Click Start Instances and start instances as prompted.
        7. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Check whether there are large SQL tasks.

        +
        1. On the Compute Instances page, expand the instances of the tenant and click LINK in the WebUI column of a compute instance to view the status of all tasks.
        2. In the Sort column, select Execution Time to sort the running tasks and check whether there are tasks that have been running for hours.

          • If yes, go to 10.
          • If no, go to 12.
          +

        3. End the tasks that have been running for a long time based on service requirement and optimize the service SQL statements.
        4. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Collect fault information.

        +
        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 HetuEngine 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 the edit icon in the upper right corner, and 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 engineers and provide the collected logs.
        +
        +

        Alarm Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-45006.html b/docs/mrs/umn/ALM-45006.html new file mode 100644 index 000000000..45514e760 --- /dev/null +++ b/docs/mrs/umn/ALM-45006.html @@ -0,0 +1,99 @@ + + +

        ALM-45006 Memory Usage of a HetuEngine Compute Instance Exceeded the Threshold

        +

        +

        This section applies to MRS 3.3.1 or later.

        +

        Alarm Description

        The system checks the memory usage of HetuEngine compute instances every 30 seconds. This alarm is generated when the memory usage of the instance is greater than 80%.

        +

        This alarm is cleared when the memory usage of the HetuEngine compute instance is no more than 80%.

        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        45006

        +

        Major

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Memory Usage Exceeds The Threshold

        +

        Specifies the tenant name of the compute instance for which the alarm is generated and how much the threshold is exceeded.

        +
        +
        +
        +

        Impact on the System

        The performance of the compute instance deteriorates and the response to service SQL statements becomes slow.

        +
        +

        Possible Causes

        • The compute instance specification is too small.
        • Large SQL tasks occupy too many compute resources. No resource is available for other tasks, and the compute instance cannot respond quickly. As a result, tasks are stacked.
        +
        +

        Handling Procedure

        Check whether compute instance resources are properly configured.

        +
        1. Log in to MRS Manager as an administrator who can access the HetuEngine web UI.
        2. Choose O&M > Alarm > Alarms > Tasks Stacked on HetuEngine Compute Instance, check the Additional Information of the alarm, and view and record the tenant name for which the alarm is generated.
        3. Choose Cluster > Services > HetuEngine. In the Basic Information area in the Dashboard tab, click the link next to HSConsole Web UI. The HSConsole page is displayed.
        4. On the Compute Instance page, click Configure in the Operation column of the tenant to which the compute instance belongs. Check whether the resource configured for the compute instance is proper. (The the minimum resources are used by default. You can adjust the configuration based on the site requirements.)

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

        5. Return to the compute instance list, click Stop Instances in the Operation column, and stop instances as prompted.

          Tasks submitted to the stopped compute instances will be interrupted.

          +
          +

        6. Click Configure, add resources to the target compute instance based on the site requirements, and click OK. Click Start Instances and start instances as prompted.
        7. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Check whether there are large SQL tasks.

        +
        1. On the Compute Instances page, expand the instances of the tenant and click LINK in the WebUI column of a compute instance to view the status of all tasks.
        2. In the Sort column, select Execution Time to sort the running tasks and check whether there are tasks that have been running for hours.

          • If yes, go to 10.
          • If no, go to 12.
          +

        3. End the tasks that have been running for a long time based on service requirement and optimize the service SQL statements.
        4. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Collect fault information.

        +
        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 HetuEngine 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 the edit icon in the upper right corner, and 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 engineers and provide the collected logs.
        +
        +

        Alarm Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +

        +
        + + diff --git a/docs/mrs/umn/ALM-45007.html b/docs/mrs/umn/ALM-45007.html new file mode 100644 index 000000000..46cba56d7 --- /dev/null +++ b/docs/mrs/umn/ALM-45007.html @@ -0,0 +1,96 @@ + + +

        ALM-45007 Number of Workers of a HetuEngine Compute Instance Is Less Than the Threshold

        +

        +

        This section applies to MRS 3.3.1 or later.

        +

        Alarm Description

        The system checks the number of Workers of a HetuEngine compute instance every 60 seconds. This alarm is generated when the number of Workers is less than 80% of the initial value.

        +

        This alarm is cleared when the number of Workers running on the HetuEngine compute instance is no less than 80% of the initial value.

        +

        Alarm Attributes

        + +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        45007

        +

        Major

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Worker Less Threshold

        +

        Specifies the tenant name of the compute instance for which the alarm is generated and how much the threshold is exceeded.

        +
        +
        +
        +

        Impact on the System

        The performance of the compute instance deteriorates and the SQL response becomes slow.

        +
        +

        Possible Causes

        • YARN queue resources are insufficient.
        • A large number of tasks are running, causing OMM memory overflow on Worker nodes. As a result, the number of Worker nodes decreases.
        +
        +

        Handling Procedure

        Check whether YARN resource queue resources are sufficient.

        +
        1. Log in to MRS Manager as an administrator who can access the HetuEngine web UI.
        2. Choose O&M > Alarm > Alarms > Number of Workers of a HetuEngine Compute Instance Is Less Than the Threshold, check the Additional Information of the alarm, and view and record the tenant name for which the alarm is generated.
        3. Click Tenant Resources, select the tenant of the compute instance, and check whether the resource quota of the tenant is sufficient.

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

        4. Increase the maximum percentage of the tenant's resources based on the actual usage.
        5. Wait 5 to 10 minutes and check whether the alarm is cleared.

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

        +

        Check whether there is a large number of running tasks.

        +
        1. Choose Cluster > Services > HetuEngine.
        2. In the Basic Information area on the Dashboard tab page, click the link next to HSConsole Web UI to access the HSConsole page.
        3. On the Compute Instances page, expand the instances of the tenant and click LINK in the WebUI column of a compute instance to view the status of all tasks.
        4. Check whether the number of running tasks exceeds 50.

          • If yes, go to 10.
          • If no, go to 12.
          +

        5. Reduce the number of jobs submitted at a time or add compute instance resources based on service requirements.
        6. Wait 5 to 10 minutes and check whether the alarm is cleared.

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

        +

        Collect fault information.

        +
        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 HetuEngine 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 the edit icon in the upper right corner, and 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +
        + + diff --git a/docs/mrs/umn/ALM-45008.html b/docs/mrs/umn/ALM-45008.html new file mode 100644 index 000000000..3303a0ec7 --- /dev/null +++ b/docs/mrs/umn/ALM-45008.html @@ -0,0 +1,99 @@ + + +

        ALM-45008 Query Latency of HetuEngine Compute Instances Exceeds the Threshold

        +

        +

        This section applies to MRS 3.5.0 or later.

        +

        Alarm Description

        The system checks the query latency of HetuEngine compute instances every 30 seconds. This alarm is generated when the query latency of a HetuEngine compute instance is greater than or equal to 60 seconds.

        +

        This alarm is cleared when the query latency is less than 60s.

        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        45008

        +

        Warning

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Running Queries Delay

        +

        Specifies the tenant name of the compute instance for which the alarm was generated and how much the threshold is exceeded.

        +
        +
        +
        +

        Impact on the System

        If the query latency of the HetuEngine compute instance exceeds the threshold, the SQL response of the service is slow.

        +
        +

        Possible Causes

        • The compute instance specification is too small.
        • Large SQL tasks occupy too many compute resources. No resource is available for other tasks, and the compute instance cannot respond quickly. As a result, tasks are stacked.
        +
        +

        Handling Procedure

        Check whether compute instance resources are properly configured.

        +
        1. Log in to MRS Manager as an administrator who can access the HetuEngine web UI.
        2. Choose O&M > Alarm > Alarms. In the right pane, click alarm Query Latency of HetuEngine Compute Instances Exceeds the Threshold, and view and record the tenant name in Additional Information.
        3. Choose Cluster > Services > HetuEngine. In the Basic Information area on the Dashboard page, click the link next to HSConsole Web UI. The HSConsole page is displayed.
        4. On the Compute Instance page, click Configure in the Operation column of the tenant to which the compute instance belongs. Check whether the resources configured for the compute instance are proper. (The the minimum resources are used by default. You can adjust the configuration based on site requirements.)

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

        5. Return to the compute instance list, click Stop Instances in the Operation column, and stop instances as prompted.

          Tasks submitted to the stopped compute instances will be interrupted.

          +
          +

        6. Click Configure, add resources to the target compute instance based on site requirements, and click OK. Click Start Instances and start instances as prompted.
        7. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Check whether there are large SQL tasks.

        +
        1. On the Compute Instances page, expand the instances of the tenant and click LINK in the WebUI column of a compute instance to view the status of all tasks.
        2. In the Sort column, select Execution Time to sort the running tasks and check whether there are tasks that have been running for hours.

          • If yes, go to 10.
          • If no, go to 12.
          +

        3. Stop the tasks that have been running for a long time based on service requirement and optimize the service SQL statements.
        4. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Collect fault information.

        +
        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 HetuEngine 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 the edit icon in the upper right corner, and 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +

        +
        + + diff --git a/docs/mrs/umn/ALM-45009.html b/docs/mrs/umn/ALM-45009.html new file mode 100644 index 000000000..7064ce99e --- /dev/null +++ b/docs/mrs/umn/ALM-45009.html @@ -0,0 +1,99 @@ + + +

        ALM-45009 Task Failure Rate of HetuEngine Compute Instances Exceeds the Threshold

        +

        +

        This section applies to MRS 3.5.0 or later.

        +

        Alarm Description

        The system checks the task failure rate of HetuEngine compute instances every 30 seconds. This alarm is generated when the task failure rate of a HetuEngine compute instance is greater than or equal to 50%.

        +

        This alarm is cleared when the task failure rate is less than 50%.

        +
        +

        Alarm Attributes

        +
        + + + + + + + + + +

        Alarm ID

        +

        Alarm Severity

        +

        Auto Cleared

        +

        45009

        +

        Warning

        +

        Yes

        +
        +
        +
        +

        Alarm Parameters

        +
        + + + + + + + + + + + + + + + + + + + + + + +

        Type

        +

        Parameter

        +

        Description

        +

        Location Information

        +

        Source

        +

        Specifies the cluster for which the alarm was generated.

        +

        ServiceName

        +

        Specifies the service for which the alarm was generated.

        +

        RoleName

        +

        Specifies the role for which the alarm was generated.

        +

        HostName

        +

        Specifies the host for which the alarm was generated.

        +

        Additional Information

        +

        Task Failure Rate

        +

        Specifies the tenant name of the compute instance for which the alarm was generated and how much the threshold is exceeded.

        +
        +
        +
        +

        Impact on the System

        If the task failure rate of HetuEngine compute instances is too high, service running is adversely affected. You need to locate and rectify the fault in a timely manner.

        +
        +

        Possible Causes

        • The compute instance specification is too small.
        • Large SQL tasks occupy too many compute resources. No resource is available for other tasks, and the compute instance cannot respond quickly. As a result, tasks are stacked.
        +
        +

        Handling Procedure

        Check whether compute instance resources are properly configured.

        +
        1. Log in to MRS Manager as an administrator who can access the HetuEngine web UI.
        2. Choose O&M > Alarm > Alarms. In the right pane, click alarm Task Failure Rate of HetuEngine Compute Instances Exceeds the Threshold, and view and record the tenant name in Additional Information.
        3. Choose Cluster > Services > HetuEngine. In the Basic Information area on the Dashboard page, click the link next to HSConsole Web UI. The HSConsole page is displayed.
        4. On the Compute Instance page, click Configure in the Operation column of the tenant to which the compute instance belongs. Check whether the resources configured for the compute instance are proper. (The the minimum resources are used by default. You can adjust the configuration based on site requirements.)

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

        5. Return to the compute instance list, click Stop Instances in the Operation column, and stop instances as prompted.

          Tasks submitted to the stopped compute instances will be interrupted.

          +
          +

        6. Click Configure, add resources to the target compute instance based on site requirements, and click OK. Click Start Instances and start instances as prompted.
        7. Wait 2 minutes and check whether the alarm is cleared.

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

        +

        Check whether there are large SQL tasks.

        +
        1. On the Compute Instances page, expand the instances of the tenant and click LINK in the WebUI column of a compute instance to view the status of all tasks.
        2. In the Sort column, select Execution Time to sort the running tasks and check whether there are tasks that have been running for hours.

          • If yes, go to 10.
          • If no, select all failed tasks in the Failed column, collect detailed error information about SQL running in the computing instance, and go to 12.
          +

        3. Stop the tasks that have been running for a long time based on service requirement and optimize the service SQL statements.
        4. Wait 2 minutes and check whether the alarm is cleared.

          • If yes, no further action is required.
          • If no, select all failed tasks in the Failed column, collect detailed error information about SQL running in the computing instance, and go to 12.
          +

        +

        Collect fault information.

        +
        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 HetuEngine 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 the edit icon in the upper right corner, and 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        +
        +

        Related Information

        None.

        +
        +

        +
        + + diff --git a/docs/mrs/umn/ALM-45289.html b/docs/mrs/umn/ALM-45289.html index c0bfbe62f..99e1be299 100644 --- a/docs/mrs/umn/ALM-45289.html +++ b/docs/mrs/umn/ALM-45289.html @@ -65,15 +65,15 @@

    Possible Causes

    The heap memory of the PolicySync instance is overused or the heap memory is inappropriately allocated.

    -

    Handling Procedure

    1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45289 PolicySync 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 > PolicySync Heap Memory Usage. Click OK.
    3. Check whether the heap memory used by PolicySync 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 > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 PolicySync cannot meet the heap memory required by the PolicySync process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the PolicySync heap memory usage.

      +

      Handling Procedure

      1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45289 PolicySync 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 > PolicySync Heap Memory Usage. Click OK.
      3. Check whether the heap memory used by PolicySync 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 > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 PolicySync cannot meet the heap memory required by the PolicySync process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the PolicySync heap memory usage.

      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.

          When the service is rebooted, it becomes unavailable and can disrupt business operations. When the instance is rebooted, it cannot be used and any tasks running on the current instance node will fail.

      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 Ranger for the target cluster.
      3. Click the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

      This alarm is automatically cleared after the fault is rectified.

      diff --git a/docs/mrs/umn/ALM-45290.html b/docs/mrs/umn/ALM-45290.html index 88d577167..e269ee96e 100644 --- a/docs/mrs/umn/ALM-45290.html +++ b/docs/mrs/umn/ALM-45290.html @@ -66,15 +66,15 @@

      Possible Causes

      The direct memory of the PolicySync process is overused or the direct memory is inappropriately allocated.

      Handling Procedure

      Check the direct memory usage.

      -
      1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45290 PolicySync 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 > PolicySync Direct Memory Usage. Click OK.
      3. Check whether the direct memory used by the PolicySync 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 > Services > Ranger > Instance > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 configured for PolicySync cannot meet the direct memory required by the PolicySync process. You are advised to check the direct memory usage of PolicySync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer direct memory usage.

        +
        1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45290 PolicySync 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 > PolicySync Direct Memory Usage. Click OK.
        3. Check whether the direct memory used by the PolicySync 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 > Services > Ranger > Instance > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 configured for PolicySync cannot meet the direct memory required by the PolicySync process. You are advised to check the direct memory usage of PolicySync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer direct memory usage.

        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.

            When the service is rebooted, it becomes unavailable and can disrupt business operations. When the instance is rebooted, it cannot be used and any tasks running on the current instance node will fail.

        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 Ranger for the target cluster.
        3. Click the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

        This alarm is automatically cleared after the fault is rectified.

        diff --git a/docs/mrs/umn/ALM-45291.html b/docs/mrs/umn/ALM-45291.html index a5d551eeb..99f070c00 100644 --- a/docs/mrs/umn/ALM-45291.html +++ b/docs/mrs/umn/ALM-45291.html @@ -66,15 +66,15 @@

        Possible Causes

        The non-heap memory of the PolicySync instance is overused or the non-heap memory is inappropriately allocated.

        Handling Procedure

        Check non-heap memory usage.

        -
        1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45291 PolicySync 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 > PolicySync Non-Heap Memory Usage. Click OK.
        3. Check whether the non-heap memory used by PolicySync reaches the threshold (90% 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 > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 PolicySync instance cannot meet the non-heap memory required by the PolicySync process. You are advised to change the value of -XX:MaxPermSize in GC_OPTS to twice that of the current non-heap memory size or change the value based on site requirements.

          +
          1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45291 PolicySync 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 > PolicySync Non-Heap Memory Usage. Click OK.
          3. Check whether the non-heap memory used by PolicySync reaches the threshold (90% 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 > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 PolicySync instance cannot meet the non-heap memory required by the PolicySync process. You are advised to change the value of -XX:MaxPermSize in GC_OPTS to twice that of 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.

              When the service is rebooted, it becomes unavailable and can disrupt business operations. When the instance is rebooted, it cannot be used and any tasks running on the current instance node will fail.

          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 Ranger for the target cluster.
          3. Click the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

          This alarm is automatically cleared after the fault is rectified.

          diff --git a/docs/mrs/umn/ALM-45292.html b/docs/mrs/umn/ALM-45292.html index 3183da56e..3f06d296a 100644 --- a/docs/mrs/umn/ALM-45292.html +++ b/docs/mrs/umn/ALM-45292.html @@ -67,15 +67,15 @@

          Possible Causes

          The heap memory of the PolicySync process is overused or inappropriately allocated, causing frequent occurrence of the GC process.

          Handling Procedure

          Check the GC duration.

          -
          1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45292 PolicySync 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 > PolicySync GC Duration. Click OK.
          3. Check whether the GC duration of the PolicySync 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 > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 PolicySync cannot meet the heap memory required by the PolicySync process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the PolicySync heap memory usage.

            +
            1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45292 PolicySync 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 > PolicySync GC Duration. Click OK.
            3. Check whether the GC duration of the PolicySync 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 > PolicySync. Click Instance Configuration and then All Configurations, and choose PolicySync > 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 PolicySync cannot meet the heap memory required by the PolicySync process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the PolicySync heap memory usage.

            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.

                When the service is rebooted, it becomes unavailable and can disrupt business operations. When the instance is rebooted, it cannot be used and any tasks running on the current instance node will fail.

            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 Ranger for the target cluster.
            3. Click the edit icon in the upper right corner, and set Start 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 the edit icon in the upper right corner, and set Start 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 Clearance

            This alarm is automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-45293.html b/docs/mrs/umn/ALM-45293.html new file mode 100644 index 000000000..abccd4676 --- /dev/null +++ b/docs/mrs/umn/ALM-45293.html @@ -0,0 +1,132 @@ + + +

            ALM-45293 Ranger User Synchronization Exception

            +

            Alarm Description

            The system checks synchronization status of the UserSync process every 5 minutes. This alarm is generated when a synchronization exception occurs. This alarm is cleared when user synchronization becomes normal.

            +
            +

            Alarm Attributes

            +
            + + + + + + + + + + + + + +

            Alarm ID

            +

            Alarm Severity

            +

            Alarm Type

            +

            Service Type

            +

            Auto Cleared

            +

            45293

            +

            Major

            +

            Quality of service

            +

            Ranger

            +

            Yes

            +
            +
            +
            +

            Alarm Changes

            +
            + + + + + + + + + + + +

            Change Type

            +

            Version

            +

            Description

            +

            Reason for Change

            +

            New

            +

            3.3.1

            +

            New alarm

            +

            New alarm

            +
            +
            +
            +

            Alarm Parameters

            +
            + + + + + + + + + + + + + + + + + + + + + + +

            Type

            +

            Parameter

            +

            Description

            +

            Location Information

            +

            Source

            +

            Specifies the cluster for which the alarm was generated.

            +

            ServiceName

            +

            Specifies the service for which the alarm was generated.

            +

            RoleName

            +

            Specifies the role for which the alarm was generated.

            +

            HostName

            +

            Specifies the host for which the alarm was generated.

            +

            Additional Information

            +

            Trigger Condition

            +

            Specifies the trigger condition, that is, an exception occurs during Ranger user synchronization.

            +
            +
            +
            +

            Impact on the System

            Unsynchronized users cannot access the native Ranger page and set permission policies for other users. As a result, some users may fail to access services that require Ranger permissions.

            +
            +

            Possible Causes

            The RangerAdmin instance is abnormal.

            +

            The UserSync instance is abnormal.

            +

            The LDAP service is abnormal.

            +
            +

            Handling Procedure

            Check whether the UserSync is abnormal.

            +
            1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45293 Ranger User Synchronization Exception. 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 UserSync instance on the host for which the alarm is generated, and check whether the instance status is abnormal.

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

            3. On MRS Manager, choose Cluster > Services > Ranger, click Instances, and click UserSync. On the displayed page, click More > Restart Instance, or restart the Ranger service.
            4. Check whether the alarm is cleared in 5 to 10 minutes.

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

            +

            Check whether the RangerAdmin is abnormal.

            +
            1. On MRS Manager, choose O&M > Alarm > Alarms to check whether alarm "ALM-45276 Abnormal RangerAdmin Status" is reported.

              • If yes, go to 6.
              • If no, go to 8.
              +

            1. Rectify the fault by following the handling procedure of "ALM-45276 Abnormal RangerAdmin Status".
            2. Check whether the alarm is cleared in 5 to 10 minutes.

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

            +

            Check whether the LDAP service is abnormal.

            +
            1. On MRS Manager, choose O&M > Alarm > Alarms to check whether alarm "ALM-25000 LdapServer Service Unavailable" is reported.

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

            1. Clear the alarm according to the handling procedure of "ALM-25000 LdapServer Service Unavailable".
            2. Check whether the alarm is cleared in 5 to 10 minutes.

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

            +

            Collect fault information.

            +
            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 the edit icon in the upper right corner, and set Start 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 Clearance

            This alarm is automatically cleared after the fault is rectified.

            +
            +

            Related Information

            None.

            +
            +

            +
            + + diff --git a/docs/mrs/umn/ALM-45294.html b/docs/mrs/umn/ALM-45294.html new file mode 100644 index 000000000..180dcd0e0 --- /dev/null +++ b/docs/mrs/umn/ALM-45294.html @@ -0,0 +1,124 @@ + + +

            ALM-45294 RangerKMS Process Is Abnormal

            +

            Alarm Description

            The RangerKMS process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.

            +

            This alarm is cleared when the process status recovers.

            +
            +

            Alarm Attributes

            +
            + + + + + + + + + + + + + +

            Alarm ID

            +

            Alarm Severity

            +

            Alarm Type

            +

            Service Type

            +

            Auto Cleared

            +

            45294

            +

            Major

            +

            Quality of service

            +

            Ranger

            +

            Yes

            +
            +
            +
            +

            Alarm Changes

            +
            + + + + + + + + + + + +

            Change Type

            +

            Version

            +

            Description

            +

            Reason for Change

            +

            New

            +

            3.3.1

            +

            New alarm

            +

            New alarm

            +
            +
            +
            +

            Alarm Parameters

            +
            + + + + + + + + + + + + + + + + + + + + + + +

            Type

            +

            Parameter

            +

            Description

            +

            Location Information

            +

            Source

            +

            Specifies the cluster for which the alarm was generated.

            +

            ServiceName

            +

            Specifies the service for which the alarm was generated.

            +

            RoleName

            +

            Specifies the role for which the alarm was generated.

            +

            HostName

            +

            Specifies the host for which the alarm was generated.

            +

            Additional Information

            +

            Trigger Condition

            +

            Specifies the alarm triggering condition.

            +
            +
            +
            +

            Impact on the System

            If the process status is abnormal, the process cannot provide services properly. As a result, the entire service may become abnormal.

            +
            +

            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. The process may also be suspended and enter the T state.

            +
            +

            Handling Procedure

            Check whether the process is in the D, Z, or T state.

            +
            1. Log in to MRS Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

              • If the alarm is not in the list, no further action is required.
              • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.
              +

            2. Log in to the host where the alarm is generated as the root user and run the su - omm command to switch to the omm user.
            3. Run the following command to check the process state:

              ps ww -eo stat,cmd| grep -w Dproc_rangerkms | grep -v grep | awk '{print$1}'

              +

            4. Check whether the command output contains any abnormal state (D, Z, or T).

              • If the output contains any abnormal state, go to 5.
              • If the output does not contain abnormal states, go to 7.
              +

            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. Wait 5 minutes and check whether the alarm is cleared.

              • If the alarm is cleared, no further action is required.
              • If the alarm fails to be cleared, go to 7.
              +

            +

            Collect fault information.

            +
            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 Ranger for the target cluster.
            3. Click the edit icon in the upper right corner, and set Start 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 Clearance

            This alarm is automatically cleared after the fault is rectified.

            +
            +

            Related Information

            None.

            +
            +
            + + diff --git a/docs/mrs/umn/ALM-45435.html b/docs/mrs/umn/ALM-45435.html index 9571065ca..e915ddd1c 100644 --- a/docs/mrs/umn/ALM-45435.html +++ b/docs/mrs/umn/ALM-45435.html @@ -65,7 +65,7 @@

            Possible Causes

            Table metadata modification fails or is not executed on one or more ClickHouseServer nodes.

            -

            Handling Procedure

            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
            2. Log in to the node where the client is installed as the client installation user and run the following commands:

              cd {Client installation path}

              +

              Handling Procedure

              1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
              2. Log in to the node where the client is installed as the client installation user and run the following commands:

                cd {Client installation path}

                source bigdata_env

                • For a cluster with Kerberos authentication enabled (security mode):

                  kinit Component service user

                  clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port 9440 --secure

                  @@ -81,7 +81,7 @@

              1. If the table has been deleted, manually clear the alarm and check whether the alarm is reported again.

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

              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 the edit icon 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 the edit icon 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 Clearance

              This alarm is automatically cleared after the fault is rectified.

              diff --git a/docs/mrs/umn/ALM-45436.html b/docs/mrs/umn/ALM-45436.html index 541e59647..a8b1f5949 100644 --- a/docs/mrs/umn/ALM-45436.html +++ b/docs/mrs/umn/ALM-45436.html @@ -63,7 +63,7 @@

            Possible Causes

            The data write policy is improper, causing unbalanced data among nodes.

            -

            Handling Procedure

            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
            2. Log in to the node where the client is installed as the client installation user and run the following commands:

              cd {Client installation path}

              +

              Handling Procedure

              1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
              2. Log in to the node where the client is installed as the client installation user and run the following commands:

                cd {Client installation path}

                source bigdata_env

                • Security mode (with Kerberos enabled):

                  kinit Component service user

                  clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port 9440 --secure

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

                • Balance data with a few clicks or migrate data based on service requirements.
                • 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. 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 the edit icon 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 the edit icon 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 Clearance

              This alarm is automatically cleared after the fault is rectified.

              diff --git a/docs/mrs/umn/ALM-45437.html b/docs/mrs/umn/ALM-45437.html index 728ee8acc..9bef05fdd 100644 --- a/docs/mrs/umn/ALM-45437.html +++ b/docs/mrs/umn/ALM-45437.html @@ -66,7 +66,7 @@

            Possible Causes

            The data distribution in the ClickHouse table is improper, or the background merge task is executed slowly.

            -

            Handling Procedure

            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
            2. Log in to the node where the client is installed as the client installation user and run the following commands:

              cd {Client installation path}

              +

              Handling Procedure

              1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
              2. Log in to the node where the client is installed as the client installation user and run the following commands:

                cd {Client installation path}

                source bigdata_env

                • Security mode (with Kerberos enabled):

                  kinit Component service user

                  clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port 9440 --secure

                  @@ -78,7 +78,7 @@
                • If the number of parts does not decrease, check whether the partition key of the table is set properly. If the number of partitions is too large, rectify the service logic.
                • If the command output is empty, the table does not exist. This alarm is a historical alarm and can be ignored. Manually clear it.

            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 the edit icon 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 the edit icon 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 Clearance

            This alarm is automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-45438.html b/docs/mrs/umn/ALM-45438.html index 0b69d9178..6434286af 100644 --- a/docs/mrs/umn/ALM-45438.html +++ b/docs/mrs/umn/ALM-45438.html @@ -66,9 +66,9 @@

          Possible Causes

          The disk capacity of the ClickHouseServer node is too small.

          -

          Handling Procedure

          1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
          2. Expand the disk capacity of the node for which the alarm is generated.
          3. Go to 4 if the expansion fails or the alarm persists after the expansion.
          +

          Handling Procedure

          1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
          2. Expand the disk capacity of the node for which the alarm is generated.
          3. Go to 4 if the expansion fails or the alarm persists after the expansion.

          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 the edit icon 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 the edit icon 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 Clearance

          This alarm is automatically cleared after the fault is rectified.

          diff --git a/docs/mrs/umn/ALM-45439.html b/docs/mrs/umn/ALM-45439.html index 28f1dbb1e..4a73cec85 100644 --- a/docs/mrs/umn/ALM-45439.html +++ b/docs/mrs/umn/ALM-45439.html @@ -6,7 +6,7 @@

          Alarm Description

          The system checks the disk capacity of the ClickHouseServer node every 1 minute. This alarm is generated when the system detects that the disk capacity exceeds 90% and the ClickHouseServer node enters the read-only mode.

          This alarm is automatically cleared when the system detects that the disk capacity is lower than 90% and the ClickHouseServer node exits the read-only mode.

          If the ClickHouseServer node is in read-only mode and you need to log in to the client to clear data, you can manually exit the read-only mode using the following method:

          -

          Log in to FusionInsight Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, search for profiles.default.readonly, and change its value to 0.

          +

          Log in to MRS Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, search for profiles.default.readonly, and change its value to 0.

          Alarm Attributes

          @@ -69,11 +69,11 @@

          Possible Causes

          The disk usage of the ClickHouse node exceeds 90%.

          -

          Handling Procedure

          1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
          2. Expand the disk capacity of the node for which the alarm is generated.
          3. Go to 4 if the expansion fails or the alarm persists after the expansion.

            After the capacity expansion, this alarm can be automatically cleared only when profiles.default.readonly is auto. If its value has been manually changed, change it back to auto. If profiles.default.readonly needs to be set to 0 or 1 based on service requirements, manually clear this alarm.

            +

            Handling Procedure

            1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
            2. Expand the disk capacity of the node for which the alarm is generated.
            3. Go to 4 if the expansion fails or the alarm persists after the expansion.

              After the capacity expansion, this alarm can be automatically cleared only when profiles.default.readonly is auto. If its value has been manually changed, change it back to auto. If profiles.default.readonly needs to be set to 0 or 1 based on service requirements, manually clear this alarm.

            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 the edit icon 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 the edit icon 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 Clearance

            This alarm is automatically cleared after the fault is rectified.

            diff --git a/docs/mrs/umn/ALM-45440.html b/docs/mrs/umn/ALM-45440.html index 1a95478bf..c1d040808 100644 --- a/docs/mrs/umn/ALM-45440.html +++ b/docs/mrs/umn/ALM-45440.html @@ -66,7 +66,7 @@

            Possible Causes

            • The ClickHouse service is overloaded.
            • The connection between the ClickHouse and ZooKeeper is abnormal.

            Handling Procedure

            Check whether the ClickHouse service load is heavy.

            -
            1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the database name, table name, role name and IP address for the hostname in Location.
            2. Log in to the node where the client is installed as the client installation user and run the following commands:

              cd {Client installation path}

              +
              1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the database name, table name, role name and IP address for the hostname in Location.
              2. Log in to the node where the client is installed as the client installation user and run the following commands:

                cd {Client installation path}

                source bigdata_env

                • For a cluster with Kerberos authentication enabled (security mode):

                  kinit Component service user

                  clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port 9440 --secure

                  @@ -81,11 +81,11 @@

                  Check whether an error message similar to the following is displayed:

                  Not executing fetch of part xxx because n fetches already executing, max n
                  • If yes, go to 7.
                  • If no, go to 9.
                  -

                • On FusionInsight Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, and check whether the value of background_pool_size is twice the number of cores on the node.

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

                • On MRS Manager, choose Cluster > Services > ClickHouse > Configurations > All Configurations, and check whether the value of background_pool_size is twice the number of cores on the node.

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

                • Set this parameter to twice the number of cores on the node and synchronize the configuration. Wait for a while and check whether the alarm is cleared.

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

              Check the connectivity between ClickHouse and ZooKeeper.

              -
              1. Log in to the node where the ClickHouseServer instance is located, go to ${BIGDATA_HOME}/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc, and check whether the port numbers of the ClickHouseServer and ZooKeeper in the config.xml file are the same, as shown in the following information in bold:

                To view the ZooKeeper port number, choose Cluster > Services > ZooKeeper > Configurations > All Configurations on FusionInsight Manager, and check the value of clientPort.

                +
                1. Log in to the node where the ClickHouseServer instance is located, go to ${BIGDATA_HOME}/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc, and check whether the port numbers of the ClickHouseServer and ZooKeeper in the config.xml file are the same, as shown in the following information in bold:

                  To view the ZooKeeper port number, choose Cluster > Services > ZooKeeper > Configurations > All Configurations on MRS Manager, and check the value of clientPort.

                    <zookeeper>
     <session_timeout_ms>10000</session_timeout_ms>
@@ -106,7 +106,7 @@
                2. Change the port number to the ZooKeeper port number, restart the ClickHouseServer instance, and check whether the alarm is cleared.

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

                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 the edit icon 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 the edit icon 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 Clearance

                This alarm is automatically cleared after the fault is rectified.

                diff --git a/docs/mrs/umn/ALM-45441.html b/docs/mrs/umn/ALM-45441.html index d89c43029..93e35ddd1 100644 --- a/docs/mrs/umn/ALM-45441.html +++ b/docs/mrs/umn/ALM-45441.html @@ -62,12 +62,12 @@

                Possible Causes

                • The ZooKeeper service is abnormal.
                • The ClickHouse service is overloaded.

                Handling Procedure

                Check whether ZooKeeper is normal.

                -
                1. On FusionInsight Manager, choose Cluster > Services > ZooKeeper > quorumpeer.
                2. Check whether ZooKeeper instances are normal.

                  • If yes, go to 6.
                  • If no, go to 3.
                  +
                  1. On MRS Manager, choose Cluster > Services > ZooKeeper > quorumpeer.
                  2. Check whether ZooKeeper instances are normal.

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

                  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 5.
                    • If no, go to 10.

                  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 whether the ClickHouse service load is heavy.

                  -
                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                  2. Log in to the node where the client is installed as the client installation user and run the following commands:

                    cd {Client installation path}

                    +
                    1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                    2. Log in to the node where the client is installed as the client installation user and run the following commands:

                      cd {Client installation path}

                      source bigdata_env

                      • For a cluster with Kerberos authentication enabled (security mode):

                        kinit Component service user

                        clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port 9440 --secure

                        @@ -78,7 +78,7 @@

                      • Check whether a large amount of data is written. If yes, wait until the task is complete 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. 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 the edit icon 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 the edit icon 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 Clearance

                This alarm is automatically cleared after the fault is rectified.

                diff --git a/docs/mrs/umn/ALM-45442.html b/docs/mrs/umn/ALM-45442.html index b481fcd9b..99b8b4390 100644 --- a/docs/mrs/umn/ALM-45442.html +++ b/docs/mrs/umn/ALM-45442.html @@ -61,12 +61,12 @@

                Possible Causes

                The ClickHouse service is overloaded.

                -

                Handling Procedure

                1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                2. Choose Cluster > ClickHouse > Instance, select an instance based on the alarm information. Choose Chart > Concurrency to check whether the actual number of concurrent SQL statements is greater than SQL concurrency threshold.

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

                  Handling Procedure

                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                  2. Choose Cluster > ClickHouse > Instance, select an instance based on the alarm information. Choose Chart > Concurrency to check whether the actual number of concurrent SQL statements is greater than SQL concurrency threshold.

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

                  3. Confirm with the user whether a large number of tasks were being executed during the alarming period.

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

                  4. On FusionInsight Manager, choose O&M and click Alarm > Thresholds in the navigation pane on the left. On the displayed page, click ClickHouse > Concurrency and adjust the threshold, or wait until the task is complete. Check whether the alarm is cleared.

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

                  5. On MRS Manager, choose O&M and click Alarm > Thresholds in the navigation pane on the left. On the displayed page, click ClickHouse > Concurrency and adjust the threshold, or wait until the task is complete. 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. 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 the edit icon 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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  diff --git a/docs/mrs/umn/ALM-45443.html b/docs/mrs/umn/ALM-45443.html index d6c0e9655..8a138cc69 100644 --- a/docs/mrs/umn/ALM-45443.html +++ b/docs/mrs/umn/ALM-45443.html @@ -62,7 +62,7 @@

                  Possible Causes

                  • The ClickHouse service is overloaded.
                  • The execution of SQL statements takes a long time.

                  Handling Procedure

                  Check whether the ClickHouse service load is heavy.

                  -
                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                  2. Log in to the node where the client is installed as the client installation user and run the following commands:

                    cd {Client installation path}

                    +
                    1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                    2. Log in to the node where the client is installed as the client installation user and run the following commands:

                      cd {Client installation path}

                      source bigdata_env

                      • For a cluster with Kerberos authentication enabled (security mode):

                        kinit Component service user

                        clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port --secure

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

                    Checking whether the SQL statements take a long time.

                    -
                    1. Check the logical cluster to which the alarm object belongs. Log in to FusionInsight Manager, click Cluster, choose Services > ClickHouse, and click Logic Cluster. On the displayed page, choose Query Management > Ongoing Slow Queries. Check which SQL statements take a long time on the displayed page, confirm with the user to adjust services, optimize slow SQL statements, and check whether the optimization is successful.

                      • If yes, go to 5.
                      • If no, go to 6.
                      +
                      1. Check the logical cluster to which the alarm object belongs. Log in to MRS Manager, click Cluster, choose Services > ClickHouse, and click Logic Cluster. On the displayed page, choose Query Management > Ongoing Slow Queries. Check which SQL statements take a long time on the displayed page, confirm with the user to adjust services, optimize slow SQL statements, and check whether the optimization is successful.

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

                      2. After the SQL statements are complete, 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. 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 the edit icon 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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  diff --git a/docs/mrs/umn/ALM-45444.html b/docs/mrs/umn/ALM-45444.html index 63b859419..431fcda2d 100644 --- a/docs/mrs/umn/ALM-45444.html +++ b/docs/mrs/umn/ALM-45444.html @@ -60,7 +60,7 @@

                Possible Causes

                The ClickHouse process runs improperly.

                -

                Handling Procedure

                1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                2. Log in to the node where the client is installed as the client installation user and run the following commands:

                  cd {Client installation path}

                  +

                  Handling Procedure

                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                  2. Log in to the node where the client is installed as the client installation user and run the following commands:

                    cd {Client installation path}

                    source bigdata_env

                    • For a cluster with Kerberos authentication enabled (security mode):

                      kinit Component service user

                      clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port 9440 --secure

                      @@ -71,7 +71,7 @@

                    • Wait for several minutes 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. 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 the edit icon 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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  diff --git a/docs/mrs/umn/ALM-45445.html b/docs/mrs/umn/ALM-45445.html new file mode 100644 index 000000000..18c7151d9 --- /dev/null +++ b/docs/mrs/umn/ALM-45445.html @@ -0,0 +1,131 @@ + + +

                  ALM-45445 Failed to Send Data Files to Remote Shards When ClickHouse Writes Data to a Distributed Table

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  The ClickHouse instance checks the distributed table every 300 seconds. If the number of consecutive failures exceeds the threshold, an alarm is generated. In this case, the node where the ClickHouse instance writes data to the distributed table cannot send data files to remote shard nodes.

                  +

                  This alarm is cleared when the number of consecutive failures falls below the threshold.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45445

                  +

                  Major

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Changes

                  +
                  + + + + + + + + + + + +

                  Change Type

                  +

                  Version

                  +

                  Description

                  +

                  Reason for Change

                  +

                  New

                  +

                  3.3.1

                  +

                  New alarm

                  +

                  New alarm

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  The results of operations such as distributed table queries are abnormal.

                  +
                  +

                  Possible Causes

                  The status of some ClickHouse shard nodes is abnormal.

                  +
                  +

                  Handling Procedure

                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address of the hostname in Location.
                  2. Log in to the node where the client is installed as the client installation user and run the following commands:

                    cd {Client installation path}

                    +

                    source bigdata_env

                    +
                    • For a cluster with Kerberos authentication enabled (security mode):

                      kinit Component service user

                      +

                      clickhouse client --host IP address of the ClickHouseServer instance for which the alarm is reported --port 9440 --secure

                      +
                    • For a cluster with Kerberos authentication disabled (normal mode):

                      clickhouse client --host IP address of the ClickHouseServer instance for which the alarm is reported --user Username --password --port 9000

                      +
                    +

                  3. Run the following SQL statement to obtain the shard based on the value of data_path. For example, if the value of data_path is /srv/Bigdata/clickhouse/data1.../shard2_all_replicas, the desired shard is shard2.

                    select database, table, data_path, data_files, error_count from system.distribution_queue where data_files != 0 and error_count != 0;

                    +

                  4. Run the following SQL statement to obtain the node IP address (value of the host field in the system table system.clusters) of the shard where data fails to be sent to (shard_num obtained in 3):

                    select * from system.clusters;

                    +

                  5. Log in to the ClickHouse node (IP address obtained in 2) by referring to 4, run the following statement, and check whether the result can be returned:

                    SELECT 1;

                    +

                    If yes, go to 6.

                    +

                    If no, go to 10.

                    +

                  6. Log in to the ClickHouse node (IP address obtained in 2) by referring to 4, run the following statement (database_name and table_name indicate the database name and table name of the local table corresponding to the distributed table):

                    select name,type from system.columns where database='database_name' and table='table_name'

                    +

                  7. Log in to the ClickHouse node for which the alarm is generated by referring to 2 and run the following statement (database_name and table_name indicate the database name and table name of the distributed table to which data is written):

                    select name,type from system.columns where database='database_name' and table='table_name'

                    +

                  8. Check whether the results obtained in 6 and 7 are the same.

                    If yes, go to 10.

                    +

                    If no, ensure that the column information of the distributed table is consistent with that of the corresponding local table, and then try to write data to the distributed table.

                    +

                  9. Wait for several 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 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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45446.html b/docs/mrs/umn/ALM-45446.html new file mode 100644 index 000000000..8b9c4a4dd --- /dev/null +++ b/docs/mrs/umn/ALM-45446.html @@ -0,0 +1,105 @@ + + +

                  ALM-45446 Mutation Task of ClickHouse Is Not Complete for a Long Time

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  The system checks mutation tasks every 5 minutes. This alarm is generated when the system detects that a mutation task has been running for at least slow_mutation_cost_time minutes. This alarm is automatically cleared when the system does not detect any running mutation task or the running time of a mutation task is less than slow_mutation_cost_time minutes.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45446

                  +

                  Minor

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  • Server resources are occupied, and the performance of the ClickHouse service deteriorates.
                  • Data is inconsistent.
                  +
                  +

                  Possible Causes

                  The data volume is too large. As a result, the mutation task runs slowly or is suspended.

                  +
                  +

                  Handling Procedure

                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                  2. Log in to the node where the client is installed and run the following commands:

                    cd {Client installation path}

                    +

                    source bigdata_env

                    +
                    • Security mode (with Kerberos enabled):

                      kinit Component service user

                      +

                      clickhouse client --host IP address of the ClickHouseServer instance for which the alarm is reported --port 21427 --secure

                      +
                    • Normal mode (with Kerberos disabled):

                      clickhouse client --host IP address of the ClickHouseServer instance for which the alarm is reported --user Username --password --port 21423

                      +
                    +

                  3. Log in to MRS Manager, choose Cluster > Services > ClickHouse, click Configurations and then All Configurations. Search for the value of the slow_mutation_cost_time parameter, enter the parameter value in the following SQL statement, and run the following statement to check whether any result is returned:

                    SELECT * FROM system.mutations WHERE is_done = 0 AND create_time < now() - INTERVAL The value SECOND

                    +

                    Add the actual value of slow_mutation_cost_time to the preceding statement.

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

                  4. Wait for a while and run the statement in 3 again. Check whether the value of parts_to_do in the returned result decreases.

                    • If yes, wait until the mutation task is complete.
                    • If no, go to 5.
                    +

                    +

                  5. If the value of parts_to_do remains unchanged, stop the mutation task. Run the following statement and run the statement in 3 again to check whether the current mutation task is in the returned result list:

                    KILL MUTATION WHERE database = 'Database name' AND table = 'Table name' AND mutation_id ='mutation ID'

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

                    +

                  1. Wait for several minutes and check whether the alarm is cleared.

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

                  +

                  Collect fault information.

                  +
                  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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45447.html b/docs/mrs/umn/ALM-45447.html new file mode 100644 index 000000000..7577aa385 --- /dev/null +++ b/docs/mrs/umn/ALM-45447.html @@ -0,0 +1,108 @@ + + +

                  ALM-45447 ClickHouse Table Read-Only

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  The system checks the table status every minute. This alarm is generated when the system detects that a table is read-only. This alarm is automatically cleared when no table is read-only.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45447

                  +

                  Minor

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  • Data cannot be written to or modified.
                  • Data synchronization in the replication table is interrupted, causing data inconsistency.
                  +
                  +

                  Possible Causes

                  The ZooKeeper is overloaded and metadata is lost.

                  +
                  +

                  Handling Procedure

                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address of the hostname in Location.
                  2. Log in to the node where the client is installed and run the following commands:

                    cd {Client installation path}

                    +

                    source bigdata_env

                    +
                    • Security mode (with Kerberos enabled):

                      kinit Component service user

                      +

                      clickhouse client --host IP address of the ClickHouseServer instance that reports the alarm --port 21427 --secure

                      +
                    • Normal mode (with Kerberos disabled):

                      clickhouse client --host IP address of the ClickHouseServer instance for which the alarm is reported --user Username --password --port 21423

                      +
                    +

                  3. Run the following SQL statement to check whether any table is in the read-only state:

                    select database,table from system.replicas where is_readonly = 1

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

                  4. Specify the database and table queried in 3 in the following statements and run them in sequence. Then, run the SQL statement in 3 and check whether the result contains any read-only table.

                    system restore replica database.table;

                    +

                    system restart replica database.table;

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

                  5. Specify the database and table queried in 3 in the following statements and run them in sequence. Then, run the SQL statement in 3 and check whether the result contains the read-only table.

                    detach table database.table;

                    +

                    attach table database.table;

                    +
                    • If yes, go to 6.
                    • If no, go to 8.
                    +

                  6. Run the following SQL statement to view the structure information of the read-only table. In the statement, database and table are those queried in 3.

                    show create table database.table;

                    +

                  7. Run the following SQL statement to delete the read-only table and create a read-only table based on the table structure information in 6. Wait for several minutes, run the SQL statement in 3, and check whether the result contains the read-only table.

                    drop database.table no delay;

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

                    +

                  8. Wait several minutes and check whether the alarm is automatically cleared.

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

                  +

                  Collect fault information.

                  +
                  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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45448.html b/docs/mrs/umn/ALM-45448.html new file mode 100644 index 000000000..6f29e90f1 --- /dev/null +++ b/docs/mrs/umn/ALM-45448.html @@ -0,0 +1,93 @@ + + +

                  ALM-45448 Rapid Increase of Znodes Used by ClickHouse

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  Metadata in ClickHouse is stored on ZooKeeper Znodes. The number of occupied Znodes may increase sharply even if service requirements do not change greatly. This alarm is generated when the number of occupied Znodes in two hours exceeds the threshold. If a large amount of data is imported or services are migrated, ignore this alarm.

                  +

                  This alarm is cleared when the system detects that the increase in two hours is lower than the threshold.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45448

                  +

                  Major

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  ZooKeeper server resources are occupied. The number of Znodes will reach the upper limit in a short period of time, affecting the ClickHouse service.

                  +
                  +

                  Possible Causes

                  • If the ClickHouse service volume retains at large scale, increase the value of ZNODE_GROWTH_LIMIT on the ClickHouse configuration page.
                  • Major service changes, migration, and data import have been performed in ClickHouse.
                  +
                  +

                  Handling Procedure

                  1. Choose Cluster > ClickHouse > Instances > All Configurations, and search for ZNODE_GROWTH_LIMIT, increase the value of ZNODE_GROWTH_LIMIT. The default value is 100000, the maximum value is 200000, and the value is configured based a step of 50000. Wait for 2 hours and check whether the alarm is cleared.

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

                  2. Confirm with the service party whether there are new service requests or a large amount of data is imported or migrated during the period when the alarm is reported.

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

                  3. Wait for 2 hours and check whether the alarm is cleared.

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

                  +

                  Collect fault information.

                  +
                  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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45449.html b/docs/mrs/umn/ALM-45449.html new file mode 100644 index 000000000..a48f23d9b --- /dev/null +++ b/docs/mrs/umn/ALM-45449.html @@ -0,0 +1,94 @@ + + +

                  ALM-45449 The Counter Number of zxid Used by ClickHouse Exceeds the Threshold

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  ClickHouse uses ZooKeeper Transaction ID (zxid) to manage transactions. The zxid is a 64-bit number used to keep consistency of the distributed system. The zxid has two parts: the high order 32-bits for the epoch and the low order 32-bits for the counter. The epoch number represents the lifecycle of the leader, and the counter number indicates the location of a transaction in the request. Each time a new transaction is generated, the counter number is automatically increased by 1. When the value of zxid reaches the maximum value, that is, the counter number reaches 0xffffffff, the cluster forcibly elects the leader and ZooKeeper is unavailable in a short period. The system checks the counter number every two hours. This alarm is generated when the the counter number of zxid exceeds the threshold.

                  +

                  This alarm is cleared when the counter number is smaller than the threshold.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45449

                  +

                  Major

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  ZooKeeper leader election is forcibly triggered at an uncertain time, which may interrupt the ClickHouse service.

                  +
                  +

                  Possible Causes

                  The counter number of ZooKeeper zxid exceeds the threshold.

                  +
                  +

                  Handling Procedure

                  1. Log in to MRS Manager and choose Cluster > Services > ZooKeeper. On the Dashboard page of the ZooKeeper service, click More and select Service Rolling Restart in the upper right corner. In the displayed dialog box, enter the password and click OK. On the Service Rolling Restart page, click OK and wait until the rolling restart of the ZooKeeper service is complete.

                    Restart the ZooKeeper service during off-peak hours of ClickHouse.

                    +
                    +

                  2. Wait for 2 hours and check whether the alarm is cleared.

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

                  +

                  Collect fault information.

                  +
                  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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +

                  +
                  + + diff --git a/docs/mrs/umn/ALM-45450.html b/docs/mrs/umn/ALM-45450.html new file mode 100644 index 000000000..6b0728d5a --- /dev/null +++ b/docs/mrs/umn/ALM-45450.html @@ -0,0 +1,91 @@ + + +

                  ALM-45450 ClickHouse Failed to Obtain a Temporary Agency Credential

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  After the cold-hot separation function and an agency are configured, the system checks the status of the temporary agency credential every minute. This alarm is generated when the the temporary agency credential fails to be obtained for three consecutive times.

                  +

                  This alarm is automatically cleared when the system successfully obtains the temporary agency credential.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45450

                  +

                  Critical

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  The system cannot access OBS after the temporary agency credential expires. Operations such as reading and writing cold data in OBS cannot be performed on tables configured with cold and hot separation policies.

                  +
                  +

                  Possible Causes

                  • The OBS parameters configured for ClickHouse are incorrect.
                  • The IAM service is abnormal.
                  +
                  +

                  Handling Procedure

                  1. Check whether the cold and hot separation configuration is correct. If the configuration is incorrect, modify the configuration and restart the ClickHouse instance. Wait for 3 minutes and check whether the alarm is cleared.

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

                  +

                  Collect fault information.

                  +
                  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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45451.html b/docs/mrs/umn/ALM-45451.html new file mode 100644 index 000000000..509b0b729 --- /dev/null +++ b/docs/mrs/umn/ALM-45451.html @@ -0,0 +1,91 @@ + + +

                  ALM-45451 ClickHouse Failed to Access OBS

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  When cold-hot separation is enabled, the system checks the OBS access every minute. This alarm is generated when the system detects that OBS cannot be accessed for three consecutive times.

                  +

                  This alarm is automatically cleared when the system successfully accesses OBS.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45451

                  +

                  Critical

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  For tables configured with the cold-hot separation policy, cold data on OBS cannot be read or written. Hot data on local disks cannot be moved to OBS.

                  +
                  +

                  Possible Causes

                  • Parameters such as the endpoint used by ClickHouse to access OBS are incorrect.
                  • OBS is abnormal.
                  +
                  +

                  Handling Procedure

                  1. Check whether the cold and hot separation configuration is correct. If the configuration is incorrect, modify the configuration and restart the ClickHouse instance. Wait for 3 minutes and check whether the alarm is cleared.

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

                  +

                  Collect fault information.

                  +
                  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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45452.html b/docs/mrs/umn/ALM-45452.html new file mode 100644 index 000000000..512226efd --- /dev/null +++ b/docs/mrs/umn/ALM-45452.html @@ -0,0 +1,91 @@ + + +

                  ALM-45452 ClickHouse's Local Disk Space Is Below the Cold-Hot Separation Threshold

                  +

                  This section is available for MRS 3.3.1-LTS or later version only.

                  +
                  +

                  Alarm Description

                  When cold-hot separation is enabled, the system checks the remaining space of the local disk specified in the cold-hot separation policy every 5 minutes. This alarm is generated if the remaining space is lower than the move_factor threshold.

                  +

                  This alarm is automatically cleared when the remaining space of the local disk is greater than the move_factor threshold.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Alarm Type

                  +

                  Service Type

                  +

                  Auto Cleared

                  +

                  45452

                  +

                  Major

                  +

                  Quality of service

                  +

                  ClickHouse

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster or system for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  Some hot data on the local disk is moved to OBS, affecting the read and write performance of the system.

                  +
                  +

                  Possible Causes

                  The local disk capacity configured for cold-hot separation on the ClickHouseServer node is too small.

                  +
                  +

                  Handling Procedure

                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address of the hostname in Location.
                  2. Expand the disk capacity of the node for which the alarm is generated.
                  3. Check whether the alarm is cleared after disk expansion.

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

                  +

                  Collect fault information.

                  +
                  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 the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None.

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45475.html b/docs/mrs/umn/ALM-45475.html new file mode 100644 index 000000000..e8cdb6f80 --- /dev/null +++ b/docs/mrs/umn/ALM-45475.html @@ -0,0 +1,80 @@ + + +

                  ALM-45475 A Single Replica Exists in the Kudu Data Table

                  +

                  Alarm Description

                  The system checks the replica status of the Kudu data table. This alarm is generated when a single replica is detected in the Kudu data table.

                  +

                  This alarm is cleared when all Kudu data tables have multiple replicas or no data.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Auto Cleared

                  +

                  45475

                  +

                  Major

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  If a hardware fault occurs, for example, a slow disk or a faulty disk, the Kudu data table may lose data.

                  +
                  +

                  Handling Procedure

                  1. Run the following command to query details about each data table and check for the table with only one replica:

                    kudu table describe {Kudu master address (separated by commas)} {Data table name}

                    +

                    You can view details about the table with only one replica on the Kudu web UI.

                    +

                  +

                  Collect fault information.

                  +
                  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 Kudu for the target cluster.
                  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45476.html b/docs/mrs/umn/ALM-45476.html new file mode 100644 index 000000000..e9d6cf4d5 --- /dev/null +++ b/docs/mrs/umn/ALM-45476.html @@ -0,0 +1,86 @@ + + +

                  ALM-45476 Kudu Failed to Enter the Maintenance Mode

                  +

                  Alarm Description

                  Kudu will enter the maintenance mode during disk replacement. This alarm is generated when Kudu fails to enter the maintenance mode.

                  +

                  This alarm is cleared when Kudu successfully enters the maintenance mode.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Auto Cleared

                  +

                  45476

                  +

                  Major

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +

                  Additional Information

                  +

                  Trigger Condition

                  +

                  Specifies the threshold for triggering the alarm.

                  +
                  +
                  +
                  +

                  Impact on the System

                  A slow or faulty disk cannot be replaced.

                  +
                  +

                  Possible Causes

                  • The Kudu instance is abnormal, and the process cannot be stopped.
                  • The permission on the etc configuration directory of Kudu is abnormal, and data cannot be written into the configuration file.
                  +
                  +

                  Handling Procedure

                  Collect fault information.

                  +
                  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 Kudu for the target cluster.
                  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45477.html b/docs/mrs/umn/ALM-45477.html new file mode 100644 index 000000000..f9b9cdd14 --- /dev/null +++ b/docs/mrs/umn/ALM-45477.html @@ -0,0 +1,84 @@ + + +

                  ALM-45477 Failed to Restore Data After a Disk of Kudu Is Replaced

                  +

                  Alarm Description

                  This alarm is generated when Kudu fails to restore data by invoking the script in SetupTool after a disk is replaced.

                  +

                  This alarm is cleared when the data is successfully restored.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Auto Cleared

                  +

                  45477

                  +

                  Critical

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  Kudu fails to restore data, and historical data is unavailable.

                  +
                  +

                  Possible Causes

                  Kudu fails to restore the UUID or the data from the remote end.

                  +
                  +

                  Handling Procedure

                  Collect fault information.

                  +
                  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 Kudu for the target cluster.
                  3. Click the edit icon in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.

                    Collect NodeAgent logs and check whether data is successfully restored after the disk replacement.

                    +

                    The logs are saved in the following directory:

                    +
                    /var/log/Bigdata/nodeagent/scriptlog/disk_manager_notify.log
                    Figure 1 Collecting NodeAgent logs
                    +
                    +
                    +

                  4. Contact O&M personnel and provide the collected logs.
                  +
                  +

                  Alarm Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45478.html b/docs/mrs/umn/ALM-45478.html new file mode 100644 index 000000000..11fa1256c --- /dev/null +++ b/docs/mrs/umn/ALM-45478.html @@ -0,0 +1,83 @@ + + +

                  ALM-45478 Kudu Failed Data Balancing

                  +

                  Alarm Description

                  The system periodically balances data among Kudu data tables. This alarm is generated when the system detects that the data balancing API returns a failure response.

                  +

                  This alarm is cleared when the Kudu data balancing API is successfully called.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Auto Cleared

                  +

                  45478

                  +

                  Major

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  Failed to call the data balancing API. The Kudu component may be abnormal.

                  +
                  +

                  Possible Causes

                  The segment or replica in the Kudu data table is lost.

                  +
                  +

                  Handling Procedure

                  Handle the Kudu instance exception.

                  +
                  1. On MRS Manager, choose O&M > Alarm > Alarms. On the displayed page, locate alarm ALM-45478 Kudu Failed Data Balancing.
                  2. In the Location field, record the host name and role name.
                  3. Choose Cluster > Services > Kudu > Instances. Click the role name for the host name obtained in 2 and restore the instance. Then, check whether the alarm is cleared.

                    • 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.
                    +

                  5. On the Kudu web UI, check whether any segment or replica is missing.
                  +

                  Collect fault information.

                  +
                  1. On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                  1. Expand the Service drop-down list, and select Kudu for the target cluster.
                  2. Click the edit icon in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
                  3. Contact O&M personnel and provide the collected logs.
                  +
                  +

                  Alarm Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45479.html b/docs/mrs/umn/ALM-45479.html new file mode 100644 index 000000000..bcb60ff25 --- /dev/null +++ b/docs/mrs/umn/ALM-45479.html @@ -0,0 +1,88 @@ + + +

                  ALM-45479 Number of Tablets of the Tserver Process Exceeds the Threshold

                  +

                  Alarm Description

                  The system checks the Kudu service status every 60 seconds. This alarm is generated when the number of tablets of the Tserver process exceeds the threshold.

                  +

                  This alarm is cleared when the number of tablets of the Tserver process becomes normal and the system considers that the Kudu service recovers.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Auto Cleared

                  +

                  45479

                  +

                  Minor

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  If the number of tablets exceeds the threshold, the query performance of the Kudu engine deteriorates.

                  +
                  +

                  Possible Causes

                  The Tserver usage is too high or the Tserver load is unbalanced.

                  +
                  +

                  Handling Procedure

                  Handle the Kudu instance exception.

                  +
                  1. On MRS Manager, choose O&M > Alarm > Alarms, and check whether alarm ALM-45479 Number of Tablets of the Tserver Process Exceeds the Threshold exists.

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

                  2. Choose O&M > Alarm > Thresholds > Kudu, locate the threshold of this alarm, compare the threshold with the monitored number of tablets in the Tserver process of the cluster, and handle the alarm accordingly.

                    • If the threshold is not properly set, change the threshold and go to 5.
                    • If the Tserver load is unbalanced, go to 3.
                    • If the Tserver usage is too high, delete obsolete tables or add Tserver nodes, and go to 3.
                    +

                  3. Log in to the Kudu node where the number of tablets exceeds the threshold.
                  4. Run the following commands to balance the load of the cluster (during off-peak hours, recommended):

                    su omm

                    +

                    cd /opt/Bigdata/FusionInsight_Kudu_xxx/install/FusionInsight-Kudu-xxx/kudu/bin

                    +

                    ./kudu cluster rebalance <master_addresses> [-tables=<tables>]

                    +

                    The preceding parameters can be obtained from the KuduMaster web UI. The tables parameter is optional.

                    +

                  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.
                    +

                  +

                  Collect fault information.

                  +
                  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 Kudu for the target cluster.
                  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45480.html b/docs/mrs/umn/ALM-45480.html new file mode 100644 index 000000000..fba009872 --- /dev/null +++ b/docs/mrs/umn/ALM-45480.html @@ -0,0 +1,95 @@ + + +

                  ALM-45480 Tablet Leaders of a Tserver Process Are Unevenly Distributed

                  +

                  Alarm Description

                  The system checks the Kudu service status every 60 seconds. This alarm is generated when the ratio of tablet leaders of a Tserver process to total tablet leaders in the cluster exceeds the threshold.

                  +

                  This alarm is cleared when the ratio of tablet leaders of a Tserver process to total tablet leaders in the cluster becomes normal.

                  +
                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Auto Cleared

                  +

                  45480

                  +

                  Minor

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +
                  +
                  +
                  +

                  Impact on the System

                  If Tserver tablet leaders are unevenly distributed, the query performance of the Kudu engine deteriorates.

                  +
                  +

                  Possible Causes

                  • Tserver instances are added or restarted.
                  • The threshold is not properly set.
                  +
                  +

                  Handling Procedure

                  Handle the uneven distribution of tablet leaders.

                  +
                  1. On MRS Manager, choose O&M > Alarm > Alarms, and check whether alarm ALM-45480 Tablet Leaders of a Tserver Process Are Unevenly Distributed exists.

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

                  2. Log in to the Kudu node where the number of tablet leaders exceeds the threshold.
                  3. Run the following commands to manually adjust the number of tablet leaders:

                    su omm

                    +

                    cd /opt/Bigdata/FusionInsight_Kudu_xxx/install/FusionInsight-Kudu-xxx/kudu/bin

                    +

                    ./kudu tablet leader_step_down <master_addresses> <tablet_id> [-new_leader_uuid=<new_tablet_server_uuid>]

                    +
                    • master_addresses: The value is in the format of KuduMaster service IP address 1:7051,KuduMaster service IP address 2:7051,KuduMaster service IP address 3:7051.

                      KuduMaster service IP address: You can log in to MRS Manager and choose Cluster > Services > Kudu > Instances to view the service IP address of the KuduMaster instance.

                      +
                    • tablet_id: tablet ID to be adjusted.

                      You can log in to Manager, choose Cluster > Services > Kudu, and click KuduMaster(KuduMaster) next to KuduMaster WebUI to access the KuduMaster web UI. Choose Tables on the menu bar, click the ID in the Table Id column, and obtain the target tablet ID in Detail.

                      +
                    • new_tablet_server_uuid: ID of the target tablet servers.

                      You can log in to the KuduMaster web UI, choose Tablet Servers on the menu bar, and view the UUID.

                      +
                    • new_leader_uuid: You are advised to set the UUID of the node with a small number of tablet leaders.
                    +
                    +

                  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.
                    +

                  +

                  Change the threshold.

                  +
                  1. On MRS Manager, choose O&M > Alarm > Alarms, and check whether alarm ALM-45480 Tablet Leaders of a Tserver Process Are Unevenly Distributed exists.

                    • If yes, go to 6.
                    • If no, go to 8.
                    +

                  2. Choose Cluster > Kudu > Configurations > All Configurations > KuduMaster, locate the alarm threshold parameter TABLET_LEADER_UNBALANCE_SCALE, change the value, and rolling-restart all Kudu Masters to make the configuration take effect.
                  3. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

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

                  +

                  Collect fault information.

                  +
                  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 Kudu for the target cluster.
                  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45481.html b/docs/mrs/umn/ALM-45481.html new file mode 100644 index 000000000..6aec3b73d --- /dev/null +++ b/docs/mrs/umn/ALM-45481.html @@ -0,0 +1,92 @@ + + +

                  ALM-45481 KuduTserver Has Full Disks

                  +

                  The system checks Kudu disk metrics every 60 seconds. This alarm is generated when the number of fully occupied disks for a Tserver is not 0.

                  +

                  This alarm is automatically cleared when the number of fully occupied disks for the Tserver becomes 0.

                  +

                  Alarm Attributes

                  +
                  + + + + + + + + + +

                  Alarm ID

                  +

                  Alarm Severity

                  +

                  Auto Cleared

                  +

                  45481

                  +

                  Major

                  +

                  Yes

                  +
                  +
                  +
                  +

                  Alarm Parameters

                  +
                  + + + + + + + + + + + + + + + + + + + + + + +

                  Type

                  +

                  Parameter

                  +

                  Description

                  +

                  Location Information

                  +

                  Source

                  +

                  Specifies the cluster for which the alarm was generated.

                  +

                  ServiceName

                  +

                  Specifies the service for which the alarm was generated.

                  +

                  RoleName

                  +

                  Specifies the role for which the alarm was generated.

                  +

                  HostName

                  +

                  Specifies the host for which the alarm was generated.

                  +

                  Additional Information

                  +

                  Trigger Condition

                  +

                  Specifies the threshold for triggering the alarm.

                  +
                  +
                  +
                  +

                  Impact on the System

                  Users cannot use the Kudu service properly.

                  +
                  +

                  Possible Causes

                  The disk configuration cannot meet service requirements, and the disk space used by the Kudu service is insufficient.

                  +
                  +

                  Handling Procedure

                  Check the disk capacity and delete unnecessary files and data tables.

                  +
                  1. Log in to MRS Manager. In the alarm list, click the drop-down arrow in the row that contains the alarm, and view the role name and the IP address of the hostname in Location.
                  2. Log in to the node for which the alarm is generated as user root and run the df -h command to check the mount directory where the disk usage is 100%.
                  3. Run the find / -xdev -size +500M; command to view files larger than 500 MB in the directory obtained in 2. Check whether such files are mistakenly written to the directory.

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

                  4. Delete the mistakenly written files and check whether the alarm is cleared 2 minutes later.

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

                  5. Check whether Kudu contains unnecessary data tables.

                    • If yes, go to 6.
                    • If no, go to 8.
                    +

                  6. Use kudu table delete <master_addresses> <table_name> [-nomodify_external_catalogs] to delete unnecessary tables.
                  7. Check whether the alarm is cleared.

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

                  8. Contact the disk administrator to expand the disk capacity.
                  9. Check whether the alarm is cleared.

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

                  +

                  Collect fault information.

                  +
                  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 Kudu for the target cluster, and click OK.
                  3. Click the edit icon 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 Clearance

                  This alarm is automatically cleared after the fault is rectified.

                  +
                  +

                  Related Information

                  None

                  +
                  +
                  + + diff --git a/docs/mrs/umn/ALM-45642.html b/docs/mrs/umn/ALM-45642.html index f0d9ba766..3614301d1 100644 --- a/docs/mrs/umn/ALM-45642.html +++ b/docs/mrs/umn/ALM-45642.html @@ -67,11 +67,11 @@
                  • There are too many MemTables. As a result, write traffic is limited or write stops, and ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold is generated.
                  • The size of SST files at level 0 is too large, and ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold is generated.
                  • The estimated compaction size exceeds the threshold, and ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold is generated.

                Handling Procedure

                Check whether write traffic limiting or write stop is caused due to too many MemTables.

                -
                1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                2. In the alarm list, check whether ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold 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-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold exists.

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

                  3. Handle the alarm by following the instructions provided in section ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold.
                  4. After ALM-45643 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                  Check whether write traffic limiting or write stop is caused due to too many SST files at level 0.

                  -
                  1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                  2. In the alarm list, check whether ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold exists.

                    • If yes, go to 7.
                    • If no, go to 9.
                    +
                    1. On MRS Manager, choose O&M > Alarm > Alarms.
                    2. In the alarm list, check whether ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold exists.

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

                    3. Handle the alarm by following the instructions provided in section ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold.
                    4. After ALM-45644 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                    Check whether write traffic limiting or write stop is caused because the estimated compaction size exceeds the threshold.

                    @@ -79,7 +79,7 @@

                  3. Handle the alarm by following the instructions provided in section ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold.
                  4. After ALM-45647 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                  Collect fault information.

                  -
                  1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                  2. Choose O&M > Alarm > Alarms > ALM-45642 RocksDB Continuously Triggers Write Traffic Limiting, view Location, and obtain the name of the task for which the alarm is generated.
                  3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                  1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the native Yarn page.

                    Figure 1 Application ID of a job
                    +
                    1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                    2. Choose O&M > Alarm > Alarms > ALM-45642 RocksDB Continuously Triggers Write Traffic Limiting, view Location, and obtain the name of the task for which the alarm is generated.
                    3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                    1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the native Yarn page.

                      Figure 1 Application ID of a job
                      • If yes, go to 16.
                      • If no, go to 18.

                    2. Click the application ID of the failed job to go to the job page.

                      1. Click Logs in the Logs column to view JobManager logs.
                        Figure 2 Clicking Logs
                      2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs.
                        Figure 3 Clicking the ID in the Attempt ID column
                        diff --git a/docs/mrs/umn/ALM-45643.html b/docs/mrs/umn/ALM-45643.html index 53a0a93ab..4c4cea38c 100644 --- a/docs/mrs/umn/ALM-45643.html +++ b/docs/mrs/umn/ALM-45643.html @@ -65,7 +65,7 @@

                        Possible Causes

                        The write pressure of RocksDB is high.

                        Handling Procedure

                        Check TaskManager logs for the write pressure of RocksDB and collect logs.

                        -
                        1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                        2. Choose O&M > Alarm > Alarms > ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                        3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                        1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                          Figure 1 Application ID of a job
                          +
                          1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                          2. Choose O&M > Alarm > Alarms > ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                          3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                          1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                            Figure 1 Application ID of a job
                            • If yes, go to 5.
                            • If no, go to 6.

                          2. Click the application ID of the failed job to go to the job page.

                            1. Click Logs in the Logs column to view JobManager logs.
                              Figure 2 Clicking Logs
                            2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs. Then go to 7.
                              Figure 3 Clicking the ID in the Attempt ID column
                              diff --git a/docs/mrs/umn/ALM-45644.html b/docs/mrs/umn/ALM-45644.html index b6f152e11..45fab2ce0 100644 --- a/docs/mrs/umn/ALM-45644.html +++ b/docs/mrs/umn/ALM-45644.html @@ -66,7 +66,7 @@
                              • The compaction pressure of RocksDB is too high, and ALM-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold and ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold are generated.
                              • There are too many SST files at level 0.

                        Handling Procedure

                        Check whether the compaction pressure of RocksDB is too high and ALM-45646 is generated.

                        -
                        1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                        2. In the alarm list, check whether ALM-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold 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-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold exists.

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

                          3. Handle the alarm by following the instructions provided in section ALM-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold.
                          4. After ALM-45646 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                          Check whether the compaction pressure of RocksDB is too high and ALM-45647 is generated.

                          @@ -74,7 +74,7 @@

                        3. Handle the alarm by following the instructions provided in section ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold.
                        4. After ALM-45647 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                        Check TaskManager logs for the number of SST files at level 0 and collect logs.

                        -
                        1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                        2. Choose O&M > Alarm > Alarms > ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                        3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                        1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                          Figure 1 Application ID of a job
                          +
                          1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                          2. Choose O&M > Alarm > Alarms > ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                          3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                          1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                            Figure 1 Application ID of a job
                            • If yes, go to 12.
                            • If no, go to 13.

                          2. Click the application ID of the failed job to go to the job page.

                            1. Click Logs in the Logs column to view JobManager logs.
                              Figure 2 Clicking Logs
                            2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs. Then go to 14.
                              Figure 3 Clicking the ID in the Attempt ID column
                              diff --git a/docs/mrs/umn/ALM-45645.html b/docs/mrs/umn/ALM-45645.html index ccd47098b..26a731d47 100644 --- a/docs/mrs/umn/ALM-45645.html +++ b/docs/mrs/umn/ALM-45645.html @@ -66,7 +66,7 @@

                              Possible Causes

                              The number of pending flush requests of RocksDB for the Flink job is too large.

                              Handling Procedure

                              Check TaskManager logs for the number of pending flush requests and collect logs.

                              -
                              1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                              2. Choose O&M > Alarm > Alarms > ALM-45645 Pending Flush Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                              3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                              1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                Figure 1 Application ID of a job
                                +
                                1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                                2. Choose O&M > Alarm > Alarms > ALM-45645 Pending Flush Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                  Figure 1 Application ID of a job
                                  • If yes, go to 5.
                                  • If no, go to 6.

                                2. Click the application ID of the failed job to go to the job page.

                                  1. Click Logs in the Logs column to view JobManager logs.
                                    Figure 2 Clicking Logs
                                  2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs. Then go to 7.
                                    Figure 3 Clicking the ID in the Attempt ID column
                                    diff --git a/docs/mrs/umn/ALM-45646.html b/docs/mrs/umn/ALM-45646.html index 86487c07b..c755231b1 100644 --- a/docs/mrs/umn/ALM-45646.html +++ b/docs/mrs/umn/ALM-45646.html @@ -66,7 +66,7 @@

                                    Possible Causes

                                    The number of pending compaction requests of RocksDB for the Flink job is too large.

                                    Handling Procedure

                                    Check TaskManager logs for the number of pending compaction requests and collect logs.

                                    -
                                    1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                                    2. Choose O&M > Alarm > Alarms > ALM-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                    3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                    1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                      Figure 1 Application ID of a job
                                      +
                                      1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                                      2. Choose O&M > Alarm > Alarms > ALM-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                      3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                      1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                        Figure 1 Application ID of a job
                                        • If yes, go to 5.
                                        • If no, go to 6.

                                      2. Click the application ID of the failed job to go to the job page.

                                        1. Click Logs in the Logs column to view JobManager logs.
                                          Figure 2 Clicking Logs
                                        2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs. Then go to 7.
                                          Figure 3 Clicking the ID in the Attempt ID column
                                          diff --git a/docs/mrs/umn/ALM-45647.html b/docs/mrs/umn/ALM-45647.html index 4753b57d1..b3e6a76fb 100644 --- a/docs/mrs/umn/ALM-45647.html +++ b/docs/mrs/umn/ALM-45647.html @@ -67,7 +67,7 @@

                                          Possible Causes

                                          The estimated compaction data size of RocksDB is too large.

                                          Handling Procedure

                                          Check TaskManager logs for the estimated compaction data size and collect logs.

                                          -
                                          1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                                          2. Choose O&M > Alarm > Alarms > ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                          3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                          1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                            Figure 1 Application ID of a job

                                            +
                                            1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                                            2. Choose O&M > Alarm > Alarms > ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                            3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                            1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                              Figure 1 Application ID of a job

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

                                            2. Click the application ID of the failed job to go to the job page.

                                              1. Click Logs in the Logs column to view JobManager logs.
                                                Figure 2 Clicking Logs
                                              2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs. Then go to 7.
                                                Figure 3 Clicking the ID in the Attempt ID column
                                                diff --git a/docs/mrs/umn/ALM-45648.html b/docs/mrs/umn/ALM-45648.html index a8b20971f..b23d3bc7f 100644 --- a/docs/mrs/umn/ALM-45648.html +++ b/docs/mrs/umn/ALM-45648.html @@ -68,11 +68,11 @@
                                                • The estimated compaction size exceeds the threshold, and ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold is generated.

                                          Handling Procedure

                                          Check whether there are too many MemTables.

                                          -
                                          1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                          2. In the alarm list, check whether ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold 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-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold exists.

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

                                            3. Handle the alarm by following the instructions provided in section ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold.
                                            4. After ALM-45643 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                                            Check whether the number of SST files at level 0 is too large.

                                            -
                                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                            2. In the alarm list, check whether ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold exists.

                                              • If yes, go to 7.
                                              • If no, go to 9.
                                              +
                                              1. On MRS Manager, choose O&M > Alarm > Alarms.
                                              2. In the alarm list, check whether ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold exists.

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

                                              3. Handle the alarm by following the instructions provided in section ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold.
                                              4. After ALM-45644 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                                              Check whether the estimated compaction size exceeds the threshold.

                                              diff --git a/docs/mrs/umn/ALM-45649.html b/docs/mrs/umn/ALM-45649.html index e44dc0d51..b82da9151 100644 --- a/docs/mrs/umn/ALM-45649.html +++ b/docs/mrs/umn/ALM-45649.html @@ -66,11 +66,11 @@
                                              • There are too many SST files at level 0, causing slow queries. In addition, ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold is generated.
                                              • The cache hit ratio is lower than 60%, causing frequent swap-ins and swap-outs of the block cache.

                                          Handling Procedure

                                          Check whether the number of SST files at level 0 is too large.

                                          -
                                          1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                          2. In the alarm list, check whether ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold 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-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold exists.

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

                                            3. Handle the alarm by following the instructions provided in section ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold.
                                            4. After ALM-45644 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                                            Check the cache hit ratio in TaskManager logs and collect logs.

                                            -
                                            1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                                            2. Choose O&M > Alarm > Alarms > ALM-45649 P95 Latency of RocksDB Get Requests Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                            3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                            1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                              Figure 1 Application ID of a job
                                              +
                                              1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                                              2. Choose O&M > Alarm > Alarms > ALM-45649 P95 Latency of RocksDB Get Requests Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                              3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                              1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                                Figure 1 Application ID of a job
                                                • If yes, go to 9.
                                                • If no, go to 10.

                                              2. Click the application ID of the failed job to go to the job page.

                                                1. Click Logs in the Logs column to view JobManager logs.
                                                  Figure 2 Clicking Logs
                                                2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs. Then go to 11.
                                                  Figure 3 Clicking the ID in the Attempt ID column
                                                  diff --git a/docs/mrs/umn/ALM-45650.html b/docs/mrs/umn/ALM-45650.html index db5d51b8b..0db71ac70 100644 --- a/docs/mrs/umn/ALM-45650.html +++ b/docs/mrs/umn/ALM-45650.html @@ -68,11 +68,11 @@
                                                  • The estimated compaction size exceeds the threshold, and ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold is generated.

                                          Handling Procedure

                                          Check whether write traffic limiting or write stop is caused due to too many MemTables.

                                          -
                                          1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                          2. In the alarm list, check whether ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold 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-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold exists.

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

                                            3. Handle the alarm by following the instructions provided in section ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold.
                                            4. After ALM-45643 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                                            Check whether the number of SST files at level 0 is too large.

                                            -
                                            1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                            2. In the alarm list, check whether ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold exists.

                                              • If yes, go to 7.
                                              • If no, go to 9.
                                              +
                                              1. On MRS Manager, choose O&M > Alarm > Alarms.
                                              2. In the alarm list, check whether ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold exists.

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

                                              3. Handle the alarm by following the instructions provided in section ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold.
                                              4. After ALM-45644 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                                              Check whether the estimated compaction size exceeds the threshold.

                                              @@ -80,7 +80,7 @@

                                            3. Handle the alarm by following the instructions provided in section ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold.
                                            4. After ALM-45647 is cleared, wait a few minutes and check whether this alarm is cleared.

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

                                            Collect fault information.

                                            -
                                            1. Log in to FusionInsight Manager as a user who has the FlinkServer management permission.
                                            2. Choose O&M > Alarm > Alarms > ALM-45650 P95 Latency of RocksDB Write Requests Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                            3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                            1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                              Figure 1 Application ID of a job
                                              +
                                              1. Log in to MRS Manager as a user who has the FlinkServer management permission.
                                              2. Choose O&M > Alarm > Alarms > ALM-45650 P95 Latency of RocksDB Write Requests Continuously Exceeds the Threshold, view Location, and obtain the name of the task for which the alarm is generated.
                                              3. Choose Cluster > Services > Yarn and click the link next to ResourceManager WebUI to go to the native Yarn page.
                                              1. Locate the abnormal task based on its name displayed in Location, search for and record the application ID of the job, and check whether the job logs are available on the Yarn page.

                                                Figure 1 Application ID of a job
                                                • If yes, go to 16.
                                                • If no, go to 18.

                                              2. Click the application ID of the failed job to go to the job page.

                                                1. Click Logs in the Logs column to view JobManager logs.
                                                  Figure 2 Clicking Logs
                                                2. Click the ID in the Attempt ID column and click Logs in the Logs column to view and save TaskManager logs.
                                                  Figure 3 Clicking the ID in the Attempt ID column
                                                  diff --git a/docs/mrs/umn/ALM-45652.html b/docs/mrs/umn/ALM-45652.html index 8182e8793..590b8c7b1 100644 --- a/docs/mrs/umn/ALM-45652.html +++ b/docs/mrs/umn/ALM-45652.html @@ -60,27 +60,27 @@

                                                  Possible Causes

                                                  The ZooKeeper, HDFS, Yarn, KrbServer, or DBService service on which Flink depends is unavailable.

                                                  Handling Procedure

                                                  Check whether the ZooKeeper service on which Flink depends is abnormal.

                                                  -
                                                  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms.
                                                  2. In the alarm list, check whether "ALM-13000 ZooKeeper Service Unavailable" exists.

                                                    • If yes, go to 3.
                                                    • If no, go to 5.
                                                    +
                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms.
                                                    2. In the alarm list, check whether "ALM-13000 ZooKeeper Service Unavailable" exists.

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

                                                    3. Handle the alarm by referring to "ALM-13000 ZooKeeper Service Unavailable."
                                                    4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

                                                    Check whether the HDFS service on which Flink depends is abnormal.

                                                    -
                                                    1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                                    2. In the alarm list, check whether "ALM-14000 HDFS Service Unavailable" exists.

                                                      • If yes, go to 7.
                                                      • If no, go to 9.
                                                      +
                                                      1. On MRS Manager, choose O&M > Alarm > Alarms.
                                                      2. In the alarm list, check whether "ALM-14000 HDFS Service Unavailable" exists.

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

                                                      3. Handle the alarm by referring to "ALM-14000 HDFS Service Unavailable."
                                                      4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

                                                      Check whether the Yarn service on which Flink depends is abnormal.

                                                      -
                                                      1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                                      2. In the alarm list, check whether "ALM-18000 Yarn Service Unavailable" exists.

                                                        • If yes, go to 11.
                                                        • If no, go to 13.
                                                        +
                                                        1. On MRS Manager, choose O&M > Alarm > Alarms.
                                                        2. In the alarm list, check whether "ALM-18000 Yarn Service Unavailable" exists.

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

                                                        3. Handle the alarm by referring to "ALM-18000 Yarn Service Unavailable."
                                                        4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

                                                        Check whether the KrbServer service on which Flink 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 15.
                                                          • If no, go to 17.
                                                          +
                                                          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 15.
                                                            • If no, go to 17.

                                                          3. Handle the alarm by referring to "ALM-25500 KrbServer Service Unavailable."
                                                          4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

                                                          Check whether the DBService service on which Flink depends is abnormal.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
                                                          2. In the alarm list, check whether "ALM-27001 DBService Service Unavailable" exists.

                                                            • If yes, go to 19.
                                                            • If no, go to 21.
                                                            +
                                                            1. On MRS Manager, choose O&M > Alarm > Alarms.
                                                            2. In the alarm list, check whether "ALM-27001 DBService Service Unavailable" exists.

                                                              • If yes, go to 19.
                                                              • If no, go to 21.

                                                            3. Handle the alarm by referring to "ALM-27001 DBService Service Unavailable."
                                                            4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

                                                            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 Flink 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 Flink 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 Clearance

                                                  This alarm is automatically cleared after the fault is rectified.

                                                  diff --git a/docs/mrs/umn/ALM-45653.html b/docs/mrs/umn/ALM-45653.html index 3f6914a56..a3a6ef460 100644 --- a/docs/mrs/umn/ALM-45653.html +++ b/docs/mrs/umn/ALM-45653.html @@ -60,7 +60,7 @@

                                                  Possible Causes

                                                  The HA certificate file is invalid.

                                                  Handling Procedure

                                                  View alarm information.

                                                  -
                                                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45653 Invalid Flink HA Certificate File, view Location, obtain the name of the host for which the alarm is generated, and click the host name to view its IP address.
                                                  +
                                                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms > ALM-45653 Invalid Flink HA Certificate File, view Location, obtain the name of the host for which the alarm is generated, and click the host name to view its IP address.

                                                  Check whether the HA certificate file in the system is valid.

                                                  1. Log in to the host for which the alarm is generated as user omm.
                                                  2. Run the cd ${BIGDATA_HOME}/FusionInsight_Flink_*/install/FusionInsight-Flink-*/ha/local/cert command to go to the directory where the HA certificate is stored.
                                                  3. Run the ls -l command to check whether the server.crt file exists.

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

                                                  4. Run the openssl x509 -in server.crt -text -noout command and check whether the command output is normal.

                                                    • If yes, go to 9.
                                                    • If no, go to 6.
                                                    @@ -68,7 +68,7 @@

                                                  5. Check whether this alarm is generated again during periodic system check.

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

                                                  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 Flink 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 Flink 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 Clearance

                                                  This alarm is automatically cleared after the fault is rectified.

                                                  diff --git a/docs/mrs/umn/ALM-45654.html b/docs/mrs/umn/ALM-45654.html index 14d91a5b7..b28ef0935 100644 --- a/docs/mrs/umn/ALM-45654.html +++ b/docs/mrs/umn/ALM-45654.html @@ -60,14 +60,14 @@

                                                  Possible Causes

                                                  The HA certificate is about to expire.

                                                  Handling Procedure

                                                  View alarm information.

                                                  -
                                                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45654 Flink HA Certificate Is About to Expire, view Location, obtain the name of the host for which the alarm is generated, and click the host name to view its IP address.
                                                  +
                                                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms > ALM-45654 Flink HA Certificate Is About to Expire, view Location, obtain the name of the host for which the alarm is generated, and click the host name to view its IP address.

                                                  Check whether the HA certificate file in the system is valid. If it is not, generate a new one.

                                                  1. Log in to the host for which the alarm is generated as user omm.
                                                  2. Run the cd ${BIGDATA_HOME}/FusionInsight_Flink_*/install/FusionInsight-Flink-*/ha/local/cert command to go to the directory where the HA certificate is stored.
                                                  3. Run the openssl x509 -noout -text -in server.crt command to query the effective time and due time of the HA certificate.
                                                  4. Perform 6 to 7 during off-peak hours to update the certificate file as needed.
                                                  5. Run the cd ${BIGDATA_HOME}/FusionInsight_Flink_*/install/FusionInsight-Flink-*/flink/sbin command to go to the Flink script directory.
                                                  6. Run the sh proceed_ha_ssl_cert.sh command to generate a new HA certificate. Then, check whether the alarm is cleared 1 minute later.

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

                                                  7. On the node where the standby FlinkServer instance is located, repeat 6 to 7. Then, check whether the alarm is cleared 1 minute later.

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

                                                  8. Check whether this alarm is generated again during periodic system check.

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

                                                  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 Flink 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 Flink 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 Clearance

                                                  This alarm is automatically cleared after the fault is rectified.

                                                  diff --git a/docs/mrs/umn/ALM-45655.html b/docs/mrs/umn/ALM-45655.html index a7dc37b09..d035f0185 100644 --- a/docs/mrs/umn/ALM-45655.html +++ b/docs/mrs/umn/ALM-45655.html @@ -60,7 +60,7 @@

                                                  Possible Causes

                                                  The HA certificate file has expired.

                                                  Handling Procedure

                                                  View alarm information.

                                                  -
                                                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms > ALM-45655 Flink HA Certificate File Has Expired, view Location, obtain the name of the host for which the alarm is generated, and click the host name to view its IP address.
                                                  +
                                                  1. Log in to MRS Manager, choose O&M > Alarm > Alarms > ALM-45655 Flink HA Certificate File Has Expired, view Location, obtain the name of the host for which the alarm is generated, and click the host name to view its IP address.

                                                  Check whether the HA certificate file in the system is valid. If it is not, generate a new one.

                                                  1. Log in to the host for which the alarm is generated as user omm.
                                                  2. Run the cd ${BIGDATA_HOME}/FusionInsight_Flink_*/install/FusionInsight-Flink-*/ha/local/cert command to go to the directory where the HA certificate is stored.
                                                  3. Run the openssl x509 -noout -text -in server.crt command to query the effective time and due time of the HA certificate and check whether the HA certificate file is valid.

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

                                                  4. Run the cd ${BIGDATA_HOME}/FusionInsight_Flink_*/install/FusionInsight-Flink-*/flink/sbin command to go to the Flink script directory.
                                                  5. Run the sh proceed_ha_ssl_cert.sh command to generate a new HA certificate. Then, check whether the alarm is cleared 1 minute later.

                                                    • If yes, go to 8.
                                                    • If no, go to 7.
                                                    @@ -68,7 +68,7 @@

                                                  6. Check whether this alarm is generated again during periodic system check.

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

                                                  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 Flink 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 Flink 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 Clearance

                                                  This alarm is automatically cleared after the fault is rectified.

                                                  diff --git a/docs/mrs/umn/ALM-45736.html b/docs/mrs/umn/ALM-45736.html index 691de3dc0..647c5d9bf 100644 --- a/docs/mrs/umn/ALM-45736.html +++ b/docs/mrs/umn/ALM-45736.html @@ -60,7 +60,7 @@

                                                  Possible Causes

                                                  • The HDFS service on which the Guardian service depends is abnormal.
                                                  • The TokenServer role instance is abnormal.

                                                  Handling Procedure

                                                  Check the HDFS service status.

                                                  -
                                                  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. On the page that is displayed, check whether "ALM-14000 HDFS Service Unavailable" is reported.

                                                    • If yes, go to 2.
                                                    • If no, go to 3.
                                                    +
                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. On the page that is displayed, check whether "ALM-14000 HDFS Service Unavailable" is reported.

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

                                                    2. Clear this alarm according to the alarm help.

                                                      After the alarm is cleared, wait a few minutes and check whether the alarm GuardianService Unavailable is cleared.
                                                      • If yes, no further action is required.
                                                      • If no, go to 3.

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

                                                  2. In the alarm list, check whether the alarm "Guardian Service Unavailable" 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 Guardian for the destination 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 Guardian for the destination 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 Clearance

                                                  This alarm is automatically cleared after the fault is rectified.

                                                  diff --git a/docs/mrs/umn/ALM-45737.html b/docs/mrs/umn/ALM-45737.html index dd20b39ae..e46f92a76 100644 --- a/docs/mrs/umn/ALM-45737.html +++ b/docs/mrs/umn/ALM-45737.html @@ -65,15 +65,15 @@

                                                  Possible Causes

                                                  The heap memory of the TokenServer instance is overused or the heap memory is inappropriately allocated.

                                                  Handling Procedure

                                                  Check heap memory usage.

                                                  -
                                                  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45737 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer Heap Memory Usage. Then click OK.
                                                  3. Check whether the heap memory used by TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 TokenServer cannot meet the heap memory required by the TokenServer process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by TokenServer. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer heap memory usage.

                                                    +
                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45737 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer Heap Memory Usage. Then click OK.
                                                    3. Check whether the heap memory used by TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 TokenServer cannot meet the heap memory required by the TokenServer process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by TokenServer. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer heap memory usage.

                                                    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.

                                                      During service or instance restart, Guardian may fail to be accessed and jobs cannot access OBS.

                                                    Collect fault information.

                                                    -
                                                    1. On FusionInsight Manager, choose O&M > Log > Download.
                                                    2. Expand the Service drop-down list, and select Guardian for the destination 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 Guardian for the destination 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 Clearance

                                                    This alarm is automatically cleared after the fault is rectified.

                                                    diff --git a/docs/mrs/umn/ALM-45738.html b/docs/mrs/umn/ALM-45738.html index 20ccefcd5..7ab9a8882 100644 --- a/docs/mrs/umn/ALM-45738.html +++ b/docs/mrs/umn/ALM-45738.html @@ -65,15 +65,15 @@

                                                    Possible Causes

                                                    The direct memory of the TokenServer process is overused or the direct memory is inappropriately allocated.

                                                    Handling Procedure

                                                    Check the direct memory usage.

                                                    -
                                                    1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45738 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer Direct Memory Usage. Then click OK.
                                                    3. Check whether the direct memory used by TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 configured for TokenServer cannot meet the direct memory required by the TokenServer process. You are advised to check the direct memory usage of TokenServer and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by TokenServer. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer direct memory usage.

                                                      +
                                                      1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45738 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer Direct Memory Usage. Then click OK.
                                                      3. Check whether the direct memory used by TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 configured for TokenServer cannot meet the direct memory required by the TokenServer process. You are advised to check the direct memory usage of TokenServer and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by TokenServer. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer direct memory usage.

                                                      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.

                                                        During service or instance restart, Guardian may fail to be accessed and jobs cannot access OBS.

                                                      Collect fault information.

                                                      -
                                                      1. On FusionInsight Manager, choose O&M > Log > Download.
                                                      2. Expand the Service drop-down list, and select Guardian for the destination 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 Guardian for the destination 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 Clearance

                                                      This alarm is automatically cleared after the fault is rectified.

                                                      diff --git a/docs/mrs/umn/ALM-45739.html b/docs/mrs/umn/ALM-45739.html index ec8b49259..ea1b91cf5 100644 --- a/docs/mrs/umn/ALM-45739.html +++ b/docs/mrs/umn/ALM-45739.html @@ -65,15 +65,15 @@

                                                      Possible Causes

                                                      The non-heap memory of the TokenServer instance is overused or the non-heap memory is inappropriately allocated.

                                                      Handling Procedure

                                                      Check non-heap memory usage.

                                                      -
                                                      1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45739 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer Non-Heap Memory Usage. Then click OK.
                                                      3. Check whether the non-heap memory used by TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 TokenServer instance cannot meet the non-heap memory required by the TokenServer process. You are advised to change the value of -XX:MaxPermSize in GC_OPTS to twice that of the current non-heap memory size or change the value based on site requirements.

                                                        +
                                                        1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45739 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer Non-Heap Memory Usage. Then click OK.
                                                        3. Check whether the non-heap memory used by TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 TokenServer instance cannot meet the non-heap memory required by the TokenServer process. You are advised to change the value of -XX:MaxPermSize in GC_OPTS to twice that of 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.

                                                          During service or instance restart, Guardian may fail to be accessed and jobs cannot access OBS.

                                                        Collect fault information.

                                                        -
                                                        1. On FusionInsight Manager, choose O&M > Log > Download.
                                                        2. Expand the Service drop-down list, and select Guardian for the destination 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 Guardian for the destination 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 Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-45740.html b/docs/mrs/umn/ALM-45740.html index 83dcfea2a..f2f45c756 100644 --- a/docs/mrs/umn/ALM-45740.html +++ b/docs/mrs/umn/ALM-45740.html @@ -65,15 +65,15 @@

                                                        Possible Causes

                                                        The heap memory of the TokenServer process is overused or inappropriately allocated, causing frequent occurrence of the GC process.

                                                        Handling Procedure

                                                        Check the GC duration.

                                                        -
                                                        1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45740 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer GC Duration. Then click OK.
                                                        3. Check whether the GC duration of the TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 TokenServer cannot meet the heap memory required by the TokenServer process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by TokenServer. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer heap memory usage.

                                                          +
                                                          1. Log in to MRS Manager and choose O&M > Alarm > Alarms > ALM-45740 TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, 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 > TokenServer GC Duration. Then click OK.
                                                          3. Check whether the GC duration of the TokenServer 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 > Guardian. On the page that is displayed, click the Instance tab. On this tab page, choose TokenServer > Instance Configuration. Click All Configurations, and choose TokenServer > 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 TokenServer cannot meet the heap memory required by the TokenServer process. You are advised to change the value of -Xmx in GC_OPTS to twice that of the heap memory used by TokenServer. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer heap memory usage.

                                                          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.

                                                            During service or instance restart, Guardian may fail to be accessed and jobs cannot access OBS.

                                                          Collect fault information.

                                                          -
                                                          1. On FusionInsight Manager, choose O&M > Log > Download.
                                                          2. Expand the Service drop-down list, and select Guardian for the destination 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 Guardian for the destination 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 Clearance

                                                          This alarm is automatically cleared after the fault is rectified.

                                                          diff --git a/docs/mrs/umn/ALM-45741.html b/docs/mrs/umn/ALM-45741.html index c137ff28c..cb858b77e 100644 --- a/docs/mrs/umn/ALM-45741.html +++ b/docs/mrs/umn/ALM-45741.html @@ -63,7 +63,7 @@

                                                        5. Click Manage Agency. On the page that is displayed, rebind the cluster to an agency. Then check whether the alarm is cleared a few minutes later.

                                                          • 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 Service drop-down list, and select Guardian 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 Guardian 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 Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-45742.html b/docs/mrs/umn/ALM-45742.html index 901e1d2a3..3ee5b6975 100644 --- a/docs/mrs/umn/ALM-45742.html +++ b/docs/mrs/umn/ALM-45742.html @@ -59,7 +59,7 @@

                                                        Possible Causes

                                                        An underlying interface of ECS is abnormal.

                                                        Handling Procedure

                                                        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 Guardian 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 Guardian 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 Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-45743.html b/docs/mrs/umn/ALM-45743.html index 4b86f4ea7..86948a2ba 100644 --- a/docs/mrs/umn/ALM-45743.html +++ b/docs/mrs/umn/ALM-45743.html @@ -59,7 +59,7 @@

                                                        Possible Causes

                                                        The IAM service is abnormal.

                                                        Handling Procedure

                                                        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 Guardian 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 Guardian 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 Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-45744.html b/docs/mrs/umn/ALM-45744.html new file mode 100644 index 000000000..dd3a9bfe5 --- /dev/null +++ b/docs/mrs/umn/ALM-45744.html @@ -0,0 +1,96 @@ + + +

                                                        ALM-45744 Average RPC Processing Time of the Guardian TokenServer Exceeds the Threshold

                                                        +

                                                        Alarm Description

                                                        The system checks the average RPC processing time of the TokenServer service every 30 seconds. This alarm is generated when the average RPC processing time of the TokenServer instance has exceeded the threshold for five consecutive times.

                                                        +

                                                        This alarm is cleared when the system detects that the average RPC processing time falls below the threshold.

                                                        +

                                                        This alarm applies only to MRS 3.5.0 or later.

                                                        +
                                                        +

                                                        Alarm Attributes

                                                        +
                                                        + + + + + + + + + +

                                                        Alarm ID

                                                        +

                                                        Alarm Severity

                                                        +

                                                        Auto Cleared

                                                        +

                                                        45744

                                                        +

                                                        Critical (default threshold: 200 ms)

                                                        +

                                                        Major (default threshold: 100 ms)

                                                        +

                                                        Yes

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Alarm Parameters

                                                        +
                                                        + + + + + + + + + + + + + + + + + + + + + + +

                                                        Type

                                                        +

                                                        Parameter

                                                        +

                                                        Description

                                                        +

                                                        Location Information

                                                        +

                                                        Source

                                                        +

                                                        Specifies the cluster for which the alarm was generated.

                                                        +

                                                        ServiceName

                                                        +

                                                        Specifies the service for which the alarm was generated.

                                                        +

                                                        RoleName

                                                        +

                                                        Specifies the role for which the alarm was generated.

                                                        +

                                                        HostName

                                                        +

                                                        Specifies the host for which the alarm was generated.

                                                        +

                                                        Additional Information

                                                        +

                                                        Trigger Condition

                                                        +

                                                        Specifies the alarm triggering condition.

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Impact on the System

                                                        If the average RPC processing time of the Guardian TokenServer instance exceeds the threshold, service access to OBS may slow down or even OBS cannot be accessed.

                                                        +
                                                        +

                                                        Possible Causes

                                                        • The alarm threshold is improperly configured.
                                                        • The memory configured for the Guardian TokenServer instance is too small, and frame freezing occurs on the JVM due to frequent full garbage collection.
                                                        +
                                                        +

                                                        Handling Procedure

                                                        Check whether the alarm threshold is set properly.

                                                        +
                                                        1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the host name of the TokenServer instance for which this alarm is generated.
                                                        2. On MRS Manager, choose Cluster > Services > Guardian. On the page that is displayed, click the Instances tab, click the TokenServer role for the host name obtained in 1, click the drop-down list in the upper right corner of the Chart area, and select Customize. On the Customize Statistics page, choose RPC > Average Time of TokenServer RPC Processing, and click OK.
                                                        3. Check whether the average RPC processing time of TokenServer reaches the alarm threshold (200 ms for critical alarms and 100 ms for major alarms).

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

                                                        4. On MRS Manager, choose O&M > Alarm > Thresholds, select the desired cluster, choose Guardian > RPC, and click Average Time of TokenServer RPC Processing. In the right pane, locate the default rule, and click Modify in the Operation column. On the Modify Rule page, change the threshold for the Critical or Major alarm severity to 150% of the peak value within one day after the alarm is generated, and click OK.
                                                        5. Wait 5 minutes and check whether the alarm is automatically cleared.

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

                                                        +

                                                        Check whether the memory of the Guardian TokenServer is too small.

                                                        +
                                                        1. On MRS Manager, choose O&M > Alarm > Alarms and check whether alarm TokenServer Heap Memory Usage Exceeds the Threshold is reported on the TokenServer node.

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

                                                        2. Rectify the fault by following the handling procedure of ALM-45737 TokenServer Heap Memory Usage Exceeds the Threshold.
                                                        3. Wait 10 minutes and check whether the alarm is automatically cleared.

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

                                                        +

                                                        Collect fault information.

                                                        +
                                                        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 Guardian for the target cluster.
                                                        3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        +
                                                        +

                                                        Related Information

                                                        None.

                                                        +
                                                        +
                                                        + + diff --git a/docs/mrs/umn/ALM-45745.html b/docs/mrs/umn/ALM-45745.html new file mode 100644 index 000000000..e88085e82 --- /dev/null +++ b/docs/mrs/umn/ALM-45745.html @@ -0,0 +1,96 @@ + + +

                                                        ALM-45745 Average RPC Queuing Time of the Guardian TokenServer Exceeds the Threshold

                                                        +

                                                        Alarm Description

                                                        The system checks the average RPC queuing time of the TokenServer service every 30 seconds. This alarm is generated when the average RPC queuing time of the TokenServer instance has exceeded the threshold for five consecutive times.

                                                        +

                                                        This alarm is cleared when the system detects that the average RPC queuing time falls below the threshold.

                                                        +

                                                        This alarm applies only to MRS 3.5.0 or later.

                                                        +
                                                        +

                                                        Alarm Attributes

                                                        +
                                                        + + + + + + + + + +

                                                        Alarm ID

                                                        +

                                                        Alarm Severity

                                                        +

                                                        Auto Cleared

                                                        +

                                                        45745

                                                        +

                                                        Critical (default threshold: 300 ms)

                                                        +

                                                        Major (default threshold: 200 ms)

                                                        +

                                                        Yes

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Alarm Parameters

                                                        +
                                                        + + + + + + + + + + + + + + + + + + + + + + +

                                                        Type

                                                        +

                                                        Parameter

                                                        +

                                                        Description

                                                        +

                                                        Location Information

                                                        +

                                                        Source

                                                        +

                                                        Specifies the cluster for which the alarm was generated.

                                                        +

                                                        ServiceName

                                                        +

                                                        Specifies the service for which the alarm was generated.

                                                        +

                                                        RoleName

                                                        +

                                                        Specifies the role for which the alarm was generated.

                                                        +

                                                        HostName

                                                        +

                                                        Specifies the host for which the alarm was generated.

                                                        +

                                                        Additional Information

                                                        +

                                                        Trigger Condition

                                                        +

                                                        Specifies the alarm triggering condition.

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Impact on the System

                                                        If the average RPC queuing time of the Guardian TokenServer instance exceeds the threshold, service access to OBS may slow down or even OBS cannot be accessed.

                                                        +
                                                        +

                                                        Possible Causes

                                                        • The alarm threshold is improperly configured.
                                                        • The memory configured for the Guardian TokenServer instance is too small, and frame freezing occurs on the JVM due to frequent full garbage collection.
                                                        +
                                                        +

                                                        Handling Procedure

                                                        Check whether the alarm threshold is set properly.

                                                        +
                                                        1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the Location field of the alarm details, view the host name of the TokenServer instance for which this alarm is generated.
                                                        2. On MRS Manager, choose Cluster > Services > Guardian. On the page that is displayed, click the Instances tab, click the TokenServer role for the host name obtained in 1, click the drop-down list in the upper right corner of the Chart area, and select Customize. On the Customize Statistics page, choose RPC > Average Time of TokenServer RPC Queuing, and click OK.
                                                        3. Check whether the average RPC queuing time of TokenServer reaches the alarm threshold (300 ms for critical alarms and 200 ms for major alarms).

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

                                                        4. On MRS Manager, choose O&M > Alarm > Thresholds, select the desired cluster, choose Guardian > RPC, and click Average Time of TokenServer RPC Queuing. In the right pane, locate the default rule, and click Modify in the Operation column. On the Modify Rule page, change the threshold for the Critical or Major alarm severity to 150% of the peak value within one day after the alarm is generated, and click OK.
                                                        5. Wait 5 minutes and check whether the alarm is automatically cleared.

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

                                                        +

                                                        Check whether the memory of the Guardian TokenServer is too small.

                                                        +
                                                        1. On MRS Manager, choose O&M > Alarm > Alarms and check whether alarm TokenServer Heap Memory Usage Exceeds the Threshold is reported on the TokenServer instance.

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

                                                        2. Rectify the fault by following the handling procedure of ALM-45737 TokenServer Heap Memory Usage Exceeds the Threshold.
                                                        3. Wait 10 minutes and check whether the alarm is automatically cleared.

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

                                                        +

                                                        Collect fault information.

                                                        +
                                                        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 Guardian for the target cluster.
                                                        3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        +
                                                        +

                                                        Related Information

                                                        None.

                                                        +
                                                        +
                                                        + + diff --git a/docs/mrs/umn/ALM-47001.html b/docs/mrs/umn/ALM-47001.html new file mode 100644 index 000000000..7ed280469 --- /dev/null +++ b/docs/mrs/umn/ALM-47001.html @@ -0,0 +1,93 @@ + + +

                                                        ALM-47001 MemArtsCC Service Unavailable

                                                        +

                                                        This section is available for MRS 3.3.1-LTS or later version only.

                                                        +
                                                        +

                                                        Alarm Description

                                                        The system checks the status of the ZooKeeper service on which the MemArtsCC depends every 60 seconds. This alarm is generated when the ZooKeeper service is unavailable.

                                                        +

                                                        This alarm is automatically cleared when the ZooKeeper service is normal.

                                                        +
                                                        +

                                                        Alarm Attributes

                                                        +
                                                        + + + + + + + + + + + + + +

                                                        Alarm ID

                                                        +

                                                        Alarm Severity

                                                        +

                                                        Alarm Type

                                                        +

                                                        Service Type

                                                        +

                                                        Auto Cleared

                                                        +

                                                        47001

                                                        +

                                                        Critical

                                                        +

                                                        Error handling

                                                        +

                                                        MemArtsCC

                                                        +

                                                        Yes

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Alarm Parameters

                                                        +
                                                        + + + + + + + + + + + + + + + + + + +

                                                        Type

                                                        +

                                                        Parameter

                                                        +

                                                        Description

                                                        +

                                                        Location Information

                                                        +

                                                        Source

                                                        +

                                                        Specifies the cluster or system for which the alarm is generated.

                                                        +

                                                        ServiceName

                                                        +

                                                        Specifies the service for which the alarm is generated.

                                                        +

                                                        RoleName

                                                        +

                                                        Specifies the role for which the alarm is generated.

                                                        +

                                                        HostName

                                                        +

                                                        Specifies the host for which the alarm is generated.

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Impact on the System

                                                        The service will be unavailable.

                                                        +
                                                        +

                                                        Possible Causes

                                                        The ZooKeeper service on which the MemArtCC service depends is unavailable.

                                                        +
                                                        +

                                                        Handling Procedure

                                                        Handling ZooKeeper exceptions

                                                        +
                                                        1. Log in to MRS Manager and choose O&M > Alarm > Alarms. On the ZooKeeper dashboard page, check whether the ZooKeeper service is faulty.

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

                                                        2. Rectify the ZooKeeper fault based on the error information and alarm information and the ZooKeeper help document.
                                                        1. After the ZooKeeper service becomes normal, wait for 60 seconds and check whether the alarm is cleared.

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

                                                        +

                                                        Collect fault information.

                                                        +
                                                        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 MemArtsCC for the target cluster.
                                                        3. Click the edit icon in the upper right corner, and set Start 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 send the collected logs.
                                                        +
                                                        +

                                                        Alarm Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        +
                                                        +

                                                        Related Information

                                                        None

                                                        +
                                                        +
                                                        + + diff --git a/docs/mrs/umn/ALM-47002.html b/docs/mrs/umn/ALM-47002.html new file mode 100644 index 000000000..555b1387f --- /dev/null +++ b/docs/mrs/umn/ALM-47002.html @@ -0,0 +1,83 @@ + + +

                                                        ALM-47002 MemArtsCC Disk Fault

                                                        +

                                                        This section is available for MRS 3.3.1-LTS or later version only.

                                                        +
                                                        +

                                                        Alarm Description

                                                        The alarm module checks the status of the local disk used by MemArtsCC every 60 seconds. This alarm is generated when the alarm module detects that the disk status is abnormal. This alarm is cleared when the disk becomes normal.

                                                        +
                                                        +

                                                        Alarm Attributes

                                                        +
                                                        + + + + + + + + + +

                                                        Alarm ID

                                                        +

                                                        Alarm Severity

                                                        +

                                                        Auto Cleared

                                                        +

                                                        47002

                                                        +

                                                        Major

                                                        +

                                                        Yes

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Alarm Parameters

                                                        +
                                                        + + + + + + + + + + + + + + + + + + +

                                                        Type

                                                        +

                                                        Parameter

                                                        +

                                                        Description

                                                        +

                                                        Location Information

                                                        +

                                                        Source

                                                        +

                                                        Specifies the cluster or system for which the alarm is generated.

                                                        +

                                                        ServiceName

                                                        +

                                                        Specifies the service for which the alarm is generated.

                                                        +

                                                        RoleName

                                                        +

                                                        Specifies the role for which the alarm is generated.

                                                        +

                                                        HostName

                                                        +

                                                        Specifies the host for which the alarm is generated.

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Impact on the System

                                                        MemArtsCC becomes abnormal or its performance deteriorates.

                                                        +
                                                        +

                                                        Possible Causes

                                                        The disk used by MemArtsCC is damaged or the permission is read-only.

                                                        +
                                                        +

                                                        Handling Procedure

                                                        1. Log in to MRS Manager, choose O&M > Alarm > Alarms, search for "ALM-47002 MemArtsCC Disk Fault", and locate the abnormal disk directory based on the alarm information.
                                                        2. Contact O&M engineers to check whether the disk is faulty.

                                                          • If yes, replace the disk, restart the CCSideCar and CCWorker roles of the faulty node, and go to 3.
                                                          • If no, go to 4.
                                                          +

                                                        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.
                                                          +

                                                        +

                                                        Collect fault information.

                                                        +
                                                        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 MemArtsCC for the target cluster.
                                                        3. Click the edit icon in the upper right corner, and set Start 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 send the collected logs.
                                                        +
                                                        +

                                                        Alarm Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        +
                                                        +

                                                        Related Information

                                                        None

                                                        +
                                                        +
                                                        + + diff --git a/docs/mrs/umn/ALM-47003.html b/docs/mrs/umn/ALM-47003.html new file mode 100644 index 000000000..7a994426e --- /dev/null +++ b/docs/mrs/umn/ALM-47003.html @@ -0,0 +1,84 @@ + + +

                                                        ALM-47003 Memory Usage of the MemArtsCC Worker Process Exceeds the Threshold

                                                        +

                                                        This section is available for MRS 3.5.0-LTS or later version only.

                                                        +
                                                        +

                                                        Alarm Description

                                                        The system checks the memory usage of the CCWorker process of the MemArtsCC component every 30 seconds. This alarm is generated when the memory usage exceeds the threshold.

                                                        +

                                                        This alarm is cleared when the system detects that the memory usage of CCWorker process is lower than the threshold.

                                                        +
                                                        +

                                                        Alarm Attributes

                                                        +
                                                        + + + + + + + + + +

                                                        Alarm ID

                                                        +

                                                        Alarm Severity

                                                        +

                                                        Auto Cleared

                                                        +

                                                        47003

                                                        +

                                                        Major

                                                        +

                                                        Yes

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Alarm Parameters

                                                        +
                                                        + + + + + + + + + + + + + + + + + + +

                                                        Type

                                                        +

                                                        Parameter

                                                        +

                                                        Description

                                                        +

                                                        Location Information

                                                        +

                                                        Source

                                                        +

                                                        Specifies the cluster or system for which the alarm is generated.

                                                        +

                                                        ServiceName

                                                        +

                                                        Specifies the service for which the alarm is generated.

                                                        +

                                                        RoleName

                                                        +

                                                        Specifies the role for which the alarm is generated.

                                                        +

                                                        HostName

                                                        +

                                                        Specifies the host for which the alarm is generated.

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Impact on the System

                                                        The CCWorker process process may restart, which temporarily reduces the cache hit ratio.

                                                        +
                                                        +

                                                        Possible Causes

                                                        There is more disk space added to CCWorker, there is a sudden increase in service data, or the workload increases significantly when upper-layer computing services (such as Spark, Hive, and HetuEngine) sent many concurrent requests to the MemArtsCC component.

                                                        +
                                                        +

                                                        Handling Procedure

                                                        1. Log in to MRS Manager, choose O&M > Alarm > Alarms, search for ALM-47003 Memory Usage of the MemArtsCC Worker Process Exceeds the Threshold, and locate the abnormal MemArtsCC instance node based on the alarm information. Obtain the alarm threshold in additional information.
                                                        2. Choose Cluster > Services > MemArtsCC > Configurations > All Configurations > CCWorker (Role), search for the memory_limit parameter, and check the maximum available memory of the CCWorker instance in the current cluster. Check whether the service concurrency and data volume increase for a long time and the alarm is not automatically cleared.

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

                                                        3. This alarm can be ignored temporarily. After the service peak hours, the alarm will be automatically cleared.
                                                        4. Increase the maximum available memory in 2 and click Save.
                                                        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.
                                                          +

                                                        +

                                                        Collect fault information.

                                                        +
                                                        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 MemArtsCC for the target cluster.
                                                        3. Click the edit icon in the upper right corner, and set Start 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 send the collected logs.
                                                        +
                                                        +

                                                        Alarm Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        +
                                                        +

                                                        Related Information

                                                        None

                                                        +
                                                        +
                                                        + + diff --git a/docs/mrs/umn/ALM-47004.html b/docs/mrs/umn/ALM-47004.html new file mode 100644 index 000000000..79b0c1101 --- /dev/null +++ b/docs/mrs/umn/ALM-47004.html @@ -0,0 +1,85 @@ + + +

                                                        ALM-47004 Average Latency of MemArtsCC Worker Read Requests Exceeds the Threshold

                                                        +

                                                        This section is available for MRS 3.5.0-LTS or later version only.

                                                        +
                                                        +

                                                        Alarm Description

                                                        The system checks the average latency of all read requests to the MemArtsCC Worker process component every 30 seconds. This alarm is generated when the average latency exceeds the limit.

                                                        +

                                                        This alarm is cleared when the latency of MemArtsCC Worker read requests is lower than the threshold.

                                                        +
                                                        +

                                                        Alarm Attributes

                                                        +
                                                        + + + + + + + + + +

                                                        Alarm ID

                                                        +

                                                        Alarm Severity

                                                        +

                                                        Auto Cleared

                                                        +

                                                        47004

                                                        +

                                                        Major

                                                        +

                                                        Yes

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Alarm Parameters

                                                        +
                                                        + + + + + + + + + + + + + + + + + + +

                                                        Type

                                                        +

                                                        Parameter

                                                        +

                                                        Description

                                                        +

                                                        Location Information

                                                        +

                                                        Source

                                                        +

                                                        Specifies the cluster or system for which the alarm was generated.

                                                        +

                                                        ServiceName

                                                        +

                                                        Specifies the service for which the alarm was generated.

                                                        +

                                                        RoleName

                                                        +

                                                        Specifies the role for which the alarm was generated.

                                                        +

                                                        HostName

                                                        +

                                                        Specifies the host for which the alarm was generated.

                                                        +
                                                        +
                                                        +
                                                        +

                                                        Impact on the System

                                                        The cache performance may deteriorate.

                                                        +
                                                        +

                                                        Possible Causes

                                                        There is a soaring increase of concurrent requests sent by upper-layer computing services (such as Spark, Hive, and HetuEngine). Or, the service load or disk load increases significantly that even a fault occurs.

                                                        +
                                                        +

                                                        Handling Procedure

                                                        1. Log in to MRS Manager, choose O&M > Alarm > Alarms, search for ALM-47004 Average Latency of MemArtsCC Worker Read Requests Exceeds the Threshold, and locate the abnormal MemArtsCC instance node based on the alarm information. Obtain the alarm threshold in additional information.
                                                        2. On the Alarms page, check whether a disk fault alarm is generated.

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

                                                        3. Contact O&M engineers to rectify the disk fault. Then, check whether the alarm is cleared.

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

                                                        4. Ignore the alarm. Check whether the alarm is cleared when service load goes down.

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

                                                        +

                                                        Collect fault information.

                                                        +
                                                        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 MemArtsCC for the target cluster.
                                                        3. Click the edit icon in the upper right corner, and set Start 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 engineers and send the collected logs.
                                                        +
                                                        +

                                                        Alarm Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        +
                                                        +

                                                        Related Information

                                                        None

                                                        +
                                                        +
                                                        + + diff --git a/docs/mrs/umn/ALM-50201.html b/docs/mrs/umn/ALM-50201.html index 06316830a..5f2f0d763 100644 --- a/docs/mrs/umn/ALM-50201.html +++ b/docs/mrs/umn/ALM-50201.html @@ -55,17 +55,17 @@
                                                      -

                                                      Impact on the System

                                                      FusionInsight Manager cannot be used to perform cluster operations on the Doris service, and Doris service functions are unavailable.

                                                      +

                                                      Impact on the System

                                                      MRS Manager cannot be used to perform cluster operations on the Doris service, and Doris service functions are unavailable.

                                                      Possible Causes

                                                      The FE and BE instances are abnormal.

                                                      Handling Procedure

                                                      Restart the Doris service.

                                                      -
                                                      1. Log in to FusionInsight Manager and choose Cluster > Services > Doris.
                                                      1. On the page that is displayed, click More and select Restart Service. In the displayed dialog box, verify the password and click OK to restart the Doris service. After the service is started, go to 3.

                                                        During the restart of the Doris service, the Doris service is unavailable and cannot provide services for external systems. Tasks connected to the Doris service fail.

                                                        +
                                                        1. Log in to MRS Manager and choose Cluster > Services > Doris.
                                                        1. On the page that is displayed, click More and select Restart Service. In the displayed dialog box, verify the password and click OK to restart the Doris service. After the service is started, go to 3.

                                                          During the restart of the Doris service, the Doris service is unavailable and cannot provide services for external systems. Tasks connected to the Doris service fail.

                                                          -

                                                        2. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, check whether this alarm is cleared.

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

                                                        3. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, check whether this 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 Service drop-down list, select Doris for the target cluster, and click OK.
                                                        3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                        3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                        This alarm is automatically cleared after the fault is rectified.

                                                        diff --git a/docs/mrs/umn/ALM-50202.html b/docs/mrs/umn/ALM-50202.html index ebfa9044c..6cb686fb7 100644 --- a/docs/mrs/umn/ALM-50202.html +++ b/docs/mrs/umn/ALM-50202.html @@ -65,12 +65,12 @@

                                                        Possible Causes

                                                        The alarm threshold or alarm trigger count is improperly configured.

                                                        Handling Procedure

                                                        Check whether the alarm threshold or alarm trigger count is properly configured.

                                                        -
                                                        1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > CPU Usage of FE (FE).
                                                        2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                          Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                          +
                                                          1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > CPU Usage of FE (FE).
                                                          2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                            Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                          3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                          4. Wait 2 minutes and check whether the alarm is automatically 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. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                          3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                          3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                          This alarm is automatically cleared after the fault is rectified.

                                                          diff --git a/docs/mrs/umn/ALM-50203.html b/docs/mrs/umn/ALM-50203.html index 8cfcd3775..d09bd4e7e 100644 --- a/docs/mrs/umn/ALM-50203.html +++ b/docs/mrs/umn/ALM-50203.html @@ -65,12 +65,12 @@

                                                          Possible Causes

                                                          • The alarm threshold or alarm trigger count is improperly configured.

                                                          Handling Procedure

                                                          Check whether the alarm threshold or alarm trigger count is properly configured.

                                                          -
                                                          1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > Memory Usage of FE (FE).
                                                          2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                            Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                            +
                                                            1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > Memory Usage of FE (FE).
                                                            2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                              Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                            3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                            4. Wait 2 minutes and check whether the alarm is automatically 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. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                            3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                            3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                            This alarm is automatically cleared after the fault is rectified.

                                                            diff --git a/docs/mrs/umn/ALM-50205.html b/docs/mrs/umn/ALM-50205.html index 8853d6348..e5731a0d1 100644 --- a/docs/mrs/umn/ALM-50205.html +++ b/docs/mrs/umn/ALM-50205.html @@ -65,12 +65,12 @@

                                                            Possible Causes

                                                            The alarm threshold or alarm trigger count is improperly configured.

                                                            Handling Procedure

                                                            Check whether the alarm threshold or alarm trigger count is properly configured.

                                                            -
                                                            1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > CPU and Memory > CPU Usage of BE (BE).
                                                            2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                              Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                              +
                                                              1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > CPU and Memory > CPU Usage of BE (BE).
                                                              2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                                Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                              3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                              4. Wait 2 minutes and check whether the alarm is automatically 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. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                              3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                              3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                              This alarm is automatically cleared after the fault is rectified.

                                                              diff --git a/docs/mrs/umn/ALM-50206.html b/docs/mrs/umn/ALM-50206.html index 848692d96..39e965ef7 100644 --- a/docs/mrs/umn/ALM-50206.html +++ b/docs/mrs/umn/ALM-50206.html @@ -65,12 +65,12 @@

                                                              Possible Causes

                                                              The alarm threshold or alarm trigger count is improperly configured.

                                                              Handling Procedure

                                                              Check whether the alarm threshold or alarm trigger count is properly configured.

                                                              -
                                                              1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > CPU and Memory > Memory Usage of BE (BE).
                                                              2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                                Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                                +
                                                                1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > CPU and Memory > Memory Usage of BE (BE).
                                                                2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.

                                                                  Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

                                                                3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                4. Wait 2 minutes and check whether the alarm is automatically 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. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                                3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                This alarm is automatically cleared after the fault is rectified.

                                                                diff --git a/docs/mrs/umn/ALM-50207.html b/docs/mrs/umn/ALM-50207.html index 325311b0e..2925936ea 100644 --- a/docs/mrs/umn/ALM-50207.html +++ b/docs/mrs/umn/ALM-50207.html @@ -65,12 +65,12 @@

                                                                Possible Causes

                                                                • After the MySQL client is connected to Doris, the connection is not closed.
                                                                • A large number of services are concurrently connected to Doris.

                                                                Handling Procedure

                                                                Check whether the alarm threshold or alarm trigger count is properly configured.

                                                                -
                                                                1. Log in to FusionInsight Manager, choose O&M, and click Alarm > Thresholds in the navigation pane on the left. Click the name of the desired cluster > Doris > Connection > FE MySQL Port Connections (FE).
                                                                2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.

                                                                  If there are a large number of connections, ensure there are only necessary connections. Otherwise, the service performance may be degraded or even the service may be unavailable.

                                                                  +
                                                                  1. Log in to MRS Manager, choose O&M, and click Alarm > Thresholds in the navigation pane on the left. Click the name of the desired cluster > Doris > Connection > FE MySQL Port Connections (FE).
                                                                  2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                  3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.

                                                                    If there are a large number of connections, ensure there are only necessary connections. Otherwise, the service performance may be degraded or even the service may be unavailable.

                                                                  4. Wait for 2 minutes 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. In the navigation pane on the left, choose Log > Download.
                                                                  2. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                                  3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                  3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                  This alarm is automatically cleared after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-50208.html b/docs/mrs/umn/ALM-50208.html index 1438379e8..49a75f55e 100644 --- a/docs/mrs/umn/ALM-50208.html +++ b/docs/mrs/umn/ALM-50208.html @@ -65,12 +65,12 @@

                                                                  Possible Causes

                                                                  The Doris service is abnormal.

                                                                  Handling Procedure

                                                                  Check whether the Doris service is normal.

                                                                  -
                                                                  1. Log in to FusionInsight Manager and choose Cluster > Services > Doris.
                                                                  2. Check whether Running Status of the Doris service is Normal.

                                                                    • If yes, go to 4.
                                                                    • If no, go to 3.
                                                                    +
                                                                    1. Log in to MRS Manager and choose Cluster > Services > Doris.
                                                                    2. Check whether Running Status of the Doris service is Normal.

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

                                                                    3. If the service process is not started, start it first and check whether the alarm is cleared.

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

                                                                    4. Check whether other Doris-related alarms are generated in the cluster. If yes, clear them by referring to the alarm help. Then, check whether this 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. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                  You need to manually clear the alarm after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-50209.html b/docs/mrs/umn/ALM-50209.html index 217949c8c..6d319fff1 100644 --- a/docs/mrs/umn/ALM-50209.html +++ b/docs/mrs/umn/ALM-50209.html @@ -65,11 +65,11 @@

                                                                  Possible Causes

                                                                  The Doris service is abnormal.

                                                                  Handling Procedure

                                                                  Check the Doris service status.

                                                                  -
                                                                  1. Log in to FusionInsight Manager and choose Cluster > Services > Doris.
                                                                  2. Check whether Running Status of the Doris service is Normal.

                                                                    • If yes, go to 4.
                                                                    • If no, go to 3.
                                                                    +
                                                                    1. Log in to MRS Manager and choose Cluster > Services > Doris.
                                                                    2. Check whether Running Status of the Doris service is Normal.

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

                                                                    3. If the service process is not started, start it first.
                                                                    4. Check whether other alarms are generated in the cluster. If yes, clear the alarms by referring to the alarm help. Then, check whether this 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. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                  You need to manually clear the alarm after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-50210.html b/docs/mrs/umn/ALM-50210.html index 1daec229a..1f3890580 100644 --- a/docs/mrs/umn/ALM-50210.html +++ b/docs/mrs/umn/ALM-50210.html @@ -64,13 +64,13 @@

                                                                  Possible Causes

                                                                  The number of concurrent service requests is large in the cluster, or the compaction queue is small.

                                                                  Handling Procedure

                                                                  Check whether the alarm threshold or alarm trigger count is properly configured.

                                                                  -
                                                                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Performance > Maximum compaction score of all BE nodes (BE).
                                                                  2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                  3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                  4. Wait 2 minutes and check whether the alarm is cleared in the alarm list.

                                                                    • If yes, no further action is required.
                                                                    • If no, go to 5.
                                                                    +
                                                                    1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Performance > Maximum compaction score of all BE nodes (BE).
                                                                    2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                    3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                    4. Wait 2 minutes and check whether the alarm is cleared in the alarm list.

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

                                                                    5. Choose Cluster > Services > Doris > Configurations > All Configurations > BE(Role) > Customization, add the max_base_compaction_threads parameter to be.conf with a value of 10, and add the max_cumu_compaction_threads parameter with a value 20.
                                                                    6. Click Save. Click Instances, select the BE instances whose configuration has expired, click More, and select Restart Instance to restart the Doris BE instances.

                                                                      During BE instance restart, the tasks running on BE nodes will fail. The tasks on BE nodes that are not restarted are not affected.

                                                                    7. 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. In the navigation pane on the left, choose Log > Download.
                                                                    2. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                  This alarm is automatically cleared after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-50211.html b/docs/mrs/umn/ALM-50211.html index 9ac1dd549..7790d5eab 100644 --- a/docs/mrs/umn/ALM-50211.html +++ b/docs/mrs/umn/ALM-50211.html @@ -65,16 +65,16 @@

                                                                  Possible Causes

                                                                  The processing capability of the master FE node is insufficient due to a large number of concurrent service requests in the Doris cluster or insufficient memory for FE processes.

                                                                  Handling Procedure

                                                                  Check the GC duration.

                                                                  -
                                                                  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50211.
                                                                  2. Choose Cluster > Services > Doris > Instances, click the FE instance for which the alarm is generated, and click the Chart tab of the instance.

                                                                    Select JVM from Chart Category on the left, and check whether Accumulated GC duration of the old generation of the FE process is greater than 3 seconds.
                                                                    • If yes, go to 3.
                                                                    • If no, go to 5.
                                                                    +
                                                                    1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50211.
                                                                    2. Choose Cluster > Services > Doris > Instances, click the FE instance for which the alarm is generated, and click the Chart tab of the instance.

                                                                      Select JVM from Chart Category on the left, and check whether Accumulated GC duration of the old generation of the FE process is greater than 3 seconds.
                                                                      • If yes, go to 3.
                                                                      • If no, go to 5.

                                                                    3. Choose Cluster > Services > Doris > Configurations > All Configurations > FE(Role) > JVM, and increase the value of -Xmx in FE_GC_OPTS. The default value is 8GB.

                                                                      • If this alarm is generated occasionally, increase the value by 0.5 times. If this alarm is generated frequently, double the parameter 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.

                                                                    Check whether the alarm threshold or alarm trigger count is properly configured.

                                                                    -
                                                                    1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Queue Length of BE Periodic Report Tasks on the FE (FE).
                                                                    2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                    3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                    4. Wait 2 minutes and check whether the alarm is automatically cleared.

                                                                      • If yes, no further action is required.
                                                                      • If no, go to 9.
                                                                      +
                                                                      1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Queue Length of BE Periodic Report Tasks on the FE (FE).
                                                                      2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                      3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                      4. Wait 2 minutes and check whether the alarm is automatically 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 Doris for the target cluster.
                                                                      3. Click the edit icon in the upper right corner, and set Start 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 Doris for the target cluster.
                                                                      3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    diff --git a/docs/mrs/umn/ALM-50212.html b/docs/mrs/umn/ALM-50212.html index 32f491f80..d81c04f1d 100644 --- a/docs/mrs/umn/ALM-50212.html +++ b/docs/mrs/umn/ALM-50212.html @@ -65,13 +65,13 @@

                                                                    Possible Causes

                                                                    The heap memory of the FE process is overused or inappropriately allocated, causing frequent occurrence of the GC process.

                                                                    Handling Procedure

                                                                    Check the GC duration.

                                                                    -
                                                                    1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50212.
                                                                    2. Choose Cluster > Services > Doris > Instances, click the FE instance for which the alarm is generated, and click the Chart tab of the instance.

                                                                      Select JVM from Chart Category on the left, and check whether Accumulated GC duration of the old generation of the FE process is greater than 3 seconds.
                                                                      • If yes, go to 3.
                                                                      • If no, go to 5.
                                                                      +
                                                                      1. On MRS Manager, choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50212.
                                                                      2. Choose Cluster > Services > Doris > Instances, click the FE instance for which the alarm is generated, and click the Chart tab of the instance.

                                                                        Select JVM from Chart Category on the left, and check whether Accumulated GC duration of the old generation of the FE process is greater than 3 seconds.
                                                                        • If yes, go to 3.
                                                                        • If no, go to 5.

                                                                      3. Choose Cluster > Services > Doris > Configurations > All Configurations > FE(Role) > JVM, and increase the value of -Xmx in FE_GC_OPTS. The default value is 8G.

                                                                        • 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 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 Doris for the target cluster.
                                                                      3. Click the edit icon 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 Doris for the target cluster.
                                                                      3. Click the edit icon 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 Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      diff --git a/docs/mrs/umn/ALM-50213.html b/docs/mrs/umn/ALM-50213.html index 535f8dc8f..be431dbc9 100644 --- a/docs/mrs/umn/ALM-50213.html +++ b/docs/mrs/umn/ALM-50213.html @@ -65,10 +65,10 @@

                                                                      Possible Causes

                                                                      There are a large number of concurrent service requests, causing too many queuing tasks.

                                                                      Handling Procedure

                                                                      Check whether the alarm threshold or alarm trigger count is properly configured.

                                                                      -
                                                                      1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Number of tasks that are queuing in the thread pool for interaction between the FE and the BE (FE).
                                                                      2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                      3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                      4. Wait 2 minutes and check whether the alarm is automatically cleared.

                                                                        • If yes, no further action is required.
                                                                        • If no, go to 5.
                                                                        +
                                                                        1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Number of tasks that are queuing in the thread pool for interaction between the FE and the BE (FE).
                                                                        2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                        3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                        4. Wait 2 minutes and check whether the alarm is automatically 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. Expand the Service drop-down list, and select Doris for the target cluster.
                                                                        3. Click the edit icon in the upper right corner, and set Start 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 Doris for the target cluster.
                                                                        3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      diff --git a/docs/mrs/umn/ALM-50214.html b/docs/mrs/umn/ALM-50214.html index 8e0cce86c..aff4e8e79 100644 --- a/docs/mrs/umn/ALM-50214.html +++ b/docs/mrs/umn/ALM-50214.html @@ -65,13 +65,13 @@

                                                                      Possible Causes

                                                                      Large tasks may block the task execution of the queue.

                                                                      Handling Procedure

                                                                      Check the execution status of FE tasks.

                                                                      -
                                                                      1. On FusionInsight Manager, choose Cluster > Services > Doris. Click the Chart tab, select Connection from Chart Category in the left pane, and view the FE MySQL Port Connections chart. If the number of connections is large, click Instances, select the FE instance, and click the Chart tab. Select CPU and Memory from Chart Category and view the CPU Usage of FE chart. If the CPU usage is high, check the Time field in FE audit log /var/log/Bigdata/audit/doris/fe/fe.audit.log to collect statistics on the average task duration. If the value is also high, the alarm is caused by large concurrent tasks.
                                                                      2. After connecting to Doris, run the following command to check whether the default value of queryTimeout is too large. The default value is 300 seconds.

                                                                        show variables like 'query_timeout';

                                                                        +
                                                                        1. On MRS Manager, choose Cluster > Services > Doris. Click the Chart tab, select Connection from Chart Category in the left pane, and view the FE MySQL Port Connections chart. If the number of connections is large, click Instances, select the FE instance, and click the Chart tab. Select CPU and Memory from Chart Category and view the CPU Usage of FE chart. If the CPU usage is high, check the Time field in FE audit log /var/log/Bigdata/audit/doris/fe/fe.audit.log to collect statistics on the average task duration. If the value is also high, the alarm is caused by large concurrent tasks.
                                                                        2. After connecting to Doris, run the following command to check whether the default value of queryTimeout is too large. The default value is 300 seconds.

                                                                          show variables like 'query_timeout';

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

                                                                        3. Run the following command to shorten the timeout period based on site requirements to block the tasks that take a long time:

                                                                          set global query_timeout=xxx;

                                                                          -

                                                                        4. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Queue Length of Query Execution Thread Pool (BE).
                                                                        5. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                        6. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                        7. Wait 10 minutes and check whether the alarm is automatically cleared.

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

                                                                        8. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Queue Length of Query Execution Thread Pool (BE).
                                                                        9. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                        10. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                        11. Wait 10 minutes and check whether the alarm is automatically cleared.

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

                                                                        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 Doris for the target cluster.
                                                                        3. Click the edit icon 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 Doris for the target cluster.
                                                                        3. Click the edit icon 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 Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      diff --git a/docs/mrs/umn/ALM-50215.html b/docs/mrs/umn/ALM-50215.html index 132c3e656..4dec3937c 100644 --- a/docs/mrs/umn/ALM-50215.html +++ b/docs/mrs/umn/ALM-50215.html @@ -65,10 +65,10 @@

                                                                      Possible Causes

                                                                      • The network has a latency.
                                                                      • There are too many concurrent large SQL tasks.

                                                                      Handling Procedure

                                                                      1. Log in to the host where the faulty node is deployed as user root and run ping IP addresses of all Doris nodes to check whether the peer host can be pinged.

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

                                                                      2. Contact the network administrator to restore the network.
                                                                      3. On FusionInsight Manager, choose Cluster > Services > Doris. Click the Chart tab, select Connection from Chart Category in the left pane, and view the FE MySQL Port Connections chart. If the number of connections is large, click Instances, select the FE instance, and click the Chart tab. Select CPU and Memory from Chart Category and view the CPU Usage of FE chart. If the CPU usage is high, check the Time field in FE audit log /var/log/Bigdata/audit/doris/fe/fe.audit.log to collect statistics on the average task duration. If the value is also high, the alarm is caused by large concurrent tasks.
                                                                      4. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Performance > Longest duration of RPC requests received by each method of the FE thrift interface (FE).
                                                                      5. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                      6. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                      7. Wait 10 minutes and check whether the alarm is automatically cleared.

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

                                                                      8. Contact the network administrator to restore the network.
                                                                      9. On MRS Manager, choose Cluster > Services > Doris. Click the Chart tab, select Connection from Chart Category in the left pane, and view the FE MySQL Port Connections chart. If the number of connections is large, click Instances, select the FE instance, and click the Chart tab. Select CPU and Memory from Chart Category and view the CPU Usage of FE chart. If the CPU usage is high, check the Time field in FE audit log /var/log/Bigdata/audit/doris/fe/fe.audit.log to collect statistics on the average task duration. If the value is also high, the alarm is caused by large concurrent tasks.
                                                                      10. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Performance > Longest duration of RPC requests received by each method of the FE thrift interface (FE).
                                                                      11. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                      12. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                      13. Wait 10 minutes and check whether the alarm is automatically cleared.

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

                                                                      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 Doris for the target cluster.
                                                                      3. Click the edit icon 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 Doris for the target cluster.
                                                                      3. Click the edit icon 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 Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      diff --git a/docs/mrs/umn/ALM-50216.html b/docs/mrs/umn/ALM-50216.html index 9888f8582..5b586556c 100644 --- a/docs/mrs/umn/ALM-50216.html +++ b/docs/mrs/umn/ALM-50216.html @@ -65,14 +65,14 @@

                                                                      Possible Causes

                                                                      The FE heap memory is too small.

                                                                      Handling Procedure

                                                                      Check the FE heap memory usage.

                                                                      -
                                                                      1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > Memory usage of the FE node (FE).

                                                                        1. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                        2. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                        +
                                                                        1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > Memory usage of the FE node (FE).

                                                                          1. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                          2. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.

                                                                        2. Log in to the FE node for which the alarm is generated as user omm, run the top command to check the memory usage of processes, locate the process with high memory usage, and check whether the process belongs to the current service and is running properly.

                                                                          • If yes, go to 3.
                                                                          • If no, isolate or stop the process, or adjust the memory size, and check whether the memory is released.

                                                                        3. Restart the affected services or instances and check whether the alarm is cleared.

                                                                          • If yes, no further action is required.
                                                                          • If no, go to 4.
                                                                          • During the restart of the Doris service, the Doris service is unavailable and cannot provide services for external systems. Tasks connected to the Doris service fail.
                                                                          • During instance restart, the tasks running on the nodes of the instance will fail. The tasks on instance nodes that are not restarted are not affected.

                                                                        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 Doris for the target cluster.
                                                                        3. Click the edit icon in the upper right corner, and set Start 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 Doris for the target cluster.
                                                                        3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      diff --git a/docs/mrs/umn/ALM-50217.html b/docs/mrs/umn/ALM-50217.html index 08cde2831..1eca227d6 100644 --- a/docs/mrs/umn/ALM-50217.html +++ b/docs/mrs/umn/ALM-50217.html @@ -65,15 +65,15 @@

                                                                      Possible Causes

                                                                      The FE heap memory is too small.

                                                                      Handling Procedure

                                                                      Check heap memory usage.

                                                                      -
                                                                      1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > Heap memory usage of the FE node (FE).

                                                                        1. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                        2. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                        -

                                                                      2. On FusionInsight Manager, choose Cluster > Services > Doris > FE > Configurations > All Configurations, search for the FE_GC_OPTS parameter, increase the value of -Xmx as required, click Save, and click OK.

                                                                        • If this alarm is generated, the heap memory configured for the current Doris instance is not enough for data transmission. You are advised to open the instance monitoring page, display the Doris heap memory resource status monitoring chart, and observe the change trend of the heap memory used by Doris 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 approximately the same value to prevent performance deterioration caused by heap size adjustment after each GC.
                                                                        • The sum of -Xmx and XX:MaxPermSize cannot be greater than the actual physical memory of the node server.
                                                                        +
                                                                        1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, select the name of the desired cluster, and choose Doris > CPU and Memory > Heap memory usage of the FE node (FE).

                                                                          1. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                          2. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                          +

                                                                        2. On MRS Manager, choose Cluster > Services > Doris > FE > Configurations > All Configurations, search for the FE_GC_OPTS parameter, increase the value of -Xmx as required, click Save, and click OK.

                                                                          • If this alarm is generated, the heap memory configured for the current Doris instance is not enough for data transmission. You are advised to open the instance monitoring page, display the Doris heap memory resource status monitoring chart, and observe the change trend of the heap memory used by Doris 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 approximately the same value to prevent performance deterioration caused by heap size adjustment after each GC.
                                                                          • The sum of -Xmx and XX:MaxPermSize cannot be greater than the actual physical memory of the node server.

                                                                        3. Restart the affected services or instances and check whether the alarm is cleared.

                                                                          • If yes, no further action is required.
                                                                          • If no, go to 4.
                                                                          • During the restart of the Doris service, the Doris service is unavailable and cannot provide services for external systems. Tasks connected to the Doris service fail.
                                                                          • During instance restart, the tasks running on the nodes of the instance will fail. The tasks on instance nodes that are not restarted are not affected.

                                                                        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 Doris for the target cluster.
                                                                        3. Click the edit icon in the upper right corner, and set Start 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 Doris for the target cluster.
                                                                        3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                        This alarm is automatically cleared after the fault is rectified.

                                                                        diff --git a/docs/mrs/umn/ALM-50219.html b/docs/mrs/umn/ALM-50219.html index b3b1e671c..ea1249258 100644 --- a/docs/mrs/umn/ALM-50219.html +++ b/docs/mrs/umn/ALM-50219.html @@ -65,12 +65,12 @@

                                                                        Possible Causes

                                                                        Large tasks may block the task execution of the queue.

                                                                        Handling Procedure

                                                                        Check the execution status of tasks.

                                                                        -
                                                                        1. On FusionInsight Manager, choose Cluster > Services > Doris. Click the Chart tab, select Connection from Chart Category in the left pane, and view the FE MySQL Port Connections chart. If the number of connections is large, click Instances, select the FE instance, and click the Chart tab. Select CPU and Memory from Chart Category and view the CPU Usage of FE chart. If the CPU usage is high, check the Time field in FE audit log /var/log/Bigdata/audit/doris/fe/fe.audit.log to collect statistics on the average task duration. If the value is also high, the alarm is caused by large concurrent tasks.
                                                                        2. After connecting to Doris, run the following command to check the queryTimeout value of the system:

                                                                          show variables like 'query_timeout';

                                                                          +
                                                                          1. On MRS Manager, choose Cluster > Services > Doris. Click the Chart tab, select Connection from Chart Category in the left pane, and view the FE MySQL Port Connections chart. If the number of connections is large, click Instances, select the FE instance, and click the Chart tab. Select CPU and Memory from Chart Category and view the CPU Usage of FE chart. If the CPU usage is high, check the Time field in FE audit log /var/log/Bigdata/audit/doris/fe/fe.audit.log to collect statistics on the average task duration. If the value is also high, the alarm is caused by large concurrent tasks.
                                                                          2. After connecting to Doris, run the following command to check the queryTimeout value of the system:

                                                                            show variables like 'query_timeout';

                                                                            If the value is too large, run the set global query_timeout=xxx; command to shorten the timeout interval and block tasks that last for a long time.

                                                                            -

                                                                          3. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Queue Length of Query Execution Thread Pool (BE).
                                                                          4. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                          5. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                          6. Wait 10 minutes and check whether the alarm is automatically cleared.

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

                                                                          7. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Queue > Queue Length of Query Execution Thread Pool (BE).
                                                                          8. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                          9. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                          10. Wait 10 minutes and check whether the alarm is automatically cleared.

                                                                            • If yes, no further action is required.
                                                                            • If no, go to 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 Doris for the target cluster.
                                                                          3. Click the edit icon 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 Doris for the target cluster.
                                                                          3. Click the edit icon 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 Clearance

                                                                        This alarm is automatically cleared after the fault is rectified.

                                                                        diff --git a/docs/mrs/umn/ALM-50220.html b/docs/mrs/umn/ALM-50220.html index 764fa422f..1dab70681 100644 --- a/docs/mrs/umn/ALM-50220.html +++ b/docs/mrs/umn/ALM-50220.html @@ -68,7 +68,7 @@

                                                                      3. Contact the network administrator to restore the network.
                                                                      4. Wait for a while and check whether the alarm is cleared in the alarm list.

                                                                        • 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 Service drop-down list, and select Doris for the target cluster.
                                                                      3. Click the edit icon 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 Doris for the target cluster.
                                                                      3. Click the edit icon 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 Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      diff --git a/docs/mrs/umn/ALM-50221.html b/docs/mrs/umn/ALM-50221.html index 24a986f3f..d0a3bef93 100644 --- a/docs/mrs/umn/ALM-50221.html +++ b/docs/mrs/umn/ALM-50221.html @@ -64,9 +64,9 @@

                                                                    Possible Causes

                                                                    • The disk space of the cluster is full.
                                                                    • Data skew occurs among BE nodes.
                                                                    -

                                                                    Handling Procedure

                                                                    1. Log in to FusionInsight Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                                                                    2. Expand the disk capacity of the node for which the alarm is generated.
                                                                    3. Go to 4 if the expansion fails or the alarm persists after the expansion.
                                                                    +

                                                                    Handling Procedure

                                                                    1. Log in to MRS Manager, choose O&M > Alarm > Alarms, and view the role name and the IP address for the hostname in Location.
                                                                    2. Expand the disk capacity of the node for which the alarm is generated.
                                                                    3. Go to 4 if the expansion fails or the alarm persists after the expansion.

                                                                    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 Doris 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 the edit icon 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 Doris 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 the edit icon 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 Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    diff --git a/docs/mrs/umn/ALM-50222.html b/docs/mrs/umn/ALM-50222.html index adf3085e4..903b78dc3 100644 --- a/docs/mrs/umn/ALM-50222.html +++ b/docs/mrs/umn/ALM-50222.html @@ -64,7 +64,7 @@

                                                                    Possible Causes

                                                                    • The hard disk is faulty.
                                                                    • The disk permissions are set incorrectly.

                                                                    Handling 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.

                                                                      @@ -77,7 +77,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 Doris and OMS for the target cluster.
                                                                  3. Click the edit icon 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 Doris and OMS for the target cluster.
                                                                  3. Click the edit icon 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 Clearance

                                                                  This alarm is automatically cleared after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-50223.html b/docs/mrs/umn/ALM-50223.html index 09d62848f..810ae4b40 100644 --- a/docs/mrs/umn/ALM-50223.html +++ b/docs/mrs/umn/ALM-50223.html @@ -65,14 +65,14 @@

                                                                  Possible Causes

                                                                  Too much BE node memory has been occupied by other processes, or the maximum memory set for the BE service is too large.

                                                                  Handling Procedure

                                                                  Check whether the maximum memory set for the BE node is proper.

                                                                  -
                                                                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > CPU and Memory > Relationship between the maximum memory size of the BE and the remaining memory size of the machine (BE).
                                                                  2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                  3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                  4. Wait 2 minutes and check whether the alarm is automatically cleared.

                                                                    • If yes, no further action is required.
                                                                    • If no, go to 5.
                                                                    +
                                                                    1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > CPU and Memory > Relationship between the maximum memory size of the BE and the remaining memory size of the machine (BE).
                                                                    2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                    3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                    4. Wait 2 minutes and check whether the alarm is automatically cleared.

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

                                                                    1. Log in to the BE node for which the alarm is generated as user omm, run the top command to check the memory usage of processes, locate the process with high memory usage, and check whether the process belongs to the current service and is running properly.

                                                                      • If yes, go to 6.
                                                                      • If no, isolate or stop the process, or adjust the memory size, and check whether the memory is released.
                                                                      -

                                                                    2. Log in to the BE node for which the alarm is generated as user omm and run the free -g command to check the total memory and remaining memory in the system and estimate the memory usage.
                                                                    3. On FusionInsight Manager, choose Cluster > Services > Doris > Configurations > All Configurations > BE(Role) > Memory and decrease the value of mem_limit. This parameter specifies the maximum memory allowed for BE. Then save the modification and restart the BE instance.

                                                                      During BE instance restart, the tasks running on BE nodes will fail. The tasks on BE nodes that are not restarted are not affected.

                                                                      +

                                                                    4. Log in to the BE node for which the alarm is generated as user omm and run the free -g command to check the total memory and remaining memory in the system and estimate the memory usage.
                                                                    5. On MRS Manager, choose Cluster > Services > Doris > Configurations > All Configurations > BE(Role) > Memory and decrease the value of mem_limit. This parameter specifies the maximum memory allowed for BE. Then save the modification and restart the BE instance.

                                                                      During BE instance restart, the tasks running on BE nodes will fail. The tasks on BE nodes that are not restarted are not affected.

                                                                    6. After the BE instance is restarted, 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 FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                    2. Expand the Service drop-down list, and select Doris for the target cluster.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Doris for the target cluster.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                  This alarm is automatically cleared after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-50224.html b/docs/mrs/umn/ALM-50224.html index 97ad4ab48..f33153299 100644 --- a/docs/mrs/umn/ALM-50224.html +++ b/docs/mrs/umn/ALM-50224.html @@ -65,10 +65,10 @@

                                                                  Possible Causes

                                                                  A BE exception may occur. As a result, the number of failed tasks increases in a certain scenario.

                                                                  Handling Procedure

                                                                  Check whether the alarm threshold or alarm trigger count is properly configured.

                                                                  -
                                                                  1. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Exception > Check whether the number of failed tasks of a certain type increases (BE).
                                                                  2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                  3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                  4. Wait 2 minutes and check whether the alarm is automatically cleared.

                                                                    • If yes, no further action is required.
                                                                    • If no, go to 5.
                                                                    +
                                                                    1. Log in to MRS Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, and choose Doris > Exception > Check whether the number of failed tasks of a certain type increases (BE).
                                                                    2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
                                                                    3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
                                                                    4. Wait 2 minutes and check whether the alarm is automatically 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. Expand the Service drop-down list, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                  You need to manually clear the alarm after the fault is rectified.

                                                                  diff --git a/docs/mrs/umn/ALM-50225.html b/docs/mrs/umn/ALM-50225.html index 8cf10386f..a9b56b906 100644 --- a/docs/mrs/umn/ALM-50225.html +++ b/docs/mrs/umn/ALM-50225.html @@ -64,11 +64,11 @@

                                                                  Possible Causes

                                                                  The FE instance is faulty or restarted.

                                                                  -

                                                                  Handling Procedure

                                                                  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50225.
                                                                  2. Choose Cluster > Services > Doris > Instances, click the FE instance for which the alarm is generated, and check whether Running Status of the instance is Restoring.

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

                                                                    Handling Procedure

                                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50225.
                                                                    2. Choose Cluster > Services > Doris > Instances, click the FE instance for which the alarm is generated, and check whether Running Status of the instance is Restoring.

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

                                                                    3. Wait 2 minutes and check whether the alarm is automatically 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 Service drop-down list, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    diff --git a/docs/mrs/umn/ALM-50226.html b/docs/mrs/umn/ALM-50226.html index 858db6b40..519805519 100644 --- a/docs/mrs/umn/ALM-50226.html +++ b/docs/mrs/umn/ALM-50226.html @@ -64,11 +64,11 @@

                                                                  Possible Causes

                                                                  The BE instance is faulty or restarted.

                                                                  -

                                                                  Handling Procedure

                                                                  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50226.
                                                                  2. Choose Cluster > Services > Doris > Instances, click the BE instance for which the alarm is generated, and check whether Running Status of the instance is Restoring.

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

                                                                    Handling Procedure

                                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50226.
                                                                    2. Choose Cluster > Services > Doris > Instances, click the BE instance for which the alarm is generated, and check whether Running Status of the instance is Restoring.

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

                                                                    3. Wait 2 minutes and check whether the alarm is automatically 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 Service drop-down list, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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, select Doris for the target cluster, and click OK.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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 Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    diff --git a/docs/mrs/umn/ALM-50227.html b/docs/mrs/umn/ALM-50227.html new file mode 100644 index 000000000..4b9bbbd64 --- /dev/null +++ b/docs/mrs/umn/ALM-50227.html @@ -0,0 +1,92 @@ + + +

                                                                    ALM-50227 Concurrent Doris Tenant Queries Exceeds the Threshold

                                                                    +

                                                                    Alarm Description

                                                                    The system checks concurrent tenant queries on FE nodes every 30 seconds. This alarm is generated when the number exceeds the threshold (90% by default).

                                                                    +

                                                                    This alarm is cleared when the number of concurrent queries from the FE nodes falls below the threshold.

                                                                    +

                                                                    This alarm applies only to MRS 3.3.1 or later.

                                                                    +
                                                                    +

                                                                    Alarm Attributes

                                                                    +
                                                                    + + + + + + + + + +

                                                                    Alarm ID

                                                                    +

                                                                    Alarm Severity

                                                                    +

                                                                    Auto Cleared

                                                                    +

                                                                    50227

                                                                    +

                                                                    Major

                                                                    +

                                                                    Yes

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Alarm Parameters

                                                                    +
                                                                    + + + + + + + + + + + + + + + + + + + + + + +

                                                                    Type

                                                                    +

                                                                    Parameter

                                                                    +

                                                                    Description

                                                                    +

                                                                    Location Information

                                                                    +

                                                                    Source

                                                                    +

                                                                    Specifies the cluster or system for which the alarm was generated.

                                                                    +

                                                                    ServiceName

                                                                    +

                                                                    Specifies the service for which the alarm was generated.

                                                                    +

                                                                    RoleName

                                                                    +

                                                                    Specifies the role for which the alarm was generated.

                                                                    +

                                                                    HostName

                                                                    +

                                                                    Specifies the host for which the alarm was generated.

                                                                    +

                                                                    Additional Information

                                                                    +

                                                                    Detail

                                                                    +

                                                                    Specifies the alarm triggering condition.

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Impact on the System

                                                                    Too many concurrent queries consume a large number of system resources. This leads to slow response and even request rejection.

                                                                    +
                                                                    +

                                                                    Possible Causes

                                                                    There is a large number of service requests.

                                                                    +
                                                                    +

                                                                    Handling Procedure

                                                                    Check the actual number of concurrent tenant queries on FE nodes.

                                                                    +
                                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50227.
                                                                    2. Choose Cluster > Services > Doris > Instances, select the FE instance for which the alarm is generated, and click Chart. Click Tenant Resource in the Chart Category pane, and check whether the actual number of concurrent queries in the Number of Concurrent Tenant Queries chart is greater than the threshold. The default value is 90%.

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

                                                                    3. Check whether a large number of tasks were being executed during the alarm period.

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

                                                                    4. On MRS Manager, choose O&M > Alarm > Thresholds > Name of the desired cluster > Doris > Tenant Resources. Increase the threshold value and trigger counts based on service requirements. Check whether the alarm is cleared.

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

                                                                    +

                                                                    Collect fault information.

                                                                    +
                                                                    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 Doris 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 the edit icon 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 Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    +
                                                                    +

                                                                    Related Information

                                                                    None.

                                                                    +
                                                                    +
                                                                    + + diff --git a/docs/mrs/umn/ALM-50228.html b/docs/mrs/umn/ALM-50228.html new file mode 100644 index 000000000..1ee2141d4 --- /dev/null +++ b/docs/mrs/umn/ALM-50228.html @@ -0,0 +1,95 @@ + + +

                                                                    ALM-50228 Memory Usage of a Doris Tenant Exceeds the Threshold

                                                                    +

                                                                    Alarm Description

                                                                    The system checks the memory usage of BE nodes every 30 seconds. This alarm is generated when the memory usage of a tenant exceeds the threshold.

                                                                    +

                                                                    This alarm is cleared when the system detects that the memory usage of tenant's BE nodes is lower than the threshold.

                                                                    +

                                                                    This alarm applies only to MRS 3.3.1 or later.

                                                                    +
                                                                    +

                                                                    Alarm Attributes

                                                                    +
                                                                    + + + + + + + + + +

                                                                    Alarm ID

                                                                    +

                                                                    Alarm Severity

                                                                    +

                                                                    Auto Cleared

                                                                    +

                                                                    50228

                                                                    +

                                                                    Critical (default threshold: 90%)

                                                                    +

                                                                    Major (default threshold: 85%)

                                                                    +

                                                                    Yes

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Alarm Parameters

                                                                    +
                                                                    + + + + + + + + + + + + + + + + + + + + + + +

                                                                    Type

                                                                    +

                                                                    Parameter

                                                                    +

                                                                    Description

                                                                    +

                                                                    Location Information

                                                                    +

                                                                    Source

                                                                    +

                                                                    Specifies the cluster or system for which the alarm was generated.

                                                                    +

                                                                    ServiceName

                                                                    +

                                                                    Specifies the service for which the alarm was generated.

                                                                    +

                                                                    RoleName

                                                                    +

                                                                    Specifies the role for which the alarm was generated.

                                                                    +

                                                                    HostName

                                                                    +

                                                                    Specifies the host for which the alarm was generated.

                                                                    +

                                                                    Additional Information

                                                                    +

                                                                    Detail

                                                                    +

                                                                    Specifies the alarm triggering condition.

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Impact on the System

                                                                    Processes respond slowly or do not work.

                                                                    +
                                                                    +

                                                                    Possible Causes

                                                                    The data queried by the tenant is too large, and memory soft limit is not enabled.

                                                                    +
                                                                    +

                                                                    Handling Procedure

                                                                    Check the memory used by the BE nodes of the tenant.

                                                                    +
                                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50228.
                                                                    2. Click Thresholds and choose Name of the desired cluster > Doris > Tenant Resources > Memory Usage Exceeds Threshold to view and record the threshold.
                                                                    3. Choose Cluster > Services > Doris > Instances, select the BE instance for which the alarm is generated, and click Chart. Select Tenant Resource from the Chart Category pane, check whether the actual memory usage in the Memory Used by Tenants chart is greater than the threshold obtained in 2, and record the name of the tenant whose memory usage exceeds the threshold.

                                                                      • If yes, go to 3.
                                                                      • If no, go to 8.
                                                                      +

                                                                    4. Check whether a large amount of table data were being queried during the alarm period.

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

                                                                    5. Choose Tenant Resources > Tenant Resources Management. In the tenant list, click the tenant name in 2, and then the Resource tab. Click the edit button on the right of Resource Details, and check whether Memory Soft Limit is enabled.

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

                                                                    6. Enable Soft Memory Limit and click OK. Check whether the alarm is cleared in the alarm list.

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

                                                                    7. Choose O&M > Alarm > Thresholds > Name of the desired cluster > Doris > Tenant Resources. Increase the threshold value and trigger counts based on service requirements. Check whether the alarm is cleared in the alarm list.

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

                                                                    +

                                                                    Collect fault information.

                                                                    +
                                                                    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 Doris for the target cluster.
                                                                    3. In the Host area, select the host to which the role belongs and click OK.
                                                                    4. Click the edit icon 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 Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    +
                                                                    +

                                                                    Related Information

                                                                    None.

                                                                    +
                                                                    +
                                                                    + + diff --git a/docs/mrs/umn/ALM-50229.html b/docs/mrs/umn/ALM-50229.html new file mode 100644 index 000000000..fb9b0a4a1 --- /dev/null +++ b/docs/mrs/umn/ALM-50229.html @@ -0,0 +1,97 @@ + + +

                                                                    ALM-50229 Doris FE Failed to Connect to OBS

                                                                    +

                                                                    Alarm Description

                                                                    The system checks whether the connection between the Doris FE nodes and OBS is available every 30 seconds. This alarm is generated when the connection status code is not 0.

                                                                    +

                                                                    This alarm is cleared when the connection status code is 0.

                                                                    +

                                                                    This alarm applies only to MRS 3.3.1 or later.

                                                                    +
                                                                    +

                                                                    Alarm Attributes

                                                                    +
                                                                    + + + + + + + + + +

                                                                    Alarm ID

                                                                    +

                                                                    Alarm Severity

                                                                    +

                                                                    Auto Cleared

                                                                    +

                                                                    50229

                                                                    +

                                                                    Critical

                                                                    +

                                                                    Yes

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Alarm Parameters

                                                                    +
                                                                    + + + + + + + + + + + + + + + + + + + + + + +

                                                                    Type

                                                                    +

                                                                    Parameter

                                                                    +

                                                                    Description

                                                                    +

                                                                    Location Information

                                                                    +

                                                                    Source

                                                                    +

                                                                    Specifies the cluster or system for which the alarm was generated.

                                                                    +

                                                                    ServiceName

                                                                    +

                                                                    Specifies the service for which the alarm was generated.

                                                                    +

                                                                    RoleName

                                                                    +

                                                                    Specifies the role for which the alarm was generated.

                                                                    +

                                                                    HostName

                                                                    +

                                                                    Specifies the host for which the alarm was generated.

                                                                    +

                                                                    Additional Information

                                                                    +

                                                                    Detail

                                                                    +

                                                                    Specifies the alarm triggering condition.

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Impact on the System

                                                                    Some functions of Doris are unavailable, for example, cold-hot separation and Hive OBS Catalog.

                                                                    +
                                                                    +

                                                                    Possible Causes

                                                                    • The obtained AK/SK is invalid.
                                                                    • This alarm is generated when OBS connection fails.
                                                                    +
                                                                    +

                                                                    Handling Procedure

                                                                    Determine the cause.

                                                                    +
                                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50229, and check the CurrentValue in Additional Information.

                                                                      • If CurrentValue is 2, the obtained AK/SK is invalid. Go to 2.
                                                                      • If CurrentValue is 3, OBS fails to be connected. Go to 7.
                                                                      +

                                                                    +

                                                                    The obtained AK/SK is invalid.

                                                                    +
                                                                    1. Log in to the MRS Service console, move the cursor on the username in the upper right corner, and choose My Credentials.
                                                                    2. Click Access Keys and check whether Status of the target key is Enabled.

                                                                      • If yes, go to 4.
                                                                      • If no, click Enable in the Operation column of the row containing the key.
                                                                      +

                                                                    3. Click Delete in the row where the key is to delete the key. Click Create Access Key and click OK. Download the new access key and obtain the AK and SK.
                                                                    4. Set the obs.access_key and obs.secret_key parameters to the obtained AK/SK.
                                                                    5. Wait for about 1 minute, log in to MRS Manager, choose O&M > Alarm > Alarms, and check whether the alarm is cleared.

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

                                                                    +

                                                                    Failed to connect to OBS.

                                                                    +
                                                                    1. Check whether the network connection between the cluster and OBS is normal.

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

                                                                    2. Log in to the MRS management console. In the service list, choose Identity and Access Management. Click Agencies in the navigation pane. In the agency list, click the agency name configured for the MRS cluster.
                                                                    3. Click Permissions and click the name of each policy in the permission list.
                                                                    4. In the Content area, search for Action and check whether obs is contained.

                                                                      • If yes, go to 12.
                                                                      • If no, go to 11.
                                                                      +

                                                                    5. Create an OBS permission policy by following the instructions provided in the guide for configuring doris cold and hot data separation. Wait for about 15 to 20 minutes and check whether the alarm is cleared.

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

                                                                    1. Contact O&M personnel for fault diagnosis and rectification.
                                                                    +
                                                                    +

                                                                    Alarm Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    +
                                                                    +

                                                                    Related Information

                                                                    None.

                                                                    +
                                                                    +
                                                                    + + diff --git a/docs/mrs/umn/ALM-50230.html b/docs/mrs/umn/ALM-50230.html new file mode 100644 index 000000000..5c88f99fb --- /dev/null +++ b/docs/mrs/umn/ALM-50230.html @@ -0,0 +1,97 @@ + + +

                                                                    ALM-50230 Doris BE Cannot Connect to OBS

                                                                    +

                                                                    Alarm Description

                                                                    The system checks whether the connection between the Doris BE nodes and OBS is available every 30 seconds. This alarm is generated when the connection status code is not 0.

                                                                    +

                                                                    This alarm is cleared when the connection status code is 0.

                                                                    +

                                                                    This alarm applies only to MRS 3.3.1 or later.

                                                                    +
                                                                    +

                                                                    Alarm Attributes

                                                                    +
                                                                    + + + + + + + + + +

                                                                    Alarm ID

                                                                    +

                                                                    Alarm Severity

                                                                    +

                                                                    Auto Cleared

                                                                    +

                                                                    50230

                                                                    +

                                                                    Critical

                                                                    +

                                                                    Yes

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Alarm Parameters

                                                                    +
                                                                    + + + + + + + + + + + + + + + + + + + + + + +

                                                                    Type

                                                                    +

                                                                    Parameter

                                                                    +

                                                                    Description

                                                                    +

                                                                    Location Information

                                                                    +

                                                                    Source

                                                                    +

                                                                    Specifies the cluster or system for which the alarm was generated.

                                                                    +

                                                                    ServiceName

                                                                    +

                                                                    Specifies the service for which the alarm was generated.

                                                                    +

                                                                    RoleName

                                                                    +

                                                                    Specifies the role for which the alarm was generated.

                                                                    +

                                                                    HostName

                                                                    +

                                                                    Specifies the host for which the alarm was generated.

                                                                    +

                                                                    Additional Information

                                                                    +

                                                                    Detail

                                                                    +

                                                                    Specifies the alarm triggering condition.

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Impact on the System

                                                                    Some functions of Doris are unavailable, for example, cold-hot separation and Hive OBS Catalog.

                                                                    +
                                                                    +

                                                                    Possible Causes

                                                                    • The obtained AK/SK is invalid.
                                                                    • This alarm is generated when OBS connection fails.
                                                                    +
                                                                    +

                                                                    Handling Procedure

                                                                    Determine the cause.

                                                                    +
                                                                    1. Log in to MRS Manager and choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50230, and check the CurrentValue in Additional Information.

                                                                      • If CurrentValue is 2, the obtained AK/SK is invalid. Go to 2.
                                                                      • If CurrentValue is 3, OBS fails to be connected. Go to 7.
                                                                      +

                                                                    +

                                                                    The obtained AK/SK is invalid.

                                                                    +
                                                                    1. Log in to the MRS Service console, move the cursor on the username in the upper right corner, and choose My Credentials.
                                                                    2. Click Access Keys and check whether Status of the target key is Enabled.

                                                                      • If yes, go to 4.
                                                                      • If no, click Enable in the Operation column of the row containing the key.
                                                                      +

                                                                    3. Click Delete in the row where the key is to delete the key. Click Create Access Key and click OK. Download the new access key and obtain the AK and SK.
                                                                    4. Set the obs.access_key and obs.secret_key parameters to the obtained AK/SK.
                                                                    5. Wait for about 1 minute, log in to MRS Manager, choose O&M > Alarm > Alarms, and check whether the alarm is cleared.

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

                                                                    +

                                                                    Failed to connect to OBS.

                                                                    +
                                                                    1. Check whether the network connection between the cluster and OBS is normal.

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

                                                                    2. Log in to the MRS management console. In the service list, choose Identity and Access Management. Click Agencies in the navigation pane. In the agency list, click the agency name configured for the MRS cluster.
                                                                    3. Click Permissions and click the name of each policy in the permission list.
                                                                    4. In the Content area, search for Action and check whether obs is contained.

                                                                      • If yes, go to 12.
                                                                      • If no, go to 11.
                                                                      +

                                                                    5. Create an OBS permission policy by following the instructions provided in the guide for configuring doris cold and hot data separation. Wait for about 15 to 20 minutes and check whether the alarm is cleared.

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

                                                                    1. Contact O&M personnel for fault diagnosis and rectification.
                                                                    +
                                                                    +

                                                                    Alarm Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    +
                                                                    +

                                                                    Related Information

                                                                    None.

                                                                    +
                                                                    +
                                                                    + + diff --git a/docs/mrs/umn/ALM-50231.html b/docs/mrs/umn/ALM-50231.html new file mode 100644 index 000000000..422dfae6e --- /dev/null +++ b/docs/mrs/umn/ALM-50231.html @@ -0,0 +1,99 @@ + + +

                                                                    ALM-50231 Abnormal Tablets Exist in Doris

                                                                    +

                                                                    Alarm Description

                                                                    The alarm module checks for abnormal tablets in the Doris cluster every 5 minutes. This alarm is generated when an abnormal tablet is detected.

                                                                    +

                                                                    This alarm is cleared when no abnormal tablet exists in the Doris cluster.

                                                                    +

                                                                    This alarm applies only to MRS 3.5.0.

                                                                    +
                                                                    +

                                                                    Alarm Attributes

                                                                    +
                                                                    + + + + + + + + + +

                                                                    Alarm ID

                                                                    +

                                                                    Alarm Severity

                                                                    +

                                                                    Auto Cleared

                                                                    +

                                                                    50231

                                                                    +

                                                                    Critical

                                                                    +

                                                                    Yes

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Alarm Parameters

                                                                    +
                                                                    + + + + + + + + + + + + + + + + + + +

                                                                    Type

                                                                    +

                                                                    Parameter

                                                                    +

                                                                    Description

                                                                    +

                                                                    Location Information

                                                                    +

                                                                    Source

                                                                    +

                                                                    Specifies the cluster or system for which the alarm was generated.

                                                                    +

                                                                    ServiceName

                                                                    +

                                                                    Specifies the service for which the alarm was generated.

                                                                    +

                                                                    RoleName

                                                                    +

                                                                    Specifies the role for which the alarm was generated.

                                                                    +

                                                                    HostName

                                                                    +

                                                                    Specifies the host for which the alarm was generated.

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Impact on the System

                                                                    Tablet exceptions may cause data query or write failures.

                                                                    +
                                                                    +

                                                                    Possible Causes

                                                                    The Doris data write frequency is too high, causing abnormal compaction operations or tablet migration failures.

                                                                    +
                                                                    +

                                                                    Handling Procedure

                                                                    1. Log in to MRS Manager, choose O&M > Alarm > Alarms, wait two minutes, and check whether the alarm is automatically cleared (the alarm logic includes the automatic clearance function).

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

                                                                    +

                                                                    Check the abnormal tablet and rectify the fault.

                                                                    +
                                                                    1. Select the alarm and check the value of tabletId in Additional Information. If there are a large number of abnormal tablets and the additional information cannot completely display related information, search for "Abnormal tablets have" in the ${BIGDATA_LOG_HOME}/nodeagent/monitorlog/pluginmonitor.log file on the Master FE node. View the information about all abnormal tablets.
                                                                    2. Log in to the node where MySQL is installed and connect to the Doris database.

                                                                      If Kerberos authentication (security mode) has been enabled for the cluster, run the following commands to connect to the Doris database:

                                                                      +

                                                                      export LIBMYSQL_ENABLE_CLEARTEXT_PLUGIN=1

                                                                      +

                                                                      mysql -uDatabase login username -pDatabase login password -PConnection port for FE queries -hIP address of the Doris FE instance

                                                                      +
                                                                      • To obtain the query connection port of the Doris FE instance, you can log in to MRS Manager, choose Cluster > Services > Doris > Configurations, and query the value of query_port of the Doris service.
                                                                      • You can log in to MRS Manager and choose Cluster > Services > Doris > Instances to view the service IP address of any Doris FE instance.
                                                                      +
                                                                      +

                                                                    3. Run the following command to view details about the abnormal tablet:

                                                                      show tablet tabletId;

                                                                      +

                                                                      Record the DbName and TableName values of the abnormal tablet. Copy and run the command in the DetailCmd column in the command output as follows:

                                                                      +

                                                                      show proc xxx;

                                                                      +

                                                                      In the command output, check whether the value of LstFailedTime is NULL and whether the value of VersionCount is greater than the specified threshold (200 by default).

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

                                                                    4. Run the following command to view the tablet repair and scheduling tasks that are being executed in the system:

                                                                      show proc "/cluster_balance";

                                                                      +

                                                                      Check whether the values of pending_tablets and running_tablets in the command output decrease significantly based on the actual running environment.

                                                                      +
                                                                      • If yes, go to 6.
                                                                      • If no, go to 8.
                                                                      +

                                                                    5. Restore the abnormal table first. In the command, replace tableName with the table name recorded in 4.

                                                                      admin repair table tableName;

                                                                      +

                                                                    6. After the abnormal table is restored, wait 2 minutes and check whether the alarm is automatically cleared in the alarm list.

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

                                                                    +

                                                                    Collect fault information.

                                                                    +
                                                                    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 Doris for the target cluster.
                                                                    3. Click the edit icon 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 Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    +
                                                                    +

                                                                    Related Information

                                                                    None.

                                                                    +
                                                                    +
                                                                    + + diff --git a/docs/mrs/umn/ALM-50232.html b/docs/mrs/umn/ALM-50232.html new file mode 100644 index 000000000..a84d9417d --- /dev/null +++ b/docs/mrs/umn/ALM-50232.html @@ -0,0 +1,112 @@ + + +

                                                                    ALM-50232 Large Tablets in Doris

                                                                    +

                                                                    Alarm Description

                                                                    The alarm module checks whether a tablet greater than 3 GB (specified by the alarm_tablet_max_size parameter) exists in the Doris cluster every 5 minutes. This alarm is generated when such a tablet exists in the Doris cluster.

                                                                    +

                                                                    This alarm is cleared when no such a tablet exists in the Doris cluster.

                                                                    +

                                                                    This alarm applies only to MRS 3.5.0.

                                                                    +
                                                                    +

                                                                    Alarm Attributes

                                                                    +
                                                                    + + + + + + + + + +

                                                                    Alarm ID

                                                                    +

                                                                    Alarm Severity

                                                                    +

                                                                    Auto Cleared

                                                                    +

                                                                    50232

                                                                    +

                                                                    Warning

                                                                    +

                                                                    Yes

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Alarm Parameters

                                                                    +
                                                                    + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                                    Type

                                                                    +

                                                                    Parameter

                                                                    +

                                                                    Description

                                                                    +

                                                                    Location Information

                                                                    +

                                                                    Source

                                                                    +

                                                                    Specifies the cluster or system for which the alarm was generated.

                                                                    +

                                                                    ServiceName

                                                                    +

                                                                    Specifies the service for which the alarm was generated.

                                                                    +

                                                                    RoleName

                                                                    +

                                                                    Specifies the role for which the alarm was generated.

                                                                    +

                                                                    HostName

                                                                    +

                                                                    Specifies the host for which the alarm was generated.

                                                                    +

                                                                    Additional Information

                                                                    +

                                                                    db

                                                                    +

                                                                    Specifies the database where a large tablet exists.

                                                                    +

                                                                    table

                                                                    +

                                                                    Specifies the table name of the large tablet.

                                                                    +
                                                                    +
                                                                    +
                                                                    +

                                                                    Impact on the System

                                                                    If a tablet is large, the Doris query speed or compaction speed may slow down.

                                                                    +
                                                                    +

                                                                    Possible Causes

                                                                    The data written to the Doris table is greater than the estimated value or the partition settings are improper. As a result, the sizes of tablets in different partitions differ greatly.

                                                                    +
                                                                    +

                                                                    Handling Procedure

                                                                    Check whether the imported data is too large or the table field partitions are improperly set.

                                                                    +
                                                                    1. Log in to MRS Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 50232, and view the db and table values in Additional Information. If there are too many large tablets and the additional information cannot completely display related information, search for "Large tablets have" in the ${BIGDATA_LOG_HOME}/nodeagent/monitorlog/pluginmonitor.log file on the Master FE node. View the information about all large tablets.
                                                                    2. Log in to the node where MySQL is installed and connect to the Doris database.

                                                                      If Kerberos authentication (security mode) has been enabled for the cluster, run the following commands to connect to the Doris database:

                                                                      +

                                                                      export LIBMYSQL_ENABLE_CLEARTEXT_PLUGIN=1

                                                                      +

                                                                      mysql -uDatabase login username -pDatabase login password -PConnection port for FE queries -hIP address of the Doris FE instance

                                                                      +
                                                                      • To obtain the query connection port of the Doris FE instance, you can log in to MRS Manager, choose Cluster > Services > Doris > Configurations, and query the value of query_port of the Doris service.
                                                                      • You can log in to MRS Manager and choose Cluster > Services > Doris > Instances to view the service IP address of any Doris FE instance.
                                                                      +
                                                                      +

                                                                    3. Run the following command to view details about the abnormal tablet:

                                                                      show tablets from dbName.tableName;

                                                                      +

                                                                      Check whether the ratio of the tablet sizes in the command output is less than 10%.

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

                                                                    4. The imported data is greater than the estimated data. As a result, the sizes of tablets in different partitions differ greatly. Run the following command to view the table creation statement:

                                                                      show create table dbName.tableName;

                                                                      +

                                                                      Re-estimate the amount of data to be written to the table. Based on the data volume, increase the size of BUCKETS to ensure that the tablet size in each partition ranges from 100 MB to 3 GB. Re-create the tableNameBak table and go to 6.

                                                                      +

                                                                    5. Tablet sizes in different partitions vary greatly due to improper settings of table partition fields. Run the following command to view the table creation statement:

                                                                      show create table dbName.tableName;

                                                                      +

                                                                      Reset the partition field in the table creation statement. The partition field can be used to distinguish data in the table more evenly. Create the tableNameBak table and go to 6.

                                                                      +

                                                                    6. Run the following command to write the data in the tableName table reported in the alarm to the tableNameBak table:

                                                                      insert into tableNameBak select * from tableName;

                                                                      +

                                                                    7. After data is successfully written, run the following commands to check whether the number of data records in the tableName table is the same as that in the tableNameBak table:

                                                                      select count(*) from dbName.tableName;

                                                                      +

                                                                      select count(*) from dbName.tableNameBak;

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

                                                                    8. Run the following command to delete the tableNameBak table:

                                                                      drop table dbName.tableNameBak;

                                                                      +

                                                                      After the table is deleted, increase the value of BUCKETS or reset the table fields to create a table, perform 6 to 7 to import data, and compare the data. If the data records are still inconsistent, go to 11.

                                                                      +

                                                                    9. Run the following command to delete the tableName table:

                                                                      drop table dbName.tableName;

                                                                      +

                                                                      Run the following command to change the table name:

                                                                      +

                                                                      alter table dbName.tableNameBak rename dbName.tableName;

                                                                      +

                                                                    1. After the data in the two tables is consistent, wait 5 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 MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
                                                                    2. Expand the Service drop-down list, and select Doris for the target cluster.
                                                                    3. Click the edit icon in the upper right corner, and set Start 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.
                                                                    +
                                                                    +
                                                                    + + diff --git a/docs/mrs/umn/ALM-50401.html b/docs/mrs/umn/ALM-50401.html index 1442d0046..2719ca94c 100644 --- a/docs/mrs/umn/ALM-50401.html +++ b/docs/mrs/umn/ALM-50401.html @@ -62,13 +62,13 @@

                                                                  Possible Causes

                                                                  Too many jobs are submitted instantaneously.

                                                                  -

                                                                  Handling Procedure

                                                                  1. Log in to FusionInsight Manager and choose Cluster > Services > JobGateway.
                                                                  2. Click the Instances tab, click Add Instance, and add JobServer instances based on the number of submitted jobs.
                                                                  1. After the instances are added, restart the JobGateway service.

                                                                    The job functions of JobGateway will become unavailable during the service restart.

                                                                    +

                                                                    Handling Procedure

                                                                    1. Log in to MRS Manager and choose Cluster > Services > JobGateway.
                                                                    2. Click the Instances tab, click Add Instance, and add JobServer instances based on the number of submitted jobs.
                                                                    1. After the instances are added, restart the JobGateway service.

                                                                      The job functions of JobGateway will become unavailable during the service restart.

                                                                    2. Wait 5 minutes and check whether the alarm is automatically 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. Expand the Service drop-down list, and select JobGateway 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.
                                                                    1. 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 JobGateway 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.
                                                                    1. Contact O&M personnel and provide the collected logs.

                                                                    Alarm Clearance

                                                                    This alarm is automatically cleared after the fault is rectified.

                                                                    diff --git a/docs/mrs/umn/ALM-50402.html b/docs/mrs/umn/ALM-50402.html index dc01b6ad9..a057f9277 100644 --- a/docs/mrs/umn/ALM-50402.html +++ b/docs/mrs/umn/ALM-50402.html @@ -61,12 +61,12 @@

                                                                    Possible Causes

                                                                    The node where the JobGateway service locates is faulty.

                                                                    -

                                                                    Handling Procedure

                                                                    1. Log in to FusionInsight Manager, choose Cluster > Services > JobGateway, and click the Instance tab. Check for JobServer or JobBalancer instances that are faulty or not started and view the host names of these instances.
                                                                    2. On the Alarm page of FusionInsight Manager, check whether the NodeAgent Process Is Abnormal alarm is generated.

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

                                                                      Handling Procedure

                                                                      1. Log in to MRS Manager, choose Cluster > Services > JobGateway, and click the Instance tab. Check for JobServer or JobBalancer instances that are faulty or not started and view the host names of these instances.
                                                                      2. On the Alarm page of MRS Manager, check whether the NodeAgent Process Is Abnormal alarm is generated.

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

                                                                      3. Check whether the host name in the alarm information is the same as the host name in 1.

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

                                                                      4. Clear the alarm by following the instructions provided in ALM-12006 NodeAgent Process Is Abnormal.
                                                                      5. In the alarm list, check whether alarm JobGateway Service Unavailable is cleared.

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

                                                                      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 JobGateway 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 JobGateway 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 Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      diff --git a/docs/mrs/umn/ALM-50406.html b/docs/mrs/umn/ALM-50406.html new file mode 100644 index 000000000..31ff117ea --- /dev/null +++ b/docs/mrs/umn/ALM-50406.html @@ -0,0 +1,82 @@ + + +

                                                                      ALM-50406 Failure Rate of the JobServer Job Submission API Exceeds the Threshold

                                                                      +

                                                                      This section is available for MRS 3.5.0-LTS or later version only.

                                                                      +
                                                                      +

                                                                      Alarm Description

                                                                      The system checks the failure rate of the JobServer job submission API every 30 seconds. This alarm is generated when the failure rate exceeds the threshold (80% by default).

                                                                      +

                                                                      This alarm is cleared when the failure rate falls below the threshold.

                                                                      +
                                                                      +

                                                                      Alarm Attributes

                                                                      +
                                                                      + + + + + + + + + +

                                                                      Alarm ID

                                                                      +

                                                                      Alarm Severity

                                                                      +

                                                                      Auto Cleared

                                                                      +

                                                                      50406

                                                                      +

                                                                      Critical

                                                                      +

                                                                      Yes

                                                                      +
                                                                      +
                                                                      +
                                                                      +

                                                                      Alarm Parameters

                                                                      +
                                                                      + + + + + + + + + + + + + + + + +

                                                                      Parameter

                                                                      +

                                                                      Description

                                                                      +

                                                                      Source

                                                                      +

                                                                      Specifies the cluster or system for which the alarm was generated.

                                                                      +

                                                                      ServiceName

                                                                      +

                                                                      Specifies the service for which the alarm was generated.

                                                                      +

                                                                      RoleName

                                                                      +

                                                                      Specifies the role for which the alarm was generated.

                                                                      +

                                                                      HostName

                                                                      +

                                                                      Specifies the host for which the alarm was generated.

                                                                      +
                                                                      +
                                                                      +
                                                                      +

                                                                      Impact on the System

                                                                      A job may fail to be submitted, for example, through the REST API.

                                                                      +
                                                                      +

                                                                      Possible Causes

                                                                      The JobServer instance on the node is abnormal.

                                                                      +
                                                                      +

                                                                      Handling Procedure

                                                                      1. On MRS Manager, choose O&M > Alarm > Alarms, expand details of this alarm in the right pane, and obtain HostName of the node for which the alarm is generated in Location.
                                                                      1. On MRS Manager, choose Cluster > Services > JobGateway > Instances.
                                                                      2. Select the instance for which the alarm is generated, click More, and select Instance Rolling Restart.

                                                                        Services may be affected or interrupted during the restart. You are advised to perform the restart during off-peak hours.

                                                                        +
                                                                        +

                                                                      3. Check whether the instance running status is normal after the restart.

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

                                                                      4. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

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

                                                                      +

                                                                      Collect fault information.

                                                                      +
                                                                      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 JobGateway 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.
                                                                      1. Contact O&M personnel and provide the collected logs.
                                                                      +
                                                                      +

                                                                      Alarm Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      +
                                                                      +

                                                                      Related Information

                                                                      None.

                                                                      +
                                                                      +
                                                                      + + diff --git a/docs/mrs/umn/ALM-50407.html b/docs/mrs/umn/ALM-50407.html new file mode 100644 index 000000000..ff9a0072f --- /dev/null +++ b/docs/mrs/umn/ALM-50407.html @@ -0,0 +1,82 @@ + + +

                                                                      ALM-50407 Failure Rate of the JobServer Job Query API Exceeds the Threshold

                                                                      +

                                                                      This section is available for MRS 3.5.0-LTS or later version only.

                                                                      +
                                                                      +

                                                                      Alarm Description

                                                                      The system checks the failure rate of the JobServer job query API every 30 seconds. This alarm is generated when the failure rate exceeds the threshold (80% by default).

                                                                      +

                                                                      This alarm is cleared when the failure rate falls below the threshold.

                                                                      +
                                                                      +

                                                                      Alarm Attributes

                                                                      +
                                                                      + + + + + + + + + +

                                                                      Alarm ID

                                                                      +

                                                                      Alarm Severity

                                                                      +

                                                                      Auto Cleared

                                                                      +

                                                                      50407

                                                                      +

                                                                      Critical

                                                                      +

                                                                      Yes

                                                                      +
                                                                      +
                                                                      +
                                                                      +

                                                                      Alarm Parameters

                                                                      +
                                                                      + + + + + + + + + + + + + + + + +

                                                                      Parameter

                                                                      +

                                                                      Description

                                                                      +

                                                                      Source

                                                                      +

                                                                      Specifies the cluster or system for which the alarm was generated.

                                                                      +

                                                                      ServiceName

                                                                      +

                                                                      Specifies the service for which the alarm was generated.

                                                                      +

                                                                      RoleName

                                                                      +

                                                                      Specifies the role for which the alarm was generated.

                                                                      +

                                                                      HostName

                                                                      +

                                                                      Specifies the host for which the alarm was generated.

                                                                      +
                                                                      +
                                                                      +
                                                                      +

                                                                      Impact on the System

                                                                      A job may fail to be queried, for example, through the REST API.

                                                                      +
                                                                      +

                                                                      Possible Causes

                                                                      The JobServer instance on the node is abnormal.

                                                                      +
                                                                      +

                                                                      Handling Procedure

                                                                      1. On MRS Manager, choose O&M > Alarm > Alarms, expand details of this alarm in the right pane, and obtain HostName of the node for which the alarm is generated in Location.
                                                                      1. On MRS Manager, choose Cluster > Services > JobGateway > Instances.
                                                                      2. Select the instance for which the alarm is generated, click More, and select Instance Rolling Restart.

                                                                        Services may be affected or interrupted during the restart. You are advised to perform the restart during off-peak hours.

                                                                        +
                                                                        +

                                                                      3. Check whether the instance running status is normal after the restart.

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

                                                                      4. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

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

                                                                      +

                                                                      Collect fault information.

                                                                      +
                                                                      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 JobGateway 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.
                                                                      1. Contact O&M personnel and provide the collected logs.
                                                                      +
                                                                      +

                                                                      Alarm Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      +
                                                                      +

                                                                      Related Information

                                                                      None.

                                                                      +
                                                                      +
                                                                      + + diff --git a/docs/mrs/umn/ALM-50408.html b/docs/mrs/umn/ALM-50408.html new file mode 100644 index 000000000..6345fb203 --- /dev/null +++ b/docs/mrs/umn/ALM-50408.html @@ -0,0 +1,82 @@ + + +

                                                                      ALM-50408 Failure Rate of the JobServer Job Termination API Exceeds the Threshold

                                                                      +

                                                                      This section is available for MRS 3.5.0-LTS or later version only.

                                                                      +
                                                                      +

                                                                      Alarm Description

                                                                      The system checks the failure rate of the JobServer job termination API every 30 seconds. This alarm is generated when the failure rate exceeds the threshold (80% by default).

                                                                      +

                                                                      This alarm is cleared when the failure rate falls below the threshold.

                                                                      +
                                                                      +

                                                                      Alarm Attributes

                                                                      +
                                                                      + + + + + + + + + +

                                                                      Alarm ID

                                                                      +

                                                                      Alarm Severity

                                                                      +

                                                                      Auto Cleared

                                                                      +

                                                                      50408

                                                                      +

                                                                      Critical

                                                                      +

                                                                      Yes

                                                                      +
                                                                      +
                                                                      +
                                                                      +

                                                                      Alarm Parameters

                                                                      +
                                                                      + + + + + + + + + + + + + + + + +

                                                                      Parameter

                                                                      +

                                                                      Description

                                                                      +

                                                                      Source

                                                                      +

                                                                      Specifies the cluster or system for which the alarm was generated.

                                                                      +

                                                                      ServiceName

                                                                      +

                                                                      Specifies the service for which the alarm was generated.

                                                                      +

                                                                      RoleName

                                                                      +

                                                                      Specifies the role for which the alarm was generated.

                                                                      +

                                                                      HostName

                                                                      +

                                                                      Specifies the host for which the alarm was generated.

                                                                      +
                                                                      +
                                                                      +
                                                                      +

                                                                      Impact on the System

                                                                      A job may fail to be terminated, for example, through the REST API.

                                                                      +
                                                                      +

                                                                      Possible Causes

                                                                      The JobServer instance on the node is abnormal.

                                                                      +
                                                                      +

                                                                      Handling Procedure

                                                                      1. On MRS Manager, choose O&M > Alarm > Alarms, expand details of this alarm in the right pane, and obtain HostName of the node for which the alarm is generated in Location.
                                                                      1. On MRS Manager, choose Cluster > Services > JobGateway > Instances.
                                                                      2. Select the instance for which the alarm is generated, click More, and select Instance Rolling Restart.

                                                                        Services may be affected or interrupted during the restart. You are advised to perform the restart during off-peak hours.

                                                                        +
                                                                        +

                                                                      3. Check whether the instance running status is normal after the restart.

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

                                                                      4. Choose O&M > Alarm > Alarms and check whether the alarm is cleared.

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

                                                                      +

                                                                      Collect fault information.

                                                                      +
                                                                      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 JobGateway 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.
                                                                      1. Contact O&M personnel and provide the collected logs.
                                                                      +
                                                                      +

                                                                      Alarm Clearance

                                                                      This alarm is automatically cleared after the fault is rectified.

                                                                      +
                                                                      +

                                                                      Related Information

                                                                      None.

                                                                      +
                                                                      +
                                                                      + + diff --git a/docs/mrs/umn/CLASS.TXT.json b/docs/mrs/umn/CLASS.TXT.json index 2da8bc0bd..65440f0f0 100644 --- a/docs/mrs/umn/CLASS.TXT.json +++ b/docs/mrs/umn/CLASS.TXT.json @@ -130,7 +130,7 @@ "product_code":"mrs", "title":"ApacheDoris", "uri":"mrs_08_0161.html", - "doc_type":"productdesc", + "doc_type":"usermanual", "p_code":"4", "code":"15" }, @@ -139,7 +139,7 @@ "product_code":"mrs", "title":"Basic Principles", "uri":"mrs_08_0162.html", - "doc_type":"productdesc", + "doc_type":"usermanual", "p_code":"15", "code":"16" }, @@ -148,7 +148,7 @@ "product_code":"mrs", "title":"Relationship with Other Components", "uri":"mrs_08_0163.html", - "doc_type":"productdesc", + "doc_type":"usermanual", "p_code":"15", "code":"17" }, @@ -271,10 +271,10 @@ }, { "desc":"Guardian is a service that provides temporary authentication credentials for services such as HDFS, Hive, Spark, HBase, Loader and HetuEngine to access OBS in decoupled s", - "product_code":"", + "product_code":"mrs", "title":"Guardian", "uri":"mrs_08_0159.html", - "doc_type":"", + "doc_type":"usermanual", "p_code":"4", "code":"31" }, @@ -485,6 +485,15 @@ "p_code":"51", "code":"54" }, + { + "desc":"Impala provides fast, interactive SQL queries directly on your Apache Hadoop data stored in HDFS, HBase, or the Object Storage Service (OBS). In addition to using the sam", + "product_code":"mrs", + "title":"Impala", + "uri":"mrs_08_0038.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"55" + }, { "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", @@ -492,7 +501,7 @@ "uri":"mrs_08_0093.html", "doc_type":"usermanual", "p_code":"4", - "code":"55" + "code":"56" }, { "desc":"Database for Internet of Things (IoTDB) is a software system that collects, stores, manages, and analyzes IoT time series data. Apache IoTDB uses a lightweight architectu", @@ -500,8 +509,8 @@ "title":"IoTDB Basic Principles", "uri":"mrs_08_0094.html", "doc_type":"usermanual", - "p_code":"55", - "code":"56" + "p_code":"56", + "code":"57" }, { "desc":"The IoTDB stores data locally, so it does not depend on any other component for storage. However, in a security cluster environment, IoTDB depends on the KrbServer compon", @@ -509,8 +518,8 @@ "title":"Relationship Between IoTDB and Other Components", "uri":"mrs_08_0095.html", "doc_type":"usermanual", - "p_code":"55", - "code":"57" + "p_code":"56", + "code":"58" }, { "desc":"Visualized O&M covers installation, uninstallation, one-click start and stop, configurations, clients, monitoring, alarms, health checks, and logs.Visualized permission m", @@ -518,35 +527,35 @@ "title":"IoTDB Enhanced Open Source Features", "uri":"mrs_08_0096.html", "doc_type":"usermanual", - "p_code":"55", - "code":"58" - }, - { - "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":"JobGateway", - "uri":"mrs_08_0149.html", - "doc_type":"", - "p_code":"4", + "p_code":"56", "code":"59" }, { - "desc":"JobGateway allows you to submit jobs through REST APIs.As a gateway component for submitting big data jobs, JobGateway provides fully controllable enterprise-level big da", - "product_code":"", - "title":"JobGateway Basic Principles", - "uri":"mrs_08_0150.html", - "doc_type":"", - "p_code":"59", + "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":"JobGateway", + "uri":"mrs_08_0149.html", + "doc_type":"usermanual", + "p_code":"4", "code":"60" }, + { + "desc":"JobGateway allows you to submit jobs through REST APIs.As a gateway component for submitting big data jobs, JobGateway provides fully controllable enterprise-level big da", + "product_code":"mrs", + "title":"JobGateway Basic Principles", + "uri":"mrs_08_0150.html", + "doc_type":"usermanual", + "p_code":"60", + "code":"61" + }, { "desc":"JobGateway is a service that allows you to submit Spark, Hive, MapReduce, and Flink jobs through REST APIs.", - "product_code":"", + "product_code":"mrs", "title":"Relationships Between JobGateway and Other Components", "uri":"mrs_08_0152.html", - "doc_type":"", - "p_code":"59", - "code":"61" + "doc_type":"usermanual", + "p_code":"60", + "code":"62" }, { "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.", @@ -555,7 +564,7 @@ "uri":"mrs_08_0013.html", "doc_type":"usermanual", "p_code":"4", - "code":"62" + "code":"63" }, { "desc":"Kafka is an open source, distributed, partitioned, and replicated commit log service. Kafka is publish-subscribe messaging, rethought as a distributed commit log. It prov", @@ -563,17 +572,17 @@ "title":"Kafka Basic Principles", "uri":"mrs_08_00131.html", "doc_type":"usermanual", - "p_code":"62", - "code":"63" + "p_code":"63", + "code":"64" }, { - "desc":"As a message publishing and subscription system, Kafka provides high-speed data transmission methods for data transmission between different subsystems of the FusionInsig", + "desc":"As a message publishing and subscription system, Kafka provides high-speed data transmission methods for data transmission between different subsystems of the platform. I", "product_code":"mrs", "title":"Relationship Between Kafka and Other Components", "uri":"mrs_08_00132.html", "doc_type":"usermanual", - "p_code":"62", - "code":"64" + "p_code":"63", + "code":"65" }, { "desc":"Monitors the following topic-level metrics:Topic Input TrafficTopic Output TrafficTopic Rejected TrafficNumber of Failed Fetch Requests Per SecondNumber of Failed Produce", @@ -581,8 +590,8 @@ "title":"Kafka Enhanced Open Source Features", "uri":"mrs_08_00133.html", "doc_type":"usermanual", - "p_code":"62", - "code":"65" + "p_code":"63", + "code":"66" }, { "desc":"KafkaManager is a tool for managing Apache Kafka and provides GUI-based metric monitoring and management of Kafka clusters.KafkaManager supports the following operations:", @@ -591,7 +600,7 @@ "uri":"mrs_08_0032.html", "doc_type":"usermanual", "p_code":"4", - "code":"66" + "code":"67" }, { "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.", @@ -600,7 +609,7 @@ "uri":"mrs_08_0064.html", "doc_type":"usermanual", "p_code":"4", - "code":"67" + "code":"68" }, { "desc":"To manage the access control permissions on data and resources in a cluster, it is recommended that the cluster be installed in security mode. In security mode, a client ", @@ -608,8 +617,8 @@ "title":"KrbServer and LdapServer Principles", "uri":"mrs_08_00641.html", "doc_type":"usermanual", - "p_code":"67", - "code":"68" + "p_code":"68", + "code":"69" }, { "desc":"In an MRS cluster that uses the security mode, mutual access between services is implemented based on the Kerberos security architecture. When a service (such as HDFS) in", @@ -617,8 +626,17 @@ "title":"KrbServer and LdapServer Enhanced Open Source Features", "uri":"mrs_08_00642.html", "doc_type":"usermanual", - "p_code":"67", - "code":"69" + "p_code":"68", + "code":"70" + }, + { + "desc":"Kudu is a column-store manager developed for the Apache Hadoop platform. Kudu shares the common technical properties of Hadoop ecosystem applications, that is, it runs on", + "product_code":"mrs", + "title":"Kudu", + "uri":"mrs_08_0039.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"71" }, { "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.", @@ -627,7 +645,7 @@ "uri":"mrs_08_0017.html", "doc_type":"usermanual", "p_code":"4", - "code":"70" + "code":"72" }, { "desc":"Loader is developed based on the open source Sqoop component. It is used to exchange data and files between MRS and relational databases and file systems. Loader can impo", @@ -635,8 +653,8 @@ "title":"Loader Basic Principles", "uri":"mrs_08_00171.html", "doc_type":"usermanual", - "p_code":"70", - "code":"71" + "p_code":"72", + "code":"73" }, { "desc":"The components that interact with Loader include HDFS, HBase, MapReduce, and ZooKeeper. Loader works as a client to use certain functions of these components, such as sto", @@ -644,8 +662,8 @@ "title":"Relationship Between Loader and Other Components", "uri":"mrs_08_00172.html", "doc_type":"usermanual", - "p_code":"70", - "code":"72" + "p_code":"72", + "code":"74" }, { "desc":"Loader is developed based on Sqoop. In addition to the Sqoop functions, Loader has the following enhanced features:Provides data conversion functions.Supports GUI-based c", @@ -653,8 +671,8 @@ "title":"Loader Enhanced Open Source Features", "uri":"mrs_08_00173.html", "doc_type":"usermanual", - "p_code":"70", - "code":"73" + "p_code":"72", + "code":"75" }, { "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.", @@ -663,7 +681,7 @@ "uri":"mrs_08_0066.html", "doc_type":"usermanual", "p_code":"4", - "code":"74" + "code":"76" }, { "desc":"Manager is the O&M management system of MRS and provides unified cluster management capabilities for services deployed in clusters.Manager provides functions such as perf", @@ -671,8 +689,8 @@ "title":"Manager Basic Principles", "uri":"mrs_08_00661.html", "doc_type":"usermanual", - "p_code":"74", - "code":"75" + "p_code":"76", + "code":"77" }, { "desc":"Manager provides the visualized and convenient alarm monitoring function. Users can quickly obtain key cluster performance indicators, evaluate cluster health status, cus", @@ -680,8 +698,8 @@ "title":"Manager Key Features", "uri":"mrs_08_00662.html", "doc_type":"usermanual", - "p_code":"74", - "code":"76" + "p_code":"76", + "code":"78" }, { "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.", @@ -690,7 +708,7 @@ "uri":"mrs_08_0050.html", "doc_type":"usermanual", "p_code":"4", - "code":"77" + "code":"79" }, { "desc":"MapReduce is the core of Hadoop. As a software architecture proposed by Google, MapReduce is used for parallel computing of large-scale datasets (larger than 1 TB). The c", @@ -698,8 +716,8 @@ "title":"MapReduce Basic Principles", "uri":"mrs_08_00501.html", "doc_type":"usermanual", - "p_code":"77", - "code":"78" + "p_code":"79", + "code":"80" }, { "desc":"HDFS features high fault tolerance and high throughput, and can be deployed on low-cost hardware for storing data of applications with massive data sets.MapReduce is a pr", @@ -707,8 +725,8 @@ "title":"Relationship Between MapReduce and Other Components", "uri":"mrs_08_00502.html", "doc_type":"usermanual", - "p_code":"77", - "code":"79" + "p_code":"79", + "code":"81" }, { "desc":"JobHistoryServer (JHS) is the server used to view historical MapReduce task information. Currently, the open source JHS supports only single-instance services. JHS HA can", @@ -716,8 +734,35 @@ "title":"MapReduce Enhanced Open Source Features", "uri":"mrs_08_00503.html", "doc_type":"usermanual", - "p_code":"77", - "code":"80" + "p_code":"79", + "code":"82" + }, + { + "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":"MemArtsCC", + "uri":"mrs_08_0116.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"83" + }, + { + "desc":"MemArtsCC is a distributed lightweight caching system deployed on the compute side in the storage-compute decoupled architecture. It prefetches data from remote object st", + "product_code":"mrs", + "title":"MemArtsCC Basic Principles", + "uri":"mrs_08_0117.html", + "doc_type":"usermanual", + "p_code":"83", + "code":"84" + }, + { + "desc":"OBS provides a new InputStream: OBSMemArtsCCInputStream. This InputStream reads data from the MemArtsCC cluster deployed on the compute side to reduce OBS server pressure", + "product_code":"mrs", + "title":"Relationships Between MemArtsCC and Other Components", + "uri":"mrs_08_0118.html", + "doc_type":"usermanual", + "p_code":"83", + "code":"85" }, { "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.", @@ -726,7 +771,7 @@ "uri":"mrs_08_0067.html", "doc_type":"usermanual", "p_code":"4", - "code":"81" + "code":"86" }, { "desc":"Oozie is an open-source workflow engine that is used to schedule and coordinate Hadoop jobs.The Oozie engine is a web application integrated into Tomcat by default. Oozie", @@ -734,8 +779,8 @@ "title":"Oozie Basic Principles", "uri":"mrs_08_00671.html", "doc_type":"usermanual", - "p_code":"81", - "code":"82" + "p_code":"86", + "code":"87" }, { "desc":"Provides roles of administrator and common users to support Oozie permission management.Supports single sign-on and sign-out, HTTPS access, and audit logs.", @@ -743,8 +788,8 @@ "title":"Oozie Enhanced Open Source Features", "uri":"mrs_08_00672.html", "doc_type":"usermanual", - "p_code":"81", - "code":"83" + "p_code":"86", + "code":"88" }, { "desc":"OpenTSDB is a distributed, scalable time series database based on HBase. OpenTSDB is designed to collect monitoring information of a large-scale cluster and implement sec", @@ -753,7 +798,7 @@ "uri":"mrs_08_0035.html", "doc_type":"usermanual", "p_code":"4", - "code":"84" + "code":"89" }, { "desc":"Presto is an open source SQL query engine for running interactive analytic queries against data sources of all sizes. It applies to massive structured/semi-structured dat", @@ -762,7 +807,7 @@ "uri":"mrs_08_0031.html", "doc_type":"usermanual", "p_code":"4", - "code":"85" + "code":"90" }, { "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.", @@ -771,7 +816,7 @@ "uri":"mrs_08_0041.html", "doc_type":"usermanual", "p_code":"4", - "code":"86" + "code":"91" }, { "desc":"Apache Ranger offers a centralized security management framework and supports unified authorization and auditing. It manages fine grained access control over Hadoop and r", @@ -779,8 +824,8 @@ "title":"Ranger Basic Principles", "uri":"mrs_08_00411.html", "doc_type":"usermanual", - "p_code":"86", - "code":"87" + "p_code":"91", + "code":"92" }, { "desc":"Ranger provides PABC-based authentication plug-ins for components to run on their servers. Ranger currently supports authentication for the following components like HDFS", @@ -788,8 +833,8 @@ "title":"Relationship Between Ranger and Other Components", "uri":"mrs_08_004102.html", "doc_type":"usermanual", - "p_code":"86", - "code":"88" + "p_code":"91", + "code":"93" }, { "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.", @@ -798,7 +843,7 @@ "uri":"mrs_08_0008.html", "doc_type":"usermanual", "p_code":"4", - "code":"89" + "code":"94" }, { "desc":"The Spark component applies to versions earlier than MRS 3.x.Spark is an open source parallel data processing framework. It helps you easily develop unified big data appl", @@ -806,8 +851,8 @@ "title":"Basic Principles of Spark", "uri":"mrs_08_00081.html", "doc_type":"usermanual", - "p_code":"89", - "code":"90" + "p_code":"94", + "code":"95" }, { "desc":"Based on existing JDBCServer in the community, multi-active-instance mode is used to achieve HA. In this mode, multiple JDBCServers coexist in the cluster and the client ", @@ -815,8 +860,8 @@ "title":"Spark HA Solution", "uri":"mrs_08_00082.html", "doc_type":"usermanual", - "p_code":"89", - "code":"91" + "p_code":"94", + "code":"96" }, { "desc":"Data computed by Spark comes from multiple data sources, such as local files and HDFS. Most data computed by Spark comes from the HDFS. The HDFS can read data in large sc", @@ -824,8 +869,8 @@ "title":"Relationship Among Spark, HDFS, and Yarn", "uri":"mrs_08_00083.html", "doc_type":"usermanual", - "p_code":"89", - "code":"92" + "p_code":"94", + "code":"97" }, { "desc":"Enterprises usually store massive data, such as from various databases and warehouses, for management and information collection. However, diversified data sources, hybri", @@ -833,8 +878,8 @@ "title":"Spark Enhanced Open Source Feature: Optimized SQL Query of Cross-Source Data", "uri":"mrs_08_00084.html", "doc_type":"usermanual", - "p_code":"89", - "code":"93" + "p_code":"94", + "code":"98" }, { "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.", @@ -843,7 +888,7 @@ "uri":"mrs_08_0071.html", "doc_type":"usermanual", "p_code":"4", - "code":"94" + "code":"99" }, { "desc":"The Spark2x component applies to MRS 3.x and later versions.Spark is a memory-based distributed computing framework. In iterative computation scenarios, the computing cap", @@ -851,8 +896,8 @@ "title":"Basic Principles of Spark2x", "uri":"mrs_08_007101.html", "doc_type":"usermanual", - "p_code":"94", - "code":"95" + "p_code":"99", + "code":"100" }, { "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.", @@ -860,8 +905,8 @@ "title":"Spark2x HA Solution", "uri":"mrs_08_007102.html", "doc_type":"usermanual", - "p_code":"94", - "code":"96" + "p_code":"99", + "code":"101" }, { "desc":"Based on existing JDBCServers in the community, multi-active-instance HA is used to achieve the high availability. In this mode, multiple JDBCServers coexist in the clust", @@ -869,8 +914,8 @@ "title":"Spark2x Multi-active Instance", "uri":"mrs_08_007103.html", "doc_type":"usermanual", - "p_code":"96", - "code":"97" + "p_code":"101", + "code":"102" }, { "desc":"In the JDBCServer multi-active instance mode, JDBCServer implements the Yarn-client mode but only one Yarn resource queue is available. To solve the resource limitation p", @@ -878,8 +923,8 @@ "title":"Spark2x Multi-tenant", "uri":"mrs_08_007104.html", "doc_type":"usermanual", - "p_code":"96", - "code":"98" + "p_code":"101", + "code":"103" }, { "desc":"Data computed by Spark comes from multiple data sources, such as local files and HDFS. Most data comes from HDFS which can read data in large scale for parallel computing", @@ -887,8 +932,8 @@ "title":"Relationship Between Spark2x and Other Components", "uri":"mrs_08_007105.html", "doc_type":"usermanual", - "p_code":"94", - "code":"99" + "p_code":"99", + "code":"104" }, { "desc":"Compared with Spark 1.5, Spark2x has some new open-source features. The specific features or concepts are as follows:DataSet: For details, see SparkSQL and DataSet Princi", @@ -896,8 +941,8 @@ "title":"Spark2x Open Source New Features", "uri":"mrs_08_007106.html", "doc_type":"usermanual", - "p_code":"94", - "code":"100" + "p_code":"99", + "code":"105" }, { "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.", @@ -905,8 +950,8 @@ "title":"Spark2x Enhanced Open Source Features", "uri":"mrs_08_007107.html", "doc_type":"usermanual", - "p_code":"94", - "code":"101" + "p_code":"99", + "code":"106" }, { "desc":"CarbonData is a new Apache Hadoop native data-store format. CarbonData allows faster interactive queries over PetaBytes of data using advanced columnar storage, index, co", @@ -914,8 +959,8 @@ "title":"CarbonData Overview", "uri":"mrs_08_007108.html", "doc_type":"usermanual", - "p_code":"101", - "code":"102" + "p_code":"106", + "code":"107" }, { "desc":"Enterprises usually store massive data, such as from various databases and warehouses, for management and information collection. However, diversified data sources, hybri", @@ -923,8 +968,8 @@ "title":"Optimizing SQL Query of Data of Multiple Sources", "uri":"mrs_08_007109.html", "doc_type":"usermanual", - "p_code":"101", - "code":"103" + "p_code":"106", + "code":"108" }, { "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.", @@ -933,7 +978,7 @@ "uri":"mrs_08_0014.html", "doc_type":"usermanual", "p_code":"4", - "code":"104" + "code":"109" }, { "desc":"Apache Storm is a distributed, reliable, and fault-tolerant real-time stream data processing system. In Storm, a graph-shaped data structure called topology needs to be d", @@ -941,8 +986,8 @@ "title":"Storm Basic Principles", "uri":"mrs_08_00141.html", "doc_type":"usermanual", - "p_code":"104", - "code":"105" + "p_code":"109", + "code":"110" }, { "desc":"Storm provides a real-time distributed computing framework. It can obtain real-time messages from data sources (such as Kafka and TCP connection), perform high-throughput", @@ -950,8 +995,8 @@ "title":"Relationship Between Storm and Other Components", "uri":"mrs_08_00142.html", "doc_type":"usermanual", - "p_code":"104", - "code":"106" + "p_code":"109", + "code":"111" }, { "desc":"CQLContinuous Query Language (CQL) is an SQL-like language used for real-time stream processing. Compared with SQL, CQL has introduced the concept of (time-sequencing) wi", @@ -959,8 +1004,8 @@ "title":"Storm Enhanced Open Source Features", "uri":"mrs_08_00143.html", "doc_type":"usermanual", - "p_code":"104", - "code":"107" + "p_code":"109", + "code":"112" }, { "desc":"Tez is Apache's latest open source computing framework that supports Directed Acyclic Graph (DAG) jobs. It can convert multiple dependent jobs into one job, greatly impro", @@ -969,7 +1014,7 @@ "uri":"mrs_08_0030.html", "doc_type":"usermanual", "p_code":"4", - "code":"108" + "code":"113" }, { "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.", @@ -978,7 +1023,7 @@ "uri":"mrs_08_0051.html", "doc_type":"usermanual", "p_code":"4", - "code":"109" + "code":"114" }, { "desc":"The Apache open source community introduces the unified resource management framework Yarn to share Hadoop clusters, improve their scalability and reliability, and elimin", @@ -986,8 +1031,8 @@ "title":"Yarn Basic Principles", "uri":"mrs_08_00511.html", "doc_type":"usermanual", - "p_code":"109", - "code":"110" + "p_code":"114", + "code":"115" }, { "desc":"ResourceManager in Yarn manages resources and schedules tasks in the cluster. In versions earlier than Hadoop 2.4, SPOFs may occur on ResourceManager in the Yarn cluster.", @@ -995,8 +1040,8 @@ "title":"Yarn HA Solution", "uri":"mrs_08_00512.html", "doc_type":"usermanual", - "p_code":"109", - "code":"111" + "p_code":"114", + "code":"116" }, { "desc":"The Spark computing and scheduling can be implemented using YARN mode. Spark enjoys the compute resources provided by YARN clusters and runs tasks in a distributed way. S", @@ -1004,8 +1049,8 @@ "title":"Relationship Between YARN and Other Components", "uri":"mrs_08_00513.html", "doc_type":"usermanual", - "p_code":"109", - "code":"112" + "p_code":"114", + "code":"117" }, { "desc":"In the native Yarn resource scheduling mechanism, if the whole Hadoop cluster resources are occupied by those MapReduce jobs submitted earlier, jobs submitted later will ", @@ -1013,8 +1058,8 @@ "title":"Yarn Enhanced Open Source Features", "uri":"mrs_08_00514.html", "doc_type":"usermanual", - "p_code":"109", - "code":"113" + "p_code":"114", + "code":"118" }, { "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.", @@ -1023,7 +1068,7 @@ "uri":"mrs_08_0070.html", "doc_type":"usermanual", "p_code":"4", - "code":"114" + "code":"119" }, { "desc":"ZooKeeper is a distributed, highly available coordination service. ZooKeeper provides two functions:Prevents the system from single point of failures (SPOFs) and provides", @@ -1031,8 +1076,8 @@ "title":"ZooKeeper Basic Principle", "uri":"mrs_08_00701.html", "doc_type":"usermanual", - "p_code":"114", - "code":"115" + "p_code":"119", + "code":"120" }, { "desc":"Figure 1 shows the relationship between ZooKeeper and HDFS.As the client of a ZooKeeper cluster, ZKFailoverController (ZKFC) monitors the status of NameNode. ZKFC is depl", @@ -1040,8 +1085,8 @@ "title":"Relationship Between ZooKeeper and Other Components", "uri":"mrs_08_00702.html", "doc_type":"usermanual", - "p_code":"114", - "code":"116" + "p_code":"119", + "code":"121" }, { "desc":"In security mode, an ephemeral node is deleted as long as the session that created the node expires. Ephemeral node deletion is recorded in audit logs so that ephemeral n", @@ -1049,8 +1094,8 @@ "title":"ZooKeeper Enhanced Open Source Features", "uri":"mrs_08_00703.html", "doc_type":"usermanual", - "p_code":"114", - "code":"117" + "p_code":"119", + "code":"122" }, { "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.", @@ -1059,7 +1104,7 @@ "uri":"mrs_08_0006.html", "doc_type":"usermanual", "p_code":"1", - "code":"118" + "code":"123" }, { "desc":"Modern enterprises' data clusters are developing towards centralization and cloudification. Enterprise-class big data clusters must meet the following requirements:Carry ", @@ -1067,8 +1112,8 @@ "title":"Multi-tenant", "uri":"mrs_08_0042.html", "doc_type":"usermanual", - "p_code":"118", - "code":"119" + "p_code":"123", + "code":"124" }, { "desc":"MRS is a platform for massive data management and analysis and has high security. MRS protects user data and service running from the following aspects:Network isolationT", @@ -1076,8 +1121,8 @@ "title":"Security Hardening", "uri":"mrs_08_0043.html", "doc_type":"usermanual", - "p_code":"118", - "code":"120" + "p_code":"123", + "code":"125" }, { "desc":"Big data components have their own web UIs to manage their own systems. However, you cannot easily access the web UIs due to network isolation. For example, to access the", @@ -1085,8 +1130,8 @@ "title":"Easy Access to Web UIs of Components", "uri":"mrs_08_0044.html", "doc_type":"usermanual", - "p_code":"118", - "code":"121" + "p_code":"123", + "code":"126" }, { "desc":"Based on Apache Hadoop open source software, MRS optimizes and improves the reliability and performance of main service components.HA for all management nodesIn the Hadoo", @@ -1094,8 +1139,8 @@ "title":"Reliability Enhancement", "uri":"mrs_08_0045.html", "doc_type":"usermanual", - "p_code":"118", - "code":"122" + "p_code":"123", + "code":"127" }, { "desc":"The job management function provides an entry for you to submit jobs in a cluster, including MapReduce, Spark, HiveQL, and SparkSQL jobs. MRS works with Data Lake Governa", @@ -1103,8 +1148,8 @@ "title":"Job Management", "uri":"mrs_08_0046.html", "doc_type":"usermanual", - "p_code":"118", - "code":"123" + "p_code":"123", + "code":"128" }, { "desc":"MRS provides standard elastic big data clusters on the cloud. Nine big data components, such as Hadoop and Spark, can be installed and deployed. Currently, standard cloud", @@ -1112,8 +1157,8 @@ "title":"Bootstrap Actions", "uri":"mrs_08_0025.html", "doc_type":"usermanual", - "p_code":"118", - "code":"124" + "p_code":"123", + "code":"129" }, { "desc":"MRS provides multiple metadata storage methods. When deploying Hive and Ranger during MRS cluster creation, select one of the following storage modes as required:Local: M", @@ -1121,8 +1166,8 @@ "title":"Metadata", "uri":"mrs_08_0075.html", "doc_type":"usermanual", - "p_code":"118", - "code":"125" + "p_code":"123", + "code":"130" }, { "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.", @@ -1130,8 +1175,8 @@ "title":"Cluster Management", "uri":"mrs_08_0048.html", "doc_type":"usermanual", - "p_code":"118", - "code":"126" + "p_code":"123", + "code":"131" }, { "desc":"MRS supports cluster lifecycle management, including creating and terminating clusters.Creating a cluster: After you specify a cluster type, components, number of nodes o", @@ -1139,8 +1184,8 @@ "title":"Cluster Lifecycle Management", "uri":"mrs_08_0053.html", "doc_type":"usermanual", - "p_code":"126", - "code":"127" + "p_code":"131", + "code":"132" }, { "desc":"The processing capability of a big data cluster can be horizontally expanded by adding nodes. If the cluster scale does not meet service requirements, you can manually sc", @@ -1148,8 +1193,8 @@ "title":"Manually Scale Out/In a Cluster", "uri":"mrs_08_0054.html", "doc_type":"usermanual", - "p_code":"126", - "code":"128" + "p_code":"131", + "code":"133" }, { "desc":"More and more enterprises use technologies such as Spark and Hive to analyze data. Processing a large amount of data consumes huge resources and costs much. Typically, en", @@ -1157,8 +1202,8 @@ "title":"Auto Scaling", "uri":"mrs_08_0022.html", "doc_type":"usermanual", - "p_code":"126", - "code":"129" + "p_code":"131", + "code":"134" }, { "desc":"Task nodes can be created and used for computing only. They do not store persistent data and are the basis for implementing auto scaling.When MRS is used only as a comput", @@ -1166,8 +1211,8 @@ "title":"Task Node Creation", "uri":"mrs_08_0023.html", "doc_type":"usermanual", - "p_code":"126", - "code":"130" + "p_code":"131", + "code":"135" }, { "desc":"When detecting that a host is abnormal or faulty and cannot provide services or affects cluster performance, you can exclude the host from the available nodes in the clus", @@ -1175,8 +1220,8 @@ "title":"Isolating a Host", "uri":"mrs_08_0056.html", "doc_type":"usermanual", - "p_code":"126", - "code":"131" + "p_code":"131", + "code":"136" }, { "desc":"Tags are cluster identifiers. Adding tags to clusters can help you identify and manage your cluster resources. By associating with Tag Management Service (TMS), MRS allow", @@ -1184,8 +1229,8 @@ "title":"Managing Tags", "uri":"mrs_08_0057.html", "doc_type":"usermanual", - "p_code":"126", - "code":"132" + "p_code":"131", + "code":"137" }, { "desc":"MRS can monitor big data clusters in real time and identify system health status based on alarms and events. In addition, MRS allows you to customize monitoring and alarm", @@ -1193,8 +1238,8 @@ "title":"Cluster O&M", "uri":"mrs_08_0049.html", "doc_type":"usermanual", - "p_code":"118", - "code":"133" + "p_code":"123", + "code":"138" }, { "desc":"The following operations are often performed during the running of a big data cluster:Big data clusters often change, for example, cluster scale-out and scale-in.When a s", @@ -1202,8 +1247,8 @@ "title":"Message Notification", "uri":"mrs_08_0024.html", "doc_type":"usermanual", - "p_code":"118", - "code":"134" + "p_code":"123", + "code":"139" }, { "desc":"Before using MRS, ensure that you have read and understand the following restrictions.MRS clusters must be created in VPC subnets.You are advised to use any of the follow", @@ -1212,7 +1257,7 @@ "uri":"mrs_08_0027.html", "doc_type":"usermanual", "p_code":"1", - "code":"135" + "code":"140" }, { "desc":"After you enable CTS, the system starts recording operations on cloud resources. You can view operation records of the last 7 days on the CTS management console. For deta", @@ -1221,7 +1266,7 @@ "uri":"mrs_08_0026.html", "doc_type":"usermanual", "p_code":"1", - "code":"136" + "code":"141" }, { "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.", @@ -1230,7 +1275,7 @@ "uri":"mrs_01_0452.html", "doc_type":"usermanual", "p_code":"", - "code":"137" + "code":"142" }, { "desc":"Use IAM to implement fine-grained permission control over your MRS. With IAM, you can:Create IAM users under your cloud account for employees based on your enterprise's o", @@ -1238,8 +1283,8 @@ "title":"Creating an MRS User", "uri":"mrs_01_0453.html", "doc_type":"usermanual", - "p_code":"137", - "code":"138" + "p_code":"142", + "code":"143" }, { "desc":"Custom policies can be created to supplement the system-defined policies of MRS. For the actions that can be added to custom policies, see Permissions Policies and Suppor", @@ -1247,8 +1292,8 @@ "title":"Creating a Custom Policy", "uri":"mrs_01_0455.html", "doc_type":"usermanual", - "p_code":"137", - "code":"139" + "p_code":"142", + "code":"144" }, { "desc":"IAM user synchronization is to synchronize IAM users bound with MRS policies to the MRS system and create accounts with the same usernames but different passwords as the ", @@ -1256,8 +1301,8 @@ "title":"Synchronizing IAM Users to MRS", "uri":"mrs_01_0495.html", "doc_type":"usermanual", - "p_code":"137", - "code":"140" + "p_code":"142", + "code":"145" }, { "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.", @@ -1266,7 +1311,7 @@ "uri":"mrs_01_0024.html", "doc_type":"usermanual", "p_code":"", - "code":"141" + "code":"146" }, { "desc":"MapReduce Service (MRS) is a cloud service that is used to deploy and manage the Hadoop system and enables one-click Hadoop cluster deployment. MRS provides enterprise-le", @@ -1274,8 +1319,8 @@ "title":"How to Use MRS", "uri":"mrs_01_0511.html", "doc_type":"usermanual", - "p_code":"141", - "code":"142" + "p_code":"146", + "code":"147" }, { "desc":"The first step of using MRS is to create a cluster. This section describes how to create a cluster on the MRS management console.When creating a cluster, pay attention to", @@ -1283,8 +1328,8 @@ "title":"Creating a Cluster", "uri":"mrs_01_0027.html", "doc_type":"usermanual", - "p_code":"141", - "code":"143" + "p_code":"146", + "code":"148" }, { "desc":"Through the Files tab page, you can create, delete, import, export, delete files in the analysis cluster.MRS clusters process data from OBS or HDFS. OBS provides customer", @@ -1292,8 +1337,8 @@ "title":"Uploading Data and Programs", "uri":"mrs_01_0028.html", "doc_type":"usermanual", - "p_code":"141", - "code":"144" + "p_code":"146", + "code":"149" }, { "desc":"You can submit programs developed by yourself to MRS to execute them, and obtain the results.This section describes how to submit a job (take a MapReduce job as an exampl", @@ -1301,17 +1346,17 @@ "title":"Creating a Job", "uri":"mrs_01_0029.html", "doc_type":"usermanual", - "p_code":"141", - "code":"145" + "p_code":"146", + "code":"150" }, { "desc":"This section instructs you to use security clusters and run MapReduce, Spark, and Hive programs.The Presto component of MRS 3.x does not support Kerberos authentication.Y", "product_code":"mrs", "title":"Using Clusters with Kerberos Authentication Enabled", "uri":"mrs_09_0003.html", - "doc_type":"qs", - "p_code":"141", - "code":"146" + "doc_type":"usermanual", + "p_code":"146", + "code":"151" }, { "desc":"You can terminate an MRS cluster that is no longer use after job execution is complete.You can manually terminate a cluster after data analysis is complete or when the cl", @@ -1319,8 +1364,8 @@ "title":"Terminating a Cluster", "uri":"mrs_01_0469.html", "doc_type":"usermanual", - "p_code":"141", - "code":"147" + "p_code":"146", + "code":"152" }, { "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.", @@ -1329,16 +1374,16 @@ "uri":"mrs_01_0030.html", "doc_type":"usermanual", "p_code":"", - "code":"148" + "code":"153" }, { - "desc":"This section describes how to create MRS clusters.Quick Creation of a Hadoop Analysis Cluster: On the Quick Config tab page, you can quickly configure parameters to creat", + "desc":"This section describes how to create MRS clusters.Quickly Creating a Doris Cluster: On the Quick Config tab page, you can quickly configure parameters to create Doris clu", "product_code":"mrs", "title":"Methods of Creating MRS Clusters", "uri":"mrs_01_0025.html", "doc_type":"usermanual", - "p_code":"148", - "code":"149" + "p_code":"153", + "code":"154" }, { "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.", @@ -1346,17 +1391,17 @@ "title":"Quick Creation of a Cluster", "uri":"mrs_01_24297.html", "doc_type":"usermanual", - "p_code":"148", - "code":"150" + "p_code":"153", + "code":"155" }, { "desc":"This section describes how to quickly create a Doris cluster. Doris is a high-performance, real-time analytical database, suitable for report analysis, ad hoc query, and ", - "product_code":"", + "product_code":"mrs", "title":"Quickly Creating a Doris Cluster", "uri":"mrs_01_249283.html", - "doc_type":"", - "p_code":"150", - "code":"151" + "doc_type":"usermanual", + "p_code":"155", + "code":"156" }, { "desc":"This section describes how to quickly create a Hadoop analysis cluster for analyzing and querying vast amounts of data. In the open-source Hadoop ecosystem, Hadoop uses Y", @@ -1364,8 +1409,8 @@ "title":"Quick Creation of a Hadoop Analysis Cluster", "uri":"mrs_01_0512.html", "doc_type":"usermanual", - "p_code":"150", - "code":"152" + "p_code":"155", + "code":"157" }, { "desc":"This section describes how to quickly create an HBase query cluster. The HBase cluster uses Hadoop and HBase components to provide a column-oriented distributed cloud sto", @@ -1373,8 +1418,8 @@ "title":"Quick Creation of an HBase Analysis Cluster", "uri":"mrs_01_0496.html", "doc_type":"usermanual", - "p_code":"150", - "code":"153" + "p_code":"155", + "code":"158" }, { "desc":"This section describes how to quickly create a ClickHouse cluster. ClickHouse is a columnar database management system used for online analysis. It features the ultimate ", @@ -1382,8 +1427,8 @@ "title":"Quick Creation of a ClickHouse Cluster", "uri":"mrs_01_2354.html", "doc_type":"usermanual", - "p_code":"150", - "code":"154" + "p_code":"155", + "code":"159" }, { "desc":"This section describes how to quickly create a real-time analysis cluster. The real-time analysis cluster uses Hadoop, Kafka, Flink, and ClickHouse to collect, analyze, a", @@ -1391,8 +1436,8 @@ "title":"Quick Creation of a Real-time Analysis Cluster", "uri":"mrs_01_2355.html", "doc_type":"usermanual", - "p_code":"150", - "code":"155" + "p_code":"155", + "code":"160" }, { "desc":"The first step of using MRS is to create a cluster. This section describes how to create a cluster on the Custom Config tab of the MRS management console.You can create a", @@ -1400,8 +1445,8 @@ "title":"Creating a Custom Cluster", "uri":"mrs_01_0513.html", "doc_type":"usermanual", - "p_code":"148", - "code":"156" + "p_code":"153", + "code":"161" }, { "desc":"The analysis cluster, streaming cluster, and hybrid cluster provided by MRS use fixed templates to deploy cluster processes. Therefore, you cannot customize service proce", @@ -1409,8 +1454,8 @@ "title":"Creating a Custom Topology Cluster", "uri":"mrs_01_0121.html", "doc_type":"usermanual", - "p_code":"148", - "code":"157" + "p_code":"153", + "code":"162" }, { "desc":"Tags are used to identify clusters/nodes. Adding tags to clusters can help you identify and manage your cluster resources.Cluster tags: You can add up to 10 tags to a clu", @@ -1418,8 +1463,8 @@ "title":"Adding a Tag to a Cluster/Node", "uri":"mrs_01_0048.html", "doc_type":"usermanual", - "p_code":"148", - "code":"158" + "p_code":"153", + "code":"163" }, { "desc":"MRS clusters provision, manage, and use big data components through the management console. Big data components are deployed in a user's VPC. If the MRS management consol", @@ -1427,8 +1472,8 @@ "title":"Communication Security Authorization", "uri":"mrs_01_0786.html", "doc_type":"usermanual", - "p_code":"148", - "code":"159" + "p_code":"153", + "code":"164" }, { "desc":"In big data application scenarios, especially real-time data analysis and processing, the number of cluster nodes needs to be dynamically adjusted according to data volum", @@ -1436,8 +1481,8 @@ "title":"Configuring an Auto Scaling Rule", "uri":"mrs_01_0061.html", "doc_type":"usermanual", - "p_code":"148", - "code":"160" + "p_code":"153", + "code":"165" }, { "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.", @@ -1445,8 +1490,8 @@ "title":"Managing Data Connections", "uri":"mrs_01_24050.html", "doc_type":"usermanual", - "p_code":"148", - "code":"161" + "p_code":"153", + "code":"166" }, { "desc":"MRS data connections are used to manage external source connections used by components in a cluster. For example, if Hive metadata uses an external relational database, a", @@ -1454,8 +1499,8 @@ "title":"Configuring Data Connections", "uri":"mrs_01_0633.html", "doc_type":"usermanual", - "p_code":"161", - "code":"162" + "p_code":"166", + "code":"167" }, { "desc":"Switch the Ranger metadata of the existing cluster to the metadata stored in the RDS database. This operation enables multiple MRS clusters to share the same metadata, an", @@ -1463,8 +1508,8 @@ "title":"Configuring Ranger Data Connections", "uri":"mrs_01_24051.html", "doc_type":"usermanual", - "p_code":"161", - "code":"163" + "p_code":"166", + "code":"168" }, { "desc":"This section describes how to switch the Hive metadata of an active cluster to the metadata stored in a local database or RDS database after you create a cluster. This op", @@ -1472,8 +1517,8 @@ "title":"Configuring a Hive Data Connection", "uri":"mrs_01_24487.html", "doc_type":"usermanual", - "p_code":"161", - "code":"164" + "p_code":"166", + "code":"169" }, { "desc":"This operation applies to clusters earlier than MRS 3.x.The bootstrap action script has been prepared by referring to Preparing the Bootstrap Action Script.After the boot", @@ -1481,8 +1526,8 @@ "title":"Installing Third-Party Software Using Bootstrap Actions", "uri":"mrs_01_0413.html", "doc_type":"usermanual", - "p_code":"148", - "code":"165" + "p_code":"153", + "code":"170" }, { "desc":"This section describes how to view and delete a failed MRS task.If a cluster fails to be created, terminated, scaled out, or scaled in, the Manage Failed Tasks page is di", @@ -1490,8 +1535,8 @@ "title":"Viewing Failed MRS Tasks", "uri":"mrs_01_0043.html", "doc_type":"usermanual", - "p_code":"148", - "code":"166" + "p_code":"153", + "code":"171" }, { "desc":"Choose Clusters > Cluster History and click the name of a target cluster. You can view the cluster configuration and deployed node information.The following table describ", @@ -1499,8 +1544,8 @@ "title":"Viewing Information of a Historical Cluster", "uri":"en-us_topic_0057514383.html", "doc_type":"usermanual", - "p_code":"148", - "code":"167" + "p_code":"153", + "code":"172" }, { "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.", @@ -1509,7 +1554,7 @@ "uri":"mrs_01_0034.html", "doc_type":"usermanual", "p_code":"", - "code":"168" + "code":"173" }, { "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.", @@ -1517,8 +1562,8 @@ "title":"Logging In to a Cluster", "uri":"mrs_01_0082.html", "doc_type":"usermanual", - "p_code":"168", - "code":"169" + "p_code":"173", + "code":"174" }, { "desc":"This section describes remote login, MRS cluster node types, and node functions.MRS cluster nodes support remote login. The following remote login methods are available:G", @@ -1526,8 +1571,8 @@ "title":"MRS Cluster Node Overview", "uri":"mrs_01_0081.html", "doc_type":"usermanual", - "p_code":"169", - "code":"170" + "p_code":"174", + "code":"175" }, { "desc":"This section describes how to remotely log in to an ECS in an MRS cluster using the remote login (VNC mode) function provided on the ECS management console or a key or pa", @@ -1535,8 +1580,8 @@ "title":"Logging In to an ECS", "uri":"mrs_01_0083.html", "doc_type":"usermanual", - "p_code":"169", - "code":"171" + "p_code":"174", + "code":"176" }, { "desc":"This section describes how to determine the active and standby management nodes of Manager on the Master1 node.You can log in to other nodes in the cluster from the Maste", @@ -1544,8 +1589,8 @@ "title":"Determining Active and Standby Management Nodes of Manager", "uri":"mrs_01_0086.html", "doc_type":"usermanual", - "p_code":"169", - "code":"172" + "p_code":"174", + "code":"177" }, { "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.", @@ -1553,8 +1598,8 @@ "title":"Cluster Overview", "uri":"mrs_01_0514.html", "doc_type":"usermanual", - "p_code":"168", - "code":"173" + "p_code":"173", + "code":"178" }, { "desc":"You can quickly view the status of all clusters and jobs by viewing the dashboard information, and obtain relevant MRS documents from Overview in the left navigation pane", @@ -1562,8 +1607,8 @@ "title":"Cluster List", "uri":"en-us_topic_0012799688.html", "doc_type":"usermanual", - "p_code":"173", - "code":"174" + "p_code":"178", + "code":"179" }, { "desc":"The cluster list contains all clusters in MRS. You can view clusters in various states. If a large number of clusters are involved, navigate through multiple pages to vie", @@ -1571,8 +1616,8 @@ "title":"Checking the Cluster Status", "uri":"en-us_topic_0012808230.html", "doc_type":"usermanual", - "p_code":"173", - "code":"175" + "p_code":"178", + "code":"180" }, { "desc":"You can monitor and manage the clusters you have created. Choose Clusters > Active Clusters. Select a cluster and click its name to go to the cluster details page. On the", @@ -1580,8 +1625,8 @@ "title":"Viewing Basic Cluster Information", "uri":"en-us_topic_0012808231.html", "doc_type":"usermanual", - "p_code":"173", - "code":"176" + "p_code":"178", + "code":"181" }, { "desc":"To view patch information about cluster components, you can download the required patch if the cluster component, such as Hadoop or Spark, is faulty. On the MRS console, ", @@ -1589,8 +1634,8 @@ "title":"Viewing Cluster Patch Information", "uri":"mrs_01_0036.html", "doc_type":"usermanual", - "p_code":"173", - "code":"177" + "p_code":"178", + "code":"182" }, { "desc":"MRS cluster nodes are classified into management nodes, control nodes, and data nodes. The change trends of key host monitoring metrics on each type of node can be calcul", @@ -1598,8 +1643,8 @@ "title":"Viewing and Customizing Cluster Monitoring Metrics", "uri":"mrs_01_0515.html", "doc_type":"usermanual", - "p_code":"173", - "code":"178" + "p_code":"178", + "code":"183" }, { "desc":"You can manage the following status and metrics of all components (including role instances) and hosts on the MRS console:Status information: includes operation, health, ", @@ -1607,8 +1652,8 @@ "title":"Managing Components and Monitoring Hosts", "uri":"mrs_01_0517.html", "doc_type":"usermanual", - "p_code":"173", - "code":"179" + "p_code":"178", + "code":"184" }, { "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.", @@ -1616,8 +1661,8 @@ "title":"Cluster O&M", "uri":"mrs_01_24295.html", "doc_type":"usermanual", - "p_code":"168", - "code":"180" + "p_code":"173", + "code":"185" }, { "desc":"Through the Files tab page, you can create, delete, import, export, delete files in the analysis cluster. Currently, file creation is not supported. Streaming clusters do", @@ -1625,8 +1670,8 @@ "title":"Importing and Exporting Data", "uri":"en-us_topic_0019489057.html", "doc_type":"usermanual", - "p_code":"180", - "code":"181" + "p_code":"185", + "code":"186" }, { "desc":"If the current subnet does not have sufficient IP addresses, you can change to another subnet in the same VPC of the current cluster to obtain more available subnet IP ad", @@ -1634,8 +1679,8 @@ "title":"Changing the Subnet of a Cluster", "uri":"mrs_01_24259.html", "doc_type":"usermanual", - "p_code":"180", - "code":"182" + "p_code":"185", + "code":"187" }, { "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).On the ", @@ -1643,8 +1688,8 @@ "title":"Configuring Message Notification", "uri":"mrs_01_0062.html", "doc_type":"usermanual", - "p_code":"180", - "code":"183" + "p_code":"185", + "code":"188" }, { "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.", @@ -1652,8 +1697,8 @@ "title":"Checking Health Status", "uri":"mrs_01_0223.html", "doc_type":"usermanual", - "p_code":"180", - "code":"184" + "p_code":"185", + "code":"189" }, { "desc":"This section describes how to manage health checks on the MRS console.Health check management operations on the MRS console apply only to clusters of MRS 1.9.2 to MRS 2.1", @@ -1661,8 +1706,8 @@ "title":"Before You Start", "uri":"mrs_01_0603.html", "doc_type":"usermanual", - "p_code":"184", - "code":"185" + "p_code":"189", + "code":"190" }, { "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", @@ -1670,8 +1715,8 @@ "title":"Performing a Health Check", "uri":"mrs_01_0224.html", "doc_type":"usermanual", - "p_code":"184", - "code":"186" + "p_code":"189", + "code":"191" }, { "desc":"You can view the health check result on MRS and export it for further analysis.A system health check includes MRS Manager, service-level, and host-level health checks:MRS", @@ -1679,8 +1724,8 @@ "title":"Viewing and Exporting a Health Check Report", "uri":"mrs_01_0225.html", "doc_type":"usermanual", - "p_code":"184", - "code":"187" + "p_code":"189", + "code":"192" }, { "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.", @@ -1688,8 +1733,8 @@ "title":"Remote O&M", "uri":"mrs_01_0520.html", "doc_type":"usermanual", - "p_code":"180", - "code":"188" + "p_code":"185", + "code":"193" }, { "desc":"If you need technical support personnel to help you with troubleshooting, you can use the O&M authorization function to authorize technical support personnel to access yo", @@ -1697,8 +1742,8 @@ "title":"Authorizing O&M", "uri":"mrs_01_0641.html", "doc_type":"usermanual", - "p_code":"188", - "code":"189" + "p_code":"193", + "code":"194" }, { "desc":"If you need technical support personnel to help you with troubleshooting, you can use the log sharing function to provide logs in a specific time to technical support per", @@ -1706,8 +1751,8 @@ "title":"Sharing Logs", "uri":"mrs_01_0642.html", "doc_type":"usermanual", - "p_code":"188", - "code":"190" + "p_code":"193", + "code":"195" }, { "desc":"You can view operation logs of clusters and jobs on the Operation Logs page. Log information is typically used for quickly locating faults in case of cluster exceptions, ", @@ -1715,8 +1760,8 @@ "title":"Viewing MRS Operation Logs", "uri":"en-us_topic_0012808265.html", "doc_type":"usermanual", - "p_code":"180", - "code":"191" + "p_code":"185", + "code":"196" }, { "desc":"You can terminate an MRS cluster after job execution is complete.You can manually terminate a cluster after data analysis is complete or when the cluster encounters an ex", @@ -1724,8 +1769,8 @@ "title":"Terminating a Cluster", "uri":"mrs_01_0042.html", "doc_type":"usermanual", - "p_code":"180", - "code":"192" + "p_code":"185", + "code":"197" }, { "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.", @@ -1733,8 +1778,8 @@ "title":"Managing Nodes", "uri":"mrs_01_24296.html", "doc_type":"usermanual", - "p_code":"168", - "code":"193" + "p_code":"173", + "code":"198" }, { "desc":"The storage and computing capabilities of MRS can be improved by simply adding Core nodes or Task nodes instead of modifying system architecture, reducing O&M costs. Core", @@ -1742,8 +1787,8 @@ "title":"Manually Scaling Out a Cluster", "uri":"mrs_01_0041.html", "doc_type":"usermanual", - "p_code":"193", - "code":"194" + "p_code":"198", + "code":"199" }, { "desc":"You can reduce the number of core or task nodes to scale in a cluster based on service requirements so that MRS delivers better storage and computing capabilities at lowe", @@ -1751,35 +1796,35 @@ "title":"Manually Scaling In a Cluster", "uri":"mrs_01_0060.html", "doc_type":"usermanual", - "p_code":"193", - "code":"195" + "p_code":"198", + "code":"200" }, { "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":"", + "product_code":"mrs", "title":"Removing ClickHouseServer Instance Nodes", "uri":"mrs_01_248971.html", - "doc_type":"", - "p_code":"193", - "code":"196" + "doc_type":"usermanual", + "p_code":"198", + "code":"201" }, { "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":"", + "product_code":"mrs", "title":"Constraints on ClickHouseServer Scale-in", "uri":"mrs_01_248972.html", - "doc_type":"", - "p_code":"196", - "code":"197" + "doc_type":"usermanual", + "p_code":"201", + "code":"202" }, { "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":"", + "product_code":"mrs", "title":"Scaling In ClickHouseServer Nodes", "uri":"mrs_01_248973.html", - "doc_type":"", - "p_code":"196", - "code":"198" + "doc_type":"usermanual", + "p_code":"201", + "code":"203" }, { "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", @@ -1787,8 +1832,8 @@ "title":"Managing a Host (Node)", "uri":"mrs_01_0211.html", "doc_type":"usermanual", - "p_code":"193", - "code":"199" + "p_code":"198", + "code":"204" }, { "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", @@ -1796,8 +1841,8 @@ "title":"Isolating a Host", "uri":"mrs_01_0212.html", "doc_type":"usermanual", - "p_code":"193", - "code":"200" + "p_code":"198", + "code":"205" }, { "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", @@ -1805,8 +1850,8 @@ "title":"Canceling Host Isolation", "uri":"mrs_01_0213.html", "doc_type":"usermanual", - "p_code":"193", - "code":"201" + "p_code":"198", + "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.", @@ -1814,8 +1859,8 @@ "title":"Job Management", "uri":"mrs_01_0522.html", "doc_type":"usermanual", - "p_code":"168", - "code":"202" + "p_code":"173", + "code":"207" }, { "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", @@ -1823,8 +1868,8 @@ "title":"Introduction to MRS Jobs", "uri":"mrs_01_0051.html", "doc_type":"usermanual", - "p_code":"202", - "code":"203" + "p_code":"207", + "code":"208" }, { "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", @@ -1832,8 +1877,8 @@ "title":"Running a MapReduce Job", "uri":"mrs_01_0052.html", "doc_type":"usermanual", - "p_code":"202", - "code":"204" + "p_code":"207", + "code":"209" }, { "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", @@ -1841,8 +1886,8 @@ "title":"Running a SparkSubmit Job", "uri":"mrs_01_0524.html", "doc_type":"usermanual", - "p_code":"202", - "code":"205" + "p_code":"207", + "code":"210" }, { "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", @@ -1850,8 +1895,8 @@ "title":"Running a HiveSQL Job", "uri":"mrs_01_0525.html", "doc_type":"usermanual", - "p_code":"202", - "code":"206" + "p_code":"207", + "code":"211" }, { "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", @@ -1859,8 +1904,8 @@ "title":"Running a SparkSql Job", "uri":"mrs_01_0526.html", "doc_type":"usermanual", - "p_code":"202", - "code":"207" + "p_code":"207", + "code":"212" }, { "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", @@ -1868,8 +1913,8 @@ "title":"Running a Flink Job", "uri":"mrs_01_0527.html", "doc_type":"usermanual", - "p_code":"202", - "code":"208" + "p_code":"207", + "code":"213" }, { "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", @@ -1877,8 +1922,8 @@ "title":"Running a Kafka Job", "uri":"mrs_01_0494.html", "doc_type":"usermanual", - "p_code":"202", - "code":"209" + "p_code":"207", + "code":"214" }, { "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", @@ -1886,8 +1931,8 @@ "title":"Viewing Job Configuration and Logs", "uri":"mrs_01_0055.html", "doc_type":"usermanual", - "p_code":"202", - "code":"210" + "p_code":"207", + "code":"215" }, { "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", @@ -1895,8 +1940,8 @@ "title":"Stopping a Job", "uri":"mrs_01_0056.html", "doc_type":"usermanual", - "p_code":"202", - "code":"211" + "p_code":"207", + "code":"216" }, { "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", @@ -1904,8 +1949,8 @@ "title":"Copying Jobs", "uri":"mrs_01_0057.html", "doc_type":"usermanual", - "p_code":"202", - "code":"212" + "p_code":"207", + "code":"217" }, { "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", @@ -1913,8 +1958,8 @@ "title":"Deleting a Job", "uri":"mrs_01_0058.html", "doc_type":"usermanual", - "p_code":"202", - "code":"213" + "p_code":"207", + "code":"218" }, { "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", @@ -1922,8 +1967,8 @@ "title":"Configuring Job Notification Rules", "uri":"mrs_01_0762.html", "doc_type":"usermanual", - "p_code":"202", - "code":"214" + "p_code":"207", + "code":"219" }, { "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.", @@ -1931,8 +1976,8 @@ "title":"Component Management", "uri":"mrs_01_0200.html", "doc_type":"usermanual", - "p_code":"168", - "code":"215" + "p_code":"173", + "code":"220" }, { "desc":"MRS contains different types of basic objects. Table 1 describes these objects.", @@ -1940,8 +1985,8 @@ "title":"Object Management", "uri":"mrs_01_0201.html", "doc_type":"usermanual", - "p_code":"215", - "code":"216" + "p_code":"220", + "code":"221" }, { "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 ", @@ -1949,8 +1994,8 @@ "title":"Viewing Configuration", "uri":"mrs_01_0202.html", "doc_type":"usermanual", - "p_code":"215", - "code":"217" + "p_code":"220", + "code":"222" }, { "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", @@ -1958,8 +2003,8 @@ "title":"Managing Services", "uri":"mrs_01_0203.html", "doc_type":"usermanual", - "p_code":"215", - "code":"218" + "p_code":"220", + "code":"223" }, { "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", @@ -1967,8 +2012,8 @@ "title":"Configuring Service Parameters", "uri":"mrs_01_0204.html", "doc_type":"usermanual", - "p_code":"215", - "code":"219" + "p_code":"220", + "code":"224" }, { "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 ", @@ -1976,8 +2021,8 @@ "title":"Configuring Customized Service Parameters", "uri":"mrs_01_0205.html", "doc_type":"usermanual", - "p_code":"215", - "code":"220" + "p_code":"220", + "code":"225" }, { "desc":"If Configuration Status of some services is Configuration expired or Configuration failed, synchronize configuration for the cluster or service to restore its configurati", @@ -1985,8 +2030,8 @@ "title":"Synchronizing Service Configuration", "uri":"mrs_01_0206.html", "doc_type":"usermanual", - "p_code":"215", - "code":"221" + "p_code":"220", + "code":"226" }, { "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", @@ -1994,8 +2039,8 @@ "title":"Managing Role Instances", "uri":"mrs_01_0207.html", "doc_type":"usermanual", - "p_code":"215", - "code":"222" + "p_code":"220", + "code":"227" }, { "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", @@ -2003,8 +2048,8 @@ "title":"Configuring Role Instance Parameters", "uri":"mrs_01_0208.html", "doc_type":"usermanual", - "p_code":"215", - "code":"223" + "p_code":"220", + "code":"228" }, { "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", @@ -2012,8 +2057,8 @@ "title":"Synchronizing Role Instance Configuration", "uri":"mrs_01_0209.html", "doc_type":"usermanual", - "p_code":"215", - "code":"224" + "p_code":"220", + "code":"229" }, { "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", @@ -2021,8 +2066,8 @@ "title":"Decommissioning and Recommissioning a Role Instance", "uri":"mrs_01_0210.html", "doc_type":"usermanual", - "p_code":"215", - "code":"225" + "p_code":"220", + "code":"230" }, { "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", @@ -2030,8 +2075,8 @@ "title":"Starting and Stopping a Cluster", "uri":"mrs_01_0214.html", "doc_type":"usermanual", - "p_code":"215", - "code":"226" + "p_code":"220", + "code":"231" }, { "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", @@ -2039,8 +2084,8 @@ "title":"Synchronizing Cluster Configuration", "uri":"mrs_01_0215.html", "doc_type":"usermanual", - "p_code":"215", - "code":"227" + "p_code":"220", + "code":"232" }, { "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", @@ -2048,8 +2093,8 @@ "title":"Exporting Cluster Configuration", "uri":"mrs_01_0216.html", "doc_type":"usermanual", - "p_code":"215", - "code":"228" + "p_code":"220", + "code":"233" }, { "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", @@ -2057,8 +2102,8 @@ "title":"Performing Rolling Restart", "uri":"mrs_01_0628.html", "doc_type":"usermanual", - "p_code":"215", - "code":"229" + "p_code":"220", + "code":"234" }, { "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.", @@ -2066,8 +2111,8 @@ "title":"Alarm Management", "uri":"mrs_01_0112.html", "doc_type":"usermanual", - "p_code":"168", - "code":"230" + "p_code":"173", + "code":"235" }, { "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", @@ -2075,8 +2120,8 @@ "title":"Viewing the Alarm List", "uri":"en-us_topic_0040980162.html", "doc_type":"usermanual", - "p_code":"230", - "code":"231" + "p_code":"235", + "code":"236" }, { "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 ", @@ -2084,8 +2129,8 @@ "title":"Viewing the Event List", "uri":"mrs_01_0602.html", "doc_type":"usermanual", - "p_code":"230", - "code":"232" + "p_code":"235", + "code":"237" }, { "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", @@ -2093,8 +2138,8 @@ "title":"Viewing and Manually Clearing an Alarm", "uri":"mrs_01_0113.html", "doc_type":"usermanual", - "p_code":"230", - "code":"233" + "p_code":"235", + "code":"238" }, { "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.", @@ -2102,8 +2147,8 @@ "title":"Patch Management", "uri":"mrs_01_0409.html", "doc_type":"usermanual", - "p_code":"168", - "code":"234" + "p_code":"173", + "code":"239" }, { "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", @@ -2111,8 +2156,8 @@ "title":"Patch Operation Guide for Versions Earlier than MRS 1.7.0", "uri":"mrs_01_0410.html", "doc_type":"usermanual", - "p_code":"234", - "code":"235" + "p_code":"239", + "code":"240" }, { "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", @@ -2120,8 +2165,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":"234", - "code":"236" + "p_code":"239", + "code":"241" }, { "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", @@ -2129,8 +2174,8 @@ "title":"Rolling Patches", "uri":"mrs_01_0431.html", "doc_type":"usermanual", - "p_code":"234", - "code":"237" + "p_code":"239", + "code":"242" }, { "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", @@ -2138,8 +2183,8 @@ "title":"Restoring Patches for the Isolated Hosts", "uri":"mrs_01_0412.html", "doc_type":"usermanual", - "p_code":"234", - "code":"238" + "p_code":"239", + "code":"243" }, { "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", @@ -2147,17 +2192,17 @@ "title":"Patch Update", "uri":"mrs_01_248926.html", "doc_type":"usermanual", - "p_code":"234", - "code":"239" + "p_code":"239", + "code":"244" }, { "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":"", + "product_code":"mrs", "title":"MRS 3.1.2-LTS.2 Patch Description", "uri":"mrs_01_9043.html", - "doc_type":"", - "p_code":"234", - "code":"240" + "doc_type":"usermanual", + "p_code":"239", + "code":"245" }, { "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.", @@ -2165,8 +2210,8 @@ "title":"Tenant Management", "uri":"mrs_01_0303.html", "doc_type":"usermanual", - "p_code":"168", - "code":"241" + "p_code":"173", + "code":"246" }, { "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", @@ -2174,8 +2219,8 @@ "title":"Before You Start", "uri":"mrs_01_0604.html", "doc_type":"usermanual", - "p_code":"241", - "code":"242" + "p_code":"246", + "code":"247" }, { "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", @@ -2183,8 +2228,8 @@ "title":"Overview", "uri":"mrs_01_0304.html", "doc_type":"usermanual", - "p_code":"241", - "code":"243" + "p_code":"246", + "code":"248" }, { "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", @@ -2192,8 +2237,8 @@ "title":"Creating a Tenant", "uri":"mrs_01_0305.html", "doc_type":"usermanual", - "p_code":"241", - "code":"244" + "p_code":"246", + "code":"249" }, { "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 ", @@ -2201,8 +2246,8 @@ "title":"Creating a Sub-tenant", "uri":"mrs_01_0306.html", "doc_type":"usermanual", - "p_code":"241", - "code":"245" + "p_code":"246", + "code":"250" }, { "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", @@ -2210,8 +2255,8 @@ "title":"Deleting a Tenant", "uri":"mrs_01_0307.html", "doc_type":"usermanual", - "p_code":"241", - "code":"246" + "p_code":"246", + "code":"251" }, { "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", @@ -2219,8 +2264,8 @@ "title":"Managing a Tenant Directory", "uri":"mrs_01_0308.html", "doc_type":"usermanual", - "p_code":"241", - "code":"247" + "p_code":"246", + "code":"252" }, { "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", @@ -2228,8 +2273,8 @@ "title":"Restoring Tenant Data", "uri":"mrs_01_0309.html", "doc_type":"usermanual", - "p_code":"241", - "code":"248" + "p_code":"246", + "code":"253" }, { "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", @@ -2237,8 +2282,8 @@ "title":"Creating a Resource Pool", "uri":"mrs_01_0310.html", "doc_type":"usermanual", - "p_code":"241", - "code":"249" + "p_code":"246", + "code":"254" }, { "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", @@ -2246,8 +2291,8 @@ "title":"Modifying a Resource Pool", "uri":"mrs_01_0311.html", "doc_type":"usermanual", - "p_code":"241", - "code":"250" + "p_code":"246", + "code":"255" }, { "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", @@ -2255,8 +2300,8 @@ "title":"Deleting a Resource Pool", "uri":"mrs_01_0312.html", "doc_type":"usermanual", - "p_code":"241", - "code":"251" + "p_code":"246", + "code":"256" }, { "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", @@ -2264,8 +2309,8 @@ "title":"Configuring a Queue", "uri":"mrs_01_0313.html", "doc_type":"usermanual", - "p_code":"241", - "code":"252" + "p_code":"246", + "code":"257" }, { "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 ", @@ -2273,8 +2318,8 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"mrs_01_0314.html", "doc_type":"usermanual", - "p_code":"241", - "code":"253" + "p_code":"246", + "code":"258" }, { "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", @@ -2282,8 +2327,8 @@ "title":"Clearing Configuration of a Queue", "uri":"mrs_01_0315.html", "doc_type":"usermanual", - "p_code":"241", - "code":"254" + "p_code":"246", + "code":"259" }, { "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 +2336,8 @@ "title":"Bootstrap Actions", "uri":"mrs_01_24565.html", "doc_type":"usermanual", - "p_code":"168", - "code":"255" + "p_code":"173", + "code":"260" }, { "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", @@ -2300,8 +2345,8 @@ "title":"Introduction to Bootstrap Actions", "uri":"mrs_01_0414.html", "doc_type":"usermanual", - "p_code":"255", - "code":"256" + "p_code":"260", + "code":"261" }, { "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", @@ -2309,8 +2354,8 @@ "title":"Preparing the Bootstrap Action Script", "uri":"mrs_01_0417.html", "doc_type":"usermanual", - "p_code":"255", - "code":"257" + "p_code":"260", + "code":"262" }, { "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 ", @@ -2318,8 +2363,8 @@ "title":"View Execution Records", "uri":"mrs_01_0415.html", "doc_type":"usermanual", - "p_code":"255", - "code":"258" + "p_code":"260", + "code":"263" }, { "desc":"Add a bootstrap action.This operation applies to clusters earlier than MRS 3.x.", @@ -2327,8 +2372,8 @@ "title":"Adding a Bootstrap Action", "uri":"mrs_01_0416.html", "doc_type":"usermanual", - "p_code":"255", - "code":"259" + "p_code":"260", + "code":"264" }, { "desc":"Modify an existing bootstrap action on an MRS cluster.", @@ -2336,8 +2381,8 @@ "title":"Modifying a Bootstrap Action", "uri":"mrs_01_24566.html", "doc_type":"usermanual", - "p_code":"255", - "code":"260" + "p_code":"260", + "code":"265" }, { "desc":"Delete a bootstrap action on an MRS cluster.", @@ -2345,8 +2390,8 @@ "title":"Deleting a Bootstrap Action", "uri":"mrs_01_24567.html", "doc_type":"usermanual", - "p_code":"255", - "code":"261" + "p_code":"260", + "code":"266" }, { "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", @@ -2354,8 +2399,8 @@ "title":"Sample Scripts", "uri":"mrs_01_0418.html", "doc_type":"usermanual", - "p_code":"255", - "code":"262" + "p_code":"260", + "code":"267" }, { "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.", @@ -2364,7 +2409,7 @@ "uri":"mrs_01_0088.html", "doc_type":"usermanual", "p_code":"", - "code":"263" + "code":"268" }, { "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.", @@ -2372,8 +2417,8 @@ "title":"Installing a Client", "uri":"mrs_01_24212.html", "doc_type":"usermanual", - "p_code":"263", - "code":"264" + "p_code":"268", + "code":"269" }, { "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", @@ -2381,8 +2426,8 @@ "title":"Installing a Client (Version 3.x or Later)", "uri":"mrs_01_0090.html", "doc_type":"usermanual", - "p_code":"264", - "code":"265" + "p_code":"269", + "code":"270" }, { "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 ", @@ -2390,8 +2435,8 @@ "title":"Installing a Client (Versions Earlier Than 3.x)", "uri":"mrs_01_0091.html", "doc_type":"usermanual", - "p_code":"264", - "code":"266" + "p_code":"269", + "code":"271" }, { "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.", @@ -2399,8 +2444,8 @@ "title":"Updating a Client", "uri":"mrs_01_24213.html", "doc_type":"usermanual", - "p_code":"263", - "code":"267" + "p_code":"268", + "code":"272" }, { "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", @@ -2408,8 +2453,8 @@ "title":"Updating a Client (Version 3.x or Later)", "uri":"mrs_01_24209.html", "doc_type":"usermanual", - "p_code":"267", - "code":"268" + "p_code":"272", + "code":"273" }, { "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", @@ -2417,8 +2462,8 @@ "title":"Updating a Client (Versions Earlier Than 3.x)", "uri":"mrs_01_0089.html", "doc_type":"usermanual", - "p_code":"267", - "code":"269" + "p_code":"272", + "code":"274" }, { "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.", @@ -2426,80 +2471,80 @@ "title":"Using the Client of Each Component", "uri":"mrs_01_24183.html", "doc_type":"usermanual", - "p_code":"263", - "code":"270" + "p_code":"268", + "code":"275" }, { "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 ", "product_code":"mrs", "title":"Using a ClickHouse Client", "uri":"mrs_01_24184.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"271" + "doc_type":"usermanual", + "p_code":"275", + "code":"276" }, { "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", "product_code":"mrs", "title":"Using a Flink Client", "uri":"mrs_01_24185.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"272" + "doc_type":"usermanual", + "p_code":"275", + "code":"277" }, { "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", "product_code":"mrs", "title":"Using a Flume Client", "uri":"mrs_01_24186.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"273" + "doc_type":"usermanual", + "p_code":"275", + "code":"278" }, { "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", "product_code":"mrs", "title":"Using an HBase Client", "uri":"mrs_01_24187.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"274" + "doc_type":"usermanual", + "p_code":"275", + "code":"279" }, { "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", "product_code":"mrs", "title":"Using an HDFS Client", "uri":"mrs_01_24188.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"275" + "doc_type":"usermanual", + "p_code":"275", + "code":"280" }, { "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 ", "product_code":"mrs", "title":"Using a Hive Client", "uri":"mrs_01_24189.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"276" + "doc_type":"usermanual", + "p_code":"275", + "code":"281" }, { "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", "product_code":"mrs", "title":"Using a Kafka Client", "uri":"mrs_01_24191.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"277" + "doc_type":"usermanual", + "p_code":"275", + "code":"282" }, { "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", "product_code":"mrs", "title":"Using the Oozie Client", "uri":"mrs_01_24193.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"278" + "doc_type":"usermanual", + "p_code":"275", + "code":"283" }, { "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", @@ -2507,17 +2552,17 @@ "title":"Using a Storm Client", "uri":"mrs_01_24194.html", "doc_type":"usermanual", - "p_code":"270", - "code":"279" + "p_code":"275", + "code":"284" }, { "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", "product_code":"mrs", "title":"Using a Yarn Client", "uri":"mrs_01_24196.html", - "doc_type":"cmpntguide", - "p_code":"270", - "code":"280" + "doc_type":"usermanual", + "p_code":"275", + "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.", @@ -2526,7 +2571,7 @@ "uri":"mrs_01_0440.html", "doc_type":"usermanual", "p_code":"", - "code":"281" + "code":"286" }, { "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", @@ -2534,17 +2579,17 @@ "title":"MRS Storage-Compute Decoupling", "uri":"mrs_01_0467.html", "doc_type":"usermanual", - "p_code":"281", - "code":"282" + "p_code":"286", + "code":"287" }, { "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":"", + "product_code":"mrs", "title":"Interconnecting with OBS Using the Cluster Agency Mechanism", "uri":"mrs_01_249279.html", - "doc_type":"", - "p_code":"281", - "code":"283" + "doc_type":"usermanual", + "p_code":"286", + "code":"288" }, { "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", @@ -2552,8 +2597,8 @@ "title":"Configuring a Storage-Compute Decoupled Cluster (Agency)", "uri":"mrs_01_0768.html", "doc_type":"usermanual", - "p_code":"283", - "code":"284" + "p_code":"288", + "code":"289" }, { "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", @@ -2561,17 +2606,17 @@ "title":"Configuring a Storage-Compute Decoupled Cluster (AK/SK)", "uri":"mrs_01_0468.html", "doc_type":"usermanual", - "p_code":"283", - "code":"285" + "p_code":"288", + "code":"290" }, { "desc":"By default, components in an MRS 3.2.0-LTS.1 or later cluster support prevention against accidental data deletion. Native HDFS garbage collection can be used in the Hadoo", - "product_code":"", + "product_code":"mrs", "title":"Configuring the Policy for Clearing Component Data in the Recycle Bin", "uri":"mrs_01_249150.html", - "doc_type":"", - "p_code":"283", - "code":"286" + "doc_type":"usermanual", + "p_code":"288", + "code":"291" }, { "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.", @@ -2579,8 +2624,8 @@ "title":"Interconnecting MRS with OBS Using an Agency", "uri":"mrs_01_0643.html", "doc_type":"usermanual", - "p_code":"283", - "code":"287" + "p_code":"288", + "code":"292" }, { "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", @@ -2588,8 +2633,8 @@ "title":"Interconnecting Flink with OBS", "uri":"mrs_01_1288.html", "doc_type":"usermanual", - "p_code":"287", - "code":"288" + "p_code":"292", + "code":"293" }, { "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", @@ -2597,8 +2642,8 @@ "title":"Interconnecting Flume with OBS", "uri":"mrs_01_24279.html", "doc_type":"usermanual", - "p_code":"287", - "code":"289" + "p_code":"292", + "code":"294" }, { "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", @@ -2606,8 +2651,8 @@ "title":"Interconnecting HDFS with OBS", "uri":"mrs_01_1292.html", "doc_type":"usermanual", - "p_code":"287", - "code":"290" + "p_code":"292", + "code":"295" }, { "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", @@ -2615,8 +2660,8 @@ "title":"Interconnecting Hive with OBS", "uri":"mrs_01_1286.html", "doc_type":"usermanual", - "p_code":"287", - "code":"291" + "p_code":"292", + "code":"296" }, { "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", @@ -2624,8 +2669,8 @@ "title":"Interconnecting MapReduce with OBS", "uri":"mrs_01_0617.html", "doc_type":"usermanual", - "p_code":"287", - "code":"292" + "p_code":"292", + "code":"297" }, { "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", @@ -2633,8 +2678,8 @@ "title":"Interconnecting Spark2x with OBS", "uri":"mrs_01_1289.html", "doc_type":"usermanual", - "p_code":"287", - "code":"293" + "p_code":"292", + "code":"298" }, { "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", @@ -2642,8 +2687,8 @@ "title":"Interconnecting Sqoop with External Storage Systems", "uri":"mrs_01_24294.html", "doc_type":"usermanual", - "p_code":"287", - "code":"294" + "p_code":"292", + "code":"299" }, { "desc":"source ${client_home}/bigdata_envsource ${client_home}/Hudi/component_envvim ${client_home}/Hudi/hudi/conf/hdfs-site.xmlkinit Usernameimport org.apache.hudi.QuickstartUti", @@ -2651,8 +2696,8 @@ "title":"Interconnecting Hudi with OBS", "uri":"mrs_01_24171.html", "doc_type":"usermanual", - "p_code":"287", - "code":"295" + "p_code":"292", + "code":"300" }, { "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", @@ -2660,116 +2705,116 @@ "title":"Configuring Fine-Grained Permissions for MRS Multi-User Access to OBS", "uri":"mrs_01_0632.html", "doc_type":"usermanual", - "p_code":"283", - "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.", - "product_code":"", - "title":"Interconnecting with OBS Using the Guardian Service", - "uri":"mrs_01_248986.html", - "doc_type":"", - "p_code":"281", - "code":"297" - }, - { - "desc":"Create an MRS cluster.The MRS cluster must contain basic components such as Guardian, Ranger, and Hadoop.Currently, only MRS 3.3.0-LTS and later versions support intercon", - "product_code":"", - "title":"Scenarios", - "uri":"mrs_01_248987.html", - "doc_type":"", - "p_code":"297", - "code":"298" - }, - { - "desc":"This section describes how to enable storage and compute decoupling for the Guardian component. After this feature is enabled, Guardian can provide temporary authenticati", - "product_code":"", - "title":"Interconnecting the Guardian Service with OBS", - "uri":"mrs_01_248978.html", - "doc_type":"", - "p_code":"297", - "code":"299" - }, - { - "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":"Interconnecting Components with OBS Using Guardian", - "uri":"mrs_01_248988.html", - "doc_type":"", - "p_code":"297", - "code":"300" - }, - { - "desc":"MRS clusters allow Hive to connect to OBS through Metastore.Interconnecting Hive with OBS through MetastoreLog in to the node where the Hive client is located and run the", - "product_code":"", - "title":"Interconnecting Hive with OBS", - "uri":"mrs_01_248989.html", - "doc_type":"", - "p_code":"300", + "p_code":"288", "code":"301" }, { - "desc":"source Client installation directory/bigdata_envNormal cluster (Kerberos authentication disabled)yarn-session.sh -nm \"session-name\" -dyarn-session.sh -nm \"session-name\" -", - "product_code":"", - "title":"Interconnecting Flink with OBS", - "uri":"mrs_01_248991.html", - "doc_type":"", - "p_code":"300", + "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":"Interconnecting with OBS Using the Guardian Service", + "uri":"mrs_01_248986.html", + "doc_type":"usermanual", + "p_code":"286", "code":"302" }, { - "desc":"In an MRS cluster, Location can be set to an OBS file system path during Spark table creation and Spark can connect to OBS through Hive Metastore.Setting the location to ", - "product_code":"", - "title":"Interconnecting Spark with OBS", - "uri":"mrs_01_248992.html", - "doc_type":"", - "p_code":"300", + "desc":"Create an MRS cluster.The MRS cluster must contain basic components such as Guardian, Ranger, and Hadoop.Currently, only MRS 3.3.0-LTS and later versions support intercon", + "product_code":"mrs", + "title":"Scenarios", + "uri":"mrs_01_248987.html", + "doc_type":"usermanual", + "p_code":"302", "code":"303" }, { - "desc":"sourceClient installation directory/bigdata_envsourceClient installation directory/Hudi/component_envvimClient installation directory/Hudi/hudi/conf/hdfs-site.xmlkinit Us", - "product_code":"", - "title":"Interconnecting Hudi with OBS", - "uri":"mrs_01_248993.html", - "doc_type":"", - "p_code":"300", + "desc":"This section describes how to enable storage and compute decoupling for the Guardian component. After this feature is enabled, Guardian can provide temporary authenticati", + "product_code":"mrs", + "title":"Interconnecting the Guardian Service with OBS", + "uri":"mrs_01_248978.html", + "doc_type":"usermanual", + "p_code":"302", "code":"304" }, { - "desc":"In an MRS cluster, Location can be set to an OBS file system path during HetuEngine table creation and HetuEngine can connect to OBS through Hive Metastore.Setting Locati", - "product_code":"", - "title":"Interconnecting HetuEngine with OBS", - "uri":"mrs_01_248995.html", - "doc_type":"", - "p_code":"300", + "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":"Interconnecting Components with OBS Using Guardian", + "uri":"mrs_01_248988.html", + "doc_type":"usermanual", + "p_code":"302", "code":"305" }, { - "desc":"cd Client installation directorysource bigdata_envkinitUser performing HDFS operationsThe following commands are examples.Access the OBS file system.hdfs dfs -ls obs://OB", - "product_code":"", - "title":"Interconnecting HDFS with OBS", - "uri":"mrs_01_248996.html", - "doc_type":"", - "p_code":"300", + "desc":"MRS clusters allow Hive to connect to OBS through Metastore.Interconnecting Hive with OBS through MetastoreLog in to the node where the Hive client is located and run the", + "product_code":"mrs", + "title":"Interconnecting Hive with OBS", + "uri":"mrs_01_248989.html", + "doc_type":"usermanual", + "p_code":"305", "code":"306" }, { - "desc":"cd Client installation directorysource bigdata_envkinitUser performing HDFS operationsAccess the OBS file system.hdfs dfs -ls obs://OBS parallel file system name/Pathhdfs", - "product_code":"", - "title":"Interconnecting Yarn with OBS", - "uri":"mrs_01_248997.html", - "doc_type":"", - "p_code":"300", + "desc":"source Client installation directory/bigdata_envNormal cluster (Kerberos authentication disabled)yarn-session.sh -nm \"session-name\" -dyarn-session.sh -nm \"session-name\" -", + "product_code":"mrs", + "title":"Interconnecting Flink with OBS", + "uri":"mrs_01_248991.html", + "doc_type":"usermanual", + "p_code":"305", "code":"307" }, + { + "desc":"In an MRS cluster, Location can be set to an OBS file system path during Spark table creation and Spark can connect to OBS through Hive Metastore.Setting the location to ", + "product_code":"mrs", + "title":"Interconnecting Spark with OBS", + "uri":"mrs_01_248992.html", + "doc_type":"usermanual", + "p_code":"305", + "code":"308" + }, + { + "desc":"sourceClient installation directory/bigdata_envsourceClient installation directory/Hudi/component_envvimClient installation directory/Hudi/hudi/conf/hdfs-site.xmlkinit Us", + "product_code":"mrs", + "title":"Interconnecting Hudi with OBS", + "uri":"mrs_01_248993.html", + "doc_type":"usermanual", + "p_code":"305", + "code":"309" + }, + { + "desc":"In an MRS cluster, Location can be set to an OBS file system path during HetuEngine table creation and HetuEngine can connect to OBS through Hive Metastore.Setting Locati", + "product_code":"mrs", + "title":"Interconnecting HetuEngine with OBS", + "uri":"mrs_01_248995.html", + "doc_type":"usermanual", + "p_code":"305", + "code":"310" + }, + { + "desc":"cd Client installation directorysource bigdata_envkinitUser performing HDFS operationsThe following commands are examples.Access the OBS file system.hdfs dfs -ls obs://OB", + "product_code":"mrs", + "title":"Interconnecting HDFS with OBS", + "uri":"mrs_01_248996.html", + "doc_type":"usermanual", + "p_code":"305", + "code":"311" + }, + { + "desc":"cd Client installation directorysource bigdata_envkinitUser performing HDFS operationsAccess the OBS file system.hdfs dfs -ls obs://OBS parallel file system name/Pathhdfs", + "product_code":"mrs", + "title":"Interconnecting Yarn with OBS", + "uri":"mrs_01_248997.html", + "doc_type":"usermanual", + "p_code":"305", + "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.", - "product_code":"", + "product_code":"mrs", "title":"Interconnecting MapReduce with OBS", "uri":"mrs_01_248998.html", - "doc_type":"", - "p_code":"300", - "code":"308" + "doc_type":"usermanual", + "p_code":"305", + "code":"313" }, { "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.", @@ -2778,7 +2823,7 @@ "uri":"mrs_01_0644.html", "doc_type":"usermanual", "p_code":"", - "code":"309" + "code":"314" }, { "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", @@ -2786,8 +2831,8 @@ "title":"Web UIs of Open Source Components", "uri":"mrs_01_0362.html", "doc_type":"usermanual", - "p_code":"309", - "code":"310" + "p_code":"314", + "code":"315" }, { "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 ", @@ -2795,8 +2840,8 @@ "title":"List of Open Source Component Ports", "uri":"mrs_01_0504.html", "doc_type":"usermanual", - "p_code":"309", - "code":"311" + "p_code":"314", + "code":"316" }, { "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", @@ -2804,8 +2849,8 @@ "title":"Access Through Direct Connect", "uri":"mrs_01_0645.html", "doc_type":"usermanual", - "p_code":"309", - "code":"312" + "p_code":"314", + "code":"317" }, { "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 ", @@ -2813,8 +2858,8 @@ "title":"EIP-based Access", "uri":"mrs_01_0646.html", "doc_type":"usermanual", - "p_code":"309", - "code":"313" + "p_code":"314", + "code":"318" }, { "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", @@ -2822,8 +2867,8 @@ "title":"Access Using a Windows ECS", "uri":"mrs_01_0647.html", "doc_type":"usermanual", - "p_code":"309", - "code":"314" + "p_code":"314", + "code":"319" }, { "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 ", @@ -2831,8 +2876,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":"309", - "code":"315" + "p_code":"314", + "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.", @@ -2841,7 +2886,7 @@ "uri":"mrs_01_0128.html", "doc_type":"usermanual", "p_code":"", - "code":"316" + "code":"321" }, { "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", @@ -2849,8 +2894,8 @@ "title":"Accessing MRS Manager", "uri":"mrs_01_0129.html", "doc_type":"usermanual", - "p_code":"316", - "code":"317" + "p_code":"321", + "code":"322" }, { "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", @@ -2858,8 +2903,8 @@ "title":"Accessing MRS Manager (MRS 2.x or Earlier)", "uri":"mrs_01_0102.html", "doc_type":"usermanual", - "p_code":"316", - "code":"318" + "p_code":"321", + "code":"323" }, { "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.", @@ -2868,7 +2913,7 @@ "uri":"mrs_01_0606.html", "doc_type":"usermanual", "p_code":"", - "code":"319" + "code":"324" }, { "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.", @@ -2876,8 +2921,8 @@ "title":"Getting Started", "uri":"admin_guide_000001.html", "doc_type":"usermanual", - "p_code":"319", - "code":"320" + "p_code":"324", + "code":"325" }, { "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", @@ -2885,8 +2930,8 @@ "title":"MRS Manager Introduction", "uri":"admin_guide_000002.html", "doc_type":"usermanual", - "p_code":"320", - "code":"321" + "p_code":"325", + "code":"326" }, { "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 ", @@ -2894,8 +2939,8 @@ "title":"Querying the MRS Manager Version", "uri":"admin_guide_000003.html", "doc_type":"usermanual", - "p_code":"320", - "code":"322" + "p_code":"325", + "code":"327" }, { "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 ", @@ -2903,8 +2948,8 @@ "title":"Logging In to MRS Manager", "uri":"admin_guide_000004.html", "doc_type":"usermanual", - "p_code":"320", - "code":"323" + "p_code":"325", + "code":"328" }, { "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", @@ -2912,8 +2957,8 @@ "title":"Logging In to the Management Node", "uri":"admin_guide_000005.html", "doc_type":"usermanual", - "p_code":"320", - "code":"324" + "p_code":"325", + "code":"329" }, { "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,8 +2966,8 @@ "title":"Home Page", "uri":"admin_guide_000006.html", "doc_type":"usermanual", - "p_code":"319", - "code":"325" + "p_code":"324", + "code":"330" }, { "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", @@ -2930,8 +2975,8 @@ "title":"Overview", "uri":"admin_guide_000007.html", "doc_type":"usermanual", - "p_code":"325", - "code":"326" + "p_code":"330", + "code":"331" }, { "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", @@ -2939,8 +2984,8 @@ "title":"Managing Monitoring Metric Reports", "uri":"admin_guide_000008.html", "doc_type":"usermanual", - "p_code":"325", - "code":"327" + "p_code":"330", + "code":"332" }, { "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,8 +2993,8 @@ "title":"Cluster", "uri":"admin_guide_000009.html", "doc_type":"usermanual", - "p_code":"319", - "code":"328" + "p_code":"324", + "code":"333" }, { "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.", @@ -2957,8 +3002,8 @@ "title":"Cluster Management", "uri":"admin_guide_000010.html", "doc_type":"usermanual", - "p_code":"328", - "code":"329" + "p_code":"333", + "code":"334" }, { "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", @@ -2966,8 +3011,8 @@ "title":"Overview", "uri":"admin_guide_000011.html", "doc_type":"usermanual", - "p_code":"329", - "code":"330" + "p_code":"334", + "code":"335" }, { "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 ", @@ -2975,8 +3020,8 @@ "title":"Performing a Rolling Restart of a Cluster", "uri":"admin_guide_000012.html", "doc_type":"usermanual", - "p_code":"329", - "code":"331" + "p_code":"334", + "code":"336" }, { "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", @@ -2984,8 +3029,8 @@ "title":"Managing Expired Configurations", "uri":"admin_guide_000013.html", "doc_type":"usermanual", - "p_code":"329", - "code":"332" + "p_code":"334", + "code":"337" }, { "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", @@ -2993,8 +3038,8 @@ "title":"Downloading the Client", "uri":"admin_guide_000014.html", "doc_type":"usermanual", - "p_code":"329", - "code":"333" + "p_code":"334", + "code":"338" }, { "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,", @@ -3002,8 +3047,8 @@ "title":"Modifying Cluster Attributes", "uri":"admin_guide_000015.html", "doc_type":"usermanual", - "p_code":"329", - "code":"334" + "p_code":"334", + "code":"339" }, { "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", @@ -3011,8 +3056,8 @@ "title":"Managing Cluster Configurations", "uri":"admin_guide_000016.html", "doc_type":"usermanual", - "p_code":"329", - "code":"335" + "p_code":"334", + "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.", @@ -3020,8 +3065,8 @@ "title":"Managing Static Service Pools", "uri":"admin_guide_000017.html", "doc_type":"usermanual", - "p_code":"329", - "code":"336" + "p_code":"334", + "code":"341" }, { "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", @@ -3029,8 +3074,8 @@ "title":"Static Service Resources", "uri":"admin_guide_000018.html", "doc_type":"usermanual", - "p_code":"336", - "code":"337" + "p_code":"341", + "code":"342" }, { "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", @@ -3038,8 +3083,8 @@ "title":"Configuring Cluster Static Resources", "uri":"admin_guide_000019.html", "doc_type":"usermanual", - "p_code":"336", - "code":"338" + "p_code":"341", + "code":"343" }, { "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", @@ -3047,8 +3092,8 @@ "title":"Viewing Cluster Static Resources", "uri":"admin_guide_000020.html", "doc_type":"usermanual", - "p_code":"336", - "code":"339" + "p_code":"341", + "code":"344" }, { "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.", @@ -3056,8 +3101,8 @@ "title":"Managing Clients", "uri":"admin_guide_000021.html", "doc_type":"usermanual", - "p_code":"329", - "code":"340" + "p_code":"334", + "code":"345" }, { "desc":"MRS Manager supports unified management of cluster client installation information. After a user downloads and installs a client, MRS Manager automatically records inform", @@ -3065,8 +3110,8 @@ "title":"Managing a Client", "uri":"admin_guide_000022.html", "doc_type":"usermanual", - "p_code":"340", - "code":"341" + "p_code":"345", + "code":"346" }, { "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", @@ -3074,8 +3119,8 @@ "title":"Batch Upgrading Clients", "uri":"admin_guide_000023.html", "doc_type":"usermanual", - "p_code":"340", - "code":"342" + "p_code":"345", + "code":"347" }, { "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", @@ -3083,8 +3128,8 @@ "title":"Updating the hosts File in Batches", "uri":"admin_guide_000024.html", "doc_type":"usermanual", - "p_code":"340", - "code":"343" + "p_code":"345", + "code":"348" }, { "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.", @@ -3092,8 +3137,8 @@ "title":"Managing a Service", "uri":"admin_guide_000026.html", "doc_type":"usermanual", - "p_code":"328", - "code":"344" + "p_code":"333", + "code":"349" }, { "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", @@ -3101,8 +3146,8 @@ "title":"Overview", "uri":"admin_guide_000027.html", "doc_type":"usermanual", - "p_code":"344", - "code":"345" + "p_code":"349", + "code":"350" }, { "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.", @@ -3110,8 +3155,8 @@ "title":"Other Service Management Operations", "uri":"admin_guide_000029.html", "doc_type":"usermanual", - "p_code":"344", - "code":"346" + "p_code":"349", + "code":"351" }, { "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,", @@ -3119,8 +3164,8 @@ "title":"Service Details Page", "uri":"admin_guide_000030.html", "doc_type":"usermanual", - "p_code":"346", - "code":"347" + "p_code":"351", + "code":"352" }, { "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", @@ -3128,8 +3173,8 @@ "title":"Performing Active/Standby Switchover of a Role Instance", "uri":"admin_guide_000031.html", "doc_type":"usermanual", - "p_code":"346", - "code":"348" + "p_code":"351", + "code":"353" }, { "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 ", @@ -3137,8 +3182,8 @@ "title":"Resource Monitoring", "uri":"admin_guide_000032.html", "doc_type":"usermanual", - "p_code":"346", - "code":"349" + "p_code":"351", + "code":"354" }, { "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 ", @@ -3146,8 +3191,8 @@ "title":"Collecting Stack Information", "uri":"admin_guide_000033.html", "doc_type":"usermanual", - "p_code":"346", - "code":"350" + "p_code":"351", + "code":"355" }, { "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 ", @@ -3155,8 +3200,8 @@ "title":"Switching Ranger Authentication", "uri":"admin_guide_000415.html", "doc_type":"usermanual", - "p_code":"346", - "code":"351" + "p_code":"351", + "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.", @@ -3164,8 +3209,8 @@ "title":"Service Configuration", "uri":"admin_guide_000034.html", "doc_type":"usermanual", - "p_code":"344", - "code":"352" + "p_code":"349", + "code":"357" }, { "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", @@ -3173,8 +3218,8 @@ "title":"Modifying Service Configuration Parameters", "uri":"admin_guide_000035.html", "doc_type":"usermanual", - "p_code":"352", - "code":"353" + "p_code":"357", + "code":"358" }, { "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", @@ -3182,8 +3227,8 @@ "title":"Modifying Custom Configuration Parameters of a Service", "uri":"admin_guide_000036.html", "doc_type":"usermanual", - "p_code":"352", - "code":"354" + "p_code":"357", + "code":"359" }, { "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.", @@ -3191,8 +3236,8 @@ "title":"Instance Management", "uri":"admin_guide_000037.html", "doc_type":"usermanual", - "p_code":"328", - "code":"355" + "p_code":"333", + "code":"360" }, { "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", @@ -3200,8 +3245,8 @@ "title":"Overview", "uri":"admin_guide_000038.html", "doc_type":"usermanual", - "p_code":"355", - "code":"356" + "p_code":"360", + "code":"361" }, { "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", @@ -3209,8 +3254,8 @@ "title":"Decommissioning and Recommissioning an Instance", "uri":"admin_guide_000040.html", "doc_type":"usermanual", - "p_code":"355", - "code":"357" + "p_code":"360", + "code":"362" }, { "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", @@ -3218,8 +3263,8 @@ "title":"Managing Instance Configurations", "uri":"admin_guide_000043.html", "doc_type":"usermanual", - "p_code":"355", - "code":"358" + "p_code":"360", + "code":"363" }, { "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", @@ -3227,8 +3272,8 @@ "title":"Viewing the Instance Configuration File", "uri":"admin_guide_000044.html", "doc_type":"usermanual", - "p_code":"355", - "code":"359" + "p_code":"360", + "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.", @@ -3236,8 +3281,8 @@ "title":"Instance Group", "uri":"admin_guide_000045.html", "doc_type":"usermanual", - "p_code":"355", - "code":"360" + "p_code":"360", + "code":"365" }, { "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 ", @@ -3245,8 +3290,8 @@ "title":"Managing Instance Groups", "uri":"admin_guide_000046.html", "doc_type":"usermanual", - "p_code":"360", - "code":"361" + "p_code":"365", + "code":"366" }, { "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", @@ -3254,8 +3299,8 @@ "title":"Viewing Information About an Instance Group", "uri":"admin_guide_000047.html", "doc_type":"usermanual", - "p_code":"360", - "code":"362" + "p_code":"365", + "code":"367" }, { "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", @@ -3263,8 +3308,8 @@ "title":"Configuring Instantiation Group Parameters", "uri":"admin_guide_000048.html", "doc_type":"usermanual", - "p_code":"360", - "code":"363" + "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.", @@ -3272,8 +3317,8 @@ "title":"Hosts", "uri":"admin_guide_000049.html", "doc_type":"usermanual", - "p_code":"319", - "code":"364" + "p_code":"324", + "code":"369" }, { "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,8 +3326,8 @@ "title":"Host Management Page", "uri":"admin_guide_000050.html", "doc_type":"usermanual", - "p_code":"364", - "code":"365" + "p_code":"369", + "code":"370" }, { "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", @@ -3290,8 +3335,8 @@ "title":"Viewing the Host List", "uri":"admin_guide_000051.html", "doc_type":"usermanual", - "p_code":"365", - "code":"366" + "p_code":"370", + "code":"371" }, { "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", @@ -3299,8 +3344,8 @@ "title":"Viewing the Host Dashboard", "uri":"admin_guide_000052.html", "doc_type":"usermanual", - "p_code":"365", - "code":"367" + "p_code":"370", + "code":"372" }, { "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", @@ -3308,8 +3353,8 @@ "title":"Checking Host Processes and Resources", "uri":"admin_guide_000053.html", "doc_type":"usermanual", - "p_code":"365", - "code":"368" + "p_code":"370", + "code":"373" }, { "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 +3362,8 @@ "title":"Host Maintenance Operations", "uri":"admin_guide_000054.html", "doc_type":"usermanual", - "p_code":"364", - "code":"369" + "p_code":"369", + "code":"374" }, { "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 ", @@ -3326,8 +3371,8 @@ "title":"Starting and Stopping All Instances on a Host", "uri":"admin_guide_000056.html", "doc_type":"usermanual", - "p_code":"369", - "code":"370" + "p_code":"374", + "code":"375" }, { "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", @@ -3335,8 +3380,8 @@ "title":"Performing a Host Health Check", "uri":"admin_guide_000057.html", "doc_type":"usermanual", - "p_code":"369", - "code":"371" + "p_code":"374", + "code":"376" }, { "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 ", @@ -3344,8 +3389,8 @@ "title":"Configuring Racks for Hosts", "uri":"admin_guide_000058.html", "doc_type":"usermanual", - "p_code":"369", - "code":"372" + "p_code":"374", + "code":"377" }, { "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", @@ -3353,8 +3398,8 @@ "title":"Isolating a Host", "uri":"admin_guide_000059.html", "doc_type":"usermanual", - "p_code":"369", - "code":"373" + "p_code":"374", + "code":"378" }, { "desc":"Administrators can export information about all hosts on MRS Manager.", @@ -3362,8 +3407,8 @@ "title":"Exporting Host Information", "uri":"admin_guide_000062.html", "doc_type":"usermanual", - "p_code":"369", - "code":"374" + "p_code":"374", + "code":"379" }, { "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,8 +3416,8 @@ "title":"Resource Overview", "uri":"admin_guide_000063.html", "doc_type":"usermanual", - "p_code":"364", - "code":"375" + "p_code":"369", + "code":"380" }, { "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", @@ -3380,8 +3425,8 @@ "title":"Distribution", "uri":"admin_guide_000064.html", "doc_type":"usermanual", - "p_code":"375", - "code":"376" + "p_code":"380", + "code":"381" }, { "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", @@ -3389,8 +3434,8 @@ "title":"Trend", "uri":"admin_guide_000065.html", "doc_type":"usermanual", - "p_code":"375", - "code":"377" + "p_code":"380", + "code":"382" }, { "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", @@ -3398,8 +3443,8 @@ "title":"Cluster", "uri":"admin_guide_000066.html", "doc_type":"usermanual", - "p_code":"375", - "code":"378" + "p_code":"380", + "code":"383" }, { "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 ", @@ -3407,8 +3452,8 @@ "title":"Host", "uri":"admin_guide_000067.html", "doc_type":"usermanual", - "p_code":"375", - "code":"379" + "p_code":"380", + "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.", @@ -3416,8 +3461,8 @@ "title":"O&M", "uri":"admin_guide_000068.html", "doc_type":"usermanual", - "p_code":"319", - "code":"380" + "p_code":"324", + "code":"385" }, { "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 +3470,8 @@ "title":"Alarms", "uri":"admin_guide_000069.html", "doc_type":"usermanual", - "p_code":"380", - "code":"381" + "p_code":"385", + "code":"386" }, { "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", @@ -3434,8 +3479,8 @@ "title":"Overview of Alarms and Events", "uri":"admin_guide_000070.html", "doc_type":"usermanual", - "p_code":"381", - "code":"382" + "p_code":"386", + "code":"387" }, { "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", @@ -3443,8 +3488,8 @@ "title":"Configuring the Threshold", "uri":"admin_guide_000071.html", "doc_type":"usermanual", - "p_code":"381", - "code":"383" + "p_code":"386", + "code":"388" }, { "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", @@ -3452,8 +3497,8 @@ "title":"Configuring the Alarm Masking Status", "uri":"admin_guide_000072.html", "doc_type":"usermanual", - "p_code":"381", - "code":"384" + "p_code":"386", + "code":"389" }, { "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,8 +3506,8 @@ "title":"Log", "uri":"admin_guide_000073.html", "doc_type":"usermanual", - "p_code":"380", - "code":"385" + "p_code":"385", + "code":"390" }, { "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 ", @@ -3470,8 +3515,8 @@ "title":"Log Online Search", "uri":"admin_guide_000074.html", "doc_type":"usermanual", - "p_code":"385", - "code":"386" + "p_code":"390", + "code":"391" }, { "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", @@ -3479,8 +3524,8 @@ "title":"Log Download", "uri":"admin_guide_000075.html", "doc_type":"usermanual", - "p_code":"385", - "code":"387" + "p_code":"390", + "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.", @@ -3488,8 +3533,8 @@ "title":"Perform a Health Check", "uri":"admin_guide_000076.html", "doc_type":"usermanual", - "p_code":"380", - "code":"388" + "p_code":"385", + "code":"393" }, { "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", @@ -3497,8 +3542,8 @@ "title":"Viewing a Health Check Task", "uri":"admin_guide_000077.html", "doc_type":"usermanual", - "p_code":"388", - "code":"389" + "p_code":"393", + "code":"394" }, { "desc":"MRS Manager allows you to download and delete health check reports.", @@ -3506,8 +3551,8 @@ "title":"Managing Health Check Reports", "uri":"admin_guide_000078.html", "doc_type":"usermanual", - "p_code":"388", - "code":"390" + "p_code":"393", + "code":"395" }, { "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", @@ -3515,8 +3560,8 @@ "title":"Modifying Health Check Configuration", "uri":"admin_guide_000079.html", "doc_type":"usermanual", - "p_code":"388", - "code":"391" + "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.", @@ -3524,8 +3569,8 @@ "title":"Configuring Backup and Backup Restoration", "uri":"admin_guide_000080.html", "doc_type":"usermanual", - "p_code":"380", - "code":"392" + "p_code":"385", + "code":"397" }, { "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 ", @@ -3533,8 +3578,8 @@ "title":"Creating a Backup Task", "uri":"admin_guide_000081.html", "doc_type":"usermanual", - "p_code":"392", - "code":"393" + "p_code":"397", + "code":"398" }, { "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", @@ -3542,8 +3587,8 @@ "title":"Creating a Backup Restoration Task", "uri":"admin_guide_000082.html", "doc_type":"usermanual", - "p_code":"392", - "code":"394" + "p_code":"397", + "code":"399" }, { "desc":"You can also maintain and manage backup restoration tasks on MRS Manager.", @@ -3551,8 +3596,8 @@ "title":"Managing Backup and Backup Restoration Tasks", "uri":"admin_guide_000083.html", "doc_type":"usermanual", - "p_code":"392", - "code":"395" + "p_code":"397", + "code":"400" }, { "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.", @@ -3560,8 +3605,8 @@ "title":"Audit", "uri":"admin_guide_000084.html", "doc_type":"usermanual", - "p_code":"319", - "code":"396" + "p_code":"324", + "code":"401" }, { "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", @@ -3569,8 +3614,8 @@ "title":"Overview", "uri":"admin_guide_000085.html", "doc_type":"usermanual", - "p_code":"396", - "code":"397" + "p_code":"401", + "code":"402" }, { "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", @@ -3578,8 +3623,8 @@ "title":"Configuring Audit Log Dumping", "uri":"admin_guide_000086.html", "doc_type":"usermanual", - "p_code":"396", - "code":"398" + "p_code":"401", + "code":"403" }, { "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.", @@ -3587,8 +3632,8 @@ "title":"Tenant Resources", "uri":"admin_guide_000087.html", "doc_type":"usermanual", - "p_code":"319", - "code":"399" + "p_code":"324", + "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.", @@ -3596,8 +3641,8 @@ "title":"Multi-Tenancy", "uri":"admin_guide_000088.html", "doc_type":"usermanual", - "p_code":"399", - "code":"400" + "p_code":"404", + "code":"405" }, { "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", @@ -3605,8 +3650,8 @@ "title":"Overview", "uri":"admin_guide_000089.html", "doc_type":"usermanual", - "p_code":"400", - "code":"401" + "p_code":"405", + "code":"406" }, { "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,8 +3659,8 @@ "title":"Technical Principles", "uri":"admin_guide_000090.html", "doc_type":"usermanual", - "p_code":"400", - "code":"402" + "p_code":"405", + "code":"407" }, { "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", @@ -3623,8 +3668,8 @@ "title":"Multi-Tenant Management", "uri":"admin_guide_000091.html", "doc_type":"usermanual", - "p_code":"402", - "code":"403" + "p_code":"407", + "code":"408" }, { "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", @@ -3632,8 +3677,8 @@ "title":"Multi-Tenant Model", "uri":"admin_guide_000092.html", "doc_type":"usermanual", - "p_code":"402", - "code":"404" + "p_code":"407", + "code":"409" }, { "desc":"MRS cluster resources are classified into computing resources and storage resources. The multi-tenant architecture implements resource isolation.Computing resourcesComput", @@ -3641,8 +3686,8 @@ "title":"Resource Overview", "uri":"admin_guide_000093.html", "doc_type":"usermanual", - "p_code":"402", - "code":"405" + "p_code":"407", + "code":"410" }, { "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", @@ -3650,8 +3695,8 @@ "title":"Dynamic Resources", "uri":"admin_guide_000094.html", "doc_type":"usermanual", - "p_code":"402", - "code":"406" + "p_code":"407", + "code":"411" }, { "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", @@ -3659,8 +3704,8 @@ "title":"Storage Resources", "uri":"admin_guide_000095.html", "doc_type":"usermanual", - "p_code":"402", - "code":"407" + "p_code":"407", + "code":"412" }, { "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.", @@ -3668,8 +3713,8 @@ "title":"Multi-Tenancy Usage", "uri":"admin_guide_000096.html", "doc_type":"usermanual", - "p_code":"400", - "code":"408" + "p_code":"405", + "code":"413" }, { "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", @@ -3677,8 +3722,8 @@ "title":"Overview", "uri":"admin_guide_000097.html", "doc_type":"usermanual", - "p_code":"408", - "code":"409" + "p_code":"413", + "code":"414" }, { "desc":"Administrators need to determine the service scenarios of cluster resources and then plan tenants. After that, administrators add tenants and configure dynamic resources,", @@ -3686,8 +3731,8 @@ "title":"Process Overview", "uri":"admin_guide_000098.html", "doc_type":"usermanual", - "p_code":"408", - "code":"410" + "p_code":"413", + "code":"415" }, { "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 +3740,8 @@ "title":"Using the Superior Scheduler", "uri":"admin_guide_000099.html", "doc_type":"usermanual", - "p_code":"399", - "code":"411" + "p_code":"404", + "code":"416" }, { "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.", @@ -3704,8 +3749,8 @@ "title":"Creating Tenants", "uri":"admin_guide_000100.html", "doc_type":"usermanual", - "p_code":"411", - "code":"412" + "p_code":"416", + "code":"417" }, { "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", @@ -3713,8 +3758,8 @@ "title":"Adding a Tenant", "uri":"admin_guide_000101.html", "doc_type":"usermanual", - "p_code":"412", - "code":"413" + "p_code":"417", + "code":"418" }, { "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", @@ -3722,8 +3767,8 @@ "title":"Adding a Sub-Tenant", "uri":"admin_guide_000102.html", "doc_type":"usermanual", - "p_code":"412", - "code":"414" + "p_code":"417", + "code":"419" }, { "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", @@ -3731,8 +3776,8 @@ "title":"Adding a User and Binding the User to a Tenant Role", "uri":"admin_guide_000103.html", "doc_type":"usermanual", - "p_code":"412", - "code":"415" + "p_code":"417", + "code":"420" }, { "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.", @@ -3740,8 +3785,8 @@ "title":"Managing Tenants", "uri":"admin_guide_000104.html", "doc_type":"usermanual", - "p_code":"411", - "code":"416" + "p_code":"416", + "code":"421" }, { "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", @@ -3749,8 +3794,8 @@ "title":"Managing Tenant Directories", "uri":"admin_guide_000105.html", "doc_type":"usermanual", - "p_code":"416", - "code":"417" + "p_code":"421", + "code":"422" }, { "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", @@ -3758,8 +3803,8 @@ "title":"Restoring Tenant Data", "uri":"admin_guide_000106.html", "doc_type":"usermanual", - "p_code":"416", - "code":"418" + "p_code":"421", + "code":"423" }, { "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", @@ -3767,8 +3812,8 @@ "title":"Deleting a Tenant", "uri":"admin_guide_000107.html", "doc_type":"usermanual", - "p_code":"416", - "code":"419" + "p_code":"421", + "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.", @@ -3776,8 +3821,8 @@ "title":"Managing Resources", "uri":"admin_guide_000108.html", "doc_type":"usermanual", - "p_code":"411", - "code":"420" + "p_code":"416", + "code":"425" }, { "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", @@ -3785,8 +3830,8 @@ "title":"Adding a Resource Pool", "uri":"admin_guide_000109.html", "doc_type":"usermanual", - "p_code":"420", - "code":"421" + "p_code":"425", + "code":"426" }, { "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", @@ -3794,8 +3839,8 @@ "title":"Modifying a Resource Pool", "uri":"admin_guide_000110.html", "doc_type":"usermanual", - "p_code":"420", - "code":"422" + "p_code":"425", + "code":"427" }, { "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", @@ -3803,8 +3848,8 @@ "title":"Deleting a Resource Pool", "uri":"admin_guide_000111.html", "doc_type":"usermanual", - "p_code":"420", - "code":"423" + "p_code":"425", + "code":"428" }, { "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", @@ -3812,8 +3857,8 @@ "title":"Configuring a Queue", "uri":"admin_guide_000112.html", "doc_type":"usermanual", - "p_code":"420", - "code":"424" + "p_code":"425", + "code":"429" }, { "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", @@ -3821,8 +3866,8 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"admin_guide_000113.html", "doc_type":"usermanual", - "p_code":"420", - "code":"425" + "p_code":"425", + "code":"430" }, { "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", @@ -3830,8 +3875,8 @@ "title":"Clearing Queue Configurations", "uri":"admin_guide_000114.html", "doc_type":"usermanual", - "p_code":"420", - "code":"426" + "p_code":"425", + "code":"431" }, { "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", @@ -3839,8 +3884,8 @@ "title":"Managing Global User Policies", "uri":"admin_guide_000115.html", "doc_type":"usermanual", - "p_code":"411", - "code":"427" + "p_code":"416", + "code":"432" }, { "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.", @@ -3848,8 +3893,8 @@ "title":"Using the Capacity Scheduler", "uri":"admin_guide_000116.html", "doc_type":"usermanual", - "p_code":"399", - "code":"428" + "p_code":"404", + "code":"433" }, { "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.", @@ -3857,8 +3902,8 @@ "title":"Creating Tenants", "uri":"admin_guide_000117.html", "doc_type":"usermanual", - "p_code":"428", - "code":"429" + "p_code":"433", + "code":"434" }, { "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", @@ -3866,8 +3911,8 @@ "title":"Adding a Tenant", "uri":"admin_guide_000118.html", "doc_type":"usermanual", - "p_code":"429", - "code":"430" + "p_code":"434", + "code":"435" }, { "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", @@ -3875,8 +3920,8 @@ "title":"Adding a Sub-Tenant", "uri":"admin_guide_000119.html", "doc_type":"usermanual", - "p_code":"429", - "code":"431" + "p_code":"434", + "code":"436" }, { "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", @@ -3884,8 +3929,8 @@ "title":"Adding a User and Binding the User to a Tenant Role", "uri":"admin_guide_000120.html", "doc_type":"usermanual", - "p_code":"429", - "code":"432" + "p_code":"434", + "code":"437" }, { "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,8 +3938,8 @@ "title":"Managing Tenants", "uri":"admin_guide_000121.html", "doc_type":"usermanual", - "p_code":"428", - "code":"433" + "p_code":"433", + "code":"438" }, { "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", @@ -3902,8 +3947,8 @@ "title":"Managing Tenant Directories", "uri":"admin_guide_000122.html", "doc_type":"usermanual", - "p_code":"433", - "code":"434" + "p_code":"438", + "code":"439" }, { "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", @@ -3911,8 +3956,8 @@ "title":"Restoring Tenant Data", "uri":"admin_guide_000123.html", "doc_type":"usermanual", - "p_code":"433", - "code":"435" + "p_code":"438", + "code":"440" }, { "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", @@ -3920,8 +3965,8 @@ "title":"Deleting a Tenant", "uri":"admin_guide_000124.html", "doc_type":"usermanual", - "p_code":"433", - "code":"436" + "p_code":"438", + "code":"441" }, { "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", @@ -3929,8 +3974,8 @@ "title":"Clearing Non-associated Queues of a Tenant", "uri":"admin_guide_000125.html", "doc_type":"usermanual", - "p_code":"433", - "code":"437" + "p_code":"438", + "code":"442" }, { "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.", @@ -3938,8 +3983,8 @@ "title":"Managing Resources", "uri":"admin_guide_000126.html", "doc_type":"usermanual", - "p_code":"428", - "code":"438" + "p_code":"433", + "code":"443" }, { "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", @@ -3947,8 +3992,8 @@ "title":"Adding a Resource Pool", "uri":"admin_guide_000127.html", "doc_type":"usermanual", - "p_code":"438", - "code":"439" + "p_code":"443", + "code":"444" }, { "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", @@ -3956,8 +4001,8 @@ "title":"Modifying a Resource Pool", "uri":"admin_guide_000128.html", "doc_type":"usermanual", - "p_code":"438", - "code":"440" + "p_code":"443", + "code":"445" }, { "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", @@ -3965,8 +4010,8 @@ "title":"Deleting a Resource Pool", "uri":"admin_guide_000129.html", "doc_type":"usermanual", - "p_code":"438", - "code":"441" + "p_code":"443", + "code":"446" }, { "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", @@ -3974,8 +4019,8 @@ "title":"Configuring a Queue", "uri":"admin_guide_000130.html", "doc_type":"usermanual", - "p_code":"438", - "code":"442" + "p_code":"443", + "code":"447" }, { "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", @@ -3983,8 +4028,8 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"admin_guide_000131.html", "doc_type":"usermanual", - "p_code":"438", - "code":"443" + "p_code":"443", + "code":"448" }, { "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", @@ -3992,8 +4037,8 @@ "title":"Clearing Queue Configurations", "uri":"admin_guide_000132.html", "doc_type":"usermanual", - "p_code":"438", - "code":"444" + "p_code":"443", + "code":"449" }, { "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", @@ -4001,8 +4046,8 @@ "title":"Switching the Scheduler", "uri":"admin_guide_000133.html", "doc_type":"usermanual", - "p_code":"399", - "code":"445" + "p_code":"404", + "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.", @@ -4010,8 +4055,8 @@ "title":"System Configuration", "uri":"admin_guide_000134.html", "doc_type":"usermanual", - "p_code":"319", - "code":"446" + "p_code":"324", + "code":"451" }, { "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 +4064,8 @@ "title":"Configuring Permissions", "uri":"admin_guide_000135.html", "doc_type":"usermanual", - "p_code":"446", - "code":"447" + "p_code":"451", + "code":"452" }, { "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.", @@ -4028,8 +4073,8 @@ "title":"Managing Users", "uri":"admin_guide_000136.html", "doc_type":"usermanual", - "p_code":"447", - "code":"448" + "p_code":"452", + "code":"453" }, { "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", @@ -4037,8 +4082,8 @@ "title":"Creating a User", "uri":"admin_guide_000137.html", "doc_type":"usermanual", - "p_code":"448", - "code":"449" + "p_code":"453", + "code":"454" }, { "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", @@ -4046,8 +4091,8 @@ "title":"Modifying User Information", "uri":"admin_guide_000138.html", "doc_type":"usermanual", - "p_code":"448", - "code":"450" + "p_code":"453", + "code":"455" }, { "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 ", @@ -4055,8 +4100,8 @@ "title":"Exporting User Information", "uri":"admin_guide_000139.html", "doc_type":"usermanual", - "p_code":"448", - "code":"451" + "p_code":"453", + "code":"456" }, { "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", @@ -4064,8 +4109,8 @@ "title":"Locking a User", "uri":"admin_guide_000140.html", "doc_type":"usermanual", - "p_code":"448", - "code":"452" + "p_code":"453", + "code":"457" }, { "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", @@ -4073,8 +4118,8 @@ "title":"Unlocking a User", "uri":"admin_guide_000141.html", "doc_type":"usermanual", - "p_code":"448", - "code":"453" + "p_code":"453", + "code":"458" }, { "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", @@ -4082,8 +4127,8 @@ "title":"Deleting a User", "uri":"admin_guide_000142.html", "doc_type":"usermanual", - "p_code":"448", - "code":"454" + "p_code":"453", + "code":"459" }, { "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 ", @@ -4091,8 +4136,8 @@ "title":"Changing a User Password", "uri":"admin_guide_000143.html", "doc_type":"usermanual", - "p_code":"448", - "code":"455" + "p_code":"453", + "code":"460" }, { "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", @@ -4100,8 +4145,8 @@ "title":"Initializing a Password", "uri":"admin_guide_000144.html", "doc_type":"usermanual", - "p_code":"448", - "code":"456" + "p_code":"453", + "code":"461" }, { "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 ", @@ -4109,8 +4154,8 @@ "title":"Exporting an Authentication Credential File", "uri":"admin_guide_000145.html", "doc_type":"usermanual", - "p_code":"448", - "code":"457" + "p_code":"453", + "code":"462" }, { "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", @@ -4118,8 +4163,8 @@ "title":"Managing User Groups", "uri":"admin_guide_000147.html", "doc_type":"usermanual", - "p_code":"447", - "code":"458" + "p_code":"452", + "code":"463" }, { "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", @@ -4127,8 +4172,8 @@ "title":"Managing Roles", "uri":"admin_guide_000148.html", "doc_type":"usermanual", - "p_code":"447", - "code":"459" + "p_code":"452", + "code":"464" }, { "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 +4181,8 @@ "title":"Security Policies", "uri":"admin_guide_000149.html", "doc_type":"usermanual", - "p_code":"447", - "code":"460" + "p_code":"452", + "code":"465" }, { "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", @@ -4145,8 +4190,8 @@ "title":"Configuring Password Policies", "uri":"admin_guide_000150.html", "doc_type":"usermanual", - "p_code":"460", - "code":"461" + "p_code":"465", + "code":"466" }, { "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", @@ -4154,8 +4199,8 @@ "title":"Configuring the Independent Attribute", "uri":"admin_guide_000151.html", "doc_type":"usermanual", - "p_code":"460", - "code":"462" + "p_code":"465", + "code":"467" }, { "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.", @@ -4163,8 +4208,8 @@ "title":"Configuring Interconnections", "uri":"admin_guide_000153.html", "doc_type":"usermanual", - "p_code":"446", - "code":"463" + "p_code":"451", + "code":"468" }, { "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 ", @@ -4172,8 +4217,8 @@ "title":"Configuring SNMP Northbound Parameters", "uri":"admin_guide_000154.html", "doc_type":"usermanual", - "p_code":"463", - "code":"464" + "p_code":"468", + "code":"469" }, { "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", @@ -4181,8 +4226,8 @@ "title":"Configuring Syslog Northbound Parameters", "uri":"admin_guide_000155.html", "doc_type":"usermanual", - "p_code":"463", - "code":"465" + "p_code":"468", + "code":"470" }, { "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.", @@ -4190,8 +4235,8 @@ "title":"Configuring Monitoring Metric Dumping", "uri":"admin_guide_000156.html", "doc_type":"usermanual", - "p_code":"463", - "code":"466" + "p_code":"468", + "code":"471" }, { "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", @@ -4199,8 +4244,8 @@ "title":"Importing a Certificate", "uri":"admin_guide_000157.html", "doc_type":"usermanual", - "p_code":"446", - "code":"467" + "p_code":"451", + "code":"472" }, { "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,8 +4253,8 @@ "title":"OMS Management", "uri":"admin_guide_000159.html", "doc_type":"usermanual", - "p_code":"446", - "code":"468" + "p_code":"451", + "code":"473" }, { "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 ", @@ -4217,8 +4262,8 @@ "title":"Overview of the OMS Page", "uri":"admin_guide_000160.html", "doc_type":"usermanual", - "p_code":"468", - "code":"469" + "p_code":"473", + "code":"474" }, { "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", @@ -4226,8 +4271,8 @@ "title":"Modifying OMS Service Configuration Parameters", "uri":"admin_guide_000162.html", "doc_type":"usermanual", - "p_code":"468", - "code":"470" + "p_code":"473", + "code":"475" }, { "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.", @@ -4235,8 +4280,8 @@ "title":"Component Management", "uri":"admin_guide_000164.html", "doc_type":"usermanual", - "p_code":"446", - "code":"471" + "p_code":"451", + "code":"476" }, { "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", @@ -4244,8 +4289,8 @@ "title":"Viewing Component Packages", "uri":"admin_guide_000165.html", "doc_type":"usermanual", - "p_code":"471", - "code":"472" + "p_code":"476", + "code":"477" }, { "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.", @@ -4253,8 +4298,8 @@ "title":"Cluster Management", "uri":"admin_guide_000166.html", "doc_type":"usermanual", - "p_code":"319", - "code":"473" + "p_code":"324", + "code":"478" }, { "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.", @@ -4262,8 +4307,8 @@ "title":"Configuring Client", "uri":"admin_guide_000170.html", "doc_type":"usermanual", - "p_code":"473", - "code":"474" + "p_code":"478", + "code":"479" }, { "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", @@ -4271,8 +4316,8 @@ "title":"Installing a Client", "uri":"admin_guide_000171.html", "doc_type":"usermanual", - "p_code":"474", - "code":"475" + "p_code":"479", + "code":"480" }, { "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", @@ -4280,8 +4325,8 @@ "title":"Using a Client", "uri":"admin_guide_000172.html", "doc_type":"usermanual", - "p_code":"474", - "code":"476" + "p_code":"479", + "code":"481" }, { "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", @@ -4289,8 +4334,8 @@ "title":"Updating the Configuration of an Installed Client", "uri":"admin_guide_000173.html", "doc_type":"usermanual", - "p_code":"474", - "code":"477" + "p_code":"479", + "code":"482" }, { "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.", @@ -4298,8 +4343,8 @@ "title":"Cluster Mutual Trust Management", "uri":"admin_guide_000174.html", "doc_type":"usermanual", - "p_code":"473", - "code":"478" + "p_code":"478", + "code":"483" }, { "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 ", @@ -4307,8 +4352,8 @@ "title":"Overview of Mutual Trust Between Clusters", "uri":"admin_guide_000175.html", "doc_type":"usermanual", - "p_code":"478", - "code":"479" + "p_code":"483", + "code":"484" }, { "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", @@ -4316,8 +4361,8 @@ "title":"Changing Manager's Domain Name", "uri":"admin_guide_000176.html", "doc_type":"usermanual", - "p_code":"478", - "code":"480" + "p_code":"483", + "code":"485" }, { "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", @@ -4325,8 +4370,8 @@ "title":"Configuring Cross-Manager Mutual Trust Between Clusters", "uri":"admin_guide_000177.html", "doc_type":"usermanual", - "p_code":"478", - "code":"481" + "p_code":"483", + "code":"486" }, { "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 ", @@ -4334,8 +4379,8 @@ "title":"Assigning User Permissions After Cross-Cluster Mutual Trust Is Configured", "uri":"admin_guide_000178.html", "doc_type":"usermanual", - "p_code":"478", - "code":"482" + "p_code":"483", + "code":"487" }, { "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", @@ -4343,8 +4388,8 @@ "title":"Configuring Scheduled Backup of Alarm and Audit Information", "uri":"admin_guide_000182.html", "doc_type":"usermanual", - "p_code":"473", - "code":"483" + "p_code":"478", + "code":"488" }, { "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", @@ -4352,8 +4397,8 @@ "title":"Modifying the MRS Manager Routing Table", "uri":"admin_guide_000183.html", "doc_type":"usermanual", - "p_code":"473", - "code":"484" + "p_code":"478", + "code":"489" }, { "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 ", @@ -4361,8 +4406,8 @@ "title":"Switching to the Maintenance Mode", "uri":"admin_guide_000189.html", "doc_type":"usermanual", - "p_code":"473", - "code":"485" + "p_code":"478", + "code":"490" }, { "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 ", @@ -4370,8 +4415,8 @@ "title":"Routine Maintenance", "uri":"admin_guide_000191.html", "doc_type":"usermanual", - "p_code":"473", - "code":"486" + "p_code":"478", + "code":"491" }, { "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.", @@ -4379,8 +4424,8 @@ "title":"Log Management", "uri":"admin_guide_000192.html", "doc_type":"usermanual", - "p_code":"319", - "code":"487" + "p_code":"324", + "code":"492" }, { "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", @@ -4388,8 +4433,8 @@ "title":"About Logs", "uri":"admin_guide_000193.html", "doc_type":"usermanual", - "p_code":"487", - "code":"488" + "p_code":"492", + "code":"493" }, { "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", @@ -4397,8 +4442,8 @@ "title":"Manager Log List", "uri":"admin_guide_000194.html", "doc_type":"usermanual", - "p_code":"487", - "code":"489" + "p_code":"492", + "code":"494" }, { "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", @@ -4406,8 +4451,8 @@ "title":"Configuring the Log Level and Log File Size", "uri":"admin_guide_000195.html", "doc_type":"usermanual", - "p_code":"487", - "code":"490" + "p_code":"492", + "code":"495" }, { "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 ", @@ -4415,8 +4460,8 @@ "title":"Configuring the Number of Local Audit Log Backups", "uri":"admin_guide_000196.html", "doc_type":"usermanual", - "p_code":"487", - "code":"491" + "p_code":"492", + "code":"496" }, { "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", @@ -4424,8 +4469,8 @@ "title":"Viewing Role Instance Logs", "uri":"admin_guide_000197.html", "doc_type":"usermanual", - "p_code":"487", - "code":"492" + "p_code":"492", + "code":"497" }, { "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.", @@ -4433,8 +4478,8 @@ "title":"Backup and Recovery Management", "uri":"admin_guide_000198.html", "doc_type":"usermanual", - "p_code":"319", - "code":"493" + "p_code":"324", + "code":"498" }, { "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 ", @@ -4442,8 +4487,8 @@ "title":"Introduction", "uri":"admin_guide_000399.html", "doc_type":"usermanual", - "p_code":"493", - "code":"494" + "p_code":"498", + "code":"499" }, { "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.", @@ -4451,8 +4496,8 @@ "title":"Backing Up Data", "uri":"admin_guide_000201.html", "doc_type":"usermanual", - "p_code":"493", - "code":"495" + "p_code":"498", + "code":"500" }, { "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", @@ -4460,8 +4505,8 @@ "title":"Backing Up Manager Data", "uri":"admin_guide_000202.html", "doc_type":"usermanual", - "p_code":"495", - "code":"496" + "p_code":"500", + "code":"501" }, { "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", @@ -4469,8 +4514,8 @@ "title":"Backing Up CDL Data", "uri":"admin_guide_000343.html", "doc_type":"usermanual", - "p_code":"495", - "code":"497" + "p_code":"500", + "code":"502" }, { "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", @@ -4478,8 +4523,8 @@ "title":"Backing Up ClickHouse Metadata", "uri":"admin_guide_000348.html", "doc_type":"usermanual", - "p_code":"495", - "code":"498" + "p_code":"500", + "code":"503" }, { "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", @@ -4487,8 +4532,8 @@ "title":"Backing Up ClickHouse Service Data", "uri":"admin_guide_000349.html", "doc_type":"usermanual", - "p_code":"495", - "code":"499" + "p_code":"500", + "code":"504" }, { "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", @@ -4496,8 +4541,17 @@ "title":"Backing Up DBService Data", "uri":"admin_guide_000203.html", "doc_type":"usermanual", - "p_code":"495", - "code":"500" + "p_code":"500", + "code":"505" + }, + { + "desc":"To ensure Doris service data security, you need to back up Doris service data especially before you perform a major operation on Doris (such as upgrade or migration). The", + "product_code":"mrs", + "title":"Backing Up Doris Data", + "uri":"admin_guide_000423.html", + "doc_type":"usermanual", + "p_code":"500", + "code":"506" }, { "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", @@ -4505,8 +4559,8 @@ "title":"Backing Up HBase Metadata", "uri":"admin_guide_000204.html", "doc_type":"usermanual", - "p_code":"495", - "code":"501" + "p_code":"500", + "code":"507" }, { "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", @@ -4514,8 +4568,8 @@ "title":"Backing Up HBase Service Data", "uri":"admin_guide_000205.html", "doc_type":"usermanual", - "p_code":"495", - "code":"502" + "p_code":"500", + "code":"508" }, { "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", @@ -4523,8 +4577,8 @@ "title":"Backing Up NameNode Data", "uri":"admin_guide_000208.html", "doc_type":"usermanual", - "p_code":"495", - "code":"503" + "p_code":"500", + "code":"509" }, { "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 ", @@ -4532,8 +4586,8 @@ "title":"Backing Up HDFS Service Data", "uri":"admin_guide_000209.html", "doc_type":"usermanual", - "p_code":"495", - "code":"504" + "p_code":"500", + "code":"510" }, { "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 ", @@ -4541,8 +4595,8 @@ "title":"Backing Up Hive Service Data", "uri":"admin_guide_000210.html", "doc_type":"usermanual", - "p_code":"495", - "code":"505" + "p_code":"500", + "code":"511" }, { "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 ", @@ -4550,8 +4604,8 @@ "title":"Backing Up IoTDB Metadata", "uri":"admin_guide_000350.html", "doc_type":"usermanual", - "p_code":"495", - "code":"506" + "p_code":"500", + "code":"512" }, { "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", @@ -4559,8 +4613,8 @@ "title":"Backing Up IoTDB Service Data", "uri":"admin_guide_000360.html", "doc_type":"usermanual", - "p_code":"495", - "code":"507" + "p_code":"500", + "code":"513" }, { "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", @@ -4568,8 +4622,8 @@ "title":"Backing Up Kafka Metadata", "uri":"admin_guide_000211.html", "doc_type":"usermanual", - "p_code":"495", - "code":"508" + "p_code":"500", + "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.", @@ -4577,8 +4631,8 @@ "title":"Recovering Data", "uri":"admin_guide_000215.html", "doc_type":"usermanual", - "p_code":"493", - "code":"509" + "p_code":"498", + "code":"515" }, { "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", @@ -4586,8 +4640,8 @@ "title":"Restoring Manager Data", "uri":"admin_guide_000216.html", "doc_type":"usermanual", - "p_code":"509", - "code":"510" + "p_code":"515", + "code":"516" }, { "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", @@ -4595,8 +4649,8 @@ "title":"Restoring CDL Data", "uri":"admin_guide_000345.html", "doc_type":"usermanual", - "p_code":"509", - "code":"511" + "p_code":"515", + "code":"517" }, { "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", @@ -4604,8 +4658,8 @@ "title":"Restoring ClickHouse Metadata", "uri":"admin_guide_000358.html", "doc_type":"usermanual", - "p_code":"509", - "code":"512" + "p_code":"515", + "code":"518" }, { "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", @@ -4613,8 +4667,8 @@ "title":"Restoring ClickHouse Service Data", "uri":"admin_guide_000359.html", "doc_type":"usermanual", - "p_code":"509", - "code":"513" + "p_code":"515", + "code":"519" }, { "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", @@ -4622,8 +4676,17 @@ "title":"Restoring DBService data", "uri":"admin_guide_000217.html", "doc_type":"usermanual", - "p_code":"509", - "code":"514" + "p_code":"515", + "code":"520" + }, + { + "desc":"Doris 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", + "product_code":"mrs", + "title":"Restoring Doris Service Data", + "uri":"admin_guide_000424.html", + "doc_type":"usermanual", + "p_code":"515", + "code":"521" }, { "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", @@ -4631,8 +4694,8 @@ "title":"Restoring HBase Metadata", "uri":"admin_guide_000218.html", "doc_type":"usermanual", - "p_code":"509", - "code":"515" + "p_code":"515", + "code":"522" }, { "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", @@ -4640,8 +4703,8 @@ "title":"Restoring HBase Service Data", "uri":"admin_guide_000219.html", "doc_type":"usermanual", - "p_code":"509", - "code":"516" + "p_code":"515", + "code":"523" }, { "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", @@ -4649,8 +4712,8 @@ "title":"Restoring NameNode Data", "uri":"admin_guide_000222.html", "doc_type":"usermanual", - "p_code":"509", - "code":"517" + "p_code":"515", + "code":"524" }, { "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", @@ -4658,8 +4721,8 @@ "title":"Restoring HDFS Service Data", "uri":"admin_guide_000223.html", "doc_type":"usermanual", - "p_code":"509", - "code":"518" + "p_code":"515", + "code":"525" }, { "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", @@ -4667,8 +4730,8 @@ "title":"Restoring Hive Service Data", "uri":"admin_guide_000224.html", "doc_type":"usermanual", - "p_code":"509", - "code":"519" + "p_code":"515", + "code":"526" }, { "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", @@ -4676,8 +4739,8 @@ "title":"Restoring IoTDB Metadata", "uri":"admin_guide_000351.html", "doc_type":"usermanual", - "p_code":"509", - "code":"520" + "p_code":"515", + "code":"527" }, { "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", @@ -4685,8 +4748,8 @@ "title":"Restoring IoTDB Service Data", "uri":"admin_guide_000361.html", "doc_type":"usermanual", - "p_code":"509", - "code":"521" + "p_code":"515", + "code":"528" }, { "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", @@ -4694,8 +4757,8 @@ "title":"Restoring Kafka Metadata", "uri":"admin_guide_000225.html", "doc_type":"usermanual", - "p_code":"509", - "code":"522" + "p_code":"515", + "code":"529" }, { "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", @@ -4703,8 +4766,8 @@ "title":"Enabling Cross-Cluster Replication", "uri":"admin_guide_000200.html", "doc_type":"usermanual", - "p_code":"493", - "code":"523" + "p_code":"498", + "code":"530" }, { "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,", @@ -4712,8 +4775,8 @@ "title":"Managing Local Quick Restoration Tasks", "uri":"admin_guide_000229.html", "doc_type":"usermanual", - "p_code":"493", - "code":"524" + "p_code":"498", + "code":"531" }, { "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", @@ -4721,8 +4784,8 @@ "title":"Modifying a Backup Task", "uri":"admin_guide_000230.html", "doc_type":"usermanual", - "p_code":"493", - "code":"525" + "p_code":"498", + "code":"532" }, { "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", @@ -4730,8 +4793,8 @@ "title":"Viewing Backup and Restoration Tasks", "uri":"admin_guide_000231.html", "doc_type":"usermanual", - "p_code":"493", - "code":"526" + "p_code":"498", + "code":"533" }, { "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", @@ -4739,71 +4802,80 @@ "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":"493", - "code":"527" + "p_code":"498", + "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.", - "product_code":"", + "product_code":"mrs", "title":"SQL Inspector", "uri":"admin_guide_000407.html", - "doc_type":"", - "p_code":"319", - "code":"528" + "doc_type":"usermanual", + "p_code":"324", + "code":"535" }, { "desc":"SQL engines in the big data field are emerging one after another. In addition to a wide range of solutions, some problems are exposed. For example, the quality of SQL inp", - "product_code":"", + "product_code":"mrs", "title":"Overview", "uri":"admin_guide_000408.html", - "doc_type":"", - "p_code":"528", - "code":"529" + "doc_type":"usermanual", + "p_code":"535", + "code":"536" }, { - "desc":"You can add rules for specified tenants and SQL engines on FusionInsight Manager. The system will display hints on, intercept, or block SQL requests matched by the rules.", - "product_code":"", + "desc":"You can add rules for specified tenants and SQL engines on MRS Manager. The system will display hints on, intercept, or block SQL requests matched by the rules.Exercise c", + "product_code":"mrs", "title":"Adding an SQL Inspection", "uri":"admin_guide_000409.html", - "doc_type":"", - "p_code":"528", - "code":"530" + "doc_type":"usermanual", + "p_code":"535", + "code":"537" }, { - "desc":"You can configure rules for Hive SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the Hive service has b", - "product_code":"", + "desc":"You can configure rules for Hive SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the Hive service has been instal", + "product_code":"mrs", "title":"Configuring Hive SQL Inspection", "uri":"admin_guide_000412.html", - "doc_type":"", - "p_code":"528", - "code":"531" + "doc_type":"usermanual", + "p_code":"535", + "code":"538" }, { - "desc":"You can configure rules for ClickHouse SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the ClickHouse s", - "product_code":"", + "desc":"You can configure rules for ClickHouse SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the ClickHouse service has", + "product_code":"mrs", "title":"Configuring ClickHouse SQL Inspection", "uri":"admin_guide_000413.html", - "doc_type":"", - "p_code":"528", - "code":"532" + "doc_type":"usermanual", + "p_code":"535", + "code":"539" }, { - "desc":"You can configure rules for HetuEngine SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the HetuEngine s", - "product_code":"", + "desc":"You can configure rules for HetuEngine SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the HetuEngine service has", + "product_code":"mrs", "title":"Configuring HetuEngine SQL Inspection", "uri":"admin_guide_000416.html", - "doc_type":"", - "p_code":"528", - "code":"533" + "doc_type":"usermanual", + "p_code":"535", + "code":"540" }, { - "desc":"You can configure rules for Spark SQL inspection on FusionInsight Manager and configure rule parameters as you need.The cluster client that contains the Spark service has", - "product_code":"", + "desc":"You can configure rules for Spark SQL inspection on MRS Manager and configure rule parameters as you need.The cluster client that contains the Spark service has been inst", + "product_code":"mrs", "title":"Configuring Spark SQL Inspection", "uri":"admin_guide_000414.html", - "doc_type":"", - "p_code":"528", - "code":"534" + "doc_type":"usermanual", + "p_code":"535", + "code":"541" + }, + { + "desc":"This function applies only to clusters of MRS 3.5.0 and later versions.You can configure inspection rules for Doris SQL statements on MRS Manager and set rule parameters ", + "product_code":"mrs", + "title":"Configuring Doris SQL Inspection", + "uri":"admin_guide_000427.html", + "doc_type":"usermanual", + "p_code":"535", + "code":"542" }, { "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.", @@ -4811,8 +4883,8 @@ "title":"Security Management", "uri":"admin_guide_000233.html", "doc_type":"usermanual", - "p_code":"319", - "code":"535" + "p_code":"324", + "code":"543" }, { "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.", @@ -4820,8 +4892,8 @@ "title":"Security Overview", "uri":"admin_guide_000234.html", "doc_type":"usermanual", - "p_code":"535", - "code":"536" + "p_code":"543", + "code":"544" }, { "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 ", @@ -4829,8 +4901,8 @@ "title":"Right Model", "uri":"admin_guide_000235.html", "doc_type":"usermanual", - "p_code":"536", - "code":"537" + "p_code":"544", + "code":"545" }, { "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", @@ -4838,8 +4910,8 @@ "title":"Right Mechanism", "uri":"admin_guide_000236.html", "doc_type":"usermanual", - "p_code":"536", - "code":"538" + "p_code":"544", + "code":"546" }, { "desc":"The big data platform performs user identity authentication to prevent invalid users from accessing the cluster. The cluster provides authentication capabilities in both ", @@ -4847,8 +4919,8 @@ "title":"Authentication Policies", "uri":"admin_guide_000237.html", "doc_type":"usermanual", - "p_code":"536", - "code":"539" + "p_code":"544", + "code":"547" }, { "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", @@ -4856,8 +4928,8 @@ "title":"Permission Verification Policies", "uri":"admin_guide_000238.html", "doc_type":"usermanual", - "p_code":"536", - "code":"540" + "p_code":"544", + "code":"548" }, { "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", @@ -4865,8 +4937,8 @@ "title":"User Account List", "uri":"admin_guide_000239.html", "doc_type":"usermanual", - "p_code":"536", - "code":"541" + "p_code":"544", + "code":"549" }, { "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", @@ -4874,8 +4946,8 @@ "title":"Default Permission Information", "uri":"admin_guide_000240.html", "doc_type":"usermanual", - "p_code":"536", - "code":"542" + "p_code":"544", + "code":"550" }, { "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", @@ -4883,8 +4955,8 @@ "title":"MRS Manager Security Functions", "uri":"admin_guide_000241.html", "doc_type":"usermanual", - "p_code":"536", - "code":"543" + "p_code":"544", + "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.", @@ -4892,8 +4964,8 @@ "title":"Account Management", "uri":"admin_guide_000242.html", "doc_type":"usermanual", - "p_code":"535", - "code":"544" + "p_code":"543", + "code":"552" }, { "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.", @@ -4901,8 +4973,8 @@ "title":"Account Security Settings", "uri":"admin_guide_000243.html", "doc_type":"usermanual", - "p_code":"544", - "code":"545" + "p_code":"552", + "code":"553" }, { "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 ", @@ -4910,8 +4982,8 @@ "title":"Unlocking LDAP Users and Management Accounts", "uri":"admin_guide_000245.html", "doc_type":"usermanual", - "p_code":"545", - "code":"546" + "p_code":"553", + "code":"554" }, { "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", @@ -4919,8 +4991,8 @@ "title":"Internal an Internal System User", "uri":"admin_guide_000246.html", "doc_type":"usermanual", - "p_code":"545", - "code":"547" + "p_code":"553", + "code":"555" }, { "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", @@ -4928,8 +5000,8 @@ "title":"Enabling and Disabling Permission Verification on Cluster Components", "uri":"admin_guide_000247.html", "doc_type":"usermanual", - "p_code":"545", - "code":"548" + "p_code":"553", + "code":"556" }, { "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 ", @@ -4937,8 +5009,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":"545", - "code":"549" + "p_code":"553", + "code":"557" }, { "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.", @@ -4946,8 +5018,8 @@ "title":"Changing the Password for a System User", "uri":"admin_guide_000249.html", "doc_type":"usermanual", - "p_code":"544", - "code":"550" + "p_code":"552", + "code":"558" }, { "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", @@ -4955,8 +5027,8 @@ "title":"Changing the Password for User admin", "uri":"admin_guide_000250.html", "doc_type":"usermanual", - "p_code":"550", - "code":"551" + "p_code":"558", + "code":"559" }, { "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", @@ -4964,8 +5036,17 @@ "title":"Changing the Password for an OS User", "uri":"admin_guide_000251.html", "doc_type":"usermanual", - "p_code":"550", - "code":"552" + "p_code":"558", + "code":"560" + }, + { + "desc":"By default, the password validity period of an OS user is 90 days. This topic describes how to change the validity period.You are advised to periodically change a user's ", + "product_code":"mrs", + "title":"Changing the OS User Password Validity Period", + "uri":"admin_guide_000420.html", + "doc_type":"usermanual", + "p_code":"558", + "code":"561" }, { "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.", @@ -4973,8 +5054,8 @@ "title":"Changing the Password for a System Internal User", "uri":"admin_guide_000252.html", "doc_type":"usermanual", - "p_code":"544", - "code":"553" + "p_code":"552", + "code":"562" }, { "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", @@ -4982,8 +5063,8 @@ "title":"Changing the Password for the Kerberos Administrator", "uri":"admin_guide_000253.html", "doc_type":"usermanual", - "p_code":"553", - "code":"554" + "p_code":"562", + "code":"563" }, { "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 ", @@ -4991,8 +5072,8 @@ "title":"Changing the Password for the OMS Kerberos Administrator", "uri":"admin_guide_000254.html", "doc_type":"usermanual", - "p_code":"553", - "code":"555" + "p_code":"562", + "code":"564" }, { "desc":"This section applies only to MRS 3.1.0. For later versions, see Modifying OMS Service Configuration Parameters.It is recommended that the administrator periodically chang", @@ -5000,8 +5081,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":"553", - "code":"556" + "p_code":"562", + "code":"565" }, { "desc":"This section applies only to MRS 3.1.0. For later versions, see Modifying OMS Service Configuration Parameters.It is recommended that the administrator periodically chang", @@ -5009,8 +5090,8 @@ "title":"Changing the Password for the LDAP Administrator", "uri":"admin_guide_000256.html", "doc_type":"usermanual", - "p_code":"553", - "code":"557" + "p_code":"562", + "code":"566" }, { "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", @@ -5018,8 +5099,8 @@ "title":"Changing the Password for a Component Running User", "uri":"admin_guide_000257.html", "doc_type":"usermanual", - "p_code":"553", - "code":"558" + "p_code":"562", + "code":"567" }, { "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.", @@ -5027,8 +5108,8 @@ "title":"Changing the Password for a Database User", "uri":"admin_guide_000258.html", "doc_type":"usermanual", - "p_code":"544", - "code":"559" + "p_code":"552", + "code":"568" }, { "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", @@ -5036,8 +5117,8 @@ "title":"Changing the Password of the OMS Database Administrator", "uri":"admin_guide_000259.html", "doc_type":"usermanual", - "p_code":"559", - "code":"560" + "p_code":"568", + "code":"569" }, { "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 ", @@ -5045,8 +5126,8 @@ "title":"Changing the Password for the Data Access User of the OMS Database", "uri":"admin_guide_000260.html", "doc_type":"usermanual", - "p_code":"559", - "code":"561" + "p_code":"568", + "code":"570" }, { "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", @@ -5054,8 +5135,8 @@ "title":"Changing the Password for a Component Database User", "uri":"admin_guide_000261.html", "doc_type":"usermanual", - "p_code":"559", - "code":"562" + "p_code":"568", + "code":"571" }, { "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", @@ -5063,8 +5144,8 @@ "title":"Resetting the Component Database User Password", "uri":"admin_guide_000363.html", "doc_type":"usermanual", - "p_code":"559", - "code":"563" + "p_code":"568", + "code":"572" }, { "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 ", @@ -5072,8 +5153,8 @@ "title":"Changing the Password for User omm in DBService", "uri":"admin_guide_000354.html", "doc_type":"usermanual", - "p_code":"559", - "code":"564" + "p_code":"568", + "code":"573" }, { "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.", @@ -5081,8 +5162,8 @@ "title":"Security Hardening", "uri":"admin_guide_000271.html", "doc_type":"usermanual", - "p_code":"535", - "code":"565" + "p_code":"543", + "code":"574" }, { "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", @@ -5090,8 +5171,8 @@ "title":"Hardening Policies", "uri":"admin_guide_000272.html", "doc_type":"usermanual", - "p_code":"565", - "code":"566" + "p_code":"574", + "code":"575" }, { "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", @@ -5099,8 +5180,8 @@ "title":"Configuring a Trusted IP Address to Access LDAP", "uri":"admin_guide_000274.html", "doc_type":"usermanual", - "p_code":"565", - "code":"567" + "p_code":"574", + "code":"576" }, { "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 ", @@ -5108,8 +5189,8 @@ "title":"HFile and WAL Encryption", "uri":"admin_guide_000276.html", "doc_type":"usermanual", - "p_code":"565", - "code":"568" + "p_code":"574", + "code":"577" }, { "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", @@ -5117,8 +5198,8 @@ "title":"Configuring Hadoop Security Parameters", "uri":"admin_guide_000277.html", "doc_type":"usermanual", - "p_code":"565", - "code":"569" + "p_code":"574", + "code":"578" }, { "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", @@ -5126,8 +5207,8 @@ "title":"Configuring an IP Address Whitelist for Modification Allowed by HBase", "uri":"admin_guide_000278.html", "doc_type":"usermanual", - "p_code":"565", - "code":"570" + "p_code":"574", + "code":"579" }, { "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", @@ -5135,8 +5216,8 @@ "title":"Updating a Key for a Cluster", "uri":"admin_guide_000279.html", "doc_type":"usermanual", - "p_code":"565", - "code":"571" + "p_code":"574", + "code":"580" }, { "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 ", @@ -5144,8 +5225,8 @@ "title":"Hardening the LDAP", "uri":"admin_guide_000280.html", "doc_type":"usermanual", - "p_code":"565", - "code":"572" + "p_code":"574", + "code":"581" }, { "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", @@ -5153,8 +5234,8 @@ "title":"Configuring Kafka Data Encryption During Transmission", "uri":"admin_guide_000281.html", "doc_type":"usermanual", - "p_code":"565", - "code":"573" + "p_code":"574", + "code":"582" }, { "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", @@ -5162,8 +5243,8 @@ "title":"Configuring HDFS Data Encryption During Transmission", "uri":"admin_guide_000282.html", "doc_type":"usermanual", - "p_code":"565", - "code":"574" + "p_code":"574", + "code":"583" }, { "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", @@ -5171,8 +5252,8 @@ "title":"Encrypting the Communication Between the Controller and the Agent", "uri":"admin_guide_000284.html", "doc_type":"usermanual", - "p_code":"565", - "code":"575" + "p_code":"574", + "code":"584" }, { "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", @@ -5180,17 +5261,17 @@ "title":"Updating SSH Keys for User omm", "uri":"admin_guide_000285.html", "doc_type":"usermanual", - "p_code":"565", - "code":"576" + "p_code":"574", + "code":"585" }, { - "desc":"FusionInsight Manager allows you to configure the timeout duration of the Manager page based on service requirements. You must properly set the timeout duration to preven", - "product_code":"", + "desc":"MRS Manager allows you to configure the timeout duration of the Manager page based on service requirements. You must properly set the timeout duration to prevent informat", + "product_code":"mrs", "title":"Changing the Timeout Duration of the Manager Page", "uri":"admin_guide_000410.html", - "doc_type":"", - "p_code":"565", - "code":"577" + "doc_type":"usermanual", + "p_code":"574", + "code":"586" }, { "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.", @@ -5198,8 +5279,8 @@ "title":"Security Maintenance", "uri":"admin_guide_000287.html", "doc_type":"usermanual", - "p_code":"535", - "code":"578" + "p_code":"543", + "code":"587" }, { "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", @@ -5207,8 +5288,8 @@ "title":"Account Maintenance Suggestions", "uri":"admin_guide_000289.html", "doc_type":"usermanual", - "p_code":"578", - "code":"579" + "p_code":"587", + "code":"588" }, { "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", @@ -5216,8 +5297,8 @@ "title":"Password Maintenance Suggestions", "uri":"admin_guide_000290.html", "doc_type":"usermanual", - "p_code":"578", - "code":"580" + "p_code":"587", + "code":"589" }, { "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", @@ -5225,8 +5306,8 @@ "title":"Log Maintenance Suggestions", "uri":"admin_guide_000291.html", "doc_type":"usermanual", - "p_code":"578", - "code":"581" + "p_code":"587", + "code":"590" }, { "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", @@ -5234,8 +5315,8 @@ "title":"Security Statement", "uri":"admin_guide_000315.html", "doc_type":"usermanual", - "p_code":"535", - "code":"582" + "p_code":"543", + "code":"591" }, { "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.", @@ -5243,620 +5324,620 @@ "title":"Alarm Reference (Applicable to MRS 3.x)", "uri":"mrs_01_1298.html", "doc_type":"usermanual", - "p_code":"319", - "code":"583" + "p_code":"324", + "code":"592" }, { "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", "product_code":"mrs", "title":"ALM-12001 Audit Log Dumping Failure", "uri":"ALM-12001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"584" + "doc_type":"usermanual", + "p_code":"592", + "code":"593" }, { "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", "product_code":"mrs", "title":"ALM-12004 OLdap Resource Abnormal", "uri":"ALM-12004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"585" + "doc_type":"usermanual", + "p_code":"592", + "code":"594" }, { "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", "product_code":"mrs", "title":"ALM-12005 OKerberos Resource Abnormal", "uri":"ALM-12005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"586" + "doc_type":"usermanual", + "p_code":"592", + "code":"595" }, { "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", "product_code":"mrs", "title":"ALM-12006 Node Fault", "uri":"ALM-12006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"587" + "doc_type":"usermanual", + "p_code":"592", + "code":"596" }, { "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", "product_code":"mrs", "title":"ALM-12007 Process Fault", "uri":"ALM-12007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"588" + "doc_type":"usermanual", + "p_code":"592", + "code":"597" }, { "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", "product_code":"mrs", "title":"ALM-12010 Manager Heartbeat Interruption Between the Active and Standby Nodes", "uri":"ALM-12010.html", - "doc_type":"alarm", - "p_code":"583", - "code":"589" + "doc_type":"usermanual", + "p_code":"592", + "code":"598" }, { "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", "product_code":"mrs", "title":"ALM-12011 Manager Data Synchronization Exception Between the Active and Standby Nodes", "uri":"ALM-12011.html", - "doc_type":"alarm", - "p_code":"583", - "code":"590" + "doc_type":"usermanual", + "p_code":"592", + "code":"599" }, { "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", "product_code":"mrs", "title":"ALM-12012 NTP Service Is Abnormal", "uri":"ALM-12012.html", - "doc_type":"alarm", - "p_code":"583", - "code":"591" + "doc_type":"usermanual", + "p_code":"592", + "code":"600" }, { "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", "product_code":"mrs", "title":"ALM-12014 Partition Lost", "uri":"ALM-12014.html", - "doc_type":"alarm", - "p_code":"583", - "code":"592" + "doc_type":"usermanual", + "p_code":"592", + "code":"601" }, { "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 ", "product_code":"mrs", "title":"ALM-12015 Partition Filesystem Readonly", "uri":"ALM-12015.html", - "doc_type":"alarm", - "p_code":"583", - "code":"593" + "doc_type":"usermanual", + "p_code":"592", + "code":"602" }, { "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", "product_code":"mrs", "title":"ALM-12016 CPU Usage Exceeds the Threshold", "uri":"ALM-12016.html", - "doc_type":"alarm", - "p_code":"583", - "code":"594" + "doc_type":"usermanual", + "p_code":"592", + "code":"603" }, { "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", "product_code":"mrs", "title":"ALM-12017 Insufficient Disk Capacity", "uri":"ALM-12017.html", - "doc_type":"alarm", - "p_code":"583", - "code":"595" + "doc_type":"usermanual", + "p_code":"592", + "code":"604" }, { "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 ", "product_code":"mrs", "title":"ALM-12018 Memory Usage Exceeds the Threshold", "uri":"ALM-12018.html", - "doc_type":"alarm", - "p_code":"583", - "code":"596" + "doc_type":"usermanual", + "p_code":"592", + "code":"605" }, { "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", "product_code":"mrs", "title":"ALM-12027 Host PID Usage Exceeds the Threshold", "uri":"ALM-12027.html", - "doc_type":"alarm", - "p_code":"583", - "code":"597" + "doc_type":"usermanual", + "p_code":"592", + "code":"606" }, { "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":"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":"583", - "code":"598" + "doc_type":"usermanual", + "p_code":"592", + "code":"607" }, { "desc":"For MRS 3.3.0 and its later versions:For HDDs, the alarm is triggered when any of the following conditions is met:By default, the system collects data every 3 seconds. Th", "product_code":"mrs", "title":"ALM-12033 Slow Disk Fault", "uri":"ALM-12033.html", - "doc_type":"alarm", - "p_code":"583", - "code":"599" + "doc_type":"usermanual", + "p_code":"592", + "code":"608" }, { "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 ", "product_code":"mrs", "title":"ALM-12034 Periodical Backup Failure", "uri":"ALM-12034.html", - "doc_type":"alarm", - "p_code":"583", - "code":"600" + "doc_type":"usermanual", + "p_code":"592", + "code":"609" }, { "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", "product_code":"mrs", "title":"ALM-12035 Unknown Data Status After Recovery Task Failure", "uri":"ALM-12035.html", - "doc_type":"alarm", - "p_code":"583", - "code":"601" + "doc_type":"usermanual", + "p_code":"592", + "code":"610" }, { "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", "product_code":"mrs", "title":"ALM-12037 NTP Server Abnormal", "uri":"ALM-12037.html", - "doc_type":"alarm", - "p_code":"583", - "code":"602" + "doc_type":"usermanual", + "p_code":"592", + "code":"611" }, { "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":"583", - "code":"603" + "doc_type":"usermanual", + "p_code":"592", + "code":"612" }, { "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", "product_code":"mrs", "title":"ALM-12039 Active/Standby OMS Databases Not Synchronized", "uri":"ALM-12039.html", - "doc_type":"alarm", - "p_code":"583", - "code":"604" + "doc_type":"usermanual", + "p_code":"592", + "code":"613" }, { "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,", "product_code":"mrs", "title":"ALM-12040 Insufficient System Entropy", "uri":"ALM-12040.html", - "doc_type":"alarm", - "p_code":"583", - "code":"605" + "doc_type":"usermanual", + "p_code":"592", + "code":"614" }, { "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", "product_code":"mrs", "title":"ALM-12041 Incorrect Permission on Key Files", "uri":"ALM-12041.html", - "doc_type":"alarm", - "p_code":"583", - "code":"606" + "doc_type":"usermanual", + "p_code":"592", + "code":"615" }, { "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", "product_code":"mrs", "title":"ALM-12042 Incorrect Configuration of Key Files", "uri":"ALM-12042.html", - "doc_type":"alarm", - "p_code":"583", - "code":"607" + "doc_type":"usermanual", + "p_code":"592", + "code":"616" }, { "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", "product_code":"mrs", "title":"ALM-12045 Read Packet Dropped Rate Exceeds the Threshold", "uri":"ALM-12045.html", - "doc_type":"alarm", - "p_code":"583", - "code":"608" + "doc_type":"usermanual", + "p_code":"592", + "code":"617" }, { "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 ", "product_code":"mrs", "title":"ALM-12046 Write Packet Dropped Rate Exceeds the Threshold", "uri":"ALM-12046.html", - "doc_type":"alarm", - "p_code":"583", - "code":"609" + "doc_type":"usermanual", + "p_code":"592", + "code":"618" }, { "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", "product_code":"mrs", "title":"ALM-12047 Read Packet Error Rate Exceeds the Threshold", "uri":"ALM-12047.html", - "doc_type":"alarm", - "p_code":"583", - "code":"610" + "doc_type":"usermanual", + "p_code":"592", + "code":"619" }, { "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", "product_code":"mrs", "title":"ALM-12048 Write Packet Error Rate Exceeds the Threshold", "uri":"ALM-12048.html", - "doc_type":"alarm", - "p_code":"583", - "code":"611" + "doc_type":"usermanual", + "p_code":"592", + "code":"620" }, { "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 ", "product_code":"mrs", "title":"ALM-12049 Network Read Throughput Rate Exceeds the Threshold", "uri":"ALM-12049.html", - "doc_type":"alarm", - "p_code":"583", - "code":"612" + "doc_type":"usermanual", + "p_code":"592", + "code":"621" }, { "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", "product_code":"mrs", "title":"ALM-12050 Network Write Throughput Rate Exceeds the Threshold", "uri":"ALM-12050.html", - "doc_type":"alarm", - "p_code":"583", - "code":"613" + "doc_type":"usermanual", + "p_code":"592", + "code":"622" }, { "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", "product_code":"mrs", "title":"ALM-12051 Disk Inode Usage Exceeds the Threshold", "uri":"ALM-12051.html", - "doc_type":"alarm", - "p_code":"583", - "code":"614" + "doc_type":"usermanual", + "p_code":"592", + "code":"623" }, { "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", "product_code":"mrs", "title":"ALM-12052 TCP Temporary Port Usage Exceeds the Threshold", "uri":"ALM-12052.html", - "doc_type":"alarm", - "p_code":"583", - "code":"615" + "doc_type":"usermanual", + "p_code":"592", + "code":"624" }, { "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", "product_code":"mrs", "title":"ALM-12053 Host File Handle Usage Exceeds the Threshold", "uri":"ALM-12053.html", - "doc_type":"alarm", - "p_code":"583", - "code":"616" + "doc_type":"usermanual", + "p_code":"592", + "code":"625" }, { "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", "product_code":"mrs", "title":"ALM-12054 Invalid Certificate File", "uri":"ALM-12054.html", - "doc_type":"alarm", - "p_code":"583", - "code":"617" + "doc_type":"usermanual", + "p_code":"592", + "code":"626" }, { "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 ", "product_code":"mrs", "title":"ALM-12055 The Certificate File Is About to Expire", "uri":"ALM-12055.html", - "doc_type":"alarm", - "p_code":"583", - "code":"618" + "doc_type":"usermanual", + "p_code":"592", + "code":"627" }, { "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 ", "product_code":"mrs", "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":"583", - "code":"619" + "doc_type":"usermanual", + "p_code":"592", + "code":"628" }, { "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", "product_code":"mrs", "title":"ALM-12061 Process Usage Exceeds the Threshold", "uri":"ALM-12061.html", - "doc_type":"alarm", - "p_code":"583", - "code":"620" + "doc_type":"usermanual", + "p_code":"592", + "code":"629" }, { "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", "product_code":"mrs", "title":"ALM-12062 OMS Parameter Configurations Mismatch with the Cluster Scale", "uri":"ALM-12062.html", - "doc_type":"alarm", - "p_code":"583", - "code":"621" + "doc_type":"usermanual", + "p_code":"592", + "code":"630" }, { "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", "product_code":"mrs", "title":"ALM-12063 Unavailable Disk", "uri":"ALM-12063.html", - "doc_type":"alarm", - "p_code":"583", - "code":"622" + "doc_type":"usermanual", + "p_code":"592", + "code":"631" }, { "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", "product_code":"mrs", "title":"ALM-12064 Host Random Port Range Conflicts with Cluster Used Port", "uri":"ALM-12064.html", - "doc_type":"alarm", - "p_code":"583", - "code":"623" + "doc_type":"usermanual", + "p_code":"592", + "code":"632" }, { "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.", "product_code":"mrs", "title":"ALM-12066 Trust Relationships Between Nodes Become Invalid", "uri":"ALM-12066.html", - "doc_type":"alarm", - "p_code":"583", - "code":"624" + "doc_type":"usermanual", + "p_code":"592", + "code":"633" }, { "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 ", "product_code":"mrs", "title":"ALM-12067 Tomcat Resource Is Abnormal", "uri":"ALM-12067.html", - "doc_type":"alarm", - "p_code":"583", - "code":"625" + "doc_type":"usermanual", + "p_code":"592", + "code":"634" }, { "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 ", "product_code":"mrs", "title":"ALM-12068 ACS Resource Exception", "uri":"ALM-12068.html", - "doc_type":"alarm", - "p_code":"583", - "code":"626" + "doc_type":"usermanual", + "p_code":"592", + "code":"635" }, { "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 ", "product_code":"mrs", "title":"ALM-12069 AOS Resource Exception", "uri":"ALM-12069.html", - "doc_type":"alarm", - "p_code":"583", - "code":"627" + "doc_type":"usermanual", + "p_code":"592", + "code":"636" }, { "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", "product_code":"mrs", "title":"ALM-12070 Controller Resource Is Abnormal", "uri":"ALM-12070.html", - "doc_type":"alarm", - "p_code":"583", - "code":"628" + "doc_type":"usermanual", + "p_code":"592", + "code":"637" }, { "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", "product_code":"mrs", "title":"ALM-12071 Httpd Resource Is Abnormal", "uri":"ALM-12071.html", - "doc_type":"alarm", - "p_code":"583", - "code":"629" + "doc_type":"usermanual", + "p_code":"592", + "code":"638" }, { "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", "product_code":"mrs", "title":"ALM-12072 FloatIP Resource Is Abnormal", "uri":"ALM-12072.html", - "doc_type":"alarm", - "p_code":"583", - "code":"630" + "doc_type":"usermanual", + "p_code":"592", + "code":"639" }, { "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", "product_code":"mrs", "title":"ALM-12073 CEP Resource Is Abnormal", "uri":"ALM-12073.html", - "doc_type":"alarm", - "p_code":"583", - "code":"631" + "doc_type":"usermanual", + "p_code":"592", + "code":"640" }, { "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", "product_code":"mrs", "title":"ALM-12074 FMS Resource Is Abnormal", "uri":"ALM-12074.html", - "doc_type":"alarm", - "p_code":"583", - "code":"632" + "doc_type":"usermanual", + "p_code":"592", + "code":"641" }, { "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", "product_code":"mrs", "title":"ALM-12075 PMS Resource Is Abnormal", "uri":"ALM-12075.html", - "doc_type":"alarm", - "p_code":"583", - "code":"633" + "doc_type":"usermanual", + "p_code":"592", + "code":"642" }, { "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 ", "product_code":"mrs", "title":"ALM-12076 GaussDB Resource Is Abnormal", "uri":"ALM-12076.html", - "doc_type":"alarm", - "p_code":"583", - "code":"634" + "doc_type":"usermanual", + "p_code":"592", + "code":"643" }, { "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", "product_code":"mrs", "title":"ALM-12077 User omm Expired", "uri":"ALM-12077.html", - "doc_type":"alarm", - "p_code":"583", - "code":"635" + "doc_type":"usermanual", + "p_code":"592", + "code":"644" }, { "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", "product_code":"mrs", "title":"ALM-12078 Password of User omm Expired", "uri":"ALM-12078.html", - "doc_type":"alarm", - "p_code":"583", - "code":"636" + "doc_type":"usermanual", + "p_code":"592", + "code":"645" }, { "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", "product_code":"mrs", "title":"ALM-12079 User omm Is About to Expire", "uri":"ALM-12079.html", - "doc_type":"alarm", - "p_code":"583", - "code":"637" + "doc_type":"usermanual", + "p_code":"592", + "code":"646" }, { "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", "product_code":"mrs", "title":"ALM-12080 Password of User omm Is About to Expire", "uri":"ALM-12080.html", - "doc_type":"alarm", - "p_code":"583", - "code":"638" + "doc_type":"usermanual", + "p_code":"592", + "code":"647" }, { "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-12081 User ommdba Expired", "uri":"ALM-12081.html", - "doc_type":"alarm", - "p_code":"583", - "code":"639" + "doc_type":"usermanual", + "p_code":"592", + "code":"648" }, { "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", "product_code":"mrs", "title":"ALM-12082 User ommdba Is About to Expire", "uri":"ALM-12082.html", - "doc_type":"alarm", - "p_code":"583", - "code":"640" + "doc_type":"usermanual", + "p_code":"592", + "code":"649" }, { "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", "product_code":"mrs", "title":"ALM-12083 Password of User ommdba Is About to Expire", "uri":"ALM-12083.html", - "doc_type":"alarm", - "p_code":"583", - "code":"641" + "doc_type":"usermanual", + "p_code":"592", + "code":"650" }, { "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", "product_code":"mrs", "title":"ALM-12084 Password of User ommdba Expired", "uri":"ALM-12084.html", - "doc_type":"alarm", - "p_code":"583", - "code":"642" + "doc_type":"usermanual", + "p_code":"592", + "code":"651" }, { "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", "product_code":"mrs", "title":"ALM-12085 Service Audit Log Dump Failure", "uri":"ALM-12085.html", - "doc_type":"alarm", - "p_code":"583", - "code":"643" + "doc_type":"usermanual", + "p_code":"592", + "code":"652" }, { "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", "product_code":"mrs", "title":"ALM-12087 System Is in the Upgrade Observation Period", "uri":"ALM-12087.html", - "doc_type":"alarm", - "p_code":"583", - "code":"644" + "doc_type":"usermanual", + "p_code":"592", + "code":"653" }, { "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", "product_code":"mrs", "title":"ALM-12089 Inter-Node Network Is Abnormal", "uri":"ALM-12089.html", - "doc_type":"alarm", - "p_code":"583", - "code":"645" + "doc_type":"usermanual", + "p_code":"592", + "code":"654" }, { "desc":"HA checks the disaster resources of Manager every 86 seconds. This alarm is generated when HA detects that the disaster resources have been abnormal for 10 consecutive ti", - "product_code":"", + "product_code":"mrs", "title":"ALM-12091 Abnormal disaster Resources", "uri":"ALM-12091.html", - "doc_type":"", - "p_code":"583", - "code":"646" + "doc_type":"usermanual", + "p_code":"592", + "code":"655" }, { "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 ", "product_code":"mrs", "title":"ALM-12101 AZ Unhealthy", "uri":"ALM-12101.html", - "doc_type":"alarm", - "p_code":"583", - "code":"647" + "doc_type":"usermanual", + "p_code":"592", + "code":"656" }, { "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", "product_code":"mrs", "title":"ALM-12102 AZ HA Component Is Not Deployed Based on DR Requirements", "uri":"ALM-12102.html", - "doc_type":"alarm", - "p_code":"583", - "code":"648" + "doc_type":"usermanual", + "p_code":"592", + "code":"657" }, { "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", "product_code":"mrs", "title":"ALM-12103 Executor Resource Exception", "uri":"ALM-12103.html", - "doc_type":"alarm", - "p_code":"583", - "code":"649" + "doc_type":"usermanual", + "p_code":"592", + "code":"658" }, { "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", "product_code":"mrs", "title":"ALM-12104 Abnormal Knox Resources", "uri":"ALM-12104.html", - "doc_type":"alarm", - "p_code":"583", - "code":"650" + "doc_type":"usermanual", + "p_code":"592", + "code":"659" }, { "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", "product_code":"mrs", "title":"ALM-12110 Failed to get ECS temporary AK/SK", "uri":"ALM-12110.html", - "doc_type":"alarm", - "p_code":"583", - "code":"651" + "doc_type":"usermanual", + "p_code":"592", + "code":"660" }, { "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", @@ -5864,8 +5945,8 @@ "title":"ALM-12172 Failed to Report Metrics to Cloud Eye", "uri":"ALM-12172.html", "doc_type":"usermanual", - "p_code":"583", - "code":"652" + "p_code":"592", + "code":"661" }, { "desc":"For MRS 3.3.0 and its later versions:For HDDs, the alarm is triggered when any of the following conditions is met:By default, the system collects data every 3 seconds. Th", @@ -5873,35 +5954,35 @@ "title":"ALM-12180 Suspended Disk I/O", "uri":"ALM-12180.html", "doc_type":"usermanual", - "p_code":"583", - "code":"653" + "p_code":"592", + "code":"662" }, { "desc":"The system checks the CGroup task usage of user omm every 5 minutes. This alarm is generated when the CGroup task usage exceeds 90%. This alarm is cleared when the CGroup", - "product_code":"", + "product_code":"mrs", "title":"ALM-12186 CGroup Task Usage Exceeds the Threshold", "uri":"ALM-12186.html", - "doc_type":"", - "p_code":"583", - "code":"654" + "doc_type":"usermanual", + "p_code":"592", + "code":"663" }, { "desc":"The system checks the disk space every 60 seconds. When detecting that the disk space is expanded, the system expands disk partition. This alarm is generated when the dis", - "product_code":"", + "product_code":"mrs", "title":"ALM-12187 Failed to Expand Disk Partition Capacity", "uri":"ALM-12187.html", - "doc_type":"", - "p_code":"583", - "code":"655" + "doc_type":"usermanual", + "p_code":"592", + "code":"664" }, { "desc":"NodeAgent checks the status of the diskmgt disk monitoring service every 5 minutes. This alarm is generated when diskmgt disk monitoring is unavailable.This alarm is clea", - "product_code":"", + "product_code":"mrs", "title":"ALM-12188 diskmgt Disk Monitoring Unavailable", "uri":"ALM-12188.html", - "doc_type":"", - "p_code":"583", - "code":"656" + "doc_type":"usermanual", + "p_code":"592", + "code":"665" }, { "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", @@ -5909,359 +5990,449 @@ "title":"ALM-12190 Number of Knox Connections Exceeds the Threshold", "uri":"ALM-12190.html", "doc_type":"usermanual", - "p_code":"583", - "code":"657" + "p_code":"592", + "code":"666" + }, + { + "desc":"The system checks the disk I/O usage every 30 seconds and compares the actual disk I/O usage with the threshold. This alarm is generated when the disk I/O usage exceeds t", + "product_code":"mrs", + "title":"ALM-12191 Disk I/O Usage Exceeds the Threshold", + "uri":"ALM-12191.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"667" + }, + { + "desc":"The system checks the average load every 30 seconds and compares the actual average load with the threshold. This alarm is generated when the average load exceeds the thr", + "product_code":"mrs", + "title":"ALM-12192 Host Load Exceeds the Threshold", + "uri":"ALM-12192.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"668" + }, + { + "desc":"The system checks whether a user password is about to expire at 1:00 a.m. every day. This alarm is generated when a user password is about to expire in less than 5 days b", + "product_code":"mrs", + "title":"ALM-12200 Password Is About to Expire", + "uri":"ALM-12200.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"669" + }, + { + "desc":"The system checks the CPU usage every 30 seconds and compares the check result with the default threshold. This alarm is generated when the CPU usage exceeds the threshol", + "product_code":"mrs", + "title":"ALM-12201 Process CPU Usage Exceeds the Threshold", + "uri":"ALM-12201.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"670" + }, + { + "desc":"The system checks the memory usage of main OMS processes every 30 seconds. This alarm is generated when the memory usage of main OMS processes is greater than 90% (defaul", + "product_code":"mrs", + "title":"ALM-12202 Process Memory Usage Exceeds the Threshold", + "uri":"ALM-12202.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"671" + }, + { + "desc":"The system checks the GC duration of main OMS processes every 30 seconds. If the GC duration of an OMS process exceeds the threshold for three consecutive times, this ala", + "product_code":"mrs", + "title":"ALM-12203 Process Full GC Duration Exceeds the Threshold", + "uri":"ALM-12203.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"672" + }, + { + "desc":"The system checks the wait duration of a disk read every 30 seconds and compares the actual wait duration with the threshold. This alarm is generated when the wait durati", + "product_code":"mrs", + "title":"ALM-12204 Wait Duration of a Disk Read Exceeds the Threshold", + "uri":"ALM-12204.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"673" + }, + { + "desc":"The system checks the wait duration of a disk write every 30 seconds and compares the actual wait duration with the threshold. This alarm is generated when the wait durat", + "product_code":"mrs", + "title":"ALM-12205 Wait Duration of a Disk Write Exceeds the Threshold", + "uri":"ALM-12205.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"674" + }, + { + "desc":"The system checks whether a user password has expired at 1:00 a.m. every day. This alarm is generated when a user password has expired.This alarm is cleared when the user", + "product_code":"mrs", + "title":"ALM-12206 Password Has Expired", + "uri":"ALM-12206.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"675" + }, + { + "desc":"When slow disk detection is enabled, the system checks the slow disk processing status every 10 minutes by default. This alarm is generated when the following disk or nod", + "product_code":"mrs", + "title":"ALM-12207 Slow Disk Processing Timeout", + "uri":"ALM-12207.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"676" }, { "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", "product_code":"mrs", "title":"ALM-13000 ZooKeeper Service Unavailable", "uri":"ALM-13000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"658" + "doc_type":"usermanual", + "p_code":"592", + "code":"677" }, { "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", "product_code":"mrs", "title":"ALM-13001 Available ZooKeeper Connections Are Insufficient", "uri":"ALM-13001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"659" + "doc_type":"usermanual", + "p_code":"592", + "code":"678" }, { "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", "product_code":"mrs", "title":"ALM-13002 ZooKeeper Direct Memory Usage Exceeds the Threshold", "uri":"ALM-13002.html", - "doc_type":"alarm", - "p_code":"583", - "code":"660" + "doc_type":"usermanual", + "p_code":"592", + "code":"679" }, { "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", "product_code":"mrs", "title":"ALM-13003 GC Duration of the ZooKeeper Process Exceeds the Threshold", "uri":"ALM-13003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"661" + "doc_type":"usermanual", + "p_code":"592", + "code":"680" }, { "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", "product_code":"mrs", "title":"ALM-13004 ZooKeeper Heap Memory Usage Exceeds the Threshold", "uri":"ALM-13004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"662" + "doc_type":"usermanual", + "p_code":"592", + "code":"681" }, { "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", "product_code":"mrs", "title":"ALM-13005 Failed to Set the Quota of Top Directories of ZooKeeper Components", "uri":"ALM-13005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"663" + "doc_type":"usermanual", + "p_code":"592", + "code":"682" }, { "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", "product_code":"mrs", "title":"ALM-13006 Znode Number or Capacity Exceeds the Threshold", "uri":"ALM-13006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"664" + "doc_type":"usermanual", + "p_code":"592", + "code":"683" }, { "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", "product_code":"mrs", "title":"ALM-13007 Available ZooKeeper Client Connections Are Insufficient", "uri":"ALM-13007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"665" + "doc_type":"usermanual", + "p_code":"592", + "code":"684" }, { "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", "product_code":"mrs", "title":"ALM-13008 ZooKeeper Znode Usage Exceeds the Threshold", "uri":"ALM-13008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"666" + "doc_type":"usermanual", + "p_code":"592", + "code":"685" }, { "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", "product_code":"mrs", "title":"ALM-13009 ZooKeeper Znode Capacity Usage Exceeds the Threshold", "uri":"ALM-13009.html", - "doc_type":"alarm", - "p_code":"583", - "code":"667" + "doc_type":"usermanual", + "p_code":"592", + "code":"686" }, { "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", "product_code":"mrs", "title":"ALM-13010 Znode Usage of a Directory with Quota Configured Exceeds the Threshold", "uri":"ALM-13010.html", - "doc_type":"alarm", - "p_code":"583", - "code":"668" + "doc_type":"usermanual", + "p_code":"592", + "code":"687" }, { "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", "product_code":"mrs", "title":"ALM-14000 HDFS Service Unavailable", "uri":"ALM-14000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"669" + "doc_type":"usermanual", + "p_code":"592", + "code":"688" }, { "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, ", "product_code":"mrs", "title":"ALM-14001 HDFS Disk Usage Exceeds the Threshold", "uri":"ALM-14001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"670" + "doc_type":"usermanual", + "p_code":"592", + "code":"689" }, { "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", "product_code":"mrs", "title":"ALM-14002 DataNode Disk Usage Exceeds the Threshold", "uri":"ALM-14002.html", - "doc_type":"alarm", - "p_code":"583", - "code":"671" + "doc_type":"usermanual", + "p_code":"592", + "code":"690" }, { "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", "product_code":"mrs", "title":"ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold", "uri":"ALM-14003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"672" + "doc_type":"usermanual", + "p_code":"592", + "code":"691" }, { "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", "product_code":"mrs", "title":"ALM-14006 Number of HDFS Files Exceeds the Threshold", "uri":"ALM-14006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"673" + "doc_type":"usermanual", + "p_code":"592", + "code":"692" }, { "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", "product_code":"mrs", "title":"ALM-14007 NameNode Heap Memory Usage Exceeds the Threshold", "uri":"ALM-14007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"674" + "doc_type":"usermanual", + "p_code":"592", + "code":"693" }, { "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", "product_code":"mrs", "title":"ALM-14008 DataNode Heap Memory Usage Exceeds the Threshold", "uri":"ALM-14008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"675" + "doc_type":"usermanual", + "p_code":"592", + "code":"694" }, { "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 ", "product_code":"mrs", "title":"ALM-14009 Number of Dead DataNodes Exceeds the Threshold", "uri":"ALM-14009.html", - "doc_type":"alarm", - "p_code":"583", - "code":"676" + "doc_type":"usermanual", + "p_code":"592", + "code":"695" }, { "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", "product_code":"mrs", "title":"ALM-14010 NameService Service Is Abnormal", "uri":"ALM-14010.html", - "doc_type":"alarm", - "p_code":"583", - "code":"677" + "doc_type":"usermanual", + "p_code":"592", + "code":"696" }, { "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", "product_code":"mrs", "title":"ALM-14011 DataNode Data Directory Is Not Configured Properly", "uri":"ALM-14011.html", - "doc_type":"alarm", - "p_code":"583", - "code":"678" + "doc_type":"usermanual", + "p_code":"592", + "code":"697" }, { "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 ", "product_code":"mrs", "title":"ALM-14012 JournalNode Is Out of Synchronization", "uri":"ALM-14012.html", - "doc_type":"alarm", - "p_code":"583", - "code":"679" + "doc_type":"usermanual", + "p_code":"592", + "code":"698" }, { "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", "product_code":"mrs", "title":"ALM-14013 Failed to Update the NameNode FsImage File", "uri":"ALM-14013.html", - "doc_type":"alarm", - "p_code":"583", - "code":"680" + "doc_type":"usermanual", + "p_code":"592", + "code":"699" }, { "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", "product_code":"mrs", "title":"ALM-14014 NameNode GC Time Exceeds the Threshold", "uri":"ALM-14014.html", - "doc_type":"alarm", - "p_code":"583", - "code":"681" + "doc_type":"usermanual", + "p_code":"592", + "code":"700" }, { "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", "product_code":"mrs", "title":"ALM-14015 DataNode GC Time Exceeds the Threshold", "uri":"ALM-14015.html", - "doc_type":"alarm", - "p_code":"583", - "code":"682" + "doc_type":"usermanual", + "p_code":"592", + "code":"701" }, { "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% ", "product_code":"mrs", "title":"ALM-14016 DataNode Direct Memory Usage Exceeds the Threshold", "uri":"ALM-14016.html", - "doc_type":"alarm", - "p_code":"583", - "code":"683" + "doc_type":"usermanual", + "p_code":"592", + "code":"702" }, { "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", "product_code":"mrs", "title":"ALM-14017 NameNode Direct Memory Usage Exceeds the Threshold", "uri":"ALM-14017.html", - "doc_type":"alarm", - "p_code":"583", - "code":"684" + "doc_type":"usermanual", + "p_code":"592", + "code":"703" }, { "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 ", "product_code":"mrs", "title":"ALM-14018 NameNode Non-heap Memory Usage Exceeds the Threshold", "uri":"ALM-14018.html", - "doc_type":"alarm", - "p_code":"583", - "code":"685" + "doc_type":"usermanual", + "p_code":"592", + "code":"704" }, { "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 ", "product_code":"mrs", "title":"ALM-14019 DataNode Non-heap Memory Usage Exceeds the Threshold", "uri":"ALM-14019.html", - "doc_type":"alarm", - "p_code":"583", - "code":"686" + "doc_type":"usermanual", + "p_code":"592", + "code":"705" }, { "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", "product_code":"mrs", "title":"ALM-14020 Number of Entries in the HDFS Directory Exceeds the Threshold", "uri":"ALM-14020.html", - "doc_type":"alarm", - "p_code":"583", - "code":"687" + "doc_type":"usermanual", + "p_code":"592", + "code":"706" }, { "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", "product_code":"mrs", "title":"ALM-14021 NameNode Average RPC Processing Time Exceeds the Threshold", "uri":"ALM-14021.html", - "doc_type":"alarm", - "p_code":"583", - "code":"688" + "doc_type":"usermanual", + "p_code":"592", + "code":"707" }, { "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). ", "product_code":"mrs", "title":"ALM-14022 NameNode Average RPC Queuing Time Exceeds the Threshold", "uri":"ALM-14022.html", - "doc_type":"alarm", - "p_code":"583", - "code":"689" + "doc_type":"usermanual", + "p_code":"592", + "code":"708" }, { "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", "product_code":"mrs", "title":"ALM-14023 Percentage of Total Reserved Disk Space for Replicas Exceeds the Threshold", "uri":"ALM-14023.html", - "doc_type":"alarm", - "p_code":"583", - "code":"690" + "doc_type":"usermanual", + "p_code":"592", + "code":"709" }, { "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 ", "product_code":"mrs", "title":"ALM-14024 Tenant Space Usage Exceeds the Threshold", "uri":"ALM-14024.html", - "doc_type":"alarm", - "p_code":"583", - "code":"691" + "doc_type":"usermanual", + "p_code":"592", + "code":"710" }, { "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", "product_code":"mrs", "title":"ALM-14025 Tenant File Object Usage Exceeds the Threshold", "uri":"ALM-14025.html", - "doc_type":"alarm", - "p_code":"583", - "code":"692" + "doc_type":"usermanual", + "p_code":"592", + "code":"711" }, { "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", "product_code":"mrs", "title":"ALM-14026 Blocks on DataNode Exceed the Threshold", "uri":"ALM-14026.html", - "doc_type":"alarm", - "p_code":"583", - "code":"693" + "doc_type":"usermanual", + "p_code":"592", + "code":"712" }, { "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", "product_code":"mrs", "title":"ALM-14027 DataNode Disk Fault", "uri":"ALM-14027.html", - "doc_type":"alarm", - "p_code":"583", - "code":"694" + "doc_type":"usermanual", + "p_code":"592", + "code":"713" }, { "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", "product_code":"mrs", "title":"ALM-14028 Number of Blocks to Be Supplemented Exceeds the Threshold", "uri":"ALM-14028.html", - "doc_type":"alarm", - "p_code":"583", - "code":"695" + "doc_type":"usermanual", + "p_code":"592", + "code":"714" }, { "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", "product_code":"mrs", "title":"ALM-14029 Number of Blocks in a Replica Exceeds the Threshold", "uri":"ALM-14029.html", - "doc_type":"alarm", - "p_code":"583", - "code":"696" + "doc_type":"usermanual", + "p_code":"592", + "code":"715" }, { "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 ", @@ -6269,170 +6440,206 @@ "title":"ALM-14030 HDFS Allows Write of Single-Replica Data", "uri":"ALM-14030.html", "doc_type":"usermanual", - "p_code":"583", - "code":"697" + "p_code":"592", + "code":"716" }, { "desc":"The DataNode process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This ala", - "product_code":"", + "product_code":"mrs", "title":"ALM-14031 DataNode Process Is Abnormal", "uri":"ALM-14031.html", - "doc_type":"", - "p_code":"583", - "code":"698" + "doc_type":"usermanual", + "p_code":"592", + "code":"717" }, { "desc":"The JournalNode process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This ", - "product_code":"", + "product_code":"mrs", "title":"ALM-14032 JournalNode Process Is Abnormal", "uri":"ALM-14032.html", - "doc_type":"", - "p_code":"583", - "code":"699" + "doc_type":"usermanual", + "p_code":"592", + "code":"718" }, { "desc":"The ZKFC process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This alarm i", - "product_code":"", + "product_code":"mrs", "title":"ALM-14033 ZKFC Process Is Abnormal", "uri":"ALM-14033.html", - "doc_type":"", - "p_code":"583", - "code":"700" + "doc_type":"usermanual", + "p_code":"592", + "code":"719" }, { "desc":"The Router process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This alarm", - "product_code":"", + "product_code":"mrs", "title":"ALM-14034 Router Process Is Abnormal", "uri":"ALM-14034.html", - "doc_type":"", - "p_code":"583", - "code":"701" + "doc_type":"usermanual", + "p_code":"592", + "code":"720" }, { "desc":"The HttpFS process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This alarm", - "product_code":"", + "product_code":"mrs", "title":"ALM-14035 HttpFS Process Is Abnormal", "uri":"ALM-14035.html", - "doc_type":"", - "p_code":"583", - "code":"702" + "doc_type":"usermanual", + "p_code":"592", + "code":"721" + }, + { + "desc":"This alarm applies only to MRS 3.3.1 or later.The system checks the NameNode process status every 30 seconds. This alarm is generated when the NameNode is in the safe mod", + "product_code":"mrs", + "title":"ALM-14036 NameNode Is In Safe Mode", + "uri":"ALM-14036.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"722" + }, + { + "desc":"This alarm applies only to MRS 3.3.1 or later.The NameNode checks whether there are DataNodes that are not managed in the cluster every 8 hours. This alarm is generated w", + "product_code":"mrs", + "title":"ALM-14037 DataNodes Outside the Cluster", + "uri":"ALM-14037.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"723" + }, + { + "desc":"The system checks the size of the used HDFS Router heap memory and the maximum size of the heap memory that can be allocated every 30 seconds, calculates the ratio of the", + "product_code":"mrs", + "title":"ALM-14038 Router Heap Memory Usage Exceeds the Threshold", + "uri":"ALM-14038.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"724" + }, + { + "desc":"The system checks the number of slow operations per second on HDFS DataNode instances every 60 seconds and compares the number with the threshold. This alarm is generated", + "product_code":"mrs", + "title":"ALM-14039 Slow DataNodes Exist in the Cluster", + "uri":"ALM-14039.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"725" }, { "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 ", "product_code":"mrs", "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":"583", - "code":"703" + "doc_type":"usermanual", + "p_code":"592", + "code":"726" }, { "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 ", "product_code":"mrs", "title":"ALM-16001 Hive Warehouse Space Usage Exceeds the Threshold", "uri":"ALM-16001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"704" + "doc_type":"usermanual", + "p_code":"592", + "code":"727" }, { "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 ", "product_code":"mrs", "title":"ALM-16002 Hive SQL Execution Success Rate Is Lower Than the Threshold", "uri":"ALM-16002.html", - "doc_type":"alarm", - "p_code":"583", - "code":"705" + "doc_type":"usermanual", + "p_code":"592", + "code":"728" }, { "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%", "product_code":"mrs", "title":"ALM-16003 Background Thread Usage Exceeds the Threshold", "uri":"ALM-16003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"706" + "doc_type":"usermanual", + "p_code":"592", + "code":"729" }, { "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", "product_code":"mrs", "title":"ALM-16004 Hive Service Unavailable", "uri":"ALM-16004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"707" + "doc_type":"usermanual", + "p_code":"592", + "code":"730" }, { "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", "product_code":"mrs", "title":"ALM-16005 The Heap Memory Usage of the Hive Process Exceeds the Threshold", "uri":"ALM-16005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"708" + "doc_type":"usermanual", + "p_code":"592", + "code":"731" }, { "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", "product_code":"mrs", "title":"ALM-16006 The Direct Memory Usage of the Hive Process Exceeds the Threshold", "uri":"ALM-16006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"709" + "doc_type":"usermanual", + "p_code":"592", + "code":"732" }, { "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 ", "product_code":"mrs", "title":"ALM-16007 Hive GC Time Exceeds the Threshold", "uri":"ALM-16007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"710" + "doc_type":"usermanual", + "p_code":"592", + "code":"733" }, { "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", "product_code":"mrs", "title":"ALM-16008 Non-Heap Memory Usage of the Hive Process Exceeds the Threshold", "uri":"ALM-16008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"711" + "doc_type":"usermanual", + "p_code":"592", + "code":"734" }, { "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 ", "product_code":"mrs", "title":"ALM-16009 Map Number Exceeds the Threshold", "uri":"ALM-16009.html", - "doc_type":"alarm", - "p_code":"583", - "code":"712" + "doc_type":"usermanual", + "p_code":"592", + "code":"735" }, { "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. ", "product_code":"mrs", "title":"ALM-16045 Hive Data Warehouse Is Deleted", "uri":"ALM-16045.html", - "doc_type":"alarm", - "p_code":"583", - "code":"713" + "doc_type":"usermanual", + "p_code":"592", + "code":"736" }, { "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", "product_code":"mrs", "title":"ALM-16046 Hive Data Warehouse Permission Is Modified", "uri":"ALM-16046.html", - "doc_type":"alarm", - "p_code":"583", - "code":"714" + "doc_type":"usermanual", + "p_code":"592", + "code":"737" }, { "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", "product_code":"mrs", "title":"ALM-16047 HiveServer Has Been Deregistered from ZooKeeper", "uri":"ALM-16047.html", - "doc_type":"alarm", - "p_code":"583", - "code":"715" + "doc_type":"usermanual", + "p_code":"592", + "code":"738" }, { "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", @@ -6440,386 +6647,449 @@ "title":"ALM-16048 Tez or Spark Library Path Does Not Exist", "uri":"ALM-16048.html", "doc_type":"usermanual", - "p_code":"583", - "code":"716" + "p_code":"592", + "code":"739" + }, + { + "desc":"The system checks the percentage of sessions connected to MetaStore to the maximum number of sessions allowed by MetaStore every 30 seconds. This alarm is generated when ", + "product_code":"mrs", + "title":"ALM-16051 Percentage of Sessions Connected to MetaStore Exceeds the Threshold", + "uri":"ALM-16051.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"740" + }, + { + "desc":"The system periodically checks the latency for MetaStore to access the meta database during table creation. This alarm is generated when the average latency in the last 5", + "product_code":"mrs", + "title":"ALM-16052 Latency for MetaStore to Access the Meta Database During Table Creation Exceeds the Threshold", + "uri":"ALM-16052.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"741" + }, + { + "desc":"The system periodically checks the average HQL submission time, which is the time for calling the MapReduce/Spark/Tez APIs to submit Yarn jobs, including the time for upl", + "product_code":"mrs", + "title":"ALM-16053 Average HQL Submission Time of Hive in the Last 5 Minutes Exceeds the Threshold", + "uri":"ALM-16053.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"742" }, { "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.", "product_code":"mrs", "title":"ALM-17003 Oozie Service Unavailable", "uri":"ALM-17003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"717" + "doc_type":"usermanual", + "p_code":"592", + "code":"743" }, { "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", "product_code":"mrs", "title":"ALM-17004 Oozie Heap Memory Usage Exceeds the Threshold", "uri":"ALM-17004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"718" + "doc_type":"usermanual", + "p_code":"592", + "code":"744" }, { "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", "product_code":"mrs", "title":"ALM-17005 Oozie Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-17005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"719" + "doc_type":"usermanual", + "p_code":"592", + "code":"745" }, { "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", "product_code":"mrs", "title":"ALM-17006 Oozie Direct Memory Usage Exceeds the Threshold", "uri":"ALM-17006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"720" + "doc_type":"usermanual", + "p_code":"592", + "code":"746" }, { "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", "product_code":"mrs", "title":"ALM-17007 Garbage Collection (GC) Time of the Oozie Process Exceeds the Threshold", "uri":"ALM-17007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"721" + "doc_type":"usermanual", + "p_code":"592", + "code":"747" + }, + { + "desc":"In HA mode, Oozie depends on ZooKeeper. This alarm is generated when the connection between Oozie and ZooKeeper is abnormal for three consecutive times.This alarm is clea", + "product_code":"mrs", + "title":"ALM-17008 Abnormal Connection Between Oozie and ZooKeeper", + "uri":"ALM-17008.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"748" + }, + { + "desc":"Oozie depends on DBService. After a task is submitted, the system checks DBService connectivity. This alarm is generated when the service fails the check for 10 consecuti", + "product_code":"mrs", + "title":"ALM-17009 Abnormal Connection Between Oozie and DBService", + "uri":"ALM-17009.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"749" + }, + { + "desc":"Oozie depends on HDFS. After a task is submitted, the system checks HDFS connectivity. This alarm is generated when the service fails the check for 3 consecutive times.Th", + "product_code":"mrs", + "title":"ALM-17010 Abnormal Connection Between Oozie and HDFS", + "uri":"ALM-17010.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"750" + }, + { + "desc":"Oozie depends on YARN. After a task is submitted, the system checks YARN connectivity. This alarm is generated when the service fails the check for 5 consecutive times.Th", + "product_code":"mrs", + "title":"ALM-17011 Abnormal Connection Between Oozie and YARN", + "uri":"ALM-17011.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"751" }, { "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 ", "product_code":"mrs", "title":"ALM-18000 Yarn Service Unavailable", "uri":"ALM-18000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"722" + "doc_type":"usermanual", + "p_code":"592", + "code":"752" }, { "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", "product_code":"mrs", "title":"ALM-18002 NodeManager Heartbeat Lost", "uri":"ALM-18002.html", - "doc_type":"alarm", - "p_code":"583", - "code":"723" + "doc_type":"usermanual", + "p_code":"592", + "code":"753" }, { "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", "product_code":"mrs", "title":"ALM-18003 NodeManager Unhealthy", "uri":"ALM-18003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"724" + "doc_type":"usermanual", + "p_code":"592", + "code":"754" }, { "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", "product_code":"mrs", "title":"ALM-18008 Heap Memory Usage of ResourceManager Exceeds the Threshold", "uri":"ALM-18008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"725" + "doc_type":"usermanual", + "p_code":"592", + "code":"755" }, { "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", "product_code":"mrs", "title":"ALM-18009 Heap Memory Usage of JobHistoryServer Exceeds the Threshold", "uri":"ALM-18009.html", - "doc_type":"alarm", - "p_code":"583", - "code":"726" + "doc_type":"usermanual", + "p_code":"592", + "code":"756" }, { "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", "product_code":"mrs", "title":"ALM-18010 ResourceManager GC Time Exceeds the Threshold", "uri":"ALM-18010.html", - "doc_type":"alarm", - "p_code":"583", - "code":"727" + "doc_type":"usermanual", + "p_code":"592", + "code":"757" }, { "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", "product_code":"mrs", "title":"ALM-18011 NodeManager GC Time Exceeds the Threshold", "uri":"ALM-18011.html", - "doc_type":"alarm", - "p_code":"583", - "code":"728" + "doc_type":"usermanual", + "p_code":"592", + "code":"758" }, { "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", "product_code":"mrs", "title":"ALM-18012 JobHistoryServer GC Time Exceeds the Threshold", "uri":"ALM-18012.html", - "doc_type":"alarm", - "p_code":"583", - "code":"729" + "doc_type":"usermanual", + "p_code":"592", + "code":"759" }, { "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", "product_code":"mrs", "title":"ALM-18013 ResourceManager Direct Memory Usage Exceeds the Threshold", "uri":"ALM-18013.html", - "doc_type":"alarm", - "p_code":"583", - "code":"730" + "doc_type":"usermanual", + "p_code":"592", + "code":"760" }, { "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", "product_code":"mrs", "title":"ALM-18014 NodeManager Direct Memory Usage Exceeds the Threshold", "uri":"ALM-18014.html", - "doc_type":"alarm", - "p_code":"583", - "code":"731" + "doc_type":"usermanual", + "p_code":"592", + "code":"761" }, { "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", "product_code":"mrs", "title":"ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold", "uri":"ALM-18015.html", - "doc_type":"alarm", - "p_code":"583", - "code":"732" + "doc_type":"usermanual", + "p_code":"592", + "code":"762" }, { "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", "product_code":"mrs", "title":"ALM-18016 Non Heap Memory Usage of ResourceManager Exceeds the Threshold", "uri":"ALM-18016.html", - "doc_type":"alarm", - "p_code":"583", - "code":"733" + "doc_type":"usermanual", + "p_code":"592", + "code":"763" }, { "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", "product_code":"mrs", "title":"ALM-18017 Non Heap Memory Usage of NodeManager Exceeds the Threshold", "uri":"ALM-18017.html", - "doc_type":"alarm", - "p_code":"583", - "code":"734" + "doc_type":"usermanual", + "p_code":"592", + "code":"764" }, { "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", "product_code":"mrs", "title":"ALM-18018 NodeManager Heap Memory Usage Exceeds the Threshold", "uri":"ALM-18018.html", - "doc_type":"alarm", - "p_code":"583", - "code":"735" + "doc_type":"usermanual", + "p_code":"592", + "code":"765" }, { "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", "product_code":"mrs", "title":"ALM-18019 Non Heap Memory Usage of JobHistoryServer Exceeds the Threshold", "uri":"ALM-18019.html", - "doc_type":"alarm", - "p_code":"583", - "code":"736" + "doc_type":"usermanual", + "p_code":"592", + "code":"766" }, { "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", "product_code":"mrs", "title":"ALM-18020 Yarn Task Execution Timeout", "uri":"ALM-18020.html", - "doc_type":"alarm", - "p_code":"583", - "code":"737" + "doc_type":"usermanual", + "p_code":"592", + "code":"767" }, { "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", "product_code":"mrs", "title":"ALM-18021 Mapreduce Service Unavailable", "uri":"ALM-18021.html", - "doc_type":"alarm", - "p_code":"583", - "code":"738" + "doc_type":"usermanual", + "p_code":"592", + "code":"768" }, { "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", "product_code":"mrs", "title":"ALM-18022 Insufficient Yarn Queue Resources", "uri":"ALM-18022.html", - "doc_type":"alarm", - "p_code":"583", - "code":"739" + "doc_type":"usermanual", + "p_code":"592", + "code":"769" }, { "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", "product_code":"mrs", "title":"ALM-18023 Number of Pending Yarn Tasks Exceeds the Threshold", "uri":"ALM-18023.html", - "doc_type":"alarm", - "p_code":"583", - "code":"740" + "doc_type":"usermanual", + "p_code":"592", + "code":"770" }, { "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", "product_code":"mrs", "title":"ALM-18024 Pending Yarn Memory Usage Exceeds the Threshold", "uri":"ALM-18024.html", - "doc_type":"alarm", - "p_code":"583", - "code":"741" + "doc_type":"usermanual", + "p_code":"592", + "code":"771" }, { "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", "product_code":"mrs", "title":"ALM-18025 Number of Terminated Yarn Tasks Exceeds the Threshold", "uri":"ALM-18025.html", - "doc_type":"alarm", - "p_code":"583", - "code":"742" + "doc_type":"usermanual", + "p_code":"592", + "code":"772" }, { "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", "product_code":"mrs", "title":"ALM-18026 Number of Failed Yarn Tasks Exceeds the Threshold", "uri":"ALM-18026.html", - "doc_type":"alarm", - "p_code":"583", - "code":"743" + "doc_type":"usermanual", + "p_code":"592", + "code":"773" }, { "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", "product_code":"mrs", "title":"ALM-19000 HBase Service Unavailable", "uri":"ALM-19000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"744" + "doc_type":"usermanual", + "p_code":"592", + "code":"774" }, { "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", "product_code":"mrs", "title":"ALM-19006 HBase Replication Sync Failed", "uri":"ALM-19006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"745" + "doc_type":"usermanual", + "p_code":"592", + "code":"775" }, { "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 ", "product_code":"mrs", "title":"ALM-19007 HBase GC Time Exceeds the Threshold", "uri":"ALM-19007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"746" + "doc_type":"usermanual", + "p_code":"592", + "code":"776" }, { "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", "product_code":"mrs", "title":"ALM-19008 Heap Memory Usage of the HBase Process Exceeds the Threshold", "uri":"ALM-19008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"747" + "doc_type":"usermanual", + "p_code":"592", + "code":"777" }, { "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", "product_code":"mrs", "title":"ALM-19009 Direct Memory Usage of the HBase Process Exceeds the Threshold", "uri":"ALM-19009.html", - "doc_type":"alarm", - "p_code":"583", - "code":"748" + "doc_type":"usermanual", + "p_code":"592", + "code":"778" }, { "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", "product_code":"mrs", "title":"ALM-19011 RegionServer Region Number Exceeds the Threshold", "uri":"ALM-19011.html", - "doc_type":"alarm", - "p_code":"583", - "code":"749" + "doc_type":"usermanual", + "p_code":"592", + "code":"779" }, { "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", "product_code":"mrs", "title":"ALM-19012 HBase System Table Directory or File Lost", "uri":"ALM-19012.html", - "doc_type":"alarm", - "p_code":"583", - "code":"750" + "doc_type":"usermanual", + "p_code":"592", + "code":"780" }, { "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", "product_code":"mrs", "title":"ALM-19013 Duration of Regions in transaction State Exceeds the Threshold", "uri":"ALM-19013.html", - "doc_type":"alarm", - "p_code":"583", - "code":"751" + "doc_type":"usermanual", + "p_code":"592", + "code":"781" }, { "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 ", "product_code":"mrs", "title":"ALM-19014 Capacity Quota Usage on ZooKeeper Exceeds the Threshold Severely", "uri":"ALM-19014.html", - "doc_type":"alarm", - "p_code":"583", - "code":"752" + "doc_type":"usermanual", + "p_code":"592", + "code":"782" }, { "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", "product_code":"mrs", "title":"ALM-19015 Quantity Quota Usage on ZooKeeper Exceeds the Threshold", "uri":"ALM-19015.html", - "doc_type":"alarm", - "p_code":"583", - "code":"753" + "doc_type":"usermanual", + "p_code":"592", + "code":"783" }, { "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", "product_code":"mrs", "title":"ALM-19016 Quantity Quota Usage on ZooKeeper Exceeds the Threshold Severely", "uri":"ALM-19016.html", - "doc_type":"alarm", - "p_code":"583", - "code":"754" + "doc_type":"usermanual", + "p_code":"592", + "code":"784" }, { "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", "product_code":"mrs", "title":"ALM-19017 Capacity Quota Usage on ZooKeeper Exceeds the Threshold", "uri":"ALM-19017.html", - "doc_type":"alarm", - "p_code":"583", - "code":"755" + "doc_type":"usermanual", + "p_code":"592", + "code":"785" }, { "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). ", "product_code":"mrs", "title":"ALM-19018 HBase Compaction Queue Size Exceeds the Threshold", "uri":"ALM-19018.html", - "doc_type":"alarm", - "p_code":"583", - "code":"756" + "doc_type":"usermanual", + "p_code":"592", + "code":"786" }, { "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", "product_code":"mrs", "title":"ALM-19019 Number of HBase HFiles to Be Synchronized Exceeds the Threshold", "uri":"ALM-19019.html", - "doc_type":"alarm", - "p_code":"583", - "code":"757" + "doc_type":"usermanual", + "p_code":"592", + "code":"787" }, { "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", "product_code":"mrs", "title":"ALM-19020 Number of HBase WAL Files to Be Synchronized Exceeds the Threshold", "uri":"ALM-19020.html", - "doc_type":"alarm", - "p_code":"583", - "code":"758" + "doc_type":"usermanual", + "p_code":"592", + "code":"788" }, { "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", @@ -6827,197 +7097,260 @@ "title":"ALM-19021 Handler Usage of RegionServer Exceeds the Threshold", "uri":"ALM-19021.html", "doc_type":"usermanual", - "p_code":"583", - "code":"759" + "p_code":"592", + "code":"789" }, { "desc":"When the MetricController instance is installed for HBase, the alarm module checks the health status of the active HBase MetricController instance every 120 seconds. This", - "product_code":"", + "product_code":"mrs", "title":"ALM-19022 HBase Hotspot Detection Is Unavailable", "uri":"ALM-19022.html", - "doc_type":"", - "p_code":"583", - "code":"760" + "doc_type":"usermanual", + "p_code":"592", + "code":"790" }, { "desc":"When the MetricController instance is installed for the HBase service, self-healing from hotspotting is automatically enabled. The alarm module checks whether there are r", - "product_code":"", + "product_code":"mrs", "title":"ALM-19023 Region Traffic Restriction for HBase", "uri":"ALM-19023.html", - "doc_type":"", - "p_code":"583", - "code":"761" + "doc_type":"usermanual", + "p_code":"592", + "code":"791" }, { "desc":"The system checks P99 latency for RPC requests on each RegionServer instance of the HBase service every 30 seconds. This alarm is generated when P99 latency for RPC reque", - "product_code":"", + "product_code":"mrs", "title":"ALM-19024 RPC Requests P99 Latency on RegionServer Exceeds the Threshold", "uri":"ALM-19024.html", - "doc_type":"", - "p_code":"583", - "code":"762" + "doc_type":"usermanual", + "p_code":"592", + "code":"792" }, { "desc":"The system checks the hdfs://hacluster/hbase/autocorrupt and hdfs://hacluster/hbase/MasterData/autocorrupt directories on HDFS of each HBase service every 120 seconds. Th", - "product_code":"", + "product_code":"mrs", "title":"ALM-19025 Damaged StoreFile in HBase", "uri":"ALM-19025.html", - "doc_type":"", - "p_code":"583", - "code":"763" + "doc_type":"usermanual", + "p_code":"592", + "code":"793" }, { "desc":"The system checks the hdfs://hacluster/hbase/corrupt directory on the HDFS of each HBase service every 120 seconds. This alarm is generated when there are WAL files in th", - "product_code":"", + "product_code":"mrs", "title":"ALM-19026 Damaged WAL Files in HBase", "uri":"ALM-19026.html", - "doc_type":"", - "p_code":"583", - "code":"764" + "doc_type":"usermanual", + "p_code":"592", + "code":"794" + }, + { + "desc":"The system checks the P99 latency for responding to RPC requests on each RegionServer instance of the HBase service every 30 seconds. This alarm is generated when P99 lat", + "product_code":"mrs", + "title":"ALM-19030 P99 Latency of RegionServer RPC Request Exceeds the Threshold", + "uri":"ALM-19030.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"795" + }, + { + "desc":"The system checks the number of RegionServer RPC connections in each HBase service every 30 seconds. This alarm is generated when the number of RPC connections of a Regio", + "product_code":"mrs", + "title":"ALM-19031 Number of RegionServer RPC Connections Exceeds the Threshold", + "uri":"ALM-19031.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"796" + }, + { + "desc":"The system checks the number of tasks waiting in the RPC write queue for the RegionServer instances of the HBase service every 30 seconds. This alarm is generated when th", + "product_code":"mrs", + "title":"ALM-19032 Number of Tasks in the RegionServer RPC Write Queue Exceeds the Threshold", + "uri":"ALM-19032.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"797" + }, + { + "desc":"The system checks the number of tasks waiting in the RPC read queue for the RegionServer instances of the HBase service every 30 seconds. This alarm is generated when the", + "product_code":"mrs", + "title":"ALM-19033 Number of Tasks in the RegionServer RPC Read Queue Exceeds the Threshold", + "uri":"ALM-19033.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"798" + }, + { + "desc":"The system checks the number of RegionServer WAL write timeouts in each HBase service every 30 seconds. This alarm is generated when the number of WAL write timeouts on a", + "product_code":"mrs", + "title":"ALM-19034 Number of RegionServer WAL Write Timeouts Exceeds the Threshold", + "uri":"ALM-19034.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"799" + }, + { + "desc":"The system checks the size of the RegionServer call queue for each HBase service every 30 seconds. This alarm is generated when the call queue of a RegionServer instance ", + "product_code":"mrs", + "title":"ALM-19035 Size of the RegionServer Call Queue Exceeds the Threshold", + "uri":"ALM-19035.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"800" + }, + { + "desc":"The system checks for bad blocks in HBase key directories every 5 minutes, including the hbase.version file and the hbase:meta and master:store table directories. This al", + "product_code":"mrs", + "title":"ALM-19036 Bad Blocks Exist in HBase Key Directory Data", + "uri":"ALM-19036.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"801" }, { "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", "product_code":"mrs", "title":"ALM-20002 Hue Service Unavailable", "uri":"ALM-20002.html", - "doc_type":"alarm", - "p_code":"583", - "code":"765" + "doc_type":"usermanual", + "p_code":"592", + "code":"802" }, { "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 ", "product_code":"mrs", "title":"ALM-23001 Loader Service Unavailable", "uri":"ALM-23001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"766" + "doc_type":"usermanual", + "p_code":"592", + "code":"803" }, { "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", "product_code":"mrs", "title":"ALM-23003 Loader Task Execution Failure", "uri":"ALM-23003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"767" + "doc_type":"usermanual", + "p_code":"592", + "code":"804" }, { "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", "product_code":"mrs", "title":"ALM-23004 Loader Heap Memory Usage Exceeds the Threshold", "uri":"ALM-23004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"768" + "doc_type":"usermanual", + "p_code":"592", + "code":"805" }, { "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", "product_code":"mrs", "title":"ALM-23005 Loader Non-Heap Memory Usage Exceeds the Threshold", "uri":"ALM-23005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"769" + "doc_type":"usermanual", + "p_code":"592", + "code":"806" }, { "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", "product_code":"mrs", "title":"ALM-23006 Loader Direct Memory Usage Exceeds the Threshold", "uri":"ALM-23006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"770" + "doc_type":"usermanual", + "p_code":"592", + "code":"807" }, { "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", "product_code":"mrs", "title":"ALM-23007 Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold", "uri":"ALM-23007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"771" + "doc_type":"usermanual", + "p_code":"592", + "code":"808" }, { "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", "product_code":"mrs", "title":"ALM-24000 Flume Service Unavailable", "uri":"ALM-24000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"772" + "doc_type":"usermanual", + "p_code":"592", + "code":"809" }, { "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 ", "product_code":"mrs", "title":"ALM-24001 Flume Agent Exception", "uri":"ALM-24001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"773" + "doc_type":"usermanual", + "p_code":"592", + "code":"810" }, { "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", "product_code":"mrs", "title":"ALM-24003 Flume Client Connection Interrupted", "uri":"ALM-24003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"774" + "doc_type":"usermanual", + "p_code":"592", + "code":"811" }, { "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", "product_code":"mrs", "title":"ALM-24004 Exception Occurs When Flume Reads Data", "uri":"ALM-24004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"775" + "doc_type":"usermanual", + "p_code":"592", + "code":"812" }, { "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 ", "product_code":"mrs", "title":"ALM-24005 Exception Occurs When Flume Transmits Data", "uri":"ALM-24005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"776" + "doc_type":"usermanual", + "p_code":"592", + "code":"813" }, { "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", "product_code":"mrs", "title":"ALM-24006 Heap Memory Usage of Flume Server Exceeds the Threshold", "uri":"ALM-24006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"777" + "doc_type":"usermanual", + "p_code":"592", + "code":"814" }, { "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", "product_code":"mrs", "title":"ALM-24007 Flume Server Direct Memory Usage Exceeds the Threshold", "uri":"ALM-24007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"778" + "doc_type":"usermanual", + "p_code":"592", + "code":"815" }, { "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", "product_code":"mrs", "title":"ALM-24008 Flume Server Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-24008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"779" + "doc_type":"usermanual", + "p_code":"592", + "code":"816" }, { "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", "product_code":"mrs", "title":"ALM-24009 Flume Server Garbage Collection (GC) Time Exceeds the Threshold", "uri":"ALM-24009.html", - "doc_type":"alarm", - "p_code":"583", - "code":"780" + "doc_type":"usermanual", + "p_code":"592", + "code":"817" }, { "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", @@ -7025,8 +7358,8 @@ "title":"ALM-24010 Flume Certificate File Is Invalid or Damaged", "uri":"ALM-24010.html", "doc_type":"usermanual", - "p_code":"583", - "code":"781" + "p_code":"592", + "code":"818" }, { "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", @@ -7034,8 +7367,8 @@ "title":"ALM-24011 Flume Certificate File Is About to Expire", "uri":"ALM-24011.html", "doc_type":"usermanual", - "p_code":"583", - "code":"782" + "p_code":"592", + "code":"819" }, { "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", @@ -7043,8 +7376,8 @@ "title":"ALM-24012 Flume Certificate File Has Expired", "uri":"ALM-24012.html", "doc_type":"usermanual", - "p_code":"583", - "code":"783" + "p_code":"592", + "code":"820" }, { "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", @@ -7052,8 +7385,8 @@ "title":"ALM-24013 Flume MonitorServer Certificate File Is Invalid or Damaged", "uri":"ALM-24013.html", "doc_type":"usermanual", - "p_code":"583", - "code":"784" + "p_code":"592", + "code":"821" }, { "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", @@ -7061,8 +7394,8 @@ "title":"ALM-24014 Flume MonitorServer Certificate Is About to Expire", "uri":"ALM-24014.html", "doc_type":"usermanual", - "p_code":"583", - "code":"785" + "p_code":"592", + "code":"822" }, { "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 ", @@ -7070,575 +7403,710 @@ "title":"ALM-24015 Flume MonitorServer Certificate File Has Expired", "uri":"ALM-24015.html", "doc_type":"usermanual", - "p_code":"583", - "code":"786" + "p_code":"592", + "code":"823" }, { "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", "product_code":"mrs", "title":"ALM-25000 LdapServer Service Unavailable", "uri":"ALM-25000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"787" + "doc_type":"usermanual", + "p_code":"592", + "code":"824" }, { "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", "product_code":"mrs", "title":"ALM-25004 Abnormal LdapServer Data Synchronization", "uri":"ALM-25004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"788" + "doc_type":"usermanual", + "p_code":"592", + "code":"825" }, { "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", "product_code":"mrs", "title":"ALM-25005 nscd Service Exception", "uri":"ALM-25005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"789" + "doc_type":"usermanual", + "p_code":"592", + "code":"826" }, { "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", "product_code":"mrs", "title":"ALM-25006 Sssd Service Exception", "uri":"ALM-25006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"790" + "doc_type":"usermanual", + "p_code":"592", + "code":"827" }, { "desc":"The system checks the number of process connections on the SlapdServer node every 30 seconds and compares the actual number with the threshold. This alarm is generated wh", - "product_code":"", + "product_code":"mrs", "title":"ALM-25007 Number of SlapdServer Connections Exceeds the Threshold", "uri":"ALM-25007.html", - "doc_type":"", - "p_code":"583", - "code":"791" + "doc_type":"usermanual", + "p_code":"592", + "code":"828" }, { "desc":"The system checks the CPU usage of the SlapdServer node every 30 seconds and compares the actual usage with the threshold. This alarm is generated when the SlapdServer CP", - "product_code":"", + "product_code":"mrs", "title":"ALM-25008 SlapdServer CPU Usage Exceeds the Threshold", "uri":"ALM-25008.html", - "doc_type":"", - "p_code":"583", - "code":"792" + "doc_type":"usermanual", + "p_code":"592", + "code":"829" }, { "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", "product_code":"mrs", "title":"ALM-25500 KrbServer Service Unavailable", "uri":"ALM-25500.html", - "doc_type":"alarm", - "p_code":"583", - "code":"793" + "doc_type":"usermanual", + "p_code":"592", + "code":"830" }, { "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", "product_code":"mrs", "title":"ALM-26051 Storm Service Unavailable", "uri":"ALM-26051.html", - "doc_type":"alarm", - "p_code":"583", - "code":"794" + "doc_type":"usermanual", + "p_code":"592", + "code":"831" }, { "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", "product_code":"mrs", "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":"583", - "code":"795" + "doc_type":"usermanual", + "p_code":"592", + "code":"832" }, { "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", "product_code":"mrs", "title":"ALM-26053 Storm Slot Usage Exceeds the Threshold", "uri":"ALM-26053.html", - "doc_type":"alarm", - "p_code":"583", - "code":"796" + "doc_type":"usermanual", + "p_code":"592", + "code":"833" }, { "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", "product_code":"mrs", "title":"ALM-26054 Nimbus Heap Memory Usage Exceeds the Threshold", "uri":"ALM-26054.html", - "doc_type":"alarm", - "p_code":"583", - "code":"797" + "doc_type":"usermanual", + "p_code":"592", + "code":"834" }, { "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", "product_code":"mrs", "title":"ALM-27001 DBService Service Unavailable", "uri":"ALM-27001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"798" + "doc_type":"usermanual", + "p_code":"592", + "code":"835" }, { "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", "product_code":"mrs", "title":"ALM-27003 DBService Heartbeat Interruption Between the Active and Standby Nodes", "uri":"ALM-27003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"799" + "doc_type":"usermanual", + "p_code":"592", + "code":"836" }, { "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", "product_code":"mrs", "title":"ALM-27004 Data Inconsistency Between Active and Standby DBServices", "uri":"ALM-27004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"800" + "doc_type":"usermanual", + "p_code":"592", + "code":"837" }, { "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", "product_code":"mrs", "title":"ALM-27005 Database Connections Usage Exceeds the Threshold", "uri":"ALM-27005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"801" + "doc_type":"usermanual", + "p_code":"592", + "code":"838" }, { "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", "product_code":"mrs", "title":"ALM-27006 Disk Space Usage of the Data Directory Exceeds the Threshold", "uri":"ALM-27006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"802" + "doc_type":"usermanual", + "p_code":"592", + "code":"839" }, { "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", "product_code":"mrs", "title":"ALM-27007 Database Enters the Read-Only Mode", "uri":"ALM-27007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"803" + "doc_type":"usermanual", + "p_code":"592", + "code":"840" }, { "desc":"The system checks the memory usage of the Impalad process every 30 seconds. This alarm is generated when the system detects that the memory usage exceeds the default thre", - "product_code":"", + "product_code":"mrs", "title":"ALM-29007 Impalad Process Memory Usage Exceeds the Threshold", "uri":"ALM-29007.html", - "doc_type":"", - "p_code":"583", - "code":"804" + "doc_type":"usermanual", + "p_code":"592", + "code":"841" }, { "desc":"The system checks the number of client connections to the Impalad node every 30 seconds. This alarm is generated when the number of client connections exceeds the customi", - "product_code":"", + "product_code":"mrs", "title":"ALM-29008 Number of ODBC Connections to Impalad Exceeds the Threshold", "uri":"ALM-29008.html", - "doc_type":"", - "p_code":"583", - "code":"805" + "doc_type":"usermanual", + "p_code":"592", + "code":"842" }, { "desc":"The system checks the total number of queries being submitted by the Impalad node every 60 seconds. This alarm is generated when the number of queries exceeds the customi", - "product_code":"", + "product_code":"mrs", "title":"ALM-29010 Number of Queries Being Submitted by Impalad Exceeds the Threshold", "uri":"ALM-29010.html", - "doc_type":"", - "p_code":"583", - "code":"806" + "doc_type":"usermanual", + "p_code":"592", + "code":"843" }, { "desc":"The system checks the total number of queries being executed by the Impalad node every 60 seconds. This alarm is generated when the number of queries exceeds the customiz", - "product_code":"", + "product_code":"mrs", "title":"ALM-29011 Number of Queries Being Executed by Impalad Exceeds the Threshold", "uri":"ALM-29011.html", - "doc_type":"", - "p_code":"583", - "code":"807" + "doc_type":"usermanual", + "p_code":"592", + "code":"844" }, { "desc":"The system checks the total number of queries being waited by the Impalad node every 60 seconds. This alarm is generated when the number of queries exceeds the customized", - "product_code":"", + "product_code":"mrs", "title":"ALM-29012 Number of Queries Being Waited by Impalad Exceeds the Threshold", "uri":"ALM-29012.html", - "doc_type":"", - "p_code":"583", - "code":"808" + "doc_type":"usermanual", + "p_code":"592", + "code":"845" }, { "desc":"The system checks the FGC time of the Impalad service every 60 seconds. This alarm is generated when the FGC time exceeds the threshold (12 seconds) for five consecutive ", - "product_code":"", + "product_code":"mrs", "title":"ALM-29013 Impalad FGC Time Exceeds the Threshold", "uri":"ALM-29013.html", - "doc_type":"", - "p_code":"583", - "code":"809" + "doc_type":"usermanual", + "p_code":"592", + "code":"846" }, { "desc":"The system checks the FGC time of the Catalog service every 60 seconds. This alarm is generated when the FGC time exceeds the threshold (12 seconds) for five consecutive ", - "product_code":"", + "product_code":"mrs", "title":"ALM-29014 Catalog FGC Time Exceeds the Threshold", "uri":"ALM-29014.html", - "doc_type":"", - "p_code":"583", - "code":"810" + "doc_type":"usermanual", + "p_code":"592", + "code":"847" }, { "desc":"The system checks the memory usage of the Catalog process every 30 seconds. This alarm is generated when the system detects that the memory usage exceeds the default thre", - "product_code":"", + "product_code":"mrs", "title":"ALM-29015 Catalog Process Memory Usage Exceeds the Threshold", "uri":"ALM-29015.html", - "doc_type":"", - "p_code":"583", - "code":"811" + "doc_type":"usermanual", + "p_code":"592", + "code":"848" }, { "desc":"In MRS 3.1.5, the system checks every 60 seconds whether the Hive Server2 HTTP port (28000) of Impalad responds to cURL requests. This alarm is generated when the returne", - "product_code":"", + "product_code":"mrs", "title":"ALM-29016 Impalad Instance in the Sub-healthy State", "uri":"ALM-29016.html", - "doc_type":"", - "p_code":"583", - "code":"812" + "doc_type":"usermanual", + "p_code":"592", + "code":"849" }, { "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", "product_code":"mrs", "title":"ALM-38000 Kafka Service Unavailable", "uri":"ALM-38000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"813" + "doc_type":"usermanual", + "p_code":"592", + "code":"850" }, { "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", "product_code":"mrs", "title":"ALM-38001 Insufficient Kafka Disk Capacity", "uri":"ALM-38001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"814" + "doc_type":"usermanual", + "p_code":"592", + "code":"851" }, { "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", "product_code":"mrs", "title":"ALM-38002 Kafka Heap Memory Usage Exceeds the Threshold", "uri":"ALM-38002.html", - "doc_type":"alarm", - "p_code":"583", - "code":"815" + "doc_type":"usermanual", + "p_code":"592", + "code":"852" }, { "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", "product_code":"mrs", "title":"ALM-38004 Kafka Direct Memory Usage Exceeds the Threshold", "uri":"ALM-38004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"816" + "doc_type":"usermanual", + "p_code":"592", + "code":"853" }, { "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", "product_code":"mrs", "title":"ALM-38005 GC Duration of the Broker Process Exceeds the Threshold", "uri":"ALM-38005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"817" + "doc_type":"usermanual", + "p_code":"592", + "code":"854" }, { "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", "product_code":"mrs", "title":"ALM-38006 Percentage of Kafka Partitions That Are Not Completely Synchronized Exceeds the Threshold", "uri":"ALM-38006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"818" + "doc_type":"usermanual", + "p_code":"592", + "code":"855" }, { "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. ", "product_code":"mrs", "title":"ALM-38007 Status of Kafka Default User Is Abnormal", "uri":"ALM-38007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"819" + "doc_type":"usermanual", + "p_code":"592", + "code":"856" }, { "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", "product_code":"mrs", "title":"ALM-38008 Abnormal Kafka Data Directory Status", "uri":"ALM-38008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"820" + "doc_type":"usermanual", + "p_code":"592", + "code":"857" }, { "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":"(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":"583", - "code":"821" + "doc_type":"usermanual", + "p_code":"592", + "code":"858" }, { "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 ", "product_code":"mrs", "title":"ALM-38010 Topics with Single Replica", "uri":"ALM-38010.html", - "doc_type":"alarm", - "p_code":"583", - "code":"822" + "doc_type":"usermanual", + "p_code":"592", + "code":"859" }, { "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", "product_code":"mrs", "title":"ALM-38011 User Connection Usage on Broker Exceeds the Threshold", "uri":"ALM-38011.html", - "doc_type":"alarm", - "p_code":"583", - "code":"823" + "doc_type":"usermanual", + "p_code":"592", + "code":"860" + }, + { + "desc":"The system checks the number of partitions on each Broker instance of the Kafka service every 30 seconds. You can view the number of partitions on the Broker instance das", + "product_code":"mrs", + "title":"ALM-38012 Number of Broker Partitions Exceeds the Threshold", + "uri":"ALM-38012.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"861" + }, + { + "desc":"The system checks the latency of Produce requests on Broker instances in the request queue every 30 seconds. This alarm is generated when the latency of Produce requests ", + "product_code":"mrs", + "title":"ALM-38013 Produce Request Latency in the Request Queue Exceeds the Threshold", + "uri":"ALM-38013.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"862" + }, + { + "desc":"The system checks the total latency of Produce requests on Broker instances every 30 seconds. This alarm is generated when the total latency of Produce requests on a Brok", + "product_code":"mrs", + "title":"ALM-38014 Total Produce Request Latency Exceeds the Threshold", + "uri":"ALM-38014.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"863" + }, + { + "desc":"The system checks the latency of Fetch requests on Broker instances in the request queue every 30 seconds. This alarm is generated when the latency of Fetch requests on a", + "product_code":"mrs", + "title":"ALM-38015 Fetch Request Latency in the Request Queue Exceeds the Threshold", + "uri":"ALM-38015.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"864" + }, + { + "desc":"The system checks the total latency of Fetch requests on Broker instances every 30 seconds. This alarm is generated when the total latency of Fetch requests on a Broker i", + "product_code":"mrs", + "title":"ALM-38016 Total Fetch Request Latency Exceeds the Threshold", + "uri":"ALM-38016.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"865" + }, + { + "desc":"The system checks the partition reassignment time every 10 minutes. The check interval can be modified by the Kafka configuration auto.reassign.check.interval.ms. This al", + "product_code":"mrs", + "title":"ALM-38017 Partition Reassignment Duration Exceeds the Threshold", + "uri":"ALM-38017.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"866" + }, + { + "desc":"If you have configured a threshold to report Kafka consumer lag on the Alarms page of Kafka UI (there is no such rule by default), the system reports the alarm based on t", + "product_code":"mrs", + "title":"ALM-38018 Kafka Consumer Lag", + "uri":"ALM-38018.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"867" }, { "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", "product_code":"mrs", "title":"ALM-43001 Spark2x Service Unavailable", "uri":"ALM-43001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"824" + "doc_type":"usermanual", + "p_code":"592", + "code":"868" }, { "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%", "product_code":"mrs", "title":"ALM-43006 Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold", "uri":"ALM-43006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"825" + "doc_type":"usermanual", + "p_code":"592", + "code":"869" }, { "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 ", "product_code":"mrs", "title":"ALM-43007 Non-Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold", "uri":"ALM-43007.html", - "doc_type":"alarm", - "p_code":"583", - "code":"826" + "doc_type":"usermanual", + "p_code":"592", + "code":"870" }, { "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", "product_code":"mrs", "title":"ALM-43008 The Direct Memory Usage of the JobHistory2x Process Exceeds the Threshold", "uri":"ALM-43008.html", - "doc_type":"alarm", - "p_code":"583", - "code":"827" + "doc_type":"usermanual", + "p_code":"592", + "code":"871" }, { "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 (", "product_code":"mrs", "title":"ALM-43009 JobHistory2x Process GC Time Exceeds the Threshold", "uri":"ALM-43009.html", - "doc_type":"alarm", - "p_code":"583", - "code":"828" + "doc_type":"usermanual", + "p_code":"592", + "code":"872" }, { "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%", "product_code":"mrs", "title":"ALM-43010 Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold", "uri":"ALM-43010.html", - "doc_type":"alarm", - "p_code":"583", - "code":"829" + "doc_type":"usermanual", + "p_code":"592", + "code":"873" }, { "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", "product_code":"mrs", "title":"ALM-43011 Non-Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold", "uri":"ALM-43011.html", - "doc_type":"alarm", - "p_code":"583", - "code":"830" + "doc_type":"usermanual", + "p_code":"592", + "code":"874" }, { "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", "product_code":"mrs", "title":"ALM-43012 Direct Heap Memory Usage of the JDBCServer2x Process Exceeds the Threshold", "uri":"ALM-43012.html", - "doc_type":"alarm", - "p_code":"583", - "code":"831" + "doc_type":"usermanual", + "p_code":"592", + "code":"875" }, { "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 (", "product_code":"mrs", "title":"ALM-43013 JDBCServer2x Process GC Time Exceeds the Threshold", "uri":"ALM-43013.html", - "doc_type":"alarm", - "p_code":"583", - "code":"832" + "doc_type":"usermanual", + "p_code":"592", + "code":"876" }, { "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 ", "product_code":"mrs", "title":"ALM-43017 JDBCServer2x Process Full GC Number Exceeds the Threshold", "uri":"ALM-43017.html", - "doc_type":"alarm", - "p_code":"583", - "code":"833" + "doc_type":"usermanual", + "p_code":"592", + "code":"877" }, { "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 ", "product_code":"mrs", "title":"ALM-43018 JobHistory2x Process Full GC Number Exceeds the Threshold", "uri":"ALM-43018.html", - "doc_type":"alarm", - "p_code":"583", - "code":"834" + "doc_type":"usermanual", + "p_code":"592", + "code":"878" }, { "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", "product_code":"mrs", "title":"ALM-43019 Heap Memory Usage of the IndexServer2x Process Exceeds the Threshold", "uri":"ALM-43019.html", - "doc_type":"alarm", - "p_code":"583", - "code":"835" + "doc_type":"usermanual", + "p_code":"592", + "code":"879" }, { "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", "product_code":"mrs", "title":"ALM-43020 Non-Heap Memory Usage of the IndexServer2x Process Exceeds the Threshold", "uri":"ALM-43020.html", - "doc_type":"alarm", - "p_code":"583", - "code":"836" + "doc_type":"usermanual", + "p_code":"592", + "code":"880" }, { "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", "product_code":"mrs", "title":"ALM-43021 Direct Memory Usage of the IndexServer2x Process Exceeds the Threshold", "uri":"ALM-43021.html", - "doc_type":"alarm", - "p_code":"583", - "code":"837" + "doc_type":"usermanual", + "p_code":"592", + "code":"881" }, { "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", "product_code":"mrs", "title":"ALM-43022 IndexServer2x Process GC Time Exceeds the Threshold", "uri":"ALM-43022.html", - "doc_type":"alarm", - "p_code":"583", - "code":"838" + "doc_type":"usermanual", + "p_code":"592", + "code":"882" }, { "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", "product_code":"mrs", "title":"ALM-43023 IndexServer2x Process Full GC Number Exceeds the Threshold", "uri":"ALM-43023.html", - "doc_type":"alarm", - "p_code":"583", - "code":"839" + "doc_type":"usermanual", + "p_code":"592", + "code":"883" + }, + { + "desc":"This section applies only to MRS 3.3.1-LTS or later.This alarm is generated when the JDBCServer process forwards requests and triffic control is triggered due to insuffic", + "product_code":"mrs", + "title":"ALM-43028 JDBCServer Session Overflow", + "uri":"ALM-43028.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"884" + }, + { + "desc":"This section applies only to MRS 3.5.0-LTS or later.After a user submits a JDBC job, the system attempts to create a JDBCServer process and establish a session connection", + "product_code":"mrs", + "title":"ALM-43029 JDBCServer Job Submission Timed Out", + "uri":"ALM-43029.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"885" }, { "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", "product_code":"mrs", "title":"ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold", "uri":"ALM-44004.html", - "doc_type":"alarm", - "p_code":"583", - "code":"840" + "doc_type":"usermanual", + "p_code":"592", + "code":"886" }, { "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", "product_code":"mrs", "title":"ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold", "uri":"ALM-44005.html", - "doc_type":"alarm", - "p_code":"583", - "code":"841" + "doc_type":"usermanual", + "p_code":"592", + "code":"887" }, { "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", "product_code":"mrs", "title":"ALM-44006 Presto Worker Process GC Time Exceeds the Threshold", "uri":"ALM-44006.html", - "doc_type":"alarm", - "p_code":"583", - "code":"842" + "doc_type":"usermanual", + "p_code":"592", + "code":"888" }, { "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", "product_code":"mrs", "title":"ALM-45000 HetuEngine Service Unavailable", "uri":"ALM-45000.html", - "doc_type":"alarm", - "p_code":"583", - "code":"843" + "doc_type":"usermanual", + "p_code":"592", + "code":"889" }, { "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", "product_code":"mrs", "title":"ALM-45001 Faulty HetuEngine Compute Instances", "uri":"ALM-45001.html", - "doc_type":"alarm", - "p_code":"583", - "code":"844" + "doc_type":"usermanual", + "p_code":"592", + "code":"890" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the HetuEngine QAS disk usage every 60 seconds and compares the actual disk usage with the threshold. The dis", "product_code":"mrs", "title":"ALM-45003 HetuEngine QAS Disk Capacity Is Insufficient", "uri":"ALM-45003.html", - "doc_type":"alarm", - "p_code":"583", - "code":"845" + "doc_type":"usermanual", + "p_code":"592", + "code":"891" + }, + { + "desc":"This section applies to MRS 3.3.1 or later.The system checks the number of running tasks on a HetuEngine compute instance every 30 seconds. This alarm is generated when t", + "product_code":"mrs", + "title":"ALM-45004 Tasks Stacked on HetuEngine Compute Instance", + "uri":"ALM-45004.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"892" + }, + { + "desc":"This section applies to MRS 3.3.1 or later.The system checks the average CPU usage of HetuEngine compute instances every 30 seconds. This alarm is generated when the aver", + "product_code":"mrs", + "title":"ALM-45005 CPU Usage of HetuEngine Compute Instance Exceeded the Threshold", + "uri":"ALM-45005.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"893" + }, + { + "desc":"This section applies to MRS 3.3.1 or later.The system checks the memory usage of HetuEngine compute instances every 30 seconds. This alarm is generated when the memory us", + "product_code":"mrs", + "title":"ALM-45006 Memory Usage of a HetuEngine Compute Instance Exceeded the Threshold", + "uri":"ALM-45006.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"894" + }, + { + "desc":"This section applies to MRS 3.3.1 or later.The system checks the number of Workers of a HetuEngine compute instance every 60 seconds. This alarm is generated when the num", + "product_code":"mrs", + "title":"ALM-45007 Number of Workers of a HetuEngine Compute Instance Is Less Than the Threshold", + "uri":"ALM-45007.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"895" + }, + { + "desc":"This section applies to MRS 3.5.0 or later.The system checks the query latency of HetuEngine compute instances every 30 seconds. This alarm is generated when the query la", + "product_code":"mrs", + "title":"ALM-45008 Query Latency of HetuEngine Compute Instances Exceeds the Threshold", + "uri":"ALM-45008.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"896" + }, + { + "desc":"This section applies to MRS 3.5.0 or later.The system checks the task failure rate of HetuEngine compute instances every 30 seconds. This alarm is generated when the task", + "product_code":"mrs", + "title":"ALM-45009 Task Failure Rate of HetuEngine Compute Instances Exceeds the Threshold", + "uri":"ALM-45009.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"897" }, { "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", "product_code":"mrs", "title":"ALM-45175 Average Time for Calling OBS Metadata APIs Is Greater than the Threshold", "uri":"ALM-45175.html", - "doc_type":"alarm", - "p_code":"583", - "code":"846" + "doc_type":"usermanual", + "p_code":"592", + "code":"898" }, { "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", "product_code":"mrs", "title":"ALM-45176 Success Rate of Calling OBS Metadata APIs Is Lower than the Threshold", "uri":"ALM-45176.html", - "doc_type":"alarm", - "p_code":"583", - "code":"847" + "doc_type":"usermanual", + "p_code":"592", + "code":"899" }, { "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", "product_code":"mrs", "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":"583", - "code":"848" + "doc_type":"usermanual", + "p_code":"592", + "code":"900" }, { "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", "product_code":"mrs", "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":"583", - "code":"849" + "doc_type":"usermanual", + "p_code":"592", + "code":"901" }, { "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", @@ -7646,8 +8114,8 @@ "title":"ALM-45179 Number of Failed OBS readFully API Calls Exceeds the Threshold", "uri":"ALM-45179.html", "doc_type":"usermanual", - "p_code":"583", - "code":"850" + "p_code":"592", + "code":"902" }, { "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", @@ -7655,8 +8123,8 @@ "title":"ALM-45180 Number of Failed OBS read API Calls Exceeds the Threshold", "uri":"ALM-45180.html", "doc_type":"usermanual", - "p_code":"583", - "code":"851" + "p_code":"592", + "code":"903" }, { "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", @@ -7664,8 +8132,8 @@ "title":"ALM-45181 Number of Failed OBS write API Calls Exceeds the Threshold", "uri":"ALM-45181.html", "doc_type":"usermanual", - "p_code":"583", - "code":"852" + "p_code":"592", + "code":"904" }, { "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", @@ -7673,224 +8141,242 @@ "title":"ALM-45182 Number of Throttled OBS Operations Exceeds the Threshold", "uri":"ALM-45182.html", "doc_type":"usermanual", - "p_code":"583", - "code":"853" + "p_code":"592", + "code":"905" }, { "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", "product_code":"mrs", "title":"ALM-45275 Ranger Service Unavailable", "uri":"ALM-45275.html", - "doc_type":"alarm", - "p_code":"583", - "code":"854" + "doc_type":"usermanual", + "p_code":"592", + "code":"906" }, { "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", "product_code":"mrs", "title":"ALM-45276 Abnormal RangerAdmin Status", "uri":"ALM-45276.html", - "doc_type":"alarm", - "p_code":"583", - "code":"855" + "doc_type":"usermanual", + "p_code":"592", + "code":"907" }, { "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", "product_code":"mrs", "title":"ALM-45277 RangerAdmin Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45277.html", - "doc_type":"alarm", - "p_code":"583", - "code":"856" + "doc_type":"usermanual", + "p_code":"592", + "code":"908" }, { "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", "product_code":"mrs", "title":"ALM-45278 RangerAdmin Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45278.html", - "doc_type":"alarm", - "p_code":"583", - "code":"857" + "doc_type":"usermanual", + "p_code":"592", + "code":"909" }, { "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", "product_code":"mrs", "title":"ALM-45279 RangerAdmin Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45279.html", - "doc_type":"alarm", - "p_code":"583", - "code":"858" + "doc_type":"usermanual", + "p_code":"592", + "code":"910" }, { "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", "product_code":"mrs", "title":"ALM-45280 RangerAdmin GC Duration Exceeds the Threshold", "uri":"ALM-45280.html", - "doc_type":"alarm", - "p_code":"583", - "code":"859" + "doc_type":"usermanual", + "p_code":"592", + "code":"911" }, { "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", "product_code":"mrs", "title":"ALM-45281 UserSync Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45281.html", - "doc_type":"alarm", - "p_code":"583", - "code":"860" + "doc_type":"usermanual", + "p_code":"592", + "code":"912" }, { "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 ", "product_code":"mrs", "title":"ALM-45282 UserSync Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45282.html", - "doc_type":"alarm", - "p_code":"583", - "code":"861" + "doc_type":"usermanual", + "p_code":"592", + "code":"913" }, { "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", "product_code":"mrs", "title":"ALM-45283 UserSync Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45283.html", - "doc_type":"alarm", - "p_code":"583", - "code":"862" + "doc_type":"usermanual", + "p_code":"592", + "code":"914" }, { "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", "product_code":"mrs", "title":"ALM-45284 UserSync Garbage Collection (GC) Time Exceeds the Threshold", "uri":"ALM-45284.html", - "doc_type":"alarm", - "p_code":"583", - "code":"863" + "doc_type":"usermanual", + "p_code":"592", + "code":"915" }, { "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", "product_code":"mrs", "title":"ALM-45285 TagSync Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45285.html", - "doc_type":"alarm", - "p_code":"583", - "code":"864" + "doc_type":"usermanual", + "p_code":"592", + "code":"916" }, { "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", "product_code":"mrs", "title":"ALM-45286 TagSync Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45286.html", - "doc_type":"alarm", - "p_code":"583", - "code":"865" + "doc_type":"usermanual", + "p_code":"592", + "code":"917" }, { "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", "product_code":"mrs", "title":"ALM-45287 TagSync Non Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45287.html", - "doc_type":"alarm", - "p_code":"583", - "code":"866" + "doc_type":"usermanual", + "p_code":"592", + "code":"918" }, { "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", "product_code":"mrs", "title":"ALM-45288 TagSync Garbage Collection (GC) Time Exceeds the Threshold", "uri":"ALM-45288.html", - "doc_type":"alarm", - "p_code":"583", - "code":"867" + "doc_type":"usermanual", + "p_code":"592", + "code":"919" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the heap memory usage of the PolicySync service every 60 seconds. This alarm is generated when the heap ", - "product_code":"", + "product_code":"mrs", "title":"ALM-45289 PolicySync Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45289.html", - "doc_type":"", - "p_code":"583", - "code":"868" + "doc_type":"usermanual", + "p_code":"592", + "code":"920" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the direct memory usage of the PolicySync service every 60 seconds. This alarm is generated when the dir", - "product_code":"", + "product_code":"mrs", "title":"ALM-45290 PolicySync Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45290.html", - "doc_type":"", - "p_code":"583", - "code":"869" + "doc_type":"usermanual", + "p_code":"592", + "code":"921" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the non-heap memory usage of the PolicySync service every 60 seconds. This alarm is generated when the n", - "product_code":"", + "product_code":"mrs", "title":"ALM-45291 PolicySync Non-Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45291.html", - "doc_type":"", - "p_code":"583", - "code":"870" + "doc_type":"usermanual", + "p_code":"592", + "code":"922" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the GC duration of the PolicySync process every 60 seconds. This alarm is generated when the GC duration", - "product_code":"", + "product_code":"mrs", "title":"ALM-45292 PolicySync GC Duration Exceeds the Threshold", "uri":"ALM-45292.html", - "doc_type":"", - "p_code":"583", - "code":"871" + "doc_type":"usermanual", + "p_code":"592", + "code":"923" + }, + { + "desc":"The system checks synchronization status of the UserSync process every 5 minutes. This alarm is generated when a synchronization exception occurs. This alarm is cleared w", + "product_code":"mrs", + "title":"ALM-45293 Ranger User Synchronization Exception", + "uri":"ALM-45293.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"924" + }, + { + "desc":"The RangerKMS process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.This al", + "product_code":"mrs", + "title":"ALM-45294 RangerKMS Process Is Abnormal", + "uri":"ALM-45294.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"925" }, { "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.", "product_code":"mrs", "title":"ALM-45425 ClickHouse Service Unavailable", "uri":"ALM-45425.html", - "doc_type":"alarm", - "p_code":"583", - "code":"872" + "doc_type":"usermanual", + "p_code":"592", + "code":"926" }, { "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 ", "product_code":"mrs", "title":"ALM-45426 ClickHouse Service Quantity Quota Usage in ZooKeeper Exceeds the Threshold", "uri":"ALM-45426.html", - "doc_type":"alarm", - "p_code":"583", - "code":"873" + "doc_type":"usermanual", + "p_code":"592", + "code":"927" }, { "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 ", "product_code":"mrs", "title":"ALM-45427 ClickHouse Service Capacity Quota Usage in ZooKeeper Exceeds the Threshold", "uri":"ALM-45427.html", - "doc_type":"alarm", - "p_code":"583", - "code":"874" + "doc_type":"usermanual", + "p_code":"592", + "code":"928" }, { "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", "product_code":"mrs", "title":"ALM-45428 ClickHouse Disk I/O Exception", "uri":"ALM-45428.html", - "doc_type":"alarm", - "p_code":"583", - "code":"875" + "doc_type":"usermanual", + "p_code":"592", + "code":"929" }, { "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", "product_code":"mrs", "title":"ALM-45429 Table Metadata Synchronization Failed on the Added ClickHouse Node", "uri":"ALM-45429.html", - "doc_type":"alarm", - "p_code":"583", - "code":"876" + "doc_type":"usermanual", + "p_code":"592", + "code":"930" }, { "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", "product_code":"mrs", "title":"ALM-45430 Permission Metadata Synchronization Failed on the Added ClickHouse Node", "uri":"ALM-45430.html", - "doc_type":"alarm", - "p_code":"583", - "code":"877" + "doc_type":"usermanual", + "p_code":"592", + "code":"931" }, { "desc":"The ClickHouseServer instance distribution does not meet the topology allocation requirements.Some ClickHouseServer instances are unavailable.During installation or capac", @@ -7898,8 +8384,8 @@ "title":"ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation", "uri":"ALM-45431.html", "doc_type":"usermanual", - "p_code":"583", - "code":"878" + "p_code":"592", + "code":"932" }, { "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", @@ -7907,8 +8393,8 @@ "title":"ALM-45432 ClickHouse User Synchronization Process Fails", "uri":"ALM-45432.html", "doc_type":"usermanual", - "p_code":"583", - "code":"879" + "p_code":"592", + "code":"933" }, { "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", @@ -7916,8 +8402,8 @@ "title":"ALM-45433 ClickHouse AZ Topology Exception", "uri":"ALM-45433.html", "doc_type":"usermanual", - "p_code":"583", - "code":"880" + "p_code":"592", + "code":"934" }, { "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", @@ -7925,143 +8411,278 @@ "title":"ALM-45434 A Single Replica Exists in the ClickHouse Data Table", "uri":"ALM-45434.html", "doc_type":"usermanual", - "p_code":"583", - "code":"881" + "p_code":"592", + "code":"935" }, { "desc":"This section applies only to MRS 3.3.0 or later.This alarm is generated when the metadata in a distributed table or in the local table of the distributed table has been i", - "product_code":"", + "product_code":"mrs", "title":"ALM-45435 Inconsistent Metadata of ClickHouse Tables", "uri":"ALM-45435.html", - "doc_type":"", - "p_code":"583", - "code":"882" + "doc_type":"usermanual", + "p_code":"592", + "code":"936" }, { "desc":"This section applies only to MRS 3.3.0 or later.This alarm is generated when data skew occurs in the local table of a distributed table between ClickHouse nodes. This ala", - "product_code":"", + "product_code":"mrs", "title":"ALM-45436 Skew ClickHouse Table Data", "uri":"ALM-45436.html", - "doc_type":"", - "p_code":"583", - "code":"883" + "doc_type":"usermanual", + "p_code":"592", + "code":"937" }, { "desc":"This section applies only to MRS 3.3.0 or later.This alarm is generated when the number of parts exceeds the threshold specified by part_num_threshold.This alarm is autom", - "product_code":"", + "product_code":"mrs", "title":"ALM-45437 Excessive Parts in the ClickHouse Table", "uri":"ALM-45437.html", - "doc_type":"", - "p_code":"583", - "code":"884" + "doc_type":"usermanual", + "p_code":"592", + "code":"938" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the disk capacity of the ClickHouseServer node every 1 minute. This alarm is generated when the usage of", - "product_code":"", + "product_code":"mrs", "title":"ALM-45438 ClickHouse Disk Usage Exceeds 80%", "uri":"ALM-45438.html", - "doc_type":"", - "p_code":"583", - "code":"885" + "doc_type":"usermanual", + "p_code":"592", + "code":"939" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the disk capacity of the ClickHouseServer node every 1 minute. This alarm is generated when the system d", - "product_code":"", + "product_code":"mrs", "title":"ALM-45439 ClickHouse Node Enters the Read-Only Mode", "uri":"ALM-45439.html", - "doc_type":"", - "p_code":"583", - "code":"886" + "doc_type":"usermanual", + "p_code":"592", + "code":"940" }, { "desc":"This section applies only to MRS 3.3.0 or later.When the number of ClickHouse replicas is greater than 1, the system periodically checks the replicated table. This alarm ", - "product_code":"", + "product_code":"mrs", "title":"ALM-45440 Inconsistency Between ClickHouse Replicas", "uri":"ALM-45440.html", - "doc_type":"", - "p_code":"583", - "code":"887" + "doc_type":"usermanual", + "p_code":"592", + "code":"941" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the connection between ClickHouse and ZooKeeper every minute. This alarm is generated when the connectio", - "product_code":"", + "product_code":"mrs", "title":"ALM-45441 Zookeeper Disconnected", "uri":"ALM-45441.html", - "doc_type":"", - "p_code":"583", - "code":"888" + "doc_type":"usermanual", + "p_code":"592", + "code":"942" }, { "desc":"This section applies only to MRS 3.3.0 or later.The alarm module checks the number of concurrent ClickHouse requests every 30 seconds. This alarm is generated when the nu", - "product_code":"", + "product_code":"mrs", "title":"ALM-45442 Too Many Concurrent SQL Statements", "uri":"ALM-45442.html", - "doc_type":"", - "p_code":"583", - "code":"889" + "doc_type":"usermanual", + "p_code":"592", + "code":"943" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks slow SQL queries for ClickHouse every 1 minute. This alarm is generated when the execution time of a SQL", - "product_code":"", + "product_code":"mrs", "title":"ALM-45443 Slow SQL Queries in the Cluster", "uri":"ALM-45443.html", - "doc_type":"", - "p_code":"583", - "code":"890" + "doc_type":"usermanual", + "p_code":"592", + "code":"944" }, { "desc":"This section applies only to MRS 3.3.0 or later.The health check module checks ClickHouse instances every 30 seconds. If the number of consecutive failures exceeds the th", - "product_code":"", + "product_code":"mrs", "title":"ALM-45444 Abnormal ClickHouse Process", "uri":"ALM-45444.html", - "doc_type":"", - "p_code":"583", - "code":"891" + "doc_type":"usermanual", + "p_code":"592", + "code":"945" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.The ClickHouse instance checks the distributed table every 300 seconds. If the number of consecutive fai", + "product_code":"mrs", + "title":"ALM-45445 Failed to Send Data Files to Remote Shards When ClickHouse Writes Data to a Distributed Table", + "uri":"ALM-45445.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"946" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.The system checks mutation tasks every 5 minutes. This alarm is generated when the system detects that a", + "product_code":"mrs", + "title":"ALM-45446 Mutation Task of ClickHouse Is Not Complete for a Long Time", + "uri":"ALM-45446.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"947" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.The system checks the table status every minute. This alarm is generated when the system detects that a ", + "product_code":"mrs", + "title":"ALM-45447 ClickHouse Table Read-Only", + "uri":"ALM-45447.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"948" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.Metadata in ClickHouse is stored on ZooKeeper Znodes. The number of occupied Znodes may increase sharply", + "product_code":"mrs", + "title":"ALM-45448 Rapid Increase of Znodes Used by ClickHouse", + "uri":"ALM-45448.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"949" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.ClickHouse uses ZooKeeper Transaction ID (zxid) to manage transactions. The zxid is a 64-bit number used", + "product_code":"mrs", + "title":"ALM-45449 The Counter Number of zxid Used by ClickHouse Exceeds the Threshold", + "uri":"ALM-45449.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"950" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.After the cold-hot separation function and an agency are configured, the system checks the status of the", + "product_code":"mrs", + "title":"ALM-45450 ClickHouse Failed to Obtain a Temporary Agency Credential", + "uri":"ALM-45450.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"951" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.When cold-hot separation is enabled, the system checks the OBS access every minute. This alarm is genera", + "product_code":"mrs", + "title":"ALM-45451 ClickHouse Failed to Access OBS", + "uri":"ALM-45451.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"952" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.When cold-hot separation is enabled, the system checks the remaining space of the local disk specified i", + "product_code":"mrs", + "title":"ALM-45452 ClickHouse's Local Disk Space Is Below the Cold-Hot Separation Threshold", + "uri":"ALM-45452.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"953" + }, + { + "desc":"The system checks the replica status of the Kudu data table. This alarm is generated when a single replica is detected in the Kudu data table.This alarm is cleared when a", + "product_code":"mrs", + "title":"ALM-45475 A Single Replica Exists in the Kudu Data Table", + "uri":"ALM-45475.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"954" + }, + { + "desc":"Kudu will enter the maintenance mode during disk replacement. This alarm is generated when Kudu fails to enter the maintenance mode.This alarm is cleared when Kudu succes", + "product_code":"mrs", + "title":"ALM-45476 Kudu Failed to Enter the Maintenance Mode", + "uri":"ALM-45476.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"955" + }, + { + "desc":"This alarm is generated when Kudu fails to restore data by invoking the script in SetupTool after a disk is replaced.This alarm is cleared when the data is successfully r", + "product_code":"mrs", + "title":"ALM-45477 Failed to Restore Data After a Disk of Kudu Is Replaced", + "uri":"ALM-45477.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"956" + }, + { + "desc":"The system periodically balances data among Kudu data tables. This alarm is generated when the system detects that the data balancing API returns a failure response.This ", + "product_code":"mrs", + "title":"ALM-45478 Kudu Failed Data Balancing", + "uri":"ALM-45478.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"957" + }, + { + "desc":"The system checks the Kudu service status every 60 seconds. This alarm is generated when the number of tablets of the Tserver process exceeds the threshold.This alarm is ", + "product_code":"mrs", + "title":"ALM-45479 Number of Tablets of the Tserver Process Exceeds the Threshold", + "uri":"ALM-45479.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"958" + }, + { + "desc":"The system checks the Kudu service status every 60 seconds. This alarm is generated when the ratio of tablet leaders of a Tserver process to total tablet leaders in the c", + "product_code":"mrs", + "title":"ALM-45480 Tablet Leaders of a Tserver Process Are Unevenly Distributed", + "uri":"ALM-45480.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"959" + }, + { + "desc":"The system checks Kudu disk metrics every 60 seconds. This alarm is generated when the number of fully occupied disks for a Tserver is not 0.This alarm is automatically c", + "product_code":"mrs", + "title":"ALM-45481 KuduTserver Has Full Disks", + "uri":"ALM-45481.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"960" }, { "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 ", "product_code":"mrs", "title":"ALM-45585 IoTDB Service Unavailable", "uri":"ALM-45585.html", - "doc_type":"alarm", - "p_code":"583", - "code":"892" + "doc_type":"usermanual", + "p_code":"592", + "code":"961" }, { "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%", "product_code":"mrs", "title":"ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45586.html", - "doc_type":"alarm", - "p_code":"583", - "code":"893" + "doc_type":"usermanual", + "p_code":"592", + "code":"962" }, { "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) ", "product_code":"mrs", "title":"ALM-45587 IoTDBServer GC Duration Exceeds the Threshold", "uri":"ALM-45587.html", - "doc_type":"alarm", - "p_code":"583", - "code":"894" + "doc_type":"usermanual", + "p_code":"592", + "code":"963" }, { "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", "product_code":"mrs", "title":"ALM-45588 IoTDBServer Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45588.html", - "doc_type":"alarm", - "p_code":"583", - "code":"895" + "doc_type":"usermanual", + "p_code":"592", + "code":"964" }, { "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", "product_code":"mrs", "title":"ALM-45589 ConfigNode Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45589.html", - "doc_type":"alarm", - "p_code":"583", - "code":"896" + "doc_type":"usermanual", + "p_code":"592", + "code":"965" }, { "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", @@ -8069,8 +8690,8 @@ "title":"ALM-45590 ConfigNode GC Duration Exceeds the Threshold", "uri":"ALM-45590.html", "doc_type":"usermanual", - "p_code":"583", - "code":"897" + "p_code":"592", + "code":"966" }, { "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", @@ -8078,8 +8699,8 @@ "title":"ALM-45591 ConfigNode Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45591.html", "doc_type":"usermanual", - "p_code":"583", - "code":"898" + "p_code":"592", + "code":"967" }, { "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 ", @@ -8087,8 +8708,8 @@ "title":"ALM-45592 IoTDBServer RPC Execution Duration Exceeds the Threshold", "uri":"ALM-45592.html", "doc_type":"usermanual", - "p_code":"583", - "code":"899" + "p_code":"592", + "code":"968" }, { "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", @@ -8096,8 +8717,8 @@ "title":"ALM-45593 IoTDBServer Flush Execution Duration Exceeds the Threshold", "uri":"ALM-45593.html", "doc_type":"usermanual", - "p_code":"583", - "code":"900" + "p_code":"592", + "code":"969" }, { "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.", @@ -8105,8 +8726,8 @@ "title":"ALM-45594 IoTDBServer Intra-Space Merge Duration Exceeds the Threshold", "uri":"ALM-45594.html", "doc_type":"usermanual", - "p_code":"583", - "code":"901" + "p_code":"592", + "code":"970" }, { "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", @@ -8114,17 +8735,17 @@ "title":"ALM-45595 IoTDBServer Cross-Space Merge Duration Exceeds the Threshold", "uri":"ALM-45595.html", "doc_type":"usermanual", - "p_code":"583", - "code":"902" + "p_code":"592", + "code":"971" }, { "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", "product_code":"mrs", "title":"ALM-45615 CDL Service Unavailable", "uri":"ALM-45615.html", - "doc_type":"alarm", - "p_code":"583", - "code":"903" + "doc_type":"usermanual", + "p_code":"592", + "code":"972" }, { "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", @@ -8132,8 +8753,8 @@ "title":"ALM-45616 CDL Job Execution Exception", "uri":"ALM-45616.html", "doc_type":"usermanual", - "p_code":"583", - "code":"904" + "p_code":"592", + "code":"973" }, { "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", @@ -8141,512 +8762,647 @@ "title":"ALM-45617 Data Queued in the CDL Replication Slot Exceeds the Threshold", "uri":"ALM-45617.html", "doc_type":"usermanual", - "p_code":"583", - "code":"905" + "p_code":"592", + "code":"974" }, { "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", "product_code":"mrs", "title":"ALM-45635 FlinkServer Job Execution Failure", "uri":"ALM-45635.html", - "doc_type":"alarm", - "p_code":"583", - "code":"906" + "doc_type":"usermanual", + "p_code":"592", + "code":"975" }, { "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", "product_code":"mrs", "title":"ALM-45636 FlinkServer Job Checkpoints Keep Failing", "uri":"ALM-45636.html", - "doc_type":"alarm", - "p_code":"583", - "code":"907" + "doc_type":"usermanual", + "p_code":"592", + "code":"976" }, { "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", "product_code":"mrs", "title":"ALM-45636 Flink Job Checkpoints Keep Failing", "uri":"ALM-45636-1.html", - "doc_type":"alarm", - "p_code":"583", - "code":"908" + "doc_type":"usermanual", + "p_code":"592", + "code":"977" }, { "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", "product_code":"mrs", "title":"ALM-45637 FlinkServer Task Is Continuously Under Back Pressure", "uri":"ALM-45637.html", - "doc_type":"alarm", - "p_code":"583", - "code":"909" + "doc_type":"usermanual", + "p_code":"592", + "code":"978" }, { "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", "product_code":"mrs", "title":"ALM-45638 Number of Restarts After FlinkServer Job Failures Exceeds the Threshold", "uri":"ALM-45638.html", - "doc_type":"alarm", - "p_code":"583", - "code":"910" + "doc_type":"usermanual", + "p_code":"592", + "code":"979" }, { "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", "product_code":"mrs", "title":"ALM-45638 Number of Restarts After Flink Job Failures Exceeds the Threshold", "uri":"ALM-45638-1.html", - "doc_type":"alarm", - "p_code":"583", - "code":"911" + "doc_type":"usermanual", + "p_code":"592", + "code":"980" }, { "desc":"The system checks the checkpointing timeout of Flink jobs every 30 seconds. This alarm is generated if the checkpointing timeout of a Flink job is longer than the thresho", "product_code":"mrs", "title":"ALM-45639 Checkpointing of a Flink Job Times Out", "uri":"ALM-45639.html", - "doc_type":"alarm", - "p_code":"583", - "code":"912" + "doc_type":"usermanual", + "p_code":"592", + "code":"981" }, { "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", "product_code":"mrs", "title":"ALM-45640 FlinkServer Heartbeat Interruption Between the Active and Standby Nodes", "uri":"ALM-45640.html", - "doc_type":"alarm", - "p_code":"583", - "code":"913" + "doc_type":"usermanual", + "p_code":"592", + "code":"982" }, { "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", "product_code":"mrs", "title":"ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes", "uri":"ALM-45641.html", - "doc_type":"alarm", - "p_code":"583", - "code":"914" + "doc_type":"usermanual", + "p_code":"592", + "code":"983" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45642 RocksDB Continuously Triggers Write Traffic Limiting", "uri":"ALM-45642.html", - "doc_type":"", - "p_code":"583", - "code":"915" + "doc_type":"usermanual", + "p_code":"592", + "code":"984" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45643 MemTable Size of RocksDB Continuously Exceeds the Threshold", "uri":"ALM-45643.html", - "doc_type":"", - "p_code":"583", - "code":"916" + "doc_type":"usermanual", + "p_code":"592", + "code":"985" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45644 Number of SST Files at Level 0 of RocksDB Continuously Exceeds the Threshold", "uri":"ALM-45644.html", - "doc_type":"", - "p_code":"583", - "code":"917" + "doc_type":"usermanual", + "p_code":"592", + "code":"986" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45645 Pending Flush Size of RocksDB Continuously Exceeds the Threshold", "uri":"ALM-45645.html", - "doc_type":"", - "p_code":"583", - "code":"918" + "doc_type":"usermanual", + "p_code":"592", + "code":"987" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45646 Pending Compaction Size of RocksDB Continuously Exceeds the Threshold", "uri":"ALM-45646.html", - "doc_type":"", - "p_code":"583", - "code":"919" + "doc_type":"usermanual", + "p_code":"592", + "code":"988" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45647 Estimated Pending Compaction Size of RocksDB Continuously Exceeds the Threshold", "uri":"ALM-45647.html", - "doc_type":"", - "p_code":"583", - "code":"920" + "doc_type":"usermanual", + "p_code":"592", + "code":"989" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45648 RocksDB Frequently Encounters Write-Stopped", "uri":"ALM-45648.html", - "doc_type":"", - "p_code":"583", - "code":"921" + "doc_type":"usermanual", + "p_code":"592", + "code":"990" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45649 P95 Latency of RocksDB Get Requests Continuously Exceeds the Threshold", "uri":"ALM-45649.html", - "doc_type":"", - "p_code":"583", - "code":"922" + "doc_type":"usermanual", + "p_code":"592", + "code":"991" }, { "desc":"This section applies to MRS 3.3.0 or later.The system checks the RocksDB monitoring data of jobs at the user-specified alarm reporting interval (metrics.reporter.alarm.jo", - "product_code":"", + "product_code":"mrs", "title":"ALM-45650 P95 Latency of RocksDB Write Requests Continuously Exceeds the Threshold", "uri":"ALM-45650.html", - "doc_type":"", - "p_code":"583", - "code":"923" + "doc_type":"usermanual", + "p_code":"592", + "code":"992" }, { "desc":"This section applies to MRS 3.3.0 or later.The alarm module checks the Flink status every 60 seconds. This alarm is generated when the Flink service is unavailable. This ", - "product_code":"", + "product_code":"mrs", "title":"ALM-45652 Flink Service Unavailable", "uri":"ALM-45652.html", - "doc_type":"", - "p_code":"583", - "code":"924" + "doc_type":"usermanual", + "p_code":"592", + "code":"993" }, { "desc":"This section applies to MRS 3.3.0 or later.Flink checks whether the HA certificate file is valid (whether the certificate exists and whether its format is correct) in the", - "product_code":"", + "product_code":"mrs", "title":"ALM-45653 Invalid Flink HA Certificate File", "uri":"ALM-45653.html", - "doc_type":"", - "p_code":"583", - "code":"925" + "doc_type":"usermanual", + "p_code":"592", + "code":"994" }, { "desc":"This section applies to MRS 3.3.0 or later.Flink checks whether the HA certificate file is about to expire in the first health check or at 01:00:00 every day. This alarm ", - "product_code":"", + "product_code":"mrs", "title":"ALM-45654 Flink HA Certificate Is About to Expire", "uri":"ALM-45654.html", - "doc_type":"", - "p_code":"583", - "code":"926" + "doc_type":"usermanual", + "p_code":"592", + "code":"995" }, { "desc":"This section applies to MRS 3.3.0 or later.Flink checks whether the HA certificate file has expired in the first health check or at 01:00:00 every day. This alarm is gene", - "product_code":"", + "product_code":"mrs", "title":"ALM-45655 Flink HA Certificate File Has Expired", "uri":"ALM-45655.html", - "doc_type":"", - "p_code":"583", - "code":"927" + "doc_type":"usermanual", + "p_code":"592", + "code":"996" }, { "desc":"The alarm module checks the Guardian service status every 60 seconds. This alarm is generated if Guardian is unavailable.This alarm is cleared after Guardian recovers.Gua", "product_code":"mrs", "title":"ALM-45736 Guardian Service Unavailable", "uri":"ALM-45736.html", - "doc_type":"alarm", - "p_code":"583", - "code":"928" + "doc_type":"usermanual", + "p_code":"592", + "code":"997" }, { "desc":"The system checks the heap memory usage of the TokenServer service every 60 seconds. This alarm is generated when the heap memory usage of the TokenServer instance exceed", - "product_code":"", + "product_code":"mrs", "title":"ALM-45737 TokenServer Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45737.html", - "doc_type":"", - "p_code":"583", - "code":"929" + "doc_type":"usermanual", + "p_code":"592", + "code":"998" }, { "desc":"The system checks the direct memory usage of the TokenServer service every 60 seconds. This alarm is generated when the direct memory usage of the TokenServer instance ex", - "product_code":"", + "product_code":"mrs", "title":"ALM-45738 TokenServer Direct Memory Usage Exceeds the Threshold", "uri":"ALM-45738.html", - "doc_type":"", - "p_code":"583", - "code":"930" + "doc_type":"usermanual", + "p_code":"592", + "code":"999" }, { "desc":"The system checks the heap memory usage of the TokenServer service every 60 seconds. This alarm is generated when the non-heap memory usage of the TokenServer instance ex", - "product_code":"", + "product_code":"mrs", "title":"ALM-45739 TokenServer Non-Heap Memory Usage Exceeds the Threshold", "uri":"ALM-45739.html", - "doc_type":"", - "p_code":"583", - "code":"931" + "doc_type":"usermanual", + "p_code":"592", + "code":"1000" }, { "desc":"The system checks the GC duration of the TokenServer process every 60 seconds. This alarm is generated when the GC duration of the TokenServer process exceeds the thresho", - "product_code":"", + "product_code":"mrs", "title":"ALM-45740 TokenServer GC Duration Exceeds the Threshold", "uri":"ALM-45740.html", - "doc_type":"", - "p_code":"583", - "code":"932" + "doc_type":"usermanual", + "p_code":"592", + "code":"1001" }, { "desc":"Guardian caches the temporary AK/SK of the ECS agency. When the cache does not exist or is about to expire, Guardian calls the securitykey API of ECS to update the AK/SK.", "product_code":"mrs", "title":"ALM-45741 Failed to Call the ECS securitykey API", "uri":"ALM-45741.html", - "doc_type":"alarm", - "p_code":"583", - "code":"933" + "doc_type":"usermanual", + "p_code":"592", + "code":"1002" }, { "desc":"When Guardian calls an IAM API to obtain the temporary AK/SK, it needs to first obtain related metadata via the ECS Metadata API. This alarm is generated when Guardian fa", "product_code":"mrs", "title":"ALM-45742 Failed to Call the ECS Metadata API", "uri":"ALM-45742.html", - "doc_type":"alarm", - "p_code":"583", - "code":"934" + "doc_type":"usermanual", + "p_code":"592", + "code":"1003" }, { "desc":"This alarm is generated when Guardian fails to call the IAM API to obtain a temporary AK/SK.The task may fail to obtain the temporary AK/SK for accessing OBS. As a result", "product_code":"mrs", "title":"ALM-45743 Failed to Call the IAM API", "uri":"ALM-45743.html", - "doc_type":"alarm", - "p_code":"583", - "code":"935" + "doc_type":"usermanual", + "p_code":"592", + "code":"1004" + }, + { + "desc":"The system checks the average RPC processing time of the TokenServer service every 30 seconds. This alarm is generated when the average RPC processing time of the TokenSe", + "product_code":"mrs", + "title":"ALM-45744 Average RPC Processing Time of the Guardian TokenServer Exceeds the Threshold", + "uri":"ALM-45744.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1005" + }, + { + "desc":"The system checks the average RPC queuing time of the TokenServer service every 30 seconds. This alarm is generated when the average RPC queuing time of the TokenServer i", + "product_code":"mrs", + "title":"ALM-45745 Average RPC Queuing Time of the Guardian TokenServer Exceeds the Threshold", + "uri":"ALM-45745.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1006" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.The system checks the status of the ZooKeeper service on which the MemArtsCC depends every 60 seconds. T", + "product_code":"mrs", + "title":"ALM-47001 MemArtsCC Service Unavailable", + "uri":"ALM-47001.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1007" + }, + { + "desc":"This section is available for MRS 3.3.1-LTS or later version only.The alarm module checks the status of the local disk used by MemArtsCC every 60 seconds. This alarm is g", + "product_code":"mrs", + "title":"ALM-47002 MemArtsCC Disk Fault", + "uri":"ALM-47002.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1008" + }, + { + "desc":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the memory usage of the CCWorker process of the MemArtsCC component every 30 seconds. ", + "product_code":"mrs", + "title":"ALM-47003 Memory Usage of the MemArtsCC Worker Process Exceeds the Threshold", + "uri":"ALM-47003.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1009" + }, + { + "desc":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the average latency of all read requests to the MemArtsCC Worker process component eve", + "product_code":"mrs", + "title":"ALM-47004 Average Latency of MemArtsCC Worker Read Requests Exceeds the Threshold", + "uri":"ALM-47004.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1010" }, { "desc":"The alarm module checks the Doris service status every 60 seconds. This alarm is generated when the alarm module detects that all FE and BE instances are abnormal.This al", - "product_code":"", + "product_code":"mrs", "title":"ALM-50201 Doris Service Unavailable", "uri":"ALM-50201.html", - "doc_type":"", - "p_code":"583", - "code":"936" + "doc_type":"usermanual", + "p_code":"592", + "code":"1011" }, { "desc":"The system checks the CPU usage of the FE instance every 30 seconds. The CPU usage has a default threshold. This alarm is generated when the CPU usage exceeds the thresho", - "product_code":"", + "product_code":"mrs", "title":"ALM-50202 FE CPU Usage Exceeds the Threshold", "uri":"ALM-50202.html", - "doc_type":"", - "p_code":"583", - "code":"937" + "doc_type":"usermanual", + "p_code":"592", + "code":"1012" }, { "desc":"The system checks the memory usage of the FE instance every 30 seconds. This alarm is generated when the memory usage exceeds the threshold (95% by default) for multiple ", - "product_code":"", + "product_code":"mrs", "title":"ALM-50203 FE Memory Usage Exceeds the Threshold", "uri":"ALM-50203.html", - "doc_type":"", - "p_code":"583", - "code":"938" + "doc_type":"usermanual", + "p_code":"592", + "code":"1013" }, { "desc":"The system checks the CPU usage of the BE instance every 30 seconds. This alarm is generated when the CPU usage exceeds the threshold (95% by default) for multiple consec", - "product_code":"", + "product_code":"mrs", "title":"ALM-50205 BE CPU Usage Exceeds the Threshold", "uri":"ALM-50205.html", - "doc_type":"", - "p_code":"583", - "code":"939" + "doc_type":"usermanual", + "p_code":"592", + "code":"1014" }, { "desc":"The system checks the memory usage of the BE instance every 30 seconds. This alarm is generated when the memory usage exceeds the threshold for multiple consecutive times", - "product_code":"", + "product_code":"mrs", "title":"ALM-50206 BE Memory Usage Exceeds the Threshold", "uri":"ALM-50206.html", - "doc_type":"", - "p_code":"583", - "code":"940" + "doc_type":"usermanual", + "p_code":"592", + "code":"1015" }, { "desc":"The system checks the number of MySQL port connections every 30 seconds. This alarm is generated when the ratio of the number of current connections to the maximum number", - "product_code":"", + "product_code":"mrs", "title":"ALM-50207 Ratio of Connections to the FE MySQL Port to the Maximum Connections Allowed Exceeds the Threshold", "uri":"ALM-50207.html", - "doc_type":"", - "p_code":"583", - "code":"941" + "doc_type":"usermanual", + "p_code":"592", + "code":"1016" }, { "desc":"The system checks the number of failures to clear historical metadata image files on the FE node every 30 seconds. This alarm is generated when the number of failures exc", - "product_code":"", + "product_code":"mrs", "title":"ALM-50208 Failures to Clear Historical Metadata Image Files Exceed the Threshold", "uri":"ALM-50208.html", - "doc_type":"", - "p_code":"583", - "code":"942" + "doc_type":"usermanual", + "p_code":"592", + "code":"1017" }, { "desc":"The system checks the number of failures to generate metadata image files on the FE node every 30 seconds. This alarm is generated when the number of failures exceeds the", - "product_code":"", + "product_code":"mrs", "title":"ALM-50209 Failures to Generate Metadata Image Files Exceed the Threshold", "uri":"ALM-50209.html", - "doc_type":"", - "p_code":"583", - "code":"943" + "doc_type":"usermanual", + "p_code":"592", + "code":"1018" }, { "desc":"The system checks the maximum compaction score of all BE nodes every 30 seconds. This alarm is generated when the maximum compaction score exceeds the threshold (10 by de", - "product_code":"", + "product_code":"mrs", "title":"ALM-50210 Maximum Compaction Score of All BE Nodes Exceeds the Threshold", "uri":"ALM-50210.html", - "doc_type":"", - "p_code":"583", - "code":"944" + "doc_type":"usermanual", + "p_code":"592", + "code":"1019" }, { "desc":"The system checks the queue length of each BE periodic report task on FE every 30 seconds. This alarm is generated when the queue length exceeds the threshold (10 by defa", - "product_code":"", + "product_code":"mrs", "title":"ALM-50211 FE Queue Length of BE Periodic Report Tasks Exceeds the Threshold", "uri":"ALM-50211.html", - "doc_type":"", - "p_code":"583", - "code":"945" + "doc_type":"usermanual", + "p_code":"592", + "code":"1020" }, { "desc":"The system checks the accumulated old-generation GC duration of the FE process every 30 seconds. This alarm is generated when the accumulated GC duration exceeds the thre", - "product_code":"", + "product_code":"mrs", "title":"ALM-50212 Accumulated Old-Generation GC Duration of the FE Process Exceeds the Threshold", "uri":"ALM-50212.html", - "doc_type":"", - "p_code":"583", - "code":"946" + "doc_type":"usermanual", + "p_code":"592", + "code":"1021" }, { "desc":"The system checks the number of queuing tasks in the FE thread pool for interacting with BE every 30 seconds. This alarm is generated when the number of queuing tasks exc", - "product_code":"", + "product_code":"mrs", "title":"ALM-50213 Number of Tasks Queuing in the FE Thread Pool for Interacting with BE Exceeds the Threshold", "uri":"ALM-50213.html", - "doc_type":"", - "p_code":"583", - "code":"947" + "doc_type":"usermanual", + "p_code":"592", + "code":"1022" }, { "desc":"The system checks the number of queuing tasks in the FE thread pool for processing tasks every 30 seconds. This alarm is generated when the number of queuing tasks exceed", - "product_code":"", + "product_code":"mrs", "title":"ALM-50214 Number of Tasks Queuing in the FE Thread Pool for Task Processing Exceeds the Threshold", "uri":"ALM-50214.html", - "doc_type":"", - "p_code":"583", - "code":"948" + "doc_type":"usermanual", + "p_code":"592", + "code":"1023" }, { "desc":"The system checks the longest duration of RPC requests received by each FE Thrift method every 30 seconds. This alarm is generated when the longest duration exceeds the t", - "product_code":"", + "product_code":"mrs", "title":"ALM-50215 Longest Duration of RPC Requests Received by Each FE Thrift Method Exceeds the Threshold", "uri":"ALM-50215.html", - "doc_type":"", - "p_code":"583", - "code":"949" + "doc_type":"usermanual", + "p_code":"592", + "code":"1024" }, { "desc":"The system checks the memory usage of the FE node every 30 seconds. This alarm is generated when the memory usage exceeds the threshold (95% by default).This alarm is cle", - "product_code":"", + "product_code":"mrs", "title":"ALM-50216 Memory Usage of the FE Node Exceeds the Threshold", "uri":"ALM-50216.html", - "doc_type":"", - "p_code":"583", - "code":"950" + "doc_type":"usermanual", + "p_code":"592", + "code":"1025" }, { "desc":"The system checks the heap memory usage of the FE node every 30 seconds. This alarm is generated when the heap memory usage exceeds the threshold (95% by default).This al", - "product_code":"", + "product_code":"mrs", "title":"ALM-50217 Heap Memory Usage of the FE Node Exceeds the Threshold", "uri":"ALM-50217.html", - "doc_type":"", - "p_code":"583", - "code":"951" + "doc_type":"usermanual", + "p_code":"592", + "code":"1026" }, { "desc":"The system checks the length of the waiting queue in the query execution thread pool every 30 seconds. This alarm is generated when the length exceeds the threshold (20 b", - "product_code":"", + "product_code":"mrs", "title":"ALM-50219 Length of the Queue in the Thread Pool for Query Execution Exceeds the Threshold", "uri":"ALM-50219.html", - "doc_type":"", - "p_code":"583", - "code":"952" + "doc_type":"usermanual", + "p_code":"592", + "code":"1027" }, { "desc":"The system checks the rate of TCP packet receiving errors every 30 seconds. This alarm is generated when the error rate exceeds the threshold (5% by default).This alarm i", - "product_code":"", + "product_code":"mrs", "title":"ALM-50220 Error Rate of TCP Packet Receiving Exceeds the Threshold", "uri":"ALM-50220.html", - "doc_type":"", - "p_code":"583", - "code":"953" + "doc_type":"usermanual", + "p_code":"592", + "code":"1028" }, { "desc":"The system checks the usage of BE data disks every 30 seconds. This alarm is generated when the disk usage exceeds the threshold (95% by default).This alarm is cleared wh", - "product_code":"", + "product_code":"mrs", "title":"ALM-50221 BE Data Disk Usage Exceeds the Threshold", "uri":"ALM-50221.html", - "doc_type":"", - "p_code":"583", - "code":"954" + "doc_type":"usermanual", + "p_code":"592", + "code":"1029" }, { "desc":"The system checks the disk status of a specified data directory on BE every 30 seconds. This alarm is generated when the disk status is not 1 (1 indicates the normal stat", - "product_code":"", + "product_code":"mrs", "title":"ALM-50222 Disk Status of a Specified Data Directory on BE Is Abnormal", "uri":"ALM-50222.html", - "doc_type":"", - "p_code":"583", - "code":"955" + "doc_type":"usermanual", + "p_code":"592", + "code":"1030" }, { "desc":"The system checks whether the maximum memory required by BE is greater than the available memory every 30 seconds. This alarm is generated when the value is not 1 (1 indi", - "product_code":"", + "product_code":"mrs", "title":"ALM-50223 Maximum Memory Required by BE Is Greater Than the Remaining Memory of the Machine", "uri":"ALM-50223.html", - "doc_type":"", - "p_code":"583", - "code":"956" + "doc_type":"usermanual", + "p_code":"592", + "code":"1031" }, { "desc":"The system checks whether the number of failed tasks of a certain type on BE is increasing every 30 seconds. This alarm is generated when the system detects that the valu", - "product_code":"", + "product_code":"mrs", "title":"ALM-50224 Failures a Certain Task Type on BE Are Increasing", "uri":"ALM-50224.html", - "doc_type":"", - "p_code":"583", - "code":"957" + "doc_type":"usermanual", + "p_code":"592", + "code":"1032" }, { "desc":"The system checks the FE process status every 30 seconds. This alarm is generated when the value is greater than 0 (0 indicates that the FE process is normal and 1 indica", - "product_code":"", + "product_code":"mrs", "title":"ALM-50225 FE Instance Fault", "uri":"ALM-50225.html", - "doc_type":"", - "p_code":"583", - "code":"958" + "doc_type":"usermanual", + "p_code":"592", + "code":"1033" }, { "desc":"The system checks the BE process status every 30 seconds. This alarm is generated when the value is greater than 0 (0 indicates that the BE process is normal and 1 indica", - "product_code":"", + "product_code":"mrs", "title":"ALM-50226 BE Instance Fault", "uri":"ALM-50226.html", - "doc_type":"", - "p_code":"583", - "code":"959" + "doc_type":"usermanual", + "p_code":"592", + "code":"1034" + }, + { + "desc":"The system checks concurrent tenant queries on FE nodes every 30 seconds. This alarm is generated when the number exceeds the threshold (90% by default).This alarm is cle", + "product_code":"mrs", + "title":"ALM-50227 Concurrent Doris Tenant Queries Exceeds the Threshold", + "uri":"ALM-50227.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1035" + }, + { + "desc":"The system checks the memory usage of BE nodes every 30 seconds. This alarm is generated when the memory usage of a tenant exceeds the threshold.This alarm is cleared whe", + "product_code":"mrs", + "title":"ALM-50228 Memory Usage of a Doris Tenant Exceeds the Threshold", + "uri":"ALM-50228.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1036" + }, + { + "desc":"The system checks whether the connection between the Doris FE nodes and OBS is available every 30 seconds. This alarm is generated when the connection status code is not ", + "product_code":"mrs", + "title":"ALM-50229 Doris FE Failed to Connect to OBS", + "uri":"ALM-50229.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1037" + }, + { + "desc":"The system checks whether the connection between the Doris BE nodes and OBS is available every 30 seconds. This alarm is generated when the connection status code is not ", + "product_code":"mrs", + "title":"ALM-50230 Doris BE Cannot Connect to OBS", + "uri":"ALM-50230.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1038" + }, + { + "desc":"The alarm module checks for abnormal tablets in the Doris cluster every 5 minutes. This alarm is generated when an abnormal tablet is detected.This alarm is cleared when ", + "product_code":"mrs", + "title":"ALM-50231 Abnormal Tablets Exist in Doris", + "uri":"ALM-50231.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1039" + }, + { + "desc":"The alarm module checks whether a tablet greater than 3 GB (specified by the alarm_tablet_max_size parameter) exists in the Doris cluster every 5 minutes. This alarm is g", + "product_code":"mrs", + "title":"ALM-50232 Large Tablets in Doris", + "uri":"ALM-50232.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1040" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the number of jobs submitted to JobServer every 30 seconds. This alarm is generated when the number of j", - "product_code":"", + "product_code":"mrs", "title":"ALM-50401 Number of JobServer Jobs Waiting to Be Executed Exceeds the Threshold", "uri":"ALM-50401.html", - "doc_type":"", - "p_code":"583", - "code":"960" + "doc_type":"usermanual", + "p_code":"592", + "code":"1041" }, { "desc":"This section applies only to MRS 3.3.0 or later.The system checks the JobGateway service status every 60 seconds. This alarm is generated when the JobGateway service is a", - "product_code":"", + "product_code":"mrs", "title":"ALM-50402 JobGateway Service Unavailable", "uri":"ALM-50402.html", - "doc_type":"", - "p_code":"583", - "code":"961" + "doc_type":"usermanual", + "p_code":"592", + "code":"1042" + }, + { + "desc":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the failure rate of the JobServer job submission API every 30 seconds. This alarm is g", + "product_code":"mrs", + "title":"ALM-50406 Failure Rate of the JobServer Job Submission API Exceeds the Threshold", + "uri":"ALM-50406.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1043" + }, + { + "desc":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the failure rate of the JobServer job query API every 30 seconds. This alarm is genera", + "product_code":"mrs", + "title":"ALM-50407 Failure Rate of the JobServer Job Query API Exceeds the Threshold", + "uri":"ALM-50407.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1044" + }, + { + "desc":"This section is available for MRS 3.5.0-LTS or later version only.The system checks the failure rate of the JobServer job termination API every 30 seconds. This alarm is ", + "product_code":"mrs", + "title":"ALM-50408 Failure Rate of the JobServer Job Termination API Exceeds the Threshold", + "uri":"ALM-50408.html", + "doc_type":"usermanual", + "p_code":"592", + "code":"1045" }, { "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.", @@ -8655,7 +9411,7 @@ "uri":"mrs_01_0648.html", "doc_type":"usermanual", "p_code":"", - "code":"962" + "code":"1046" }, { "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.", @@ -8663,8 +9419,8 @@ "title":"Introduction to MRS Manager", "uri":"mrs_01_0101.html", "doc_type":"usermanual", - "p_code":"962", - "code":"963" + "p_code":"1046", + "code":"1047" }, { "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", @@ -8672,8 +9428,8 @@ "title":"Checking Running Tasks", "uri":"mrs_01_0105.html", "doc_type":"usermanual", - "p_code":"962", - "code":"964" + "p_code":"1046", + "code":"1048" }, { "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.", @@ -8681,8 +9437,8 @@ "title":"Monitoring Management", "uri":"mrs_01_0106.html", "doc_type":"usermanual", - "p_code":"962", - "code":"965" + "p_code":"1046", + "code":"1049" }, { "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", @@ -8690,8 +9446,8 @@ "title":"Dashboard", "uri":"mrs_01_0107.html", "doc_type":"usermanual", - "p_code":"965", - "code":"966" + "p_code":"1049", + "code":"1050" }, { "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,", @@ -8699,8 +9455,8 @@ "title":"Managing Services and Monitoring Hosts", "uri":"mrs_01_0232.html", "doc_type":"usermanual", - "p_code":"965", - "code":"967" + "p_code":"1049", + "code":"1051" }, { "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", @@ -8708,8 +9464,8 @@ "title":"Managing Resource Distribution", "uri":"mrs_01_0233.html", "doc_type":"usermanual", - "p_code":"965", - "code":"968" + "p_code":"1049", + "code":"1052" }, { "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", @@ -8717,8 +9473,8 @@ "title":"Configuring Monitoring Metric Dumping", "uri":"mrs_01_0235.html", "doc_type":"usermanual", - "p_code":"965", - "code":"969" + "p_code":"1049", + "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.", @@ -8726,8 +9482,8 @@ "title":"Alarm Management", "uri":"mrs_01_0236.html", "doc_type":"usermanual", - "p_code":"962", - "code":"970" + "p_code":"1046", + "code":"1054" }, { "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", @@ -8735,8 +9491,8 @@ "title":"Viewing and Manually Clearing an Alarm", "uri":"mrs_01_0237.html", "doc_type":"usermanual", - "p_code":"970", - "code":"971" + "p_code":"1054", + "code":"1055" }, { "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", @@ -8744,8 +9500,8 @@ "title":"Configuring an Alarm Threshold", "uri":"mrs_01_0238.html", "doc_type":"usermanual", - "p_code":"970", - "code":"972" + "p_code":"1054", + "code":"1056" }, { "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", @@ -8753,8 +9509,8 @@ "title":"Configuring Syslog Northbound Interface Parameters", "uri":"mrs_01_0239.html", "doc_type":"usermanual", - "p_code":"970", - "code":"973" + "p_code":"1054", + "code":"1057" }, { "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", @@ -8762,8 +9518,8 @@ "title":"Configuring SNMP Northbound Interface Parameters", "uri":"mrs_01_0240.html", "doc_type":"usermanual", - "p_code":"970", - "code":"974" + "p_code":"1054", + "code":"1058" }, { "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.", @@ -8771,8 +9527,8 @@ "title":"Alarm Reference (Applicable to Versions Earlier Than MRS 3.x)", "uri":"mrs_01_0241.html", "doc_type":"usermanual", - "p_code":"962", - "code":"975" + "p_code":"1046", + "code":"1059" }, { "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", @@ -8780,8 +9536,8 @@ "title":"ALM-12001 Audit Log Dump Failure", "uri":"alm_12001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"976" + "p_code":"1059", + "code":"1060" }, { "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", @@ -8789,8 +9545,8 @@ "title":"ALM-12002 HA Resource Is Abnormal", "uri":"alm_12002.html", "doc_type":"usermanual", - "p_code":"975", - "code":"977" + "p_code":"1059", + "code":"1061" }, { "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.", @@ -8798,8 +9554,8 @@ "title":"ALM-12004 OLdap Resource Is Abnormal", "uri":"alm_12004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"978" + "p_code":"1059", + "code":"1062" }, { "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", @@ -8807,8 +9563,8 @@ "title":"ALM-12005 OKerberos Resource Is Abnormal", "uri":"alm_12005.html", "doc_type":"usermanual", - "p_code":"975", - "code":"979" + "p_code":"1059", + "code":"1063" }, { "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", @@ -8816,8 +9572,8 @@ "title":"ALM-12006 Node Fault", "uri":"alm_12006.html", "doc_type":"usermanual", - "p_code":"975", - "code":"980" + "p_code":"1059", + "code":"1064" }, { "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", @@ -8825,8 +9581,8 @@ "title":"ALM-12007 Process Fault", "uri":"alm_12007.html", "doc_type":"usermanual", - "p_code":"975", - "code":"981" + "p_code":"1059", + "code":"1065" }, { "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", @@ -8834,8 +9590,8 @@ "title":"ALM-12010 Manager Heartbeat Interruption Between the Active and Standby Nodes", "uri":"alm_12010.html", "doc_type":"usermanual", - "p_code":"975", - "code":"982" + "p_code":"1059", + "code":"1066" }, { "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", @@ -8843,8 +9599,8 @@ "title":"ALM-12011 Data Synchronization Exception Between the Active and Standby Manager Nodes", "uri":"alm_12011.html", "doc_type":"usermanual", - "p_code":"975", - "code":"983" + "p_code":"1059", + "code":"1067" }, { "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 ", @@ -8852,8 +9608,8 @@ "title":"ALM-12012 NTP Service Is Abnormal", "uri":"alm_12012.html", "doc_type":"usermanual", - "p_code":"975", - "code":"984" + "p_code":"1059", + "code":"1068" }, { "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 ", @@ -8861,8 +9617,8 @@ "title":"ALM-12016 CPU Usage Exceeds the Threshold", "uri":"alm_12016.html", "doc_type":"usermanual", - "p_code":"975", - "code":"985" + "p_code":"1059", + "code":"1069" }, { "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", @@ -8870,8 +9626,8 @@ "title":"ALM-12017 Insufficient Disk Capacity", "uri":"alm_12017.html", "doc_type":"usermanual", - "p_code":"975", - "code":"986" + "p_code":"1059", + "code":"1070" }, { "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", @@ -8879,8 +9635,8 @@ "title":"ALM-12018 Memory Usage Exceeds the Threshold", "uri":"alm_12018.html", "doc_type":"usermanual", - "p_code":"975", - "code":"987" + "p_code":"1059", + "code":"1071" }, { "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", @@ -8888,8 +9644,8 @@ "title":"ALM-12027 Host PID Usage Exceeds the Threshold", "uri":"alm_12027.html", "doc_type":"usermanual", - "p_code":"975", - "code":"988" + "p_code":"1059", + "code":"1072" }, { "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", @@ -8897,8 +9653,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":"975", - "code":"989" + "p_code":"1059", + "code":"1073" }, { "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 ", @@ -8906,8 +9662,8 @@ "title":"ALM-12031 User omm or Password Is About to Expire", "uri":"alm_12031.html", "doc_type":"usermanual", - "p_code":"975", - "code":"990" + "p_code":"1059", + "code":"1074" }, { "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 ", @@ -8915,8 +9671,8 @@ "title":"ALM-12032 User ommdba or Password Is About to Expire", "uri":"alm_12032.html", "doc_type":"usermanual", - "p_code":"975", - "code":"991" + "p_code":"1059", + "code":"1075" }, { "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", @@ -8924,8 +9680,8 @@ "title":"ALM-12033 Slow Disk Fault", "uri":"alm_12033.html", "doc_type":"usermanual", - "p_code":"975", - "code":"992" + "p_code":"1059", + "code":"1076" }, { "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", @@ -8933,8 +9689,8 @@ "title":"ALM-12034 Periodic Backup Failure", "uri":"alm_12034.html", "doc_type":"usermanual", - "p_code":"975", - "code":"993" + "p_code":"1059", + "code":"1077" }, { "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", @@ -8942,8 +9698,8 @@ "title":"ALM-12035 Unknown Data Status After Recovery Task Failure", "uri":"alm_12035.html", "doc_type":"usermanual", - "p_code":"975", - "code":"994" + "p_code":"1059", + "code":"1078" }, { "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", @@ -8951,8 +9707,8 @@ "title":"ALM-12037 NTP Server Is Abnormal", "uri":"alm_12037.html", "doc_type":"usermanual", - "p_code":"975", - "code":"995" + "p_code":"1059", + "code":"1079" }, { "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", @@ -8960,8 +9716,8 @@ "title":"ALM-12038 Monitoring Indicator Dump Failure", "uri":"alm_12038.html", "doc_type":"usermanual", - "p_code":"975", - "code":"996" + "p_code":"1059", + "code":"1080" }, { "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", @@ -8969,8 +9725,8 @@ "title":"ALM-12039 GaussDB Data Is Not Synchronized", "uri":"alm_12039.html", "doc_type":"usermanual", - "p_code":"975", - "code":"997" + "p_code":"1059", + "code":"1081" }, { "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", @@ -8978,8 +9734,8 @@ "title":"ALM-12040 Insufficient System Entropy", "uri":"alm_12040.html", "doc_type":"usermanual", - "p_code":"975", - "code":"998" + "p_code":"1059", + "code":"1082" }, { "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", @@ -8987,8 +9743,8 @@ "title":"ALM-13000 ZooKeeper Service Unavailable", "uri":"alm_13000.html", "doc_type":"usermanual", - "p_code":"975", - "code":"999" + "p_code":"1059", + "code":"1083" }, { "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", @@ -8996,8 +9752,8 @@ "title":"ALM-13001 Available ZooKeeper Connections Are Insufficient", "uri":"alm_13001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1000" + "p_code":"1059", + "code":"1084" }, { "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", @@ -9005,8 +9761,8 @@ "title":"ALM-13002 ZooKeeper Memory Usage Exceeds the Threshold", "uri":"alm_13002.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1001" + "p_code":"1059", + "code":"1085" }, { "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", @@ -9014,8 +9770,8 @@ "title":"ALM-14000 HDFS Service Unavailable", "uri":"alm_14000.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1002" + "p_code":"1059", + "code":"1086" }, { "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", @@ -9023,8 +9779,8 @@ "title":"ALM-14001 HDFS Disk Usage Exceeds the Threshold", "uri":"alm_14001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1003" + "p_code":"1059", + "code":"1087" }, { "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", @@ -9032,8 +9788,8 @@ "title":"ALM-14002 DataNode Disk Usage Exceeds the Threshold", "uri":"alm_14002.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1004" + "p_code":"1059", + "code":"1088" }, { "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.", @@ -9041,8 +9797,8 @@ "title":"ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold", "uri":"alm_14003.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1005" + "p_code":"1059", + "code":"1089" }, { "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", @@ -9050,8 +9806,8 @@ "title":"ALM-14004 Number of Damaged HDFS Blocks Exceeds the Threshold", "uri":"alm_14004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1006" + "p_code":"1059", + "code":"1090" }, { "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", @@ -9059,8 +9815,8 @@ "title":"ALM-14006 Number of HDFS Files Exceeds the Threshold", "uri":"alm_14006.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1007" + "p_code":"1059", + "code":"1091" }, { "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", @@ -9068,8 +9824,8 @@ "title":"ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold", "uri":"alm_14007.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1008" + "p_code":"1059", + "code":"1092" }, { "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", @@ -9077,8 +9833,8 @@ "title":"ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold", "uri":"alm_14008.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1009" + "p_code":"1059", + "code":"1093" }, { "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", @@ -9086,8 +9842,8 @@ "title":"ALM-14009 Number of Faulty DataNodes Exceeds the Threshold", "uri":"alm_14009.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1010" + "p_code":"1059", + "code":"1094" }, { "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", @@ -9095,8 +9851,8 @@ "title":"ALM-14010 NameService Service Is Abnormal", "uri":"alm_14010.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1011" + "p_code":"1059", + "code":"1095" }, { "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 ", @@ -9104,8 +9860,8 @@ "title":"ALM-14011 HDFS DataNode Data Directory Is Not Configured Properly", "uri":"alm_14011.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1012" + "p_code":"1059", + "code":"1096" }, { "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", @@ -9113,8 +9869,8 @@ "title":"ALM-14012 HDFS JournalNode Data Is Not Synchronized", "uri":"alm_14012.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1013" + "p_code":"1059", + "code":"1097" }, { "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 ", @@ -9122,8 +9878,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":"975", - "code":"1014" + "p_code":"1059", + "code":"1098" }, { "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", @@ -9131,8 +9887,8 @@ "title":"ALM-16001 Hive Warehouse Space Usage Exceeds the Threshold", "uri":"alm_16001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1015" + "p_code":"1059", + "code":"1099" }, { "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 ", @@ -9140,8 +9896,8 @@ "title":"ALM-16002 Hive SQL Execution Success Rate Is Lower Than the Threshold", "uri":"alm_16002.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1016" + "p_code":"1059", + "code":"1100" }, { "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", @@ -9149,8 +9905,8 @@ "title":"ALM-16004 Hive Service Unavailable", "uri":"alm_16004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1017" + "p_code":"1059", + "code":"1101" }, { "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", @@ -9158,8 +9914,8 @@ "title":"ALM-18000 Yarn Service Unavailable", "uri":"alm_18000.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1018" + "p_code":"1059", + "code":"1102" }, { "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 ", @@ -9167,8 +9923,8 @@ "title":"ALM-18002 NodeManager Heartbeat Lost", "uri":"alm_18002.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1019" + "p_code":"1059", + "code":"1103" }, { "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", @@ -9176,8 +9932,8 @@ "title":"ALM-18003 NodeManager Unhealthy", "uri":"alm_18003.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1020" + "p_code":"1059", + "code":"1104" }, { "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", @@ -9185,8 +9941,8 @@ "title":"ALM-18004 NodeManager Disk Usability Ratio Is Lower Than the Threshold", "uri":"alm_18004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1021" + "p_code":"1059", + "code":"1105" }, { "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", @@ -9194,8 +9950,8 @@ "title":"ALM-18006 MapReduce Job Execution Timeout", "uri":"alm_18006.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1022" + "p_code":"1059", + "code":"1106" }, { "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", @@ -9203,8 +9959,8 @@ "title":"ALM-19000 HBase Service Unavailable", "uri":"alm_19000.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1023" + "p_code":"1059", + "code":"1107" }, { "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", @@ -9212,8 +9968,8 @@ "title":"ALM-19006 HBase Replication Sync Failed", "uri":"alm_19006.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1024" + "p_code":"1059", + "code":"1108" }, { "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", @@ -9221,8 +9977,8 @@ "title":"ALM-25000 LdapServer Service Unavailable", "uri":"alm_25000.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1025" + "p_code":"1059", + "code":"1109" }, { "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", @@ -9230,8 +9986,8 @@ "title":"ALM-25004 Abnormal LdapServer Data Synchronization", "uri":"alm_25004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1026" + "p_code":"1059", + "code":"1110" }, { "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", @@ -9239,8 +9995,8 @@ "title":"ALM-25500 KrbServer Service Unavailable", "uri":"alm_25500.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1027" + "p_code":"1059", + "code":"1111" }, { "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", @@ -9248,8 +10004,8 @@ "title":"ALM-27001 DBService Is Unavailable", "uri":"alm_27001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1028" + "p_code":"1059", + "code":"1112" }, { "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", @@ -9257,8 +10013,8 @@ "title":"ALM-27003 DBService Heartbeat Interruption Between the Active and Standby Nodes", "uri":"alm_27003.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1029" + "p_code":"1059", + "code":"1113" }, { "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", @@ -9266,8 +10022,8 @@ "title":"ALM-27004 Data Inconsistency Between Active and Standby DBServices", "uri":"alm_27004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1030" + "p_code":"1059", + "code":"1114" }, { "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", @@ -9275,8 +10031,8 @@ "title":"ALM-28001 Spark Service Unavailable", "uri":"alm_28001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1031" + "p_code":"1059", + "code":"1115" }, { "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", @@ -9284,8 +10040,8 @@ "title":"ALM-26051 Storm Service Unavailable", "uri":"alm_26051.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1032" + "p_code":"1059", + "code":"1116" }, { "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", @@ -9293,8 +10049,8 @@ "title":"ALM-26052 Number of Available Supervisors in Storm Is Lower Than the Threshold", "uri":"alm_26052.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1033" + "p_code":"1059", + "code":"1117" }, { "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", @@ -9302,8 +10058,8 @@ "title":"ALM-26053 Slot Usage of Storm Exceeds the Threshold", "uri":"alm_26053.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1034" + "p_code":"1059", + "code":"1118" }, { "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 ", @@ -9311,8 +10067,8 @@ "title":"ALM-26054 Heap Memory Usage of Storm Nimbus Exceeds the Threshold", "uri":"alm_26054.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1035" + "p_code":"1059", + "code":"1119" }, { "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 ", @@ -9320,8 +10076,8 @@ "title":"ALM-38000 Kafka Service Unavailable", "uri":"alm_38000.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1036" + "p_code":"1059", + "code":"1120" }, { "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 ", @@ -9329,8 +10085,8 @@ "title":"ALM-38001 Insufficient Kafka Disk Space", "uri":"alm_38001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1037" + "p_code":"1059", + "code":"1121" }, { "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", @@ -9338,8 +10094,8 @@ "title":"ALM-38002 Heap Memory Usage of Kafka Exceeds the Threshold", "uri":"alm_38002.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1038" + "p_code":"1059", + "code":"1122" }, { "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", @@ -9347,8 +10103,8 @@ "title":"ALM-24000 Flume Service Unavailable", "uri":"alm_24000.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1039" + "p_code":"1059", + "code":"1123" }, { "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", @@ -9356,8 +10112,8 @@ "title":"ALM-24001 Flume Agent Is Abnormal", "uri":"alm_24001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1040" + "p_code":"1059", + "code":"1124" }, { "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", @@ -9365,8 +10121,8 @@ "title":"ALM-24003 Flume Client Connection Failure", "uri":"alm_24003.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1041" + "p_code":"1059", + "code":"1125" }, { "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", @@ -9374,8 +10130,8 @@ "title":"ALM-24004 Flume Fails to Read Data", "uri":"alm_24004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1042" + "p_code":"1059", + "code":"1126" }, { "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", @@ -9383,8 +10139,8 @@ "title":"ALM-24005 Data Transmission by Flume Is Abnormal", "uri":"alm_24005.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1043" + "p_code":"1059", + "code":"1127" }, { "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", @@ -9392,8 +10148,8 @@ "title":"ALM-12041 Permission of Key Files Is Abnormal", "uri":"alm_12041.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1044" + "p_code":"1059", + "code":"1128" }, { "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", @@ -9401,8 +10157,8 @@ "title":"ALM-12042 Key File Configurations Are Abnormal", "uri":"alm_12042.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1045" + "p_code":"1059", + "code":"1129" }, { "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", @@ -9410,8 +10166,8 @@ "title":"ALM-23001 Loader Service Unavailable", "uri":"alm_23001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1046" + "p_code":"1059", + "code":"1130" }, { "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", @@ -9419,8 +10175,8 @@ "title":"ALM-12357 Failed to Export Audit Logs to OBS", "uri":"alm_12357.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1047" + "p_code":"1059", + "code":"1131" }, { "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", @@ -9428,8 +10184,8 @@ "title":"ALM-12014 Device Partition Lost", "uri":"alm_12014.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1048" + "p_code":"1059", + "code":"1132" }, { "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 ", @@ -9437,8 +10193,8 @@ "title":"ALM-12015 Device Partition File System Read-Only", "uri":"alm_12015.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1049" + "p_code":"1059", + "code":"1133" }, { "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 ", @@ -9446,8 +10202,8 @@ "title":"ALM-12043 DNS Parsing Duration Exceeds the Threshold", "uri":"alm_12043.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1050" + "p_code":"1059", + "code":"1134" }, { "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", @@ -9455,8 +10211,8 @@ "title":"ALM-12045 Read Packet Dropped Rate Exceeds the Threshold", "uri":"alm_12045.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1051" + "p_code":"1059", + "code":"1135" }, { "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 ", @@ -9464,8 +10220,8 @@ "title":"ALM-12046 Write Packet Dropped Rate Exceeds the Threshold", "uri":"alm_12046.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1052" + "p_code":"1059", + "code":"1136" }, { "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", @@ -9473,8 +10229,8 @@ "title":"ALM-12047 Read Packet Error Rate Exceeds the Threshold", "uri":"alm_12047.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1053" + "p_code":"1059", + "code":"1137" }, { "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", @@ -9482,8 +10238,8 @@ "title":"ALM-12048 Write Packet Error Rate Exceeds the Threshold", "uri":"alm_12048.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1054" + "p_code":"1059", + "code":"1138" }, { "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", @@ -9491,8 +10247,8 @@ "title":"ALM-12049 Read Throughput Rate Exceeds the Threshold", "uri":"alm_12049.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1055" + "p_code":"1059", + "code":"1139" }, { "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%) ", @@ -9500,8 +10256,8 @@ "title":"ALM-12050 Write Throughput Rate Exceeds the Threshold", "uri":"alm_12050.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1056" + "p_code":"1059", + "code":"1140" }, { "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", @@ -9509,8 +10265,8 @@ "title":"ALM-12051 Disk Inode Usage Exceeds the Threshold", "uri":"alm_12051.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1057" + "p_code":"1059", + "code":"1141" }, { "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", @@ -9518,8 +10274,8 @@ "title":"ALM-12052 Usage of Temporary TCP Ports Exceeds the Threshold", "uri":"alm_12052.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1058" + "p_code":"1059", + "code":"1142" }, { "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", @@ -9527,8 +10283,8 @@ "title":"ALM-12053 File Handle Usage Exceeds the Threshold", "uri":"alm_12053.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1059" + "p_code":"1059", + "code":"1143" }, { "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", @@ -9536,8 +10292,8 @@ "title":"ALM-12054 The Certificate File Is Invalid", "uri":"alm_12054.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1060" + "p_code":"1059", + "code":"1144" }, { "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", @@ -9545,8 +10301,8 @@ "title":"ALM-12055 The Certificate File Is About to Expire", "uri":"alm_12055.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1061" + "p_code":"1059", + "code":"1145" }, { "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", @@ -9554,8 +10310,8 @@ "title":"ALM-18008 Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold", "uri":"alm_18008.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1062" + "p_code":"1059", + "code":"1146" }, { "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", @@ -9563,8 +10319,8 @@ "title":"ALM-18009 Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold", "uri":"alm_18009.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1063" + "p_code":"1059", + "code":"1147" }, { "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.", @@ -9572,8 +10328,8 @@ "title":"ALM-20002 Hue Service Unavailable", "uri":"alm_20002.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1064" + "p_code":"1059", + "code":"1148" }, { "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", @@ -9581,8 +10337,8 @@ "title":"ALM-43001 Spark Service Unavailable", "uri":"alm_43001.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1065" + "p_code":"1059", + "code":"1149" }, { "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", @@ -9590,8 +10346,8 @@ "title":"ALM-43006 Heap Memory Usage of the JobHistory Process Exceeds the Threshold", "uri":"alm_43006.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1066" + "p_code":"1059", + "code":"1150" }, { "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", @@ -9599,8 +10355,8 @@ "title":"ALM-43007 Non-Heap Memory Usage of the JobHistory Process Exceeds the Threshold", "uri":"alm_43007.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1067" + "p_code":"1059", + "code":"1151" }, { "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%", @@ -9608,8 +10364,8 @@ "title":"ALM-43008 Direct Memory Usage of the JobHistory Process Exceeds the Threshold", "uri":"alm_43008.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1068" + "p_code":"1059", + "code":"1152" }, { "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", @@ -9617,8 +10373,8 @@ "title":"ALM-43009 JobHistory GC Time Exceeds the Threshold", "uri":"alm_43009.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1069" + "p_code":"1059", + "code":"1153" }, { "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", @@ -9626,8 +10382,8 @@ "title":"ALM-43010 Heap Memory Usage of the JDBCServer Process Exceeds the Threshold", "uri":"alm_43010.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1070" + "p_code":"1059", + "code":"1154" }, { "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", @@ -9635,8 +10391,8 @@ "title":"ALM-43011 Non-Heap Memory Usage of the JDBCServer Process Exceeds the Threshold", "uri":"alm_43011.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1071" + "p_code":"1059", + "code":"1155" }, { "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%", @@ -9644,8 +10400,8 @@ "title":"ALM-43012 Direct Memory Usage of the JDBCServer Process Exceeds the Threshold", "uri":"alm_43012.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1072" + "p_code":"1059", + "code":"1156" }, { "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", @@ -9653,8 +10409,8 @@ "title":"ALM-43013 JDBCServer GC Time Exceeds the Threshold", "uri":"alm_43013.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1073" + "p_code":"1059", + "code":"1157" }, { "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", @@ -9662,8 +10418,8 @@ "title":"ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold", "uri":"alm_44004.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1074" + "p_code":"1059", + "code":"1158" }, { "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", @@ -9671,8 +10427,8 @@ "title":"ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold", "uri":"alm_44005.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1075" + "p_code":"1059", + "code":"1159" }, { "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", @@ -9680,8 +10436,8 @@ "title":"ALM-44006 Presto Worker Process GC Time Exceeds the Threshold", "uri":"alm_44006.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1076" + "p_code":"1059", + "code":"1160" }, { "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", @@ -9689,8 +10445,8 @@ "title":"ALM-18010 Number of Pending Yarn Tasks Exceeds the Threshold", "uri":"alm_18010.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1077" + "p_code":"1059", + "code":"1161" }, { "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", @@ -9698,8 +10454,8 @@ "title":"ALM-18011 Memory of Pending Yarn Tasks Exceeds the Threshold", "uri":"alm_18011.html", "doc_type":"usermanual", - "p_code":"975", - "code":"1078" + "p_code":"1059", + "code":"1162" }, { "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", @@ -9707,8 +10463,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":"975", - "code":"1079" + "p_code":"1059", + "code":"1163" }, { "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", @@ -9716,8 +10472,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":"975", - "code":"1080" + "p_code":"1059", + "code":"1164" }, { "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", @@ -9725,8 +10481,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":"975", - "code":"1081" + "p_code":"1059", + "code":"1165" }, { "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.", @@ -9734,8 +10490,8 @@ "title":"Object Management", "uri":"mrs_01_0242.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1082" + "p_code":"1046", + "code":"1166" }, { "desc":"MRS contains different types of basic objects as described in Table 1.", @@ -9743,8 +10499,8 @@ "title":"Managing Objects", "uri":"mrs_01_0243.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1083" + "p_code":"1166", + "code":"1167" }, { "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", @@ -9752,8 +10508,8 @@ "title":"Viewing Configurations", "uri":"mrs_01_0244.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1084" + "p_code":"1166", + "code":"1168" }, { "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 ", @@ -9761,8 +10517,8 @@ "title":"Managing Services", "uri":"mrs_01_0245.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1085" + "p_code":"1166", + "code":"1169" }, { "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", @@ -9770,8 +10526,8 @@ "title":"Configuring Service Parameters", "uri":"mrs_01_0246.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1086" + "p_code":"1166", + "code":"1170" }, { "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", @@ -9779,8 +10535,8 @@ "title":"Configuring Customized Service Parameters", "uri":"mrs_01_0247.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1087" + "p_code":"1166", + "code":"1171" }, { "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", @@ -9788,8 +10544,8 @@ "title":"Synchronizing Service Configurations", "uri":"mrs_01_0248.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1088" + "p_code":"1166", + "code":"1172" }, { "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", @@ -9797,8 +10553,8 @@ "title":"Managing Role Instances", "uri":"mrs_01_0249.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1089" + "p_code":"1166", + "code":"1173" }, { "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", @@ -9806,8 +10562,8 @@ "title":"Configuring Role Instance Parameters", "uri":"mrs_01_0250.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1090" + "p_code":"1166", + "code":"1174" }, { "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", @@ -9815,8 +10571,8 @@ "title":"Synchronizing Role Instance Configuration", "uri":"mrs_01_0251.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1091" + "p_code":"1166", + "code":"1175" }, { "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", @@ -9824,8 +10580,8 @@ "title":"Decommissioning and Recommissioning a Role Instance", "uri":"mrs_01_0252.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1092" + "p_code":"1166", + "code":"1176" }, { "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 ", @@ -9833,8 +10589,8 @@ "title":"Managing a Host", "uri":"mrs_01_0254.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1093" + "p_code":"1166", + "code":"1177" }, { "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", @@ -9842,8 +10598,8 @@ "title":"Isolating a Host", "uri":"mrs_01_0255.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1094" + "p_code":"1166", + "code":"1178" }, { "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 ", @@ -9851,8 +10607,8 @@ "title":"Canceling Host Isolation", "uri":"mrs_01_0256.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1095" + "p_code":"1166", + "code":"1179" }, { "desc":"A cluster is a collection of service components. You can start or stop all services in a cluster.", @@ -9860,8 +10616,8 @@ "title":"Starting or Stopping a Cluster", "uri":"mrs_01_0258.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1096" + "p_code":"1166", + "code":"1180" }, { "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", @@ -9869,8 +10625,8 @@ "title":"Synchronizing Cluster Configurations", "uri":"mrs_01_0259.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1097" + "p_code":"1166", + "code":"1181" }, { "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", @@ -9878,8 +10634,8 @@ "title":"Exporting Configuration Data of a Cluster", "uri":"mrs_01_0260.html", "doc_type":"usermanual", - "p_code":"1082", - "code":"1098" + "p_code":"1166", + "code":"1182" }, { "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.", @@ -9887,8 +10643,8 @@ "title":"Log Management", "uri":"mrs_01_0264.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1099" + "p_code":"1046", + "code":"1183" }, { "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", @@ -9896,8 +10652,8 @@ "title":"About Logs", "uri":"mrs_01_1226.html", "doc_type":"usermanual", - "p_code":"1099", - "code":"1100" + "p_code":"1183", + "code":"1184" }, { "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", @@ -9905,8 +10661,8 @@ "title":"Manager Log List", "uri":"mrs_01_1227.html", "doc_type":"usermanual", - "p_code":"1099", - "code":"1101" + "p_code":"1183", + "code":"1185" }, { "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", @@ -9914,8 +10670,8 @@ "title":"Viewing and Exporting Audit Logs", "uri":"mrs_01_0265.html", "doc_type":"usermanual", - "p_code":"1099", - "code":"1102" + "p_code":"1183", + "code":"1186" }, { "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", @@ -9923,8 +10679,8 @@ "title":"Exporting Service Logs", "uri":"mrs_01_0267.html", "doc_type":"usermanual", - "p_code":"1099", - "code":"1103" + "p_code":"1183", + "code":"1187" }, { "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", @@ -9932,8 +10688,8 @@ "title":"Configuring Audit Log Exporting Parameters", "uri":"mrs_01_0270.html", "doc_type":"usermanual", - "p_code":"1099", - "code":"1104" + "p_code":"1183", + "code":"1188" }, { "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.", @@ -9941,8 +10697,8 @@ "title":"Health Check Management", "uri":"mrs_01_0271.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1105" + "p_code":"1046", + "code":"1189" }, { "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", @@ -9950,8 +10706,8 @@ "title":"Performing a Health Check", "uri":"mrs_01_0274.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1106" + "p_code":"1189", + "code":"1190" }, { "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", @@ -9959,8 +10715,8 @@ "title":"Viewing and Exporting a Health Check Report", "uri":"mrs_01_0275.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1107" + "p_code":"1189", + "code":"1191" }, { "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", @@ -9968,8 +10724,8 @@ "title":"Configuring the Number of Health Check Reports to Be Reserved", "uri":"mrs_01_0277.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1108" + "p_code":"1189", + "code":"1192" }, { "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", @@ -9977,8 +10733,8 @@ "title":"Managing Health Check Reports", "uri":"mrs_01_0278.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1109" + "p_code":"1189", + "code":"1193" }, { "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.", @@ -9986,8 +10742,8 @@ "title":"DBService Health Check Indicators", "uri":"mrs_01_0279.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1110" + "p_code":"1189", + "code":"1194" }, { "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", @@ -9995,8 +10751,8 @@ "title":"Flume Health Check Indicators", "uri":"mrs_01_0280.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1111" + "p_code":"1189", + "code":"1195" }, { "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:", @@ -10004,8 +10760,8 @@ "title":"HBase Health Check Indicators", "uri":"mrs_01_0281.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1112" + "p_code":"1189", + "code":"1196" }, { "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 ", @@ -10013,8 +10769,8 @@ "title":"Host Health Check Indicators", "uri":"mrs_01_0282.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1113" + "p_code":"1189", + "code":"1197" }, { "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", @@ -10022,8 +10778,8 @@ "title":"HDFS Health Check Indicators", "uri":"mrs_01_0284.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1114" + "p_code":"1189", + "code":"1198" }, { "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", @@ -10031,8 +10787,8 @@ "title":"Hive Health Check Indicators", "uri":"mrs_01_0285.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1115" + "p_code":"1189", + "code":"1199" }, { "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", @@ -10040,8 +10796,8 @@ "title":"Kafka Health Check Indicators", "uri":"mrs_01_0288.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1116" + "p_code":"1189", + "code":"1200" }, { "desc":"Indicator: KerberosAdmin Service AvailabilityDescription: The system checks the KerberosAdmin service status. If the check result is abnormal, the KerberosAdmin service i", @@ -10049,8 +10805,8 @@ "title":"KrbServer Health Check Indicators", "uri":"mrs_01_0289.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1117" + "p_code":"1189", + "code":"1201" }, { "desc":"Indicator: SlapdServer Service AvailabilityDescription: The system checks the SlapdServer service status. If the status is abnormal, the SlapdServer service is unavailabl", @@ -10058,8 +10814,8 @@ "title":"LdapServer Health Check Indicators", "uri":"mrs_01_0291.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1118" + "p_code":"1189", + "code":"1202" }, { "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", @@ -10067,8 +10823,8 @@ "title":"Loader Health Check Indicators", "uri":"mrs_01_0292.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1119" + "p_code":"1189", + "code":"1203" }, { "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.", @@ -10076,8 +10832,8 @@ "title":"MapReduce Health Check Indicators", "uri":"mrs_01_0293.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1120" + "p_code":"1189", + "code":"1204" }, { "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", @@ -10085,8 +10841,8 @@ "title":"OMS Health Check Indicators", "uri":"mrs_01_0294.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1121" + "p_code":"1189", + "code":"1205" }, { "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", @@ -10094,8 +10850,8 @@ "title":"Spark Health Check Indicators", "uri":"mrs_01_0530.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1122" + "p_code":"1189", + "code":"1206" }, { "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", @@ -10103,8 +10859,8 @@ "title":"Storm Health Check Indicators", "uri":"mrs_01_0531.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1123" + "p_code":"1189", + "code":"1207" }, { "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", @@ -10112,8 +10868,8 @@ "title":"Yarn Health Check Indicators", "uri":"mrs_01_0532.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1124" + "p_code":"1189", + "code":"1208" }, { "desc":"Indicator: Average ZooKeeper Service Request Processing LatencyDescription: This indicator is used to check the average delay for the ZooKeeper service to process request", @@ -10121,8 +10877,8 @@ "title":"ZooKeeper Health Check Indicators", "uri":"mrs_01_0533.html", "doc_type":"usermanual", - "p_code":"1105", - "code":"1125" + "p_code":"1189", + "code":"1209" }, { "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.", @@ -10130,8 +10886,8 @@ "title":"Static Service Pool Management", "uri":"mrs_01_0534.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1126" + "p_code":"1046", + "code":"1210" }, { "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", @@ -10139,8 +10895,8 @@ "title":"Viewing the Status of a Static Service Pool", "uri":"mrs_01_0535.html", "doc_type":"usermanual", - "p_code":"1126", - "code":"1127" + "p_code":"1210", + "code":"1211" }, { "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", @@ -10148,8 +10904,8 @@ "title":"Configuring a Static Service Pool", "uri":"mrs_01_0536.html", "doc_type":"usermanual", - "p_code":"1126", - "code":"1128" + "p_code":"1210", + "code":"1212" }, { "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.", @@ -10157,8 +10913,8 @@ "title":"Tenant Management", "uri":"mrs_01_0537.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1129" + "p_code":"1046", + "code":"1213" }, { "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", @@ -10166,8 +10922,8 @@ "title":"Overview", "uri":"mrs_01_0538.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1130" + "p_code":"1213", + "code":"1214" }, { "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", @@ -10175,8 +10931,8 @@ "title":"Creating a Tenant", "uri":"mrs_01_0539.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1131" + "p_code":"1213", + "code":"1215" }, { "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", @@ -10184,8 +10940,8 @@ "title":"Creating a Sub-tenant", "uri":"mrs_01_0540.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1132" + "p_code":"1213", + "code":"1216" }, { "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", @@ -10193,8 +10949,8 @@ "title":"Deleting a tenant", "uri":"mrs_01_0541.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1133" + "p_code":"1213", + "code":"1217" }, { "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", @@ -10202,8 +10958,8 @@ "title":"Managing a Tenant Directory", "uri":"mrs_01_0542.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1134" + "p_code":"1213", + "code":"1218" }, { "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", @@ -10211,8 +10967,8 @@ "title":"Restoring Tenant Data", "uri":"mrs_01_0543.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1135" + "p_code":"1213", + "code":"1219" }, { "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", @@ -10220,8 +10976,8 @@ "title":"Creating a Resource Pool", "uri":"mrs_01_0544.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1136" + "p_code":"1213", + "code":"1220" }, { "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", @@ -10229,8 +10985,8 @@ "title":"Modifying a Resource Pool", "uri":"mrs_01_0545.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1137" + "p_code":"1213", + "code":"1221" }, { "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", @@ -10238,8 +10994,8 @@ "title":"Deleting a Resource Pool", "uri":"mrs_01_0546.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1138" + "p_code":"1213", + "code":"1222" }, { "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 ", @@ -10247,8 +11003,8 @@ "title":"Configuring a Queue", "uri":"mrs_01_0547.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1139" + "p_code":"1213", + "code":"1223" }, { "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 ", @@ -10256,8 +11012,8 @@ "title":"Configuring the Queue Capacity Policy of a Resource Pool", "uri":"mrs_01_0548.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1140" + "p_code":"1213", + "code":"1224" }, { "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", @@ -10265,8 +11021,8 @@ "title":"Clearing Configuration of a Queue", "uri":"mrs_01_0549.html", "doc_type":"usermanual", - "p_code":"1129", - "code":"1141" + "p_code":"1213", + "code":"1225" }, { "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.", @@ -10274,8 +11030,8 @@ "title":"Backup and Restoration", "uri":"mrs_01_0550.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1142" + "p_code":"1046", + "code":"1226" }, { "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", @@ -10283,8 +11039,8 @@ "title":"Introduction", "uri":"mrs_01_0551.html", "doc_type":"usermanual", - "p_code":"1142", - "code":"1143" + "p_code":"1226", + "code":"1227" }, { "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,", @@ -10292,8 +11048,8 @@ "title":"Backing Up Metadata", "uri":"mrs_01_0553.html", "doc_type":"usermanual", - "p_code":"1142", - "code":"1144" + "p_code":"1226", + "code":"1228" }, { "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", @@ -10301,8 +11057,8 @@ "title":"Restoring Metadata", "uri":"mrs_01_0555.html", "doc_type":"usermanual", - "p_code":"1142", - "code":"1145" + "p_code":"1226", + "code":"1229" }, { "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", @@ -10310,8 +11066,8 @@ "title":"Modifying a Backup Task", "uri":"mrs_01_0558.html", "doc_type":"usermanual", - "p_code":"1142", - "code":"1146" + "p_code":"1226", + "code":"1230" }, { "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", @@ -10319,8 +11075,8 @@ "title":"Viewing Backup and Restoration Tasks", "uri":"mrs_01_0559.html", "doc_type":"usermanual", - "p_code":"1142", - "code":"1147" + "p_code":"1226", + "code":"1231" }, { "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 +11084,8 @@ "title":"Security Management", "uri":"mrs_01_0560.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1148" + "p_code":"1046", + "code":"1232" }, { "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", @@ -10337,8 +11093,8 @@ "title":"Default Users of Clusters with Kerberos Authentication Disabled", "uri":"mrs_01_0561.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1149" + "p_code":"1232", + "code":"1233" }, { "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", @@ -10346,8 +11102,8 @@ "title":"Default Users of Clusters with Kerberos Authentication Enabled", "uri":"mrs_01_24044.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1150" + "p_code":"1232", + "code":"1234" }, { "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", @@ -10355,8 +11111,8 @@ "title":"Changing the Password of an OS User", "uri":"mrs_01_0562.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1151" + "p_code":"1232", + "code":"1235" }, { "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", @@ -10364,8 +11120,8 @@ "title":"Changing the password of user admin", "uri":"mrs_01_0563.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1152" + "p_code":"1232", + "code":"1236" }, { "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 ", @@ -10373,8 +11129,8 @@ "title":"Changing the Password of the Kerberos Administrator", "uri":"mrs_01_0564.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1153" + "p_code":"1232", + "code":"1237" }, { "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", @@ -10382,8 +11138,8 @@ "title":"Changing the Passwords of the LDAP Administrator and the LDAP User", "uri":"mrs_01_0565.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1154" + "p_code":"1232", + "code":"1238" }, { "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", @@ -10391,8 +11147,8 @@ "title":"Changing the Password of a Component Running User", "uri":"mrs_01_0566.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1155" + "p_code":"1232", + "code":"1239" }, { "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 ", @@ -10400,8 +11156,8 @@ "title":"Changing the Password of the OMS Database Administrator", "uri":"mrs_01_0567.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1156" + "p_code":"1232", + "code":"1240" }, { "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 ", @@ -10409,8 +11165,8 @@ "title":"Changing the Password of the Data Access User of the OMS Database", "uri":"mrs_01_0568.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1157" + "p_code":"1232", + "code":"1241" }, { "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", @@ -10418,8 +11174,8 @@ "title":"Changing the Password of a Component Database User", "uri":"mrs_01_0569.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1158" + "p_code":"1232", + "code":"1242" }, { "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", @@ -10427,8 +11183,8 @@ "title":"Replacing the HA Certificate", "uri":"mrs_01_0571.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1159" + "p_code":"1232", + "code":"1243" }, { "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", @@ -10436,8 +11192,8 @@ "title":"Updating Cluster Keys", "uri":"mrs_01_0572.html", "doc_type":"usermanual", - "p_code":"1148", - "code":"1160" + "p_code":"1232", + "code":"1244" }, { "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.", @@ -10445,8 +11201,8 @@ "title":"Permissions Management", "uri":"mrs_01_0573.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1161" + "p_code":"1046", + "code":"1245" }, { "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", @@ -10454,8 +11210,8 @@ "title":"Creating a Role", "uri":"mrs_01_0420.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1162" + "p_code":"1245", + "code":"1246" }, { "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", @@ -10463,8 +11219,8 @@ "title":"Creating a User Group", "uri":"mrs_01_0421.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1163" + "p_code":"1245", + "code":"1247" }, { "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", @@ -10472,8 +11228,8 @@ "title":"Creating a User", "uri":"mrs_01_0422.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1164" + "p_code":"1245", + "code":"1248" }, { "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 ", @@ -10481,8 +11237,8 @@ "title":"Modifying User Information", "uri":"mrs_01_0423.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1165" + "p_code":"1245", + "code":"1249" }, { "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", @@ -10490,8 +11246,8 @@ "title":"Locking a User", "uri":"mrs_01_0424.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1166" + "p_code":"1245", + "code":"1250" }, { "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", @@ -10499,8 +11255,8 @@ "title":"Unlocking a User", "uri":"mrs_01_0425.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1167" + "p_code":"1245", + "code":"1251" }, { "desc":"If an MRS cluster user is not required, the administrator can delete the user on MRS Manager.", @@ -10508,8 +11264,8 @@ "title":"Deleting a User", "uri":"mrs_01_0426.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1168" + "p_code":"1245", + "code":"1252" }, { "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 ", @@ -10517,8 +11273,8 @@ "title":"Changing the Password of an Operation User", "uri":"mrs_01_0427.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1169" + "p_code":"1245", + "code":"1253" }, { "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", @@ -10526,8 +11282,8 @@ "title":"Initializing the Password of a System User", "uri":"mrs_01_0428.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1170" + "p_code":"1245", + "code":"1254" }, { "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", @@ -10535,8 +11291,8 @@ "title":"Downloading a User Authentication File", "uri":"mrs_01_0429.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1171" + "p_code":"1245", + "code":"1255" }, { "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", @@ -10544,8 +11300,8 @@ "title":"Modifying a Password Policy", "uri":"mrs_01_0430.html", "doc_type":"usermanual", - "p_code":"1161", - "code":"1172" + "p_code":"1245", + "code":"1256" }, { "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.", @@ -10553,8 +11309,8 @@ "title":"MRS Multi-User Permission Management", "uri":"mrs_01_0340.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1173" + "p_code":"1046", + "code":"1257" }, { "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", @@ -10562,8 +11318,8 @@ "title":"Users and Permissions of MRS Clusters", "uri":"mrs_01_0341.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1174" + "p_code":"1257", + "code":"1258" }, { "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", @@ -10571,8 +11327,8 @@ "title":"Default Users of Clusters with Kerberos Authentication Enabled", "uri":"mrs_01_0342.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1175" + "p_code":"1257", + "code":"1259" }, { "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", @@ -10580,8 +11336,8 @@ "title":"Creating a Role", "uri":"mrs_01_0343.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1176" + "p_code":"1257", + "code":"1260" }, { "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", @@ -10589,8 +11345,8 @@ "title":"Creating a User Group", "uri":"mrs_01_0344.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1177" + "p_code":"1257", + "code":"1261" }, { "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", @@ -10598,8 +11354,8 @@ "title":"Creating a User", "uri":"mrs_01_0345.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1178" + "p_code":"1257", + "code":"1262" }, { "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", @@ -10607,8 +11363,8 @@ "title":"Modifying User Information", "uri":"mrs_01_0346.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1179" + "p_code":"1257", + "code":"1263" }, { "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", @@ -10616,8 +11372,8 @@ "title":"Locking a User", "uri":"mrs_01_0347.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1180" + "p_code":"1257", + "code":"1264" }, { "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", @@ -10625,8 +11381,8 @@ "title":"Unlocking a User", "uri":"mrs_01_0348.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1181" + "p_code":"1257", + "code":"1265" }, { "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 ", @@ -10634,8 +11390,8 @@ "title":"Deleting a User", "uri":"mrs_01_0349.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1182" + "p_code":"1257", + "code":"1266" }, { "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", @@ -10643,8 +11399,8 @@ "title":"Changing the Password of an Operation User", "uri":"mrs_01_0350.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1183" + "p_code":"1257", + "code":"1267" }, { "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", @@ -10652,8 +11408,8 @@ "title":"Initializing the Password of a System User", "uri":"mrs_01_0351.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1184" + "p_code":"1257", + "code":"1268" }, { "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", @@ -10661,8 +11417,8 @@ "title":"Downloading a User Authentication File", "uri":"mrs_01_0352.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1185" + "p_code":"1257", + "code":"1269" }, { "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", @@ -10670,8 +11426,8 @@ "title":"Modifying a Password Policy", "uri":"mrs_01_0353.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1186" + "p_code":"1257", + "code":"1270" }, { "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", @@ -10679,8 +11435,8 @@ "title":"Configuring Cross-Cluster Mutual Trust Relationships", "uri":"mrs_01_0354.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1187" + "p_code":"1257", + "code":"1271" }, { "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 ", @@ -10688,8 +11444,8 @@ "title":"Configuring Users to Access Resources of a Trusted Cluster", "uri":"mrs_01_0355.html", "doc_type":"usermanual", - "p_code":"1173", - "code":"1188" + "p_code":"1257", + "code":"1272" }, { "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.", @@ -10697,8 +11453,8 @@ "title":"Patch Operation Guide", "uri":"mrs_01_0574.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1189" + "p_code":"1046", + "code":"1273" }, { "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", @@ -10706,8 +11462,8 @@ "title":"Patch Operation Guide for Versions Earlier than MRS 1.7.0", "uri":"mrs_01_0575.html", "doc_type":"usermanual", - "p_code":"1189", - "code":"1190" + "p_code":"1273", + "code":"1274" }, { "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", @@ -10715,8 +11471,8 @@ "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":"1189", - "code":"1191" + "p_code":"1273", + "code":"1275" }, { "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", @@ -10724,8 +11480,8 @@ "title":"Supporting Rolling Patches", "uri":"mrs_01_0577.html", "doc_type":"usermanual", - "p_code":"1189", - "code":"1192" + "p_code":"1273", + "code":"1276" }, { "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", @@ -10733,8 +11489,8 @@ "title":"Restoring Patches for the Isolated Hosts", "uri":"mrs_01_0578.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1193" + "p_code":"1046", + "code":"1277" }, { "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", @@ -10742,8 +11498,8 @@ "title":"Rolling Restart", "uri":"mrs_01_0579.html", "doc_type":"usermanual", - "p_code":"962", - "code":"1194" + "p_code":"1046", + "code":"1278" }, { "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.", @@ -10752,7 +11508,7 @@ "uri":"mrs_01_0528.html", "doc_type":"usermanual", "p_code":"", - "code":"1195" + "code":"1279" }, { "desc":"The Hadoop community version provides two authentication modes: Kerberos authentication (security mode) and Simple authentication (normal mode). When creating a cluster, ", @@ -10760,8 +11516,8 @@ "title":"Security Configuration Suggestions for Clusters with Kerberos Authentication Disabled", "uri":"mrs_01_0419.html", "doc_type":"usermanual", - "p_code":"1195", - "code":"1196" + "p_code":"1279", + "code":"1280" }, { "desc":"For clusters in security mode with Kerberos authentication enabled, security authentication is required during application development.Kerberos, is now used to a concept ", @@ -10769,8 +11525,8 @@ "title":"Security Authentication Principles and Mechanisms", "uri":"mrs_07_020001.html", "doc_type":"usermanual", - "p_code":"1195", - "code":"1197" + "p_code":"1279", + "code":"1281" }, { "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", @@ -10779,7 +11535,7 @@ "uri":"mrs_01_0785.html", "doc_type":"usermanual", "p_code":"", - "code":"1198" + "code":"1282" }, { "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.", @@ -10788,7 +11544,7 @@ "uri":"mrs_01_0316.html", "doc_type":"usermanual", "p_code":"", - "code":"1199" + "code":"1283" }, { "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", @@ -10796,8 +11552,8 @@ "title":"Before You Start", "uri":"mrs_01_0605.html", "doc_type":"usermanual", - "p_code":"1199", - "code":"1200" + "p_code":"1283", + "code":"1284" }, { "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", @@ -10805,8 +11561,8 @@ "title":"Introduction", "uri":"mrs_01_0317.html", "doc_type":"usermanual", - "p_code":"1199", - "code":"1201" + "p_code":"1283", + "code":"1285" }, { "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 ", @@ -10814,8 +11570,8 @@ "title":"Backing Up Metadata", "uri":"mrs_01_0319.html", "doc_type":"usermanual", - "p_code":"1199", - "code":"1202" + "p_code":"1283", + "code":"1286" }, { "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", @@ -10823,8 +11579,8 @@ "title":"Restoring Metadata", "uri":"mrs_01_0321.html", "doc_type":"usermanual", - "p_code":"1199", - "code":"1203" + "p_code":"1283", + "code":"1287" }, { "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 ", @@ -10832,8 +11588,8 @@ "title":"Modifying Backup Tasks", "uri":"mrs_01_0324.html", "doc_type":"usermanual", - "p_code":"1199", - "code":"1204" + "p_code":"1283", + "code":"1288" }, { "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", @@ -10841,8 +11597,8 @@ "title":"Viewing Backup and Restoration Tasks", "uri":"mrs_01_0325.html", "doc_type":"usermanual", - "p_code":"1199", - "code":"1205" + "p_code":"1283", + "code":"1289" }, { "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.", @@ -10851,7 +11607,7 @@ "uri":"mrs_01_0444.html", "doc_type":"usermanual", "p_code":"", - "code":"1206" + "code":"1290" }, { "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", @@ -10859,8 +11615,8 @@ "title":"HDFS Data", "uri":"mrs_01_0445.html", "doc_type":"usermanual", - "p_code":"1206", - "code":"1207" + "p_code":"1290", + "code":"1291" }, { "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", @@ -10868,8 +11624,8 @@ "title":"Hive Metadata", "uri":"mrs_01_0446.html", "doc_type":"usermanual", - "p_code":"1206", - "code":"1208" + "p_code":"1290", + "code":"1292" }, { "desc":"Hive data is not backed up independently. For details, see HDFS Data.", @@ -10877,8 +11633,8 @@ "title":"Hive Data", "uri":"mrs_01_0447.html", "doc_type":"usermanual", - "p_code":"1206", - "code":"1209" + "p_code":"1290", + "code":"1293" }, { "desc":"Currently, HBase data can be backed up in the following modes:SnapshotsReplicationExportCopyTableHTable APIOffline backup of HDFS dataTable 1 compares the impact of opera", @@ -10886,8 +11642,8 @@ "title":"HBase Data", "uri":"mrs_01_0448.html", "doc_type":"usermanual", - "p_code":"1206", - "code":"1210" + "p_code":"1290", + "code":"1294" }, { "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", @@ -10895,8 +11651,8 @@ "title":"Kafka Data", "uri":"mrs_01_0449.html", "doc_type":"usermanual", - "p_code":"1206", - "code":"1211" + "p_code":"1290", + "code":"1295" }, { "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.", @@ -10905,7 +11661,7 @@ "uri":"mrs_01_9002.html", "doc_type":"usermanual", "p_code":"", - "code":"1212" + "code":"1296" }, { "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", @@ -10913,35 +11669,35 @@ "title":"Precautions for MRS 3.x", "uri":"mrs_01_0614.html", "doc_type":"usermanual", - "p_code":"1212", - "code":"1213" + "p_code":"1296", + "code":"1297" }, { "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":"Installing the Flume Client", "uri":"mrs_01_0392.html", - "doc_type":"cmpntguide", - "p_code":"1212", - "code":"1214" + "doc_type":"usermanual", + "p_code":"1296", + "code":"1298" }, { "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", "product_code":"mrs", "title":"Installing the Flume Client on Clusters of Versions Earlier Than MRS 3.x", "uri":"mrs_01_1594.html", - "doc_type":"cmpntguide", - "p_code":"1214", - "code":"1215" + "doc_type":"usermanual", + "p_code":"1298", + "code":"1299" }, { "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", "product_code":"mrs", "title":"Installing the Flume Client on MRS 3.x or Later Clusters", "uri":"mrs_01_1595.html", - "doc_type":"cmpntguide", - "p_code":"1214", - "code":"1216" + "doc_type":"usermanual", + "p_code":"1298", + "code":"1300" }, { "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.", @@ -10950,187 +11706,187 @@ "uri":"en-us_topic_0000001349287889.html", "doc_type":"usermanual", "p_code":"", - "code":"1217" + "code":"1301" }, { "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":"MRS Overview", "uri":"mrs_03_0002.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1218" + "doc_type":"usermanual", + "p_code":"1301", + "code":"1302" }, { "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", "product_code":"mrs", "title":"What Is MRS Used For?", "uri":"mrs_03_0001.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1219" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1303" }, { "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.", "product_code":"mrs", "title":"How Do I Create an MRS Cluster Using a Custom Security Group?", "uri":"mrs_03_1012.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1220" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1304" }, { "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", "product_code":"mrs", "title":"How Do I Use MRS?", "uri":"mrs_03_1013.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1221" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1305" }, { "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.", "product_code":"mrs", "title":"Can I Configure a Phoenix Connection Pool?", "uri":"mrs_03_1105.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1222" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1306" }, { "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", "product_code":"mrs", "title":"Does MRS Support Change of the Network Segment?", "uri":"mrs_03_1019.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1223" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1307" }, { "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", "product_code":"mrs", "title":"Can I Downgrade the Specifications of an MRS Cluster Node?", "uri":"mrs_03_1125.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1224" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1308" }, { "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", "product_code":"mrs", "title":"What Is the Relationship Between Hive and Other Components?", "uri":"mrs_03_1046.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1225" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1309" }, { "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.", "product_code":"mrs", "title":"Does an MRS Cluster Support Hive on Spark?", "uri":"mrs_03_1048.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1226" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1310" }, { "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", "product_code":"mrs", "title":"What Are the Differences Between Hive Versions?", "uri":"mrs_03_1081.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1227" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1311" }, { "desc":"MRS cluster 2.0.5 or later supports Hive connections on DataLake Governance Center (DGC) and provides the IAM user synchronization function.", "product_code":"mrs", "title":"Which MRS Cluster Version Supports Hive Connection and User Synchronization?", "uri":"mrs_03_1095.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1228" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1312" }, { "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. ", "product_code":"mrs", "title":"What Are the Differences Between OBS and HDFS in Data Storage?", "uri":"mrs_03_1062.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1229" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1313" }, { "desc":"Download it from https://github.com/Intel-bigdata/HiBench.", "product_code":"mrs", "title":"How Do I Obtain the Hadoop Pressure Test Tool?", "uri":"mrs_03_1092.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1230" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1314" }, { "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 ", "product_code":"mrs", "title":"What Is the Relationship Between Impala and Other Components?", "uri":"mrs_03_1065.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1231" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1315" }, { "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", "product_code":"mrs", "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":"1218", - "code":"1232" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1316" }, { "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", "product_code":"mrs", "title":"What Is the Relationship Between Kudu and HBase?", "uri":"mrs_03_1066.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1233" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1317" }, { "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", "product_code":"mrs", "title":"Does MRS Support Running Hive on Kudu?", "uri":"mrs_03_1068.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1234" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1318" }, { "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", "product_code":"mrs", "title":"What Are the Solutions for processing 1 Billion Data Records?", "uri":"mrs_03_1133.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1235" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1319" }, { "desc":"MRS does not support the change of the DBService IP address.", "product_code":"mrs", "title":"Can I Change the IP address of DBService?", "uri":"mrs_03_1137.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1236" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1320" }, { "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", "product_code":"mrs", "title":"Can I Clear MRS sudo Logs?", "uri":"mrs_03_1155.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1237" + "doc_type":"usermanual", + "p_code":"1302", + "code":"1321" }, { "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", @@ -11138,8 +11894,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":"1218", - "code":"1238" + "p_code":"1302", + "code":"1322" }, { "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", @@ -11147,762 +11903,6 @@ "title":"What Is Spark ThriftServer?", "uri":"en-us_topic_0000001442773925.html", "doc_type":"usermanual", - "p_code":"1218", - "code":"1239" - }, - { - "desc":"Kafka supports PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL.", - "product_code":"mrs", - "title":"What Access Protocols Are Supported by Kafka?", - "uri":"en-us_topic_0000001442494337.html", - "doc_type":"usermanual", - "p_code":"1218", - "code":"1240" - }, - { - "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", - "product_code":"mrs", - "title":"What Is the Compression Ratio of zstd?", - "uri":"en-us_topic_0000001392255170.html", - "doc_type":"usermanual", - "p_code":"1218", - "code":"1241" - }, - { - "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?", - "uri":"mrs_03_1202.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1242" - }, - { - "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?", - "uri":"mrs_03_1204.html", - "doc_type":"faq", - "p_code":"1218", - "code":"1243" - }, - { - "desc":"For MRS 3.1.0 clusters, Python 2.7 or 3.x is recommended for Spark tasks.", - "product_code":"mrs", - "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":"1218", - "code":"1244" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Enable Different Service Programs to Use Different YARN Queues?", - "uri":"mrs_03_1221.html", - "doc_type":"usermanual", - "p_code":"1218", - "code":"1245" - }, - { - "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":"1218", - "code":"1246" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Unbind an EIP from an MRS Cluster Node?", - "uri":"mrs_03_1246.html", - "doc_type":"usermanual", - "p_code":"1218", - "code":"1247" - }, - { - "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":"Account and Password", - "uri":"mrs_03_2003.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1248" - }, - { - "desc":"The default account for logging in to Manager is admin, and the password is the one you set when you created the cluster.", - "product_code":"mrs", - "title":"What Is the Account for Logging In to Manager?", - "uri":"mrs_03_1027.html", - "doc_type":"faq", - "p_code":"1248", - "code":"1249" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Query and Change the Password Validity Period of an Account?", - "uri":"mrs_03_1249.html", - "doc_type":"usermanual", - "p_code":"1248", - "code":"1250" - }, - { - "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":"Accounts and Permissions", - "uri":"mrs_03_2004.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1251" - }, - { - "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":"1251", - "code":"1252" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Assign Tenant Management Permission to a New Account?", - "uri":"mrs_03_1035.html", - "doc_type":"faq", - "p_code":"1251", - "code":"1253" - }, - { - "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.", - "product_code":"mrs", - "title":"How Do I Customize an MRS Policy?", - "uri":"mrs_03_1118.html", - "doc_type":"faq", - "p_code":"1251", - "code":"1254" - }, - { - "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.", - "product_code":"mrs", - "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":"1251", - "code":"1255" - }, - { - "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 ", - "product_code":"mrs", - "title":"Does Hue Support Account Permission Configuration?", - "uri":"mrs_03_1121.html", - "doc_type":"faq", - "p_code":"1251", - "code":"1256" - }, - { - "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":"Client Usage", - "uri":"mrs_03_2005.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1257" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Configure Environment Variables and Run Commands on a Component Client?", - "uri":"mrs_03_1031.html", - "doc_type":"faq", - "p_code":"1257", - "code":"1258" - }, - { - "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":"1257", - "code":"1259" - }, - { - "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", - "product_code":"mrs", - "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":"1257", - "code":"1260" - }, - { - "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":"Web Page Access", - "uri":"mrs_03_2006.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1261" - }, - { - "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", - "product_code":"mrs", - "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":"1261", - "code":"1262" - }, - { - "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", - "product_code":"mrs", - "title":"Why Cannot I Refresh the Dynamic Resource Plan Page on MRS Tenant Tab?", - "uri":"mrs_03_1156.html", - "doc_type":"faq", - "p_code":"1261", - "code":"1263" - }, - { - "desc":"sh /opt/Bigdata/apache-tomcat-7.0.78/bin/shutdown.sh", - "product_code":"mrs", - "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":"1261", - "code":"1264" - }, - { - "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":"Alarm Monitoring", - "uri":"mrs_03_2007.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1265" - }, - { - "desc":"The Kafka topic monitoring function cannot send alarms by email or SMS message. However, you can view alarm information on Manager.", - "product_code":"mrs", - "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":"1265", - "code":"1266" - }, - { - "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":"1265", - "code":"1267" - }, - { - "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":"1265", - "code":"1268" - }, - { - "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":"Performance Tuning", - "uri":"mrs_03_2008.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1269" - }, - { - "desc":"An MRS cluster does not support system reinstallation.", - "product_code":"mrs", - "title":"Does an MRS Cluster Support System Reinstallation?", - "uri":"mrs_03_1017.html", - "doc_type":"faq", - "p_code":"1269", - "code":"1270" - }, - { - "desc":"The OS of an MRS cluster cannot be changed.", - "product_code":"mrs", - "title":"Can I Change the OS of an MRS Cluster?", - "uri":"mrs_03_1203.html", - "doc_type":"faq", - "p_code":"1269", - "code":"1271" - }, - { - "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":"1269", - "code":"1272" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Stop the Firewall Service?", - "uri":"mrs_03_1072.html", - "doc_type":"faq", - "p_code":"1269", - "code":"1273" - }, - { - "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":"Job Development", - "uri":"mrs_03_2009.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1274" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Get My Data into OBS or HDFS?", - "uri":"mrs_03_1015.html", - "doc_type":"faq", - "p_code":"1274", - "code":"1275" - }, - { - "desc":"MRS clusters support Spark jobs submitted in Spark, Spark Script, or Spark SQL mode.", - "product_code":"mrs", - "title":"What Types of Spark Jobs Can Be Submitted in a Cluster?", - "uri":"mrs_03_1050.html", - "doc_type":"faq", - "p_code":"1274", - "code":"1276" - }, - { - "desc":"You can run only one Spark task at a time after the minimum tenant resources of an MRS cluster is changed to 0.", - "product_code":"mrs", - "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":"1274", - "code":"1277" - }, - { - "desc":"You need to understand the concept ApplicationMaster before understanding the essential differences between Yarn-client and Yarn-cluster.In Yarn, each application instanc", - "product_code":"mrs", - "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":"1274", - "code":"1278" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1279" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1280" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1281" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1282" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1283" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1284" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1285" - }, - { - "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 ", - "product_code":"mrs", - "title":"Why DataArtsStudio Occasionally Fail to Schedule Spark Jobs and the Rescheduling also Fails?", - "uri":"mrs_03_1208.html", - "doc_type":"faq", - "p_code":"1274", - "code":"1286" - }, - { - "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. ", - "product_code":"mrs", - "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":"1274", - "code":"1287" - }, - { - "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 ", - "product_code":"mrs", - "title":"Why Submitted Yarn Job Cannot Be Viewed on the Web UI?", - "uri":"mrs_03_1223.html", - "doc_type":"usermanual", - "p_code":"1274", - "code":"1288" - }, - { - "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 ", - "product_code":"mrs", - "title":"How Do I Modify the HDFS NameSpace (fs.defaultFS) of an Existing Cluster?", - "uri":"mrs_03_1224.html", - "doc_type":"usermanual", - "p_code":"1274", - "code":"1289" - }, - { - "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 ", - "product_code":"mrs", - "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":"1274", - "code":"1290" - }, - { - "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", - "product_code":"mrs", - "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":"1274", - "code":"1291" - }, - { - "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", - "product_code":"mrs", - "title":"Data Import and Export of DistCP Jobs", - "uri":"mrs_03_1238.html", - "doc_type":"usermanual", - "p_code":"1274", - "code":"1292" - }, - { - "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":"Cluster Upgrade/Patching", - "uri":"mrs_03_2010.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1293" - }, - { - "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.", - "product_code":"mrs", - "title":"Can I Upgrade an MRS Cluster?", - "uri":"mrs_03_1089.html", - "doc_type":"usermanual", - "p_code":"1293", - "code":"1294" - }, - { - "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.", - "product_code":"mrs", - "title":"Can I Change the MRS Cluster Version?", - "uri":"mrs_03_1021.html", - "doc_type":"usermanual", - "p_code":"1293", - "code":"1295" - }, - { - "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":"Cluster Access", - "uri":"mrs_03_2013.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1296" - }, - { - "desc":"No. You can select the login mode when creating the cluster. You cannot change the login mode after you created the cluster.", - "product_code":"mrs", - "title":"Can I Switch Between the Two Login Modes of MRS?", - "uri":"mrs_03_1029.html", - "doc_type":"usermanual", - "p_code":"1296", - "code":"1297" - }, - { - "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":"1296", - "code":"1298" - }, - { - "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.", - "product_code":"mrs", - "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":"1296", - "code":"1299" - }, - { - "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 ", - "product_code":"mrs", - "title":"How Do I Access an MRS Cluster from a Node Outside the Cluster?", - "uri":"mrs_03_1234.html", - "doc_type":"usermanual", - "p_code":"1296", - "code":"1300" - }, - { - "desc":"You have obtained the account AK and SK. For details, see How Do I Manage Access Keys?Install ICAgent on the MRS node. For details, see Installing ICAgent.For the first i", - "product_code":"", - "title":"How Do I Interconnect MRS with LTS?", - "uri":"mrs_03_1244.html", - "doc_type":"", - "p_code":"1296", - "code":"1301" - }, - { - "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":"Big Data Service Development", - "uri":"mrs_03_2014.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1302" - }, - { - "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", - "product_code":"mrs", - "title":"Can MRS Run Multiple Flume Tasks at a Time?", - "uri":"mrs_03_1059.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1303" - }, - { - "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, ", - "product_code":"mrs", - "title":"How Do I Change FlumeClient Logs to Standard Logs?", - "uri":"mrs_03_1058.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1304" - }, - { - "desc":"hadoopstreaming.jar: /opt/share/hadoop-streaming-* (* indicates the Hadoop version.)JDK environment variables: /opt/client/JDK/component_envHadoop environment variables: ", - "product_code":"mrs", - "title":"Where Are the JAR Files and Environment Variables of Hadoop Stored?", - "uri":"mrs_03_1064.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1305" - }, - { - "desc":"HBase supports the Snappy, LZ4, and gzip compression algorithms.", - "product_code":"mrs", - "title":"What Compression Algorithms Does HBase Support?", - "uri":"mrs_03_1042.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1306" - }, - { - "desc":"No. Hive on HBase supports only data query.", - "product_code":"mrs", - "title":"Can MRS Write Data to HBase Through the HBase External Table of Hive?", - "uri":"mrs_03_1044.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1307" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I View HBase Logs?", - "uri":"mrs_03_1045.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1308" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Set the TTL for an HBase Table?", - "uri":"mrs_03_1140.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1309" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Balance HDFS Data?", - "uri":"mrs_03_1113.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1310" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Change the Number of HDFS Replicas?", - "uri":"mrs_03_1061.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1311" - }, - { - "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", - "product_code":"mrs", - "title":"What Is the Port for Accessing HDFS Using Python?", - "uri":"mrs_03_1060.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1312" - }, - { - "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 ", - "product_code":"mrs", - "title":"How Do I Modify the HDFS Active/Standby Switchover Class?", - "uri":"mrs_03_1196.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1313" - }, - { - "desc":"smallint is recommended.", - "product_code":"mrs", - "title":"What Is the Recommended Number Type of DynamoDB in Hive Tables?", - "uri":"mrs_03_1047.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1314" - }, - { - "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", - "product_code":"mrs", - "title":"Can the Hive Driver Be Interconnected with DBCP2?", - "uri":"mrs_03_1049.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1315" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I View the Hive Table Created by Another User?", - "uri":"mrs_03_1082.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1316" - }, - { - "desc":"Run the following statement to export the query result of Hive data:", - "product_code":"mrs", - "title":"Can I Export the Query Result of Hive Data?", - "uri":"mrs_03_1149.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1317" - }, - { - "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?", - "uri":"mrs_03_1194.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1318" - }, - { - "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", - "product_code":"mrs", - "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":"1302", - "code":"1319" - }, - { - "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", - "product_code":"mrs", - "title":"What If an Excel File Downloaded on Hue Failed to Open?", - "uri":"mrs_03_1160.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1320" - }, - { - "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", - "product_code":"mrs", - "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":"1302", - "code":"1321" - }, - { - "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", - "product_code":"mrs", - "title":"How Do I Reset Kafka Data?", - "uri":"mrs_03_1106.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1322" - }, - { - "desc":"Run the --bootstrap-server command to query the information about the client.", - "product_code":"mrs", - "title":"How Do I Obtain the Client Version of MRS Kafka?", - "uri":"mrs_03_1145.html", - "doc_type":"faq", "p_code":"1302", "code":"1323" }, @@ -11910,136 +11910,892 @@ "desc":"Kafka supports PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL.", "product_code":"mrs", "title":"What Access Protocols Are Supported by Kafka?", - "uri":"mrs_03_1146.html", - "doc_type":"faq", + "uri":"en-us_topic_0000001442494337.html", + "doc_type":"usermanual", "p_code":"1302", "code":"1324" }, + { + "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", + "product_code":"mrs", + "title":"What Is the Compression Ratio of zstd?", + "uri":"en-us_topic_0000001392255170.html", + "doc_type":"usermanual", + "p_code":"1302", + "code":"1325" + }, + { + "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?", + "uri":"mrs_03_1202.html", + "doc_type":"usermanual", + "p_code":"1302", + "code":"1326" + }, + { + "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?", + "uri":"mrs_03_1204.html", + "doc_type":"usermanual", + "p_code":"1302", + "code":"1327" + }, + { + "desc":"For MRS 3.1.0 clusters, Python 2.7 or 3.x is recommended for Spark tasks.", + "product_code":"mrs", + "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":"1302", + "code":"1328" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Enable Different Service Programs to Use Different YARN Queues?", + "uri":"mrs_03_1221.html", + "doc_type":"usermanual", + "p_code":"1302", + "code":"1329" + }, + { + "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":"1302", + "code":"1330" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Unbind an EIP from an MRS Cluster Node?", + "uri":"mrs_03_1246.html", + "doc_type":"usermanual", + "p_code":"1302", + "code":"1331" + }, + { + "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":"Account and Password", + "uri":"mrs_03_2003.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1332" + }, + { + "desc":"The default account for logging in to Manager is admin, and the password is the one you set when you created the cluster.", + "product_code":"mrs", + "title":"What Is the Account for Logging In to Manager?", + "uri":"mrs_03_1027.html", + "doc_type":"usermanual", + "p_code":"1332", + "code":"1333" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Query and Change the Password Validity Period of an Account?", + "uri":"mrs_03_1249.html", + "doc_type":"usermanual", + "p_code":"1332", + "code":"1334" + }, + { + "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":"Accounts and Permissions", + "uri":"mrs_03_2004.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1335" + }, + { + "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":"usermanual", + "p_code":"1335", + "code":"1336" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Assign Tenant Management Permission to a New Account?", + "uri":"mrs_03_1035.html", + "doc_type":"usermanual", + "p_code":"1335", + "code":"1337" + }, + { + "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.", + "product_code":"mrs", + "title":"How Do I Customize an MRS Policy?", + "uri":"mrs_03_1118.html", + "doc_type":"usermanual", + "p_code":"1335", + "code":"1338" + }, + { + "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.", + "product_code":"mrs", + "title":"Why Is the Manage User Function Unavailable on the System Page on MRS Manager?", + "uri":"mrs_03_1037.html", + "doc_type":"usermanual", + "p_code":"1335", + "code":"1339" + }, + { + "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 ", + "product_code":"mrs", + "title":"Does Hue Support Account Permission Configuration?", + "uri":"mrs_03_1121.html", + "doc_type":"usermanual", + "p_code":"1335", + "code":"1340" + }, + { + "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":"Client Usage", + "uri":"mrs_03_2005.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1341" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Configure Environment Variables and Run Commands on a Component Client?", + "uri":"mrs_03_1031.html", + "doc_type":"usermanual", + "p_code":"1341", + "code":"1342" + }, + { + "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":"1341", + "code":"1343" + }, + { + "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", + "product_code":"mrs", + "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":"1341", + "code":"1344" + }, + { + "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":"Web Page Access", + "uri":"mrs_03_2006.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1345" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Change the Session Timeout Duration for an Open Source Component Web UI?", + "uri":"mrs_03_1151.html", + "doc_type":"usermanual", + "p_code":"1345", + "code":"1346" + }, + { + "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", + "product_code":"mrs", + "title":"Why Cannot I Refresh the Dynamic Resource Plan Page on MRS Tenant Tab?", + "uri":"mrs_03_1156.html", + "doc_type":"usermanual", + "p_code":"1345", + "code":"1347" + }, + { + "desc":"sh /opt/Bigdata/apache-tomcat-7.0.78/bin/shutdown.sh", + "product_code":"mrs", + "title":"What Do I Do If the Kafka Topic Monitoring Tab Is Unavailable on Manager?", + "uri":"mrs_03_1166.html", + "doc_type":"usermanual", + "p_code":"1345", + "code":"1348" + }, + { + "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":"Alarm Monitoring", + "uri":"mrs_03_2007.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1349" + }, + { + "desc":"The Kafka topic monitoring function cannot send alarms by email or SMS message. However, you can view alarm information on Manager.", + "product_code":"mrs", + "title":"In an MRS Streaming Cluster, Can the Kafka Topic Monitoring Function Send Alarm Notifications?", + "uri":"mrs_03_1055.html", + "doc_type":"usermanual", + "p_code":"1349", + "code":"1350" + }, + { + "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":"1349", + "code":"1351" + }, + { + "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":"1349", + "code":"1352" + }, + { + "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":"Performance Tuning", + "uri":"mrs_03_2008.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1353" + }, + { + "desc":"An MRS cluster does not support system reinstallation.", + "product_code":"mrs", + "title":"Does an MRS Cluster Support System Reinstallation?", + "uri":"mrs_03_1017.html", + "doc_type":"usermanual", + "p_code":"1353", + "code":"1354" + }, + { + "desc":"The OS of an MRS cluster cannot be changed.", + "product_code":"mrs", + "title":"Can I Change the OS of an MRS Cluster?", + "uri":"mrs_03_1203.html", + "doc_type":"usermanual", + "p_code":"1353", + "code":"1355" + }, + { + "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":"usermanual", + "p_code":"1353", + "code":"1356" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Stop the Firewall Service?", + "uri":"mrs_03_1072.html", + "doc_type":"usermanual", + "p_code":"1353", + "code":"1357" + }, + { + "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":"Job Development", + "uri":"mrs_03_2009.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1358" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Get My Data into OBS or HDFS?", + "uri":"mrs_03_1015.html", + "doc_type":"usermanual", + "p_code":"1358", + "code":"1359" + }, + { + "desc":"MRS clusters support Spark jobs submitted in Spark, Spark Script, or Spark SQL mode.", + "product_code":"mrs", + "title":"What Types of Spark Jobs Can Be Submitted in a Cluster?", + "uri":"mrs_03_1050.html", + "doc_type":"usermanual", + "p_code":"1358", + "code":"1360" + }, + { + "desc":"You can run only one Spark task at a time after the minimum tenant resources of an MRS cluster is changed to 0.", + "product_code":"mrs", + "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":"usermanual", + "p_code":"1358", + "code":"1361" + }, + { + "desc":"You need to understand the concept ApplicationMaster before understanding the essential differences between Yarn-client and Yarn-cluster.In Yarn, each application instanc", + "product_code":"mrs", + "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":"1358", + "code":"1362" + }, + { + "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", + "product_code":"mrs", + "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":"usermanual", + "p_code":"1358", + "code":"1363" + }, + { + "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", + "product_code":"mrs", + "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":"1358", + "code":"1364" + }, + { + "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", + "product_code":"mrs", + "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":"1358", + "code":"1365" + }, + { + "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", + "product_code":"mrs", + "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":"1358", + "code":"1366" + }, + { + "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", + "product_code":"mrs", + "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":"usermanual", + "p_code":"1358", + "code":"1367" + }, + { + "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", + "product_code":"mrs", + "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":"usermanual", + "p_code":"1358", + "code":"1368" + }, + { + "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", + "product_code":"mrs", + "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":"usermanual", + "p_code":"1358", + "code":"1369" + }, + { + "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 ", + "product_code":"mrs", + "title":"Why DataArtsStudio Occasionally Fail to Schedule Spark Jobs and the Rescheduling also Fails?", + "uri":"mrs_03_1208.html", + "doc_type":"usermanual", + "p_code":"1358", + "code":"1370" + }, + { + "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. ", + "product_code":"mrs", + "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":"1358", + "code":"1371" + }, + { + "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 ", + "product_code":"mrs", + "title":"Why Submitted Yarn Job Cannot Be Viewed on the Web UI?", + "uri":"mrs_03_1223.html", + "doc_type":"usermanual", + "p_code":"1358", + "code":"1372" + }, + { + "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 ", + "product_code":"mrs", + "title":"How Do I Modify the HDFS NameSpace (fs.defaultFS) of an Existing Cluster?", + "uri":"mrs_03_1224.html", + "doc_type":"usermanual", + "p_code":"1358", + "code":"1373" + }, + { + "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 ", + "product_code":"mrs", + "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":"1358", + "code":"1374" + }, + { + "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", + "product_code":"mrs", + "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":"1358", + "code":"1375" + }, + { + "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", + "product_code":"mrs", + "title":"Data Import and Export of DistCP Jobs", + "uri":"mrs_03_1238.html", + "doc_type":"usermanual", + "p_code":"1358", + "code":"1376" + }, + { + "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":"Cluster Upgrade/Patching", + "uri":"mrs_03_2010.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1377" + }, + { + "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.", + "product_code":"mrs", + "title":"Can I Upgrade an MRS Cluster?", + "uri":"mrs_03_1089.html", + "doc_type":"usermanual", + "p_code":"1377", + "code":"1378" + }, + { + "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.", + "product_code":"mrs", + "title":"Can I Change the MRS Cluster Version?", + "uri":"mrs_03_1021.html", + "doc_type":"usermanual", + "p_code":"1377", + "code":"1379" + }, + { + "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":"Cluster Access", + "uri":"mrs_03_2013.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1380" + }, + { + "desc":"No. You can select the login mode when creating the cluster. You cannot change the login mode after you created the cluster.", + "product_code":"mrs", + "title":"Can I Switch Between the Two Login Modes of MRS?", + "uri":"mrs_03_1029.html", + "doc_type":"usermanual", + "p_code":"1380", + "code":"1381" + }, + { + "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":"usermanual", + "p_code":"1380", + "code":"1382" + }, + { + "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.", + "product_code":"mrs", + "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":"usermanual", + "p_code":"1380", + "code":"1383" + }, + { + "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 ", + "product_code":"mrs", + "title":"How Do I Access an MRS Cluster from a Node Outside the Cluster?", + "uri":"mrs_03_1234.html", + "doc_type":"usermanual", + "p_code":"1380", + "code":"1384" + }, + { + "desc":"You have obtained the account AK and SK. For details, see How Do I Manage Access Keys?Install ICAgent on the MRS node. For details, see Installing ICAgent.For the first i", + "product_code":"mrs", + "title":"How Do I Interconnect MRS with LTS?", + "uri":"mrs_03_1244.html", + "doc_type":"usermanual", + "p_code":"1380", + "code":"1385" + }, + { + "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":"Big Data Service Development", + "uri":"mrs_03_2014.html", + "doc_type":"usermanual", + "p_code":"1301", + "code":"1386" + }, + { + "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", + "product_code":"mrs", + "title":"Can MRS Run Multiple Flume Tasks at a Time?", + "uri":"mrs_03_1059.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1387" + }, + { + "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, r", + "product_code":"mrs", + "title":"How Do I Change FlumeClient Logs to Standard Logs?", + "uri":"mrs_03_1058.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1388" + }, + { + "desc":"hadoopstreaming.jar: /opt/share/hadoop-streaming-* (* indicates the Hadoop version.)JDK environment variables: /opt/client/JDK/component_envHadoop environment variables: ", + "product_code":"mrs", + "title":"Where Are the JAR Files and Environment Variables of Hadoop Stored?", + "uri":"mrs_03_1064.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1389" + }, + { + "desc":"HBase supports the Snappy, LZ4, and gzip compression algorithms.", + "product_code":"mrs", + "title":"What Compression Algorithms Does HBase Support?", + "uri":"mrs_03_1042.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1390" + }, + { + "desc":"No. Hive on HBase supports only data query.", + "product_code":"mrs", + "title":"Can MRS Write Data to HBase Through the HBase External Table of Hive?", + "uri":"mrs_03_1044.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1391" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I View HBase Logs?", + "uri":"mrs_03_1045.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1392" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Set the TTL for an HBase Table?", + "uri":"mrs_03_1140.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1393" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Balance HDFS Data?", + "uri":"mrs_03_1113.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1394" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Change the Number of HDFS Replicas?", + "uri":"mrs_03_1061.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1395" + }, + { + "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", + "product_code":"mrs", + "title":"What Is the Port for Accessing HDFS Using Python?", + "uri":"mrs_03_1060.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1396" + }, + { + "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 ", + "product_code":"mrs", + "title":"How Do I Modify the HDFS Active/Standby Switchover Class?", + "uri":"mrs_03_1196.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1397" + }, + { + "desc":"smallint is recommended.", + "product_code":"mrs", + "title":"What Is the Recommended Number Type of DynamoDB in Hive Tables?", + "uri":"mrs_03_1047.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1398" + }, + { + "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", + "product_code":"mrs", + "title":"Can the Hive Driver Be Interconnected with DBCP2?", + "uri":"mrs_03_1049.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1399" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I View the Hive Table Created by Another User?", + "uri":"mrs_03_1082.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1400" + }, + { + "desc":"Run the following statement to export the query result of Hive data:", + "product_code":"mrs", + "title":"Can I Export the Query Result of Hive Data?", + "uri":"mrs_03_1149.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1401" + }, + { + "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?", + "uri":"mrs_03_1194.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1402" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Do If a \"hivesql/hivescript\" Job Fails to Submit After Hive Is Added?", + "uri":"mrs_03_1200.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1403" + }, + { + "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", + "product_code":"mrs", + "title":"What If an Excel File Downloaded on Hue Failed to Open?", + "uri":"mrs_03_1160.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1404" + }, + { + "desc":"Applicable versions: MRS 3.1.0 and earlierModify the following file on the two Hue nodes:/opt/Bigdata/*_Porter_8.*/install/*-Hue-*/hue/apps/beeswax/src/beeswax/models.py/", + "product_code":"mrs", + "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":"1386", + "code":"1405" + }, + { + "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", + "product_code":"mrs", + "title":"How Do I Reset Kafka Data?", + "uri":"mrs_03_1106.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1406" + }, + { + "desc":"Run the --bootstrap-server command to query the information about the client.", + "product_code":"mrs", + "title":"How Do I Obtain the Client Version of MRS Kafka?", + "uri":"mrs_03_1145.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1407" + }, + { + "desc":"Kafka supports PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL.", + "product_code":"mrs", + "title":"What Access Protocols Are Supported by Kafka?", + "uri":"mrs_03_1146.html", + "doc_type":"usermanual", + "p_code":"1386", + "code":"1408" + }, { "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 ", "product_code":"mrs", "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":"1302", - "code":"1325" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1409" }, { "desc":"Kudu supports Snappy, LZ4, and zlib. LZ4 is used by default.", "product_code":"mrs", "title":"What Compression Algorithms Does Kudu Support?", "uri":"mrs_03_1067.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1326" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1410" }, { "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", "product_code":"mrs", "title":"How Do I View Kudu Logs?", "uri":"mrs_03_1069.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1327" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1411" }, { "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 ", "product_code":"mrs", "title":"How Do I Handle the Kudu Service Exceptions Generated During Cluster Creation?", "uri":"mrs_03_1169.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1328" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1412" }, { "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", "product_code":"mrs", "title":"Does OpenTSDB Support Python APIs?", "uri":"mrs_03_1070.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1329" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1413" }, { "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", "product_code":"mrs", "title":"How Do I Configure Other Data Sources on Presto?", "uri":"mrs_03_1147.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1330" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1414" }, { "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 ", "product_code":"mrs", "title":"How Do I Connect to Spark Shell from MRS?", "uri":"mrs_03_1157.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1331" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1415" }, { "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 ", "product_code":"mrs", "title":"How Do I Connect to Spark Beeline from MRS?", "uri":"mrs_03_1158.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1332" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1416" }, { "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/", "product_code":"mrs", "title":"Where Are the Execution Logs of Spark Jobs Stored?", "uri":"mrs_03_1159.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1333" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1417" }, { "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", "product_code":"mrs", "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":"1302", - "code":"1334" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1418" }, { "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", "product_code":"mrs", "title":"How Do I Check Whether the ResourceManager Configuration of Yarn Is Correct?", "uri":"mrs_03_1163.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1335" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1419" }, { "desc":"cd /opt/Client installation directorysourcebigdata_envkinit MRS cluster userThe user must have the ClickHouse administrator permissions.set allow_drop_detached=1;SELECT *", "product_code":"mrs", "title":"How Do I Modify the allow_drop_detached Parameter of ClickHouse?", "uri":"mrs_03_1210.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1336" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1420" }, { "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", "product_code":"mrs", "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":"1302", - "code":"1337" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1421" }, { "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", "product_code":"mrs", "title":"How Do I Do If ClickHouse Consumes Excessive CPU Resources?", "uri":"mrs_03_1209.html", - "doc_type":"faq", - "p_code":"1302", - "code":"1338" + "doc_type":"usermanual", + "p_code":"1386", + "code":"1422" }, { "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", @@ -12047,8 +12803,8 @@ "title":"How Do I Enable the Map Type on ClickHouse?", "uri":"mrs_03_1217.html", "doc_type":"usermanual", - "p_code":"1302", - "code":"1339" + "p_code":"1386", + "code":"1423" }, { "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", @@ -12056,170 +12812,170 @@ "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":"1302", - "code":"1340" + "p_code":"1386", + "code":"1424" }, { "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":"API", "uri":"mrs_03_2015.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1341" + "doc_type":"usermanual", + "p_code":"1301", + "code":"1425" }, { "desc":"When you use the API for adjusting cluster nodes, the value of node_id is fixed to node_orderadd.", "product_code":"mrs", "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":"1341", - "code":"1342" + "doc_type":"usermanual", + "p_code":"1425", + "code":"1426" }, { "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":"Cluster Management", "uri":"mrs_03_2016.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1343" + "doc_type":"usermanual", + "p_code":"1301", + "code":"1427" }, { "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", "product_code":"mrs", "title":"How Do I View All Clusters?", "uri":"mrs_03_1002.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1344" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1428" }, { "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", "product_code":"mrs", "title":"How Do I View Log Information?", "uri":"mrs_03_1003.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1345" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1429" }, { "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", "product_code":"mrs", "title":"How Do I View Cluster Configuration Information?", "uri":"mrs_03_1004.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1346" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1430" }, { "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 ", "product_code":"mrs", "title":"How Do I Install Kafka and Flume in an MRS Cluster?", "uri":"mrs_03_1054.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1347" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1431" }, { "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.", "product_code":"mrs", "title":"How Do I Stop an MRS Cluster?", "uri":"mrs_03_1016.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1348" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1432" }, { "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", "product_code":"mrs", "title":"Can I Expand Data Disk Capacity for MRS?", "uri":"mrs_03_1018.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1349" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1433" }, { "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.", "product_code":"mrs", "title":"Can I Add Components to an Existing Cluster?", "uri":"mrs_03_1024.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1350" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1434" }, { "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", "product_code":"mrs", "title":"Can I Delete Components Installed in an MRS Cluster?", "uri":"mrs_03_1028.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1351" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1435" }, { "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", "product_code":"mrs", "title":"Can I Change MRS Cluster Nodes on the MRS Console?", "uri":"mrs_03_1034.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1352" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1436" }, { "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", "product_code":"mrs", "title":"How Do I Shield Cluster Alarm/Event Notifications?", "uri":"mrs_03_1130.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1353" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1437" }, { "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", "product_code":"mrs", "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":"1343", - "code":"1354" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1438" }, { "desc":"su ommvim /opt/knox/bin/gateway.shsh /opt/knox/bin/gateway.sh stopsh /opt/knox/bin/gateway.sh start", "product_code":"mrs", "title":"How Do I Configure the knox Memory?", "uri":"mrs_03_1162.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1355" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1439" }, { "desc":"Log in to a Master node as user root and run the Python3 command to query the Python version.", "product_code":"mrs", "title":"What Is the Python Version Installed for an MRS Cluster?", "uri":"mrs_03_1171.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1356" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1440" }, { "desc":"The configuration file paths of commonly used components are as follows:", "product_code":"mrs", "title":"How Do I View the Configuration File Directory of Each Component?", "uri":"mrs_03_1198.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1357" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1441" }, { "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 ", "product_code":"mrs", "title":"How Do I Do If the Time on MRS Nodes Is Incorrect?", "uri":"mrs_03_1211.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1358" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1442" }, { "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\"", @@ -12227,17 +12983,17 @@ "title":"How Do I Query the Startup Time of an MRS Node?", "uri":"mrs_03_1250.html", "doc_type":"usermanual", - "p_code":"1343", - "code":"1359" + "p_code":"1427", + "code":"1443" }, { "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", "product_code":"mrs", "title":"How Do I Do If Trust Relationships Between Nodes Are Abnormal?", "uri":"mrs_03_1212.html", - "doc_type":"faq", - "p_code":"1343", - "code":"1360" + "doc_type":"usermanual", + "p_code":"1427", + "code":"1444" }, { "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 ", @@ -12245,35 +13001,35 @@ "title":"How Do I Adjust the Memory Size of the manager-executor Process?", "uri":"mrs_03_1228.html", "doc_type":"usermanual", - "p_code":"1343", - "code":"1361" + "p_code":"1427", + "code":"1445" }, { "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":"Kerberos Usage", "uri":"mrs_03_2018.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1362" + "doc_type":"usermanual", + "p_code":"1301", + "code":"1446" }, { "desc":"You cannot change the Kerberos service after an MRS cluster is created.", "product_code":"mrs", "title":"How Do I Change the Kerberos Authentication Status of a Created MRS Cluster?", "uri":"mrs_03_1038.html", - "doc_type":"faq", - "p_code":"1362", - "code":"1363" + "doc_type":"usermanual", + "p_code":"1446", + "code":"1447" }, { "desc":"The Kerberos authentication service uses ports 21730 (TCP), 21731 (TCP/UDP), and 21732 (TCP/UDP).", "product_code":"mrs", "title":"What Are the Ports of the Kerberos Authentication Service?", "uri":"mrs_03_1131.html", - "doc_type":"faq", - "p_code":"1362", - "code":"1364" + "doc_type":"usermanual", + "p_code":"1446", + "code":"1448" }, { "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 ", @@ -12281,35 +13037,35 @@ "title":"How Do I Deploy the Kerberos Service in a Running Cluster?", "uri":"mrs_03_1148.html", "doc_type":"usermanual", - "p_code":"1362", - "code":"1365" + "p_code":"1446", + "code":"1449" }, { "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", "product_code":"mrs", "title":"How Do I Access Hive in a Cluster with Kerberos Authentication Enabled?", "uri":"mrs_03_1152.html", - "doc_type":"faq", - "p_code":"1362", - "code":"1366" + "doc_type":"usermanual", + "p_code":"1446", + "code":"1450" }, { "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", "product_code":"mrs", "title":"How Do I Access Presto in a Cluster with Kerberos Authentication Enabled?", "uri":"mrs_03_1153.html", - "doc_type":"faq", - "p_code":"1362", - "code":"1367" + "doc_type":"usermanual", + "p_code":"1446", + "code":"1451" }, { "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", "product_code":"mrs", "title":"How Do I Access Spark in a Cluster with Kerberos Authentication Enabled?", "uri":"en-us_topic_0000001442653993.html", - "doc_type":"faq", - "p_code":"1362", - "code":"1368" + "doc_type":"usermanual", + "p_code":"1446", + "code":"1452" }, { "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", @@ -12317,26 +13073,26 @@ "title":"How Do I Prevent Kerberos Authentication Expiration?", "uri":"mrs_03_1167.html", "doc_type":"usermanual", - "p_code":"1362", - "code":"1369" + "p_code":"1446", + "code":"1453" }, { "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":"Metadata Management", "uri":"mrs_03_2019.html", - "doc_type":"faq", - "p_code":"1217", - "code":"1370" + "doc_type":"usermanual", + "p_code":"1301", + "code":"1454" }, { "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", "product_code":"mrs", "title":"Where Can I View Hive Metadata?", "uri":"mrs_03_1119.html", - "doc_type":"faq", - "p_code":"1370", - "code":"1371" + "doc_type":"usermanual", + "p_code":"1454", + "code":"1455" }, { "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.", @@ -12345,6 +13101,6 @@ "uri":"mrs_01_9003.html", "doc_type":"usermanual", "p_code":"", - "code":"1372" + "code":"1456" } ] \ No newline at end of file diff --git a/docs/mrs/umn/admin_guide_000002.html b/docs/mrs/umn/admin_guide_000002.html index d75ee2bad..0c153dab1 100644 --- a/docs/mrs/umn/admin_guide_000002.html +++ b/docs/mrs/umn/admin_guide_000002.html @@ -5,48 +5,47 @@
                                                                      • 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 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. -
                                                                    Table 1 Functions of each portal on the operation bar

                                                                    Portal

                                                                    +
                                                                    - - - - - - - - - - - - - - - diff --git a/docs/mrs/umn/admin_guide_000003.html b/docs/mrs/umn/admin_guide_000003.html index 65c51772e..1e74fb7db 100644 --- a/docs/mrs/umn/admin_guide_000003.html +++ b/docs/mrs/umn/admin_guide_000003.html @@ -8,7 +8,7 @@

                                                                    ./queryManager.sh

                                                                    The following information is displayed:

                                                                         Version             Package                                                          Cputype
-     ***                 FusionInsight_Manager_***                                        x86_64
                                                                    + *** ***_Manager_*** x86_64

                                                                    *** indicates the version number. Replace it with the actual version number.

                                                                    diff --git a/docs/mrs/umn/admin_guide_000011.html b/docs/mrs/umn/admin_guide_000011.html index 1c5566234..9da102bf9 100644 --- a/docs/mrs/umn/admin_guide_000011.html +++ b/docs/mrs/umn/admin_guide_000011.html @@ -4,7 +4,7 @@

                                                                    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.

                                                                    -

                                                                    For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from Manager. You can choose More in the upper right corner of the Homepage to access cluster maintenance and management functions.

                                                                    +

                                                                    For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from Manager. You can choose More in the upper right corner of the Homepage to access cluster maintenance and management functions.

                                                                    Table 1 Functions of each portal on the operation bar

                                                                    Portal

                                                                    Function Description

                                                                    +

                                                                    Function Description

                                                                    Home Page

                                                                    +

                                                                    Home Page

                                                                    Displays key monitoring metrics of clusters and host statuses in column charts, line charts, and tables. You can customize a dashboard for key monitoring metrics and drag them onto any positions on the UI. The Summary tab page supports automatic data update. For details, see Home Page.

                                                                    +

                                                                    Displays key monitoring metrics of clusters and host statuses in column charts, line charts, and tables. You can customize a dashboard for key monitoring metrics and drag them onto any positions on the UI. The Summary tab page supports automatic data update. For details, see Home Page.

                                                                    Cluster

                                                                    +

                                                                    Cluster

                                                                    Provides guidance on how to monitor, operate, and configure services in a cluster, helping you manage services in a unified manner. For details, see Cluster.

                                                                    +

                                                                    Provides guidance on how to monitor, operate, and configure services in a cluster, helping you manage services in a unified manner. For details, see Cluster.

                                                                    Host

                                                                    +

                                                                    Host

                                                                    Provides guidance on how to monitor and operate hosts, helping you manage hosts in a unified manner. For details, see Hosts.

                                                                    +

                                                                    Provides guidance on how to monitor and operate hosts, helping you manage hosts in a unified manner. For details, see Hosts.

                                                                    Operation

                                                                    +

                                                                    Operation

                                                                    Provides guidance on how to query and handle alarms, helping you identify and rectify product faults and potential risks in a timely manner to ensure smooth system running. For details, see O&M.

                                                                    +

                                                                    Provides guidance on how to query and handle alarms, helping you identify and rectify product faults and potential risks in a timely manner to ensure smooth system running. For details, see O&M.

                                                                    Audit

                                                                    +

                                                                    Audit

                                                                    Allows you to query and export audit logs, and view all user activities and operations. For details, see Audit.

                                                                    +

                                                                    Allows you to query and export audit logs, and view all user activities and operations. For details, see Audit.

                                                                    Tenant Resources

                                                                    +

                                                                    Tenant Resources

                                                                    Provides a unified tenant management platform. For details, see Tenant Resources.

                                                                    +

                                                                    Provides a unified tenant management platform. For details, see Tenant Resources.

                                                                    System

                                                                    +

                                                                    System

                                                                    Provides system management settings of MRS 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.
                                                                    Table 1 Maintenance and management operations

                                                                    UI Portal

                                                                    diff --git a/docs/mrs/umn/admin_guide_000012.html b/docs/mrs/umn/admin_guide_000012.html index aab19f08c..27c731cb2 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 MRS Manager.
                                                                    2. Choose Cluster > Name of the target cluster > Dashboard. On this tab page, choose More > Rolling-restart Service.

                                                                      For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from Manager. You can choose More in the upper right corner of the Homepage to access cluster maintenance and management functions.

                                                                      +

                                                                      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.

                                                                        For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from Manager. You can choose More in the upper right corner of the Homepage to access cluster maintenance and management functions.

                                                                      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

                                                                        diff --git a/docs/mrs/umn/admin_guide_000013.html b/docs/mrs/umn/admin_guide_000013.html index 98f8ee7ec..8cb94265f 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 MRS Manager.
                                                                        2. Choose Cluster > Name of the desired cluster > Dashboard.

                                                                          For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from Manager. You can choose More in the upper right corner of the Homepage to access cluster maintenance and management functions.

                                                                          +
                                                                          1. Log in to MRS Manager.
                                                                          2. Choose Cluster > Name of the desired cluster > Dashboard.

                                                                            For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from Manager. You can choose More in the upper right corner of the Homepage to access cluster maintenance and management functions.

                                                                          3. On this page, choose More > Synchronize Configuration.
                                                                          4. In the dialog box that is displayed, click OK.

                                                                          Restart configuration-expired instances.

                                                                          diff --git a/docs/mrs/umn/admin_guide_000014.html b/docs/mrs/umn/admin_guide_000014.html index a4f4c3f5d..e4403703e 100644 --- a/docs/mrs/umn/admin_guide_000014.html +++ b/docs/mrs/umn/admin_guide_000014.html @@ -3,14 +3,101 @@

                                                                          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 MRS Manager.
                                                                          2. Choose Cluster > Name of the desired cluster > Dashboard. On the page that is displayed, choose More > Download Client.

                                                                            For MRS 3.3.0 or later, the Cluster > Dashboard page has been removed from Manager.

                                                                            -
                                                                            -

                                                                            The Download Cluster Client dialog box is displayed.

                                                                            +

                                                                            Procedure

                                                                            1. Log in to MRS Manager.
                                                                            2. In the upper right corner of the home page, click Download Client.

                                                                              The Download Cluster Client dialog box is displayed.

                                                                            3. Select a client type for Select Client Type.

                                                                              • Complete Client: the package contains scripts, compilation files, and configuration files.
                                                                              • Configuration Files Only: the package contains only the client configuration files.

                                                                                This type is applicable to application development tasks. For example, after a complete client is downloaded and installed, the cluster administrator modifies the service configuration on MRS Manager, and developers need to update the client configuration files.

                                                                              Set Select Platform Type to x86_64 or aarch64. To run the client on x86 nodes, select x86_64; to tun the client on TaiShan nodes, select aarch64. By default, you should select a client that has the same architecture as your servers.

                                                                              -

                                                                            4. Determine whether to generate a client software package file on the cluster node.

                                                                              • If yes, select Save to Path and click OK to generate the client file.

                                                                                The generated file is stored in the /tmp/FusionInsight-Client directory on the active management node by default. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directory. If the client file already exists in the path, the existing client file will be replaced.

                                                                                +

                                                                              • Select the path for downloading the client file and set related parameters. Click OK. For MRS 3.5.0 and later versions, perform this step. For versions earlier than MRS 3.5.0, go to 5.

                                                                                • Server: Download the file to the active OMS node of the cluster.

                                                                                  The generated file is stored in the /tmp/FusionInsight-Client directory on the active OMS node by default. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directory. If the client file already exists in the path, the existing client file will be replaced.

                                                                                  +

                                                                                  When a cluster has many services installed, the cluster client file becomes quite large. Additionally, decompressing this file during installation can consume significant disk space. It's recommended to download the client files to a different directory that has ample space, or to promptly remove unnecessary files from the client download directory after installation. Doing so helps avoid exhausting the /tmp directory's disk space, which could interrupt the normal operation of the cluster nodes.

                                                                                  +
                                                                                  +

                                                                                  After the file is generated, copy the obtained package to another directory, for example, /opt/Bigdata/hadoopclient, as user omm or client installation user.

                                                                                  +
                                                                                • Browser: Download the file to the local computer.
                                                                                • Remote node: Download the file to a node other than the active OMS node. If you select this option, you need to set the following parameters: +
                                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                                  Table 1 Parameters

                                                                                  Parameter

                                                                                  +

                                                                                  Description

                                                                                  +

                                                                                  Example Value

                                                                                  +

                                                                                  Save to Path

                                                                                  +

                                                                                  Path for storing client files.

                                                                                  +

                                                                                  If there is already a client file in the path, it will be overwritten. For a remote node, write permission for the path is required.

                                                                                  +

                                                                                  /tmp/FusionInsight-Client-Remote/

                                                                                  +

                                                                                  Host IP Address

                                                                                  +

                                                                                  IP address of the remote node.

                                                                                  +
                                                                                  NOTE:

                                                                                  The platform type of the remote node must be the same as that of the downloaded client. Otherwise, the client may fail to be installed.

                                                                                  +
                                                                                  +

                                                                                  x.x.x.x

                                                                                  +

                                                                                  Host Port

                                                                                  +

                                                                                  Host port of the remote node.

                                                                                  +

                                                                                  22

                                                                                  +

                                                                                  Username

                                                                                  +

                                                                                  Username for logging in to the remote node.

                                                                                  +

                                                                                  For a remote node, write permission for the path is required.

                                                                                  +

                                                                                  xxx

                                                                                  +

                                                                                  Authentication Method

                                                                                  +

                                                                                  You can choose one of the following methods:

                                                                                  +
                                                                                  • Password: Use the password for login.
                                                                                  • SSH private keys: Use SSH private keys for login.
                                                                                  • None: To use this method, passwordless login needs to be enabled for the node.
                                                                                  +

                                                                                  Password

                                                                                  +

                                                                                  Password

                                                                                  +

                                                                                  This parameter is mandatory when Authentication Method is set to Password.

                                                                                  +

                                                                                  This parameter indicates the password used for login.

                                                                                  +

                                                                                  xxx

                                                                                  +

                                                                                  SSH Private Keys

                                                                                  +

                                                                                  This parameter is mandatory when Authentication Method is set to SSH private keys.

                                                                                  +

                                                                                  Click Select File and select a local file to upload.

                                                                                  +

                                                                                  -

                                                                                  +

                                                                                  Auto Deployment

                                                                                  +

                                                                                  Whether to enable auto deployment. This parameter is mandatory when Select Client Type is set to Complete Client.

                                                                                  +
                                                                                  • If you set this parameter to yes, the client is automatically installed and deployed on the current node.
                                                                                  • If you set this parameter to no, the client will not be automatically installed and deployed. You need to manually install the client after it is downloaded.
                                                                                  +

                                                                                  Yes

                                                                                  +

                                                                                  Deployment Path

                                                                                  +

                                                                                  This parameter is mandatory when Auto Deployment is set to Yes. If only the configuration file is downloaded, this parameter will not be displayed.

                                                                                  +

                                                                                  The deployment path must be empty if it already exists on the remote node. Otherwise, it will be created automatically. The path also requires operate and write permissions.

                                                                                  +

                                                                                  /opt/testclient

                                                                                  +
                                                                                  +
                                                                                  +
                                                                                +

                                                                              • Determine whether to generate a client software package file on the cluster node. For versions earlier than MRS 3.5.0, perform this step.

                                                                                • If yes, select Save to Path and click OK to generate the client file.

                                                                                  The generated file is stored in the /tmp/FusionInsight-Client directory on the active management node by default. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directory. If the client file already exists in the path, the existing client file will be replaced.

                                                                                  After the file is generated, copy the obtained package to another directory, for example, /opt/Bigdata/hadoopclient, as user omm or client installation user.

                                                                                • If no, click OK to download the client file to the local host.

                                                                                  The system starts to download the client software package.

                                                                                diff --git a/docs/mrs/umn/admin_guide_000022.html b/docs/mrs/umn/admin_guide_000022.html index 80f5b8860..f526c980d 100644 --- a/docs/mrs/umn/admin_guide_000022.html +++ b/docs/mrs/umn/admin_guide_000022.html @@ -9,14 +9,65 @@

                                                                            Add client information.

                                                                            1. To manually add information about an installed client, click Add and manually add the IP address, installation path, user, platform information, and registration information of the client as prompted.
                                                                            2. Configure the client information and click OK.
                                                                            +

                                                                            Install MRS patches in batches. (supported only by MRS 3.3.0 and later versions)

                                                                            +
                                                                            1. If a patch has been installed in the current cluster, select the clients on which the patch is to be installed on the Client Management page and choose More > Batch install patches. In the displayed dialog box, select "I accept the risk of possible service interruption during patch installation." Click OK to install the MRS patches on the selected client.

                                                                              During patch installation, clients cannot run properly and services on the clients may be interrupted.

                                                                              +
                                                                              +

                                                                            Modify client information.

                                                                            -
                                                                            1. Modify information about the manually registered client.

                                                                              On the Client Management page, select the target client and click Modify. After modifying the information, click OK.

                                                                              +
                                                                              1. Modify information about the manually registered client.

                                                                                On the Client Management page, select the target client and click Modify. After modifying the information, click OK.

                                                                                +

                                                                              +

                                                                              Update client information (available for MRS 3.5.0 and later versions).

                                                                              +
                                                                              1. If you modify service configuration parameters on Manager and restart the service, update the configuration of the installed client.

                                                                                • Updating a client: On the Client Management page, select the client you want to update and click Update in the Operation column. Select the checkbox for risk confirmation, configure the information in Table 1, and click OK.
                                                                                • Updating clients in batches: On the Client Management page, select the clients you want to update (the clients you selected must be installd by the same user), and choose More > Batch Update. Select the checkbox for risk confirmation, configure the information in Table 1, and click OK.
                                                                                +

                                                                                During configuration update, clients cannot run properly and services on the clients may be interrupted.

                                                                                +
                                                                                + +
                                                                                + + + + + + + + + + + + + + + + + + + + + +
                                                                                Table 1 Parameters for updating the client configuration

                                                                                Parameter

                                                                                +

                                                                                Description

                                                                                +

                                                                                Example Value

                                                                                +

                                                                                Authentication Method

                                                                                +

                                                                                You can choose one of the following methods:

                                                                                +
                                                                                • Password: Use the password for login.
                                                                                • SSH private keys: Use SSH private keys for login.
                                                                                • None: To use this method, passwordless login needs to be enabled.
                                                                                +

                                                                                Password

                                                                                +

                                                                                Password/SSH Private Keys

                                                                                +
                                                                                • This parameter is mandatory when Authentication Method is set to Password.
                                                                                • This parameter is mandatory when Authentication Method is set to SSH private keys. Click Select File and select a local file to upload.
                                                                                +

                                                                                xxx

                                                                                +

                                                                                Host Port

                                                                                +

                                                                                Host port of the node where the client is to be updated

                                                                                +

                                                                                22

                                                                                +

                                                                                Installation Package Path

                                                                                +

                                                                                Path for storing the installation package of the updated client

                                                                                +

                                                                                If there is already a client file in the path, it will be overwritten. For a remote node, write permission for the path is required.

                                                                                +

                                                                                /tmp/FusionInsight-Client/

                                                                                +
                                                                                +

                                                                              Delete client information.

                                                                              -
                                                                              1. On the Client Management page, select the target client and click Delete. In the displayed dialog box, click OK.

                                                                                To delete multiple clients, select the all of them and click Batch Delete. In the displayed dialog box, click OK.

                                                                                +
                                                                                1. On the Client Management page, select the target client and click Delete. In the displayed dialog box, click OK.

                                                                                  To delete multiple clients, select the all of them and click Batch Delete. In the displayed dialog box, click OK.

                                                                                Export client information.

                                                                                -
                                                                                1. On the Client Management page, click Export All to export information about all registered clients to the local PC.

                                                                                  On the Client Management page, only components that have clients are displayed in the component list. Therefore, some components that do not have clients and have special components are not displayed.

                                                                                  +
                                                                                  1. On the Client Management page, click Export All to export information about all registered clients to the local PC.

                                                                                    On the Client Management page, only components that have clients are displayed in the component list. Therefore, some components that do not have clients and have special components are not displayed.

                                                                                    The following components are not displayed:

                                                                                    LdapServer, KrbServer, DBService, Hue, MapReduce, and Flume

                                                                                    diff --git a/docs/mrs/umn/admin_guide_000040.html b/docs/mrs/umn/admin_guide_000040.html index b27f3b8ef..02f14507b 100644 --- a/docs/mrs/umn/admin_guide_000040.html +++ b/docs/mrs/umn/admin_guide_000040.html @@ -3,9 +3,12 @@

                                                                                    Decommissioning and Recommissioning an Instance

                                                                                    Scenario

                                                                                    Some role instances provide services for external services in distributed and parallel mode. Services independently store information about whether each instance can be used. Therefore, you need to use MRS Manager to recommission or decommission these instances to change the instance running status.

                                                                                    Some instances do not support the recommissioning and decommissioning functions.

                                                                                    -
                                                                                    The following roles support decommissioning and recommissioning: HDFS DataNode, YARN NodeManager, and HBase RegionServer.
                                                                                    • By default, if the number of the DataNodes is less than or equal to that of HDFS replicas, decommissioning cannot be performed. If the number of HDFS replicas is three and the number of DataNodes is less than four in the system, decommissioning cannot be performed. In this case, an error will be reported and force MRS Manager to exit the decommissioning 30 minutes after MRS Manager attempts to perform the decommissioning.
                                                                                    • You can enable quick decommissioning before decommissioning DataNodes for clusters of MRS 3.3.0 or later. In this case, when the number of DataNodes meets the value of dfs.namenode.decommission.force.replication.min, the system decommissions the nodes and adds HDFS copies at the same time. If data is written during quick decommissioning, data may be lost. Exercise caution when performing this operation. The parameters related to quick decommissioning are listed as follows. You can search for and view the parameters on the HDFS configuration page on FusionInsight Manager.

                                                                                      dfs.namenode.decommission.force.enabled: whether to enable quick decommissioning for DataNode. If this parameter is set to true, the function is enabled.

                                                                                      +
                                                                                      The following roles support decommissioning and recommissioning: HDFS DataNode, YARN NodeManager, and HBase RegionServer.
                                                                                      • By default, if the number of the DataNodes is less than or equal to that of HDFS replicas, decommissioning cannot be performed. If the number of HDFS replicas is three and the number of DataNodes is less than four in the system, decommissioning cannot be performed. In this case, an error will be reported and force MRS Manager to exit the decommissioning 30 minutes after MRS Manager attempts to perform the decommissioning.
                                                                                      • You can enable quick decommissioning before decommissioning DataNodes for clusters of MRS 3.3.0 or later. In this case, when the number of DataNodes meets the value of dfs.namenode.decommission.force.replication.min, the system decommissions the nodes and adds HDFS copies at the same time. If data is written during quick decommissioning, data may be lost. Exercise caution when performing this operation. The parameters related to quick decommissioning are listed as follows. You can search for and view the parameters on the HDFS configuration page on MRS Manager.

                                                                                        dfs.namenode.decommission.force.enabled: whether to enable quick decommissioning for DataNode. If this parameter is set to true, the function is enabled.

                                                                                        dfs.namenode.decommission.force.replication.min: minimum number of available copies of a block required for DataNode quick decommissioning. The value ranges from 1 to 3.

                                                                                        -
                                                                                      • During MapReduce task execution, files with 10 replicas are generated. Therefore, if the number of DataNode instances is less than 10, decommissioning cannot be performed.
                                                                                      • If the number of DataNode racks (the number of racks is determined by the number of racks configured for each DataNode) is greater than 1 before the decommissioning, and after some DataNodes are decommissioned, that of the remaining DataNodes changes to 1, the decommissioning will fail. Therefore, before decommissioning DataNode instances, you need to evaluate the impact of decommissioning on the number of racks to adjust the DataNodes to be decommissioned.
                                                                                      • If multiple DataNodes are decommissioned at the same time, and each of them stores a large volume of data, the DataNodes may fail to be decommissioned due to timeout. To avoid this problem, it is recommended that one DataNode be decommissioned each time and multiple decommissioning operations be performed.
                                                                                      +
                                                                                    • During MapReduce task execution, files with 10 replicas are generated. Therefore, if the number of DataNode instances is less than 10, decommissioning cannot be performed.
                                                                                    • If the number of DataNode racks (the number of racks is determined by the number of racks configured for each DataNode) is greater than 1 before the decommissioning, and after some DataNodes are decommissioned, that of the remaining DataNodes changes to 1, the decommissioning will fail. Therefore, before decommissioning DataNode instances, you need to evaluate the impact of decommissioning on the number of racks to adjust the DataNodes to be decommissioned.
                                                                                    • If multiple DataNodes are decommissioned at the same time, and each of them stores a large volume of data, the DataNodes may fail to be decommissioned due to timeout. To avoid this problem, it is recommended that one DataNode be decommissioned each time and multiple decommissioning operations be performed.
                                                                                    • During broker decommissioning, if the number of remaining brokers after decommissioning is less than the number of built-in topic replicas (3 by default) of the Kafka service, the broker cannot be decommissioned. If the instance is forcibly deleted, the service functions are unavailable. (The following broker constraints are added to MRS 3.5.0.)
                                                                                    • If multiple brokers are decommissioned at the same time and the data volume of the topic partitions maintained by each broker is large, the brokers may fail to be decommissioned due to timeout. To avoid this problem, you are advised to decommission only one broker each time.
                                                                                    • You can view the partition migration progress during broker decommissioning on the Kafka UI, and increase traffic limit to accelerate partition migration during off-peak hours. To avoid service interruption, you can reduce the partition migration traffic or cancel ongoing partition migration tasks.
                                                                                    • Do not delete topics during broker decommissioning. Otherwise, there will be residual metadata of the migration tasks.
                                                                                    • After adding a broker instance or recommissioning a broker, the system triggers partition balancing in 10 minutes. (You can use the auto.reassign.check.interval.ms parameter of the Kafka component on Manager to adjust the trigger time.)
                                                                                    • Decommissioning or recommissioning constraints for Doris BE nodes
                                                                                      • After decommissioning, the remaining normal BE nodes must be no less than the copies of any table. Otherwise, decommissioning will fail.
                                                                                      +
                                                                                      • BE node storage space

                                                                                        Before cluster decommissioning, the disk space of non-decommissioned BE nodes in the cluster must be enough to store data of all BE nodes to be decommissioned. About 10% of the storage space of each non-decommissioned BE node must be reserved after decommissioning to ensure that the remaining instances can run properly.

                                                                                        +
                                                                                      +
                                                                                    diff --git a/docs/mrs/umn/admin_guide_000071.html b/docs/mrs/umn/admin_guide_000071.html index 8b0cb15df..c002ee0ef 100644 --- a/docs/mrs/umn/admin_guide_000071.html +++ b/docs/mrs/umn/admin_guide_000071.html @@ -72,7 +72,7 @@

                                                                                  Monitoring Metric Reference

                                                                                  MRS Manager alarm monitoring metrics are classified as node information metrics and cluster service metrics. Table 2 describes the metrics for which you can configure thresholds on nodes.

                                                                                  -

                                                                                  On FusionInsight Manager of MRS 3.3.0 or later, alarms of some components can be reported by severity. Each alarm severity has a threshold. You can view them on the FusionInsight Manager configuration page.

                                                                                  +

                                                                                  On MRS Manager of MRS 3.3.0 or later, alarms of some components can be reported by severity. Each alarm severity has a threshold. You can view them on the MRS Manager configuration page.

                                                                                  - @@ -110,7 +110,7 @@

                                                                                2. Check whether the current tenant needs to be associated with resources of other services.

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

                                                                                3. Click Associate Service to configure other service resources used by the current tenant, and click OK.

                                                                                  • Set Service to HBase and Association Type to Exclusive or Shared.
                                                                                    • Exclusive indicates that the service resources are used by the tenant exclusively and cannot be associated with other tenants.
                                                                                    • Shared indicates that the service resources can be shared with other tenants.
                                                                                    -
                                                                                  • MRS 3.2.0 or later: Set Service to ClickHouse.
                                                                                    • Association Type: When Service is set to ClickHouse, Association Type can only be set to Shared. MRS 3.3.0 and later versions support Exclusive and Shared.
                                                                                    • Associate Logical Cluster: If the logical cluster function is not enabled for ClickHouse, default_cluster is selected by default. If the function is enabled, select the logical cluster to which you want to associate.
                                                                                    • CPU Priority: The CPU priority ranges from –20 to 19. This value is associated with the NICE value of the OS. A smaller value indicates a higher CPU priority.
                                                                                    • Memory: The maximum value of this parameter is 100, in percentage. For example, if this parameter is set to 80, the total memory that can be used by the current tenant is calculated as follows: Available memory x 80%.
                                                                                    • Concurrency: The maximum number of concurrent resources available for all the users bound to the tenant. This parameter is required for clusters of MRS 3.3.0 or later.
                                                                                    +
                                                                                  • MRS 3.2.0 or later: Set Service to ClickHouse.
                                                                                    • Association Type: When Service is set to ClickHouse, Association Type can only be set to Shared. MRS 3.3.0 and later versions support Exclusive and Shared.
                                                                                    • Associate Logical Cluster: If the logical cluster function is not enabled for ClickHouse, default_cluster is selected by default. If the function is enabled, select the logical cluster to which you want to associate.
                                                                                    • CPU Priority: The CPU priority ranges from –20 to 19. This value is associated with the NICE value of the OS. A smaller value indicates a higher CPU priority.
                                                                                    • Memory: The maximum value of this parameter is 100, in percentage. For example, if this parameter is set to 80, the total memory that can be used by the current tenant is calculated as follows: Available memory x 80%.
                                                                                    • Concurrency: The maximum number of concurrent resources available for all the users bound to the tenant. This parameter is required for clusters of MRS 3.3.0 or later.
                                                                                  • Only HBase can be associated with a new tenant. However, HDFS, HBase, and Yarn can be associated with existing tenants.
                                                                                  • To associate an existing tenant with service resources, click the target tenant in the tenant list, switch to the Service Associations page, and click Associate Service to configure resources to be associated with the tenant.
                                                                                  • To disassociate an existing tenant from service resources, click the target tenant in the tenant list, switch to the Service Associations page, and click Delete in the Operation column. In the displayed dialog box, select I have read the information and understand the impact and click OK.
                                                                                  diff --git a/docs/mrs/umn/admin_guide_000109.html b/docs/mrs/umn/admin_guide_000109.html index 8820e3e79..120b2b526 100644 --- a/docs/mrs/umn/admin_guide_000109.html +++ b/docs/mrs/umn/admin_guide_000109.html @@ -4,7 +4,7 @@

                                                                                  Scenario

                                                                                  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 pool on MRS Manager and add the hosts that have not been added to any custom resource pools to this resource pool so that specified queues can use the computing resources provided by these hosts.

                                                                                  The system contains a default resource pool by default. All NodeManagers that are not added to custom resource pools belong to this resource pool.

                                                                                  -

                                                                                  Procedure

                                                                                  1. Log in to MRS Manager.
                                                                                  2. Choose Tenant Resources > Resource Pool.
                                                                                  3. Click Add Resource Pool.
                                                                                  4. Set resource pool attributes.

                                                                                    • Cluster: Select the cluster to which the resource pool is to be added. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)
                                                                                    • Name: Enter the name of the resource pool. The name contains 1 to 50 characters, including digits, letters, and underscores (_), and cannot start with an underscore (_).
                                                                                    • Resource Label: Enter the resource label of the resource pool. The value can contain 1 to 50 characters, including digits, letters, underscores (_), and hyphens (-), and must start with a digit or letter.
                                                                                    • Resource: In the Available Hosts area, select specified hosts and click to add the hosts to the Selected Hosts area. Only hosts in the cluster can be selected. The host list in the resource pool can be left blank.

                                                                                      You can filter hosts by host name, number of CPU cores, memory, operating system, or platform type based on service requirements.

                                                                                      +

                                                                                      Procedure

                                                                                      1. Log in to MRS Manager.
                                                                                      2. Choose Tenant Resources > Resource Pool.
                                                                                      3. Click Add Resource Pool.
                                                                                      4. Set resource pool attributes.

                                                                                        • Cluster: Select the cluster to which the resource pool is to be added. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)
                                                                                        • Name: Enter the name of the resource pool. The name contains 1 to 50 characters, including digits, letters, and underscores (_), and cannot start with an underscore (_).
                                                                                        • Resource Label: Enter the resource label of the resource pool. The value can contain 1 to 50 characters, including digits, letters, underscores (_), and hyphens (-), and must start with a digit or letter.
                                                                                        • Resource: In the Available Hosts area, select specified hosts and click to add the hosts to the Selected Hosts area. Only hosts in the cluster can be selected. The host list in the resource pool can be left blank.

                                                                                          You can filter hosts by host name, number of CPU cores, memory, operating system, or platform type based on service requirements.

                                                                                      5. Click OK.

                                                                                        After the resource pool is created, you can view its name, members, and mode in the resource pool list. Hosts that are added to the custom resource pool are no longer members of the default resource pool.

                                                                                        diff --git a/docs/mrs/umn/admin_guide_000110.html b/docs/mrs/umn/admin_guide_000110.html index 8003c23bc..4823ade12 100644 --- a/docs/mrs/umn/admin_guide_000110.html +++ b/docs/mrs/umn/admin_guide_000110.html @@ -3,7 +3,7 @@

                                                                                        Modifying a Resource Pool

                                                                                        Scenario

                                                                                        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.

                                                                                        -

                                                                                        Procedure

                                                                                        1. Log in to MRS Manager.
                                                                                        2. Choose Tenant Resources > Resource Pool.
                                                                                        3. Locate the row that contains the specified resource pool, and click Edit in the Operation column (for MRS 3.3.0 or later, click Modify).
                                                                                        4. In the Resource area, modify hosts.

                                                                                          • Adding hosts: Select desired hosts in Available Hosts and click to add them to the resource pool.
                                                                                          • Deleting hosts: Select desired hosts in Selected Hosts and click to remove them from the resource pool. The host list in the resource pool can be left blank.
                                                                                          +

                                                                                          Procedure

                                                                                          1. Log in to MRS Manager.
                                                                                          2. Choose Tenant Resources > Resource Pool.
                                                                                          3. Locate the row that contains the specified resource pool, and click Edit in the Operation column (for MRS 3.3.0 or later, click Modify).
                                                                                          4. In the Resource area, modify hosts.

                                                                                            • Adding hosts: Select desired hosts in Available Hosts and click to add them to the resource pool.
                                                                                            • Deleting hosts: Select desired hosts in Selected Hosts and click to remove them from the resource pool. The host list in the resource pool can be left blank.

                                                                                          5. Click OK.
                                                                                        diff --git a/docs/mrs/umn/admin_guide_000113.html b/docs/mrs/umn/admin_guide_000113.html index 35bf16889..5d6ae927e 100644 --- a/docs/mrs/umn/admin_guide_000113.html +++ b/docs/mrs/umn/admin_guide_000113.html @@ -10,7 +10,7 @@

                                                                                        Procedure

                                                                                        1. On MRS Manager, choose Tenant Resources.
                                                                                        2. Choose Dynamic Resource Plan.
                                                                                        3. Click the Resource Distribution Policy tab.
                                                                                        4. Select the name of the target cluster from Cluster and select a resource pool from Resource Pool.
                                                                                        5. Locate the row that contains the target queue in the Resource Allocation area, and click Modify in the Operation column.
                                                                                        6. On the Resource Configuration Policy tab of the Modify Resource Allocation window, set the resource configuration policy of the queue in the resource pool.

                                                                                          • Weight: indicates the resources that a tenant can obtain. Its initial value is the same as the minimum resource percentage.
                                                                                          • Minimum Resource: indicates the minimum resources that a tenant can obtain.
                                                                                          • Maximum Resource: indicates the maximum resources that a tenant can obtain.
                                                                                          • Reserved Resource: indicates the resources that are reserved for the tenant's queues and cannot be lent to other tenants' queues.

                                                                                        7. Click the User Policy tab in the Modify Resource Allocation window and set the user policy.

                                                                                          defaultUser(built-in) indicates that the policy specified for defaultUser is used if a user does not have a policy. The default policy cannot be deleted.

                                                                                          -
                                                                                          • Click Add User Policy to add a user policy.
                                                                                            • Username: indicates the name of a user.
                                                                                            • Weight: indicates the resources that the user can obtain.
                                                                                            • Max vCores: indicates the maximum number of virtual cores that the user can obtain.
                                                                                            • Max Memory(MB): indicates the maximum memory that the user can obtain.
                                                                                            +
                                                                                            • Click Add User Policy to add a user policy.
                                                                                              • Username: indicates the name of a user.
                                                                                              • Priority: When task queues need to compete for resources, a queue with a higher priority obtains resources first. However, not all containers can be started. (This parameter is displayed for MRS 3.5.0 and later versions only.)
                                                                                              • Max vCores: indicates the maximum number of virtual cores that the user can obtain.
                                                                                              • Max Memory(MB): indicates the maximum memory that the user can obtain.
                                                                                            • Click Modify in the Operation column to modify an existing user policy.
                                                                                            • Click Clear in the Operation column to delete an existing user policy.

                                                                                          • Click OK.
                                                                                        diff --git a/docs/mrs/umn/admin_guide_000115.html b/docs/mrs/umn/admin_guide_000115.html index bdb1402d9..08b3be9bc 100644 --- a/docs/mrs/umn/admin_guide_000115.html +++ b/docs/mrs/umn/admin_guide_000115.html @@ -6,7 +6,7 @@

                                                                                        Procedure

                                                                                        • Add a policy.
                                                                                          1. On MRS Manager, choose Tenant Resources.
                                                                                          2. Choose Dynamic Resource Plan.
                                                                                          3. Click the Global User Policy tab.

                                                                                            defaults(default setting) indicates that the policy specified for defaults is used if a user does not have a global policy. The default policy cannot be deleted.

                                                                                            -
                                                                                          4. Click Create Global User Policy. In the displayed dialog box, set the following parameters:
                                                                                            • Cluster: Select the target cluster. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)
                                                                                            • Username: indicates the user for whom resource scheduling is controlled. Enter an existing username in the current cluster.
                                                                                            • Max Running Apps: indicates the maximum number of tasks that the user can run in the current cluster.
                                                                                            • Max Pending Apps: indicates the maximum number of tasks that the user can suspend in the current cluster.
                                                                                            • Default Queue: indicates the queue of the user. Enter the name of an existing queue in the current cluster.
                                                                                            +
                                                                                          5. Click Create Global User Policy. In the displayed dialog box, set the following parameters:
                                                                                            • Cluster: Select the target cluster. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)
                                                                                            • Username: indicates the user for whom resource scheduling is controlled. Enter an existing username in the current cluster.
                                                                                            • Max Running Apps: indicates the maximum number of tasks that the user can run in the current cluster.
                                                                                            • Max Pending Apps: indicates the maximum number of tasks that the user can suspend in the current cluster.
                                                                                            • Default Queue: indicates the queue of the user. Enter the name of an existing queue in the current cluster.
                                                                                        • Modify a policy.
                                                                                          1. On MRS Manager, choose Tenant Resources.
                                                                                          2. Choose Dynamic Resource Plan.
                                                                                          3. Click the Global User Policy tab.
                                                                                          4. In the row that contains the desired user policy, click Modify in the Operation column.
                                                                                          5. In the displayed dialog box, modify parameters and click OK.
                                                                                          diff --git a/docs/mrs/umn/admin_guide_000118.html b/docs/mrs/umn/admin_guide_000118.html index 113c2a76e..ba4253335 100644 --- a/docs/mrs/umn/admin_guide_000118.html +++ b/docs/mrs/umn/admin_guide_000118.html @@ -14,7 +14,7 @@
                                                                                  4. - diff --git a/docs/mrs/umn/admin_guide_000127.html b/docs/mrs/umn/admin_guide_000127.html index 9b47b43b2..b3bbf888a 100644 --- a/docs/mrs/umn/admin_guide_000127.html +++ b/docs/mrs/umn/admin_guide_000127.html @@ -4,7 +4,7 @@

                                                                                  Scenario

                                                                                  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 pool on MRS Manager and add the hosts that have not been added to any custom resource pools to this resource pool so that specified queues can use the computing resources provided by these hosts.

                                                                                  The system contains a default resource pool by default. All NodeManagers that are not added to custom resource pools belong to this resource pool.

                                                                                  -

                                                                                  Procedure

                                                                                  1. Log in to MRS Manager.
                                                                                  2. Choose Tenant Resources > Resource Pool.
                                                                                  3. Click Add Resource Pool.
                                                                                  4. Set resource pool attributes.

                                                                                    • Cluster: Select the cluster to which the resource pool is to be added. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)
                                                                                    • Name: Enter the name of the resource pool. The name contains 1 to 50 characters, including digits, letters, and underscores (_), and cannot start with an underscore (_).
                                                                                    • Resource Label: Enter the resource label of the resource pool. The value can contain 1 to 50 characters, including digits, letters, underscores (_), and hyphens (-), and must start with a digit or letter.
                                                                                    • Resource: In the Available Hosts area, select specified hosts and click to add the hosts to the Selected Hosts area. Only hosts in the cluster can be selected. The host list in the resource pool can be left blank.

                                                                                      You can filter hosts by host name, number of CPU cores, memory, operating system, or platform type based on service requirements.

                                                                                      +

                                                                                      Procedure

                                                                                      1. Log in to MRS Manager.
                                                                                      2. Choose Tenant Resources > Resource Pool.
                                                                                      3. Click Add Resource Pool.
                                                                                      4. Set resource pool attributes.

                                                                                        • Cluster: Select the cluster to which the resource pool is to be added. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)
                                                                                        • Name: Enter the name of the resource pool. The name contains 1 to 50 characters, including digits, letters, and underscores (_), and cannot start with an underscore (_).
                                                                                        • Resource Label: Enter the resource label of the resource pool. The value can contain 1 to 50 characters, including digits, letters, underscores (_), and hyphens (-), and must start with a digit or letter.
                                                                                        • Resource: In the Available Hosts area, select specified hosts and click to add the hosts to the Selected Hosts area. Only hosts in the cluster can be selected. The host list in the resource pool can be left blank.

                                                                                          You can filter hosts by host name, number of CPU cores, memory, operating system, or platform type based on service requirements.

                                                                                      5. Click OK.

                                                                                        After the resource pool is created, you can view its name, members, and mode in the resource pool list. Hosts that are added to the custom resource pool are no longer members of the default resource pool.

                                                                                        diff --git a/docs/mrs/umn/admin_guide_000128.html b/docs/mrs/umn/admin_guide_000128.html index 9b04b66c8..fd6ce5e26 100644 --- a/docs/mrs/umn/admin_guide_000128.html +++ b/docs/mrs/umn/admin_guide_000128.html @@ -3,7 +3,7 @@

                                                                                        Modifying a Resource Pool

                                                                                        Scenario

                                                                                        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.

                                                                                        -

                                                                                        Procedure

                                                                                        1. Log in to MRS Manager.
                                                                                        2. Choose Tenant Resources > Resource Pool.
                                                                                        3. Locate the row that contains the specified resource pool, and click Edit in the Operation column (for MRS 3.3.0 or later, click Modify).
                                                                                        4. In the Resource area, modify hosts.

                                                                                          • Adding hosts: Select desired hosts in Available Hosts and click to add them to the resource pool.
                                                                                          • Deleting hosts: Select desired hosts in Selected Hosts and click to remove them from the resource pool. The host list in the resource pool can be left blank.
                                                                                          +

                                                                                          Procedure

                                                                                          1. Log in to MRS Manager.
                                                                                          2. Choose Tenant Resources > Resource Pool.
                                                                                          3. Locate the row that contains the specified resource pool, and click Edit in the Operation column (for MRS 3.3.0 or later, click Modify).
                                                                                          4. In the Resource area, modify hosts.

                                                                                            • Adding hosts: Select desired hosts in Available Hosts and click to add them to the resource pool.
                                                                                            • Deleting hosts: Select desired hosts in Selected Hosts and click to remove them from the resource pool. The host list in the resource pool can be left blank.

                                                                                          5. Click OK.
                                                                                        diff --git a/docs/mrs/umn/admin_guide_000133.html b/docs/mrs/umn/admin_guide_000133.html index dc0fbc5ff..c429af667 100644 --- a/docs/mrs/umn/admin_guide_000133.html +++ b/docs/mrs/umn/admin_guide_000133.html @@ -11,24 +11,24 @@
                                                                                        Impact on the system
                                                                                        • Because the ResourceManager is restarted during scheduler switching, submitting jobs to Yarn will fail at that time.
                                                                                        • After the scheduler is switched, the parameters of the scheduler that takes over the workload are used.

                                                                                        Procedure

                                                                                        -
                                                                                        1. Log in to FusionInsight Manager. Choose Cluster > Services > Yarn and check whether the Yarn service status is normal. If the service is abnormal, restore the service.
                                                                                        2. Log in to the active management node as user omm.
                                                                                        3. Switch the scheduler.

                                                                                          • Run the following command to switch from the Capacity scheduler to the Superior scheduler:

                                                                                            sh ${BIGDATA_HOME}/om-server/om/sbin/cleanSwitchScheduler.sh 1

                                                                                            +
                                                                                            1. Log in to MRS Manager. Choose Cluster > Services > Yarn and check whether the Yarn service status is normal. If the service is abnormal, restore the service.
                                                                                            2. Log in to the active management node as user omm.
                                                                                            3. Switch the scheduler.

                                                                                              • Run the following command to switch from the Capacity scheduler to the Superior scheduler:

                                                                                                sh ${BIGDATA_HOME}/om-server/om/sbin/cleanSwitchScheduler.sh 1

                                                                                                If information similar to the following is displayed, the switch is successful:

                                                                                                -
                                                                                                Will change scheduler type to SUPERIOR
-Start to delete all tenant resource.  
-End to delete all tenant resource.  
-Start to delete all resource pool.  
-End to delete all resource pool.  
-...  
-End to switch scheduler by reset.
                                                                                                +
                                                                                                Will change scheduler type to SUPERIOR
+Start to delete all tenant resource.  
+End to delete all tenant resource.  
+Start to delete all resource pool.  
+End to delete all resource pool.  
+...  
+End to switch scheduler by reset.
                                                                                              • Run the following command to switch from the Capacity scheduler to the Superior scheduler:

                                                                                                sh ${BIGDATA_HOME}/om-server/om/sbin/cleanSwitchScheduler.sh 0

                                                                                                If information similar to the following is displayed, the switch is successful:

                                                                                                -
                                                                                                Will change scheduler type to CAPACITY  
-Start to delete all tenant resource.  
-End to delete all tenant resource.  
-Start to delete all resource pool.  
-End to delete all resource pool.  
-...  
-End to switch scheduler by reset.
                                                                                                +
                                                                                                Will change scheduler type to CAPACITY  
+Start to delete all tenant resource.  
+End to delete all tenant resource.  
+Start to delete all resource pool.  
+End to delete all resource pool.  
+...  
+End to switch scheduler by reset.

                                                                                              You can query the scheduler switching logs on the active management node.

                                                                                              • ${BIGDATA_LOG_HOME}/controller/aos/clean_switch_scheduler.log
                                                                                              • ${BIGDATA_LOG_HOME}/controller/aos/aos.log
                                                                                              • ${BIGDATA_LOG_HOME}/controller/aos/plugin.log
                                                                                              diff --git a/docs/mrs/umn/admin_guide_000145.html b/docs/mrs/umn/admin_guide_000145.html index 36534917f..07d73872d 100644 --- a/docs/mrs/umn/admin_guide_000145.html +++ b/docs/mrs/umn/admin_guide_000145.html @@ -7,9 +7,71 @@

                                                                                              Prerequisites

                                                                                              Before downloading the keytab file of a Human-Machine user, the password of the user must be changed at least once on the Manager portal or a client; otherwise, the downloaded keytab file cannot be used For details, see Changing a User Password.

                                                                                              -

                                                                                              Procedure

                                                                                              1. Log in to MRS Manager.
                                                                                              2. Choose System > Permission > User.
                                                                                              3. Locate the row that contains the user whose keytab file needs to be exported, choose More > Download Authentication Credential, specify the save path after the file is automatically generated, and keep the file properly.

                                                                                                The authentication credential includes the krb5.conf file of the Kerberos service.

                                                                                                -

                                                                                                After the authentication credential file is decompressed, you can obtain the following two files:

                                                                                                -
                                                                                                • The krb5.conf file contains the authentication service connection information.
                                                                                                • The user.keytab file contains user authentication information.
                                                                                                +

                                                                                                Procedure

                                                                                                1. Log in to MRS Manager.
                                                                                                2. Choose System > Permission > User.
                                                                                                3. Locate the row that contains the target user, and choose More > Download Authentication Credential.
                                                                                                4. Select a location for downloading the authentication credential and set related parameters. This operation is supported only in MRS 3.5.0 and later versions.

                                                                                                  If the credential is downloaded to the server or a remote node, delete it after using it to prevent leakage.

                                                                                                  +
                                                                                                  • Browser: Download the file to the local computer.
                                                                                                  • Server: Download the file to the active OMS node of the cluster.

                                                                                                    The generated file is stored in the /tmp/FusionInsight-Keytab/ directory on the active OMS node by default. If the path does not exist, it will be created. If the path already has an authentication credential file, the existing authentication credential file will be overwritten. For user omm, write permission for the path is required.

                                                                                                    +

                                                                                                    After the file is generated, copy the downloaded package to another directory as the omm user.

                                                                                                    +
                                                                                                  • Remote node: Download the file to a node other than the active OMS node. If you select this option, you need to set the following parameters: +
                                                                                  Table 2 Node monitoring metrics

                                                                                  Metric Group

                                                                                  diff --git a/docs/mrs/umn/admin_guide_000072.html b/docs/mrs/umn/admin_guide_000072.html index b5e982294..8fb341366 100644 --- a/docs/mrs/umn/admin_guide_000072.html +++ b/docs/mrs/umn/admin_guide_000072.html @@ -1,11 +1,10 @@

                                                                                  Configuring the Alarm Masking Status

                                                                                  -

                                                                                  Scenario

                                                                                  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 masked.
                                                                                  • When a third-party product is integrated with MRS, some alarms of the product are duplicated with the alarms of MRS and need to be masked.
                                                                                  • When the deployment environment is special, certain alarms may be falsely reported and need to be masked.
                                                                                  -

                                                                                  After an alarm is masked, new alarms with the same ID as the alarm are neither displayed on the Alarm page nor counted. The reported alarms are still displayed.

                                                                                  -
                                                                                  -

                                                                                  Procedure

                                                                                  1. Log in to MRS Manager.
                                                                                  2. Choose O&M > Alarm > Masking Setting.
                                                                                  3. In the Masking Setting area, select the specified service or module.
                                                                                  4. Select an alarm from the alarm list.

                                                                                    Figure 1 Masking an alarm
                                                                                    +

                                                                                    Masking an Alarm

                                                                                    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 masked.
                                                                                    • When a third-party product is integrated with MRS, some alarms of the product are duplicated with the alarms of MRS and need to be masked.
                                                                                    • When the deployment environment is special, certain alarms may be falsely reported and need to be masked.
                                                                                    +

                                                                                    After an alarm is masked, new alarms with the same ID as the alarm are neither displayed on the Alarm page nor counted. The reported alarms are still displayed.

                                                                                    +
                                                                                    1. Log in to MRS Manager.
                                                                                    2. Choose O&M > Alarm > Masking Setting.
                                                                                    3. In the Masking Setting area, select the specified service or module.
                                                                                    4. Select an alarm from the alarm list.

                                                                                      Figure 1 Masking an alarm
                                                                                      The information about the alarm is displayed, including the alarm name, ID, severity, masking status, and operations can be performed on the alarm.
                                                                                      • The masking status includes Display and Masking.
                                                                                      • Operations include Masking and Help.

                                                                                      You can filter specified alarms based on the masking status and alarm severity.

                                                                                      @@ -13,6 +12,26 @@

                                                                                    5. Set the masking status for an alarm:

                                                                                      • Click Masking. In the displayed dialog box, click OK to change the alarm masking status to Masking.
                                                                                      • Click Cancel Masking. In the dialog box that is displayed, click OK to change the masking status of the alarm to Display.

                                                                                    +

                                                                                    Configuring Alarm Masking and Alarm Trigger Count

                                                                                    This operation is available in clusters of MRS 3.5.0 or later only.

                                                                                    +
                                                                                    +

                                                                                    The MRS allows you to mask alarms and number of trigger times on the background. If the number of alarm report times is less than or equal to the number of alarm trigger times, no alarm will be reported.

                                                                                    +
                                                                                    1. Log in to the active OMS node as user omm using PuTTY.
                                                                                    2. Run the following command to modify the alarm_filter_config.json configuration file. If the file does not exist, create it.

                                                                                      vi $BIGDATA_HOME/om-server/OMS/workspace/conf/fms/alarm_filter_config.json

                                                                                      +

                                                                                    3. Configure or add parameters based on service demands.

                                                                                      • Alarm ID: ID of the alarm to be masked, for example, 12016.
                                                                                      • is_filtered: Whether to mask the alarm. true indicates that the alarm is masked and not reported. false indicates that the alarm is reported after certain times of trigger.
                                                                                      • smoothing_times: trigger count. If the number of alarm trigger times is less than or equal to the value of this parameter, no alarm will be reported. The value is an integer greater than 0.
                                                                                      +

                                                                                      The is_filtered parameter takes priority over the smoothing_times parameter.

                                                                                      +

                                                                                      For example, if the configuration is as follows, alarm 12016 is masked and alarm 12017 is reported after it is triggered for more than three times:

                                                                                      +
                                                                                      { 
+  "12016": { 
+    "is_filtered": true, 
+    "smoothing_times": 1 
+  }, 
+  "12017": { 
+    "is_filtered": false, 
+    "smoothing_times": 3 
+  } 
+}
                                                                                      +

                                                                                    4. Restart the FMS service on the active OMS node as user omm to apply the configuration.

                                                                                      sh $BIGDATA_HOME/om-server/OMS/workspace/bin/omm_s_fm_ctl.sh restart

                                                                                      +

                                                                                    5. Log in to the active OMS node as user omm using PuTTY. Perform steps 2 and 3.
                                                                                    +
                                                                                    diff --git a/docs/mrs/umn/admin_guide_000101.html b/docs/mrs/umn/admin_guide_000101.html index d6cc8b5f2..f3ba37e98 100644 --- a/docs/mrs/umn/admin_guide_000101.html +++ b/docs/mrs/umn/admin_guide_000101.html @@ -14,7 +14,7 @@

                                                                                  Cluster

                                                                                  Indicates the cluster for which you want to create a tenant. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)

                                                                                  +

                                                                                  Indicates the cluster for which you want to create a tenant. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)

                                                                                  Name

                                                                                  @@ -25,7 +25,7 @@

                                                                                  Tenant Resource Type

                                                                                  Specifies whether the tenant is a leaf tenant.

                                                                                  -
                                                                                  • When Leaf Tenant Resource is selected, the current tenant is a leaf tenant and no sub-tenant can be added.
                                                                                  • When Non-leaf Tenant Resource is selected, the current tenant is not a leaf tenant and sub-tenants can be added to the current tenant.
                                                                                    NOTE:

                                                                                    MRS 3.2.0 or later: If you select ClickHouse for Service, this parameter can only be set to Leaf Tenant.

                                                                                    +
                                                                                    • When Leaf Tenant Resource is selected, the current tenant is a leaf tenant and no sub-tenant can be added.
                                                                                    • When Non-leaf Tenant Resource is selected, the current tenant is not a leaf tenant and sub-tenants can be added to the current tenant.
                                                                                      NOTE:

                                                                                      MRS 3.2.0 or later: If you select ClickHouse for Service, this parameter can only be set to Leaf Tenant.

                                                                                  Cluster

                                                                                  Indicates the cluster for which you want to create a tenant. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)

                                                                                  +

                                                                                  Indicates the cluster for which you want to create a tenant. (This parameter is unavailable for clusters of MRS 3.3.0 or later.)

                                                                                  Name

                                                                                  @@ -25,7 +25,7 @@

                                                                                  Tenant Resource Type

                                                                                  Specifies whether the tenant is a leaf tenant.

                                                                                  -
                                                                                  • When Leaf Tenant Resource is selected, the current tenant is a leaf tenant and no sub-tenant can be added.
                                                                                  • When Non-leaf Tenant Resource is selected, the current tenant is not a leaf tenant and sub-tenants can be added to the current tenant.
                                                                                    NOTE:

                                                                                    MRS 3.2.0 or later: If you select ClickHouse for Service, this parameter can only be set to Leaf Tenant.

                                                                                    +
                                                                                    • When Leaf Tenant Resource is selected, the current tenant is a leaf tenant and no sub-tenant can be added.
                                                                                    • When Non-leaf Tenant Resource is selected, the current tenant is not a leaf tenant and sub-tenants can be added to the current tenant.
                                                                                      NOTE:

                                                                                      MRS 3.2.0 or later: If you select ClickHouse for Service, this parameter can only be set to Leaf Tenant.

                                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                                  Table 1 Parameters

                                                                                  Parameter

                                                                                  +

                                                                                  Description

                                                                                  +

                                                                                  Example Value

                                                                                  +

                                                                                  Save to Path

                                                                                  +

                                                                                  Path for storing the authentication credential file.

                                                                                  +

                                                                                  If there is already a credential file in the path, it will be overwritten. For a remote node, write permission for the path is required.

                                                                                  +

                                                                                  /tmp/FusionInsight-Keytab-Remote/

                                                                                  +

                                                                                  Host IP Address

                                                                                  +

                                                                                  IP address of the remote node.

                                                                                  +

                                                                                  x.x.x.x

                                                                                  +

                                                                                  Host Port

                                                                                  +

                                                                                  Host port of the remote node.

                                                                                  +

                                                                                  22

                                                                                  +

                                                                                  Username

                                                                                  +

                                                                                  Username for logging in to the remote node.

                                                                                  +

                                                                                  For a remote node, write permission for the path is required.

                                                                                  +

                                                                                  xxx

                                                                                  +

                                                                                  Authentication Method

                                                                                  +

                                                                                  You can choose one of the following methods:

                                                                                  +
                                                                                  • Password: Use the password for login.
                                                                                  • None: To use this method, passwordless login needs to be enabled.
                                                                                  +

                                                                                  Password

                                                                                  +

                                                                                  Password

                                                                                  +

                                                                                  This parameter is mandatory when Authentication Method is set to Password.

                                                                                  +

                                                                                  This parameter indicates the password used for login.

                                                                                  +

                                                                                  xxx

                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  4. +

                                                                                4. Click OK. After the file is automatically generated, specify the save path and keep the file properly.

                                                                                  The authentication credential includes the krb5.conf file of the Kerberos service.

                                                                                  +

                                                                                  After the authentication credential file is decompressed, you can obtain the following two files:

                                                                                  +
                                                                                  • The krb5.conf file contains the authentication service connection information.
                                                                                  • The user.keytab file contains user authentication information.

                                                                          diff --git a/docs/mrs/umn/admin_guide_000148.html b/docs/mrs/umn/admin_guide_000148.html index ea8ebe948..3c48aa6ca 100644 --- a/docs/mrs/umn/admin_guide_000148.html +++ b/docs/mrs/umn/admin_guide_000148.html @@ -22,9 +22,9 @@

                                                                          Task Example (Creating a Manager Role)

                                                                          1. Choose System > Permission > Role.
                                                                          2. On the displayed page, click Create Role and fill in Role Name and Description.
                                                                          3. In the Configure Resource Permission area, click Manager and set permissions for the role.

                                                                            Manager permissions:

                                                                            • Cluster
                                                                              • view permission: permission to view information on the Cluster page and view alarms and events under O&M > Alarm.
                                                                              • management permission: permission for management on the Cluster and O&M pages.
                                                                            • User
                                                                              • view permission: permission to view information on pages under System > Permission.
                                                                              • management permission: permission for management on pages under System > Permission.
                                                                              -
                                                                            • Audit

                                                                              management permission: permission for management on the Audit page.

                                                                              -
                                                                            • Tenant

                                                                              management permission: permission for management on the Tenant page and permission to view alarms and events under O&M > Alarm.

                                                                              -
                                                                            • System

                                                                              management permission: permission for management on all pages except those under Permission on the System page and permission to view alarms and events under O&M > Alarm.

                                                                              +
                                                                            • Audit

                                                                              management permission: permission for management on the Audit page.

                                                                              +
                                                                            • Tenant
                                                                              • view permission: permission to view information on the Tenant Resources page.
                                                                              • management permission: permission for management on the Tenant page and permission to view alarms and events under O&M > Alarm.
                                                                              +
                                                                            • System
                                                                              • view permission: permission to view all pages except those under Permission on the System module.
                                                                              • management permission: permission for management on all pages except those under Permission on the System page and permission to view alarms and events under O&M > Alarm.

                                                                          4. Click OK.
                                                                          diff --git a/docs/mrs/umn/admin_guide_000150.html b/docs/mrs/umn/admin_guide_000150.html index f0df0877b..0425b4fc2 100644 --- a/docs/mrs/umn/admin_guide_000150.html +++ b/docs/mrs/umn/admin_guide_000150.html @@ -5,7 +5,7 @@
                                                                          • Modify password policies based on service security requirements, because they involve user management security. Otherwise, security risks may be incurred.
                                                                          • Change the user password after modifying the password policy, and then the new password policy can take effect.
                                                                          -

                                                                          Modifying a Password Policy (Versions Earlier than MRS 3.1.2-LTS.6)

                                                                          1. Log in to MRS Manager.
                                                                          2. Choose System > Permission > Security Policy > Password Policy.
                                                                          3. Click Modify in the Operation column and modify the password policy as prompted.

                                                                            For details about the parameters, see Table 1. +

                                                                            Modifying a Password Policy (Versions Earlier than MRS 3.1.2-LTS.6)

                                                                            1. Log in to MRS Manager.
                                                                            2. Choose System > Permission > Security Policy > Password Policy.
                                                                            3. Click Modify in the Operation column and modify the password policy as prompted.

                                                                              For details about the parameters, see Table 1.
                                                                              - + + + + + + + +
                                                                              Table 1 Password policy parameters

                                                                              Parameter

                                                                              Description

                                                                              @@ -58,7 +58,7 @@

                                                                            4. Click OK to save the configurations. Change the user password after modifying the password policy, and then the new password policy can take effect.
                                                                              5. -

                                                                              Adding a Password Policy (MRS 3.1.2-LTS.6 and Later Versions)

                                                                              1. Log in to MRS Manager.
                                                                              2. Choose System > Permission > Security Policy > Password Policy.
                                                                              3. Click Add Password Policy and modify the password policy as prompted.

                                                                                For details about the parameters, see Table 2. +

                                                                                Adding a Password Policy (MRS 3.1.2-LTS.6 and Later Versions)

                                                                                1. Log in to MRS Manager.
                                                                                2. Choose System > Permission > Security Policy > Password Policy.
                                                                                3. Click Add Password Policy and modify the password policy as prompted.

                                                                                  For details about the parameters, see Table 2.
                                                                                  - + + + +
                                                                                  Table 2 Password policy parameters

                                                                                  Parameter

                                                                                  Description

                                                                                  @@ -120,12 +120,12 @@

                                                                                  A maximum of 32 password policies can be created.

                                                                                  -

                                                                                  Modifying a Password Policy (MRS 3.1.2-LTS.6 and Later Versions)

                                                                                  1. Log in to MRS Manager.
                                                                                  2. Choose System > Permission > Security Policy > Password Policy.
                                                                                  3. Click Modify in the row that contains the target password policy. On the Modify Password Policy page, modify the password policy as prompted.

                                                                                    For details about the parameters, see Table 2.

                                                                                    +

                                                                                    Modifying a Password Policy (MRS 3.1.2-LTS.6 and Later Versions)

                                                                                    1. Log in to MRS Manager.
                                                                                    2. Choose System > Permission > Security Policy > Password Policy.
                                                                                    3. Click Modify in the row that contains the target password policy. On the Modify Password Policy page, modify the password policy as prompted.

                                                                                      For details about the parameters, see Table 2.

                                                                                    4. Click OK to save the configurations.
                                                                                    • Users (except admin) cannot modify their own password policies.
                                                                                    • After the password policy bound to a user is modified, if the remaining password validity period is greater than the password validity period in the new password policy, the password validity period is set to the validity period in the new password policy. If the remaining password validity period is less than the password validity period in the new password policy, the password validity period remains unchanged.
                                                                                    -

                                                                                    Deleting a Password Policy (MRS 3.1.2-LTS.6 and Later Versions)

                                                                                    1. Log in to MRS Manager.
                                                                                    2. Choose System > Permission > Security Policy > Password Policy.
                                                                                    3. Click Delete in the row that contains the target password policy. In the dialog box that is displayed, click OK.
                                                                                    +

                                                                                    Deleting a Password Policy (MRS 3.1.2-LTS.6 and Later Versions)

                                                                                    1. Log in to MRS Manager.
                                                                                    2. Choose System > Permission > Security Policy > Password Policy.
                                                                                    3. Click Delete in the row that contains the target password policy. In the dialog box that is displayed, click OK.

                                                                                    The default password policy and the password policy that has been bound to a user cannot be deleted.

                                                                                    diff --git a/docs/mrs/umn/admin_guide_000162.html b/docs/mrs/umn/admin_guide_000162.html index 25c1344e2..5a56669de 100644 --- a/docs/mrs/umn/admin_guide_000162.html +++ b/docs/mrs/umn/admin_guide_000162.html @@ -89,7 +89,7 @@

                                                                                    To reset the password of the LDAP account, you need to restart ACS. The procedure is as follows:

                                                                                    1. Log in to the active management node as user omm using PuTTY, and run the following command to update the domain configuration:

                                                                                      sh ${BIGDATA_HOME}/om-server/om/sbin/restart-RealmConfig.sh

                                                                                      The command is run successfully if the following information is displayed:

                                                                                      -
                                                                                      Modify realm successfully. Use the new password to log into FusionInsight again.
                                                                                      +
                                                                                      Modify realm successfully...
                                                                                    2. Run the sh $CONTROLLER_HOME/sbin/acs_cmd.sh stop command to stop ACS.
                                                                                    3. Run the sh $CONTROLLER_HOME/sbin/acs_cmd.sh start command to start ACS.

                                                                                  diff --git a/docs/mrs/umn/admin_guide_000171.html b/docs/mrs/umn/admin_guide_000171.html index 98ffa8530..b57cdf350 100644 --- a/docs/mrs/umn/admin_guide_000171.html +++ b/docs/mrs/umn/admin_guide_000171.html @@ -16,10 +16,97 @@
                                                                                  • x86_64: indicates the client software package that can be deployed on the x86 servers.
                                                                                  • aarch64: indicates the client software package that can be deployed on the TaiShan servers.

                                                                                  The cluster supports two types of clients: x86_64 and aarch64. The client type must match the architecture of the node for installing the client. Otherwise, client installation will fail.

                                                                                  -

                                                                                4. Determine whether to generate a client file on the cluster node.

                                                                                  • If yes, select Save to Path, and click OK to generate the client file. By default, the client file is generated in /tmp/FusionInsight-Client on the active management node. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directories. Copy the software package to the file directory, for example, /opt/Bigdata/hadoopclient, on the server where the client is to be installed as user omm or root. Then, go to 5.

                                                                                    If you cannot obtain the permissions of user root, use user omm.

                                                                                    +

                                                                                  • Select the path for saving the downloaded client file.

                                                                                    You can directly download the client file to the node where the client is to be installed, or download the file to the active OMS node or local computer and copy it to the node where the client is to be installed.

                                                                                    +
                                                                                    • Server: Download the file to the active OMS node of the cluster.

                                                                                      The generated file is stored in the /tmp/FusionInsight-Client directory on the active OMS node by default. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directory. If the client file already exists in the path, the existing client file will be replaced.

                                                                                      +

                                                                                      When a cluster has many services installed, the cluster client file becomes quite large. Additionally, decompressing this file during installation can consume significant disk space. It's recommended to download the client files to a different directory that has ample space, or to promptly remove unnecessary files from the client download directory after installation. Doing so helps avoid exhausting the /tmp directory's disk space, which could interrupt the normal operation of the cluster nodes.

                                                                                      -
                                                                                    • If no, click OK and specify a local save path to download the complete client. Wait until the download is complete and go to 4.
                                                                                    -

                                                                                  • Upload the software package.

                                                                                    Use WinSCP to upload the obtained software package as the user (such as user_client) who prepares for the installation, to the directory (such as /opt/Bigdata/hadoopclient) of the server where the client is to be installed.

                                                                                    +

                                                                                    After the file is generated, copy the obtained package to another directory, for example, /opt/Bigdata/hadoopclient, as user omm or client installation user.

                                                                                    +
                                                                                  • Browser: Download the file to the local computer.
                                                                                  • Remote node: Download the file to a node other than the active OMS node. If you select this option, you need to set the following parameters: +
                                                                                    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                                    Table 1 Parameters

                                                                                    Parameter

                                                                                    +

                                                                                    Description

                                                                                    +

                                                                                    Example Value

                                                                                    +

                                                                                    Save to Path

                                                                                    +

                                                                                    Path for storing client files.

                                                                                    +

                                                                                    If there is already a client file in the path, it will be overwritten. For a remote node, write permission for the path is required.

                                                                                    +

                                                                                    /tmp/FusionInsight-Client-Remote/

                                                                                    +

                                                                                    Host IP Address

                                                                                    +

                                                                                    IP address of the remote node.

                                                                                    +
                                                                                    NOTE:

                                                                                    The platform type of the remote node must be the same as that of the downloaded client. Otherwise, the client may fail to be installed.

                                                                                    +
                                                                                    +

                                                                                    x.x.x.x

                                                                                    +

                                                                                    Host Port

                                                                                    +

                                                                                    Host port of the remote node.

                                                                                    +

                                                                                    22

                                                                                    +

                                                                                    Username

                                                                                    +

                                                                                    Username for logging in to the remote node.

                                                                                    +

                                                                                    For a remote node, write permission for the path is required.

                                                                                    +

                                                                                    xxx

                                                                                    +

                                                                                    Authentication Method

                                                                                    +

                                                                                    You can choose one of the following methods:

                                                                                    +
                                                                                    • Password: Use the password for login.
                                                                                    • SSH private keys: Use SSH private keys for login.
                                                                                    • None: To use this method, passwordless login needs to be enabled for the node.
                                                                                    +

                                                                                    Password

                                                                                    +

                                                                                    Password

                                                                                    +

                                                                                    This parameter is mandatory when Authentication Method is set to Password.

                                                                                    +

                                                                                    This parameter indicates the password used for login.

                                                                                    +

                                                                                    xxx

                                                                                    +

                                                                                    SSH Private Keys

                                                                                    +

                                                                                    This parameter is mandatory when Authentication Method is set to SSH private keys.

                                                                                    +

                                                                                    Click Select File and select a local file to upload.

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    Auto Deployment

                                                                                    +

                                                                                    Whether to enable auto deployment. This parameter is mandatory when Select Client Type is set to Complete Client.

                                                                                    +
                                                                                    • If you set this parameter to yes, the client is automatically installed and deployed on the current node.
                                                                                    • If you set this parameter to no, the client will not be automatically installed and deployed. You need to manually install the client after it is downloaded.
                                                                                    +

                                                                                    Yes

                                                                                    +

                                                                                    Deployment Path

                                                                                    +

                                                                                    This parameter is mandatory when Auto Deployment is set to Yes. If only the configuration file is downloaded, this parameter will not be displayed.

                                                                                    +

                                                                                    The deployment path must be empty if it already exists on the remote node. Otherwise, it will be created automatically. The path also requires operate and write permissions.

                                                                                    +

                                                                                    /opt/testclient

                                                                                    +
                                                                                    +
                                                                                    +
                                                                                  +

                                                                                  Copy the obtained software package to the file directory (for example, /tmp/FusionInsight-Client) of the server where the client is to be installed as the user (for example, user_client) who is preparing to install the client.

                                                                                  The name of the client software package is in the follow format: FusionInsight_Cluster_<Cluster ID>_Services_Client.tar.

                                                                                  The following steps and sections use FusionInsight_Cluster_1_Services_Client.tar as an example.

                                                                                  The host where the client is to be installed can be a node inside or outside the cluster. If the node is a server outside the cluster, it must be able to communicate with the cluster, and the NTP service must be enabled to ensure that the time is the same as that on the server.

                                                                                  For example, you can configure the same NTP clock source for external servers as that of the cluster. After the configuration, you can run the ntpq -np command to check whether the time is synchronized.
                                                                                  • If there is an asterisk (*) before the IP address of the NTP clock source in the command output, the synchronization is normal. For example:
                                                                                    remote refid st t when poll reach delay offset jitter 
@@ -40,7 +127,7 @@
                                                                                  -

                                                                                5. Log in as user user_client to the server where the client is to be installed.
                                                                                6. Decompress the software package.

                                                                                  Go to the directory where the installation package is stored, for example, /opt/Bigdata/hadoopclient. Run the following command to decompress the installation package to a local directory:

                                                                                  +

                                                                                7. Log in as user user_client to the server where the client is to be installed.
                                                                                8. Decompress the software package.

                                                                                  Go to the directory where the installation package is stored, for example, /opt/Bigdata/hadoopclient. Run the following command to decompress the installation package to a local directory:

                                                                                  tar -xvf FusionInsight_Cluster_1_Services_Client.tar

                                                                                9. Verify the software package.

                                                                                  Run the following command to verify the decompressed file and check whether the command output is consistent with the information in the sha256 file:

                                                                                  sha256sum -c FusionInsight_Cluster_1_Services_ClientConfig.tar.sha256

                                                                                  diff --git a/docs/mrs/umn/admin_guide_000173.html b/docs/mrs/umn/admin_guide_000173.html index ce7b5f2f0..fcad40e39 100644 --- a/docs/mrs/umn/admin_guide_000173.html +++ b/docs/mrs/umn/admin_guide_000173.html @@ -7,8 +7,96 @@

                                                                                  10. Procedure

                                                                                  Method 1:

                                                                                  1. Log in to MRS Manager. Click the wanted cluster from the Cluster drop-down list.
                                                                                  2. Click More and select Download Client. In the Download Cluster Client dialog box, select Configuration Files Only.

                                                                                    The generated compressed file contains the configuration files of all services.

                                                                                    -

                                                                                  3. Determine whether to generate a configuration file on the cluster node.

                                                                                    • If yes, select Save to Path, and click OK to generate the client file. By default, the client file is generated in /tmp/FusionInsight-Client on the active management node. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directories. Then, go to 4.
                                                                                    • If no, click OK and specify a local save path to download the complete client. Wait until the download is complete, and go to 4.
                                                                                    -

                                                                                  4. Use WinSCP to save the compressed file to the installation directory of the client as the client installation user, such as /opt/hadoopclient.
                                                                                  5. Decompress the software package.

                                                                                    Run the following commands to go to the directory where the client is installed, and decompress the file to a local directory. For example, the downloaded client file is FusionInsight_Cluster_1_Services_Client.tar.

                                                                                    +

                                                                                  6. Select the path for saving the downloaded client configuration file.

                                                                                    • Server: Download the file to the active OMS node of the cluster.

                                                                                      The generated file is stored in the /tmp/FusionInsight-Client directory on the active OMS node by default. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directory. If the client file already exists in the path, the existing client file will be replaced.

                                                                                      +

                                                                                      When a cluster has many services installed, the cluster client file becomes quite large. Additionally, decompressing this file during installation can consume significant disk space. It's recommended to download the client files to a different directory that has ample space, or to promptly remove unnecessary files from the client download directory after installation. Doing so helps avoid exhausting the /tmp directory's disk space, which could interrupt the normal operation of the cluster nodes.

                                                                                      +
                                                                                      +

                                                                                      After the file is generated, copy the obtained package to another directory, for example, /opt/Bigdata/hadoopclient, as user omm or client installation user.

                                                                                      +
                                                                                    • Browser: Download the file to the local computer.
                                                                                    • Remote node: Download the file to a node other than the active OMS node. If you select this option, you need to set the following parameters: +
                                                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                                      Table 1 Parameters

                                                                                      Parameter

                                                                                      +

                                                                                      Description

                                                                                      +

                                                                                      Example Value

                                                                                      +

                                                                                      Save to Path

                                                                                      +

                                                                                      Path for storing client files.

                                                                                      +

                                                                                      If there is already a client file in the path, it will be overwritten. For a remote node, write permission for the path is required.

                                                                                      +

                                                                                      /tmp/FusionInsight-Client-Remote/

                                                                                      +

                                                                                      Host IP Address

                                                                                      +

                                                                                      IP address of the remote node.

                                                                                      +
                                                                                      NOTE:

                                                                                      The platform type of the remote node must be the same as that of the downloaded client. Otherwise, the client may fail to be installed.

                                                                                      +
                                                                                      +

                                                                                      x.x.x.x

                                                                                      +

                                                                                      Host Port

                                                                                      +

                                                                                      Host port of the remote node.

                                                                                      +

                                                                                      22

                                                                                      +

                                                                                      Username

                                                                                      +

                                                                                      Username for logging in to the remote node.

                                                                                      +

                                                                                      For a remote node, write permission for the path is required.

                                                                                      +

                                                                                      xxx

                                                                                      +

                                                                                      Authentication Method

                                                                                      +

                                                                                      You can choose one of the following methods:

                                                                                      +
                                                                                      • Password: Use the password for login.
                                                                                      • SSH private keys: Use SSH private keys for login.
                                                                                      • None: To use this method, passwordless login needs to be enabled for the node.
                                                                                      +

                                                                                      Password

                                                                                      +

                                                                                      Password

                                                                                      +

                                                                                      This parameter is mandatory when Authentication Method is set to Password.

                                                                                      +

                                                                                      This parameter indicates the password used for login.

                                                                                      +

                                                                                      xxx

                                                                                      +

                                                                                      SSH Private Keys

                                                                                      +

                                                                                      This parameter is mandatory when Authentication Method is set to SSH private keys.

                                                                                      +

                                                                                      Click Select File and select a local file to upload.

                                                                                      +

                                                                                      -

                                                                                      +

                                                                                      Auto Deployment

                                                                                      +

                                                                                      Whether to enable auto deployment. This parameter is mandatory when Select Client Type is set to Complete Client.

                                                                                      +
                                                                                      • If you set this parameter to yes, the client is automatically installed and deployed on the current node.
                                                                                      • If you set this parameter to no, the client will not be automatically installed and deployed. You need to manually install the client after it is downloaded.
                                                                                      +

                                                                                      Yes

                                                                                      +

                                                                                      Deployment Path

                                                                                      +

                                                                                      This parameter is mandatory when Auto Deployment is set to Yes. If only the configuration file is downloaded, this parameter will not be displayed.

                                                                                      +

                                                                                      The deployment path must be empty if it already exists on the remote node. Otherwise, it will be created automatically. The path also requires operate and write permissions.

                                                                                      +

                                                                                      /opt/testclient

                                                                                      +
                                                                                      +
                                                                                      +
                                                                                    +

                                                                                  7. Use WinSCP to save the compressed file to the installation directory of the client as the client installation user, such as /opt/hadoopclient.
                                                                                  8. Decompress the software package.

                                                                                    Run the following commands to go to the directory where the client is installed, and decompress the file to a local directory. For example, the downloaded client file is FusionInsight_Cluster_1_Services_Client.tar.

                                                                                    cd /opt/hadoopclient

                                                                                    tar -xvf FusionInsight_Cluster_1_Services_Client.tar

                                                                                  9. Verify the software package.

                                                                                    Run the following command to verify the decompressed file and check whether the command output is consistent with the information in the sha256 file:

                                                                                    diff --git a/docs/mrs/umn/admin_guide_000176.html b/docs/mrs/umn/admin_guide_000176.html index 64644cd11..a47bd47f8 100644 --- a/docs/mrs/umn/admin_guide_000176.html +++ b/docs/mrs/umn/admin_guide_000176.html @@ -113,7 +113,7 @@ The password reset after changing cluster domain name is: "Admin@123Test#$%@123"

                                                                                10. Click OK. Proceed with the subsequent steps only after the modification is complete.
                                                                                11. Log in to the active management node as user omm.
                                                                                12. Run the following command to update the domain configuration:

                                                                                  sh ${BIGDATA_HOME}/om-server/om/sbin/restart-RealmConfig.sh

                                                                                  The command is executed successfully if the following information is displayed:

                                                                                  -
                                                                                  Modify realm successfully. Use the new password to log into FusionInsight again.
                                                                                  +
                                                                                  Modify realm successfully...

                                                                                  After the restart, some hosts and services cannot be accessed and an alarm is generated. This problem can be automatically resolved in about 1 minute after restart-RealmConfig.sh is run.

                                                                                  1. Log in to MRS Manager using the new password of user admin (for example, Admin@123Admin@123). On the dashboard, click next to the name of the target cluster and select Restart.

                                                                                    In the displayed dialog box, enter the password of the current login user and click OK.

                                                                                    diff --git a/docs/mrs/umn/admin_guide_000177.html b/docs/mrs/umn/admin_guide_000177.html index e7b7a6d1b..5b53c0d83 100644 --- a/docs/mrs/umn/admin_guide_000177.html +++ b/docs/mrs/umn/admin_guide_000177.html @@ -38,7 +38,7 @@

                                                                                  2. Click OK.
                                                                                  3. Log in to the active management node as user omm, and run the following command to update the domain configuration:

                                                                                    sh ${BIGDATA_HOME}/om-server/om/sbin/restart-RealmConfig.sh

                                                                                    The command is executed successfully if the following information is displayed:

                                                                                    -
                                                                                    Modify realm successfully. Use the new password to log into FusionInsight again.
                                                                                    +
                                                                                    Modify realm successfully...

                                                                                    After the restart, some hosts and services cannot be accessed and an alarm is generated. This problem can be automatically resolved in about 1 minute after restart-RealmConfig.sh is run.

                                                                                  4. Log in to MRS Manager and start all clusters.

                                                                                    Click next to the name of the target cluster and select Start. In the displayed Start Cluster dialog box, click OK. Wait until the cluster is started.

                                                                                  5. Log in to the other MRS Manager and repeat the preceding operations.
                                                                                  diff --git a/docs/mrs/umn/admin_guide_000201.html b/docs/mrs/umn/admin_guide_000201.html index 36ef27e4f..4e24ad759 100644 --- a/docs/mrs/umn/admin_guide_000201.html +++ b/docs/mrs/umn/admin_guide_000201.html @@ -18,6 +18,8 @@
                                                                                13. Backing Up DBService Data
                                                                                  14. +
                                                                                14. Backing Up Doris Data
                                                                                  +
                                                                                15. Backing Up HBase Metadata
                                                                                16. Backing Up HBase Service Data
                                                                                  diff --git a/docs/mrs/umn/admin_guide_000209.html b/docs/mrs/umn/admin_guide_000209.html index b916897fe..b8578118b 100644 --- a/docs/mrs/umn/admin_guide_000209.html +++ b/docs/mrs/umn/admin_guide_000209.html @@ -8,7 +8,7 @@

                                                                                  Prerequisites

                                                                                  • If data needs to be backed up to the remote HDFS, you have prepared a standby cluster for data backup. The authentication mode of the standby cluster is the same as that of the active cluster. For other backup modes, you do not need to prepare the standby cluster.
                                                                                  • If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same MRS Manager, mutual trust has been configured. For details, see Configuring Cross-Manager Mutual Trust Between Clusters. If the active cluster is deployed in normal mode, no mutual trust is required.
                                                                                  • Cross-cluster replication has been configured for the active and standby clusters. For details, see Enabling Cross-Cluster Replication.
                                                                                  • Time is consistent between the active and standby clusters and the NTP services on the active and standby clusters use the same time source.
                                                                                  -
                                                                                  • Backup policies, including the backup task type, period, backup object, backup directory, and Yarn queue required by the backup task are planned based on service requirements.
                                                                                  • The HDFS in the standby cluster has sufficient space. You are advised to save backup files in a custom directory.
                                                                                  • On the HDFS client, you have executed the hdfs lsSnapshottableDir command as user hdfs to check the list of directories for which HDFS snapshots have been created in the current cluster and ensured that the HDFS parent directory or subdirectory where data files to be backed up are stored does not have HDFS snapshots. Otherwise, the backup task cannot be created.
                                                                                  • If you want to back up data to NAS, you have deployed the NAS server in advance.
                                                                                  +
                                                                                  • Backup policies, including the backup task type, period, backup object, backup directory, and Yarn queue required by the backup task are planned based on service requirements.
                                                                                  • The HDFS in the standby cluster has sufficient space. You are advised to save backup files in a custom directory.
                                                                                  • On the HDFS client, you have executed the hdfs lsSnapshottableDir command as user hdfs to check the list of directories for which HDFS snapshots have been created in the current cluster and ensured that the HDFS parent directory or subdirectory where data files to be backed up are stored does not have HDFS snapshots. Otherwise, the backup task cannot be created.
                                                                                  • If you want to back up data to NAS, you have deployed the NAS server in advance.
                                                                                  • If you want to back up data to OBS, you have connected the current cluster to OBS and have the permission to access OBS.

                                                                                  Procedure

                                                                                  1. On MRS Manager, choose O&M > Backup and Restoration > Backup Management.
                                                                                  2. Click Create.
                                                                                  3. Set Name to the name of the backup task.
                                                                                  4. Select the cluster to be operated from Backup Object.
                                                                                  5. Set Mode to the type of the backup task.

                                                                                    Periodic indicates that the backup task is executed by the system periodically. Manual indicates that the backup task is executed manually.

                                                                                    @@ -49,6 +49,8 @@
                                                                                  6. SFTP: indicates that backup files are stored in the server using the SFTP protocol.
                                                                                    If you select this option, set the following parameters:
                                                                                    • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
                                                                                    • Server IP Address: indicates the IP address of the server where the backup data is stored.
                                                                                    • Port: indicates the port number used to connect to the backup server over the SFTP protocol. The default value is 22.
                                                                                    • Username: indicates the username for connecting to the server using the SFTP protocol.
                                                                                    • Password: indicates the password for connecting to the server using the SFTP protocol.
                                                                                    • Server Shared Path: indicates the backup path on the SFTP server.
                                                                                    • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
                                                                                    • Queue Name: indicates the name of the Yarn queue used for backup task execution. The name must be the same as the name of the queue that is running properly in the cluster.
                                                                                    • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                    • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 100.
                                                                                    • NameService Name: indicates the NameService name of the backup directory. The default value is hacluster.
                                                                                    +
                                                                                  7. OBS: indicates that backup files are stored in OBS. (available in MRS 3.5.0 and later)

                                                                                    If you select this option, configure the following parameters:

                                                                                    +
                                                                                    • Target Path: indicates the OBS directory for storing backup data.
                                                                                    • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
                                                                                    • Queue Name: indicates the name of the Yarn queue used for backup task execution. The name must be the same as the name of the queue that is running properly in the cluster.
                                                                                    • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                    • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 100.

                                                                                  8. Set Maximum Number of Recovery Points to the number of snapshots that can be retained in the cluster.
                                                                                  9. Set Backup Content to one or multiple HDFS directories to be backed up based on service requirements.

                                                                                    You can select backup data using either of the following methods:

                                                                                    • Adding a backup data file

                                                                                      Click the name of a database in the navigation tree to show all the tables in the database, and select specified tables.

                                                                                      diff --git a/docs/mrs/umn/admin_guide_000210.html b/docs/mrs/umn/admin_guide_000210.html index 74e9ff447..29065db5f 100644 --- a/docs/mrs/umn/admin_guide_000210.html +++ b/docs/mrs/umn/admin_guide_000210.html @@ -3,7 +3,7 @@

                                                                                      Backing Up Hive Service Data

                                                                                      Scenario

                                                                                      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 can be used to recover the system if an exception occurs or the operation has not achieved the expected result, minimizing the adverse impacts on services.

                                                                                      You can create a backup task on MRS Manager to back up Hive service data. Both automatic and manual backup tasks are supported.

                                                                                      -
                                                                                      • Hive backup and restoration cannot identify the service and structure relationships of objects such as Hive tables, indexes, and views. When executing backup and restoration tasks, you need to manage unified restoration points based on service scenarios to ensure proper service running.
                                                                                      • Hive backup and restoration do not support Hive on RDB data tables. You need to back up and restore original data tables in external databases independently.
                                                                                      • If the backup data of the standby cluster is lost in an existing Hive backup task that contains Hive on HBase tables, the next incremental backup will fail, and you need to create a Hive backup task again. However, the next full backup task will be normal.
                                                                                      • After the backup function of MRS Manager is used to back up the HDFS directories at the Hive table level, the Hive tables cannot be deleted and recreated.
                                                                                      +
                                                                                      • Hive backup and restoration cannot identify the service and structure relationships of objects such as Hive tables, indexes, and views. When executing backup and restoration tasks, you need to manage unified restoration points based on service scenarios to ensure proper service running.
                                                                                      • Hive backup and restoration do not support Hive on RDB data tables. You need to back up and restore original data tables in external databases independently.
                                                                                      • If the backup data of the standby cluster is lost in an existing Hive backup task that contains Hive on HBase tables, the next incremental backup will fail, and you need to create a Hive backup task again. However, the next full backup task will be normal.
                                                                                      • After the backup function of MRS Manager is used to back up the HDFS directories at the Hive table level, the Hive tables cannot be deleted and recreated.
                                                                                      • If you want to back up data to OBS in MRS 3.5.0 and later, you have connected the current cluster to OBS and have the permission to access OBS.

                                                                                      Prerequisites

                                                                                      • If data needs to be backed up to the remote HDFS, you have prepared a standby cluster for data backup. The authentication mode of the standby cluster is the same as that of the active cluster. For other backup modes, you do not need to prepare the standby cluster.
                                                                                      • If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same MRS Manager, mutual trust has been configured. For details, see Configuring Cross-Manager Mutual Trust Between Clusters. If the active cluster is deployed in normal mode, no mutual trust is required.
                                                                                      • Cross-cluster replication has been configured for the active and standby clusters. For details, see Enabling Cross-Cluster Replication.
                                                                                      • Time is consistent between the active and standby clusters and the NTP services on the active and standby clusters use the same time source.
                                                                                      • Backup policies, including the backup task type, period, backup object, backup directory, and Yarn queue required by the backup task are planned based on service requirements.
                                                                                      • The HDFS in the standby cluster has sufficient space. You are advised to save backup files in a custom directory.
                                                                                      • On the HDFS client, you have executed the hdfs lsSnapshottableDir command as user hdfs to check the list of directories for which HDFS snapshots have been created in the current cluster and ensured that the HDFS parent directory or subdirectory where data files to be backed up are stored does not have HDFS snapshots. Otherwise, the backup task cannot be created.
                                                                                      • If you want to back up data to NAS, you have deployed the NAS server in advance.
                                                                                      @@ -43,6 +43,8 @@
                                                                                    • SFTP: indicates that backup files are stored in the server using the SFTP protocol.
                                                                                      If you select this option, set the following parameters:
                                                                                      • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
                                                                                      • Server IP Address: indicates the IP address of the server where the backup data is stored.
                                                                                      • Port: indicates the port number used to connect to the backup server over the SFTP protocol. The default value is 22.
                                                                                      • Username: indicates the username for connecting to the server using the SFTP protocol.
                                                                                      • Password: indicates the password for connecting to the server using the SFTP protocol.
                                                                                      • Server Shared Path: indicates the backup path on the SFTP server.
                                                                                      • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
                                                                                      • Queue Name: indicates the name of the Yarn queue used for backup task execution. The name must be the same as the name of the queue that is running properly in the cluster.
                                                                                      • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                      • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 100.
                                                                                      • NameService Name: indicates the NameService name of the backup directory. The default value is hacluster.
                                                                                      +
                                                                                    • OBS: indicates that backup files are stored in OBS.

                                                                                      If you select this option, set the following parameters:

                                                                                      +
                                                                                      • Target Path: indicates the OBS directory for storing backup data.
                                                                                      • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
                                                                                      • Queue Name: indicates the name of the Yarn queue used for backup task execution. The name must be the same as the name of the queue that is running properly in the cluster.
                                                                                      • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                      • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 100.

                                                                                  10. Set Maximum Number of Recovery Points to the number of snapshots that can be retained in the cluster.
                                                                                  11. Set Backup Content to one or multiple Hive tables to be backed up.

                                                                                    You can select backup data using either of the following methods:

                                                                                    • Adding a backup data file

                                                                                      Click the name of a database in the navigation tree to show all the tables in the database, and select specified tables.

                                                                                      diff --git a/docs/mrs/umn/admin_guide_000215.html b/docs/mrs/umn/admin_guide_000215.html index 4451c7943..906ac2c1b 100644 --- a/docs/mrs/umn/admin_guide_000215.html +++ b/docs/mrs/umn/admin_guide_000215.html @@ -14,6 +14,8 @@
                                                                                    • Restoring DBService data
                                                                                      • +
                                                                                    • Restoring Doris Service Data
                                                                                      +
                                                                                    • Restoring HBase Metadata
                                                                                    • Restoring HBase Service Data
                                                                                      diff --git a/docs/mrs/umn/admin_guide_000223.html b/docs/mrs/umn/admin_guide_000223.html index 548df2856..4ed20ccc7 100644 --- a/docs/mrs/umn/admin_guide_000223.html +++ b/docs/mrs/umn/admin_guide_000223.html @@ -22,6 +22,8 @@
                                                                                    • SFTP: indicates that backup files are stored in the server using the SFTP protocol.
                                                                                      If you select SFTP, set the following parameters:
                                                                                      • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
                                                                                      • Server IP Address: indicates the IP address of the server where the backup data is stored.
                                                                                      • Port: indicates the port number used to connect to the backup server over the SFTP protocol. The default value is 22.
                                                                                      • Username: indicates the username for connecting to the server using the SFTP protocol.
                                                                                      • Password: indicates the password for connecting to the server using the SFTP protocol.
                                                                                      • Source Path: indicates the full path of the backup file on the backup server, for example, Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz.
                                                                                      • Queue Name: indicates the name of the Yarn queue used for backup task execution.
                                                                                      • Recovery Point List: Click Refresh and select an HDFS directory that has been backed up in the standby cluster.
                                                                                      • Target NameService Name: indicates the NameService name of the backup directory. The default value is hacluster.
                                                                                      • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                      • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 100.
                                                                                      +
                                                                                    • OBS: indicates that backup files are stored in OBS (supported in MRS 3.5.0 and later only).

                                                                                      If you select this option, configure the following parameters:

                                                                                      +
                                                                                      • Source Path: indicates the full OBS path of a backup file, for example, Backup path/xxx/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz.
                                                                                      • Queue Name: indicates the name of the YARN queue used for executing the backup task.
                                                                                      • Recovery Point List: Click Refresh and select an OBS directory that has been backed up.
                                                                                      • Target NameService Name: indicates the NameService name of the backup directory. The default value is hacluster.
                                                                                      • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                      • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 100.

                                                                                  12. In the Backup Data column of the Data Configuration page, select one or more pieces of backup data that needs to be restored based on service requirements. In the Target Path column, specify the target location after backup data restoration.

                                                                                    You are advised to set Target Path to a new path that is different from the backup path.

                                                                                  13. Click Verify to check whether the restoration task is configured correctly.

                                                                                    • If the queue name is incorrect, the verification fails.
                                                                                    • If the specified directory to be restored does not exist, the verification fails.
                                                                                    diff --git a/docs/mrs/umn/admin_guide_000224.html b/docs/mrs/umn/admin_guide_000224.html index 704ec61cf..71d583574 100644 --- a/docs/mrs/umn/admin_guide_000224.html +++ b/docs/mrs/umn/admin_guide_000224.html @@ -22,6 +22,8 @@
                                                                                  14. SFTP: indicates that backup files are stored in the server using the SFTP protocol.
                                                                                    If you select SFTP, set the following parameters:
                                                                                    • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
                                                                                    • Server IP Address: indicates the IP address of the server where the backup data is stored.
                                                                                    • Port: indicates the port number used to connect to the backup server over the SFTP protocol. The default value is 22.
                                                                                    • Username: indicates the username for connecting to the server using the SFTP protocol.
                                                                                    • Password: indicates the password for connecting to the server using the SFTP protocol.
                                                                                    • Source Path: indicates the full path of the backup file on the backup server, for example, Backup path/Backup task name_Data source_Task creation time.
                                                                                    • Queue Name: indicates the name of the Yarn queue used for backup task execution.
                                                                                    • Recovery Point List: Click Refresh and select an HDFS directory that has been backed up in the standby cluster.
                                                                                    • Target NameService Name: indicates the NameService name of the backup directory. The default value is hacluster.
                                                                                    • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                    • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 1.
                                                                                    +
                                                                                  15. OBS: indicates that backup files are stored in OBS (supported in MRS 3.5.0 and later only).

                                                                                    If you select this option, configure the following parameters:

                                                                                    +
                                                                                    • Source Path: indicates the full OBS path of a backup file, for example, Backup path/xxx/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz.
                                                                                    • Queue Name: indicates the name of the YARN queue used for backup task execution.
                                                                                    • Recovery Point List: Click Refresh and select an OBS directory that has been backed up.
                                                                                    • Target NameService Name: indicates the NameService name of the backup directory. The default value is hacluster.
                                                                                    • Maximum Number of Maps: indicates the maximum number of maps in a MapReduce task. The default value is 20.
                                                                                    • Maximum Bandwidth of a Map (MB/s): indicates the maximum bandwidth of a map. The default value is 100.

                                                                                  16. Set Backup Data in the Data Configuration to one or multiple backup data sources to be recovered based on service requirements. In the Target Database and Target Path columns, specify the target database and file save path after backup data recovery.

                                                                                    Configuration restrictions:

                                                                                    • Data can be restored to the original database, but data tables must be stored in a new path that is different from the backup path.
                                                                                    • To restore Hive index tables, select the Hive data tables that correspond to the Hive index tables to be restored.
                                                                                    • If a new restoration directory is selected to avoid affecting the current data, HDFS permission must be manually granted so that users who have permission of backup tables can access this directory.
                                                                                    • Data can be restored to other databases. In this case, HDFS permission must be manually granted so that users who have permission of backup tables can access the HDFS directory that corresponds to the database.
                                                                                    diff --git a/docs/mrs/umn/admin_guide_000240.html b/docs/mrs/umn/admin_guide_000240.html index 69c29db1b..836e6d74b 100644 --- a/docs/mrs/umn/admin_guide_000240.html +++ b/docs/mrs/umn/admin_guide_000240.html @@ -27,7 +27,7 @@

                                                                                  17. Manager_viewer

                                                                                  Manager viewer who has the permission to view information about Homepage, Cluster, Hosts, Alarm, Events, and System > Permission.

                                                                                  +

                                                                                  Manager viewer, who has permission to view Homepage, Cluster, Hosts, Alarms and Events, Tenant Resources (available in MRS 3.5.0 and later), and System.

                                                                                  Manager_tenant

                                                                                  diff --git a/docs/mrs/umn/admin_guide_000249.html b/docs/mrs/umn/admin_guide_000249.html index ae3f841e8..133d48f10 100644 --- a/docs/mrs/umn/admin_guide_000249.html +++ b/docs/mrs/umn/admin_guide_000249.html @@ -8,6 +8,8 @@
                                                                                17. Changing the Password for an OS User
                                                                                  18. +
                                                                                18. Changing the OS User Password Validity Period
                                                                                  +
                                                                                  19. diff --git a/docs/mrs/umn/admin_guide_000363.html b/docs/mrs/umn/admin_guide_000363.html index 5800bb6c2..aa07b33de 100644 --- a/docs/mrs/umn/admin_guide_000363.html +++ b/docs/mrs/umn/admin_guide_000363.html @@ -2,7 +2,7 @@

                                                                                  Resetting the Component Database User Password

                                                                                  Scenario

                                                                                  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 database users to improve system O&M security.

                                                                                  -

                                                                                  This section applies only to MRS 3.1.2-LTS.6 or later. For versions earlier than MRS 3.1.2-LTS.6, see Changing the Password for a Component Database User.

                                                                                  +

                                                                                  This section applies only to MRS 3.1.2-LTS.6 or later. For versions earlier than MRS 3.1.2-LTS.6, see Changing the Password for a Component Database User.

                                                                                  Impact on the System

                                                                                  To reset passwords, you need to stop and then restart services, during which services are unavailable.

                                                                                  diff --git a/docs/mrs/umn/admin_guide_000399.html b/docs/mrs/umn/admin_guide_000399.html index f5e902ff7..5ec62085d 100644 --- a/docs/mrs/umn/admin_guide_000399.html +++ b/docs/mrs/umn/admin_guide_000399.html @@ -67,6 +67,13 @@

                                                                                  tableinfo files and data files of HBase system tables.

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse metadata.

                                                                                  +
                                                                                  • LocalDir
                                                                                  • RemoteHDFS
                                                                                  +
                                                                                  @@ -83,7 +90,7 @@

                                                                              Table-level user data. For a cluster with multiple services installed, backup and restoration are supported for multiple HBase service instances and the backup and restoration operations are consistent with those of a single HBase service instance.

                                                                              • RemoteHDFS
                                                                              • NFS
                                                                              • CIFS
                                                                              • SFTP
                                                                              +
                                                                              • RemoteHDFS
                                                                              • NFS
                                                                              • CIFS
                                                                              • SFTP
                                                                              • OBS

                                                                              HDFS

                                                                              @@ -98,6 +105,20 @@

                                                                              Table-level user data. For a cluster with multiple services installed, backup and restoration are supported for multiple Hive service instances and the backup and restoration operations are consistent with those of a single Hive service instance.

                                                                              ClickHouse

                                                                              +

                                                                              Table-level user data.

                                                                              +
                                                                              • RemoteHDFS
                                                                              • OBS
                                                                              +

                                                                              Doris

                                                                              +

                                                                              Doris data. This function is available for MRS 3.3.1 or later.

                                                                              +
                                                                              • RemoteHDFS
                                                                              • OBS
                                                                              +
                                                                              diff --git a/docs/mrs/umn/admin_guide_000407.html b/docs/mrs/umn/admin_guide_000407.html index d0918e0d7..fa385f2d7 100644 --- a/docs/mrs/umn/admin_guide_000407.html +++ b/docs/mrs/umn/admin_guide_000407.html @@ -20,6 +20,8 @@
                                                                            5. Configuring Spark SQL Inspection
                                                                              6. +
                                                                            6. Configuring Doris SQL Inspection
                                                                              +
                                                                              7. diff --git a/docs/mrs/umn/admin_guide_000408.html b/docs/mrs/umn/admin_guide_000408.html index 7a5cf3af1..9a60b9bf6 100644 --- a/docs/mrs/umn/admin_guide_000408.html +++ b/docs/mrs/umn/admin_guide_000408.html @@ -3,7 +3,7 @@

                                                                              Overview

                                                                              SQL engines in the big data field are emerging one after another. In addition to a wide range of solutions, some problems are exposed. For example, the quality of SQL input statements is uneven, SQL problems are difficult to locate, and large SQL statements consume too many resources.

                                                                              Low-quality SQL statements pose unexpected impacts on the data analysis platform, degrading system performance or platform stability.

                                                                              -

                                                                              This function is supported only by MRS 3.3.0 or later.

                                                                              +

                                                                              This function is supported only by MRS 3.3.0 or later.

                                                                              Function Description

                                                                              MRS allows you to configure inspection rules for mainstream SQL engines (Hive, Spark, HetuEngine, and ClickHouse). MRS can identify typical large SQL queries and low-quality SQL statements and intercepts them before execution or block them during execution. Users do not need to change how they submit SQL statements or change SQL syntax. Service modifications are not required and inspection is easy to implement.

                                                                              • You can configure SQL inspection rules on the UI that also allows you to query and modify the rules.
                                                                              • During query response and execution, each SQL engine proactively inspects SQL statements based on the rules.
                                                                              • Administrators can select to display hints on, intercept, or block SQL statements. The system logs SQL inspection events in real time for SQL audit. O&M engineers can analyze the logs, evaluate SQL statement quality on the live network, detect target statements, and take effective measures.
                                                                              diff --git a/docs/mrs/umn/admin_guide_000409.html b/docs/mrs/umn/admin_guide_000409.html index 64c25b451..765cb6621 100644 --- a/docs/mrs/umn/admin_guide_000409.html +++ b/docs/mrs/umn/admin_guide_000409.html @@ -1,11 +1,11 @@

                                                                              Adding an SQL Inspection

                                                                              -

                                                                              Scenario

                                                                              You can add rules for specified tenants and SQL engines on FusionInsight Manager. The system will display hints on, intercept, or block SQL requests matched by the rules.

                                                                              +

                                                                              Scenario

                                                                              You can add rules for specified tenants and SQL engines on MRS Manager. The system will display hints on, intercept, or block SQL requests matched by the rules.

                                                                              Exercise caution when you add or modify a SQL inspection rule for a cluster, enable a rule, and set the threshold. An improper rule may cause upper-layer service interruption.

                                                                              -

                                                                              Adding a Rule

                                                                              1. Log in to FusionInsight Manager as a user with the Manager administrator rights.
                                                                              2. Click Cluster and choose SQL Inspector. The SQL Inspector page is displayed.

                                                                                You can click View Supported Rules to view all SQL inspection rules supported by the current cluster.

                                                                                +

                                                                                Adding a Rule

                                                                                1. Log in to MRS Manager as a user with the Manager administrator rights.
                                                                                2. Click Cluster and choose SQL Inspector. The SQL Inspector page is displayed.

                                                                                  You can click View Supported Rules to view all SQL inspection rules supported by the current cluster.

                                                                                3. Click Add Rule. After the password of the current user is verified, the Add Rule page is displayed.
                                                                                4. Set the required parameters and click OK.

                                                                                  @@ -21,7 +21,7 @@

                                                                                  Parameter

                                                                                  ID

                                                                                  Rule ID

                                                                                  -

                                                                                  For details about meaning of the rules corresponding to the IDs, see Table 1.

                                                                                  +

                                                                                  For details about meaning of the rules corresponding to the IDs, see Table 1.

                                                                                  Tenant

                                                                                  @@ -48,273 +48,339 @@

                                                                                  MRS SQL Inspection Rules

                                                                                  -
                                                                                  - - + + + @@ -18,19 +29,19 @@ - - -
                                                                                  Table 1 MRS SQL inspection rules

                                                                                  ID

                                                                                  +
                                                                                  - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - - - - - - + - - - - - - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + + + + + + + + + + + + + + + diff --git a/docs/mrs/umn/admin_guide_000410.html b/docs/mrs/umn/admin_guide_000410.html index 59784d467..382cf1201 100644 --- a/docs/mrs/umn/admin_guide_000410.html +++ b/docs/mrs/umn/admin_guide_000410.html @@ -1,10 +1,10 @@

                                                                                  Changing the Timeout Duration of the Manager Page

                                                                                  -

                                                                                  FusionInsight Manager allows you to configure the timeout duration of the Manager page based on service requirements. You must properly set the timeout duration to prevent information leakage in long-time exposure of the web page.

                                                                                  -

                                                                                  This function is supported only by MRS 3.3.0 or later.

                                                                                  +

                                                                                  MRS Manager allows you to configure the timeout duration of the Manager page based on service requirements. You must properly set the timeout duration to prevent information leakage in long-time exposure of the web page.

                                                                                  +

                                                                                  This function is supported only by MRS 3.3.0 or later.

                                                                                  -

                                                                                  Changing the Timeout Duration of the Manager Page

                                                                                  1. Log in to FusionInsight Manager.
                                                                                  2. Choose System > OMS.
                                                                                  3. In the list, locate the row that contains tomcat and click Modify Configuration.
                                                                                  4. On the displayed page, set Session Timeout as required and click OK.

                                                                                    • Set the minimum session duration based on service requirements. Otherwise, there will be security risks.
                                                                                    • Currently, you cannot use the method described as follows to change the timeout duration of component web UIs.
                                                                                    +

                                                                                    Changing the Timeout Duration of the Manager Page

                                                                                    1. Log in to MRS Manager.
                                                                                    2. Choose System > OMS.
                                                                                    3. In the list, locate the row that contains tomcat and click Modify Configuration.
                                                                                    4. On the displayed page, set Session Timeout as required and click OK.

                                                                                      • Set the minimum session duration based on service requirements. Otherwise, there will be security risks.
                                                                                      • Currently, you cannot use the method described as follows to change the timeout duration of component web UIs.

                                                                                    diff --git a/docs/mrs/umn/admin_guide_000412.html b/docs/mrs/umn/admin_guide_000412.html index 9c5044695..fa4cb4d5f 100644 --- a/docs/mrs/umn/admin_guide_000412.html +++ b/docs/mrs/umn/admin_guide_000412.html @@ -1,13 +1,13 @@

                                                                                    Configuring Hive SQL Inspection

                                                                                    -

                                                                                    Scenario

                                                                                    You can configure rules for Hive SQL inspection on FusionInsight Manager and configure rule parameters as you need.

                                                                                    +

                                                                                    Scenario

                                                                                    You can configure rules for Hive SQL inspection on MRS Manager and configure rule parameters as you need.

                                                                                    Prerequisites

                                                                                    • The cluster client that contains the Hive service has been installed in the /opt/hadoopclient directory.
                                                                                    • The Hive service of the cluster is running properly.
                                                                                    • For a cluster with Kerberos authentication enabled, a user with Hive operation permissions has been created.

                                                                                    Constraints

                                                                                    • By default, SQL inspection rules need 5 seconds to take effect dynamically. After the queue is modified, it takes 10 minutes for Hive inspection rules to be reloaded.
                                                                                    • Interception and blocking rules will interrupt SQL tasks, so you need to set parameters of these rules properly based on the site requirements.
                                                                                    • For the rule dynamic_0001 (the number of files scanned by SQL statements exceeds the threshold), when the Spark and Tez engines reach the threshold, interception logs are printed in Yarn task logs and cannot be output on the Beeline client.
                                                                                    • Blocking rules have execution latency. For example, if the running_0004 rule is used and the threshold of the scanned data volume is 10 GB, the statement may be blocked when the data volume is 15 GB or higher due to the determination period and task concurrency.
                                                                                    -

                                                                                    Procedure

                                                                                    1. Log in to FusionInsight Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                    2. Add rules for Hive by referring to Adding an SQL Inspection.

                                                                                      For details about the rules supported by the Hive SQL engine, see MRS SQL Inspection Rules.

                                                                                      +

                                                                                      Procedure

                                                                                      1. Log in to MRS Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                      2. Add rules for Hive by referring to Adding an SQL Inspection.

                                                                                        For details about the rules supported by the Hive SQL engine, see MRS SQL Inspection Rules.

                                                                                        For example, add a rule whose ID is static_0001 to check whether count distinct appears more than two times in the SQL statement. If so, the system displays a hint.

                                                                                        Figure 1 Adding a Hive SQL inspection rule

                                                                                      3. Log in to the node where the Hive client is installed and run the following command to switch to the client installation directory.

                                                                                        cd /opt/hadoopclient

                                                                                        diff --git a/docs/mrs/umn/admin_guide_000413.html b/docs/mrs/umn/admin_guide_000413.html index 6452c9752..a5a25174d 100644 --- a/docs/mrs/umn/admin_guide_000413.html +++ b/docs/mrs/umn/admin_guide_000413.html @@ -1,13 +1,13 @@

                                                                                        Configuring ClickHouse SQL Inspection

                                                                                        -

                                                                                        Scenario

                                                                                        You can configure rules for ClickHouse SQL inspection on FusionInsight Manager and configure rule parameters as you need.

                                                                                        +

                                                                                        Scenario

                                                                                        You can configure rules for ClickHouse SQL inspection on MRS Manager and configure rule parameters as you need.

                                                                                        Prerequisites

                                                                                        • The cluster client that contains the ClickHouse service has been installed in the /opt/hadoopclient directory.
                                                                                        • The ClickHouse logical cluster is running properly.
                                                                                        • For clusters with Kerberos authentication enabled, you need to create a service user who has the permission to operate the ClickHouse table. For example, create a human-machine user clickhouseuser.
                                                                                        • A tenant associated with the ClickHouse service has been created and associated with the ClickHouse service user. For details, see Creating Tenants

                                                                                        Constraints

                                                                                        • The default dynamic validity period of a rule is 1 minute.
                                                                                        • Interception and blocking rules will interrupt SQL queries, so you need to set parameters of these rules properly based on the site requirements.
                                                                                        • After configuring ClickHouse rules, you need to log in to the client again for the rules to take effect.
                                                                                        -

                                                                                        Procedure

                                                                                        1. Log in to FusionInsight Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                        2. Add rules for ClickHouse by referring to Adding an SQL Inspection.

                                                                                          For details about the rules supported by the ClickHouse SQL engine, see MRS SQL Inspection Rules.

                                                                                          +

                                                                                          Procedure

                                                                                          1. Log in to MRS Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                          2. Add rules for ClickHouse by referring to Adding an SQL Inspection.

                                                                                            For details about the rules supported by the ClickHouse SQL engine, see MRS SQL Inspection Rules.

                                                                                            For example, add a rule whose ID is static_0008 and checks whether a SQL statement executes the cluster-level table update operation. If so, the system displays a hint.

                                                                                            Figure 1 Adding a ClickHouse SQL inspection rule

                                                                                          3. Log in to the node where the ClickHouse client is installed and run the following command to switch to the client installation directory.

                                                                                            cd /opt/hadoopclient

                                                                                            diff --git a/docs/mrs/umn/admin_guide_000414.html b/docs/mrs/umn/admin_guide_000414.html index 05fbf475d..f22c8e6a9 100644 --- a/docs/mrs/umn/admin_guide_000414.html +++ b/docs/mrs/umn/admin_guide_000414.html @@ -1,13 +1,13 @@

                                                                                            Configuring Spark SQL Inspection

                                                                                            -

                                                                                            Scenario

                                                                                            You can configure rules for Spark SQL inspection on FusionInsight Manager and configure rule parameters as you need.

                                                                                            +

                                                                                            Scenario

                                                                                            You can configure rules for Spark SQL inspection on MRS Manager and configure rule parameters as you need.

                                                                                            Prerequisites

                                                                                            • The cluster client that contains the Spark service has been installed in the /opt/hadoopclient directory.
                                                                                            • Spark is running properly.
                                                                                            • A tenant, for example, sparkstatic1 has been added to Tenant Resources. For details, see Creating Tenants.
                                                                                            • For a cluster with Kerberos authentication enabled, a service user has been created, for example, user sparkuser. The user belongs to groups hive, hadoop, and supergroup, the primary group is hive, and the bound role is set to sparkstatic1.

                                                                                            Constraints

                                                                                            • The default dynamic validity period of a rule is 6 minutes.
                                                                                            • Only SQL jobs are supported.
                                                                                            • Interception and blocking rules will interrupt SQL queries, so you need to set parameters of these rules properly based on the site requirements.
                                                                                            • The static rule static_0007 is not required for Spark because it has a Cartesian product restriction (controlled by spark.sql.crossJoin.enabled, which is true by default). If the spark parameter is false, the static_0007 rule will not take effect.
                                                                                            • Dynamic rules do work on carbon tables.
                                                                                            • The dynamic rule dynamic_0002 supports SELECT, ALTER TABLE ADD PARTITION and ALTER TABLE DROP PARTITION. If you use a batch deletion statement that contains judgment conditions, for example, ALTER TABLE DROP PARTITION (pt < 10), the statement will be intercepted before the dynamic_0002 rule because the number of partitions is limited by spark.sql.dropPartitionsInBatch.limit, which is defaulted to 1000.
                                                                                            • Blocking rules has execution latency. For example, if the running_0004 rule is used and the threshold of the scanned data volume is 10 GB, the statement may be blocked when the data volume is 15 GB or higher due to the determination period and task concurrency.
                                                                                            • If a job does not exceed the threshold until the last several tasks are complete before the block action is triggered, the job cannot be canceled.
                                                                                            • Blocking rule running_0004: The SQL execution duration includes the execution duration on the Driver side and the job running duration. When the SQL execution is blocked on the Driver side, the job cannot be canceled even if the execution duration exceeds the value of interruption threshold. This problem may occur when INSERT OVERWRITE is performed on a large number of partitions where storage and compute are decoupled.
                                                                                            -

                                                                                            Procedure

                                                                                            1. Log in to FusionInsight Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                            2. Add rules for Spark by referring to Adding an SQL Inspection.

                                                                                              For details about the rules supported by the Spark SQL engine, see MRS SQL Inspection Rules.

                                                                                              +

                                                                                              Procedure

                                                                                              1. Log in to MRS Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                              2. Add rules for Spark by referring to Adding an SQL Inspection.

                                                                                                For details about the rules supported by the Spark SQL engine, see MRS SQL Inspection Rules.

                                                                                                For example, add a rule whose ID is static_0001 to check whether count distinct appears more than two times in the SQL statement. If so, the system displays a hint.

                                                                                                Figure 1 Adding a Spark SQL inspection rule

                                                                                              3. Log in to the node where the Spark client is installed and run the following command to switch to the client installation directory.

                                                                                                cd /opt/hadoopclient

                                                                                                @@ -29,7 +29,7 @@
                                                                                                If the action set in the rule is Intercept, the following information is displayed:
                                                                                                Error in query: static_0001 Occurrence num of 'COUNT(DISTINCT)'(6) reaches the intercept threshold(2)

                                                                                                In Spark Beeline, you can obtain SQL inspection details from logs.

                                                                                                -
                                                                                                1. Log in to FusionInsight Manager and choose Cluster > Services > Yarn. On the Dashboard page, click the link next to ResourceManager WebUI to enter the Yarn web UI.
                                                                                                2. Click the ID of the target application on the All Applications page. The application details page is displayed.

                                                                                                  +
                                                                                                  1. Log in to MRS Manager and choose Cluster > Services > Yarn. On the Dashboard page, click the link next to ResourceManager WebUI to enter the Yarn web UI.
                                                                                                  2. Click the ID of the target application on the All Applications page. The application details page is displayed.

                                                                                                  3. Click Logs of the application. On the displayed page, click stdout logs to view SQL inspection details.

                                                                                                    diff --git a/docs/mrs/umn/admin_guide_000416.html b/docs/mrs/umn/admin_guide_000416.html index 3de830e15..a6b168b9e 100644 --- a/docs/mrs/umn/admin_guide_000416.html +++ b/docs/mrs/umn/admin_guide_000416.html @@ -1,13 +1,13 @@

                                                                                                    Configuring HetuEngine SQL Inspection

                                                                                                    -

                                                                                                    Scenario

                                                                                                    You can configure rules for HetuEngine SQL inspection on FusionInsight Manager and configure rule parameters as you need.

                                                                                                    +

                                                                                                    Scenario

                                                                                                    You can configure rules for HetuEngine SQL inspection on MRS Manager and configure rule parameters as you need.

                                                                                                    Prerequisites

                                                                                                    • The cluster client that contains the HetuEngine service has been installed in the /opt/hadoopclient directory.
                                                                                                    • The HetuEngine service and compute instances are running properly.
                                                                                                    • If Kerberos authentication has been enabled for the cluster, you need to create a HetuEngine user and grant related permissions to the user. In addition, you need to use Ranger to assign the user the permission to manage databases, tables, and columns of the data source.

                                                                                                    Constraints

                                                                                                    • The default dynamic validity period of a rule is 5 minutes.
                                                                                                    • Interception and blocking rules will interrupt SQL queries, so you need to set parameters of these rules properly based on the site requirements.
                                                                                                    • Blocking rules are controlled by session-level parameters of the system. To configure blocking rules, service users must have the set session permission.
                                                                                                    • For static rule static_0003, the total number of joins in queries does not include Semi joins and Anti joins.
                                                                                                    • When prompt rules are configured for dynamic_0001 and dynamic_0002, prompt messages are recorded only in logs and are not displayed on the client.
                                                                                                    • The client and server send asynchronous requests. For blocking rule Running_0001, after the server blocks the requests, the message "Query is gone " may be displayed on the client. In this case, you can view logs to check whether the requests are blocked.
                                                                                                    -

                                                                                                    Procedure

                                                                                                    1. Log in to FusionInsight Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                                    2. Add rules for HetuEngine by referring to Adding an SQL Inspection.

                                                                                                      For details about the rules supported by the HetuEngine SQL engine, see MRS SQL Inspection Rules.

                                                                                                      +

                                                                                                      Procedure

                                                                                                      1. Log in to MRS Manager, click Cluster, and choose SQL Inspector. The SQL Inspector page is displayed.
                                                                                                      2. Add rules for HetuEngine by referring to Adding an SQL Inspection.

                                                                                                        For details about the rules supported by the HetuEngine SQL engine, see MRS SQL Inspection Rules.

                                                                                                        For example, add a rule whose ID is static_0001 to check whether count distinct appears more than two times in the SQL statement. If so, the system displays a hint.

                                                                                                        Figure 1 Adding a HetuEngine SQL inspection rule

                                                                                                      3. Log in to the node where the HetuEngine client is installed and run the following command to switch to the client installation directory:

                                                                                                        cd /opt/hadoopclient

                                                                                                        diff --git a/docs/mrs/umn/admin_guide_000420.html b/docs/mrs/umn/admin_guide_000420.html new file mode 100644 index 000000000..c0d9fefa1 --- /dev/null +++ b/docs/mrs/umn/admin_guide_000420.html @@ -0,0 +1,22 @@ + + +

                                                                                                        Changing the OS User Password Validity Period

                                                                                                        +

                                                                                                        Scenario

                                                                                                        By default, the password validity period of an OS user is 90 days. This topic describes how to change the validity period.

                                                                                                        +

                                                                                                        You are advised to periodically change a user's login password of the cluster node operating system to improve system O&M security.

                                                                                                        +
                                                                                                        +

                                                                                                        Procedure

                                                                                                        1. Log in to the node where you want to change the password validity period of the OS user password as the root user.
                                                                                                        2. Change the OS user password validity period.

                                                                                                          • Legacy users

                                                                                                            Run the following command to change the password validity period:

                                                                                                            +

                                                                                                            chage -MValidity period (days) user_name

                                                                                                            +
                                                                                                            • Validity period (days): how many days the password is valid since its creation. If this parameter is set to 99999, the password never expires. Set this parameter based on the site requirements.
                                                                                                            • user_name: OS user whose validity period you want to change, for example, ommdba.
                                                                                                            • You are advised to set this parameter based on service demands and periodically change the user password.
                                                                                                            +
                                                                                                            +
                                                                                                          • New users

                                                                                                            Run the following command to edit the file and change the value of PASS_MAX_DAYS, which indicates the password validity period, in days. If the value is changed to 99999, the password never expires.

                                                                                                            +

                                                                                                            vi /etc/login.defs

                                                                                                            +
                                                                                                          +

                                                                                                        +
                                                                                                        +
                                                                                                        + + diff --git a/docs/mrs/umn/admin_guide_000423.html b/docs/mrs/umn/admin_guide_000423.html new file mode 100644 index 000000000..ec9c08ef8 --- /dev/null +++ b/docs/mrs/umn/admin_guide_000423.html @@ -0,0 +1,80 @@ + + +

                                                                                                        Backing Up Doris Data

                                                                                                        +

                                                                                                        Scenario

                                                                                                        To ensure Doris service data security, you need to back up Doris service data especially before you perform a major operation on Doris (such as upgrade or migration). The backup data can be used to recover the system if an exception occurs or the operation has not achieved the expected result, minimizing the adverse impacts on services.

                                                                                                        +

                                                                                                        You can create automatic or manual tasks on Manager to back up Doris data.

                                                                                                        +

                                                                                                        This topic is available for clusters of MRS 3.5.0 and later only.

                                                                                                        +
                                                                                                        +
                                                                                                        +

                                                                                                        Prerequisites

                                                                                                        • To back up data to a remote HDFS, the following conditions must be met:
                                                                                                          • A standby cluster for backing up data has been created. The authentication mode must be the same as that of the active cluster.
                                                                                                          • At least one DBroker instance of the Doris service has been deployed in the active cluster.
                                                                                                          • If the active and standby clusters are deployed in security mode and they are not managed by the same MRS Manager, mutual trust must be configured. For details, see Configuring Cross-Manager Mutual Trust Between Clusters. If the active and standby clusters are deployed in normal mode, no mutual trust is required.
                                                                                                          • The time on the active and standby clusters must be the same, and the NTP service on the active and standby clusters uses the same time source.
                                                                                                          • The HDFS in the standby cluster has sufficient space. You are advised to save backup files in a custom directory.
                                                                                                          • The value of hadoop.rpc.protection of Doris must be the same as that of hadoop.rpc.protection of HDFS in both active and standby clusters.
                                                                                                          +
                                                                                                        • You have planned the backup type, period, object, and directory based on service requirements.
                                                                                                        • If you want to back up data to OBS, you have connected the current cluster to OBS and have the permission to access OBS.
                                                                                                        +
                                                                                                        +

                                                                                                        Backing Up Doris Data

                                                                                                        1. On MRS Manager, choose O&M > Backup and Restoration > Backup Management.
                                                                                                        2. Click Create.
                                                                                                        3. Set Name to the name of the backup task.
                                                                                                        4. Select the desired cluster from Backup Object.
                                                                                                        5. Set Mode to the type of the backup task.

                                                                                                          • Periodic: indicates that the backup task is periodically executed. If you select this mode, you need to set other parameters by referring to Table 1.
                                                                                                          • Manual: indicates that the backup task is manually executed.
                                                                                                          + +
                                                                                  Table 1 MRS SQL inspection rules

                                                                                  ID

                                                                                  Description

                                                                                  +

                                                                                  Description

                                                                                  Engine

                                                                                  +

                                                                                  Engine

                                                                                  Threshold

                                                                                  +

                                                                                  Threshold

                                                                                  Example SQL Statement

                                                                                  +

                                                                                  Example SQL Statement

                                                                                  +

                                                                                  Impact

                                                                                  static_0001

                                                                                  +

                                                                                  static_0001

                                                                                  Check whether the number of occurrences of count(distinct) in the SQL statement exceeds the limit.

                                                                                  +

                                                                                  Check whether the number of the count(distinct) functions used in a SQL statement exceeds the preconfigured threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  Number of occurrences of count(distinct)

                                                                                  -

                                                                                  Recommended value: 10

                                                                                  +

                                                                                  Number of the count(distinct) functions

                                                                                  +

                                                                                  Recommended value: 10

                                                                                  SELECT COUNT(DISTINCT deviceId), COUNT(DISTINCT collDeviceId)

                                                                                  -

                                                                                  FROM table

                                                                                  -

                                                                                  GROUP BY deviceName, collDeviceName, collCurrentVersion;

                                                                                  +

                                                                                  SELECT COUNT(DISTINCT deviceId), COUNT(DISTINCT collDeviceId)

                                                                                  +

                                                                                  FROM table

                                                                                  +

                                                                                  GROUP BY deviceName, collDeviceName, collCurrentVersion;

                                                                                  +

                                                                                  The select count(distinct) syntax generates only one Reduce. When a large table is processed, the data volume to shuffle is large and the execution is slow. If there are multiple count distinct, multiple records are generated for the same record for shuffling, increasing the shuffling amount and slowing down the job execution.

                                                                                  static_0002

                                                                                  +

                                                                                  static_0002

                                                                                  Check whether the not in <subquery> statement is used in the SQL statement.

                                                                                  +

                                                                                  Check whether not in <subquery> is used in a SQL statement.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  SELECT *

                                                                                  -

                                                                                  FROM Orders o

                                                                                  -

                                                                                  WHERE Orders.Order_ID not in (Select Order_ID

                                                                                  -

                                                                                  FROM HeldOrders h

                                                                                  -

                                                                                  where h.order_id = o.order_id);

                                                                                  +

                                                                                  SELECT *

                                                                                  +

                                                                                  FROM Orders o

                                                                                  +

                                                                                  WHERE Orders.Order_ID not in (Select Order_ID

                                                                                  +

                                                                                  FROM HeldOrders h

                                                                                  +

                                                                                  where h.order_id = o.order_id);

                                                                                  +

                                                                                  The not in subquery performance is poor. If the listed values of the not in clause contains null, no data is returned in the result.

                                                                                  static_0003

                                                                                  +

                                                                                  static_0003

                                                                                  Check whether the number of joins in the SQL statement exceeds the limit.

                                                                                  +

                                                                                  Check whether the number of joins in a SQL statement exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  Number of joins

                                                                                  -

                                                                                  Recommended value: 20

                                                                                  +

                                                                                  Number of joins

                                                                                  +

                                                                                  Recommended value: 20

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  +

                                                                                  The more tables are joined, the more files, partitions, and data are scanned. As a result, the SQL statement occupies too much memory, affecting cluster stability.

                                                                                  static_0004

                                                                                  +

                                                                                  static_0004

                                                                                  Check whether the number of the union all operators in a SQL statement exceeds the threshold.

                                                                                  +

                                                                                  Check whether the number of the union all operators in a SQL statement exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  Number of the union all operators in a statement

                                                                                  -

                                                                                  Recommended value: 20

                                                                                  +

                                                                                  Number of the union all operators in a statement

                                                                                  +

                                                                                  Recommended value: 20

                                                                                  select * from tables t1

                                                                                  -

                                                                                  union all select * from tables t2

                                                                                  -

                                                                                  union all select * from tables t3

                                                                                  -

                                                                                  union all select * from tables t4

                                                                                  -

                                                                                  union all select * from tables t5

                                                                                  -

                                                                                  union all select * from tables t6

                                                                                  -

                                                                                  union all select * from tables t7

                                                                                  -

                                                                                  union all select * from tables t8

                                                                                  -

                                                                                  union all select * from tables t9;

                                                                                  +

                                                                                  select * from tables t1

                                                                                  +

                                                                                  union all select * from tables t2

                                                                                  +

                                                                                  union all select * from tables t3

                                                                                  +

                                                                                  union all select * from tables t4

                                                                                  +

                                                                                  union all select * from tables t5

                                                                                  +

                                                                                  union all select * from tables t6

                                                                                  +

                                                                                  union all select * from tables t7

                                                                                  +

                                                                                  union all select * from tables t8

                                                                                  +

                                                                                  union all select * from tables t9;

                                                                                  +

                                                                                  A large number of union all operations may generate ultra-large result sets. As a result, a large number of HDFS and Yarn resources are occupied during shuffling.

                                                                                  static_0005

                                                                                  +

                                                                                  static_0005

                                                                                  The number of subquery nesting layers exceeds the limit.

                                                                                  +

                                                                                  Check whether the number of nested subqueries exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  Maximum number of nested subqueries

                                                                                  -

                                                                                  Recommended value: 20

                                                                                  +

                                                                                  Number of nested subqueries

                                                                                  +

                                                                                  Recommended value: 20

                                                                                  select * from (

                                                                                  -

                                                                                  with temp1 as (select * from tables)

                                                                                  -

                                                                                  select * from temp1);

                                                                                  +

                                                                                  select * from (

                                                                                  +

                                                                                  with temp1 as (select * from tables)

                                                                                  +

                                                                                  select * from temp1);

                                                                                  +

                                                                                  If there are too many SQL nesting layers, temporary data is generated for multiple times, and SQL statements are difficult to maintain and modify. You are advised to avoid multiple nested queries to improve execution efficiency and SQL maintainability.

                                                                                  static_0006

                                                                                  +

                                                                                  static_0006

                                                                                  Check whether the length of the SQL statement string exceeds the upper limit.

                                                                                  +

                                                                                  Check whether the length of a SQL statement exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  Length of the SQL string, in KB

                                                                                  -

                                                                                  Recommended value: 10

                                                                                  +

                                                                                  Length of the SQL statement, in KB

                                                                                  +

                                                                                  Recommended value: 10

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  +

                                                                                  If a SQL string is too long, the SQL statement may be too complex, which may cause memory and performance problems. In addition, the SQL statement is difficult to maintain.

                                                                                  static_0007

                                                                                  +

                                                                                  static_0007

                                                                                  Check whether the Cartesian product exists when multiple tables are associated.

                                                                                  +

                                                                                  Check whether the Cartesian product exists when multiple tables are associated.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  select * from A,B;

                                                                                  +

                                                                                  select * from A,B;

                                                                                  +

                                                                                  The Cartesian product causes data expansion. When a task is running, a large amount of HDFS space and YARN resources may be occupied, affecting the execution of other tasks.

                                                                                  static_0008

                                                                                  +

                                                                                  static_0008

                                                                                  Check whether alter table update operation is performed at the cluster level (on cluster).

                                                                                  +

                                                                                  Check whether alter table update is performed at the cluster level (on cluster).

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  alter table testtb1 on cluster default_cluster update price=10.0 where id='100'

                                                                                  +

                                                                                  alter table testtb1 on cluster default_cluster update price=10.0 where id='100'

                                                                                  +

                                                                                  Updating and deleting data consume a large number of CPU and memory resources. Cluster-level operations pose high pressure on the database. As a result, tasks on some nodes may fail to be executed, time out, or do not respond for a long time, affecting cluster stability.

                                                                                  static_0009

                                                                                  +

                                                                                  static_0009

                                                                                  Check whether alter table delete operation is performed at the cluster level (on cluster).

                                                                                  +

                                                                                  Check whether alter table delete is performed at the cluster level (on cluster).

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  alter table testtb1 on cluster default_cluster delete where id ='10'

                                                                                  +

                                                                                  alter table testtb1 on cluster default_cluster delete where id ='10'

                                                                                  static_0010

                                                                                  +

                                                                                  static_0010

                                                                                  Check whether the alter table add column operation is performed at the cluster level (on cluster).

                                                                                  +

                                                                                  Check whether alter table add column is performed at the cluster level (on cluster).

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  alter table testtb1 on cluster default_cluster add column testc String

                                                                                  +

                                                                                  alter table testtb1 on cluster default_cluster add column testc String

                                                                                  +

                                                                                  Adding and deleting columns consume a large number of CPU and memory resources. Cluster-level operations pose high pressure on the database. As a result, tasks on some nodes may fail to be executed, time out, or do not respond for a long time, causing metadata inconsistency and affecting cluster stability.

                                                                                  static_0011

                                                                                  +

                                                                                  static_0011

                                                                                  Check whether the alter table drop column operation is performed at the cluster level (on cluster).

                                                                                  +

                                                                                  Check whether alter table drop column is performed at the cluster level (on cluster).

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  alter table testtb1 on cluster default_cluster drop column testc

                                                                                  +

                                                                                  alter table testtb1 on cluster default_cluster drop column testc

                                                                                  static_0012

                                                                                  +

                                                                                  static_0012

                                                                                  Check whether the optimize final operation is performed at the cluster level (on cluster).

                                                                                  +

                                                                                  Check whether optimize final is performed at the cluster level (on cluster).

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  optimize table testtb1 on cluster default_cluster final

                                                                                  +

                                                                                  optimize table testtb1 on cluster default_cluster final

                                                                                  +

                                                                                  Manual combination consumes a large number of CPU and memory resources and disk I/O resources when the table data volume is large. Cluster-level operations pose high pressure on the database. As a result, tasks on some nodes may fail to be executed, time out, or do not respond for a long time, affecting cluster stability.

                                                                                  static_0013

                                                                                  +

                                                                                  static_0013

                                                                                  Check whether the drop table operation is performed at the cluster level (on cluster).

                                                                                  +

                                                                                  Check whether drop is performed at the cluster level (on cluster).

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  drop table testtb1 on cluster default_cluster;

                                                                                  +

                                                                                  drop table/database test on cluster default_cluster;

                                                                                  +

                                                                                  Dropping tables consumes a large number of CPU and memory resources and disk I/O resources when the metadata volume and data volume are large. Cluster-level operations pose high pressure on the database. As a result, tasks on some nodes may fail to be executed, time out, or do not respond for a long time, affecting cluster stability.

                                                                                  static_0014

                                                                                  +

                                                                                  static_0014

                                                                                  Check whether the truncate table operation is performed at the cluster level (on cluster).

                                                                                  +

                                                                                  Check whether truncate table is performed at the cluster level (on cluster).

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  truncate table testtb1 on cluster default_cluster;

                                                                                  +

                                                                                  truncate table testtb1 on cluster default_cluster;

                                                                                  +

                                                                                  Deleting table data consumes a large number of CPU and memory resources and disk I/O resources when the table data volume is large. Cluster-level operations pose high pressure on the database. As a result, tasks on some nodes may fail to be executed, time out, or do not respond for a long time, affecting cluster stability.

                                                                                  dynamic_0001

                                                                                  +

                                                                                  dynamic_0001

                                                                                  Check whether the number of scanned files exceeds the limit.

                                                                                  +

                                                                                  Check whether the number of scanned files exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • Doris

                                                                                  Number of files that will be scanned or have been scanned

                                                                                  -

                                                                                  Recommended value: 100,000

                                                                                  +

                                                                                  Number of files that will be scanned or have been scanned

                                                                                  +

                                                                                  Recommended value: 100,000

                                                                                  SELECT ss_ticket_number FROM store_sales WHERE ss_ticket_number=72291252 LIMIT 10;

                                                                                  +

                                                                                  SELECT ss_ticket_number FROM store_sales WHERE ss_ticket_number=72291252 LIMIT 10;

                                                                                  +

                                                                                  Scanning a large number of files with a SQL statement can generate a large number of slices, overloading HiveServer memory and potentially causing the instance to crash. This can also consume a significant amount of cluster resources, delaying other tasks.

                                                                                  dynamic_0002

                                                                                  +

                                                                                  dynamic_0002

                                                                                  Check whether the number of partitions involved in operations (select, delete, update, and alter) on a table exceeds the upper limit.

                                                                                  +

                                                                                  Check whether the number of partitions involved in a table operation (select, delete, update, or alter) exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  • Doris

                                                                                  Number of partitions involved in the delete or alter operation

                                                                                  -

                                                                                  Recommended value: 10,000

                                                                                  +

                                                                                  Number of partitions involved in the delete or alter operation

                                                                                  +

                                                                                  Recommended value: 10,000

                                                                                  DELETE FROM table_name WHERE column_name = value

                                                                                  +

                                                                                  DELETE FROM table_name WHERE column_name = value

                                                                                  +

                                                                                  Scanning too many partitions can overload the database, causing it to run slowly and consume excessive memory in HiveServer and MetaStore. This can lead to frequent GC, disrupting other tasks and potentially causing the instance to restart unexpectedly.

                                                                                  dynamic_0003

                                                                                  +

                                                                                  dynamic_0003

                                                                                  When the right table of a join is a distributed table, check whether the data volume of the right table exceeds the upper limit.

                                                                                  +

                                                                                  When the right table of a join is a distributed table, check whether the data volume of the right table exceeds the threshold.

                                                                                  ClickHouse

                                                                                  +

                                                                                  ClickHouse

                                                                                  Number of rows in the right table when the join operation is performed.

                                                                                  -

                                                                                  Recommended value: 100,000,000

                                                                                  +

                                                                                  Number of rows in the right table of a join

                                                                                  +

                                                                                  Recommended value: 100,000,000

                                                                                  SELECT name, text FROM table_1 JOIN table_2 ON table_1.Id = table_2.Id

                                                                                  +

                                                                                  SELECT name, text FROM table_1 JOIN table_2 ON table_1.Id = table_2.Id

                                                                                  +

                                                                                  Large data volumes in the right table can cause the join operation to consume excessive memory, potentially leading to memory insufficiency, service failure, and cluster instability.

                                                                                  running_0001

                                                                                  +

                                                                                  dynamic_0004

                                                                                  Check whether the number of result rows returned by the Select statement to the client exceeds the upper limit.

                                                                                  +

                                                                                  Check whether a SQL statement overwrites the same table where it reads data.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark

                                                                                  Number of rows in the query result

                                                                                  -

                                                                                  Recommended value: 100,000

                                                                                  +

                                                                                  N/A

                                                                                  select * from table

                                                                                  +

                                                                                  N/A

                                                                                  +

                                                                                  Such SQL statements may cause data loss or inconsistency.

                                                                                  running_0002

                                                                                  +

                                                                                  running_0001

                                                                                  Check whether the peak memory usage of the SQL statement exceeds the absolute value limit.

                                                                                  +

                                                                                  Check whether the number of rows returned by a Select statement to the client exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  • Doris

                                                                                  Memory occupied by SQL running, in MB

                                                                                  +

                                                                                  Number of rows in the query result

                                                                                  +

                                                                                  Recommended value: 100,000

                                                                                  N/A

                                                                                  +

                                                                                  select * from table

                                                                                  +

                                                                                  Large query results can cause server memory overload, leading to OOM exceptions and instability. Excessive results also slow down query efficiency.

                                                                                  running_0003

                                                                                  +

                                                                                  running_0002

                                                                                  Check whether the running duration of the SQL statement exceeds the upper limit.

                                                                                  +

                                                                                  Check whether the peak memory usage of a SQL statement exceeds the threshold (absolute value).

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  • Doris

                                                                                  SQL running duration threshold, in seconds

                                                                                  +

                                                                                  Memory occupied by a SQL statement during runtime, in MB

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  +

                                                                                  Long-running tasks consume cluster resources, slowing down other tasks and overall performance.

                                                                                  running_0004

                                                                                  +

                                                                                  running_0003

                                                                                  The amount of data scanned by the SQL statements.

                                                                                  +

                                                                                  Check whether the running duration of a SQL statement exceeds the threshold.

                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  • Doris

                                                                                  Amount of data scanned by the SQL statement, in GB

                                                                                  -

                                                                                  Recommended value: 10,240

                                                                                  +

                                                                                  Running duration of a SQL statement, in seconds

                                                                                  N/A

                                                                                  +

                                                                                  N/A

                                                                                  +

                                                                                  Long-running tasks can monopolize cluster resources, reducing overall utilization. They also generate a significant amount of intermediate data. To avoid delays, tasks that fail to meet expectations should be adjusted promptly.

                                                                                  +

                                                                                  running_0004

                                                                                  +

                                                                                  Check whether the size of data scanned by a SQL statement exceeds the threshold.

                                                                                  +
                                                                                  • Hive
                                                                                  • Spark
                                                                                  • HetuEngine
                                                                                  • ClickHouse
                                                                                  +

                                                                                  Data scanned by a SQL statement, in GB

                                                                                  +

                                                                                  Recommended value: 10,240

                                                                                  +

                                                                                  N/A

                                                                                  +

                                                                                  Large datasets can consume significant memory resources, impacting other tasks' performance. Intermediate data can also fill disk space, compromising cluster stability.

                                                                                  +

                                                                                  running_0005

                                                                                  +

                                                                                  Check whether the amount of shuffle data that has been written by a SQL statement exceeds the threshold.

                                                                                  +

                                                                                  Spark

                                                                                  +

                                                                                  Amount of shuffle data written by a SQL statement, in GB

                                                                                  +

                                                                                  N/A

                                                                                  +

                                                                                  When executing SQL statements with operators like join and aggregation, a significant amount of data is shuffled, leading to high disk usage and potentially causing disk space exhaustion, which can compromise cluster stability.
                                                                                  + + + + + + + + + + + + + +
                                                                                  Table 1 Periodic backup parameters

                                                                                  Parameter

                                                                                  +

                                                                                  Description

                                                                                  +

                                                                                  Started

                                                                                  +

                                                                                  Time when the task is started for the first time

                                                                                  +

                                                                                  Period

                                                                                  +

                                                                                  The task execution interval. The options include Hours and Days.

                                                                                  +

                                                                                  Backup Policy

                                                                                  +
                                                                                  • Full backup at the first time and incremental backup subsequently
                                                                                  • Full backup every time
                                                                                  • Full backup once every n times
                                                                                  +
                                                                                  NOTE:

                                                                                  Currently, Doris supports only full backup each time. Incremental backup is not supported.

                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  +

                                                                                5. In Configuration, select Doris under Metadata and other data.
                                                                                6. Set Path Type of Doris to a backup directory type.

                                                                                  +

                                                                                  + + + + + + + + + + +
                                                                                  Table 2 Path of backup data

                                                                                  Directory Type

                                                                                  +

                                                                                  Description

                                                                                  +

                                                                                  RemoteHDFS

                                                                                  +

                                                                                  Indicates that backup files are stored in the HDFS directory of the standby cluster. If you select this option, configure the following parameters:

                                                                                  +
                                                                                  • Destination NameService Name: indicates the NameService name of the standby cluster, for example, hacluster. You can obtain it from the NameService Management page of HDFS on the standby cluster.
                                                                                  +
                                                                                  • IP Mode: indicates the mode of the target IP address. The system automatically selects an IP address mode based on the cluster network type, for example, IPv4 or IPv6.
                                                                                  • Destination NameNode IP Address: indicates the service plane IP address of the active NameNode in the standby cluster.
                                                                                  • Destination NameNode RPC Port: indicates the value of dfs.namenode.rpc.port in the HDFS configuration of the destination cluster.
                                                                                  • DBroker IP: indicates the IP address of a service plane where the DBroker role in the cluster is deployed. The DBroker is used to transmit data during backup.
                                                                                  • Target Path: indicates the HDFS directory for storing standby cluster backup data. The storage path cannot be an HDFS hidden directory, such as a snapshot or recycle bin directory, or a default system directory, such as /hbase or /user/hbase/backup.
                                                                                  +

                                                                                  OBS

                                                                                  +

                                                                                  Indicates that backup files are stored in an OBS directory. You need to set the Target Path to the OBS directory for storing backup data.

                                                                                  +
                                                                                  +
                                                                                  +

                                                                                7. Set Maximum Number of Recovery Points to the number of snapshots that can be retained in the cluster.
                                                                                8. Set Backup Content to one or multiple Doris tables to be backed up.

                                                                                  You can select backup data using either of the following methods:

                                                                                  +
                                                                                  • Adding a backup data file

                                                                                    Click the name of a database in the navigation pane to show all the tables in the database, and select specified tables.

                                                                                    +
                                                                                  +
                                                                                  • Using regular expressions
                                                                                    1. Click Query Regular Expression.
                                                                                    2. Enter the database where the Doris tables are located in the first text box as prompted. The database must be the same as the existing database, for example, /example_db.
                                                                                    3. Enter a regular expression in the second box. Standard regular expressions are supported. For example, to search for all tables that contain the keyword test in the database, enter test.*.
                                                                                    4. Click Refresh to view the displayed tables in Directory Name.
                                                                                    5. Click Synchronize to save the result.
                                                                                    +
                                                                                    • When entering regular expressions, click or to add or delete an expression.
                                                                                    • If the selected table or directory is incorrect, click Clear Selected Node to deselect it.
                                                                                    +
                                                                                    +
                                                                                  +

                                                                                9. Click Verify to check whether the backup task is configured correctly.

                                                                                  The possible causes of the verification failure are as follows:

                                                                                  +
                                                                                  • The target NameNode IP address is incorrect.
                                                                                  • The name of the NameService is incorrect.
                                                                                  • The table to be backed up does not exist.
                                                                                  • The format of the table to be backed up is incorrect.
                                                                                  • The tables to be backed up must come from the same database.
                                                                                  +

                                                                                10. Click OK.
                                                                                11. In the Operation column of the created task in the backup task list, click More and select Back Up Now to execute the backup task.

                                                                                  After the backup task is executed, the system automatically creates a subdirectory for each backup task in the backup directory. The format of the subdirectory name is Backup task name_Data source_Task creation time, and the subdirectory is used to save latest data source backup files. All the backup file sets are stored in the related snapshot directories.

                                                                                  +

                                                                                  12. + + +
                                                                                  +
                                                                                  +
                                                                                  Parent topic: Backing Up Data
                                                                                  +
                                                                                  +
                                                                                  + diff --git a/docs/mrs/umn/admin_guide_000424.html b/docs/mrs/umn/admin_guide_000424.html new file mode 100644 index 000000000..5a481754a --- /dev/null +++ b/docs/mrs/umn/admin_guide_000424.html @@ -0,0 +1,52 @@ + + +

                                                                                  Restoring Doris Service Data

                                                                                  +

                                                                                  Scenario

                                                                                  Doris 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 data adjustment in the Doris, an exception occurs or the operation has not achieved the expected result. All modules are faulty and become unavailable. Data is migrated to a new cluster.

                                                                                  +

                                                                                  System administrators can create a recovery task in MRS Manager to recover Doris data. Only manual restoration tasks are supported.

                                                                                  +

                                                                                  When executing backup and restoration tasks, you need to manage unified restoration points based on service scenarios to ensure proper service running.

                                                                                  +
                                                                                  • This topic is available for clusters of MRS 3.5.0 and later only.
                                                                                  • Data can be restored only when the system version during data backup is the same as the current system version.
                                                                                  • To restore data when services are normal, manually back up the latest management data before restoring data. Otherwise, the Doris data generated after data backup and before data restoration will be lost.
                                                                                  +
                                                                                  +
                                                                                  +

                                                                                  Impact on the System

                                                                                  After data is restored, the data generated after data backup and before data restoration is lost.

                                                                                  +
                                                                                  +

                                                                                  Prerequisites

                                                                                  • To restore data from a remote HDFS, the following conditions must be met:
                                                                                    • A standby cluster for restoring data has been created, and data in this cluster has been backed up. For details, see Backing Up Doris Data. If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same MRS Manager, mutual trust has been configured. For details, see Configuring Cross-Manager Mutual Trust Between Clusters. If the active cluster is deployed in normal mode, you do not need to configure mutual trust.
                                                                                    • At least one DBroker instance of the Doris service has been deployed in the active cluster.
                                                                                    • The time on the active and standby clusters must be the same, and the NTP service on the active and standby clusters uses the same time source.
                                                                                    • The value of hadoop.rpc.protection of Doris must be the same as that of hadoop.rpc.protection of HDFS in both active and standby clusters.
                                                                                    +
                                                                                  +
                                                                                  • If you want to restore data from OBS, you have connected the Doris cluster to OBS and have the permission to access OBS.
                                                                                  • The database for storing restored data tables, the location for storing the data tables in HDFS, and the list of users who can access the restored data have been planned.
                                                                                  • Check the path for storing Doris backup files.
                                                                                  • Stop the upper-layer Doris applications.
                                                                                  +
                                                                                  +

                                                                                  Restoring Doris Service Data

                                                                                  1. On MRS Manager, choose O&M > Backup and Restoration > Backup Management.
                                                                                  2. In the Operation column of a specified task in the task list, click More and select View History to view historical execution records of backup tasks.

                                                                                    In the window that is displayed, select a success record and click View in the Backup Path column to view its backup path information and find the following information:

                                                                                    +
                                                                                    • Backup Object: indicates the backup data source.
                                                                                    • Backup Path: indicates the full path for storing backup files.

                                                                                      Select the correct path and copy the full path of backup files in Backup Path.

                                                                                      +
                                                                                    +

                                                                                  3. Choose Restoration Management and click Create.
                                                                                  4. Set Task Name to the name of the restoration task.
                                                                                  5. Select the desired cluster from Recovery Object.
                                                                                  6. In Restoration Configuration, select Doris under Service data.
                                                                                  7. Set Path Type of Doris to a restoration directory type.

                                                                                    +

                                                                                    + + + + + + + + + + +
                                                                                    Table 1 Path for data restoration

                                                                                    Directory Type

                                                                                    +

                                                                                    Description

                                                                                    +

                                                                                    RemoteHDFS

                                                                                    +
                                                                                    The backup files are stored in the HDFS directory of the standby cluster. If you select this option, you also need to configure the following parameters:
                                                                                    • Source NameService Name: indicates the NameService name of the backup data cluster, for example, hacluster. You can obtain it from the NameService Management page of HDFS of the standby cluster.
                                                                                    • IP Mode: indicates the mode of the target IP address. The system automatically selects an IP address mode based on the cluster network type, for example, IPv4 or IPv6.
                                                                                    • Source NameNode IP Address: indicates the service plane IP address of the NameNode in the standby cluster.
                                                                                    • Source NameNode RPC Port: indicates the value of dfs.namenode.rpc.port in the HDFS configuration of the standby cluster.
                                                                                    • DBroker IP: indicates the IP address of a service plane where the DBroker role in the cluster is deployed. The DBroker is used to transmit data during restoration.
                                                                                    • Source Path: indicates the full path of the HDFS directory for storing backup data of the standby cluster. For details, see Backup Path obtained in 2. for example, Backup path/Backup task name_Data source_Task creation time/.
                                                                                    +
                                                                                    +

                                                                                    OBS

                                                                                    +

                                                                                    Data is restored from OBS. If you select this option, you also need to configure the following parameters:

                                                                                    +

                                                                                    Source Path: indicates the full OBS directory of the backup files. Specify this path by referring to 2, for example, Backup path/Backup task name_Data source_Task creation time/.

                                                                                    +
                                                                                    +
                                                                                    +

                                                                                  8. Click Refresh and select a Doris backup file set that has been backed up.
                                                                                  9. In the Data Configuration area, select one or more pieces of backup data for Select Data based on service requirements.

                                                                                    Configuration restrictions are as follows:

                                                                                    +
                                                                                    • There is a database with the same name as the original database of the selected backup data in the Doris of the cluster.
                                                                                    • The backup data is restored to the backup table with the same name as the original table in the database.
                                                                                    • If there is a table with the same name in Doris, ensure that the structures of the two tables are the same, including table names, columns, partitions, and materialized views.
                                                                                    +

                                                                                  10. Set Original Configurations to true, indicating that the configuration of the backup data, such as the number of copies, will be used. If this parameter is set to false, the default configuration is used to create a table.
                                                                                  11. Click OK.
                                                                                  12. In the restoration task list, locate a created task and click Start in the Operation column to execute the restoration task.

                                                                                    • After the restoration is successful, the progress bar is in green.
                                                                                    • After the restoration is successful, the restoration task cannot be re-executed.
                                                                                    • If the restoration task fails during the first execution, rectify the fault and click Retry to re-execute the task.
                                                                                    +

                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  Parent topic: Recovering Data
                                                                                  +
                                                                                  +
                                                                                  + diff --git a/docs/mrs/umn/admin_guide_000427.html b/docs/mrs/umn/admin_guide_000427.html new file mode 100644 index 000000000..cab1bb382 --- /dev/null +++ b/docs/mrs/umn/admin_guide_000427.html @@ -0,0 +1,66 @@ + + +

                                                                                  Configuring Doris SQL Inspection

                                                                                  +

                                                                                  This function applies only to clusters of MRS 3.5.0 and later versions.

                                                                                  +

                                                                                  Scenario

                                                                                  You can configure inspection rules for Doris SQL statements on MRS Manager and set rule parameters based on your needs.

                                                                                  +
                                                                                  +

                                                                                  Prerequisites

                                                                                  • The node to be connected to the Doris database can communicate with the MRS cluster.
                                                                                  • FE and BE instances are normal.
                                                                                  • The MySQL client has been installed.
                                                                                  +
                                                                                  +

                                                                                  Constraints

                                                                                  • A SQL inspection rule is automatically applied in 5 minutes.
                                                                                  • Interception and blocking rules will interrupt SQL queries, so you need to set parameters of these rules properly based on the site requirements.
                                                                                  +
                                                                                  +

                                                                                  Procedure

                                                                                  1. Create a user with the Doris administrator permissions to connect to the Doris service.

                                                                                    1. Log in to MRS Manager as user admin, choose System > Permission > Role, click Create Role, set the following parameters, and click OK.
                                                                                      • Role Name: Enter a role name, for example, dorisrole.
                                                                                      • Configure Resource Permission: In the resource permission list, choose Name of the target cluster > Doris and select Doris Administrator Permission according to the permission you need. Click Doris Read and Write Privileges and select Select, Drop, Load, Alter, Create, and Grant permission in the internal row.
                                                                                      +
                                                                                      Figure 1 Creating a Doris role
                                                                                      +
                                                                                    2. Click User. If Kerberos authentication is enabled for the cluster (the cluster is in security mode), add a human-machine user. If Kerberos authentication is disabled for the cluster (the cluster is in normal mode), add a machine-machine user. Bind the user to the created role.
                                                                                    3. Change the initial password.
                                                                                    +

                                                                                  2. Log in to MRS Manager as a user with the Manager_administrator and Manager_viewer permissions and choose Cluster > SQL Inspector.
                                                                                  3. Add a rule for Doris by referring to Adding an SQL Inspection.

                                                                                    For details about the rules supported by the Doris SQL engine, see MRS SQL Inspection Rules.

                                                                                    +

                                                                                    For example, add the static_0001 rule while setting the threshold to 1 for the Hint action and 6 for the Intercept action. This rule detects a SQL statement that contains more than one count distinct.

                                                                                    +
                                                                                    Figure 2 Adding a Doris SQL inspection rule
                                                                                    +

                                                                                  4. Log in to the node where MySQL is installed and connect to the Doris database.

                                                                                    If Kerberos authentication (security mode) has been enabled for the cluster, run the following commands to connect to the Doris database:

                                                                                    +

                                                                                    export LIBMYSQL_ENABLE_CLEARTEXT_PLUGIN=1

                                                                                    +
                                                                                    • Directly connect to the FE node to access the Doris database.

                                                                                      mysql -uDatabase login username -p -PConnection port for FE queries -hIP address of the Doris FE instance

                                                                                      +

                                                                                      Enter the password for logging in to the database.

                                                                                      +
                                                                                    • Connect the DBalancer service. DBalancer connects to the FE node to access the Doris database based on the configured policy.

                                                                                      mysql -uDatabase login user -p -PTCP access port of DBalancer -hIP address of the Doris DBalancer instance

                                                                                      +

                                                                                      Enter the password for logging in to the database.

                                                                                      +
                                                                                    +
                                                                                    • The database login user is the user created in 1 and has the Doris administrator permission.
                                                                                    • To obtain the query connection port of the Doris FE instance, you can log in to MRS Manager, choose Cluster > Services > Doris > Configurations, and query the value of query_port of the Doris service.
                                                                                    • To obtain the query connection port of the Doris FE instance, you can log in to MRS Manager, choose Cluster > Services > Doris > Configurations, and query the value of balancer_tcp_port of the Doris service.
                                                                                    • To obtain the IP address of the Doris FE or DBalancer instance, log in to MRS Manager of the MRS cluster and choose Cluster > Services > Doris > Instances to view the service IP address of any FE or DBalancer instance.
                                                                                    • You can also use the MySQL connection software or Doris web UI to connect to the database.
                                                                                    +
                                                                                    +

                                                                                    Enter the password of the dorisuser user after running the command.

                                                                                    +

                                                                                  5. Check the configured SQL inspection rules.

                                                                                    use __internal_schema;

                                                                                    +

                                                                                    select * from sqldefend_rule;

                                                                                    +
                                                                                    +-------------+----------+--------------------+--------+-----------------+------+------+------+
+| rule_name   | is_group | group_or_user_name | action | threshold_value | p_1  | p_2  | p_3  |
++-------------+----------+--------------------+--------+-----------------+------+------+------+
+| static_0001 |        1 | A                  |      1 |               3 | NULL | NULL | NULL |
+| static_0001 |        1 | A                  |      2 |               2 | NULL | NULL | NULL |
++-------------+----------+--------------------+--------+-----------------+------+------+------+
                                                                                    +

                                                                                  6. Create a database and switch to the database.

                                                                                    create database test;

                                                                                    +

                                                                                    use test;

                                                                                    +

                                                                                  7. Create tables t1, t2, and t3.

                                                                                    create table if not exists t1(id int) engine=olap distributed by hash(id);

                                                                                    +

                                                                                    create table if not exists t2(id int) engine=olap distributed by hash(id);

                                                                                    +

                                                                                    create table if not exists t3(id int) engine=olap distributed by hash(id);

                                                                                    +

                                                                                  8. Check whether the static_0001 rule has taken effect.

                                                                                    select count(distinct id) from t1 except select count(distinct id) from t2 intersect select count(distinct id) from t3 union all select count(distinct id) from t1 except select count(distinct id) from t2 intersect select count(distinct id) from t3;

                                                                                    +

                                                                                    The number of count distinct in this statement exceeds the threshold configured in 3.

                                                                                    +
                                                                                    • If the number of count distinct is greater than the threshold for a hint but is no more than the threshold for interception, the statement will be executed successfully. Run the following command to view the detailed prompt information:

                                                                                      show warnings;

                                                                                      +
                                                                                      +----------------------------------------------+-------------+------------------------------------------------------------------------------------+
+| QueryId                                      | RuleType    | Message                                                                            |
++----------------------------------------------+-------------+------------------------------------------------------------------------------------+
+| stmt[306, 887f43753bb749c9-b6ed36350f9454a8] | STATIC_RULE | static_0001 number of count(distinct) in the query 6 more than the allowed limit 1 |
++----------------------------------------------+-------------+------------------------------------------------------------------------------------+
                                                                                      +

                                                                                      887f43753bb749c9-b6ed36350f9454a8 indicates the query ID. To view the SQL statement corresponding to the message, run the following command:

                                                                                      +

                                                                                      select * from query_history where query_id='887f43753bb749c9-b6ed36350f9454a8';

                                                                                      +
                                                                                    • If number of count distinct is greater than the interception threshold, the statement will be interrupted and fail to be executed and the following information is displayed:
                                                                                      ERROR ... detailMessage = static_0001 number of count(distinct) in the query 7 more than the allowed limit 6
                                                                                      +

                                                                                      show warnings;

                                                                                      +

                                                                                      The statement output is empty.

                                                                                      +
                                                                                      Empty set (0.00 sec)
                                                                                      +
                                                                                    +
                                                                                    • If the action set in the SQL inspection rule is Block, the following information may be displayed:
                                                                                      ERROR ... detailMessage = running_0001 Num of result rows num reaches the fuse threshold(1000), so cancel the output
                                                                                      +
                                                                                    • You can query SQL inspection details in /var/log/Bigdata/doris/fe/fe.log and /var/log/Bigdata/audit/doris/fe/fe.audit.log.
                                                                                    +
                                                                                    +

                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  +
                                                                                  Parent topic: SQL Inspector
                                                                                  +
                                                                                  +
                                                                                  + diff --git a/docs/mrs/umn/en-us_image_0000001392574002.png b/docs/mrs/umn/en-us_image_0000001392574002.png deleted file mode 100644 index 944b5296a58ed33df1aaf888b33a17ba09bed2f9..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 90492 zcmd42bzB=?w?0aNLUAY*3s$5Qw?c4Ap|m)ZV#U41-62@f0;RYYiWYZw*I)%gfZ#!b zOYmI!J->6#`@Z-7dq4N?Pm-Bgvu9?{%HC@~YprKTsHwaoz@^4TLqj8we=qw14Gr4~ z4GkmX3D$!|%|r1A8X5zdysY#`&kV$pk1wrTChB-@vl<~Q zyxfGhI{WM;Z#*a(%3ZZ7bZwqF8Faz43>uE~v@W}FO9I|M>MB#y-?YU2`oVj3>b2t3 zmcPhQ6ZrN%#RV*%mM0(IeRJiRHzp!*nt7-{&YTMNl{8wno1G8;w=!6}*S^aAU)@rp)ltCb}b-i+(oYJ^a*>)uKGkU1$ydgy>55!d%%Ly;C zb==pU)D)+(i}U=cmnW;=9E!Tc;Ciy5!|>;AKi)B?7!6CJOXj@JE z8T;r{a$BrL{+lv8F$J8W8F{o`${oS7S*i-fJaX;CsOqui-B&kB9nPQLuF@CHAK{EX ztsvd@OFj}3H2z3o5?d+n?vOH{upDWqh<9G?CfYb;s2YW zKD;376^v@r@ws^-Ratg~UmtBJ*0UVLeBA<+Z(WX7C-Kxy)Zj+JqmFpQ{Cju&R1cW1 zQ&Ig09J8>s`0DXym_9-0vg#d~*)$!Zy^_>8gSptwS`Yc;b|ZEI5c=8l!vdkcKkhT2 zfh>$vETWv|#-9r895|xdg^XL@xjT_j=`fqE^!jkayScA%|JY2G9$)S_6C^H(YU7u% zV~@%C7c~xk6kkE=?>S(yGY}Hgh`HDcf(1#C0i4K# zC*uW4_oYpt$aRSllAiT6HK1j#taHf?5@EGc7GpAv?NMv`(FZ4FjaU9r=Zb>|i95?S zlag*K1rz1h-VIFM=QioSPU3$I#e*m1@z(lp-keD`#b?p_M8ukP=nUa5ng~c2jVn3{ zt2;JLRb(pmdGO>O4rMZ1Qmk7ONpm_+Twsr9D$6@i3eXHJ&3qT&`rIpLQ20L@pz#mo zke)<5LU)taf9urQU$10(XBfIL9O3$yQsR7j&=||Kk-a;m9W!O99eo@O(HH940RLI@eQ)v5r^~lwy#|l>$`u@PxUy(J>1Z^oLr0zh z&AVy^fYn6}Q_R~@tJj)nur;j0LkG+2EZmFGZ^Ajw@jsR)LGNqr{4ya?F+Ew@%DLt| z+!axsS1OinH?zPZJy%=rOn3g^TjK#%*k@>>C{_yAvBcL{NY{nOy)RQ4M~7-vS((mK z*r%AA5A1K~JC(6lJH3N;kl?)5eKSw?H@)}wVrO@rx%(qUv*mgIUYfIjrI56PT&XMe zN|R?6r=r_ZNdGrs%~|;}Vawx6d}|k+xobl%M+oo87)`yx&$MAi#y#xAY1OE~AqiFf zjD2LHXvG>}Zn}=UBeRPnN#gQMK3N=9wk0oYs9pNgU74#Y9XR20c=Zv;6A-<(^9hb1 zo!eUUFzv;02I%e7c1 zlk&D|6$n!X2oMjPVONEU_liYUa@81%2^dWF(I)8E)Bk$K6E|pKrq%bvHxCa*)rNVP z-Z#-xH$6QhU+Fd}E@a?{MdEO9Md{M=IbCC<$Hm&~;@el>lR(xYo5R!s!{HW%3zn|I z=5R9H`7LZ47ek6CSQNNZgd>e(D5=DJ8+?$20T_C@L{_E~UQ$45^HSj~wc&}>`HKjN zB~O)9<&|7gr)-@tc%FBpq!+&ol4i|sFgQi+%=O489Y^YXtLXF_OA+1uzKxFG^U{kI z=`Hb-M!sTvpO;@^P4F$=uGuj>E!;}ZW~oGAiq1+ZTpDGE=1}%>SpyBCL6BqDQon>j zS{}7~Rk+6WR{`gRm|EA#t1DE$zdOCV@c5(w3~Qx~0~A^1K{T&|vwCuP&z6Op%S+w^ znX+~PvOB%qdEA+$_Z`~9|K99w1xI|~qk6rmy7%%0$S-KS0ceIK0)OJVhO&GF-7p5J zB3|6i0A@;Wrq62IS>5>^$9Src7bK15U6qn(wWw^?aQ_>5MBvN55-FukWt9TkLn}~B zT;=gALA9H79#bvyN5sq1@~BL(268M4ZC($hj3|wY25o+MbvyQ01PTG2W03h-lW4-6 zl2Yr=%q<18mG&CwS)5!fLGV4_{I3rK=GR&t7SA7=Ir+@t%mLS44ZdXNbXz& z{W$IMrKi;5`=xc2;;lRFyKl|(zKm8a&Fz;i2&)SdO!1E>q*Z9*nu=XiTLpbCPGrSB zu_l0f1Oj^)P&2-p;twxa00$og8GoCq$WVqzaVl4EEDO9xUKfVn(py0l=Q3paJTlFm zs5vj=$X>Wk`OkJpt9lM+)5Q(JG5wlx1k1n#3qlp$8TA3NqnyP*ZGkxj1gV|73yCwp zivD;CO!k&T8eapbh~q(ld4Ma6#oh^eHAdfMmcBHDlyIB71;3iOa33_GIy^F8vsbU# z3CNZAtt_5Wcv)6^dX+%(!l+&nc{%zW8?C=U?K=eLVAg(H{0!~J$Kd)=@Oi4A@86MB zTHt=cEZ)iRcMv&;u-k9v=T#*m#HQlL8P}fk^u0so!;lGbMWS`l%lmG#4i-f2A>o$6S8H~H9Lg-)W`IN`-h14v{EcXua9=$q)F z(i!wrs@KJeQ)!@FZc0~gXbI%RmwmYz--?R%3oCTd_}ofWSB!6%$}AEHoeXa5_Y7); zjKKX|2dJYm+2otsiNJksA4S|>seE295wVCj<7puAX^O6{$c(b;;uL57qv{2E02#EG zU5B_>o&6lwqk6L0K0Y57(!QX({5JNd%@Pr^WUld>G?z2q%`^njfJ+${5AjV0e(g;4 zwcQK9H4=}W;>nOMwfa8ia7WLJzbo1NeRq0Ub>9ypy;ltys1rNIRN*yN|Fp|;G)Y=? z1+hZ&glmKHKvo>j=tYwt@XT+hTC4@`Cfd`!i?e10Nu>0e-}B|$1Gz}Buhh9Bg&K16 z)N{Q~s8tGu9#aE{LCgp!Ak>7%Uc-^+&nU{{&qVpk=H@emq{0 zwgbB&EdL`3jSW(MI37Lw-YCR|nHE@wS86MqFA z69ymHcfR(YnfiK0uQ6f+^LyeT!}8A)#>L{sJM_aRpE1@J26rxgdLx11+Ise)%kleK zGg`S2K#Y#oeKFMi5c{Xe4x8<%7NMPfWf^|4WXUL%q#1A3z2(^f$1Al zJiAzjK27qK6b^7MqLp;#>I9pw{pM9*O{_AuBhtbDYdPEyo-zW?yKNKNlaQQykYryDwMi<(WYq93qDyuBhd!J9pD_!$>9^L=Ran z7sQ+C-m6&KOSie9tiaNO3$Y+m>d&2p%aFL5o`$8<;S+LzmnF}gFpR0PaE_iCMK_o} zD~<4A@f;^4OJPmq%h)lqzk&D>lHAMZ2g?$eRxlOHl?AZI`CZdaSlUT)_EQ_} z7Z{CAkLo9W6L>yMV=L9CtIMqnA5{u+PPHI@B{<)QlSW306fGw6Yy3)H+89Q#HjOVL z#uph>9?l-S9`x8+cV^6Tb`O1TF>U(q&TpPt( z(zWnsXSBxViH(h%bj0(QWXJ7-w;p@WqF?Fu zi0E!ZAaz5MRu&zfxR!LI3%C3td#B7TPfm6SQ#LK-1uA)J?EaaYNvgI?eT%{77p}PG z*Or+e3uIaUToX}A@pC`_{+jCVto3*4l-80l)m{Tnjcuywf7$j_N^Tj!vlxqLI#?!D%-m%eRuJC`x74(I?ab*)p; z=j3@vY2S74P)n=23VhqYE|Ca+Yobg-D-SRLj~H;q-`MaJ8uY`AKTv-<{^xCoN^`?l zccgObo4khNz!L|909|eL*SBNb&D%KJ#(kq1JE6e9h8MD~prO1{ zSSe4Ji!DLKtpAz_2&kIXd6kKoq)fvVD;+`B=hP!kB3X%p`+fiez^GK!WY?wCYudY1RF^?e$RiQ3LzLd;`)+z z2#6)M8^>JNn2YmN1gBhU+_|tGOuJnzeZ1fJuo#`#vp}Qi9%^^t^Bs`KMOH~$T}??BPHtR}fLCL$k__GdkOxD1cL_*f625~U1LpTK8{vOU6RsVz)nt4< zth%mV^n~oPQTh|frPBZEj#a1Xe0dy{DxxsnE)@E1o`5&9Ek*N@732ebC`{lskFD3j zIN>VeT=OzhNWssHa2>#6Xq8zksr`*N;FMWpRX|Z>b-cs;A~?J7e$Ge<1aVPdSW!uS zNyoq5i=H~w3OV$VLSPcZu3-CT;!W|rcNJ4r*U5-$xKWkglAmm(@)L6fuCo?1=GzyW zK*J}UB`}}wZ4I}fy*wTh9!qkBw#zXM)tGyDQI*!WI-xb?YA^;pDIbpD4)3p7f&ePd zX&m#=Wo_BqVIU$*ez&fnI>br}b$E6=M~_p6!f;qR??7u*EoWW)m_Cl~w-+b%)PGyE z6l!D+hb@m?97?>0)i=l|Gz&=UKb4Kd7tc<~CS0+Tt)-!f{{5pU?Jsw;OlTi7g_4cyqC$A4Cn-?i zV4B8#5YAm~YSN)pnt;(^o8G*~I#ccKou91#Is5EBPo+l>>Cl}>)aU5rP6}0z3%CsU zbYTHIT;h`5N6G`(C4r6hgp~Dzx!Q4}OU61XIQnc6s)UH4fYe+_qp?da$>uGqGVUR# zVW3T^%N_`<06AB&QcdXuQ>tG?<9>|>MmprJ)wfc?$Hs7f&#pP#h-z{OSbP|*0sp%F zL`mNHI0gCWH=UF~Mc0B78qgu@M_JRO#l?#*)a6{wHBIN~`Bf9eWGh;E&Fw&_!!$F8 zp3Y+~yT=&VcgbbhodjoZKZ-Y@)m*U=zAA&ip4O24O`+Ce5=VLjo!`gguf}M6@HiYk z9gcQ55yR3F6D;bs?b#WpYO^qu-}$2fYmDm61T)tW$xiz<>RXxoQAcB^Ci~vM9EIS` zcCuK%Gges9^mdjOqam(@e~@K){>m7y95_5<-qsVW>833qPmf=@lR||cP~Pgl7Ai^T z8X{Zzco7dwKX>wA>t3j}@putRy)AA2-O2M_Z$|>j#)zTv)4Ca>G0UL%)Jh_!9BcSs zWO<9-SFoZGJni`fgJtNH!$WUQ3~srO{(H_cNhsY~ei5N`=n%7F*#4the(8R);d!Nr zrV9N{dK8X$6FPiYVgc@G>s;~fmmeKbezpeFjL?&O0te_W@yyeklA|BwRGW_DSxL5IDIDNSq3(Li8)Snh^=c?eN zjzV~}4LISbjLqAm8vUW(_zwzNnSm%KR^Cf`un6czqB=O2L$wDq89{3A!rWyl1-d-? zqEo(lb8_c^Sg!!xx%Qt;z&{kE-^ug&)qfJBY_vNlRD&InxiyY5ha_){^6pf(xzFCvGY8L(dfnk|S2R zZhyw=lAtB;Fx!$BS&F5;I4e@$MBR{;>#8UOksJ|27ZgxZ5-O$+*{5{I(2Jw$+dpp; z%5GjR69G-bOdpKnaWZuK=Gtt>;@#SBo_yD(cSpY4e!P@@j;XyydwIy_u&RsLdyKhK zT(yhfO;6R|11dVk)XWzblcx|=KOIe0vsM6f4&l&&+>h_A6Qv#ZdM^;!Y2ifuF?McjkW5}L_$UjrlR z)azJ&<3#*htn-gxNShN-f9jPt{X*DL`(!pESb5QIU0%*d8TwQFAiq{1(98IV82<^6 zL}mwcNIm)0sz^B&ct^!r9u?!~=`^LS5zDFrg;q5*Xf!v{9eyobb12H)SX8pK8MIM9 z7`8RJ^lceL(H*Nf zF$D5W40Kl1tDkIo!(BX-s16jYD))0RBtFst)7Ka#wld%rE>_2uW&ybyJoRlp7iM-} z@+G%fj+BV{)o8?CQRz0;UCIFYP1VzEq+&hjzDu~<^S8{l-JV{`Th{#$RAqntiKMf6 z539LC#bOMLSLKnt7&Q=*S~0X^m92sU{(krE(``9myG^u4rBR%zB_%|(-R3ggGvcx`gZuv&0F*v(uxx<@V zo^a_$JM=KVf9x&ygx~7a$oJ_c?Dl=vmz*%8d{jD0Ah11F{R@W0ScwZdn5~$@*to~3 z5&L2?o6yiM*Jj;zH<>5z+im#f=NnF#=T>GBwSK;FU36_$nT`Q`CAICz`|*Ep;-f5Xlk2gO@kMq9mBA1;jpN~SYE)`s3W`n7H(n}`?)$VsWOY^SpS$h9vXXlkC z_49Tjjd!hkj)tlDlHn}eX@3|8=`vi}5_JzLd8yZ)cD*@-JgE-OG)o(L??LD6*>)u8 zxnw{?X>tqg3|)6@umz`OUE7-P?*;ndvlJGNC+h4jwjc>i=U%O(0bA|<8pgPxH8z}8 zHadS0a2C$AkbPS+BNQIi)_CiL@3AFW*x?=C<(EHyd<w!t0|sLpWQ9qKtDW7?_bC}lj~s9>ri4LkZ`wsE&IN%@uz;YiaX z;Fh0ySBP9q6Rh$%FV|JSEku%d=X$>xxfvIW=?x5Y-Lku^G8nJA?NpD?%3t6|zHBZT z!BerRC|RqDN+LdgMptt+*7R;tTT96cbs1K1A|&|Gi1)TPfoDQr>HHI`D>5Wl;E4D7 znr{<~K%T*c_jqsDrvLvI_k>PBG;|z8QJ>~*_5c0}- zI#_%d-HJSgalDe~$eghegQo}A)GWwz@hd|bAFwgvJv!4$m!H01mG*_zi|Zva19#l^ zX&8L;Mg=Cl9v^1?Mp_^I#l>-qZ3HnFlBgo1%0@;3^tE4P1$PT}a0{q*cOOOP03<20 zNUa^Sb<)4I%!IAdk5t>YMgbhbBMBdQZKApa-6n5h3>k#NxgiCKZcz;wES_Vs)d`tF(QwJzR16AW!Q@ma`mEkX2rSZ+#0ArNcn z`Qq_n+JWT>lAjbqwY!rhylZ8Rw;_I@YOf3i-95> zKhBcCr}}f~#r$J!K2MA!u0=CfYz;4W78Kxd-%2-oC=i|5iFbSD9!X9Wt#N6Ix+7Z- z)885rm&fpmjrNR{A0tw{O{{zKd->(x)^5#Orzv zX=hQ>yPj{3$8!sa$M^}AdliOh*gs%io(aU?+-Tg_L#G@C|KylYSl4`&kY@2k1k-1 z5hG?5;=OMXvW#{i;<sBGSV8xfRY@?BPaewfDC1O1VPK^OU}h;(w3SvJL^u)V-klUd_79L<*;Yp zl;poV7|BQ^>0TE2sJ~R|f$rDRX{vr(eRP_$hL%~UNs7Cc=Eg$VXZW-%)m*ehBAixv zMZ{vf5t?3v;B&&@AYT(Zr3`A2l3Jr|isyS#ZlfY{VN6yc5#JvFdB3OTC*6Y^J6_~G z^#HzlP;sQ&H~s4&^h@$XzXe`4pS&s^?@}M}NnWb_);X{x@Bjo!7LPa|s{XpHQTd>M z;T#$VkQ(yMKKIUhIy`hZ9km&oDi%}~3iwcGU054(Kq;H;g$KqFoOg7{-i&)m z1#Ys6WV7@zOp3g}Y^eAr$fsS&6mb^Q(8Z>jJ}5!858+h-#$L0>Z5MRxI zXEM(A>tNJtCexiWQBgGyK3%bT)j;8#R27`sN?h~%$?1OASxQeiQWKr{fQrH1@+*a% zBa1C!hL6Tf!~mm*jgO|m`653s@C%@k4k|Mc-*CE>i~DWbQiC5vScBSNzD>-ZF+`~^ zdzrJgx58-G+Qx~Xof+&1OcmS=f^swVfu*nr1%&Hv27R5YNr90V^!OEBqJU8!lBeIt zmaDA8daJXaV)YN9KI< zFJ>rV@Q4}z+h@}s0|n#5m5)yb(g-@9Rfa@)rr=ld)fkt9u1* z$Zwjfr3r=!9SramBT6~6)LLGo=8LY)hsIO14iat9C7~UdQ-LJ`bN89}nao&&W3^*( zqua|{32JWqdhw73q~zDD4H3*N{jU`>VG#aX{XLk_`#TGGPn&Rl0uRP4VY(eIXRhfN z&DGa>@$p>3iRFV^Qlzx*+NA>Ay)1haVqw!XkDf5B-=4>$AUy`kr5#}); zYSOL+$31JpmN0L;8pm5)EzcJccWgKOGky%8E5@?CR^Af8F}I>lUTR3|Joz)jL%&Ha zIqbIMct=L@7d%i!m%Kze&C1RzAC8NbzTY~C-H|tDRSIoZIGQ6c@y_(A3x#&mn0$j& z4HDt@!47D(1fBRPx$&ShhUZf;&Ef8tokEpN_PJ&Gl*__dyOpH1%41dwDgaXawSwx2 z(a7REj-P798$C_F?vA9LyENUUsq+{;zjlh*KVpxo^Yiu&RkV&L6~zC1Eo48sUeIwy zd`+fk>}HAHS!{gn6Zq`ghPb|o8==Y&-0hX60Zt-7i!5t?Dti(`)Z>>;=IB*&RUWo=l>|Qr(@D{UA|*5c6AfLYb$s58-!)0aq{OL( ze-A@cLp3g%%pt9=*>}lYdAr}%cTf;=ab$;lx7~!_%}ApIicB+V>#1ws%i_Vd6hH-% z*nX!MrXw?%8m$BMSaD7#R#vO+#!+ZLe=lIar`DZeR{1k&%|@l$fUfg)mxSnL9oY?<$H*3sM*7+EIY`!Gd}2y@@B{rImi|ee25=on?k1rhi^luxaFRhQHB&Fbt)KbJjUV){~!(s1G_4eo^na4z@7}z_< z*5EdfX*A47iWd0;pO{Q%pv_Om=0$_PCHwb1J5g)7$Bt&1B|Fhe-IdTtJqBle*j7USja_hp;Iq|09CHUTGp5)iKM}|^kD>%-WsnX( zrRas-`^PkyuWPKh@T1RNgynvnZ>n8;O`O`l;Ws-Y1jKvJ5zn5KR?qD%g!4!d!a{RN zq~cZ3gdtl~Z+nIs**gke%=*nH`?^v$zbj@Xa^! z#hZkNG9nLLf&i1i#Ub1k@-;nYe9Nk2**S(_lmp%aIUx1NIT?SBkKu9hLU_l#g6)Xd zIFhH%Gz{3;W-)z6jS2;E-yT2fGP^n;VKrl%KS z2LaX>vaFF;aovR5*|D^5(mv&>e+pX=NB&nz)~L&dUY`tB z6HZ$MKaT}`?AL*jq{@m7T+JC$JY(oX_%PJaCs2s=9z`An@v78yRYhV(n(2 zrg-7(ZDdmB>pa%?@Fg(G69A>g<*E3xh1yt#2{!Ra*+v8Z|!#M4gD*$ry`_G1(8WrsbROZzcjKgWeu0q1J#p`pqU z3#-Om{Iidswc3oU?v8o6TGsbVUk3PZ4!~*`BVaYu?e5upKe?>V$`7U{G>#8PwAX3UIgJ8aCG=aWF$G`2NlmVhE^vjE%%$^in3%C^QeCN zC4-Ppzn{FS7#)&TvRLc`QVcRapjW(Xmvy?8$Y+<-8l)8J#~aqxKu!g)VSS}_h?5V z%?Ye-J?+I|&?bSU4AU+C4R9)I=Lzhi17Z{8RZAGo-&+8D?Sfiy?-!j2@L`E9RR{SV^dC4av zP;qe?&}BP!<=EdmHRCiVUqbrxr}V?LCtxGeURS+dEZ=~LOg9iXCS7MTBKFvt%!hAJ zVX9*3uq1$uQeajkh0+Vj;-u@j8+tTO)p^v{Re3xc%8P4G4oKo#6&K(LsY@ z-xPI#INFIWqJ_bqM`FL)sMr^87Y}wnE<$8oF43!Usz6?^nqUvi25=bQ((vc!5f#cJ ziT!|gN#%)1-UmmUnGiqEh~k>s`{)^hk5E;Fx~4a*flVWGs+2A32YAo?iNq!DL+lmq z>t^7OboH>28+zbcSfI`My&dZBD?KsK zyZrt~P!=Y2Pwi`8=vo2|35ovWcZ8>EibA_X9fhBEMe04C6MOnVJ!|KY+TgT-> zh6DnUHK*@73W_8mSyOx-3D{QBEy_pTSbYS!QPptk;txf(VhcGGZlWZm<+GL5Jr;*L zGZ^Kp!rQc$l(}kOQyk)|#*48~VyxCZgZ{PNM3(j31HqL0-W^aYT8~Bzs&eA!0ImYuR#57)2bh0*!k7XK519&*hT61zv%j8%uMxo&-`m25}F3Xn7$*@Pp;8h8cT3iBWq%^_J$P{qpO>e-hG}bY>)S z^j61%brIz+itNV`$p|OOfjY2Uy2r3EBq%TlK6IUNnun@BcZBVhKJ6QF*@=8MQ!Ww{ z$srVHWLpT*0|v?!@CGD;*=}qFJJfji>oF zsW`cJl93t^gMbR>@b}s;-dlKc1vzL3*sYul93`0Fr`4I-ujNEY%%-u+@A(_O!00Sx z>!Y3dycv#MQx(QD9X6Uux0bp%I`&!u~Pl}_b23C+EiQ<%H_&-#nW z%^pqKu2PyTCChh8Yh0u^94wk2gvCCmLp@zQsA?C*FWNa)K9j3QU8U3XxD<^2= znJ@A4M9-assj;k;-Z8`mvdPVEC~w_j8F*r71$=8Aan@Ms1uNWAEaO4l+}@LaA09jx zq?NFEq#tm3pyJ(eJCRTa;_Zi)rp`FV=sx?od!OhDw#MvXm~D-XadG(iCbjwSja>di z?wDjUK-#I|>rG}?cb91_PTgC4?qaK=?q2JiK3H-mZCJ=aXMe%x&VGpmh7SiX&bmH5 z4JGJ$c>(qFBz^JLk34Jk`IAN*x_wrYg@ig*ULyQAoieq{;FWINwR}26jP$pd=e~Tw zxmlRycQTZQ+Fk8i4#6ChO#1s{tp_pRi%$4-Ox6e>m=^>l$dHF5dT%VdWo36SMg6h6 zTvg;Eeuml`Uw0C$@1J+N1QQsDgK{rk;`hnVJf5<9*3{Y<=_k9q^ZeufbA(&9q95z5 zz+p@W=E{}S72)|!mr%6&%?bhJ5*b!?%Z-&x`*tw1v#u?wS`q+m&&lAQn|Vg+Yh+1J zjiGLO?teW(poBLpO4{hn$ZXB;ckUtko~#KcOCTzIq}#KO)L|4y>7BUHL5Q@xHah+j ztrkaJEEb2b96#b#ZiEQS*<2GZ*UJM1;)-JdPld;mIlSdb{;f`=J@paIcDL%mQ^U^N zxFoc=0y_3jJ%Ys^y-m&-y{Rx7Zy)2CzNvf12I9ac4~gM2+0JveWom+9uP5MBUn1Wz z(6I8Ae4fAe@o0HPwK7Iu;Ze%JeqEp_WR#9Se{t|!m{W)Ifg~CIm*HsweI;T0Uwki5 zO8cncc%;>1D*`NJBB^f)dQUCR3^tWDSC1oWQ3eQ2)oaUtWu+ZAh>Nu1UiXh{^opYEbjg70U4dGw)-PGB zDq=lHdeI|(@hPl*^xJb=9Ki4BA-^&cX+w!8M^@~!r9=ZjBdSPXOb?+7=S!pNUHr&$ z@#qIo%>3ZI4%_R5J|q?=P;IQN5`z?+7pF!XJOwrNrt`JPj;dHZ(A_H!|ATe>q>VZ9 zkZHrkp|?aR|L(nUSov_aeq>9PvrYu;`11dWS6ppGx+H@M6qoURchi_WhVs4U5sj;^ z$Wpunxle=E9av|wtL!}#{)?kQQb$f}7 zY&OKN{Z_@Qjy{u0ofEP65ucw>(-D^ObOcLxgv{6q+vXkaObkSgA$dr zTwL!^zRbkP!bAzm9@IFoe=Ob`C&b{BuD!;`2G1k2t$U1izv0=+aeh-<6uD8xc;giQ z;t1Jvd|qpErEELh8LrnDYN|raj~LbX;VsNa*%!mikk&~Wp)mikm!|0?xiD}_yAI?&Vomtq5cuzBTpL2GD-|vV_`-tCL8HrUX z9x8xkBOFNe%>?_GF{F`GtWC-IPw_`TI3pvML9O3~J-P$ZY&J>l;+P1n5}pHhgkZ@r z2SO;QH0brEgQo^AK73qra<>E7UdlYaBT-l$N646xXN4%c#X_6ZFwKaSS0bTJ&^d<> z_w!=Rk(seSM96x=nP18$+7OEDu@NQ`YVGdPK@F4;_>NTP>J&43MvJ%h^R*kWj@FhOU>}Zxz-Y?qf zYuklP@gVv%(~T(b5tTy|zXVAMAEx=jr{6=f^ zE$o20bUtT^I#%fL*Lp6Ls5siGtU@5bBPmhfplnt78|8ZCFYesTcp$MtYrc;Hzhli; zp+77BMk%>?&7GMLeh)KB53@kB$VTby2F(zmKQt%JHx9S^CV0D$itFR*Witg0Tb)E+;dmKZ$zfxs*(}nb(>nNC?^A`~J%8 z2}WIsvw+;TjueK-JTtijK^FjbE%tIdD~t675tKzcm}tQgB{f`odsrA@kxJdrfnco~9I=Z7X|YxN`J)ZOAO_Z33EI9yagcA zDQqGA$F&TbdzkLlo)c{jc$hT4Yo{Ow98ETqB*}Vu7Oa1x@F20_>M{@u(Io?j*p0gn za}J0_cBWmKt!@D>!B|iCB^9`#vFf5HRkhgq|7YnySd~Y-6{G-Obbzp!er!d29OElF z>w0!Hgq`)XybaEKVZYn>JMv|RzwWrtRfWaL6;B5Iqa!WLDnDrW@|U+6-dc>fmi=<; zS5ZL%Q?Z5PEGK+Ri-36>+P_|+2668>YA2#GW+<*gdoo#$?86Rnz07uLtG3AmG*6V%&YKgwYd}RvBFZ zjDbAsj?u%m`=51l8%xYnno92~vU4FAn7cuZk!u0bcB#GBZTNMGq&v90aTC2tCVDTb zFj!IoDa#{y3wYu&c!|xMGv0Q4W%n*Iq{|HORitnTa4AE!%il^!6*SM zn=4WU6V1eZmf}}<8*4r}Ye3U+!e@dYkt9*SMl}1aBp~7QjT9j-A``LZinWI2d%wZ7h6vS#MHz;1k8@(U2b)Z zJ6KWo8QT9s9@3@Np936fw!UA4sBiW7Z1JVk^?6bNi5n5-->w&rF-z+oF?KAdoHeyE zH)BQIJK$XypM4kQJ~YKz5$Za`su*E=Y`1RS61qO_Su3!9>T^jIFpvlVVx=mrI4%x( z`d1tP{yG`|r?3r{DkSNE3D>s#_As4l+QC^_nr?H04opLI8gd7h!HrrTpXZyG_nRw3 zcP0d!4C?w43_*0|S8nrNPuxelt#^hHwix&g5y*AcRimo!^ER1h?an+8ad!)5A>tZ_ z0vGd?kGwv=6=b6R+LHe&gDtB5mbMC_B}t1)OCOW$a!U1>{>b?=c$Av0lT#A`rAjI~+5{#Wf@4b*#WC#k0Tsf{}^ zR*BHsR9yfwBV$u_#h-e+9!h`8f4}bw(k5-m%zgtE-T!Ut-@StIhaNce$S)fGFd}>q zKfx_p2)EUva?`c#pS;&U&x>PPmOV^VCH>E}rlSnF|FQa1DL9PIyJ+R+Kjk!*4}c-( zb$L+Z|Gw(qy)bqE6(LmJ|4lsfo+Y6M=0RUR{@*?NzqYM&ez)uNQrqIg|F8AHfBMq@ zs`+8c_NbvS@^uD@OUxdS>aWgB(=D0q>UmgLx# zZ8X3YduYnw&>n4Mox77{r!gHJXkdH01y0GG{Wk-!A+a@xzgBO*(VS1=JjPYAB6j-8 zzWrRw{%%#u*~tum1l>*RALU2a(iN1u+TZi-(b)fdX1ZDZsMAL zEDg&}v{8y0q~tZ8L(b)`moLh%p>DoAF{F(sm(zlp!hi2K>+Zc4YxR=1Ob1`m$LfF< z*p33$Nxl&_QlFw7^hTaQ8krKcxsUwwzD5HLdLr|cUkM6Ux%LSz*79kTdqKIB^&1bU zR_MyDhxO`R@I3Szg7TFg>Tp@~xiuVlD&}=wXIVmNv(3I}kSb~~c276e{rpc2JQ?Y= zTTQ(&3M9Rc%V&B4NpkK|j&8*XB@KeYdgLF9x10b9YDHTNA@uVh*c&$r586Qg>8y zTxS+qE-31D*Y3pI^)hWzJ1z^8z|Pu#8yT%0G$yHy2DJz*a^RHkpORhQP?$J|wjl`5 z=u>-0UsQ7CZL?m}l_}3bkYB)ma{=sB9ezD~X{SHBM*2HYgj2sYr7t@FH3t#w#OxFI z{d0grTg;|n20wUi=~`H-wKm$v-b)xLBYdrH-+Zp9U+IZ6lFTE^r%w_$Y1h(M9P|DD zdP+{TutnogOApj7IH%tOq=On6PYLRu#+OY`6erw?Uqst9Zlz`OLfYn0^T5U}KrEkc z36TTffBxN*WjAw+HTU`{^Z<|DIZe?ph+!k@oz&W>gW=FxKeg|r&dFGzmv8Onr-q|+ zZR6Fomn{vpL#eM;Y(lh!YVutkyIB8l$ZAR<_3cT27`m(VOH;j?w+UNYUqucL=4;cl zg^UKe)sqsB7r7`#Z zHQcx44Ti!?ZT}Fg|MufJray7dddr;n9kZW{p6{J-ZMgsqMmgqSLoh>kR?iZV)zMhz z&Fl)}owfcr0m~Nmn#U{Sg8D92IaIB+wT}e97Cac+!TRHLpOxY4tx#(UL!?G|E1ccG zW?z(?dldJ~Fgc^bg~_P-2tOhx6T%-#sgKQo{bDTguReziqa0#0GM7RUH>dqSEk9`n-p5l>n_ntEe`P^%85Iu zL|-ePEwas|>uY0I*2+}zNdK^(y8UYWd3T8h_V*O24=Y76GZBCOh$^f@$`N{vQq>(MohJ6Pm`z8q zHh5V=rdF2!hI9;%0m=Ht97qe3)JVRU4KM#qDRV6RrTccTL+R9m!)15)WhNI%GxdjB zLGEKfU!TUA{=%q>RB3RV!;}kd7CUuc+xy)cJ{7|>ooaWV40=oSl0w3Re5)RJ?gyd) z%WU;7t;_gWk6i|z8Vd@JL(|B^0q>$H)c0e`QKo zxj(l0DxGEl`O$LjkaVw@>AvTu;X^wtavOKR%0HOp|9%dtU5B52{2JJvGaA0w9U60J zF|e$?)6{dDwzmuFtja=lgNgd)HH?N>{p8ntI>u*{#%~h_AIpk)@9cA(?dJ65nEr4D z1R(>=Z#K?`1ZyuYrbPGZ1(jQAP21YeF5HQg2O>fiiWMI3yS{s+eCr4rzmQLBrVbJk zf5wzy%Sc9**VK@_yi8W*_~T;yr`%lxv9b)`2Z&Gy6YkK9ry^mB{WUlB$73iC+#&9M z?bw1Hg?C>JchR^Vk3SM63(Xyqsj4?nsUXP|KV{&oNM0xt(u(%x$b^ME7>(q|V-JmW z`(AIn6ZhCA4kNt#{$8Z>%QB)E?;^s%YJUd^0gTv_TKQOp*qIb=|6jblbyOVN^DjCH zdP1<^P6EMQgF|o~f;$9v2!p!>4-niT1oz+$!QBRTcW3ZH?&N%vbAG@3)_Uu{x9+|D z*L3gcy=zxhSJnPh?QWiygvNZ*jf(tz4UfWLWo53GuKoPsPDc1w!7h5537B+&} zoF1uC`!zE!XO$;QTf~4P?ZC@4)1#{$*Rb%M)+Z{wx?c9)kgA9ER0L(9zMNMkH?!^N zhm0N`M$+c5#ekTR-JLTR$TBmtqxa0BNTTmDlHFHG+6F&XjBxpg?;|@O1s3;2a zb}j1+vp^U_BfWWUyHT0~I8*u1kYCBCSeGDY&+%?s*~zNm;=>xtPWR+r3gx96g}uJL zZ}{tOUr__)P}%IfnfQ3Q-;v@mBl=C`Um>(_o@F(Od}|zQ5Kyg4kQK;hdo~lg`l;gJ zv{N(3$(!L^6zzel$LUy8vWo+%J5 zwJ-`0K{Sw-ORfGUOUcv6PI0GsXrRH#y(qFKQSgO-Jsz_ID-r)T>zh%VZE(Ma{m8_Z z5-)~x;#B5z%32p@k8AHXDHfgIszkM@3tE59uOw;JTZeD$9?+r%-Vln8dc z79*m*D?1A`NAhW@(LnN`twBZQU%W(Qt`n4lj6~QUzYAU{S0V^nvu0Jj{H#v09ns>^ zFm_I?O+ScFvQL@p8XVjyWT;K`{$9$0c1-@}9dmdGS5tvkK+l_1MrkoUKxlDbL&+Cq?Xi>bHdE5Mx++kLU!DbMOT>8*i_9tC z1e6zzbM#0V?~!SY`9P?JmtWScOX;-Ep~EY0ebRrgN)5E9V{>AfIlI-Hv8DE==`c!e zFvjaD#A;t`vO6|8$x)?N!gI64rT7@oU>hI|*|sBH4+ffyWR2BE35YMv$6loQ_cC1x zFSUkZRs)YV#ZQt@0mln+t3UMc~5uN=T`pWgm$3Mu6`j#1X1M_GIN)h(k! zY(4mbo3NT)ZwP;cF;7mPfwK~4HTk@#y)C@H7*(j=uSRgYnlO7FhuU}^l;X$tX1*5C zlR{;*bNX@IYiD0_grlGXr{?9yI2?S_jZ(8w$R^wA;Yxe|#_s+`ys<;*%~WlCWr|wl z!~I{&=2knU>Q@dC!M8f9N!z03kdBv5v6MLDndFo3BrT<}VARA9n$lFcXG*md**Q&M zF}`g!A!ZSoEl0k+5t*2A#00@0kFX3`t2xq9dF~^{_o@soT$k#F}JQ%VzzQL@V3U|&4!F;_u1+u!ULbal-U*^|6Oa2;43F3hWxUX#jnl>OLagq9%;f4`YGB%%O1rxae%!g< ztBhH(#@*o+%GL+?idb=paZ_cwnXNL9FMX{?7hQ&5%+mFm(r?i7)of+l;3*O#)@1%; zJ?Qc_?;?ndCTv)^a7$X94seZ(jJ`xfd^)Hat%sduE;V+S4joj~ps=n>#5m?N={0tR z;m~VT7$Tq>x0boCK9iA=p`oSy*d2!Bwy?0w?Dq%{+jQu@6Bn!*zVoK=gzU3dcr2UN ze+C2Jr`qVdNlW)PCqVb8GXbXyE0508&@b`)ePPMmv6Rv%g>CfGj(fptMM>fLyII0v z7Qb1oMUDu2Mz!d&)2lzf=NR`3uusfaM!K%#o)%qdm1@VH_-zZTG34?Yq_5vi(8~V4 za_o|)obX$DVVx~;1=Rm;fnBWrg5MSYPh*Zr7fhbNM~tClgq5HEwhORp76hyz^#8O; z4~B^7{ClP)@pAn)Lt&kR+0Iv$)P-XleW3N5Pn!F5i&KI^S7eEeFMf}l zuZc7`rg0JK!|a4}Y?%nXOZewjjuT5OD_Bpm129r8q?b1Z}>pT$6el$X~Vjc@`gVC$AgehH@2^!*HuCgnN8vg2N(Z`P}}YNq%Kzi z==DydQ&GO7q&@kWjOKRtxEnLBwz^d7;VM=aaXyReGZO{P# zy<-5$&AhNU-=9=x|HVHN&@Av>?ztDwJ`vr7SK$&Jexsg$I5^hSXM*btBgZO7;+wk& z+KT*o4fa+O+F0XX{(vPbVp^e}$MO)3kvWRy1phu+qyqg|MsAU7+0yn=$UcMQ6`6^z z!}JbA%VPR!jS5c_T6HC@a{fa(N!I;OTUZ$pWKg?6Uq@{X)Z#Lb+P?{~r7i6GfN0Av zCB7-%D)97F&jI{bh>nSLP&P3iblshArba)kFT6tTy$w@mL1P*Tw;!>!6ogaW9OOrv z2UGt13xDys2b1Wgk<`)W%ArrGb;1)K$s}~&xYP9YBo%(R&AX3)#V~%P>__|gFQftA z&I+--x>qD!%bj-LepTDZKh`Vd_E~r1!;rk#o2}+)7hEnAybS92*-=U!+#lwn- z_Gs_tq8pQit+sH@2jM;WqC}ceI{4TZfY~(!=D|gBKb)$Ci)Qmgc5O`gHHdjJ;cXY# zOlsQDZS*s;GC;f=TFxW|W>{uCm2HX`E}x${e_H)XRq5B5y)*@SF;rS;XX3!%w0Yl` zg8=vA03gB&W55LstPNkp!_Buf+QG6of90cru>dp4>~PA^?nbuc$cVshonVJ-(}5e5<@(0=70#nApdVYMQoPmBhQ#h)?w<`~PD<#n4RyZVkyuY8O z#vSogMno+pzwZwHW_<(s`q-;E2|}BmoEc?#Rg)$~+0;#CS&Ra2u(R*LUFf&C@q7!D zDy%TKQSlTcu@x7~cYQp`qgqTc_o2(Gpo}p%I+|w`tEtfYiXxiXB_F>}fIBG@q^k_{ zs?cAY6GSYaia}*7D>PHzbbeDmk$wQ{TXL5OxomkW8grnyILnT_J|hunH#>pAa34g& zOtCXxT3D9Lf4#DkVre;Ox3ePudXU){8bEgMt4O1AdI|esFn$2ywx|5Z#kmB0M6Lnq z@@IT^#SZe_{3`@FPjzp0D-@M4fvCZ`f|IVONu$OQ?9RkD_aUpnB5G$CAQ@G*lM9FB zFT6TOap=SN426yQc*tL63d7C9b}#>=elZ%8rhJ&lwJGoZ%D;YsR$pI`bPQc$Y1-kj zMo@wZm!ZQgQMnZmsPkyT*Y8JkYR=e{C<4IqCqHfg?cAI^J+$pGKJ7f+XA*TWc90*x zx!WLn{D}`RGH!j=gHIGtF;sb04hv9NduC_5&MPWHk9x0%iEYDP(PUBje2|ttMvt9V zU??sqsE?h9`|ZgYKfl1ORv*I4&m+sQwVks*<+>N&9hSD@pWD2(%+@}aJRJ#M zNQQHf-h#K^;YT_wQK_PLXXI66Aw;No&Pn&$+lm1>E5c=%B( z!zU@Y{RPW&D=Zss+nmGI8!1Pn{ssR}ydq*UR*L{`3+`$NHHrVZN)~nqLW?Q(cQapT z3G?GROg3%FKX(u^+Wi|8H4>R@N6WV&rDwN)7tnv{eLOnHFrI<6 z+k)6RhqH4oxxkc1aL|yZb4>Ng(RW`LX;$C?zS+e9D;hZ`(iu4P$%9MW62?dIFI0Lk zyXN>UMHk6=lx61h`8>=n3JTNly*}Ntjm*O(4;dsJ7?hOCMWoRu%dyf^)*F$c>z1;) z{GRtUgPB|CF(e8xhSK4A!}#tw@~WxLVtup*g9HPv(MFFO>9S80Yx?;c!a?b5ey+3O zIF*6hy;#uopnR^JpGb=l3#WADZ$;T7Rh>YtFv1Xe7C)>AG1nA*XQw-G_Z$OGP5Y_d5VJY4Bl&Jq)VpMtc=0_Ih8O>gUwyN_FT_)B`Lhhpu1_^w3R2q_S^!hSG3eq+)r<9 zib{k0qC{bujOKA3fX>Jrt&NzqRPTX#o?hR!UA+` zs(ilO=tQ5C?_~W&JJYMDRJ-oxaGKH9L@%mTm#-WLdfJKZc7N8pbD1Q2gzkf%u8QGe zD7ZM3puF8Z%#?ZK{r=3&J{?P4>k;?+QIqT5D|)pO16VxI|Mj+U-46*C-DlCF8|9#)<5^j?x7)!L_HWUo4+9}UkR4gd<>!uzf~Ue#4C zo0V*eOwcmtSt}aXGWWEZ$tb$qLx;{o)iK6M1{p!%>-Ms_jqT6ApxXF^@Pi$`+l97a z>DO$fgN{!}D`23hZEtxb5Ye1vy)S@Q5`~kpS_`#vu!iZd-K7S({LX(xY%h~ zESb4xXw#v)1I|mIpY1a%+d8(jn+H3t&`WaPru}|h&l$i!?x1mypi5T_l#b<6s5epQ zZh*R2-}Tma@Zo-Elx;At%9N4Fw;f1r%Gq+iXYwucS_q!>Y3AM#Hr5P~7frpp#CT#v zEyYs3GhUFl(r@waLD25XU@r)y(sHpiJSW%vhyP8(UbtOH)R-@#chOseD$B*5ZW<3O z#h$wKveOwqze;zk-Lyr&pr(q%e1U1XXY7~)Mu}=A86@yZWq;vPaznGoN-i|5Wh{04 zeD-u#>*lcS>`5<37Vn8DVDi-Gae~0P(K9s4w)i_*iMIjFR4fIcJ1+cvPsIq_D2qOA9zjCX^e=^T-&`t!Y?; zD>(u>-T21SmH_x9gwN>;iS<<^jI^nKYIn_+hWhT6YQpPOJ)1r&cY~}(M)N)AzJ5aC zqj5p?IRm`(zC$~CVlKGL=fsxDBOVHc3bft|pF)D3Y#fR<39oE!iM%g>l|t7LnevZ1 z^3H*NDrB9VCueu<3jVW)GSl408{LdJD%Nh%UJ(ZYfa6PuBdKTlbx`o0EULYU1wGRr zx*Zpe2gz;giwxI;D`n{X213oPE7JSs=&^R?!5p-g=Z*=cT{g$&+HAC`Ajvhv!sK3M zj!}Go-r&<2aOUUJKDBt(s`X>7e(Agf&eyxlK*{;(&yPX+*8N`whDU1XBedmhAa!o7 z`ycQheFKi>gpWl_p!;>VSL!oo7%zFH5Ag!9oNKq%)h>+5=K z5waaX65HEenb&X3GIWr=Qn!SU*c6!FLhK&;P|P z22({A`IJPh?3@)A(Z1(|O1=``an?;~uutZA;{vA9p_-0fvZac83OCq1gwv-GW%}P*Uz_+0XaY=8zN+H;2wpQ%~h zh+X{Z&x&6+u&$LgjfiNq zLO#Fektad^;bMd`tgiv%q=t4Fk`=``l^-bLGy$EiOfw0-t@}I zo^%Ql%J`LTvtuX@z1k1M?iZwep1Nm0;o{=r6qS@Z!f+(87r(qbO&bpS7oMY(R(hSMtY>Vr3DeDls_Ip##s2J1 zy$+B1=HdMmo+ybzPN@XWF_e`ljCp@*0sdH$YIEYyrVzTPb>@HZF&ME4FdzEIu>S(% z{(s^;{|opZ_+cv+<$~BFxrJ~4ufX@8-#b|^&B?4Ufpl~W*vd1qAxOQu`UM+**nCX; zD|Wt)0^Ug<-V-vnPIsD{zsNooi6}jB`1mZ0?^|S0N}-SFD7H-8+v{QfZ)+MK3NX{`) zJka`?`|cqv#=d7xWTJI&;1{VDCfDzPAq6~_ji>|Bdb2#Jk5{jn%ASQ&Gv8QzB*6e zK#9iq4PM7oC;h^f8|~t3ZMMoM7(I8ok*R;BcTo8X%FDCzioymerL#eU`*XE#N9c7e zB#4M;2N_8B`9=)7(F}?F#yNB?LP%xCl!!{oOG~#v>Q8UaGQ61%HF_Hdv@DASkxH`j zY7+ujW!K?tup$7>l&U7M;TnfMkx4o zhT9pu*JbdHn-yaeV6tpuqO}~daqKPOQbJT-{#z0DjyGU{GuX?R$AV>Cwp;J--gV;e_4U|4o1S{|H4-R&dFeFac2Cmi z5!1CId%j`+C9{qbmn;GWRuf@Ss<{e*WitMDNJ~zCYmCsBR#_|Eko4Z*Fl$8#li{7! ziABe*+|P9aNGDF?piAPtjZT#o#nB#GXo8aFg4AGf@Vn)QXF^YUNx+FC$8>rn6^pm3 z!Yc+9jeo$|W3#_aNpL0Mevtu7^y*DRvGPpRmHqt{jx+tJz&+_nO`GV< zDb^t}u;d}9Eh1gpEHZ7LyHoC~YqZkd+v)rO%?iN`ZZ}J7rDMqfjvvZBCf|1Y3_Wxr}`9E~+ z>6yW@8IDgHGg1pps?E^pj|w?Z*PT-j&lmjn4RjsjWaEp?@e#`Y`BA4`(>C_&@Ia0r z$WFaiPEbM}ug3KT_q*w<7u03Xid%msY>VEn2WkzlrN#$cpDNvmFW;PnI|llQ71_|6 zaF!B7Z?T%kr$@BQ54Q->Aq_<=!@+txf%BF9@n8Q)SyHBKrJj{*3DL-?eP6rImX(VO zhEL(w2|~ZX&d%mawHF7PNwu4t_2{qGg2~QrHljukSl?PSXou9Etmn#>XjJ&a-1MpN z_CXjD={MM7J0|9pT1nq%iJgbOu#bOZ-s{#x%k1%+KS38`LGB?vGc9fMjDyevWs>qq zUE9M^$u$AJ+ZYeb!=x-zUpSKPOfW7KaQptrS!u!l%7YbtLvgGl$+vqqd{#D!c~sDA zVfiP;72f_US%Tm-5a<}QsYr{u!q-)2NvgU3;QaYdoel0u%PhN{|n8JmiQdc+PawPQ){cY7M~bYJc>L1O-cM6Z}4u>GM(y2 zIYBT1L82~8qJawH2=Lh0aJ2ap(3S-I&(-T3AF^#0ILa|SYtrukBlg#8-e&;>4qf0lg0iC zS&e`ZBaAk#Gms?vB=-C%@#j188mxgA#MuXsv8yeqM~VLyEYriUc~ z*5AB$CQ7usz)-%|XgMhX-}ZK)7(AvJs{hc^s1F-x{Y8M;2n*n6=4>;>V)|181vJVu zVL0a(l2^6o97Y;=^)W<%8}kPvln8j*+YvPL;aN)re75}x3a6L+%nu=e11K4?){?-qVd=` zJ2li8G1i2jf%D~M*|S&F-yCEgKfT)7ZfpIwqlba$dgYS5{eEh8JX5&hXR}?$a7eiM zH%hBs$Pa=LND+Y&tv-rGKklm$PuOxGrkFgQ-LTe4mSv!}?I+EAPx{!q!TnmUQ3ug~ z8C_+F;S%P=-vXirGOM0-VmwtD#L>fpHWm1&ZKKKUc35`@NYBaqz|sqzwr~0tG*Hg2 z+59#L{ChlFk)yB4Z%MH%68}7VF_gnZ0rko{t8JtQ+Y|sU#Wol>8BNb{Zb3uSpI>`E z2WOAf11u8!$ZgIg$k|tHa?-y)o3CURJxL_UWagecZvJ;+2=-(P;p@gh98LQO@D-|X zgNbqDSK@7$Ayt~Q3GL8y!Up!~5X2jNiDW9TbDM&js^`5Aa5;X>)_o>p(?hPlwV4K_ zi~ekWE3ouqCBW(582(rt@l#@K1ja$Y4HSz)8#?h-521oDJ4sN3}p9} zsjclFC2Wla1%$K|#8nwD^}T}Ri^;Us31tRMV4|5)5x6zp?yxrC1f7-N$^E)li!{eGpSZ&kgW^R*Go_z7)w>rg*8CbCo zhsw8zCiW`3gFETZDSbA)d9_%9^ILz7FJ6aPjG6^mv64Yo-j-#aZ0|;6lj){5Zv%CR zNH+uOkZxBKi9!yS#UJkCWj~1T9kX}t%vcCPmur&+qZB5*gHR@Og+vPe;&s;!H^Uob zaJ~KMub%9)17{TDv$ThTzWXFEf&OC=PH(YjiIXfT&s>aTok>Io7 z(UD%L&U_t)Fs)M;!s z+#-OKp?sS@y8JY^$f?8=x!x@uC7^9hy-=T({8hnmY zLb~n0)%A3_rh;n#S8~ai@hiCBjlh%3xfX;bjJy|_A7b@AeLkgxvc;R zDYqP~@kDvRo^5NV$1|FItl)i{8bz=tdmf9T?z*>dS)vK%m3^)Ovyd=H3@K>~r~JT6 zCHdS^YcJ$|WlQXMZecRzk~SOqv{*j8zLmLrH*)?)7oXYqy6M7B*<)bQUdxsP_fayy zwwoR5n(M@UnL5zGIy>BN)cY=Bf1{_-Y-YYs5#E4&-KcgUENIOV>{*@Z`7y5S!uy{ zPvoi#PmE8;O|Xww(6FSfuU3E-VTB;FY_R$d@cKRsLB=HXd7HGjHJRC`OZNRO5nvaH z5e5%zp-O%KIm}Tl0u2?1u_do2ak*Av06(|tZ7kP266#l$ANfaE=A~t6+R)~{!yaG% z3mF)IR_TN?LfgjMeg@f}&FtedEil1t-|UBOPO~dZ$eQ^mPIL4QH{~&=W4FDpVxON= zT6IbE7@4z*d4k%~Vhr^^dF^Cm=J2sKFs6dJzHHZ#u-7^%U;Yg~%_^H;SZgM2NAlz) z6A@~q1Y74-L)qK7hg}7*(v??`@`!hw=bKa0ys5icPR%cwQiuYuGZLH7&ttP`y+PYA z%>-S8uQG{qpyx20m8%K{%o!w2^5q|e#NY~_HkhZ3@`*1bSqMgrXc0sVe~_vL9xi0| z+4Y)^_u%km8rnRiEvectEb>1n^^657fkmtwRHs z5gaE)RJ$iW!4q7SVE>dwHMzZ4H14A$#-X7|>3^};2B@NOwW#;?|XhUU7fiXP|G^bQz3sv>M29CoS8HOJ^KE@)x9sU zaZ(&OGV0QxPI{LbU z+*jiMNRA`-0);3bW(Dy5-zs28aFp{lb-Vso0l6OUcj*)d+iyKPV*@28^4;X5e+eGW zRD)B)FsYLGDm2_zD(&Gu#&F;?N+->R_0+=t4-X2xG~IUYPu`%{?p0xstE8=urm?cl z=AI4JC~~=K4?W{CuI!b^q);$!B>GAVy#Qm%V?}MQ*ynA?zvKeyl=oAt`19CiI~tGX zXNBLq1TBwHdPG1Fha+HB>Y~*j*RNx&E&U_!S4;*uoDPl(C`pr#uc<85*w9-rWVh;g zHqr%o3c$XS^! znBmmo3yH~T0mb>J--Jre7M#x zJsPK9d)K^uKO#y3Ii0MWf6v0q*EZ|Pw*{IIRqQiFaFx32O)UzV1xqC&^xnZkCfU7;6zPmH~sG#;R zoiDw5!}HTIQ_JFKf~I5MG!|;-f}-2a=cx;aD^3avJhzaMFE&H`G{rfUvyBaLE1CG{ zt0N2dn=aZ!gOV>1BN%G1A{b_1E)iAVJz;oMP}XUz&w?f8p$0UuSo0XfRMG&64MEyr4nXN~rnDLcM@EN+1f^R<^*$Q<#vQh2h*Ut zh(A)O+p29n_oj-~{g7zOy%Of%^TDjI<=%+eRz%W0-tv$D*I^)Xw(~;#R_eq|!gD_P+TD!bO z`#0t}q7ji}a#Ncx&6aa_{ul7(AHkh?$+g_1$&lDXml9!eUOtD9%l?R<4->+U z^VQ>=)sZeT@;M=+Hjx3*sH&T~XG51GDdk)z=kb_;ftj7SD@7cA3-3^$C$bE)jd(%t zt19$*ME=H)aLMh6DkaQF2Ag3^iePIoz8BRs$XtEu1&4e@=<{ zY*Yx#N}p76B@C+LKcmslR9+TU@ybn3e0=a(y^T=ch0cxMki*2vGTx_z#^TUD;%%YO z;g+0FrB~RD6qS!?4%g5=u+XrRp`dAEqCn1p%!})}`U4iXd?cho{WRQiJzO*-;1@>M zfv_w}HMGs{WiY^%T|}_B1wTy`n6M z-|$?q{f-k$cCf8F)~mehrVc1Ha61yvEP(vOujn!vb=r6tsq72<2}(@DP=KuNGuXZ- z>Ip>Re$Ux*ISfk~F!sR3@@J!*V}t7VunbR21WQI3qj%C{&zrqiwmtVsZoKhGJuP}R zTF+xKO$wWqc*^(kl&SCG&2Xs_QcNececn);r_MRQlj7mfo=aWorz`4M-0P}0i5M2! zkaxVSQ&NtW&Ryi6(Q8Xv0cDu`nZ#@xI^_2m!(!K*BCU|F4YBvhTuk$t_a2O|ph$a{MOtsVHZZA}y2TWEq{fq%SY3gH3ZIiiL1`6=HhQ!N+;JVlAY$m= z!pmh}B>Fdp3$5PUx^I`V3Pl1v+3Q$ctQ|u-GH*=vy?N8Ah|yvrd-q3lY@pjN zqu4OSm8}TVa`U(x<~NgYREk~M^s1?8iN%s_CmlK;H{>f%2*>3O^}*2VJ(^*gZZ0%Z zwd8p#jJ(sAjaA$eW_KNyvsfrtdot|vvwimJuR1FDm)WP@czijUt8FVz!EPLx?q@0Wy_J4V z9GstkL*T&2pA^K`n*LJaoYU#DDxVJjfyL;hi|g0>m~6)(4zlQ+1vZtOtU*+71^&&L z^uglLgrZ4?9g&w3m-+1JqJdZVnaoyY=<6yfm`sGEBRQWk%Kl1)Jc=~7tST9k-dI>> z(M?HE%webBK8soy#I@hCSx%YS`iV@j6YR%%OJBZZU@{fUuh|${&Sh)rG*Yw%Nycn0 zraq$BL&JgUB=a>|rf``GB8r=^m192Uv{LGo@97xHBS8Y8j5gsR869XIC(QLJJnq!YLjCUiDNDJ`~NSfa%T zW7`*%Anl03oIYA-IHd`~9MOzQeb#Kp+Rw=HsX~RbA)((UEF2m$$ORUL&L?h%IMj_% zOABY?E@Wb_Gtt+ezQaN+;^%GQB8Pa!x+&O)V zlONqivTtxpX?^B9s$BE27C}1YgShI*y*HNsXk@pbor0y&vBp(<+j|JdNX`AKpQLG; z6-#Vr)@tx-#p8{-DFI9qovA>ToH1*8auOxPL-SFED#%ztmX zci3@Mpen40g>oU(B{#gzN_-h*7r3~_@uBWI*;_|5DabyhtW%fW$C)a%wAj9F&^{Xa z@X76gt7=!BHs%#iTU&PDt(nrvsG!LeA(yQyc6~?kicV7XF(UU9JpGK2tc@)Iul_WZ zUFR9;(vR_AP|jOZ7+{_w9&>aUwdpy34CIKWlmQtL1j7AzAdbx6!GP~`6nvZdVyFqn z(IL>tBW%&rSR%d~9k^&7;ruEJsgAIFN2h;L$1%6p&eb0>K-*AdGJvXc>S!q%9VgMw z8hgZ(uJ8~lSJc4cco)z4N+&Y3Qj%|@>%=i;rR3LcLTRdS$LY7JRJLVoGi>u|ZiIDt z@sZ{!u9U1>?ooCWdtBI-NRoSBkbqq${mCvY<>^E4y5TO(cyvXuQa-s#3kOLVp-?GB zy~C^XnF?xLs=3Mc-pUy~w$*My<5r;AHX#w3xV9y8GroRn#n%uPIgb&<4I59c0>xk3 zjHD;T0`PR~97vU5F0s5i!K@g7$dk-JczK4SezSViw!>{ENbZ)CO208!4&ri)5%DcD zE94YU_$#S&XJdXMMI-hJOmt-{8kk7 zj9*d&x;kPXd)Tjg=i1I1RzRZ+Ni$sXyaMv60*`L*>Pio&Va9i*vqUDd+w5-d8lC&I zG<9rMBjPXTLVYXFT}d% zWs1wiuRLh!@7&DivVIOqcgz_%O?5$YIM*3DA6#mFXvZ<&tQozrkF1{jm9_#K_9tgk z#qph}+SMB6e(9;jt`ca>3mqLaUnK8VVS{~2f{Qp@L^dFr^`pbbhV7!jyOl6EduC5tQUqvC&+Zb#1W&+852R954xk1 zJ&LOk^9rul$q)kfd&P##Tog6?p7Z>}N@|IB1o^b%ik`f&XRu{=tVwhxAJY6No{_6VfR$)F0%^t2G#M-DTqNG~bzxpsf zbS%f?Qje80X* z7x8x1eUO(@(H$%tvoxJ5XS;oPEh8xzmzS4jl)(84J0A4dedm`~#nhoMI49Yg{80(X zM`Ew8P2|YZ;L@Frl)saOX!ZwF)e$TPb!LH~9lNnU(#A_1z46sF|A(?@zybU6+UwSG z^N+^coW*IL6a+&;92{iaW#H#pA+_UIYJT5HjQvRE8oaOYL$l3bVX=nZu=*SQHCfdI zjoY!O(dCw2N!?|)C!bL{1yOQJ3}hr8cvd=U+Rz$Wa|`hV%L1pm``QXMSzWoAC2Z$8 zk15@zKHC%Lhb0p-n(Ib{+VJVx`fw{3*~3cYQY7pnDqjahBPsHBVse&P;Uqb>U}zL^ zA5U_>3!8M=4CJg2&UD*D7u3?$g^~s=JBXP){9tnC!TaOHS3&nwny^@WWw8Ld!&gd% z%pyEg_e0HiN5f5FA5U9v5{WUkWV=)&7pKm|Tx*b$9%xdr%=ZI`q@ep12%Z&Rne2h? zglpoC_vnNxMB06ro@a-n*FcA>@qpA=J`Ie8SHn5zl?y>iu2gI87hHR6^r!c?!a3M; zxAN^$bhqwSFI(=)uj#ZNy#$=%TbsOjv}v=|DQ+Q)e%@-fRdWnpD^%sMr0m7+__Mmd z<_$GMQ2+pp+WF3TpLg1+TosPEz73Yw+g4MiPItZ~Hcex?m?@;`kdv7n$^5&6riUuS4JOHIjH8nrRGNTJxk2b{V)USpp+l(n>=S`p1Q}r>Ol&^ z3abYI0I#(RA_4>FXGaeJ24R6jD5|s29DI=t4n|N-YkC7Op&c4P^o={Hgu_-VPtAu< zd8iT~5jHuspz>~!x^!}C9yeE{CvRxx9J*uWrm{>TTyXfH{~Xru?*pGsqO_~DpdjQ5 z1Mr27-E`>JkKe~n8Y2}<7w~5PIO%`6<0AAZ?%AKe01WW6LSPE<=jcQh*ZK1s0Kk`^ zS^xLWpDgb&@&0WL!u)%Fzb~+SQT!#R--qwV&u^IioB#kXDX>5NZy7Q=$sGMxx56v? z2M0(?l1fT32o#}_cX#dr*NY$-1%>JP8Y>(!GG=LB*VAuk#P7b@d2SGC{V)*8^nzuW zcd3PLLv5SSB(}D^TT(c!)S&O0^~#-(=HE)E_aFi& zFd>WpF;WmCz~I~8j}E|KGL_XRD8qff@Cv;F_SgOWeZgUkIXb^WQMx|Op040oBB zi+<`%sTkNM4a&NOQs_xrCVB$^W)}b~*hyB;e!eW}I_mYl);w}aSG6!2)b|Iy>aj98 zXDF3R#@UMg#VYfOTFY;Zjan{CPKkORN1SdgdW>4tQVk6a>1y#5JIxa*S(vJM?61q z#WGwjTI|`<>a86F)UJGJaZ!I&Y+~o4V?Z*gUup|p!b0R3(o0*!E9ZA2VTa8DgG8@f z9RUI1C`#z@#z<8~<6&5i3@YU*MbP3&ePaSKOk@8A2sc=5s!dQ|6fr}z>e*Y1e| zi0;)v0hnfoEQHH%o$R|NKDU)5I`8^! zR;$2icZS);Q$S+086(?_>bAz)7JVtc%W`f3d==cBvU1kYa&~82ShvF!z~K|G9$a#Q z3!@QPdx6KW$>n4kiOdtmZ(i8vG+Q4ob8;vj<}x3Wf2l#;!qQ2@$FsAu#+?k0i`dM2 zF(fqNvG3yHDtdZlo14Zk$q1ZvVa4S9lEMhz$ro2a06tTa-81s@U!vB*{^apv#Y?T1 zi0Q&ZcOh&szW<|bsgB_UDMEFNmr1F<3v=xOQtx3SO&e9h>}5buWI6OgI7s(8q09VX z@t9s8m@u2m@l^A?jB?m!`YOhC%gJ&Ay1x=0ym0}Cz*#k0CJ-|{glY~9t$xVbwtCPD zo9bx+*O6H!G?sJ;G%)MAaoXS^^42uDzEilyUC<(P(tEu)V+EVKFJ;4$ty|0T6{KM# zQ)uNV<>uz*3cZF3m|;EVQJ2m~B~7i6Ha5uIR?>9bC~MbpnLz4w@nLFes_@%4;kspa z`i0SF_-B763V6s0SqOM?jt_RUnH67b80MWcaXRcq;gW8*Y6HHslnI`pR(K)P&6OU< zi)Zy#o`5Va?C9?DtrMNEvmWDu($6U+y8{mw-3R&>b?b@r;uc9aKkEVMHM#jFG@~MPIS!7GyVuDD*F26FeBi6XJAG1%R+1= z>QB$KUe#Rf@V5Hs>XMK-{y*jjmbmsUXGB?>f9&2h>*gxeoLAayrja%ZU=$za!pd22 zw-8`$l3qAikFVp_6EgRx93*JMLtm(&9$v|EJ)Bw6uRK`QYf>|*M8O4`w^1q;%+ltq8XqSuc)q`Pxg2ktW{wc2orNT z>{-H7IYNEiYU!Ok&e;?1XPqNAiXz{8UoU#gkVPjQL1$5C3FZKq9VOX4I~t$x6nf% zA>p1_=9}-{=l}17*Llnklk=Xl&)#eAwf0FB6OG9I)2@ej?Ts|^O<2A8ie4^ba)<;X($TKEjzra|+ANW$&*!HbYf9s$BMG@tA@5f70M?K{B8w9Ws^VC@g7!Ny5yJ7P;I5JYGATg)C zs*?HKN#kz8VpYzW`h~dj!#FQ+Ng2bDGOQ)TPSgvFODy1E*no+RAELRGQeR)+Jc~V2 z$%fZ&!OidgpxhA(Ztfe~p9n=C`hM4E`KCO7#jsO!y^9V6wm#RBw%_?wS!2uCp3Tfo zU1aQus&b{62gtR9ui8ZYM~@&*@f^&c%c*W~KPxvQxjTC!L z?uuD4(rMs^rCh#p#8%|ja;JR(|5jUwuKs{(LnturY#O|lVB4)+ zbhHAStZY6f5R2Xbe*+I@sUeN3L;MkT^C+`vazT^XhwCcf8N)>4gUt@}n#do0(N1te zj7h~gN=(DsK{U225$A9wUz73Skmm~4wc6@-^O?M3Wa0<23Y%@?BdB58e4o!L9A$)I zA3W5>xLg;w&?5_lzNTzgBBl8O{?o{yUM-tGLq&+7KL1R4{)PJTYVW%0JfZrB=+7@d zF4q>n@}mM9mAb;pU#R6%i_(dTv+;HT8u4x8IOMw;5!Y~u?%k1(W0MnBHCxKst|8H9 zym!+MmobTvt4RbalONBs|XDhP+gZw;X;C^OQi9e%vPElQ%AOU36}pCtlJOMz4t2Oa8Y@%Ww2If4I%uysI~+f%b-tpppAw41d43$X|Cy z0`l%9*{FP`#>C$bx-aaw|DZM+nu7leDPnnn7qWa@y;)94%`-(oVB5p#!t+X!>32Pq zd%Tv0ir--c%xkajyZq}-ZgLi%q{7DrO$e>`%#>+eY%D@j)TO6`I6gQ0#-5S>*T)9k z_z5eSy@bqf6pl;TF0hDVl47%5IJxGg+p|)o1b)5DQn@Jc8ZfMP{1jU~u|dQaKcnRt z#YC5_xspN^h9|b-+i@P^-}^FV6c3)(b29st^c(ili&IDQG5!<-lF#{3&YT;vjb%}Wc`+dC=(HAeB))|c^Qtn z%(Dp1g*yuQFaCP<#TDAxrcD_eYZ{%#PntwVMP&#!*O(h1>ULx|-Ti}0q|HY#6bzcl zb2)dKTvCmC0y08=et4mDor2$9KCT)zjo5g1dkHRL+}*6#JBy$GOW*UzuhG+6P_ey8 z|6;)rvgiCoLHYG?c3~d{Vcn!}IWL2cT*-cUvvl|Kr+1-^9Q4_r#|6N|=`bLD>(`%C zU)COM-fNK@pypD^_Yw%n%i-?AFNTqr(T3?7w3lH0*3vd*w9TxlXqsSB5{cBu=ow~z z87zdwciBTLZX?o1A%4u7<7BmAOxcR@_=^`W_(sG{;tgJm!-p_OD=m7%oRx#Wv-~#V zhC|fchTd(;EtFEe#3m^0t76i&r{q$_clt1$-U>u}<2VzP)W=GnJ%&yXeCpc{(~#%e z3qiVK~lXKWci-XBTX8xt7GhQ+6M#>*5Gu_^Bf z@_RM#ZR#(f*=(lcq@-f@31QBhK5akSm6({s&(GiYl7S^MCI*c|CdzmN@S@2g;dI}~ zX!!oIGc<}~GbS`aH)f1!Zdy|??->c1dwP~;v(#et-1(qV| zWP^Ikn}>uG2MDU;y`#+(GhzMY{xfj*vR8wnOHTPWN>MsmrCX~34%4bO9yQk$7@?T- zC5nD2`*`7K6+iO6AiwPZkyOCsETH?NsjKkejWU&ZBL8XcIh1hDFn<)R(opXr9(AAP z=uu=bs;h?TAtrY3!k}&i^)i>gmNO#(;xF@F8Pn(n2oyI|tiUL@{juD6lrN?|B}3@`LBY_bRa(ohmVfSw{s7fL6=StE6WQg-ne5U#5Vl$m zeX!R%pZqA*E76O4Mk{`B*B3W&4z|&cATIW~;z*>OJJz*%H;zRFmN671GH!!fuN#U^c7sa4}vS|*`}(W}%tYLZ+q8egav&&cnME+0Eu zl7m1x^abQEtkR7VS31`Ojgdx}G8a!}^8WYH;o+CUnlBfk`Lp_R+S*hz($npCx7Tnc z9fC$B=`j3l7mg6m&5h(eQ^`?}h-;#vTq;U$S+zu%#U@;}wB9>OV2jRm-9c(m>OCvY~InD?@&8tFjb522Ip7M|*%OI|hLV$DZk*p3Z5Nl-6bqNELT{s!5e z4!nknqHh4$7%OYyfWC?;-8%hAFK6a#)F7Iy18s6lb5G{0p# zT7{cv4CYb+k5TjBuOrO!JLMon2K(K(!a0$%73Z}$pOriaic20Fostl2Ih5)L+}zxB z@8AEZlcm8cFK@vSu${8CG@RDV?su=XwG~#c1m?YXuTRZOv{cP@7MwQHQ6W1?db`AZ zO$we~DvI6;S&=G$LCt8Sfcyyzi12RPwtrO5c3RIez#r6(TV*-jncEs)zl^@oR4?(H`WFYT<2d zZJQmU-7S-ASNQo6eGnP%WnC+)6yUrD3oQyaH#dVq8EAYP{uFBztU2LHYA4W_(&ihy zXqd0OseCVLOfmN<*?gyATJ=$_Gqi_YHSDGP34?I$2PezyopLG5L~NSu=?k0yK3G1q z{_O(;Q?7=~ce6R%HTBzzp`{75m+3RistK#h`$AmEKK;lV>J=LH8l7&K#oZ_!#d@lc zIo?deFC?=uY~X2e4xrQNVX`>xpMNgeykrVdA1K={cEebowl3wbQXs8eU3-IMAj>P5 z)+>?=>WvAkB=0E3hNupjm#Pv8!{BdzZww zPwjHsafCidl?A}(TLm1o`Z}rbMgc!%=AxhGtIo`|w~q&QYO8&g?u<%1=QcGrK^{0g z(9d#-l5}{K?e3`Nw7Ah{1_E#;zW^8WZ7SemZlV+{6}>er&`<1UStF>hjhb@LN=o^a#rm(b z{+^_`d-W^7CrR!+wN7vOf#|$;3-)+Awf1w%8PQ4Hu|^Cl7~5uJWNfwUw6q|*jMRe_ zG!|$eVsm74Y*oYGn#&bdEOgCR#I#K_Y!94X&EaJZYVosh+L{9+6cRHV7z`1f?fL0^lz`iEM@fXZ|$`6LjWLbMse7Yo%CzV)gw!k3KVBn;wHGdF$49XCL{k$GS$~ zM;D{#VuI^);nnj(`HAKC)xvutSx<4iCu{)d+;bn{lH@ObiM*fL=boHG(9+B`DOBrl zTIZCXrk8tc!uZru&%<>XPfgXmE*H10o}eg@4$zAt#^HBkVCqL&h#OXY#ucKJUD-MuAojcizY7&TbeRfASo1ic1tRpL{S;=7rgZGun2mwnlrjD!_{BA5U2bE}r_-@^JkeI3W9%Z3bCML1O_=ENrysi_w{FDg4OY z99mokhl||2_?rZ{srz%unOmf`R-&06omx89IJ{(h)hgP&d$*b*g5z!{vJ1KOISvex7+Wy*3eZ((|BiVnA1(SYf zSW<&&?hR_Vgc8o`Y8-dNjK$Wr)q#TyADC4~-K9>qN&8W}Gc0NWX0AreciCEq=dl^E$H7oJq`E2sW-+So$zGwoqDlE4Mnr*EdJ|K z_c^UkP|?8?2%f%De8ZxPLG7qjt5Fs0L3|FOWbo`>)6*0Cm{tCj(NMvv*1GOImN>V- zwIeX3C?&;h-dg+@pW*JIYM+h+M-?Tn39`zlpiDiI!yill$0k2V@&Ei$L%e^%rG2c} z(&Lw*(1?go7cS^2Jby=dWx#;CZL14G_^al1O%14;Ln!9g<2ntM@+ce8q{yqbPiNj`to(UWnRgWC}U4PxhNwa4obzrw0$BYvHmYX$IDNvRf=yV zB>mZ-ty3h8-*%IBf(n~oezWFs$(CYf_K^1)E)$&8fL*o8JeYQVbU8spt^1+BibOp4 z26&J~6A^tbMk0K_XLN3~NN}R5si|#p?T#NajmSgL#+W-aG-S`X|HLN8S=G(Y(?{1C zN`hoWFRB#U1(=Bn4sj2iE7|QhwWe4&oC1G^-$E~uvm-kz~xUBT{3P{a-e0(rf z?si#dujP@P+S(h?p`u$hHa7bgx~D{+|A{cV9TkHYfBTjDB531Rzi&+`4Uk+PB~NkR z`?j+&J1}x%8^;YGcTi~P!1KROrOMLZQC9EMBc~E0&+mIi^6M0e50Kbn4_35EO727{ zd7s9y>vAwqY{_K{>CPJbkTnL_DrR#F4H%iflYFF0{Z+@|d`6kDzixS6)rR;^pN zo|yhhxIkf;ns9xy4wKECnwqj_WT8=H{X4f*YA6qqaUQuI$|4Dp4p6K;3D@ye9#Cg^ zwqR{~FM%@OR3mWyeU#jzY z4lgfnZfW-<$!d+TM_76;si-FxG?AZ$C<#?;27tjS!+AX*~E>(%j*$h*-$FG!FI zRy=sYluiEA`r{jJRi<&$o{prIERgT0ya@|4P*r`y$IqW8WlFp&0XHPO zHDrw`wF{GQ8u|$6p({K*N`Mj*is8?bQ~yu2QTXf+5&Q!%uFM!i-v9A@Vonu0bTpP? zkIPe)DV8EjTa(rkk;|-wo_$P4*ZGutIW#Tu!V%8mM3@_?&I?$zt9f&7vymz6 z*r%IpQf_xZk=#L^(Fv3h`1tsG_cPx32+kTQBJR$mg>jl;UoNz~zkG!5*$wvTFf4t{ z+B^6hyS3#97oUzl$bR~&JHt*ar00ES-_X!3Pdjvc^~uefpDpi$ixy=8{!Y1h^T}W# zuY-faHA|YC_PG$phZR_x3hcB!d0_cbi)|@b^H%4TTHc2H-2^T!t~eR*f()4A2248F z(eWEb2Q{dN63*L_P&xG=kvN@NXe=Y*u^vUR&`Rt^JW|5}d}nU@D2$uY&Cm9uFdi>x zQoTmZADylU{E zqZk5s1acA!9gY6~g*NBxrX}J#dkN6>a)Ap{zMFG_*aOh3PFeIcH`AB0cP}gf?yYfX ziP-p*^{CSGq}>Of9UC!hRuwMv+nbZ_DQ5?13@?j{>SSbO03ssXxcsfEii#E>D>5|_ za{;_>om|TXM%{~aZ=#_|`8##?xC7Yqz{6MY{qwSfEUOBR*`Pl8vBxn9UK(;iWz0IrpQ&1$tf{M)4bu6%IGzx&&9?r${xkKKiCKV$~O88X_bKfl{) zh4chB?7!|Y8hQQmgjR~=(WZO-(8;X%iUPNTPg7j-{0CP0$#Ui^>N`8f7|FNg)cNt2|kDi&>!T! zD<3}w7+7Q+?PL#DI(Xqc$U)O&pJ)GZkoKZGW54l$pIEH__-_OX6H5i^g}_Ei)p}(u zE!+^=EIm=ijZ-Ywdixa2;Hb$ z%Bw`{Bb8bN@Xk?8G0f)H@tba)&4b5&WBEW=YT?2%MOK`n{VaW92=+T+p0UrlA{(lWOn55jQxR=T!CY$CoZT*|R^jL~eJep3bzhOJ& zMIscM7CjRC9RcqtP*oklOZl?-{FKZh4CZ0q=&4!58<(C#JQwgsFkc{k!{g}|W><>6 zZqmGr{D&?5uc^SNOQE507EqO(%nuo_!`Rd#Z`aam(eEqg)e_kN+OPPg%*) z+U4B)PcL)ll}m=G^x#_2MmH|e53Wa^i<9Bz$}0z602IPYAK#&Q`Q~2_VIQjAFc(3Y zd4~nqvyD}fYv1LkXQD&m1+ru}Cw9-kOSjAffvz1zj1cE)oevrS zNkXvF0Yr!E+n5HXF?q1*U&%RD+OGxO^HA+(sw<31ll{$ySRQ^scn#DP_6E8Zf??xl z-D>&`v+70eb$uZl;dx~(d~Szz*Q@h$cPwoALQ9p#$=e^he1t3H2`!r@o1Y?mWVeu$ zeFQ9r#aVfc?y<*N+SZAEti#h`XWPN( z92+|Fwjgqn0dasz!jhyP&F2B|GPek}d((%=pwU-PT3BN;kLDkoyI-8R{=EZbm1Ec( zVlVPSef1GYF+kt z1o_k*kYgJsd2+|b)5ix4RKlrF7?_1z@`x1LE+Uh!^+c8q!&$7sq?b5Ws=ja1pzAEe zZG<^L?gP8Vjdnp6d9yB&E?F;(_2!R()i=9j>H51yMn-J)<#Uf`kCt)qs~MTR^@bSN zNLm=}_~~JhD8c4JEOPZuIhJ#(&pXRI>QzLyYvEMnsk$!%%fC()%k*XQ-A8mPmF z{$tt6oCwakNeZ>d0h4fW%v$9B%6)~G+Z>c&gv1H{1xx2N6G6Tueo^9_g~c5LN;<&L7lh}=LG>3Lf_TThmbImm!Mg-E&ycjIRUfNGVSKD zIGF$QSJusMH8`H)oBoj=0FBn*ANc#^K>?EKzjOEJmt(p?$ap@otnHo_&86hRwR}@g zQaqb?$o;*qs%h$k(=k2Y!tC3-XZp~($CFJpNAX*JmG&Rt@(dYTB&jQ zBO^{YbF62SbA`q)0&HnA`~?frC8Es7z4=V}{&|#5qtFZUJE{&2Ie`2~<5G)O4hL|h z%z0E=MO#lVYNj)u2b89z+-J%x7-@Q_4dNtQM zn5bi8Lay=>Uxf%$0n(^enF)OJhaAj#S4=iG37qBiLiNpSw0D7tQ)7|fWEuGS=|I9q z#5K*w*0xzE~^gm{~?Q9*fStVq0ES}r?-kT##dr!tXI;c*^_nNH9A)!RQHNBW+4d~A6 z36kdNxwomK)oJz>%ko;^7JaG}rpwcFN?!C7Wb$sVydN7_=s3qKb2)M)SvP;IOl276 zU&6~}Z%VGAUEgUuP0<~u|ZLf_4?SQ9+WP- zLDPrRvLZG~l$p(oD!u%m_-4Qa(+kHW2S-nR*e>dB#2@fK!K`&y+W^v+IaV%PFz|!i z+qTqy81M4rFExBx2WfNqulIATX`g|rF)ArZC) z_v^Y}F`PxNMT{@JK}n^1ow82Eh=}S~C?{FXKc<`P2{YFL3&@@fGs!BoXEc>YpyW4_ zqO&@_Ma&N;Vmx3t>MMM#>nIl|)!LXNdh_?j%p=lQV%P@3{-m0BPHnL{96lopgJAYi zCzf*_gvU*=W9!N}j-WiF7GvL}ng{pSom&j*(?8k_1O95z(Vzkv;a90`QsQ;RdR!u3 zBP!h(*9kbKQf~)~repaSls2h6U*8dDKJ5}M0X50*XUBTpuQAv`yumB~P!wdf--}LH zgu&`K=ZA`|FIJe8H=-#PKR$~AiiF9A5Bo+tYcMJ6W;gUt(yANC;W@?9!! zF0<=qS5K7Ilai7GDUmO6J_~8v8Mh_cL}QsPGQRKT)K&DpPv4kZlV^`@mb%3YCXly% z(NlO(4rZ5?{w{ILgr1*jb_Op9CA*)$8BAdMwOiQ!vgPLF{k(iXgP>Z09?OSF`OUgd znsiOYGRflqldPp-`Yr5be~g-1k)doJkyrhGw4h(i;y zCN;0czx)k{{^w+$N*~hDh-g>E)j1v^DmbHAH^V+$at3<|+>SOdk2i(YnBctsir)`a z1RF=tW@mgW3QGDM$3O(n0fD@mM{{LO)?CUWj~eA2ANUqdW;;8+Q(y3unMo13I>>9m zjJ1#;!Qh7?GQXL6`~MHAi19aUGv`&w<&(=B=09}*i){T} zgoIlB7QVQ;{1xSivKo+HKVy{3woCF+1XMTL0$#@szJy3cTSMb5sPdFqHP8WeIo|?h z4#+Jn_Nz1@_x^Sc5Q!X1+N@1wrL|(DCzCX~}xYj^j;L z`N=?A1@XUEOUYP&?Du3Fjm)Skm}27tArXj#ZadE&rJFk9dUS>&Fk+YuJGWyT6*cf< z*c8V%l1Y&;(lD!2iQfVwph~YRZafhY#ZqJLX&7%{gESZYKrtD!RvR>SFi0Ve(w;x8 zUFiN2Nw*-+k?S=IuI2CDQ*VK#Co43?Y|b{K zdRE}89O3DlN(oe~?tFKk+}+*VpIGk&{%|@>KOY|L>WeZi*9ri_8sJ&x%G@LY=CgCD z)d3lSC5Z$kWx!o>^vrwz{byXfTdYbEQp|^|po!yOqAK%2H-*lRh57;z;a*^U9dib- zM+OExtgX;(3%8*H0=gB|&L7AX_(Q)ECCl&Br1f}ayPQkQK~t6UD?z0JBG39Qo{0U5 zU7rJqAZ*n%r$P;=X^Czv?#eItdF~sDA!BOjv7R3+MZ82Mror&@(F?vH5QUKEZA#)} z&92G(&At3&JptV$h8!hiezX8Wt6M5hEbmh+Z_*w#2^c3r?mPO(G3(yEwPON@`Uo79 zu4Otrx$!PV-_$fOBqYS1(fa;V9AOWWtW?yHY}71|y7|hYJ3$sPFKX-IEA(x;yH6;d zRU+Ogd`TjnwWQSqkKGMJSU?zlN>#v3RCh__b*&R-5=RL>=<2dUggR$MGoycJ(?;0ww8r)KGb zsgiIqn(j=yJ~+R7{1)$}>FRP!kqzvuLD?4e+C)nv^JQI%uQt|yuGS>)~&OZ&OG)eGa8UkPZTr=)4lu^lW`tj~Y_0Y5+8SRXhdV!1!eEhBo zULX^r5+uBpKa%VjKVRYA>%aCVnfqtm-A2{_K~}S?gi^a>>oLSOtC;~FNg3<0$*{me zplC@t*m>(Pq<;s{tX$1UNaxQm(p~N?l>EL@cCwf6{dpJ8yX)rLPoD&B%0}*fhVbV+ z8`W1v^i5h;M6IIP4-NQuy6U`2LutDxhne3rd`r#8t*RGXj#Yu<5Az}`a|F_m31ah;`MEv%U*$y5h07AsuI(W5Vm71hXhYRe^7QIA|Vgt1Lt`8 z_}*+CPyOSF|7VWx=f?uIV7XHkYie93;si6p%iHQYL9;(pweO#wwA=u)kDrhINImUKT+1tr`XMY4gpofmmAVaPMBiv^DKTtBE}G@1dqK{fwx6hDxS}uhOeuX`PS+B}=MePC%evfl)Sn z1-t|JyY8)9w~`NzG&L#8?o35QCzbZ-f2v!lCt;e!5{^`cPi^@qxSWn`YJ6_6dgwUY zKTvMZ|HR(?EOUx*HGWl1S;@?svAn7NIS{}9{11(!8=!VsW>td=mi%sTAwm9;%A^ss zIgR?baNuY8^#gZf=wFCYL!|^E2|qD$p`M8oM(rS_0*Rrt>%?Jidqhsn*Ly#t8a@|Ekn+Jag*9 z0j?p1J)i9BHD+hyWlu1__rx5j+}YW|nXqJKWH^9gJhfLT48CifZ;VvMR=A)yy5$Q2 zVZbKsp$tfvq9Z^$2QUnlWsunSa{3E*$s;-9w&pN;##R#Xs#W5}rtsgBhdEyc1`-lgBBhAUFdlj;~-x zfno9O7$Gxlef?0MKhmv@g* zcJm$BwbgZ7JKb<|AkTqV_+Zhby9$7Spo8mxk`?ZlRKt)L%gs3|iw3%^yyL9@L+zzB zS7q`1V<-H0P|tSbx1}&1a>srDo6h;U6>cd9YtmP#-|v-KR$V+~odQ-JiU9&j2`F{? zOG-*ORe+_08|!zCfqo9K@B65;0~A|jE@=rsxf^^|_+{Bi1IHbu85m(Si%Ki;^Q(!A zi&Mo$)5Blz&So}-SYFN7N6CH%ZqD6c52NaenwlW;oI3aKUjUN;zKCYw^C6D@w`?*m zJDG3*a$fz7$!R!$rrT{x&)2Mw{A-od4Azh_<+ko_G;l3g%5`85fHS1J2`eirKiUd# zILsIV*rM#-?gp@E{eXY~5|aAmGI*dJx&mH3KR@p~6KfZlkT9|mTM30RF)=NW#`gk9 zJC!|NK%X7kL@dH&$~2JJX^+P}JH*I$@nT9}t(Kl%hR?=K>%50!SAtY{ICP9RKm`8q#fVUoE!wV$ zVWl+SNzX^H_Q16ompd7e+yQD8ic#y!RFB{UB1nF~QAR~I`0*T|Vea}5k3qFPk;9-s zt@U*Dgj=5@xryl9HwhHo7p z9Ifzn{~!_gW=t0U=xVNffaELu7o$yQ74RVU2CYR4F77Gqo65^AGM-WEuUs!VTYt)m zZ@L!*KB7ztq`;gGfDuYeaxqCf?wrh4@p0m6n9q%Bj$bsMHM{7zB4}R>^8tylvB$#= zF^R36*AGR8*4-`~zc0e93$9Nq1{aRMlRtj{BOao9-sIrEPmgrXbS~G73V};$vC!+4 zf<(MJxV-#klV{H@?9`{H-vN6HS=OBrkX#$Kwb<}7_+mx;$(U>&TewE@IZ3H~X;1Zz zEF$pmHh30a4d$<_f3yHD3N6sHZxhquwXSy$C?4$VM^_}Y`u}Ve5Hhbd3-$dCVqy=K^vrT+FU3!T#7;8byKsFzG+_H|bm|4!$`v z3TA7s^yd&8KKN?H?Hy4fCCBIv`j>(g*z4!zZxgOdy8G_v{GCd@+&V)K(kODdD4wUB zt0caIs!XdmvH_j@y(dPGbRbhM|M#9KyKq&{fSi&X%&#)`(ZY^pQJg=8B#{+V-^cE4 zX!k=^kU!sL=7y=IG5{BgD|?g`8CkTe_*XG(eIEx&|r!LO#ZZxH#hq-KJHK z7MMoT&Bq6cfFvmejLu6{EiJ9GSI5Qwl>({gQw&c!B=54&lov?g-z-4DRxm5(wJ#PT470-udP4Y3|*mGF3Tqq*8gH) zkYy8MbdBHj$@{i{6jT34H6L|DTfP^*_u+)TjDdSvc@#(SV=?ADJN`FQ>*6m5wz?u? znZo|av{Zh*+E2&je(Gh3ymHX#aS)j$$bRArKKZQbX*=)d174s&CY6IWxp9d`q4nPn zpc`;fCLf@PxbvGMRo2mO5B>049?{bCWBK9;sZa@S(g2L$pGo+|mXYBOlDth!V-|(H z#cLR|jg-dAx3dHEVXC0^WQ7bZ9>%|Nko-A}&VN0OltT4-EiaSDi?00Vg%^_zLs|50 zsmREaZ_d`nG%Qa-B1H38{xp|grm7-7-L_^cCO&ApH{38{D8QnHHoiU>-*xo;^^G}a$>wBfBkqi*y%A`h3z;9 zeNEWXTA!Hc#nvxcv_ahe8bv+dUE6F_Eoy!~ItH|KPa+O7y*(_uGt+7?FhzJZDmS+L zE!mWC4rmo1RIU;fi}8z~!z%1|{?2^S9wd{6+4lBnX$Vh-=r6N?xMA6+tg)lj~>WR-aw&?yfN2A|_Q<=)ku)HW9y`_^|FWFQ065M5}W9&~RL1|(pO6FsrGDt9H%oZ&RJ&L1vmtahb~ zJ&Q~x*ZIm2*Rx{8we~y|jN2#wa`&|JsXAt!*8|+gU2i95eE@RGq1a4-=+wds0Q#Gr zoo%0Y+WGMYz`$HU$N;&~BD&DP*Vk9<)lr(uOn*8iKmOzC-l_!n zDdU*AG~`EiNBLgwIjT79hkRv%=IKRBFA|HkQ=(?y2xqL)9KJIK}nBKzs(56!guCx^LT@9prP z-5}SZ#$zRW31qUr9FOM0>W>CTN5|flmX@c`I3I?K4jinZ4KDH%1i0e3gQ7NXAYILX!>bbfqs5LrBZmhHsqTe~~(tuf(& z6{BtWnvK@(mfreT?4de^$4wrYjXYWG&Fr2#I{bQ>F(k9L))WNFaL)M7On@9gdIj_` z_V)J5AQuHKuK;VtaN-FBo{}1xBIoxmw3hhy5L%k|)a_J6m#{-B^K5tqK7H%!hqs$# zF%8*kg}L>~3xm(??n0-WAKxFxRLN_|e%U>O$A_zuYtyy$PQeSi@p!Ik1(C{>l#8Il zRwW!9J78{}#7Pa-UNvUVo;^ESZZ#wR{Lj5w{I!m2J6_`xD-|HxTyHvsiMr^uam{_# z_O0x>pOROG8znz(kprAlBr=^0wPXTN78Z--`0MyK|A0MsS$<{cA)Q{2>njm$Dy5An zN{anyFMGA4x`;Vii>s_y@y!lLt4gF|hIsz@Bz#-jQtOC-&zO!&0`~6u-14$M9FC$M z8v)3e3T)z>5baIvOXK@KEnG(Lqxm@riWI#rp)=49ty~)$R6t?a=)i2XvDl~nw%{$W z2+50%JvC!~{NS+C2YMYqyqWY-YAQSxMUO zA(PLBI@>$e;-$78{!DGeby17xC@b|)H52&i)#_(2n`y*1qO@(e)1 z317pCA5WREZ+vLx_X%mdh+hBDe8aren)7V1ol}SWI9&kzyG?R84{BT(T;u(b{&LBg z{&G7{z(-_9FaQI(94DcZaawESd4@RCg5@4cU`8|Y5^)AC zajGi0u~N>*{M1qZ*vwT_?CiT0mIN##+ z?5(CFolXx_oGp6yq#l{=G5c@lsH1ZB)}Kr5b@~vN%~X1Y;XCbIC_+xwz8x!&(3F~+ zgpO1W?v&Tmn9O!3qhFum0Ue-c@Wv)4@kAm~S4StUJw~{B@8>xf23P@}OUoI7pRTERkCo9tVL#ET;)<92wN7vMe9u~g+-dNRZ9q*d4VXE z%FRaTC>ceaKjy_}*c=+R1S1L$lO~2PglicX#5j-F=bz%yc%F;}*#Pib)MGcmMy4M4 z0{n$^!0z?4RWz2dEfq9H#1++{q?T`eyXm8KN70Q&0N17JdCW@dc6yhaY_L9Pdqc1z(^lalUBYPae`h5z$3 z_-?^JpSA{xQ^)sCer)X=F5pqA_N0hx^9L7IZ|*u`q9i=qVyx!etFe5|!mxmBVZttQ zS^aHuMqs>c@j^tb$>xgpt}&}`%z>AM^Ks=6601AstZsi!S5InghETxo+LoWr>|{itTli8 z1HVhLJC&z?JI$mJs;hcuIlJYr6|XJ%HD9*7Ki!W`jx2=+IZ`?E=pON zy3Qhj94lnA48sW$#OKROpQdwNTDK>1?vNyL0#kk>fn{N!Z*;FPzzreqoaUm?E1*wa zZ5@9NiC+v>>nhQXidNj!Rk4$1(K}K4l;!vbeW~?WcJavQH%8ILNgkeD1O}0fzg>S% zhyT*+Khcm=l*9W^(2US>OqBt!ZyzOPo3P0;3eVw12|GjI9t@6$<3D4i{n8BJtHlrW zrj|lXNUvAXlAsMSpwL7DlDiv#s&zFaNodD4<{G?#3l~5Ogzx6!mUMBc<&cEQ9acRt zuiOWUe!meeQ`md3u*@y;r}vUdwELn?W{JBgj6_(k-&4<>CrfT-NW#;Dm%S%36yt3_ zf+u;4MZP~7wU=32&l`HrcM?;t#{|_Vjjatldh;6L{Ovz+o+mCgO!n_3eK<3z@n=b| zJ>Uf86uOPcIuydrcTaJ}Pf7e-vsP8O2anb`ow1Y4gE7MH?UcWos7`+D z(=3{*c6kM{F~(5m4!=XlY%;KscVI%W19!3aO8n99Zfs^6s_2S-ZX`)~VLJ+iHsKfz zZV*{`xO&V)BFlN|KgzhHOBM_g9wMN>P}W8>CI;y(xuz_j)c z>KX|$8QHuac%Y@ay22EEm-q8*-Vr&DVzbAjZtuW#12e}A* zwppXyR%UEFW9-&`<}zxYfKFibItz zkoFbH?QZI$0#f69zpwI@EyqmUFbl}mYZX?j#nh9uD$UyY@IJ`5FQzPp-!s>WYqlf2 zIVXH6UvPB3wdwk^ujQ+812>q~Tu8JK$I40;qq$MbVpXQ#`Uh8MLO7}R+Yw4l&*-+A zWmt&_#_>U5m@k|3UBz-aLwB;oBmykLJshTB_>eJOa-n&jhDo#>lGlJS!};5cn8`K| zPiLkFq%9S*Ma&et@uMgId-v*dC2yWOU)=IL;!2pk^#a{!?5d+`z$pEe71G8~N0&Tj z4x9e*RD75t5a{CLH}IdgVLQ8&7m{?xy>$Xm++?{>Qr12=(LZig^Pu8Ol7HN$ro)YG z!e4v3tKGx!uwCyy*m(MBYui((^pM0Ckkf3o*EX)4__OIxwRSWo{ulb8c}7a+pj5Il zPR|cbqXsJBs+0BG1rahaDk#kgo+eI}82Rc91Ys2Oq2yMMK0+Y838quM60iHFF*PsJ z!zODuvh;IiJ_~y!=P2`@a>FV1QFem;!!`sj%7W2Q2l+Yf61<4q)9R{z0KLnAg9thm z8Ads)>-8;<_omIWpq;?iUx)2+5h7kM?+d)XM$F6%u6^G){zz*mi$~H~#Y2+1?<|=n z1@C|?%+^OhR!81vfuFdUc|$g`#Hy1Z|AWvfE0q~PNx=Wuh5>&ez8oKJ=cuhP$&o`y zvm$qp3n=T)DmG&{YBQ3n#`RX_ie5I!Q(rOp)4fpt)hH_p7@=WhU`;f;s(Q@jMJ;lt zjzwnR(F>Uc1qFA!FIoYJ9WGAsfV`2&Om9t!OL^7D{tb*CDLZ*l7I4z5pF4fsCZp3s zVX`6{#XNsd_xle2k-uH9VhFX-kZq@{t9v1p^C1l@m-nUdd|~hcCBowpI+7(o4!{xDGE{mu4);YL0Zwmi+BF`)k}2&EBno2 z4C;FrC&$VydfVFb+$#`|kdn=$<{r>iL3O^^*?^h@e5vMZI#?3Tk{O=S1ikteRcX@beA zZ)cqx&3~?1Y8Yj!-V?(faC^^W44B!m==oW$sMpI+Q%36AH|N_2Mn>|wx->xRHk*8a zDQMBSk>LyQo5PAZx0id9P^=8drr0&xTPq@5P!No@%S?A->~DV;c9sII5&P=gHN@pk z%|j#Ji}$dB@$!2MtfJBA&>~b zBDF^Fcy6y+0V>4dAtwbQyf1M0PXhVLzr*_l;M_U!k1+d*4b5=%@x8C8{s2<*!_rK? z&hTB-LZ5)X?7Q&H?qQC;WY~no!q>^N9;`bRgFqg=Se+5^ua(lal6%TS)L$<%(L7rP4N5hmfc}Z#1QpqK=L*Q9Mch!3S zYH%20co|n`=BY5aYQ84SNNN2|8L#KFYdVrG;d5{E1Ml`WMT$XHhd*Af^4pXIFX)!1 z@G6e&`_Q$==Y{FB)E-2k`q>d);&T|x^n{^xdnEem3i7LuDZY@BUZ z&a@B;;`CZ4f_RAF3H+{@wD|kEWx+P^p+00CVlCMkq)+8nwUwp^=sB$G>c=>wF3?+dm@bR0fiHV8TxfkC~dlZjUd;UDNPROD@Z?wi+ zEgbM^f;;4Zz8jR!i~*L}l)UN5f&w80@Ext_8CN5t*dqTalXbzJm)mDaAN*_lr;ObM ztA0K)jW-oYD!#hs&$3N^5(AS<2EYwm{yIAAJN|L&J5xs~POz!>;`1UjmJZJTt55Ru z5#Z8(3OCl#epqZsy^xCCd8ol1%EABwoKb0DioG`#Fo*KglL}{rwv4M9PmUj)Z>lp_>0K;D)z1;O1#_s5 zm8N(3kR*igEFMoXIm)FHvob!2Y}t3RCt1c=iWxF8?(3~{KHu;8{OUoUpuWB1x|a%l_V4Jn-8Ux_jG>CvpgQf% zds^@JuJ2k4P&ian=ve0|#od4X`onTpG5-C9Q~%&c<^2#5Iwr$?pQi&Avj&Bopn0I*V4O^sox?c^Y^$Y`jku>iz0q!|jf(nv)deUdby(9zMc zu()_wJU=VzuA5u=fddDefNch_hbUDSmlCD;8_Bu3xwt=Uj!Ad|^&5o5WkA1m9tCPq z&C)Vwx1~}h1W0|i14X?6jjm>I|9xa1PB!$a^g7RKRflV5MP;QknTY>3{qgz*@e|2i z&qMDtopSSH>6&Zrx|60oDs{H+&E^Q|g?5sT`S&@lL02)8d-racbtMjbpKd-v@>J%B zbEA1-5^dX3niHfipC9oN2gfIG_}5dvae@SGY;0_??W9;lR8&rRxeiY?5dnKP`*Y?xKAi1&z)>lyfb#r_m{16cwR5Pe(NR9%i z7M%vPgpd}sG%;aa5C_bfA}kv4kAyW(t2jCq!Gouayc=CA8ewK+3?H`H9Ey5FwcHDn_XipUN_zDRsL zhlU=5)FFOzF6pQdRlrTJ#>U2}%AKOZ!tkUd?EClc8}C>To`2M=Or>u=*+`aJkfrAH~=ev_}N9@k7dCtv=*amKQy29@C zW7M+YKuAkBF-YOW-hk-ss&5xa7$d6)%6l;W)Gnat9R3Bx_$>Ko4j{QFSE5Fj5}jSw zySwlHNYVI8w6rPJgUfsMlJ^C6cZ&+hEjhcm_+@5X>n*lS7Ri^FlVe2zjseIR85kK~ zFQmef8yO`*U7C%3L5Zl{Y-?g-(&_2P9eMgaC^`p6N4EXkCL>GhLR<6|KLEX+4{6G* z{Cu0vbr9E|UOTyg%q%P{3o9!}nax=2D#xdyS=pg!9Pl^jAwp2a<XtS!T-Q{6e(nhMSPdDQUudA|fo>r8p1 zKIgA>;6qv@si<-#0j>RNb0mP6Utf`WqmrG#H8XHX(n&CY;aP5zt}L~a_< zKg3>n^2ksPyqC#PISbNa&C&zTB|}Wp=mW zL_`h|G`zjNe+0vTO@pu02J^A?cu6#to_PYTIo*yrlyL@u{DW-C!?qB)1DQVt^AbO)joqG?!TXdgJXPt_w;<1 zgtOBmv3r2R&h#O?gj9sPxe{Fa$EYgDYd#m>O{P`{;#x=sW^JCNrzgO{7j~L|1BcBlNFsXW2LjOodFc|}h=;F1 zpYvSxyW&WR)DyE|fX<;ee0&>f8p7U`Cyx~|F%tA1i!NKa&I91cfrd4wrK8I(C{Q^Y za>?du?j1wJi7M=<)pZ0uBkZ=C2HDsTYI$4_D<>ulk-MbUYrwJw3K;?uDT%gH5|wg&|-l58z4`(Tkt9kyPMD3-&EE*_7C zu`zTNAKz)h-ATCS`%Ck*57d4%FEG1q1K_8%$B$g*mnHG;UiT}jLE+{B?vvKT6 zD*c7bFLCB3CU+*ugQcKaZmc9MfIfsXyXs#3o%-H>>WfyKih@E+U^)jv!Xz6_^XQq1as#2Z-yaX>Hg)OUo-OM|GG| zhn$1#h^m)Y4QyBc_;{Xt6gR%%)rqwU`|-iSjM-UJl+Vs*BM>^!hHw+WApqy$4J%?H zY)VIY`|?pffuf$Cp3viPIlw%;xA2^Sj9zM5Lt`qHSNWw^vwGl>8(Zs~ia zqkzuKpin3}gb$t@m6Jz8+F#;kW16R9Tt%Ra6VhDt`Q@8C(JOqFpVsIIBI1+9FA(9~ z)mKZp=l;_A4tYX4H;s)co7cZ>?d92mGQ_qQa%E(EUEAcJS!<#HIZXb@V%dA2s;+nJ z$LGB|d75yg@7pQPNc;Gp0J$uJYLd)=G7Cni;eau>tR&{+HdUQPna9R*!04x9^S<0U zO%_20_DSjdqc~`?8|d$c{(KDBW-CLo12^e=p_00{PtHj z189fl5N5%K*!!Upo=L;C-6JS;ctQeG&F3N5jpXEHyVnK5Mqk&YgG8@2K}#D3&YCI_ z*3J6AoP`;e%G8oS{;)o?8T0ZcxAd{o#$U~@uU4TBVLcG53fLJu6emXtjAh!FB&_{| z!&JDJr2Fvo9OI%W; zA!n)f75nj($98GNfBCrJqMaL7X)qW?*5xf|M#8_~DvDu*qUZZ#TnOcM_NboHv%o5s&}4=}^9bWnof#y8@tP^IK}D>e~Mf zJf7b9%gg%pEWCdrJMnHG0u@fF{Pi^|Dp`l!nCS2S-FqMM;dT7itw+LPk?RWI)c*QT zyDyTM|NHfSCJy)qrSAWAQTxvWkN^AwWp}F@b-HD)D~U)A4i+7Wk`AATZG?SlZEt^V zS@{)sM@wJ_;n{CFq{4CH^#%9?r=Xw~(38qKX;Ibv+0@)Dz|VhjBV`Y~EhSI029dTm zW6?^dsqP&*apJ_ulfbS5eO`nIRG&`eM{fOxI@i{xoj-S@+{0O&*K%OJXLOV|& zox{K)(@#(1#L6u?KpjNeH~e{XHvOvC7g`DB`UM;lbKA|X^NECtPeg0aIgdGKe5=!M zTIh>1{!TN!Zk{V5lbU^vgw=-3`no-IKNL2Q-z_bVq7Urp_MhYEa>_2b zOfH`qWQfoh$a?F^)@%Zg`OqO-X(@sBkRab!c5I>QKtC?We&*oKf}7RCdfrN&#%R^j ztZ%nsXr5Huax39Somf3=*kegQ;tUN4b&Zd{^?hNX>n%SI= zUpGiieIA-nM?EQ9uPlw8irq$vVyS$q3i()f!3TQ1rD|-wLpvxP3d4mG(#Dz+(U;0F4?`k2dYPOfj+OkD3Myh_q0&L zY|I3A8~Ai@6$E zi`{*H-jGqT@48BISv0NDJ}9r-gSYAx<@s^XF)`r09qg0pYQFstWdl}W64=K9b? zf1ItMs-9YPjrVuS;S!B3a*V`7Sq2N+zB4DI@@`)+8$rqh)Pt7y% z;oo|l%~`_!#uUWUamjtDLy$C^eqCU|8+bd4&Gn>kiR|rf_|w))1n<=h0IDxiSPOnivhteWi3{|Hu|EVqd z{#n+-i1Cx13mH_wt@1v5jFhBOg}c<{;3RoY#ZPC6rpn>6EPMjYl~sVK`T5p_TC z;q1_F` z`)2Nf1Y91_?t37-5d5g~t_Q=1{bMs{1E)02-ZIOWGVXll&k{YN;ix=yI$ai*V5ZLA zGIJ%)^^Wr`6AuKs6UK5=*!^m=*RjzT!O*Y*jn;DY*2E26KDxkZ>1JFs!HZwi*B~*+(>Wl=d9s3_i@)ds?HnFZt&Qp zzDhmkO1755IZoUvydfp5I`>95`vLt~e?8jy!4KuUtY%v-Ed$ATr_u9K_2>Nw0U3SP zf$DB|eVi)0S7P4G>z^9$h`sll;91M;gCQRB5e)9n2st7P>Vih~LbMi#>5BBS=}s|m zO3gLLG&>$^eo}@r*IZ6=YnNztu9%d{7A+!P$)Rw9X+Ex)Ijpk3*Q!RW+8evR!lQn! zV*<4Nvc|cN8qVI`nFP_)h)1p2dhDvh_0>y{j|txk-jm0Qkv+)CrsXeR-}=YvibG0z zj8Qm^=lg4;eSH&Ya37PO2hSVMv@=+X$RtV9jwW+DXlUlRSN8WFyCN!ml6H@p@d24v zQYFWKzo{SpMuNrFY~C)rIQ!v5s2-n`!H=VqeFs!JuE^~>#KUbClWl4^AA*s^9b?&e z=Ao{EXH?Ta7;;-XSklMGxjs;2J@Aw1j}d_u`@21HU$g6y(>J^G;?Ttp<1*TG%{gw| z>MkuFaEVcFiI1P$Z(H*&cr7+?ndmFEI~f9d`<3J5#W5L0VpV`wngY?B#B`sTHGh z%KO)%i>{d3+hO()Y?>3d?|m9LuQfj#`MZz)4TJE6?8{3dugQ(_=ORbFE__l(l4hqCdvv67+vVLIRZFtMj$ z_|)dr)yLdV+Mn~GfD}Wec5YAefPMF|@s+VXT%sKl;jGrfbl-;+IJ2f zD&@Vu(?@|t-i%c$(qlylj+^}Qr^5R0xPk@di_uVzKA)MQk}!HkU3VZQyZ7_QYcdHV zbJ5EV1&BEwQn_fR@tnrxY>aVW9kH%+xO(9IDQh~W-0*DSel;eXT z?;M<$V%2q+>``MXZ#P*&I)LSH%I@QgQ}#eX*$0XKm*a_k_l}j>bZ*S5tLOCMRRdF% zt{%u})Kt&u>>T-QBd0OYn>NTI&+c_)_ET4F2P_yrL1F*UPSEpq>&@2w7ZYBa;hjdO z!&DtL))%9Sxx_m5=9qTINnAKN;F4YaR{Eh5D2eBj?^^k&l{J{v?)96?#HeW;IVfOO zp>fA1Q$fZ=ykrSoQ*ok?hZsvP3anI;xiaSSSZ>bdHS|mr~1go7|-6DUb!FNzgt7-0`Go z)KzO!8z07nZrs#;e5|BT>}?;$e429iG@2;MgMh78nViWH8FnkhFkMoa7X2wc!(YSXuMt&lxNIC-%B%7H6(i~e*Ire$^K z4dO^vc6TPeY+?PEMlRrII|vNu4=iGiRTYos`Q@41KiNoDWE^ z>yITBd?fQ}qTKt>M@_#?>07$s)zxsk>9o-UCC^U+rOl^0st zMadG4hEkcspMN(L(b=8W(*6Pu6qwp4-iL+`<#$Av@bS``wuh=o;e0TxX4STs%AgQ`TZ`6vV|0IJzTm|aqu6gBS=b%BDD!*rFA}A-l34Kt&we7t zo6QH`V8B;_JF(2j)?KOsmjD=^dXZ)94}&cLSn!xm_8~bfOA9edDr!jwDab zr}O(WiAOwF;)L~&_5I{t+i1U%O!ADI?eGtzH4Le$=6gqH{TiR~TrUS_8jQiG-kJD$ zqCm`}yE_7p52Y8IEeO_m%j|=R+dFzkSthSeb{11PNfn8Yjl7Abf@MU11kILJK?EH^CF!0WUn9?WU!Bz9{ciL-aH!%QJ)XlcI zz&*H;m7FaVT*0#TnvObml3-yT%6YSbv&`?UrL=co@V-L~50B9=OE&f`u)WUa$~L(3 z+c_6+&V_}qcLTFOG`ni&DRQaKoF1T)I%ybR5XkPBP;V#8(gYqHi~bEK|*$rbIgUzXS-6VC6%Ghvb~@H(0?Y_QgxJ9kUpi~;RXa6zrxu$n zm(JCvwsk=IMtRDiv*r7J3Z+a`&i|>ESt1xNohyIpR0OX7w7jGm9gk&f*Ejx5AG~S~ zHhjOd|A6mEOrneMEO7wbiAAR@=UE}ud;GR@?WH#s)HAd3)@BOB<=+a7zHa{EWs@;P z%2i9K7it!+Sd$;s%P$P{&R$OzOR%&UC>o$0F%7#uJ8Pcm$6sL|SF+##rCWY!HeNre ziFGD2!qRr+xa)!348)D6&&tSENXAMLH?W8|)_<4bd&Qo~JiKCXR;LP`c9=WHa^`>| z>9tc1L>>t$=KTzLDwdDCVy2&`N*P4NDwX>5H1!g54<>JP?Rc2>{I+k6B9{@vtZAwE z_UV(0KPeXm5;5xX12_9L=?Ail);{Mto*-BE+?eKya6UM2tTUu2Gs);%^g(gzfSaa# znfE#|ch7YwZD0!Xm1ySBMY-#dQTQ)OC6-w$@v*u|8qST^hl^Fp-Oi*Zt5}bfaNRgQ zluF1`6dn@1$gcHp#zX3_Xr|zCQ`65i>(3hp4c9lHKoStS6ctZ%KLv}Z5(`6$z0?uxuD(D`7hIt4`V z^;d@3)!f)<$wO=eQ5tw4$gRKQuKEM{*RR*Tyno^!{_}L&|L6I;|NjI3-ZZNJ8N>4b z${wno7>Dq8un1rT14BausI>iR^7w^lL8{%*S`B~$bzR+TXvC01Bk&6LpErp5wzk+{ zX7PM#dhV>EB0dXoXbA`G(NS>#WN2z>X{n!~dV?hYkyo9AvONbkcd$DbfFAyZ zpkbl;r^^V|V+02Cy_B)k!EdBO|byr$gZa`~p-U0qHW~Hphf2l6mvnt!w8d zf0bT}?kmDMjf814@@SxjabEm%73qYr_2Ft5)@DYm7x>y__uQ^f3M(f3bXDI zaeaLO*x?ZP&cNUxUE+kJot@pphVS6L_Rh}WP4}Teh<9w&000F9gANfueApOle}8{?8vbD%UE_m@M!xH_Nw#s_jZc!g z=xd&?#Koe!=K8|BE*X6@Bd~;Asoem(;W+*Ls0mK@Ax<~q_|Lvr^tJ7_)_=Fvj(O|T z-yipX`joZzAWasOjRElnxPoj9CKR9~z(EKdk!gV8%mM5Kl=|UZYXRzs6%TD#=(N8I z)c!}AX-ZFQx<3+!cYvU)!J+?w1B?I+`_6`@Q^4Fn_ZTAYk2$)_ot&M0sp(pRwZlSm zzJw26931!<^mWwSlw4)FK)$qHZmqrYIAiD!3eJC(IBrmzSZA0=QxvaN)WDuM2}6&d zzp7~9ham9*Hln%m<-ghV-E-Imb#<8EjbK4QFp=%~((uQyRmnHYOr-<_M*!9J#~ht8 z2q+64dLEHrm&NF`VM~6$iAkuZkByCeTl1%3QiaEdRy{T;?98b^9qx~E4Y9A=k7t_X zYtu{A2-HLgPV|VRvJ_^T&WkURb15686s4WXgxl4G>dfX|z7ylsW!Ku=1mxq<l{TOwXXb~LD1s{ush_V6Vdj>+{mHKLzYo0lxfc^x81 zk4WS^_ntpwY@m67D$*~s3{%Km1;a^YFM@!-TK*7we(E<7VNekY3w}|!=$YUVKFPHhR5~jS%vNV=rS_VH_ zyPzUkZZH1>mr!!W)1prk)obMWO;dur3!JQTmqy4S!mjpJ*fzvI`L!Tn8rPEQgGYz@ ze^TPmX>-gw;lbfgYzD7KAW&9s&$aC3t&2m&-Z|_sU6!n{l`))}@Yz&^-NBGx7E-ER zTxBQE+M&?d%;Pz$@d=JLTIkJ}tJX(brsMiU#D31<7B3(_K}9%=I7JFg3WSw|S(SYQFzP03UM?K+a{V#f);3dn)Gq$eOqiOSYI!!e6WP zk9EH~zM;7AV-!0-_(Dec)1v$Rp}9yR1(skW8lACGwehuruS~8Q*?p>W<;X1qM{M!( znSzVVyX!b;5^-hj+azU8>Myw?W$v#%A1B~Eczvxg)<&^sMNI!3%6+qmY;;CYr;{M@ zYs3C=3y$Ra9C59#c|~YagB}HOtiNhs)Ig`!SxOlzKB(s?X>fb=`(NvidWAp_E*fVz zPrek`jAm16(J#1|L-P8U*=P0t{dIzsEWmz}XEHmGuBti{##=mEOF~qD;@O5V|PB!MPBE z)O7gB77r$xathhzr}m*pqYcBz=qT20iU;L$>lP?8gsNLJS3B9D(xrt!GIUJj55LQM zSQ1FH!s@T`x8fJRz5q~PYXql;t}ci9qooo|Fhfiy4*%is(N@=F$%zyGBx$AEiUSH# zte(S>>7uTlw;UZ;!weduizF)L24ATaYUYOB_Kv$Tv37}wwZ_V!DI2|$g8?y)wvRhZ z9&mLgU~rvMWU0@^HN!nA%9HNi3JY3Yvm`mnYyRpwq0mG5hJGUD0S~yT2cGa zy)8MHpT%-f-F9eiQJ}H=jyRVg#%P}sVQVfp$8<_GHX`Co-_|aT z;Tv{Y0HE+n!B`c)`!IG-77b`oWF~56A3ViZyBje4^%4rYjS=_n+53A$ckECOxTe5% z=REe}8LP9C(?@>Ah=>TO()47LdTO33p!#A9X+FUeRASn}Ae7K)zY>LFQS@?5HmE(T zG*+_TqnWYN*iX+k&LFq6gMCnR|JuN?w+_K*yC#ufF~CgA-M2)eg|=W~j_J=oQ6LwO z#yzM$210bh0VAIz`W;l{*fb}I%{X`CK~oFG#b;MxuFb=^E+AXt!{EjKV_~v&GIM2O z`?lwL$)sw8hdsZKhjT77XN{U;;hNJ|)u?snBn9ak_F*p=SWb(`;5`tK?PA4 z;-!TnN9IMBM~U>*E7f?9F@;>qcxv2b+emlGz2y5^1jVQbD|~N$-+$jK6NCX$S#h>O zmi5{!Ax9jB_I}YsQPuU63@d=W1EIp+`eqh4esqk`8|0&X#R z`M`H7OTu>*7@3oCt5_y?fL!fS=CHKJigmMuubj4gtk=@a3=y$f^rPG!BT`N zaZ=lQgG3tVy)9($ef|vI7AxyNN4mF`Lmn%?m_SX!JZO62IWO@(JZY$Bdnu@sCsEKS zNYu=!crJcfa7}e~>$bPN_Zgm7R+MKexLEae@F*KzI5jBeh5kh)m$psZUzc(b1w5 z6ow>(pYPe;hW-qk6TUZkf=^|J9~$EzU>PYk4`Zb9XJBApML~$84tr%_kbsQ!1TMix zkUK-%YiDOt^cri+%Em4x8ANzHtLpWgvmdiop~6I>x}tf<)W z!jeBjnD1tm_>G?i1~f-3{6zI~OzH8IVJY1u{jB{$d=FHcQe_f{dfNQN44;_k<~RS| zAa|22O&%o{;)Cdk4l6q20*;9kui+I|CyVJx@0rSL2eydn!xr1YguxdP)U1*zUUP`k zbWQ4}mw)17<*N22`>p4cstvILfq|)8L$Dt3XiMXjTD_le zjF3=E5arW1qdJ`8m z2KY|(*XBOPMs}R?j_qxUzC4(@UE5DReu?ykpy^p-MJjGZ?Z=Ge7nnrcNN;F}EE0(H1+I}XI;f%#JxC`CPI$HJ9Xd&c9vE#60h3()o^MUg!s?`R@ zjbJeGqq`Aa%AhbnVdD5HtbzDMeEJ2&F4 zP{|6&@SG90OO^!1L-cWLL0##1XGSj^-OytrI4YLXp!r! zS}cJk5)!W`95Re|5j}qXzuu0xj%i2Hu;1s{p6ra-J0Bt96QAv`aGb4r5e|bAL<9sc z88vr2_39speRB;!zrlvrk>5mXGBba4jz`|YV0PvP5v&(F4O=RB35Voi;Wr*fexvs5 zt~q%Z+I#|mNs?zpT(jz$=|;RlZj!$Gc@#Obk0*zRF+gYdRb=)OgXJ$(8^fV7`psz6 zFamBq>*mE&yL5abd1|Vstjl%N*{kj~%JU1m#;CyHuSflF_l`$w?J%XSVth(BRKg$Y7WNdY zYELDU>VjQmefmZRR~YNk&BpKms%w35o}wenH@N&o^}LHe2b*Y_z1Ao?q%j-K0y<(P zNhA`SQsnie+;0U9w}R4i_%izOxoxfy)n8W<5U z{99PEaZ_6ULmxcLzR|#zHV`KYUXnsnk_CEdhwV*9HUcu$Er%Ze@>&p;@kR`Bub!rD zg6F8TZqWUqYEN~&v%D(dOM7QubKpuitLOKx@~Av&s)iA`ard4ZY{-r4mt7bhD9`8E zc+k;dpJm3I1zbyE21si%bPE0@;c|o;&phi#CzmhDEeEu1+g=|Gp^LD*y?i)fvGVOo z`mj?Xra%8XoKN zlT&^O=^J>EDAk7#(;*24*IDnMz|&uA52^= z4h}RVUhkhmv-a^njLm>~n+kpXklk)(y6qy0dGq?y_{0^|$lWJq`fV{5xur8*Ju6*C z94NB5Ez|3V5nnFSjtCt4CHj{FDeJRAxxQP;``f-;Kcp34o!hy1GcT_64w~2z+^=^= z@W0;sUy4RS^4y=@6V)D23KcM|y?@H#24id68Tb2!s;U?2d0|j{>fGaM!(S}ZrvFns zkqSl;S6qDg&)*w_+oRo=dffyJ7W?BDZ+hBMmRj;V%Pi<7Sm5X!xXHU)apdH+0&2{R{}0SbpO~GBa{90SZEZCXk^=?RreV5hu^^Qtahl`VJyXkF}Z!G5!G3(b>uTa-r!Te=a#bu{JjSupa zNm8#Ja=Q2_$JVtb5j0|?6x<;wYC?HFB)nw$tWGY!JW8MU1_<8At{NOBfn@F~A6Cu5 zFlDjLeiNnFcP<#$)R0r(zCC9Xv5!i@U?p81Y9`2a)VpMOsmBv0-?neQT3)HFtZdG; zKE?C>awgDOGS;sxM)*;FT-<(Uo>@H9sizO+;BOyF|U2|$sR5|9Lwi?l7_uN8dWA%#+x| zN#D8f+_$aYwLs8(vi4O;f|8lsz$L@cmM2~(s;eDlTBFx>hE9akgi_W6OvJF06;D*b zLm_i@^o(!2nfFW@RwtOzJo4UPH|T!5x;V^1J(u3lb!ppr);iPD8_DIG6h8h*BRcFl zqgBh7lz;a!E55Z52Im&FnXZ$hE()7{edu+AF}SAgsK3M^|N29|^@omnpQNQzs$Qph zT85urgpONC$ZHLLGxN|KjPTA~G`{pu*2&xZ=MQ_B_{E>Gp&%^;=@ZBe>DGExgD2f& zg$2g-N|z;7SkCO698j|7P$OmbscFf_Op)3L^h2ntsMvSd_wlC=MTLid1P?I;36vo> z4l;FU-=1tNQl#oQlKDfyPjJhm1VLg?QEy4Lr{i|_vd0Uk1zBbA6t7|S17PjIxYFf zdD;FwLNQKgSUP%u4F##`Sfao&z3WK7<)264Sb|oB?#`ttB6LyL zY$7$huIKG~mcO(h6qauJ8ME3vXhR(oOM(;nC?%f8uwTY-jbkV>ePw*@Huw>&X=B<= zTneY+ULXTlP;HYw%}gn$;dAcE(lR0COtERqHg+_cUS{ah*anD z5nt-w)mMfaOT)p*D)*VAYtuo zIxQsQ`{l77v7#SdsNUMr+Kjq;ykNnfo;TQ=L0MZ=LG?DvFDp1$e_`oLOy?P=aCfwH z_W4jVA#VGnO1WL#*>D62!meBl1;-8CVpja#wMYw_V3zwc!7pWUH%?yZ7Ktyte2NCo ztjrv+xt-a{LD);RDeP1F_`HEJatC5FLy=w+uOyy$oY*MV^+cN9W zMT%y-9igSS6zV2}JAjQsZvK`u;(y|Br`Pi zA=#W<%D5E+JEx>QthqT{y!#{n&3lfn{BvQ*JJC~8bvEb&)A!6qPK`)$nd;=xb|ag5`@SGRQJoKdxaneFf1Z@{P=pZT0tdm;aU|)4wE1dt*r?!8VJB zu~#x*&slyV7X%^kanr&(vmCF+mF(7PZFF&Ewa(7=yt32ze&*6^mmWlre*PT`Tp0PL zmmt&6{0H7=xKa0dJ?+M7Q&{dC$u=@~01l=wByE*(*Dt0i{O^gDLd?`{PqW7-mz(8w z1&0#^rz=7%D=(1wZa$ZMO<)4~@mh!zu`qNo`?q&bC%T{3^tq|4&Tf=W+k?VQf4HK0 zTQise!n3KvMHhAj?AqR60yaUY*`6Cth1}btAV-znK~u)iEP-Y4LKPBeS9*{;6Ti36 z!_q~l?PQXd9cIZbOibGKnJqH{T+evr7(-A2=|3clt6S89OC9yRn6I{KjMm&1y?ZK4%RQDoswl z4XLu-d2K+LFR3p*94DNn4sK(vN75S15#)PRxD0IRprE#~-I1zh0rz+sWv^$Zd6 zXaTn$88^3R=WW@eQkFWd!E2;PFaEY7thOiry!8XnEL5mFx7FwL&S+Gn+-fr`3p3!7 z|Kawz*l<}i$De*IIb|%SC7%XaW0S)OP=HqoxObso1O3AO2;~VR%1J;~`ma(&y+CvR zAlOz&^2691Xrho~kVAkDkns_v{Fol8^#&dvZz4ldm*5O(^h^2j=tdW_R@c3|w(_eZ zuUU>)Hzm|3=GC(6r8e7~=GcG&$yw3WDy4%wP1RO8xpRUl@y!a7h)@z^jKw2ru`BNaO7}akwt8V zLSJ~>4B9+)q{g!nf>;H1BQWI9R`;`q7TVt{b>HwwUfSZG@6t;g z>Uyo#lCRlhu~M5>`+Y~%dt$Zf3B8C0m@Xt=WTaiFSvuP_xcQr!UPx_LSLyZEQ;YI0 z&R6#nON~i>2Z&2kI!7tFU-Q!jSZJ*)(j}k@k+%F^Ow|6T)c*Qp6D{^>(D)U7yU#fv__4MsIh+>3OO>^*)d!m_OwstUNd{K=tu-!|M}xolVd6L0<&lG-$v zCs6?F^|(erXP}l{)4VTE%A3=3Zt={u`scbrj)|Hb9Ixe13vxyz4rR6tK2n*u!c=WF zj~Q%=o)nLG5R{oSy%_R>xUz)B*JGCk91SG5=iw7b-Yev%HM$f-QG*g)sILuJtY@v0 zmf0GQ>59945k1|(y;S$07!ixmxVTipphgCis@`aWTIp^f1}6E{z+jeO zoy>xg63zcL_{v~xcG~vXvP7pHq0^&wy|781uF}5y@J>p4jIv$-h$wT1GP|Hsy zmkVvSi!}^n{$D=f>F8?VEPGake_?u4OhT z&4FEMvc8J6;hO`w48X2>$Rq+xi^{xp?kyUP{sRk?M2LU@T^O)`U}M%Di3~vi(CUWa zQz>e$C8eb@D@FzeT&NzrXk4t#&0fB z88z>SrEI93k@f8LgPjeF6Bs(ns$7^s#T8XSoDZENl~RoGi**kXEq~PYW*W~G9glJG zXY3FYWZG66?G*nU=WuLS8G4G@8K^LVqkT$|D)T~4F*}^Xr$jUf3PxfAF(+6;KSpD* zl*^azo!m>6mNFq91!OD8#Z0j(8cp4@x;`4cc4B-IXnaCMggM4r@dQHO`{xI74l{C) zM}c5eLsOFjFkTRh0u2!|BN<`#11^1Jo(`07h3!5+b@%YVSq)!91zbEJZFqV1>(`IG zhjFE)mM{$mi7YfUB39SdQs`1^x${d{}Ea9>|4AcLSl4AeGZOFP3A zMxKW(3D!p+x$rWsZJB*o&%GTd=CH-Vw2be^z%d${(Fzuo50ortSE*H>q|ErbSQBoh zF+1a04X=nXkE|`p2&|~eraMxr zU7QGAdK@S-DeLVam7C<>d8?E{&NH&Sd(66g$vT$lbz1*gti>oFSz=*jx#yTcFVCJ# zXRUQBT(#IHo#F2G zwUM;VR=)I{p157q?3AA;>1)c0|NchxK4y?0u3WFCUTJFSH6sD3CDH{H7HId!|*t6Z;* zk=qmZvs!T5^K~YsA@=v3K}swoZ%G5yJ31FW?+q^Bv)p*|aXt;>g#1}3;Y6tU6Gzh5 z&}nY1J;w59At>leid~!Y=_B{HM4233N1-WYcI9We%JtmVbIm73=#KYf{Hg>-TbxN` z<{hA0)PUPr+KzI{SV`$TqOS>##ijPMT8 zrjPGdj>a{&t9~o^5!8|X_*QP-xLGq80&*@W3$yk{|CMM-XQTe2*^e-80xNPNV$v9=SV*D!QrC5#-ZB-VT4?7P|6|1?DOCqJ}EBE;7;QqXT+k3RoUZdr*v_*$V zA(=;8JSZc>5HV&-tLM{GrzE6>+Na_=1t)nL}zc-o6ERz zm&)toa^4<%NSIhnTlF@ICvhOsSX^y8U{cW~LKP_pyLDEjB)(6MqNa^a@0!>a0pG@0 zcY~{ivpdShJIZTpI|B@QuRY(}SeBh6h|gmnugN#_l@}J9%0&3TCliqPXH#9xiGL~P z-bz}&UbvvVZ#kcOxS*O;`Tia(HMs0ITutLG6Jjb3kcs7k+wQoH__X9Z^#^BlwuFux zK0q2MsoxE5{V2CSho(4)>X+Tj=OG(`(`!vJ%BkK#v*JA+S|f;JB`o;jU< z6_@{P>W$Zfc*cmgObd=O(%vCv5YPv%nqh8~-ePmp5(`)}wNRPJ-8Udsq<@%1=!u*g znD9nvEH{$%@y}cGRa%4w)AuS5=Rmh0k^~U+4=qC&9O@h>%U^$kt+8ycd6vsaJ4?f666j!-#cP`p z;NUNIXw9@WAt5Pk#IyvAKe?4j0|~?l5UuSVfsg6j)y)PBqRpmZrk@=7`8Z|3eTe1j zFu$c1ar$h3sc`T-y!GVaqj@J*-*1)@PO!NudMxy{l$GA|q5N;{eRot;S=KM+ZUc%o zL1H%us3@o)IjCe6FdzsBh(IA(at^jlk|ZD!il7vNWTAv2V@oJWA|PN<1OdrOawrPk zzExm%e>3lUGvAuGX4YHp;vYiYy5XFC_Sxb0+j}7U;Cs6vdJhanzR6*wjY$-v23_E% zZF(7&X2W6}<7P+whSlyY-4+re42>hjk#QzZ$MWx*Ou>Fod`%Y z&$0_!A8Wr1nW3sI3q&rIM5w8(rK2vz!|j((H}HKdW%XkiYP{k3ICC4b`DmV1pFV%F z=F$i4=ZMkVGnds&cX^-|Ym)XepGfSdMx2TH^Wh|`82#j5Cs-jIMa%2q_o2vI!=QmE z3h@YA=L@L&*FZ%?$?gFA@SN82d1!bpOJmxOQ+VZ|vw7k+G zaQ$9inRc}11C^o~tJY4RrIGF_qWaQMj>A`591>R`7uM%&DOoZxX1% zjk(K3>Eg@`^d3G|41Lx3mawm-&!vpp`q{c`Ei>ZnBVecQXEMVn3f{4O7Z1q2n=M<* ztD7#qxg+e!ZZ3lbze?ty-_9TUv7X-)rD63(AR+A6o4c04@VB4}-96LZp&!)=r zE%3_MN1B(+TFXlk?FSoNR#)qm#(Rlq%9?;&9j)HT#~L4}@lb{?x~Ox!;j~Qx$ViVX zmu+AGjc60egr9=rzOs9L zRU8gPYg*lnppBRDZ1muItdw`+S;X6*%xXGffN`?hUWSp1Zrel%yx^BVh@>{0RZO6- zKw|URh^l()Lo3xX(N+^)vhbj9_CzmEK=SFgALZXM2g&)$_|e~xdsL|(I&n~*=g!Pd z(|0c|q;wZA}YFzc^S8jBw}2o0=+4|Q!peK8Ds^K8%axy?I<+##&Au3=(6o?no3Es|jF zm~K4XTH~_>*)3aC*YfR|%TiyhZkKkl*=GB!K7mbM)dru@iFj|(S^MTh=JnV-FQLG4I z4}B$b?&*I2tn>+7{{YvDNf8Jq2HiRHsvaR^p_Q{TD! zQL{{D5i9e@>fhJ-yzB+n_K0etbPC4~+FT+(R)X=ASW`SJR_S$2ut+90CM;6$jlhBR z`$J`*_Mh9mD7Q^lhT!eko?*3P$7x(QlYcbif-XI7T)A^vh1)f z!8$@kOEVsAjOBBmfBMGk`XxgoUg*t&WSIeq^DBf;U{M__VWxR9GZiPM=JX*h>h-L< zc;stp8KArg5o!2_QMf(JiSuk#u`Zi2y~xPUC$|MdDbX;1-+^;+5eb=Z9XEcUMA&ME z=eSGu{wSLngWrshYo#3sI6wDavv*rx``O2cw*yYH%oT8DEQtjwkUt4ehMuz{9vpwoYY+Hv(bPY$K*kzsPRJtu>Iv{ynFP<7LrY{c zOUql((bIqlDclP8f=~!TaDraCtwQ*&%D<$h2Y;fc2hLFanf=NT0s?FlD>$8=@|d4E)>hOZh(;e!0Mk z+3Eciv-y%SptH8o_-}(WEYy?BfLH{8c`Yq1k0i*r>f&cYLiLaUg>dnrp`D$beHGz8 zger6jEQ$s6%eh1W-6D_W}M*(&g{u$WWag`+I8e9Vq zg!_mjq)8BoM9fl7cJ{O6k@*C!afR&{c#^heB77Ji1S9IUh-is{WB?9 z2hW*mMo24iw+aEjt&QRw4+V8ClE|@QcBr~fya`04Uh^{n{e*K10UZTx3B4@b$5Z*( zJ-En|^crq@qt=4vM6)Jq@kJcS;{~2T{Pf2N4^7VniMi3eK9|C?PZ5Pq2$xu(^!1IB z>=g8d{3`oK_N_fQp8P;G^O|Vpw{MEq4f;NrAEfa|hd>K~Nk^pm?E$X>6Jy;Ke4Vu8 z4PUvXB`7}G(em<&p=*;|%KI!4c|U z6;Tm%^?-W1?$Y}6NH82ChPQNevmnH?y6OrpkzDHbGWNtKlNi$-RAmBbzZxWSTK4Pk zc|k314Oj?U$-J%9ajt6r;+{w0$+CX5Dyy;nr_qSGMyErR;i&HmlLQx@;wETZ4&iku zQVP7L=I@#YbJIpI3u?FlGNXB?kNqTbFjt3LnI1qZ6_;}KEA${5-&x|6lbmZV7J@%1 zV8nf|QI4uy0N;yV{aab~-j7%6s(QAAX7rdY;-?g2tP$RZ6)l$y*0^HE6yl{3%kJey zn$V78YayUc^5y@swMZzW7%KJ%Q7_1me29vRi){DcYHu*y#4=@m^8Gt{fcg!9TwS6j zcmAv%%~SGjupBlY`meyOt?yjei)iHsaK4-n4%l^+4- z1d;xe%ITSzPbnJ+1v(FEuzq?;F=uAQ{U-bQdw+g=RR*%<80XeRQIYr5`!Om1P)h2a z1|(85+1KDWgxH|S^k(h=g5K<|BQMS(;s-(t;Tou8a|aicl*9?FMEDCptsrCuO2W3t zC^iN9-o1pzY)ZwBJCD*B?OokuymC|2DKjLUUI9V`?%>tn`4<91m;uvXFo*0)^>Tox z3Kj1Ktu9>*7Z(?YYruvY>$SzBBCryq9mWMcm;e&R>xacST8 zU8;@nJAi6w`k!ZISpsCp{7iB8luamgWB7ZK>zkG|N)q#k#)2hrgc9@>J&quI3ZX$H z+!h`NsTB`C}SDynf}Jn*Xhhxhes4@6l#9&*t7 z{6y zpV9|d(Ae168zf_E*kQYqhHuNZi}8ojvQPS$0??mrTOL9TRFy4ul&a;nuqf~5Vq-E7 zXMm~Pf}_|U=Z=2Y^oZmkhqv6OUNu$^mdlKJ{|{Qr2wUgvJ=iAmGM=3IuIdH&a`A4mJ>ht}@I=yQAQux?kH6L=;*5UorCB#@3 zV)$X_eAN-PS71j%!P+R(Sdr42KR>U^o_XAn?_1p;+@+sYVp7t;NRSvgqn#O7u*}hDEvCst!UIVKj z1$fKVt2)BCy!{k(b=;K6H%>Kmf8~=#RNxdxXtz}dwn;ie3yU&sPLfBcIZ$-roFl24 zQU7Y%YL%VN4GR8F!^N{BQ|ri*=gtUOAhTTYLNhPCph)0dZe%u;C5{qgj6fQ zdcLc9NzHfDH3j!3RBAE$@|7#xrdOqS(+#P5t+=EF0a;R!#j@b30bvJeg_1l|p&4*a z4;_-d(boHDCOazGVZ0p}=&P}Y7^1kA0xnq)+@FP&3Jh-?l&3Wa)m+8o%rH8e}a zQ!<(s00R!#J$AQ=+~fjN9!$l{iue)NfOW^6WJ+a*s@+tf{sW7>Nfv@f*T$lP0m_^T zU|8^@VK+2|jwRqjmkb$W448njcyun@PR`AZ^qYX#5nzo1FdE^-K|hM?fa^v$j+JLV zb#|tMYo&B!-tB=yyh^J&e4>$~mj#`O0rogTFiC8y31(TCz&2eDM=0|lA+!MEfMniy z`Rh>JOy?WOAtALQkZdi`aZ^%KMwaf{qhnLj%G{O|j?e;51ePnGW;Vboo1+b(!Uu5m zIxIIZ+ZH+K6nyb&ytYGy}CUg7=tYz z13SU*NKN$AhDQwl1SLSC>Kz*E--ks-!>$x?z>F2F4M288RrWC*QG;b9y^y8`c9~qo z9{3>K_b?qLb$0j6@m3)ueX87&ek%hRO&B525^_>hH)f8q!TL6A5%UkHGl2W0L$4PEFV;qvdss@XOf4L174yC&aC~6267%J38r=&f5#sFEz zD=pDsa$Ewvih6a$clhNw>2_^@IR4C~EUGo&3_%!9zNN3PFO)EoQo(A9ALsT{IDCN1 zm|GicCw4Rv)$Z(f2q2OPGV`t4^_4eCaoQRzzc>+PjZ5!k@bVcR=SGe zD&Vp1VuOYrQ)^M&FuRNx{)D%)*iMqKqIYo4NLQm)(9*O7$*s{S(c8T zf#?qYm}&j9(*xz#IHXj}&Ow(N#c`Q)Hzr(b<7PVN6^3_h--c8y>QK1)EFhsQ1I83s zGs;gn;|I#TtxQeBOkm{8b=E}f>uk2j9l-w+-d5#87&eNwb`d?;Dzn$_?H!vN_6 zs@jhuR98_u-aExT@B8wxy7!)i2}&|#(!x`+gygE6@znzFDLD|N<~i)bW0tS|X}r2( zxM+HSY?A1~FkP{+p4BrfEB(QP1l5uT08|qI?bpRUmn%7Hn!MKM-Wj`a04>9PgVY-e zERbWKtF4JOOXW*t?<_0k;-{;SAf`^sT&UNY;acB8FMof3jfMl* zUi(%_kj^gFm1AIApHG#MS{@g^H)Af)Kjy%8eN75I)w(8~(8Iq`9DULneXF}Vw|SJ8bPRV|k+jgmGz8I`y9BhrCFMlf6Iu+6p}d(J7cH0|4QxvE`- z93jC_i?AdDNV89mnVnlHuDNU|AN#ML5>TToyksJ|n{745TE#)};ue+c#pCmM}FJE6B_ha9E;oLfT+6zB`549$HvRQ9?JT>MF zS(H)&yVN`l%@=7&m)T&Y zWhsC0PQDG*K`F<-V?wES{ufHff7S)lgYkr@$Muwl`jQ_`a(BC9qhuDaU1o{FW}Cl%hDiEs$J#<#c?@Muy>&>J9?)AXT9$?N z{7NXKOP@#H2x~juLnXU8lRu3uOxR8N6N0+zoBUa3Mqccpx!^kM6{e1^BCZY^-wDCb zR7dI8EYF^+8L$aT<@FHQaJcb~_YsBj`sKiRa;EF-(S-^7hYPNsIFqEw(q1Qj{|(hU z6i`Uh5K}|YHu8#BCoK}0I?S%;bPU)^hG>^1$ahscJXbkVGE=6Dc2`kp)5johV zGG5%#P`tA59aw6=uA$pRIn5&O>r|9BT$=i7emeW!G%Ho7c#{f7;&3+fRwmm-W(b9# zUIg>Cv(D@jG0Q*IrBJmT@04f!bbNuZzw4c4pp(7Kj@`(Bd8gHyw6`|B-bW{b%bbM{ z9iBq@Px$(`pD}U0wAAU$x=`Cvn?EDEuV}@tk3ZH1{TWT=BU?Y5h41;JLksA8QnMa zQK!Xutz500sHcsh5^qQKPuPnMjt=+uj33@#NCz*m?`iMH*(gQ1L5D#i<-E6LY0=J4 zH%f~&w57!coARJG7DF-rXFY)S&a!Y&PO(mr&rp0;Mw@65SV(i~)`G8NH@Yv~`YGkZ z2T^){cXi~ec70LM>kyHq{7p%h43kVf-qQa&bu{%E{-0gal-K*ez0dvsF{Js=Gd?ya zWfsw<)Z-fu@H3%apBI_Lh}yE6lK-=;CM}u%5b7qRbZv@BD!Y){tWPO0=DVe)#n<0% zmOmgge^^&yj#F?d_4 z(rXH7qr)C8`mkv=j=H}25Il!1GK+8qwI5VJBU-*ZThFAg zSK}-hGUF^se%KGR{T<#CXQg^nL$Fxx>G6eE@^T)l9-d01y@$nc z_j3!|u6TC8KeiopYGXj}H<=!)U8ASER*go#b~?xTbgdOVU~DX;-%B&4uu_PY@mdk; z)NnsYd8}lUtih+L!)kH9UD2L0MJgWRhEB}8cW(D4MFtjO2OOw74rLZ-TJqMfcDcVl zt;-%!&k%n^^CV3n3l?K_;)80`%>?$6eH}kiXY@&OKBrZc`~LU(>~xVGk=8rjp3Ybv zh*>*}gZ+ju!$i4pOTJ@OaG~^PJ;vQ~JG@JB@9+BU9NvKPky39k=al-b{e}F;GMSIk zI6M4G32D-lCg`2$*PuH`>XklHku0lhp*H36rwc z&%|l`eMgV=+@>U_Vki0?@Swfo{*zi8Cqpbh^$J*_2PQ>77xT0nDDfdO;`7EF-$Pu& zB)gFqOy(K zAiKrz87F;wa|mkw!%!mWT*uU0hECR^E6akR*Yvy@>)@pOq;v&~h_WlOJnXGe;v;+NxZ1H98Kd~}s zUllHyIl1bv$k6bVHD1o^V^B})DAz=ll|+(Vc*!tKU~rkJB@R>6F341)%$r2cq;D<7 zHM=rQUX)Q)pgTK;pHp4W6-ipiWP7x(9K?Cgz9sY`mJyp_$eXYj8<88_pDg2#njUQ{ zAhp?FnKN_;xL+9W|4APb47nrUp+^{priD-D_Uyxicr15;~~yNT1)N&90PdAc7z znsj`_*p>3_j*PhfNPMGDTX6ezR@|Ounc4~l?dHw|3%|HNW!}!o!O#MwcJASnYQ2)C zR2kg21>p$>R4c7MYt?h|DU=%ab$rysoP_OwT|X`DYOafLR%2tA!19@59Rh7xVWEE@ zws9oq=`1!;XI}FV9bL1S?zd>_ur;86d)sd1@R<*vPA(IT7fv8d)cChIYt6?J%(5c| zxka>X>}~Ane^2Ri5Qz#F!5&RgRO1UAJbzNdk*zGKb#!TX_^kh=vw%!yW8-~QPNKs2 zasCi(pJ6XgX-iF(X7Q6UsdJ+G(FJ+q1%U?{(2dF;?-aAuH4RFB;7Y2v1)Z2yKG!u_ z&d&+dTmA-;Sq5fq^+;i&0cn16~e zOz_g5b0vy3G+twe5%x#DNVcwWBepJ=8zuIJ)%g<%8QPDE-$dA*cQwS(H;M*FVf>jA zUN%%WopoHGOj@EVPH|r8{k*ZTl71Fn>>oH`g>W6Up3iLle zG?~uXf39`z>6Cn`$DI*LiLCZ_N0Y{5(PD(IpiAjQXMqAn+FZ#%toy>;$WN%LXOSi! zP{h~v0{d{XGbn)p`!mt#uZ1I}uj^|ZJ*E9GzIj})I?UXwkU`IvI5-ayF*sS=@WIMr z7*$#G?HJTsYvZtEyRx`aoP(R4em{irT%S5gT64^@QSF*_CA29BsBv9xeG{l=8&>;i zp=@n_O>+)PCoe;HYeA|(UVurx&kT(9QV`eHDoE2 z)O~iO71%3iC!)=vm_rB{-k0>PIBzi8?g;O2LWkTN<%Ac6L*& z*%_ghQ_a@WhW2)Xu`egZ&0QjHCTb7}-64+{E2B@pbbr*I;1xIEC}&qt<;3rtlh@R7 zZJkX_ATzD3N4nwwj@?EiPi)C&%(L9N@0*!~A2vQwX4{O4iflIYo zQ!h$O1WhFe&lIE^;QH4xa3^#UoTuL~nhbiE6p4B5{V+GjB&3roaUh}6N~nPLp4;zY z9)8^l7NC=7s`Hez>8qOt+&>1jPu0Mqf9g$4Y}D4SabCzhfRPZnxj@fJuCaP!buQ4! zM5Hr5f~jZlMqS3lT%_>}w`;H75FG1KbOMB7r>~19{ZkVPZVwJ|s5p(h;%Jh{Si8I8 zlmAtYXzsc?pSJbT4#F^50<`xsSQ-7g?@u@+c}NB%NvI7!>tS=$l-xDc)fAGnaecHj zKj-de&`2ZIgzMEe-mzpkx3gbGd8x9KT!z!n2CwE;bObEU$PX5oDw4@#gtACsP>O|J zHjW9M%93~NB#f~32k!~bGbuRb9GNsB%-ylJkjN#5j7U~Ieur6Cv^mrf-|JLsM=oT% z?hw*rAW}ffpwizJ(Cx^(xM)@IbkR9@x&S4U z{{AedU*0LObEZ>_j1uS>z7nZ#4J%b#IF`*+(qJ97^cFYX5>tuLuM(77ylbw+Y( zWG(F*b8$pWVWkzhUD9fwLWna4c>;D1`7`L$i diff --git a/docs/mrs/umn/en-us_image_0000001532607778.png b/docs/mrs/umn/en-us_image_0000001532607778.png deleted file mode 100644 index d89f3b990403eeb9f8709b1966d59f882843dc4c..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 74715 zcmX_nWl&sOu=PzsAOs7N;5G~pf;$8YGQbcdxVr`z-1QQ41{nqo9^Bm>g1fsr4DJpe z_q}>w)vi~?yyh{13m)_=@aYfxo=0e+|;V4KSd6cK&qMHpV&QEz`?LXkC7$bRLZBbHfjrGRGf%PAq%Ge2ftb@Mr z9%iH@GLngw?0|Sf4$?fQcchgHPMA;ia#l`IAEBwNeCSla&c50j1m50Z7I+>V12T=I z8FYr4JCa^+;2&Pil!?p`{|;R&i3ZqW;S3I+MU)=k6Ioa#v<7BqaIT> z+Py<-c(KmUkYX}M8EkjRg+uT~jqTdy6$jmT(Rnu=byxSski{zP&`p)Yv%J(>f#&YO z>z_UN$VzUx>C77D+e!tvc9T2^t^|xS$<8bZ4(7GIIGm`Ksydvw9FACXZ%{+Fa`Ja_ zZmBf|eIDZDK8(OV({ZFohzigXnC`V0WME$8UhGn~lF35=Gpe6)?yRXswA-JYE1Rl^ zc!y8rQ%k|<7sT;$1F)$kU#EZ(p0KkD7+fwo`KULuk6bIlrZ#?TShJ;()~T_)M#sad z@pi9-Cuh+N&%b-CBT^{3f9o(g6=I$_A(7ZB&lMHZZQ)1>$Kr8xO(!;1K>@oD>8$X6 z3`c$(t#YC%Wtys+)_Q@tjJSW6coKA~uhG^@L8FbHkw9 zhH@*>f{Rlfeo@L1-nb?&;Ll=*qkl(9^#WOcZ`O~`}oRu!<<}vdn*p=)FeW_SY zO`86cD_R0V0{xEUrd(h=I(J#gRtjII@X{v>0R;gC19{PP^uKhP>sk~Bf z0)G~|)U_#N!PcLKE4ipi_534QRaX7R4fTGWUdE>zKZ>H)&6c&aL1_zNx(1U6Iawab z@w_&dL!S7ykX=LH3S8T;ueRyx0^UR7$-nhxulMHA^(afy)d>%^%{`(P>ko+2wuXu` zo+MK#Nw=iWKTtxf3|)gT;MN!g?qGw@eJrJfb59bIG})7Oj#kXqB_~k;u!Q9WqqVH( zJyU5R$1Gdt{^d^~vWsZyGN@wS1s7)K!>SN?;D>_Mgpr)ImMZ>7Q82`#DeQ5R3}U1Ncu>lS*PFj}J1*RPOPRw;COX)$fN+YC zV9&lDt7-coH^hb$cE4E%!OxwU>L+r5-AWQi9t_mG=fM{W9QQ)-IYPfhF>#gdt}got z-}0Nn)YwcFzGRfTD@|NWrXFjwXMz5DwI2hKjx`B$TcC^j*y_uNf?uP@q||K1NPriX zo`9iyz!q-zH=;L&m=EMeR3QZDB3$Avn8AeIh==BzBQ8tlW3!#LSHq4IS0 z3~G=KvqJ8drZ}+y2B!EjoxeoyjH$x>*iioxX^_1!RN4gaa2bAM#?CuO$W_JG-IxmU zH%53CoM{;AyslVthy>Wr$yPa?Tu3uE7LV0EQs7a(F$*KUn5sQpG@-wTuxCkz>QjmY z`E+V zOB?D51$Wn+HkLS%ke7GrU}O45)vP)U?pRtVr^(9AebGxK-wq-m1vP-I4So}7dL%h> zuhIy1mo0bvpAm6*FD3w+aQSy6O&DI$&%-A1jb#k&GB^fzF+qMSW}`OR9L+O`!=QVg0dqO>%tYb*9`3<$Z zG?1$CC-C0gAR&ZvigGmMGitU!ac8tv#^k)`+4V^9z{Gj>|s2Jps@EDimdnHx6T0Q^Ff3%0E#eBW0%C$Ec_Ko7GEiJi`(^ z+yM!4CjQ^}31B|~8&b)_0>Fq!*2FXdD%KkP=HRGgha+MwQBR#Bk&?DtBO5}-=o4@C zLH{lzXl}hva!*jVyQx>Qx`&oq5eKg80iGL}d9>1k6ETeZbo9|XrTAjXu@0yivE-l{ z35W_MH4GR(= z^bwE|5-}ES!f6DJXcCnACLCCy|9(-=86vS;MkJRtYn`QCoRx&7VVn{2e*YTZ?Nw-` z5M>G-K8rV|J#JcwIXG)rI(Z6IF!8O3RpUUlR%wVGQ)=X$)6n^bwJwV@^?TcbE6%DUVFmH@0w z07gS4e4!oqxiJBJG^dg@HuXey#4+n!M0UHEPewEQ=&CVaGfH0B!?iYD!X$MPGcM8} zS?WY`Md9KEa{4v18WQEH=7@c(BSPb=5phmo=j8N~r@KU#NqdVPqp_E@U%u;f4x=~~ zaUSe%es$Y-c;B7T4~`8V1vRnDv!L7CGwFo^d!0W%GF%gf@RHbB!EOYsKa?2x+o7|f z@F)mdA*UU37=tZ)R&cP_5As!tl2@0wyNcv$bjY4ADL5*TH^VxFGg*9_G|Fqv7uWR> z!}+d`)RpAM4|X;YoSrWBW(9~8&7*AoAUE{==j4qit{QSv35Q9$>l?P~nXL({J14_w zrE$6AWi+?vVV5tQhlJ(}!r>mRG5kib|3k%P%7EB`%ObjZzd4g6oU^ z0Z0*DaT);+r4g2=l_FRd`%c7%0>;bu>>S32rB%@}BdO;7gHek`l0L!6_ z4JqHdOjh{+P8J`v=u5m!d%Wa6%-i^&?o6iEOi|B7WgT-oh7Ydnoup@e~l zZ_8cdm=eC6DJy+M7h#*UT|ceV&72k!4x?R0^t+kUZ$Ql)m?>nMy1Z%_;*G>H?Fpg5 zMA~?L?gM*8C#!6G!W0R5n;Ik6{Fl%fPCmr^@n*Y}?bezQvqO#`B=J(g%PY<0Hh70n zug4HGfW3?ewaJEe&(gjg93L9$6d&r8tCgH3AYuQx%Z6T;nMdH~-|!hTnjy>B?*(1I zJ~NnAwgQvnDy~D;MKf&5ypt@a96NWo0ZqhJ5`K4@mtSzRej)d$N?k@MMu0mnI1AapyKth;h?mUi!~A&x}X zBxlP`E--$4cK6)JK8$-F{GHLv6a2;WlMt%E|7OhVtLaIU_yU=$ZQ36OscACfV)8QB zR@|4hn{?&lK1W#9R1|{wwAKvrnf*4MpFg?8VE3i=&5!r5K5bpavm=sZ0`&k_%3Jf~ zV3jOr)FKC6+(@*i92O@?v#PN)BmO3o8f3D#RaQ$EER%`7U?lmZv(l5uPQS^nUHz*W z^s~s}XNX)%(v~L3y5x)T_m<$Q-=B>}rj}R6o_7{ry9?>n+=gaqqI#&?Zl7`&)-g-9 z-h_tJCLoi^rU~hMA4D@)7al(TrT!ub7s?Mg6=NMj|HKqu-&!d=QbMHEDdS>EjB~Kk z`Q(IF-IpC!bg#hY4zf@blg%h_+r=XR#iinsPTb% zqESp@5xpqTF4+oA2C!L|ql8;HihG1bZ^Z2~fv7}C_k?I;p8{LLhb?Og90&5W-~h3V z&jEh(X)@LUXG-XoDLTHXQXygW!K<&(A0) zcjZ`*{#{$jHC9L6gEC^UmXr0o{^3}A`xxet7 zTz>B6z}noJ)1G`6{z%gT(Qt0u@E+AR330-nEsu;NCJ{2o&N-t}AG;d24ph_fh+vmCQCo+;jW2q!7I*(WkH88co@W}iw&1dDovGv$=00P#S$KGMa_I%C`mYbKs}nT zfnRG!{j}EwQ2+{LMeLPK!dfZjhAB%@Hosq*3R}y#4WQLodC~jM)>F&E@*2+c#b;kX zKY!Bhh(GiGO@IKR?WJl(PzwLWkkgY~j0cR+)?Ld`gTnL*-Y4A{nB(iR;4_8!a0w&fp@D@QVt!Gek$lL4se6<{e(~ObF7Mif50*5O=d3_rzw@ zLoF}K6M~5ud+|XJM{6Ybn=C$U3pnHC$Ekb%XKz%`0u%%u2N;ivSf!%!+Dm{skByE7oZLdTK-+C4U zhyB(B;-(1sy}967y${!375(F(YE-A>ij0&l4i5Z3UL^J4Z?OpJiSsAmF^OK%!P;1Z zPTXDKZi;fP|PH(%HB;i!%JX@wN$q*S2xTr|&R2R^4e+|W(o(_9~@_nnJH)F1!| z0*sOBOx9R$S3j8@eX+mqCJF4Y{QEO(ifm?VOrtTb5l!;;&H*DQ55!T+7rI+;xCXBz z4{O8(O5U0{31>-XVfQKhZBLc7DHzI@6ks)Hk&6v)64HH`!QSxZ>LWg7^?W+e?jCjcA6vJKV`$+AKi;CtJsN5q!7yrurf@{rSN{^9)&?h9nbR;HFil7~P} z6LxCa#hR3Xjb#)XY>XB#H=v_v-iJxjWZ(DYkHoMV}J*zwW)fbBKq zFXP~wi4yV$Ug`-f@g}`A$&9DhKICyiAjzA3gndhk4d)0C&-tyO-;Asa+}ZJY^HYm( z7A+_&W>d}4$taFecS9Sl?0xo?Fd$hzY$8%d8N@6GUvfVb%w0EjflX8%R!{`e|IU!| zbHx~9{95PgUn;~Ne+kjikKr2eANZD9`|EMv%-t#}uQ3(h|B6e|(453`+JKX0D~CPsdt|cEcuGfn?)6yCyR6@H z6nNsXza*wE7{TBwR@)tPXQ7aNJ5FB0{423Zc=VR{dDib9`6s*Gch5csl)m#q1AA6A z4j#J9FD&5VSNi2J)YQ4ASl26^o-`cFbrHBu&#{^LZD8vX!CELUAZJny|py{S^1YvE8?8%B0fk-s;VzgK;_Ut_@1$ZH3_h**rwKz9-halTg(shko zMbj2HV>jV10$k0yaT$*~S2z69Yi`bXK)O2A<|R@GJiV>7e=1M%C({`cI-+y$bhY5u z%q(QhE+2Z{TrNL8i0~flbfgH}94@|ka$9A4Zn45|P5yDRrc;!1yArwsexw$@?+s1< z>I_pZCEJ;llZ(k-5DQ~XLskdZ-A^(s6F7tTeekd4V$o(UV-Re10`&T~aY{Rr40`-N zl)T*FtisI}>W{|lJV)-Q+|do1ND!Bd$Joj6V1GIJb|szU>MMDeImYLulp+mKUgS=N3Vh zJzMHZx|}0{;mQgxy`AbAc;)#?wAX(90I70kOeE+rea3BbjdV`nM-GZnM2M)&f$92P zu=`1i_(3tEET{q!&$WZmXi2wmV3;^Tu|5Fl2pxB3fS>SO!*jn(McFdna3+^-zB(UdLu1DA& zF7_*+_HSV=t?wLWvTKi9944+=rEKXWee{wSWXO+dhGaI?=EswgAZN8FI=yw9oA}0Q zJPmrKl-DbMYL4}=+RnDagB$8w%l(?UFBfO)f@XM1Hja?iNHTV5M7eYjLBl{C`-E_3 ze2&>oD-LA6Ya3OV#>g&aiydL6+sQ`sIbWj#kt*C$-7l`?6cF{58_0kM($N7tHZQoV z)isz~u5+Of>y=YGRn$Pp;o-$w^>{+|U*>RC6cl{yG44I4&-~+n?=KT)v3EeQ-7O|` z{n^=``01Fj5{S0jAlKDtZSiHx2CiBK2V(-MZqLku)vZnnUZt@<k8JphU_A^4c=Pf#A`XkkY#GFOf8wXj(|kuepny}CF* z2*PSoOOOF4pRlkaKIr$>IFs_%=OFG$Vmurf)$Qu)ld=nuRA4r1(0=y)Vs5eh{!V%olm9=KHX!9QRwnjm%!!?xx9f4AGpy`wL@}-9j19}{; z&*#hP+C7B4Hfz~6B-={G((Bo3X%fbw#4}Zw=c{+bd^{b6hjNQwP8y4T%juDBV}R54 z=s}WhSLMp!_m0P#Ea{(?xZ(q(_31T1{Q5e{3yt?~9u|>O zp&MZQ09hTLN31vRgnS&G@oT5hy=UyIs#7*N8%>3-?v3IlBqf!9{20mkh^2Ep5uWGy zJo;I|wP^j0DOi6645l6A!8w8Nd+;l|*-upq-TACmcwYlAH&T?3u zh3aLsOu7-Q1cauYHX{aAmTv_b=x(PEFnyOf`{FGv`Is(LqClR%J}M^%L({Ep9jy2p z$3J&zeGZGSezkeQtv9SZet)~Qu0fBQEFZSHlrPYmIL#yF>X zS-$I=V<(eQYq+YBY3D2(eeKEkaB&ka_h0q-fEG|vu^?wt9KG6184LfnaXQ+q@|=o< zk;!ShVq4+blD+Ml-goqI*^#UZuc38(Xxsx|-Hp7G=^MVr?D$*M)*$2(SWJFdQ7~}C z?zSbh!tQ4jPA(Fs7FB+OnpFW>!VMOgMOmqDXpFrItAj|r9qLPL_#La?7ESi(Xm}AA zdLAZJ95y%m3bESEckKC**ysuUoyna(-;jH=*kHte?{%Z`a4TTDu}Pz?hErmGG%e+J z!ML)TNq?U|kfgu@2C9!Z96}UMi`9?Ju1m-V2g%kWMnu{+;ER6;zYwxSQ<)2y6eSv+ zLrWbV;`k$u5)94Ef({#N><$t3B;)G{^duru_EW}PJ&~ac^R)GH+vN4yR$b}l+9mFp;!=GCjZLZZZ=y3g+lauUrQCIL{Qdv+?PgdTGEJ_%Wm7&({a$vN- zRC>~_Ab%Roo4S6KK4Vn(OspTF+!^lRlvM@d8|P(g+~wA7q&MCyUeO^ZfEO6n3xa}78o_JN!MyYT zu{I|RUEf@O1vB}AzeNHyPc5PJjKZl*wV!P&rq&%0%;b(9reJZFzuLfw z60+j^T8<2Yaeumv}!7cTS;R zR`}6|lP62_>92s0ZcDk`MpuDSoM}hkiXV94Igl(38Y01AUgSfs#L7C)22aNKW!z9+|D9ljqDS zJrKr6O97j+&M7E>eetI@xl@pmVGu7?rk2J9!BfKheT2R&v!R}0sM&vWqsH9)0hxMx z;bsvp3CBZ?4u$1tE|XfVU5!hG$A?Gm-$nwIAB=WTY>Q}5&SM94PE_5I15*!#@PoGoLrFuvY%J$KOmC&xWV1Y0$T3bdZ5JKen$ zJ>jrYZ@>Odg6Zepz${NgN-GKipzCFKz$UV<+bx^8Zjbk|I5W@e*G!PWtplXtpbI}e zf*MFn7*=`iVP_?cX#9e_8HBw+O|HKY(-5!L;(&eaud~I}pf4QnE&BV@=RPxJ{Q)9k zG>2rbxt`h8B%5_L;g47}4@$e`bKj$t=VB5M`&6orV=vwKH1>6}|4$1bqBm`ov+zEw&I3DEO1jRF);LhruL0zb? ztce>5lRF)1*D{+(Hpw%NFU=3*y0mw==j(Aa0#8BNW%yF$3j(~ybgj!w42=`{II7|r zqkwqImi*Jxz46+PrUK+2xq>h%ajyCmyKTP`zhH1YGjH-hX53ds-FE|E)) zW2-joF434<~`7b#x4@3$NNI43vc&U8tQzK4yK^5y|*}xte{Ddz)oBQr$Y2Xr@ zTo-2?IU96;9OEM-deHF=Hf3{_-&IDyw;#I-z?=~1=D40q^C>l}my3`UW5BgK6RJ6} zT&;Jgddq3ADJ@9F-KAr);Dsky#^yt3NRMjJbExi_WO+mJBm%>D}GClOWpZg>fHR$NG4FcsC$9h zrBc3hWYmofKAP~CR|_b7t86*4C=_njb5Nr3cf?^~XNOqi2bHXyqx$BF-V~_V4oa5p zPRGJNldWMww-mH)RnnX`A=q_o_m>&Ht3@y7el;G_O`e^nza}rW`S2E3@xS3QGl>EM zTbPe$;E@*0MdWoB9)^G$k?AkAGcwLYB9tQ>OPAL%%vq)uBrADj`n7EOxHO zWB%zQfVBPOK&#ap?e~7uT#>8ULI8adg!l;nQa`>O@;dCr#EGMuATBkL`mP{N+w2f< zEL)^$fPuo`Aig5mqP!8w?!!asqNYtXXM!nIb!;b%nV-Z99;X3)I-A>b7M!e428-Y_ zQM>p5wmghAuAAJ=h~2Q}*p3S#Kp2HdYg)OL7sjzNeW&e<8=RaC_o}Rn(wzgxn6YjQ zC&(>EA}ccyik+R^h%fIP_1P{jI%UTT>27lOY7B(#1VKl86r0&wF3+WRuiOi23ojQ4IfW}K8oeOdf{3u z1SrXp*8t|YogtZN*{3u*sp2nK>%n3x8Y@0R7}Q2O7iMo2n<`W zm8P;!zd9J7(i=`1Jdpomf?MC=&y;kAlf8yuKCr;sa}oGE6Foegh3`<8XuUQmA8~keH&*S*_xNeiLyD}_(oe~CA)EI}2?7a%yjBXGm%9Hwm}Jj$ zz^iz7MNr<$+GzQ8>->~JF=7nm9q#ifacIU2#v2c^Kz_!0LnG4XvcEEc3>=Z(w1D@0 zO6^a66shDIqP|%KCm-H{VNNH@Yt%IYVSf6%aRCHSYPB6h2ZNxVh4^w-Av!*XW?5L+ z-*R-}_-L8vAxT9^cKqg>dv0QTWClwl0TeJD)7@`sq}&+4 za-{q&&Uapr#g>FK9ER5ACB!NNySZ>XwuyaXyvajL+HZkg=FPb6SvW;GmPsDblHOu~r0PBdwGb zjuR1X&(|RbZ4kYi1tSR5I(NpVgomH&?SGA!c1=VHzzM*gO(&4(flkVOwccnq=PfDc z(g^Mf3SMI4O@iMXdSVE`I?=zi35~(LZ)@F`sGq*pic*6B8KY^r%yy*X7Fxo+BQ_0w zzAL`WzDhlAhtOpb$w*04Fyk== zg%L}iWNMAvlnb$U_0XsnKU*TrutmHnuYGNzYV!V_nH5t42F(UozMozm7!Y}47kS(oaeIEe zzFp%@-O5goh2g!CN_sdKqErIb#xHk_^h2Omn`fc=r|oFZm&R0}1GmEN*~hc{rdyiq z7~@lr+|iv z`tssYfTf3-4$>Q07*y;selME}gvm0fS==Ppn98bVIwAb5E}lSu{?sL`W!|2o*CD>( za`G1`lOsf}_wc|;f5=HU%6Ndj#ht z)&}2aB!!cI?lfSk_YMlbq-F+Zg7xA0fOf;&&p5k6)^2JrLQVL?p7V>`LG{+>AWIt0 zl--_B7ksfpk1(G^#1=;ZoU4*JHD>raX^j1w7Gp*%M1>!Py~qx=dEo@On`(snm+XFg zBpA}TZ^|2FONi6f82yU{wf3zPsx(E~`c6gDa-|9G&a2)Yea2x7O?sJEhA*mXcJqwI z)tJyKT5_)U_yO&gQvo{_Z^dlaLjs3Cw*3GVQ;PF$c@kiPh$5Y`7wdn91%HiW&%j#u ztbg%IFoAMsIDUs94}UlFfR=l1ZP$<{YsrUk*;XXl!QQ*t(+9*J4-oJo!wJ_{)sVWp9huNCS} z$r9~kTV8v@tXC1S{7x2-&DTo6)a}@2FCT}f{+XsHh~hbUmSe( zrNzhX4X-Kx_S>iFrpa3{0@B1k*?q`Zu)Ftr+dRpmE|)36@=ybXCnIc@30k$eGr_p6 zTN&gz9dVKr&W)LPNx}-2qby*4*U^c8jv23XfB zCSwV)--52(@g}?L?;dEjgyi!>(+nq9ww>HjFA) z#L?@_nQmhm((H_+auL zGzBc*@P(b7CcN^ocfzrq&KcVd0Yzo7B}Qv3S3qZiNb0lsgm1DZ6s30xM14FDKLiWe zyG_L>xNn3xdgNOy_6zJM@&Deyu6roF6pI98*!olZbzjLf@lChCiS5e*b$-ZK$oSeW z8v#lp2gVhx^Vkp*t?5hl_fEb2l}Azp-Q*fP>6Rd^CAj5Lv1~;;Qy6~WptTLa?$hXo zL~kS$<(YPtw(sFK(LI?r0W|fV8G&QS-Y{RquqHBTA@f#U4I72qJe%nJ$Nupw` z!iZacmap$StqTX%-vK&QS0(m0OG&r2R`Xmv<}cW#eCtQ8!@uwd$fia^N>pW6`)HW! z6G@Dhqe{dGQ*vgH0*q_ahGng{4P_*(#*Rz#FI6cq2)=;Eql3a=)Sbt=kzT(fIHfiy z8Q&HY*_^s~#*(U0J1qs1_#+a^JUc3IC?c~HCre61K;hH2O`>=tx4BzRUGswl2@x`(=e#VtlQ4 z><;=D|d?RDXg1+T(if$k1HYmbN>J_;OZ@6IT-uEEI*OQHU`eP8PRCkL1+f>~{B#;QOUN=SKmepkbRFHY?@9@e8m7 zX)cBly0yKG>qx7qXcm(-dQgsgNp*~UZD8HxmSD9z{mKDk_0GC6IYmksFW)h0!|uo7 zG)nD96pfj8z6twA!9zq;INpxxrgk+}YZX2=mX_-nAZ(yGMQ!-CW7U^<)$_i43=8E$ zTYDu5H}TDJ#|^^z3hlJ?U@0U^kY z)EO;pGZUV=X^;|?B7dmdvK_&Gksx*3uAOF1Hzb{SM-%LeEf=?S!nND`qlOB{+dQG0PME2tuN?o+*XO;i;aHVDfgS-s;7?G#5xb@#FHY_#bG9VWEP<_Hc~8qAuEJs z%KUNZsOle+>}bQSPH^M?ai_vZLFV{8IX|&~#Kn*hhvlI_;~qwR)SgRqs=Z0RDH{310xe^h73HwdO;N6%NXA7{$fA~N6kNqoM{A#Tfo;P1wGKHp-&Qu z{w1)&I5PB0O)^gT% zD}G*ls_<5&@1dWuZ(5W|W$2HuHu)FFrY;UgN{dfRQ96@1xIIdXVu7pUG{@*psAULo zr6Xec~lYR}Aofk)wL(hOvFv`K_Gj zZtzI7a!_iRIVD?E9gxrusEOSf-Mze%VV7zQcDFBrM^7gEC$b$uTl#c z|0vvZ6kjoyyf7%zM*h)%HFi)G!mb@F)D8vU%#fF(1Qp!hVDDy5!|-hKhH{xF)JvQE z5{9dj=cap6rIJU;1%B;*7GgkWP|0@RE4JL~PAC3tX=JM@9KH;U>(btITw0g))YHq< zho@*JR8U;kTsU}nX-peag^s?Ez_=2UyV4HyiV13MajMP9i_ZV9U^4H_S6CzQblVgoXgWdR-xDhhDu^Ghh_$Ai z9cs1J7&@Hl;_`^jm#>KaKun#RE2p5}J&3$~nArWoL$KXnM^>mg`%q}ZRn4b)aPA%r00=1Z%oH7Mv{&nTwak8R3|kY- zNxb84ao+|=#CT4UQTchZnwk}-d9!>?d9Fdspcha{aK08z6!fK!k7%KqNb)xi!%b9wGCDeHLKrx{^>!Rv2#tIqx_~+&QJJ38OV|ZjeDgxSCQHy z(~JpoW||J*FQYEiVIN!~bvcO+KO`%Y$@17YQQ9CAuN5zmaD8O2pDo)$By>IU(rTo`wJxso|tBD|>lvXi;dWc4-ld&vAX4tfU?QHPgK8Lx>RAxT3Dm za3#KR(|GkS;YL05RLI~Tq0#_xZg*i_&!0NeK+ktiPECo`IkVp|!@8!Czm7A1>T&nW z$zhT8SJBW`pNE%wlrYKzeMFbe-A^L`GUl}PRf#a<*RMR}TirdaLsHLnkqM{rNM!%# zA%!Skoe$;V4qvYwFOFDGFVS4ar<-664X?~1mIwUlDRxTIO`;&|(lzh<)vz4x6mW`} zu_mXc6nUHc^A{+09(l3ZbQ2p!&qo!93Ycrp4zBe!()V~I7m#^{y_tNfv^WEMv%YAx zX*aK3F=xs>RLPy4t%#N#39nx|xc{2q=Gf8pgE#bUcehe?rg;%LcVCe*O<7<4(Un9> zSY&+KIcl=vlw4P_TJCNR$(Gn zS(66f%e2Jpq&>yMdZwWJ#-C(&`YSPxSY|)jIHi`gnqQ}%;-oYvUI-%qD$1*&3OJZ(RxlE7+%5N^e; zA?^P%sw7B7eWsvzNDnTqd~miCh!W@l7c|Sn z3zeYd>r_qAZVI`ij&F0F_b?~*-@VrXQB>MuBQ+i#@0-*F?fr@bz`v;28Gx}Qz93q` zPmTSX!F>`HMLm2`vKRv|*@8Rf0GrkB@o=~KBO{Ny59cgjZ6}p-_jz-DDBP`YD~Q?? z(SC$3Uu%x~?){vy3HR{|TfeTA8NZOHM!u^Bc6a}tf>MS1ATJRZe0%VluUkKYX}n~N z@p=4tdCkYgy~uBaY@VG(64u*#uw7-xw^LZrvIi>M`CWe>$D)N z%}e4wh@hZ<{!!|SLzTCsNE#u-Iw!&36t8bt_LrBQ))BVFE4_Vs5E(u6B>J@URH28% zpphFS#p+BxStQc+2?`$ znZmeukykF-u+q@<@HzJKMtCpqO~i^fu%o!=cD|oqz=%u<|M^id=YtFG1jkeNr1}^Lgg23 zNl@>;ep^;wpK{+X`05@2?oCzbm_bF7E$qA$vEc&I_%}qBwrN|WjouDTr)&p$nI962 z!p?<2n|y#@vJPyc9Nmmbxm!Cis#h72cAka5DSl5}G^b4%GY|3utwY_u6cFjUecY^% zJ{^7)!L7=kl7+%9ywn)h%CuA18PczTDnT12@U!W%=i#hF$vrl3hf-Iv_r{$ z7EWL7lB~<>)7kpK@6>n{Cp4IHlWi6zva_(_6Ygo_?MBV8ZdGY??!R~&WF}uqxnZEM zH>$xZt7jgaeUnC|b4KKQg4Oa!I(AGf{BYvA=&_G3pVD;65e3N4`gFYBj`JL-k2<9I zzz1lumOtyhFFkuoIgF1b(9+UO{XYFN@82T-?=V+<$SYefK|NPHuxleCbO6-w`9(OL zB`~>8wX{YxWJAAXLqBAu3}Y=Wq!J@IeuF!ye2IykwHymCvEXd6=*6D^xJh2N%CUrw@zxJtUC)w0@f7IlZxQf};K$6y;s;J|; z#@7E*-a>88LjPCFC?uSwZ!4XzT|A*jJYhh-gyEzxcXL6u)z$6a6fgr9|3<9GsZGB% zDpTkK37~te%KbA8XUWFQg?YwB{=`O#WPrILP*lE4BhwhlsmXAzVJ{`szx)b@**Rd( zBwr}43hA;6iCSuLMrG{7Uiq&s*=tC1qu82&=BMX|8H9KHB9#+a62~>N-i233n(`v7 zCx71I7?K%<)fLHSE7aTa0s>tcy2PL~!)f_cU%q}S>;i$sewEq?zQrz-4MB+z1%3FK z-vM!rF6~!HfqOYe8FLz)Ha4PNXcQpFe$sq@RMqI^P(t~`9ev2N5dwSH>$yy3ob?U> zFtVH1*$mokoHYbp2_hD_KG;^TUWRw2Ez!#aFI!~K{``xJPm4AZ9tLZ-a6lYm4>rz1 z=)r_g5#xxkkL&EsD z;?_k_K|kuDQwCzGulV_DoO;R!ua{u@*4zB=1*+Bycu1iL)~U8|kEnIv%8EUsukrhh~tiixXU%{K#~FQ^Cy0fHb* zjQNO|(^TYDxMC4$ZktUR^SdzBc3s%qEXN)jaFZz=h1O28YqUHpNM)B?fD&|Z8 z7T*xILo$z&F|99MXk<;>VW)A0(k2`3Xy$n9m<3H=#%yC(H(d*1{=b2T%!&|EuhsuY z*;|IiwJqzyDaJS&@4h;lp+}#Q8?jBqkcPF^JdvF?pySuwv10QScbM|xY+4sl& zp6(yrvwPMk88WNttuZumDivJ4IPx-=-OJiSovBHzT`urvn)WeQoolDVxh6Qp;u!Qf&V>&e^`TUhS7?I-3D*~mx*pz0!Xl!26E(ie z3NrWiUrS+Xm@~*&T$mv?eu{GdQPW+`j>?jg>f-CeAJ8b;QjEn5>k7tJjY2up#f3#D zhH6w(Bs?2zSv9wVn((Y0Hf2YqBbcNA{6UNZP@|g;8nX7$#guf%N*ffK$fgo*(O(0^ z*|+D$Hn;d`&;M%Np<^+2$CQ_ki5!dA$e6y$-2^24l zMnoxj+S%gu$svqI(S_bhiEu%y@CYV@Wf3MvWYZayK{->aFghn5)l)AK1MB3bRJt+UQM zJdmtu)7+iBetIe*8tKTJ_#?zDKSoh%Gait?Wnj+_k0gBervy1)qPlROg+%SlI8Zz{ zU4e2OL{Vh~1qB$3t*r%ok+Mf6jNBD9j+49wPjB)~D}QLcvAuC5h=q(Gi_f+uTs@Fk zcPox|O?k*rx1e}6Y>O4MjdG=>^nV)So+kK9FJ z@d=4WRFL>mW3R?X`ic3M&55usv^$EjfZa|%PLCAn0$MK?OrKc!rzNgV{7Cr4}_Z zWrEgq9t=tF5y9njbo!P2az0>Ay>P3Zd!JgQFOI0GsfjDPT4R4|9SVobT51|VSQKK- zb##7E@pk6AlG<=h9tiH{i#JK2*D=L#7BkuU;WfZf)wL9FQb9&?C{nznu?=}sC7r2d zP|CcdjmBy(xaNb+C}(`l!oZ{A?(=(zwiLnhtcR}^06MiFUqeSSPoc@J{Yzw#_)$4||%@^TU(EU@=2NtSN58ofwK8|h(IV8ZSZAg?jT!z{o z_FeV0>InvoL*2an%n>4WTkgNy0*mp?tq~)?wdY?c|iQI)F zuaOhCv-$Hed+h{{qmh3%__Q=1hm4sS6$2EOHamuC=edC$kNp0;{{VQ8?JVy>UPpNd zu0e`ojPc}09arjXMxb7?DXJ{eZhN`mhO~hVY4ki!tU6jzEU&q2At< zvEka!ot+(-_MmPoST@MFHxVZkjxmIYy588Hr7UhACf>o+7Va@C+&!34-MC#uBB@9v z!CE(sE{~LXpq?qMmZy6;hmi$V#vQDCzH`M=BD|M`Fw{^1*4JpzVi^D9PZs(5Z*E_1)=NbGA> zxL!vuS1Xi#y$D`|duwE9Xu?O|G(&G)6aSTnsGELpGrqTIE@)DJ%B`Vf&027N0Xt$c zwwqdZKk`L#xm`>|1k9{S=c6(3LzB#8B9Y_n!i@oDj`Tec&U|DrAqJ!iB}GYk+>LQ> z9%ZWh_m&9!#@NluiewCBQM-8|+%=BSk07H5*nmBy&uO$?(@v9aBZmgJt>$M7)6#Kd z^spB0Yp0r0R95TVI+U^(Ght{M4?Vh-htz^b?dle_qPo7*_ZJKCa*jeb&RZ@vT|PgJ zNe~7oe^KVqMq=>F*{!PcRXpafzGgJx3;11z47%(t)2R9I$<*m>3~Z9Xquu&)_Gx0L ztMPO6^1vTc{m&YF^pDAs;Rk4-Aq{qlBKEe7$F<(S+9W@?uv=THofz#UwYlFPQeQC; z2a9{%Vh%(D2GjLAGSh7Uf4WZtoK#G|u>k1UsY$B3X6LJ2*L}XOdHBcMX6&R_5ymJ{ zgqJfC9ku&@n$!@_^i0rxk^z`dnWm_)rQKnyi~z$)xv)f|}ak@X@Yv zetI=-F2hw2Ynr+e;1I)Exk7oVoMEJhN+J48Na+`_?;B1Wn5y(gkgbS5 zTTitj!qynW8RM`o-N4&i`eQSwhCDv53&6C#+p|{>|M~y1gAI!^rGXVm$ zF~@$o?jL?8*-PRX+v7do*=Z3+>Bwx}0URA&i8oLk#w80yJ>}|JRPl9pwYR2r8bsr_ zD=k-!#WsGAP9>Cr&5NCR1Y1e`X#dLYEH38I1Su%=uWGs{ME{a6T;E36SM@SF(2gDprkfN#IsSsqFSylXtVLS|oCk4#cYBY`0(Z(^WtBgXe z`dCEVhaHL2oMgM{ckZ1!9>G5GL(Bg}Mao)=zviwljR`qhNAeQBUv|E-ypUzYk5}aT zx>-D)Sd!=&hWq~RB@T{dTs9*HIZl3?Ot_kkQGNL!L@~0WvMi5l7F97?!TxJG&PcJY zM%jV4hM)HR$+41yw9oOkM6nBCUmbR<@ACf{RW)r1zN3s_5_W{R7OrK?ww8z9%7v zM~Z9=W(^6H@vJMrq-_Yut( zGK%!Lc%5#3p&p912K)XfUXY~dzOChT9r6~*ntRr!w{LoXr?A>UFLKykp3xlk zy!P_3>#5@4`99-yNe94|2qJ#!;rmA7Y@aVD&`VmCx!23uwSWHxaeRHr#KWl)*NHLy z-Cz-X8r|6&Li8Gi^mak{3VAgIv=;^46bu~1#gH7ik1(0=?5+&Yl>I=35JvgRu>PgScn&hmV)>~+3$@|N9k{R%o-dU}%&$%zoBci;G2OkUEi7%9rFOTVVo4(=t?>W*Y<4m8n6yQ zIzKpsZU{7?)UUduDXtLH$`EzFR!bF*eAd%S8wJyS|D0_)B}y8)QvG|2tF zag~@2PSrJWWVFwgmHk)unqk#`yu_m5`dhtf-%;hg+gpsV26M#4;%YT#eaIasu*zATJTwWP2m9$_LSX*VS!mVMrJ(pjNtgt2%Dl=cJ|W--@E;6cRmN zZgg19@IY%-V}G0c(tLc9N#O%%DbGF`q}Xp%+e+k0_%pQ(aJvZDT;aUCUh_{d%~}R? z2Frpf9UevCEC&yFa+jvOa&c6Qv*ZZ*Ai7y{g*WiYP4t=um0#|n!koq#_I}GnKiuV@ zvl3oC5%VuQu`Qjr@&=&UOtMPbQcD=GB5Gj(#S4rVF zGWQjxfsvqSUh(;LKA6kt95b?Qkcn#Ziy^)TbC-mHt*12)wI%=F-u^nCL%EjNgPAo& zr$xvdPHoMg>~v;v)7R_ACb?!k-e`Ze^W=kPkWSeTr3ERbZ`jC)0LqU-=;k4|^;ws* zc-ZrlLHwHZn$`k0-k5dI*XdR?;>4s7?nv{*l~4Cse`dZEJ$l_EelEKGUPdrntYLi8 z<{THN?<3;g@jad6jtaly0x9a7W+(q4?iT@JEY&*ub?!0x2-2Zd1%{LZ%<1g4poW#l zyKk1Fh(^^;NS|S!|R>MeF1dV)T=1;t<55w|E8+fiJz2R>^~$u4x}>ZPvc&A zQ3ImTQ=^41cy(mO*+>elX!6@PxL!9r*bjVIjHb6OT+Wlg?k?vevMaPgj1QJHqzp^= zprqk?YpcD+lL+nz*e%-pIz|Ad;TM$Yho2i42bLu^|H=PxOx$S8Xd*EHTB8%-!<h zo29`NFU#{EQdbwC`B20nMzXxRV@3uV7uCLFaH>wL}a z1od4d(f9)cy&*`L*Ee@RV^@9AOLZ3r!b30w*xg2cbHBupJ=g3#!U>qPh?h8d<putzhZRf#*a5?>2+Zq&1Uv%FpKN*bGl=94aqK;T@&n_cUy>hu1Q7mx0$C1cJ zv8`cgsCdl(_&T}mzCZ0N-^3HI0LKuV_)U>``_6CgF@Jqa_{wWa5&g1Y`M@CDg>Vbf zDy`@t&Pu*#l`%)foFFWgxT#Z^8c1 z`>b4=oPS7%zezIw8v@BK=T~_SOLTWs%T>jRsI}iS()1kx^x7P|ki#xpEY5_LxR(`( z7bh@a`hc<_HBR_mfmS_fZ^pxCz7r3Qbj{?=G=$sZ2~Ld@USY@mls?Ln2h_vS!{P6z zHuPI6j3la(isy^zQ4cB&4NdVvb6U8>rA%_96u7M@t6S+BM~^A2)7!Mhcto}L5@SSN zHAbSn#3n!sF_xP9j~-tJ8Il@6IxKMbBM?FcZ(_vSuEuo+5A6~~lUs+S#N*)s-woPl+&jLqufI22_K?SaRogCc{M0|aDyoE%sK)iytdP9Jta}LA zLypm;x1?7Y3GQ2UW_|l|=C7SF=_SViB*`g>NQ?X9cxXAk-u1=qsE;b;vM&9-60Im- zi1}Ti&$SA>n>V(vNdA%-k>ZW*C=IVYLY=$0WnDXYM2@cu zY;q;s-rG_q@z$zDbUX7al@Q`>h#NST(!>D%IV}b#etX+hvcV$Ga-O_=nynuNBl z2q@@0k}I^d=FrWtut7E!&}E#GgR1g1r9WqTd2<}ttRwCFN#(`%uHfgAPPZR!#~&X? zJXg3C1V^LbX(S6-IQT?$KNuEMZwb0pZANHVTgh3}<+Ep9r|9ETerCX+T7u3!;_#cj zhM5-N_=|H|J(hnN6?mdd)vg3iuk&wcpyYC^@YC}#-x!GHvDm$4G}=zDVeHCS;0rhj zvgE#*q!=j0c+ljF<#--8dPnPLUl>p$T2IdtBaYj<%DBYM=`Mx!@`mxy1OQk zCJ4IpFMnYY@u=&%KHLJN*cX$Fv7iuqdg%haohs}mi^!8f)>~RF6d=?=3UhYB`TFiw zl2fqLRm^siP>CpUq-!LuFSY1$oBnzyTFI(E?1eqEc2NZyd=vJSq^wd$MamZq!lYx) zyY&I^$N8OEWdik)y&xPBfl-F4*>k>&$Ui2RqirW%p2*zH7U=Ni>?(-f^BFm_LkTO^6) zsHc~+9eye^{{Y}uVxt~yme1R()T2((X4&XtW>Lx4WKXD$V62pDUL+N@;L2j-{VHiQM&VPWsk;t6Wfg(Zv_E@$ z+o{fDVeOd{->n!8mCV$}`PR=K-bh`g@RkMnVfDx&WA2UwC)4xp1ScumPt0K?Wo0f( z3J}a*(pCHV)9+4msC(9H{jb)HG~xAo7kbp;TtzIo#R+Lrcqtoszo*yizN#1rpzaaw zzWU+pxJ+-{&{F<|wQ3N)R#%ujemBoV!F$2eE% zy#9ue8>+Vgz_eZ*1ee_^D~oH}7#a67N8vB7=1-I+u`|e9-3Sg{8r{Hyb5%xNkJhn3e+V zgPR)kz*wnWC8{A<(M{Ya%PmxkbLCoqfCQ%cXne9g-b`XRL{EijejVX z3Vk1fMt+#65E;#<642qL^&G^KBJL9<$@=Pq(rs~;!06v43btc6A0ZQ|eIe(Y%DcUs zO`^&L7yWWTYjCdHF_@uITAoVk*+_N;S^@GxpeU z5G)rwstc%CE?1@4k_vJW9K~`X3bf8>q5v(U!Hc9R4E;o5*PFs%B5bk1s$~$u{MZYQ zf^z>FZ3DV7C96*#lW=+qj!}{5mbvY6E<>85I7QxGRbIXu!?qIJP6DSqy-4hOV2)aM zj@dSQIxi4_WjNXQ_X=LfNQ+)Chu{4xH{LpwMC}n0?;-o=Fg!ip>0`+^uDqWb7;2BZ z8?dNQt2Le<6#CH1bL-Stn?y8uxD#yPY-{!=s7uSR8e3HH=!;);dma z=NDO9Z0&aqM$rS6`zUTTlxRNDsfkDacv3 zX)v*^dC^tT8ft;LrZU@MqYlNLLXr4aL-H7lcP=A=h@hK-m+QtwNb|Z1I`e|fMWN-% zdW~N=bKGhEI`o7o*ym20-wdOArX(HUUWH@lN(@uF{x8e1PKEzR@N;D@y}g|X6Wpfa$&Ue7HY0?injE1@fF zU=&auXHL)1jTt(La@H@Mk==U7KRz=kaSH_G*q_Q5``b^B89YaJl&5CM+G=FPog9j{ z-H_9{xx&o5M3JlJFai4O&fe-?S0(AF`0d9~5fWah{0r+gwZGu)8OJkJePYd6u5kS@ z%`tm%xLHEhLPOv1J67w&>uP13LqMZ+l6`!h8ob7`3m&OS+N52TpU@<@)Dg9px!a z!grBuax0G;$RQju#H7E!s8~XGXYx+@no#2*&D1ie=&PSj!<(X##u3e?3I3@B5I-xd z@f-T6*9LsVvZT&v$)r8kiywaj!-#PyaHk96vRlAN$k+6VJ+7CEdqir13%4oN1%5{& z-<$Yy609dtZKe0u*V3QxHwW75Ml}yRTc0SH*GXtN{0wPQW9DFn)l<^isw*J!fk{uf zYHKy_{qv|}tTC;QoW%?>A8D#FbRoJ~-I}oQWLEcBsCE=+*bYEk{sp+bNvn;*d*czB zjDxqZlpQMfcG@QKZPOj=Ik6Eb*0XC%fL!R)irLIC`(AO#W;atcxjzSNd)XO5yDRWN zq`^x_1=S?-lgZK>_P2-89c)J`BT;uKhmz0_+@JqWhe`=xr-Vbu@SAv%{)`hU*!{{Ft@T_Ef4F#cAPY z8}1s;M35{aL1_N&&PR=>*Zq^qlY3p6ZaG2*jd2vpA!F;SUW4T^aHf_c@ z1l6va(OE|jiFKd9>Jwfpcd{`r!-bA9103;L1=c64UC+G-gO?`LaFPbEr)^Ha8f#Jx zU+*p#dfY@b#9P3=!-5b^sbGnTo)Xyf6MIVP+|fsk85Cl!6@B;~qA+iJ*D2Q?ma^SJ z-H4Y)lFXlUEh_GM(DX7zj7gO!If$gG*>|5wZSCCy6iuT<6=NuHn|D7;E=2pW^x5z< zFVMWbqccHjc@V|2%FMALZ)eaCBf7cMGxbEQWujCAy=5R-FJo)0Rq)e;$MAkM9!t7$ zTh(>3!8hg)6;>LN1S1KF=?}#&G<>Ux&FcN*6!;C~;R~PQ`Mct-48^!v`DU7@#zPo- zlWNcI?jbkX-gMI8WK*rNyRK3W=>t$&FqG|RwTF6M0lfE}MKzZk zMNOl|iVuIfF8&(}5J6ihX^3L3@eY@yd^6w4zIDV&#-y*CBQE51S3zp7HpFpcCDkqW zt)+5^3w}PomT~7;&HK2+!CM$@xR><|C>|p3sH@3Jr1=Zz_95Ms!9=z*3K<5EI2x0!C0JCa9#Qk2bH9#|?V>1)wgRUhJ<-qmhb z64Xzi#N9?i82nB^%o^o*e4w~?L}c9_%UK>Ho~8L`c!@QG+wftLyAGx#c3?i70|iJC zvx)jWq7r7c0hjH`t5-5M9Rvp5SW|pe*NMMvXu3OBqX-v=ej@>Eb|hc*26y6@RpdKp zlhrtk!a*z2!v~pg@Yaf>UJloX~A)Y6a zmnWm~>e{w;mvb1asjS1^A6*V*f?e?!hRSnXM%yyx8AIlJ-pVV)5Ls-9o82~`1=|wT zG*gd?pgK3J)ej}{m%?T|TlTJs*uzGn)0t8RcU|=8tXMH`b+X)XQT$11ex?-+JO8G+ z_u4P|=9!;o{JdimA%Y7= zzJ`Hd-5vTkI*`Nh_Lz@OZU)^hqdsNZqQoB^NCz+M(#cXa7yvXHs`0ehZ7wbrVc zuwq}yA`4cbk7f^h(VQgQNvtYNXqk^tM;b<(WlmnPAyv4n?$E4iKmikYr>MrA4maSR zpopl{zt4J=sRQ6)$H=U@ox?VF*8dBPa3^1Dk8|wkwZrqR!nQ_XBRhrs`Et7qgAO~x z>@rUSy(Fj824z}!IghQAT*RZmbuZ2v;^55j($ikvI3RBIl$U4sbVfC{k-A+cKocc168suD}1=d^Y4_)#8RxUwB&M-sk=?}B+i!PpJA z#&KluW&%zqXpA)R621+FHRo?4!esLXaukNaTBl_vLu8U5c z*J=>gzQ4T2w%87@(8rE{8gq!A$=&q*i0oAcwrcH4Uny^xmgh|$ zsar{*+s~n9*ZtHX$~L-=!AA8aOXuF)LW{2amBm^lrOqy4i;Ql4B3}>6QyX(L8Sd2h zuD@v{ilwTgpgRy0C#_M<(nnwlfI<^b)fVrD3RvBbz@f73x3{uR|GAhQtUgh7<20iF zYc3a$D;Vdh1xrz#E2t(2Bf+L}L-kQ!NE<)WnN_*?rT(gA-DBDA%>R-*Lfnc`VA5(< zbeudKK#Ga|{7d;6nLS?~Q-nqmA$4m0TliAyGgW{3oMHEkbOkvk8@H}tdTwZ4R6Vs6 z*SqU)cdXX#DVlmLf)OchRU0(H$RED~oxZ4{);n-$eq+YmNM}E(x-0SQQ!sNvYoa8G z+dW!!>I~^($%xr`#P@K^=#i$s959Ghl!P zGte3N0bER33aSGa%Z}X~40uvC1x9YuDh0h7(Kmgh(y_1GW>p_`eA)-%LK==`d@fZ> z@6hYWYWPkQ6(J720?gTvIAO0hd*YT$T!6~ufhfa{nISY<0StGcB?o+~;^bXYe`oes z~gzE@*fsp8J5A+cmRhg>V3_>h6k zbF=x}uM%Ze>0{*lzIuc~9YGz?AFE(K`ob#YXJ%y?sybf1>h4iKAyZR2e&zCTCGqNp zuFTM-mD5(tQR&5_Xor<{2Z6~8@Ohb&V@c<0>pXZ9foM4BYgaPR*0Kyygv}nGrnqOI z6Z6<=B=@TabqRzHP7E`+s?#c_Z%4Dtc(%51M3k!#r#$Gw+Y>W zgKq6*7~uX}G={D4=d3BM2J)FCOyZ_QJxenTN}b&GWi0t0>1c~K!-MOIY?CgZMEIAO>?igPxcDg6 z*LD_#zET;bWqSSsmiqMhYp!^Le9cI2Babc$VnpttRHc|_TWBy6}lYdqybeI8X3 zp{X$1xXRwHH4$P*8N$(I!qwU(xc`{URqM_GdO3s)bH9MY zV^p8H4XWUa)FvfLN0Jm+==$)d*H;>Ya-Hk2i)zXT>}Bvr4^%we+`L$HDpbQ4JcGA* zH>sYZtqi7jc2w8zNHM?(5H6ol{>FLbA)kc3lR{hHxPibVeR4~8Q!QepfXq>-5XXJ1 z+NAl*k=@k%AdfW54~s2N8+;y&i7>+@8S_{b%61*}>ug=z)-L6F$yjHvuMVroEd&LO zu^;!Dn~nh4RmU>(F{+JcY?j-J5k!-P-E+9_I@Y^PgSF7I z4l>5ZC~!I*gH^uL5x$ti;D&cCS`y>41=$7w)PARA5!XAyk&?O793LMosHll$UhYqL z4mRI3QLel}IEaX}MuPqM1G%}`@F?YYn;tr_J^ep)|NODRY51#zsy1qxsKU?-Mvr91 z;+o&kysBnt5k<^1&+La`NM0RYrHuuYXSAssSi@&ATkfq7dB#FbJA zWz37@=;5w6L*sc8A?1*5&V@vP!Z%Q7Y(qDhvo^r*`b$`ZA}E>A&hSl96%l04;qHmH zW(f~$^3A<;37Z{8Kq#JCdvRBpcb88TyHELAJj*9e)D*^dZ(HMS^;c#^xD{@tLV%AV zHG9+fP}Qc@Rl-;X6IJ!COwMu&{mSDb4=ro&!PJ<8tdd@U5+zH{$!8)4DG{P=+WW%- z%W&**g6BPoMrEQMP4IV~AtPY1ZE_zi(Y&wEJZ^IE<8il#IkL4V8?u@gZFp)he zl^H6Fc?+iv#~28Gn&ZO21aS6_-N4-+8idxzKLg?sEV__q7I*RaoBecx0wzmW<=bfN ztLrw+N1A0g%wJR6AE2HsX%^mGh-NIz<=T=q@nju#@(@&WL;XYlKqaYWZl|A82$U+o zIFYu`17vM+q~pxbs~5%IN55ii=2*L72=yvkd>G6AS@A3Zn4vW9Y>yp8l`Hen#_!#Y4HXjGgIGNB&bnLhxX5qsm5We=)KxR;kA>9t zBrD&%Lg>-r4hf1yPxt)OhY8b*PNzBV$4fI!x)9D-gTl0I9XvHCQ9ovCJ@t)EZVk3u zEJp9vJxwc|(mYSDsa_c(W=<#9bZjzs{;ByM>8g&kg}`WkIfOeGF}cZz;ozj4i^HB& zA6R*lV31%6Gjkba1#k&KdsdbI<@waWu`l@Qi&yjG?2=Kl&;O@B>A@;#82aJLX@|n# zn6dHca|VBHY(F@-dFIGHZE@5g;tRYd21BJyG1@g)N4I~wEC?|gDK8+MbxiV^g2UT{ zuDXWO;5Xfx&-sV06>63UdPi;7-dQlAr(q`L2s@w*%rQ_#5v^gvOOUXmw ztqDNwtc4f(7>NT;TW!|8ZFU~be54%`C{ou<8v;yyda?R3be^Fd@*ekA!cV+vJ4)l* zgN)4;V)cgK)ou5=G#Zt`C8@HP6nHt&x#Nvp?KpgBsrgWQaJ0;wnPI(dXJpL4%|nf) zbX{fewD{TqRKLK%H=r0C6k zD8N(Cp)1Gl^YplBlX)@j;K9!K$J@NhH6BqloxPok&u8A(u7m(cm|m9Gc$40GUd|>q zOk)J;tZG;pL~?B(1&D8lD4lx^G4%4dXIS?k&wQqsx6R14+ttS%!%5=m%()OvW7?n7 z+wMg$w#r@w-O0i~igr&{FbeM}+do}9vLzJ8V=uivq8e+F+Ys}3FbWK&9=k?*cMf*Q z*J6ik@8=C+%`VnZvptI7-MTuAVDC z>>S_%&oBGipC?^cUeagwnpU`LQ%|S2F661xFsu?(2LQt8HLgOj?SZrG`{oZvTAh!Z zVz1`{k&u`4s%F=Y;E!c>uq=GW5r0T5!5?rt+r@eV!~pJBF+^{V1bW^ciNV{`;G>=O zr}!I+JL@I6B9|~k4Rvs3bXS2OO~j&Imi4R{cde@ynnIs$0R@RM8LK6c-EQN~;AdQ$ z%#Ee2_anoaw>KBO*uQJ#h9=yUgl1_24=>vwI(rZVTwI1)!*PWp7n>$jAin((TVRAr zk^7bRN4@p zr$p6+`0hOwtzSgW-0gl`(M}Ba_1tbO;jo&=C7L=v@s6MPs?mR1R)>R)H&I(DUbLy| z<3;y;IVsS&`%cJMpb*+KSCwnyU@<5~UyIA*nZwl>kNslzMegA#8^)cIRiU!Qz)kVw zXQq_EKxNr(=nhs`bk!TUq#-Y*+*Pc?>gc*ir|I$jJ$OiTwBHa4?ZQC4LtnNRgHPF& zzgb4a)#gr9_v|(?hMoM!S|FNF=jCrKfg^jmn$so&EAV zz*k^XV*6t!i*6pX5U9D4bRHbYoh7aSxdE?Uqb1o_(BV$c^J(o!55eeY+N1%5f6>)N{kBgZK_MTG%*nUEj-W0UcBejig> zj!{j|u(v1niLN$!757YBh==N-ZlIqScU^069I0CF*g5%GchvP(`9@CjKtqUD(WapG z-z>WC!Ty?lB9MT+P7jg4-+b1GI;vdwZ@&y#0Y_?$N#Hd(Hxy&67en-RRHSb3Vcagx520_@=A zh-oRu-Olt83DW#j(?wJ@@xwOxxoDLaxC4=sV}Yt3B&`%$#_bo;GqFkW)K~^L?tb&- zi!E*&IGizl!Xa8unaRRF4&uic4;Zq|kD|!Q+!^|*mrjUww#G=cs94d+Tc7t>otnF4 zTX4V*lRZgt`~`jo5pr%M5~&}-GSS^?yFaLS9e1RBMaJ=Ca9L-jr8lM!((C4unaR`|j?ZWee^FGK-mGw2O zNT!g=D)2yl4Lg{srQ_gaPL8MW9hA}h@=d4A6P7sakUkoZU)hAJuXmR`DXVn@YdRpG zSW!|I|9+cR-??2Kzn79Y&SmD@I=YQH~0|B&K<7%&!3n)%FZRkB%-eFRtfVP1WwFj z_RM+Gc4vV-WA;esJDXy!ZHZAr(aNwei2lw#W!`N~spB_W&nr^xWYN~gX0In_IJc)` z9+~;8gz=*H0ON(Kfgcj_CG|}mkE@5l(1?J!i=AMO1PT3gU+^TS;`1VyZ18hR6S_Eu zuL+$zG&26OR@5P8Frsx7e%8oFB>}9Ruiw05y44F)z>5L^^9>Vf}~W z)==ozt#(ci-!Ib30J>|5SEdndebm>bpu^El!g%}}Cq1d_Fg@+#>oAqJ;FPl{vF})M z@5l_+s8vDg%d6v(Q=fiGZb$t3M$m(+l3=Hd=lgK(E6-59=8aUf9XsDy83fCXX~696 zv-aQzz{Dn^P|klAjVrpe)b8=99;r^xKlbpS*s{6xy zUiOd#i{uPvJr=tw*%y}Bt!_biL1;nf9d+tPj+g>Ox&B0g_$-M?d-4bcj`?v`)sqq5 zMl_`*J7C-=0Axbzd@Xx;>Y7Emk8x}L%4nqNft{l}YI_5%S2e>p*6oDD0ctp(t#keX zo9Qd(S;i(}DxJGC!#x~ge#l_+tv`e2iss$V`u-2b6{3m=s~|!)S;ZFiTJas@H2fRY zJMtCwvya|qz%5x9H>g%;`tUs0tJ^=J%fZHaJu)yO)v79cHuOF1 zuC;%L9>CFqgj8ZOjnME$b3(d=%w7A=*hL!CH<8%+zDWa;7jIjNz<;7f|8fo+jK7!C zCrSE9@TvJc2I(z5J)Xf*&hH~L%oaYao?-wKI%D2J^g@PO^AFQa4&4@qv%j;dPH=@M z%}kXh9|F&pdG5y}Ar4J})EzzMn%X)$Ra+)1|7fC}<#Qkv$qx@>rjA+>!3U8Ck$*13 ze*W~)SNC)NlEK+SU>|bXe4g!bk(L-wkQ=yRQM$p(r^}~IzJy)m@b+M-bs%eXVi0C? zyVNVFClXCE`L7;lzJs;B7Uu&rp$pq04{(~D0se~*08R@*3*qx?{olI({ah5J7Rt0m zUH)Gt`Mbq`g#9lI;r`8+2nuod|N7zIUpE?zzK4=PLFQ2*dU<5w=kVm3|7QJv5@N?j z&J9HdzEk_h#Q#St{}A(=kNfc6%!QuRMNsMUyu5P|Q4kUI|77N0f79#z`41Tplz;c5 ze>3whrrVSL7VYPorvIB|g2<&#jtIj4Db>FSb$xzESfl*S)PFMbcP!w&D`>KO6G8d# zY6;gV@BD^aT6vLok@ug9y0HBJA)9Yx991W6g4zF#`HT4<@4EblssC){Z%{bwXI-hk z4f5NUz8kCbOiy?g!w205{r&p?62a%o|GR9jRSKy6u0g2u|2M= zf3656=g8s3vG?))LJI08f&6Rg_+NUk`znom@8KVyhk;Oj3kAcA=cwhvKl2S0hi)Tj|fz9{Ve|Cl61KkoU#|_Q_46i1b+*z26S*2JD3;IP){j)NWJXTEZ zQj#qz^25#hm_VVYIDid?v$M0Rz_CV`6BQgh^jHt~xYO8l28GX?$7f$&Q&%!_uQUG= zX}lF2+aM@B<|vPHc}hnLecO#0n8sl~^!AFWSKy}-VRQUOAEtT7w@T zDs*K6z0YONPS;|~$p4K6xOMH8cvnIwPFFvKY6)^40jGbjXYBg8=7jWxQ#GziwV~s7 zvkKkvJ$28x(i=YjZ(_+F_)7dlF?(Vr=C(%y&oOU*If0o(zdE|s(T^@Wm8a4LHODUT zj&#Yn1QV(n59E1cy!f~)23XIt7tQBgLcYEwTD=DCZ{_>F4Ya&TpE-7>5^O$n_)zd35dkzWnY_@ z7DFlDx289*nWg>t2EC+O>izDNPI5B^MqOU^rKU_DPg=~>bHclDG`iFy$&j&-rHxHa zI?Ws(ngclaB?ATkW~-NQVL5e>rmTZoI1y2od_yCu%gIg$VnVF~B%d6GzT;L@qN*ZO zIlh|r8^fb01lQxqyaBPVr}E292JiR-FP`zdz3Fr-tu&x$=q$6vm$YKHk><(curIgW za;&(}ntOrWJM}WS*x*RK-Jm+y{IG$t(h@d`W+0TcG^l2& zRCfHp_%JJb=x>^kmGaAOaqaWom&=QimBr_riwqGk*iktt!o;Xvg-HA50x8vT~?hho&>lE}6_Ut3NzQqQ2uqf_^_93BF`{q0whVkLZqEO_OLKlD+AeonAqWX$z^ z4usoxqM*mVlX#Qu@twhkGf^#R$W!!Ep!TmhY zoeZK~w6ikTyyj7%^ZX6b6zfedhd)7LFhZy|2hxbn(G7pr9rTo&J)FKNVoAk>z+<@+ zD*o91#S*O{HAbUTMhp{iLbEs+gC!#7%CZlwC~Nk9*7?d5Z!Kk}f6oCrmRR|0$^rh# z|Hsx_2F1}u?b=U*1$Wor1cJK^!QF%VKyY^_xVw9Bf)6%0AvnR^ZE$xT;LLmKJKwMO zUw2hk?cP;gyO-SewSp4XJmqq4B#Yx1#NIkE@@i2(f1d6i2yM!4Y+1KNKq-}AERHLLJJSp2i8RZ@r1~6+OF|-lOS+(vMm`>Jnnl~ZoVK)N;T_awC@PNI zk;3@!TWGy~02>cas)#pIRg_0wpU$H;NODL9>vWSs`{b>)D=5&35wr~mhfX{@PCkRX zP=pGsc5vJ+Ivx)5Wn&9)v>VAweThTrAUR8GQ{}A|4`MZ|i@>VQ`-^)EQTpujI3L=g z81%#&cA>CdhM+v$sN0st+v%1p+UBhv}<=Kh!V5y`BZ1^>y8aEaKkgpZ;&UTL4(`gD+%Xh>OIyoxkPx1FO5TW1J$)I}2GX2I=YAwzAk8z!z? zCm<^S8NNu!t88teD{EgGhcJAW*s=?@&7O{ej zuoRosYqwF*4ov5Of>4QJ7|GT-${se@U>mvnv5zVXG*! zn#nm>=8~02s<%Iy4?5OZDA;4C^x3J7epp4kFw!70gi?rVW0q(jnK|8_DgMb^UxS|7 zQoKFlzIXdak}_-L{4po_?_QqJM|pFiEJpNN7T`$}2d-i)NRzI2o=J&sc6Xwd>~Qo2R8Jw|++I=kF&NRXbWHcBdPp0qxQZ%!1zA z0(j(}Vpo@k_vTAGAGVPUd>Ef*FI_9X$=KAJvaeLlm1OX$YWPIPxW7~c&JAzI4H?!l z{`zJqtSs;obb{gfW{lIbIlJT)Qkf^i-%u4R)C`GAURvDc`t61ZetSZoGz=Wxe1GD) zpsa>GzIFNCUQ!A_PnMr%r^~Zl?0?KbZ*g>^v%6*mh;~H^5Oa8CE!WFrwS*3Ih;EJ0 zC{Rw+QVxXH#;d4Yk8e5>xEUQ?pqrWenR!k9?r7$?hr6+ucRL8=7H5y|g`?rzbHuAIh@U2Ysu5;7AV;1qy7nx!e2iM(4xi2l>ul}8h z!@RFk8~@|A7=3))EV$kt54^ksi(Xxo{+r8i+&K=pczjVYc4}}#@eUfdul=@t8UmRj zKi#~+Sly8S{Kt+|h-_!mT=q&gz-Mk)0@A#`)Dw;Wnp#255?u2;A+S`%8fRkT232O^ zd~0k3lG{Kc#Gs7{8DH90TsDEMWA8=2<_gy5miD!8IkuFF#JB$*t8V?5P18pfULw%(_&cIOf|j$8iMvp8SdbO4L`*Rnk#89`%RPCM8=0*5Fh zgTL)RIO2N47YH63XUMo8(6qKCFta~BwO;%j{yFEuWhZ4Q9Q3koNK#ivB`OvIexk2G zx_k3B3lc@{%V>o5N1Xlx(T!H=_TZsFk!nodR`UEn-E1~#C__fB`eO_@5{`Fvf(1(} zLOb}=d27**t@q#v7r^b|IReG^{TZGyxEu85)Xm>(vRUAQXl5;eg&LRieL5VgG&7#K zlotLHR+^#eCZrV5i-X;(HQZ&AW4!;>DSLEtfg$j0HAL=#Yd}#yc<8&D zUVBg%7tR&vo~ zRyE*T-?C;ZEW%W?c2Y7BKg*MkE`Ole@Yy&5#2gLew5lgL4qsHiFYNc&gYJ$(FZ$sO zUUvZraRG1pF$ooUB+7qDJ){FleY1k_$lAw#q>PhNULP92_f3ihj@!+bu-jm$E;L zqQQ2OI%IY>zy-d&rRE(N_%dPXvn}O3mdMmkT&>({j^JlzXlE?8yGY!w} zFpU3*H)0eoZ@ijQ0{GsB4vD^wy}ty$ZZ9CO&e|o=?^=$m(e{<*gcaxG``#i-~S`C%rxHrH;i@u^5r6WysE$#TqgwVx8y~rXZ zq0ETD25q0<5=;K_Mn7?MdrCsMVtRz2!@^Y_RO&QOAHC>q+IW5BU9v`rWGO| zNzDfM#?tau)59D^jf?q~^Mby()aXT9tlkvPkgit)bz3M|$dOEfPzDU%wF6ORn)`=H z;?Wm%zHijdp8T%e=q==VvTAm=YW61rAHmDi<~e+h&h7p_ay)h(>vcdIQAf7truktu z`Gxc3&*m~1$l^%f(zqkrAm_`yF2i**H8h9cpG2{3j#e}?8f`wfc>3ckJ&fhl@~H1u z7A{eGfl|Wzvj?V3yHZt=)d|2Oo-=N_EI?WB8E{b>7?CEyy&s@ZG`xVi>GZzh5RGUp zcV=^_|6S)7OCk`_a+9eYj-?82y|Bj6GU0aJpLHIR4|`Qa5bof~g&H&5AU{YR+OXlr5pJ zoAJ9;hOn>sj#wZSiZCnZs{U5`@H<;FiPY1<+2X{HzFfBz_0DssctFFC&rj$F*PA)b zd<@s{LS<}Asus#Um9IOoEpv=cdM#Zqf6H?m`9vgmFr``*IuL4ZJ)sUmldzPQ+A>kB zlsl@fZl+s_y64G$~MG{-M+CFmMRjNMSeDLOnIU|G>&o*ZAtE!9b+pB!JsP*5od z{$zJSwK~l#uQKuc(B`pisHI3EAI-h!DJQ<_33&47rX?A;EW4R35Fp^kO5%vg;sLiA zVM!YNbdLvKMtIl}EATD4cqkJZq;(PNYRv-yNkpSL{Ob8CimTd!hc3ij_uOF5aR$e4 zoO<@0a57)b|CQ>W<`>AjWSXX>q;Ar&0c6&v*S`}e6&0Af9x?pj)U}Sf1serfDg)>O zt%r47gPTb+)P;u)jnsf%f@I1D3kF(&PO))j>O@QHQ$`5^{zUpM$+7iRf|;uz_QkpK zuYr{L9Pyo53R&wi3SfST95{MB^`?XW>wPyevaXh#{TeZHx9MtSD*7xX@9);j)kKLK zAD}WnLl!=yXSe459MIypseC4s-f7}?^}*F>$^dVq?v)bo3YEa9C7W#hUe$Vh5Z;mU z@!^-Gx;C#;s>A9yiHbGs=%b^&O0=6 zc#6-m>=KE|Ty7GH&_yI{<`4T@75-uVlD5`N>HKhsgEDw4QFW%Q{vI_Zdc}jz_b*UF zjW+XF|5f$#u5hUaCsC65p{IDlc`S>OWEpR?Q1+`p2uYb~bZSjM$TJPIVx~jT`)ojfEmip0oezWBU#}HOJV5 z2IHjiE*%fPx!t3A3s1<-&y+S6j`wnDHCilM*Rm+n|6OctSn3_{tIN<*oqg`guc2xA zVjNryj2zLQ_`5#zxIc?RaDOOYX};>DbW+7>Oda23ZnRREIC}fsSFJA;^RdcLZge&R zWBgZ@fQsj5k4JTaxm?I0JbGb1&OyH9ea^_5ndk3%lpT@@$2z)*h92t{ zGrGJLcctFWa{4Tb-5c=tmac>;o>iJH)b^+~+R)!V-n{4oCd=J(bku(jaKO_Q;B zb>)Aw{R58jH2>e&m})Q$nt!#ZXXecB*CX8P+@i?8h@}#~esFz}$9&-d%<)%`bC+N2zWmlFJVfdSLRZ%UE%kZT$Ay>OZ0-H ztrU!cGNUmv(tt1A_Z*dLlXfANWvz`?@IA6*~u5wgef)m~$J*&a{V zb^}rs0vV3I0{IzJD6&2d+)@c}{eKC7bIT^&=$^UJ(80z1^5Zf6J`)k3qtpdxqGoD{)!Z9slCoseQ zCaguzR)5L;n;D-TrH&&d|Bwe`ZrFJn7g}dE6#84AN~OS%597^y*IsVv+9?8%Sz8pd z7BXuX`3!R1^=0GuFpk%qz!g02^svP8+$z9fGM)84xsekn=DGtL2Kgi9Uz6Bw0W8QsVcVG83bl03WoLiVv&0Dj)J`$#Q5J0Kj z5b2c}F>S{eyL%~4)Xw__*+7mjZQZsh2Q)C;-1ZC6!aKU&1PqDl$j=&8SJW z3FA?&5}E)d89!T>-U_QH@$q2=u7g+$dmtm~9xm77JoB!Gst?8N*7t)#{5orSG!Ah7 z5=*bm&%kG0Ea>rIl8IKfz2d4Xg3cc`-H?83k=#F8vdw|D-w zz@UZvl|1SLp<^kur~AG{B-V|p3h!$f$^JWP`1r50FNeE38x7CP4dki&?Ky3ncirm~W)JhK=H!^^s_~ zi#jR(8>cl~9C<{=a`u=aIVSEiU8bxz{?PkXVk4pJI`%(6I`5Mg|27$j<3eA*{l z7DYsoN$5pqzjzhgT{PTq|Gqsjl4lpK?O3q*9P|A0NjfZ0_9>;DY?-$JK5(0yKnLT2 z!DNuD94|}SKv{%=!nj1^Tr4ri$F_TJnfM~|Q)f*LI=I62>;PMSD_LC7A+OBz z2bpuRp_`Bq+6mNeb+yf#Ly#pKS(#wTRubQ~PR{FKV|!WvAuNVI8WnB-{@lwVe@9h= zX+Ep4RfnJYDpA8nO-jic@kSC&M3jK&@}oV=Ysmo*qGz2ym_MCjOCGx(Q~fbE3BMkw2yS>z`&u;wY;UcpWRIY z#&PwkS|VRdnO!T`>F@s9`f;P~R_W4jD$GXlD!VmLt7=Gj*XE`%6R_LPSoy6PY2m?o zK$qHMOht8soy2PWE@(7^2QH5t5xLe(W{ZLXE^Yf&-@_^!HM_{Ai>yl~sgtiO+dSGL zOOn*3!z>${%feCZnFng@S85`k^U5}5Unl7ZHkP`<;jaY+rrOG69DR3W<&KuC^z}A@ zNCy;#JHr+NRkJ+qV^t;fPdGioOYy>U`ilKlm+{?unE{JRYnvr`@M^ThcT9XOlfZCU z*4T$GEj(g&qRb8&=V2_4rgA52*E_f*3*XZ1t1J@1?>U*4p9emdk^Qj6uOyFx@9=8; zQ^5#~knsa#X?|T>!fSHl0l3w@qo4bMb^HfmDKJvUc6@CB6Mu=ck4n8cpZq1ze>jyO_S-&+%s&LQCDwNkQ+(MZ@Q>5&fDQZ|-18Ao!+1czXgR)=;J>|Bgw6o_7W^;> zT}Q%A2~X1Ff0iQDG+39&W5czjM)MPC`vzJTEQI!1WTeWWju*$99aiNB3*Oh#*YXMi zx=GOm_E^L(j;_Z#O!!q0A|BST*95j3wNW=}beDKERsxoMo};rU1QI_hDePkE`o}RR z^IBIOy}+o(N)n7Sz491)IqdGo4r^^lGw4@}>%&B(nd{*72B@t`Q-!KI>+jqgj`Hgh z{FA8z{O#(r`Pf4M5@@R{3%*qI29jrxOdp1m0Sga~6xKEoqneqJFDg%yRj}Fr)Z-Uj>4i_q#lt(v1ayBz@9yZz`TCc@A!)PbU{^(Z zsjZVOKW%@hTD+K4-ahel-lOH94hICHWeVyyLCWQ!zH@z@ z{3Wa;Lgs&kp0K#BxLZgPz(6)Mch#{CNtDu@^6p9kdc&u@Qh%DX+r27ASs0AfxTyA` zU_0bOv=*rH@+&*DWX+f$T%E3a(+X0IWZT+lB*kM;GB47SO>L)&s>5yz-M%8$UxW5V z$pkit6$iL9_XomyT3qHTl#=kQLGUpiY`apw8S=M&dr(bT+49SL;i`MIgw&FdNm z(hu7R6khPGrd`Jv1r?*eS&e8~M85vOzL8jW1~2XkOo7vyNzXMh5<7cR&T(^e2+u^h z!B&So5chy|Z;~^a5S=X!{5q*-=uwI=AU0Qe3|eyva7~dJ{n#Iu!De_90U}j^d)-Sg)v0t-8=&OsiWXCDiSJeDhUoY z#nh4ZUttz@l=Klkwfd?kTrkDWaz;X%28|_ThDnj+EV$;>lQH^M2w+AS`tl+qaPwO5 zc)ZH?)KDHl@miNa`g<}b4lG%;>_R>~mnwdIo@b^qCQGo-tESPI!9~h|$-hjYikI|k zO4u1kld!@#p4mHhVE^u_@&nQvzdp-#DFoVEK${Bz1!-L3)$w;`Hdm5su+U9XS2A$sf)EGJTEv&5DqrZHKs#>UsjpV;(tIOt>AE8*PM0b@bM9a)0Ssmu@e z8tpdpK|U8gwTwWEu>KnfJO&J>$4kL|eQUE2_z~E0Gyj#bd@VemfFl9aGb}C1m(70v zo2;M)`x|N3zi4mXRCI*7>Prw?n>i$2m<*r&wk+pUyN4BWS|C{<7~Zs&i@RTzsF;n! zW_24!O56k8($}YzVd?sW^0BYfC*D4jFRs0>o}#cy`A_v+jX-ESG~3`%c%^>TRifcUT~*Wr0p3zY0%gX zwsQLXf_~OBK-mn$1pNu%G~0=3dpPCR-#^f3ci_td$4`5AMI*$Fs#4UIm1@P!Ai;r+nT@8t=udum1hG2nt%#1foL zA%aMlwCOMTFv+0Cf@XPr!=Juzu0=ykoDOpimCw~hnbd-4lswFw&^IO5!>SAjH=d9_ zt1P;A|IXDY{agk)*rz6nMr8=l?bIKhF& z-0}%#hE0R+swYFGKUR=y%;DkDcA3dPwjM~#Dq*Yf6X1jLg3pk282Q?LtFrFD{pY@1 zP5hfeFg%0*gqg`K04U$nBL_lNH1}8@f@+d8FDh4E@2u!L zQiR<*sOBG?hIkos)*0BQzb-+i7lj}DwEfm|$2yT&{T*}~`b_O`Vo)$$ZesfEvX8%< z>%7emmIb`t?gXTUl^j1`T@iM@K0bj1r4D7(sOA$8u0KX=r_Okv@Mm0Tg3NUVnn%0b znraCW##Us_`B4R=vum%xqW70u-DP7#Fx7kx+Xjc4q?za>ZF&Y-k;35xlJV5dxTs{l zQNvUnrV8bFW+cyCU|>O)LZ9sTvcz^b0mW%9>v}ZUunRo8LG418j3pFoElwW>pH)PU`LM^wR>{o z$s1kewdfXH$k%NDk3q|5fHe*2@#T*M0{mNr#xh90WU!O6jpdAh(d>@he_^O>(sj%D z$x#AEX)s7aQy}1I@*GkpIATa7K~bY^4~^CsYW+RRFfCpL9<8-h;8LizJ55B+baNgu z-7wOtZF2toIfQ6kSE}nE@W<+XUz;wG+CR^!>kJ`AJbO2MIt^`O#qeuHeQ?W_|B1~4 z!z1Y@P_?x~>6JP1a`A0)9C{cdCsRnN@5`qZsU@V7+tUt6eSiIJwE?yZ1zxct<+Ssfh#g$9?KXan~~>%4Epf7n|L!(LawrKT?Qv>~Ey8@o?|t zL-JL=P`9A3tsPsVSnKp3Me56rG_vO_){cgvEPF+hbJ7gyNee$^)WFv#+5s*&WX>-} z=zU{ri2A<1JiOur*gX*b_lFA!JO4nI;+OQNznjH!Oxn{vPgrp=WS4hSO*H1%vwW0C zG|`!+)+gcydzMY#&&B5JBhCl`kVhB7ztT1-SbzvZG%Y+1(!SQi@#6r+9K}oz%bTA? zk;MC2ys|&K-b@^Ah;C?XO4TNfPjy*-_jXZ1U_hy&3Lf^cO>e3lU7CCOA?u{+ z$?H2rbwiN=2^ko7>1ofx{ulK*ni_5(c#%MAjL5mEM;AgT@G(hY!Gvf51+ zin&LP642d65iHpt3t^Gaiv0Q;#sM~mB}iL0FSn;vp&B!{UtHYWPc6EYc+wl0Ml3rGktLPtI8A)|Z-=jt;} zUMw8H+gPew$C^c2cC~Q|YWGgZp1>R0TIObx% zdCLbLXKvoLxGjM8e{TR_5c))SlDXki*!}sxCT4YAAwHaoTvtX-zNeinJ&&)~)2Cx{ zrp|t{7hcp${AFYxBs{<8^j}H(uSpDsmZ0P1xAj@lU4`1TCCs7zHYOQZ=8%N%i1L;; zcfi$k-bZ51uPhO#Sn-_$O0pEDe2iS^$=7d1XAn$jdM&ssVDUj2%@ARmZheQtlWN5GSsTsk{}w^hf8Gb1PqmiDlxmW}cG48yO5mrX z7bM}QJ(N<{5afCCklDfDx6W^eGH^yz)BV9Wo7X0jz+`dw>QN^$d0XFvfp!9?2eF|@;z;<8WF z(YZw+ft#VrZ08yDtvN5w`NJ`p{$Kpgd^t(Qd%8KWN=~Sm05j?1^+5tt45>sUD>!Fg zfTMhvR1h#r_-~dsif_cq-`2q!Q)#~RJ6l$`?H?bEwyR&EthDpfx~8qc%58 z4I+u)ml?)WY*}M&Ye*Wgx>BLV$T-vKYj4An31l|LOppu^hU{>RJxS(p3RKQR!$ zPN#IGCp*^MiCSjuu0Mtj+Vd&c-{DXa+r3L>@=H1Nn-C!@_uWp>(MQ7!%@ABE7P7=v zNzmS$w@r*z67f=wm1+cssrnI_7*HCcO)rp%Rm}Mj&0Yy1l@%R-WP8;K`sb@KvG)mB z*n36H-G#9bvh!)&=3sjBeWH2ih*pVRSo_IOP14>qVTz@p1?+kdzm+gx)3Ml8eA>y$ zuhu_CHgbtI<3aiB{*Oa+UtT>2VWbwNogh3eha#J-d!GOXsHH?$%Op8E~d zgri+s3@2Loc}z6$biu-}f<8+u_9i~pO8$JSFeQc_Ckyjbm)1MRy}i9Ih*7T=o1rMR{9k*cXwUIz=?g$_yjFv?tuI%E*K zx{}W-De~Wz`XIQ+WSR{CXY1Q)Ka>YncA#<~qmN>-i47 zebtux)i6>V6i>&+a7Z_`a54$FXFo;7gqk%j&A5leynq`W%Ln)Oco+UFAqKY_EoLvhlkC(=&N7}GS5 z?^Cr3`B(Z811g19REkiceB>OI!aQW;Vi28U*Kw)#F30sm2jCgjl zD_xcGGsWdcmHNt~UYJ)v_Bf$A;iWvo?X7-DEIs)cY7~^qZ!ih@)?Zj_{%*0 zk84<43MJRIjbxy3ql}nbQkf!p&j~D5=@giCckLR5fM3S%aQa?vJ%o^fZKB%>_}uGn za2Y3_mChN>Sl;FrXAu%MT;q>jR^!sVwlBWEOwkLhN#%s}2r)vdXkP7J_-;%L6z_i$ zR5UAE815n0>V%GiU%#tPSMHdY(WI?3;G=McuC6`j`z887_?TnbUp8mwI}-*u5u(Wi z1e^mRQ{KUHcvsmW25J(P;AoPtV4B4`SJhl3Z)*1_>e_vjnlt(D?mll7o#LLJzJY4} zE9m9F!cN;?LuX}jtbZTwA#AXUZwv(81*8=?2M{&b(BXwVQ)l&*m4l5RNnA@-kFBN;huMm(3@Txf}4;@wE%Q z&A}9<*5#c&R@B7t2ajGewwg^8i_9w888|K}<LG z#XnZS1wOTQ^N$b_bcWsMJ9cmb9c^Pi`jH$9@~r;&dBmnk(Jbl`6Y!M(i{@8SPqMN$ z>%cn39g^|fF~#fa18i7|V1LQkz*myeLyJb~t6gRePJS>IcKvt;a>4jx7C>5Fm#Wrk z7yUu&?t}q)N|L8!A=fxKDX9AUcvuC6<`f~?YSSfPeAC|lZ)SrHpUes$4d%_jKLFO| zp zw4@1;LZt0$;D3;Kx&0+?GMt6=GZ$A%>?g}HmXg*9#?nf6%s8O~Tx#OS_Ks~_LaZK; z8e0pGT8qPnMw#0UgG<|$8>Mvnlj9I7J$#lJ0+3BL>%KbS+5zwM5-6ujf1hYK=IEu< zYzb!uCC#VB?iZ~q#xz^we0KpQN#DroQ&*o>4BA`@7Bwdc-H%vHA?fEgo#BrgpqrnIJ_CrKOzX{no2F|jePAST>Rty$ zyy<0hpEIq7I>r!$d>p%GZv|NKKDQydf#!@1d$a1uF)iB>jd!rZTZ~+0CCnw1Gv_x< zlq=wkJ37Ptydyz(%0NKc}c?0vYHE(^}r5|qElfni`_h%EU(aN{i z%og+Fr35)sz_EU)9r=}ks`PZXILb^ha+Aw^Gl)?r$a_bbtoaPy$mB2qJvB8oF)yno zhQlLyyS1HV`@~Rpq$=#E6;o>1q%6&305ErZYiHu(v@A19)=+iyL#(_ZL+dU0jR#IJ2 zq2`UBKk{AH=hhYds2CkJYi349U6%8|O_&CX&)N8RKO`^n)4rOr@nHG@&W$(1C*UVW zXgkC-RMI{gis~)XAj9rTjLZ~zBW#8zHl*bo%5;oX3^CN*{X;p7w@C4ovahqN?skU$ z9U(jmU=Db+BJK!UlHQHW4ET_->dUmeojcdOx)(*>!_9h%xLa5JXZGb_FYg3>rP5J3 zDdP@-%T+qIKx$>=eb3LCnkfYxJl%t9AGq9tapww4Xgb}V`s!2Ts0xoMB0TM-vDxg( z{X>?#%Qr>P^uZh~4o^sDKdP4bH7+uzh1P5Nej;hGc)F#*?{7#X^R$L7^MF30MvI<8@C zSyDc(<~hsnrPNQK;HSPh;NZQo$lMuT!!7_RB}aQ;TUF$OeHsrnd^DX+KR&LUiJ-H( zCj7X~R7n6B613Gn=z4(Lmwv0>CBoHfH*bq z9yF)if7YQeW;ywIpPdK+v+Hh}rqp1n*by^i^ zeKy?apW2D-jsnhK@)zIVe+M?YNge~D9_Jpiw)U!(EuIQ&VixVeX)&<9)S?^Ty^o(M zg0?j6?^h-Z^!b*@z-`rOh!p;%qC89O5KsiP8%Y2<#@g0hCDU#87Y z!|AQdHzTfSxY zL=S)5kf@_PdK|OAKat@s_z^p))pa^GGjnabQD$YM4qd(foHR|#hnxRZ*Q!?hOaqYZ z+&gLZEa+7B-w1wpzfUk3^r5>$;^t*DR599FB78}nBOWPnyIx=e9-#%!?hNZsWzbJp z?ATp!BW^@80?&TtRT1{SIq>V~nmD-Z5+Vhr#3}M}n*Is>fQzU|#Qwirm{@UKN=qhz zq9n~1uOT(U`_F9{Fe}~Mvc&2#y>IrZ_5Zv%Jz6Ha$^UZkjqQJyyF(7_N^cEY#iMfhhY5IcNLc@GvkAR683ECuTF&B-4f!)_*tV1^>fT( zJ+QI8Gq@AII*vT7C+F_Z4~)idoIV6m*JRgP^eF`Ap=oW)ebBVq2D(G9Hd%#;j@qP4U$xrz1$CbxV5ongy+?Z~&- z8}wyo<$LjedVL^Ww)(VTM#&$+?_G=05$%pVmb(@8YVvQPF>iq~^x~S)5t{qFIxy(^ z(F}JXsi#KOFrqqan5Ju!f^<~49>Yjc`CKb6?%GAGfq#hvGt1OBJc7kyBYOP!0OeY> zI_^h%&#LV%IEgwb)@)&vY{3Q?1GHt0o>L9(B1ddVq9^Dtt9`|cgf)hdhLS2(Reyn| zQT^}f>c8F;^xp2Gw*$0U59+}k4VZWz{DK(vN*fU&_JT1N6{=8&En2BB@0MSlf>4IQrzSRv1*j57JM zxtpl$v^P`BrV`h;+6ScfL5i7ep=4d%3j-&A?c0~=a5)$+<3Wl_6I2Q>otLo|)vBU5 z1gl=e$UTGYI+Xxq73Bhh2R^RrgnE!?+SxDYErbRmEW;NUUnQ=DSv{ z6X9qalnEiXXIo7l!*l=6${J;r4^FkjF)obZanR1&4pj~K6RSt4?zp(PgQoa1C?#3g zqp1DK+@|u(zZ}eed$l;*6J*VrFO9Ie=#G|mM@&1WUq9PRt<9g{U(~M4NgKmWm}))+ zIOpRMvKFelJMZt}*HVsKD(&cWp2nqGvkt7$W!A^}3izBMZyKpNa|~f--3j^7RhH6t zbgPY3SRKq*1|HS~jzURa$Yp_AZ;*l||BW2OmwDZZ ze8HiEgZp}(uOCGhyJ_`;CD{nL4d0GEDNsvVk@|0Xv(@i^e|P)zsAjnLH%fwR15luv zAZB8fDWHDAzP~%KJ|7U4^98>=)a68Bsev0O&=Q@#)aY?sPgz>7i-hnmmmyeS*5hYL zo0=l!kD#$*bcps&XwJJIUPAuWA?AaZ(^+m=?Z6wz8wH+1LuV_M+rQxG;_Z)pTII99(e~<@ zLoIm7xb2%dy4PAk0ZO8wgL&2S)0kOP4nVE#4iu zsm(9#?T)S&9q-#c?Kirlkci^`kIX{G&<(b-oh9UnNFu?$quGqs_hn}iFg@3-4Q(}j*j|SGDH{U zb_a*!t8Td>G4k`{Pq_AO3#^dWX)U5S1h^GtEY8;?<_o7c%+2fdF4QhaYGrcrsX(YK ztrc5Py&GAS@hQqe%leL@3_}L|STnCnlN)~HM|1ujgy6=XpC8~6p3-Wl!)yJXf4=*- zO7tiG`|06jB&uh6fHS=7?TtriQ!I7csE~WcKRI4ZD(k(eF?10-6ui-vKdtkNEjlwx zANa#IA!Lk%`NlN+WobMyQ{RlaaY)OCt`?Y+r3<8K>>C^E$>x{A1YB!*bU$;lYOq=A1mo1nj2+k zl3F29Bl?aWXwd!2UP;6)zTg;p%F_;x=3vxITyDn|&jHEC54C=@8|+!)f`*vMK((TF zC|rguB9>HjZhiJ6_RGYg^Y8KqjnPHe$UCBaVd8=|{Iy4YTuZ=HJn9P)meiO%h@@a> z0{7+VF-FLZ%xCOi;3A)~=td;NS(c!A*0s&;vMACY>)e#I?K}AA14DaNRKpxTwzDtVQMK-qnc;de5JffVMo!xTFHk~?c2OVCH8};FssnmlsapeV<(T1?rx~H+P z`KifVYfy;4GOH&^Dq}6Pg8sg({{_BOyY21{s~}_#6_QGcI@(eXl%mFN_mpmQTO?j_ z$OFEwnYI$)k`)2O)%0(&iy{#;8qydO@^(DrxR29DKJD8JiJ!bOH?cJRkvWuE%<5+| z7#NApGzugGWF?l~t-Wkox_v2%qBQHLbU*XPXMrM4`jpmF`%8(Ujjyjwob?D}bKo5> zgDEU@yvBdrKYuxYh47zQz6~^2ibYZn+5s(khnY}youM)SrtDrMNZ5K-pEGGrf4Y#U zYat+J{z525cu0>o>(&gj&H0LIw0g>jl3nXu=qZahy@gdUU@?(HuJ2;U9a?K%_699+ z6eWH!9KX=Yh3Y2!-#*QiAu2ai8LQ(}?)O)mR}RIdf~{hXYT-)``;44reB1E3nI)l( zph@UX|-Ud>QR_nIm=%iO3ttK zv^^Ltj$o9s1XO8&?t#@~C1^*pHm*}edKlQ)s=2rY*tXOtIlsrZsiA>$KW3#Z2j<4i=OQll?WxuZ^^n?QkQ^It3ebZuL zMR=}_JY@FT83Bqa!WH>>>V3^e>?~lx@zi{@A{O^_ zDy)aW+6Y=7{p4YxQ`H>U0^mhMghLyxak2!vS0uvJi!U$Y#dO{aNb%W}YY7lw)3b-d z*RP01hRloT0z7x=jryzVQ&*$VS#FH*M2*cO=F*QC`0vrFJ*v$YTuG5{ug>yOBnU*) zlmBIReE6ikhO@$G!IS;LHFwV$RzY?ybK{2N5|8@QZpmGb99o~(*69h6%|1~GZ$!E2bWIB0?MReHRv997 zv7sK^&nh|lxp46t!%6fwzG&Bj7O3q{y>Qi0(|P$`|IzNLdeadU&|#4b*0UX++x5U& z=B<2F?#N({&O|-Yp%Gs0t#_^U@Swhok0cX)y`;()myqZu%HWnFcLS;InSGK{QX6q%LqV=5F1Ojn}S=KLsbWv^#0&J%2ugNrz+Ewn|qb%S)HnB z+Z4>^RE4RFI+cz3aKhMrm40_bMwB1{y{@QpSy;_@Ye~?Hd)v`NYj<3gK!WF9p08(M z#p@I3u)1JnkY>2H;vk<*O`vguzpRTydbkge{(C&e0(&G=DC6hEy$yQ@>Tu$Zxz*07 zLAQi&Is@YzI0;Wfs9gn#vH!j^AQ1PiPsqA=_7^~FKa~~!*ss(Q^dm;n`ld{6@`CVr z`m8HjAKuNj7|eQ;@UdU*@2TOE$XVb+M6 zNjy2caxTL{x9L6~M+Majyv8LoM{C6Gl$qX)$RwoY``>^rkZW$_1B%JB~32J!!c8D!L`m z69RV}@%#DC*TSDj@ux2G(?K^nE60M)7O3m(j3A-^Igs#lM9z3n+yQG|INvQ?9Q9>d zJ{5~_`y~!B{Ej%bunoNzS)-e$f%#+nN^eZ&2llm=CKNO_wSKJAL_bz8d&OB+=eq2bSGl?=|dTPxr7csrv4CBidQ@QnSPt3EX_46C*( z{RUB?mIPrm`dP3_RGPE8ShGZ}=FV7&W6WIhLtE#k>>fri^v~gqxZU8)YHNuyyGP3k zE%)1WmPguM%H1iY&(sw1yQSarhHl?Kp@8wFrP!0f20?u62E)Y71n!}B2D%F1ATHjoUO(p@ECDIQSh|NmNlp}obC`-;_Qk$dDEE+i=`6Gr z_kU3tdNx`+~s=JFTZs~Yh)Xd z&FVRPLU6WD@%6J}pQA)0_)1rJaloYPjh_D?6D@B#6KR?{6h~z(aKG~;pDaCJ zQNr-YN{*|(xgo0nP}4TX@NL3dN+JO|eI=k`W3J8Wv$GiiROtVWdme@k?)Wo$cyad@ zi1Tb~e(dU2%deS=VCA7LR&zdA4H^9?`^G@bJtseR}w%PJ~%F6*&k zn}6RZk6W&rIe=lLAiNP}KOP*fcdS}U6iAmRhI{xhpjjigr`@aUeWf3m{A&|Ci9yGB zAEyUorv{0i;Ld}VZRrXGQB&5exv#BQHNS7x-CYFuVK8M=KoDkH|Hg}Rl9=;CUweCdjn$Ua zI$T9b7$m)u%M_<>&|O~4(479Ms)j7XL<*`MC1a=6l{X}8E)EIs(;B?~IVB`xw9rC$ z&K}dIw&1FFM&V%;AFFfRdZhQP)iXWY$){L`9Emf#kJ1=V>V!b8Ri9RHSI&^hLr@;Y zeZ?t88R?1E(vUG*2t}8Ye4E-%<;z;*@kU8*NIG5r99(q4%L~;I^k;|Vr(4cQ_~|?C zl9=~V@%WDUCKnAm(DlkhqP^#_0{;nmQl3i?r1AH-7!osut9;VCzNR4TR@Ez88gOMa zhYiSLq1HQygQYCC)lcfv4S-M0h-kcD@qoPiI>V@U?%j0Y0xV1-~hz?QzL{Y?K;pNQ1O3X0mV}>v6-x0@HzdIlipLSv) zBJW1Y;r7J_iYo|E;#7lUcBv^0F&_|3h+6sPwI)fGr0$)r1J;*pcjJE<^@!TlFTDOw zDRYjghb&K$0JvcfC`J>B)Yvd!wBw7WqLGl)7!lJRl6+cYs#aB-0sfAHczfV2X(D2v zEG~^fVITF|-Q~sLV+Rb@I}lOk_;l_)*z6?A=0{ykxIlw>lYV&k_immpR)1q^v$Gv0 z>eB*RgxTj4WMW7UJS?%dY~3t`nAM%KHUvZNKp6%mmYRo0^Nmw5c55Bc*SkG2qpGZz z64h5DsH1%IU+>#~;D{V@)7OGwZ??ikRlge(dv#_iy2h-mFH(>9?(i;@iD|+OW+agm zjZUhZqlk>IspCU_R_LQq)mb%~qD7`SSZF@$B?oo+rucBO2Rn?)wRK%k4=PHCii3a& z=4thYxDn*H0B747bL6liazavS>DGMj??78d2}~bolM8E(W#2Y6Y;uq@kz5mp7Dw@o z-|0Du%$+AziOR|k9y`uYI=wQRrY=JqbyvuQ(uLGe9k0DKU~3d;n<~*+dM}Yp;~Z2g zWLFI3O|seCMIIiud)caN?hmyL1V8auw{YMw2S~p?QSKDYugI-`(pvS;gzG>9@YZ-x z7mDbGiee-z?-C`0Mkk3Mi)b@no1_DS`T=|Y3hhi$upT@SN_vAt;&ft^k(tR`9%k`H7wL8reC<-s-GUC?{JXfUTD_4H>HZC} zzVEUwQG7>7NBO0tA%5*+>B8Bw#drD5u+Ip8; z;OH$cL;7Aw8W(srYW0!nZNrePDQCf@HT?D5ejkp{|KTZw5n5{>{B243H772#`S9Id z72Ucd(C2)H_zb_fJOl6C2 zo!mA9DAA@U*dB69Pjp=_&V`jRcn5YbYHo@ILLC(d+`h+J=W!h9a?(UgD5xl{vi9l{-X8k4v4< z`MSvdMS0Il2SSKL1sIar$ey1!C4D$26bCCPgYdC0kgRjo4IfrwRs zDlM~lt0J+vFg6p`BhcB-k0NBN z_=TYisuHmB=*xgBDO_xwG1yOR;X*nIDBQ^?jHrPhtG)8K!e|KbS_DK=dt7vKWp>5I zUbqzVqnzg2y8dVQRNs}AiQje0^0V0qsUb~CrxYk2s_x^dTf?mpPrO^;Y!z@H?(9Xg zol!XfeWW9v!z)Ux_4?K~EBOdP_|ez)Z{q`@%^9X$Dph9NRi~cg)nlXBhL$A4eq+K* zQLr5@JNkTB03g^YT7;*70Vr3B2HDE)U+@*t^X_)$yVo}fR562_etsV8{kU#NjdB@9p=Hf! zC5(Dk@tqV=d$}*w8yi`_D%w;tMVrzJi2xX}gFLLIdlYKlrGDAzDXKp(H_=1Lek{}& zYLeBz|G8rf<8|zeH#?tNquq)6h}M<85GblNCgmMbhW4VUDe>~jI|zasYE;U53PDc~ z*Y8I5(nZb{#91av%4|2cHDI@F4Uw6gF9K!nKQY9;M`DZ|*<2;JHAPrN>UEBM-O~!% zSc5G;ceQu%=KxB1{PU7CqJLE}>LqxZsd}7{{>b$o*wxu^^{DJV_q+QN@H{5`crldL zzL+@jDx=Q>JmYHp4iYqmD+LCOrWt?_dSf>4Zv~zbN|kc2-%5uLt6t)dwohn<{ez}H zuBd^)jS1=ucd*xEu!H|2z#wORd-5vA6a=&N%yyRgY|IV(lPU$id|YFG+%doC5PsPe ze!Q9Mz7~s%v@gzD9wrd7{x=@<@t)&w?&@-ee%IJ4{E<=n@r?NKJSTWw-jc|EXrpQH zCoauu$}kr?cQwdGUwF*xpXcQxRW* zI?knvFAVh4gJ68(>*fI4?}G3;5|TSA7FW8tU?&E;z~N<0vYUU0*8WZmkGEG37y1nG z&p=&{ZSnw@$BaYHHqwozql;VQy)DDKc1f)h5Xj&^WyZ@qh3Yq{2YTZkog zz)TDsh92!!rSWJ6ievQ^4REge-6I+ZLj8G8j-3vU?{s|MZ^5r;FAh%-ZSt_l12mFm zUx`=vcDT+6#4PLz+je8`IWKvyyiq8i);AY}2bG^OfKEkF| zXnz}=do^`IbQ30*aymI?y8if?uRFjx`G2ZQ@Rey#NNj$K2>80nL}o)@?4+8np^Ku; zI+kwrD;0{eBOq7FtidxfjR`z^a_c3m46^=`F_0uYyZ|5 zwh<+kUZdP^z*s8Hk{?0Y^yZkB5kd}+u8~zd+({O0_Z$h=YOPQpZD7IiX8&g(?FU!i z#Ap8^;;w;&LE}-OOA#^@0h#|0Cuf&jNi#~#aSp+{a<%mJ9SfE)O@eVx5#MgDx z^pTjoRw)So87@^eRSu~pwdoaC_B_^8OE$DRpve)gwd7TFsSd14|IgK9`aAn^@Tw36 z#)1mafj_cbQJQmzVBNgROyX|n)zz9ep)lJZVXNCX)1XiNUSC9hq^e|p9rsvPy}`7C zZv|jKYgiQxrRM2lAW~@Z@v)I{rTzrScX^xak6vEMjR?P`Po{;#VpeZJL%Yt^w_P)y z4b}jxHU8~8NgqjRuVbf0HD&9aNsgZW0-P9gI4l}|)mfm7uy>B2j<9LFe!GyIb-5+q z=-meK;pHhRUtDtEmn>kB@x!s^Ch^&|`+#;icdSstu!+i&@UdkE6Dpdxl^>_+8F+B zmN+R`2-Uck6q&$kdJOkqEEzK;IlF6kA*K+wuw7z!hC8{8le0j05o=f`x`%ie_r@4#0j2Z^kG8Y%D!CLMrEQIykgBJpuidvrRs&}BNfPB(_iu4qpB3ww0$a6P$aB3i&gquMi zYo6M|Gf`f2oSwMrlN!!XTlKQ|lKrk14x8lqT4UIf77B(vdeqxZ1U`k#vkE$=K#3;7 zYfL^v2%Oz7hm#)Ouan9{7m6CSzi#+R1IEKOjmdrQUX@WKbiZi>)AWWEuf5(xeQm3~ zy~aCCPoO(v3-Xm_cafzXmm{U^TXJ+#I-WS3hS}rgH9dI}_g97;&9M-8Zc9l$D`yCY zw+LS2NK~(48~vZjEim?(+u^%ln&)g*qSFyEk;WW}ee@d8PN{GW^>rS@~ zP=YKSrPd`_BLl@z#dUjeOmqt(BpY!|kXW4v&`i+Srvxk$M{K7uKeoMv4{niT{y6ml zZoUw=%(*FUxGm^;_$e*ug;?EQU)M#Je-?YUx<}$|C%GY%zHi{WC$8DvTSsXs7%qpJ z*P`0Q5*jO+{|B|CzK@x|1wN?95yS46Bf+HeGF^GFSP$GV}h)bf`iR-4ZGN`uVX+WW{xS*IdeES0%(nD zY-MUJcBJ`o$JQBWGNS1XkfZjfw^PQdC*@jk@aZ0ow!?0Fn96;8v&X&p8Vs03Y6-;U zdga7&5FGD#(O@;wW#Z+18rRnlyYnGlqtO1I@3E@87~mSQT0G}TDIAuSbtRuwAH2iv zVfEewm9Wa89RB$G5DU;Ax!-u<`DYU`tgSeS=T0a%dVb~tz%$ujTHgMhYF4_GfoIhr zuYO4VhSPLNQ2OHnii1iU9sx}5S*`K-KH0S}5t+;XenR0F%3ZV2UK@Gtc)Q0v0qgu= zIdjNGrMlkUtFqbqJ%>5A7&d7-XW!vBc=eWha>g!XBn~P~WOozd&1AkhIFaK0cgAUM zTAaYkf+6fNcV$cF(x)>Zgz-B76jFkiTD+KQxIBR9rb!p2B)m0N%j66+=VW(*A+~)T zC0GtSBspO%4pcH|vp4$t05_bh1v`^NwCBbvC;ze;4_x`3cwvBQ#w z#-|!)b&fFlwVD`gL5SrqgG1!;*<)$@{HP~QjuV4AU4VZHYl~bD5p$-_*w0!Uvzbxu zrQncEfUuQSg5o17J8!MYG9v}KG_Xw-NDTjDm;}i?2bsrz-IAE zL}ACp#p}K#83OZCv2h5bw9i?LKBJOI^uLg}9qLtd_{Tu03=Ti+p@$IcxIj|weATHd zL@62rjzo$~OjOC2$6aE+zpz8X#qJL(i{sqS*Q{QvNKUB#Bh$&i_pqhtVk#DXv8 zZ=MUZ9yo7t$Ry*-AV=0rgb-3k+#f7C`o)hEUzjb)+FC7IvWV&>eePx6sJi;0-jn^?*d z@iuzY7eZ*@#;{rF6+_dGg5~ViHLo>@IP4QLh4cx&lwdQNjYTMV`3%s6-q}$HWCU>? zmci+3{v;x#i78l8YAO1zzHG6=;snWy<_ zbNA&+S?se|-^WJ)^1W3l^SW)IdIePg%P$l$GoJhZNmz!|k+q1oJCw+IH`0&rc0@?d)t1Vp#A=Vswb%`!QeuUh(Otq2gW*yoI zyEn<<_jgj-Iof6CSad{_Lksq!R-vG`yN%-ur$!nEVLPLxamSk&7v1t~MU_9J5QQqk zB}ZquIMslXoPRqB#@AwFYbI(GpJeE*+O9CU<^6h9^j+AAFMO)i_`hEEr7zj~db3Yx zobc*r*chCPtsX|K&T=RGRc&>tX$R;aACuqS&_-~XENoF$t@{A08EbLd5wR7`8t04I zfj?>Z$9T*$&cUvCWIm-Z2{`ktstN7%AG>}cKL^Pm>i(7vH#a`z%<@fFpUidK2C=_6 zMBf&4m%UCO&t)<@Se#_#r@~B&_Wk44!EZbL6IClDG}ONIFN_&Q5dzOF(0>)BfQ7$d z{ZH|%YM2YjN(xI=C1Alhd)Y%NH8L<VD6+Xcb|5%|L;w$b#W|SR%9fN6QU+%8^ zNJ`+`8Uet*sXC1Et1Th8+5RMNeYWN8%2TGYJt^q^IJN~Fd0}{2e*cR8{#|10XxA@Q zv+rNQ?+^n^Di=I^$1C}A9tU=6u*Yy&`J`x{4Qcn>CMDs^XHp=#@mTCmN7%;2)%(=E z#T4hwm4;-l_uF2-@e|4J`tCTdJ;%5eW+iUBBWQYL_DKGGDFeUxkQrf$!=-*?Z_1&` z;C#2*d=}3O3hs`O2#`kep6e9sqKJZB;XFS1jhb zfV~_+X5U8d2R{ur({B*bS76S!yH^C#!55EL4;nmgli(Kkjd#T^x`XY3eWQYOL*90QK;WZi%g3O6 zU3Prgq+Fqd^w+~#NEshC#^yWBVbkGj%FdD6A~)LETK~itF|k1m>z6w*PnWA-`Ll=9 z-W}Ui7i}?Bb{p?qxvQM^`ekpfSnd-@__ut4Uw*fZWotX_1*#NM{=%026IUwOtynX> z;WvHklgE7rE9dp~OYf)6>Q&{~%+l5vC2qrMxPk?mvoXK$v)r=mtPLlPr+oJGAp#p> z>|@GXmz0hP&He3|xPbUCI(Y5qpM~f>vaeu8R}gm7tr{$T_@TVh@t$ADuAsKCy_LRv zZtufy4yfyz2zrJ8jaZpMuu=vMT&8El0Q_A0Z}(!m`$jQ@d$KcN82+tJsXAmmk1NWE@D>+O=ZQihX7exO9 z9h+BWUZd-CZCpi+t4dsxqUtmJUYhP;pMM%aqwe&t=$XCbubJ1c>fV0oCR$`a%5!2?lV^2>NrDV)M2>R~L0e^jVAuX!)6NKofaK8Gx?n?2$m4 zU9<3Lcdcx9_nGwT_r9%K*E})Tf&a#o(v0+n@}x$?8vBtYn%EhPC>r#>2JOrLZDpJH zWT=X>X_v-ODGV3Gw}bxtKUUAp)E|mSY2$c`uQEu||Bv;m!A1fVnR@(4*^-Mqzo|Wx zwWDdy|G&Ir53$)6Ae=1!2!vS$S*>3w3Vq}g3VVxFmw)b@=cV}i|6W9cJ?y9w&wB}- zZ5iOqNL+N(@QZ$;U(dNPb^n*o`QKmDlVtc4O`_P6z!G=ALUrkUIZ5!)->fLdB18Kdyj4PB#7SsSqNRdYJ6A$anCal9dca z3GV(#H#^wmhnqNsS)!TCMPO$>QtYf?r>+7_g3O9Mk#NS0lmEt!C%459=7ju&_9OD_!%!Ixn%HxlqU3_z#Zk(&7+GIc(zytXa$t zpyqN7j+%*l(uyz&ei9hHY0sYzMom)fc^pv(tNbEqvciin`un)NzQ)cF0UC!N^ij%| z?_K@`3VqJ6Yli^VRB*$Uz(`bz8OHT9!CCU5c&0RZc6NKq*cf|MZtGKTFOhFfD(BM9 z#sq|F);`2i!u1emSd(sB0=@$-!BhIYxA*URhnQXFmKb{D4Ht!L@Nb zHx5*IWO|Hay%In1lYbZE!CQ}t4>mGYWZ4Wj-t#>jx)A<#Ahok^wK0VQE{<+o-N3E!>H{;Mkk1=aGZ)`cE26=RaLA3njJ>o7_>w}UiKi8HqgvLyAFPf<^!Sb>O zTP4R`NL#4I^8nL#CFN|7P6O%Kf|70Ly4LW!*Sy@?{NxHCv0>8D+p&k?%o&S`)D|a zGj+Q0e&A;+hdXI!$eDrl)2<@H& zL}%Ts=c`XizR_&+MrqZ3e0|8sd}?V2Kvd06)3bwX!;nhVmp+s&Zo`C`AH-950IWKb zHz&2-E;a`^B^1wO=u_wql9=&BeHp4*n8!1(P^7)ElgY-97m6{zPR^qeQWp=Lw1KcnXO`BJ5rkzuCwY4<*v2MbnsDVc!cZRl-A8|2;>u zs$2IG=j&yR$Zv6nj_Z6rx~GUK^K(`f&)#?7yPTIOVB&T98ebUfpQM^86?L{p<|4A4 zJ=s=Zz4?@T@i@ob=LWv&U$SWX{lGSY2P@moB68+U?CqQDG&mqgU4G8Q`^D+Etgfr#sROnnZz@{*Gpsao*nVi{X~$N&usUShwHkOT47|JDfPdU zup0Hlo9G4GT&(Zz4m!6eP0#kP9sPi9_z|GE<~b@Sj4db_x|URZQhA^&X* zKI&wS&nMKfH7a{5HDE-7U1KdGcN+cb?)RqT|9wj&McdtokFR>FqPBqpx>$C*1$U=p z4aN|<3qQhcL_J|OaBH!v8#)Z(8;EtMFwtKd8c_Fto_u(C918+JzF3@S2{bT&3jD*U zQ7}!xZga4f_0LP=_HV%ZKfu((q@nviqLhi{^>QD6(>(l^up|N(UyrJz7p|-90c_WN zp-HCA$I!jY)tNZnhXoI^?$*qVHhtcNtapF+ojP8ij`JlVEAU0ql3vx98kD-h1oR0f z)cyVGHf!$ZMms)7fJYqh`6h?+$z0PybyP59&PFHg=lW}KWB!PWICnb;oX-y*a+ioPRp z6BFTn1@-A>Uaame!Cbj+^OKWAZ4U(Ux<-O&wHq7*6yTfvQsQe!A5Eg@hBB15kU;9^ z537S;6M^LS(Espy0#Q#O?Umx|%%zBIGD*KjqI%n4m7W6Vsi+$iL zYHm74JcoX-QuKnM%7UiV%3ogP%0K)gUYlQ5F(q!%JsS4sach7bu`<@2g7en%VvrAi} z5vGOL%f?qlEXroHg_ZAGQ@m9?ZBZ@;`nzXexSu+Ue8S1ts4Wsmi)CZ@>VKM+RYR}# z8TxTMoG6(m#;8@B+6^CO##i2{;FyU}aA#?%+%M9}Ewc8AXu9S-wMNlLf3rLHOWbSN z7Wk@sn`GN&bXRInCn$QB{ywB1K}yqu-OQJffasy@vQOtR+893T)7<=`y00$w7{5~0 z<{3wC#w$<2z_Jpg|3`ktEm>_|n+)@0;s?Y@VT=C|e7pvD-VnXbE zfA}nQ3A-3Eosyjd$R;vo&}gcpCaQ6^)tLR}up^MHU)GOy#QH*$n+sm<5>M!1Xc(L* zwcnKvY!dxYDMZGXxjw}c`e+UjW0p!lrK>9e$z}Fsh3a(bHOFI`_~fg@<*8F&&%V=V zK~>MbAfl~0Z|{UKbjHUxoMFA}@;AqkMbbE`-kWHjVVOhB*ubPVJgTjVZ$&F%R{!W1r4GcP29OX&R$e(2hyOByX8PlBJrTah>R8{O2Ei(G&` zo(@p6HAJ!Fz^{m6vEm7KY2A>USq_zg=8|Wh{Ckxx$m#sRNJbq(KB2+os3P4YaA>8^ zvF|NLG+l@`7x0qN?&3*`o(O9|DAgCHl5`4m|1m->|MvA-OC5nAWSs;?I^*6}_n9H#5;9|+RX zWamU}=0mcJOQU(&lRKs}*cs5w^cJ9h5&Zk|kEWAl$m0d8Bx8pk4w#4duqaNEVBi;* z8J5<_!>mYfBU*^1^5n+;vSiN6I%+KkO*Q34?Kt40;1;$44^dmIoI1CPu8zxSr4j+^ ztc_&Piq2m{F(!MFt3&jWFfnGY$BeqKS4}uN{tYX1k>Bo6gHe@?e4{6gFKyu3KCEO~ z(IvbO7>umW)XoE*^ty#+3|Ba1(1090f(=|v=S1e(0gHC^pwb~apb{sSd(l32n)c8j3B@d zsmnWKus+`PS*c>@y32<^FGF0>p>iTyS5P?}C({231+1^XHKA`p}?zm&D-T88FoB_Gm5g%XAMT!=vDzB z;bcNCg@v(C z_ujl;lQFbHiBdE$ow^U{o^e4OBr!Q^}IqBDMTdY+rnkowolVAI?_XtLADkHbR(7wjU)RbH;rwWrqJ{De%nk^Ks z5mcu4_x1KwpcsV&Ci=Tnt~A%iB335qG#A3vL~ceiboIoZA(oddi^@zW)VN_QgIWlm z_acy*p?X9k;fZ;No58_{)0#rNQ`2dc%f637JWkc}s2&(7ddWWzf0=9wgkKE9kxIvkmbr>E&`cmx(;K~orszub87-I@x{ zbtYC_c`t~~MfgaZ|M5;lusFx&fXkIx8Kf7*#giN?^gcX6|7V@!7KbAQGtK|NRfcNU zBxTt2-SSp-#dB8*ZK6te(L zGQ&=(m8=xvCezlJSWl>rONm|Y82k@iy^~JwgYLf%;eUK5<&(dBDRFmNN@Ou3%vAF4 z9Vie2edX7lnT_D$NL$+W$bU5qt@e*%lh2Ou@gsKV_Ut0tqi`9Tg|o3{n@UY4zwvXn9fCb3t+l zim*NHn(#;XKU}BVB?RCqy276H;5>M{ZxS$$Q_<*G=BZzLydOUAHNKB!{>E0KXlcZ=v;hE%m+>jHNXw*LO$ zdeOgq%(3HV#8>w846{LOWvw4fd zmxSx4(SGO62T7v;Q zYPCl~oZ8rtesfNZnca2R46Tm%Svu$Dm)Vdh?7zzLRT6IN+&t1n&+pqIcg8>|v7_@F zk2#WK9xhI(ak`e&4V(=>b7a|f)}l$;;`{7ITYzAoY0#(cO9HAhfw6=y#Z_Lc37$s$ zf0$DG=5iY?24E13gC#MD#^dq_sA-wOz{s{ zbZ~}NUEzv~M5j4+e#|#II!eQ|DQ#s%iOob%(q{OpRde%Q6RrW7U+QF%?Co9i^rAov z!kt!uACt^DW!9FqP@~_!RM%+$F@sU?nDc~)gd4%6vJQ}!Ny ze5_D~d)~tyu-^YQZt2;I6x4?n58l_{O@y#1aM`0l6 zjA2rV!oiyq(c0emt{qK+U`6*)hXx?ge9Cjhb*JhJ{~Nx=@?tgi<9ufcuDi28OQ1bd z!A0ee{vO?^=LfZg9l07DT{+%G%&Y=R!TjwAy}8x~ti7FLfkQlt%=sgc(m9?mnaV*U zWbP%4E|QX6)Nq!t*@%UAp_NysIemZ}=}e%|klR2d>X>%TuF7O7XO1q?*XxSpyBhw0 z5U{|K^oHH1rJJ#+Ba#exP5CbqRaiT=f2oreLVJN>iD>m$-sP=cY_g)6exjf5FFn0U zpw@j7>O&6>S%chiYXDq`N#VeI+hc+_s#Fzx)xCM&y$e~T8Sf7r$*KZ_bLUjf%`JH& z99F*V#@JC`fdCg}{7X3|^OG7o1|Qat&ezZ8iyQkvr6iH3ZSUAXpW4U`GaCt}wDHW* zXbOcT7dqaKD0<&T&U14mtxve-P6lAO35GM9HMMSq>Co#mgR@@rhWuB?v} zT|LG90}NAV7HA8^aWT23FMu(wIBHS;$lZu?!jP+?W*XD`kVY+<+g76naB{!y?=h2) zMBfDRD5s-Wf;^t9Xelo3@Jk4=@(yIR2LzhY8r`zn)w-+0?(i4qw4N*~^D@IbkOFTq zZDKC;vo@)K=rC*NXkfSY7~(>jozt2@?)qQRj7v=8l+2ux(Tqw$4h7+SVSx(!1i;^e zNHIt;R+Z5{;#BofO3okhq^e1xL^4w&~V-Fjv`feU-OAf*16x&LxoHgsrd5J zYqXWoT-{)sk5u!XwAqrlBbMO6)F|Nhd7$TxlKi_iS5}8Pc_aABG-hgSJR;Q~=2M=767|1WfP!$Jyf)qL=R!&3TmgA4Cr)f8U6k$` zeWAYm>YL&34+9HNS_h^q=N=ki-$_ev?M4xxPUnS#wMs7q;h6zAf`xF2Sy?j9*ShLz z#OA6_pLQh-48O~Z`v^h9Jak=8<^yW+TBR*Aa%!8Hq$;C0X|_4oWxLUoTp*v>`dTA& zxHA<0@x1nXDw3RcJn0g3s+DG^U=bB3LE71wZDfR5rOk+2hko%_I!&Vz*TO#V=&yq~ z6?sLbSGO^8qe|eZufjzZnZAB=j9zW5xu!P4$Otb6!zL&+62V<@-Xm&Hzt8!=sB+V2 zs^VxohlB+%GQ7^q0RBMcj~Wag5g@#?v%sbVZnuxGd515xVzG7v(7W?D6-V}j%Og}U zJDxVxI~cS*qFxyM8$56e87Cx?%$pSfOeN41Tt<;Pog!2SzX!TKaXJ0viwE_2bJcjq z?6WsWD=L!n^2YTw@Qp5FHjoT7X^Yk6XMXLEm%*?V6y1nQ0G(h$XBmai4WtSt@`H=d z%2IT`CP-DEulMQ~Krkj)UY}2;(?c^sXjS!krKt?7WGP$gUPNWrd(Mo)>n@YO9%Zh3 zDJG2$|80cx%ps2YJpq?p%X8~j*DxDtl*F4;^=As?9{Pk=oJ#@!%@-Z+PN{4#fHTQH6B4qODi4pY|J zWa^Pju-kHLj$w!E-6oUum?znPCz$DLGjx%fej;z>Opk#~f>9a65hq&jgRIK&i!TVD z>yQ9^P!loyw(GncOkOJr{AUz)nw+9CBAUil6?L87h*>A`G1E9^BlEPJ7x?DlzCU#J zAT+QUOlZ{AMm+Fu`ff)hoP`G?@J5abXo#+%b6-yaf&CgLftraUW-JeLUg$CNxQKkL zVLm4ne({W95_{oZRcVC|HhZ`|BD&frY+Bfbis9>Wi#SDVx`;dyPz;7bg>~@ztG+b(YK;~|3mx*?T!f9I3O#M5o5kk2vUc4% zD{BoVT|WVKJPV>OBn!gnKI=Vyom>}`aI+&+GrLO_aypY0>`2>By2f!2^n8?@Wp-ih zVA3_~kGe8Od*s@^E`-u}TdV;LQE5L6AdLZUQ2`&0F&ATv;Vm1~O!C%jElzuyxSV4R z;g|C}>kf>~8k>egk@Xbe|7jz088zJm@>Sq1vdodNGuAc%W$FkaAmNVhlA6@ zG*Sb^q1f?4B%{{euuA^^a3qTlL&DzaL7TAD)>$7k=^wOoGBwjlk8d#0IElk3b&jpn zT~Dd&>j0k=78#O6?0P^GzBsly`bzR zD=Vw~;(Zu3M5&~TYtY=pQ(RY!b8Mc2HvIRG_n3cXVmMTgXqFcp(ui_u5wTMC{8v8k z+oOiIw!NeEi?8{u@^-OfuMt{Z>G6*&$JCDeX_%Rd6m){;pN7{u!1tn@yAcr(toN2Z zGM#PCn9O;gM;y&H9T0N*&c-Dl?JXdrh#Sjg_GQT7<4387;=uq9T%~6Yy0Z8=MCP=J zvr5o41#Y46>}H5(#Oda?V5!KiO4vUtHI>-P>M6YfJ1pMn*Orz3F`Y{Y|*w(Mam98(KIVSr#C%b9O8RXA+yFMW6gX}sK#jFUy4nw1!#;U91A zzbPR*8ILg((p*1@+ye!&KAmljK>!^CoP+Kh|E>PsBc{+^6K-k)*I+t@Z*=betLrSI z+W6MKU8EEWlp;m`cyPDkB@}mPfEJ1tf);m&Lb0I5y(vy{m*NntxRwwg#WlF=n{(dh z`SPrDve!!H!>pB=tl2Z!dtcZ6^L9bt#TfzB6;cV*DlsHM7Iec=rQ$Ao&yo9dN;A=D z7F2BTTFPxOdFa<46+Ppht@(B+`2>JThCXM%mo#b|{ny{Ltu@c?I7fjDJ|2>8TW$~( z>GlV?dNZc7U3^e@-21hy!Q;6tIS59Hq^%#ywTL?ea*gie9Oq#1(!y)ck#y1QtK9vm zxlD7;yE%pC_8j)b-VX{1wCjEwr#H8MS^_JRbL_~?)BPe-pPk#&%t8Yz9N^1`qXAH5tfRjVDY zvyvWjA1PhbkeNyE^geTb#3iEe?{p$NU-`adpvkh84cNI!&^ zu)bS-r?qjAmT@5~CWSBk_x|Qpc?ON05hrtpO1k3lq-aS+Kt@8P;9gB)(MAgTR7GRg z;j{i1cK5TG12uOo zLX#aej>QjsdQLnHAM}OKOBzw{$i!uh;p(i|22E7#;k>JbQvv>7<}UjDY{cUIy~>3iPp(b+=x4$@DSC8zYS*k# z)FKa|uD#({=FSid1|udF%Kn%|^vl%0>f?9ARXI=2uedb)ct%AIe_ztsGLM!OY1YC-KXyPe zz@=9k=r5n;H;nGs%vQS}8tKKm;hB9g0wo~BRm`WVkMbv6nswHDfK&}SS#|Xwb8|(0 zrvZW8GSM23(&`+I`AoqtE_=fq6~@D*WYTTM+1&TX@#tH;cGH({Kp2eqC8dm&TM?Ti&z1Oo zSBO+$T@~{to~ddT2l`&qdiAZbAuqjwl4x6Au~5@Kw&|knYTX{x1-0;TmpZH|WZ>$0 zfs~ow=;2N`a4MIQK8H0kh$t1&82+`25S7fx#;0mS|DCtnqRvnoW_ z6jp28UsEW|@%O_c22B#=!=FKvI-<=(ZqcGi^c&KgLUGPr(F z6j5BIg*No<>(sQ|3b7yy^p%T4pWat)oHAq5+y(jNi>6)7f6NVAnI^xac_!fNhE=79 zDy($Ie9C5MW0W>LBD2}vS~-{u{;1m&-yV^gaL9&!NV`{S!@y6lPXD-`@NLcC@A{L& zzqj+=WoOBo%l{a?H+(-AoI5h6e8UU>9f#3Ep5e>d3Y6|{Oj#Ses96|b^TXn5dVhRf zS+gqe%RHo9$*fEY1cOs#{LxkA`%s%J7H@&5UE9*Gc5F(|76xrRY#Vyn5BtwR+l44W z`lB1SNM}@q#6O`dQ?s+?)qc6xUV&G4#>>*x$xp%HzWm316mz+&z)Kx{4FzLyCB1@| zHmyh_@1g<5sOG)nnDo92E~mOO8=4khGosw1qUq>wD_kENiZiFri!5t1jZ7*f`XZ1) zLu`bzG$jIaTl4Vvt0S$;Yv}m$s(hb4Yq8=yGjD^d*}!=ILVX!@&)!u*two~8Rqxo~ zT&80_ORcT*gg8u?URKD|?D%1Nv4T#9lM`` z-?A42jW=bw^d$NWyGdb5mYP%Y`v^M)Uh-xMF-4ver@Qybk!sAuV9`j`CGmvqoHhC= z229BpRaC9bAZC-*HCRE1(+}boBG5f<>Yfj5D}x99OMC2G)#Dyasgt7$#9@kB`_Ymd z(%$J(S_fn?Rv1gu>6Xlb7aaOroG;XYT88fj*WH)lb1r?sqQg^C zq^)b;zaIM)2oR;#2+Bqy)SN<8-Io$Hw8KGB42s zfAgKe%091ynzLbp?xEYmYC)!KiZ`(ysb!dW>4C{Q4R-Uw)=yL!J9Ng;lLcSxQMOTs zj&xb0Lh*<8&@wJ*=@%fFU5P;B-MJr7DqxVrkWTD`Ro4D`DK^^N{(7MRTfng%y|O7h zS-PcMWY1pwaPndk`}dI$?bEVI8kwF%ujU|Ex@#=LoOl*G5v53u>JefzL7)qS#~Aud z2!5x5JJD#p$nj3Qe7w_gdE?`SEHlsMr7^oxziEjM{<8gaCeX0AHY67|f0Ei3wVJb$ zjQ|GYW)OHG9z9mAMN`59lhimWq~u5U6h>5c!aAet*a^hXG~!vK*g-f10NWLe(iaqU zwsOR$n`tf=ix_iSl=A-H?y0+~f2Jhw1IH_-8(uFvSPj(6PkC6eabU9qP&KurMuFek z(^mHC81?L`eA@N5(*0gL#F1C5)lZ-*4IGMF^d=c~n#hrYwI`^!n8{O)m`Atx@3i)Y zA7ZONEF>e_-P5MtIdEyFz!voIN@HsTAN#$1DYI7r$WOtS{T?t=TP5ViT9I^hp=C1 zY}{NfyP!ZUU1kTtZkf!QrKYA$Cc0EpUY;XSv519q9yXGV(KtgWl+mu*#^Up~I2^O0cg4~Sq1V4C44Gf_xR7(AKs2Sro zy+fF^pkNU;m%;agm_>E_6EdGK+InneS!MYj@T~ zX2ikdF5h92rn;Ps`81CGqZ$=Ezn`HGtCjK-16`7EX!4faB~rD161IGClMeS-*r`aEbo|u6_*SvoFJUzF=ae?=_ z3WJ9$abd;oy{=z?vNN3o=Qe<57_i{a&K)g7F|3zoh>l8hIwOM z`x~iTx}xnXWepMS?Q`sH_dJKb9|$4!kIk1Lf4oLJ{u+x9bL4A ztTD~mLowr2Z|zHlwMgMyJm&*I@3Bq4q3zW^`g+T5PYSl&;b9- z5{G3D5bPCE6`j20MpD+=U&}_lWJ*KF^2$v@YU!)RC_wFU0fnR4K&uldt(XmF=#7z| zYyDeoM9M#wPc3O^n<@K?1)}QBqynLp&6v$eUETzzQAH~|ouJZ@icg=Q5*o4gf@0%r zwl7${+4+zcIYNE-Lp{~#P2Ww}nmV6aOe1b~b#$#%+$L^iGiNY7dpwa+H! ztuoDLjj>16IS~BYoIKrx`Hk+?&M)@W@YY&-mkbt~hm{w8(Gfxbqj0Ayh7-@FmFRGi z59+(|ik76z13aG&4&tv6kM}9apo$_JXY7>{>XNQ$ zyDd}HAa3N?r`^iE*Ry<U4Hyh9?>kgewz-+a|xxwhjsqP{V0zgzgk1fkj*9W|Y@{(ImLFsub2mH)G0D7Yy*P zzPEA^hs9Iq35g42Zhs1TZ9+%>RH)_%H)|N3>igQok)QvwE#WHglC18HyOZNo+SH>K@%g%wHqFy@UTw@DPOSu`SGy-W zJFWfsa-CxTQ>sg{u*F=`M;{1w>U3-h=vUztBrBN)52kYoo((s|j%cFz1lJEM-X3g5 zlyA|P__~lKxtVi&h){;}Hxz__MJK_Vt2~$KXf%|@K8AS%CeS7q(fiFMfQf~btrW#F zLdL8)hC!z&0Gx$uS;XJ6uW=!qssn_-J><_H1+$UWe7fXt6df^>FM(dMR^|h*)*t9K z-8WS|mpghB3bCltEd2XT?vqrOydh2Tj>Pfpge3c@JgfbE?WBd`RM zGM8$?pID|p0)tIdgyxOkB!|vBgKy6?SOU#iinB7s+JI?`%G58GX3+XX5*_N(ptxskFI}wstfPwwHy(KU@%Y5K zcKRmsCKQbW2zH)0XtuROZ+hhO=@YrA_^l}<`R?#?ogfczT_|0*g!{5%b4EN};8de< ziqo>ES(;7(X-Ai5ewAir_UVsK3S?tYF;Pjla<|}MnRlxArsPHGv|R>Dp@ARl zj1TPCEOGfi@*svvse%p`0310%+ZObie~a2|9!5dv{28R!!plyIe!P7YWdjF-*YLxc z72WsoVZOI!k$j)zrk(C4bSDpv7spJ@*l|)_{+@7LkjH}y8XahLWda80?^vw&nrh5E zad70g+tCQd!%Fc!0{C_4ej#wv1+o4yd24kgOuVD)qr`7AkZ!wGWW4_`-*zk@=NoxE$aAQc$)vzLF@AbmuTyHdOuO1a6DXRk%y zN81t+%nb`Rmcq#MHy=xPD!PRHGX{1D9GD};&%9B$euni>Y)h179s8rxK|K$Y=PKI%jl?9*+k0)z$%5Thg$Ws;%_}%# zTGhaBK>@~KeMYP{1*>=+c=@U`+Z)m*<7<>{DJK3bZ>~cgK3mo7(h`!x*Ka@@<&Vo` zTCuToi#+m^1KI|lE7C#U;k6jDPS+)u(2bexMWx4DO>ql0o8zT2Cd9>hjCNS zVtGxIh?Ol#q~qe<*#gjz#^(JVa^mE)>h1&~ebpIsA8UGm+B+OY#byM zjPn)W6hTf?$pbrZ76fbT1LkXvuKd*N|jaC;~j_Icm<>BPIy0j2hKfPAA>cv`aAebeMNRh zKtwB%y8U8j?^k48o#i5fiF49g!9;Yi%xutu)aApu*2DRwsn4g<_^v7Fxb8d2iu2Tv z7yiLXG?wESF!G=gHdB0vB07Zi@e6%s=jM73d$>aL>gPZmzBf+V#0s-|FuQ}t8={B% zD)jGT8npQ!dU$HtOLLQz_-(=URyXLy2;jD%*Z+F_aSi$SAQ^PKfpO_z@9tnHvUZE_ z)RXP(dfLlW6iHiLHEBOhPk-kdC&zMK;Oo9fPrF67GfyGL_4@3)+n2BA+QxN!-d$CP z4raII7;^=~H;}epTO>`7*G{kwmMd$WfWW(5CZNGARNsYbdHS?zo&!{=5uXG z&8E)A!YUV?sbm&n5)d_i6@o7s3hSi3!aUB9V2iTxB{Fj#buyB!4cAjT?{CmR41E*l za0Z=O@5W7M-z!E6ADsU2yKMd_4B3&xbP=MZziC6XqfUnf2D}KHXklIsyGu3ftLx=x ztE+!lsp|BBwmX&RYB&e+I%SLhje!`b|966ThvZR1SIZbZhP)0u0U; ztj>iRbZq?~8bR})5>(>yfuL6#uiva(7nxBM$VyV+ryt)tRxYq)pYQl-nW zGCngR3h-dd+^O3e8}uOkaD3Q#ir|wr?03%XG)9Vp-dLH`L%QDm{yay2BX6&EE>}bA1Kj`PMIQ7Q!6|jnB?h#u#|SQ|DhI3f}^;L;ItkLy$l4 zDnL!wR$N*m#r>4qAYF=_<`{osVqzqULQV5Cwn1T*<<7Tn3Lo?Z5|bH?(&RKfi@al( z4JWPOMLgJ3<5uYfhdI_V!9m{K_YoQT!$W5JkKaRY5#^z^{M-W{556)o#;(s`lK>hV zE~Q(4e%o1985zD#z4NeqCcV7Pcpd;P`VwFy7%1CgmT}OFN^a zR&AT{D=AtMZNO3`&y_B#5X*1xHz9`F7y7tiGB0AJr;pne{NBV zOEM)$W!BQa;G{$VVd-YzhBR*Efzg9FZ>IIn%EKd#^=pGGR0OyneXR)ow4V?L01)kp z_E}r7Byp_I*z~rc>fVGwml|yRSn5C9mBmioehdg6`8U-z`E|LGc-ewN5@>r!m&vb4X<;%15jFnpl!T(+8+LAsGOV(MFZ%udP>Zb zCs-mX@-n)`hxnm|UE$5@I7&Aw)^MxI8op|7jte}yh}_o+jM82d$FZelTKo%vI~JDl zwMVJquY)P-1wmcaTSnFG&w$+lks88i2J3}g7Qr}z5^LcqWabJNVBaY8&#*^#-%|WU za7KY8)iqUynf;#Qir?t{F_Axd68hh($@}=>Rx$PSZN{by%Lu}-rtiR?aEqdge68yE z-irFo8vSYyn=c+&;Q`do15H)loiQYaQ#$}TCGlHp*S9gs-CoVgm<-L4QfW8k588g)(PfmIWH3Z o#pvYF|JC>Y?`KyK6V@aBKeT|W`^{3}C+L@of~I_>?5B|b2N!)r6951J diff --git a/docs/mrs/umn/en-us_image_0000001583087429.png b/docs/mrs/umn/en-us_image_0000001583087429.png deleted file mode 100644 index fe595ccd37963a98bf6ad51b30a9105c5183985d..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 42441 zcmYg%Wl&pP)HP6~XbZGZv=lEc!5s<|Z;QLT6D(-)r!7+4rD*X&aCZwKI0V-Ox8VBm z&NuJO`{&O6bM`s+%${}k+H36}U(^)|@hI`o(9j5#K7aa#hV}yb{4W0z`}yhCj=7A6 zMu(>KNk+>T{h-~)lUlpsY4In`bY+(H@Q4VGN{ZFC**0~B8N4}t_Xfj_#^G#9&*aA(j=~}C)Ee6dfeq0T=1y$SGu+It7I`f$&qGuA!TXiwN5Tv*s zwxav&9BlimuC<;A_0jyOp!Xoy^S6U5@~%M5r`)x{!|A?m_`4c5a{~HtfPvuQ#wp9} z_*QubzbIT9l|A7~PYXX<+;RB7A@5SqFCOU8T6i`*_|oIaBCj4MnGMArJ8+_6o&+DC z-tgt&f8b*XONYl_uh<6)jyom7#gacP-U(9F{?ATM|Nnr|EH4!5JF3;Ayv`N%8z9%tirC*yzJbu$w)4WL>Hr!<5|4unS;N|Tt|t)gNDs@S%+F3GB} zvY96Jadm6ct^Jw@-Z@9(+!Z*5b?u|+HD1~29-U$Gin^`j*w4O%g zVx$1&5;NM~NXO8e<(<{ayMI-%Je>m7*(XTn@^p&x>-_{fhr*h41Q{J%p5;tsSS6U8 zd_YBT{JznL=+iNU>}efZt@zPd`^MnjxFDo{D9M%#@_Yn8tyA#=3%`rNVR}jG8B+4VbIzcax)_l zy)&))b4qU9aLQy;<4b^~S9Z2%gV2?k>m)^H@QtV^w@FXoOQrj=)+^d~a zOB3H`xns)4)EBU5XORiidl9q4G_ZdJY?MDgUwVA940Z+WtZn=-H6YBErRvjC@b*N@ z@mc81Jqlz9!8rFDP#J7NVbB3Qw6E~$7(lBs){$HZAjAjmRetyX^$d;eGo zB+M}=z@E)ljleb-pU#jz#hj}}=wWx0S$_oV6kn>%=bj4e^U*bo4LYWdV>btB#JInZ zEe`o7^I^&$uYDAsiHFF|{e!ftYKWi2W>G7yjg$5A;t!j$bHeD42s>`*G!dh-y zO;S!sd@&|Sxhg>U3zfK#Tan}-sXql_kQuucyH5h+J4A6U5!np7RQ&@YuytNBWB?kj+ff4yotML?F`(U|G{H@LhU4W?ryU5)Z2g zdC}G;`JTLfGmg!&Y<1~wPo$pvHd@W->5=Brvp9ao?`j}V(plh+tF5Osw_`9SRl~zm zj;Z_7;ecM3=WIYgK}S0t>27W`b zj=)GNAs4sJFz%aPDbw|FGYWetq2&^T&b+T)nqtIuJkgmL1d%_w>(KsQ_>tQ2I~GFo z#tK7bcU95m|AwRpOjrUbsQo?y<~>9TP8L`svtGvN zGL&LL^KIs^Hm0v+;%qoGxQPzntdrrIQz@5I!haueX^J+wF%UUZ9Q87R&<}&qFO(qC zeJWd>(fcyiE<0;nWMQ>^na8oa-se-bx2&bBP`~Jbo7` zZ!!+%=-JoIEoIrf!Xtp|bjh6Avx57;);#zaEsG)x!C0)6iNDn`qd|(^NG46s`~-fc zPXhJIM2`u4uruFL%pYf3U418;x>&d&I9e4RpF1~PTK3JmZ)ea{e3ejgmBq8s=S?gf z1+pR6s5nSx{9rh154&NTd1{SR+S`J+)8w~GB)B)*KARa6>dgoRg+p;*r@sE<*B)L% zRvRW^HvTx&0$fddGr~)Xt4v}nga+AUm0$*M@5_0SeK#+!dR0GiqiLe6@0Z?xsq1$L zM{dt|jHjg@#ps4Y3$V%C$)LtL#|P9ic6A1x4vGgy6m|_IR(E1q%PX+^^c6dzm{N{m~(dv_R zFZN??UAjFfT6xWPNJTxszL*JRs=v9*lJ-)?wh$}kFYe9?hHu9AT2FO@X)TrG5rdf@ z9;X5Ih08iA436Q}XzWNno@C%n$M0XqtZ3zEM#!`lsM=-@B8 z@sYAm@-526=L*o;30dhj|HZfz6g*RvdGkkV z<3VZPXEOh18DhDg&?)YW#Rkvoud(l*Eu7~~WHz%j6VR+910$rmM%AKAj$ZXV1)UDLs(}}=pewwi zrFLtO8+omAt;S9>k}aWz5N_Ryb#7%4(6d*nE=fq|)hSXwS)6AXbv$|V$LF)Cqr-x4 zIr9(J8DoGPc&(M{5RCMwr7Pd~fH-K$Fj zKIbR(z(OqCY2-)#5_javq{#jFyQq>W8U>v6*8rR^ZTCE_u{1Uh9Q)9@R@N6+?*Ogg zutETd-Tyo=49ex) z0+t<4`2941mx*3{;P}TCI1Tec>8iO6Z|97!Laxw%k{>9mX>0D zXTc-%7}t&rO-H!hR&wj~4<)6=+p|Z~?>2HqBG5(dlWqL4!WQ8;*AJd0c_M+|IZG6p zc$U;I-`Gj!7>W2tCEl)41zg`WDm34mq_K9QCnh27P8dA;y;gi(@PW3Go8B7IV5<0= z2d98-X4}kz)5(trRw}!WZEBKf@zDv*Uh$>Gm?22gIc1fX4(Y+(NZm&!@a$w^c1m4V z?ZA|&tK@r5yWD;hY?8u`^t(=|eYqp4Fxe{2lWM(wIcG9=I!ES+?ssE~?<37odAK@R zi7ChU%~)t;b(=cQq$8<|wq=k#ie`dlBg;UWLoh*fKWah8wqe^RX~DWiQmK{0MfEdf z&}MPOb3QjW^Fn9n&c3acX2}{E$0r83wuMMt_)qQREcZt=@Xbb*59SUrr*kk@LX=oS zV_~}Wywp^m?+dqgU!D!Gos{8#is*i;hP@yP(XVhicrHnmu^%3kh^GjMMt3)hij5FI z+(&45ckcD4O$Mbuy_4VI#~p=KZd#Z!EXrw8#%VSjGrJLfwcSIR%F^2?o9GA zknFK~(olr7vJSQRTn#bpXls;s$8%~WT_@BZ1S2`QUR{$EHg@uBUbZspikwFqZEhu& z>-{bm9A=MPd*r`A>9zJ2NcozS_SwP$J?6pC_r8Z!V+>aTS%~K0vp`fyUKTmEbbm<_ zMPAQm__w+ud-kvdggld^{cmdBz121X>x*tjl;d%(jfO4P51$2vsk`(#Nssu=lE&Kn z@$XX-FQD<~5*Nf#vpQej7yQ2RC(2+@a$OqvGgs~IQYAz?Mygl4{LwC_Cdrsw1L$0s zD^BYC_93fBLQK)NF6e7tAJgx7aH?$%En?_rf>LZq^Cs>5NWtp;4_m?QM6qRxD1VF$ ziT|?df2(yi4ew&VH8GH1b;<)_jB_}VZS$W@XJ$z@eHYo~nxy2Z`wiwyrq4_0p8nKK ztVLCys{EVTPDIVXmUx_kMgtcO_R_^mVaK-T(88RkG^2QAK!0lFDQG+r|a zfc+SMj&JQP%3T_~Bq)-)STVZIw^dt$m$8kEIplHNiD=n+gdpbm+Fx8C)Cly$s1F?8 zk#lJHc*%d}^KC$T!zMu7eagXFx+d)sE zfekhB;N%D=jT2t{BEj&z^EWBvTQ#g;j8lsB<}9AcC4m7X_3}%6bz2`Ge#u=5DmPQ- zOna5O3J;cy1WOJq8s&KKO!8EF$@!xX{ zOqE}(LU!Znd&!TDKw0bmtevf~z0i-Yho8i#PBL=322b#`(#{~F6?uZ_(4fT7C+f8tp{N+M3=JFJBZY-2W9Bo%M#4%oCDOegb6 z^|ce^O@;_!XJ%C{$Z8n{fAchF7ca#OBoO5|mLpC-vB$LaA#X(V>sUs=)k#Hp?@LB) zyY*@5GPKrOe00}U-IEPm;pG_O7D}LJ&nY6guInJ2; zQDYuo>NN~RQDmo&y+F?i$7KHJY{pfRnR1f*g3r#InUO97>#fHkm55=yy7PA`>^~fe z5|8MoPUX;i9*$qeOxoWTA-=3)-!L~3rxi>e*|G(|MYVg5!iM?3KgOHH`nKXs87vI_ zz+P|mNU=rMO0uVKyQ7oQNis9%Uht{04+hD*gl)YcTc$5ZNcz)$^z4DCfdmDj znR?XNWPL!Z)%Um-%=GFtJDE4cv6sSXBeohAy$QQn@oKGc`7!hlT1~!~nkm9z?ZZLe z+PSP)wrh$E^8G8_x!&$4tPuNdZNKd~sKfK_8wA%?#j+Fzz4S2MwyzlM?*6g0h3BoU zWSzYIPyCxXSt+Z=Rx21s=4*05XK`Zv`jILr*~O%^Y4`)hC8&+`S&rfexl!$2uGvbEsC|`qtdI6r$6?W-oDLGVZY=OT^mgh-ULT zg_iQu(91hTg?AM2u>>_7Vb9N!Qygg+cbavcV5FT}$^PVKBkY$Oh$#eRt z>V@n1&U}JHLw1P+;x+4^up}{hc1uL&3h!aAab`GJsS7=_!pWjZC^e}05AoBAzKEC0 zZbsH|wx*mr_45;MtO{d=)sv`m?lQ#omG7L}Z)9%S5> z<@jer@dxnVy;ZBisT1$W*2D=>!%Vkw-s_?-^`P)|Ig;E|4qGKt9Ejo6DQ^g3O57;f zMjUdq0jUc$5zO}cAvB91S!WPim?lj!l7V?MWPf^eI{rg1GPEPCei&t{jAIx}y*-Zq z{uJsXbhDGJBF-@GF!y?&%Hr)RiOgDWxN;d2^oZ)E+C)! zSX@oF`zMGMBIo$06Jw5rZ8K(qCJH^BHpd^$zq;J3p<0PLcQ8a7KJG2@#@$wY*%VSw zQL(1gQd<5QXw?2M{+8~odNJY6>&dcP3KHuhG#n!5qM%{i6@M8}F+2mt5G`ICzH%m9 zpecdF$@avSaztr!+%I&q)+ls?nA$fY8CmMgj1O@N6)zdGwa$##Z^NMwX>jxyugF!G zzTt8S5*SJ7d5wX^Blet(BZfm=x8{Nuy1eY4Xrp@k7E=#$KFq#S0W7yhaN?u-crCIT zC79Ah$C{BQNZrmSTNe|m^}gqiV_ayBd6BU^WoU0$lNqIZ{^c#x9LrV?;~ddHi$<;0 z5XJe{hOBo&hjE%&Y7RM-TVNj85&4aUh>so$B&L$IsgF>TrFtRPS|~CttWnSO*DVDp zaU&w)^QA!91oi_m2$z(~6;2FB!v$#g02!?E8PPa}z_Z`bW^5|!i0jhp#<2OnH_Qq{ zx-^6n9pgXoICro}*$Q3>I#zKW;Ziy)m2-CT|Iu|tM^nk0C&?O-1_e~sqD2OJS}xjD z!TJk94cL>LGbI&^w+q*8%`_hEvc?vjZz*lkS9%Z;qxc}O9Ckm36jsN`$7v|xhv81> zFDG-Jrr(K1Bk-c~YfabKuMEuiurwnTn;@1FhcjQEk!8R-d{K;;bZQ7_?40GC25rdq zP$=7PS}+(+_>%3rqP?9ma$8Ik)c!XLlAP?s&SqoyRiOH!u9lrY+G@QbA}mL`Q!gbs z3H4>4E_mf%_?6+lu#r|@!-3XqaVxtd;Ox71&mwoqQ3kDK)yoe``*urjDaiqj!%*jK zE$t8c3@q1f<>!TcqZ?+fQrsnugA;nfc|O?++EBF4svm_*nwFT&7?sQ~pqG?dlJadG z#p#?iA^G-YL-^URruZ{%AZEPK6+Z$t-HlBkd~$kZW`w>0_kmm!Z|2d(#%%Mi!eMUL z$dW$wfl=QvQp=5}KbRmUGz>^l<+|yh$hr7adEQv3HwNVFq;P;-`#7sYMMxKKLJl=t2mvVhy9zm1ESKs=dEjG4q6QEN#_X z(!WN%BU7@#nh;gpk?cE9%5Pu_mxB#*3E)kec!27YxP)AKqV6EXSk1;@=IU(X-bMk% zfcsVkC}Jwr7VcP|e2}={_3uwNE0}j>CmeW`A+1cpM^Waoxz|PV$T#g;tf^Hs$*j2%h{H$G!0o;^C)4b{g183>dr%|CY^lwVIZDc(A1lbEb z8onlkd$ox)CTBDCyyLJiG)`rGrK@7mACceQ&VXS?TjjE4wvD-|zvrW+MINi0XrM&)Zv3Z1J)oDM|PpD5^f%n$|XMz17o0^VQVT8l1Q_7)ya1!Ynm|2=pmg zrVxoGwr>KloZD8pQO!RghfwNK4LX?SJQ_&=sqdF0?Y@OjxRFUyf+_dTdU6YW19Ze( z&hOJoSBGg36kUlg#Fp$l4KVYEh4q!;n8&QA?^j+0^QZcG?=kS z3f&X{fqrb6qO@BYKtqwQnxj=Dn_?;(a>HKQe{}YhG}sWIsf#XQBz}U^9KPQu$kEBMw?kOWiFcSx4}UgCe+7HVqK3nE{h5}FAnTpts>8R_$HY#avFC^;;Z~ZA*sAP z0a+!wMgPSnMw|GBDIHK-Y_1n%!R;$F3VU0~e$qdD&A4}L4=ts=iET9X&6!{jn{R+# z-`75>m*pS0*Tv-nw?ITrdqt88Xz$0Gu#w~5XF_c)_GI??$*G~aZ0JjV@ipssgHbqX zsqf9GQJbMQG~J-~3Q6x6jrU^%dGX(Cf+;~44^GQIp^4mWP#=bwCWp63A#Jwv$I~~k zMOeLK3B1LNS~3nN0}Jf*^eG|Lcq=#OJ)_j9CMK>4FDU7PZMQBqe&Q>w>7tr`G&!5C zhIj#+-am6v$GG-xsOu^+W`dZ3oBV20_npISES9yvMD4iIY;mQbNZ=vm9r7)yR3xlN z_>9qdW{R59q`UUa47bow6azAxCjZbPK`jo9d=VCypQ6XkN~*;cK&tY0kAIHk*ikW=iwg03JSky)cePf#_F84^Bk`V!wE%KZTcLYyk-v0n5+)yfmCpg zWx4KnI>KSn!7tqQ%e1xr>Za}3N#6k0G}CRyjv4J0cF*1{*y8&2AU3J|@knhh_ETNZ z?4by>{})d5re`nnY<62WROl*=I%M~OA$`I|f3>4PQRIH;H4q&71=ql%T6}@L+H89> zwfS-QZmG>Zp4dFA(qy1z;8TF{j72N+Hu%Cflf-Uzjnd@v;R&QoDofGk`!8Z&Hfhv| zo-KyW<-f~5R*j>@!IoR`$@`dlu#Xn0c75ohHA3>p_kcGxS7apT_MP~rW*;Vw){NPr zSEuvqwxAoxvG3ElXoIuCV2ixh8%E5$Mhxgzcnrsqk1A&BqGCIRWFqV8$mBE&|aY)sVMTuH{AhLJH&OTwf0+*uaJNCNu6n6`9J@$&G~_j2$Y zu(!)-nSz z;Ob=AjJ;QOh=SMp%uI>NQImcMydWXu8}W@e^ONZwfes?|Ujd`(w5Ld>w{TJS@qxOX z9ue%-sO`R|t*mNmBZ=LZeV9P@0d#l+y?JHc?YZXa`}bP&1+=^F?F{fwW5$I{f}maz zJu`D82Y0nQG)PvHs@XtSl*rDzsHQFK*F_OQ1ipbCj%N!RrJ>H5yCpUho$GJEyf;;+ zu}GYcEp}e2tXDYGv)EDk1JyjGM#VTV?8Y}X~}7`E1CcK;CxW zOE!#gy~(U(cc#GZ-^b*T5-JdiMF-1-Jd?1g7-Yh8LAgg*T% zpzD}vJd5(3g1IO44Ia2OEt<^4rP9L31C5K`t_o2Ob-Zp9&ma(DSUbg6vi{o;wL1IG z2Nn_GYGp-Y{h^ytXdSyA3K+ zD(V2WS=mhR%ruyWP%>C-c##b-o}F%s6KM;s%g>$z#w={*<@qYV5PvyWsuT@1ca#$= z*^H(<+S)Q=d(rmex2g~!t;{scr0)qX5f<>Oa=6VD4VsCpSl4)XJ9_HbXP8s|$v|{{ zlcKx$QJ~F~9;Gk$$%^QefX^9ZMg9kshVO`Gr`B&pgA zwfYsQ{odNzX9ELt?VzLZ&-e~Lxo$0GWU{WJN?c>YW#?~@T0jSNDh(UV^h!%3`k~7i z(sc`LXlKyB+}_s$nCP(lrkNk<4Abj>_p2j=eg_ofN<0TxtIoQ52yN zWjW@8Ug+FvGt~rIgOeQ!R|seok`KMW6Wnv>e?%F^Nf|mv>x65p%K&{dxln= z3Hbf(LEYtVsNww6hKl%7s$z!I@`q4F$@O}akgz~qxD2nV8aI9lK~2!+Yez`nS24;? z8jt0wAKKGS?R-RbIT*PtXwdwD)~k1`?e!rUpH1C!PBk*+UF1382@(H&=^RJmv-p7P zCE#r->7gKRJ$v>D5q*oa4}Y=@&-DN4;FsAVZy*OoT1v5)g-IERUMlh$^SK~eshT*6 z7e##;R?DA{^A0@DenFIkpxtaFIvqXr{I9^Z%sS{KnB%<7pv%%gs`)y5s#f*ft?OIt zga}F2z4IS1`jXNv91+Rx{bl`u`jI9AN7Ig$W)^|qG2j`@(+VJ$VzCR zUG}vgAx%AT())n8E0a}Q45-V839EXp!Vyzzj~z-ak-o9`DI+~ytDEe!K5_q%fRsha zx8oIYj13-GB_=IHWq`MmXN{&9(CPrUknHT33X#BMltz_JkawY#wfRNR8gKAGmHeamW8FRH!ou8B2vN7W_g0rJc(YjT()6~^3e=gD+*i-_s36h{im{8&c- zhOu@J`RVnW3>_W+lFl%tri9dKqY@E~m{3yG&BD5jDEP&f@?xGGZHzQmGZ^&B*F%m| z{=-0h;>v0+z}y7rtuxdDATMp7==XL%h}m~?*7#t;+o8?&T(1lKmX-W7tN+J6MIfuT zwBcEqhSqPpY1ew|&5n&UM>N3q?rZO3E6gu6eRs*KBUU{U05!!PEW$n>J-ndW1!8^++a zCIov)mP#8EzC&MI5ZiehDd;zV6m@$f(zQKz2}BNtWcc1&45I7@;=a zxY5Aet5^TTCVzd#rTe>7qM0_=70f-#G6+tJX|mVRj^ zS*Nn%V&{wO$(MYbH+9(p2fi+%uoefZNaAmbB&txQoT}P0b}eE4ut~;s3l%Y zqf&00+j4;Tq!#gUv6#ivC?ieuIK~@x>O9;vmhg@YT9e(sRvPNj^N;%7Asg4glwKFr z2pAsdYv~aIpj_PYFSKfFs)aE?OZ1j9<<#$i;Fh6SGhM%H1>r&aTZpJWhY?eie@a3y zBKFMX5lIjC=o9wF92cK9^UPrJ&1`(v>+KS*20?DCsZeB7Xefq%y4n&KoU7MA(?2MY zs6zh%NNqTgmuuVkJyG{1`^>jNt_VfX#52F-?I>pLrXe({Ys z!+z#aYIh9go{JHDq(?uVY{3*?pEA`Yl%VXC!??G2-8jo6({%-nI9H?4>J&ZJSo8zN z`#);3%CCUEYL4~@jxYqfp<|jre80{HU2EKtIjokC1cT)B(NZr?uB58*Z=5Q!Ltxji zSnQfL_t}^x{?1U+Xl8`%r}29NsrwVo+=nyKYU9>{dPj2M8rK(L*7jD4ej8?QaV=%X z#otPZ;L1^0m)4<=ru<#aNA6H zN7!Lf1GAR|Skjqzb{%6EK9Yz;jg_?+TcJr-NLj693{K7;rIZWKc}V(1SUv^t-tJ>(;EH9vUzE`V3y(+0vYm3LG=1mNl0E#|HAc@DE89gcg z=!G`mYt0Q-2MEZXZQq?hEt>CzPevtBmh|`Is&@|!Rct=053wmI*2iwq zX`a|xz|N3IZ`3Ss$3;$be^9r+POz;#)&1k)CiDKwP_B-Z*)In* zDU^p-k}LY?bJ7~WGZ3@YorRhN&9%VJ0!4CbK@E7x-jv(=UTv)oZ&&emyJPOQMC$x)YM!R4x68 z{|eZHK18(rv!YnVdoXOx3C=R?U18MVx6^HtdXDp>xZFw*=7rEK+8TT}F0P)1$i)QU zkZhAGs<;bOH`-|a;r*S)9cCjX`{KEcG6yq_WR%3OduIT9GMXqxgBAre{0WIT5=GHl z5ZHP53Do{(L5O!f>9MEQXB@v@>U(OfSa_M?wLZPA?cr>~TY332u08>_;md{4rJ6f+ zm2foseynTj{R?YDW!auCwto>h9yOV`yqgh-lv=!FQK_3kvHmHDof}j1j zStqJ4Ya{pl_k)x_j>_jwo;SXEN=Z>3{@c$tNbjHx`QukAYB!M|q_yCg6>A z<-}Bzz2LQ5;0s_gz>dEq7*7<8c%po80`7NzS))k&?_ldI-z3VCYqE&>7j zevf{!h znTo8uuO^hc2SF(xEgzm;D()|yEH7RJfSa<&>I;&+qTj}B)k=5_uz zbdE|rs4JCAojtgY#bH4+Fk7yqU>(j6=ZvhkEJJc%gs5^vhiKQS8{0tQ*Z{E&>I9Xe zNcQ{vXVG8-SUOhy)b(B}cvnyc<$R(~TaXxHQ}WuwzY+B;XZs4TmIc$>1^qM)zT$j3 zIn%BRLTMN+eUY}V&>;rHiNtKV#r@TR+c8%+h{kVE9rqd4osZBsG^obOX>JEHuDWfg z+%yORZWY@Z8P5cq4?u-EtF#w|@9zma9+bj&C%LIOwSBKLC*B`MabLv*=4nUP};Oxiz81rgdny-+e-@s3wC&%!i0%5 z|1FzHnlyXd+Z1_&*cME>9UJPAPR#-P0Zvj|z)72!h6%&QwR(RG*s@0}CJgS89!h37 z>x55f3zuuob0^#3a=fXOu*rl8wDK*hsh@#tHjhgWmD#cD#;6(#nIGF~!Y(P}awAghR#5o#M(25b!27hMG91Jd!jlfD(Z%2G+O+mVqS zdW>59i6h1mUsxH*^xEC@tI2u|C=dNRT)K6>1SeosJ33|=clwFLAza4y-+D+i0{)R; z)B$n7#O$reZegmJ>e1nK=^To9nbLTPaa~X)-ak(nOcQfp`VF z7s+$?5FAjxB4X;y%YLFQGw)Jk$!XP6i-4U8zd?yj1Ih!2e{yc^*1vFqx*~cvcmxIN zYXiJral^Q_9UeWYi`=~YQ>)gSM?NiJFt+$($0se11g8hQd3WclGR`54#2wn&h_oTQ z1HCqv@v$YC^E2x0 zWWE>^ec|^JyQW+Izs>T0l1=1!BK~i2OoXAO7crwrGEoU!-m$`^Uhl#MZ=%*0K(U#o zG}b`tT6w$S(q|gPhodkLMhcT(IoV8YH;Nb>|JOJ%5;C?q)YEU{&C}gDB z+-Te>D$ovHK6C7hdzChCM%%GQgztl04&MJz_yzmY(S>Wg)!aQseb2gd^_e|O>Q;~N z%C|q$#@-r=1no^MVnXE!vhJ~1UUAz7#cHK|y7Ms&7$O1qE37ZvGIriQQnPEyrd1Ut zD^1;V;oP02eXUQ6DKTBsC8xEB-Eb;XPF6!Te2q2rjjr$i*&sx{)iWg)jA<8?Zn>ZN zk$peU9m&+;d#8lmt4;4FSjC_CaZjpiVlD?U;UFK_?+Ev|g6WNCb;eIsXPaAnji7i3 z;d9XK3GE%6N6iP=+$p1a-;Gntf9to24Y(IXiW=jhQujvFVIzY?OU!m1gpv^FECRq_ zeeKDb(hA6(LHo>zp_4rn(c5-E%R6g*y*3jR-6$0lk*ETBJBUVLXKXl+y70+@8!3R= zraS)zc%;04BF+P)nFc-3FQOiB9sR;5=BiGY#%M>ZZ+{{~A^PsS*d>=26X_pjggA5T z18r|M>Y;e!9D0SK1rwP!PUE7Rj5Jr^E}G}guI4&QYXGdO>;HkQaYeYgKUK5ihF~?I z&2n_<58jA5V$bsaG){5%baK6t+SEcHZ=CvIFOpY{AjA6A0-qkKhvPWM3o-Pq;qMwl zEI647*po5&+DAr{_BEc zreWndVM0SSg+A!NtX5X}<|(+i*a~VFRPw~M;zK2dkM**r-L?qaHwb1>RE_CmsCU1p zrvi#aUjGYXK9mXd(INcPZSQpG_dPg^MztxAlSBp;@aX<8hJQB{%+}2@6?T+T)HchL z7%_E$@Sp+wy~hLD!^LB5!V_3B-$KHqM@YYwi)a}_N>w*S7=8ski_Q@dKmE0M6%hdU zQsGzv#TT@a9|>&zUYqgBOp%brLmyYrA14$3%S{xaR`m6xHFOm7_0q|Mb11`^_hT@& zgE#6)*`ln}s|>oE^I4VUeOO;-sjkDO$E{POuLNbjFp#e$#F5 z++EI1?PZ3x!w9}u)1+2^tZ=tw69aat8QDc8vUkC%EU;eqzh4KrU#1QY z3ljCJZiU${*5WUaNJFRa8@oYh+Rc6SFGe-+Nc`Uu0@_{bwZ+;mMl=z;c6q|pKT>g8 znD_%g;?*138Po$55M?+2nk9dDGWSg|OVQ$%L*k^lqg! zGg&kWlL3Cke7W`|!N+PsLJnU0ITi$}2*KCT-(r|mkeL9w)F@D0{%HAAz{S!A5X3qP%WQtKAX{;2<(B0sGgeAo9s_M zQddX5lW;FD9<@d3#Sf19HtQf2jHk%PtgsSj-u3>Rv>-}minnVI$$RI&naq&JfnzJc zdp?R2fU+YFv0%iJs=bX834G|U`Q_2ASK9bQj;lT%n^`%DG2?SQGZr`Lw}D5-%Pw-`?Wn=&5TcBJ1HpFQo*px_&Lsqw*i?X}QKdr$XIX$<3V z5g_)({w3;~e{qM9d`mm6F|2gy2BZ4nEQ#s)*Q?&og}mlAT|2c-eiJ=mk_`4d7x!<3 z{gEYzDH-Tz$?RZXJ>3@b=a2^be-Z@03h4L0V^eyS)Vub1vwy+AA(w^UuMzyzECd4i zWbYVF?P%)@w+4lW4bF{A8vE+O%>8ko!7NaOxnvJlsBwS}GnjYL~x$)xt1 zk%HG8aRo}!K&wr%h9jww(tf2B+wzF3B7W%H$~$xUBpQb+I?-24Ya>O2@M#Or1(piu zx~jwIfGf$kbDQ5BBZ*Yq{4Mk6XDm_}fa7&&b&joOB&{j8RGEIQ9E@fm2_?Vyt&mh z2L&IYR8ghTwm9TkQ+IlBV!7yp03PAgHm{PKO9ZW`aXs0-?^A^h*+Fo!kM|hkmx2>_ z2Gpg))3-tOzi5MHNZI`T$k4!VhX5hU zm1M5{Ak!(3$!^De7J+I>2EMgHD!Zer1Qua6Vs`kxLSL@JDbtPf8TtQbtgFBF%|){# zAUbuRPD#|&nPc#;d&=E0yM4BN4EPsZrMWALF6=kQ4VlwxSq+Mpyi5$g1tSYEF&A?&x zY|QKtdv$(h#pqVCU<9og3a?e(UtgN6z+Te)He>DbB-hnJplHb*k!F zE6u}dp+VYN>lDZv5rtfO+=uyqJXWVe zkBO|Q32CEGqOWx7KRfSj?e$<8u_+aH8?Na4^eywmtn8`h*dK3QbkE%1m090!z6dlr ztU&q}O^6!^=W_Vcm>4Y#Z8!G>1AU9YnX5jj{6eFouD1S4`~uH2B7?&dzYw)#v5l7} zr?vI>_E6-` zaxFw;d})~bmi%=4XZ`)$Sx}WXUK?9p@0>P3*W3NHfW9(I1r_mxnIY(&R}&S75WE*2 zKgeSc;Yxi#&7EB=saN4zld(`{HxHlrln0FDiKK;I2Y7pNtO-fTwqh9oY8z`(VRsI$ zq=44n{NUIrAmTKH$3%3od3t5E*X!XPlqWk0C?9udPfynC0ppW-$mh>&_UJ$6Fi*j~ z#KipX9}4uoPK-5sn~VE+)K|uru-S~0+jYtF;;5F{d%JbB@MHrax4w)cadt8*9Co%W zu@|9r7MB8b6#IL-h=?5TF{|suodYwBUdx*$NQtr6!RSktk^Zx#?IdXwW5DG}OkTM= z#Z!At%m-JR$By(0SEDXPARC;LYgDAi0^W5{CTX&Bw4GgrI{= zZ4MF<>%zcku8--E&jfSPX6o~^$qTI&4%b1+D$FD-x7_-POH#Y-dGnWma7$s zzdlm??;mSDHk4>U#5PDNQJDOY{9fc`oyVmWTY%t&=FxH561r|6og-NlqDJ^VNpJ1E zu|Zd9`sVj;-s6$gcfcy|Om%~c*DO_?-OVT@1&zc=P62t7=lb zadrRwaX`MuJT5EB*gWP-fV=-7stwv9!gH26hZ;+t=3FiW*mM{G&$9-}o(I|uM( z15HM=l7g%ZGsN1D3D2Refo?!@?EV<%lU~PZrO1f;H zYw|tx3UaqknizaC!Vjm` zvqje%mJ)FWVK%zmhQ6Zxfnp-45$h_B?2x#3GTn*Su`y1;x7sTK>UMXU(Xp}rZcZHo z&PQ_IzshK5yq&E=PRBGhw*?8}T1*oP^(d3qB1(mPksyXA1;x03s1xg|&XXnzfY{C# zEWw)1{;v%_(IA`cq^3W_j~%Ozq#>VWjjY6=t^10z zQz75WNno3=%+4wa!8B zY+#8<5CYRMw`st~l^q7iL{1MQ-CTP_eQJ)EfNenMq{O@Th(8NxiS;o|xw-4<6OguG zdz`?x?$=8D4@!gJYzDSKMy6l1=2z=e1E9k*pt#qgQl!`hu9r8D>m-H6aBgEP1Nl`g z$CA7`QT5K$NEUT?;WV|O>8}hc{Q{0H%MCvK@A|F;zY52>AZ8la-LhO65*lb})?N0_ zWR(G?AkL)f`%27FWi%(gm=x&>0bc=hUEWAA1rIyqb(Pv76>{NLf4$MD$}5ocfh@Pt z?VF7tvC!mXMe`M@;Kw%suZ4Kt5cP1N)s??a8F`t9)#Ws;{0s&x_w8XHHPkI-Dmr&o zOmEClCqMGRO<@`fiJ!grxXlKM@CZ+de|TC`ZaY}}(HnpGnbu8`=2u)F%@l8+fAE9v z-KJs_Ej zZ4?iVXT6qbj^lrxlJr$qv2nR20A^O~k&F<?Hvxr{TjJ_E>R zy?ODiS(vzLS*}z~HFXbS6=Xn<^&y@^B}1WbKxw+k(fDELXG-p{jkP-7_6pZ^+UVZF zguVEX%CPwa!4HN0vW)5f^#V+$nWQI<-50**Eli$BnoZvgAqI@pjgFXEC!wV=<*jci z_^x^GZH7gEh}ybrxsIoyRCfM{8++9L(*Am=a0>$0kU4mYIGv9nO_dfUUJa2N|9NBxXwe~te4`~9Z_)u#~)xsC} z)^O4#v-G`Rp=HFBCC)7>#lxkWCK218M-8GPbXf#>mGk#AAqwl$umK;swKGwFbtG+( z1a^f+YBjYIX!OgIj~OAku}I9Cc?~tSk<-1kIarFvoo(bgrWc{_K*(AAo8YIUoo3c~ zi9qBg`{8K{H6VH~ATkkA*XR%uwit!g4j;#95L_@j_o602U4W)}+xmMUQn6f1tO&M* z!8EKsk#E&nDLAjXJ3q@J8fdsjYJ*=2R5H}NhC+T|SS3GFdq&#FS*ItND5pF{wzLSd zcW+r;Ht?0v)KB$s{;bt*^Jb$?aE_@#x!-oy^C2siALgj{A)!o{i>gmvOCRSgm-|er z9(~0$B{4c99@?+WwgNJPY6bMY_B#RTh4`)Y!jNQ5%oV;4{gC{VYfJqXk39=1c%i1n zj{!of-9Rw@O}MYQ8>8=BdABhy94c1Oy}IiE_b-PR8^ywiR1WX-2pN-ul^pKl5Bh~H zG>U-tX(5GrwFFH!yfAvG}L9!ImuCl>YGtrh6>@<52kU zi&&FHL*+sO*Ly(dWEzod<*EVS!0{+YhtdxWhP{)Li-mZqLf^D|%b3L>5d~*9-cvk* zo5AI9ff(lpU;dFR92HYPC+TyC!f>`fF+C2q|Z z!?d|LVnUJ|0D%y*=P&)oe9vWcpO)R*m=f7@s`6{SDtIZ9id;#r)Az7&{4{i>xdn77 zPeJdlxFt4aMI;E_^i^8Q_czevB%Mq_Y8t{_8KBQ^JiTpHU%)5;u`~62(bV@-+w#>SG zG>>NnhiznNU2=2tNC4=CYo|TMu*Aws>j7xQ=sSmj*H-^z;{6*v%G>-wwh7nF(HD*o(<%2D zz7~V+k<|ToZD_XLb)-H{z`edJs1Q?mPEEWtL&jN+a>!jD_xnZvK8ZVuLSq5fHLhih&Uf5A}S#aR-v7!6ff+MAeB6OS*GGc;}SW(VTT`v$2l$zWa$ zr*h#t4C-uMI4dWVzq5KDFR}2gj=@UQjSunU(sNM@P45SX=PF$kjLZN`xlAm>OBIdk z$DCOb?TUVVo*2udAmHhbIw~z_<>iBhorVy#A^r%VF39cq(%}LS?7sLWyg&c87Ws!G zBNS1`GOvH3cm>;&>`HpqI5x+h%lh|?96L^eGQFU(_a^IyfZ+)d9dDG!MLr(10!fdh zLWgiR>PZm=b4P6f(@<0cW6>3YXw3Yn@@t+S7n!-I{B38)-(92yL+KGbNsPQ5jd*L; z`kK%FocMh?D?|2ddW<#Zqd$|=a;Bulrw5RcD{Yi4^kXO0A=;n%nhbKnO{h(##Wtd& z%xb!DQO_S+9or8^wIx>{NDIui{G9m6{B3$x#{ys29=Pgw`@5w!iCWfqKWt}VmY_Fw$gNFe=E7A=-gxCo(TvK+-bL};Joyxs|4jS zz+o?wMa)0-%S-I;#&2@>K@LE96~bTzAC8I^g<6j*vc=7EOif|`hY z?_VqP`O>7F+e$`Q04Y@VXT9$({Urn8&+x+O zUc$M#wY;ggGJsT(Dsis4Kh9t;EW~g9thg;0Y0j4vRAhm1v$n%og#A{Awp+WB=PRh= zm*IL?18``pXb!eH(4zOo7!$9)&1c)uT+I<15jNH`Nd0%d))|&u-`ikp=jWvk6=$f% zr9Q|c|Jt205B{c=DUp04&^_1%LD~kcb+Bz^OSm6>0G}RG=oYB-u0Nw)4Jdv;S}Kt| ziLjLULOw^7Pc>@Ad&7Na_qo{AXn<{Z&ODWTbQvYec08I8wPYj+s8^eukW zFRUY;;hoXb2!W|>H(*PNNuT^$cyYHTaCE>MmAt6#U8k3;X<1`c`O4j(1jSFhqP>vf z&bloBpn#ZxNte{EcJ`9cM|-n(mJ|c_UE6``1`Cm-UkY*qWD#!Mt~T964s*}E1i6~P z5Kb=K#yhrijF>&(8fnJgc`Muhu^_7cA0MHA86Ei*u(9xN1;I?a(Sz2LkfB)oP6ka^ z`)jX!CL(tkpf}drcUJ-~(yws^touW>r9;KIsm$kZuti+kH3RouVn*io`F%F1r!XcZC zWm?NKN3u!T;va7S!)1c^lS2`X91_+1Eo+UBTpi;I%@XE6VAVLIogglTax+?^y1(g#oiZtr9m!oh^`t~vXIKczt0s4{+ z9DjB^n_KhIn9=#}Uu-3J^zbH)RJW<*9U#~ewuHQOoeY%M{u zQqgp|DGD5g*2P(P2)=Kk!t3k76qsqes~?kTHZVZ?RkYc!%u<$&si8MhlUq37TC;jE zZeKTOB4e4xf=Qtz);iD2x5eL>4lMvsgbJRt)qUBw^+U6sHNw#nw?08Qw6MrfL^wf^ zJ^y*>YuCa11C7jv_hEx5S(w&()-qn-!sKOIkNtfDzje&}yfl{C!NKjH2Imimheucv zo*KL(6q(F~xc)D{jWvl>G#r^e73$z=j+$ur;{+>xUNzv(i zh59-B8vu&@$Mw&o4tKIyi5w6cIj&x_X|@(s6}$m&cbD4yj6PW&o|ofAz4!7$xVAF? zYeKej1@8*VdgH0%?uVDp+Z2A7tWjA%6YG$tsWe1&YpbuAN4r7$&>z(qi9p9quy+WB z;ot(hoNhZ0v)$ac2>2tj|0uR;8+(1)C9|AUtnP=KHe)hf3A=;7Txs%llx#QflCJi< zYdAA(%6I!nINX7*xq~@`zsm`|Kh2(Y73F z$V1zzZhcI))P+;`$+W(W9;IMkvl^-*$;eD48hC6uf|nnyS;ijWz>`MQ*f1viRr=Rc zGG2fIWcF6d*!;A&Ty{h2%{ONgq5f2M8%@E=zLu_O>>CZuu9HL6bN$$t&+aONd}Yu+ z+6GKn5NgY$HEH4v>pf^0P`Zj5B5e_w6ckPvmCE2Tpo5v9wcbX?mk{-j>kjx3Z)!5g z$W%C(swfkL;@}bs?Kto3Uqx)lp+kAShhMTRh&!gAo55J?B>2IVgnDpb0q<*nw3ln# z#xM@P=Y?3A1qH#d!$$QCN{2~Q#b1H-1OqUn#}d3%Qx!MftyI-5w^ZdX^ugR!yVBo^ zuehL#P3UgHc^sVKCVyKrlJ+Qx;^muPaP7xyy?GwuSTg=7v1No#ZMUsulgDc&@i%bs z6vo#h8b@(vkxK~rpwH9+Od=HH_*k;j*mUZ7lqWr^K%vJ-a>nX5@g0MB4b*G&1;1^2 zAER!FHt|F#wTl*(Bj6`z?-ED!nT_uFcmHCxAk=rJjA)cy(AJ$XF2p?t3uP)z0;OqIpt6W*Hl6>Mlj zxutOzozXKB($QXubh4-V9&xxj__g?w|Q!%05J zOCEws%&9QezE8F(H6klfrTDv8sy9h%+%}#Z<{b6S8ZR=?5-AWNf>y^p7LizQ7ZQlf zfHj4=yEbRB^7JhX5^qacD2*twXN+$-g=?wK0)r4i!;!+7I6C>A!Qho*q;BQ>Z(qFq zm?RxLeX^1;H=+=sTI0QVf~6c41w-2L@rM#$=(f2;`uO{5lk4{<+y3n;lS|j{6@R+* z`G!CL-{m_V?jIVzn}1L~|IBCTeFY=zeVYyKEHr?_h#`ZxyBD|KL>joHtIl<7j%6|5 zKdj6(J*dFH*O4SR?iDt~o=#&gwr(1|GYk*?puKJ6CSdJlNvkJ8f|eFBe{(>cSw4-n zNgIbaKoT!|IRA8L4c?Lx!$78^@tkPM=bI`Nmu*wXZc> z1bBL-uW<^?ZT2FnUdPrtoKqs`8sx@^Y%VIcjoZMJy+7_uZVqCL9QEJX8k{ibEj zd2g&}xydEYj?DPy+AsX&RgV#P*1U9)xRtAXs; z+xHYOsxiM}Qh;DElRCo`~x2CHH;|^DbXn0+z z>*s&M=MyK(xzZ#9?*hFWdSS>dH5DY9j*(pV)VZ!+L8tpr%xu*bZ|x~o*NxR;li@RO zDxOD;n<68nsD5BtcOg|jCAF^Nv^s7)ZtbqTFCS0X$H3Xmk4|ZZs`T9a8f+?#y~;R4 z!_n?|DL6wHHQNQ8I5=~Y-8{s^-nLzjzjhYLjEUyFV)!c%A$9Zt>yiOZ@bZLnjXL;Y z{e48DWRMDZ_0$l2-1-w(;WfLie05fPbGS$R6s4rCtGRcP6(`L;v$>P$R!xuWYiqzP zD%D%^FRqi~yJ#*S4wzfw1~&S#H|LHY zMI%TT#CvY403PymaWBc*&8anR9QE#hYuMmKQQ@U13X^SISAPIMOcIETo)B@J{4m>T z#6iM*Z1O0JR*rkw#Wk5g39-dM)U~Z<3^MX=k1AwzQ=`NzVpojvf`*L~E23&6Oh*^rlYNbrYvp#r&BhFqEck?7>rHMn zLF|^HFH|1761nQU>7Ww>OZ*k$8i6Ify;=9gA8e=}S*vhL$9*9Sgmr0&hvs8T)KsCR zvuDtz8H$@F(cOgyux?h2e0oo)W*ztjFAEu}0>V=mD!lr0QdI=*R3w8$EjN3__+`aC z+986EbXw+`#_c+E4J}RacRYsR!sWj*(Ecm!5$WnQBzOxJSD1!UbpVe_q9PxsSs%ZE zjz|t0CF_Ceouj*X0TxVnR z!`j)_Sk+TOMl=TFQD^S#f(8ykgEY&HiO6u{E;a4%k^q0H;&<;F&xgO!u`vX4@xwW} zkK!k_aZE9MaVL^VZ#zHbj!OnP)LBoy+Z14I=Kqdlen0&DwAD?3J~PIXA$`RJu3#c1 z7fA6(M7bQt9~qi#RJtCGwctNK7C4{PtbRFsTz=TlZRgrLq)S=ER;BseILwt&8AGA! z{7~L^%;ym+W+R7mp|oN2qEC>yrwV*f2Tvy{p;GuZ^sLec_|`>V9R%+rQXW>AotL

                                                                                  WrQ74`S}~EjYHdaRe90{zKBzl=J&l2;qEUf*s25@ z5gD;TP6t$AV%>pqEkH>b`C%?Luj4(uMY-EAHz@fbNLyGN1_ zP;N?y`k&QD?iBopA(T3XJvT=u(SrIc>oJqX+h^M)KF}nK6EFDZ`nEq1O7BWw*wdY> z)q1S&IB}0^^()09-Ql836XasQ^uYqjw>E7zT97_9U8DaYgPX^1hgyLdw>v)_n{rYh zCG-B^_~jIqISPS%RNvcw^QX%)jm%u@=;PxEgc*zQQ7-+?@gNJPH8!_feX({klQ)KQ z3GC$R7I%}w@3KNHldei@XJxUpnj{yMXiLeHOS=NOn8nuCj}HQ&N}0{-x%(`3^?M6{ zSnf^wjM7M#sWQ4cjXKT*$>snG0gMf&D;Abb z%MOUY=9#qIe}b48NtCxH?PfwLK^^y?wq+2V=F$DPiL3&~LcdLvD3iy9a7dpZN*OAk^}p(eq&Z1z%V8`jXAjIv$d%ex>Tn zLU5hlS*z{X(ddMrE$z$}BeQ8D9Lg7R2$Pp<+PKT}>bUn)7iZ;Av*Ahpl?Ao1eg&oa zRzO4=$C*)tr${1cMi4Ks{0;$xJITPsH*^a>lrNKt$8Jg*MP23OVvh1&C+%JvZ=ZZ9 zF%VDGaQHBxYO>aX%p6`wpJILtS5!FEPSfFX!;<(fK)ZXUpiHkBiuu~yl-*vQyYC`~ zc7d)6X-;TaxcD2`sb+P}i&P~zSi%2B)E*$SzeIDXDJ3)1Gs1a%?D-b$cf(2S^Tfn$ zw!&<>~9({R;&d;q0YkS;PHd>iuCK1>WHEQq4HeHGnY;Da=l@bk7V}gI1{1Q zl5HGDMYwvOGkQ3j8ildGC${?#mZ#yEv&BJ3D9^y5U^#X0rOEx#RH(H&_{PQgk*LZb z+uA-&%wH(2ap%PQF=kHNFjK@}=n8AH)dlxckEYYXDg9{JZJ(h|J9E&Nfktm?VxlZ# zgM|r?$=0+f>?2xLcrC?x#mZcJ*#rQmEpy4ah&_yK8l zXW@iF22qq5WNJJ}WoaBy@8Dijk$0(08vpO2{hy-s?ey+p`HO9G5g}FQDWcY)P4IYu z-g1@XPWXDY@iEOFjrBVWC} zXHE~ZuaM=LzUf~0C$$l;h&gyu8v4kdfe9kuTa8^ESJGXJ+rEo*w^~lsXEYnB39J;+g`LW-#J+gNC08+HPq<%RD0+$vy<0J4jg`XBYZMatIjPV$fcg z_WtVoNlgM!w(QLd{;{@jXgHEJeNaxfc2>`{DmU*$ZTtgXiJ)ecN#DqxtwF$Ze?D*L zVE%(Vfe(!}mfcxUjy#FSw&$>T%bW4}$VN}=gn+-eX!W(&;l%Xu+CUeWN@L+c;z@ui z!LyB;iRooOw-(oquFq_kip})>WAy27^Qj-%RclgHw-x1McR-_-{oC4pne?(jr-{w4 z$?^w5w&+jw;y9F(trf|n+Vy{4@9`p3pWqWMpFyb{+>`dJZ?0(+`kv^M#~Qt(6)jeR zQ={qGV7v@@lj1LQMV}wA-_(IAlEq;vTjXaqzHd;>u*LMI#BFwEk=&w}DR{>xAAsC& zTAwaPqC-wbli%dvd2HiXoUeLZ^0v(WmFEw&BHqkOb1=0S-@c` zw9`fs9EYEfzcZ$lUNC!LH)=q#Q z1XH(!X0rO9`W;8uyhSHXr`HGVy(_neEwi@%^_Ni}*W&5QWd*K5$lnOl|CNp_e7o(Rj5A4U zR1UX%V8R9Yo@x@ zms1;639cws`;}XWw|+xhSo1$xfSBlUz6G%3SHO#N3+i2E%9QgRz5CcWi9GeoX}F~= zYeG7Ib|lA=4XSrh-BI9`ZTTqak+edNJ8}2?&JvHeJ&fw3+d(>;!<&6!#SXM)<8w5g z-g7)o_F=FDC1GZgQ7!KmQL5Ou$jY_RLV4LVEM_#r62qbKNGi3{9$P21d2vZ#Ai#pt z#*=fzBYV%bzEM+uc863`cXFBB=cimcH-v=z2gl8s-{=J(@YfyoQY!vSAYJk5>~IEt zNSYzT;$y1k%e9kxIj!lhG&R1>V_f;e2L*e>6(bkadDGb4UVyFd2~GubvTDw$b_@$b z3RiUv0NEwJ89eiO@%?swAF6pjn7WHLK?~THpqd2p`Qq!NIj6taUd_Ybi-F~-a_SW| z$*B^J^vGw5#~)#-%e|E;b5lH=Xo^>Ib>Gq-gW8BZRkIJm9Clg);Qy00#Il?lO&&`a zdBX;V;HNcOkuwtlGtLZr6cAS86w1e7xQ~b{`Ns~ucl8?OA7`~0GVIN?ECeR_Mx6EF zEV)&7kM}yqAmyptEAa#K&cj8FIR#WO4jz^t*YrZ7vIfgb(MO&yFjy-EAxWAk?DXWL z1XTGW)|)x>!RhP`&~3xlt~Hb@6Zh~x*Xo(l2n3Ks+=Ns<^GwPr+8H%_`<<*U7o3f~ zRm|}3(`%fu>#b0N=LcC7#*FUr$y3sz%oU%ZV(Yw$9ZD=ny2+5k^4CK3QS*_^ud-I; zOSprUZUArsT%~bA>-{DHRR#qyUX)ykLHF(~duG*8r{Z;8PB*te-1P_Yf;x@r%k$9X zme%Bhoh??pIw_=^o*rdM@zoC~zPIGBK0B1V>WSLNtFnV7^B3b2f6VcZQpUmgxcbBM zLnHHSek^gKT)i{lGlr8;N*3D*1@Q6GXg?n7G(@XE8Z@3AJz}e?BqCFd9{^-fPBUjP z;831i_~o>~NkzOWz1;ltkocG!R}%E&IVV$fu%$X*55UbiPdgCDM)vFxo1 zeCF69`{Qt;b{MRh#P@EVV`>oa#n0foBQM?R<)~1 zRlBw_*yjk_!`OEc-5`}c-aAaH1@6YO_fiwEx9vq&6n@eai93Gw`{eQ{MmqhIt8`x4 zjAIbuqlV1R&G|q3=C*d%I92VGmP_ql8Ogsw#R{tuL7CV}nesJK#mZQAv;rSLa9Cq^ zr}yvpEw3bY(6Tzgj}9vZzuy4XI$$P_prZskOW`{#%~$vIw)(!_#Y3{s`{9~(8?oP0#>Pf6`N7#kubMy!hayRP zVJXm*9|%(J6sX1^Vdc1xRweeN3u!Q`y&dclm)GFU!;}Ff5(jb9-{7>zr*d+iVHb|9 zqcGYFAY$1tTbQ~es%~pIMpoAHen=Z4!6HkB$Jn z_VtkQ)27APpqGBfx4jUwm9Y;>xGICXUZo?jStlG2TC%nj-07f8WLrL_1K)xy_NC#` z#+p-hOo3m6S;KTLElr}9miT2FcAI|-@vvgBzi1!U_J}zp)Tbgp;*H)${ShJ`)7Vw@ zDb5N3@S5pZz7g`uF-9|e^m@xba(QTTbaks;oO@UR%#VvzQf{rCHKsr~1#a~zr?7KMEVQAw(oQldg?E?2^y*ZJ2+GS+^&%ni$SX@b7 z_ftmcJC`;SnLpCT%cSUhpYq)lH;8VQ=UBaEg?y{~)^Ara+cb)Of<*82z=W~zaNi=CeP(hLHaNSK^ z1j^d9Ho=K)4#&69s!U4}bm>C%+4iQgD8X`uomH_%%mwgpJrG~*`1icnzw;u$??_MD zaG#>ZA=X=ZS1QRd(GT=|5+w)3{!jY!-?V-GZlDts$DwO6m~8m;i~MLnIhiEn z7|K2?Hlcly@gHFE|MT$6I?lZduau2crJu(QBjvpCZMk>ot5Uns)TZ25(o^X3j6727LssF;6|F2*5V?q*u zwRTq{?Ts{-fEuX;v^hPysQ+>3oGwyjF~K2c@A>z$7+FBk6$}@?NZwDF7dg|?2Q--fhm8B5e@x&Ar#hAl zE{S?o^tbpYpdgRh_?bw0md`hMWaMvqCEXVd?~W4UEt0rjLZr~q(MKnRg`$lVfqGu> zP6en=njAu2-ITgvToDLLdG6q|Rh$z-r(0xdI<8fdIVrKTk&BiEq3ruc#}CudJPXeX zL2JsvWe&xdh$hcu*Fv7n?sEf?C&fIn&5fVQuCsaWLY$~Mf4s6}JmtdQx}0%(FFFJ; z@&oG($#N+>dPC6g_PfNy?&o<)tdPYA`Y}w;`&D=T?$}&pw`Bja8p49F5&w8}?s{ln zRiw>LU1jvmd`U7CZMW)lQu11qTaMDv5a_Oycguy!Xsp#+H9S-aBx-|RviiDQPGb<{ zQvcO`c3cvY$X1*Rkum5X62e@f1FQe{%=P0z`h~!|p1~RnXc;?y=^Fawqz9xd?%=g{ zr*NP6G?um6?NR`9@yZArs`xGaB-2s4%B=6jX8DbPZ1M2h4n1q%@-!EY|3K(?-!{19 zU|co8)Po|q=l@lm+hxp_e!@W5rEF-h+EbC>qyW}r?`N6cN0_6^^Hu7#tGv|PMPKl^ z+|eyr_n36B?ya5%adVe21p1uS;pgUm(}NsT3}Om9P~9`%`xz({HT|8Ml3{u0R8iQa z!klz!O3w)l2t#MP!WpRY8Cvms86971gVbYTYy|vli;_Pf$aD&$Gn#kVyC>EF`gGDq zNXD1BbP`Z6Q~7{gpMnogvSxxbL0jFxHOD*9YhOpZ&^T0{ayRv;EyW=w3y6xRN)PgW zWCszaLh{v^5xc&g>|jO$wGrp+eXTF9RulnOf9a?~`Q7Tip8zv@Q@%*-(3qYnpDdt+{v`c6>KDB9dZP&6(PtK9oo%A)LE-&i5S?Xfv2{KA zxJe~Us4Gx;l6W1y^1ln(-x3SPqz?m^uO$sebIFRqYf$9o4aM7hZ%D5FI?+I2Ae@Y* z+<_+gR>Ik)j$Q_1j?&3Wl+EPcM36Y1!&Z9V5lSYT#h3V5bj^&6W@LBGxD=OW^&3rS zEWZ1rgR$hWX1tdE?NW>pta5-cRMIgz=MhuGKpsuQYUhj#-Lh25STI-gIl#JYTNwL2 zgMs^FZ2XI`KHe4nUOZ;Oz%w>_@4zWe8#^wC3Dct?L#>hMG;MqQ4v@+DbP#b=`e1Tp zbpe?>ihr?OhHmcUFo^?bsbKozf7R-9%1dQcf1i4UGt#KN6Nw9bjH8X?DdW`n13)ZZ ztGU_8*Cvc+^7y3bXTQ^X0BQpNj^G&aeYqqK)uwyY#{c&47fp?cw(X3v+w?In^p$YM zO?=j1=Y*eH%P?Ln-fDdQL%dA#gc^<3uPgGUI^i_TD2{qio}B?WXzi*zEp|{OhUrzP zsnXnm1c56oR=Xy%Nq&JfiUjBXCLCHPRetj^brikOsx52e8;2gNd)66d*lku*vw%?&~ zFsa975b^dKrO;lS_~|tAG5_Rfsh*@BflJy%Yg&3q6NPl3mJ_dq-j3*)fN**~s$xm2 zZ}0Y~X<3tR?kRQg+VU`z91KkFGtVcD)b@)sO(}TL7wB!D>Dv_?-%S&uW_I;8@U+oq zfG+ZG9%FW0n+i`F7|J;5#T0-9j~?WFJicum1vXSs+wXcs)OG2|-1>IKxv|p_?nje+ zL`@a~RS^4hAM7|$-1BK`2sK(M+q7M9n@Uk&HI4FmWild9;b0Wh?^;^!g)8PT|40dK zefLmr%fz%a^MG1DHK76n2aCsfoHvRcKzh_=gwj63en?XnC0J(1`oG}nOeG?u`EgEysZg%7izw3Ekq%w|1OnrI@ng}%$nf62K!v6Z!ACXNrI4p(S^xk1hxkLLma`@>JcS29X$V*Ez|BvvWK4t+eGb4FJLK8Te2ssWjYLAhu#Dy0 zpQ5T=Piklc|NS|(V&Rw9ows9N*MT&86IKBA_*YF(WGVi#_m|kc;X^1W9 zJoMx63qej3_@`VOA&R?~3^?0V(+ATWo($mB#ZD1(Fwn96bm@wIgXMgLEgVw%fT8E( z#z>U_pHLDX%s=LQb4WiM*qO;`K%vRW+EE%mTw;QU!C8i9C3KGPSV*(E`W0R{Pkg; z@*NV~6M0fizT9oIDc5d{lxODBajZATq%Sm2Z}7WrUv9Gm&TfKiO@4^s&sAmS6chwT z=ON-|;EAXh&`xRC?FN6x7`y|bgLt=!!*i;kFep`^&PMTZI1uZFtnF_BpdY`QZSK7I z|E4mYB(O*lKQeUYYuvGVnilsl zV$$@-Es(0%Kn2PV=O_46u1Ci8;!D!u`R?|frG-`iaYaSNu|qA=@Qx_BYr1=t(54t4 zKd{B+T}b%?!NW0~&E*G{;@&RXcO@8_)zEF$^nszeO@m&AwXqHM$BO&~m57*brE7pE&W1SN)IZHa{?1;K4ghb3cNBs`5|W|ajMF2YCh3%#E| zjIDNwV?qil?LWD>)v;22Tz`clnF=}np<(Nt7DX?Y?_pyaA44pjZdz1VT@Z}HsJ{LA z!{&>HQk9Z8;liCR<38+s*V$z4OC07asncl$Jqn`K7TU*HJlwNR~iK!rXYRv+ajC znYG_ffV+FYxYw=3qqF5ZT3_YG!hfgg*^Ed*@-`N8x0tOwtSE}Qdp0t~{BE&P^!;&+ zUq*qa*6#A;9kpRoApKmony_%%^J%^J;;8Y9hXAGX2wDV_fWd3yJghlk!Y z((LJq#FPqo329iqg2V1Du#5)jT7*2g=>MX;qXWC+4SU%Z${u1|eWo%63sx9~>0XC- zpxvUf`urby%?H%k&Y1%3Ar&VM&aU=cHSf7bTw7+Q-n!?{JsSSH!j9`H%8oGU=-_Gb zkM|JhGNKjew)7AME9j*1zPAAc4RnG`>-ZlkOvsL^s zckNl{+f`EIcMBFWR2v>tg#IO_#dbnN?Kcr`(eEr;dEx8}83aCQ`gBFCMJ}CC|D0KG zEZl9N>EQx-F};)q{vpfhT4eHAaXvPU!PA%5rm$$8dZr%V8byk_&Vm~>A8Rq52rpN@ zGIAiR+2mCbyeRcPrHB*8jtX+r=yryZl1(gYQQe3x(aCR(#NN=_6*Dk=us7=?{R*>G z7a`nSY%7sbn5H>bzTo}~k@&T9Y46M5*5cUTv|Y)*61PsEN`>M;xHx6MxD4QcD$a@B zg70LJrJp4M4d3l57_)`O{eL2dA2QN3QQP3HIb|gL5$ire=GY=TbDi<;I5XaBS;fiY zG}(!OlqRP;6k=D`a|uZ}!rDKam&WG*z?Oz4G*cQGZqvc&|qVIXHu>|k{KI8&?wxY5DyRE% zjFyoly6cu-(Q$sez9$9&L@MBr7cKQ20mkxSP{D7ND3-C*a};$#ZVB#4*>`;7Ey z8f-$X(|Y@NVp;!7q|K`CnhtUaDvnH1{fk%~Y4oj1(uRlqU`C8nJET2->3O1^A+lMF zNwCi&Ejb_)$x2?b=9fI>u#$6i2_MY?G4(WJw&WZ%zjb$mr>Hd&YH{!xP2M;SdL3i- zPE3<4=+O9YQt(d|FNM>1emhc5FHil@E~>}mfEc&LsD0Ccn$V7Nf5{-zqCG|xM9p>C8Cw3f!g1x2Xl|W~{0W0#Y zS>lbdJA)i0RL6S2YJ5KtFh!)*<&f9ehyAF5U`uMmH=09^Oj_udtXJXdpA*}~+5Un+ z-TCVW%r{A%r>^PFEpXaeTGT&x$M?l3RSZ1Wo=bTk-!s~2}AaxEzkyTtJ zsDLI$tK(L^M6#s4CEuUu1u6u;?<>*+jQD(^D*PclPg;eSd3ElSTNs{OuqJccZ(rBqcA9!kNiVm z9wkMZ*t`)!GU0lWETYtOW2$DmfIE=MHaD-$|BZe%L$0!bj$LI|pq$OV3jTdn@uNIs zy>7}|e)cBcTGqd4t~zV!=c1Nx1$2wdJ~v-X@qesVZ`&NsfY4I3rkQdWCSL(M9!Jb7N@NlKy=v*O9lBo z>w8wbudJ^xcaM73x}%Oq$3~jze*<_K?1Tn_zt^-4gk!Z{%xeC<-VwIaPyQxRobGR4 zw%~QnxoE@Ql9Iv|s$SJP{`zpnzwB!XV@mkxAjrH%0FEqTx90R5bJdGU(~Bu+;>d98 z5_rOu58$h~6UsN1`>MR#Hq+jV$!r4L8(5KY*_>uP_BkPtG-M!cA3#^s#TU2&-4rB7 z6Dk}S84m4|S&*dxE>XA*^+#H}KOcYO_cpyM7H|!vmxV*$umM2PIlXw92?Z1fN(JDn zOc<6@c)d<29Lb;2ULAYtldSpJ-J2}SJx$g z6;R4}O5X?2PmU$tjdGPOdz3iJ5Ujev#$9Hf8UPymWq_lLQ@THMj@D9a(Gox_kYDoOdHx_2edys^+*8xV*xS$DFkDw|&5VT+yE+!fSNRE$N8< zacjrq)p2zGx@_DVlslih^qL(IT6qyE3jBZypK1l2O)H~|r(O~Pa zY>9I6_-BOXSHP0}#q84AWy4)xtg3_K=C!qsfza~zbeMr^t20cY$30=_#Tm$H1h2a^ z;a0tGTY`qPsJz|vlA^Uby}8XniVK_diqx>7Dz}#BJ+ZZ0Kwt!Sh`(xy@X}BL{#n|T z@BNsx&YXJe&YHO*wW1&`JKlotC82%B$%{~y!&^JlX&6%2P4|uUNod=b2>p{@9d6br zNpxIQu=B})pUauy+T{@B4xrdAHjuqnO!x!Cna+mw4OISpmB)O)dG@-#_j(`Dq2Dps zVyC|`O)$M0gehma;qP%@UYFnj0r-saOKPyM;Y5eFy5&|q2u8U^GktCpFw`hFO#(- zn1+_LNYhh)m%LNc5h{$o*26J5o}S!68k=v%w8u`grD|3QC7tR=6aHAr^IhG&8Noa@ zK<}sMGl53Lw?@lIS&tv8GPTED4fiVF5}cCN6_(QNg%Q6In5W!%nVO{k1#L-8jON9@ zWH|Nxn?92;MGFpY5|^M-jl~rErKlOHW7im4^&?p)vGpWokM5U|U z{tFMUn)k=YQHp~iA=jP$zalmQ(Zd>6_71TXW!%5;N7D52@W5t4N{*vX`L4sDvkzea z%zSawj@5f==|=v^n@976vI0NFy`TTiqEJ6S3t(Jv?$U&nyH=oJS21Xz8vF zvy&qf8Z3;$r5%+fRd(Qgr{H^gpx4(f8c1r+5{O8thq)V@ReXlfa3_AUfb3(!6&Ml$ zK%wHNJbv$^b@no`H8>|){JTY+ zd2E&h)dfaTs*T9}ym0T8wswb~*Z zARx#Zk%H|X|IrhGx_)4dl~qI?L;jwKD79}S;$5Am(b)Kd{=>@F%hR)9{XNiAt8csq zMmO$k;f2bV>-F>?tRqSwddx(}Pf=FLdDSGl-6yfq@{a`}gZbT`KwCq_4-l?9s==uY z5{H9BYpDLMzju;d@zpiUV;49Y3`$BPGB1?;Peq-LiFE%6$70mk87d{GQKzPb0$;7ZAiWcWS z&$RP$0Jm(8TsG2RyoW-ESll)Cdu~7gDy2$dr%0XnM_4kMM(q!u5%=T&{(MJ72|j>; zU|`_cW#1Y5=MDmNE5QdltzsWsgZ7&#w2JbWO?)N1xkx(coUB<6U;nKp77HARw4c22LvUeTadGB2A~7>;E$);;_QzoC|EI67ev2~fx>b=96a*>uIE{M z-|OD@UV9zG=fVN_$L|!c-F$`SnuUUNm|)k_b9GhLxR0azMm1T~E;@IQ?)OJT?|l)9 zj@+f6@)pydge_Gp-4;B8UqByDuXa;!417#bb^l4K?N2aB*O)>>`F<9Kgz$9$=hV#fi1Mg{c!xT|InJpVN&8A<6H@qIpK{<+_ z^=8NK0iIRme|p-4gi;;2jV-=@Etevk7#z(wm>nHc4Ma9aS!V>oA9lQ$;0C?xWYvsb3wJE*0M4e7vgSS(TNA6Op}*DDMspHRq_m>>fp# z<%W19wrz73R!dB`8rgyA=(^{W2_(DSYq(sm&9iH$?f0_DX=HN$E!NjJ_>&%idwLyR zP3q6%hY~73V^%c;JaL1;z>@FPJ1S9ITg$;eM?dwY*%$7$@}B*|XVLS@#eOqkkR}(@ z@V3s2F^@lzcg?7~8SpoO9BnSIS>2d5+i|waTdNFJd$U!;I(+ae&=ze~zr7X;D|nZT z>#JUy8^iAO!6M8(nJE>@zOwO)Eo%HOU0lg83*BNzZPFWrD|8`{E+Xm3_=l+0TYP|S z>EYA4zY(HLkVil;6Qf7T5=XsiUc0-JE)!#o#krHz>6LAZ$ACRoX8+DOH0s2wVY!gt z>d+2($DcoOqrgY!#$(9$cPx^(HZb|7ltSG9Ep~*PKIz>Tru+8E(e{YN*dGf0ekHoSalt1~P3t(`6owS*9Vwy-aE-w0M3Hy;X{~Cq5fNWd5p(bf( zN4M7>Yx7oluWLJwQh_`lAMkhcEPMJGlnZrM`@csrEU;JS_ZTn=3Z*2?kVkfR$IW9a z@k%pDO&fQ&_$Dr%(2^7X?bx<~F#;7VIKs!rXCe+HQKuc`8s^PPre~xR`q_IX6?J95 zS&1A9!f4FJz+_GSyy~;B>OIsWqZ#0~PKHQBsmRMRa|>ZnZsbkB)xdPy)8VkyPAjS( zHkNL|WHg`2)6O_eGqDcWLkY!WMpIQRLH2~GSioOQ=_3(cJ6|QH`I8nh@|Neks1sDXp)FI31!df?rt`YeOT#%Vv)(ORp8L`6 zF|9T{$^{rSg*@8Hu)RcKokr3^>ZFw@w61MXd=Ks4OX;d?^*JiUmR>p~EGEjZ z_3Woh1m*1nc;DOR&*CMzh}}lO^a;fk?mtd{)jB+Tnnw=?$?w%-(KR5Ui+vnGgg=v1=rosxS>2Z47i$t0|K%3`yh=))t zgu$w3orPtIMK&REM+fVb<#9*QI+!VZo-uNrktsegNzpSGh{eR5kSx+ckAW38i#@>i zzhE#*&hsTI8b)R&05oHXw>xDm{|; z1(e@tsX%h^PKrD3FZ_!GhfpI~BSm~I%ccCH8j(RtQ^?L34+}xp*AL{G z?q}rvZC|d&Z}TolT4d*v%{&^N&z%9#6U;qK+1cI{sSgf`qZ^Co-)dj6)Dpmu$NSWEXa6$-J-O3vC&rPM`E0rGKY1V5RXZ zO2|DBw{W^oiy199t-n0Of5#vZ&PGQUH9Tk@6jIIh`swAZCcuA^_^opT* z9{T3kXTe^m+lQF$fz6&&v-Pf>OWmqty%eq=Hq-qeniUz*K!HZ^5?|)$Nl#`nv+| z^hfY?c?Br1c(hekaoNVj48HCwfwWuA)Wz(EYgIaUY*k%!dD(?tz}|T18%p*W^focw z_eCxv5>~U#222O*GbZK^A8Mwh4;)9~m*Nlgf716A!%VB>^7lET*;PjMjb-%a5Npb|~KDL-Z&5p;pN7i?@IX zZ5A-(`ld1haD&$+Yt5d8tIGMy!(M9d#t=)_T(%nK#`x|ND|V5Nb3sioUSY9OjzsvL z1-8cWUR0^b@i}>aNdn*E55rEoyrBZ7;fZV8U7VC|?D5fmG@S#9{bMQ@D%pcgv!E;K zQSLQb804hBaoETGDdo-W z!eDN6Tzrwygvq>wEHXR#@3lk`}wz`YWMv&QkheAZ+uMysDJ_N^BX5w^Uiofg4`GZrM_&B z#=N=HUprb_6ZQF+98FrF}MX2jh~5hMr`qk?%~?cfsAbUX?si4237)Z{fl$ zhP&RD-S4b{-m47L>Mb{y5RFco#j=dPR2byKmoUwsJdd?0ZX#Jn(}!uFTsoSdC^nB% zIN>8dlx9TOu5?CEBxB721m9UK$r?1A=&j;<|FyI+_dRvzh!lYY) znYc3YiZY|)qqGP2RicBrTV29tI2DcPw+UG{sB$a|i&$zYo`M#?J&m*;SkbNVPs|{xJuX$A#OZMtI0A3MDz`!#9g z9SH((E8jG?`r*24S>``Qkwfx0#nVPQ*=;t9F#KP_6#U*ixlt)h+_4%yK2b?b!ekbX zTnxhrvMw>e2v^r_)faBAggqD8cTv|FnV@R0E9(de@PW(NZ{0NQM>OCs3>I%S^HZi@ zlgEZIw|^=}BqjRBdZ{w+cO}>>^Q8Oi1hy$r;JSW7<0-gje%ey58sP@; zsGFHIH?^pUhFc+#M$tY#X+67VFlT=DU6xnMn_It2ZUK?Wvn?vi*y*| z7Sx2umGykHlaOS8KB=&Q`|jCKB(FQ!?0={A5qy&gX%zbeVb;>Q69^qI^}@woHTs?cN$-(KN3YS9 z`&wmU?|b5qhu#_*&0`RR{U`GWn^)>w`Ex~fInLJB%nau@Ts02-g#O29p%gx~(a2sw z-t{9=d}3Ruk}tM&an(CARRl$J6rVT~LydF+aKw0l>+Qic_Fxl6WHo1{l6{}&kNh2h zg4%BaweLZoR46Ma=hz2>pY|9@p4Kmhd8{bNKZ%TqVw0z>3bX??tux@@{kD$JVz#wW$~A=a557BxdfB~x&A=#V|_6~o6) z)Idfyf}4%x1&N92Q7x8NgayT*B4oIL-8o>WX|}dwPmOpha^m|WlU71t0z|L3DWyGA z1qktNr2+Yf)=};zoH|iUiYG9H?KTQIXH36!B?(T5s&h!I9KnYw!qSh7n|?e}i3Bmp zGPlo)Du9oEtO&;tUC1k3T}~~QAuB=!OeGh){yM1of9eUFM}abxfC+PE8{P!jBluz7Y8OJLp06ZS=jTOqYn~S#8@2qgItb|}?_F&W zfSQ`0AJW!{ak>TC8gQ*$SOsjAta`hajaEE|K5&d;KKS{h;Zg8XecWPKN@<8o$b#>W ziAnEhoKvY=K^cyyT~8C}7K$KCv_5jrfKC5eoXlhT&ct5*Her?NgOzPTZa7>12!IoG zw6z786C-!-?vrqisD8xUQ}kr*NMcmvQAI^=k{Z7e)S;Hxp;_xmF+cfNoo*B^$o*~5 zQX2XYmdsm0S}=~>UWFxomarbvs#vVV(-|!>4oQ%=ILKOUBkoCaJv*BcKz&db1(s}m zuRJUtdXczUZnXx35w4TB2?P47UWPa)YU_#c(PIDSwbPRlnsZa3svkJ&g`S@ONx({Sa)8PJy+C;E%^8^* zW>81@_xFqc5GtvgCW5g>Y8+E3aECVs$#WIO>hqPG$%ERv8hc2t{xXT{DDdTuH#sAx5dcv@A#dd4)1mhv^%i;^D8h7W^%wGbm7&rYtkJ|Kb z{&z8%s1?BI57v&KOwEHBGApR3ZSI@&M(HagelMd9C0QA_l(=SgQG%34RluBR8r9Fr z3y`oTvtgge{Mi9AYhxqnLKl~%5>+v3!$fPz(yv^LO9pCTyEkQV%}&vE%3NK=2-*4{ zdM%z@`8(@6dK!AVFTLEs{v2@uw=>}aNBIz$jLb%t6^SM2(B{Xk5eUdhH3L>fJ}kjI zH((#Jsm{^Yk5RAo5-Nmh<-n70w&V^Y3H}Kh$wTEkoNCAgsv!KYa3FiCMy4X8!t%X7 z`!@7CFSVo)Su`p|gY$Pm8UC(}i1|)RvZ6+VG{rXkSz;f}bE!XMi*z!V#@M^yRGGDE z-3q7DEp$jB9Az@NFQZN{WlK)FKIDDvXd}tUujabhkiGyhX`S9JEVFH%-g9gP_z_!$ z{@i+bzCZc1GF}`OS+EMb_AIisGS1A%7aV0uD6B7GLQU#?d|IWV zyICKHc$%W*PWWtn4p-lJg_Ue+w_3JmN`x$)cu#EuoEN7y_@~U);yZi{Iqa+ouA@PC zEz1VW!h5nZ<{BX-5LLrk5BnQ{?jop3%+5-~`@mA0$65fTZ1FJS`J0VHB||pZ>#FUi zg|P)_WzUQf7uk^md&x>*Z6QP%L|!+GgQc!c@XV1!mxDo<<1c&jABx>W>yIDED!3>x zjE$dvg_YtxJrER(P4e_wOBnlBYWV)XBLC@zI47z0nIYi!_TIkSw>%i}({sO^fY{{ge?!vBC-R+r=d0W-}p{jm;~+o4W&>1bzGVYo`k{?X_2)hBzH zJ8ymm(gzWk5<%-vEFnxU=avnGff;MO+VyT;k533_!eFH^oZywGB zfrw1(q=VUvpYtFkcpa27673q7EY>7FdbEpO2^h5yvYy!7vBDFyzvw z>2mfvxiZIeon^@Nv2Au~SXslFY@1Wb&7b!#C$+zSRkqpz`xY|-Faq_g&PpCe`#}d1 zA^g9bVCW2=;h&6Jl;bloYMNBi!Ha!wGO$03rMR~?j~tDNq7pZS+I%`Yjcl`)3Pj1F zBW0VO$h5*Tt3{(f-H+MT{oD$xFRHTzP7$8IDZOs|l_o9y+|#;O-^~4-xGIk$lY3Ne z&t)0l!8`>#<~b|AAhzsb)^@${{79P%%PCj5U}vnZmEYqpFYUL1w_f2bT^>@;B};vi z5t)o|6lQI<%@#+ZH9$;~AX)`=Q=7g)EI%TY=`*Dht6JA^XH7$$bu#q%T0+{;c;%7Q zAo+mw#Cst{AhHp^=ZF7o%+Q^$M|w`Nt91KdU{+4D$qPq+Q6iS|4@)~I$Ck5P(8E(8 z9f600g4{0-K2#ROVB+G5Bufg+_GlCJU&N#P9plHrU47T6?$p)!4dz3Y)ad1w%Gp80iIWAcLCkz14^-EK zSncb5WoRHC5;%j^CG-yYuf1(nlOw8EQVLuM819$uRpfi9gZ&^xty)+oHFPm z>!vqGDfg&d`aND=UJ&629S}MYIeZ)<@hEZqcrqB>Q_draoX}BLPhysa@9|CrtS0F zt>QS$)BG$fn{k;^W8-lQ)Z@npiZ4d%xOoX@4jCnfUJ;CXO|QXqzhYym;qdMcuy!u2 ztf&4>riw-#6;CpeA*RjOC`~xf1dXN*`Thfyip(^Dt_kXvmQ zQmN|UqNl{{6SU#jfS}Up+V~Z)h}4#cvFD-RWEj#*DJ&lufXr`-WD#TMu|-n+-ZISn z97{vO-^vLQ zfc%OLhXmS+2~zmY&}R0(riF5Kf-P3!%~+;iUJJYs#UZ!%cWea7W*A;?Vp3`ixC9Wy zs^(umsTeWK_DpNklOrPCppuZYm>`$V<{8KrrO%w&70OQE-?UE{35+?wk}O@Dg$v4J za@DEQ!-szHa-=8q<1D#I(Zz56)^~4GZIKWjzE^Pjt+9nup3OkasyN!ky8HTRzF64x zKO+R5>o^?QIdn1s%as z=2-^AP}q-Yd3Ym+Bm})z{Y|a^=Z62s{H#o!)Ag_BU-NXtMS?A}c<3Fs0zJWM-Pv*H z{|y$eQ*}F&?27&(*kUJ$hGjHMOy%<@q$dJaKmRi)?|Y#6dIQP=3_f{{)4|`iz7vl!@|viuPLfX_1~??Atp&U7r0zcOB&&#BTmL7>p+DYnzou3c1?ADU-X8t3m8KD z394)t#N(}v@tcix{Jo(m3en#tL5B#9{e{v#ah|@TEra#s;)U5sORMpOVnV+j!G~lY z76R%aJm2TjDID--#(ie8(ev6G16HF}hVaOt?!|`w>4SeFd~35zl9rFSN^X-hHHa6^ zWIe=r6;m7JO@DXh5rP3AL|J5B^ZuJ7N~+DgWOMYqM&ih#`ifNb=u5kKSdX&X_k7V} z90-WpX&9NVigV&B_wQ1-_(XFRE_mH9(7Gw*l6_@H3$3thD-J{IjI=*_f~l<}C!~{ePz;8GwX;zxTwbf5mO4&B(E5T3;g{#3W{w zp7u=we}cv=I26~$Xf`CQcw?f}0s=dGTaJL8Q@#Ps)7`BKmo+H=RYJwndf%9hPm8=2 zDqN@OW-PQ^s=umxhm|iymYi!*avLV@Vza=jUj?Ex#oW0vzEEOI367hk6oI{5C3VjA z)ouyyoJlRZ;Er(raW<*}fVoVB!gApIAvVWlwbHNZ4gC;fCvWHYURdH0m*do_MJp*y z$((wwn#W)1zQ2OlzvE3T2Tv~&?B>)nJa7dl0TR6H>npqVfsFT8^tP8w9~n2RzP$fL z!IrLKIPX7bwbgc_a-n=rpfma)<+z<_jUT>bfj;b6wsuU^Ve?qOS#fY&$tZpyTSdnA z)TeGERLRZeWNHv_CklZ5PhgH<<-27R^)-nIkA7=vqOO(_?z@=>G>qI-3yJ^TjiTk? zpD0sNcMI^%u)+jQOaRcV6X4tWyvxgYzI328rP{cJ)0FcvYdSKdm~BK=)kXI!zm^t` zO`w)^&Z*kK_2iw*T*=gHK=O&*pzhuryUw1DR^39beX;3VFiv`QPP!Q|2yhA3g;;}s z=xD+{&ZXiZFsVZDnJwL(<;0>0s_Hd`g2n^yBERV0wJ@#z*W)P|G#}{cbJ13en`~h} zF6)J1HX=Qe4#pBk`_}iLB$Uh_v*j|vye&rHr-h`XFFgQn4X*Q%J)i5aMcWjJsV`Dk z-BFnHy!#uW3teA}f~iDF5@Sls!@^X~0hZ6fg0E^2fI9JO)>JAksimck`3FhH0#diO zfqu;&zFEo`dhiAR+@&r_tK09TGNncuMn_9W8gp4Ogm55=ol~}J>*IK=36YK2kadqPL|)w7}-a-yN~VT zVt8HnTp#9#Rf?$q-j;}b7SMY^&iu@KV{6*Ap=TtlY&9buuW0Uie#h*vq(33=RhV3c ztV9tQar%k_t`SbvFVb}_pXchI5Y+PuI~EC_H%(^1Jc)N04x}1!NO>y7D>O8!@JCPG}hA5Yx}a_wFkq@%Hk6mzv@ zLHNgImsnRc8Tscc)k!ln%=TSR<==BASi58yaK~O;9CuyP?)Y#=W|K0Ft4n1Nknm6GO{?C1P`O zmSLWzp@a8_Q%=sh4oKV%F+Vj--1>?JTHITsPW6Mietx}b8FgZ>N2#|5MDFQ3R3G>E zCxr^^^$&^-XAO+N?mZXTW`l!(77Rsrm#&I&2k#M7Y@?zLVC+USr!Ed^67uG3j7L+U zz}R*>KmXZpc)Yo*dAvDa+&2fV z#0sAK2QTX3S2zCbx!=m8#;s8wuh@8a#l|Hir%u$S{_JOOz4g{BTj0Mu^q=p>|BnCO zMMFy@XqLC$dhx}d{js+6#Qmn1-jd|)$;(SKp($T_lk$j}+%p$PPF2qQq8DzN`GfsL z@A!ZCibh+MKz);ln@r@?5#NLRv->}dA^c`TM}fh$JW-Jmqo-^p@`jG|KBRqj_`aca zX9@;(5W}H5s#5&>l9-FW*p$&C!tRxXzIKp)we1CWhlN}x^;Z~1n#r$IiMdSDqbaUf z%-bfBt2^r6pT!Mez=2AUzW1Po>eP}YzMEMh_rn=eR~D_mXisB;X~bYVGb!mAIZq69 zXAdi?iU_(VjlN_t9yt_4T-t%(+>t!FUacXM2x=AKFBgPL#PmCYsZIg&PICb7?~(ey zN~7a@d=FROD})!0+INqdut8x@V^L3F)Ht?C)`!KU1&pS^B`tYEN481)BYbRyeOAzK=AN*ego^pYrGYXFeN;-;^09$Uyd1Nt&@7nP?FnHGA;P`X^v3AQ6u(FO z2cMD{Cfg|HsM9Oqy1Xq&L0aff361a-g^v^r|aW9mGKcxPNj zOKzw|hgnRa=jFFmfiG0p0!^bu8A!rz3!H`w*II0{NO}zK3=egw61$P6oZOUidyC|? zJ>g%!QeYqL<-c(xCjV?K{x%lU<(aw{cFe)460zb~Yoc7OuYTXYZS-i*@M(-p!)$t- z=Jy0HOHbP^4x^Mh&S!e##8ah~ZT?;zc||P$>ekQouB#oGMWxiK>#FP@_8JM&C?j2# z{I2BU`YUbArNPrZK1yo;bvm!hS1IuHifW!^6D?o zR68VMTO;njqGH}tQ{_6+CQcG(izd6pp@%FJ4av+qxUUqyx;D9=Pfr>X3rlwRb?yqS z@1w#iD$Lokdp28{XFwmuOX`}Q?xH0Y|J&LEdx5dJw9fzhM?O(|3r4E21Ybd)mP&Sh zC7k+0#=c_1rA<5O8#3k^T+?~akuf!%7^Ahw@rZQ%HH$B+?NO>xNZ&9qcRO%rxg%7r zrA89=g|Mk3DP*xM+53+~oYCWF`};e^sLq1_~zahMp+qsMgZq!aTrah9EG4@MKf2*K&mzR&*LYQmR;uA#d z=3EjswJpV4EZc6s+%uWnL!KoY!Cjc}P%Pc}nl|{FL)p?|@D<}Xb<|Bg`9qzTcDP5H z)5LSFP9YI&PjT>lABnwNEWSFa_eSqSINgkmr>9U0@ZevylP7e_WM8OQ7CJ2MF6{JC z{?tSG-r-O96M;nksMsHEeNN|pha47&`n?wNe6Gy(Rz<+%dPf^97cgISIUGiE88O25 zw_C_jKGvzW-Q$b5{M0nqAY;DonEIoN(o|5lO@)+{dSK^Rm){zTpG;IXO7P+I&68a+ zUt5yOYD-N%9y{dUlWBFf<@zpNAe*bFzHe|yu-^2pxz6i4|C5Q>-Da$%pSJ4uN~t}n z+-3poJ-yX8p`F?&%X^5Y^Z!DK*&a$6?w}`xGG(Y(bbQr=LPYI6ptiJr716iK=vOP7 zBxIY9zFMm6ED(L~4%I4SdJ_&M5+MoJX6~L_zsmU4s9_`#cd8kuovJ@c40dPl@0QY^ z3yeogEz~NpeLQ=Pd{9z&IaS%2T6kGV1EZ%Z2vnsLs^i#n*F zNdX!kOAX4HpE#`@SjcCc5c@S|88uEAe62ms-)Y7{#!8qZN`5m5zp}$q)<$(D6!zt% zMDLSO$4yr0U@$fL1F?L5UXS7Ej2T zvQSIO)+d(5yM@)ZU|c}uyx2sFQo79Xt>o|PkA-upL3&4lON}W&IzaqlcF}p zvs33>BM5v|Dr&b?5{;!9jR9%kLIrrN3bAj!{I(viEtMZTEh%hIe5O%}`zz97CPM8} z#gm2+GtvFaE}7@H#rkmVpNu3kN|-1!uh7jV(F9uze-$E;(<~VuiAB`og6KL+j0~sCh|gg zm_LLCq`9*k7PIQ8y@Ifu7vI z%Rx;{zH^)48xN09;-=7gI!Y6ALST+-CZdk-u=9r?VRPwKj0+s37!o;%q`*yUI*#b$_QmMCG7DY}a z60J$t!(9=DF^%hhCf*ss^@w%5)c2g2EH_nCiOg76x}o!J9zBuB{10n`W9l>M)LRw3 zVJ}i`;kYNikVdts@V6tu;gyWzV*e!{6|HFpG?AR~DPB&{E@1n#4qJ6ZAj{}XW2`aQ zRB}dek#2C7BVvR<6~095X`f$PGQQh33H_n zWfvClg9g65^C40Dq0G&mIb8+z?s`yCrPN(4Qsu_x1v(ztcV^TdyYo?t^+3TepZ-EX zz3#6S;>|v))ffCqmw&!pR4=8y+Bt@i%DTtuhb4vMrG%#-o0!rw?w&+|Bl`)uNX(O8 z_Q}t;^9)S|hK^R;nXJ$4ti!!A`Z@f3yHEZ$?~J0+C%-MA4dQ_pd|^*b?qGdL{aVal zWN{TMj%A9*H&-8<1r=%HAEKMiJZWgZbSj;XSsdh;MBI=&B+EaqDy+27ceIK=Y0vdh z<5Q~q+mbHwf`uL>6mxX`KWMZSOs8eprINbI=L5oA@|MhXOG__(ASO=)S^(&!ubH0w zMj8sH_4vnR3VnL@SlfBK^(oW3IXkl_bNX&f<%CL*b8lp|%|V4)J7eUJlW#B7%)#5^#jj5x3rdL=ZUP*=guA8%K80tI9%yLjO=6v(KUY z(X+&!_LEYoHN{_PoGceS;480dqOz6lZqd!tX$4Pi^?Z=Nnb%QfoKN@aWcCeRUZueM zoP)k4p7hm&r9Ivi9H>?NB?;?ow2U{3Z56Wqnr^aBb)c4}H`aoT1`>Mi=VMJ%WD9cj zhOq0B5qHz5p*;F)71ox%wJ|q@qPIq8COk3BgVy(pQ;yqn9OZer#15H3V}I9vL}q^> zXS`I|mTCBD{b`Hmpp@<)eW7}3p! zBN&;4jeihR=dH9fZPy!`Q|r9DvY9qh;G)Gcc#hs~2{lUJ_I0E<8pSSUiY=Y~W4R{T&c%eoxSM0_mP(Qiw{i_&@VDLMDbA`DyR4r|3Qwli3uwQoyWzZu%ELl!pQI-DE!DjJ=zQLK zdPEj{(%Iw)O%O>|tnp=|BZj#@KKP<;@29a7DD38u&!qGw;UlSpry?b|QXWOS^~`@* zw}2e5$?)~ahf>SvTl>Uh5i$2n4gKOiF=dplkEypPEhsj0Id8^9oBX|w&<@^2=(Z#D ze8$g&p<4paJ3O+1Pma`y>ep)aCh&apB^488va}eztLCt)RibN|b*)K8hq>^QuBT-- z-&McWv>)uCohE;ATF77tTu#F*QnR7=uR`jBmy=tPnBc**i|;m_jb%Pi?qk~RHHUv6dQ`S>HKFM?mzH8B3#7= zkFIcxkJ}TJBM(`oPG?XzZi&f06G`@a5ri^?N}|fvV~@}yc6>-8D?FVl9(h={!S$gd z^nG3MZLJT2@ZwrsuuA4Um-(O;ay;)2Cg+QSfr2_qoWL&4X^q2ftBgNn-XlV-;<@q* z9oT|+>s^Wb0stbu<+_%(NpWY3adMNPxuBbjvE+u3VaPnmBK?jYXL80=F#xSVk+9Gr zwn`z3q+gc0_z-p!00>+{!&13o;mSB_EzieOYHoo#ReSW)7 zQH-*?{Z$!b$pjs;SXKB~Gd`lnL+SKb?Ecnm9d&m~jgC+qeO4N9>w*{g`GKy5Fn_bDkd!D#P8x@k@PQ7aV-vRc;-OUIrGi3Nh-f=mB|jEJ zbW~uE6O((y-qmIBlhyNRJPneBXvzaTq?gT+jPU1=Kca%>j|lf*?n$^h9B*z{WeDS&4gzZFsq zTGuHM7=9HbzDMl4U+Y=QhWnBB9@|3ZKX@7AFN@z70!+3BoWq$bJg>-Rjo=Qe)&U#_fX=bZ)CQOSWh@Y8Q!x$xgtW>~`fzm6Lt z{Q^e*?JDNN+sz`|6W`JbD)!X3uXOzXcmw0cm5P?Hhgt5 z%_SJSBq;Rh8C&o2jNq|(%%L@8LmnQIW}&-)OKhW<^I$^8@U05JX?HK*7&7A?=VGC< zM{MmG>QuSALj4-RPjK52dkl5I1L!!%ZNIPwD$i z_G%6{q|HZ9rZJP6hjf!eFN^dGac8%ME-hBchtrpm_KVIK3*_wz{|9R0_6B_4J+}=% zV9BWQa1Y1ke`PA{HkIQ|n=I$?wntz%gz;V8f_u=f^D z{#_fms7+$Hb^VoPT2~;|Fu8gmU3U+kXe5*{&+cJ#?B#nXE7)8n@8d(6hZ@$>!~GTP zSQ$UNhlsQ(G_9bp@1P`q@+VxWU-pGamEJS7yl3PSvLY$)j)PjPyTbec5*U?y1tUy$ zpHAufgw*A^Z})_jXDr&cP=&kc)w0ROvZ!(Of{>-N=ea>{J`ZYL!iu<#Vk_9r=ab9m({el)lsP z*R}|6UXv6!RPv|yEhI~~%E==>nc}2MUYU9cX;qcf+uakoz1c0kwcIkY9G*uGih1s6 z>@CC?fqzp5_rM&)1KcW1Gu%ow++NnVLxJjGCkRnLADTGnW62L z@jB`F05?jDk{6kYwSpK8`9WTRLy~muU+;JR%O!Ug5++kGorwODI_L2A==LtLZWMd= z5WC|{@3zD#o6?h)u-d3|z9?|LqMBQcG&MR6YpSjDZHs5RfkPqZDygqK6R0wgJss5j z9P=am3-P+#+*jFg1RAXKAv~bgN9AzCAC9?a{CoajCp&K#ED+DPb~%*3j_xXcgwDe) ztRbw@@9GSTdmpQ&y~FBcml{{Z@$?)+71?11`)b|{^KJz%aw#giW^k!yFv9ct)%vbW zYmD?qF5$B zrdrR^6=uf(#+r3wyKM4<1m-$OfR(q>=7YJjqwipytQZ&6PYW%Z)2=!95`SivL`G@^ z{-fr7(!fPssIfWaSaUbcDZ_$#*3lhE41S=0hMJLJr3-zw$GgtOGH#(SDxykZYoK=v ztjE+!wDf^g18WxXta_-#6!(ozMCK;UJFRvLoXCcyy_}6ibF9pc-WRsvtzPza&7qd? zYTQ3kAZPclYQYNgdRC4ZY_0~;oxg$`dgi;F)q^ZMINmgCF;16u5@TRQmE{Bb+o+yAygMrtQ5Z!ws~bnn zyy;1JtaFuQ_n!-MQgkz{7!-Tq!x^pz5C_B}>RbZt7RsWn$2jh(IfqAd#Z(V&mwNl8 zDcrL59?q|7*;jEy|C9K z_RVU_zp^0ARcn>Ne=#>4BTzJ*Tc$ zBqGs5q|&;s`Q-HuWw&hapO$xdqoqD|*dei@HX1xfgcBQioY(8R0u>e%1cuoF(W3Mp z)rBU`vu-)!Ca0fSUegzL)avfAgZ-A9IjryUMy6!J6e#a)m3$R~POK-Gwy6J=vCMdz zh%SaB*;5e7PykGP2J#_yL0bL=eLf0Gox}h{sMGNaI4!uQlIvCSu+d@G%(g-lQ>;~l z$OmCzv1%^jaWt;z0~4teEZ{H%X1f7wcw004Z|^PVxQGG~8=hIyjTYzH5K<5!To*&T zn?Q;MVlII3$r~raiy!O*drvjo-N=d8y-Mu)d#dsFa)oiT@ooVThg@RD6dK66Vj>R# z!I`nRc-cWcz(&J6ObZ7fPH*O-FE*H|nY;?V%H+P<+~r<{%e`|{q6KOBWY(8T_G4^3 z^ZR($v4p5Q#39gMKrx(UV_tr|2jcHx)+|sE6}WyL1|2>@83rMJ!IzAhTW~ruOQdwy zO`_pX0P4hZPm+TNVN4&kB5afHOvd^I!Vp3(%xh3kb8r9!o0lC4ViD%E_VIA_0sAhq zR8w$L<^Lf3=wM_VaMol!>kSqIsjN-s#F;r@4Az~1oMz~g2$st9Bez{obFOBwY|ml) zSw@Xt1(Bte4Y2C#j+W{X@<2B^hu}yaz74G3$_8FSr~AA7`&2qT3p=-Xsx z77U~-n^@yn?>mJA1YGK(s}scZrOG-aZWWP*T*N0i`(vudg{Hb&sfA6;dpSbRrAS4Zr2!9>e5 z##e9)anMEWNDzuo#+bn)0#`PWm%y!qaIa0vA4o?~_C3yX&%izwP5rAP%o>9O7uPRC zY(r)iW_^ginecJZ{ku(s7s3OpP>cik%z8_KKbyrb_Y%=NhoAHBbb-~W>setJ!*Owr z-Wh?E5nbcL)J1JCGAN#&8br|?)ZVm%sVV`83-~m0)uwHcIIl(&Vp-eU*o8?RnW}5%4h5j2kw_IDB0C<9|OQ^dGw5&od z0dJ~|%IS5b^$>$w5W?$)WMX7BFp%*5T~bh)>K1Z#5nl2fj$rKu4`driiMO0{VdxkuUkAl~JPc2~B73(b3-`ywR*xNP79DN@ zT@mzDQRj57pRZw^CGw^U8XkmD3}M8&k?=vrn{K=dm}DTm?$&BO1vt-&oXo#|u@@o_ zL@A^LFxT;Pf1>;=2Q`S&Z^#s_U?hVr*%ogxp0gj|{%v4Ej{6DK9a~@LLeb6Tg4`DR zhyahO&hhqnSL>Yv%~IYP5q(VrFtlc8XuGuk6P^e(>q~s%QShN+!}zhpe6XNS039vr zK_TwgxOG=cC6K!Bh)U74F4mM`-B4C|!AFC4VV`Rjy;<6Vh73V!^$1V|^uDOi=>)x0 z;E@SV_Y5u7XaTw(N}c0`n0<+^$*l(^HbYV{2zmedz&pD9g{D!&nGpCo05AJkj10UN z&<*p}n6aj9o85)o?o%jv{zO$Xk6SA{*yZ!FEKk4lo8P9)`CfV9jpbE7E$Ls#Ly*C& zlHb^Dmy9Vs0o}z;Y#Z2V$*AxUneXZ!|;N11hgBFT9{Hgclrq znx0+da-=o2P$U|amzRv=FPAfPn9tak7aa?UwWMR9Krv{(w3sIyQy5EUVQ1XVz| z5(>L|!(X^VN+ysDM{c>slc0Icc!|M^&t7;BVx%RN-#MRwK3)*2ATleod%c~xI zLNyS$i*@P?FC5_|NXNIxdaJ+!Azz8XUpjvJM7!Z7k0 zpg!>E_C5D14No)aH$&pP8a#VF=+^CYc?uYW!+XxGrx1Xj{>ft+=1t^HbkW}7c9E*R zLSF;u4z@<17R3S`HZJ(UTf;0Zn^SCy%_0@J?P5IubTF{h7C{-K2N0Gl0AX>A)!44@G$F&Yz>zv}AF4UZ@Cnx!|3Im1Hu2oMJCtYRg7Z99y+ zT6zpc%Uzw`rtVjN0$LPgbhyGWgD z_ior_TOnlCka5OfgQHMViKM~be*9)lZm4X1?qRzR#VnyYulS-WbKo69y_TU(w| z*Sg`}zcS{=wq*<;=kZcSnk@Gd`@6kkFH{M3eHtnk<-V8T(VbHUpEC7c>MYqQ?t99Y zq_E9Ro8MM$wl|$PB5EIQH<$I#+YmUOx|12K$<1-YbKoxy9U)uRl+|55*jzSnVzai# z_9JG^z2t$BXH0>}jzSVl{4r7!fwyAvvbAQ8SMsWK`5GYZ_o2lViU-jL2BplzKxb82 zbUo7kb`~XpJ+Ba+1Agn%w6+tQH5(c{;LU$zR;_QP&|gOaYQ);iXO#J+2?!G?J`W4W zmjst`bHWR@_g6^+4?}(lM8A*=7dMM+D@^YOC)dR)GC0+}4Q9$_>eL_pQ5GkqW`w_4jf+UR8KwHIz71_!3p&018mZTvnL&MmU66<&}l@>q46}S)r#y?x!>0 z%~C5ASVkd{<0^yfyR%c`UkzGbhd8nR+QX3wvSPE{FX60NH=o5jM_G0p<)r_>bWIg6 z=U}Ef#4@r#9L`3W1FSm}L!HQVJU5gOpX>f4GdqCbP;*)TV%@I8u_NI!6O+$PU}lRk zkN|OoYWb6rNTXet&k?m2|WLI%DfPb0J@T+MN{$(LvPh4TQ62g@gA#NR|53|+3`y<}X zG(5*N3>aikf(^RT`X)OQ92WN})xZm9!{zq}$b}qggj7~oTZcl=dT>x7dzBzCcAk`LduZmx@Xh*1_ikdBZTeih7052#NK~6yUKLAHC54nhvOrcZe{Cl$n zKr0jpIItPBK78jT@NCgJ$V~wDJAusnh27w<*FYw+7702R`Ai^b7qKu?=yvRZdtOs{ zKL#Fcu61%aYx=>3xhN%fVJ5KWoSfG@G{MLEu>F~ncvd=`Zh*Vw%EC^&HVdllZE1D^34>h==|wiE>xH=nvvQ)Gr$8kifLyh8V_uX_?B}wlH{OdyyIpK8(tSIg z1zrfwnM4a%*y)A*d2L!ByB)0ThIGolJHlH8Wsnzw(kpQJJZqVwm~A7EtpHe9w12fj z-Z>7zGE*~`E6k$@fI5U8y$k}~+mXW{CZHrVryhjMV>A6#dKVk&&HdWBkn=f&KE)4b z(zqk&A#n(0834BjkSZSpS+|(0(zNq|Yp8UlfQspcYYVwx6;^~3Q%!n&pAd-_*S5Z3j2IQ#O7n%Sg=L_ck47AEP|JXj%pQ4PyslT z3BxzC7Db+jPk^T}uMoC9A-B6Wvv{;N8*Eh^Na7SwjbB5$5ZlV;d{TN$uoW#8m&Y-G zLrTEnR_=mn80>3gH58}LqpT6tHt=qQyIKD2u}~_ThoF8ao`FpiGy%6=&dIe$_AbCXHhqC) znA=j#g;H^yxf3>}5nzd813y$&AhArN_aoRe7oO}H-wufn?FI<&iAuzJKe)?5V03%v zn3?{VOHqMrphtzn#=rwU_5};Hy9aeA>VB3)NL(|1%c9fW=F5mB^~j2KT~|&VG2}qn zmX{QQeLb|j#hZphFQBEKY{t7${ffGug_kdq^*WT4W{lt7oZ>#+Gd`Bb)I(~mL%U#O zP-j{R)t>LVEc_I7y0)BxS0)hpWjCb92~i$o2*_FZYF#it%egQ#3;3otDeqYZ4`uax zz3{FD$_D|SO1;1aK(4450{t1RXaCzYds$v)D>~KPbW1K|4F3fM`ko;dhzKPO3jmnC zD6FMc+2s#@Hy7q+gwhyxw@P}2zj7T>QcaC3XmpbOn?80_qzY+?Fs zgWfq@Z6U5a1YLI^V{WHYu)qNORkvz%Ar`%I$^g|LN!RYaE+oS!P9$9MX!bW#U#q3*!_G+zD+EOAmN=VMDO&5CaREe z$_o&6NqFOZ1#(=dTGUTWNVx5;On>aO&{0}92WDu=hJ1Eyf?_kOt8j&3WH6W5Y=+$| z=tGo)Dx&Ht%KG=Av=w_FRsH64d67C3m(EYWW`Rlz`Q$y;2*s>$J~OTRv!7v;iYC}x z13b}t8!{MH~U(3dF4N&_hAPT+D^ zD2_rM1Dnkt(>M#=vuhCmo{I{8fum+fpz))~ttZoAU%>J+u@4Fx*Hnb_9dIJ{(R+nC z{qh5XR;(|YrA|M$0@mfcK>-OnT2QSDvE{y z-Va+PRIK^#Y2cNtLv3K;tQJMyZP-8CGjJDSXKrSb0#%ba3>P(N$7ws{BqbBcP0`Sws4Pd zZ!NiH;ce^P+Lp*WJ#PG8zY~6Ec1n0l%LKHuTiM`kwJGU8?&-!wS1SMe%5=Zq{|#<1 zt1EAh=oqgnHFXud=P15(71fOvDTk&fp zRwHWKDYWPn%|2zRj!uGhAn0)A+Bua5%eff~SjG(qDo}+2#DcTe7xtj?rtcJdj zO6D28|}2ZL0(-Q#}(T05ju zN)aCB=Y9PA%aVS~M?q7zpKrO}`JvWzQb3-om*O5XS>Mgau8iwbP)M(J^Jvc34U8xHH}G9u%0?3HPm_PtG%08vL>N)31HHg!hZ6yPst~ zfV=*F(7u-%H8jS#pi5k?Y3#?xDzWjeYw?K$?3Nwtt0nwBI`W(TnlTykVII?!M*b~N zakWz#`bb(sQ^uiOi{sE{F(ttqA}3!QTt@8fPA^1XjIC>Vp7s_S1A5aOl|pTztQ{$h zTNrd~g)Y<4iV1&go9kKV8U7|FdGbZxnL1a##`Vvn-nIk_ zZB5OUc@~8rC%D=;2HkWgrSHXBQIDo6)F>hU1mkLh ze=P0^Jg^3AmT?Mfb;e25cPH-O!c2NndL@p*bD7SIQl?xywOuA(Edl!xhR|skk(RwF zps#`GKgB#%m1VBVDh)^KizE03_|sg~ivRJt=jn2vn8ZS-rEhp1$=d9UtHi6zpRcxk zHuW3T-`!=K>%4KIftRtN<_tGj!~?#98%e zRMsO_u7Xo7%0b&-14#<#7(Cw+XPj3L3~u!Jz7mix3tK@0c6zi|W;_L4J3}3G4 z3$|Ct8<4I|$`qfkwYN3?e09LyNMlV zh)+VvLw`+lKU-nxYe}&kboh<3=!oTRopNk1#UCgF{IV+0)nS~^hM!Zlip68- zZ5rneZSN^&Cp4v50xt^|k=<&dKa=X}z}wPu2k~QXjyuZWi zS0~$6N(w$#+?wy(P;_Qfj!dRr?xWxi0P(F z@x2fFTP*a;P%F!TV{}kgY)>#*OtUdxiQiYx4v1NVWzn=d2KRpxQ+Ib2D8468N`IuC z%JsQkO3c7lOQ_L1VEwVzSufzxWwOSPJi>qf{5J>wKg@x3OgbII@=ck9hZl!~HR!zye4A zBN_jQEok-?oYYYtr3G$iquUG(p}LlB`;3QE!8P;=ua+braEVMDGQ99b}rJ`Pv)Q5jR)Fu=jlhRGP*Q=t4NhUgE?(RshH z1eSL2raeFE$PORTwIJg^xZYg=%Ft}>gjVp3MCQl!(A?ZXcmUtAH0%5TOW*Hs7uGdF z!?eKAT1+_d=CB|LPUb4Pac7+xU*QsQ<%KEy zstj75>n3&(_d|v&XjtcjGdfarq2K8)dA5PSS;zc!=X7RFZCc?H{9=jl&nq(ibED{4 z?o1NJ9oxL~tqb2OjXjh#-Q>y4tqMqB!naC88~fmiCpU`3RZ$zazQU4}zqv{gwbMi1 zu^l)!-7`ETKAxp1UZE+@nn*Zk|9#xYO`dJ(OMbTn{v;! zZa*yNnYaEJed`}w%zUfV-eQA!;YYlGhAe#5Ml$AXE49MK18PJG=EL&%qX<$l$?WLy zRf^43fyA>jL}_oV6VBO40x*7ZW0z^&4-UqBx#;J8QEbC8BZFYX{=j-}-Lbu}Z3do+ zkD!&ndgzrf)66%|p(f`k1}!y9a|Hds1Be-p*Jr*Q_@s$wLg+ibex2_Ka1oe6?TkjN zJiHI3#XEQ2FllOYY?B*-cIlg?_TQJ<-?h|uJb|(hNcvo>=Sw7!X|O2%Ad5b_Vwcz~ zO4zuSl}X_2BHrQZ8?c~I=lp41*nJ^bN+`%%yDvi_=2urlu`u%aJI9HyH;M9}&_-7& z8g_bkXvG1Dz>yPaf~FM*@q@7374gq55gtds`F{~J9-JXP2ni0}h$Yot`o@U5z#?gJ%X7!XU6v=2tU%4d0@b@XTSj zpSI+6(C#QCSH5}Q3f`Bi7qH5}5S=#A8d$p+4TV^GzO`gFmMlfg0kg1SFb?|WqMy$} z+>WnWx$8vMMovKa zoD=^0XdGA!hzgko8V5)MbA#2z*3W<){Kp&jAr*p|fj?Q#!U8{@duKjOvC>txb5mbf zmx{779!FyUn|EXgn?xvFzUqx6T70q}nSD>?$604*Anci)Qos_;*I{a)mKf<#-G zkwDkxs+t??)a4?D`&fGRtB)<6mWm`<+%o8{GH2K3^v-!beF^;V{|9?_KOzR?eWwau z8q`0wbm6oEtIXJU`ORH$@lMquBqPzYsMvklHt#8Ev`O}=cIAUp9_j=ryaI=W@YcXcSAJA8)kD3hf z-$b_&$y4~B!!m~T?aQj?s20zj`97rQ>>P91Dh*iR8%Pr(wtsQt1x_>Oq1((0RSKl} z$ho1>z_rY{>({1!geb+(>c&~lfbcli0DAxJN6)j5)<`+7gK0D)T}Ec}t@XaZU5MHl zeYBF6y?Xi;oYJer&-`xJZD!jQQ3=TE%;UCKch=8;eEyd;mco>RgRunzg(>>ka=1~o z!hE<|o3*iOm4vdmJ8+M`IC<>3%+1-KYuxx9{f z1)0j3FJ}o3!qRrQ80K9I=nm4$1Q-+Sm{qu$;;ioXaXch;j(_;}(pb<*Gy2Lb$)WFn zVtIJ1GB6sTjU98waH!hO`JiL0DKRoui&@13O`I;;Z4t8WVOrnCO~{*pa>9~XS25dL zNb2t6y!ugGeGe?d{kMb^P1rj#$koQ7WdbPr>|j$rErJY@pQo_*aGBQ3gx;IDhdvd3m;e#O`((C_@YU! zRCfxGMV0`L4>&W;s-Q*oXoZ96)neCT@vq@Losvy`SQX>eF|>@K4?5^JS@)i!cp~SZ z)|_Ac6F*yFtrXyo3O|g+ON2pG0W(oe@B#2?0XFe6HVL^W42DfYr3#&S`#UJs3drOR z91a3yPpQH@1>KZF>#X$6LFL_p7DfN`SypPJ1M0F*5IGO-Lsbar9y=5+BWGOQI0T3M zNa+rd85IBvd$qf76Dky@kVvNWiB^wZ4E{z)56NhFyS0P}CYgD!hlKQq!x%7Q*3UA? zTdzq1c@USr%qnep4?lQj!<8>yhC=}J$MY1I*WyePps2}2gi0bT6`_cBi3&}1&SHDz<8>H2&BR^y1hpb4yM$<`&8O^8 z^Q@EU1~X*bW?Uh3c8KY6)3;8WGvnxls{ng8Rc|-EteTj6oA?8xgVP|fkzJb*?(otN zVZj~PfXo|({Hh{;{)~rYBv3sg?!?qFwOEUuu}Y~aF|Qu|E<}H#>qdCsd(1A-C&iry zHAIn1NWXLOsg=Ax&-v#j)A#7UjSmSwT`P2*tME;v#E5LKrTB`Zp$DK&zYFQKy*mJj z#YrgDh=b)8G9wS~Nr1z)3{B0nYQ_)XDgFLo&K^ z!$khw(_8WWr$y~>qMMUDK(Z&vVSA2W_ethO@0HO&qu9TR7eAFD4FaVb9IpG$kf?EwJH7&%mT6NY4PsngQ>~#7TdfpTcc-US5W-iS1olnHWl6s5u=Gp zvyT~+Qk0awZNc01N`~cSSBv3~E9fGq{DIp#YTxmU1NT$jbmEfj>APjt#8;S{q~e^` zO{1U1ZyY?u#GO%|HwC^(?5{y7pFM3Cp~fyq`qLE9bKb=#hl^mJLb{ZP&W0RGRs1y@ z`+8BA1C{Vz;^z+?>T;lj4@2b_U$|OjXi7JHUqY4ajLsR`Zs|`B7#-ApUBHz`UDX$i z&3PS`N5k@bt+J_jN8mR}2$W=TNO9UD%eOPX zKv^3QrJg6eF(3{UWarma4;#rNwSLKl0!R1QR{YaS+8(anK_UGspYrCoB>>07fw97d zR&F&q?i+aovA^I9!3iwo;( zan|vWw=JD0*9BzkoO9YBnS9Ifb?Y1Sor%_rvbyIz|3y(I<@HQ#xT4Ue#^6JPULxq|>3pgR1pZa;V0oEL3nL|eN| zRJ|7V-lX2&SwFMTO2K4>#kbJT^Vd2;8nbl#g7m#gC|)R1KB^moQcP0a$>pA@=|9R=iF^&k1#zzklY>_I>Pm@V?C3rYdwv3IObIxh(H>AY8C@e2axn$~_Gf22KIIi4stryBj0u)k#(e_6YC zmGHN3(VbGVwW9D!tZ^c)jzS~Fqi>$lO)VABx3obs5h`wc+-Vu;yWE{8SM%kO3F%1_ z{ULMGI96#K{sclaq9$}s7yNO?Ts$DbeNXEA^Y5Y1IGj!tGxzB&m|c(C`H!hr@&1oB z5<%#omO^wQ!YF?lE#e%1G9OY%NLlIUBd1ZDMkD71gWWxjfP7WJ;iU2g8u_;-;rOa zY^RuCBPB!O0BSvs9QnJGh;gF&({Sps4`b4L#$W3>#-vmcObp&vfLoj4U{NcdnOsE# z(^E#<#o1?%=ibKkp*9UuBo3~Px0(=K_B!HypX%uAWIEL+q^`h8&-(BiH6>T7pv1wZ zHWx=Awv%^YXY;RS88Hec?h5u5Cr>_y7SgyKpG?3p`MXWHwj?$W@7H76mY&h%9+waE zWNQ3*1oL+SW`uB&Px!FdHKC)@(0D>};0scnw5t!!j=ZT)9(FL+jW`pdgY2zwi?b;q zd2m5m;gin$g}&d&=+9-mmtGDPiOKVCze5)P?lGG*@R^oEqb5+4z(ARe8(4`lj?OBm z*~Hz4yfmZU=@FZ?Nmopo;NxTzwNshL#vnWIQ~WiC>O>bhR3-j9e-UX{OC4-7sE& zh4Se7%O$mAhms3Ffds9wF?>?=e!DvjTy7t*oHsbpVQbM7PW z_u6q+M-R$W(E4@3-^pCJrA(H+O=^8%-7m-UFrVu4FQRmCYw{ae;L3%i);ye1O&IMN z8tn~|68qbIfqIp~rB;@+{2kd*cR91rs}>DkOFO?vH1)RLh&)mSW{cg`X=3_xbziSC z^z0xS%qehhjk*%fjWuBrk})y?*Tj6O99^5ufPn6HC{OCy^|TNpaq#+#@&=~^d}qHn z;F;znlHsy%Gx>H$eu;_so6cz0gxGhVg2ZRY!YBd)D3nfLDJTdLR4smWyN(90F_fAz z_H+hy6zi+NdYwZ1l=x`kw)PSxJz z@i&TTkBYpLW-*)X=fr__f&>*Rl_)+_OHaqpE7MC$oA>UWxESgwn5c2UKN3)yVp}eD zF6QHZI6ZGYw$olfcy=h_^_E>735D0~G$8$DyayVgEy7=c{$+_^zRvTAmg&^KJM#4c zO}mi3E+fY+$(T$gsGj=9Y?(N18Oy{b)O^)Ppiqpn+|s)`O(Tlp*-cVE@M)p-)3p^+ z`-O}{v130;QwCG9u}sn67io4Zt?;Xt3Gh>{1l*>E-B_`smtSz7`n9gQ$r`EiDB;{h zv{7_WM$_PV9H7kD@FrqttswYuy1W4n`L9skNmY)3A1n`*C*i#b*hnlko{0H&5N?lj z>Znv>pM?66&k;xwxFEdB*Cgf9mwa@+ih}U$N>p~MMPq;E_niZWZVHe(|FD+Y&RY-9 zBx0UCW<*D|wY4o3ep>6O@$nhIX1E4rwxHfPt_;~we6Ptxk9rhT{2dna{D$-JX;f5>x=5`kJ@ zd9o=QR_QfUD#(T9bh;Nb4dxyaH-;f;xAPg%C| z$~eLoT#c0ZA*!q@zEBt5u#m0&05i2$w=m52au2j_U$^fG)0@%juJEAf{P^qU`48Nw zvU@s9#NNeZ$2qDQ52}Hl`j)z}O|RvRe;=w!?z8-Yp(0K2pP8cGgK1db5zX%Lrz>hK z?HbICb|P~+lZgIw{7wvEf)Ho)8FQs19EiM-m>dP^g($J&`pen}$HsQzUo|W5z(2ka z=T-XDIF+XjeqZ`7_)xp_H#-!nJY{i0%JAESE1ihpA*bh!BSJd}S1t5!xNh?4eZIoR z4*ayyQ8Ol_-7Akf$rXy$%rb^m($ij0a^*SX@16Sgb!h4ljJnv`^D z>3LtCKTplmdamhw&*+}`WxI-oU;weC8#JBn78jBaX~++C&L`6pBklM|Cbr;CXD9uh z>HlQ!-Q$}q)3wo*3KbE$9F(d^^C_dp_wXFnIdUr^k8pWK_i$Aam-VX>K%H z**+9$J(5GVwR9M~Mf9kdd1!lhOmgP6(~WPn1EhFoc6V;CJ1+MnwG`%m| zFkGs-k(PS*%c5DcX5s!A6`YC@tUY;(8s(AKiVRmr>fi{LUzvw0M4oj5IPb{)Wsz8M zqfqO6S?dd`fg27|r~^Z$f%j0{ib^B+K}5Bp{uMy{b6=UEbwLQs0R~FPsJwylAE+4t zE{gDT^v`)nhag~GB@biZ&S6o2du`h_Z#%WiVi;b4UtFv8ee&*mY|Q?zuvIr&a@uE? z1ipayI9k{eNhm^N>1tC6>%Lrnqirb+%BqM|#Axoy+O&A_le+gJsqq zZ%@&aCd17%Ra+PvO;F9@y$^O#(VU^M>*$a};i*(Q3QNeBprJJ#9WT_Ig?l#`Tv^JH zaqG4%ZS-;Q-0!|uAFeak8sIvQ{>ufF41mQUDGBsGbxC}k=+QunzK37GkGs=Tt8eYt z^1_@>2MQJ9$*+sVU>-1E9Hyi%HfHOVEBz^c(6yx=b9Tpck)QKij|=zYJO#FmnZmL9 z>#PGaMNGvnZ>_hwn~A&V5y6+n)b)(uw;SR^Z*;@k<-kgd(KmD$g6L6Ro`UePVajUT zDCmPM@aP?c0UFo|G{aZALDpZ}zkKs5;SVu_yMyV>7it46;=SmJ#o^b)p{ePCC*!+) z$#%uX+1iIYw^J3`aTnJIPxtT^u~_+2jNT^T+h4}WQtSfWUm`ctjUsyC57lQ~-|0wq zrq7w5(tlVqG@yd?!hx3Lh=lIGuFhNLmv{DQk&%fJ1|JjI_oa5HR905*(a4Wz6#11( zIAMW0Uny<1U_%;J4v+@;c2{~Rj7g_Bze*GI=BC1-AGm$}8*=%`J}Z;LvkOC32Xpr4 z>jMAJ--*S8Xvw*S2W+Km-UJo3twqc)((`VtWk??Lq_k}%cl<52@=?ys^}>-QqJezX zcqwcGn4DW({!WRhIcZ0Gp*FNLQGQh;9UWSmP)!_ZEftcD@hJSXsnXKY(y`E1juQ;f zxr#Y*I*5O(!tQ&5+}H* zp*z`YfPI=m!{VQ%zkIsx#!QRIIAgo?M+Gwc93J&5@3{k}L)?zwcf9aZ@!jV;91rY4 zwkUMSK|c+hij_n~=9xJK%XxdoQ2GhOPimP)f~2|h&}{AaAB8{66<65)mm1Y$oO;+ee@>L2HKw}TT9#^F4(;*FC3G1LkW-0?UDQoOt)05tZWIV1 zXEqJRqyql>c){%){Qk#c;S=UJ0KV!u5&ppw9b_ydCrPRiKRhl90ECW%#9mtt${Qd^ zIK5$;;WOK#Cw|wfDrh7_Bf5d9-=1)C64IX%N-X#QtUg7+DG1bD=wq9nppdV2y$+^?%G`ZeY$d z?4ii|I&u5rjP9nTOE_>RZG#WM7D9DZqofG3t516U*s>h`$O_>Dk34-Tn&1EHBoA*n ze?@4FpjIYAL>DU8V7HP6Wn>UMKw-)F%?!ndny5WF?`6(`cMx1$wj{BLH&`(z{*ByC zQJk&swe&}=IkwEYYhEP#wnR808@71FZ*?qXx>`h4fhd{x;i`vt0{Mpza2Vl`%B&e=FrY9$zgm_op-6$Ge#G~8NT<<^smzz^K`Dv?!4{$x7aRX0t1HuVQ zaaSE~LLOoF?(?GX5|P&{@-I30Zm2Dt+(MVVSH}4v^USXbW2*XEY6F^1Rd^$Euk|yQ zL>7g}w^?}Z_LQ9!+uPr(K6>)C>>grkcJ4mYYo=Q-Rji-kPv)sVQu5)Yvb%HgTMQ z&nLCs3{=((Hl4CyU6uz*$eX1~qo4c<9OT2@$UCPWTh=n;{8wgib@1OgQV52&6q!z* zQlbDU0d^z}&p6a`{gLg>Lu)xs$jbv16-_TeDVPmR^`0bUpCvpdq7LwwUbCVvNl}ar z_9A*t7M;;mZ~&!Lqlc>^>?i7Q@-%J}x#6lB@IOYpAFjq``5Y7p_MAfzK}>#rr$eH0 zsI7fUK`%=7>~)S~Tj?e7?ru2u2~aI@OG&bk0wa5YOFhrwlW)ehcm9d(O!6}6EPH{w zxro_%Ifpz*gi<)t+DchD&X|Zi81xH;G#y(q?#G;y_!4Oq(*W(a9p4K{j397aP&tzi z!4p2%^lmp)pr@lqey2le+d_cN1lYz9LP0`w)7#Xlx=RI7^>89iI(=8ojJ{V$TB#ccOOJ9MB(mttv4;u zldGcZK@cIG?pBli?^U!k2^bSDYeH^`>g1lHs&< zwn-~8WU`m_ZaFn`;0$9B{M%4tMqM9|r=c~^~ zk&u2{lT;>&!@+G+-DwreZT>*_Jv0izH?pY9r*hg&`kMvfty`zmgVn!^H#8@80j7~M z1%Vel@^hUMzFMw?;eta74FhUsoG1Op=ksCUuRb-UhUTX_4`BW*K(|Z-dXWV~BEas62$Nu=YCA<)N*_I2^Nr7LwNegeY(oV#;thhF{;) z)3fZ*i1)?S2W>Vm01!g-H|#MAdai1{)gl!b?#enGb1o$4I?%2YOuxC_>V&qskrfd~ z&zy?vRdvo}fW^^6{qxU+pI^E*AzgpbR5y+`?jAO6ut}t*!i03R0A)p$d4=Mj&k@Z! zWB`&ivI|1SEA-e@t_%QT>1~hihe(_UARn`XUb4+Fv|oZ*D#Ii%^d3TL#c(QJ>Q}b2 zkf@w-kmq4y;iyTd%>t6vi{Q*PYtcuC5z;gmW$kUYBJ=i&{+)Q*nGdSjhKnf5*2PBrzga~}8z0vg*d zMWd_rp2qJia8KE?b=&rK9yKgB+|D*!15`YafcY{+%xYpf2^M6d}yT9VPICPa_awVdY7@ytDg z+ZPh#Ovo4w(E*4lzF`xcC_oG#YyYvleCEyd)uWXvTP)gHj|XT+D5R0Pj86VGeNT;F zrIv&~F$X^fhY2`afJMzqE3u*^49?elJu#`WXl|WX(`G9yO*Z~ew~E3cHqyNQMiP4reRkgN;2i< z6w$x#v*e9wU{;O58E zKjgDlb!|%4a}bUWL2t?w5R(nnCMn7#s_|8Z%knxRO<40I4tu;)?gMBk4p_qDC&lhO zM{t{?KKD+0yUO8LBmkiiO`lA<^8tOJAY~9Bx);rx07gL`BC0!`8P%2Kbj?R0S!y`n^$FBrYRqu)|TfrW>j)s|(4>QAjrFbtbgZEFRt z`CMdDTLG5x%MGm(Wk&{3Wety;`yLb8PpG=(2G=}-UMSgpes7$7^muBxRX`UAnASB< z2`(2vcooZh>JJWa!*;*QEXljO5}b~~AwtPds~~tB8_L4En~8DnvpG0C#?u12f$%-A z4LpL-v|H=iXIOq9c&f?xYFz<%qPp9Tc*JDqKT{`9~{I`W2D z22t@t0A;8;DploCY9d{|5- zI0aWwOTA147mB=q*ng}fqD#|@6|G6CI&PpuOa|1!PlJlfn~{YDepYJVVWDet_Ch6r z(Er}S!D&2LE0i_7QRM=C>pH?yysgHS_eNG$c&5;?1P^!MgEIvF!pieYSw2CC0TNrQ zcA_hsa%3Sk9pdhxydTniRPo$8k@}#`}pC z%1H|OJp#i&?MQx%U8pHQUA~{eS;W@sfTNALqVOd5sA|B+MC@Kj5hp$|*-i~Lfd7wA zQhMl2NHAmMlKL+RIz5L*M&b2*NqA3b@m_)A5Bo8Pi(n&!MJ5uhejEkjd}RIqjCdd zf-j2D4FFKOs1eX%Z9NtFCftO1N2Bs=U_bFAZi{Lme49n|C4wJo6Nk_7uwHQqBCS+9;^`borr%5^VC*$nXvEVsxhEt z3H-6y2J#s({S_}9Fe=)OfoZb`hP36V-n8`5WOx@GID&;E>9eavuZt3k4 z<=5ib!B|_h?@@oPEsT@B1m_ZbAS)RSj-^M*Dc9t^XdXj@sTDPZOgQmfw9xhmQ` zicPD9J&Wme@SqiDUUYYfgK-x~@QX8nq+(aHG_<-ARj z*NKJ#kJ$aear{l6P(8SuANoe*d#9xJ1VP@erF&mVQnbVKuuFeHpfYRfs9pS?cePGW zUy;4sA4@$fmbMmcl(A z+B!HV7SPRH`n;$HKGmqcaMq%1ZdYQvX-8D|^fattbhU8g@%mF6te(f-H`%H1fHJvA z?0kn4PyOW2dy)5@r;@r+=GwtiJ$wj8tp#rF!D2b-%R+PC7Q5FQIcvJyCAxp%Y=&uEKZ4-uL?AKY~TFS#goo-@OUGyeCbpziAecBMHu4 z^`KRrwtG&N^klYfO!`cHd->I?^!k#arX$@i@IIC^DjBg)U1xuu6JO_gRe-s4+WG>) zQMqGY`|HPgj-07G-*rO1`NWqlZ`m5p0 znEJDE@|!96_@z~T!|k)#K{I+;`3R438$DZcqWzPbHPiQo@Y{)Ps2^C*0njchvV86} zL_y!iZw81SE`(Y*G#WxG*; z-(GZ|k>h?#uDZ-+dM|HiA?UMwHFWVI!GH(inU&gLuHKYjFm0+D#tATk``hJ8a;4~4 zIECE=CTy8`MA+fVYJI(G&K?;4Z>D6mJdpmB{lo02W%8x6SNJ`5#a~5CO*Jta_NV{{ z1FE-I%)^!z!-uN;)<^zz``{m(mwJS7h4QSzxZXcvDfyD(57%by9x}|>zCWgFJT|>4 zTiCNdU0Sw@AK96zA%{cePZJsO+sBiH!!{o6oh@~xdA6`)u-?!a<`3^m&jFgoZnAyn zoHGNld9}pgu<5uE6agRG4G_$^TKBuV2nq1rMtGMQ@zh6k085P)r-tM z54%I;wtv_oL?KQJ&JnJar=by3MU;8hy3BcNci5!rLu7^~46*sU-Z6ZTo0r{4O((Y7gRA8N60Z zq9f$4P3_6=!rXU#F3;A_F9FQK9pH`dubo69_;F_7j%bbO0b z(HTzGAmfm7)V6)N%{2BDeM8*ksnOkc#y2BlDUBtT@lSeUu%(XVKZ96C{L$=XdR8mL zRBKRWfb1ID0L!fdvx$L4&Hy+31-G|L;GZXacv-kZ6x@|XfObhwV?47->t3l3+YAi_ z7nHcaS+vWat-PL`x<5;fS|S{o%p+X#4(ZEKb2|VDU^e~?ur*PV@%b;K z4%<$rev6sad)}>~DoeG2+&>vR>agmdwCA_3aR<}H8#uDNrDSUN_>sj>gJIfA$)8$f zCyPg_dv6|D{I_L~5(cJno$#xxnA_huo_E2~ukBp7Ew!bfcYJ}WDb3(p!mnRmV(i22 z=9kbQ5^?}^LRbnhe&1lD5-RiW&i7a2VdYrKh^Yww4KpZ)IC(eOB`?ITZW5BunyDc% zKfc>Qga@Hrn+wNGP4&akCFH`t`DpZC%=~}W6HfmYb z(}!wuBIk0g{!dLoHKOCisO}~xE*e#L5gb6G;$JOp&W{!askBw#-x^q)yXTM@;FNmFjU9c(KZ!L)% z4#2=GmAUNpqKOBgv2^oO#<4L(!N*DgqJWcQ8FvNLzpIHb?yu#ftFE=~<%Pc!vlZNX ze7;GJ-;VYj)u?VWdJnTk9A=H_F%24?Sq^v9&v<-MFwlmET1CBsqPeK1@2iBO2qJ%6 zN7PD%6}XG&-Et-`%LUG(Z8=-ly+?6ItW3mcu9D_xY&&6sf5ys0>*W%~&IBSo-n%`b z0Oha)r*!z4HuM4!@*+T}SbK(Ywm%Fkq9A(J8flJyo^>D^UF0FS3;P$AU5##yKGAz_ zV2AgtHqd_W@`!%G(<~@4qWj#VoU*^pmjw5~$nHh&!hm3s``##`S7KR_VI@2Ph}ce$ zxa$N?K!;eqD!Lc7@Q*Awb~L9z2lk z2pYIKuyoKz*>$+1ddkn&%+KFY9J=k0p^3aVln9!QR2GRBB7br>rD_R<=b(VxBq+~3 zQ#A@0pTM`0@F9DV=?lW_I>=dKFDilYsEcMP9vf0Pb2Q5U+#V_Ds3k7r_3 z1tKU;h3Phj|DscsN~EXJFUV#sb-7DIgb_(Lb7@ht!M#clj4?np#3p`v6bRutl-2I9uTLs1W3exZ#*vj&l@%Oa4nNR9#aYP-rW*_LQ-; zx+Kgu7x)hjG)U2CI=q`j!Gq`v$kcy!=)#b4ACnF+m!ww?b%nDbW;tu-; zXk7ubc`hucjfojr-|He0@rUk}6TKEu7+6&s`K4%6hJc`|M{9#EHEKyKkAv!V53v3j zT^LQ;MfSpzFB$K0<^!Uxq>AvNxe6#lcO95*tR|2tRf1c#@~F{RcJNo>&c#;HtcjQ< zRliX+Sb%r8va9t&ZTNYS?=T^C^(L}`2$Rir;H+ady)egP4gh(I@+FIg9}_wz%@~v^ z!VBWN(OigNV5UhA#9>X)a<+=TC1NOoqWbnG$qOyEbAHSrk=-aP2_ZuQ)$;%}Y~>RxxpV`nRuWT>LH$|1NRjoO6Xqr5#GDN z@B**xtwqc=csJygMTr^6Zg{41!`~#Vc`7E}_frh+ff8Rj-NefQ(qXTuWLeHr(n}58 zDSYUDh?&^eX?*hOP6u!yU8p|?mG+{66|(>zFGs~968)kcFu0N2cI3|aLoY+OEVLX( zp@lG5iH#+2;YQJLN30Rbc6L9Cv3RatbrhPDW6PDpWUv6X0zIUq2a@rI4GZUZ;FaIx zl2#~7^iP#HW=M~~Ba2bf$$v6n*Je1Ub3IRsAaSqzQ`27b#60gW)C0doA)Jo9BSs`x z|67aL#X0zx$h8@@yD*4eC1&oV8+sS$9|m%Th~=ESP+T{0DVYk4Nh||PHIT1&upB#7 z{kM*;Cb|*ny=t`CIzAJPWHhR@Yztp(?83ugW3<@!oX))2!B`#czb2%3k&la!qBlW= zI|UE}9!5bEdJ<&28U((@XhZGly_Cb!3sj@|hA~vYQBVAqOF!)hLkRdddyyo0YZ8>k zgU=?)%Yn-YCBzH$sM^_K*q)<_5Xvjqn#ek)a56aCgZzL${Iy!?_XnMtyaPrRGA^(U z_U7~NzMZ(?g+Yr58*A0(Bs-D+5-8Y?R5sKR zLXkZBN$4sLWy@43j3ChNJyYwL%3d_C`(oq9j?y*7-RBAu4rw8fwT=IRM}GxZaUB-+ zHSa-o99E|E3G|x4pdu@P;wI`-K?Qjs^En$)!IM8D{BvBQJr%Zvys%P{6yFUcuC<(Q z=zNPMe@YJ&;qs@PXkpi*{lQ#OQ%$StE{=2oUy^Vw6a`W69`{DY`Yu(txKiJ+0jiMv zyMv{IzTLt-9oujZqG6y8o`YfZ6}|vCX=M)oueowdmwyV^3Dn8RXl($;8PI(H+G%7R zzLZE8*!`aZQFI)LD-oL8a+cxt9rGDllZ;PC^+WXhqdC+|0GEi3%Y}RHn}n8VWJXeW z=PY^N47!IKK9Zq4oKXdao(r4PdF=l2q)>UDofXu|S7Kxfq{v^PY==s{yNNY?$kGu^ z9Wj-y=A)1Ie3)03ferA&*Tj0@J~B=Y!(B_*!hW=K@2B$ z`(EX_+QiglUZ3C!>q;iluBp&R5^C$oz% zSUaG+`G%kg##BOo(owyoI+C`IfG3|RvdN9d77ySq1XL@YnV11>7=0|oryn|q9)u1OS1k~1)Y8C8 z=^o&txqyL|S@s&g9#|n#mgBxa_`^S58xFlnIJ9a7Mn9w3SXCtlhsdi>P&DPUvEx1e zcHcD~fG`_1;jlA{LP%gBwiJx^AL#qMMT=j_%>$pN@-!#0QB4OvR^;K&DF|jj6v?m= zSbr(M*p?Lue_`h*_~jvB*-otmwz3$^$gTGpXZSKO$}jc-TLQ(u?9x*~bTU{Z){ps; zgPJCr2km;;=KU&^cSm>&qDLcts$G+2!DG048s(QM5U9{swPa(5;Z_mwWuRXR{b)*r z`38>Ou}erjD=U~3kdLbdvx!`d7EY#sW>~Zwq=mwoa#Bz?Sg1x(~cI=QwHWY`UPzSg{fk^PoCP&Uh zF1X}GUK^~y=@WSejf^MnedJhB#I8{eBnkCZGY}qv@+~$=1Bzzx>01v)qDrcX*L#jN z%m@}3*fEujR!}tIBq0uysPZdA_X2a2M5%h>u(7Sg@M>w4u(y$$3(E{KTmMDFX8kB7 zgqxXiYryQmytB9r;hRUqPG0OYu!|_mKpqtOlL1YD_(nGQ+kbwmNWvzVAeRd+PXuBp zwa+`1Ax%k?p90!=rLt9ne3D5Blv6i~#_2&vykx?%4It-?!b%z$DU=sRp|FO!Ehf*w za7Alf&vPjjGYTCMJ#f#O>RwwQ+`}4llpdjAh_6OLCW9IcHF+OeqLF8$kOyPqTX14< zwcK`i#2;dTGXyaLgN#I<9yN?MU40)uB5T~K$qD5u?zSu6-)o0i(QHZ_Dm0+hQ?(}VCHusB^N*nYG4 z?$2V8Bd_F$~8fPz0kzs&KTL?`d2)vm)&-yz)d7V2SvLf zSOXpum?{DFL?wPBTmOVciBb&oJP?q7%nScs=X$%IbrUGm%EGJ~VwXP!#fA(@S9#ut zbTO!>0>ub26#IRqR$801(|-tnYf+>8LaC>9pQ-e(g&6cDBdzKZRcWRHX-(2o9dblA%@ z?Wor89J=w+YEtya?3CT3ZEu}Ljg*H0Bw_+A;y6kCp;tk@UXVL<6 z+PtYQej+f5aB)5WJw-~+@6pk{`;&sl)Y#!dGXM4128*&)5--?2N)fh=RYWCbi5(N( z34au;)V@yqty&JHg&h!i<|W3_cMAlJ#{PixfJXjA$=GygUnD}3Oy3S}pxQyblStZ= zRJYTKXw3gQH@u4H->VH<)mCbZ$6V7^6)f1M7*SLG7XGaCpj}M~Q=Pd)_&O&}<)14U zNf!;~rqb)y>}a%$p@EaWw9#3nm6~6_YefHJ3rutKN3URL^u1$*YcqyA$3}nGfhMWi9m;z{zgX~ z<%V`y$hI_+T&?xEbUQxpB51dcJdjOzMpEgX`VR@}vN<%wCCB2JpDd|YXY3*?1oWn$ zTc`In3;cE5=Es1;-NSWTi2$5AQ;9JjfMS@Vl0tp5kc|G6ulh;u+i09zOsISm286*2 zC+E>RyS@ju-*pZ@G%t00bJZ4qB}O}h_GqGK5uCTZF4b8UJRp)jWbO%MgKbfD$@$0N zkiLMa^9sI^*u@R)bp*dndxO5sq}E92OFM1MN_;+Z~JT zJ$K;jq?6g)o%76`mae=w%vGih#_{V-PDKhGPW8-XfFsgJ7^iWdL+IX4fmOtP6$(Ca z%_e2H&EP){2NN<%Er5Dclk`_@ihj* z5%7(44q6NcvBu3tQMg&u+oGi}5C#sX7N-WZ!A88+lv``N9j+REo}hyG&V-C(D(6hH zQJXS#PboQ?4s@iimjH>CKZrIDr+Xj4bcrAzDQy48)tH};gCx?`IE>CxJ+Qr@NZ(~5 zyVAF}A18Wptsz+a9)Tx;Q{^fX_zFdyW#*n92ep^yg1vPFi`w4Rp$y60K_YC#@bDd- zjI1F1tLcCT_s^#vk{*bq>NSA^sB+B1u4d@%2?p z=|!qb;_-hMU;5iz;{9->YzAA>`xO2A>j~YG$xr-Or{OSj4n3%LkVqjkTH@+y#T>S5ycJo-Km-$24VW#!HvimB+UcrX# zx0uDoL-S5oxUoN$dE3rz`uVRxYb|R|K_lzBBCmpON{1uwMJLtne3!{JII{tr6Lv#C zA@zMa_3b9(`Jg2Xfi#I&{a8~zPHegD5wuMt|16>r#p1-sl}kVS=S~}LlRR;otPPmQ z5?vlkZ!a;PSQXZKJ`{PT>HNcD_kP_>@`jG~*%Un%#qCnn&9j?8aJCLD^Ap0}MI_Hf z5ne9}nHn}v!WiKbqQDdEj|v76K26ZTGLLM!Ga<+9iE*A|$&4#CJIPVuopP!zP4K=+ z=shf)RpmXOyeF%3w=G6-Hvwu-$i3aLiE4g~C7YqSaTCakr*^Lt1fj2euEA+CpdMdW zrVp}?`S|#0oC1lS0FVAyyj~a6jmXr{kRj-W7Ml6UUBrHGX^6ublj_iQlW|)bx@LS8 zjPYWDe}OiqqnM0!0(uibxG+SRxU08uVj+qxk@)aeX^K{GK6xpen3#MmeUqA;dp`5Nm^@YSf6iZH|ee3Jdk4 zU{#4KxX`u!9kXcA(+&uOvr*()4f*^$em!ap=Y@yGb$|*CdY*__gk-k85tQ{@7k&-o z^d~TTX+=fz;B!BLxRT-rZfxG~WLGt}w_M%~zWFNG|1{>2sF}aOp^S;)FVX`)p(Ld< zuVY^QK5_MQ={}3ni<($oFS}ju^WBC9je2MoL2?LTP2v~ftCpLF>M zSi-N)H7s?)c#xfDvTc>d$Mpvia7!&d&xu51(1~2oK^K!VpD6@{Vr;C;W8;uf8NfR%zz&fE6GZJ^xOGIo!ns~YU(>&V$^tY(tTVlWm!BVKCi-{ntA6peS`X4@5QG{CHqjT{ou7KxbiQ(_gf|vt$;^E(RT~v+7&uwh zd=OMSP*-~x(6X=Ezqg&c^_~*CoMrK%@y)~)ioGWM>Tx=)W_yms2VEdlTh4wZf`X*} z4b-heqYMRQNB1&e1igciKKX@vQ0%U$*Qf@PFfvWaaSn()TgBuwofrN5#G?_bZedlj zLHF}E9pd%wFWTd?V6O;=PsrA=lUt4lI#9i(_Z-Yr?pQ@BdI9KKR#R})01nTqs>Lde z)S-DDhJi2VBDF30?mIzbk;2Wk^6WFq8*}g6=?r{sX8L2gcFbqimc4cw>V0cV*MNF1 zVA!Zyv0WFfrz8G)<~fRw(DoV;qK6} zG(dw0$%i#2pb7=Ozpm_jP;oQA&W!N#G44~_#9LLN1nd$R9e!yHv7;63#fdc+W$oK& z9XxHIlaaxn5@&9u_nUI`kHf`CuwR4wQ3E>F#X|26l3_aiM{TNxKm`$HvF+FGGcF>Rr6(lL@EJ!yV z#QzsgW@%U-5z^m70CUrW0#q<2?h|IE4 z0zH%TFnp0$*T2fp-+@ydel}6_V(TNP$FPr$UwiRkVth4pw%7TA-iwn(IGm$p%e7Z# zCSt%)0%FOaI8mq%T;P%yBL0%8omk#1Uv-^oxKuT4l{=J1iNdH+wreV=PqO$BmCBF) z75%lVyACUi zK9QsCHJNiJwNHGPo7Xyef?I*$xo~H$IR%3zKX0DSpT~nfu^9@RL}e?~l7CJN7Zbr^ zb?_^7JKPoeaVyHR%uuJKd$RSHvqwiqBdP$A&OS=FYv=}zk^|N=hAEV$KwU=7VZDB@ zE^yMD*DcG0@D+484x6jS*3enCj*H_mBF~(mgqRjFpM5WzR>d5|3RlI9iA#PYj}V6O zbp%G(lp`trjb8h3iKkA&nd)KtzsA4dHiD+Jr)c9t_k*J^Q$U6Ej9GkVX8_lkM61 z(c3dEJCjO=_9UARNxG6~t0v2?ehs4u5TN}6p zh)o>t1gE2;0}edrN}=i@*(m9~H2vjAqB!O4qmQVimq0A!uNGM`>z6`;?;`OacAWsx z5o{;}3$GM(rx;uv1_#6nI23AP_4J4##JW(FK@^s_$59DBJf2Q}1P}>H z%*!fIx*xaM5}o23>*|_E;<3VvjsxAV$9unSKOX;*yiC&(Iw5Ea9}wYzc><;CJylmm z=b(T<&@ZZgqO?TmXwOA21OGd5!q&Jyym@n2&YA^M1KQlK0cXBm*PIXEP0*k~g7Q z%y0$2+HBdy^{ugFVl{5^e>&gRo%Q@e{U^mp`Y{TAALxx0W#*o9Ye#3N4z6Umj6k^k zw^y?d+Q!ESdThiSTAA9v5-JQAsNX+-1fjzBo(QYvh0cllqlC;ZQL$}25~YA*LDEL7 zYYAz7+p|!h+V*%ee)Y7z|F*Yu0q^EQ%PyV!^9_Q~={Ve*(4xE(79}8%dh?p%6}x<+ zugAY37CSntbH$7g4r8paxH*2>tN7kS z-nH9A&@|^P$`Xf$ll2c;$8SmKyW-dqMMvnA=&nRYkd24|V}2Zc8NapA z;@4j}BWR79yw-}`!6qHA%qAVQsr$_5W7Hl%{Zv$@8z`S1qa=&BpWZ z$2FhWM_%DoE3+0G?1f@@(7#1dv>*tCpu?5Q(@DKV)_q>2@h#UmFsh#5Q_J{#fG&j{zCng=P%V`_Nc0XPzg*gFG*`A zkUn;AV*$81jJlMN>VlLY@dR*7y<+DyvGY})_toU&WQ6cAv44Z+erxyr7^ z`b+Z%_3vz}&EmxGL=KHgTAtH;X++<`{xb_jpUkRzFe%22en@nf`emElGw@13xE6IY{PMtD-Oyw_!8|t+%hLI>;~8B;wE-|KKg2iT zHyz6;*Bf~G63lSGJ5ph8*;Jq&riJ&(VJhq7( z1TCZg|0k1y|Nru6c*Q$*{s{W4Aj^C9egGds8M76{ERUAi<9(MnFUSS)Ng{3<%7 z2M>VE{e8>i@6hwE_d(5csAe06X(Ne}0wBDkOvy}8NzMV({i&y(VjFtAT&OBBfGzAW zZ3Se}I8TB=@JN>y9OngjBHOD4=X)Gsb4SP^|GsFj0dVmRAp;g@;6euaf0=bg4mV)_ zM{RBG{g!FkwyK`}X(_|6pg3AN+QzodGBNk9I_AUIPTzt6T#a&E-iglb4KpDC=M^52 zfLu5P;5r%w?+}2mGEg13GNOLMltwVdh-EkpV!W#%21ni)*;@#}@t`8rrh=2xAOJ6g z?k#!{OeO^2+|1u2NFapY%VJPUGXMd2slCo`g#cWlfR2*aJ5WbciSNhKm-FDS?Zw5# z5P(an2fo~Z0&qKcQVjuARB+WGt8ivA1>Hw^XKTPmDo45+7Tcdpoc9v#J+$?34Dpj7 zu%G@WsaY6$Wd?i$H-nnD2LkX62*7oI06h2=+!X@wjAXfQ z6asLr;WEVFEiDlP{Yu0@GwT6u!Uk=s0YD22ZMGXHC^OlqQ(WFEachSV`mTbovWR&A ztT1aUzjNS@EYudA`mSu~YiLg&`kHDk{8HfQ&=`ipj<8-_XEV&0&3uSh>XY3O_YNrl zN`ViJDCAP|E{k$wH+bJXHzW?f*Ny*P3o<>_(_Ht{r*FZ@5jF{@d$qNH^?PLy6=Uov zU6ZlmcZ>{}q_L`QP2%@45DWcK^tR4*ZbMRLYnSw7w4I-9-9-fCn9TV_heb=zl+=Zb zN)*kSj$Q!)^%W2)9+u<*whN{$BDcY7OVn&Nl=Z$xKawD zSie+L89WI(OCYyD#6~egTJjOgMmY<2ftF-^jN)1X2uuKS1lm5uB2Xlq{<{zqivEx8 ziPDi3kvI^>2AGlxW(Sc^yXXr&2ta#X8+rwRD3nCe8kM&)X-@0^cb$&QbH!vG5l%rHkExBger7=n=ys0E#ZLm7ThNLp!S zy0}5;0ziP_zHQa6u6Wnpu(1ssK5v=>zp4?cXMg0PCmLR z-nB{KEkLz1Dx?b!v!LU1;=rBQnt{t^s!5%)drJ|f4JZBq)EDA{N!7s`yC-#Yf0F!Q z@q;B94~TtFCc{!r>Qrp>uf!EDv>~nnYw|$_(o{xNs(X!8r)jM4=K8+nN?;d+uV23o z31~hrz~2uae)U&{5$h0vH<*tReh6ZBP}Ud8tM-GMeomC3RSfbcBp&itkO6%?zXZMC}Q>@*)MAY5wKvms~R@OR@eBF~I z?aIK%&L{IW-mwY3Xs#p!)o;GUJcn``i}sBEKPodVb=OvHn|T~%H|=Cr_#1BU6k_k? z-GC01eC$eCh0fPtYdyxl&v~Gxyz@WJc|kyslBs_amZR6BKGXHWVRYQFxlkRz`%Fy&!co=379r}pMQKeH zp(U?sfou+({EU9qO(DV&a#!}Yvtxk&0BPOh-#b~GWl@(HREL04`t1%o2if{?0p42# zE8=L_p3HoZkn&jIgoqkbQ-3w%JKyCZz9@(f&FVJOy<#pDCXo@rzAd$)EbPk>x$w^x z?a&_dR{_HIE9>gKKm?wLdLK@}{fD6b4d-_mTaGRFxOt2lD9!>UWX8fh$qu~-;UAEa zih==GADe(kCMtpIqvk9q)7?WZSbO@NjyWVznbjQYNEb+20w#lOfn74%=1Wtyh2hYP zzc-NBKd(f9EIR$EHgHN5f+FJO$!X(m@0)2+fymDTPADYxCL5ry!G1ioyY1{&x~ybJ z_$YQ75>AxXc15LEE1R*Cz%Ptne4};3HmE}Tm2KHT^T!ZuO6uznGc~#}n{mof zLLJFUKQe(vW+CL!FvlW;y=DZ^xryN5r3fz%B~@^I=zpV4p631ouRz;3-w^QCHS`nx z*@B_LO&cy04Bq&)s$bJ-D1SoaznbI`dkY1g1>*2)K>T2|WWSlb1|;gaE=T$LGF5+? zsvlNA`PNw}3TA?eSx?2s!-LWTFFp+EBG2msL<3~KQOYj%Er7}ZI`8O#-@(5p&#)fG zKG|@_!O+hypjU6Jl}it#HOa0+ipoLhA$&~(kf*~dbnJq1Jx-6{s@~aJslQ92dG!oV zhmxfGlAr*RcdEE}9=rc01Hig>{#Ke?oN_lrJGAF|iT?BQ{Tk_|V{y$}{SVjgJL7=N zi+L_#%`s^)!pzky8E znT_c)9s=wtE3{@Zh{y6H#{N6zP#ZC%?}OZtw?s`89V zEy_LzHE?0A<4@wIzB*#~=4pKVxyjlQ5g|gus^jZC4{hMNoWV-!W-x)TY{aeb6@mBA z641biJ%TxtkENd77*PLEQITUw@pl0g2coEkjsDKcit0#|i2+%WNn^#$+^qJIQ6D}o zGeoqaX2(V3v2p`pE=KydM^s{d=~pls5jnSHXhLF((*oLLM1`W-FS|KX(kr-`LNEhy z%-fR+JSRb{=YWX5)M&)I7g|b?T2*#%2NLE;fdjpvLq7CBsW1F>zLMP5+2V~UJ-2Vc zAI131fF)V>JwJ581E(_5-^Q4Af{j77=jT-;c%9p~FN4;j>Avh}wV%ABb-fyU2oH93 zSi7%-!WVW3iJhrb)T?6pE1vu%4y%ZhM{2s{4GH?&i|AZdt7Gs&IjA>H$O(aUX1Z%y zy)~^HbYAxc(p+AB7Whusy@e#wK`Qn#C`%O;HyZI-63pV}w&adIZ9X@#B!0krAr{p<+F z1GqBE%5c@iH|I*nSK_1B`K1v>wZ`My0_Q9%rje9dK$|eKgeMP=fQn9PkIk4Q(;D^m z=OYqkgs0E1Xzvikbo#SQ8aezX{Cr7Aa20kIN~dX_-ljnCIG!JOpTOOB%wb579m}x} zUe}X6f3LB-ZNxA*Y7itdei$I6Q}�*Tda67dnCuUD)iWDYv1xIZ65wN3FUmPx&gY zvCe;J^yXr6RmpZ*)21+6R$Si9qkRd&;oGZlSv-h`fd*b0XlEtX+D~ws%Ew+1jy`H0 zabP1(1CkqJ)rKN+VE1DNz=-+3rPjr~Vy~0@SxkYcmX<8s)~#aK;|jgn6yG#smsvzS zDR!q?q9!zOQd~FcK+tIYq}4-#15xUBcmv!}lQz8JjPyz^2FePLGta4+v+2Q##USFX zQ_f^&+QW5X`a3*toYi+}$PMJfVVDlw_LyLBz9{^p@Y8=h?)dNs;n*bVdz5KLdT6Vv z0@FpR&$1?Vl9M}pCp($mvSNnC&1-Kb1F@j`Rni*Kv2*OxXbdCz)IOUY{CqiU=46aX}q^zKG(b2+P9IANg%Sk*N1$@1+B z%{>uOw%H<|&jM#_{#W{2_b-u-Khn?E3_d>gsM*pkcf4)e%vFADIwL!1$-62FSK~@P z&-Zvl#s|xr)BUuAMxsg+vOMIGTzM9pka*fv85TQ{rp+GqNNRSD(wV_h^3D-Bn8RY2 zM)#!Q<6$Pg`&oij391i*u9G8hIG4iZr)nGjh;qi=1Vh8yRhCp{6ddL4jm~ zkQ|pt;tR!LA%ae+Uu9rL&Oq;6t-KbSGHX7?qQg`{lZ?`?{|CobUC$zHwMw=QNog z(_H|yR|sd^jCkK>3CPCy!FE}qimWi@ACK|U+&39cL_|bR{JgexuDm`BcRtA|a+P?b zsMogCAL}Rdnrv%flqrNGAKsvFl?O~&S?^t`1z4{tCkzbFqD8$h7Loa#EAd_^ViXYB zQ{5Tswv-3j;rRm>Y^#vN0fxs}eg2(d=hgyOoV$KR^?_Z`c2ZQ`Wa)Lp1t<<#v^oh8 zfnr?fmM4JDjUkHcevoaPxe6QNI}L*={wH+1M|X+s03Y=OjpCEj_pJC?8RG78pC0<# zA6dV8@Y^MEsqUia4T9PuC9=*oC>ym)>;?9-{6=lFNnxlG%t9;FqfVh<1=p&5P}AEW zqDT!f=416e#rHh|SGk_+8uu?^F`rZ!)@K9C^jHXWHg#KSfWOFMf`!f!+KS>0j{##e z*B6F#;DET&9Jt;)I3He2>Y>PLKhU-jF0G+4&m64)`X~L|9(ybJt01r1({z z{3eVkN?yN6UDMoA=WCeDQ;XeDbj;QD7lx)Jsla*nx)!5{p zrFjogoB+F6RDfOVF&82iGj)t8`U=6DmNP`G(hYpqgIAYrb(t*}fT~bP0!J$Fi&Z%` zaBdV0BXTfTCva?Wso7#Oz}+gHmqHnpp7RxS!@Gpm`t?0IHs*Uk@cyCN#Bhbtq>|VA z;cx-0XTbhCn5LBb7d=qHA>wp;J@s9`oaTrGw|ag3IhuO%enXTOxmdvE#15WaJjMrIsgOnyY|nw0USwO=*X+-TKwLnOj@24&{(VUb&=YQLy)e96yU z4Bos)NM4bejzFjoS2jt=5d^-41hDJdZrTp@MQw zJc>O$BCB%oW4L^QP?=r8_ikaK{h{cIp_~bM*7Q&T0mNVHf$r==TF45y@gbJL*dQ*} zugpD+xvR?5*+<%|_oY=@%vk~rPMqKq$w2j4Y1dwl&AU+vZe8c!)OTa9R^M22{W;D( z*ul>UC;p&%$COi!mX`eoeWg8PUsPXBw4i^qvRdQ4Asjryp_V`bnWp}mWTPY;?9U8V-!0r0hh<%ZhDR?`zb$*QsGtSyy<=TMB)h>ftAv_W8 z+n!>WqpB;a9`IG)gfIbWeCtB!Xyi^>-#oo#e~mLXesCG~@CrM`dk~@Y_TPUA1_~YY z&h@t@5#N@Oi%YZjR>)4a38k);D_ZRK&*8-lPW=&1JorZ?d3%!t_9Q{G(BIRRZL5$i zRSn)s6~Aptf*LGT|MK4ct?`CljsFUt_(^^NqDXWuFU84;UQJ$4jQtUA-o8Z~`x0&@ zc#MTK&h;Wi@cwGVW3%*Sv_?6c5qzP3j@uK!wUD^C;012~yOi{>Sv}-8?+wYX9eGJNnVe_jDE< z%m3{?)QK$IwL$MKGgXe>U8Jyv;n&|G36*t|*d0zmq4EArdh@USUB`WOfXCPO4g~L6 zl4}s?A?}YYK1+9>Rm|^9O6Z_H&ac1C2{?f zd}fQgjq9rmpMDI%ehX(~iOS8USORBDJaL8_0nPCJA7PiRA4VU~-QQNWC)$52io7Pw z=nVACGAS&_fbmDC&a)O}jtIB(-73<{NQ*__xMQ);*W^U@6$))0Vdf&G{DKHeR}6<^ z{al$fHgC8q?!mrm00)v1#+j^*HHI+EnqF!=ACyQ4cvHHC;;25qgsSJpkB6o>UeFCq zey8tNI#4HShZ8Sb3xLWA&wkUiOYFNVA)RMxziL;g+1Z;(>oI&JhRDuu5~rT%LnTag&L*=-oG9JxF}zu9oNeGI8rB(F2nr<62Km%^hzfuEh}jGgX7v z&QKX49ob(c$%mr$+A$y7#F7~XBr{V+mjYe*7Iz(xZt1nP%eK1P;0>)lHmnp5qTcU> zak^#4sWFT9tLX6$#t5TDxW_b6ucq(4P)d!d-E~>r5=#u`dz}T5r_i>6p5C73_lR?9 z#f;kEBm`|>2Fuks3#J)wqT)+~K`xK}}c}F(T&*Ue?MOf<_VVMQy*`ighIb|YYf2J~&1DUF}r&R7_JR5Qv1M3x7 zjgO)QL*41tzeJZ7MCDc~bB`s21at?m?Ya9Cs;|GJ>VieNP~zF>RtK)e>R@}6)m$HnChJX9{h978=Tk}} zJauC8ox8cN7nL&tyT%HY(B>#}_P0&fZ1EX*L=_t?cI*|JZ;7x5W!wQIOTPb7J5dW| z<~`xap_J>Won~pjf2C^Z?n!R;(M24`=VA8C$&@iMD#hVv1lOMZ6J38dd;vcNQuC{}vrto=7iK@;Bdk=-OCIgZ^H>wolpr}v);@3s^QiO1BC zZ(z$UiwEih$3SoYIe*pG71#mV{V~7D5qPkJ8N0cPE(q3onN4;3ko8`>Y)tPf(D#PI z`_9?9Whp*+{N2r>@zo|7;DSa|VT*Gh`xMk9-ur1;_7X_!`moxL6Um~y+ZDM#5!lKg zDB?60RrfSjUtb<8c+b+%YaZw|{#yG}j^jIt^FNh7Fgj-&m&FD3E+nc|Ux$D5Rr+pO zcQ5_DmXp){H4ZRMDs7{1{AQWLC(=<)shpH#;m1pI?j~-;JCJGe)7R{;MT>2Fh3@6R zIx85yEwjp}#)K zAL_~-Jtp@i3y((KyD72nrhs5NbCIt9JFf4VrcZ2{c!nzNU$&os=J;Qo>N?Z zye7BU7w4WA4>JfY6A!G3w>~Dy#1CoQS0%*nQ!Xb|w~napDwK+26}iu&@w3U=B*9F| z>W;Q9SQYHkcN{)Yj3fk6Zb-+lupq<2`4#~wUW6s9v zJ0lU&?gnaB&xROn2iNcQA5NAj4jed)Qwf+NBLgTS;QcKWvE^5sJ9ia39ZW)CM3GF? zoz|LV?LAPlq&Kr&sQqT7y8F1u=+5^#6;2?V%b-idl?yae{wA%QpA85v;q5X zpy4{Fc6ZW$QSURaf`V%2T1jv$<6o-D{y``l+IYvCy7M@76PWfYu(}OuACyW(T}k|Z zQO5ZocQuCZe9$j)AlSTcJQY&wfgy}eJw>^xd|)c`Bi_dH97O<4%AAX`DdlBSa~kh`||{ z1%V~X0+dMBAO$bt=zY|Rc=STJh zQiVs~2Yg#tD2aLU!)4K_Xncoqib+tuF6SruT$F)5$3xW zp{%!n<|EAkM#YRJh=H&YG4ev4SW^fv6>d~DPVy6$pal8d7vF$Brfe{ZVK+D-q&_T? z8JwrJ3)p9gQ<@igp=`8^`0>FJ2V^NV%~N|kX}G0eWA#9n3auA*3T0K-9#W4(A|TS0 z->F@LfKCL~oWU4ixR4V_(j=mr1%|hu@)48U*LHWlE7vtiF`I}{VTd>waTt-JA5D88 zgwTMU7SC1Ec#LBo5r(nYgj3Ryy+0|IdQ@1Km2=03b!7PFRpi|?A&s&L{{}j(ADY)Y z9N=%I)8Oxld>@p^&Lse`pV>7RcR+6FH*LUtc6?Q4*G_3SkRUOX%%JaWh`18iW&I7C z)Vmj15xXB!{OT>`Zkmf^%H2@%R=J)XA?XK1B6+c@$Az^^!aFPstFO8Oo3hi-){YFRD?eQ{%GX zTeDS-hyqFEzfAK(#Y}Qw0oOVPa* zQPBaKUL7$VT_RouTx&4Y4fUV9^z0Y+%|vBSJwhnvNr9POM2foZ+<{B-l|hH5D&TbmMTx&h3gz8FPQdXu7qXk_N- z!l>7#cl*m?SqKx5=#)IDUoaJP;h({>$@0Hv@R%r4mpHwl6TD2Eo)&iBJgnt8TTUg9*Z(!W&9Q*EO4M8B{w>X(uH z{OMxfyUq~82#K30h)(pcpDvXJ2kXO`1f95O^yxGyE=n}4Of;Nl)+ZqnYEcTx%0`*Ubp7ftFP)V@?0OD$x+aW7bYm%vv4E|9slWQr;?-U1h!+g8J5OE55A0 zulYrZ#q~r`nE1L#5Cbn$nAk0vF1;D(Z`UE-Y}%qyi+DBx&-Ov0Vdg;?+B7k(eYP+R zF3}kz6dQHLSshuDXvl^+Oj~N$p)gNohkeFVabayZ#ZwM4=aF^vH?}i(97Bz`4%Kgm zfd#|yt&RmS8WtMqYI;?;3krRShF=8ar#i%gpWxO#bvosNV%bK}E=FV4AYB6eTY}o0 z*6pXLfi2G#B5EoC^yGpSfxnP095}#a#?lre=LGx-&4H{-m^+g|$h;63-jTn6-yBLv zU>J7jNVu8>e~K_~+rrEvs0<5-PKzb<3!7d9C50c*)l0mtZc*{hL@4EcX-}4^^>|$F zcR(=&l_cr&ju8NDU0dEh*1W_1L8p-_Ko2!BdkmIEMtdsNzDgRYwbpqH=n@XZnq?Pa za+fhv_i|rD>Ojwvg_iK?*#~(bCxkhJslx=GF7(lcfJ)|d8uhQhS?l0ia}T}+bdUKwGzZYR?PympH8inTi+93;?+69Qa6V#Puw(kq#f833<1Z3f+ma(oIuF+q z;5yc(GC36pV6-8U4=R+8%!7$H8?}m5U|L_Sb%vG9tlD5!GY`F$jFxR-r%{1ATZ|So zIG=R}#ifOrLRi^IR>$FbDzzBq^a&4kWN`aB^e@rChtc}nKP}WN(p;ERXa@|&O>HRVkfW7ipAcCc%Sz%-aSF_QzWOEf6x>@I2n%!xxUmc0~B4FtMmQmnIhAs}417`g2j z>_Zj^^vF(FASkZRv*BQ({h|ehSOiEcpz!+DXm8WT0$E9V=_X~$Xes0PU~VvQkXdlO zTDH?GIQ#74+3>ib*sYvYiz~xmqt`wS8i9rl{|5a5{iA1w=7W^ww{(7}viL0+X6G!{ zl!`Md7-$^z#e&Iq9)6$$eqfz0-?+ph9iWBOkI`Hbkv>eCIV=Ww5@c!xyb!ddrmYxs z+6Y~!VcHtG|Q8T%Qe6{`aVo{%1@ zFQVN>pv@`4WrI>={tjihdGYliFbGWY8B+z~o2K?4w5At9==Rj)NY{mytm1lVeX(2p z3aH@nNjFNphawB)FK8n>xxZk$p*`Fjuof|}uRbb9MhI=Kd|DY`4)njx(a=+&>CNOw z_O@eD`*|cA6r6gKX9H&t3+CH^_710Rh%sGgXm9c>Bv=d4fb@mC@tjzF^y+6%@Wu|P`-o0+)q z9meiezE->wB!@N@EkH2$$PS_r(A^;!hQFO0N%6tzg$g`BPaP1y@S-a3a7ooiR0i0O z1xN*$w?5R9@aMsLkhT38#`VGerwt+PwHUL0dRlM!uwu{~%n^Q;TmUsk3l$2cDSZ3f zgZ0!}ur?uvwet_Ubx+@CHLyrp4PQozkBk|ZKrl|U38@dIvnr_(STwMJAVSb@#$wRU z4f=vPfwI?czqAmxGMGa!V%lxs==|J;iIHsU*CY4BX}K!34;RvN)J)nC69~6B5JAw3 z37!V*B8u&4n+VZ4-CarI`IgXi$kfw6p!q^joYhG4T^FFr@!1wwBdQ(TM+*74!XN6E zfVNEEXcWW-@I$-Ep!tBlbcw&Absq~z5$qD$-bOINv|$Q?X#hJQ>_phWVC<27vd!q2 zEVS%Z!bU^QM6$tp%x6{!BnTI1f(;S_Pa6e|qlUu{KF~3XX&AMN;wIU@QWA7F)v@a93d5;DjUAfl~)%%ZG(Q;{p-s>Rx=hkix*a zqFg+MONy050eU}G;yEm7!k$gM&#b!+B6WlK7c>>3Mj`TC-2l9W69KjW*#O!#f&JV8 z)|`f^md? zO39GFL<LV~|YmqTwB3h~$#ka^Wgz#)L zkWUSWpGpY&P}ph^Ng&k+LLsmcmqH+*y#Uu_Av^3;ZylGk76|?QL8F2_9JKoo>tBV1 z37m`ISvUj%U@g%9QNRdmj|?OX8+IPJVo(~2T4%tXxIb_Thd`Y+PvHxZg~+0hZj_kb zHG$27LPWGepl@JCOlTDi;-;zR$gt>GSR$M~+$Ho>!2&RrEtOtrv?oGn>w*@-oCexl zAHMAvR)|bAm@I7Hn@@OaO6rS7@7??Tx&N57VG%srpFgcHdKGO6Frp<)XoVIUI@n=H zAt7i2-4Kd23Lw&`gsczvDL?k!l|t%C;AFpqGLNwRKu<8TJ;k^^ct)V!pxq6!k8mPk z%#;fTnGHSx2@n}3n6sz-V0}^Ti&R-Pq7XnSL*=iZhPK}U-cY^CYPDYKdM_7cUe3|j z=0E_f&up9rDINo97dlUJiQfm~?8HcFcED5H1QRBVG%<_$_AyiAi#jE&RM!^Ag4k87 zyaezL0N2Zbfv>5b6_-~Uj{pv)(ixG!vE<4i;cE zgk5ktbSIskJd`{5pVnhPrTaMnTF87S3T-?11u+GTGwXZ{1eKEqEefK`o9hhX1%)Q4 zzYUHm=L8Zt3OIMBpq8d^59Bg9LC{BDZLsA%=!rl$crh^8L3;ovF2=#v<4od)Loz%nkI9gM6b{*3l_kldcCrDsJzgwm4nm%{WEuf6 znkwEKfIwTz9)o`jv1(2!~p2aI3<8QqBrQ|Df5R?yJnCDV(irUhZt zs-XtG0gb&@=)YH@5K3%oE$$~ceZe}{e~rS55F*a{8b%k4#=>cQ)K!gqpXm=|1@OKr z2A^V;!JGg1@r#<^b}VC_CM6NREz~MY1`!7}BZOWz-Oy7^y(*1K;|i{C zPMIv<2Y3{GxP4=_&!n&xU1dh4$*)}l>G*&- z#$6A{&Qf9wAX36=5@5Nh+)w~yXaFwkIiXiT$w;WM+C?`?#cAA2)jp^wOeY(hQ2S0m zT4zp(Y0(ZN;5OHo=EJJdU{69$WWMzqQZA6c@$-=WqkTvKZ+5J(J=d&}9ND ztk0rm>K4zU>)YI?Mz1$H#1 z0bIorfR9=*GpJ-}53n5BD?s`^km&#*RAAxyx)W%Zu)aO5LbJx%s=Yc=^8^c$3M97T zEt$g?h2xLn_vUfywzmtsH`8RCv=pdu4Upu)rCW9npW|Psv&+s&{q=k=fbsV=BfMVI zV`UuQFJjZEVT(Bw(wEIcX(`5q<$IVq;>x_S^vk15`DC$nHJ!QuNN$iQU~Bygv-3fB zU^!r1Ju$1QT_vIwx(fm_2Ky)}&(*$SW?)ztg%H|-(=Qez3$sX#7xhGh$_mwHQ~91s zOUAymRkw=jj{RsaWRek*{M*B6gCBe~LT>}Mmh3*C>$ssd*sXHc; zlmHOY(aH)AHw@wZh`y)++R8MBGY~)G4o7geN9fus{)C2|KE?lY8|Xe-semop9OQTb z;PFNM;A7PIh{Ei%boQTL)^4#Txq2H@%lpp*0(yK4k~P4a1*J3kYN~XZodcB9BJBm@ zSE#~l1thBlAj7Z)&_>ff9Y9~xnH&Atr8%R`qyBHiM2|%5npnn%Y!+52)-4{Zz6%w- zs|5S7CQl=AyElN5m8GOvYS>Aj+1FCeJwTjYUDHb5k&vM*P!}-7g67^H6RP(i7o294`g94^CW!X0*>s z)v;{aNCeHY)kTa5&ePg8N=1>`A2*j%v(N+MVY#FEFpa8r_ zZvtvXJ3yngH^uTsO-4g%?_ib(s%9S$d6wrdlUNxm3E<}fW%gbgJpCI4o;Iu}3H1!? zG%V@Nj_i|4S$K`vgg~`o-wg(1?gs?wSP|X;)+JW!E5e3cn6YF=siFY@#WlkP!9*mp zG^htP1Dg~PC>@9Bz1LndkOWlPmhsOU!G9HUoq`(^~+Wg)QN_{W%Mm)`aqJ_{lC z6_SZ`y=@V2ZA%eD{Cfa0+L~hH<7Pn1wzE>kxAt20E5^WmK#2wf=FTuiaOAFb`A`{a zRC_Z)TUTUT4c~c2Z!qipl_HN%9U4q40;4=tNIWRN0@AOef*j(3H&mynmjhHtQ<2vH zAaCdoeKBSn3H$#Y8|x2J{XwcfXw(n8;D=rC|K~1ixO&8Sb^?tztDo^@J1oA--Pa<(nr<`rXZOI~2s||l8PVQZb z``i4a50VPjX{I_gNGa6caKBdcN{k_+Law+oG0P$*U!JQyca<)k2z^^|sR_i^Z8})%&+gWQ(br zX5Ve4$68k1s8m>+12i9-sYQW@GZ*CFx$yer(pB#9B+SbW?VcFGsYrYmu~lP##FYIo z-Ngz=lC;{NP-?<1;=XaI|5U7gWIZxHS&gS;W2yIaRf_4ERy*ERjavsW>z|~gF($TU zdwWf1g4QCz3@*YkSK(h@C&uhudHw45J5S4j;w^B&&(d6nLQTu^kLg__Let{%5O=di zq1XA=@fr zp7nV@bHzGZ@ITZwL(cswZl;PFgR_A|504`ho$1+!+a$K_dXJ4C;Ub0`^ZI)%P_Nvx zNeJA}{*)N%D%(F?&9Z(X9PFvFmnkOJ>s>EZU?w&>FT=vm`_5!rDs-HL`^8kNRM8(p zE%Xm2VFqchJ8)g?{TQ=;q;_Pvg3u1Ci^f!JrUnn2oY{xN@SzAk-a^ff>6INd?P{5; zxUE#QCT|JN7~9`&-=T3|;YUE&-(K@%eir8Ks=)80;}6s>m$)|zy;u3odcw#Ze^*09 zviOA4;`>vVS{4=5b9^haba>~PC^6aNvFU}jWN}5_apejfl_TxVK2Q?hVh_q#HS`jD zCMestbF=?crFK80YUk$l`^XU8L|?2fGjy`iH|VpdLp@x8NiR};4QV!(<*fb7vD zC++HX;qXfWC0czP$vPGrPGJ6lgMLop&YA=At5l2*;qnpxV#UyW%ZM(8?6b?V4ZlK-;?d!ttEK|6Pu>Pk?dVJw(M>Yl=#lF7@Y5`udM>sfhm3&~o z|Eh$V2M?^gOD*o-38nh=TJz~%^0?3~Wg*qj4)_!vL@G>6g6f*wbgflX&!hC__VH~t zR<{>+^eXY!c5lD(vgIN+w6DTVBv^+<jq@wL=kfO11Z>EsxE5X0 z5<5fSuCAFF5YI6)bqoL_mo%9bxYh9i(bJ5tqE2h;)l@w7I_~MhCa!3RpZO`s*dh`% zP;`u`?Ex>iq+bRfj0Ozjzl!&tdIXIA_3wU*;hs+UGROM@m3ynL%p>jS_*@+)-9v@7 zs;bVO`+QRN8>U`BRBt<-thPZ#ssGyDKZ6>$eJGkczE~WKeZALH@kaUUm_0@*e52fr zLoosJH+;|M4S7txZ8Y6)gUORLj*0p8@0Nia;fBOeuBJ~uNKmrie~D{1zEb}3wh#Un D@ewYz literal 0 HcmV?d00001 diff --git a/docs/mrs/umn/en-us_image_0000002380008412.png b/docs/mrs/umn/en-us_image_0000002380008412.png new file mode 100644 index 0000000000000000000000000000000000000000..df8beeabec064481b1f5e9a13946b03a7d05ee69 GIT binary patch literal 264 zcmeAS@N?(olHy`uVBq!ia0vp^0wB!61|;P_|4#%`jKx9jP7LeL$-D$|SkfJR9T^xl z_H+M9WCij$3p^r=85o30K$!7fntTONaIU9|V~B6el#A_4Mwx7$)9 zAMAbqa)tc@=Dx=V_PrO^UbtzJme0ixNL-e(FPyv1?bP0 Hl+XkKzI9>r literal 0 HcmV?d00001 diff --git a/docs/mrs/umn/en-us_image_0000002380310204.png b/docs/mrs/umn/en-us_image_0000002380310204.png new file mode 100644 index 0000000000000000000000000000000000000000..092eae1c88559d8b96d9f8ebbba89aaa109a908d GIT binary patch literal 82117 zcmcfpcUV(d7dH&+s3?Po10yO3u~3`=M5HM#A}SyPcF<6S&>=w}BtQsJP|%U4I8)9g&d?M}OS_r&t_q$;nE4eqeIfZ`-zg4O{=Vlf2(KZQHi_*7Ty`tpGbFKk(HNa^Ogm(z?3hbfaQRi$cna zcg>}4DaA`!EGvf#tqvDbGR>v8!%iK?9+y{(Rj%J}Vs`Y>wWB8g$eEaI`|HAf;b+^n z?~OmaZO8o*QJ0cAkvOZ;m(aRr^4Ez+NN3~~b0%1|eA@e5ZXOjMl$6K*HY*73Sbv>H z@MjFvR3JFPKG&CWtn4xU$BzGZb=(#v{PExAV`0`6C3CLS8*9v_Vvo*eps+LB7h*XN z1FpSB?EY-@)dA(USd#MkwQpQRE^Vx#mp$KCo|3HdH76&ga&|Tg&TYPqnrK!-P0XmF zZs{RuGD~R>NHGV|R}1>%xW+N^)GN})9xQXv3tSxLYX7PtPtS&0xBLmhh+A%jFrYnT zi+@=!Sv9r#Wib?M|7v&pxLQU)oEp#PE%YWvKW~nNYQrCc$&c&4JYoedYV^8Vu@w7S z0?M|@GqoMOOnNguPqJtlBVFrFSM}?dpyXo8G0`jf*l4G{t9t!SFH-YoxjubrgMRUU zO}f{#l}D9#){ayO6!?qe?q_lA#+I9Gr}mq<7R27%&PsLH4uZOCC!x%>v&wI}gSa%U z8lY-ZnHaEeV=8dY8O5%5M&YKCl5;!lk&2zRNW~62B&ov&X>4JSyqSB7*r2FdWu$nj zY6nTR3PUflgdekyUvm)$`W5zuTO9Q2%KfBpQN-SgHgDM8g9etK2#?CFn-9+x4l zdq&d5^6JGeH!zhooo@APn;BLZTmrc}Gf#*vbr~m(P;_t-UmJQry(dQKWqBxUFDSn& zW+@%YKCRq;jq)Da-1Nr=?S4MqO=hb=<-g>{3EiP2aW0&}Lx zq?tvsrY3}ca%fHs9|{U7xK{-2@tN`Y(s4JSwnxn^zy@Sw4hl}0OunZm+#KikDpj%j zwbGz{PPFL?RJ|CPx~$16#s-@PrONXQLEicu0?>82nW8*HPF}AoZT9Gl#cwyI5#$E; znNYT^!i;R;tP$I-3p1c($k``KP&{FXY7hP{v-b6QQo~OAi&#j#tM{QRhJn}t3T9lR~+<_%z%%+7yTZ5z1dn?d{P1=OW11->QDJajX=eS*^0nZUMMhW0Eed|POb zE=%ld<)+v{dt8b-dt%DH1t2r#xY-8uG!vAqH{Id#Xm%IMK-5f0jNo}k2GM%LxcWsG zL2brj#Sl-ajDkT{HRCdP2%|2{DOm)$UA4K1AH#WrY z)T!H0sv8T-q;RXUcT%yOIe{%6F?&NBD+uPO3O?689Z(`q8FH4V*(fqMmKTC&n~ZaD zdKDctbAP*!8*m!UQt06;66}dvfrcEmzQiA#%U|R+PVM>l`RK+S*d92@`_1+Tl7gH} zCoQ6`s5XX@Byv4$8zsNhzpSfocdk^j$NglXbg6KzLE^Tvn!*_Kx?Ud*DKRdlS#|2d zxD$BL3&}E*{FpOt&P$6tAsPz3Qkfd1zCIq;a;W#3b?ER=trK?rA#pI^8w0^?S=UKS zD-IsD6^mK1k>`{B_OF7^fgNisdN!S?r)fp$#la;kQug#IeQcGL_YGA>v7No+gX*|i z(~l{7g3E%FZ}n>Bgo(YRglq>CdqLhnxxa)ci%2KNQivJ6t5S&cj!?F~s3GTBcm`1x zNzEW4l?%EvsE@nyN@J-)G!;>tzMgYEdq}WRDg`^gBUyKjNq8 zS2JO|>Ec2gt&EUC`YM~VZqJ1JPrWRzUi?RlFgbnDKDe77hMgDt;J+9-z}|V_vmvMI zg}iAqUwzI$f8P|@f1+cO?dr**Ek~}Co)+z*i$91MT9HC}j?$IaIwD4-gcLs&yM@{d zAMZW=LH1(!Se{VbN=f=UY#`(gCTtm0_4te1pH8p94yFZz3vI4~YUuQ=7mu)*I zQWJMnOZYycEE-cO9XS}Sn=AI*^$^0${=>o~>8>`b?42P>@_6pF+3Fu61W!!f?!omC z#cAULa!bcewvGI_+gil4KDkB<-Z<%wwvr|9JzsQFO`cJ<+`x&-NC95bKO&q`keAX- z{I*g1&9CO{c*scaQY^0}PX<05eUR1}tvC5^`dj5Y_?yLbf*{o7zg7h7n%HJ0di2rm z;G}B7OpM?i@!R`+T642WgI1Y3utd_>f%dq&6f64Voi>FDN#po6T{82;EMR~_rb)fz z-q#St_CC}V2`bCbnXQwtd=sr+UJ6&9U;X5>zp*J4s>^LE4K_#ZCrVbW5_)5x7ciisb$j!r2E=`-cm@#nA0yxARvdAysTHQomzUe6V*HEnw|EsqB*Vl zLAe=&(^-K2(Tp`FBu^aU+}eLD!Vsy{OG=y=I?d~ftvNYkFnoN*q9aL&KK);G$)m&@ z;x`sIpKr3swBpXXvfN{wOuyXVcYIYX@ZsA7rl}NMY5=Q(Oo$0t&Js+Qma1`1fEQ1& zm(n+@(IdR!=@4!%mXIl6M((8Vw!$CqO{Y~gsZ{e_P^`|rZ&#$PYI}iD<`D#UeFrNG z{#k`kR3ugnHRQa#32*o+?df0Sv&3Z1nHkf=okeKo;d64OzANAa zBZi253zem#5PB+KZwwpVDMaql7QJ5f5z^3NFDW^_~fwTD~s z&esO>eX)IWy29!5G~6Ta9(&zzgw3EeRsG0j8e(JRBP5KHjcuuXJJPd>P&U{bUn)P| zT0iDh&~g<%Sfn;#vEx3tNp50wyif41$9Tk2^Dpv}JV|k#^f2h*>p4FrNTJ8?Kw7a^ z>fz^Lt7k2N#pz`m;H&R~1buRmWP^JQe$?_gM)9&rs(;9GqVAQh)GJ-)T~R-LCIy`$ zL|<&J4W})(VhSwqUXs4~HxzL&;+GRPi3H(_<`anNQZ zx)n0qQ_{}d8_GVxpocO%TE%_m#25qmRjUS^eZsH337z^2)p{s&8Dyo8&sG2hjm*dn z{k76T41;(wWYNW9xg!;BQN{Sl(RGt9%rLAwmiJ5;Wx?@xr>PJHQX^A^W_O7G6)f%Q z@*(~Cv=qz?AIB;1BQ~L2*|$)i&A%OZJUZBk=65a(j!LcN9D6SuT-HU7cxjq(SmSY{Z5Z)1uy5y75Zg+s#>Pr>pK6scne^ z9}pPx!}(qbB2RjKF7JS|V*bV~^KZrZ>f8GUzZ_(*oIbZVM%wjj?(~<}svxfvA1A0O zDR$S2;Pq#L!-f8(Tm^^f)$V(9-r1dZv2U?b$Z1!9#j#m;5K`NqcH)8*(yUoVn9zyR zo*5o?@3K`FAz&z&wg}ov1~r_f*?X;O5NhTaqx^?-1Jfw4WifN8^O-|UV}S}i!JzhH z16-Kk$pxFtcHUlG6Bi}KE%_6WwI0(~L)pm&Gpn2DeTHpKK=v5x@d>_EiuVl{jr zE`7rZK~3@uWvf@D%TL5la*B&1+C?o0x96(5YsOPs>6Ewk>1%OpTk-R%YU&jb1Hwc# zb*T}EC#>wo;nq57)VZn`5p-e*TMETk8oRo_1gG=f7NaihV5Jh9ZbBJf*+Uh%tH~$9 z(+$Hl!%ZKxg>5jSx-W!Y^1fwyi<>AoxGJx;|JL_WPQ&~+ayZHE;sv%asPf=08uG|O zX=~}wi@#fSZ@^LuME&-9QBoh5&Q_M~*OCc4?AM2=>5CGgyYqmsBqmVOH<##ud&kW|Lws~AL^{PII>L>+t8jLperwu1@> ze{Z$!UBxt~$}TC7TJR*kxlZohJo`d#;37Bw5lURPH6%FTwXEl?G5<)?(kr1M1Ins1 zq1GUJ;`Q4x9N1fHbigm+{rKWQQ%*9}qj2}KLwYZi$+H$CGCIE*j75ViH&4EOOdlLK z>yVGBpO5(zn*nKH2X$eP)}e3-`16*)!rcP~Z3cb!h*4yNCOLY-sv-A8%VgFw?RX_^|G#e&d>8yo+d}fSmcM^*@Bk4hUMJUy}w;l&xj{{<&`X?g% zP9A5DbL{(yBuW+&TJ_aJhHHYnQi)~l;ERFmzUz2br!wmNMj89jr7g=}qwbzh&)^ZH z=@lWH+JxOWt@YiJX4CW*{y4mWy8{3GA%Y%C^+sBmfr_h@MBHk0?=iw`Hp^^DB_*zNg%z;Qm;Ot@W@;IrN=c7*9VG*F!84zA65A8!09%;#ARJQ zgDhPnp}Vx2db1&2qJ3eWbb+MG`3C>90v-w*=(Eq|9@;+D>KhF~Lh2LJcuFcOf6AXfR zu7g=-ML^`UNqLD~juE_oRCwG5Y(u^wCkj4hqVHy~ULQIk1|I$}B(oP}d0cjoDVv-S zJ~Zq}>nGQdRRTPo5pTy+MG2mEJOS?|I3$qX0B@~AV5S1`u9FzHtwEm!KS`Qy&e3Da za!1=MCW$Y*?zBHC^TBj6ume`NLwQ1_Pwm zyP896E{zxN=IIRE0EzS6-rcmtLx+W{JbA?{$FLR`Rs#A!H8%hqo;Hn!Ngg3z?T86{ zW!e$+jui&$kCE5MhqSHuS#9qAy#i-{I6+$mA|kzGZer-42zpBa+dZ`(!>rVe*RQ<@ zipczw2Y7(sQ!^d1ke(+QXrfpZ!w~>6YkTbEopYgSB{1$@uTCXD;200&7Rs_-nU{1gx) zOBbaOu9=A8jmU{6XZxJ(aF(W3PL8v~XlnXk0bsU}xtYbH3NQ+*!4nj&Fy?e-{9Fm{ zl!$3qEOB8$#vO2qm86~rR3R!A7vl^+fPa=H3STHD*nRU{OO-w74i+J5GK*JCxr&$y zX#9fHc>lFZfuEL(42l3dH51)7F>oH@It)QQttz1|_kzF5?;$iS-DJegxk@={ixPT$ z+`420CoTc5py+wyvfjWe(x^#Yb#07kQV}PI`p5s7fv(oU_-bG5BIq@1&{y98_1|pL zU+yvzOm}x*=b!`~BR&jrF=`IG$)j8H`z$s4(o-)1H4k+L{Wox&4w%a82fSkE7p>=7 z(~Rd5om}wcL4i76p?}JNS+u+5E~WTUflQfL zu(Ox@XzF{gD|EmompWhsKkPYv70!>?&5zi_NObGCUX)H`wZYGUc^d|P)42nRTNMrv zkU|wi0ES<(*XJ?zq=s%ph@PoQYWkn8Jb$LPE{ku%v(^(5qPv|$rk)RhP zR`u-V1$jk_s<>Rhicf4Fbrw%nFyvf9bx`fPFl!U?sCSouG>{z~#=fclJ3&{tN{nE% z+jGE9OzY49Y%ejlr$iToP>fOS&d^;S&s+gQpfEVLHhCw#V(DMK+QBydxa;d{&1Tn^TI^XWlM zl5!bg#z*D)-{_1|L1~-Nhjc{W#huqaEmEjCqv`L*V19_#jGx{yXZs1N*C>~LHMAw@ z?kDfI9j4d*UI||NoB9?er(X3ICfw(2KN}*yymAb6=)s(cE6lSbRqTT?&T9!S zX?#3q@&x4SJd1iI#(6)Iw~+hD>kM3dYKWq7e&D07x(u;^?9+4+R2M08pKf} zD0fQ=$M^O7WyhqNa_@qT$J*E$89)x)0KL8g27;5r*ul+(k7~Tq%X{@EEL`8UQZ#7M zvt-4U@;Xt>K&?1}SGrZ5`BfeWGY^Ab4_Qbk;gP3DX0b^z{j=c_9jU)18$!KJOrjwek5 zRNY=P{sl#V%vHDIQ^c}0GX@4pE%^p-PS_O3OuCVrbVaMGU`%2jwN-cgHh6EOJ+TaY!@UWzc@7K*?IjP*le%NbdPUi|I=Kl8!B}Qd zTFS)6%(+GN>fRFFbH*zry24S48$PT2tGsW#`0&NMiLl@1f>C`2xjkgs znF)$XGt!TFCgnR<{>8dConLi_uVpITV|Sgx+I*OU34SI<&^-Sy*d*}pwXj#FT^P8< zE;^~kl!8&-Lxgn|9z*HRq=}cs0)?XZY`{ANR=+~w0K?>Bh+2J@q%pIKJ+C1`=-h3H z;xEYmS2XP(Ix{0VnXrlFKi95;z%iDV4e;x-=EpN}8{MYYL(*8|R~i=F1wWr^T7sDtagW8i)EBOe2BZAB#>Yo|=xBQVG>P6~Hml6c zXQQN-#msOr2y!3ktxd(p!gKMj%)M>c@S0Qnh6F2qC~+)Jksh8mL_oMyiDqav4#Zm7 z3lo+MQM$)Cmx)Zq7vvcco1qs;^p*u6YIN~;B|ZEeujm4Oh98w1p8%K=z(|Zg|5y2H zMUTmjx71&GMdW@1oEzDW(bUxR#{aapq!Xmq*k9vsMnMz<=Vkt-0o-(QV8@DviRQ8Q z{P9<<PCbp*Yikl*f7Ej};!dwaFbVOoHFUIz2lH%jLCPU~4RkrnRt0V>{S#6Y#y2 z_yFyHQj!yehLJA#^nMjmeMC#o?!e%GWQd3Hk)NaQUVwQ^`MQo9#7g76<{It`WB36m zMW8@xw|?SH)k8?fbFlV%VPY9J)}$UT8uJ#zay>Ou^w*~f&iTcs{{~eS=4?kv`SM8d zK&Cn5u|fKMsaYJuu8g!KCH~dw9(d1~=NSW2o{1+VT$PRAZ*{>|_{NVaA7k9?)Y?O0 zK?Yh+lz`g*zn#2qtI+qg6iTA2ZhrAzyRV3o-EAKV2VU$6>mT*lUwb}AW*7bGI#9v4 z5-nO%_*9Yjc)+oy!0wbGelzR&tlzsrt(n!%+>Q%&qSqP6oRweo-9K}X%e|&y6R*<( zf)?z~Hf@G&?s4Xq%5x9J$c+|)lP`s_H%^#+i&1*9pD62A=V-U$su}qBnU^ZdB&B8H zMTTx*uxTNvCtcDIrPZNeh#zT+sR{&|JXM!O376~#9J*4|(t|*~+o(H-v}QUYXm6rV zh_>-78!`Z=;cw#s?NX84MPGjqQq1h-l*uAmLD_v7=zF2;EMUh}-|oWHrWkUb)B}AV zKqgb6>|T8?^pzn67Rqih37{9@WMB}^xs(jZ1wb4>nmvtz1fZGq63{o@n?~^Ngdf4e ze`fK{37|LOWH2+FmMBspVZ4!F5V!5D+Fv*0&Il8XaghWSO_*)B5FKJnqOG!kc8N$B zo9=$n{kIW~M4H4-y7;Ys2nB|yMPp@8nA3Lm!uE35pyguapAv}N?Q>d(jZe)Cf4kg6 ziZBts ztmFh{I$bG6A@ zGsC%toZ50bDa0Hd-)YWN`JKRUsCaG6G6sap2ijzuKAsJgBs-Wp=c+$r5b#bGVF?IV zPM8o=@jIbYQ;cBwIh1`fftDGUKzk&y%aC&mZODn%m>G5sW!F??@UnH!#%1WDgH3^@ zaF9S)HW@LIUb-_yE5&!aFkFpaaqL%{SHE`m)*hcO|IcUv#jCTq^1r%jz%n(SQ~7n* zRvV$i{lD@DaO3x$_0Jv=@aA{#*UE0K@9SRiUk(nq@$2jO|1Tby1MrQX+JPt76Y{#9 zv!bNi+X~@#%T}YSN7*&AM)39*%>>zVxN5DbNk|rhI{?$At>C@2*bk`f+`NN00s~x5 zHBb657}%xn%e%vw&7%-P%0K&)pJl~V+H*gO$ji1GR#Za`R+7Y4IQp|A_)t!J)v9by z%$J&Y-J+PvQtO%|kD)q_y6V3i+3wO7S8vRSe64-E`{db+wPG{;fhk@IcGIMD=|h6+ zn#>7g48+yHu5&q9kxJ(!HN5a=70k8KP+5;Qk6ewmU7wcvZi3Mcr)J=5&Px1U#jouN zkc|t*UG!3F!hxMsg{KNLY3{N6Ut|!?TXm=SM-Ym~?yaT$E66%VZi!r(YcMR40S~BK ztzN&g=d7-X0Xo7iP)xW3#l>Xvmn4r+Z`4AUTi34)L+AJ(BaUNCN5XV;?#P_|(-6hf zF^vhdul7E=wd#&9+QZ=8ox$pvMh(oI4b`1Uq1z$0QXwkEo!OpV_*FBiZyDy$gQU9w zPqyF04GS(D=Y=#DcGu3Tx>uFz-Jqga{zW_KAqpsii948WwakpobHW5vrLn=S^cDW_ z!D!6^d|7=j%%6Tjm5H2NVO*y1%xjEs{nQ!zUdE{!T-@mL6I#W~&Ci;7#f%S(V<^_F zKlNL3zHL_eUzNk3N9{cFL4Ni7Vgf(;G}k0JeY%o4-RoCMGhI}`ULAN_`iBthLC*@4v>NE{dneO=a z9aWB`rj)QGF>E!v5?8Z(qDWBt-E_S*TEzo(tS$|mBjQ)mE=CYiuRFFPr6>`qz;A;K|Ya&rw zci${-P>qoeO`EgwTf+R=5VEV);i#3mNU{f*vCzhiN2`kP=)p($IWn#{{m9qGeZ^1r zC&WSTY6#O^0wrmW&9}Nc3M=eK`h$HMrUUYnaT2cdw)|temRq z{wQ*9a zH-4!#1pEZEmu+_U;A%GwvOf7{oYHwEomFv78*8w9WQIF2)GX6m?>E@A-ki$WsD0`A zB@K96Y8@kt25;?)3!s>bW~gm2+>f9|9X*S*9^4Spt(9#Nk(rfLF0TBpluOdpQlJi zjzIL0S&PYFxSDj)G4Fs{mj^0SxYFs8gJ7<(>KP)`wPx^iTQg1%t%K&ZVFucITn%Dx!twUk!CO*G>NSN@BglX!k1 zr)m7ym62YbiTbvSR1QV0rDBjN#rA}q2YAv-bM2N*2=|jY(z~&qk0&ouaFtDt(-!Ua z(0hs-!J^zArjC1m0s<3)^}E!|83NE2Mf3M?pFw>Rr8|M%VDhY^u;m|R$%vjuCsiMlW-)W$x{VfL|a|;E6M0wQ6t4zVpEpS z5rraG^|(;+yqk46FWq(Mt#9j32Z|YFXMRaX1!w1$18rPoGP~uco)bgHRJozHoAO8N z3hBmh$dWwRQ;{eC-iPYNTW$@()y=5hkD`)7x=UCqL>YZTwrQ8GSmnxsT!UT~b*4Cd zIl0I4_#T38%@ng1N=_g0qSGFPlW053t2hV!l)00M5&SPHVoCK2+OlHTxoOcSv~w;} z>nOEZu%@E1Q$g#ClXrEwGllGMWBg@uKmD75opdh=Kiw);yk6)<4M*mHZFMEE||w8VfbQEx~Z z9^-tg@1mx9$!zW5uQr16ijn< z>TLJxY1tSJ&j+`U-fM$FJ53d*745CK*tz7w3gi;`-&Lg`+eAjb4+cOf9`YsW4@|#V zXg~0_^HW7abc<}(j2g^?Z~ZFB;9?o<&OnFGclA35SI%;iMesg;eiiZPnSE`AEa5Rj zcTXn5e*IehYU|5zYAsAcFcIH?i<@*QYmxqfQ1+9bDVjB!Im#S3JXCdPIR$EY#Zm4kItq=Ahe{^Aq*LJj0jk2ejii zbA$VvdqP9E-5W3tV=qs8*-AYfFv``K|1xCp&6N?xf4u$n9dLeJ`N1N~_y){p zj_rsRC|2{av)|wIFG~l<6BBKAy9b_?t@G-*6yO!+7gzqT7f3eWDOG>KBcRp;=cl4o zKn|Jibl^=ZpXKZ#y9Y!aRMBQ?yMa+)({!om+ch!klNsrL7iP=O*}s<^9~I<-dN+K$ zLQXZn!X`(hu0*?kTAvS}rVa>?XnRQ7S$#K?ej_$rtgzwNpN~ab)u$YN*il$~IQ+(w zW3R+KWqmw*_LHQ;)uk?@!)i4P${enb*VafKeO3`tkmPXm*4q{1n0GHmiG%8dTqKc` z%mNL@htu6FWzZL|h?n3wk@Mf$(|Ju@YL!|{%@=kD9q7y<#(c6T1y!kvW@)mF>!@RD zoie24?(zFB{jUDJ(ZmSqMV#l6x?A! z1>NN2c!QK}x>$}>XvWcrS1S(9efylJz!MLKs*bvwXb;gK~-%O4o03VP6@Jwfw5qB-IdzOIV*IV6p6ffC0!&M z9h6oEO+c%@OVSPhq}ku)var6Nh&`+8^7 zt4hU$3K&M!;n##q^~W>iwrs@l<47YQvuQl%bQcJWcR0+fsB2AgBX2Pkek(g|D#Q%i#uzdddit1lR{H<``k@rM*LZ7Z0oRd>Ti@+&q@)CcgJyf=e|&oJqPMbc z;BMKHVkdr1*l2fX>d!6GFmUApcHew^-AyRyqXb*%Cx0a9fx10n_0xVy2Yv$u>P|%HEYvg>W^?1Sep+9H^hE^6fg~Bu?z4A-NL^W3*^?m`6 z*WXhY+@Ngnq(FiQq2rwmU>&5+64iWdBF`>G(_5 zTUv*9Q*MMiE7R^kx8o0q;6Hz;XHj-rC|RZ({6xn*{Z4p~%Xh-{&qzAr&q%`aYxY$F z8Z|(PxJ69U@&EnjitVOZD|8i=D%W2D)SPkxYKT;aj^T!)Vu^7NbXOlqsIO**|KyO; zX5F;E_vfsqC7ra@fmzFht6U`>kPNQ%Q6g@rTc+v#f>Im7mDSx`l;f^px@1J|?*F4y z5BkXeMd?upOtB5F-38Zf-Uq(r2)a5Tp=g0%E{v0Y66EtS%K5j#NN2G-?MlNM)bm1r z{E;FpQt&)-*PsXfH<+{|Ak1h=ggMiwHHb-3`?YZvpc{2?_sAMEaZ-Z7cY8s zTA!Cu-&2;rI#W>j@no!F8E+Ohi#XKp0Dc4f!U8}~|j zzl?=6z@!O{7bF4RVTVjQFG@QCfVuqB5IWx5eyXwY@xh;i@9z(cdrUi%&jT>`?0zfz zOBWmOZiT+MR~&lcK~=l9z_I!#uNRFU7ZwT5tjimf=eR~KB4WT{~USxUA3vKmAHt<{y%(Nnl7*s>3gbRT{7YS_lPu-%zq=g zkQdlMci80^UX%dnZPNeA+SWFfmlnYpQH2RqVPGPlOW_5eHU6*J+&w)0mg+lt{A*j} zE^20(Fu_&IH~p;7aSUVkPofSf?*aC!nTDiCM2Erz&JZ6?)0!EG1@H<#2ZRf6`3v!= zpZBY${O>EF16yCcjC?Yr2GlxrQ`>F-^aX)K^#1>5--3=X<$&2aS6%!(o6WmKe@-5@ zcgwbz0>bDzJpn&}NI3WZGClC*!ce%hFaCGJa~D5AqNHdUvk~t0pK}O_d?#>=3gRCK zyn4#_0`o8SZhdF(G{7G2_o{{rVrne$ug;sBgwmXhUwd)1pM-R!&x~JT2aWKD z=acA{ezHu%A;l4%&2#{pw@eXFZU3Jd@UO02WdkGIkIq~^a#>ZzUpkF2LJ#7rR^n~9 z!1P~!;#`75XsOjs3|W6AcwS+hb43b{ifXty4*wjgNROuw&fQn0;j~1m0J`uzig+me zCp9xx{|M%thz=-D7~619-;k`)?v90PV$&r&DL=^>)S($2CrGZ4(X@c z<@54}JP{ZX&^wqC?+bbmYmaTB?8-kN{ateKb_h!70*Hce9XfTqk2XZ1X-mjAdgs@ zNxc9Ri(|;yw$mduCKCgk@AzHJK(h`>x1E!fdR~lO>Awl@M~8f>VRUG+Gwh2-5}=TD zf7I|=$Iz-35znUu*2su~D#%0(I4S!vMx00ras5Kok+6UfC zZqjpOb7G*YP8L;_mqacmP(8sBhWPS)#>jQvy4yWjbpU%-%Z#oL9;_LcsIZcF0G^+B z=172uuPSvwh>^|G=M{^6x7Rb!zVtwjgjm{=U`gJU{?886X3S`rE6qE2wVcO_NkeXK zoXDkl$H=J@u)&wkr0^yWkmwtlB)UY*5kGLqW_PkNZJhWr13m5cKck$8P??c^e74CdQ%lVZCX0C6i{ct<_T6571>z;{{- zU*e8l7++@k9_HD?Ki{e;Y!v1+idJB>&cP|g3e)U=q|^M-Zy3-VGU+zC63=gg!Nd_(6Eb z$#=SEYX=MOA^Zy2X!@B!qzyw`CoY4!=~eG3TA^7GKS?Dkf+MI+Kp#of(iVva2M@wD zk8yVBek-f8GVp1kuLknh-w;`TD}%I7gOE>jZWYiuI(3W_h&Ofh^VVlHu%q0&_?_UO zA^nAPQx{ync#i1!!_9YSgoJd5*J$UEux=3v@y zS^AsV#HFCw=P=cf*A^Cq$R!VI2P9B~T8#R7ms6B823{>p&>}ur6q9|fMIsxU7sn_~ z17M%4>s9S=L)N`Qye2!IJ}<%^`kb|nebo~*2#$0^bE^DZuht}|>Jj8p0%g=B5oV`T zMM$~rk#ON=^F2jP^~^W^I%pt12n>FfPUqX)0D4Dn8xm+R5OD%`ITX%Nk4Z=2i=J;D zy8`s+gN9hz*ry+k&4lP|Mw|qp1BUn!)BhRN`wwO%3`2-+UwGC3*r0O)-vO%tecJp2jL@UZNbPE+*t6ZPjCqHQQ;I#}X=~?8` z-s_s9^U!IPgSHDDlW;GgPI=Nl=9>#|1~(nuG-?b&3Xw9Ozl1Tey36fY1Pk`FuPhy5 zf^Kp*%m{YVzTsOIBaY?Rp)fPdwOMR~tDzC5?*SN_aXZvZwr+G^?lHU`&S@b`6W^&f zleT$5Aa=cWd7>Q6Q_SHi%-B_V6ry>Sc8r>Ub#U%m;SoNY!PaJ1l8dQowW=yCncH*N z913)(V9ueYYd-kZlX4}}?dak+n85ojz8qKYzD*CLqCZdO@N-$J3nnJ2I91K8s$j0a z^jYeUfZ}0DrtS~5kurMWFmfDowsMGmi#lR%Hc%ycrj?r5Ca?gV_~2KCJ+&6vIY^3m z8VCPeoU|Z0fbLHX7SvR%!YwupGuO__uK)+RUe0g0f(O>sTS`GkQrE%fHElqqh58XER!=_S=~GmT&EgwFQI!X6T;DA|`3g;Ev%j2mtiaaF~9Xf8y0aMO6X> zL>LXZV53RQfC%=y6(y{QU0?MBqBFo$q(U2R-TvZ8f!aF_j>oTN(~ z(o;n6T8~waW}xG^r)%4dQw+3^*FPOU0-W=8U2lyO_Fl-)ic`zRF(KJvC(JxrD|DXN zjmuK*<>Rk^qfgyAauu)6b;U9ag3(egyK{K=&K__5Oq%V7deRCjf&ff!a6m{6`lRHU zuSZVnlT~C%Wz)~7w2CD*im?HHP>!{i4IVStoRPuS2->39w%XNX6>A(#CDwSG^NI`F zzT@aj5nuTeqSrVfku?MyBEexJdjvF%nE~U3NCgMZ)Y3E+P!Vo0+qz37=2WR6UXS23 z?01trKh`h{!B$Y_Ez3XsZHSt7>!K^0+^&a$%9uyX;vSaA5%|$H@qKSR|M?j!-d{!h zwPi|S3Q#w^_h&CQILv6=PJ~-$nR+j>q0# z>3NKOY{6g9fDI?ig8$iI?j~1-O?%ZW-{lOhmer`bN+Kf4aBoFau{Q z_k^1KB1K#!j+96f_yYJG!G=6X!m`f}@GYG)vUhK%chl!dC&ga-*Hujvpo6e_Ga-SW zp9OdEKdN!oiU7m+ps@zCP>wELwHqlm#EW)#oqd;izu@ZAC&3Q3*Fz-z!MNy?{Oidu z`#k(9 z&#M(~)WK+NoLxE3(?4oY>auAG`ClpAU*&|&$9JGRw>qa?iY%#=NInc|rRp5X{yI>Zp*BJ4YqPg`e z)ATe&wy!sFQA*qUU%?+eT61Q6Qd|_yqJ2S;E?Tk3T`j9q1x^vVwpOfs-NBFsxgH;@ zD8jQE+sNj>0Vt-sFL#YNa!s z_T|-7UAr2^$~WOz$5Nn17p31EsBjOfk9Fafz(~<=y%edW5(j9d_c@^t9k^m=H3)#b z-0UFLI8?EztIi6BC?d(^sf=QN!NF{nHMp^)-Gze8h7DTa5+*57XUFm9|30Dc8*wTh z;ua+PyZIG`)e^d)Z1m4#uk7v1%wg zt=E68C%!dbnS{e*{;3#*m*ns(R$#h1LWT{s$RQjlvzfBCd=}x`c0lw(h3zGtBdN!f zZV~-L2E`=w@J)4l(q4V;s44H==b*b<`FY4q%K#$jNM)@CK&P7qV8|^gx4^wQZ>fxR z9MuEN!ri+waBl1O8@4?ZH8dMwP>z(TI!9w&E*#zGxbPAKoG@_!Z=B72Go#0t^wIF#Y#2X=EjL1PP_*?;& zi>3%8@B0BZyUj6E*ivmlAUwDNlF^w}_w68! z2)Absn7;;qt$zJ{c-W@>KJy~H`Z#>BaCQ}6^jD=UuhY5&CThe^+ex>SY2QU(Gyp6L zN4st%Rr$g12~dZ`c;V9Xg(pA0d}#LNq9}1EHNk}{G88TZ8~gBPvM0Kn?EdbKhTSn- z=bMnmt_7`|L(emL*Qw`RE+`*8P!Clthv0jm+0+PDI4_R-!L|~U+t`%pT#AH}j^B|y zKKY^6je3S8Eq&9ZTl08Zw&m)*SLrNV>5{VB`qiIm?3Yp`L?8Z<`w%htTfy46C#|09 zy=;iv*#0HI7+Z`!`5}Eas+C^ojvZe0Lsdm+MPDYNeRE;O1KzWpA-uD33Z%bohx*S> zi(2+KATM48ih*}R*_Z3Lb%sOJZSmc^Z!MPXydV1bwnNf>k@bJRNj`COu>S{luzs7x z4#IJN`}U#8KiDL3h?NHJkj`*oDXW5&$U35K7!%j`f^a2(`2@*821PpZ#2tChWlsE6 zMp4Tz9l!1r@Y<2D^sVgD7iSES+JUIP&|T#Yz+#42H_QAyyIKE~ll_Q4En}5ACk)Pf zu@x}bvWl$B&wYT$M=Jx!*Tqx#@ra1ojBub50i@>HH z@w@bc`T|wf0BiZsfheLI7Ww*)Ou9_jdl+Ng%|(~=Ce_cGH`swwmnq&)#nC-4y5TL` zI|?u1m2M2h;$HnSG=9LZGgM9G`LjFHtGemy!KYh!qaNCGU-IeI|3;P7xlV7LB_LNS zv2DgJE|X8}!<1q6qa+UyjRw{ z_SiQD2f7PFywX{#MkjxlhPn}Z4$j7PwWwJEFc#ydD{tw9RN1UIJ_lK<7xCmEmackVEN`lZd4hM*fgdo~ ziZ}k;Wp}U0quDvE%z9qI1M!jz+xp_o4%f2kC3&dFxE=Q@52I_E#fJ-6QQ(u$}QGIbfn z_^JtK-pXc2raow$5VNvd5n*@aDzt$_FJ1Hm$`IlR?Hhjv431uTb@a;rL*AQ*L%sk1 z!#YVhLg}Prt0Pplq6i^LDx&3NjX4q$Gs-f`n3+PUqtL-fvQ(t9jCFe>LMgB;g2Q zV%ce>Vbj)-N7-4*FItoa&uKiKFsgPgJ`47Qai#vTG^d8aM@ns_SBcgTombSVeS5ay z6AUuchLXdeq&frh>sGE3h#G9 z4kTwb*6!QW=1_-anq>FeLw%VZo#iZL&Aly}PFx*vC3&6e}_@c5{!qccb=K@$C_ zIB2XL9_DL@^B4`gf4`t6P7A@4^lQS}=}3?>R3xeCaTVmgSo}z9R_yrWmo{r{ILt#F zA1$%OBl9hMSDvm~2ZrjW)*J0I^t%BjS!tPGI?UbyShXX91Q3#g*&(DCtltW%^38Um z`UeMt#e8C1=NIl0eeNS02&>o;l|(%B&yf>(%1;9kjDL>Cf3H=7%kxVRHPrgD;bgsi z0x)nVmx4yWE zZ})*g{;@k3*NFLuhW)cUN)btjt3P!I%!KtVep-;zKWF0Copc$gf6j#Ec0=~(f3C~y zUjzwjD_5)!x+-Mqy=YS+Us8-&{2Xff9QyFTe9I@?0MQN5?d)ix)0#aaH+l|8T@1hQ zQh#{1gI&@Obix1VBcVK|bkvAV8{r!74}Ql?t0=ROl1cQR(jACCEsgxmM;4H^g>ClN zoSzGsT%4f#T*;5~>*Y~pm!vPg6S-1f?3~?BT*HnpRdl@p!8>7Dk=wws+6I$FvCP>{ z`KWucZNCW;v}VnrG$Ji>?GoeCCNKWxqURqMyA(xY&NulP`Wfvykdu6Hue(VgY}jcn zkUZZYUD1-xlW&sKm!R+_1{%81z75f65;qI8-D~#VWU-yU>C8H$=i}dXMmD~9)E-xbe2k$;^t2sgi8|fO{!A74 zCd@7xSCcfYX;q$htY5ERR6SxUduq%HpYC;Tn~&%8@!|_lN~=%R{!Z^;_b`|yozv%H zg<1{>(A1D$6=`vue@|Ory*y{5D`{I7M`Zo>Y(8Bt(PZpxEPb^))e;A7Ot|BoeOf4c{aWC8x6JKx9Le2Y0R!c0@||WCk6FJU zxk(m&ZW~dW)35&;?&=utQ`lAf``59)@M%6oN44C5GE_ZGxuZlr0s`uVKWjbpIyT*cGPr1+ZWg^AkYS-^AT4aGRYrfFpGxydc9=u?A zYOanh@(Xq^JuIX_>^cQxE~jt*_&PT6otr%UeaFE`LqEObS|&qcEo~~cMR-*{WoL$nZNGn$BleHg*urFNxTe z&S?+Wf%s3LS-op$LnG|mLfKBqL(dWTkAo#OdO9-t&pF?i+-dsXAOUdkRN8xa<+|=O ztIx<)mn<77i})x&d+-$B?7sQZCLbrfbXXG6#eZZ9p;aK725KKskDg+a4eM1j@Q6)5 zb3QB&=12V9i6mWi026{NWBhq+Ay%<|Z#Expiz@oc10F{xIYB^kWZU1(%@{nRM!y>F zCZoH#dK4=&(0e#_^H6Db38%Q!3=z>^k%oT!3E|c+Td0NlYE_u?`y4f<<7($*xj}g5 zCbkrshL^{(`mJe}C(+4s>LNB6t|ry5)Q&fPYaP!Ufle6b=KQJMsxSLUzHU4}Tr;c7 zM)|mra??{#v_XOGz;IZf7}MFEM8$1($G;T`WImIio$Z*ApecToecnEiOuT2Z5Uzc* zVWZHW2u9cQ7+Q#a(MRM&TxWRZ2!@}Arfm4r^y|zP^b{Go5N~v+0OW_iG7VB-Ytr+& zK(R7uN=v5aI^spc0!jyK3GGW!&u(wxpCOG72RHdjI`Z*=3IEx)2c`&aY!wYo% z6-+&=iv25(IMOpTJE7D$<7f$I%}sR*YY^u8{pQNBTRe_u4)vZV`Ly81jT=ydIvMUm z$I<2RWJpein65~1-j(TH04eB)DA6>SwfG@MPn%G*))oQ0S=HA#1Uak;bZb2~ESE9DOP8Gn7_+JR7( z$qX%X}&-cA^l`QhGW5u z2Q?cS%(&-xy2Cx%`YQzr;<|8q5E9rg?n5PL7U2wr{9h?K=RiG>TU{yxVGLsJ{&1)} zTHJ{RX zgko&N0wulrnDR~FdGpf<>EY7ZxJ^ElN1!%y32cMI^|VX&Tdk=kQLS0lWH%d-i2HF{ zjKA?v`B#cSGf2bsD1F9=gPPoDq>(L!4Ye-b{t4C8>+x1FV<)|(_YpshK?QkpSqE8k zF*_5?=6JnR^?KfE0J~=cAo?RNkpVV^3>pG5UF95cErPub^79X?3!>!rtNt2xUNGXo zRpx%WNVzkyv(;bnv?%oaIM^Kk?#SkoKVr?pY_ODCCBcHZ zSMK}?I5C#Hegc3rxfK{>ewq9PD1E|L9G?GaD!-p%|79b5^ys)NQ!N>Gx$1(5WDnr% z*u?Vdoz>LT#6+K{mvh#I4}YlMIs7nZbaXV`?1=1cYObq=rNZ0rs8eQUmz>4;Pf%vL z9Pn^Z@-QffWD^^FK-eDMwlmio>f48QrDYhJ^5grV)j1M*?*>Yt6Qv;?(RsZSI++S)%(cm+FQ;l z^dBSjJUJ2j#7HI5TgjO~DTlq<(uz1URDHJNU5gX0cynm#yoeCIwzlU zB1h&HkvDkPGV=b{Nt?{on%%Rl>>~R-4>yOKs0J7mi@gSZ^FMYaA0J)jUtYn-cbE+{ z8tK3h``OW1`!6Pej}OE|fu)W5r=tU0a%e0;S3)bwS) zLq+OdIxq5E;B}8GhVk==L~j2#hv`4P$9q5Be9+;V^Wc|;3*3QdzfWZQ8!>kKJ{8my zMVok2w_5@o>yOS?{m60F*D;bB(O|aQz}&P?#CtE@eD#oWy9lQI^r0LT4MH|3cKVYe zH!V@MO`nw=UdSs1sK?6&x0oBZXgc5>#KYkl*+xxSI;^dcuRg&NYTLsy>UPrK&jK04 zO6T$BY!|}dDl;s;mN8qLm-K!LtLs<(qQ@8aVdSEy{$vun!9>;e00?Dn_7b~ruUcU}Uhh`5MStI{1iHEc@)ZlrV}Qa==KTDyy$Np#K@=$P8@ zBuSEE{L>nJ-5=>1dD9MXU-_Ui9fzgho0q`f&3NXRKBM~La_pU4u{YH@!LM{S5tbPuZt;u?*(XE?JFN9jUibQMe;N{GuX9=}1mUh%Bm=%buI%I5QZ4OL}8wr-W%!U_ORV?pfRN| z0s-u=w|bBG_%?}lgJZEmZ-Hv4RBAj4F){dQR=A00XA7pj^&`rCTke69bCuG5M~A9% zqDcO)QhUY5I=t)jP_$>pp#g_I@Ix;&o5M~l@;mhgzpbI2bpcs%Pw@hs8uIJ+$!F#5 z@Ywnq7t|d6`FxqVpu9X^{?nJiNXP9`Lg#d!#-rd)=@@wBW+wjJMQ#-95+tzbWR^-b zDkWj|(55yCqpcpKA&&&P%pL5QlJS(himBm0Gw-wqN^QC(vW9kX8*E7S^~WP471MI2 zV$itR2E~Wa4QW>+c)@`32-_nApxPL<^yGCV$GqlT>b-5&rn_WXBCUk8or{|zrycbu zo?9dQnpTo4vi_TWNF$dtZ;F@kX^6kZ9T^0xS?W{0T}!^?I=>@nD7bq%rnR69xvnuL zD}B>NZnI|ZYaZdRa?>94z zB4&e~<2MYY&ZNK15opg59Ux`e6I~7|?100{u0>1ucv5jSY@3JoyFlT>$tUqu86Wm- z1p05Ks}ZgM7agZ=rwTNQb+k#eTH0XW;#5g+vBr~y%BF=-x%HKd;cHNQ+zJ-$@LWA3 z$?lhvoJWGDTmL+Hn&LJoDWskDD}ktIX-e$=l}+89jXKFukF=XToQzZ9VBT0`T>UTH zhQB{;SZf8!`bFcv2EW-Dy74ylG` zC)w$n?cWvSCF$c1sNF>;?53rU2G1(}6$sg}ey`KhE4sm;@KsDP%I5_3{cA8Hn5rSO zxveQ@n=RZlW`ZK%H(pfKp1MAK3F6F81C>h&Bj5hotTdB$X^)1UEEmkyLvXbI5~2dI z>t&lQ0$sM@5}>B?JlV}hdu9h%>P)ficdl&RCh*7@eC&8!TM5$V_}1B9v-jq2DnqgS z(~o#u2+ULLjzN+@IjMY_XXM5%W|OQ+LH$0B=odS5n)P1cH;2M{hkis-zv zuCTNmht(ds?shGddMa*9i;&R-Ofv2rRM^!!^t;r|VU#<9?kpZ}G=*{s>yWB6FBp%! zd|EE<;~sk`(Qdtwr|>J|*oOhY;!OHGO6Dl{=5**kKDye=W{Xh0lX!fPdEF_%s9J9H zL9=obmnrj`PjB+D58$wvM+MV+ZO&!;dcOr*CF6Ix%Od5$$G4s*kOk<>-s%WUSC?qD z@@*Q=mu1pxRv?%BzmnpX>H59O3*g0X;{W`~|30#=`i9Oo3*5e&T8c(nDmX?&Ngukt zS1I!J@#>vh8*_|8M5ffWU2Nf>->iZtJpCKPpyKOds!H-aMmma1%mR0-M9!MVj@y&q zjJ96V&eleCZJDzQl}AX&OiYlm{LZ!tl~&a|FEr&me7F&!P+e!M>YMyAVUwF_buv_? zsoS&e-uS8NWUTFr%FcvM5@}IYt@&o*rBZS#kxq)vUds7qSX1pjTZR53)jjQ(W1nd3 zj`V)%>;+5tD1$}{p|rhqm&jPWzGzd|?!pL|9|_B<2Kud^>|FF17L?E?$Q*HvtaP|VC&=Bsb|J^J3W z�)cPpH0=Pe4(Rc)byv^uZyxdBVgFc9lkdI|i9bYkk`U{tz{IUy_1ogi_IEYiTB7 zi9V8kvfg%zVL%N#_+cO3u|E$nHdV(-;?#G!v8NhNu&cw2K*|RT4_;8v`oCVMXh*HB%xp!HdC?Num80I$>K@6N+NuVssns&IOK};Y_FnufggG> zN*CSrH??3ckO-rIGhNYw;N7oA;F_ovKv2Wip;N)S2xeg1BmI8VK(-Sz3{c7gpaUJR za+xtQdS75@)=S+RgZHU=H`-`f9@R9~c$6;cOBB`jYcR(zT*?cte_$X?N|*VbCG9&m z{T9jWRMY(|Vj+8t$}%e)l5HD;-S8-resX9SH>?wdnwLQF4Cs1+#a&sP?VW}C0#vO7 z<;+`k@!lqNJ2mig-H$a+#f%`k@(_R0Z2WqB)FX-4rlN>wnuHc|Pb>w=0o~w0bQmwp z6WAKW&bb*u{Ny{JdAsM0QeblubeZC4R=Pd$1HE3Bxs10QBCMb@U@VD_`zLZf zr?LvAH$}qATi=e$Et~;-e1Gm;bf;#=8&j;1H);38E^D3pg?U=A@VsEbr>bsO4SBk_ zsEi&1#JSoHkc}bjUrNd=X%#*Du>3THh_o+JRA%&KeX;vo6t!?9OSJG^cJcQu@HTM4 zw@cH4i|nMMu9df3PO`tWXbA^z$1Fut`2O6*Ye&7ID8UNrz`&^5KURwD1yIiQq%_eX z{?VhWe(l#nu;-fZq{sN%s-o|XCLoxjL*gp7J#!JyX_@v*^b#N6Ui`wFLd@(?cjjsw!5UXJFPhmgD1FI3By|JKRBr`+t5FmOQe?R8|A0pH0lmT z3dPAsIAr~42or~!*{Dq=)U3x3OY}J-5-~5wrqidr0Hho~PqVRQMEG z*v@bIrmcf~vO}qJs_1L7C#5TBFvjG4dsuNK(>o5wsrRS7hr&3_)i9cp9St|iWxf-( zYsbWIVs`af6h4$j(Aw%ez2e+C7rqr*wZCX9aj?ek;4X;Yz|d@6-*>p4`0qSbB z)IW+i?4FGTs&s{MKS(B<|le^aseS@g#xg4@(cgc15p*(ba_l!O*XU2<~`_GN66)l`YRK0Cp&FnWIbaH1* zSSjWOiF5JA%>IhCteqXDxz|kgW1U(a6O+It~UBKPdKUDF;|~iL9V(@sUf=| z2&MjXQ1ra_c)dL^#cx(V2Ur+6kwktPclXMlF4^rBL(0=)02&i~cEx~!v{N3(Y^Ap1 zVV*t%Krve43ZnsAq>?_7Ry+(;1iXjYsVlx>w{&W+czD6${96-s=!WdUPiZue4w%~u zt{^Hj4izutIk&y8yK|{8!EGPRFkR-?2@lC|p_ve3wxzt!xBj&_!;ZzR>poPGxx zQuXYFQ-1&@H<9`<+J0_Q0>Zi%^FB96GVxF^36nvKjOMmARU#=tiLoE5QQu;nN`_}G zM(V1W7ql59{qgp<>BGo05l+rr!4-8S&YMA_l3~5XC)L&B$myGEL@q_nhGOE-+E41k z9>hfJ6~VEf?sBTRi*tDKK_&?{S@9};c)*t!Kv6q{(p0jWnA!(nsl_CcsvWEi21&DM zlB$dIkOO6qgt{`&n?4+UO0L8#Dlz}U;PF_G=gy6os1sCM1x}RuKoI6cXR_J!YiD(V z-I4p;V(*`?zBCK~>e1?+?@X@O{S>pXLQGX5;D@yU@HDILk-8H5#0~(@3}-Ll&POz`QOL`~BrTsF<;aKH%jFk<>Yw-n- zh`e=8&jMK8fz5vOSWIlCbcRYn#p~w)bThGfHLjnVJti;gqgN^Z7T? zne9XG8QuC(7%RaS5DJb|3Tq`at!*CLvtwdfMHhLx7)25RB}EUZ_rZtbeG;j8w2+n| zO_(>;PxkAah7)xX#r|?f1xBhBWK$;OV3#T#@T_lf?R{U3ru0hc9XzxS+^r&4u4L0eq(tnKPzITbl%Yg&{kDWa&{obM5{1@d+Z`whg zXZ8_rfM62)>k<<+G|$;Z#ZtzuZ+f*!pry@xa&nXK2PhFv1c$ebYR^V_5(fK0=De7G z?vl0aQ{Y)2U>Ckycn1=g7h@OCknlYZd*Lp==m~149~L=;Sjb1W4(!yKThou4u;R4H zcCe`pC?Hc=yMV?sm3H9c<7rB<4SE;$E<&Iri%Hozxovyd4??%3O5ZO0<+~LF{b|P4 z(G_|YhTtV%AZ(Y!;+q^?maU0y(um**>~DKkYR5Z{Cgl4i8tpglVx1;p&~& z5uRQGv0(i{%XTkb`sH07sS9n6!;igmQ}exa;< zPpVi99!;b?Xf^raAlU_aV0+}GKkTW+kE6`;Y$k|$8QZBTZ>Zur@W(tV?35Xd2 z@5lg0M=vh4YUymc`RjK2oxcZ$lI+HB`7*;#;hCp8PyyNj zNh7a#`Hl|OT^hU9ik9v@-R=dmp5_3Nj zH~rkU1ziEydNCv8z`(SpWr;n{eKF z!3-xuU=fzzy&7zfg~bkR2vk_s`PrSP`SD#U69DEfSP<7SARHQMnd-j!rQ+VOZ$Ln} zT`|iUf5QVC_eiIqW2mbe*3_C%W+j-U^?+Gh3~SeC8oAwwK0O@`CC&`p$6v$ z#dhX2t^G8FAO31ML6UQVRd$?U7oMUbFBikQHStLHDm*hf1Gds4ejQ6~{}5ITWAtkk z*5o5Ir`nZZ=b#X^bZW%13;PHEa`WxLa9p8A=%l-nDK^xcT2LGLqsY*S?J`0Q)Q8KM z)*ghAnOt|Mj!x5MFZ>`$xVA24lU>n_HazXPy^ zMGj=Ayg=b>)W7sVkdPL${Nv4s!Tw)-$qKAU0ER5ej2r|@!+6pN2b73D1AnW5;If@1 zysK;tWIntM=*rp{29Vn->3a9wSCf>Lt*bVV*Xbp(hAENJ(gvvZnE4npC>ik08AN01 zs$Zn0A}Mc!*5>8_T?8iw)R{;hu77G&Vip#Q;c=QV(%N1-m8f{nM72ny8>OQdfuvML zD(0#Wlt!KC%=ZApRx&(H$+d}<5(Poxr_O*KEg1%vHG&^Nb`t}pyeu`<)xVIAPT7!B z!lEeNze7*N=7CV~3`6^2$%)wU^Q7@fs`u|s(drUJ%)n@jQ?j$yaI#rg3TD7}cjX0A z&xPZ$Pb5K{S;5&$B;Twy0}x?qfQK@q}{S!BMCa)m<)rigl*bgMojz2)b>h zW6C9J_b~0UDQjtVa9Ox$rru{vhVJJe<|$p#7qY9$LxQPlC3$a)Ss>6Uw$P84{7Vae zo&rnP8=7Twr?wNV;^D4p7vP(~?Vys0QN0@PNQnmrh7z^WRSZ3U(3P0PgIyimSLc}H zg`qH7f;UjY%>)w}k&3iexm((q1K*f2vIb1%WRIZV*vA|Ap|3V<({NdDJoXSXEK!HY z*>|e~|ONSGr^*RG?aJ1QFncrp$+2G35E7m9%stvoW z)_a!10N1DbSloYdEwSTTi@~P3idZ4oJ4_REDqCar#z>`kytjp?c5i~D9wSi@J>Fx( zZtmLzn_xxG7LGPmS`aNf4)y8h_dY`7W_liOVvY(o!Fv1TW~aWbeGx`5F+jJ{<~}OS z4Rh`por6&bLCjY%qLZ%Fkq(2RaMcD^Z&KR!x9pr=rAJ*05~X_g?+XucHR>=i7Tk7s z@SM8h0Lp6;4LWHc$f^Gbdft;4 zF!kjHA{++Y3iITl)jTvXb+Z*lJ_SVF3rzHbVi|L8is=~fMj?DOV+-v#J< zSahkw^?D{f5QNv(AbY5ka3kI_^9InZjfvaH<&FDO^VYa96fS{ zL*FQzA)g%W1soC^Y;HmM)e9JKRTH!Q`KgOPHf|9{Pm3>YM{o{N^{t5X(cj?$cxCtc zV)PtpZkrGx-#pdO&xV(%vYB_@FO)1v^8DV3^#o{^^qnSLk<~vUTDl7nt#2Sqxy?cT zK5%Z5{g~|o5WnHpu5xg+v-`l^b_OhP--zs4&(0EBDGWp~SBA8B+K4%)n-{FqVX=Cp zej^U}Yu(2>D}^OBCri>HrTWX{%FA`2AF(BZ1iW$yPu~8}uW<9ZQO09Lb4GzN)%pwW zzH(LD6a1JnK8r=Tx)UdT(NhYSMBMeJ<*Kc)k-KhroU6}r_(*^U=VND|G^pGfS4pG! zc-SlQsvzwAY#t+TmWUs_?4(!m7kHd{r$I+j7l`U4|8&^GQCJCHacUdMwwBuzg46f%h7U_cB`wUn`3fy zLQQH)HWItDfQBu&ee4MgWV(X5cVYZ1=@y~Y?qGH~MV@C?k7Y3&c*zFm`IiGNH%owH zb=u$rZu!~E3 zVDYfQ^RV{E!X)A+jeKry38*K8{L=v&(h9Bv9y<8}>grl|V0qiDd}RHxdd6zT_(M5R z)`^{WNF>D(eU}ykc&?QLvW#(%z~zkk*e*gi^(LbiAZS2bonMrv{ByCzHW}hYUotd^ z?qhVZC#JxI@NCcqv8IZDTbZ#OL;S1$7J7uF%n4n}$K^$0s`<5gk1(kS=0tTn}nhEOeG`H}8{a0DZ35qJVN` zkn;Nu1#!w^>^#rx0k$ot-qy%%x6ly9S8VL$<&38V zMOW^sfY&vP4ppJbZWi&h2>)CKOD`~zzZ+IFxYBS^VNR>BP1)cYBszGJh#$ht%R768 zx$6Vlx4BDacW$^$L%r=0+uda7rQ+{?lXtl0z>9yK_Ia_gHBfxKh|@En)_%q~3ln&i z&V(vK)h}NiVZwi2>nq@MWR^)a4oY2+WI8!H*~AJs{JSy}q`s&`ZU>R#gH8X>X)@jR z?)o2%8w>08KCV|Uv|I$m58PreAQrWmF8OAe&buSs?MUNK?%KY%a$~b4m;U$OdduEz zKydF>n{ol`Y6D6@JfX&Zq+_mHhn0IkoJ+lEzZF;e?qZ*u+;c0hsCuH*yWf0n5Bc#0 z(%2sM%?qyT@IuAjX`qM#vIzH6OyRw6mV7K54o0z5}hgQrMu1?9c64m<(kjW&TVhn@owf%A@4>}T&}9uecBOPkvYUC;D5;E~u8xym*kTeLPHyHU?AS`VAyd-=0 zPWwoMcSL=)NvM<7e{NTOAX(hm1w=E!R=a&GAM7;7^Ar2Gd$MLm>YsVn4;0?JO>Nl| z2;B6_8^BE{=ubd5AiIPhJ^)+&OY>GZnOa*wmfPZ^*gUhpadf>3NTj#AP*?#SCB41R+`o=Y z>HKCXQ-dR|rRg|bpc2Vnwth=+@kMJ`5zJk_+|B6hoXc$@*c#4hjhL(#iV6Y2l? z&~ph}O9OZ7Mf*92s|dP!aBk|_yUMx+wyJ?Qr3SwhgJB(t+tk$T3C)r%LrWXy$Ah=; zc)dy&928?eHYYU_@G`!phgCP)!q~_$0U4=LH~oO_4tDWknHnJOCMmSDGA;T48T-Z- zZk(t5ZlUh@O+Wg3T7z(k4jug6QUxULp5!@q0@R!UHqFoVtsnlu(!Ns34`Jh?*i^y6U^3pB+OqjJ9GCSm+t zxEq)5kq@PU8{pjSWgG*!a-b3FJiD_1JNAamvz5<5p7Z2Rx~hfXbsnX5Do(S|0yP#1 zqY->_{gDGHG40jSNWYx0bx&sXP~(sUG=*y)2+K&(rvmE zP}2j$6SucGT(!`jO6H8G8Zh)n?^zV|C!#w_^})3AM0|c}mKoI!F=`MdXOjLrd>W}{ zhg1F$dM}dSsur;mMVA|X$NNuQDJ=q5FnU^J?cTdwvs*@7fAYGp=dMZUe?4bo4lZh6EGp*A1i>LuRqrvw_l zl`Z{IUcY|H0sAQ#gzqLO^|<8u|BzPmUvwrmb1ltMrIX<64#Z*MQBW#QMJY1Lq#E4g zm7^}`pX>n$GmwV?k~sAB6QWPh<($FQyH(XYCm-hAyLT`B|C7qHLV;wnOhF(gGhURF zJpytvP{(3&Nc*9?C8@_2qh5&1H>hja#K8zvM3}ogU2Na51ON)Lu-=Aj6NBk9 zvLM}EW$w)w)31~|_x$8mAFMsGg@)oVW@S@&&;(XI(E^$=d7V2kQYb8mFVyOoyamD3 za~diWMtc_wK)uoTWlTIIzaA6Yvh9d_eMT=qStA$t`LMY?t5|_+guFD0Qp^V3?YcB` zl%cnC3BXtL)ih)qiR$&}k3SVHvk9Xw^}ChFljC@V$OJUmR)K9Hoag$BC1c@Ws%Jo-}ZekGQ%|K;?TXcE64D# zv|EKyw;c=ZQvr$}@(6_O3-CDsatd`zzv+Su$dS@Hlq`HmgJ3YzB?^$(n??J6^RE@w zf%(!gUnR2lS-*Rlx|5yE+TVxD_kw$rzh>{^jW0&pCnQ|;p=%@Qxhc5!I{|_oDQ1iL zm_*pLkAW;e;v!E``Q3>4`Q-s?-b|3vzjHL&UrfrqP?%5-P0rZ6Hyqe?7`UPAV&{$i zcu;}w}Ar)72~hl2C^Mrm4CL2p5V!`60@P7a2{FG zxZOO*1=OxRmuh|kWY3Mss2Z{fzC&Q35*p%7X1Aua?uKw#Y?^!Lv;!GAH)2j0a-g;0 z&5K#lmrEB)P3w-@^_OlCeZ;BwIZnw8%W&~AO;V{F#8HEBj~k@*`*i`$0BVeq){k#i zvYZ4k6c+nQ#Ss2|fx!St4(opZfZ1Z_d5RYT21%6YfSkm{DrDz~g~{qZ)M)9Q4 z*ZEbpSLjj0asYq^Zgd0kEitnpWvIPkFQBPD)O@srf;iCLOseT=85qy8rL7}?dw5aZ zTBvehx@y9~xwls4`WroP9j`te<9eNx&Rnt4CL{WH#Z4&e3;I*knY<^)=~fDX?OT9p~BHmC6pY{TmUQbEI-U|CKSzNz{cS!Nlod(_BDE9>o zp264i*W2u+!2nJfESx?;ozU-#iEVfg|NRjA`Qhz!b5~F5c7o&kJpNiY5Mlgu02x8E ztd|}!(t9Hk#C+yII&t@V+L#fLKFlMdH>Y{$Fs}>*Yf>~#Fx)$QT~%x_8HL;$Oubs< zRv*t#XF;$verh>V+9y;$7#IHgy+e<8x?V!6&cM1GiNO~fK56Ws=ONDcii|Obm&;x|LHGPoX^-BJzzxg)>%_|>&PH{HMi z!TtZ~#Vr9!MP@_3W2iR39L|r$on^Q7{|CQ}1+~~fF`$Y6P>F_!o5Uh7#jx|-eoO^sj_ zX~G@bQu5VU*57oJruO5W`2?yaaqN}~>o8{zyLcLKKYD}vjo;$=JGe`p_rmT55)vcj zr2<2K=taEU)&%-b^Jk%9Lnn5&!A`n1q4-(bu8hKOV@7gq9?{qKBi5kW3w-iBB&P3*D|l?mjM z2P>AB$)Y-n&xe;+_I*J-+1=jJz#IEpEkGnNTO-61u(eMvp0?zsUI0cR*A*F{pJJ(`g@apjf-{?$*cl zYrFK5WgBJRhRGiy!->zJM|Edm^;oCKZ%=`iG7wssfOp~Mlg$g_X;#;vK0#TD@I+R? zap_lSt*AD}rTglZDtPMV_|UBxVL=`s+&*?8k>3V0W=(Cww-#a;G67%T-eD1L>CLg) zm5OEJqPE1xJS(}=4{3(xtDO~h(8B5M)11xOO~Cv$?G_$#9uG~`+b2a#q3lx|w94&n z8|J1{;It&!%9eD8T(&lGxFDg3{wBF&=f;kb4 zONh4#Z9S8k z2%Rq1^zn04(YiS0Asxhn-=IyyZMQm({4hJBTgKKLFWoQ@v)>-0<~AmOykz~mlB>IM z4wEUTOa2(xk_M+nPBe<%*j&cY=MGqKO73u@xpWjmb4RxCv~fL3a9Dt=qxtGN=P&!U zAQmY;fDPE!f;zz=h*C<&jmRfJdA;h;_nj)!*F18}shd1FIiAH@Z4B&os=Hn&&8n3R z+m4JJvYu9J9bE@cXKfv@c0xu%og6(1)FjXiqi()ZdCD`+7AQ>4Gw=Zd++@EqD5`8s(+?cZii>u2~Z8?UI;BK)ut(kVq9(tUwSeZtb{av{x z?8bHF6sWybGvv%5=m5cm;k()m52j)G0!c?N6&`=zkSR&4Z8>+zhN;UiI$nTN2P84#N{az-rA)2s6P!eIE>IHmbQ9Wl;zG88PFAY?Yx2*?i|>+*9ghbV_=B zo%nolxbN1FebuQ{xvFmZo$^dzaxetf6B;R;uLD)P!@VeRk($@4=8wrL4Mb_vvYkxw zGGL8ZCnX(EaY}g0#^D$j8&KBe@q<#{hDZ*Z{ly6_ehES-eKz~P7P&E}IIl@5&ojq@ zle@k0e5cx_qU<5th-;K@XM*)CGO{WSagh*#UhfYqLzX+K9G(vWl|G@S2VFZw5x0l! zu#u>(am~AR)NojF8hZE%)jcKBz0~eE+BsYz#uABR9MBc1$*R17YC&JPeC!N*jZG@~ z2$A6%ijs=vFfy*{9%AYrbApcoAEIeGx7x)sV zXocRcFM?eMTU#Ib`S>&wksSC4h-IkbVYESz=lMliLgHGSmM1(;6FLTKFKFOYD`5*j z%=S7N3rR%rAI3(g9i2`&UYfic9xsME)2McpV4uo(7op~veOSId#(3Jf^n+4ON$YLM zI)q_qSWSZDjc5s#*TW|3*shhob0Rr*)4Qn^(@MWRD2?OI*(q8g2$`|qO1{E^i zZl*y}Zbr=9)*DKL*zFS&0eGqdo?e-Kn-PL+_8rT`2*EqWZ(zgYhpuuQHV_rkw#5yn z(u+?BQq`v0qfivKJ{6+tG7vtl)Y7jWTh-d*s;g;l)z^9{o=Hwfd^TI1mXSJC%4K+R zyfPGz6E7A#V0dZ`ylc%J%_jjpma=@#7ZL zyZdc9^{-2D!UN%e1o@3(-X=sMo*JI4m=@F3BE&tb;macUF8 zCH%zrbbRHR!PeP3$i{0&fKuYvQDt5pD*)5xWokx&0jqK#6~i&V8xG!CbuWsd*2FS( zJcG#boXSxd+_HDajMr8pTt0OdA%g}vu=y{$e7y*^xgtM8wJY!z%<*hkF< z{Z_7Emvx&2n(~LX<`hsW_BO_RjS0=td*z8gQ#NaxY>$w&O)deox&0&u@ZkLDcj2xN z4@#jwI&M!nrk@CEhJJLa+y$4qgwU>YL|>wGKysAH!5(RxX763tHoQyskV3W-xhDIb zmozCmjOOI1i?N0{%VvAO2qr&#$4axR$dupFVlfb-*Rk)fwoT)0G2Ji7e%ELC5g(1I z4h{SMny?~`7YQ+NWR=%j;{p<)@CQ^@Ir290Z!bMRR_;47;@V3bOR_mWqU6J)OP$5r z;+mUqJ+80LjdxtSmyd1r-o$JQGj7XgN9XN^hpN9*BaM8Lbe$;W~mj73MeN+!zj4+QnNZuEU@l zj0-nfGZb|~`3lx7&$H{m7KbKVHF!~SBI}@CGObm!rcLOc^x7%PY}w1;%5!aGh*U=7 zi*Xg@@c4e1n2hVw>g)r$YL1Z5X^G#Ff>^a3QWk2L;TE^KQBE6%@G0jJj0>HtM)7NI2wD=P@&zM=x}P}P3(oCVP7mQ_(>dwfkpupxW|3nun^j(E&VwgT+GHJZ>E}_Vk~jmnz1A)#kHAbdCl7#D920vctDf&I_d3(|H?j?J ze0md6WVmqM!<<%4=QF*nm+TNQWiN*^ZX4PstKXr{sX)y>%wF-VOI@+Nhpa!SNAvqd zLBNbD8M3eLfZYG9q=@P}Ca*N(tj0>&m999H|G<*5yQU=hge1!}rTL+=TNA1w(wP#Y zDwI)DQAK#BcGI~5z*5|JyY;0)dW`(;CbgNaf?+tpoYm)%jg#G6=9UdEsBTR$2GN92_WRq-LZVm`cBu(M711`R-syg=Fa& zVFEkjZW8Pj`w%VvYgHyKu~4#P#5Qw{me>4|?e zM>13xIM;Bey}Tvu(ZB2IH>Oa5y#|)=-n}rU!j~8M1>F@M}&nOwrlDQ?T)cUg@?lD)b_f%qT}1 z{$P7ldqU3~M7%+*id3_(&4k8HV z_Ig|m=RjIRwLp99aVpk>oCc8z&6G$1pmgln zx5jkrSuDN1)%^|d2#R5l&Xe=wd)8#|eV8i|V3PBXrM;k{ zw!q_Zz*-4rtef`+u&b%5UoW)kZ?@N^J)=71Qu7c+&T(HgT4dy=D8C~cd~v0?c9;`K z61KV+@FTpd$$ltYi~#V6cY_$O#`H?>4P4UpQ!!cK>D{#s1WJGvb#(O>4(1<=)UMbo zi^{QuI!{Zd$YR>fLQSZ<@;_CZ1>)2HdyPC;!R#oOH1!GyD0)SNGp-EQ#_MVT#oj}0 zP0c=OY3T_VQ0fr@(fg5C=U2rJcO9sC+WTtaXfIC16-jEr#!JSkm0;y}ggYkYbr$n9 z1o&SNpxC}_P+A2|m(tam$0GlSZtzm-PZDp?SGeX&AK(?Bx^{QD=5g&eS3pb1Sm(4e zwsyu~_V*Jzku(~|uC#mhvnk|+sej1uHw<+I>fWg?BN207E&1}tEoyVFY*u1X3nx_T zqi1Vf^?CQ)2}e+N3Dq5j$em!wSUi1ckdw~1*JxmjZ}83W90>Xy8MChfw|UsQqV@XX zeQqv*rdh#X#Ha4Mq;e4uzuU&{IOaWDl_TxlisLWWJcRkPRh8rqg&4tJJ^xV0kZH0; zCnF{GL%5MF#^j~{#oc=VHJ!EX!}_?ZtAfZ{kS43Bs0auMNDI0stP6s4=}IU{NRSeG zV0Tfl5LiWeQ;=RFB?$yV6qH`122wzT5FjR$5JD0H{~zMB&-%Rky)*xrZ|0l%#u;Z6 z{hfB7``qWc?sMIa&dEAe<(NYH&1Tpv>Kx4dxm=hs~WZA9pA?R*tbbxDq3@eYMutY8R%lif+SL zDuZjt9qUkn&&9Gy%w!egs`MXw0Us5s^hBIt-ZyeET*j>}s0uGzziiRzuB#0S(%

                                                                                  Cluster Version

                                                                                  Currently, MRS 3.1.2-LTS.6, MRS 3.2.0-LTS.2 and MRS 3.3.0-LTS.1 are supported. The default value displayed on the UI varies depending on the version.

                                                                                  +

                                                                                  Currently, MRS 3.1.2-LTS.6, MRS 3.2.0-LTS.2, MRS 3.3.0-LTS.1 and MRS 3.5.0-LTS are supported. The default value displayed on the UI varies depending on the version.

                                                                                  Components

                                                                                  diff --git a/docs/mrs/umn/mrs_01_1298.html b/docs/mrs/umn/mrs_01_1298.html index ea4413b95..e056680cb 100644 --- a/docs/mrs/umn/mrs_01_1298.html +++ b/docs/mrs/umn/mrs_01_1298.html @@ -153,6 +153,26 @@
                                                                                12. ALM-12190 Number of Knox Connections Exceeds the Threshold
                                                                                  13. +
                                                                                13. ALM-12191 Disk I/O Usage Exceeds the Threshold
                                                                                  +
                                                                                  14. +
                                                                                14. ALM-12192 Host Load Exceeds the Threshold
                                                                                  +
                                                                                  15. +
                                                                                15. ALM-12200 Password Is About to Expire
                                                                                  +
                                                                                  16. +
                                                                                16. ALM-12201 Process CPU Usage Exceeds the Threshold
                                                                                  +
                                                                                  17. +
                                                                                17. ALM-12202 Process Memory Usage Exceeds the Threshold
                                                                                  +
                                                                                  18. +
                                                                                18. ALM-12203 Process Full GC Duration Exceeds the Threshold
                                                                                  +
                                                                                  19. +
                                                                                19. ALM-12204 Wait Duration of a Disk Read Exceeds the Threshold
                                                                                  +
                                                                                  20. +
                                                                                20. ALM-12205 Wait Duration of a Disk Write Exceeds the Threshold
                                                                                  +
                                                                                  21. +
                                                                                21. ALM-12206 Password Has Expired
                                                                                  +
                                                                                  22. +
                                                                                22. ALM-12207 Slow Disk Processing Timeout
                                                                                  +
                                                                                23. ALM-13000 ZooKeeper Service Unavailable
                                                                                24. ALM-13001 Available ZooKeeper Connections Are Insufficient
                                                                                  @@ -243,6 +263,14 @@
                                                                                25. ALM-14035 HttpFS Process Is Abnormal
                                                                                  26. +
                                                                                26. ALM-14036 NameNode Is In Safe Mode
                                                                                  +
                                                                                  27. +
                                                                                27. ALM-14037 DataNodes Outside the Cluster
                                                                                  +
                                                                                  28. +
                                                                                28. ALM-14038 Router Heap Memory Usage Exceeds the Threshold
                                                                                  +
                                                                                  29. +
                                                                                29. ALM-14039 Slow DataNodes Exist in the Cluster
                                                                                  +
                                                                                30. ALM-16000 Percentage of Sessions Connected to the HiveServer to Maximum Number Allowed Exceeds the Threshold
                                                                                31. ALM-16001 Hive Warehouse Space Usage Exceeds the Threshold
                                                                                  @@ -271,6 +299,12 @@
                                                                                32. ALM-16048 Tez or Spark Library Path Does Not Exist
                                                                                  33. +
                                                                                33. ALM-16051 Percentage of Sessions Connected to MetaStore Exceeds the Threshold
                                                                                  +
                                                                                  34. +
                                                                                34. ALM-16052 Latency for MetaStore to Access the Meta Database During Table Creation Exceeds the Threshold
                                                                                  +
                                                                                  35. +
                                                                                35. ALM-16053 Average HQL Submission Time of Hive in the Last 5 Minutes Exceeds the Threshold
                                                                                  +
                                                                                36. ALM-17003 Oozie Service Unavailable
                                                                                37. ALM-17004 Oozie Heap Memory Usage Exceeds the Threshold
                                                                                  @@ -281,6 +315,14 @@
                                                                                38. ALM-17007 Garbage Collection (GC) Time of the Oozie Process Exceeds the Threshold
                                                                                  39. +
                                                                                39. ALM-17008 Abnormal Connection Between Oozie and ZooKeeper
                                                                                  +
                                                                                  40. +
                                                                                40. ALM-17009 Abnormal Connection Between Oozie and DBService
                                                                                  +
                                                                                  41. +
                                                                                41. ALM-17010 Abnormal Connection Between Oozie and HDFS
                                                                                  +
                                                                                  42. +
                                                                                42. ALM-17011 Abnormal Connection Between Oozie and YARN
                                                                                  +
                                                                                43. ALM-18000 Yarn Service Unavailable
                                                                                44. ALM-18002 NodeManager Heartbeat Lost
                                                                                  @@ -367,6 +409,20 @@
                                                                                45. ALM-19026 Damaged WAL Files in HBase
                                                                                  46. +
                                                                                46. ALM-19030 P99 Latency of RegionServer RPC Request Exceeds the Threshold
                                                                                  +
                                                                                  47. +
                                                                                47. ALM-19031 Number of RegionServer RPC Connections Exceeds the Threshold
                                                                                  +
                                                                                  48. +
                                                                                48. ALM-19032 Number of Tasks in the RegionServer RPC Write Queue Exceeds the Threshold
                                                                                  +
                                                                                  49. +
                                                                                49. ALM-19033 Number of Tasks in the RegionServer RPC Read Queue Exceeds the Threshold
                                                                                  +
                                                                                  50. +
                                                                                50. ALM-19034 Number of RegionServer WAL Write Timeouts Exceeds the Threshold
                                                                                  +
                                                                                  51. +
                                                                                51. ALM-19035 Size of the RegionServer Call Queue Exceeds the Threshold
                                                                                  +
                                                                                  52. +
                                                                                52. ALM-19036 Bad Blocks Exist in HBase Key Directory Data
                                                                                  +
                                                                                53. ALM-20002 Hue Service Unavailable
                                                                                54. ALM-23001 Loader Service Unavailable
                                                                                  @@ -485,6 +541,20 @@
                                                                                55. ALM-38011 User Connection Usage on Broker Exceeds the Threshold
                                                                                  56. +
                                                                                56. ALM-38012 Number of Broker Partitions Exceeds the Threshold
                                                                                  +
                                                                                  57. +
                                                                                57. ALM-38013 Produce Request Latency in the Request Queue Exceeds the Threshold
                                                                                  +
                                                                                  58. +
                                                                                58. ALM-38014 Total Produce Request Latency Exceeds the Threshold
                                                                                  +
                                                                                  59. +
                                                                                59. ALM-38015 Fetch Request Latency in the Request Queue Exceeds the Threshold
                                                                                  +
                                                                                  60. +
                                                                                60. ALM-38016 Total Fetch Request Latency Exceeds the Threshold
                                                                                  +
                                                                                  61. +
                                                                                61. ALM-38017 Partition Reassignment Duration Exceeds the Threshold
                                                                                  +
                                                                                  62. +
                                                                                62. ALM-38018 Kafka Consumer Lag
                                                                                  +
                                                                                63. ALM-43001 Spark2x Service Unavailable
                                                                                64. ALM-43006 Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold
                                                                                  @@ -517,6 +587,10 @@
                                                                                65. ALM-43023 IndexServer2x Process Full GC Number Exceeds the Threshold
                                                                                  66. +
                                                                                66. ALM-43028 JDBCServer Session Overflow
                                                                                  +
                                                                                  67. +
                                                                                67. ALM-43029 JDBCServer Job Submission Timed Out
                                                                                  +
                                                                                68. ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold
                                                                                69. ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold
                                                                                  @@ -529,6 +603,18 @@
                                                                                70. ALM-45003 HetuEngine QAS Disk Capacity Is Insufficient
                                                                                  71. +
                                                                                71. ALM-45004 Tasks Stacked on HetuEngine Compute Instance
                                                                                  +
                                                                                  72. +
                                                                                72. ALM-45005 CPU Usage of HetuEngine Compute Instance Exceeded the Threshold
                                                                                  +
                                                                                  73. +
                                                                                73. ALM-45006 Memory Usage of a HetuEngine Compute Instance Exceeded the Threshold
                                                                                  +
                                                                                  74. +
                                                                                74. ALM-45007 Number of Workers of a HetuEngine Compute Instance Is Less Than the Threshold
                                                                                  +
                                                                                  75. +
                                                                                75. ALM-45008 Query Latency of HetuEngine Compute Instances Exceeds the Threshold
                                                                                  +
                                                                                  76. +
                                                                                76. ALM-45009 Task Failure Rate of HetuEngine Compute Instances Exceeds the Threshold
                                                                                  +
                                                                                77. ALM-45175 Average Time for Calling OBS Metadata APIs Is Greater than the Threshold
                                                                                78. ALM-45176 Success Rate of Calling OBS Metadata APIs Is Lower than the Threshold
                                                                                  @@ -581,6 +667,10 @@
                                                                                79. ALM-45292 PolicySync GC Duration Exceeds the Threshold
                                                                                  80. +
                                                                                80. ALM-45293 Ranger User Synchronization Exception
                                                                                  +
                                                                                  81. +
                                                                                81. ALM-45294 RangerKMS Process Is Abnormal
                                                                                  +
                                                                                82. ALM-45425 ClickHouse Service Unavailable
                                                                                83. ALM-45426 ClickHouse Service Quantity Quota Usage in ZooKeeper Exceeds the Threshold
                                                                                  @@ -621,6 +711,36 @@
                                                                                84. ALM-45444 Abnormal ClickHouse Process
                                                                                  85. +
                                                                                85. ALM-45445 Failed to Send Data Files to Remote Shards When ClickHouse Writes Data to a Distributed Table
                                                                                  +
                                                                                  86. +
                                                                                86. ALM-45446 Mutation Task of ClickHouse Is Not Complete for a Long Time
                                                                                  +
                                                                                  87. +
                                                                                87. ALM-45447 ClickHouse Table Read-Only
                                                                                  +
                                                                                  88. +
                                                                                88. ALM-45448 Rapid Increase of Znodes Used by ClickHouse
                                                                                  +
                                                                                  89. +
                                                                                89. ALM-45449 The Counter Number of zxid Used by ClickHouse Exceeds the Threshold
                                                                                  +
                                                                                  90. +
                                                                                90. ALM-45450 ClickHouse Failed to Obtain a Temporary Agency Credential
                                                                                  +
                                                                                  91. +
                                                                                91. ALM-45451 ClickHouse Failed to Access OBS
                                                                                  +
                                                                                  92. +
                                                                                92. ALM-45452 ClickHouse's Local Disk Space Is Below the Cold-Hot Separation Threshold
                                                                                  +
                                                                                  93. +
                                                                                93. ALM-45475 A Single Replica Exists in the Kudu Data Table
                                                                                  +
                                                                                  94. +
                                                                                94. ALM-45476 Kudu Failed to Enter the Maintenance Mode
                                                                                  +
                                                                                  95. +
                                                                                95. ALM-45477 Failed to Restore Data After a Disk of Kudu Is Replaced
                                                                                  +
                                                                                  96. +
                                                                                96. ALM-45478 Kudu Failed Data Balancing
                                                                                  +
                                                                                  97. +
                                                                                97. ALM-45479 Number of Tablets of the Tserver Process Exceeds the Threshold
                                                                                  +
                                                                                  98. +
                                                                                98. ALM-45480 Tablet Leaders of a Tserver Process Are Unevenly Distributed
                                                                                  +
                                                                                  99. +
                                                                                99. ALM-45481 KuduTserver Has Full Disks
                                                                                  +
                                                                                100. ALM-45585 IoTDB Service Unavailable
                                                                                101. ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold
                                                                                  @@ -709,6 +829,18 @@
                                                                                102. ALM-45743 Failed to Call the IAM API
                                                                                  103. +
                                                                                103. ALM-45744 Average RPC Processing Time of the Guardian TokenServer Exceeds the Threshold
                                                                                  +
                                                                                  104. +
                                                                                104. ALM-45745 Average RPC Queuing Time of the Guardian TokenServer Exceeds the Threshold
                                                                                  +
                                                                                  105. +
                                                                                105. ALM-47001 MemArtsCC Service Unavailable
                                                                                  +
                                                                                  106. +
                                                                                106. ALM-47002 MemArtsCC Disk Fault
                                                                                  +
                                                                                  107. +
                                                                                107. ALM-47003 Memory Usage of the MemArtsCC Worker Process Exceeds the Threshold
                                                                                  +
                                                                                  108. +
                                                                                108. ALM-47004 Average Latency of MemArtsCC Worker Read Requests Exceeds the Threshold
                                                                                  +
                                                                                109. ALM-50201 Doris Service Unavailable
                                                                                110. ALM-50202 FE CPU Usage Exceeds the Threshold
                                                                                  @@ -757,10 +889,28 @@
                                                                                111. ALM-50226 BE Instance Fault
                                                                                  112. +
                                                                                112. ALM-50227 Concurrent Doris Tenant Queries Exceeds the Threshold
                                                                                  +
                                                                                  113. +
                                                                                113. ALM-50228 Memory Usage of a Doris Tenant Exceeds the Threshold
                                                                                  +
                                                                                  114. +
                                                                                114. ALM-50229 Doris FE Failed to Connect to OBS
                                                                                  +
                                                                                  115. +
                                                                                115. ALM-50230 Doris BE Cannot Connect to OBS
                                                                                  +
                                                                                  116. +
                                                                                116. ALM-50231 Abnormal Tablets Exist in Doris
                                                                                  +
                                                                                  117. +
                                                                                117. ALM-50232 Large Tablets in Doris
                                                                                  +
                                                                                118. ALM-50401 Number of JobServer Jobs Waiting to Be Executed Exceeds the Threshold
                                                                                119. ALM-50402 JobGateway Service Unavailable
                                                                                  120. +
                                                                                120. ALM-50406 Failure Rate of the JobServer Job Submission API Exceeds the Threshold
                                                                                  +
                                                                                  121. +
                                                                                121. ALM-50407 Failure Rate of the JobServer Job Query API Exceeds the Threshold
                                                                                  +
                                                                                  122. +
                                                                                122. ALM-50408 Failure Rate of the JobServer Job Termination API Exceeds the Threshold
                                                                                  +
                                                                                  123. diff --git a/docs/mrs/umn/mrs_01_248978.html b/docs/mrs/umn/mrs_01_248978.html index 425821d8b..9f3f00876 100644 --- a/docs/mrs/umn/mrs_01_248978.html +++ b/docs/mrs/umn/mrs_01_248978.html @@ -35,7 +35,7 @@
                                                                                123. Click Next. On the Select Policy/Role page, select the policy created in 4.
                                                                                124. Click Next, select All resources, click Show More, select Global resources, and click OK.
                                                                                  125. -

                                                                                  Granting OBS Access Permission to Guardian

                                                                                  1. Log in to FusionInsight Manager, choose Cluster > Services > Guardian, click Configurations, and then All Configurations. On the displayed page, search for and modify the following parameters. +

                                                                                    Granting OBS Access Permission to Guardian

                                                                                    1. Log in to MRS Manager, choose Cluster > Services > Guardian, click Configurations, and then All Configurations. On the displayed page, search for and modify the following parameters.

                                                                                      Parameter

                                                                                      Description

                                                                                      @@ -75,10 +75,10 @@
                                                                                      -
                                                                                    2. Save the service configuration, choose More > Restart Configuration-Expired Instances on the FusionInsight Manager home page, and restart all service instances whose configurations have expired as prompted.
                                                                                    3. To submit jobs on the MRS console, log in to the active OMS node as user omm and run the following command to refresh the built-in client configuration:

                                                                                      sh /opt/executor/bin/refresh-client-config.sh

                                                                                      +
                                                                                    4. Save the service configuration, choose More > Restart Configuration-Expired Instances on the MRS Manager home page, and restart all service instances whose configurations have expired as prompted.
                                                                                    5. To submit jobs on the MRS console, log in to the active OMS node as user omm and run the following command to refresh the built-in client configuration:

                                                                                      sh /opt/executor/bin/refresh-client-config.sh

                                                                                    -

                                                                                    Enabling Cascading Authorization for Hive Tables

                                                                                    1. Log in to FusionInsight Manager, choose Cluster > Services > Ranger and click Configurations.
                                                                                    2. Search for the ranger.ext.authorization.cascade.enable parameter and set it to true.

                                                                                      +

                                                                                      Enabling Cascading Authorization for Hive Tables

                                                                                      1. Log in to MRS Manager, choose Cluster > Services > Ranger and click Configurations.
                                                                                      2. Search for the ranger.ext.authorization.cascade.enable parameter and set it to true.

                                                                                      3. Click Save.
                                                                                      4. Click Instance and select all RangerAdmin instances. Click More and select Restart Instance. Enter the password, and click OK to restart all RangerAdmin instances.

                                                                                      Configuring the Recycle Bin Cleanup Policy

                                                                                      1. Log in to the OBS Console.
                                                                                      2. Select Parallel File Systems and click the file system created in Creating an OBS Parallel File System.
                                                                                      3. Choose Basic Configurations > Lifecycle Rules and click Create to create a lifecycle rule for the /user/.Trash directory.

                                                                                        For clusters that use decoupled storage and compute, configure a lifecycle policy for the related directories by referring to this chapter. Otherwise, the storage space may be used up and storage fees may increase.

                                                                                        diff --git a/docs/mrs/umn/mrs_01_248989.html b/docs/mrs/umn/mrs_01_248989.html index 47cfd50ad..72130b012 100644 --- a/docs/mrs/umn/mrs_01_248989.html +++ b/docs/mrs/umn/mrs_01_248989.html @@ -3,7 +3,7 @@

                                                                                        Interconnecting Hive with OBS

                                                                                        Interconnecting with OBS

                                                                                        MRS clusters allow Hive to connect to OBS through Metastore.

                                                                                        Interconnecting Hive with OBS through Metastore

                                                                                        -
                                                                                        1. You have configured storage and compute decoupling by referring to Interconnecting the Guardian Service with OBS.
                                                                                        2. Log in to FusionInsight Manager and choose Cluster > Services > Hive, and click Configurations.
                                                                                        3. Search for hive.metastore.warehouse.dir in the search box and change the parameter value to an OBS path, for example, obs://hivetest/user/hive/warehouse/. hivetest indicates the OBS file system name.

                                                                                          Figure 1 hive.metastore.warehouse.dir configuration
                                                                                          +
                                                                                          1. You have configured storage and compute decoupling by referring to Interconnecting the Guardian Service with OBS.
                                                                                          2. Log in to MRS Manager and choose Cluster > Services > Hive, and click Configurations.
                                                                                          3. Search for hive.metastore.warehouse.dir in the search box and change the parameter value to an OBS path, for example, obs://hivetest/user/hive/warehouse/. hivetest indicates the OBS file system name.

                                                                                            Figure 1 hive.metastore.warehouse.dir configuration

                                                                                          4. Save the configuration, choose Cluster > Services, and restart the Hive service in the service list.
                                                                                          5. Update the client configuration file.

                                                                                            1. Log in to the node where the Hive client is located and run the following command to modify hivemetastore-site.xml in the Hive client configuration file directory:

                                                                                              vi Client installation directory/Hive/config/hivemetastore-site.xml

                                                                                            2. Change the value of hive.metastore.warehouse.dir to the corresponding OBS path, for example, obs://hivetest/user/hive/warehouse/.

                                                                                            3. Change the value of hive.metastore.warehouse.dir of hivemetastore-site.xml in the HCatalog client configuration file directory to the corresponding OBS path, for example, obs://hivetest/user/hive/warehouse/.

                                                                                              vi Client installation directory/Hive/HCatalog/conf/hivemetastore-site.xml

                                                                                              @@ -20,7 +20,7 @@

                                                                                            4. Choose Settings > Roles, click Add New Role, and create a role whose Role Name is hive.

                                                                                            -
                                                                                          6. Granting the read and write permissions on OBS paths to a custom user group
                                                                                            1. Log in to FusionInsight Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                            2. Create a user group without a role, for example, hiveobs1, and bind the user group to the corresponding user.
                                                                                            3. Log in to the Ranger management page as the rangeradmin user.
                                                                                            4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                            5. Grant the Read and Write permissions on the OBS storage path to the hiveobs1 user group. In this case, all users bound to the hiveobs1 user group can access the Hive data warehouse path.

                                                                                              +
                                                                                            6. Granting the read and write permissions on OBS paths to a custom user group
                                                                                              1. Log in to MRS Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                              2. Create a user group without a role, for example, hiveobs1, and bind the user group to the corresponding user.
                                                                                              3. Log in to the Ranger management page as the rangeradmin user.
                                                                                              4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                              5. Grant the Read and Write permissions on the OBS storage path to the hiveobs1 user group. In this case, all users bound to the hiveobs1 user group can access the Hive data warehouse path.

                                                                                            7. Creating a database,table, or partition in a custom location and granting read and write permissions on OBS paths
                                                                                              1. Log in to the Ranger web UI as the Ranger administrator.
                                                                                              2. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area, and assign the Read and Write permissions on the OBS storage path to the user group of the corresponding user.

                                                                                                For example, assign the Read and Write permissions on the obs://obs-test/test/ directory to the hgroup1 user group, as shown in the following figure.

                                                                                                diff --git a/docs/mrs/umn/mrs_01_248991.html b/docs/mrs/umn/mrs_01_248991.html index d31ebad20..12bf0332d 100644 --- a/docs/mrs/umn/mrs_01_248991.html +++ b/docs/mrs/umn/mrs_01_248991.html @@ -23,7 +23,7 @@ JobManager Web Interface: http://192.168.1.150:32261
                                                                                                • Flink jobs are running on Yarn. Before configuring Flink to interconnect with the OBS file system, ensure that the interconnection between Yarn and the OBS file system is normal.
                                                                                                • Name of the OBS parallel file system/File name: The OBS file path must be written to the directory level.
                                                                                                • If Kerberos authentication has been enabled (security mode) for the cluster, grant the Read and Write permissions on OBS paths to component users in Ranger by referring to Ranger Permission Configuration.
                                                                                        -

                                                                                        Ranger Permission Configuration

                                                                                        1. Log in to FusionInsight Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                        2. Create a user group without a role, for example, obs_flink, and bind the user group to the corresponding user.
                                                                                        3. Log in to the Ranger management page as the rangeradmin user.
                                                                                        4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                        5. Click Add New Policy to add the Read and Write permissions on OBS paths to the user group created in 2. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                          +

                                                                                          Ranger Permission Configuration

                                                                                          1. Log in to MRS Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                          2. Create a user group without a role, for example, obs_flink, and bind the user group to the corresponding user.
                                                                                          3. Log in to the Ranger management page as the rangeradmin user.
                                                                                          4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                          5. Click Add New Policy to add the Read and Write permissions on OBS paths to the user group created in 2. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                          diff --git a/docs/mrs/umn/mrs_01_248992.html b/docs/mrs/umn/mrs_01_248992.html index 9869c8f39..384ffca22 100644 --- a/docs/mrs/umn/mrs_01_248992.html +++ b/docs/mrs/umn/mrs_01_248992.html @@ -8,7 +8,7 @@
                                                                                        6. Set Location to the OBS file system path when creating a table.

                                                                                          For example, to create a table named test whose Location is obs://obs-test/test/Database name/Table name, run the following command:

                                                                                          create external table testspark(name string) location "obs://obs-test/test/Database name/Table name";

                                                                                        -
                                                                                      4. Interconnecting Spark with OBS through Hive Metastore:
                                                                                        1. Complete the configurations by referring to Interconnecting the Guardian Service with OBS.
                                                                                        2. Log in to FusionInsight Manager, choose Cluster > Services > Spark and choose Configurations > All Configurations.
                                                                                        3. In the navigation pane on the left, choose SparkResource > Customization. In the custom configuration items, add spark.sql.warehouse.location.first to the custom parameter and set its value to true.
                                                                                          Figure 1 spark.sql.warehouse.location.first configuration
                                                                                          +
                                                                                        4. Interconnecting Spark with OBS through Hive Metastore:
                                                                                          1. Complete the configurations by referring to Interconnecting the Guardian Service with OBS.
                                                                                          2. Log in to MRS Manager, choose Cluster > Services > Spark and choose Configurations > All Configurations.
                                                                                          3. In the navigation pane on the left, choose SparkResource > Customization. In the custom configuration items, add spark.sql.warehouse.location.first to the custom parameter and set its value to true.
                                                                                            Figure 1 spark.sql.warehouse.location.first configuration
                                                                                          4. In the navigation pane on the left, choose JDBCServer > Customization. In the custom configuration items, add spark.sql.warehouse.location.first to the custom parameter and set its value to true.
                                                                                            Figure 2 spark.sql.warehouse.location.first configuration
                                                                                          5. Click Save to save the configuration. Click the Dashboard tab choose More > Restart Service, enter the password, click OK, and click OK again to restart Spark.
                                                                                          6. After Spark is restarted, choose More > Download Client to download and install the Spark client again. Then, go to 7.
                                                                                            If you do not download and install the client again, you can perform the following steps to update the Spark client configuration file (for example, the client directory is /opt/client):
                                                                                            1. Log in to the node where the Spark client is deployed as user root and switch to the client installation directory.

                                                                                              cd /opt/client

                                                                                            2. Run the following command to modify hive-site.xml in the configuration file directory of the Spark client:

                                                                                              vi Spark/spark/conf/hive-site.xml

                                                                                              @@ -36,13 +36,13 @@
                                                                                      -

                                                                                      Configuring Ranger Permissions

                                                                                      1. Log in to FusionInsight Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                      2. Create a user group without a role, for example, obs_spark, and bind the user group to the corresponding user.
                                                                                      3. Log in to the Ranger management page as the rangeradmin user.
                                                                                      4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                      5. Click Add New Policy to add the Read and Write permissions on OBS paths to the user group created in 2. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                        +

                                                                                        Configuring Ranger Permissions

                                                                                        1. Log in to MRS Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                        2. Create a user group without a role, for example, obs_spark, and bind the user group to the corresponding user.
                                                                                        3. Log in to the Ranger management page as the rangeradmin user.
                                                                                        4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                        5. Click Add New Policy to add the Read and Write permissions on OBS paths to the user group created in 2. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                        • Cascading authorization is not supported for view tables.
                                                                                        • Cascading authorization can be performed only on databases and tables, and cannot be on partitions. If a partition path is not in the table path, you need to manually authorize the partition path.
                                                                                        • Cascading authorization for Deny Conditions in the Hive Ranger policy is not supported. That is, the Deny Conditions permission only restricts the table permission and cannot generate the permission of the HDFS storage source.
                                                                                        • The permission of the HDFS Ranger policy is prior to that of the HDFS storage source generated by cascading authorization. If the HDFS Ranger permission has been set for the HDFS storage source of the table, the cascading permission does not take effect.

                                                                                        Configuring Permissions for CDL Service Users

                                                                                        If Kerberos authentication is enabled for the cluster (the cluster is in security mode) and you need to store real-time data to OBS after the interconnection, perform the following operations to grant the Read and Write permissions on the corresponding OBS path to the specific user:

                                                                                        -
                                                                                        1. Log in to FusionInsight Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                        2. Create a user group without a role, for example, obs_cdl, and bind the user group to the corresponding CDL service user, for example, cdluser.
                                                                                        3. Log in to the Ranger management page as the rangeradmin user.
                                                                                        4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                        5. Click Add New Policy to add the Read and Write permissions on OBS paths to the created user group. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                          The following figure shows the configurations needed for adding the Read and Write permissions on obs://OBS parallel file system name/cdldata to user group obs_cdl.

                                                                                          +
                                                                                          1. Log in to MRS Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                          2. Create a user group without a role, for example, obs_cdl, and bind the user group to the corresponding CDL service user, for example, cdluser.
                                                                                          3. Log in to the Ranger management page as the rangeradmin user.
                                                                                          4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                          5. Click Add New Policy to add the Read and Write permissions on OBS paths to the created user group. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                            The following figure shows the configurations needed for adding the Read and Write permissions on obs://OBS parallel file system name/cdldata to user group obs_cdl.

                                                                                        diff --git a/docs/mrs/umn/mrs_01_248993.html b/docs/mrs/umn/mrs_01_248993.html index eb6ae874a..d0e4103fd 100644 --- a/docs/mrs/umn/mrs_01_248993.html +++ b/docs/mrs/umn/mrs_01_248993.html @@ -39,7 +39,7 @@

                                                                                        spark.sql("select * from hudi_ro_table").show()

                                                                                      6. Run the :q command to exit the spark-shell CLI.
                                                                                      -

                                                                                      Configuring Ranger Permissions

                                                                                      1. Log in to FusionInsight Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                      2. Create a user group without a role, for example, obs_hudi, and bind the user group to the corresponding user.
                                                                                      3. Log in to the Ranger management page as the rangeradmin user.
                                                                                      4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                      5. Click Add New Policy to add the Read and Write permissions on OBS paths to the user group created in 2. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                        +

                                                                                        Configuring Ranger Permissions

                                                                                        1. Log in to MRS Manager and choose System > Permission > User Group. On the displayed page, click Create User Group.
                                                                                        2. Create a user group without a role, for example, obs_hudi, and bind the user group to the corresponding user.
                                                                                        3. Log in to the Ranger management page as the rangeradmin user.
                                                                                        4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                        5. Click Add New Policy to add the Read and Write permissions on OBS paths to the user group created in 2. If there are no OBS paths, create one in advance (wildcard character * is not allowed).

                                                                                      diff --git a/docs/mrs/umn/mrs_01_248995.html b/docs/mrs/umn/mrs_01_248995.html index 135406172..b470307fb 100644 --- a/docs/mrs/umn/mrs_01_248995.html +++ b/docs/mrs/umn/mrs_01_248995.html @@ -2,7 +2,7 @@

                                                                                      Interconnecting HetuEngine with OBS

                                                                                      Interconnecting with OBS

                                                                                      In an MRS cluster, Location can be set to an OBS file system path during HetuEngine table creation and HetuEngine can connect to OBS through Hive Metastore.

                                                                                      -
                                                                                      • Setting Location to the OBS file system path when creating a table
                                                                                        1. If a HetuEngine compute instance is running, restart it.

                                                                                          Log in to FusionInsight Manager as a user who has permission to access the HetuEngine web UI. Choose Cluster > Services > HetuEngine. In the Basic Information area in the Dashboard tab, click the link next to HSConsole WebUI. On the displayed HSConsole page, click Compute Instance. In the instance list, click Restart in the Operation column and operate as prompted.

                                                                                          +
                                                                                          • Setting Location to the OBS file system path when creating a table
                                                                                            1. If a HetuEngine compute instance is running, restart it.

                                                                                              Log in to MRS Manager as a user who has permission to access the HetuEngine web UI. Choose Cluster > Services > HetuEngine. In the Basic Information area in the Dashboard tab, click the link next to HSConsole WebUI. On the displayed HSConsole page, click Compute Instance. In the instance list, click Restart in the Operation column and operate as prompted.

                                                                                            2. Log in to the node where the HetuEngine service client is located as the client installation user and run the following command:

                                                                                              source Client installation directory/bigdata_env

                                                                                            3. Log in to the HetuEngine client based on the cluster authentication mode.
                                                                                              • Kerberos authentication has been enabled for the cluster (security mode): Run the following command to complete user authentication and log in to the HetuEngine client:

                                                                                                kinit User performing HetuEngine operations

                                                                                                hetu-cli --catalog hive --tenant default --schema default

                                                                                                @@ -11,7 +11,7 @@
                                                                                            4. Set Location to the OBS file system path when creating a table.

                                                                                              create table test(name string) with (location = 'obs://Name of the OBS parallel file system/user/hive/warehouse/test');

                                                                                            -
                                                                                          • Interconnecting with OBS through Hive Metastore
                                                                                            1. Complete the configurations by referring to Interconnecting Hive with OBS using MetaStore.
                                                                                            2. Log in to FusionInsight Manager, choose Cluster > Services > HetuEngine. On the displayed page, choose More > Synchronize Configuration. After the synchronization is complete, choose More > Synchronize Configuration again and then restart the HetuEngine service as prompted.

                                                                                              If a HetuEngine compute instance is running, stop it before restarting the service. After the service is restarted, start this compute instance.

                                                                                              +
                                                                                            3. Interconnecting with OBS through Hive Metastore
                                                                                              1. Complete the configurations by referring to Interconnecting Hive with OBS using MetaStore.
                                                                                              2. Log in to MRS Manager, choose Cluster > Services > HetuEngine. On the displayed page, choose More > Synchronize Configuration. After the synchronization is complete, choose More > Synchronize Configuration again and then restart the HetuEngine service as prompted.

                                                                                                If a HetuEngine compute instance is running, stop it before restarting the service. After the service is restarted, start this compute instance.

                                                                                              3. No location needs to be specified when you log in to the HetuEngine client to create a schema or table. The schema or table is stored on OBS by default.
                                                                                          diff --git a/docs/mrs/umn/mrs_01_248996.html b/docs/mrs/umn/mrs_01_248996.html index 6a7a8dec6..cc34a6e39 100644 --- a/docs/mrs/umn/mrs_01_248996.html +++ b/docs/mrs/umn/mrs_01_248996.html @@ -19,7 +19,7 @@

                                                                                    -

                                                                                    Configuring Ranger Permissions

                                                                                    1. Log in to FusionInsight Manager and choose System > Permission > User Group. On the displayed page, click Create User Group to create a user group without any roles, for example, obs_hadoop.
                                                                                    2. Back to FusionInsight Manager and choose System > Permission > User. On the displayed page, click Create User to create a user that is associated only with the obs_hadoop user group, for example, hadoopuser.
                                                                                    3. Log in to the Ranger management page as the rangeradmin user.
                                                                                    4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                    5. Click Add New Policy and add the Read and Write permissions on the desired OBS paths to the created user group.

                                                                                      The following figure shows the configurations needed for adding the Read and Write permissions on obs://OBS parallel file system name/hadoop to user group obs_hadoop.

                                                                                      +

                                                                                      Configuring Ranger Permissions

                                                                                      1. Log in to MRS Manager and choose System > Permission > User Group. On the displayed page, click Create User Group to create a user group without any roles, for example, obs_hadoop.
                                                                                      2. Back to MRS Manager and choose System > Permission > User. On the displayed page, click Create User to create a user that is associated only with the obs_hadoop user group, for example, hadoopuser.
                                                                                      3. Log in to the Ranger management page as the rangeradmin user.
                                                                                      4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                      5. Click Add New Policy and add the Read and Write permissions on the desired OBS paths to the created user group.

                                                                                        The following figure shows the configurations needed for adding the Read and Write permissions on obs://OBS parallel file system name/hadoop to user group obs_hadoop.

                                                                                      diff --git a/docs/mrs/umn/mrs_01_248997.html b/docs/mrs/umn/mrs_01_248997.html index cc3029e40..2fa62dfb3 100644 --- a/docs/mrs/umn/mrs_01_248997.html +++ b/docs/mrs/umn/mrs_01_248997.html @@ -24,7 +24,7 @@

                                                                                  -

                                                                                  Configuring Ranger Permissions

                                                                                  1. Log in to FusionInsight Manager and choose System > Permission > User Group. On the displayed page, click Create User Group to create a user group without any roles, for example, obs_hadoop1.
                                                                                  2. Back to FusionInsight Manager and choose System > Permission > User. On the displayed page, click Create User to create a user that is associated with the obs_hadoop1 user group and the default role, for example, hadoopuser1.
                                                                                  3. Log in to the Ranger management page as the rangeradmin user.
                                                                                  4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                  5. Click Add New Policy and add the Read and Write permissions on the desired OBS paths to the user group created in 1.

                                                                                    The following figure shows the configurations needed for adding the Read and Write permissions on obs://OBS parallel file system name/hadoop1 to user group obs_hadoop1.

                                                                                    +

                                                                                    Configuring Ranger Permissions

                                                                                    1. Log in to MRS Manager and choose System > Permission > User Group. On the displayed page, click Create User Group to create a user group without any roles, for example, obs_hadoop1.
                                                                                    2. Back to MRS Manager and choose System > Permission > User. On the displayed page, click Create User to create a user that is associated with the obs_hadoop1 user group and the default role, for example, hadoopuser1.
                                                                                    3. Log in to the Ranger management page as the rangeradmin user.
                                                                                    4. On the home page, click component plug-in name OBS in the EXTERNAL AUTHORIZATION area.
                                                                                    5. Click Add New Policy and add the Read and Write permissions on the desired OBS paths to the user group created in 1.

                                                                                      The following figure shows the configurations needed for adding the Read and Write permissions on obs://OBS parallel file system name/hadoop1 to user group obs_hadoop1.

                                                                                    diff --git a/docs/mrs/umn/mrs_01_248998.html b/docs/mrs/umn/mrs_01_248998.html index 3645c0370..c9d8cd5af 100644 --- a/docs/mrs/umn/mrs_01_248998.html +++ b/docs/mrs/umn/mrs_01_248998.html @@ -1,7 +1,7 @@

                                                                                    Interconnecting MapReduce with OBS

                                                                                    -

                                                                                    Interconnecting with OBS

                                                                                    1. Log in to FusionInsight Manager, choose Cluster > Services > MapReduce and choose Configurations > All Configurations. In the navigation tree, choose MapReduce > Customization. In the customized configuration items, add the configuration item mapreduce.jobhistory.always-scan-user-dir to core-site.xml and set the parameter to true.

                                                                                      +

                                                                                      Interconnecting with OBS

                                                                                      1. Log in to MRS Manager, choose Cluster > Services > MapReduce and choose Configurations > All Configurations. In the navigation tree, choose MapReduce > Customization. In the customized configuration items, add the configuration item mapreduce.jobhistory.always-scan-user-dir to core-site.xml and set the parameter to true.

                                                                                      2. Save the configurations and restart the MapReduce service.
                                                                                      diff --git a/docs/mrs/umn/mrs_01_249283.html b/docs/mrs/umn/mrs_01_249283.html index 0c75e72b5..720f7f4b0 100644 --- a/docs/mrs/umn/mrs_01_249283.html +++ b/docs/mrs/umn/mrs_01_249283.html @@ -2,8 +2,8 @@

                                                                                      Quickly Creating a Doris Cluster

                                                                                      This section describes how to quickly create a Doris cluster. Doris is a high-performance, real-time analytical database, suitable for report analysis, ad hoc query, and federated data lake query acceleration.

                                                                                      -

                                                                                      A Doris cluster contains only the Doris 1.2.3 component.

                                                                                      -

                                                                                      Quickly Creating a Doris Cluster

                                                                                      1. Log in to the MRS management console.
                                                                                      2. Click Create Cluster. The page for creating a cluster is displayed.
                                                                                      3. On the displayed page, click the Quick Config tab.
                                                                                      4. Configure basic information as follows. For details about the parameters, see Creating a Custom Cluster.

                                                                                        • Region: Retain the default value.
                                                                                        • Cluster Name: You can use the default name or add the project name initials or dates for distinction, for example, mrs_20180321.
                                                                                        • Cluster Type: Select Doris Cluster.
                                                                                        • Cluster Version: The latest version is selected by default. (Components vary depending on the version type. Select a version type as needed.)
                                                                                        • Component: Select Doris Cluster.
                                                                                        • AZ: Retain the default value.
                                                                                        • Enterprise Project: Select the default project.
                                                                                        • VPC: Retain the default value. If there is no available VPC, click View VPC to access the VPC console and create one.
                                                                                        • Subnet: Retain the default value.
                                                                                        • CPU Architecture: Use the default value.
                                                                                        • Cluster Nodes: Set the number of cluster nodes and node specifications based on your needs. For MRS 3.x and later, the memory of a master node must be at least 64 GB.
                                                                                        • Kerberos Authentication: Whether to enable Kerberos authentication. This option cannot be changed after you create a cluster.
                                                                                        • Username: The default value is root/admin. User root is used to remotely log in to ECSs and user admin is used to access FusionInsight Manager.
                                                                                        • Password: Set a password for user root/admin.
                                                                                        • Confirm Password: Enter the password of user root/admin again.
                                                                                        +

                                                                                        A Doris cluster contains only the Doris component.

                                                                                        +

                                                                                        Quickly Creating a Doris Cluster

                                                                                        1. Log in to the MRS management console.
                                                                                        2. Click Create Cluster. The page for creating a cluster is displayed.
                                                                                        3. On the displayed page, click the Quick Config tab.
                                                                                        4. Configure basic information as follows. For details about the parameters, see Creating a Custom Cluster.

                                                                                          • Region: Retain the default value.
                                                                                          • Cluster Name: You can use the default name or add the project name initials or dates for distinction, for example, mrs_20180321.
                                                                                          • Cluster Type: Select Doris Cluster.
                                                                                          • Cluster Version: The latest version is selected by default. (Components vary depending on the version type. Select a version type as needed.)
                                                                                          • Component: Select Doris Cluster.
                                                                                          • AZ: Retain the default value.
                                                                                          • VPC: Retain the default value. If there is no available VPC, click View VPC to access the VPC console and create one.
                                                                                          • Subnet: Retain the default value.
                                                                                          • CPU Architecture: Use the default value.
                                                                                          • Cluster Nodes: Set the number of cluster nodes and node specifications based on your needs. For MRS 3.x and later, the memory of a master node must be at least 64 GB.
                                                                                          • Kerberos Authentication: Whether to enable Kerberos authentication. This option cannot be changed after you create a cluster.
                                                                                          • Username: The default value is root/admin. User root is used to remotely log in to ECSs and user admin is used to access MRS Manager.
                                                                                          • Password: Set a password for user root/admin.
                                                                                          • Confirm Password: Enter the password of user root/admin again.

                                                                                        5. Select Enable to enable secure communications. For details, see Communication Security Authorization.
                                                                                        6. Click Create Now.

                                                                                          If Kerberos Authentication is toggled on, the system asks you to confirm whether this function is required. If it is, click Continue. If not, click Back to disable it and then proceed with the subsequent steps. This option cannot be changed after you create a cluster.

                                                                                        7. Click Back to Cluster List to view the cluster status. Click Access Cluster to view cluster details.

                                                                                          For details about cluster status during creation, see the description of the status parameters in Table 1.

                                                                                          It takes some time to create a cluster. The initial status of the cluster is Starting. The cluster status will change to Running if the cluster is successfully created.

                                                                                          diff --git a/docs/mrs/umn/mrs_01_9003.html b/docs/mrs/umn/mrs_01_9003.html index f17f0ebc2..09cdc74ea 100644 --- a/docs/mrs/umn/mrs_01_9003.html +++ b/docs/mrs/umn/mrs_01_9003.html @@ -8,7 +8,18 @@

                                                                                  2025-06-11

                                                                                  +

                                                                                  2025-08-08

                                                                                  +

                                                                                  Modified the following content:

                                                                                  + +
                                                                                  Added the following alarms: +
                                                                                  +

                                                                                  2025-06-11

                                                                                  Added the operations to interconnect MRS with LTS. For details, see How Do I Interconnect MRS with LTS?

                                                                                  Optimized the image format.

                                                                                  2025-03-14

                                                                                  +

                                                                                  2025-03-14

                                                                                  Modified the following content:

                                                                                  +

                                                                                  Modified the following content:

                                                                                  2024-08-02

                                                                                  Modified the following content:

                                                                                  -

                                                                                  Flume

                                                                                  Client installation directory/fusioninsight-flume-xxx/conf

                                                                                  +

                                                                                  Client installation directory/*-flume-xxx/conf

                                                                                  HBase

                                                                                  diff --git a/docs/mrs/umn/mrs_03_1214.html b/docs/mrs/umn/mrs_03_1214.html index ad04f988c..76427443f 100644 --- a/docs/mrs/umn/mrs_03_1214.html +++ b/docs/mrs/umn/mrs_03_1214.html @@ -2,7 +2,7 @@

                                                                                  How Do I Do If Sessions Are Not Released After Hue Connects to HiveServer and the Error Message "over max user connections" Is Displayed?

                                                                                  Applicable versions: MRS 3.1.0 and earlier

                                                                                  -
                                                                                  1. Modify the following file on the two Hue nodes:

                                                                                    /opt/Bigdata/FusionInsight_Porter_8.*/install/FusionInsight-Hue-*/hue/apps/beeswax/src/beeswax/models.py

                                                                                    +
                                                                                    1. Modify the following file on the two Hue nodes:

                                                                                      /opt/Bigdata/*_Porter_8.*/install/*-Hue-*/hue/apps/beeswax/src/beeswax/models.py

                                                                                    2. Change the configurations in lines 396 and 404.

                                                                                      Change q Changed = self.filter(owner=user, application=application).exclude(guid='').exclude(secret='') to q = self.filter(owner=user, application=application).exclude(guid=None).exclude(secret=None).

                                                                                    diff --git a/docs/mrs/umn/mrs_07_020001.html b/docs/mrs/umn/mrs_07_020001.html index 0c9fa2f5d..81463bed6 100644 --- a/docs/mrs/umn/mrs_07_020001.html +++ b/docs/mrs/umn/mrs_07_020001.html @@ -69,7 +69,7 @@
                                                                                  2. Run shell commands on the client in kinit mode.

                                                                                  ST

                                                                                  An ST is generated by the Kerberos service and used to establish a secure session between an application and application service. An ST is valid only once.

                                                                                  -

                                                                                  In FusionInsight products, the generation of an ST is based on the Hadoop-RPC communication. The underlying RPC submits a request to the Kerberos server and the Kerberos server generates an ST.

                                                                                  +

                                                                                  In MRS products, the generation of an ST is based on the Hadoop-RPC communication. The underlying RPC submits a request to the Kerberos server and the Kerberos server generates an ST.

                                                                                  Sample Authentication Code

                                                                                  import java.io.IOException;
 
diff --git a/docs/mrs/umn/mrs_08_0001.html b/docs/mrs/umn/mrs_08_0001.html
index 61344a32b..04c42a94e 100644
--- a/docs/mrs/umn/mrs_08_0001.html
+++ b/docs/mrs/umn/mrs_08_0001.html
@@ -19,7 +19,7 @@
 
                                                                                  MRS provides a unified O&M management platform for cluster management, supporting one-click cluster deployment, multi-version selection, as well as manual scaling and auto scaling of clusters without service interruption. In addition, MRS provides job management, resource tag management, and O&M of the preceding data processing components at each layer. It also provides one-stop O&M capabilities, covering monitoring, alarm reporting, configuration, and patch upgrade.
                                                                                  -

                                                                                  Product Advantages

                                                                                  MRS has a powerful Hadoop kernel team and is deployed based on enterprise-level FusionInsight big data platform. MRS has been deployed on tens of thousands of nodes and can ensure Service Level Agreements (SLAs) for multi-level users.

                                                                                  +

                                                                                  Product Advantages

                                                                                  MRS has a powerful Hadoop kernel team and is deployed based on enterprise-level big data platform. MRS has been deployed on tens of thousands of nodes and can ensure Service Level Agreements (SLAs) for multi-level users.

                                                                                  MRS has the following advantages:

                                                                                  • High performance

                                                                                    MRS supports self-developed CarbonData storage technology. CarbonData is a high-performance big data storage solution. It allows one data set to apply to multiple scenarios and supports features, such as multi-level indexing, dictionary encoding, pre-aggregation, dynamic partitioning, and quasi-real-time data query. This improves I/O scanning and computing performance and returns analysis results of tens of billions of data records in seconds. In addition, MRS supports self-developed enhanced scheduler Superior, which breaks the scale bottleneck of a single cluster and is capable of scheduling over 10,000 nodes in a cluster.

                                                                                  • Cost-effectiveness

                                                                                    Based on diversified cloud infrastructure, MRS provides various computing and storage choices and separates computing from storage, delivering cost-effective massive data storage solutions. MRS supports auto scaling to address peak and off-peak service loads, releasing idle resources on the big data platform for customers. MRS clusters can be created and scaled out when you need them, and can be terminated or scaled in after you use them, minimizing cost.

                                                                                    diff --git a/docs/mrs/umn/mrs_08_0005.html b/docs/mrs/umn/mrs_08_0005.html index 39fdb0484..b128fbdbb 100644 --- a/docs/mrs/umn/mrs_08_0005.html +++ b/docs/mrs/umn/mrs_08_0005.html @@ -5,329 +5,445 @@
                                                                                    • Hadoop includes HDFS, YARN, and MapReduce.
                                                                                    • DBService, ZooKeeper, KrbServer, and LdapServer are components used in the cluster and are not displayed during cluster creation.
                                                                                    • MRS component versions must be consistent with open-source component versions.
                                                                                    -
                                                                                    Table 1 MRS component versions

                                                                                    Component

                                                                                    +
                                                                                    - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + - - - - + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/mrs/umn/mrs_08_00132.html b/docs/mrs/umn/mrs_08_00132.html index 17fa6dee8..8e9c4e143 100644 --- a/docs/mrs/umn/mrs_08_00132.html +++ b/docs/mrs/umn/mrs_08_00132.html @@ -1,7 +1,7 @@

                                                                                    Relationship Between Kafka and Other Components

                                                                                    -

                                                                                    As a message publishing and subscription system, Kafka provides high-speed data transmission methods for data transmission between different subsystems of the FusionInsight platform. It can receive external messages in a real-time manner and provides the messages to the online and offline services for processing. The following figure shows the relationship between Kafka and other components.

                                                                                    +

                                                                                    As a message publishing and subscription system, Kafka provides high-speed data transmission methods for data transmission between different subsystems of the platform. It can receive external messages in a real-time manner and provides the messages to the online and offline services for processing. The following figure shows the relationship between Kafka and other components.

                                                                                    Figure 1 Relationship with Other Components
                                                                                    diff --git a/docs/mrs/umn/mrs_08_0038.html b/docs/mrs/umn/mrs_08_0038.html new file mode 100644 index 000000000..365ddb561 --- /dev/null +++ b/docs/mrs/umn/mrs_08_0038.html @@ -0,0 +1,27 @@ + + +

                                                                                    Impala

                                                                                    +

                                                                                    Impala

                                                                                    Impala provides fast, interactive SQL queries directly on your Apache Hadoop data stored in HDFS, HBase, or the Object Storage Service (OBS). In addition to using the same unified storage platform, Impala also uses the same metadata, SQL syntax (Hive SQL), ODBC driver, and user interface (Impala query UI in Hue) as Apache Hive. This provides a familiar and unified platform for real-time or batch-oriented queries. Impala is an addition to tools available for querying big data. Impala does not replace the batch processing frameworks built on MapReduce such as Hive. Hive and other frameworks built on MapReduce are best suited for long running batch jobs.

                                                                                    +

                                                                                    Impala provides the following features:

                                                                                    +
                                                                                    • Most common SQL-92 features of Hive Query Language (HiveQL) including SELECT, JOIN, and aggregate functions
                                                                                    • HDFS, HBase, and OBS storage, including:
                                                                                      • HDFS file formats: delimited text files, Parquet, Avro, SequenceFile, and RCFile
                                                                                      • Compression codecs: Snappy, GZIP, Deflate, BZIP
                                                                                      +
                                                                                    • Common data access interfaces including:
                                                                                      • JDBC driver
                                                                                      • ODBC driver
                                                                                      • Hue Beeswax and the Impala query UI
                                                                                      +
                                                                                    • impala-shell command line interface
                                                                                    • Kerberos authentication
                                                                                    +

                                                                                    Impala applies to offline analysis (such as log and cluster status analysis) of real-time data queries, large-scale data mining (such as user behavior analysis, interest region analysis, and region display), and other scenarios.

                                                                                    +

                                                                                    Impala consists of three roles: Impala Daemon (Impalad), Impala StateStore, and Impala Catalog Service.

                                                                                    +
                                                                                    +

                                                                                    Impala Daemon

                                                                                    The core Impala component is the Impala daemon, physically represented by the impalad process.

                                                                                    +

                                                                                    A few of the key functions that an Impala daemon performs are:

                                                                                    +
                                                                                    • Runs on all data nodes.
                                                                                    • Reads and writes to data files.
                                                                                    • Accepts queries transmitted from the impala-shell command, Hue, JDBC, or ODBC.
                                                                                    • Parallelizes the queries and transmits intermediate query results back to the central coordinator.
                                                                                    • Invokes a node to return the query results to the client.
                                                                                    +

                                                                                    The Impala daemons are in constant communication with StateStore, to confirm which daemons are healthy and can accept new work.

                                                                                    +
                                                                                    +

                                                                                    Impala StateStore

                                                                                    The Impala component known as the StateStore checks on the health of all Impala daemons in a cluster, and continuously relays its findings to each of those daemons. It is physically represented by a daemon process named statestored. You only need such a process on one host in a cluster. If an Impala daemon goes offline due to hardware failure, network error, software issue, or other reason, the StateStore informs all the other Impala daemons so that future queries can avoid making requests to the unreachable Impala daemon.

                                                                                    +
                                                                                    +

                                                                                    Impala Catalog Service

                                                                                    The Impala component known as the Catalog Service relays the metadata changes from Impala SQL statements to all the Impala daemons in a cluster. It is physically represented by a daemon process named catalogd. When you create a table, load data, and so on through Hive, you do need to issue REFRESH or INVALIDATE METADATA on an Impala daemon before executing a query there. The catalog service avoids the need to issue REFRESH and INVALIDATE METADATA statements when the metadata changes are performed by statements issued through Impala.

                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    Parent topic: Components
                                                                                    +
                                                                                    +
                                                                                    + diff --git a/docs/mrs/umn/mrs_08_0039.html b/docs/mrs/umn/mrs_08_0039.html new file mode 100644 index 000000000..7447fb7b5 --- /dev/null +++ b/docs/mrs/umn/mrs_08_0039.html @@ -0,0 +1,21 @@ + + +

                                                                                    Kudu

                                                                                    +

                                                                                    Kudu is a column-store manager developed for the Apache Hadoop platform. Kudu shares the common technical properties of Hadoop ecosystem applications, that is, it runs on commodity hardware, which is horizontally scalable, delivering high availability.

                                                                                    +

                                                                                    Kudu's design has the following benefits:

                                                                                    +
                                                                                    • Fast processing of OLAP workloads
                                                                                    • Integration with MapReduce, Spark and other Hadoop ecosystem components
                                                                                    • Tight integration with Apache Impala, making it a good, mutable alternative to using HDFS with Apache Parquet
                                                                                    • Strong but flexible consistency model, allowing you to choose consistency requirements on a per-request basis, including the option for strict-serializable consistency
                                                                                    • Strong performance for running sequential and random workloads simultaneously
                                                                                    • Easy to manage
                                                                                    • High availability Tablet Servers and Masters use the Raft Consensus Algorithm, which ensures that as long as more than half the total number of replicas is available, the tablet is available for reads and writes. For example, if 2 out of 3 replicas or 3 out of 5 replicas are available, the tablet is available. Reads can be serviced by read-only follower tablets, even in the event of a leader tablet failure.
                                                                                    • Structured data model
                                                                                    +

                                                                                    By combining all of these properties, Kudu targets support for families of applications that are difficult or impossible to implement on current generation Hadoop storage technologies.

                                                                                    +
                                                                                    A few examples of applications for which Kudu is a great solution are:
                                                                                    • Reporting applications where newly-arrived data needs to be immediately available for end users
                                                                                    • Time-series applications that must simultaneously support queries across large amounts of historic data and granular queries about an individual entity that must return very quickly
                                                                                    • Applications that use predictive models to make real-time decisions with periodic refreshes of the predictive model based on all historic data
                                                                                    +
                                                                                    +

                                                                                    Relationships with other components

                                                                                    • HBase

                                                                                      Kudu is designed based on the HBase structure and can implement fast random read/write and update functions that HBase features.

                                                                                      +

                                                                                      The differences are as follows:

                                                                                      +
                                                                                      • HBase uses ZooKeeper to ensure data consistency, whereas Kudu uses the Raft consensus algorithm to ensure consistency.
                                                                                      • HBase uses HDFS for resilient data storage, whereas Kudu uses TServer to ensure strong data consistency and reliability.
                                                                                      +
                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    Parent topic: Components
                                                                                    +
                                                                                    +
                                                                                    + diff --git a/docs/mrs/umn/mrs_08_0052.html b/docs/mrs/umn/mrs_08_0052.html index f3fc7fee0..5649babf3 100644 --- a/docs/mrs/umn/mrs_08_0052.html +++ b/docs/mrs/umn/mrs_08_0052.html @@ -36,6 +36,8 @@
                                                                                  • Hue
                                                                                    • +
                                                                                  • Impala
                                                                                    +
                                                                                  • IoTDB
                                                                                  • JobGateway
                                                                                    @@ -46,12 +48,16 @@
                                                                                  • KrbServer and LdapServer
                                                                                    • +
                                                                                  • Kudu
                                                                                    +
                                                                                  • Loader
                                                                                  • Manager
                                                                                  • MapReduce
                                                                                    • +
                                                                                  • MemArtsCC
                                                                                    +
                                                                                  • Oozie
                                                                                  • OpenTSDB
                                                                                    diff --git a/docs/mrs/umn/mrs_08_0116.html b/docs/mrs/umn/mrs_08_0116.html new file mode 100644 index 000000000..19ccea9be --- /dev/null +++ b/docs/mrs/umn/mrs_08_0116.html @@ -0,0 +1,17 @@ + + +

                                                                                    MemArtsCC

                                                                                    +
                                                                                    + + diff --git a/docs/mrs/umn/mrs_08_0117.html b/docs/mrs/umn/mrs_08_0117.html new file mode 100644 index 000000000..5a8f4704d --- /dev/null +++ b/docs/mrs/umn/mrs_08_0117.html @@ -0,0 +1,44 @@ + + +

                                                                                    MemArtsCC Basic Principles

                                                                                    +

                                                                                    MemArtsCC is a distributed lightweight caching system deployed on the compute side in the storage-compute decoupled architecture. It prefetches data from remote object storage to accelerate caching and computing jobs.

                                                                                    +

                                                                                    MemArtsCC shards objects on remote OBS and creates indexes, greatly improving the performance of reading cached data. ZooKeeper enables lightweight service discovery and provides ultra-high availability. The lifecycle management of sharded data is based on the LRU algorithm.

                                                                                    +

                                                                                    +

                                                                                    Main Features of MemArtsCC

                                                                                    • The decentralized architecture enables all instances to provide same service capabilities.
                                                                                    • The lightweight design ensures ultra-low resource usage.
                                                                                    • MemArtsCC is decoupled from applications and therefore is transparent to them and can be used without adaptation.
                                                                                    • MemArtsCC ensures high availability in case of node failures.
                                                                                    +
                                                                                    +

                                                                                    MemArtsCC Structure

                                                                                    There are CCSideCar and CCWorker roles of MemArtsCC instances.

                                                                                    +

                                                                                    In a storage-compute decoupled architecture, data of computing and analytics applications such as Spark and Hive is stored in OBS. In a MemArtsCC cluster, a service instance is called a worker. Workers cache some or all of the object data in OBS to local persistent storage (SSD/HDD). When an application reads an object through the MemArtsCC SDK, the application reads sharded data from a specific worker based on the shard index. If the cache is hit, the worker returns the shards. If the cache is not hit, the application directly reads data from OBS. The worker asynchronously loads the shards that are not hit to local storage for subsequent use.

                                                                                    +
                                                                                    Figure 1 MemArtsCC Structure
                                                                                    + +
                                                                                    • Table 1 MRS component versions

                                                                                    Component

                                                                                    MRS 3.1.2-LTS.6

                                                                                    +

                                                                                    MRS 3.1.2-LTS.6

                                                                                    MRS 3.2.0-LTS.2

                                                                                    +

                                                                                    MRS 3.2.0-LTS.2

                                                                                    3.3.0-LTS.1

                                                                                    +

                                                                                    MRS 3.3.0-LTS.1

                                                                                    +

                                                                                    MRS 3.5.0-LTS

                                                                                    Alluxio

                                                                                    +

                                                                                    Alluxio

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    CarbonData

                                                                                    +

                                                                                    CarbonData

                                                                                    2.2.0

                                                                                    +

                                                                                    2.2.0

                                                                                    2.2.0

                                                                                    +

                                                                                    2.2.0

                                                                                    2.2.0

                                                                                    +

                                                                                    2.2.0

                                                                                    +

                                                                                    2.2.0

                                                                                    CDL

                                                                                    +

                                                                                    CDL

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    1.0.0

                                                                                    +

                                                                                    1.0.0

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    ClickHouse

                                                                                    +

                                                                                    ClickHouse

                                                                                    21.3.4.25

                                                                                    +

                                                                                    21.3.4.25

                                                                                    22.3.2.2

                                                                                    +

                                                                                    22.3.2.2

                                                                                    23.3.2.37

                                                                                    +

                                                                                    23.3.2.37

                                                                                    +

                                                                                    23.3.2.37

                                                                                    DBService

                                                                                    +

                                                                                    DBService

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    Doris

                                                                                    +

                                                                                    Doris

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    1.2.3

                                                                                    +

                                                                                    1.2.3

                                                                                    +

                                                                                    2.0.13

                                                                                    Flink

                                                                                    +

                                                                                    Flink

                                                                                    1.12.2

                                                                                    +

                                                                                    1.12.2

                                                                                    1.15.0

                                                                                    +

                                                                                    1.15.0

                                                                                    1.15.0

                                                                                    +

                                                                                    1.15.0

                                                                                    +

                                                                                    1.17.1

                                                                                    Flume

                                                                                    +

                                                                                    Flume

                                                                                    1.9.0

                                                                                    +

                                                                                    1.9.0

                                                                                    1.9.0

                                                                                    +

                                                                                    1.9.0

                                                                                    1.11.0

                                                                                    +

                                                                                    1.11.0

                                                                                    +

                                                                                    1.11.0

                                                                                    Guardian

                                                                                    +

                                                                                    Guardian

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    0.1.0

                                                                                    +

                                                                                    0.1.0

                                                                                    +

                                                                                    0.1.0

                                                                                    HBase

                                                                                    +

                                                                                    HBase

                                                                                    2.2.3

                                                                                    +

                                                                                    2.2.3

                                                                                    2.2.3

                                                                                    +

                                                                                    2.2.3

                                                                                    2.4.14

                                                                                    +

                                                                                    2.4.14

                                                                                    +

                                                                                    2.4.14

                                                                                    HDFS

                                                                                    +

                                                                                    HDFS

                                                                                    3.1.1

                                                                                    +

                                                                                    3.1.1

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    HetuEngine

                                                                                    +

                                                                                    HetuEngine

                                                                                    1.2.0

                                                                                    +

                                                                                    1.2.0

                                                                                    1.2.0

                                                                                    +

                                                                                    1.2.0

                                                                                    2.0.0

                                                                                    +

                                                                                    2.0.0

                                                                                    +

                                                                                    2.1.0

                                                                                    Hive

                                                                                    +

                                                                                    Hive

                                                                                    3.1.0

                                                                                    +

                                                                                    3.1.0

                                                                                    3.1.0

                                                                                    +

                                                                                    3.1.0

                                                                                    3.1.0

                                                                                    +

                                                                                    3.1.0

                                                                                    +

                                                                                    3.1.0

                                                                                    Hudi

                                                                                    +

                                                                                    Hudi

                                                                                    0.9.0

                                                                                    +

                                                                                    0.9.0

                                                                                    0.11.0

                                                                                    +

                                                                                    0.11.0

                                                                                    0.11.0

                                                                                    +

                                                                                    0.11.0

                                                                                    +

                                                                                    0.15.0

                                                                                    Hue

                                                                                    +

                                                                                    Hue

                                                                                    4.7.0

                                                                                    +

                                                                                    4.7.0

                                                                                    4.7.0

                                                                                    +

                                                                                    4.7.0

                                                                                    4.7.0

                                                                                    +

                                                                                    4.7.0

                                                                                    +

                                                                                    -

                                                                                    IoTDB

                                                                                    +

                                                                                    IoTDB

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    0.14.0

                                                                                    +

                                                                                    0.14.0

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    JobGateway

                                                                                    +

                                                                                    JobGateway

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    1.1.0

                                                                                    +

                                                                                    1.0.0

                                                                                    +

                                                                                    1.0.0

                                                                                    Kafka

                                                                                    +

                                                                                    Kafka

                                                                                    2.11-2.4.0

                                                                                    +

                                                                                    2.11-2.4.0

                                                                                    2.11-2.4.0

                                                                                    +

                                                                                    2.11-2.4.0

                                                                                    2.12-2.8.1

                                                                                    +

                                                                                    2.12-2.8.1

                                                                                    +

                                                                                    2.12-3.6.1

                                                                                    KafkaManager

                                                                                    +

                                                                                    KafkaManager

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    KrbServer

                                                                                    +

                                                                                    KrbServer

                                                                                    1.18

                                                                                    +

                                                                                    1.18

                                                                                    1.18

                                                                                    +

                                                                                    1.18

                                                                                    1.20

                                                                                    +

                                                                                    1.20

                                                                                    +

                                                                                    1.20

                                                                                    LdapServer

                                                                                    +

                                                                                    LdapServer

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    +

                                                                                    2.7.0

                                                                                    Loader

                                                                                    +

                                                                                    Loader

                                                                                    1.99.3

                                                                                    +

                                                                                    1.99.3

                                                                                    1.99.3

                                                                                    +

                                                                                    1.99.3

                                                                                    1.99.3

                                                                                    +

                                                                                    1.99.3

                                                                                    +

                                                                                    -

                                                                                    MapReduce

                                                                                    +

                                                                                    MapReduce

                                                                                    3.1.1

                                                                                    +

                                                                                    3.1.1

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    Oozie

                                                                                    +

                                                                                    MemArtsCC

                                                                                    5.1.0

                                                                                    +

                                                                                    -

                                                                                    5.1.0

                                                                                    +

                                                                                    -

                                                                                    5.10

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    3.22

                                                                                    OpenTSDB

                                                                                    +

                                                                                    Oozie

                                                                                    -

                                                                                    +

                                                                                    5.1.0

                                                                                    -

                                                                                    +

                                                                                    5.1.0

                                                                                    -

                                                                                    +

                                                                                    5.1.0

                                                                                    +

                                                                                    5.1.0

                                                                                    Presto

                                                                                    +

                                                                                    OpenTSDB

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    Phoenix (integrated in HBase)

                                                                                    +

                                                                                    Presto

                                                                                    5.0.0

                                                                                    +

                                                                                    -

                                                                                    5.0.0

                                                                                    +

                                                                                    -

                                                                                    5.1.2

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    Ranger

                                                                                    +

                                                                                    Phoenix (integrated in HBase)

                                                                                    2.0.0

                                                                                    +

                                                                                    5.0.0

                                                                                    2.0.0

                                                                                    +

                                                                                    5.0.0

                                                                                    2.3.0

                                                                                    +

                                                                                    5.1.2

                                                                                    +

                                                                                    5.1.2

                                                                                    Spark

                                                                                    +

                                                                                    Ranger

                                                                                    -

                                                                                    +

                                                                                    2.0.0

                                                                                    -

                                                                                    +

                                                                                    2.0.0

                                                                                    3.3.1

                                                                                    +

                                                                                    2.3.0

                                                                                    +

                                                                                    2.3.0

                                                                                    Spark2x

                                                                                    +

                                                                                    Spark

                                                                                    3.1.1

                                                                                    +

                                                                                    -

                                                                                    3.1.1

                                                                                    +

                                                                                    -

                                                                                    -

                                                                                    +

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    Storm

                                                                                    +

                                                                                    Spark2x

                                                                                    -

                                                                                    +

                                                                                    3.1.1

                                                                                    -

                                                                                    +

                                                                                    3.1.1

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    Tez

                                                                                    +

                                                                                    Storm

                                                                                    0.9.2

                                                                                    +

                                                                                    -

                                                                                    0.9.2

                                                                                    +

                                                                                    -

                                                                                    0.10.2

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    YARN

                                                                                    +

                                                                                    Tez

                                                                                    3.1.1

                                                                                    +

                                                                                    0.9.2

                                                                                    3.3.1

                                                                                    +

                                                                                    0.9.2

                                                                                    3.3.1

                                                                                    +

                                                                                    0.10.2

                                                                                    +

                                                                                    0.10.2

                                                                                    ZooKeeper

                                                                                    +

                                                                                    YARN

                                                                                    3.6.3

                                                                                    +

                                                                                    3.1.1

                                                                                    3.6.3

                                                                                    +

                                                                                    3.3.1

                                                                                    3.8.1

                                                                                    +

                                                                                    3.3.1

                                                                                    +

                                                                                    3.3.1

                                                                                    MRS Manager

                                                                                    +

                                                                                    ZooKeeper

                                                                                    8.1.2

                                                                                    +

                                                                                    3.6.3

                                                                                    8.2.0.1

                                                                                    +

                                                                                    3.6.3

                                                                                    8.3.0.1

                                                                                    +

                                                                                    3.8.1

                                                                                    +

                                                                                    3.8.1

                                                                                    +

                                                                                    Sqoop

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    1.4.7

                                                                                    +

                                                                                    Kudu

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    1.17.0

                                                                                    +

                                                                                    Impala

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    -

                                                                                    +

                                                                                    4.3.0

                                                                                    +

                                                                                    MRS Manager

                                                                                    +

                                                                                    8.1.2

                                                                                    +

                                                                                    8.2.0.1

                                                                                    +

                                                                                    8.3.0.1

                                                                                    +

                                                                                    8.5.0
                                                                                    + + + + + + + + + + + + + +
                                                                                    Table 1 MemArtsCC architecture

                                                                                    Name

                                                                                    +

                                                                                    Description

                                                                                    +

                                                                                    MemArtsCC SDK

                                                                                    +

                                                                                    An SDK used by OBSA (a Hadoop client plug-in) to access OBS server objects.

                                                                                    +

                                                                                    CCSideCar

                                                                                    +

                                                                                    The management plane service. It monitors MemArtsCC, collects data, delivers configurations, and starts and stops the service.

                                                                                    +

                                                                                    CCWorker

                                                                                    +

                                                                                    The data plane service. It reads, writes, stores, and deletes data cached by MemArtsCC.

                                                                                    +
                                                                                    +
                                                                                    + + +
                                                                                    +
                                                                                    +
                                                                                    Parent topic: MemArtsCC
                                                                                    +
                                                                                    +
                                                                                    + diff --git a/docs/mrs/umn/mrs_08_0118.html b/docs/mrs/umn/mrs_08_0118.html new file mode 100644 index 000000000..1409d0e59 --- /dev/null +++ b/docs/mrs/umn/mrs_08_0118.html @@ -0,0 +1,22 @@ + + +

                                                                                    Relationships Between MemArtsCC and Other Components

                                                                                    +

                                                                                    OBS

                                                                                    OBS provides a new InputStream: OBSMemArtsCCInputStream. This InputStream reads data from the MemArtsCC cluster deployed on the compute side to reduce OBS server pressure and improve data read performance.

                                                                                    +

                                                                                    MemArtsCC persistently stores data to SSDs on the compute side. OBS interconnects with MemArtsCC to:

                                                                                    +
                                                                                    1. Improve data access performance in the decoupled storage-compute architecture.

                                                                                      The local storage of MemArtsCC avoids the cross-network access to hotspot data. This accelerates the data reads of OBS upper-layer applications.

                                                                                      +
                                                                                    1. Reduce the pressure on the OBS server.

                                                                                      MemArtsCC stores hotspot data in the compute cluster to reduce the bandwidth pressure of the OBS server.

                                                                                      +
                                                                                    +
                                                                                    +

                                                                                    Spark

                                                                                    Spark reads data from OBS. OBS reads data from MemArtsCC. If data is hit in the local cache, the data is read directly. Otherwise, the data is prefetched.

                                                                                    +
                                                                                    +

                                                                                    Hive

                                                                                    Hive reads data from OBS. OBS reads data from MemArtsCC. If data is hit in the local cache, the data is read directly. Otherwise, the data is prefetched.

                                                                                    +
                                                                                    +

                                                                                    HetuEngine

                                                                                    HetuEngine reads data from OBS. OBS reads data from MemArtsCC. If data is hit in the local cache, the data is read directly. Otherwise, the data is prefetched.

                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    +
                                                                                    Parent topic: MemArtsCC
                                                                                    +
                                                                                    +
                                                                                    +