diff --git a/umn/source/_static/images/en-us_image_0000001392414442.png b/umn/source/_static/images/en-us_image_0000001072559365.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414442.png rename to umn/source/_static/images/en-us_image_0000001072559365.png diff --git a/umn/source/_static/images/en-us_image_0000001392574038.png b/umn/source/_static/images/en-us_image_0000001080201158.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574038.png rename to umn/source/_static/images/en-us_image_0000001080201158.png diff --git a/umn/source/_static/images/en-us_image_0000001442413857.png b/umn/source/_static/images/en-us_image_0000001085773316.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413857.png rename to umn/source/_static/images/en-us_image_0000001085773316.png diff --git a/umn/source/_static/images/en-us_image_0000001532448290.png b/umn/source/_static/images/en-us_image_0000001086795516.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448290.png rename to umn/source/_static/images/en-us_image_0000001086795516.png diff --git a/umn/source/_static/images/en-us_image_0000001582927573.png b/umn/source/_static/images/en-us_image_0000001087171010.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927573.png rename to umn/source/_static/images/en-us_image_0000001087171010.png diff --git a/umn/source/_static/images/en-us_image_0000001442773633.png b/umn/source/_static/images/en-us_image_0000001087459671.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773633.png rename to umn/source/_static/images/en-us_image_0000001087459671.png diff --git a/umn/source/_static/images/en-us_image_0000001583087521.png b/umn/source/_static/images/en-us_image_0000001088608580.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087521.png rename to umn/source/_static/images/en-us_image_0000001088608580.png diff --git a/umn/source/_static/images/en-us_image_0000001532448142.png b/umn/source/_static/images/en-us_image_0000001125163135.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448142.png rename to umn/source/_static/images/en-us_image_0000001125163135.png diff --git a/umn/source/_static/images/en-us_image_0000001442653705.png b/umn/source/_static/images/en-us_image_0000001127057881.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653705.png rename to umn/source/_static/images/en-us_image_0000001127057881.png diff --git a/umn/source/_static/images/en-us_image_0000001532607774.png b/umn/source/_static/images/en-us_image_0000001133372255.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607774.png rename to umn/source/_static/images/en-us_image_0000001133372255.png diff --git a/umn/source/_static/images/en-us_image_0000001532607870.png b/umn/source/_static/images/en-us_image_0000001135452179.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607870.png rename to umn/source/_static/images/en-us_image_0000001135452179.png diff --git a/umn/source/_static/images/en-us_image_0000001582807813.png b/umn/source/_static/images/en-us_image_0000001135745627.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807813.png rename to umn/source/_static/images/en-us_image_0000001135745627.png diff --git a/umn/source/_static/images/en-us_image_0000001392574070.png b/umn/source/_static/images/en-us_image_0000001151336594.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574070.png rename to umn/source/_static/images/en-us_image_0000001151336594.png diff --git a/umn/source/_static/images/en-us_image_0000001151963015.png b/umn/source/_static/images/en-us_image_0000001151963015.png new file mode 100644 index 0000000..c5cb07b Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001151963015.png differ diff --git a/umn/source/_static/images/en-us_image_0000001532448146.png b/umn/source/_static/images/en-us_image_0000001159690571.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448146.png rename to umn/source/_static/images/en-us_image_0000001159690571.png diff --git a/umn/source/_static/images/en-us_image_0000001532448154.png b/umn/source/_static/images/en-us_image_0000001159847251.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448154.png rename to umn/source/_static/images/en-us_image_0000001159847251.png diff --git a/umn/source/_static/images/en-us_image_0000001442413881.png b/umn/source/_static/images/en-us_image_0000001169371695.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413881.png rename to umn/source/_static/images/en-us_image_0000001169371695.png diff --git a/umn/source/_static/images/en-us_image_0000001392255270.png b/umn/source/_static/images/en-us_image_0000001184290228.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392255270.png rename to umn/source/_static/images/en-us_image_0000001184290228.png diff --git a/umn/source/_static/images/en-us_image_0000001582807689.png b/umn/source/_static/images/en-us_image_0000001194201259.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807689.png rename to umn/source/_static/images/en-us_image_0000001194201259.png diff --git a/umn/source/_static/images/en-us_image_0000001583127381.png b/umn/source/_static/images/en-us_image_0000001194201487.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583127381.png rename to umn/source/_static/images/en-us_image_0000001194201487.png diff --git a/umn/source/_static/images/en-us_image_0000001532448158.png b/umn/source/_static/images/en-us_image_0000001194317737.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448158.png rename to umn/source/_static/images/en-us_image_0000001194317737.png diff --git a/umn/source/_static/images/en-us_image_0000001392255290.png b/umn/source/_static/images/en-us_image_0000001195220440.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392255290.png rename to umn/source/_static/images/en-us_image_0000001195220440.png diff --git a/umn/source/_static/images/en-us_image_0000001392734022.png b/umn/source/_static/images/en-us_image_0000001197336255.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734022.png rename to umn/source/_static/images/en-us_image_0000001197336255.png diff --git a/umn/source/_static/images/en-us_image_0000001392414806.png b/umn/source/_static/images/en-us_image_0000001205479339.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414806.png rename to umn/source/_static/images/en-us_image_0000001205479339.png diff --git a/umn/source/_static/images/en-us_image_0000001532448166.png b/umn/source/_static/images/en-us_image_0000001214152530.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448166.png rename to umn/source/_static/images/en-us_image_0000001214152530.png diff --git a/umn/source/_static/images/en-us_image_0000001532448178.png b/umn/source/_static/images/en-us_image_0000001214312492.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448178.png rename to umn/source/_static/images/en-us_image_0000001214312492.png diff --git a/umn/source/_static/images/en-us_image_0000001532448186.png b/umn/source/_static/images/en-us_image_0000001214315364.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448186.png rename to umn/source/_static/images/en-us_image_0000001214315364.png diff --git a/umn/source/_static/images/en-us_image_0000001532448170.png b/umn/source/_static/images/en-us_image_0000001216164294.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448170.png rename to umn/source/_static/images/en-us_image_0000001216164294.png diff --git a/umn/source/_static/images/en-us_image_0000001392255262.png b/umn/source/_static/images/en-us_image_0000001223688037.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392255262.png rename to umn/source/_static/images/en-us_image_0000001223688037.png diff --git a/umn/source/_static/images/en-us_image_0000001582927685.png b/umn/source/_static/images/en-us_image_0000001226576418.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927685.png rename to umn/source/_static/images/en-us_image_0000001226576418.png diff --git a/umn/source/_static/images/en-us_image_0000001532767530.png b/umn/source/_static/images/en-us_image_0000001227056330.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767530.png rename to umn/source/_static/images/en-us_image_0000001227056330.png diff --git a/umn/source/_static/images/en-us_image_0000001392414786.png b/umn/source/_static/images/en-us_image_0000001229609903.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414786.png rename to umn/source/_static/images/en-us_image_0000001229609903.png diff --git a/umn/source/_static/images/en-us_image_0000001442654033.png b/umn/source/_static/images/en-us_image_0000001229690017.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442654033.png rename to umn/source/_static/images/en-us_image_0000001229690017.png diff --git a/umn/source/_static/images/en-us_image_0000001532767466.gif b/umn/source/_static/images/en-us_image_0000001239292351.gif similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767466.gif rename to umn/source/_static/images/en-us_image_0000001239292351.gif diff --git a/umn/source/_static/images/en-us_image_0000001582807801.gif b/umn/source/_static/images/en-us_image_0000001239732331.gif similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807801.gif rename to umn/source/_static/images/en-us_image_0000001239732331.gif diff --git a/umn/source/_static/images/en-us_image_0000001532448190.png b/umn/source/_static/images/en-us_image_0000001258875319.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448190.png rename to umn/source/_static/images/en-us_image_0000001258875319.png diff --git a/umn/source/_static/images/en-us_image_0000001532448194.png b/umn/source/_static/images/en-us_image_0000001259115323.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448194.png rename to umn/source/_static/images/en-us_image_0000001259115323.png diff --git a/umn/source/_static/images/en-us_image_0000001532448202.png b/umn/source/_static/images/en-us_image_0000001259272397.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448202.png rename to umn/source/_static/images/en-us_image_0000001259272397.png diff --git a/umn/source/_static/images/en-us_image_0000001442654037.png b/umn/source/_static/images/en-us_image_0000001261300062.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442654037.png rename to umn/source/_static/images/en-us_image_0000001261300062.png diff --git a/umn/source/_static/images/en-us_image_0000001532767430.png b/umn/source/_static/images/en-us_image_0000001271157721.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767430.png rename to umn/source/_static/images/en-us_image_0000001271157721.png diff --git a/umn/source/_static/images/en-us_image_0000001582807737.png b/umn/source/_static/images/en-us_image_0000001271536445.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807737.png rename to umn/source/_static/images/en-us_image_0000001271536445.png diff --git a/umn/source/_static/images/en-us_image_0000001532448206.png b/umn/source/_static/images/en-us_image_0000001296365606.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448206.png rename to umn/source/_static/images/en-us_image_0000001296365606.png diff --git a/umn/source/_static/images/en-us_image_0000001532448210.png b/umn/source/_static/images/en-us_image_0000001296525586.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448210.png rename to umn/source/_static/images/en-us_image_0000001296525586.png diff --git a/umn/source/_static/images/en-us_image_0000001532607950.png b/umn/source/_static/images/en-us_image_0000001297838112.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607950.png rename to umn/source/_static/images/en-us_image_0000001297838112.png diff --git a/umn/source/_static/images/en-us_image_0000001297841644.png b/umn/source/_static/images/en-us_image_0000001297841644.png new file mode 100644 index 0000000..f6678bd Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001297841644.png differ diff --git a/umn/source/_static/images/en-us_image_0000001582807641.png b/umn/source/_static/images/en-us_image_0000001298155472.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807641.png rename to umn/source/_static/images/en-us_image_0000001298155472.png diff --git a/umn/source/_static/images/en-us_image_0000001392734010.png b/umn/source/_static/images/en-us_image_0000001318119582.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734010.png rename to umn/source/_static/images/en-us_image_0000001318119582.png diff --git a/umn/source/_static/images/en-us_image_0000001442773673.png b/umn/source/_static/images/en-us_image_0000001318122266.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773673.png rename to umn/source/_static/images/en-us_image_0000001318122266.png diff --git a/umn/source/_static/images/en-us_image_0000001392414454.png b/umn/source/_static/images/en-us_image_0000001318123498.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414454.png rename to umn/source/_static/images/en-us_image_0000001318123498.png diff --git a/umn/source/_static/images/en-us_image_0000001392574062.png b/umn/source/_static/images/en-us_image_0000001318157588.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574062.png rename to umn/source/_static/images/en-us_image_0000001318157588.png diff --git a/umn/source/_static/images/en-us_image_0000001392254946.png b/umn/source/_static/images/en-us_image_0000001318160568.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254946.png rename to umn/source/_static/images/en-us_image_0000001318160568.png diff --git a/umn/source/_static/images/en-us_image_0000001392414446.png b/umn/source/_static/images/en-us_image_0000001318441686.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414446.png rename to umn/source/_static/images/en-us_image_0000001318441686.png diff --git a/umn/source/_static/images/en-us_image_0000001392414474.png b/umn/source/_static/images/en-us_image_0000001318563432.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414474.png rename to umn/source/_static/images/en-us_image_0000001318563432.png diff --git a/umn/source/_static/images/en-us_image_0000001392414438.png b/umn/source/_static/images/en-us_image_0000001318636944.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414438.png rename to umn/source/_static/images/en-us_image_0000001318636944.png diff --git a/umn/source/_static/images/en-us_image_0000001392734314.png b/umn/source/_static/images/en-us_image_0000001337953138.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734314.png rename to umn/source/_static/images/en-us_image_0000001337953138.png diff --git a/umn/source/_static/images/en-us_image_0000001392414762.png b/umn/source/_static/images/en-us_image_0000001338429394.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414762.png rename to umn/source/_static/images/en-us_image_0000001338429394.png diff --git a/umn/source/_static/images/en-us_image_0000001349190333.png b/umn/source/_static/images/en-us_image_0000001349190333.png deleted file mode 100644 index 69e3720..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001349190333.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001349309917.png b/umn/source/_static/images/en-us_image_0000001349309917.png deleted file mode 100644 index 5699926..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001349309917.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532448214.png b/umn/source/_static/images/en-us_image_0000001349585581.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448214.png rename to umn/source/_static/images/en-us_image_0000001349585581.png diff --git a/umn/source/_static/images/en-us_image_0000001532448218.png b/umn/source/_static/images/en-us_image_0000001349825057.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448218.png rename to umn/source/_static/images/en-us_image_0000001349825057.png diff --git a/umn/source/_static/images/en-us_image_0000001532927622.png b/umn/source/_static/images/en-us_image_0000001351040425.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927622.png rename to umn/source/_static/images/en-us_image_0000001351040425.png diff --git a/umn/source/_static/images/en-us_image_0000001392254918.png b/umn/source/_static/images/en-us_image_0000001369746545.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254918.png rename to umn/source/_static/images/en-us_image_0000001369746545.png diff --git a/umn/source/_static/images/en-us_image_0000001392733954.png b/umn/source/_static/images/en-us_image_0000001369765657.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733954.png rename to umn/source/_static/images/en-us_image_0000001369765657.png diff --git a/umn/source/_static/images/en-us_image_0000001392733966.png b/umn/source/_static/images/en-us_image_0000001369765661.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733966.png rename to umn/source/_static/images/en-us_image_0000001369765661.png diff --git a/umn/source/_static/images/en-us_image_0000001442413925.png b/umn/source/_static/images/en-us_image_0000001369864353.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413925.png rename to umn/source/_static/images/en-us_image_0000001369864353.png diff --git a/umn/source/_static/images/en-us_image_0000001392734050.png b/umn/source/_static/images/en-us_image_0000001369886993.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734050.png rename to umn/source/_static/images/en-us_image_0000001369886993.png diff --git a/umn/source/_static/images/en-us_image_0000001442413865.png b/umn/source/_static/images/en-us_image_0000001369925585.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413865.png rename to umn/source/_static/images/en-us_image_0000001369925585.png diff --git a/umn/source/_static/images/en-us_image_0000001442653713.png b/umn/source/_static/images/en-us_image_0000001369944573.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653713.png rename to umn/source/_static/images/en-us_image_0000001369944573.png diff --git a/umn/source/_static/images/en-us_image_0000001392733962.png b/umn/source/_static/images/en-us_image_0000001369953797.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733962.png rename to umn/source/_static/images/en-us_image_0000001369953797.png diff --git a/umn/source/_static/images/en-us_image_0000001442653677.png b/umn/source/_static/images/en-us_image_0000001369960209.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653677.png rename to umn/source/_static/images/en-us_image_0000001369960209.png diff --git a/umn/source/_static/images/en-us_image_0000001442773701.png b/umn/source/_static/images/en-us_image_0000001369965777.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773701.png rename to umn/source/_static/images/en-us_image_0000001369965777.png diff --git a/umn/source/_static/images/en-us_image_0000001442413841.png b/umn/source/_static/images/en-us_image_0000001369965781.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413841.png rename to umn/source/_static/images/en-us_image_0000001369965781.png diff --git a/umn/source/_static/images/en-us_image_0000001442653669.png b/umn/source/_static/images/en-us_image_0000001369965785.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653669.png rename to umn/source/_static/images/en-us_image_0000001369965785.png diff --git a/umn/source/_static/images/en-us_image_0000001442773637.png b/umn/source/_static/images/en-us_image_0000001370061921.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773637.png rename to umn/source/_static/images/en-us_image_0000001370061921.png diff --git a/umn/source/_static/images/en-us_image_0000001442653673.png b/umn/source/_static/images/en-us_image_0000001370085637.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653673.png rename to umn/source/_static/images/en-us_image_0000001370085637.png diff --git a/umn/source/_static/images/en-us_image_0000001392574342.png b/umn/source/_static/images/en-us_image_0000001374635732.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574342.png rename to umn/source/_static/images/en-us_image_0000001374635732.png diff --git a/umn/source/_static/images/en-us_image_0000001392414394.png b/umn/source/_static/images/en-us_image_0000001375852797.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414394.png rename to umn/source/_static/images/en-us_image_0000001375852797.png diff --git a/umn/source/_static/images/en-us_image_0000001582807637.png b/umn/source/_static/images/en-us_image_0000001375901064.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807637.png rename to umn/source/_static/images/en-us_image_0000001375901064.png diff --git a/umn/source/_static/images/en-us_image_0000001442413945.png b/umn/source/_static/images/en-us_image_0000001376041769.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413945.png rename to umn/source/_static/images/en-us_image_0000001376041769.png diff --git a/umn/source/_static/images/en-us_image_0000001532448238.png b/umn/source/_static/images/en-us_image_0000001383088002.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448238.png rename to umn/source/_static/images/en-us_image_0000001383088002.png diff --git a/umn/source/_static/images/en-us_image_0000001442654061.png b/umn/source/_static/images/en-us_image_0000001388541980.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442654061.png rename to umn/source/_static/images/en-us_image_0000001388541980.png diff --git a/umn/source/_static/images/en-us_image_0000001442414237.png b/umn/source/_static/images/en-us_image_0000001388629905.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442414237.png rename to umn/source/_static/images/en-us_image_0000001388629905.png diff --git a/umn/source/_static/images/en-us_image_0000001392255246.png b/umn/source/_static/images/en-us_image_0000001388630241.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392255246.png rename to umn/source/_static/images/en-us_image_0000001388630241.png diff --git a/umn/source/_static/images/en-us_image_0000001392574002.png b/umn/source/_static/images/en-us_image_0000001388681282.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574002.png rename to umn/source/_static/images/en-us_image_0000001388681282.png diff --git a/umn/source/_static/images/en-us_image_0000001392734034.png b/umn/source/_static/images/en-us_image_0000001388835338.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734034.png rename to umn/source/_static/images/en-us_image_0000001388835338.png diff --git a/umn/source/_static/images/en-us_image_0000001392254934.png b/umn/source/_static/images/en-us_image_0000001388996278.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254934.png rename to umn/source/_static/images/en-us_image_0000001388996278.png diff --git a/umn/source/_static/images/en-us_image_0000001532767658.png b/umn/source/_static/images/en-us_image_0000001390459444.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767658.png rename to umn/source/_static/images/en-us_image_0000001390459444.png diff --git a/umn/source/_static/images/en-us_image_0000001532767498.png b/umn/source/_static/images/en-us_image_0000001390459688.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767498.png rename to umn/source/_static/images/en-us_image_0000001390459688.png diff --git a/umn/source/_static/images/en-us_image_0000001532927362.png b/umn/source/_static/images/en-us_image_0000001390618824.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927362.png rename to umn/source/_static/images/en-us_image_0000001390618824.png diff --git a/umn/source/_static/images/en-us_image_0000001532767698.png b/umn/source/_static/images/en-us_image_0000001390618884.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767698.png rename to umn/source/_static/images/en-us_image_0000001390618884.png diff --git a/umn/source/_static/images/en-us_image_0000001582807837.png b/umn/source/_static/images/en-us_image_0000001390619040.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807837.png rename to umn/source/_static/images/en-us_image_0000001390619040.png diff --git a/umn/source/_static/images/en-us_image_0000001583087433.png b/umn/source/_static/images/en-us_image_0000001390936180.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087433.png rename to umn/source/_static/images/en-us_image_0000001390936180.png diff --git a/umn/source/_static/images/en-us_image_0000001583127465.png b/umn/source/_static/images/en-us_image_0000001390938104.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583127465.png rename to umn/source/_static/images/en-us_image_0000001390938104.png diff --git a/umn/source/_static/images/en-us_image_0000001392734334.png b/umn/source/_static/images/en-us_image_0000001392734334.png deleted file mode 100644 index 622a645..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001392734334.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532448278.png b/umn/source/_static/images/en-us_image_0000001405224197.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448278.png rename to umn/source/_static/images/en-us_image_0000001405224197.png diff --git a/umn/source/_static/images/en-us_image_0000001582807613.png b/umn/source/_static/images/en-us_image_0000001410107141.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807613.png rename to umn/source/_static/images/en-us_image_0000001410107141.png diff --git a/umn/source/_static/images/en-us_image_0000001583087345.png b/umn/source/_static/images/en-us_image_0000001426500589.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087345.png rename to umn/source/_static/images/en-us_image_0000001426500589.png diff --git a/umn/source/_static/images/en-us_image_0000001438033333.png b/umn/source/_static/images/en-us_image_0000001438033333.png new file mode 100644 index 0000000..7681615 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001438033333.png differ diff --git a/umn/source/_static/images/en-us_image_0000001392414486.png b/umn/source/_static/images/en-us_image_0000001438841461.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414486.png rename to umn/source/_static/images/en-us_image_0000001438841461.png diff --git a/umn/source/_static/images/en-us_image_0000001442494125.png b/umn/source/_static/images/en-us_image_0000001438954277.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494125.png rename to umn/source/_static/images/en-us_image_0000001438954277.png diff --git a/umn/source/_static/images/en-us_image_0000001442654025.png b/umn/source/_static/images/en-us_image_0000001439442217.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442654025.png rename to umn/source/_static/images/en-us_image_0000001439442217.png diff --git a/umn/source/_static/images/en-us_image_0000001583127321.png b/umn/source/_static/images/en-us_image_0000001439562477.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583127321.png rename to umn/source/_static/images/en-us_image_0000001439562477.png diff --git a/umn/source/_static/images/en-us_image_0000001442414233.png b/umn/source/_static/images/en-us_image_0000001439594513.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442414233.png rename to umn/source/_static/images/en-us_image_0000001439594513.png diff --git a/umn/source/_static/images/en-us_image_0000001532448282.png b/umn/source/_static/images/en-us_image_0000001440858201.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448282.png rename to umn/source/_static/images/en-us_image_0000001440858201.png diff --git a/umn/source/_static/images/en-us_image_0000001532448486.png b/umn/source/_static/images/en-us_image_0000001440858217.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448486.png rename to umn/source/_static/images/en-us_image_0000001440858217.png diff --git a/umn/source/_static/images/en-us_image_0000001582807761.png b/umn/source/_static/images/en-us_image_0000001440858625.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807761.png rename to umn/source/_static/images/en-us_image_0000001440858625.png diff --git a/umn/source/_static/images/en-us_image_0000001582927861.png b/umn/source/_static/images/en-us_image_0000001440977805.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927861.png rename to umn/source/_static/images/en-us_image_0000001440977805.png diff --git a/umn/source/_static/images/en-us_image_0000001583127513.png b/umn/source/_static/images/en-us_image_0000001440977873.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583127513.png rename to umn/source/_static/images/en-us_image_0000001440977873.png diff --git a/umn/source/_static/images/en-us_image_0000001583127621.png b/umn/source/_static/images/en-us_image_0000001440978021.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583127621.png rename to umn/source/_static/images/en-us_image_0000001440978021.png diff --git a/umn/source/_static/images/en-us_image_0000001582927609.png b/umn/source/_static/images/en-us_image_0000001441097977.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927609.png rename to umn/source/_static/images/en-us_image_0000001441097977.png diff --git a/umn/source/_static/images/en-us_image_0000001583087429.png b/umn/source/_static/images/en-us_image_0000001441098753.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087429.png rename to umn/source/_static/images/en-us_image_0000001441098753.png diff --git a/umn/source/_static/images/en-us_image_0000001582927657.png b/umn/source/_static/images/en-us_image_0000001441218249.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927657.png rename to umn/source/_static/images/en-us_image_0000001441218249.png diff --git a/umn/source/_static/images/en-us_image_0000001532607778.png b/umn/source/_static/images/en-us_image_0000001441218685.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607778.png rename to umn/source/_static/images/en-us_image_0000001441218685.png diff --git a/umn/source/_static/images/en-us_image_0000001442653665.png b/umn/source/_static/images/en-us_image_0000001442653665.png deleted file mode 100644 index e837946..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001442653665.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532448138.png b/umn/source/_static/images/en-us_image_0000001532448138.png deleted file mode 100644 index 59264b7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532448138.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532448322.png b/umn/source/_static/images/en-us_image_0000001532448322.png deleted file mode 100644 index 8bc7f45..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532448322.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532448374.png b/umn/source/_static/images/en-us_image_0000001532448374.png deleted file mode 100644 index 3730487..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532448374.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532607622.png b/umn/source/_static/images/en-us_image_0000001532607622.png deleted file mode 100644 index 56604e5..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532607622.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532607638.png b/umn/source/_static/images/en-us_image_0000001532607638.png deleted file mode 100644 index 59264b7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532607638.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532607690.png b/umn/source/_static/images/en-us_image_0000001532607690.png deleted file mode 100644 index 5777903..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532607690.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532607954.png b/umn/source/_static/images/en-us_image_0000001532607954.png deleted file mode 100644 index df04447..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532607954.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532767354.png b/umn/source/_static/images/en-us_image_0000001532767354.png deleted file mode 100644 index bd8bef9..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532767354.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532767546.png b/umn/source/_static/images/en-us_image_0000001532767546.png deleted file mode 100644 index b678574..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532767546.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532767690.png b/umn/source/_static/images/en-us_image_0000001532767690.png deleted file mode 100644 index 057507d..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532767690.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532927290.png b/umn/source/_static/images/en-us_image_0000001532927290.png deleted file mode 100644 index 8bc7f45..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532927290.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532927426.png b/umn/source/_static/images/en-us_image_0000001532927426.png deleted file mode 100644 index b678574..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532927426.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532927626.png b/umn/source/_static/images/en-us_image_0000001532927626.png deleted file mode 100644 index 0ddb5db..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532927626.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532927662.png b/umn/source/_static/images/en-us_image_0000001532927662.png deleted file mode 100644 index 9b9fdec..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001532927662.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001534512058.png b/umn/source/_static/images/en-us_image_0000001534512058.png deleted file mode 100644 index 90cb2a2..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001534512058.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001535888150.png b/umn/source/_static/images/en-us_image_0000001535888150.png deleted file mode 100644 index c0d9763..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001535888150.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001582807589.png b/umn/source/_static/images/en-us_image_0000001582807589.png deleted file mode 100644 index 59264b7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001582807589.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001582807701.png b/umn/source/_static/images/en-us_image_0000001582807701.png deleted file mode 100644 index 8bc7f45..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001582807701.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001582807753.png b/umn/source/_static/images/en-us_image_0000001582807753.png deleted file mode 100644 index 56604e5..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001582807753.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001582807901.png b/umn/source/_static/images/en-us_image_0000001582807901.png deleted file mode 100644 index d386b71..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001582807901.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087273.png b/umn/source/_static/images/en-us_image_0000001583087273.png deleted file mode 100644 index b678574..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087273.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087297.png b/umn/source/_static/images/en-us_image_0000001583087297.png deleted file mode 100644 index 59264b7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087297.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087321.png b/umn/source/_static/images/en-us_image_0000001583087321.png deleted file mode 100644 index 5777903..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087321.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087389.png b/umn/source/_static/images/en-us_image_0000001583087389.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087389.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087417.png b/umn/source/_static/images/en-us_image_0000001583087417.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087417.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087453.png b/umn/source/_static/images/en-us_image_0000001583087453.png deleted file mode 100644 index 0344b30..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087453.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087517.png b/umn/source/_static/images/en-us_image_0000001583087517.png deleted file mode 100644 index b5a9b02..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087517.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087573.png b/umn/source/_static/images/en-us_image_0000001583087573.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087573.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087593.png b/umn/source/_static/images/en-us_image_0000001583087593.png deleted file mode 100644 index bcde0d1..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087593.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087601.png b/umn/source/_static/images/en-us_image_0000001583087601.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087601.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087609.png b/umn/source/_static/images/en-us_image_0000001583087609.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087609.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087625.png b/umn/source/_static/images/en-us_image_0000001583087625.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087625.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087629.png b/umn/source/_static/images/en-us_image_0000001583087629.png deleted file mode 100644 index 59264b7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087629.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583087653.png b/umn/source/_static/images/en-us_image_0000001583087653.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583087653.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127253.png b/umn/source/_static/images/en-us_image_0000001583127253.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127253.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127261.png b/umn/source/_static/images/en-us_image_0000001583127261.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127261.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127265.png b/umn/source/_static/images/en-us_image_0000001583127265.png deleted file mode 100644 index 9b9fdec..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127265.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127285.png b/umn/source/_static/images/en-us_image_0000001583127285.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127285.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127297.png b/umn/source/_static/images/en-us_image_0000001583127297.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127297.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127313.png b/umn/source/_static/images/en-us_image_0000001583127313.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127313.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127317.png b/umn/source/_static/images/en-us_image_0000001583127317.png deleted file mode 100644 index 59264b7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127317.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127329.png b/umn/source/_static/images/en-us_image_0000001583127329.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127329.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127333.png b/umn/source/_static/images/en-us_image_0000001583127333.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127333.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127341.png b/umn/source/_static/images/en-us_image_0000001583127341.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127341.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127345.png b/umn/source/_static/images/en-us_image_0000001583127345.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127345.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127365.png b/umn/source/_static/images/en-us_image_0000001583127365.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127365.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127373.png b/umn/source/_static/images/en-us_image_0000001583127373.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127373.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127377.png b/umn/source/_static/images/en-us_image_0000001583127377.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127377.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127385.png b/umn/source/_static/images/en-us_image_0000001583127385.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127385.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127389.png b/umn/source/_static/images/en-us_image_0000001583127389.png deleted file mode 100644 index 56604e5..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127389.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127393.png b/umn/source/_static/images/en-us_image_0000001583127393.png deleted file mode 100644 index bd8bef9..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127393.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127401.png b/umn/source/_static/images/en-us_image_0000001583127401.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127401.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127409.png b/umn/source/_static/images/en-us_image_0000001583127409.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127409.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127413.png b/umn/source/_static/images/en-us_image_0000001583127413.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127413.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127417.png b/umn/source/_static/images/en-us_image_0000001583127417.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127417.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127425.png b/umn/source/_static/images/en-us_image_0000001583127425.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127425.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127441.png b/umn/source/_static/images/en-us_image_0000001583127441.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127441.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127445.png b/umn/source/_static/images/en-us_image_0000001583127445.png deleted file mode 100644 index bd8bef9..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127445.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127453.png b/umn/source/_static/images/en-us_image_0000001583127453.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127453.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127457.png b/umn/source/_static/images/en-us_image_0000001583127457.png deleted file mode 100644 index d6da780..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127457.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127485.png b/umn/source/_static/images/en-us_image_0000001583127485.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127485.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127489.png b/umn/source/_static/images/en-us_image_0000001583127489.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127489.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127501.png b/umn/source/_static/images/en-us_image_0000001583127501.png deleted file mode 100644 index 59264b7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127501.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127505.png b/umn/source/_static/images/en-us_image_0000001583127505.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127505.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127509.png b/umn/source/_static/images/en-us_image_0000001583127509.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127509.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127517.png b/umn/source/_static/images/en-us_image_0000001583127517.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127517.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127525.png b/umn/source/_static/images/en-us_image_0000001583127525.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127525.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127545.png b/umn/source/_static/images/en-us_image_0000001583127545.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127545.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127553.png b/umn/source/_static/images/en-us_image_0000001583127553.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127553.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127561.png b/umn/source/_static/images/en-us_image_0000001583127561.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127561.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127597.png b/umn/source/_static/images/en-us_image_0000001583127597.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127597.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001583127613.png b/umn/source/_static/images/en-us_image_0000001583127613.png deleted file mode 100644 index 61ba034..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001583127613.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001584751969.png b/umn/source/_static/images/en-us_image_0000001584751969.png deleted file mode 100644 index df8beea..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001584751969.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001586567997.png b/umn/source/_static/images/en-us_image_0000001586567997.png deleted file mode 100644 index 710e78f..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001586567997.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001586807745.jpg b/umn/source/_static/images/en-us_image_0000001586807745.jpg deleted file mode 100644 index 4dab5a1..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001586807745.jpg and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001532448250.png b/umn/source/_static/images/en-us_image_0263895369.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448250.png rename to umn/source/_static/images/en-us_image_0263895369.png diff --git a/umn/source/_static/images/en-us_image_0000001532448274.png b/umn/source/_static/images/en-us_image_0263895376.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448274.png rename to umn/source/_static/images/en-us_image_0263895376.png diff --git a/umn/source/_static/images/en-us_image_0000001532448298.png b/umn/source/_static/images/en-us_image_0263895382.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448298.png rename to umn/source/_static/images/en-us_image_0263895382.png diff --git a/umn/source/_static/images/en-us_image_0000001532448310.png b/umn/source/_static/images/en-us_image_0263895386.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448310.png rename to umn/source/_static/images/en-us_image_0263895386.png diff --git a/umn/source/_static/images/en-us_image_0000001532448342.png b/umn/source/_static/images/en-us_image_0263895407.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448342.png rename to umn/source/_static/images/en-us_image_0263895407.png diff --git a/umn/source/_static/images/en-us_image_0000001532448262.png b/umn/source/_static/images/en-us_image_0263895412.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448262.png rename to umn/source/_static/images/en-us_image_0263895412.png diff --git a/umn/source/_static/images/en-us_image_0000001532448378.png b/umn/source/_static/images/en-us_image_0263895445.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448378.png rename to umn/source/_static/images/en-us_image_0263895445.png diff --git a/umn/source/_static/images/en-us_image_0000001532448414.png b/umn/source/_static/images/en-us_image_0263895453.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448414.png rename to umn/source/_static/images/en-us_image_0263895453.png diff --git a/umn/source/_static/images/en-us_image_0000001532448422.png b/umn/source/_static/images/en-us_image_0263895513.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448422.png rename to umn/source/_static/images/en-us_image_0263895513.png diff --git a/umn/source/_static/images/en-us_image_0000001532607762.png b/umn/source/_static/images/en-us_image_0263895526.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607762.png rename to umn/source/_static/images/en-us_image_0263895526.png diff --git a/umn/source/_static/images/en-us_image_0000001532448438.png b/umn/source/_static/images/en-us_image_0263895532.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448438.png rename to umn/source/_static/images/en-us_image_0263895532.png diff --git a/umn/source/_static/images/en-us_image_0000001532448470.png b/umn/source/_static/images/en-us_image_0263895540.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448470.png rename to umn/source/_static/images/en-us_image_0263895540.png diff --git a/umn/source/_static/images/en-us_image_0000001532448478.png b/umn/source/_static/images/en-us_image_0263895551.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448478.png rename to umn/source/_static/images/en-us_image_0263895551.png diff --git a/umn/source/_static/images/en-us_image_0000001532607642.png b/umn/source/_static/images/en-us_image_0263895574.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607642.png rename to umn/source/_static/images/en-us_image_0263895574.png diff --git a/umn/source/_static/images/en-us_image_0000001532607646.png b/umn/source/_static/images/en-us_image_0263895577.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607646.png rename to umn/source/_static/images/en-us_image_0263895577.png diff --git a/umn/source/_static/images/en-us_image_0000001532607650.png b/umn/source/_static/images/en-us_image_0263895589.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607650.png rename to umn/source/_static/images/en-us_image_0263895589.png diff --git a/umn/source/_static/images/en-us_image_0000001532607654.png b/umn/source/_static/images/en-us_image_0263895594.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607654.png rename to umn/source/_static/images/en-us_image_0263895594.png diff --git a/umn/source/_static/images/en-us_image_0000001532607658.png b/umn/source/_static/images/en-us_image_0263895607.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607658.png rename to umn/source/_static/images/en-us_image_0263895607.png diff --git a/umn/source/_static/images/en-us_image_0000001532607742.png b/umn/source/_static/images/en-us_image_0263895617.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607742.png rename to umn/source/_static/images/en-us_image_0263895617.png diff --git a/umn/source/_static/images/en-us_image_0000001532607758.png b/umn/source/_static/images/en-us_image_0263895663.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607758.png rename to umn/source/_static/images/en-us_image_0263895663.png diff --git a/umn/source/_static/images/en-us_image_0000001532607798.png b/umn/source/_static/images/en-us_image_0263895680.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607798.png rename to umn/source/_static/images/en-us_image_0263895680.png diff --git a/umn/source/_static/images/en-us_image_0000001532607802.png b/umn/source/_static/images/en-us_image_0263895683.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607802.png rename to umn/source/_static/images/en-us_image_0263895683.png diff --git a/umn/source/_static/images/en-us_image_0000001532448286.png b/umn/source/_static/images/en-us_image_0263895733.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448286.png rename to umn/source/_static/images/en-us_image_0263895733.png diff --git a/umn/source/_static/images/en-us_image_0000001532448306.png b/umn/source/_static/images/en-us_image_0263895749.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448306.png rename to umn/source/_static/images/en-us_image_0263895749.png diff --git a/umn/source/_static/images/en-us_image_0000001532607822.png b/umn/source/_static/images/en-us_image_0263895751.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607822.png rename to umn/source/_static/images/en-us_image_0263895751.png diff --git a/umn/source/_static/images/en-us_image_0000001532448366.png b/umn/source/_static/images/en-us_image_0263895771.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448366.png rename to umn/source/_static/images/en-us_image_0263895771.png diff --git a/umn/source/_static/images/en-us_image_0000001532607746.png b/umn/source/_static/images/en-us_image_0263895776.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607746.png rename to umn/source/_static/images/en-us_image_0263895776.png diff --git a/umn/source/_static/images/en-us_image_0000001532607750.png b/umn/source/_static/images/en-us_image_0263895789.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607750.png rename to umn/source/_static/images/en-us_image_0263895789.png diff --git a/umn/source/_static/images/en-us_image_0000001532607830.png b/umn/source/_static/images/en-us_image_0263895796.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607830.png rename to umn/source/_static/images/en-us_image_0263895796.png diff --git a/umn/source/_static/images/en-us_image_0000001532607834.png b/umn/source/_static/images/en-us_image_0263895802.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607834.png rename to umn/source/_static/images/en-us_image_0263895802.png diff --git a/umn/source/_static/images/en-us_image_0000001532607838.png b/umn/source/_static/images/en-us_image_0263895811.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607838.png rename to umn/source/_static/images/en-us_image_0263895811.png diff --git a/umn/source/_static/images/en-us_image_0000001583127305.jpg b/umn/source/_static/images/en-us_image_0263895818.jpg similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583127305.jpg rename to umn/source/_static/images/en-us_image_0263895818.jpg diff --git a/umn/source/_static/images/en-us_image_0000001532607906.png b/umn/source/_static/images/en-us_image_0263895827.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607906.png rename to umn/source/_static/images/en-us_image_0263895827.png diff --git a/umn/source/_static/images/en-us_image_0000001532607846.png b/umn/source/_static/images/en-us_image_0263895859.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607846.png rename to umn/source/_static/images/en-us_image_0263895859.png diff --git a/umn/source/_static/images/en-us_image_0000001532607850.png b/umn/source/_static/images/en-us_image_0263895883.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607850.png rename to umn/source/_static/images/en-us_image_0263895883.png diff --git a/umn/source/_static/images/en-us_image_0000001442653741.png b/umn/source/_static/images/en-us_image_0263899217.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653741.png rename to umn/source/_static/images/en-us_image_0263899217.png diff --git a/umn/source/_static/images/en-us_image_0000001392414386.png b/umn/source/_static/images/en-us_image_0263899218.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414386.png rename to umn/source/_static/images/en-us_image_0263899218.png diff --git a/umn/source/_static/images/en-us_image_0000001442653645.png b/umn/source/_static/images/en-us_image_0263899222.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653645.png rename to umn/source/_static/images/en-us_image_0263899222.png diff --git a/umn/source/_static/images/en-us_image_0000001392254954.png b/umn/source/_static/images/en-us_image_0263899235.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254954.png rename to umn/source/_static/images/en-us_image_0263899235.png diff --git a/umn/source/_static/images/en-us_image_0000001392254894.png b/umn/source/_static/images/en-us_image_0263899238.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254894.png rename to umn/source/_static/images/en-us_image_0263899238.png diff --git a/umn/source/_static/images/en-us_image_0000001392733934.png b/umn/source/_static/images/en-us_image_0263899257.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733934.png rename to umn/source/_static/images/en-us_image_0263899257.png diff --git a/umn/source/_static/images/en-us_image_0000001392574030.png b/umn/source/_static/images/en-us_image_0263899268.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574030.png rename to umn/source/_static/images/en-us_image_0263899268.png diff --git a/umn/source/_static/images/en-us_image_0000001392254906.png b/umn/source/_static/images/en-us_image_0263899271.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254906.png rename to umn/source/_static/images/en-us_image_0263899271.png diff --git a/umn/source/_static/images/en-us_image_0000001442413873.png b/umn/source/_static/images/en-us_image_0263899280.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413873.png rename to umn/source/_static/images/en-us_image_0263899280.png diff --git a/umn/source/_static/images/en-us_image_0000001442413869.png b/umn/source/_static/images/en-us_image_0263899283.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413869.png rename to umn/source/_static/images/en-us_image_0263899283.png diff --git a/umn/source/_static/images/en-us_image_0000001392254886.png b/umn/source/_static/images/en-us_image_0263899288.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254886.png rename to umn/source/_static/images/en-us_image_0263899288.png diff --git a/umn/source/_static/images/en-us_image_0000001392254902.png b/umn/source/_static/images/en-us_image_0263899289.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254902.png rename to umn/source/_static/images/en-us_image_0263899289.png diff --git a/umn/source/_static/images/en-us_image_0000001532607938.png b/umn/source/_static/images/en-us_image_0263899291.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607938.png rename to umn/source/_static/images/en-us_image_0263899291.png diff --git a/umn/source/_static/images/en-us_image_0000001392734038.png b/umn/source/_static/images/en-us_image_0263899293.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734038.png rename to umn/source/_static/images/en-us_image_0263899293.png diff --git a/umn/source/_static/images/en-us_image_0000001442773649.png b/umn/source/_static/images/en-us_image_0263899299.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773649.png rename to umn/source/_static/images/en-us_image_0263899299.png diff --git a/umn/source/_static/images/en-us_image_0000001442773709.png b/umn/source/_static/images/en-us_image_0263899304.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773709.png rename to umn/source/_static/images/en-us_image_0263899304.png diff --git a/umn/source/_static/images/en-us_image_0000001392573998.png b/umn/source/_static/images/en-us_image_0263899311.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392573998.png rename to umn/source/_static/images/en-us_image_0263899311.png diff --git a/umn/source/_static/images/en-us_image_0000001392254950.png b/umn/source/_static/images/en-us_image_0263899316.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254950.png rename to umn/source/_static/images/en-us_image_0263899316.png diff --git a/umn/source/_static/images/en-us_image_0000001392734350.png b/umn/source/_static/images/en-us_image_0263899322.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734350.png rename to umn/source/_static/images/en-us_image_0263899322.png diff --git a/umn/source/_static/images/en-us_image_0000001392254858.png b/umn/source/_static/images/en-us_image_0263899323.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254858.png rename to umn/source/_static/images/en-us_image_0263899323.png diff --git a/umn/source/_static/images/en-us_image_0000001442494085.png b/umn/source/_static/images/en-us_image_0263899329.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494085.png rename to umn/source/_static/images/en-us_image_0263899329.png diff --git a/umn/source/_static/images/en-us_image_0000001392254938.png b/umn/source/_static/images/en-us_image_0263899334.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254938.png rename to umn/source/_static/images/en-us_image_0263899334.png diff --git a/umn/source/_static/images/en-us_image_0000001392734042.png b/umn/source/_static/images/en-us_image_0263899339.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734042.png rename to umn/source/_static/images/en-us_image_0263899339.png diff --git a/umn/source/_static/images/en-us_image_0000001442653749.png b/umn/source/_static/images/en-us_image_0263899343.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653749.png rename to umn/source/_static/images/en-us_image_0263899343.png diff --git a/umn/source/_static/images/en-us_image_0000001442413957.png b/umn/source/_static/images/en-us_image_0263899363.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413957.png rename to umn/source/_static/images/en-us_image_0263899363.png diff --git a/umn/source/_static/images/en-us_image_0000001392414402.png b/umn/source/_static/images/en-us_image_0263899376.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414402.png rename to umn/source/_static/images/en-us_image_0263899376.png diff --git a/umn/source/_static/images/en-us_image_0000001392254890.png b/umn/source/_static/images/en-us_image_0263899383.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254890.png rename to umn/source/_static/images/en-us_image_0263899383.png diff --git a/umn/source/_static/images/en-us_image_0000001532607970.png b/umn/source/_static/images/en-us_image_0263899384.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607970.png rename to umn/source/_static/images/en-us_image_0263899384.png diff --git a/umn/source/_static/images/en-us_image_0000001392414466.png b/umn/source/_static/images/en-us_image_0263899392.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414466.png rename to umn/source/_static/images/en-us_image_0263899392.png diff --git a/umn/source/_static/images/en-us_image_0000001442773597.png b/umn/source/_static/images/en-us_image_0263899401.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773597.png rename to umn/source/_static/images/en-us_image_0263899401.png diff --git a/umn/source/_static/images/en-us_image_0000001442773601.png b/umn/source/_static/images/en-us_image_0263899403.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773601.png rename to umn/source/_static/images/en-us_image_0263899403.png diff --git a/umn/source/_static/images/en-us_image_0000001442773661.png b/umn/source/_static/images/en-us_image_0263899406.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773661.png rename to umn/source/_static/images/en-us_image_0263899406.png diff --git a/umn/source/_static/images/en-us_image_0000001442494093.png b/umn/source/_static/images/en-us_image_0263899409.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494093.png rename to umn/source/_static/images/en-us_image_0263899409.png diff --git a/umn/source/_static/images/en-us_image_0000001442413937.png b/umn/source/_static/images/en-us_image_0263899411.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413937.png rename to umn/source/_static/images/en-us_image_0263899411.png diff --git a/umn/source/_static/images/en-us_image_0000001442773629.png b/umn/source/_static/images/en-us_image_0263899420.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773629.png rename to umn/source/_static/images/en-us_image_0263899420.png diff --git a/umn/source/_static/images/en-us_image_0000001442494097.png b/umn/source/_static/images/en-us_image_0263899424.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494097.png rename to umn/source/_static/images/en-us_image_0263899424.png diff --git a/umn/source/_static/images/en-us_image_0000001442413885.png b/umn/source/_static/images/en-us_image_0263899436.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413885.png rename to umn/source/_static/images/en-us_image_0263899436.png diff --git a/umn/source/_static/images/en-us_image_0000001442494073.png b/umn/source/_static/images/en-us_image_0263899446.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494073.png rename to umn/source/_static/images/en-us_image_0263899446.png diff --git a/umn/source/_static/images/en-us_image_0000001442413917.png b/umn/source/_static/images/en-us_image_0263899452.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413917.png rename to umn/source/_static/images/en-us_image_0263899452.png diff --git a/umn/source/_static/images/en-us_image_0000001392254958.png b/umn/source/_static/images/en-us_image_0263899453.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254958.png rename to umn/source/_static/images/en-us_image_0263899453.png diff --git a/umn/source/_static/images/en-us_image_0000001442773617.png b/umn/source/_static/images/en-us_image_0263899454.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773617.png rename to umn/source/_static/images/en-us_image_0263899454.png diff --git a/umn/source/_static/images/en-us_image_0000001392733950.png b/umn/source/_static/images/en-us_image_0263899456.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733950.png rename to umn/source/_static/images/en-us_image_0263899456.png diff --git a/umn/source/_static/images/en-us_image_0000001392733930.png b/umn/source/_static/images/en-us_image_0263899458.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733930.png rename to umn/source/_static/images/en-us_image_0263899458.png diff --git a/umn/source/_static/images/en-us_image_0000001392414434.png b/umn/source/_static/images/en-us_image_0263899471.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414434.png rename to umn/source/_static/images/en-us_image_0263899471.png diff --git a/umn/source/_static/images/en-us_image_0000001442773713.png b/umn/source/_static/images/en-us_image_0263899476.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773713.png rename to umn/source/_static/images/en-us_image_0263899476.png diff --git a/umn/source/_static/images/en-us_image_0000001392414490.png b/umn/source/_static/images/en-us_image_0263899493.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414490.png rename to umn/source/_static/images/en-us_image_0263899493.png diff --git a/umn/source/_static/images/en-us_image_0000001392254850.png b/umn/source/_static/images/en-us_image_0263899495.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254850.png rename to umn/source/_static/images/en-us_image_0263899495.png diff --git a/umn/source/_static/images/en-us_image_0000001392574010.png b/umn/source/_static/images/en-us_image_0263899496.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574010.png rename to umn/source/_static/images/en-us_image_0263899496.png diff --git a/umn/source/_static/images/en-us_image_0000001442653657.png b/umn/source/_static/images/en-us_image_0263899498.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653657.png rename to umn/source/_static/images/en-us_image_0263899498.png diff --git a/umn/source/_static/images/en-us_image_0000001532767394.png b/umn/source/_static/images/en-us_image_0263899504.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767394.png rename to umn/source/_static/images/en-us_image_0263899504.png diff --git a/umn/source/_static/images/en-us_image_0000001442494045.png b/umn/source/_static/images/en-us_image_0263899520.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494045.png rename to umn/source/_static/images/en-us_image_0263899520.png diff --git a/umn/source/_static/images/en-us_image_0000001442653701.png b/umn/source/_static/images/en-us_image_0263899528.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653701.png rename to umn/source/_static/images/en-us_image_0263899528.png diff --git a/umn/source/_static/images/en-us_image_0000001442413845.png b/umn/source/_static/images/en-us_image_0263899531.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442413845.png rename to umn/source/_static/images/en-us_image_0263899531.png diff --git a/umn/source/_static/images/en-us_image_0000001392574050.png b/umn/source/_static/images/en-us_image_0263899538.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574050.png rename to umn/source/_static/images/en-us_image_0263899538.png diff --git a/umn/source/_static/images/en-us_image_0000001392574046.png b/umn/source/_static/images/en-us_image_0263899546.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574046.png rename to umn/source/_static/images/en-us_image_0263899546.png diff --git a/umn/source/_static/images/en-us_image_0000001442653745.png b/umn/source/_static/images/en-us_image_0263899555.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653745.png rename to umn/source/_static/images/en-us_image_0263899555.png diff --git a/umn/source/_static/images/en-us_image_0000001442653641.png b/umn/source/_static/images/en-us_image_0263899556.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653641.png rename to umn/source/_static/images/en-us_image_0263899556.png diff --git a/umn/source/_static/images/en-us_image_0000001442494033.png b/umn/source/_static/images/en-us_image_0263899570.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494033.png rename to umn/source/_static/images/en-us_image_0263899570.png diff --git a/umn/source/_static/images/en-us_image_0000001442653685.png b/umn/source/_static/images/en-us_image_0263899582.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653685.png rename to umn/source/_static/images/en-us_image_0263899582.png diff --git a/umn/source/_static/images/en-us_image_0000001442773609.png b/umn/source/_static/images/en-us_image_0263899589.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773609.png rename to umn/source/_static/images/en-us_image_0263899589.png diff --git a/umn/source/_static/images/en-us_image_0000001442773705.png b/umn/source/_static/images/en-us_image_0263899593.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773705.png rename to umn/source/_static/images/en-us_image_0263899593.png diff --git a/umn/source/_static/images/en-us_image_0000001392733994.png b/umn/source/_static/images/en-us_image_0263899597.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733994.png rename to umn/source/_static/images/en-us_image_0263899597.png diff --git a/umn/source/_static/images/en-us_image_0000001442773665.png b/umn/source/_static/images/en-us_image_0263899610.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773665.png rename to umn/source/_static/images/en-us_image_0263899610.png diff --git a/umn/source/_static/images/en-us_image_0000001392574078.png b/umn/source/_static/images/en-us_image_0263899616.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574078.png rename to umn/source/_static/images/en-us_image_0263899616.png diff --git a/umn/source/_static/images/en-us_image_0000001392414378.png b/umn/source/_static/images/en-us_image_0263899617.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414378.png rename to umn/source/_static/images/en-us_image_0263899617.png diff --git a/umn/source/_static/images/en-us_image_0000001442494081.png b/umn/source/_static/images/en-us_image_0263899621.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494081.png rename to umn/source/_static/images/en-us_image_0263899621.png diff --git a/umn/source/_static/images/en-us_image_0000001442653649.png b/umn/source/_static/images/en-us_image_0263899635.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653649.png rename to umn/source/_static/images/en-us_image_0263899635.png diff --git a/umn/source/_static/images/en-us_image_0000001392414478.png b/umn/source/_static/images/en-us_image_0263899637.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414478.png rename to umn/source/_static/images/en-us_image_0263899637.png diff --git a/umn/source/_static/images/en-us_image_0000001392414410.png b/umn/source/_static/images/en-us_image_0263899641.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414410.png rename to umn/source/_static/images/en-us_image_0263899641.png diff --git a/umn/source/_static/images/en-us_image_0000001392254926.png b/umn/source/_static/images/en-us_image_0263899644.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254926.png rename to umn/source/_static/images/en-us_image_0263899644.png diff --git a/umn/source/_static/images/en-us_image_0000001392414418.png b/umn/source/_static/images/en-us_image_0263899649.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414418.png rename to umn/source/_static/images/en-us_image_0263899649.png diff --git a/umn/source/_static/images/en-us_image_0000001532767506.png b/umn/source/_static/images/en-us_image_0263899656.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767506.png rename to umn/source/_static/images/en-us_image_0263899656.png diff --git a/umn/source/_static/images/en-us_image_0000001442494041.png b/umn/source/_static/images/en-us_image_0263899662.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442494041.png rename to umn/source/_static/images/en-us_image_0263899662.png diff --git a/umn/source/_static/images/en-us_image_0000001442653737.png b/umn/source/_static/images/en-us_image_0263899673.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442653737.png rename to umn/source/_static/images/en-us_image_0263899673.png diff --git a/umn/source/_static/images/en-us_image_0000001392734006.png b/umn/source/_static/images/en-us_image_0263899675.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734006.png rename to umn/source/_static/images/en-us_image_0263899675.png diff --git a/umn/source/_static/images/en-us_image_0000001442414245.png b/umn/source/_static/images/en-us_image_0264281176.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442414245.png rename to umn/source/_static/images/en-us_image_0264281176.png diff --git a/umn/source/_static/images/en-us_image_0000001392733938.png b/umn/source/_static/images/en-us_image_0265768517.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392733938.png rename to umn/source/_static/images/en-us_image_0265768517.png diff --git a/umn/source/_static/images/en-us_image_0000001442773721.jpg b/umn/source/_static/images/en-us_image_0267694670.jpg similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442773721.jpg rename to umn/source/_static/images/en-us_image_0267694670.jpg diff --git a/umn/source/_static/images/en-us_image_0000001392414778.png b/umn/source/_static/images/en-us_image_0268284607.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414778.png rename to umn/source/_static/images/en-us_image_0268284607.png diff --git a/umn/source/_static/images/en-us_image_0000001392734330.png b/umn/source/_static/images/en-us_image_0268298534.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392734330.png rename to umn/source/_static/images/en-us_image_0268298534.png diff --git a/umn/source/_static/images/en-us_image_0000001532607862.png b/umn/source/_static/images/en-us_image_0269383808.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607862.png rename to umn/source/_static/images/en-us_image_0269383808.png diff --git a/umn/source/_static/images/en-us_image_0000001532607874.png b/umn/source/_static/images/en-us_image_0269383809.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607874.png rename to umn/source/_static/images/en-us_image_0269383809.png diff --git a/umn/source/_static/images/en-us_image_0000001532607878.png b/umn/source/_static/images/en-us_image_0269383810.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607878.png rename to umn/source/_static/images/en-us_image_0269383810.png diff --git a/umn/source/_static/images/en-us_image_0000001532607882.png b/umn/source/_static/images/en-us_image_0269383814.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607882.png rename to umn/source/_static/images/en-us_image_0269383814.png diff --git a/umn/source/_static/images/en-us_image_0000001532767638.png b/umn/source/_static/images/en-us_image_0269383815.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767638.png rename to umn/source/_static/images/en-us_image_0269383815.png diff --git a/umn/source/_static/images/en-us_image_0000001532607890.png b/umn/source/_static/images/en-us_image_0269383816.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607890.png rename to umn/source/_static/images/en-us_image_0269383816.png diff --git a/umn/source/_static/images/en-us_image_0000001532767734.png b/umn/source/_static/images/en-us_image_0269383817.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767734.png rename to umn/source/_static/images/en-us_image_0269383817.png diff --git a/umn/source/_static/images/en-us_image_0000001532607898.png b/umn/source/_static/images/en-us_image_0269383818.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607898.png rename to umn/source/_static/images/en-us_image_0269383818.png diff --git a/umn/source/_static/images/en-us_image_0000001532927302.png b/umn/source/_static/images/en-us_image_0269383822.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927302.png rename to umn/source/_static/images/en-us_image_0269383822.png diff --git a/umn/source/_static/images/en-us_image_0000001532927370.png b/umn/source/_static/images/en-us_image_0269383823.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927370.png rename to umn/source/_static/images/en-us_image_0269383823.png diff --git a/umn/source/_static/images/en-us_image_0000001583087533.png b/umn/source/_static/images/en-us_image_0269383824.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087533.png rename to umn/source/_static/images/en-us_image_0269383824.png diff --git a/umn/source/_static/images/en-us_image_0000001532927418.png b/umn/source/_static/images/en-us_image_0269383826.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927418.png rename to umn/source/_static/images/en-us_image_0269383826.png diff --git a/umn/source/_static/images/en-us_image_0000001532927450.png b/umn/source/_static/images/en-us_image_0269383828.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927450.png rename to umn/source/_static/images/en-us_image_0269383828.png diff --git a/umn/source/_static/images/en-us_image_0000001532607902.png b/umn/source/_static/images/en-us_image_0269383829.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607902.png rename to umn/source/_static/images/en-us_image_0269383829.png diff --git a/umn/source/_static/images/en-us_image_0000001532927570.png b/umn/source/_static/images/en-us_image_0269383830.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927570.png rename to umn/source/_static/images/en-us_image_0269383830.png diff --git a/umn/source/_static/images/en-us_image_0000001532607910.png b/umn/source/_static/images/en-us_image_0269383831.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607910.png rename to umn/source/_static/images/en-us_image_0269383831.png diff --git a/umn/source/_static/images/en-us_image_0000001582807645.png b/umn/source/_static/images/en-us_image_0269383832.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807645.png rename to umn/source/_static/images/en-us_image_0269383832.png diff --git a/umn/source/_static/images/en-us_image_0000001532607914.png b/umn/source/_static/images/en-us_image_0269383834.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607914.png rename to umn/source/_static/images/en-us_image_0269383834.png diff --git a/umn/source/_static/images/en-us_image_0000001582807717.png b/umn/source/_static/images/en-us_image_0269383843.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807717.png rename to umn/source/_static/images/en-us_image_0269383843.png diff --git a/umn/source/_static/images/en-us_image_0000001532607918.png b/umn/source/_static/images/en-us_image_0269383844.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607918.png rename to umn/source/_static/images/en-us_image_0269383844.png diff --git a/umn/source/_static/images/en-us_image_0000001582807757.png b/umn/source/_static/images/en-us_image_0269383845.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807757.png rename to umn/source/_static/images/en-us_image_0269383845.png diff --git a/umn/source/_static/images/en-us_image_0000001532607922.png b/umn/source/_static/images/en-us_image_0269383846.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607922.png rename to umn/source/_static/images/en-us_image_0269383846.png diff --git a/umn/source/_static/images/en-us_image_0000001532607942.png b/umn/source/_static/images/en-us_image_0269383850.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607942.png rename to umn/source/_static/images/en-us_image_0269383850.png diff --git a/umn/source/_static/images/en-us_image_0000001582807817.png b/umn/source/_static/images/en-us_image_0269383851.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807817.png rename to umn/source/_static/images/en-us_image_0269383851.png diff --git a/umn/source/_static/images/en-us_image_0000001532607946.png b/umn/source/_static/images/en-us_image_0269383852.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607946.png rename to umn/source/_static/images/en-us_image_0269383852.png diff --git a/umn/source/_static/images/en-us_image_0000001532927558.jpg b/umn/source/_static/images/en-us_image_0269383855.jpg similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927558.jpg rename to umn/source/_static/images/en-us_image_0269383855.jpg diff --git a/umn/source/_static/images/en-us_image_0000001532607958.png b/umn/source/_static/images/en-us_image_0269383856.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607958.png rename to umn/source/_static/images/en-us_image_0269383856.png diff --git a/umn/source/_static/images/en-us_image_0000001532607974.png b/umn/source/_static/images/en-us_image_0269383857.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607974.png rename to umn/source/_static/images/en-us_image_0269383857.png diff --git a/umn/source/_static/images/en-us_image_0000001582807909.png b/umn/source/_static/images/en-us_image_0269383872.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807909.png rename to umn/source/_static/images/en-us_image_0269383872.png diff --git a/umn/source/_static/images/en-us_image_0000001532607978.png b/umn/source/_static/images/en-us_image_0269383873.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532607978.png rename to umn/source/_static/images/en-us_image_0269383873.png diff --git a/umn/source/_static/images/en-us_image_0000001582927521.png b/umn/source/_static/images/en-us_image_0269383875.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927521.png rename to umn/source/_static/images/en-us_image_0269383875.png diff --git a/umn/source/_static/images/en-us_image_0000001532767358.png b/umn/source/_static/images/en-us_image_0269383876.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767358.png rename to umn/source/_static/images/en-us_image_0269383876.png diff --git a/umn/source/_static/images/en-us_image_0000001582927669.png b/umn/source/_static/images/en-us_image_0269383877.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927669.png rename to umn/source/_static/images/en-us_image_0269383877.png diff --git a/umn/source/_static/images/en-us_image_0000001532767366.png b/umn/source/_static/images/en-us_image_0269383878.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767366.png rename to umn/source/_static/images/en-us_image_0269383878.png diff --git a/umn/source/_static/images/en-us_image_0000001582927757.png b/umn/source/_static/images/en-us_image_0269383880.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927757.png rename to umn/source/_static/images/en-us_image_0269383880.png diff --git a/umn/source/_static/images/en-us_image_0000001532767370.png b/umn/source/_static/images/en-us_image_0269383881.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767370.png rename to umn/source/_static/images/en-us_image_0269383881.png diff --git a/umn/source/_static/images/en-us_image_0000001582927773.png b/umn/source/_static/images/en-us_image_0269383882.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927773.png rename to umn/source/_static/images/en-us_image_0269383882.png diff --git a/umn/source/_static/images/en-us_image_0000001582927805.png b/umn/source/_static/images/en-us_image_0269383883.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927805.png rename to umn/source/_static/images/en-us_image_0269383883.png diff --git a/umn/source/_static/images/en-us_image_0000001532767378.png b/umn/source/_static/images/en-us_image_0269383884.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767378.png rename to umn/source/_static/images/en-us_image_0269383884.png diff --git a/umn/source/_static/images/en-us_image_0000001582927809.png b/umn/source/_static/images/en-us_image_0269383889.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927809.png rename to umn/source/_static/images/en-us_image_0269383889.png diff --git a/umn/source/_static/images/en-us_image_0000001532767382.png b/umn/source/_static/images/en-us_image_0269383890.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767382.png rename to umn/source/_static/images/en-us_image_0269383890.png diff --git a/umn/source/_static/images/en-us_image_0000001532767398.png b/umn/source/_static/images/en-us_image_0269383906.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767398.png rename to umn/source/_static/images/en-us_image_0269383906.png diff --git a/umn/source/_static/images/en-us_image_0000001532767406.png b/umn/source/_static/images/en-us_image_0269383907.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767406.png rename to umn/source/_static/images/en-us_image_0269383907.png diff --git a/umn/source/_static/images/en-us_image_0000001532767414.png b/umn/source/_static/images/en-us_image_0269383908.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767414.png rename to umn/source/_static/images/en-us_image_0269383908.png diff --git a/umn/source/_static/images/en-us_image_0000001532767426.png b/umn/source/_static/images/en-us_image_0269383909.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767426.png rename to umn/source/_static/images/en-us_image_0269383909.png diff --git a/umn/source/_static/images/en-us_image_0000001532767442.png b/umn/source/_static/images/en-us_image_0269383915.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767442.png rename to umn/source/_static/images/en-us_image_0269383915.png diff --git a/umn/source/_static/images/en-us_image_0000001532767474.png b/umn/source/_static/images/en-us_image_0269383916.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767474.png rename to umn/source/_static/images/en-us_image_0269383916.png diff --git a/umn/source/_static/images/en-us_image_0000001532767486.png b/umn/source/_static/images/en-us_image_0269383917.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767486.png rename to umn/source/_static/images/en-us_image_0269383917.png diff --git a/umn/source/_static/images/en-us_image_0000001532767502.png b/umn/source/_static/images/en-us_image_0269383918.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767502.png rename to umn/source/_static/images/en-us_image_0269383918.png diff --git a/umn/source/_static/images/en-us_image_0000001532767510.png b/umn/source/_static/images/en-us_image_0269383919.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767510.png rename to umn/source/_static/images/en-us_image_0269383919.png diff --git a/umn/source/_static/images/en-us_image_0000001532767522.png b/umn/source/_static/images/en-us_image_0269383920.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767522.png rename to umn/source/_static/images/en-us_image_0269383920.png diff --git a/umn/source/_static/images/en-us_image_0000001583087397.jpg b/umn/source/_static/images/en-us_image_0269383921.jpg similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087397.jpg rename to umn/source/_static/images/en-us_image_0269383921.jpg diff --git a/umn/source/_static/images/en-us_image_0000001532767542.png b/umn/source/_static/images/en-us_image_0269383922.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767542.png rename to umn/source/_static/images/en-us_image_0269383922.png diff --git a/umn/source/_static/images/en-us_image_0000001532767550.png b/umn/source/_static/images/en-us_image_0269383923.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767550.png rename to umn/source/_static/images/en-us_image_0269383923.png diff --git a/umn/source/_static/images/en-us_image_0000001532767558.png b/umn/source/_static/images/en-us_image_0269383924.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767558.png rename to umn/source/_static/images/en-us_image_0269383924.png diff --git a/umn/source/_static/images/en-us_image_0000001532767570.png b/umn/source/_static/images/en-us_image_0269383925.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767570.png rename to umn/source/_static/images/en-us_image_0269383925.png diff --git a/umn/source/_static/images/en-us_image_0000001532767578.png b/umn/source/_static/images/en-us_image_0269383926.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767578.png rename to umn/source/_static/images/en-us_image_0269383926.png diff --git a/umn/source/_static/images/en-us_image_0000001532767582.png b/umn/source/_static/images/en-us_image_0269383927.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767582.png rename to umn/source/_static/images/en-us_image_0269383927.png diff --git a/umn/source/_static/images/en-us_image_0000001532767590.png b/umn/source/_static/images/en-us_image_0269383928.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767590.png rename to umn/source/_static/images/en-us_image_0269383928.png diff --git a/umn/source/_static/images/en-us_image_0000001532767598.png b/umn/source/_static/images/en-us_image_0269383929.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767598.png rename to umn/source/_static/images/en-us_image_0269383929.png diff --git a/umn/source/_static/images/en-us_image_0000001532767602.png b/umn/source/_static/images/en-us_image_0269383930.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767602.png rename to umn/source/_static/images/en-us_image_0269383930.png diff --git a/umn/source/_static/images/en-us_image_0000001532767606.png b/umn/source/_static/images/en-us_image_0269383932.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767606.png rename to umn/source/_static/images/en-us_image_0269383932.png diff --git a/umn/source/_static/images/en-us_image_0000001532767554.png b/umn/source/_static/images/en-us_image_0269383933.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767554.png rename to umn/source/_static/images/en-us_image_0269383933.png diff --git a/umn/source/_static/images/en-us_image_0000001532767626.png b/umn/source/_static/images/en-us_image_0269383934.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767626.png rename to umn/source/_static/images/en-us_image_0269383934.png diff --git a/umn/source/_static/images/en-us_image_0000001532767650.png b/umn/source/_static/images/en-us_image_0269383936.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767650.png rename to umn/source/_static/images/en-us_image_0269383936.png diff --git a/umn/source/_static/images/en-us_image_0000001532767654.png b/umn/source/_static/images/en-us_image_0269383940.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767654.png rename to umn/source/_static/images/en-us_image_0269383940.png diff --git a/umn/source/_static/images/en-us_image_0000001532767666.png b/umn/source/_static/images/en-us_image_0269383942.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767666.png rename to umn/source/_static/images/en-us_image_0269383942.png diff --git a/umn/source/_static/images/en-us_image_0000001532767706.png b/umn/source/_static/images/en-us_image_0269383943.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767706.png rename to umn/source/_static/images/en-us_image_0269383943.png diff --git a/umn/source/_static/images/en-us_image_0000001532767714.png b/umn/source/_static/images/en-us_image_0269383945.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767714.png rename to umn/source/_static/images/en-us_image_0269383945.png diff --git a/umn/source/_static/images/en-us_image_0000001532767722.png b/umn/source/_static/images/en-us_image_0269383946.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767722.png rename to umn/source/_static/images/en-us_image_0269383946.png diff --git a/umn/source/_static/images/en-us_image_0000001532927286.png b/umn/source/_static/images/en-us_image_0269383949.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927286.png rename to umn/source/_static/images/en-us_image_0269383949.png diff --git a/umn/source/_static/images/en-us_image_0000001582927749.gif b/umn/source/_static/images/en-us_image_0269383950.gif similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927749.gif rename to umn/source/_static/images/en-us_image_0269383950.gif diff --git a/umn/source/_static/images/en-us_image_0000001532927326.png b/umn/source/_static/images/en-us_image_0269383952.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927326.png rename to umn/source/_static/images/en-us_image_0269383952.png diff --git a/umn/source/_static/images/en-us_image_0000001532927330.png b/umn/source/_static/images/en-us_image_0269383953.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927330.png rename to umn/source/_static/images/en-us_image_0269383953.png diff --git a/umn/source/_static/images/en-us_image_0000001532927334.png b/umn/source/_static/images/en-us_image_0269383956.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927334.png rename to umn/source/_static/images/en-us_image_0269383956.png diff --git a/umn/source/_static/images/en-us_image_0000001532927338.png b/umn/source/_static/images/en-us_image_0269383957.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927338.png rename to umn/source/_static/images/en-us_image_0269383957.png diff --git a/umn/source/_static/images/en-us_image_0000001532927342.png b/umn/source/_static/images/en-us_image_0269383958.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927342.png rename to umn/source/_static/images/en-us_image_0269383958.png diff --git a/umn/source/_static/images/en-us_image_0000001532927350.png b/umn/source/_static/images/en-us_image_0269383960.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927350.png rename to umn/source/_static/images/en-us_image_0269383960.png diff --git a/umn/source/_static/images/en-us_image_0000001532927366.png b/umn/source/_static/images/en-us_image_0269383961.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927366.png rename to umn/source/_static/images/en-us_image_0269383961.png diff --git a/umn/source/_static/images/en-us_image_0000001532927402.png b/umn/source/_static/images/en-us_image_0269383962.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927402.png rename to umn/source/_static/images/en-us_image_0269383962.png diff --git a/umn/source/_static/images/en-us_image_0000001532927410.png b/umn/source/_static/images/en-us_image_0269383963.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927410.png rename to umn/source/_static/images/en-us_image_0269383963.png diff --git a/umn/source/_static/images/en-us_image_0000001532927422.png b/umn/source/_static/images/en-us_image_0269383964.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927422.png rename to umn/source/_static/images/en-us_image_0269383964.png diff --git a/umn/source/_static/images/en-us_image_0000001532927434.png b/umn/source/_static/images/en-us_image_0269383966.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927434.png rename to umn/source/_static/images/en-us_image_0269383966.png diff --git a/umn/source/_static/images/en-us_image_0000001532927442.png b/umn/source/_static/images/en-us_image_0269383967.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927442.png rename to umn/source/_static/images/en-us_image_0269383967.png diff --git a/umn/source/_static/images/en-us_image_0000001532927446.png b/umn/source/_static/images/en-us_image_0269383968.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927446.png rename to umn/source/_static/images/en-us_image_0269383968.png diff --git a/umn/source/_static/images/en-us_image_0000001532927454.png b/umn/source/_static/images/en-us_image_0269383969.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927454.png rename to umn/source/_static/images/en-us_image_0269383969.png diff --git a/umn/source/_static/images/en-us_image_0000001532927458.png b/umn/source/_static/images/en-us_image_0269383970.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927458.png rename to umn/source/_static/images/en-us_image_0269383970.png diff --git a/umn/source/_static/images/en-us_image_0000001532927470.png b/umn/source/_static/images/en-us_image_0269383972.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927470.png rename to umn/source/_static/images/en-us_image_0269383972.png diff --git a/umn/source/_static/images/en-us_image_0000001532927474.png b/umn/source/_static/images/en-us_image_0269417342.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927474.png rename to umn/source/_static/images/en-us_image_0269417342.png diff --git a/umn/source/_static/images/en-us_image_0000001532927482.png b/umn/source/_static/images/en-us_image_0269417343.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927482.png rename to umn/source/_static/images/en-us_image_0269417343.png diff --git a/umn/source/_static/images/en-us_image_0000001532927490.png b/umn/source/_static/images/en-us_image_0269417344.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927490.png rename to umn/source/_static/images/en-us_image_0269417344.png diff --git a/umn/source/_static/images/en-us_image_0000001532927502.png b/umn/source/_static/images/en-us_image_0269417365.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927502.png rename to umn/source/_static/images/en-us_image_0269417365.png diff --git a/umn/source/_static/images/en-us_image_0000001582807777.png b/umn/source/_static/images/en-us_image_0269417366.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807777.png rename to umn/source/_static/images/en-us_image_0269417366.png diff --git a/umn/source/_static/images/en-us_image_0000001532927518.png b/umn/source/_static/images/en-us_image_0269417367.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927518.png rename to umn/source/_static/images/en-us_image_0269417367.png diff --git a/umn/source/_static/images/en-us_image_0000001532927522.png b/umn/source/_static/images/en-us_image_0269417368.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927522.png rename to umn/source/_static/images/en-us_image_0269417368.png diff --git a/umn/source/_static/images/en-us_image_0000001532927530.png b/umn/source/_static/images/en-us_image_0269417369.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927530.png rename to umn/source/_static/images/en-us_image_0269417369.png diff --git a/umn/source/_static/images/en-us_image_0000001532927534.png b/umn/source/_static/images/en-us_image_0269417370.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927534.png rename to umn/source/_static/images/en-us_image_0269417370.png diff --git a/umn/source/_static/images/en-us_image_0000001532927546.png b/umn/source/_static/images/en-us_image_0269417373.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927546.png rename to umn/source/_static/images/en-us_image_0269417373.png diff --git a/umn/source/_static/images/en-us_image_0000001532927550.png b/umn/source/_static/images/en-us_image_0269417374.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927550.png rename to umn/source/_static/images/en-us_image_0269417374.png diff --git a/umn/source/_static/images/en-us_image_0000001532927554.png b/umn/source/_static/images/en-us_image_0269417375.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927554.png rename to umn/source/_static/images/en-us_image_0269417375.png diff --git a/umn/source/_static/images/en-us_image_0000001532927578.png b/umn/source/_static/images/en-us_image_0269417376.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927578.png rename to umn/source/_static/images/en-us_image_0269417376.png diff --git a/umn/source/_static/images/en-us_image_0000001532927586.png b/umn/source/_static/images/en-us_image_0269417377.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927586.png rename to umn/source/_static/images/en-us_image_0269417377.png diff --git a/umn/source/_static/images/en-us_image_0000001532927602.png b/umn/source/_static/images/en-us_image_0269417379.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927602.png rename to umn/source/_static/images/en-us_image_0269417379.png diff --git a/umn/source/_static/images/en-us_image_0000001532927606.png b/umn/source/_static/images/en-us_image_0269417380.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927606.png rename to umn/source/_static/images/en-us_image_0269417380.png diff --git a/umn/source/_static/images/en-us_image_0000001532927642.png b/umn/source/_static/images/en-us_image_0269417381.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927642.png rename to umn/source/_static/images/en-us_image_0269417381.png diff --git a/umn/source/_static/images/en-us_image_0000001532927646.png b/umn/source/_static/images/en-us_image_0269417382.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927646.png rename to umn/source/_static/images/en-us_image_0269417382.png diff --git a/umn/source/_static/images/en-us_image_0000001532927650.png b/umn/source/_static/images/en-us_image_0269417383.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927650.png rename to umn/source/_static/images/en-us_image_0269417383.png diff --git a/umn/source/_static/images/en-us_image_0000001582807565.png b/umn/source/_static/images/en-us_image_0269417384.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807565.png rename to umn/source/_static/images/en-us_image_0269417384.png diff --git a/umn/source/_static/images/en-us_image_0000001582807569.png b/umn/source/_static/images/en-us_image_0269417385.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807569.png rename to umn/source/_static/images/en-us_image_0269417385.png diff --git a/umn/source/_static/images/en-us_image_0000001582807573.png b/umn/source/_static/images/en-us_image_0269417388.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807573.png rename to umn/source/_static/images/en-us_image_0269417388.png diff --git a/umn/source/_static/images/en-us_image_0000001582807577.png b/umn/source/_static/images/en-us_image_0269417389.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807577.png rename to umn/source/_static/images/en-us_image_0269417389.png diff --git a/umn/source/_static/images/en-us_image_0000001582807581.png b/umn/source/_static/images/en-us_image_0269417390.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807581.png rename to umn/source/_static/images/en-us_image_0269417390.png diff --git a/umn/source/_static/images/en-us_image_0000001532767534.png b/umn/source/_static/images/en-us_image_0269417391.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767534.png rename to umn/source/_static/images/en-us_image_0269417391.png diff --git a/umn/source/_static/images/en-us_image_0000001582807585.png b/umn/source/_static/images/en-us_image_0269417392.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807585.png rename to umn/source/_static/images/en-us_image_0269417392.png diff --git a/umn/source/_static/images/en-us_image_0000001532927430.png b/umn/source/_static/images/en-us_image_0269417393.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927430.png rename to umn/source/_static/images/en-us_image_0269417393.png diff --git a/umn/source/_static/images/en-us_image_0000001582807597.png b/umn/source/_static/images/en-us_image_0269417394.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807597.png rename to umn/source/_static/images/en-us_image_0269417394.png diff --git a/umn/source/_static/images/en-us_image_0000001582807601.png b/umn/source/_static/images/en-us_image_0269417395.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807601.png rename to umn/source/_static/images/en-us_image_0269417395.png diff --git a/umn/source/_static/images/en-us_image_0000001582807605.png b/umn/source/_static/images/en-us_image_0269417396.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807605.png rename to umn/source/_static/images/en-us_image_0269417396.png diff --git a/umn/source/_static/images/en-us_image_0000001582807617.png b/umn/source/_static/images/en-us_image_0269417397.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807617.png rename to umn/source/_static/images/en-us_image_0269417397.png diff --git a/umn/source/_static/images/en-us_image_0000001582807621.png b/umn/source/_static/images/en-us_image_0269417398.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807621.png rename to umn/source/_static/images/en-us_image_0269417398.png diff --git a/umn/source/_static/images/en-us_image_0000001582807649.png b/umn/source/_static/images/en-us_image_0269417399.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807649.png rename to umn/source/_static/images/en-us_image_0269417399.png diff --git a/umn/source/_static/images/en-us_image_0000001582807685.png b/umn/source/_static/images/en-us_image_0269417400.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807685.png rename to umn/source/_static/images/en-us_image_0269417400.png diff --git a/umn/source/_static/images/en-us_image_0000001582807697.png b/umn/source/_static/images/en-us_image_0269417401.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807697.png rename to umn/source/_static/images/en-us_image_0269417401.png diff --git a/umn/source/_static/images/en-us_image_0000001582807709.png b/umn/source/_static/images/en-us_image_0269417402.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807709.png rename to umn/source/_static/images/en-us_image_0269417402.png diff --git a/umn/source/_static/images/en-us_image_0000001582807721.png b/umn/source/_static/images/en-us_image_0269417403.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807721.png rename to umn/source/_static/images/en-us_image_0269417403.png diff --git a/umn/source/_static/images/en-us_image_0000001582807729.png b/umn/source/_static/images/en-us_image_0269417404.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807729.png rename to umn/source/_static/images/en-us_image_0269417404.png diff --git a/umn/source/_static/images/en-us_image_0000001582807765.png b/umn/source/_static/images/en-us_image_0269417405.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807765.png rename to umn/source/_static/images/en-us_image_0269417405.png diff --git a/umn/source/_static/images/en-us_image_0000001582807773.png b/umn/source/_static/images/en-us_image_0269417406.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807773.png rename to umn/source/_static/images/en-us_image_0269417406.png diff --git a/umn/source/_static/images/en-us_image_0000001582807793.png b/umn/source/_static/images/en-us_image_0269417409.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807793.png rename to umn/source/_static/images/en-us_image_0269417409.png diff --git a/umn/source/_static/images/en-us_image_0000001582807805.png b/umn/source/_static/images/en-us_image_0269417410.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807805.png rename to umn/source/_static/images/en-us_image_0269417410.png diff --git a/umn/source/_static/images/en-us_image_0000001582807809.png b/umn/source/_static/images/en-us_image_0269417413.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807809.png rename to umn/source/_static/images/en-us_image_0269417413.png diff --git a/umn/source/_static/images/en-us_image_0000001582807821.png b/umn/source/_static/images/en-us_image_0269417414.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807821.png rename to umn/source/_static/images/en-us_image_0269417414.png diff --git a/umn/source/_static/images/en-us_image_0000001532448266.png b/umn/source/_static/images/en-us_image_0269417415.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448266.png rename to umn/source/_static/images/en-us_image_0269417415.png diff --git a/umn/source/_static/images/en-us_image_0000001532767490.png b/umn/source/_static/images/en-us_image_0269417416.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767490.png rename to umn/source/_static/images/en-us_image_0269417416.png diff --git a/umn/source/_static/images/en-us_image_0000001583087409.png b/umn/source/_static/images/en-us_image_0269417417.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087409.png rename to umn/source/_static/images/en-us_image_0269417417.png diff --git a/umn/source/_static/images/en-us_image_0000001582927649.png b/umn/source/_static/images/en-us_image_0269417418.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927649.png rename to umn/source/_static/images/en-us_image_0269417418.png diff --git a/umn/source/_static/images/en-us_image_0000001582807857.png b/umn/source/_static/images/en-us_image_0269417419.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807857.png rename to umn/source/_static/images/en-us_image_0269417419.png diff --git a/umn/source/_static/images/en-us_image_0000001582807861.png b/umn/source/_static/images/en-us_image_0269417420.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807861.png rename to umn/source/_static/images/en-us_image_0269417420.png diff --git a/umn/source/_static/images/en-us_image_0000001582807869.png b/umn/source/_static/images/en-us_image_0269417421.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807869.png rename to umn/source/_static/images/en-us_image_0269417421.png diff --git a/umn/source/_static/images/en-us_image_0000001582807877.png b/umn/source/_static/images/en-us_image_0269417422.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807877.png rename to umn/source/_static/images/en-us_image_0269417422.png diff --git a/umn/source/_static/images/en-us_image_0000001582807905.png b/umn/source/_static/images/en-us_image_0269417423.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807905.png rename to umn/source/_static/images/en-us_image_0269417423.png diff --git a/umn/source/_static/images/en-us_image_0000001582807913.png b/umn/source/_static/images/en-us_image_0269417427.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807913.png rename to umn/source/_static/images/en-us_image_0269417427.png diff --git a/umn/source/_static/images/en-us_image_0000001582807921.png b/umn/source/_static/images/en-us_image_0269417428.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582807921.png rename to umn/source/_static/images/en-us_image_0269417428.png diff --git a/umn/source/_static/images/en-us_image_0000001582927517.png b/umn/source/_static/images/en-us_image_0269417429.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927517.png rename to umn/source/_static/images/en-us_image_0269417429.png diff --git a/umn/source/_static/images/en-us_image_0000001582927529.png b/umn/source/_static/images/en-us_image_0269417439.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927529.png rename to umn/source/_static/images/en-us_image_0269417439.png diff --git a/umn/source/_static/images/en-us_image_0000001582927541.png b/umn/source/_static/images/en-us_image_0269417447.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927541.png rename to umn/source/_static/images/en-us_image_0269417447.png diff --git a/umn/source/_static/images/en-us_image_0000001582927545.png b/umn/source/_static/images/en-us_image_0269417449.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927545.png rename to umn/source/_static/images/en-us_image_0269417449.png diff --git a/umn/source/_static/images/en-us_image_0000001582927549.png b/umn/source/_static/images/en-us_image_0269417455.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927549.png rename to umn/source/_static/images/en-us_image_0269417455.png diff --git a/umn/source/_static/images/en-us_image_0000001582927557.png b/umn/source/_static/images/en-us_image_0269417456.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927557.png rename to umn/source/_static/images/en-us_image_0269417456.png diff --git a/umn/source/_static/images/en-us_image_0000001582927569.png b/umn/source/_static/images/en-us_image_0269417458.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927569.png rename to umn/source/_static/images/en-us_image_0269417458.png diff --git a/umn/source/_static/images/en-us_image_0000001582927585.png b/umn/source/_static/images/en-us_image_0269417459.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927585.png rename to umn/source/_static/images/en-us_image_0269417459.png diff --git a/umn/source/_static/images/en-us_image_0000001582927593.png b/umn/source/_static/images/en-us_image_0269417460.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927593.png rename to umn/source/_static/images/en-us_image_0269417460.png diff --git a/umn/source/_static/images/en-us_image_0000001582927629.png b/umn/source/_static/images/en-us_image_0269417461.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927629.png rename to umn/source/_static/images/en-us_image_0269417461.png diff --git a/umn/source/_static/images/en-us_image_0000001582927637.png b/umn/source/_static/images/en-us_image_0269417462.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927637.png rename to umn/source/_static/images/en-us_image_0269417462.png diff --git a/umn/source/_static/images/en-us_image_0000001582927641.png b/umn/source/_static/images/en-us_image_0269417463.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927641.png rename to umn/source/_static/images/en-us_image_0269417463.png diff --git a/umn/source/_static/images/en-us_image_0000001582927645.png b/umn/source/_static/images/en-us_image_0269417464.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927645.png rename to umn/source/_static/images/en-us_image_0269417464.png diff --git a/umn/source/_static/images/en-us_image_0000001582927849.png b/umn/source/_static/images/en-us_image_0269417465.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927849.png rename to umn/source/_static/images/en-us_image_0269417465.png diff --git a/umn/source/_static/images/en-us_image_0000001582927665.png b/umn/source/_static/images/en-us_image_0269417466.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927665.png rename to umn/source/_static/images/en-us_image_0269417466.png diff --git a/umn/source/_static/images/en-us_image_0000001582927673.png b/umn/source/_static/images/en-us_image_0269417468.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927673.png rename to umn/source/_static/images/en-us_image_0269417468.png diff --git a/umn/source/_static/images/en-us_image_0000001532767514.png b/umn/source/_static/images/en-us_image_0269417469.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532767514.png rename to umn/source/_static/images/en-us_image_0269417469.png diff --git a/umn/source/_static/images/en-us_image_0000001582927689.png b/umn/source/_static/images/en-us_image_0269417473.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927689.png rename to umn/source/_static/images/en-us_image_0269417473.png diff --git a/umn/source/_static/images/en-us_image_0000001582927705.png b/umn/source/_static/images/en-us_image_0269417499.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927705.png rename to umn/source/_static/images/en-us_image_0269417499.png diff --git a/umn/source/_static/images/en-us_image_0000001582927709.png b/umn/source/_static/images/en-us_image_0269417500.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927709.png rename to umn/source/_static/images/en-us_image_0269417500.png diff --git a/umn/source/_static/images/en-us_image_0000001582927713.png b/umn/source/_static/images/en-us_image_0269417501.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927713.png rename to umn/source/_static/images/en-us_image_0269417501.png diff --git a/umn/source/_static/images/en-us_image_0000001582927717.png b/umn/source/_static/images/en-us_image_0269417502.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927717.png rename to umn/source/_static/images/en-us_image_0269417502.png diff --git a/umn/source/_static/images/en-us_image_0000001582927741.png b/umn/source/_static/images/en-us_image_0269417503.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927741.png rename to umn/source/_static/images/en-us_image_0269417503.png diff --git a/umn/source/_static/images/en-us_image_0000001582927769.png b/umn/source/_static/images/en-us_image_0269417504.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927769.png rename to umn/source/_static/images/en-us_image_0269417504.png diff --git a/umn/source/_static/images/en-us_image_0000001582927781.png b/umn/source/_static/images/en-us_image_0269417505.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927781.png rename to umn/source/_static/images/en-us_image_0269417505.png diff --git a/umn/source/_static/images/en-us_image_0000001582927785.png b/umn/source/_static/images/en-us_image_0269417506.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927785.png rename to umn/source/_static/images/en-us_image_0269417506.png diff --git a/umn/source/_static/images/en-us_image_0000001582927869.png b/umn/source/_static/images/en-us_image_0269417510.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927869.png rename to umn/source/_static/images/en-us_image_0269417510.png diff --git a/umn/source/_static/images/en-us_image_0000001582927789.png b/umn/source/_static/images/en-us_image_0269417534.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927789.png rename to umn/source/_static/images/en-us_image_0269417534.png diff --git a/umn/source/_static/images/en-us_image_0000001582927797.png b/umn/source/_static/images/en-us_image_0269417535.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927797.png rename to umn/source/_static/images/en-us_image_0269417535.png diff --git a/umn/source/_static/images/en-us_image_0000001582927813.png b/umn/source/_static/images/en-us_image_0269417537.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927813.png rename to umn/source/_static/images/en-us_image_0269417537.png diff --git a/umn/source/_static/images/en-us_image_0000001582927825.png b/umn/source/_static/images/en-us_image_0269417538.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927825.png rename to umn/source/_static/images/en-us_image_0269417538.png diff --git a/umn/source/_static/images/en-us_image_0000001582927829.png b/umn/source/_static/images/en-us_image_0269417539.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927829.png rename to umn/source/_static/images/en-us_image_0269417539.png diff --git a/umn/source/_static/images/en-us_image_0000001582927841.png b/umn/source/_static/images/en-us_image_0269417540.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927841.png rename to umn/source/_static/images/en-us_image_0269417540.png diff --git a/umn/source/_static/images/en-us_image_0000001582927857.png b/umn/source/_static/images/en-us_image_0269417541.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927857.png rename to umn/source/_static/images/en-us_image_0269417541.png diff --git a/umn/source/_static/images/en-us_image_0000001582927881.png b/umn/source/_static/images/en-us_image_0269417542.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001582927881.png rename to umn/source/_static/images/en-us_image_0269417542.png diff --git a/umn/source/_static/images/en-us_image_0000001532448294.gif b/umn/source/_static/images/en-us_image_0269417543.gif similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532448294.gif rename to umn/source/_static/images/en-us_image_0269417543.gif diff --git a/umn/source/_static/images/en-us_image_0000001532927594.gif b/umn/source/_static/images/en-us_image_0269417544.gif similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927594.gif rename to umn/source/_static/images/en-us_image_0269417544.gif diff --git a/umn/source/_static/images/en-us_image_0000001583087269.png b/umn/source/_static/images/en-us_image_0269417545.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087269.png rename to umn/source/_static/images/en-us_image_0269417545.png diff --git a/umn/source/_static/images/en-us_image_0000001583087277.png b/umn/source/_static/images/en-us_image_0269417546.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087277.png rename to umn/source/_static/images/en-us_image_0269417546.png diff --git a/umn/source/_static/images/en-us_image_0000001583087281.png b/umn/source/_static/images/en-us_image_0269417547.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087281.png rename to umn/source/_static/images/en-us_image_0269417547.png diff --git a/umn/source/_static/images/en-us_image_0000001583087289.png b/umn/source/_static/images/en-us_image_0269417548.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087289.png rename to umn/source/_static/images/en-us_image_0269417548.png diff --git a/umn/source/_static/images/en-us_image_0000001583087293.png b/umn/source/_static/images/en-us_image_0269417549.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087293.png rename to umn/source/_static/images/en-us_image_0269417549.png diff --git a/umn/source/_static/images/en-us_image_0000001583087317.png b/umn/source/_static/images/en-us_image_0269623978.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087317.png rename to umn/source/_static/images/en-us_image_0269623978.png diff --git a/umn/source/_static/images/en-us_image_0000001583087329.png b/umn/source/_static/images/en-us_image_0269624001.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087329.png rename to umn/source/_static/images/en-us_image_0269624001.png diff --git a/umn/source/_static/images/en-us_image_0000001583087333.png b/umn/source/_static/images/en-us_image_0270938821.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087333.png rename to umn/source/_static/images/en-us_image_0270938821.png diff --git a/umn/source/_static/images/en-us_image_0000001583087357.png b/umn/source/_static/images/en-us_image_0276137853.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087357.png rename to umn/source/_static/images/en-us_image_0276137853.png diff --git a/umn/source/_static/images/en-us_image_0000001583087385.png b/umn/source/_static/images/en-us_image_0276137857.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087385.png rename to umn/source/_static/images/en-us_image_0276137857.png diff --git a/umn/source/_static/images/en-us_image_0000001583087405.png b/umn/source/_static/images/en-us_image_0276137858.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087405.png rename to umn/source/_static/images/en-us_image_0276137858.png diff --git a/umn/source/_static/images/en-us_image_0000001583087413.png b/umn/source/_static/images/en-us_image_0276137859.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087413.png rename to umn/source/_static/images/en-us_image_0276137859.png diff --git a/umn/source/_static/images/en-us_image_0000001532927346.png b/umn/source/_static/images/en-us_image_0276801805.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001532927346.png rename to umn/source/_static/images/en-us_image_0276801805.png diff --git a/umn/source/_static/images/en-us_image_0000001392414374.png b/umn/source/_static/images/en-us_image_0278119935.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392414374.png rename to umn/source/_static/images/en-us_image_0278119935.png diff --git a/umn/source/_static/images/en-us_image_0000001392254854.png b/umn/source/_static/images/en-us_image_0279536633.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392254854.png rename to umn/source/_static/images/en-us_image_0279536633.png diff --git a/umn/source/_static/images/en-us_image_0000001442774001.png b/umn/source/_static/images/en-us_image_0293101307.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001442774001.png rename to umn/source/_static/images/en-us_image_0293101307.png diff --git a/umn/source/_static/images/en-us_image_0000001392574346.png b/umn/source/_static/images/en-us_image_0293131436.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001392574346.png rename to umn/source/_static/images/en-us_image_0293131436.png diff --git a/umn/source/_static/images/en-us_image_0000001583087421.png b/umn/source/_static/images/en-us_image_0293180907.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087421.png rename to umn/source/_static/images/en-us_image_0293180907.png diff --git a/umn/source/_static/images/en-us_image_0000001583087425.png b/umn/source/_static/images/en-us_image_0293234930.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087425.png rename to umn/source/_static/images/en-us_image_0293234930.png diff --git a/umn/source/_static/images/en-us_image_0000001583087445.png b/umn/source/_static/images/en-us_image_0293235730.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087445.png rename to umn/source/_static/images/en-us_image_0293235730.png diff --git a/umn/source/_static/images/en-us_image_0000001583087461.png b/umn/source/_static/images/en-us_image_0293242788.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087461.png rename to umn/source/_static/images/en-us_image_0293242788.png diff --git a/umn/source/_static/images/en-us_image_0000001583087465.png b/umn/source/_static/images/en-us_image_0293245149.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087465.png rename to umn/source/_static/images/en-us_image_0293245149.png diff --git a/umn/source/_static/images/en-us_image_0000001583087477.png b/umn/source/_static/images/en-us_image_0293246465.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087477.png rename to umn/source/_static/images/en-us_image_0293246465.png diff --git a/umn/source/_static/images/en-us_image_0000001583087481.png b/umn/source/_static/images/en-us_image_0293246731.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087481.png rename to umn/source/_static/images/en-us_image_0293246731.png diff --git a/umn/source/_static/images/en-us_image_0000001583087489.png b/umn/source/_static/images/en-us_image_0293247048.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087489.png rename to umn/source/_static/images/en-us_image_0293247048.png diff --git a/umn/source/_static/images/en-us_image_0000001583087501.png b/umn/source/_static/images/en-us_image_0293247437.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087501.png rename to umn/source/_static/images/en-us_image_0293247437.png diff --git a/umn/source/_static/images/en-us_image_0000001583087505.png b/umn/source/_static/images/en-us_image_0293267262.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087505.png rename to umn/source/_static/images/en-us_image_0293267262.png diff --git a/umn/source/_static/images/en-us_image_0000001583087513.png b/umn/source/_static/images/en-us_image_0293268152.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087513.png rename to umn/source/_static/images/en-us_image_0293268152.png diff --git a/umn/source/_static/images/en-us_image_0000001583087537.png b/umn/source/_static/images/en-us_image_0293269028.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087537.png rename to umn/source/_static/images/en-us_image_0293269028.png diff --git a/umn/source/_static/images/en-us_image_0000001583087541.png b/umn/source/_static/images/en-us_image_0293269047.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087541.png rename to umn/source/_static/images/en-us_image_0293269047.png diff --git a/umn/source/_static/images/en-us_image_0000001583087553.png b/umn/source/_static/images/en-us_image_0293269551.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087553.png rename to umn/source/_static/images/en-us_image_0293269551.png diff --git a/umn/source/_static/images/en-us_image_0000001583087565.png b/umn/source/_static/images/en-us_image_0295310731.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087565.png rename to umn/source/_static/images/en-us_image_0295310731.png diff --git a/umn/source/_static/images/en-us_image_0000001583087581.png b/umn/source/_static/images/en-us_image_0295554634.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087581.png rename to umn/source/_static/images/en-us_image_0295554634.png diff --git a/umn/source/_static/images/en-us_image_0000001583087597.png b/umn/source/_static/images/en-us_image_0295706662.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001583087597.png rename to umn/source/_static/images/en-us_image_0295706662.png diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index 1f389e7..58ff638 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -5,219 +5,154 @@ Change History ============== -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| Release Date | What's New | -+===================================+======================================================================================================================================================+ -| 2023-07-27 | Modified the following content: | -| | | -| | Modified the ALM-45431 alarm title. For details, see :ref:`ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-05-04 | Modified the following content: | -| | | -| | - Added MRS 3.2.0-LTS.1. For details, see :ref:`Creating a Custom Cluster `. | -| | - Added description of CDL and IoTDB technical principles, For details, see :ref:`CDL ` and :ref:`IoTDB `. | -| | - Added instructions for backing up and restoring CDL and IoT database data. | -| | | -| | - :ref:`Backing Up CDL Data ` | -| | - :ref:`Backing Up IoTDB Metadata ` | -| | - :ref:`Backing Up IoTDB Service Data ` | -| | - :ref:`Restoring CDL Data ` | -| | - :ref:`Restoring IoTDB Metadata ` | -| | - :ref:`Restoring IoTDB Service Data ` | -| | | -| | - Supported online patch pushing and update. For details, see :ref:`Patch Update `. | -| | - Added and updated some alarms of MRS 3.2.0-LTS.1. | -| | | -| | - :ref:`ALM-12012 NTP Service Is Abnormal ` | -| | - :ref:`ALM-12037 NTP Server Abnormal ` | -| | - :ref:`ALM-12103 Executor Resource Exception ` | -| | - :ref:`ALM-12104 Abnormal Knox Resources ` | -| | - :ref:`ALM-12172 Failed to Report Metrics to Cloud Eye ` | -| | - :ref:`ALM-12190 Number of Knox Connections Exceeds the Threshold ` | -| | - :ref:`ALM-19021 Handler Usage of RegionServer Exceeds the Threshold ` | -| | - :ref:`ALM-23001 Loader Service Unavailable ` | -| | - :ref:`ALM-23003 Loader Task Execution Failure ` | -| | - :ref:`ALM-23004 Loader Heap Memory Usage Exceeds the Threshold ` | -| | - :ref:`ALM-23005 Loader Non-Heap Memory Usage Exceeds the Threshold ` | -| | - :ref:`ALM-23006 Loader Direct Memory Usage Exceeds the Threshold ` | -| | - :ref:`ALM-23007 Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold ` | -| | - :ref:`ALM-38011 User Connection Usage on Broker Exceeds the Threshold ` | -| | - :ref:`ALM-45000 HetuEngine Service Unavailable ` | -| | - :ref:`ALM-45001 Faulty HetuEngine Compute Instances ` | -| | - :ref:`ALM-45429 Table Metadata Synchronization Failed on the Added ClickHouse Node ` | -| | - :ref:`ALM-45430 Permission Metadata Synchronization Failed on the Added ClickHouse Node ` | -| | - :ref:`ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation ` | -| | - :ref:`ALM-45432 ClickHouse User Synchronization Process Fails ` | -| | - :ref:`ALM-45433 ClickHouse AZ Topology Exception ` | -| | - :ref:`ALM-45434 A Single Replica Exists in the ClickHouse Data Table ` | -| | - :ref:`ALM-45585 IoTDB Service Unavailable ` | -| | - :ref:`ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold ` | -| | - :ref:`ALM-45587 IoTDBServer GC Duration Exceeds the Threshold ` | -| | - :ref:`ALM-45588 IoTDBServer Direct Memory Usage Exceeds the Threshold ` | -| | - :ref:`ALM-45589 ConfigNode Heap Memory Usage Exceeds the Threshold ` | -| | - :ref:`ALM-45590 ConfigNode GC Duration Exceeds the Threshold ` | -| | - :ref:`ALM-45591 ConfigNode Direct Memory Usage Exceeds the Threshold ` | -| | - :ref:`ALM-45592 IoTDBServer RPC Execution Duration Exceeds the Threshold ` | -| | - :ref:`ALM-45593 IoTDBServer Flush Execution Duration Exceeds the Threshold ` | -| | - :ref:`ALM-45594 IoTDBServer Intra-Space Merge Duration Exceeds the Threshold ` | -| | - :ref:`ALM-45595 IoTDBServer Cross-Space Merge Duration Exceeds the Threshold ` | -| | - :ref:`ALM-45615 CDL Service Unavailable ` | -| | - :ref:`ALM-45616 CDL Job Execution Exception ` | -| | - :ref:`ALM-45617 Data Queued in the CDL Replication Slot Exceeds the Threshold ` | -| | - :ref:`ALM-45635 FlinkServer Job Execution Failure ` | -| | - :ref:`ALM-45636 FlinkServer Job Checkpoints Keep Failing ` | -| | - :ref:`ALM-45636 Flink Job Checkpoints Keep Failing ` | -| | - :ref:`ALM-45637 FlinkServer Task Is Continuously Under Back Pressure ` | -| | - :ref:`ALM-45638 Number of Restarts After FlinkServer Job Failures Exceeds the Threshold ` | -| | - :ref:`ALM-45638 Number of Restarts After Flink Job Failures Exceeds the Threshold ` | -| | - :ref:`ALM-45640 FlinkServer Heartbeat Interruption Between the Active and Standby Nodes ` | -| | - :ref:`ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-11-01 | Modified the following content: | -| | | -| | - Added some FAQ. For details, see :ref:`FAQ `. | -| | - Updated the screenshots in some sections in :ref:`FusionInsight Manager Operation Guide (Applicable to 3.x) `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-9-29 | Modified the following content: | -| | | -| | Added MRS 3.1.2-LTS.3. For details, see :ref:`Creating a Custom Cluster `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2021-06-30 | Modified the following content: | -| | | -| | Added MRS 3.1.0-LTS.1. For details, see :ref:`Creating a Custom Cluster `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-03-12 | Accepted for RM-1305 and RM-2779. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-03-09 | Modified the following content: | -| | | -| | Added MRS 1.9.2. For details, see :ref:`Creating a Custom Cluster `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-02-22 | Modified the following content: | -| | | -| | - Added MRS 2.1.0. For details, see :ref:`Creating a Custom Cluster `. | -| | - Supported scale-out of nodes with new specifications. For details, see :ref:`Manually Scaling Out a Cluster `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-07-03 | Modified the following content: | -| | | -| | :ref:`Creating a Custom Cluster ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-10-09 | Accepted in OTC 3.2. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-09-10 | Modified the following content: | -| | | -| | :ref:`Sample Scripts ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-08-30 | - Added the following content: | -| | | -| | - :ref:`Installing Third-Party Software Using Bootstrap Actions ` | -| | - :ref:`Introduction to Bootstrap Actions ` | -| | - :ref:`Preparing the Bootstrap Action Script ` | -| | - :ref:`View Execution Records ` | -| | - :ref:`Adding a Bootstrap Action ` | -| | - :ref:`Sample Scripts ` | -| | | -| | - Modified the following content: | -| | | -| | - :ref:`Creating a Custom Cluster ` | -| | - :ref:`Creating a Cluster ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-05-29 | - Modified the following content: | -| | | -| | - :ref:`Creating a Cluster ` | -| | - :ref:`Creating a Custom Cluster ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-03-16 | - Added the following content: | -| | | -| | - :ref:`Manually Scaling In a Cluster ` | -| | - :ref:`Configuring an Auto Scaling Rule ` | -| | - :ref:`Configuring Message Notification ` | -| | - :ref:`ALM-12014 Device Partition Lost ` | -| | - :ref:`ALM-12015 Device Partition File System Read-Only ` | -| | - :ref:`ALM-12043 DNS Parsing Duration Exceeds the Threshold ` | -| | - :ref:`ALM-12045 Read Packet Dropped Rate Exceeds the Threshold ` | -| | - :ref:`ALM-12046 Write Packet Dropped Rate Exceeds the Threshold ` | -| | - :ref:`ALM-12047 Read Packet Error Rate Exceeds the Threshold ` | -| | - :ref:`ALM-12048 Write Packet Error Rate Exceeds the Threshold ` | -| | - :ref:`ALM-12049 Read Throughput Rate Exceeds the Threshold ` | -| | - :ref:`ALM-12050 Write Throughput Rate Exceeds the Threshold ` | -| | - :ref:`ALM-12051 Disk Inode Usage Exceeds the Threshold ` | -| | - :ref:`ALM-12052 Usage of Temporary TCP Ports Exceeds the Threshold ` | -| | - :ref:`ALM-12053 File Handle Usage Exceeds the Threshold ` | -| | - :ref:`ALM-12054 The Certificate File Is Invalid ` | -| | - :ref:`ALM-12055 The Certificate File Is About to Expire ` | -| | - :ref:`ALM-18008 Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold ` | -| | - :ref:`ALM-18009 Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold ` | -| | - :ref:`ALM-20002 Hue Service Unavailable ` | -| | - :ref:`ALM-43001 Spark Service Unavailable ` | -| | - :ref:`ALM-43006 Heap Memory Usage of the JobHistory Process Exceeds the Threshold ` | -| | - :ref:`ALM-43007 Non-Heap Memory Usage of the JobHistory Process Exceeds the Threshold ` | -| | - :ref:`ALM-43008 Direct Memory Usage of the JobHistory Process Exceeds the Threshold ` | -| | - :ref:`ALM-43009 JobHistory GC Time Exceeds the Threshold ` | -| | - :ref:`ALM-43010 Heap Memory Usage of the JDBCServer Process Exceeds the Threshold ` | -| | - :ref:`ALM-43011 Non-Heap Memory Usage of the JDBCServer Process Exceeds the Threshold ` | -| | - :ref:`ALM-43012 Direct Memory Usage of the JDBCServer Process Exceeds the Threshold ` | -| | - :ref:`ALM-43013 JDBCServer GC Time Exceeds the Threshold ` | -| | | -| | - Modified the following content: | -| | | -| | - :ref:`Creating a Cluster ` | -| | - :ref:`Uploading Data and Programs ` | -| | - :ref:`Creating a Job ` | -| | - :ref:`Cluster List ` | -| | - :ref:`Checking the Cluster Status ` | -| | - :ref:`Creating a Custom Cluster ` | -| | - :ref:`Viewing Basic Cluster Information ` | -| | - :ref:`Manually Scaling Out a Cluster ` | -| | - :ref:`Importing and Exporting Data ` | -| | - :ref:`Viewing Information of a Historical Cluster ` | -| | - :ref:`Accessing MRS Manager MRS 2.1.0 or Earlier) ` | -| | - :ref:`Changing the Password of an Operation User ` | -| | - :ref:`Initializing the Password of a System User ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-01-31 | Modified the following contents: | -| | | -| | - :ref:`Accessing MRS Manager MRS 2.1.0 or Earlier) ` | -| | - :ref:`Creating a Custom Cluster ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-11-08 | - Added the following content: | -| | | -| | - :ref:`Web UIs of Open Source Components ` | -| | | -| | - Modified the following contents: | -| | | -| | - :ref:`Creating a Cluster ` | -| | - :ref:`Creating a Custom Cluster ` | -| | - :ref:`Viewing Basic Cluster Information ` | -| | - :ref:`Manually Scaling Out a Cluster ` | -| | - :ref:`Viewing the Alarm List ` | -| | - :ref:`Viewing Information of a Historical Cluster ` | -| | - :ref:`Viewing Job Configuration and Logs ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-06-09 | - Added the following content: | -| | | -| | - :ref:`Viewing Information of a Historical Cluster ` | -| | - :ref:`Configuring Cross-Cluster Mutual Trust Relationships ` | -| | - :ref:`Configuring Users to Access Resources of a Trusted Cluster ` | -| | | -| | - Modified the following contents: | -| | | -| | - :ref:`Uploading Data and Programs ` | -| | - :ref:`Creating a Job ` | -| | - :ref:`Creating a Custom Cluster ` | -| | - :ref:`Installing a Client (Version 3.x or Later) ` | -| | - :ref:`Installing a Client (Versions Earlier Than 3.x) ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-04-06 | - Added the following content: | -| | | -| | - :ref:`Accessing MRS Manager MRS 2.1.0 or Earlier) ` | -| | - :ref:`MRS Multi-User Permission Management ` | -| | | -| | - Modified the following contents: | -| | | -| | - :ref:`Creating a Custom Cluster ` | -| | - :ref:`Manually Scaling Out a Cluster ` | -| | - :ref:`Viewing Basic Cluster Information ` | -| | - :ref:`Viewing and Manually Clearing an Alarm ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-02-20 | This issue is the first official release. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| Release Date | What's New | ++===================================+================================================================================================================================+ +| 2022-11-01 | Modified the following content: | +| | | +| | - Added some FAQ. For details, see :ref:`FAQ `. | +| | - Updated the screenshots in some sections in :ref:`FusionInsight Manager Operation Guide (Applicable to 3.x) `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2022-9-29 | Modified the following content: | +| | | +| | Added MRS 3.1.2-LTS.3. For details, see :ref:`Creating a Custom Cluster `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2021-06-30 | Modified the following content: | +| | | +| | Added MRS 3.1.0-LTS.1. For details, see :ref:`Creating a Custom Cluster `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2020-03-12 | Accepted for RM-1305 and RM-2779. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2020-03-09 | Modified the following content: | +| | | +| | Added MRS 1.9.2. For details, see :ref:`Creating a Custom Cluster `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2020-02-22 | Modified the following content: | +| | | +| | - Added MRS 2.1.0. For details, see :ref:`Creating a Custom Cluster `. | +| | - Supported scale-out of nodes with new specifications. For details, see :ref:`Manually Scaling Out a Cluster `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2019-07-03 | Modified the following content: | +| | | +| | :ref:`Creating a Custom Cluster ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2018-10-09 | Accepted in OTC 3.2. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2018-09-10 | Modified the following content: | +| | | +| | :ref:`Sample Scripts ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2018-08-30 | - Added the following content: | +| | | +| | - :ref:`Installing Third-Party Software Using Bootstrap Actions ` | +| | - :ref:`Introduction to Bootstrap Actions ` | +| | - :ref:`Preparing the Bootstrap Action Script ` | +| | - :ref:`View Execution Records ` | +| | - :ref:`Adding a Bootstrap Action ` | +| | - :ref:`Sample Scripts ` | +| | | +| | - Modified the following content: | +| | | +| | - :ref:`Creating a Custom Cluster ` | +| | - :ref:`Creating a Cluster ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2018-05-29 | - Modified the following content: | +| | | +| | - :ref:`Creating a Cluster ` | +| | - :ref:`Creating a Custom Cluster ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2018-03-16 | - Added the following content: | +| | | +| | - :ref:`Manually Scaling In a Cluster ` | +| | - :ref:`Configuring an Auto Scaling Rule ` | +| | - :ref:`Configuring Message Notification ` | +| | - :ref:`ALM-12014 Device Partition Lost ` | +| | - :ref:`ALM-12015 Device Partition File System Read-Only ` | +| | - :ref:`ALM-12043 DNS Parsing Duration Exceeds the Threshold ` | +| | - :ref:`ALM-12045 Read Packet Dropped Rate Exceeds the Threshold ` | +| | - :ref:`ALM-12046 Write Packet Dropped Rate Exceeds the Threshold ` | +| | - :ref:`ALM-12047 Read Packet Error Rate Exceeds the Threshold ` | +| | - :ref:`ALM-12048 Write Packet Error Rate Exceeds the Threshold ` | +| | - :ref:`ALM-12049 Read Throughput Rate Exceeds the Threshold ` | +| | - :ref:`ALM-12050 Write Throughput Rate Exceeds the Threshold ` | +| | - :ref:`ALM-12051 Disk Inode Usage Exceeds the Threshold ` | +| | - :ref:`ALM-12052 Usage of Temporary TCP Ports Exceeds the Threshold ` | +| | - :ref:`ALM-12053 File Handle Usage Exceeds the Threshold ` | +| | - :ref:`ALM-12054 The Certificate File Is Invalid ` | +| | - :ref:`ALM-12055 The Certificate File Is About to Expire ` | +| | - :ref:`ALM-18008 Heap Memory Usage of Yarn ResourceManager Exceeds the Threshold ` | +| | - :ref:`ALM-18009 Heap Memory Usage of MapReduce JobHistoryServer Exceeds the Threshold ` | +| | - :ref:`ALM-20002 Hue Service Unavailable ` | +| | - :ref:`ALM-43001 Spark Service Unavailable ` | +| | - :ref:`ALM-43006 Heap Memory Usage of the JobHistory Process Exceeds the Threshold ` | +| | - :ref:`ALM-43007 Non-Heap Memory Usage of the JobHistory Process Exceeds the Threshold ` | +| | - :ref:`ALM-43008 Direct Memory Usage of the JobHistory Process Exceeds the Threshold ` | +| | - :ref:`ALM-43009 JobHistory GC Time Exceeds the Threshold ` | +| | - :ref:`ALM-43010 Heap Memory Usage of the JDBCServer Process Exceeds the Threshold ` | +| | - :ref:`ALM-43011 Non-Heap Memory Usage of the JDBCServer Process Exceeds the Threshold ` | +| | - :ref:`ALM-43012 Direct Memory Usage of the JDBCServer Process Exceeds the Threshold ` | +| | - :ref:`ALM-43013 JDBCServer GC Time Exceeds the Threshold ` | +| | | +| | - Modified the following content: | +| | | +| | - :ref:`Creating a Cluster ` | +| | - :ref:`Uploading Data and Programs ` | +| | - :ref:`Creating a Job ` | +| | - :ref:`Cluster List ` | +| | - :ref:`Checking the Cluster Status ` | +| | - :ref:`Creating a Custom Cluster ` | +| | - :ref:`Viewing Basic Cluster Information ` | +| | - :ref:`Manually Scaling Out a Cluster ` | +| | - :ref:`Importing and Exporting Data ` | +| | - :ref:`Viewing Information of a Historical Cluster ` | +| | - :ref:`Accessing MRS Manager MRS 2.1.0 or Earlier) ` | +| | - :ref:`Changing the Password of an Operation User ` | +| | - :ref:`Initializing the Password of a System User ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2018-01-31 | Modified the following contents: | +| | | +| | - :ref:`Accessing MRS Manager MRS 2.1.0 or Earlier) ` | +| | - :ref:`Creating a Custom Cluster ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2017-11-08 | - Added the following content: | +| | | +| | - :ref:`Web UIs of Open Source Components ` | +| | | +| | - Modified the following contents: | +| | | +| | - :ref:`Creating a Cluster ` | +| | - :ref:`Creating a Custom Cluster ` | +| | - :ref:`Viewing Basic Cluster Information ` | +| | - :ref:`Manually Scaling Out a Cluster ` | +| | - :ref:`Viewing the Alarm List ` | +| | - :ref:`Viewing Information of a Historical Cluster ` | +| | - :ref:`Viewing Job Configuration and Logs ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2017-06-09 | - Added the following content: | +| | | +| | - :ref:`Viewing Information of a Historical Cluster ` | +| | - :ref:`Configuring Cross-Cluster Mutual Trust Relationships ` | +| | - :ref:`Configuring Users to Access Resources of a Trusted Cluster ` | +| | | +| | - Modified the following contents: | +| | | +| | - :ref:`Uploading Data and Programs ` | +| | - :ref:`Creating a Job ` | +| | - :ref:`Creating a Custom Cluster ` | +| | - :ref:`Installing a Client (Version 3.x or Later) ` | +| | - :ref:`Installing a Client (Versions Earlier Than 3.x) ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2017-04-06 | - Added the following content: | +| | | +| | - :ref:`Accessing MRS Manager MRS 2.1.0 or Earlier) ` | +| | - :ref:`MRS Multi-User Permission Management ` | +| | | +| | - Modified the following contents: | +| | | +| | - :ref:`Creating a Custom Cluster ` | +| | - :ref:`Manually Scaling Out a Cluster ` | +| | - :ref:`Viewing Basic Cluster Information ` | +| | - :ref:`Viewing and Manually Clearing an Alarm ` | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +| 2017-02-20 | This issue is the first official release. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/conf.py b/umn/source/conf.py index 65d6d7c..ce99174 100644 --- a/umn/source/conf.py +++ b/umn/source/conf.py @@ -31,13 +31,13 @@ otcdocs_git_fqdn = 'gitea.eco.tsi-dev.otc-service.com' otcdocs_git_type = 'gitea' # Those variables are needed for indexing into OpenSearch -otcdocs_doc_environment = 'internal' -otcdocs_doc_link = '/mapreduce-service/umn/' -otcdocs_doc_title = 'User Guide' -otcdocs_doc_type = 'umn' -otcdocs_service_category = 'big_data' -otcdocs_service_title = 'MapReduce Service' -otcdocs_service_type = 'mrs' +otcdocs_doc_environment = '' +otcdocs_doc_link = '' +otcdocs_doc_title = '' +otcdocs_doc_type = '' +otcdocs_service_category = '' +otcdocs_service_title = '' +otcdocs_service_type = '' otcdocs_search_environment = 'hc_de' otcdocs_search_url = "https://opensearch.eco.tsi-dev.otc-service.com/" diff --git a/umn/source/configuring_a_cluster/creating_a_custom_cluster.rst b/umn/source/configuring_a_cluster/creating_a_custom_cluster.rst index 965dddb..f4d1232 100644 --- a/umn/source/configuring_a_cluster/creating_a_custom_cluster.rst +++ b/umn/source/configuring_a_cluster/creating_a_custom_cluster.rst @@ -59,7 +59,7 @@ Software Configurations | | | | | The default name is **mrs**\ \_\ *xxxx*. *xxxx* is a random collection of letters and digits. | +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Cluster Version | Currently, MRS 1.6.3, 1.7.2, 1.9.2, 2.1.0, 3.1.0-LTS.1, 3.1.2-LTS.3 , and 3.2.0-LTS.1 are supported. The latest version of MRS is used by default. | + | Cluster Version | Currently, MRS 1.6.3, 1.7.2, 1.9.2, 2.1.0, 3.1.0-LTS.1, and 3.1.2-LTS.3 are supported. The latest version of MRS is used by default. | +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Cluster Type | The cluster types are as follows: | | | | @@ -109,6 +109,8 @@ Software Configurations | | | | | - Ranger: a framework to enable, monitor, and manage data security across the Hadoop platform | | | | + | | - Impala: an SQL query engine for processing huge volumes of data | + | | | | | - ClickHouse: A column database management system (DBMS) for on-line analytical processing (OLAP). The ClickHouse cluster table engine that uses Kunpeng as the CPU architecture does not support HDFS and Kafka. | | | | | | - Kudu: a column-oriented data store | diff --git a/umn/source/configuring_a_cluster/creating_a_custom_topology_cluster.rst b/umn/source/configuring_a_cluster/creating_a_custom_topology_cluster.rst index c90281a..5211109 100644 --- a/umn/source/configuring_a_cluster/creating_a_custom_topology_cluster.rst +++ b/umn/source/configuring_a_cluster/creating_a_custom_topology_cluster.rst @@ -116,195 +116,179 @@ Topology Adjustment for a Custom Cluster .. table:: **Table 3** Topology adjustment - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Service | Dependency | Role | Role Deployment Suggestions | Description | - +===================================================+==========================+==========================+======================================================================================+=========================================================================================================================================+ - | OMSServer | ``-`` | OMSServer | This role can be deployed it on the Master node and cannot be modified. | ``-`` | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | CDL | - Depends on Kafka. | CC(CDLConnector) | This role can be deployed in all node groups. | It is recommended that the number of CDLConnector instances to be deployed be the same as the number of Broker roles. | - | | - Depends on DBService. | | | | - | (applicable only to MRS 3.2.0 and later versions) | | | Number of role instances to be deployed: 1 to 256 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | CS(CDLService) | This role can be deployed in all node groups. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 or 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | ClickHouse | Depends on ZooKeeper. | CHS (ClickHouseServer) | This role can be deployed on all nodes. | A non-Master node group with this role assigned is considered as a Core node. | - | | | | | | - | | | | Number of role instances to be deployed: an even number ranging from 2 to 256 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | CLB (ClickHouseBalancer) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 to 256 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | ZooKeeper | ``-`` | QP(quorumpeer) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 3 to 9, with the step size of 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Hadoop | Depends on ZooKeeper. | NN(NameNode) | This role can be deployed on the Master node only. | The NameNode and ZKFC processes are deployed on the same server for cluster HA. | - | | | | | | - | | | | Number of role instances to be deployed: 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | HFS (HttpFS) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 10 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | JN(JournalNode) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 3 to 60, with the step size of 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | DN(DataNode) | This role can be deployed on all nodes. | A non-Master node group with this role assigned is considered as a Core node. | - | | | | | | - | | | | Number of role instances to be deployed: 3 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | RM(ResourceManager) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | NM(NodeManager) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 3 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | JHS(JobHistoryServer) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | TLS(TimelineServer) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 1 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Presto | Depends on Hive. | PCD(Coordinator) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | PWK(Worker) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Spark2x | - Depends on Hadoop. | JS2X(JDBCServer2x) | This role can be deployed on the Master node only. | ``-`` | - | | - Depends on Hive. | | | | - | | - Depends on ZooKeeper. | | Number of role instances to be deployed: 2 to 10 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | JH2X(JobHistory2x) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | SR2X(SparkResource2x) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 to 50 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | IS2X(IndexServer2x) | (Optional) This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 2, with the step size of 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | HBase | Depends on Hadoop. | HM(HMaster) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | TS(ThriftServer) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | RT(RESTServer) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | RS(RegionServer) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 3 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | TS1(Thrift1Server) | This role can be deployed on all nodes. | If the Hue service is installed in a cluster and HBase needs to be used on the Hue web UI, install this instance for the HBase service. | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Hive | - Depends on Hadoop. | MS(MetaStore) | This role can be deployed on the Master node only. | ``-`` | - | | - Depends on DBService. | | | | - | | | | Number of role instances to be deployed: 2 to 10 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | WH (WebHCat) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 10 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | HS(HiveServer) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 to 80 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Hue | Depends on DBService. | H(Hue) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Sqoop | Depends on Hadoop. | SC(SqoopClient) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Kafka | Depends on ZooKeeper. | B(Broker) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 3 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Flume | ``-`` | MS(MonitorServer) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | F(Flume) | This role can be deployed on all nodes. | A non-Master node group with this role assigned is considered as a Core node. | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Tez | - Depends on Hadoop. | TUI(TezUI) | This role can be deployed on the Master node only. | ``-`` | - | | - Depends on DBService. | | | | - | | - Depends on ZooKeeper. | | Number of role instances to be deployed: 1 to 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Flink | - Depends on ZooKeeper. | FR(FlinkResource) | This role can be deployed on all nodes. | ``-`` | - | | - Depends on Hadoop. | | | | - | | | | Number of role instances to be deployed: 1 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | FS(FlinkServer) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Oozie | - Depends on Hadoop. | O(oozie) | This role can be deployed on the Master node only. | ``-`` | - | | - Depends on DBService. | | | | - | | - Depends on ZooKeeper. | | Number of role instances to be deployed: 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Impala | - Depends on Hadoop. | StateStore | This role can be deployed on the Master node only. | ``-`` | - | | - Depends on Hive. | | | | - | | - Depends on DBService. | | Number of role instances to be deployed: 1 | | - | | - Depends on ZooKeeper. | | | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | Catalog | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | Impalad | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Kudu | ``-`` | KuduMaster | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 3 or 5 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | KuduTserver | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 3 to 10,000 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | Ranger | Depends on DBService. | RA(RangerAdmin) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 to 2 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | USC(UserSync) | This role can be deployed on the Master node only. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 1 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | TSC (TagSync) | This role can be deployed on all nodes. | ``-`` | - | | | | | | - | | | | Number of role instances to be deployed: 0 to 1 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | IoTDB | Depends on KerbServer. | IS (IoTDBServer) | This role can be deployed in all node groups. | It is recommended that IoTDBServer be deployed independently and not co-deployed with other data nodes. | - | | | | | | - | (applicable only to MRS 3.2.0 and later versions) | | | Number of role instances to be deployed: 3 to 256 | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ - | | | CN(ConfigNode) | This role can only be deployed in the master node group. | ``-`` | - | | | | | | - | | | | The number of role instances must be at least 3 and at most 9 with a step size of 2. | | - +---------------------------------------------------+--------------------------+--------------------------+--------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Service | Dependency | Role | Role Deployment Suggestions | Description | + +=============+==========================+==========================+===============================================================================+=========================================================================================================================================+ + | OMSServer | ``-`` | OMSServer | This role can be deployed it on the Master node and cannot be modified. | ``-`` | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | ClickHouse | Depends on ZooKeeper. | CHS (ClickHouseServer) | This role can be deployed on all nodes. | A non-Master node group with this role assigned is considered as a Core node. | + | | | | | | + | | | | Number of role instances to be deployed: an even number ranging from 2 to 256 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | CLB (ClickHouseBalancer) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 to 256 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | ZooKeeper | ``-`` | QP(quorumpeer) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 3 to 9, with the step size of 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Hadoop | Depends on ZooKeeper. | NN(NameNode) | This role can be deployed on the Master node only. | The NameNode and ZKFC processes are deployed on the same server for cluster HA. | + | | | | | | + | | | | Number of role instances to be deployed: 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | HFS (HttpFS) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 10 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | JN(JournalNode) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 3 to 60, with the step size of 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | DN(DataNode) | This role can be deployed on all nodes. | A non-Master node group with this role assigned is considered as a Core node. | + | | | | | | + | | | | Number of role instances to be deployed: 3 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | RM(ResourceManager) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | NM(NodeManager) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 3 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | JHS(JobHistoryServer) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | TLS(TimelineServer) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 1 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Presto | Depends on Hive. | PCD(Coordinator) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | PWK(Worker) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Spark2x | - Depends on Hadoop. | JS2X(JDBCServer2x) | This role can be deployed on the Master node only. | ``-`` | + | | - Depends on Hive. | | | | + | | - Depends on ZooKeeper. | | Number of role instances to be deployed: 2 to 10 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | JH2X(JobHistory2x) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | SR2X(SparkResource2x) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 to 50 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | IS2X(IndexServer2x) | (Optional) This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 2, with the step size of 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | HBase | Depends on Hadoop. | HM(HMaster) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | TS(ThriftServer) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | RT(RESTServer) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | RS(RegionServer) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 3 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | TS1(Thrift1Server) | This role can be deployed on all nodes. | If the Hue service is installed in a cluster and HBase needs to be used on the Hue web UI, install this instance for the HBase service. | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Hive | - Depends on Hadoop. | MS(MetaStore) | This role can be deployed on the Master node only. | ``-`` | + | | - Depends on DBService. | | | | + | | | | Number of role instances to be deployed: 2 to 10 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | WH (WebHCat) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 10 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | HS(HiveServer) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 to 80 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Hue | Depends on DBService. | H(Hue) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Sqoop | Depends on Hadoop. | SC(SqoopClient) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Kafka | Depends on ZooKeeper. | B(Broker) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 3 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Flume | ``-`` | MS(MonitorServer) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | F(Flume) | This role can be deployed on all nodes. | A non-Master node group with this role assigned is considered as a Core node. | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Tez | - Depends on Hadoop. | TUI(TezUI) | This role can be deployed on the Master node only. | ``-`` | + | | - Depends on DBService. | | | | + | | - Depends on ZooKeeper. | | Number of role instances to be deployed: 1 to 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Flink | - Depends on ZooKeeper. | FR(FlinkResource) | This role can be deployed on all nodes. | ``-`` | + | | - Depends on Hadoop. | | | | + | | | | Number of role instances to be deployed: 1 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | FS(FlinkServer) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Oozie | - Depends on Hadoop. | O(oozie) | This role can be deployed on the Master node only. | ``-`` | + | | - Depends on DBService. | | | | + | | - Depends on ZooKeeper. | | Number of role instances to be deployed: 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Impala | - Depends on Hadoop. | StateStore | This role can be deployed on the Master node only. | ``-`` | + | | - Depends on Hive. | | | | + | | - Depends on DBService. | | Number of role instances to be deployed: 1 | | + | | - Depends on ZooKeeper. | | | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | Catalog | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | Impalad | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Kudu | ``-`` | KuduMaster | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 3 or 5 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | KuduTserver | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 3 to 10,000 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | Ranger | Depends on DBService. | RA(RangerAdmin) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 to 2 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | USC(UserSync) | This role can be deployed on the Master node only. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 1 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ + | | | TSC (TagSync) | This role can be deployed on all nodes. | ``-`` | + | | | | | | + | | | | Number of role instances to be deployed: 0 to 1 | | + +-------------+--------------------------+--------------------------+-------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ .. |image1| image:: /_static/images/en-us_image_0000001296217772.png diff --git a/umn/source/faq/alarm_monitoring/how_do_i_understand_the_multi-level_chart_statistics_in_the_hbase_operation_requests_metric.rst b/umn/source/faq/alarm_monitoring/how_do_i_understand_the_multi-level_chart_statistics_in_the_hbase_operation_requests_metric.rst index 95b784d..8d51e1d 100644 --- a/umn/source/faq/alarm_monitoring/how_do_i_understand_the_multi-level_chart_statistics_in_the_hbase_operation_requests_metric.rst +++ b/umn/source/faq/alarm_monitoring/how_do_i_understand_the_multi-level_chart_statistics_in_the_hbase_operation_requests_metric.rst @@ -23,7 +23,7 @@ The following uses the **Operation Requests on RegionServers** monitoring item a |image4| -.. |image1| image:: /_static/images/en-us_image_0000001392734314.png -.. |image2| image:: /_static/images/en-us_image_0000001392414762.png -.. |image3| image:: /_static/images/en-us_image_0000001442414237.png -.. |image4| image:: /_static/images/en-us_image_0000001392255246.png +.. |image1| image:: /_static/images/en-us_image_0000001337953138.png +.. |image2| image:: /_static/images/en-us_image_0000001338429394.png +.. |image3| image:: /_static/images/en-us_image_0000001388629905.png +.. |image4| image:: /_static/images/en-us_image_0000001388630241.png diff --git a/umn/source/faq/big_data_service_development/how_do_i_check_whether_the_resourcemanager_configuration_of_yarn_is_correct.rst b/umn/source/faq/big_data_service_development/how_do_i_check_whether_the_resourcemanager_configuration_of_yarn_is_correct.rst index 88899da..d3e6c08 100644 --- a/umn/source/faq/big_data_service_development/how_do_i_check_whether_the_resourcemanager_configuration_of_yarn_is_correct.rst +++ b/umn/source/faq/big_data_service_development/how_do_i_check_whether_the_resourcemanager_configuration_of_yarn_is_correct.rst @@ -46,4 +46,4 @@ How Do I Check Whether the ResourceManager Configuration of Yarn Is Correct? If the latest configuration has not been loaded after the configuration synchronization is complete, a message will be displayed on the Manager page indicating that the configuration has expired. However, this will not affect services. The latest configuration will be automatically loaded when the component restarts. -.. |image1| image:: /_static/images/en-us_image_0000001392574346.png +.. |image1| image:: /_static/images/en-us_image_0293131436.png diff --git a/umn/source/faq/big_data_service_development/how_do_i_configure_other_data_sources_on_presto.rst b/umn/source/faq/big_data_service_development/how_do_i_configure_other_data_sources_on_presto.rst index 9c42dc2..86701f3 100644 --- a/umn/source/faq/big_data_service_development/how_do_i_configure_other_data_sources_on_presto.rst +++ b/umn/source/faq/big_data_service_development/how_do_i_configure_other_data_sources_on_presto.rst @@ -68,4 +68,4 @@ In this section, MySQL is used as an example. #. Restart the Presto service. -.. |image1| image:: /_static/images/en-us_image_0000001442654037.png +.. |image1| image:: /_static/images/en-us_image_0000001261300062.png diff --git a/umn/source/faq/big_data_service_development/how_do_i_connect_to_spark_beeline_from_mrs.rst b/umn/source/faq/big_data_service_development/how_do_i_connect_to_spark_beeline_from_mrs.rst index 5ff2a74..a0695c1 100644 --- a/umn/source/faq/big_data_service_development/how_do_i_connect_to_spark_beeline_from_mrs.rst +++ b/umn/source/faq/big_data_service_development/how_do_i_connect_to_spark_beeline_from_mrs.rst @@ -35,7 +35,7 @@ How Do I Connect to Spark Beeline from MRS? If the table **test** is displayed in the command output, OBS is successfully accessed. - .. figure:: /_static/images/en-us_image_0000001442414245.png + .. figure:: /_static/images/en-us_image_0264281176.png :alt: **Figure 1** Returned table name **Figure 1** Returned table name diff --git a/umn/source/faq/big_data_service_development/how_do_i_do_if_an_error_occurs_when_hive_runs_the_beeline_-e_command_to_execute_multiple_statements.rst b/umn/source/faq/big_data_service_development/how_do_i_do_if_an_error_occurs_when_hive_runs_the_beeline_-e_command_to_execute_multiple_statements.rst index 55aea10..4193933 100644 --- a/umn/source/faq/big_data_service_development/how_do_i_do_if_an_error_occurs_when_hive_runs_the_beeline_-e_command_to_execute_multiple_statements.rst +++ b/umn/source/faq/big_data_service_development/how_do_i_do_if_an_error_occurs_when_hive_runs_the_beeline_-e_command_to_execute_multiple_statements.rst @@ -15,7 +15,7 @@ Solutions: #. In the **/opt/Bigdata/client/Hive** directory on the Hive client, change **export CLIENT_HIVE_ENTIRELINEASCOMMAND=true** in the **component_env** file to **export CLIENT_HIVE_ENTIRELINEASCOMMAND=false**. - .. figure:: /_static/images/en-us_image_0000001392414806.png + .. figure:: /_static/images/en-us_image_0000001205479339.png :alt: **Figure 1** Changing the **component_env** file **Figure 1** Changing the **component_env** file diff --git a/umn/source/faq/big_data_service_development/how_do_i_do_if_sessions_are_not_released_after_hue_connects_to_hiveserver_and_the_error_message_over_max_user_connections_is_displayed.rst b/umn/source/faq/big_data_service_development/how_do_i_do_if_sessions_are_not_released_after_hue_connects_to_hiveserver_and_the_error_message_over_max_user_connections_is_displayed.rst index 6f3b76b..a8da0bb 100644 --- a/umn/source/faq/big_data_service_development/how_do_i_do_if_sessions_are_not_released_after_hue_connects_to_hiveserver_and_the_error_message_over_max_user_connections_is_displayed.rst +++ b/umn/source/faq/big_data_service_development/how_do_i_do_if_sessions_are_not_released_after_hue_connects_to_hiveserver_and_the_error_message_over_max_user_connections_is_displayed.rst @@ -17,4 +17,4 @@ Applicable versions: MRS 3.1.0 and earlier |image1| -.. |image1| image:: /_static/images/en-us_image_0000001392255290.png +.. |image1| image:: /_static/images/en-us_image_0000001195220440.png diff --git a/umn/source/faq/big_data_service_development/how_do_i_modify_the_allow_drop_detached_parameter_of_clickhouse.rst b/umn/source/faq/big_data_service_development/how_do_i_modify_the_allow_drop_detached_parameter_of_clickhouse.rst index 809feb0..43b7664 100644 --- a/umn/source/faq/big_data_service_development/how_do_i_modify_the_allow_drop_detached_parameter_of_clickhouse.rst +++ b/umn/source/faq/big_data_service_development/how_do_i_modify_the_allow_drop_detached_parameter_of_clickhouse.rst @@ -42,4 +42,4 @@ How Do I Modify the allow_drop_detached Parameter of ClickHouse? #. Run the **q;** command to exit the ClickHouse client. -.. |image1| image:: /_static/images/en-us_image_0000001392255262.png +.. |image1| image:: /_static/images/en-us_image_0000001223688037.png diff --git a/umn/source/faq/big_data_service_development/index.rst b/umn/source/faq/big_data_service_development/index.rst index a589c81..aff01ad 100644 --- a/umn/source/faq/big_data_service_development/index.rst +++ b/umn/source/faq/big_data_service_development/index.rst @@ -42,7 +42,7 @@ Big Data Service Development - :ref:`How Do I Do If an Alarm Indicating Insufficient Memory Is Reported During Spark Task Execution? ` - :ref:`How Do I Do If ClickHouse Consumes Excessive CPU Resources? ` - :ref:`How Do I Enable the Map Type on ClickHouse? ` -- :ref:`A Large Number of OBS APIs Are Called When Spark SQL Accesses Hive Partitioned Tables ` +- :ref:`It Takes a Long Time for Spark SQL to Access Hive Partitioned Tables Before Job Startup ` .. toctree:: :maxdepth: 1 @@ -85,4 +85,4 @@ Big Data Service Development how_do_i_do_if_an_alarm_indicating_insufficient_memory_is_reported_during_spark_task_execution how_do_i_do_if_clickhouse_consumes_excessive_cpu_resources how_do_i_enable_the_map_type_on_clickhouse - a_large_number_of_obs_apis_are_called_when_spark_sql_accesses_hive_partitioned_tables + it_takes_a_long_time_for_spark_sql_to_access_hive_partitioned_tables_before_job_startup diff --git a/umn/source/faq/big_data_service_development/a_large_number_of_obs_apis_are_called_when_spark_sql_accesses_hive_partitioned_tables.rst b/umn/source/faq/big_data_service_development/it_takes_a_long_time_for_spark_sql_to_access_hive_partitioned_tables_before_job_startup.rst similarity index 93% rename from umn/source/faq/big_data_service_development/a_large_number_of_obs_apis_are_called_when_spark_sql_accesses_hive_partitioned_tables.rst rename to umn/source/faq/big_data_service_development/it_takes_a_long_time_for_spark_sql_to_access_hive_partitioned_tables_before_job_startup.rst index 76d55c0..b5735b3 100644 --- a/umn/source/faq/big_data_service_development/a_large_number_of_obs_apis_are_called_when_spark_sql_accesses_hive_partitioned_tables.rst +++ b/umn/source/faq/big_data_service_development/it_takes_a_long_time_for_spark_sql_to_access_hive_partitioned_tables_before_job_startup.rst @@ -2,8 +2,8 @@ .. _mrs_03_1248: -A Large Number of OBS APIs Are Called When Spark SQL Accesses Hive Partitioned Tables -===================================================================================== +It Takes a Long Time for Spark SQL to Access Hive Partitioned Tables Before Job Startup +======================================================================================= Symptom ------- diff --git a/umn/source/faq/big_data_service_development/what_if_an_excel_file_downloaded_on_hue_failed_to_open.rst b/umn/source/faq/big_data_service_development/what_if_an_excel_file_downloaded_on_hue_failed_to_open.rst index 9c690f7..cda490c 100644 --- a/umn/source/faq/big_data_service_development/what_if_an_excel_file_downloaded_on_hue_failed_to_open.rst +++ b/umn/source/faq/big_data_service_development/what_if_an_excel_file_downloaded_on_hue_failed_to_open.rst @@ -20,7 +20,7 @@ What If an Excel File Downloaded on Hue Failed to Open? If **active** is displayed in the command output, the node is the active node. Otherwise, log in to the other Master node. - .. figure:: /_static/images/en-us_image_0000001442654025.png + .. figure:: /_static/images/en-us_image_0000001439442217.png :alt: **Figure 1** Active OMS node **Figure 1** Active OMS node @@ -42,7 +42,7 @@ What If an Excel File Downloaded on Hue Failed to Open? ProxyHTMLURLMap (https?:\/\/[^:]*:[0-9]*.*) ${PROXY_PREFIX}/proxyRedirect=$1 RV - .. figure:: /_static/images/en-us_image_0000001392414778.png + .. figure:: /_static/images/en-us_image_0268284607.png :alt: **Figure 2** Content to be deleted **Figure 2** Content to be deleted @@ -58,7 +58,7 @@ What If an Excel File Downloaded on Hue Failed to Open? ProxyHTMLURLMap (https?:\/\/[^:]*:[0-9]*.*) ${PROXY_PREFIX}/proxyRedirect=$1 RV - .. figure:: /_static/images/en-us_image_0000001392734330.png + .. figure:: /_static/images/en-us_image_0268298534.png :alt: **Figure 3** Content to be deleted **Figure 3** Content to be deleted diff --git a/umn/source/faq/client_usage/how_do_i_configure_environment_variables_and_run_commands_on_a_component_client.rst b/umn/source/faq/client_usage/how_do_i_configure_environment_variables_and_run_commands_on_a_component_client.rst index da66707..6c7c39b 100644 --- a/umn/source/faq/client_usage/how_do_i_configure_environment_variables_and_run_commands_on_a_component_client.rst +++ b/umn/source/faq/client_usage/how_do_i_configure_environment_variables_and_run_commands_on_a_component_client.rst @@ -9,7 +9,7 @@ How Do I Configure Environment Variables and Run Commands on a Component Client? #. Run the **su - omm** command to switch to user **omm**. -#. Run the **cd** *client installation directory* command to switch to the client. +#. Run the **cd** *Client installation directory* command to switch to the client. #. Run the **source bigdata_env** command to configure environment variables. diff --git a/umn/source/faq/cluster_management/how_do_i_configure_the_knox_memory.rst b/umn/source/faq/cluster_management/how_do_i_configure_the_knox_memory.rst index e942422..44f15b5 100644 --- a/umn/source/faq/cluster_management/how_do_i_configure_the_knox_memory.rst +++ b/umn/source/faq/cluster_management/how_do_i_configure_the_knox_memory.rst @@ -26,7 +26,7 @@ How Do I Configure the knox Memory? #. Run the **ps -ef \|grep knox** command to check the configured memory. - .. figure:: /_static/images/en-us_image_0000001442774001.png + .. figure:: /_static/images/en-us_image_0293101307.png :alt: **Figure 1** knox memory **Figure 1** knox memory diff --git a/umn/source/faq/cluster_management/how_do_i_do_if_the_time_on_mrs_nodes_is_incorrect.rst b/umn/source/faq/cluster_management/how_do_i_do_if_the_time_on_mrs_nodes_is_incorrect.rst index e1d0767..deb7497 100644 --- a/umn/source/faq/cluster_management/how_do_i_do_if_the_time_on_mrs_nodes_is_incorrect.rst +++ b/umn/source/faq/cluster_management/how_do_i_do_if_the_time_on_mrs_nodes_is_incorrect.rst @@ -18,7 +18,7 @@ How Do I Do If the Time on MRS Nodes Is Incorrect? server master2_ip - .. figure:: /_static/images/en-us_image_0000001442414233.png + .. figure:: /_static/images/en-us_image_0000001439594513.png :alt: **Figure 1** Adding the master node IP addresses **Figure 1** Adding the master node IP addresses diff --git a/umn/source/faq/cluster_management/how_do_i_do_if_trust_relationships_between_nodes_are_abnormal.rst b/umn/source/faq/cluster_management/how_do_i_do_if_trust_relationships_between_nodes_are_abnormal.rst index ab4b7ac..e1d126b 100644 --- a/umn/source/faq/cluster_management/how_do_i_do_if_trust_relationships_between_nodes_are_abnormal.rst +++ b/umn/source/faq/cluster_management/how_do_i_do_if_trust_relationships_between_nodes_are_abnormal.rst @@ -27,6 +27,6 @@ If "ALM-12066 Inter-Node Mutual Trust Fails" is reported on Manager or there is #. If the **home** directory of user **omm** is deleted, contact MRS support personnel. -.. |image1| image:: /_static/images/en-us_image_0000001392255270.png -.. |image2| image:: /_static/images/en-us_image_0000001392414786.png -.. |image3| image:: /_static/images/en-us_image_0000001442654033.png +.. |image1| image:: /_static/images/en-us_image_0000001184290228.png +.. |image2| image:: /_static/images/en-us_image_0000001229609903.png +.. |image3| image:: /_static/images/en-us_image_0000001229690017.png diff --git a/umn/source/faq/cluster_management/how_do_i_query_the_startup_time_of_an_mrs_node.rst b/umn/source/faq/cluster_management/how_do_i_query_the_startup_time_of_an_mrs_node.rst index 7be1fa9..0bf4627 100644 --- a/umn/source/faq/cluster_management/how_do_i_query_the_startup_time_of_an_mrs_node.rst +++ b/umn/source/faq/cluster_management/how_do_i_query_the_startup_time_of_an_mrs_node.rst @@ -11,4 +11,4 @@ Log in to the target node and run the following command to query the startup tim |image1| -.. |image1| image:: /_static/images/en-us_image_0000001392574342.png +.. |image1| image:: /_static/images/en-us_image_0000001374635732.png diff --git a/umn/source/faq/cluster_management/how_do_i_view_log_information.rst b/umn/source/faq/cluster_management/how_do_i_view_log_information.rst index 82df374..cb6a7bc 100644 --- a/umn/source/faq/cluster_management/how_do_i_view_log_information.rst +++ b/umn/source/faq/cluster_management/how_do_i_view_log_information.rst @@ -19,7 +19,7 @@ You can view operation logs of clusters and jobs on the **Operation Logs** page. .. _mrs_03_1003__fig36909253103815: -.. figure:: /_static/images/en-us_image_0000001442654061.png +.. figure:: /_static/images/en-us_image_0000001388541980.png :alt: **Figure 1** Log information **Figure 1** Log information diff --git a/umn/source/faq/job_development/how_do_i_do_if_the_spark_job_error_unknownscannerexeception_is_reported.rst b/umn/source/faq/job_development/how_do_i_do_if_the_spark_job_error_unknownscannerexeception_is_reported.rst new file mode 100644 index 0000000..862c882 --- /dev/null +++ b/umn/source/faq/job_development/how_do_i_do_if_the_spark_job_error_unknownscannerexeception_is_reported.rst @@ -0,0 +1,18 @@ +:original_name: mrs_03_1257.html + +.. _mrs_03_1257: + +How Do I Do If the Spark Job Error "UnknownScannerExeception" Is Reported? +========================================================================== + +Symptom +------- + +Spark jobs run slowly. Warning information is printed in run logs, and the error cause is **UnknownScannerExeception**. + +Solution +-------- + +Before running a Spark job, adjust the value of **hbase.client.scanner.timeout.period** (for example, from 60 seconds to 120 seconds). + +Log in to FusionInsight Manager and choose **Cluster** > **Services** > **HBase**. Click **Configurations** then **All Configurations**, search for **hbase.client.scanner.timeout.period**, and change its value to **120000** (unit: ms). diff --git a/umn/source/faq/job_development/how_do_i_view_mrs_job_logs.rst b/umn/source/faq/job_development/how_do_i_view_mrs_job_logs.rst new file mode 100644 index 0000000..fd2b4f0 --- /dev/null +++ b/umn/source/faq/job_development/how_do_i_view_mrs_job_logs.rst @@ -0,0 +1,25 @@ +:original_name: mrs_03_1172.html + +.. _mrs_03_1172: + +How Do I View MRS Job Logs? +=========================== + +#. .. _mrs_03_1172__li943507288: + + On the **Jobs** page of the MRS console, you can view logs of each job, including launcherJob and realJob logs. + + - Generally, error logs are printed in **stderr** and **stdout** for launcherJob jobs, as shown in the following figure: + + |image1| + + - You can view realJob logs on the ResourceManager web UI provided by the Yarn service on MRS Manager. + + |image2| + +#. Log in to the Master node of the cluster to obtain the job log files in :ref:`1 `. The HDFS path is **/tmp/logs/**\ *{submit_user}*\ **/logs/**\ *{application_id}*. + +#. After the job is submitted, if the job application ID cannot be found on the Yarn web UI, the job fails to be submitted. You can log in to the active Master node of the cluster and view the job submission process log **/var/log/executor/logs/exe.log**. + +.. |image1| image:: /_static/images/en-us_image_0000001151963015.png +.. |image2| image:: /_static/images/en-us_image_0000001438033333.png diff --git a/umn/source/faq/job_development/index.rst b/umn/source/faq/job_development/index.rst index 53dd51e..8519751 100644 --- a/umn/source/faq/job_development/index.rst +++ b/umn/source/faq/job_development/index.rst @@ -8,7 +8,8 @@ Job Development - :ref:`How Do I Get My Data into OBS or HDFS? ` - :ref:`What Types of Spark Jobs Can Be Submitted in a Cluster? ` - :ref:`Can I Run Multiple Spark Tasks at the Same Time After the Minimum Tenant Resources of an MRS Cluster Is Changed to 0? ` -- :ref:`What Are the Differences Between the Client Mode and Cluster Mode of Spark Jobs? ` +- :ref:`What Are the Differences Between the Client Mode and Cluster Mode of Spark Jobs? ` +- :ref:`How Do I View MRS Job Logs? ` - :ref:`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? ` - :ref:`LauncherJob Job Execution Is Failed And the Error Message "jobPropertiesMap is null." Is Displayed ` - :ref:`How Do I Do If the Flink Job Status on the MRS Console Is Inconsistent with That on Yarn? ` @@ -16,6 +17,7 @@ Job Development - :ref:`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? ` - :ref:`How Do I Do If Error Message "java.io.IOException: Connection reset by peer" Is Displayed During the Execution of a Spark Job? ` - :ref:`How Do I Do If Error Message "requestId=4971883851071737250" Is Displayed When a Spark Job Accesses OBS? ` +- :ref:`How Do I Do If the Spark Job Error "UnknownScannerExeception" Is Reported? ` - :ref:`Why DataArtsStudio Occasionally Fail to Schedule Spark Jobs and the Rescheduling also Fails? ` - :ref:`How Do I Do If a Flink Job Fails to Execute and the Error Message "java.lang.NoSuchFieldError: SECURITY_SSL_ENCRYPT_ENABLED" Is Displayed? ` - :ref:`Why Submitted Yarn Job Cannot Be Viewed on the Web UI? ` @@ -32,6 +34,7 @@ Job Development what_types_of_spark_jobs_can_be_submitted_in_a_cluster can_i_run_multiple_spark_tasks_at_the_same_time_after_the_minimum_tenant_resources_of_an_mrs_cluster_is_changed_to_0 what_are_the_differences_between_the_client_mode_and_cluster_mode_of_spark_jobs + how_do_i_view_mrs_job_logs 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 launcherjob_job_execution_is_failed_and_the_error_message_jobpropertiesmap_is_null._is_displayed how_do_i_do_if_the_flink_job_status_on_the_mrs_console_is_inconsistent_with_that_on_yarn @@ -39,6 +42,7 @@ Job Development 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 how_do_i_do_if_error_message_java.io.ioexception_connection_reset_by_peer_is_displayed_during_the_execution_of_a_spark_job how_do_i_do_if_error_message_requestid_4971883851071737250_is_displayed_when_a_spark_job_accesses_obs + how_do_i_do_if_the_spark_job_error_unknownscannerexeception_is_reported why_dataartsstudio_occasionally_fail_to_schedule_spark_jobs_and_the_rescheduling_also_fails how_do_i_do_if_a_flink_job_fails_to_execute_and_the_error_message_java.lang.nosuchfielderror_security_ssl_encrypt_enabled_is_displayed why_submitted_yarn_job_cannot_be_viewed_on_the_web_ui diff --git a/umn/source/faq/job_development/what_are_the_differences_between_the_client_mode_and_cluster_mode_of_spark_jobs.rst b/umn/source/faq/job_development/what_are_the_differences_between_the_client_mode_and_cluster_mode_of_spark_jobs.rst index 5411d87..6c5ede4 100644 --- a/umn/source/faq/job_development/what_are_the_differences_between_the_client_mode_and_cluster_mode_of_spark_jobs.rst +++ b/umn/source/faq/job_development/what_are_the_differences_between_the_client_mode_and_cluster_mode_of_spark_jobs.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001392574214.html +:original_name: en-us_topic_0000001145356345.html -.. _en-us_topic_0000001392574214: +.. _en-us_topic_0000001145356345: What Are the Differences Between the Client Mode and Cluster Mode of Spark Jobs? ================================================================================ diff --git a/umn/source/faq/kerberos_usage/how_do_i_access_spark_in_a_cluster_with_kerberos_authentication_enabled.rst b/umn/source/faq/kerberos_usage/how_do_i_access_spark_in_a_cluster_with_kerberos_authentication_enabled.rst index 33ce41e..02f3089 100644 --- a/umn/source/faq/kerberos_usage/how_do_i_access_spark_in_a_cluster_with_kerberos_authentication_enabled.rst +++ b/umn/source/faq/kerberos_usage/how_do_i_access_spark_in_a_cluster_with_kerberos_authentication_enabled.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001442653993.html +:original_name: en-us_topic_0000001152828323.html -.. _en-us_topic_0000001442653993: +.. _en-us_topic_0000001152828323: How Do I Access Spark in a Cluster with Kerberos Authentication Enabled? ======================================================================== diff --git a/umn/source/faq/kerberos_usage/index.rst b/umn/source/faq/kerberos_usage/index.rst index 443c513..e2f5582 100644 --- a/umn/source/faq/kerberos_usage/index.rst +++ b/umn/source/faq/kerberos_usage/index.rst @@ -10,7 +10,7 @@ Kerberos Usage - :ref:`How Do I Deploy the Kerberos Service in a Running Cluster? ` - :ref:`How Do I Access Hive in a Cluster with Kerberos Authentication Enabled? ` - :ref:`How Do I Access Presto in a Cluster with Kerberos Authentication Enabled? ` -- :ref:`How Do I Access Spark in a Cluster with Kerberos Authentication Enabled? ` +- :ref:`How Do I Access Spark in a Cluster with Kerberos Authentication Enabled? ` - :ref:`How Do I Prevent Kerberos Authentication Expiration? ` .. toctree:: diff --git a/umn/source/faq/mrs_overview/how_do_i_enable_different_service_programs_to_use_different_yarn_queues.rst b/umn/source/faq/mrs_overview/how_do_i_enable_different_service_programs_to_use_different_yarn_queues.rst index 795c6a9..1f11bb3 100644 --- a/umn/source/faq/mrs_overview/how_do_i_enable_different_service_programs_to_use_different_yarn_queues.rst +++ b/umn/source/faq/mrs_overview/how_do_i_enable_different_service_programs_to_use_different_yarn_queues.rst @@ -12,9 +12,9 @@ Procedure #. Log in to FusionInsight Manager and choose **Tenant Resources**. -#. In the tenant list on the left, select a parent tenant and click |image1|. On the page for adding a sub-tenant, set attributes for the sub-tenant according to :ref:`Table 1 `. +#. In the tenant list on the left, select a parent tenant and click |image1|. On the page for adding a sub-tenant, set attributes for the sub-tenant according to :ref:`Table 1 `. - .. _mrs_03_1221__en-us_topic_0263899594_tc983b52ccd084798871c7fa2b49856dd: + .. _mrs_03_1221__admin_guide_000119_tc983b52ccd084798871c7fa2b49856dd: .. table:: **Table 1** Sub-tenant parameters @@ -73,15 +73,15 @@ Procedure Roles, computing resources, and storage resources are automatically created when tenants are created. - The new role has permissions on the computing and storage resources. This role and its permissions are automatically controlled by the system and cannot be manually managed by choosing **System** > **Permission** > **Role**. The role name is in the format of *Tenant name*\ \_\ *Cluster ID*. The ID of the first cluster is not displayed by default. - - When using this tenant, create a system user and bind the user to the role of the tenant. + - When using this tenant, create a system user and bind the user to the role of the tenant. For details, see :ref:`Adding a User and Binding the User to a Tenant Role `. - The sub-tenant can further allocate the resources of its parent tenant. The sum of the resource percentages of direct sub-tenants under a parent tenant at each level cannot exceed 100%. The sum of the computing resource percentages of all level-1 tenants cannot exceed 100%. #. Check whether the current tenant needs to be associated with resources of other services. - - If yes, go to :ref:`4 `. - - If no, go to :ref:`5 `. + - If yes, go to :ref:`4 `. + - If no, go to :ref:`5 `. -#. .. _mrs_03_1221__en-us_topic_0263899594_lcdfcd36b99d84c3ba2f290f976ade15b: +#. .. _mrs_03_1221__admin_guide_000119_lcdfcd36b99d84c3ba2f290f976ade15b: Click **Associate Service** to configure other service resources used by the current tenant. @@ -99,8 +99,8 @@ Procedure c. Click **OK**. -#. .. _mrs_03_1221__en-us_topic_0263899594_l93b6a287f2a9444f9b34fcbcc1e595ac: +#. .. _mrs_03_1221__admin_guide_000119_l93b6a287f2a9444f9b34fcbcc1e595ac: Click **OK**. Wait until the system displays a message indicating that the tenant is successfully created. -.. |image1| image:: /_static/images/en-us_image_0000001392734350.png +.. |image1| image:: /_static/images/en-us_image_0263899238.png diff --git a/umn/source/faq/mrs_overview/index.rst b/umn/source/faq/mrs_overview/index.rst index f4ae890..4eb6550 100644 --- a/umn/source/faq/mrs_overview/index.rst +++ b/umn/source/faq/mrs_overview/index.rst @@ -25,10 +25,10 @@ MRS Overview - :ref:`What Are the Solutions for processing 1 Billion Data Records? ` - :ref:`Can I Change the IP address of DBService? ` - :ref:`Can I Clear MRS sudo Logs? ` -- :ref:`Is the Storm Log also limited to 20 GB in MRS cluster 2.1.0? ` -- :ref:`What Is Spark ThriftServer? ` -- :ref:`What Access Protocols Are Supported by Kafka? ` -- :ref:`What Is the Compression Ratio of zstd? ` +- :ref:`Is the Storm Log also limited to 20 GB in MRS cluster 2.1.0? ` +- :ref:`What Is Spark ThriftServer? ` +- :ref:`What Access Protocols Are Supported by Kafka? ` +- :ref:`What Is the Compression Ratio of zstd? ` - :ref:`Why Are the HDFS, YARN, and MapReduce Components Unavailable When an MRS Cluster Is Created? ` - :ref:`Why Is the ZooKeeper Component Unavailable When an MRS Cluster Is Created? ` - :ref:`Which Python Versions Are Supported by Spark Tasks in an MRS 3.1.0 Cluster? ` diff --git a/umn/source/faq/mrs_overview/is_the_storm_log_also_limited_to_20_gb_in_mrs_cluster_2.1.0.rst b/umn/source/faq/mrs_overview/is_the_storm_log_also_limited_to_20_gb_in_mrs_cluster_2.1.0.rst index de9abc1..d172da2 100644 --- a/umn/source/faq/mrs_overview/is_the_storm_log_also_limited_to_20_gb_in_mrs_cluster_2.1.0.rst +++ b/umn/source/faq/mrs_overview/is_the_storm_log_also_limited_to_20_gb_in_mrs_cluster_2.1.0.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001442653893.html +:original_name: en-us_topic_0000001145676237.html -.. _en-us_topic_0000001442653893: +.. _en-us_topic_0000001145676237: Is the Storm Log also limited to 20 GB in MRS cluster 2.1.0? ============================================================ diff --git a/umn/source/faq/mrs_overview/what_access_protocols_are_supported_by_kafka.rst b/umn/source/faq/mrs_overview/what_access_protocols_are_supported_by_kafka.rst index 2a045f2..cff0d2d 100644 --- a/umn/source/faq/mrs_overview/what_access_protocols_are_supported_by_kafka.rst +++ b/umn/source/faq/mrs_overview/what_access_protocols_are_supported_by_kafka.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001442494337.html +:original_name: en-us_topic_0000001098596550.html -.. _en-us_topic_0000001442494337: +.. _en-us_topic_0000001098596550: What Access Protocols Are Supported by Kafka? ============================================= diff --git a/umn/source/faq/mrs_overview/what_is_spark_thriftserver.rst b/umn/source/faq/mrs_overview/what_is_spark_thriftserver.rst index 47973bb..4cf6a96 100644 --- a/umn/source/faq/mrs_overview/what_is_spark_thriftserver.rst +++ b/umn/source/faq/mrs_overview/what_is_spark_thriftserver.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001442773925.html +:original_name: en-us_topic_0000001145596307.html -.. _en-us_topic_0000001442773925: +.. _en-us_topic_0000001145596307: What Is Spark ThriftServer? =========================== diff --git a/umn/source/faq/mrs_overview/what_is_the_compression_ratio_of_zstd.rst b/umn/source/faq/mrs_overview/what_is_the_compression_ratio_of_zstd.rst index fa7312f..55e3abc 100644 --- a/umn/source/faq/mrs_overview/what_is_the_compression_ratio_of_zstd.rst +++ b/umn/source/faq/mrs_overview/what_is_the_compression_ratio_of_zstd.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001392255170.html +:original_name: en-us_topic_0000001145597621.html -.. _en-us_topic_0000001392255170: +.. _en-us_topic_0000001145597621: What Is the Compression Ratio of zstd? ====================================== diff --git a/umn/source/faq/mrs_overview/which_mrs_cluster_version_supports_hive_connection_and_user_synchronization.rst b/umn/source/faq/mrs_overview/which_mrs_cluster_version_supports_hive_connection_and_user_synchronization.rst index 88a776a..c02c32c 100644 --- a/umn/source/faq/mrs_overview/which_mrs_cluster_version_supports_hive_connection_and_user_synchronization.rst +++ b/umn/source/faq/mrs_overview/which_mrs_cluster_version_supports_hive_connection_and_user_synchronization.rst @@ -5,4 +5,4 @@ Which MRS Cluster Version Supports Hive Connection and User Synchronization? ============================================================================ -MRS cluster 2.0.5 or later supports Hive connections on DataLake Governance Center (DGC) and provides the IAM user synchronization function. +MRS 2.0.5 or later supports Hive connections on DataArts Studio and provides the IAM user synchronization function. diff --git a/umn/source/faq/web_page_access/how_do_i_change_the_session_timeout_duration_for_an_open_source_component_web_ui.rst b/umn/source/faq/web_page_access/how_do_i_change_the_session_timeout_duration_for_an_open_source_component_web_ui.rst index 48fc00a..2cf749a 100644 --- a/umn/source/faq/web_page_access/how_do_i_change_the_session_timeout_duration_for_an_open_source_component_web_ui.rst +++ b/umn/source/faq/web_page_access/how_do_i_change_the_session_timeout_duration_for_an_open_source_component_web_ui.rst @@ -20,8 +20,6 @@ Checking Whether the Cluster Supports Session Timeout Duration Adjustment - MRS 3.x and later: Log in to FusionInsight Manager and choose **Cluster** > **Services** > **meta**. On the displayed page, click **Configurations** and select **All Configurations**. Search for the **http.server.session.timeout.secs** configuration item. If this configuration item exists, perform the following steps to modify it. If the configuration item does not exist, the version does not support dynamic adjustment of the session duration. - |image1| - You are advised to set all session timeout durations to the same value. Otherwise, the settings of some parameters may not take effect due to value conflict. Modifying the Timeout Duration on Manager and the Authentication Center Page @@ -101,5 +99,3 @@ Modifying the Timeout Duration for an Open-Source Component Web UI #. Restart the meta service and components on web UI, or restart the cluster during off-peak hours. To prevent service interruption, restart the service during off-peak hours or perform a rolling restart. - -.. |image1| image:: /_static/images/en-us_image_0000001392734334.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12001_audit_log_dumping_failure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12001_audit_log_dumping_failure.rst index 53ff2a1..bb605df 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12001_audit_log_dumping_failure.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12001_audit_log_dumping_failure.rst @@ -140,4 +140,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807597.png +.. |image1| image:: /_static/images/en-us_image_0269383808.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12004_oldap_resource_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12004_oldap_resource_abnormal.rst index 8263387..cd933f5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12004_oldap_resource_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12004_oldap_resource_abnormal.rst @@ -96,4 +96,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767626.png +.. |image1| image:: /_static/images/en-us_image_0269383809.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12005_okerberos_resource_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12005_okerberos_resource_abnormal.rst index 9038b98..ed9dd7f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12005_okerberos_resource_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12005_okerberos_resource_abnormal.rst @@ -89,4 +89,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607838.png +.. |image1| image:: /_static/images/en-us_image_0269383810.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12006_node_fault.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12006_node_fault.rst index dc893d0..3dce09b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12006_node_fault.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12006_node_fault.rst @@ -44,8 +44,7 @@ Services on the node are unavailable. Possible Causes --------------- -- The network is disconnected, the hardware is faulty, or the operating system runs slowly. -- The memory of the NodeAgent process is insufficient. +The network is disconnected, the hardware is faulty, or the operating system runs slowly. Procedure --------- @@ -56,13 +55,9 @@ Procedure #. Log in to the active management node as user **root**. - .. note:: - - If the faulty node is the active management node and fails login, the network of the active management node may be faulty. In this case, go to :ref:`4 `. - #. Run the **ping** *IP address of the faulty host* command to check whether the faulty node is reachable. - - If yes, go to :ref:`12 `. + - If yes, go to :ref:`12 `. - If no, go to :ref:`4 `. #. .. _alm-12006__li61437024165028: @@ -84,7 +79,7 @@ Procedure Contact the hardware administrator to check whether the hardware (CPU or memory) of the node is faulty. - If yes, go to :ref:`7 `. - - If no, go to :ref:`12 `. + - If no, go to :ref:`12 `. #. .. _alm-12006__li15590464165028: @@ -103,7 +98,7 @@ Procedure .. code-block:: - 2017-12-09 04:10:51,000 INFO (floatip) Read from ${BIGDATA_HOME}/om-server_*/om/etc/om/routeSetConf.ini,value is : yes + 2017-12-09 04:10:51,000 INFO (floatip) Read from ${BIGDATA_HOME}/om-server_8.1.0.1/om/etc/om/routeSetConf.ini,value is : yes 2017-12-09 04:10:51,000 INFO (floatip) check wsNetExport : eth0 is up. 2017-12-09 04:10:51,000 INFO (floatip) check omNetExport : eth0 is up. 2017-12-09 04:10:51,000 INFO (floatip) check wsInterface : eRth0:oms, wsFloatIp: XXX.XXX.XXX.XXX. @@ -111,7 +106,7 @@ Procedure 2017-12-09 04:10:51,000 INFO (floatip) check wsFloatIp : XXX.XXX.XXX.XXX is reachable. 2017-12-09 04:10:52,000 INFO (floatip) check omFloatIp : XXX.XXX.XXX.XXX is reachable. - - If yes, go to :ref:`12 `. + - If yes, go to :ref:`12 `. - If no, go to :ref:`9 `. #. .. _alm-12006__li3216108493510: @@ -119,7 +114,7 @@ Procedure Check whether the omNetExport log is printed after the wsNetExport is detected or whether the interval for printing two logs exceeds 10 seconds or longer. - If yes, go to :ref:`10 `. - - If no, go to :ref:`12 `. + - If no, go to :ref:`12 `. #. .. _alm-12006__li1419227193519: @@ -147,40 +142,27 @@ Procedure Feb 11 11:44:44 10-120-205-33 ntpq: nss_ldap: failed to bind to LDAP server ldaps://10.120.205.92:21780: Can't contact LDAP server - If yes, go to :ref:`11 `. - - If no, go to :ref:`14 `. + - If no, go to :ref:`12 `. #. .. _alm-12006__li5998962193529: Check whether the LdapServer node is faulty, for example, the service IP address is unreachable or the network latency is too high. If the fault occurs periodically, locate and eliminate it and run the **top** command to check whether abnormal software exists. -**Check whether the memory of the NodeAgent process is insufficient.** +**Collect the fault information.** -12. .. _alm-12006__li5888111210353: - - Log in to the faulty node as user **root** and run the following command to view the NodeAgent process logs: - - **vi /var/log/Bigdata/nodeagent/scriptlog/agent_gc.log.*.current** - -13. Check whether the log file contains an error indicating that the metaspace size or heap memory size is insufficient. - - - If yes, contact O&M personnel personnel to change the memory size. - - If no, go to :ref:`14 `. - -**Collect fault information.** - -14. .. _alm-12006__li6096449165028: +12. .. _alm-12006__li6096449165028: On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. -15. Select the following nodes from **Services** and click **OK**. +13. Select the following nodes from **Services** and click **OK**. - NodeAgent - Controller - OS -16. Click |image2| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. +14. Click |image2| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. -17. Contact O&M personnel and provide the collected logs. +15. Contact O&M personnel and provide the collected logs. Alarm Clearing -------------- @@ -192,5 +174,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127417.png -.. |image2| image:: /_static/images/en-us_image_0000001532767474.png +.. |image1| image:: /_static/images/en-us_image_0263895827.png +.. |image2| image:: /_static/images/en-us_image_0263895607.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12007_process_fault.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12007_process_fault.rst index 947c2e0..a436f52 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12007_process_fault.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12007_process_fault.rst @@ -140,5 +140,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807817.png -.. |image2| image:: /_static/images/en-us_image_0000001583127509.png +.. |image1| image:: /_static/images/en-us_image_0000001080201158.png +.. |image2| image:: /_static/images/en-us_image_0269383814.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12010_manager_heartbeat_interruption_between_the_active_and_standby_nodes.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12010_manager_heartbeat_interruption_between_the_active_and_standby_nodes.rst index eb64e94..9e00e6a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12010_manager_heartbeat_interruption_between_the_active_and_standby_nodes.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12010_manager_heartbeat_interruption_between_the_active_and_standby_nodes.rst @@ -152,5 +152,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127401.png -.. |image2| image:: /_static/images/en-us_image_0000001532767502.png +.. |image1| image:: /_static/images/en-us_image_0269383815.png +.. |image2| image:: /_static/images/en-us_image_0269383816.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12011_manager_data_synchronization_exception_between_the_active_and_standby_nodes.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12011_manager_data_synchronization_exception_between_the_active_and_standby_nodes.rst index ac6903a..27dd1cd 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12011_manager_data_synchronization_exception_between_the_active_and_standby_nodes.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12011_manager_data_synchronization_exception_between_the_active_and_standby_nodes.rst @@ -191,6 +191,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607938.png -.. |image2| image:: /_static/images/en-us_image_0000001583087593.png -.. |image3| image:: /_static/images/en-us_image_0000001582927829.png +.. |image1| image:: /_static/images/en-us_image_0269383817.png +.. |image2| image:: /_static/images/en-us_image_0000001271157721.png +.. |image3| image:: /_static/images/en-us_image_0269383818.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12012_ntp_service_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12012_ntp_service_is_abnormal.rst deleted file mode 100644 index 9285b05..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12012_ntp_service_is_abnormal.rst +++ /dev/null @@ -1,404 +0,0 @@ -:original_name: ALM-12012.html - -.. _ALM-12012: - -ALM-12012 NTP Service Is Abnormal -================================= - -Description ------------ - -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 service fails to synchronize time for two consecutive times. - -This alarm is generated when the time difference between the NTP service on a node and the NTP service on the active OMS node is greater than or equal to 20s for two consecutive times. This alarm is cleared when the time difference is less than 20s. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -12012 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+-------------------------------------------------------------------+ -| Name | Meaning | -+=============+===================================================================+ -| 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 time on the node is inconsistent with that on other nodes in the cluster. Therefore, some FusionInsight applications on the node may not run properly. - -Possible Causes ---------------- - -- The NTP service on the current node cannot start properly. -- The current node fails to synchronize time with the NTP service on the active OMS node. -- The key value authenticated by the NTP service on the current node is inconsistent with that on the active OMS node. -- The time offset between the node and the NTP service on the active OMS node is large. - -Procedure ---------- - -**Check the NTP service mode of the node.** - -#. .. _alm-12012__li24978126120: - - Log in to the active management node as user **root**, run the **su - omm** command to switch to user **omm**, and run the following command to check the resource status on the active and standby nodes: - - **sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh** - - - If "chrony" is displayed in the **ResName** column of the command output, go to :ref:`2 `. - - If "ntp" is displayed in the **ResName** column, go to :ref:`20 `. - - .. note:: - - If both "chrony" and "ntp" are displayed in the **ResName** column of the command output, the NTP service mode is being switched. Wait for 10 minutes and go to :ref:`1 ` again. If both "chrony" and "ntp" persist, contact O&M personnel personnel. - -**Check whether the chrony service on the node is started properly.** - -2. .. _alm-12012__li565253915220: - - On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. On the page that is displayed, click |image1| in the row containing the alarm, and view the name of the host for which the alarm is generated in **Location**. - -3. Check whether the chronyd process is running on the node where the alarm is generated. Log in to the node for which the alarm is generated as user **root** and run the **ps -ef \| grep** **chronyd \| grep -v grep** command to check whether the command output contains the chronyd process. - - - If yes, go to :ref:`6 `. - - If no, go to :ref:`4 `. - -4. .. _alm-12012__li112931223172310: - - Run the **systemctl chronyd start** command to start the NTP service. (Currently, only CentOS and Red Hat Enterprise Linux 7.0 or later are supported.) - -5. Check whether the alarm is cleared 10 minutes later. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Check whether the current node can synchronize time properly with the chrony service on the active OMS node.** - -6. .. _alm-12012__li128001354104320: - - Check whether the node can synchronize time with the NTP service on the active OMS node based on additional information of the alarm. - - - If yes, go to :ref:`7 `. - - If no, go to :ref:`17 `. - -7. .. _alm-12012__li920311197441: - - Check whether the synchronization with the chrony service on the active OMS node is faulty. - - Log in to the node for which the alarm is generated as user **root** and run the **chronyc sources** command. - - In the command output, if there is an asterisk (``*``) before the IP address of the chrony service on the active OMS node, the synchronization is normal. The command output is as follows: - - .. code-block:: - - MS Name/IP address Stratum Poll Reach LastRx Last sample - =============================================================================== - ^* 10.10.10.162 10 10 377 626 +16us[ +15us] +/- 308us - - In the command output, if there is no asterisk (``*``) before the IP address of the NTP service on the active OMS node, and the value of **Reach** is **0**, the synchronization is abnormal. - - .. code-block:: - - MS Name/IP address Stratum Poll Reach LastRx Last sample - =============================================================================== - ^? 10.1.1.1 0 10 0 - +0ns[ +0ns] +/- 0ns - - - If yes, go to :ref:`8 `. - - If no, go to :ref:`38 `. - -8. .. _alm-12012__li10140131164518: - - The chrony synchronization failure is typically caused by the system firewall. If the firewall can be disabled, disable it. If the firewall cannot be disabled, check the firewall configuration policy and ensure that UDP ports 123 and 323 are not disabled. (For details, see the firewall configuration policy of each system.) - -9. Check whether the alarm is cleared 10 minutes later. - - - If yes, no further action is required. - - If no, go to :ref:`10 `. - -10. .. _alm-12012__li876311455457: - - Log in to the active OMS node as user **root** and run the following command to view the authentication code whose key value index is **1M**: - - In Red Hat Enterprise Linux, run the **cat ${BIGDATA_HOME}/om-server/OMS/workspace/conf/chrony.keys** command. - -11. Run the following command to check whether the key value is the same as that queried in :ref:`10 `: - - In Red Hat Enterprise Linux, run the **diff ${BIGDATA_HOME}/om-server/OMS/workspace/conf/chrony.keys /etc/chrony.keys** command. - - .. note:: - - If the key values are the same, no result is returned after the command is executed. For example: - - .. code-block:: - - host01:~ # cat ${BIGDATA_HOME}/om-server/OMS/workspace/conf/chrony.keys - 1 M sdYbq;o^CzEAWo`. - - If no, go to :ref:`38 `. - -12. .. _alm-12012__li126135154610: - - Run the **cat ${BIGDATA_HOME}/om-server/om/packaged-distributables/ntpKeyFile** command to check whether the key value is the same as that queried in :ref:`10 `. (Compare the key value with that of the authentication key index field **1M** queried in :ref:`10 `.) - - - If yes, go to :ref:`13 `. - - If no, go to :ref:`15 `. - -13. .. _alm-12012__li119741549194615: - - Log in to the faulty node as user **root** and run the **cat /etc/chrony.keys** command in Red Hat Enterprise Linux to check whether the key value is the same as the value queried in :ref:`12 ` (use the key value of the authentication key index field **1M** for comparison). - - - If yes, go to :ref:`38 `. - - If no, go to :ref:`14 `. - -14. .. _alm-12012__li1811911136195: - - Run the **su - omm** command to switch to user **omm**, change the key value of the authentication key index field **1M** in **${NODE_AGENT_HOME}/chrony.keys** to the key value of **ntpKeyFile** in :ref:`12 `, and go to :ref:`16 `. - -15. .. _alm-12012__li12237374714: - - Run the following commands as user **root** or **omm** to change the NTP key value of the active OMS node (change **ntp.keys** to **ntpkeys** in Red Hat Enterprise Linux): - - **cd ${BIGDATA_HOME}/om-server/OMS/workspace/conf** - - **sed -i "`cat chrony.keys \| grep -n '1 M'|awk -F ':' '{print $1}'`d" chrony.keys** - - **echo "1 M \`cat ${BIGDATA_HOME}/om-server/om/packaged-distributables/ntpKeyFile`" >> chrony.keys** - - Check whether the key value of the authentication key index field **1M** in **chrony.keys** is the same as that of **ntpKeyFile**. - - - If yes, go to :ref:`16 `. - - If no, change the key value of the authentication key index field **1M** in **chrony.keys** to the key value of **ntpKeyFile** and go to :ref:`16 `. - -16. .. _alm-12012__li1681623204717: - - After 5 minutes, run the **systemctl chronyd restart** command to restart the chrony service on the active OMS node. After 15 minutes, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`38 `. - -**Check whether the time deviation between the node and the chrony service on the active OMS node is large.** - -17. .. _alm-12012__li14800634174816: - - Check whether the time deviation is large in additional information of the alarm. - - - If yes, go to :ref:`18 `. - - If no, go to :ref:`38 `. - -18. .. _alm-12012__li72571946124812: - - On the **Hosts** tab page, select the host for which the alarm is generated, and choose **More** > **Stop All Instances** to stop all the services on the node. - - If the time on the alarm node is later than that on the chrony service of the active OMS node, adjust the time of the alarm node. After adjusting the time, choose **More** > **Start All Instances** to start the services on the node. - - If the time on the alarm node is earlier than that on the chrony service of the active OMS node, wait until the time deviation is due and adjust the time of the alarm node. After adjusting the time, choose **More** > **Start All Instances** to start the services on the node. - - .. note:: - - If you do not wait, data loss may occur. - -19. After 10 minutes, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`38 `. - -**Check whether the NTP service on the node is started properly.** - -20. .. _alm-12012__li18137932125120: - - On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. On the page that is displayed, click |image2| in the row containing the alarm, and view the name of the host for which the alarm is generated in **Location**. - -21. Check whether the ntpd process is running on the node using the following method. Log in to the alarm node as user **root** and run the **ps -ef \| grep ntpd \| grep -v grep** command to check whether the command output contains the ntpd process. - - - If yes, go to :ref:`24 `. - - If no, go to :ref:`22 `. - -22. .. _alm-12012__li797292017193: - - Run the **service ntp start** command (or the **service ntpd start** command in Red Hat Enterprise Linux) to start the NTP service. - -23. After 10 minutes, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`24 `. - -**Check whether the node can synchronize time properly with the NTP service on the active OMS node.** - -24. .. _alm-12012__li3507541817193: - - Check whether the node can synchronize time with the NTP service on the active OMS node based on additional information of the alarm. - - - If yes, go to :ref:`25 `. - - If no, go to :ref:`35 `. - -25. .. _alm-12012__li3019831317193: - - Check whether the synchronization with the NTP service on the active OMS node is faulty. - - Log in to the alarm node as user **root** and run the **ntpq -np** command. - - If an asterisk (``*``) exists before the IP address of the NTP service on the active OMS node in the command output, the synchronization is in normal state. The command output is as follows: - - .. code-block:: - - remote refid st t when poll reach delay offset jitter - ============================================================================== - *10.10.10.162 .LOCL. 1 u 1 16 377 0.270 -1.562 0.014 - - If there is no asterisk (``*``) before the IP address of the NTP service on the active OMS node, as shown in the following command output, and the value of **refid** is **.INIT.**, the synchronization is abnormal. - - .. code-block:: - - remote refid st t when poll reach delay offset jitter - ============================================================================== - 10.10.10.162 .INIT. 1 u 1 16 377 0.270 -1.562 0.014 - - - If yes, go to :ref:`26 `. - - If no, go to :ref:`38 `. - -26. .. _alm-12012__li14622157181719: - - The NTP synchronization failure is typically caused by the system firewall. If the firewall can be disabled, run the **iptables -F** command to disable it. If the firewall cannot be disabled, run the **iptables -L** command to check the firewall configuration policy and ensure that the UDP port 123 is not disabled. (For details, see the firewall configuration policy of each system.) - -27. After 10 minutes, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`28 `. - -28. .. _alm-12012__li50636830155013: - - Log in to the active OMS node as user **root** and run the following command to view the authentication key index field **1M**: - - In SUSE Linux, run the **cat ${BIGDATA_HOME}/om-server/OMS/workspace/conf/ntp.keys** command. - - In Red Hat Enterprise Linux or EulerOS, run the **cat ${BIGDATA_HOME}/om-server/OMS/workspace/conf/ntpkeys** command. - -29. Run the following command to check whether the key value is the same as that queried in :ref:`28 `: - - In SUSE Linux, run the **diff ${BIGDATA_HOME}/om-server/OMS/workspace/conf/ntp.keys /etc/ntp.keys** command. - - In Red Hat Enterprise Linux or EulerOS, run the **diff ${BIGDATA_HOME}/om-server/OMS/workspace/conf/ntpkeys /etc/ntp/ntpkeys** command. - - .. note:: - - If the key values are the same, no result is returned after the command is executed. For example: - - .. code-block:: - - host01:~ # cat ${BIGDATA_HOME}/om-server/OMS/workspace/conf/ntp.keys - 1 M sdYbq;o^CzEAWo`. - - If no, go to :ref:`38 `. - -30. .. _alm-12012__li58889465155013: - - Run the **cat ${BIGDATA_HOME}/om-server/om/packaged-distributables/ntpKeyFile** command to check whether the key value is the same as that queried in :ref:`28 `. (Compare the key value with that of the authentication key index field **1M** queried in :ref:`28 `.) - - - If yes, go to :ref:`31 `. - - If no, go to :ref:`33 `. - -31. .. _alm-12012__li44851587155013: - - Log in to the faulty node as user **root** and run the **cat /etc/ntp.keys** command in SUSE Linux (or the **cat /etc/ntp/ntpkeys** command in Red Hat Enterprise Linux) to check whether the key value is the same as the value queried in :ref:`30 ` (use the key value of the authentication key index field **1M** for comparison). - - - If yes, go to :ref:`38 `. - - If no, go to :ref:`32 `. - -32. .. _alm-12012__li817715392262: - - Run the **su - omm** command to switch to user **omm**, change the key value of the authentication key index field **1M** in **${NODE_AGENT_HOME}/ntp.keys** (**${NODE_AGENT_HOME}/ntpkeys** in Red Hat Enterprise Linux) to the key value of **ntpKeyFile** in :ref:`30 `, and go to :ref:`34 `. - -33. .. _alm-12012__li22747884155013: - - Run the following commands as user **root** or **omm** to change the NTP key value of the active OMS node (change **ntp.keys** to **ntpkeys** in Red Hat Enterprise Linux): - - **cd ${BIGDATA_HOME}/om-server/OMS/workspace/conf** - - **sed -i "`cat ntp.keys \| grep -n '1 M'|awk -F ':' '{print $1}'`d" ntp.keys** - - **echo "1 M \`cat ${BIGDATA_HOME}/om-server/om/packaged-distributables/ntpKeyFile`" >>ntp.keys** - - Check whether the key value of the authentication key index field **1M** in **ntp.keys** is the same as that of **ntpKeyFile**. - - - If yes, go to :ref:`34 `. - - If no, change the key value of the authentication key index field **1M** in **ntp.keys** to the key value of **ntpKeyFile** and go to :ref:`34 `. - -34. .. _alm-12012__li30141735155013: - - After 5 minutes, run the **service ntp restart** command to restart the NTP service on the active OMS node. After 15 minutes, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`38 `. - -**Check whether the time deviation between the node and the NTP service on the active OMS node is large.** - -35. .. _alm-12012__li766317817193: - - Check whether the time deviation is large in additional information of the alarm. - - - If yes, go to :ref:`36 `. - - If no, go to :ref:`38 `. - -36. .. _alm-12012__li5505704717193: - - On the **Hosts** tab page, select the host for which the alarm is generated, and choose **More** > **Stop All Instances** to stop all the services on the node. - - If the time on the alarm node is later than that on the NTP service of the active OMS node, adjust the time of the alarm node. After adjusting the time, choose **More** > **Start All Instances** to start the services on the node. - - If the time on the alarm node is earlier than that on the NTP service of the active OMS node, wait until the time deviation is due and adjust the time of the alarm node. After adjusting the time, choose **More** > **Start All Instances** to start the services on the node. - - .. note:: - - If you do not wait, data loss may occur. - -37. After 10 minutes, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`38 `. - -**Collect the fault information.** - -38. .. _alm-12012__li3559109817193: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -39. In the **Services** area, select **NodeAgent** and **OmmServer**, and click **OK**. Expand the **Hosts** dialog box and select the alarm node and the active OMS node. - -40. Click |image3| 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**. - -41. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583087389.png -.. |image2| image:: /_static/images/en-us_image_0000001532448250.png -.. |image3| image:: /_static/images/en-us_image_0000001532767474.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12014_partition_lost.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12014_partition_lost.rst index f20bca2..6147693 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12014_partition_lost.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12014_partition_lost.rst @@ -109,4 +109,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767638.png +.. |image1| image:: /_static/images/en-us_image_0269383822.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12015_partition_filesystem_readonly.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12015_partition_filesystem_readonly.rst index 5889059..646f348 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12015_partition_filesystem_readonly.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12015_partition_filesystem_readonly.rst @@ -68,4 +68,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807717.png +.. |image1| image:: /_static/images/en-us_image_0269383823.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12016_cpu_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12016_cpu_usage_exceeds_the_threshold.rst index 72665f2..93f1c45 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12016_cpu_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12016_cpu_usage_exceeds_the_threshold.rst @@ -64,7 +64,7 @@ Procedure .. _alm-12016__fig42676420173938: - .. figure:: /_static/images/en-us_image_0000001583087533.png + .. figure:: /_static/images/en-us_image_0269383824.png :alt: **Figure 1** Setting alarm smoothing times **Figure 1** Setting alarm smoothing times @@ -73,7 +73,7 @@ Procedure .. _alm-12016__fig30961038173938: - .. figure:: /_static/images/en-us_image_0000001583127513.png + .. figure:: /_static/images/en-us_image_0000001440977805.png :alt: **Figure 2** Setting an alarm threshold **Figure 2** Setting an alarm threshold @@ -120,4 +120,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927773.png +.. |image1| image:: /_static/images/en-us_image_0269383826.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12017_insufficient_disk_capacity.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12017_insufficient_disk_capacity.rst index 2a78924..c95adf4 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12017_insufficient_disk_capacity.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12017_insufficient_disk_capacity.rst @@ -67,7 +67,7 @@ Procedure .. _alm-12017__fig6063892885745: - .. figure:: /_static/images/en-us_image_0000001582927861.png + .. figure:: /_static/images/en-us_image_0000001440977873.png :alt: **Figure 1** Setting an alarm threshold **Figure 1** Setting an alarm threshold @@ -153,5 +153,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807909.png -.. |image2| image:: /_static/images/en-us_image_0000001583127613.png +.. |image1| image:: /_static/images/en-us_image_0269383828.png +.. |image2| image:: /_static/images/en-us_image_0269383829.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst index 48325ec..daa5a9f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst @@ -113,5 +113,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927669.png -.. |image2| image:: /_static/images/en-us_image_0000001583127413.png +.. |image1| image:: /_static/images/en-us_image_0269383830.png +.. |image2| image:: /_static/images/en-us_image_0269383831.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12027_host_pid_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12027_host_pid_usage_exceeds_the_threshold.rst index 9763293..ea8570a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12027_host_pid_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12027_host_pid_usage_exceeds_the_threshold.rst @@ -97,5 +97,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607906.png -.. |image2| image:: /_static/images/en-us_image_0000001582927797.png +.. |image1| image:: /_static/images/en-us_image_0269383832.png +.. |image2| image:: /_static/images/en-us_image_0269383834.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_and_z_state_on_a_host_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_on_a_host_exceeds_the_threshold.rst similarity index 74% rename from umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_and_z_state_on_a_host_exceeds_the_threshold.rst rename to umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_on_a_host_exceeds_the_threshold.rst index b67582b..57b8add 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_and_z_state_on_a_host_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_on_a_host_exceeds_the_threshold.rst @@ -2,19 +2,15 @@ .. _ALM-12028: -ALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold -======================================================================================== +ALM-12028 Number of Processes in the D State on a Host Exceeds the Threshold +============================================================================ Description ----------- -The system checks the number of processes in the D stateand Z state of user **omm** on the host every 30 seconds and compares the actual number with the threshold. The number of processes in the D state and Z state on the host has a default threshold range. This alarm is generated when the number of processes exceeds the threshold. +The system checks the number of processes in the D state of user **omm** on the host every 30 seconds and compares the actual number with the threshold. The number of processes in the D state on the host has a default threshold range. This alarm is generated when the number of processes exceeds the threshold. -This alarm is cleared when the **Trigger Count** is **1** and the total number of processes in the D state and Z state of user **omm** on the host does not exceed the threshold. This alarm is cleared when the **Trigger Count** is greater than **1** and the total number of processes in the D state and Z state of user **omm** on the host is less than or equal to 90% of the threshold. - -.. note:: - - The function of checking the number of processes in the Z state on the host applies to MRS 3.2.0 or later. +This alarm is cleared when the **Trigger Count** is **1** and the total number of processes in the D state of user **omm** on the host does not exceed the threshold. This alarm is cleared when the **Trigger Count** is greater than **1** and the total number of processes in the D state of user **omm** on the host is less than or equal to 90% of the threshold. Attribute --------- @@ -55,13 +51,13 @@ The host responds slowly to I/O (disk I/O and network I/O) requests and some pro Procedure --------- -**Check the processes in the D state** **and Z state.** +**Check the processes in the D state.** #. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click |image1| to view the IP address of the host for which the alarm is generated. #. Log in to the host for which the alarm is generated as user **root**. () Then run the **su - omm** command to switch to user **omm**. -#. Run the following command as user **omm** to view the PID of the process that is in the D state and Z state: +#. Run the following command as user **omm** to view the PID of the process that is in the D state: **ps -elf \| grep -v "\\[thread_checkio\\]" \| awk 'NR!=1 {print $2, $3, $4}' \| grep omm \| awk -F' ' '{print $1, $3}' \| grep -E "Z|D" \| awk '{print $2}'** @@ -85,7 +81,7 @@ Procedure 7. .. _alm-12028__li4177630091049: - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. + On FusionInsight Manager, choose **O&M** > **Log** > **Download**. 8. Select **OMS** for **Service** and click **OK**. @@ -103,5 +99,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448262.png -.. |image2| image:: /_static/images/en-us_image_0000001583087581.png +.. |image1| image:: /_static/images/en-us_image_0263895749.png +.. |image2| image:: /_static/images/en-us_image_0263895796.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12033_slow_disk_fault.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12033_slow_disk_fault.rst index 860527c..b2fd158 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12033_slow_disk_fault.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12033_slow_disk_fault.rst @@ -10,27 +10,19 @@ Description - For HDDs, the alarm is triggered when any of the following conditions is met: - - The system runs the **iostat** command every 3 seconds, and detects that the **svctm** value exceeds 1000 ms for 7 consecutive periods within 30 seconds. - - The system runs the **iostat** command every 3 seconds, and detects that more than 50% of I/Os take more than 150 ms within 300s. + - The system runs the **iostat** command every 3 seconds, and detects that the **svctm** value exceeds 1000 ms for 10 consecutive periods within 30 seconds. + - The system runs the **iostat** command every 3 seconds, and detects that more than 60% of I/O exceeds 150 ms within 300 seconds. - For SSDs, the alarm is triggered when any of the following conditions is met: - The system runs the **iostat** command every 3 seconds, and detects that the **svctm** value exceeds 1000 ms for 10 consecutive periods within 30 seconds. - - The system runs the **iostat** command every 3 seconds, and detects that more than 60% of I/Os take more than 20 ms within 300 seconds. + - The system runs the **iostat** command every 3 seconds, and detects that more than 60% of I/O exceeds 20 ms within 300 seconds. This alarm is automatically cleared when the preceding conditions have not been met for 15 minutes. .. note:: - The **svctm** value can be obtained as follows: - - - MRS 3.1.0: - - Run the **iostat -x -t** command in the OS. - - |image1| - - - Versions later than MRS 3.1.0: + The formula for calculating **svctm** is as follows: svctm = (tot_ticks_new - tot_ticks_old)/(rd_ios_new + wr_ios_new - rd_ios_old - wr_ios_old) @@ -40,7 +32,7 @@ This alarm is automatically cleared when the preceding conditions have not been The system runs the **cat /proc/diskstats** command every 3 seconds to collect data. For example: - |image2| + |image1| In these two commands: @@ -58,7 +50,7 @@ Attribute ======== ============== ========== Alarm ID Alarm Severity Auto Clear ======== ============== ========== -12033 Minor Yes +12033 Major Yes ======== ============== ========== Parameters @@ -119,7 +111,7 @@ Procedure Run the **lsblk** command to check whether the mapping between the value of **DiskName** and the disk has been created. - |image3| + |image2| - If yes, go to :ref:`7 `. . - If no, go to :ref:`22 `. @@ -177,7 +169,7 @@ Procedure Check the **Command/Feature_name** column in the command output. If **READ SECTOR(S)** or **WRITE SECTOR(S)** is displayed, the disk has bad sectors. If other errors occur, the disk circuit board is faulty. Both errors indicate that the disk is abnormal and needs to be replaced. - If "No Errors Logged" is displayed, no error log exists. You can trigger the disk SMART self-check. + If "No Errors Logged" is displayed, no error log exists. You can perform step 9 to trigger the disk SMART self-check. - If yes, go to :ref:`11 `. - If no, go to :ref:`18 `. @@ -238,9 +230,9 @@ Procedure **smartctl -d sat+megaraid,2 -l error -H /dev/sda** - Check the **Command/Feature_name** column in the command output. If **READ SECTOR(S)** or **WRITE SECTOR(S)** is displayed, the disk has bad sectors. If other errors occur, the disk circuit board is faulty. Both errors indicate that the disk is abnormal and needs to be replaced. + Check the **Command/Featrue_name** column in the command output. If **READ SECTOR(S)** or **WRITE SECTOR(S)** is displayed, the disk has bad sectors. If other errors occur, the disk circuit board is faulty. Both errors indicate that the disk is abnormal and needs to be replaced. - If "No Errors Logged" is displayed, no error log exists. You can trigger the disk SMART self-check. + If "No Errors Logged" is displayed, no error log exists. You can perform step 9 to trigger the disk SMART self-check. - If yes, go to :ref:`15 `. - If no, go to :ref:`18 `. @@ -294,7 +286,7 @@ Procedure 23. Select **OMS** for **Service** and click **OK**. -24. Click |image4| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. +24. Click |image3| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. 25. Contact O&M personnel and provide the collected logs. @@ -308,7 +300,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087321.png -.. |image2| image:: /_static/images/en-us_image_0000001582807613.png -.. |image3| image:: /_static/images/en-us_image_0000001583127305.jpg -.. |image4| image:: /_static/images/en-us_image_0000001532927338.png +.. |image1| image:: /_static/images/en-us_image_0000001410107141.png +.. |image2| image:: /_static/images/en-us_image_0263895818.jpg +.. |image3| image:: /_static/images/en-us_image_0263895453.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12034_periodical_backup_failure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12034_periodical_backup_failure.rst index f857352..26b126e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12034_periodical_backup_failure.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12034_periodical_backup_failure.rst @@ -122,6 +122,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807645.png -.. |image2| image:: /_static/images/en-us_image_0000001532927370.png -.. |image3| image:: /_static/images/en-us_image_0000001532448214.png +.. |image1| image:: /_static/images/en-us_image_0269383843.png +.. |image2| image:: /_static/images/en-us_image_0000001127057881.png +.. |image3| image:: /_static/images/en-us_image_0269383844.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12035_unknown_data_status_after_recovery_task_failure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12035_unknown_data_status_after_recovery_task_failure.rst index 9322e2f..795ad1d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12035_unknown_data_status_after_recovery_task_failure.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12035_unknown_data_status_after_recovery_task_failure.rst @@ -102,5 +102,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448366.png -.. |image2| image:: /_static/images/en-us_image_0000001583127489.png +.. |image1| image:: /_static/images/en-us_image_0269383845.png +.. |image2| image:: /_static/images/en-us_image_0269383846.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12037_ntp_server_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12037_ntp_server_abnormal.rst deleted file mode 100644 index 6c5e09b..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12037_ntp_server_abnormal.rst +++ /dev/null @@ -1,165 +0,0 @@ -:original_name: ALM-12037.html - -.. _ALM-12037: - -ALM-12037 NTP Server Abnormal -============================= - -Description ------------ - -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 alarm is cleared when the NTP server recovers. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -12037 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+------------------------------------------------------------------------------+ -| Name | Meaning | -+=============+==============================================================================+ -| 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 IP address of the NTP server for which the alarm is generated. | -+-------------+------------------------------------------------------------------------------+ - -Impact on the System --------------------- - -The NTP server configured on the active OMS node is abnormal. In this case, the active OMS node cannot synchronize time with the NTP server and a time offset may be generated in the cluster. - -Possible Causes ---------------- - -- The NTP server network is abnormal. -- The NTP server authentication fails. -- The NTP server time cannot be obtained. -- The time obtained from the NTP server is not continuously updated. - -Procedure ---------- - -**Check the NTP server network.** - -#. On the FusionInsight Manager portal, click **O&M > Alarm > Alarms** and click |image1| in the row where the alarm is located. - -#. View the alarm additional information to check whether the NTP server fails to be pinged. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`4 `. - -#. .. _alm-12037__li601372919523: - - Contact the network administrator to check the network configuration and ensure that the network between the NTP server and the active OMS node is normal. Then, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`4 `. - -**Check whether the NTP server authentication fails.** - -4. .. _alm-12037__li392824159523: - - Log in to the active OMS node as user **root**. - -5. .. _alm-12037__li24978126120: - - Run the following command to check the status of the resources on the active and standby nodes: - - **su - omm** - - **sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh** - - - If "chrony" is displayed in the **ResName** column of the command output, go to :ref:`6 `. - - If "ntp" is displayed in the **ResName** column, go to :ref:`7 `. - - .. note:: - - If both "chrony" and "ntp" are displayed in the **ResName** column of the command output, the NTP service mode is being switched. Wait for 10 minutes and perform :ref:`5 ` again. If both "chrony" and "ntp" still exist in the **ResName** column, contact O&M personnel. - -6. .. _alm-12037__li179951620123417: - - Run the command **chronyc sources** to check whether the NTP server authentication fails. - - If the value of **Reach** for chrony is **0**, the connection or authentication fails. - - - If yes, go to :ref:`12 `. - - If no, go to :ref:`8 `. - -7. .. _alm-12037__li650965649523: - - Run the command **ntpq -np** to check whether the NTP server authentication fails. - - If **refid** of the NTP server is **.AUTH.**, the authentication fails. - - - If yes, go to :ref:`12 `. - - If no, go to :ref:`8 `. - -**Check whether the time can be obtained from the NTP server.** - -8. .. _alm-12037__li282496949523: - - View the alarm additional information to check whether the time can be obtained from the NTP server. - - - If yes, go to :ref:`9 `. - - If no, go to :ref:`10 `. - -9. .. _alm-12037__li549211539523: - - Contact the provider of the NTP server to rectify the NTP server fault. After the NTP server is normal, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`10 `. - -**Check whether the time obtained from the NTP server is not continuously updated.** - -10. .. _alm-12037__li301460699523: - - View the alarm additional information to check whether the time obtained from the NTP server is not continuously updated. - - - If yes, go to :ref:`11 `. - - If no, go to :ref:`12 `. - -11. .. _alm-12037__li251290419523: - - Contact the provider of the NTP server to rectify the NTP server fault. After the NTP server is normal, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`12 `. - -**Collect fault information.** - -12. .. _alm-12037__li654599509523: - - On the FusionInsight Manager, choose **O&M** > **Log > Download**. - -13. Select **NodeAgent** and **OmmServer** from the **Service** and click **OK**. - -14. Click |image2| 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**. - -15. Contact the O&M personnel and send the collected log information. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532607750.png -.. |image2| image:: /_static/images/en-us_image_0000001582927645.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12038_monitoring_indicator_dumping_failure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12038_monitoring_indicator_dumping_failure.rst index fd80790..894d56b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12038_monitoring_indicator_dumping_failure.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12038_monitoring_indicator_dumping_failure.rst @@ -147,4 +147,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927442.png +.. |image1| image:: /_static/images/en-us_image_0269383850.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12039_active_standby_oms_databases_not_synchronized.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12039_active_standby_oms_databases_not_synchronized.rst index b225668..667a497 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12039_active_standby_oms_databases_not_synchronized.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12039_active_standby_oms_databases_not_synchronized.rst @@ -149,5 +149,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927757.png -.. |image2| image:: /_static/images/en-us_image_0000001532448378.png +.. |image1| image:: /_static/images/en-us_image_0269383851.png +.. |image2| image:: /_static/images/en-us_image_0269383852.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12040_insufficient_system_entropy.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12040_insufficient_system_entropy.rst index fe2cd1e..054c525 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12040_insufficient_system_entropy.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12040_insufficient_system_entropy.rst @@ -8,14 +8,6 @@ ALM-12040 Insufficient System Entropy Description ----------- -MRS 3.2.0 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, this alarm is generated. If either is configured, the system continues to check the entropy. If the entropy is less than 100 for five consecutive times, this alarm is generated. - -This alarm is cleared when rng-tools or haveged has been installed and enabled on the target node and the entropy of the OS is greater than or equal to 100 in at least one of five entropy checks. - -MRS 3.1.2 or earlier: - The system checks the entropy for five consecutive times at 00:00 every day. Specifically, the system checks whether rng-tools or haveged has been enabled and correctly configured. If neither is configured, the system continues to check the entropy. If the entropy is less than 100 for five consecutive times, this alarm is reported. This alarm is cleared when the system detects that the true random number mode has been configured, the random number parameters have been configured in the pseudo-random number mode, or neither mode is configured but the entropy of the OS is greater than or equal to 100 in at least one of five entropy checks. @@ -174,4 +166,4 @@ Alarm Clearing This alarm is automatically cleared after the fault is rectified. -.. |image1| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12041_incorrect_permission_on_key_files.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12041_incorrect_permission_on_key_files.rst index fb4659f..813ba8d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12041_incorrect_permission_on_key_files.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12041_incorrect_permission_on_key_files.rst @@ -104,5 +104,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927558.jpg -.. |image2| image:: /_static/images/en-us_image_0000001532607890.png +.. |image1| image:: /_static/images/en-us_image_0269383855.jpg +.. |image2| image:: /_static/images/en-us_image_0269383856.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12042_incorrect_configuration_of_key_files.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12042_incorrect_configuration_of_key_files.rst index bcff1b7..22335c3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12042_incorrect_configuration_of_key_files.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12042_incorrect_configuration_of_key_files.rst @@ -120,4 +120,4 @@ Related Information #. The value of **MaxStartups** must be greater than or equal to 1000. #. At least one of the **PasswordAuthentication** and **ChallengeResponseAuthentication** parameters must be left blank or at least one of the parameters be set to **yes**. -.. |image1| image:: /_static/images/en-us_image_0000001532927502.png +.. |image1| image:: /_static/images/en-us_image_0269383857.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12045_read_packet_dropped_rate_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12045_read_packet_dropped_rate_exceeds_the_threshold.rst index 2ec0347..31db5a2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12045_read_packet_dropped_rate_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12045_read_packet_dropped_rate_exceeds_the_threshold.rst @@ -238,7 +238,7 @@ Procedure .. _alm-12045__fig52784093112834: - .. figure:: /_static/images/en-us_image_0000001582927657.png + .. figure:: /_static/images/en-us_image_0000001390618884.png :alt: **Figure 1** Configuring the alarm threshold **Figure 1** Configuring the alarm threshold @@ -288,8 +288,8 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087417.png -.. |image2| image:: /_static/images/en-us_image_0000001532767498.png -.. |image3| image:: /_static/images/en-us_image_0000001532607762.png -.. |image4| image:: /_static/images/en-us_image_0000001532448274.png -.. |image5| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895776.png +.. |image2| image:: /_static/images/en-us_image_0000001390459688.png +.. |image3| image:: /_static/images/en-us_image_0263895526.png +.. |image4| image:: /_static/images/en-us_image_0263895376.png +.. |image5| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12046_write_packet_dropped_rate_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12046_write_packet_dropped_rate_exceeds_the_threshold.rst index 0c221d2..f9d5649 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12046_write_packet_dropped_rate_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12046_write_packet_dropped_rate_exceeds_the_threshold.rst @@ -71,7 +71,7 @@ Procedure .. _alm-12046__fig153215311450: - .. figure:: /_static/images/en-us_image_0000001582807837.png + .. figure:: /_static/images/en-us_image_0000001390459444.png :alt: **Figure 1** Configuring the alarm threshold **Figure 1** Configuring the alarm threshold @@ -121,4 +121,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12047_read_packet_error_rate_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12047_read_packet_error_rate_exceeds_the_threshold.rst index 365bf04..19061f3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12047_read_packet_error_rate_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12047_read_packet_error_rate_exceeds_the_threshold.rst @@ -71,7 +71,7 @@ Procedure .. _alm-12047__fig35859496144325: - .. figure:: /_static/images/en-us_image_0000001532767698.png + .. figure:: /_static/images/en-us_image_0000001441218249.png :alt: **Figure 1** Configuring the alarm threshold **Figure 1** Configuring the alarm threshold @@ -121,4 +121,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12048_write_packet_error_rate_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12048_write_packet_error_rate_exceeds_the_threshold.rst index 947027d..2b6b206 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12048_write_packet_error_rate_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12048_write_packet_error_rate_exceeds_the_threshold.rst @@ -71,7 +71,7 @@ Procedure .. _alm-12048__fig53221363145357: - .. figure:: /_static/images/en-us_image_0000001532767658.png + .. figure:: /_static/images/en-us_image_0000001390619040.png :alt: **Figure 1** Configuring the alarm threshold **Figure 1** Configuring the alarm threshold @@ -121,4 +121,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12049_network_read_throughput_rate_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12049_network_read_throughput_rate_exceeds_the_threshold.rst index 9d25be6..2149848 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12049_network_read_throughput_rate_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12049_network_read_throughput_rate_exceeds_the_threshold.rst @@ -71,7 +71,7 @@ Procedure .. _alm-12049__fig566375315131: - .. figure:: /_static/images/en-us_image_0000001532448486.png + .. figure:: /_static/images/en-us_image_0000001440858201.png :alt: **Figure 1** Setting alarm thresholds **Figure 1** Setting alarm thresholds @@ -126,5 +126,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927869.png -.. |image2| image:: /_static/images/en-us_image_0000001582807921.png +.. |image1| image:: /_static/images/en-us_image_0269383872.png +.. |image2| image:: /_static/images/en-us_image_0269383873.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12050_network_write_throughput_rate_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12050_network_write_throughput_rate_exceeds_the_threshold.rst index 2567eaa..be268a6 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12050_network_write_throughput_rate_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12050_network_write_throughput_rate_exceeds_the_threshold.rst @@ -71,7 +71,7 @@ Procedure .. _alm-12050__fig2514972915653: - .. figure:: /_static/images/en-us_image_0000001532448282.png + .. figure:: /_static/images/en-us_image_0000001440978021.png :alt: **Figure 1** Setting alarm thresholds **Figure 1** Setting alarm thresholds @@ -126,5 +126,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767506.png -.. |image2| image:: /_static/images/en-us_image_0000001583087425.png +.. |image1| image:: /_static/images/en-us_image_0269383875.png +.. |image2| image:: /_static/images/en-us_image_0269383876.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12051_disk_inode_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12051_disk_inode_usage_exceeds_the_threshold.rst index 0bbc100..45258d8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12051_disk_inode_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12051_disk_inode_usage_exceeds_the_threshold.rst @@ -124,5 +124,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127373.png -.. |image2| image:: /_static/images/en-us_image_0000001532927410.png +.. |image1| image:: /_static/images/en-us_image_0269383877.png +.. |image2| image:: /_static/images/en-us_image_0269383878.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12052_tcp_temporary_port_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12052_tcp_temporary_port_usage_exceeds_the_threshold.rst index d5be695..45ba715 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12052_tcp_temporary_port_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12052_tcp_temporary_port_usage_exceeds_the_threshold.rst @@ -136,5 +136,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607970.png -.. |image2| image:: /_static/images/en-us_image_0000001582807913.png +.. |image1| image:: /_static/images/en-us_image_0269383880.png +.. |image2| image:: /_static/images/en-us_image_0269383881.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12053_host_file_handle_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12053_host_file_handle_usage_exceeds_the_threshold.rst index 0e28978..b258969 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12053_host_file_handle_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12053_host_file_handle_usage_exceeds_the_threshold.rst @@ -147,6 +147,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927418.png -.. |image2| image:: /_static/images/en-us_image_0000001532607746.png -.. |image3| image:: /_static/images/en-us_image_0000001582927641.png +.. |image1| image:: /_static/images/en-us_image_0269383882.png +.. |image2| image:: /_static/images/en-us_image_0269383883.png +.. |image3| image:: /_static/images/en-us_image_0269383884.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12054_invalid_certificate_file.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12054_invalid_certificate_file.rst index 892a103..38521ab 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12054_invalid_certificate_file.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12054_invalid_certificate_file.rst @@ -10,13 +10,7 @@ Description 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 invalid. -This alarm is cleared when a valid certificate is imported and the alarm detection mechanism is triggered on the next hour. - -.. note:: - - For MRS 3.2.0 or later, the certificate file is checked at the beginning of each hour. - - For versions earlier than MRS 3.2.0, the certificate file is checked on 23:00 every day. +This alarm is cleared when a valid certificate is imported. Attribute --------- @@ -66,7 +60,7 @@ Procedure - If **CA Certificate** is displayed in the additional alarm information, log in to the active OMS management node as user **omm** and go to :ref:`2 `. - If **HA root Certificate** is displayed in the additional information, view **Location** to obtain the name of the host involved in this alarm. Then, log in to the host as user **omm** and go to :ref:`3 `. - If **HA server Certificate** is displayed in the additional information, view **Location** to obtain the name of the host involved in this alarm. Then, log in to the host as user **omm** and go to :ref:`4 `. - - If **Certificate has expired** is displayed in the additional information, view **Location** to obtain the name of the host for which the alarm is generated. Then, log in to the host as user **omm** and perform :ref:`2 ` to :ref:`4 ` in sequence to check whether the certificates have expired. If these certificates have not expired, check whether other certificates have been imported. If yes, import the certificate files again. + - If **Certificate has expired** is displayed in the additional information, view **Location** to obtain the host name of the node for which the alarm is generated. Then, log in to the host as user **omm** and perform :ref:`2 ` to :ref:`4 ` to check whether the certificates have expired. If these certificates have not expired, check whether other certificates have been imported. If yes, import the certificate files again. **Check the validity period of the certificate files in the system.** @@ -154,5 +148,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448262.png -.. |image2| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895749.png +.. |image2| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12055_the_certificate_file_is_about_to_expire.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12055_the_certificate_file_is_about_to_expire.rst index 9c3dbe6..7e7f210 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12055_the_certificate_file_is_about_to_expire.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12055_the_certificate_file_is_about_to_expire.rst @@ -10,13 +10,7 @@ Description 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 certificate that is not about to expire is imported and the alarm detection mechanism is triggered on the next hour. - -.. note:: - - For MRS 3.2.0 or later, the certificate file is checked at the beginning of each hour. - - For versions earlier than MRS 3.2.0, the certificate file is checked on 23:00 every day. +This alarm is cleared when a certificate that is not about to expire is imported. Attribute --------- @@ -153,5 +147,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448262.png -.. |image2| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895749.png +.. |image2| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12057_metadata_not_configured_with_the_task_to_periodically_back_up_data_to_a_third-party_server.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12057_metadata_not_configured_with_the_task_to_periodically_back_up_data_to_a_third-party_server.rst index 83b0c36..3211f81 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12057_metadata_not_configured_with_the_task_to_periodically_back_up_data_to_a_third-party_server.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12057_metadata_not_configured_with_the_task_to_periodically_back_up_data_to_a_third-party_server.rst @@ -80,5 +80,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927570.png -.. |image2| image:: /_static/images/en-us_image_0000001583087553.png +.. |image1| image:: /_static/images/en-us_image_0269383889.png +.. |image2| image:: /_static/images/en-us_image_0269383890.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12061_process_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12061_process_usage_exceeds_the_threshold.rst index 7a983c9..119cbd5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12061_process_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12061_process_usage_exceeds_the_threshold.rst @@ -68,7 +68,7 @@ Procedure .. _alm-12061__fig437414238216: - .. figure:: /_static/images/en-us_image_0000001583127621.png + .. figure:: /_static/images/en-us_image_0000001440858217.png :alt: **Figure 1** Setting an alarm threshold **Figure 1** Setting an alarm threshold @@ -137,4 +137,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927646.png +.. |image1| image:: /_static/images/en-us_image_0269383906.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12062_oms_parameter_configurations_mismatch_with_the_cluster_scale.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12062_oms_parameter_configurations_mismatch_with_the_cluster_scale.rst index 75360de..f1aac84 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12062_oms_parameter_configurations_mismatch_with_the_cluster_scale.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12062_oms_parameter_configurations_mismatch_with_the_cluster_scale.rst @@ -126,4 +126,4 @@ Related Information - OMS is automatically restarted during the configuration update process. - Clusters with similar quantities of nodes have same Manager configurations. For example, when the number of nodes is changed from 100 to 101, no configuration item needs to be updated. -.. |image1| image:: /_static/images/en-us_image_0000001532607874.png +.. |image1| image:: /_static/images/en-us_image_0269383907.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12063_unavailable_disk.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12063_unavailable_disk.rst index 6c79cc8..3612a84 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12063_unavailable_disk.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12063_unavailable_disk.rst @@ -103,4 +103,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087405.png +.. |image1| image:: /_static/images/en-us_image_0269383908.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12064_host_random_port_range_conflicts_with_cluster_used_port.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12064_host_random_port_range_conflicts_with_cluster_used_port.rst index d14c345..14fa277 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12064_host_random_port_range_conflicts_with_cluster_used_port.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12064_host_random_port_range_conflicts_with_cluster_used_port.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767522.png +.. |image1| image:: /_static/images/en-us_image_0269383909.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12066_trust_relationships_between_nodes_become_invalid.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12066_trust_relationships_between_nodes_become_invalid.rst index 703e0df..566a6f8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12066_trust_relationships_between_nodes_become_invalid.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12066_trust_relationships_between_nodes_become_invalid.rst @@ -148,8 +148,8 @@ Perform the following steps to handle abnormal trust relationships between nodes #. If the **/home** directory of user **omm** is deleted, contact MRS support personnel for assistance. -.. |image1| image:: /_static/images/en-us_image_0000001532448306.png -.. |image2| image:: /_static/images/en-us_image_0000001583087445.png -.. |image3| image:: /_static/images/en-us_image_0000001582927685.png -.. |image4| image:: /_static/images/en-us_image_0000001532767530.png -.. |image5| image:: /_static/images/en-us_image_0000001582807737.png +.. |image1| image:: /_static/images/en-us_image_0263895789.png +.. |image2| image:: /_static/images/en-us_image_0263895540.png +.. |image3| image:: /_static/images/en-us_image_0000001226576418.png +.. |image4| image:: /_static/images/en-us_image_0000001227056330.png +.. |image5| image:: /_static/images/en-us_image_0000001271536445.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12067_tomcat_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12067_tomcat_resource_is_abnormal.rst index 463d5d8..1bf8852 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12067_tomcat_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12067_tomcat_resource_is_abnormal.rst @@ -85,5 +85,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127457.png -.. |image2| image:: /_static/images/en-us_image_0000001532767558.png +.. |image1| image:: /_static/images/en-us_image_0263895412.png +.. |image2| image:: /_static/images/en-us_image_0263895407.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12068_acs_resource_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12068_acs_resource_exception.rst index 6b5a15a..8c244ff 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12068_acs_resource_exception.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12068_acs_resource_exception.rst @@ -94,5 +94,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927805.png -.. |image2| image:: /_static/images/en-us_image_0000001532607914.png +.. |image1| image:: /_static/images/en-us_image_0263895733.png +.. |image2| image:: /_static/images/en-us_image_0263895594.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12069_aos_resource_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12069_aos_resource_exception.rst index cedf9bf..340a8d1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12069_aos_resource_exception.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12069_aos_resource_exception.rst @@ -94,5 +94,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448286.png -.. |image2| image:: /_static/images/en-us_image_0000001582927665.png +.. |image1| image:: /_static/images/en-us_image_0263895369.png +.. |image2| image:: /_static/images/en-us_image_0263895883.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12070_controller_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12070_controller_resource_is_abnormal.rst index 30080bd..10928f9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12070_controller_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12070_controller_resource_is_abnormal.rst @@ -94,4 +94,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927629.png +.. |image1| image:: /_static/images/en-us_image_0269383915.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12071_httpd_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12071_httpd_resource_is_abnormal.rst index 982e479..74c61bd 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12071_httpd_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12071_httpd_resource_is_abnormal.rst @@ -96,4 +96,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927741.png +.. |image1| image:: /_static/images/en-us_image_0269383916.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12072_floatip_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12072_floatip_resource_is_abnormal.rst index 5d4e8a6..3fed9d1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12072_floatip_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12072_floatip_resource_is_abnormal.rst @@ -113,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807857.png +.. |image1| image:: /_static/images/en-us_image_0269383917.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12073_cep_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12073_cep_resource_is_abnormal.rst index 79f94d1..578cc8a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12073_cep_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12073_cep_resource_is_abnormal.rst @@ -94,4 +94,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927546.png +.. |image1| image:: /_static/images/en-us_image_0269383918.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12074_fms_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12074_fms_resource_is_abnormal.rst index f850103..4f28c4c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12074_fms_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12074_fms_resource_is_abnormal.rst @@ -94,4 +94,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767442.png +.. |image1| image:: /_static/images/en-us_image_0269383919.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12075_pms_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12075_pms_resource_is_abnormal.rst index a044d60..9007b51 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12075_pms_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12075_pms_resource_is_abnormal.rst @@ -94,4 +94,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607658.png +.. |image1| image:: /_static/images/en-us_image_0269383920.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12076_gaussdb_resource_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12076_gaussdb_resource_is_abnormal.rst index 9cf1f89..5e62eee 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12076_gaussdb_resource_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12076_gaussdb_resource_is_abnormal.rst @@ -129,5 +129,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087397.jpg -.. |image2| image:: /_static/images/en-us_image_0000001532607742.png +.. |image1| image:: /_static/images/en-us_image_0269383921.jpg +.. |image2| image:: /_static/images/en-us_image_0269383922.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12077_user_omm_expired.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12077_user_omm_expired.rst index 214c2ab..c71367a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12077_user_omm_expired.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12077_user_omm_expired.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807821.png +.. |image1| image:: /_static/images/en-us_image_0269383923.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12078_password_of_user_omm_expired.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12078_password_of_user_omm_expired.rst index 2f629d6..a7a224c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12078_password_of_user_omm_expired.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12078_password_of_user_omm_expired.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448218.png +.. |image1| image:: /_static/images/en-us_image_0269383924.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12079_user_omm_is_about_to_expire.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12079_user_omm_is_about_to_expire.rst index dd5fe39..7445459 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12079_user_omm_is_about_to_expire.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12079_user_omm_is_about_to_expire.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448438.png +.. |image1| image:: /_static/images/en-us_image_0269383925.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12080_password_of_user_omm_is_about_to_expire.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12080_password_of_user_omm_is_about_to_expire.rst index 63ef409..834c862 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12080_password_of_user_omm_is_about_to_expire.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12080_password_of_user_omm_is_about_to_expire.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927781.png +.. |image1| image:: /_static/images/en-us_image_0269383926.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12081user_ommdba_expired.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12081user_ommdba_expired.rst index 46a546d..fe78349 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12081user_ommdba_expired.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12081user_ommdba_expired.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807877.png +.. |image1| image:: /_static/images/en-us_image_0269383927.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12082_user_ommdba_is_about_to_expire.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12082_user_ommdba_is_about_to_expire.rst index d8dc6ec..a9b10f6 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12082_user_ommdba_is_about_to_expire.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12082_user_ommdba_is_about_to_expire.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767714.png +.. |image1| image:: /_static/images/en-us_image_0269383928.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12083_password_of_user_ommdba_is_about_to_expire.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12083_password_of_user_ommdba_is_about_to_expire.rst index 71df2ba..038e22d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12083_password_of_user_ommdba_is_about_to_expire.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12083_password_of_user_ommdba_is_about_to_expire.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607974.png +.. |image1| image:: /_static/images/en-us_image_0269383929.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12084_password_of_user_ommdba_expired.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12084_password_of_user_ommdba_expired.rst index 49cf0a8..0c9c170 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12084_password_of_user_ommdba_expired.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12084_password_of_user_ommdba_expired.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087541.png +.. |image1| image:: /_static/images/en-us_image_0269383930.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12085_service_audit_log_dump_failure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12085_service_audit_log_dump_failure.rst index 4117cc1..31bb67a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12085_service_audit_log_dump_failure.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12085_service_audit_log_dump_failure.rst @@ -151,4 +151,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767510.png +.. |image1| image:: /_static/images/en-us_image_0269383932.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12087_system_is_in_the_upgrade_observation_period.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12087_system_is_in_the_upgrade_observation_period.rst index 224fd4a..486330b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12087_system_is_in_the_upgrade_observation_period.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12087_system_is_in_the_upgrade_observation_period.rst @@ -69,7 +69,7 @@ Procedure .. _alm-12087__fig1299312444469: - .. figure:: /_static/images/en-us_image_0000001532767554.png + .. figure:: /_static/images/en-us_image_0269383933.png :alt: **Figure 1** Cluster information **Figure 1** Cluster information @@ -101,4 +101,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927490.png +.. |image1| image:: /_static/images/en-us_image_0269383934.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12089_inter-node_network_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12089_inter-node_network_is_abnormal.rst index 0f97af3..5b197f4 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12089_inter-node_network_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12089_inter-node_network_is_abnormal.rst @@ -108,4 +108,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127553.png +.. |image1| image:: /_static/images/en-us_image_0269383936.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12101_az_unhealthy.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12101_az_unhealthy.rst index 5ee441e..1d1a81c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12101_az_unhealthy.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12101_az_unhealthy.rst @@ -16,7 +16,7 @@ Attribute ======== ============== ========== Alarm ID Alarm Severity Auto Clear ======== ============== ========== -12101 Critical Yes +12101 Major Yes ======== ============== ========== Parameters diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12102_az_ha_component_is_not_deployed_based_on_dr_requirements.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12102_az_ha_component_is_not_deployed_based_on_dr_requirements.rst index b9c8a12..c8bc528 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12102_az_ha_component_is_not_deployed_based_on_dr_requirements.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12102_az_ha_component_is_not_deployed_based_on_dr_requirements.rst @@ -65,4 +65,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127297.png +.. |image1| image:: /_static/images/en-us_image_0000001085773316.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12103_executor_resource_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12103_executor_resource_exception.rst deleted file mode 100644 index f691472..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12103_executor_resource_exception.rst +++ /dev/null @@ -1,90 +0,0 @@ -:original_name: ALM-12103.html - -.. _ALM-12103: - -ALM-12103 Executor Resource Exception -===================================== - -Description ------------ - -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. - -This alarm is cleared when the Executor resources are normal. - -**Resource Type** of Executor is **Single-active**. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new Executor resources have been enabled on the new active Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby Manager switchover. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -12103 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+-------------------------------------------------------------------+ -| Name | Meaning | -+=============+===================================================================+ -| 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 active/standby Manager switchover occurs. -- The Executor process keeps restarting. As a result, the cluster page may fail to be accessed. - -Possible Causes ---------------- - -The Executor process is abnormal. - -Procedure ---------- - -**Check whether the Executor process is abnormal.** - -#. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click |image1| to view the name of the host for which the alarm is generated. - -#. Log in to the host for which the alarm is generated as user **root**. - -#. Run the **su - omm** command to switch to user **omm**. - -#. Run the **sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh** command to check whether the status of the Executor resources managed by the HA is normal. In the single-node system, the Executor resource is in the normal state. In the dual-node system, the Executor resource is in the normal state on the active node and in the stopped state on the standby node. - - - If yes, go to :ref:`7 `. - - If no, go to :ref:`5 `. - -#. .. _alm-12103__li139657016249: - - Run the **vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/executor.log** command to check whether the Executor resource log of HA contains the keyword **ERROR**. If yes, analyze the log to locate the resource exception cause and fix the exception. - -#. After 5 minutes, check whether this alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`7 `. - -**Collect the fault information.** - -7. .. _alm-12103__li6152360163635: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -8. In the **Services** area, select **Controller** and **OmmServer**, and click **OK**. - -9. Click |image2| 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**. - -10. Contact O&M personnel and provide the collected logs. - -.. |image1| image:: /_static/images/en-us_image_0000001582927809.png -.. |image2| image:: /_static/images/en-us_image_0000001582807861.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12104_abnormal_knox_resources.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12104_abnormal_knox_resources.rst deleted file mode 100644 index 320e8bd..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12104_abnormal_knox_resources.rst +++ /dev/null @@ -1,86 +0,0 @@ -:original_name: ALM-12104.html - -.. _ALM-12104: - -ALM-12104 Abnormal Knox Resources -================================= - -Description ------------ - -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 alarm is cleared when HA detects that the Knox resources are normal. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -12104 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+-------------------------------------------------------------------+ -| Name | Meaning | -+=============+===================================================================+ -| 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 --------------------- - -Requests sent by upper-layer services by using Knox cannot be properly processed. - -Possible Causes ---------------- - -The Knox process is abnormal. - -Procedure ---------- - -Check whether the Knox process is normal. - -#. Log in to FusionInsight Manager. In the alarm list, locate the row that contains the alarm and view the name of the host for which the alarm is generated. - -#. Use PuTTY to log in to the host for which the alarm is generated as user **root**. - -#. Run the **su - omm** command to switch to user **omm**. - -#. Run the **sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh** command to check whether the status of the Knox resources managed by HA is normal. If the status is normal, the Knox resources are normal. Otherwise, the Knox resources are abnormal. - - - If yes, go to :ref:`7 `. - - If no, go to :ref:`5 `. - -#. .. _alm-12104__li193959911619: - - Run the **vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/knox.log** command to check whether the Knox resource log of HA contains the keyword **ERROR**. If yes, analyze the log to locate the resource exception cause and fix the exception. - -#. After 5 minutes, check whether this alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`7 `. - -Collect the fault information. - -7. .. _alm-12104__li3394198162: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -8. In the **Services** area, select **Controller** and **OmmServer**, and click **OK**. - -9. Click |image1| 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**. - -10. Contact O&M personnel and provide the collected logs. - -.. |image1| image:: /_static/images/en-us_image_0000001532767542.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12110_failed_to_get_ecs_temporary_ak_sk.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12110_failed_to_get_ecs_temporary_ak_sk.rst index afd895c..9965bb6 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12110_failed_to_get_ecs_temporary_ak_sk.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12110_failed_to_get_ecs_temporary_ak_sk.rst @@ -83,4 +83,4 @@ Procedure Contact O&M personnel. -.. |image1| image:: /_static/images/en-us_image_0000001582807757.png +.. |image1| image:: /_static/images/en-us_image_0000001216164294.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12172_failed_to_report_metrics_to_cloud_eye.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12172_failed_to_report_metrics_to_cloud_eye.rst deleted file mode 100644 index ff64ebd..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12172_failed_to_report_metrics_to_cloud_eye.rst +++ /dev/null @@ -1,69 +0,0 @@ -:original_name: ALM-12172.html - -.. _ALM-12172: - -ALM-12172 Failed to Report Metrics to Cloud Eye -=============================================== - -Description ------------ - -After metric sharing is enabled for a cluster, the Controller periodically collects cluster metrics and reports them to Cloud Eye. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -12172 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+-------------------------------------------------------------------+ -| Name | Meaning | -+=============+===================================================================+ -| 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 --------------------- - -MRS monitoring metrics are unavailable on Cloud Eye. - -Possible Causes ---------------- - -- Failed to call Cloud Eye APIs due to insufficient permissions. -- Failed to report data to Cloud Eye due to network problems. -- Failed to report data to Cloud Eye due to internal errors. - -Procedure ---------- - -#. On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. On the page that is displayed, click |image1| in the row containing the alarm and view the additional information of the alarm. -#. Rectify the fault based on the following scenarios: - - - If "Call CES to send metrics fail. Permission exception" is displayed in the additional information, the token of the resource tenant is invalid. Restart the Controller and obtain the token again. - - If "Call CES to send metrics fail. Request CES error code xxx" is displayed in the additional information, an error occurs in the request to Cloud Eye. Check the network connectivity and authentication information. - - If "Call CES to send metrics fail. CES internal error code xxx" is displayed in the additional information, the Cloud Eye service encounters an internal error and is unavailable. Contact O&M personnel and send collected fault logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532607954.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12180_suspended_disk_i_o.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12180_suspended_disk_i_o.rst index c19d301..0bf555b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12180_suspended_disk_i_o.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12180_suspended_disk_i_o.rst @@ -15,7 +15,7 @@ Description - For SSDs, the alarm is triggered when any of the following conditions is met: - - The system collects data every 3 seconds, and detects that the **svctm** value exceeds 2s for 10 consecutive periods within 30 seconds. + - The system collects data every 3 seconds, and detects that the **svctm** value exceeds 3s for 10 consecutive periods within 30 seconds. - The system collects data every 3 seconds, and detects that the **avgqu-sz** value is greater than 0, the IOPS or bandwidth is 0, and the **ioutil** value is greater than **99%** for 10 consecutive periods within 30 seconds. This alarm is automatically cleared when the preceding conditions have not been met for 90s. @@ -30,23 +30,14 @@ This alarm is automatically cleared when the preceding conditions have not been Parameters are as follows: - **avgqu-sz** indicates the disk queue depth. + - **avgqu-sz** indicates the disk queue depth. + - The sum of **r/s** and **w/s** is the IOPS. + - The sum of **rkB/s** and **wkB/s** is the bandwidth. + - **%util** is the **ioutil** value. - The sum of **r/s** and **w/s** is the IOPS. + - The formula for calculating **svctm** is as follows: - The sum of **rkB/s** and **wkB/s** is the bandwidth. - - **%util** is the **ioutil** value. - - - MRS 3.1.0: - - Run the **iostat -x -t** command in the OS. - - |image2| - - - Calculate **svctm** as follows in versions later than MRS 3.1.0: - - svctm = (tot_ticks_new - tot_ticks_old)/(rd_ios_new + wr_ios_new - rd_ios_old - wr_ios_old) + svctm = (tot_ticks_new - tot_ticks_old) / (rd_ios_new + wr_ios_new - rd_ios_old - wr_ios_old) If **rd_ios_new + wr_ios_new - rd_ios_old - wr_ios_old** is **0**, then **svctm** is **0**. @@ -54,7 +45,7 @@ This alarm is automatically cleared when the preceding conditions have not been The system runs the **cat /proc/diskstats** command every 3 seconds to collect data. For example: - |image3| + |image2| In these two commands: @@ -64,7 +55,7 @@ This alarm is automatically cleared when the preceding conditions have not been In this case, the value of **svctm** is as follows: - (19571460 - 19569526)/(1101553 + 28747977 - 1101553 - 28744856) = 0.6197 + (19571460 - 19569526) / (1101553 + 28747977 - 1101553 - 28744856) = 0.6197 Attribute --------- @@ -123,7 +114,7 @@ Procedure 6. Select **OMS** for **Service** and click **OK**. -7. Click |image4| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. +7. Click |image3| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. 8. Contact O&M personnel and provide the collected logs. @@ -137,7 +128,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807637.png -.. |image2| image:: /_static/images/en-us_image_0000001532607690.png -.. |image3| image:: /_static/images/en-us_image_0000001583087345.png -.. |image4| image:: /_static/images/en-us_image_0000001582927585.png +.. |image1| image:: /_static/images/en-us_image_0000001375901064.png +.. |image2| image:: /_static/images/en-us_image_0000001426500589.png +.. |image3| image:: /_static/images/en-us_image_0000001405224197.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12190_number_of_knox_connections_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12190_number_of_knox_connections_exceeds_the_threshold.rst deleted file mode 100644 index 7ca3973..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-12190_number_of_knox_connections_exceeds_the_threshold.rst +++ /dev/null @@ -1,90 +0,0 @@ -:original_name: ALM-12190.html - -.. _ALM-12190: - -ALM-12190 Number of Knox Connections Exceeds the Threshold -========================================================== - -Description ------------ - -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 threshold (90% by default). This alarm is automatically cleared when the number of connections to a topology falls below the threshold. - -.. note:: - - This alarm applies to clusters of MRS 3.1.0 or later. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -12190 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+-------------------------------------------------------------------+ -| Name | Meaning | -+=============+===================================================================+ -| 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. | -+-------------+-------------------------------------------------------------------+ -| Topology | Specifies the Knox topology for which the alarm is generated. | -+-------------+-------------------------------------------------------------------+ - -Impact on the System --------------------- - -The topology may reach the upper limit of connections and fail to forward requests, adversely affecting the MRS functions. - -Possible Causes ---------------- - -Hue or Manager is too frequently used, but the default maximum number of Knox connections is small. - -Procedure ---------- - -#. Log in to active and standby OMS nodes as user **root**, respectively. - -#. Add the following configuration to the **gateway-site.xml** file on the active and standby OMS nodes to increase the number of thread pools: - - **vi /opt/knox/conf/gateway-site.xml** - - .. code-block:: - - - gateway.httpclient.maxConnections - 64 - - -#. Log in to the active OMS node as user **omm** and run the following command to restart the Knox process: - - **sh /opt/knox/bin/restart-knox.sh** - -#. After 5 minutes, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -#. .. _alm-12190__li1980615424815: - - Contact O&M personnel to rectify the fault. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13000_zookeeper_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13000_zookeeper_service_unavailable.rst index c8b993c..02c0595 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13000_zookeeper_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13000_zookeeper_service_unavailable.rst @@ -197,4 +197,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807793.png +.. |image1| image:: /_static/images/en-us_image_0269383940.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13001_available_zookeeper_connections_are_insufficient.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13001_available_zookeeper_connections_are_insufficient.rst index 183fa39..fcf4000 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13001_available_zookeeper_connections_are_insufficient.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13001_available_zookeeper_connections_are_insufficient.rst @@ -136,4 +136,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927785.png +.. |image1| image:: /_static/images/en-us_image_0269383942.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13002_zookeeper_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13002_zookeeper_direct_memory_usage_exceeds_the_threshold.rst index bbf3807..75f4eb9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13002_zookeeper_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13002_zookeeper_direct_memory_usage_exceeds_the_threshold.rst @@ -109,4 +109,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807869.png +.. |image1| image:: /_static/images/en-us_image_0269383943.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13003_gc_duration_of_the_zookeeper_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13003_gc_duration_of_the_zookeeper_process_exceeds_the_threshold.rst index 2f0b068..90a90c9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13003_gc_duration_of_the_zookeeper_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13003_gc_duration_of_the_zookeeper_process_exceeds_the_threshold.rst @@ -103,4 +103,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13004_zookeeper_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13004_zookeeper_heap_memory_usage_exceeds_the_threshold.rst index b2e0176..46f0be3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13004_zookeeper_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13004_zookeeper_heap_memory_usage_exceeds_the_threshold.rst @@ -98,4 +98,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127253.png +.. |image1| image:: /_static/images/en-us_image_0269383945.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13005_failed_to_set_the_quota_of_top_directories_of_zookeeper_components.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13005_failed_to_set_the_quota_of_top_directories_of_zookeeper_components.rst index 9a10ba3..1bcde5a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13005_failed_to_set_the_quota_of_top_directories_of_zookeeper_components.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13005_failed_to_set_the_quota_of_top_directories_of_zookeeper_components.rst @@ -113,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927422.png +.. |image1| image:: /_static/images/en-us_image_0269383946.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13006_znode_number_or_capacity_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13006_znode_number_or_capacity_exceeds_the_threshold.rst index 7d12cdf..61fadf1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13006_znode_number_or_capacity_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13006_znode_number_or_capacity_exceeds_the_threshold.rst @@ -93,6 +93,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807801.gif -.. |image2| image:: /_static/images/en-us_image_0000001582927749.gif -.. |image3| image:: /_static/images/en-us_image_0000001583087513.png +.. |image1| image:: /_static/images/en-us_image_0000001239732331.gif +.. |image2| image:: /_static/images/en-us_image_0000001239292351.gif +.. |image3| image:: /_static/images/en-us_image_0269383949.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13007_available_zookeeper_client_connections_are_insufficient.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13007_available_zookeeper_client_connections_are_insufficient.rst index bb79d08..29c9548 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13007_available_zookeeper_client_connections_are_insufficient.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13007_available_zookeeper_client_connections_are_insufficient.rst @@ -97,5 +97,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767466.gif -.. |image2| image:: /_static/images/en-us_image_0000001532927402.png +.. |image1| image:: /_static/images/en-us_image_0269383950.gif +.. |image2| image:: /_static/images/en-us_image_0269383952.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13008_zookeeper_znode_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13008_zookeeper_znode_usage_exceeds_the_threshold.rst index 450c7bb..7f2fce7 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13008_zookeeper_znode_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13008_zookeeper_znode_usage_exceeds_the_threshold.rst @@ -94,4 +94,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807765.png +.. |image1| image:: /_static/images/en-us_image_0269383953.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13009_zookeeper_znode_capacity_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13009_zookeeper_znode_capacity_usage_exceeds_the_threshold.rst index 1d81a7a..88157fd 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13009_zookeeper_znode_capacity_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13009_zookeeper_znode_capacity_usage_exceeds_the_threshold.rst @@ -125,4 +125,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127345.png +.. |image1| image:: /_static/images/en-us_image_0263895683.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13010_znode_usage_of_a_directory_with_quota_configured_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13010_znode_usage_of_a_directory_with_quota_configured_exceeds_the_threshold.rst index 1148d3d..870aa9b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13010_znode_usage_of_a_directory_with_quota_configured_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-13010_znode_usage_of_a_directory_with_quota_configured_exceeds_the_threshold.rst @@ -56,14 +56,14 @@ Procedure #. Choose **Cluster** > *Name of the desired cluster* > **Services** > **ZooKeeper** and click **Resource**. In **Used Resources (By Second-Level Znode)**, check whether a large amount of data is written into the top Znode. - - If yes, go to :ref:`3 `. + - If yes, go to :ref:`4 `. - If no, go to :ref:`5 `. -#. .. _alm-13010__li19446131612914: +#. Log in to FusionInsight Manager, choose **O&M > Alarm > Alarms**, select Location from the drop-down list box next to **ALM-13010 Znode Usage of a Directory with Quota Configured Exceeds the Threshold**, and obtain the Znode path in ServiceDirectory. - Log in to FusionInsight Manager, choose **O&M > Alarm > Alarms**, select Location from the drop-down list box next to **ALM-13010 Znode Usage of a Directory with Quota Configured Exceeds the Threshold**, and obtain the Znode path in ServiceDirectory. +#. .. _alm-13010__li1298122393514: -#. Log in to the ZooKeeper client as a cluster user and delete unwanted data in the Znode for which the alarm is generated. + Log in to the ZooKeeper client as a cluster user and delete unwanted data in the Znode for which the alarm is generated. #. .. _alm-13010__li598192363510: @@ -100,4 +100,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087329.png +.. |image1| image:: /_static/images/en-us_image_0269383956.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14000_hdfs_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14000_hdfs_service_unavailable.rst index 570b387..27c665a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14000_hdfs_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14000_hdfs_service_unavailable.rst @@ -116,4 +116,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927342.png +.. |image1| image:: /_static/images/en-us_image_0269383957.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14001_hdfs_disk_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14001_hdfs_disk_usage_exceeds_the_threshold.rst index 6cbf1f5..843b81d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14001_hdfs_disk_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14001_hdfs_disk_usage_exceeds_the_threshold.rst @@ -126,4 +126,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927434.png +.. |image1| image:: /_static/images/en-us_image_0269383958.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14002_datanode_disk_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14002_datanode_disk_usage_exceeds_the_threshold.rst index 9529020..fe7de35 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14002_datanode_disk_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14002_datanode_disk_usage_exceeds_the_threshold.rst @@ -129,4 +129,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0263895382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14003_number_of_lost_hdfs_blocks_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14003_number_of_lost_hdfs_blocks_exceeds_the_threshold.rst index 6d0b6e7..cdb2301 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14003_number_of_lost_hdfs_blocks_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14003_number_of_lost_hdfs_blocks_exceeds_the_threshold.rst @@ -45,7 +45,7 @@ Parameters Impact on the System -------------------- -Data stored in HDFS is lost. HDFS may enter the security mode and cannot provide write services. Lost block data cannot be restored. +Data stored in HDFS is lost. HDFS may enter the safe mode and cannot provide write services. Lost block data cannot be restored. Possible Causes --------------- @@ -159,4 +159,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807649.png +.. |image1| image:: /_static/images/en-us_image_0269383960.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14006_number_of_hdfs_files_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14006_number_of_hdfs_files_exceeds_the_threshold.rst index 2bc009c..2bfea31 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14006_number_of_hdfs_files_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14006_number_of_hdfs_files_exceeds_the_threshold.rst @@ -136,4 +136,4 @@ The number of NameNode files is proportional to the used memory size of the Name | 300,000,000 | -Xms164G -Xmx164G -XX:NewSize=12G -XX:MaxNewSize=12G | +------------------------+------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001532927350.png +.. |image1| image:: /_static/images/en-us_image_0269383961.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14007_namenode_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14007_namenode_heap_memory_usage_exceeds_the_threshold.rst index 81c26aa..22b5150 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14007_namenode_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14007_namenode_heap_memory_usage_exceeds_the_threshold.rst @@ -140,4 +140,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607958.png +.. |image1| image:: /_static/images/en-us_image_0269383962.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14008_datanode_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14008_datanode_heap_memory_usage_exceeds_the_threshold.rst index 070c9c8..bd3d676 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14008_datanode_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14008_datanode_heap_memory_usage_exceeds_the_threshold.rst @@ -133,4 +133,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607878.png +.. |image1| image:: /_static/images/en-us_image_0269383963.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14009_number_of_dead_datanodes_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14009_number_of_dead_datanodes_exceeds_the_threshold.rst index 94b4d21..5d1038a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14009_number_of_dead_datanodes_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14009_number_of_dead_datanodes_exceeds_the_threshold.rst @@ -188,4 +188,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767590.png +.. |image1| image:: /_static/images/en-us_image_0269383964.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14010_nameservice_service_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14010_nameservice_service_is_abnormal.rst index bacdcab..0f040b3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14010_nameservice_service_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14010_nameservice_service_is_abnormal.rst @@ -205,4 +205,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927713.png +.. |image1| image:: /_static/images/en-us_image_0263895680.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14011_datanode_data_directory_is_not_configured_properly.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14011_datanode_data_directory_is_not_configured_properly.rst index 5d68806..b8af616 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14011_datanode_data_directory_is_not_configured_properly.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14011_datanode_data_directory_is_not_configured_properly.rst @@ -188,4 +188,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087537.png +.. |image1| image:: /_static/images/en-us_image_0269383966.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14012_journalnode_is_out_of_synchronization.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14012_journalnode_is_out_of_synchronization.rst index b6279e7..82a2cc3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14012_journalnode_is_out_of_synchronization.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14012_journalnode_is_out_of_synchronization.rst @@ -147,4 +147,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607650.png +.. |image1| image:: /_static/images/en-us_image_0269383967.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14013_failed_to_update_the_namenode_fsimage_file.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14013_failed_to_update_the_namenode_fsimage_file.rst index 133c550..0dac258 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14013_failed_to_update_the_namenode_fsimage_file.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14013_failed_to_update_the_namenode_fsimage_file.rst @@ -225,4 +225,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927789.png +.. |image1| image:: /_static/images/en-us_image_0269383968.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14014_namenode_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14014_namenode_gc_time_exceeds_the_threshold.rst index 4546bc7..f000d82 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14014_namenode_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14014_namenode_gc_time_exceeds_the_threshold.rst @@ -106,4 +106,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927705.png +.. |image1| image:: /_static/images/en-us_image_0269383969.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14015_datanode_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14015_datanode_gc_time_exceeds_the_threshold.rst index 22958d8..2eaaf03 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14015_datanode_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14015_datanode_gc_time_exceeds_the_threshold.rst @@ -102,4 +102,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767406.png +.. |image1| image:: /_static/images/en-us_image_0269383970.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14016_datanode_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14016_datanode_direct_memory_usage_exceeds_the_threshold.rst index 0f13a34..99acc99 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14016_datanode_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14016_datanode_direct_memory_usage_exceeds_the_threshold.rst @@ -130,4 +130,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927713.png +.. |image1| image:: /_static/images/en-us_image_0263895680.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14017_namenode_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14017_namenode_direct_memory_usage_exceeds_the_threshold.rst index 1735dea..b84b0c2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14017_namenode_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14017_namenode_direct_memory_usage_exceeds_the_threshold.rst @@ -109,4 +109,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927522.png +.. |image1| image:: /_static/images/en-us_image_0269383972.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14018_namenode_non-heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14018_namenode_non-heap_memory_usage_exceeds_the_threshold.rst index cd9a7b7..b0b8f71 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14018_namenode_non-heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14018_namenode_non-heap_memory_usage_exceeds_the_threshold.rst @@ -142,4 +142,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087625.png +.. |image1| image:: /_static/images/en-us_image_0269417342.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14019_datanode_non-heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14019_datanode_non-heap_memory_usage_exceeds_the_threshold.rst index 74cd297..7e22851 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14019_datanode_non-heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14019_datanode_non-heap_memory_usage_exceeds_the_threshold.rst @@ -138,4 +138,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607902.png +.. |image1| image:: /_static/images/en-us_image_0269417343.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14020_number_of_entries_in_the_hdfs_directory_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14020_number_of_entries_in_the_hdfs_directory_exceeds_the_threshold.rst index 6631798..4aa0768 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14020_number_of_entries_in_the_hdfs_directory_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14020_number_of_entries_in_the_hdfs_directory_exceeds_the_threshold.rst @@ -131,4 +131,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807729.png +.. |image1| image:: /_static/images/en-us_image_0269417344.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14021_namenode_average_rpc_processing_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14021_namenode_average_rpc_processing_time_exceeds_the_threshold.rst index 6f27d64..95e06b1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14021_namenode_average_rpc_processing_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14021_namenode_average_rpc_processing_time_exceeds_the_threshold.rst @@ -162,4 +162,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807617.png +.. |image1| image:: /_static/images/en-us_image_0269417365.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14022_namenode_average_rpc_queuing_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14022_namenode_average_rpc_queuing_time_exceeds_the_threshold.rst index 02b7003..3a20569 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14022_namenode_average_rpc_queuing_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14022_namenode_average_rpc_queuing_time_exceeds_the_threshold.rst @@ -186,5 +186,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807777.png -.. |image2| image:: /_static/images/en-us_image_0000001532767570.png +.. |image1| image:: /_static/images/en-us_image_0269417366.png +.. |image2| image:: /_static/images/en-us_image_0269417367.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14023_percentage_of_total_reserved_disk_space_for_replicas_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14023_percentage_of_total_reserved_disk_space_for_replicas_exceeds_the_threshold.rst index dd7817a..5bcb99f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14023_percentage_of_total_reserved_disk_space_for_replicas_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14023_percentage_of_total_reserved_disk_space_for_replicas_exceeds_the_threshold.rst @@ -125,4 +125,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448202.png +.. |image1| image:: /_static/images/en-us_image_0269417368.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14024_tenant_space_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14024_tenant_space_usage_exceeds_the_threshold.rst index cbd888b..98a1024 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14024_tenant_space_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14024_tenant_space_usage_exceeds_the_threshold.rst @@ -114,4 +114,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127441.png +.. |image1| image:: /_static/images/en-us_image_0269417369.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14025_tenant_file_object_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14025_tenant_file_object_usage_exceeds_the_threshold.rst index 0865531..71ad788 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14025_tenant_file_object_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14025_tenant_file_object_usage_exceeds_the_threshold.rst @@ -114,4 +114,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927474.png +.. |image1| image:: /_static/images/en-us_image_0269417370.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14026_blocks_on_datanode_exceed_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14026_blocks_on_datanode_exceed_the_threshold.rst index bf411b9..198a01b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14026_blocks_on_datanode_exceed_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14026_blocks_on_datanode_exceed_the_threshold.rst @@ -138,4 +138,4 @@ The average number of blocks stored in each DataNode instance in the cluster is: **Xmx** specifies memory which corresponds to the threshold of the number of DataNode blocks, and each GB memory supports a maximum of 500,000 DataNode blocks. Set the memory as required. -.. |image1| image:: /_static/images/en-us_image_0000001532767582.png +.. |image1| image:: /_static/images/en-us_image_0263895589.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14027_datanode_disk_fault.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14027_datanode_disk_fault.rst index bfc29c1..d3c0ed9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14027_datanode_disk_fault.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14027_datanode_disk_fault.rst @@ -115,4 +115,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767582.png +.. |image1| image:: /_static/images/en-us_image_0263895589.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14028_number_of_blocks_to_be_supplemented_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14028_number_of_blocks_to_be_supplemented_exceeds_the_threshold.rst index 15f5a51..5a03146 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14028_number_of_blocks_to_be_supplemented_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14028_number_of_blocks_to_be_supplemented_exceeds_the_threshold.rst @@ -147,4 +147,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448206.png +.. |image1| image:: /_static/images/en-us_image_0269417373.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14029_number_of_blocks_in_a_replica_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14029_number_of_blocks_in_a_replica_exceeds_the_threshold.rst index 9b7cc5e..e5308be 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14029_number_of_blocks_in_a_replica_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14029_number_of_blocks_in_a_replica_exceeds_the_threshold.rst @@ -123,4 +123,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607654.png +.. |image1| image:: /_static/images/en-us_image_0269417374.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14030_hdfs_allows_write_of_single-replica_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14030_hdfs_allows_write_of_single-replica_data.rst index 86542ce..416c77b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14030_hdfs_allows_write_of_single-replica_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-14030_hdfs_allows_write_of_single-replica_data.rst @@ -35,7 +35,7 @@ RoleName Specifies the role for which the alarm is generated. Impact on the System -------------------- -If this configuration is enabled on the server and the number of HDFS replicas configured on the client is 1, single-replica data can be written to HDFS. Data of a single replica may be lost. Therefore, the system does not allow write of single-replica data by default. If a service requires single-replica data write to a directory, modify the HDFS configuration item **dfs.single.replication.exclude.pattern**. +Data of a single replica may be lost. Therefore, the system does not allow write of single-replica data by default. If this configuration is enabled on HDFS and the number of HDFS replicas configured on the client is 1, single-replica data can be written to HDFS. Possible Causes --------------- @@ -47,22 +47,23 @@ Procedure #. Log in to FusionInsight Manager and choose **Cluster** > **Services** > **HDFS**. On the page that is displayed, click the **Configurations** tab then the **All Configurations** sub-tab. #. Search for **dfs.single.replication.enable** in the search box, change the value of the configuration item to **false**, and click **Save**. -#. Wait for about 10 minutes and check whether the alarm is cleared. +#. On the **Dashboard** page of the HDFS service, click **More** and select **Service Rolling Restart** in the upper right corner. +#. After the HDFS service is started, check whether the alarm is cleared. - If yes, no further action is required. - - If no, go to :ref:`4 `. + - If no, go to :ref:`5 `. **Collect fault information.** -4. .. _alm-14030__li5733165943316: +5. .. _alm-14030__li5733165943316: On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. -5. Expand the drop-down list next to the **Service** field. In the **Services** dialog box that is displayed, select **HDFS** for the target cluster. +6. Expand the drop-down list next to the **Service** field. In the **Services** dialog box that is displayed, select **HDFS** for the target cluster. -6. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. +7. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. -7. Contact O&M personnel and provide the collected logs. +8. Contact O&M personnel and provide the collected logs. Alarm Clearing -------------- @@ -74,4 +75,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807773.png +.. |image1| image:: /_static/images/en-us_image_0000001383088002.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16000_percentage_of_sessions_connected_to_the_hiveserver_to_maximum_number_allowed_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16000_percentage_of_sessions_connected_to_the_hiveserver_to_maximum_number_allowed_exceeds_the_threshold.rst index 0f014a7..e3f12df 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16000_percentage_of_sessions_connected_to_the_hiveserver_to_maximum_number_allowed_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16000_percentage_of_sessions_connected_to_the_hiveserver_to_maximum_number_allowed_exceeds_the_threshold.rst @@ -84,4 +84,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127377.png +.. |image1| image:: /_static/images/en-us_image_0269417375.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16001_hive_warehouse_space_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16001_hive_warehouse_space_usage_exceeds_the_threshold.rst index c1b61ce..4741dcc 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16001_hive_warehouse_space_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16001_hive_warehouse_space_usage_exceeds_the_threshold.rst @@ -123,4 +123,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927578.png +.. |image1| image:: /_static/images/en-us_image_0269417376.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16002_hive_sql_execution_success_rate_is_lower_than_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16002_hive_sql_execution_success_rate_is_lower_than_the_threshold.rst index e07c26d..7c392d7 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16002_hive_sql_execution_success_rate_is_lower_than_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16002_hive_sql_execution_success_rate_is_lower_than_the_threshold.rst @@ -153,4 +153,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607850.png +.. |image1| image:: /_static/images/en-us_image_0269417377.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16003_background_thread_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16003_background_thread_usage_exceeds_the_threshold.rst index 933fc4f..5869b81 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16003_background_thread_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16003_background_thread_usage_exceeds_the_threshold.rst @@ -10,6 +10,10 @@ Description 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% by default. +.. note:: + + MRS 3.X supports the multi-instance function. If the multi-instance function is enabled in the cluster and multiple Hive services are installed, determine the Hive service for which the alarm is generated based on the value of **ServiceName** in **Location** of the alarm. For example, if Hive1 service is unavailable, **ServiceName** is set to **Hive1** in **Location**, and the operation object in the handling procedure is changed from Hive to Hive1. + Attribute --------- @@ -109,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087477.png +.. |image1| image:: /_static/images/en-us_image_0269417379.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16004_hive_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16004_hive_service_unavailable.rst index f432905..46832d8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16004_hive_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16004_hive_service_unavailable.rst @@ -12,6 +12,10 @@ This alarm is generated when the HiveServer service is unavailable. The system c This alarm is cleared when the HiveServer service is normal. +.. note:: + + MRS 3.X supports the multi-instance function. If the multi-instance function is enabled in the cluster and multiple Hive service instances are installed, you need to determine the Hive service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the Hive1 service is unavailable, **ServiceName=Hive1** is displayed in **Location**, and the operation object in the procedure needs to be changed from Hive to Hive1. + Attribute --------- @@ -211,4 +215,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927286.png +.. |image1| image:: /_static/images/en-us_image_0269417380.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16005_the_heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16005_the_heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst index e4d2b52..d72348c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16005_the_heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16005_the_heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst @@ -117,4 +117,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927709.png +.. |image1| image:: /_static/images/en-us_image_0269417381.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16006_the_direct_memory_usage_of_the_hive_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16006_the_direct_memory_usage_of_the_hive_process_exceeds_the_threshold.rst index fad11f4..3bcb90e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16006_the_direct_memory_usage_of_the_hive_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16006_the_direct_memory_usage_of_the_hive_process_exceeds_the_threshold.rst @@ -117,4 +117,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767550.png +.. |image1| image:: /_static/images/en-us_image_0269417382.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16007_hive_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16007_hive_gc_time_exceeds_the_threshold.rst index 869013f..6fbbc50 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16007_hive_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16007_hive_gc_time_exceeds_the_threshold.rst @@ -119,4 +119,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127545.png +.. |image1| image:: /_static/images/en-us_image_0269417383.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16008_non-heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16008_non-heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst index 245eed1..c8fbc52 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16008_non-heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16008_non-heap_memory_usage_of_the_hive_process_exceeds_the_threshold.rst @@ -119,4 +119,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087385.png +.. |image1| image:: /_static/images/en-us_image_0269417384.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16009_map_number_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16009_map_number_exceeds_the_threshold.rst index 4f94c7a..59c1d13 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16009_map_number_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16009_map_number_exceeds_the_threshold.rst @@ -81,4 +81,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927586.png +.. |image1| image:: /_static/images/en-us_image_0269417385.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16047_hiveserver_has_been_deregistered_from_zookeeper.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16047_hiveserver_has_been_deregistered_from_zookeeper.rst index 251ff82..4ed3d86 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16047_hiveserver_has_been_deregistered_from_zookeeper.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-16047_hiveserver_has_been_deregistered_from_zookeeper.rst @@ -76,4 +76,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127385.png +.. |image1| image:: /_static/images/en-us_image_0263895811.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17004_oozie_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17004_oozie_heap_memory_usage_exceeds_the_threshold.rst index af5e4ad..d88a40c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17004_oozie_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17004_oozie_heap_memory_usage_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607918.png +.. |image1| image:: /_static/images/en-us_image_0270938821.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17005_oozie_non_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17005_oozie_non_heap_memory_usage_exceeds_the_threshold.rst index 1d93485..2201df4 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17005_oozie_non_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17005_oozie_non_heap_memory_usage_exceeds_the_threshold.rst @@ -99,4 +99,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607978.png +.. |image1| image:: /_static/images/en-us_image_0263895663.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17006_oozie_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17006_oozie_direct_memory_usage_exceeds_the_threshold.rst index 6f8e75b..c173f7d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17006_oozie_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17006_oozie_direct_memory_usage_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767602.png +.. |image1| image:: /_static/images/en-us_image_0269417388.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17007_garbage_collection_gc_time_of_the_oozie_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17007_garbage_collection_gc_time_of_the_oozie_process_exceeds_the_threshold.rst index 8390b30..ff262e8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17007_garbage_collection_gc_time_of_the_oozie_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-17007_garbage_collection_gc_time_of_the_oozie_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927857.png +.. |image1| image:: /_static/images/en-us_image_0269417389.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18000_yarn_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18000_yarn_service_unavailable.rst index 0df971d..cd498c8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18000_yarn_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18000_yarn_service_unavailable.rst @@ -130,4 +130,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127409.png +.. |image1| image:: /_static/images/en-us_image_0269417390.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18002_nodemanager_heartbeat_lost.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18002_nodemanager_heartbeat_lost.rst index 6d89f3a..d60d6b5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18002_nodemanager_heartbeat_lost.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18002_nodemanager_heartbeat_lost.rst @@ -159,5 +159,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767534.png -.. |image2| image:: /_static/images/en-us_image_0000001532448310.png +.. |image1| image:: /_static/images/en-us_image_0269417391.png +.. |image2| image:: /_static/images/en-us_image_0269417392.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18003_nodemanager_unhealthy.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18003_nodemanager_unhealthy.rst index 4a39c6b..556415e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18003_nodemanager_unhealthy.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18003_nodemanager_unhealthy.rst @@ -131,5 +131,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927430.png -.. |image2| image:: /_static/images/en-us_image_0000001532607758.png +.. |image1| image:: /_static/images/en-us_image_0269417393.png +.. |image2| image:: /_static/images/en-us_image_0269417394.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18008_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18008_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst index 4365a7b..9827a42 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18008_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18008_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst @@ -111,4 +111,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087317.png +.. |image1| image:: /_static/images/en-us_image_0269417395.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18009_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18009_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst index ef4aa67..c02f1d2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18009_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18009_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst @@ -104,4 +104,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927825.png +.. |image1| image:: /_static/images/en-us_image_0269417396.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18010_resourcemanager_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18010_resourcemanager_gc_time_exceeds_the_threshold.rst index eb86fe5..a81bcf3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18010_resourcemanager_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18010_resourcemanager_gc_time_exceeds_the_threshold.rst @@ -108,4 +108,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087505.png +.. |image1| image:: /_static/images/en-us_image_0269417397.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18011_nodemanager_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18011_nodemanager_gc_time_exceeds_the_threshold.rst index 75b1ea4..d3ec4d2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18011_nodemanager_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18011_nodemanager_gc_time_exceeds_the_threshold.rst @@ -103,4 +103,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927650.png +.. |image1| image:: /_static/images/en-us_image_0269417398.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18012_jobhistoryserver_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18012_jobhistoryserver_gc_time_exceeds_the_threshold.rst index 93c863c..76f8a81 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18012_jobhistoryserver_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18012_jobhistoryserver_gc_time_exceeds_the_threshold.rst @@ -101,4 +101,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448166.png +.. |image1| image:: /_static/images/en-us_image_0269417399.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18013_resourcemanager_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18013_resourcemanager_direct_memory_usage_exceeds_the_threshold.rst index 06465f0..e923802 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18013_resourcemanager_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18013_resourcemanager_direct_memory_usage_exceeds_the_threshold.rst @@ -111,4 +111,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807685.png +.. |image1| image:: /_static/images/en-us_image_0269417400.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18014_nodemanager_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18014_nodemanager_direct_memory_usage_exceeds_the_threshold.rst index ec3a995..d5296a9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18014_nodemanager_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18014_nodemanager_direct_memory_usage_exceeds_the_threshold.rst @@ -111,4 +111,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607910.png +.. |image1| image:: /_static/images/en-us_image_0269417401.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18015_jobhistoryserver_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18015_jobhistoryserver_direct_memory_usage_exceeds_the_threshold.rst index 29cdfbb..522c286 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18015_jobhistoryserver_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18015_jobhistoryserver_direct_memory_usage_exceeds_the_threshold.rst @@ -111,4 +111,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927673.png +.. |image1| image:: /_static/images/en-us_image_0269417402.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18016_non_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18016_non_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst index 11c79ef..d1e5da4 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18016_non_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18016_non_heap_memory_usage_of_resourcemanager_exceeds_the_threshold.rst @@ -111,4 +111,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927689.png +.. |image1| image:: /_static/images/en-us_image_0269417403.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18017_non_heap_memory_usage_of_nodemanager_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18017_non_heap_memory_usage_of_nodemanager_exceeds_the_threshold.rst index a308e50..4c0c9cc 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18017_non_heap_memory_usage_of_nodemanager_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18017_non_heap_memory_usage_of_nodemanager_exceeds_the_threshold.rst @@ -106,4 +106,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927326.png +.. |image1| image:: /_static/images/en-us_image_0269417404.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18018_nodemanager_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18018_nodemanager_heap_memory_usage_exceeds_the_threshold.rst index c66ba9a..7d42be2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18018_nodemanager_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18018_nodemanager_heap_memory_usage_exceeds_the_threshold.rst @@ -104,4 +104,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927458.png +.. |image1| image:: /_static/images/en-us_image_0269417405.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18019_non_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18019_non_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst index f4c0651..41d6af1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18019_non_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18019_non_heap_memory_usage_of_jobhistoryserver_exceeds_the_threshold.rst @@ -104,4 +104,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127313.png +.. |image1| image:: /_static/images/en-us_image_0269417406.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18020_yarn_task_execution_timeout.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18020_yarn_task_execution_timeout.rst index cc6a87f..10f8772 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18020_yarn_task_execution_timeout.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18020_yarn_task_execution_timeout.rst @@ -56,17 +56,13 @@ Procedure **Check whether the timeout interval is correctly set.** #. On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**. The **Alarms** page is displayed. - #. Select the alarm whose ID is **18020**. In the alarm details, view **Location** to obtain the timeout task name and timeout duration. - #. Based on the task name and timeout interval, choose **Cluster** > *Name of the desired cluster* > **Services** > **Yarn** > **ResourceManager (Active)** to log in to the native Yarn page. Then find the task on the native page, check its **StartTime** and calculate the task execution time based on the current system time. Check whether the task execution time exceeds the timeout duration. - - If yes, go to :ref:`4 `. + - If yes, go to :ref:`5 `. - If no, go to :ref:`10 `. -#. .. _alm-18020__li135821125144620: - - Evaluate the expected task execution time based on the service and compare it with the task timeout interval. If the timeout interval is too short, set the timeout interval (**mapreduce.application.timeout.alarm** or **spark.application.timeout.alarm**) of the client to the task expected execution time. Run the task again and check whether the alarm is cleared. +#. Evaluate the expected task execution time based on the service and compare it with the task timeout interval. If the timeout interval is too short, set the timeout interval (**mapreduce.application.timeout.alarm** or **spark.application.timeout.alarm**) of the client to the task expected execution time. Run the task again and check whether the alarm is cleared. - If yes, no further action is required. - If no, go to :ref:`5 `. @@ -121,6 +117,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927573.png -.. |image2| image:: /_static/images/en-us_image_0000001583127321.png -.. |image3| image:: /_static/images/en-us_image_0000001532448194.png +.. |image1| image:: /_static/images/en-us_image_0000001087171010.png +.. |image2| image:: /_static/images/en-us_image_0000001439562477.png +.. |image3| image:: /_static/images/en-us_image_0263895445.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18021_mapreduce_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18021_mapreduce_service_unavailable.rst index 9ae90d2..caec951 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18021_mapreduce_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18021_mapreduce_service_unavailable.rst @@ -144,4 +144,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807805.png +.. |image1| image:: /_static/images/en-us_image_0269417409.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18022_insufficient_yarn_queue_resources.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18022_insufficient_yarn_queue_resources.rst index e01eba7..e78c9ff 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18022_insufficient_yarn_queue_resources.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18022_insufficient_yarn_queue_resources.rst @@ -136,4 +136,4 @@ Reference None -.. |image1| image:: /_static/images/en-us_image_0000001532927482.png +.. |image1| image:: /_static/images/en-us_image_0269417410.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18023_number_of_pending_yarn_tasks_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18023_number_of_pending_yarn_tasks_exceeds_the_threshold.rst index f8c914e..20b81af 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18023_number_of_pending_yarn_tasks_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18023_number_of_pending_yarn_tasks_exceeds_the_threshold.rst @@ -113,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087333.png +.. |image1| image:: /_static/images/en-us_image_0263895802.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18024_pending_yarn_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18024_pending_yarn_memory_usage_exceeds_the_threshold.rst index e3f591f..29108b5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18024_pending_yarn_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18024_pending_yarn_memory_usage_exceeds_the_threshold.rst @@ -113,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087421.png +.. |image1| image:: /_static/images/en-us_image_0263895617.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18025_number_of_terminated_yarn_tasks_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18025_number_of_terminated_yarn_tasks_exceeds_the_threshold.rst index 2714615..5f3c367 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18025_number_of_terminated_yarn_tasks_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18025_number_of_terminated_yarn_tasks_exceeds_the_threshold.rst @@ -98,4 +98,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087357.png +.. |image1| image:: /_static/images/en-us_image_0269417413.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18026_number_of_failed_yarn_tasks_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18026_number_of_failed_yarn_tasks_exceeds_the_threshold.rst index 857c19e..35dffe3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18026_number_of_failed_yarn_tasks_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-18026_number_of_failed_yarn_tasks_exceeds_the_threshold.rst @@ -98,4 +98,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087481.png +.. |image1| image:: /_static/images/en-us_image_0269417414.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19000_hbase_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19000_hbase_service_unavailable.rst index 4f7a7a4..b384137 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19000_hbase_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19000_hbase_service_unavailable.rst @@ -12,6 +12,10 @@ This alarm is generated when the HBase service is unavailable. The alarm module This alarm is cleared when the HBase service recovers. +.. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, ServiceName=HBase1 is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -152,7 +156,7 @@ Procedure .. _alm-19000__fig13078536192610: - .. figure:: /_static/images/en-us_image_0000001532448266.png + .. figure:: /_static/images/en-us_image_0269417415.png :alt: **Figure 1** HBase system table **Figure 1** HBase system table @@ -179,14 +183,14 @@ Procedure .. _alm-19000__fig2133867192610: - .. figure:: /_static/images/en-us_image_0000001532767490.png + .. figure:: /_static/images/en-us_image_0269417416.png :alt: **Figure 2** HMaster is being started **Figure 2** HMaster is being started .. _alm-19000__fig41660353192610: - .. figure:: /_static/images/en-us_image_0000001583087409.png + .. figure:: /_static/images/en-us_image_0269417417.png :alt: **Figure 3** HMaster is started **Figure 3** HMaster is started @@ -199,7 +203,7 @@ Procedure On the HMaster WebUI, check whether any hbase:meta is in the **Region in Transition** state for a long time. - .. figure:: /_static/images/en-us_image_0000001582927649.png + .. figure:: /_static/images/en-us_image_0269417418.png :alt: **Figure 4** Region in Transition **Figure 4** Region in Transition @@ -273,4 +277,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807697.png +.. |image1| image:: /_static/images/en-us_image_0269417419.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19006_hbase_replication_sync_failed.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19006_hbase_replication_sync_failed.rst index 31cd45c..24181f0 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19006_hbase_replication_sync_failed.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19006_hbase_replication_sync_failed.rst @@ -12,6 +12,10 @@ The alarm module checks the HBase DR data synchronization status every 30 second When DR data synchronization succeeds, the alarm is cleared. +.. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, **ServiceName=HBase1** is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -181,4 +185,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607922.png +.. |image1| image:: /_static/images/en-us_image_0269417420.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19007_hbase_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19007_hbase_gc_time_exceeds_the_threshold.rst index d39cfdf..72f438e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19007_hbase_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19007_hbase_gc_time_exceeds_the_threshold.rst @@ -10,6 +10,10 @@ Description The system checks the old generation garbage collection (GC) time of the HBase service every 60 seconds. This alarm is generated when the detected old generation GC time exceeds the threshold (exceeds 5 seconds for three consecutive checks by default). To change the threshold, on the FusionInsight Manager portal, choose **O&M** > **Alarm** > **Thresholds** > *Name of the desired cluster* > **HBase > GC >** **GC time for old generation**. This alarm is cleared when the old generation GC time of the HBase service is shorter than or equal to the threshold. +.. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, **ServiceName=HBase1** is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -117,4 +121,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927717.png +.. |image1| image:: /_static/images/en-us_image_0269417421.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19008_heap_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19008_heap_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst index 387874d..a4ec2a2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19008_heap_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19008_heap_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst @@ -10,6 +10,10 @@ Description 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 maximum memory). +.. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, **ServiceName=HBase1** is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -114,4 +118,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927606.png +.. |image1| image:: /_static/images/en-us_image_0269417422.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19009_direct_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19009_direct_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst index 901fab8..ddc324d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19009_direct_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19009_direct_memory_usage_of_the_hbase_process_exceeds_the_threshold.rst @@ -12,6 +12,10 @@ The system checks the HBase service status every 30 seconds. The alarm is genera The alarm is cleared when the direct memory usage is less than the threshold. +.. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, **ServiceName=HBase1** is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -116,4 +120,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087501.png +.. |image1| image:: /_static/images/en-us_image_0269417423.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19011_regionserver_region_number_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19011_regionserver_region_number_exceeds_the_threshold.rst index d7eca47..570e199 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19011_regionserver_region_number_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19011_regionserver_region_number_exceeds_the_threshold.rst @@ -10,6 +10,10 @@ Description 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 monitoring page and RegionServer role monitoring page. This alarm is generated when the number of regions on a RegionServer exceeds the threshold (default value: 2000) for 20 consecutive times. The threshold can be changed by choosing **O&M** > **Alarm** > **Thresholds** > *Name of the desired cluster* > **HBase**. This alarm is cleared when the number of regions is less than or equal to the threshold. +.. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, **ServiceName=HBase1** is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -59,7 +63,7 @@ Procedure - If no, go to :ref:`3 `. - .. figure:: /_static/images/en-us_image_0000001532927346.png + .. figure:: /_static/images/en-us_image_0276801805.png :alt: **Figure 1** WebUI of HBase instance **Figure 1** WebUI of HBase instance @@ -216,4 +220,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927569.png +.. |image1| image:: /_static/images/en-us_image_0269417427.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19012_hbase_system_table_directory_or_file_lost.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19012_hbase_system_table_directory_or_file_lost.rst index bd46d22..ac49eb5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19012_hbase_system_table_directory_or_file_lost.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19012_hbase_system_table_directory_or_file_lost.rst @@ -19,6 +19,10 @@ The HBase directories and files are as follows: - Directory of the table **hbase:hindex** on the HDFS, .tableinfo file, and .regioninfo file - Directory of the **hbase:acl** table on the HDFS, .tableinfo, and .regioninfo file (This table does not exist in the common mode cluster by default.) + .. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, **ServiceName=HBase1** is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -93,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927334.png +.. |image1| image:: /_static/images/en-us_image_0269417428.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19013_duration_of_regions_in_transaction_state_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19013_duration_of_regions_in_transaction_state_exceeds_the_threshold.rst index c167131..2576f0b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19013_duration_of_regions_in_transaction_state_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19013_duration_of_regions_in_transaction_state_exceeds_the_threshold.rst @@ -10,6 +10,10 @@ Description 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 transaction state exceeds the threshold for two consecutive times. This alarm is cleared when all timeout regions are restored. +.. note:: + + If the multi-instance function is enabled in the cluster and multiple HBase service instances are installed, you need to determine the HBase service instance where the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the HBase1 service is unavailable, **ServiceName=HBase1** is displayed in **Location**, and the operation object in the procedure needs to be changed from HBase to HBase1. + Attribute --------- @@ -115,4 +119,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607834.png +.. |image1| image:: /_static/images/en-us_image_0269417429.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19014_capacity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19014_capacity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst index 7c741e3..329a43a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19014_capacity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19014_capacity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst @@ -12,6 +12,10 @@ The system checks the ZNode usage of the HBase service every 120 seconds. This a This alarm is cleared when the ZNode capacity usage is less than the critical alarm threshold. +.. note:: + + If the multi-instance function has been enabled in the cluster and multiple HBase services have been installed, determine the HBase service for which the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the value of **ServiceName** is **HBase-1**, change the operation object in the procedure from **HBase** to **HBase-1**. + Attribute --------- @@ -107,7 +111,7 @@ Procedure 9. .. _alm-19014__li5351076393624: - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. + On FusionInsight Manager, choose **O&M** > **Log** > **Download**. 10. Expand the drop-down list next to the **Service** field. In the **Services** dialog box that is displayed, select **HBase** for the target cluster. @@ -125,5 +129,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127465.png -.. |image2| image:: /_static/images/en-us_image_0000001532448342.png +.. |image1| image:: /_static/images/en-us_image_0000001390938104.png +.. |image2| image:: /_static/images/en-us_image_0263895386.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19015_quantity_quota_usage_on_zookeeper_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19015_quantity_quota_usage_on_zookeeper_exceeds_the_threshold.rst index 557f6d1..09d6218 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19015_quantity_quota_usage_on_zookeeper_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19015_quantity_quota_usage_on_zookeeper_exceeds_the_threshold.rst @@ -12,6 +12,10 @@ The system checks the ZNode usage of the HBase service every 120 seconds. This a This alarm is cleared when the ZNode quantity usage is less than the alarm threshold. +.. note:: + + If the multi-instance function has been enabled in the cluster and multiple HBase services have been installed, determine the HBase service for which the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the value of **ServiceName** is **HBase-1**, change the operation object in the procedure from **HBase** to **HBase-1**. + Attribute --------- @@ -125,5 +129,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927609.png -.. |image2| image:: /_static/images/en-us_image_0000001532448238.png +.. |image1| image:: /_static/images/en-us_image_0000001441097977.png +.. |image2| image:: /_static/images/en-us_image_0263895577.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19016_quantity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19016_quantity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst index 78a53d7..7eb73fb 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19016_quantity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19016_quantity_quota_usage_on_zookeeper_exceeds_the_threshold_severely.rst @@ -12,6 +12,10 @@ The system checks the ZNode usage of the HBase service every 120 seconds. This a This alarm is cleared when the quantity usage of the ZNode is less than the critical alarm threshold. +.. note:: + + If the multi-instance function has been enabled in the cluster and multiple HBase services have been installed, determine the HBase service for which the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the value of **ServiceName** is **HBase-1**, change the operation object in the procedure from **HBase** to **HBase-1**. + Attribute --------- @@ -125,5 +129,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927362.png -.. |image2| image:: /_static/images/en-us_image_0000001532767426.png +.. |image1| image:: /_static/images/en-us_image_0000001390618824.png +.. |image2| image:: /_static/images/en-us_image_0263895751.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19017_capacity_quota_usage_on_zookeeper_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19017_capacity_quota_usage_on_zookeeper_exceeds_the_threshold.rst index 4a0f15d..e53801b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19017_capacity_quota_usage_on_zookeeper_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19017_capacity_quota_usage_on_zookeeper_exceeds_the_threshold.rst @@ -12,6 +12,10 @@ The system checks the ZNode usage of the HBase service every 120 seconds. This a This alarm is cleared when the capacity usage of the ZNode capacity is less than the threshold. +.. note:: + + If the multi-instance function has been enabled in the cluster and multiple HBase services have been installed, determine the HBase service for which the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the value of **ServiceName** is **HBase-1**, change the operation object in the procedure from **HBase** to **HBase-1**. + Attribute --------- @@ -125,5 +129,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807761.png -.. |image2| image:: /_static/images/en-us_image_0000001583127453.png +.. |image1| image:: /_static/images/en-us_image_0000001440858625.png +.. |image2| image:: /_static/images/en-us_image_0263895513.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19018_hbase_compaction_queue_size_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19018_hbase_compaction_queue_size_exceeds_the_threshold.rst index ab5412f..c578083 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19018_hbase_compaction_queue_size_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19018_hbase_compaction_queue_size_exceeds_the_threshold.rst @@ -10,6 +10,10 @@ Description 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). This alarm is cleared when the compaction queue size is less than the threshold. +.. note:: + + If the multi-instance function has been enabled in the cluster and multiple HBase services have been installed, determine the HBase service for which the alarm is generated based on the value of **ServiceName** in **Location**. For example, if the value of **ServiceName** is **HBase-1**, change the operation object in the procedure from **HBase** to **HBase-1**. + Attribute --------- @@ -57,7 +61,7 @@ Procedure #. .. _alm-19018__li1681162011376: - On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Services** > **HBase**. On the page that is displayed, click the **Configuration** tab then the **All Configurations** sub-tab, search for **hbase.hstore.compaction.min**, **hbase.hstore.compaction.max**, **hbase.regionserver.thread.compaction.small**, and **hbase.regionserver.thread.compaction.throttle**, and set them to larger values. + On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Services** > **HBase**. On the page that is disaplyed, click the **Configuration** tab then the **All Configurations** sub-tab, search for **hbase.hstore.compaction.min**, **hbase.hstore.compaction.max**, **hbase.regionserver.thread.compaction.small**, and **hbase.regionserver.thread.compaction.throttle**, and set them to larger values. #. .. _alm-19018__li5814142393624: @@ -88,4 +92,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767650.png +.. |image1| image:: /_static/images/en-us_image_0263895551.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19019_number_of_hbase_hfiles_to_be_synchronized_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19019_number_of_hbase_hfiles_to_be_synchronized_exceeds_the_threshold.rst index ba822be..3cb5a23 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19019_number_of_hbase_hfiles_to_be_synchronized_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19019_number_of_hbase_hfiles_to_be_synchronized_exceeds_the_threshold.rst @@ -159,4 +159,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127561.png +.. |image1| image:: /_static/images/en-us_image_0000001159690571.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19020_number_of_hbase_wal_files_to_be_synchronized_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19020_number_of_hbase_wal_files_to_be_synchronized_exceeds_the_threshold.rst index 9121d87..d780a19 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19020_number_of_hbase_wal_files_to_be_synchronized_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19020_number_of_hbase_wal_files_to_be_synchronized_exceeds_the_threshold.rst @@ -159,4 +159,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127517.png +.. |image1| image:: /_static/images/en-us_image_0000001159847251.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19021_handler_usage_of_regionserver_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19021_handler_usage_of_regionserver_exceeds_the_threshold.rst deleted file mode 100644 index 236df16..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-19021_handler_usage_of_regionserver_exceeds_the_threshold.rst +++ /dev/null @@ -1,176 +0,0 @@ -:original_name: ALM-19021.html - -.. _ALM-19021: - -ALM-19021 Handler Usage of RegionServer Exceeds the Threshold -============================================================= - -Description ------------ - -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 the threshold (90% for five consecutive times by default). This alarm is cleared if the handler usage is lower than or equal to the threshold. - -.. note:: - - This section applies to MRS 3.2.0 or later. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -19021 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------------+---------------------------------------------------------+ -| Name | Meaning | -+===================+=========================================================+ -| 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 --------------------- - -RegionServers or HBase cannot provide services properly. - -Possible Causes ---------------- - -- The value of a handler is too small. -- Hotspotting occurs. - -Procedure ---------- - -**View alarm location information.** - -#. Log in to FusionInsight Manager and choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**, locate the row that contains the alarm whose **Alarm ID** is **19021**, and view the service instance and host name in **Location**. - -**Check the handler configuration.** - -2. Choose **Cluster** > **Services** > **HBase** and click the **Configurations** tab. In the upper right corner of the page, search for **hbase.regionserver.handler.count** and check whether its value is too small. The default value is **200**. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`5 `. - -3. .. _alm-19021__li195843102017: - - Change the value of this parameter to a greater value and save the configuration. Choose **Cluster** > **Services** > **HBase**, click the **Instance** tab, select the affected RegionServer instances, and choose **More** > **Instance Rolling Restart**. In the displayed dialog box, enter the username and password. In the **Instance Rolling Restart** dialog box, click **OK** and wait until the rolling restart is complete. - -4. After the configuration takes effect, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -**Check whether cluster hotspotting occurs.** - -5. .. _alm-19021__li5581133206: - - On FusionInsight Manager, choose **Cluster** > **Services** > **HBase** and click **HMaster(Active)** following **HMaster WebUI** to go to the web UI of the HBase instance. In the **Region Servers** area of the **Home** page, click **Requests** and check whether the requests in the **Filtered Read Request Count** and **Write Request Count** columns are evenly distributed. - - |image1| - - - If yes, go to :ref:`13 `. - - If no, go to :ref:`6 `. - -6. .. _alm-19021__li6799182374314: - - Check whether regions are evenly distributed. - - On FusionInsight Manager, choose **Cluster** > **Services** > **HBase** and click **HMaster(Active)** following **HMaster WebUI** to go to the web UI of the HBase instance. In the **Region Servers** area of the **Home** page, click **Base Stats** and check whether the regions in the **Num.Regions** column are evenly distributed. - - |image2| - - - If yes, go to :ref:`13 `. - - If no, go to :ref:`7 `. - -7. .. _alm-19021__li25912310204: - - Log in to the faulty RegionServer node as user **omm**. - -8. Run the following commands to go to the client installation directory and set the environment variable: - - **cd** *Client installation directory* - - **source bigdata_env** - - If the cluster uses the security mode, run the following command to perform security authentication: - - **kinit hbase** - - Enter the password as prompted (obtain the password from the MRS cluster administrator). - -9. Run the following commands to check whether the load balancing function is enabled. If the command output is **true**, the load balancing function is enabled. - - **hbase shell** - - **balancer_enabled** - - .. code-block:: - - hbase:004:0> balancer_enabled - true - Took 0.0165 seconds - => true - - - If yes, go to :ref:`13 `. - - If no, go to :ref:`10 `. - -10. .. _alm-19021__li1959839204: - - Run the following commands in HBase Shell to enable the load balancing function and check whether the function is enabled. - - **balance_switch true** - - **balancer_enabled** - - .. note:: - - You are advised to enable and manually trigger the load balancing function during off-peak hours. - -11. Run the following command to manually trigger' the load balancing function: - - **balancer** - -12. After the load balancing is complete, log in to FusionInsight Manager and choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms** and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`13 `. - -**Collect the fault information.** - -13. .. _alm-19021__li66014362013: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -14. Expand the **Service** drop-down list, and select **HBase** for the target cluster. - -15. Click |image3| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time respectively. Then, click **Download**. - -16. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532448374.png -.. |image2| image:: /_static/images/en-us_image_0000001583087517.png -.. |image3| image:: /_static/images/en-us_image_0000001532927534.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-20002_hue_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-20002_hue_service_unavailable.rst index 826d1f8..fc209d1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-20002_hue_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-20002_hue_service_unavailable.rst @@ -146,4 +146,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448414.png +.. |image1| image:: /_static/images/en-us_image_0269417439.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23001_loader_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23001_loader_service_unavailable.rst deleted file mode 100644 index 2bffba4..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23001_loader_service_unavailable.rst +++ /dev/null @@ -1,241 +0,0 @@ -:original_name: ALM-23001.html - -.. _ALM-23001: - -ALM-23001 Loader Service Unavailable -==================================== - -Description ------------ - -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 cleared when the Loader service is available. - -Attribute ---------- - -======== ============== ===================== -Alarm ID Alarm Severity Automatically Cleared -======== ============== ===================== -23001 Critical Yes -======== ============== ===================== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -When the Loader service is unavailable, the data loading, import, and conversion functions are unavailable. - -Possible Causes ---------------- - -- The internal service on which the Loader service depends is abnormal. - - - The ZooKeeper service is abnormal. - - The HDFS service is abnormal. - - The DBService service is abnormal. - - The Yarn service is abnormal. - - The Mapreduce service is abnormal. - -- Environment fault: The network is abnormal, which the Loader service cannot communicate with the depended internal services and cannot provide services. -- Software fault: The Loader service cannot run properly. - -Procedure ---------- - -**Check the ZooKeeper service status.** - -#. On the FusionInsight Manager home page, choose **Cluster** > *Name of the desired cluster* > **Services** > **ZooKeeper** to check whether the ZooKeeper running status is **Normal**. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`2 `. - -#. .. _alm-23001__li4762296581432: - - Choose **More** > **Restart Service** to restart the ZooKeeper service. In the alarm list, check whether **LoaderService Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`3 `. - -#. .. _alm-23001__li796972081432: - - On the FusionInsight Manager, check whether the alarm list contains **Process Fault**. - - - If yes, go to :ref:`4 `. - - If no, go to :ref:`7 `. - -#. .. _alm-23001__li1999976981432: - - In the **Location** area of **Process Fault**, check whether **ServiceName** is **ZooKeeper**. - - - If yes, go to :ref:`5 `. - - If no, go to :ref:`7 `. - -#. .. _alm-23001__li936862281432: - - Rectify the fault by following the steps provided in **ALM-12007 Process Fault**. - -#. In the alarm list, check whether **Loader Service Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`7 `. - -**Check the HDFS service status.** - -7. .. _alm-23001__li2767755181432: - - On the FusionInsight Manager, check whether the alarm list contains **HDFS Service Unavailable**. - - - If yes, go to :ref:`8 `. - - If no, go to :ref:`10 `. - -8. .. _alm-23001__li2728912881432: - - Rectify the fault by following the steps provided in **ALM-14000 HDFS Service Unavailable**. - -9. In the alarm list, check whether **Loader Service Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`10 `. - -**Check the DBService status.** - -10. .. _alm-23001__li508775181432: - - On the FusionInsight Manager home page, choose **Cluster** > *Name of the desired cluster* > **Services** > **DBService** to check whether the DBService running status is **Normal**. - - - If yes, go to :ref:`12 `. - - If no, go to :ref:`11 `. - -11. .. _alm-23001__li600348181432: - - Choose **More** > **Restart Service** to restart the DBService service. In the alarm list, check whether **LoaderService Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`12 `. - -**Check the Mapreduce status.** - -12. .. _alm-23001__li1459212281432: - - On the FusionInsight Manager home page, choose **Cluster** > *Name of the desired cluster* > **Services** > **Mapreduce** to check whether the Mapreduce running status is **Normal**. - - - If yes, go to :ref:`16 `. - - If no, go to :ref:`13 `. - -13. .. _alm-23001__li3072601281432: - - Choose **More** > **Restart Service** to restart the Mapreduce service. In the alarm list, check whether **LoaderService Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`16 `. - -**Check the Yarn status.** - -14. On the FusionInsight Manager home page, choose **Cluster** > *Name of the desired cluster* > **Services** > **Yarn** to check whether the Yarn running status is **Normal**. - - - If yes, go to :ref:`16 `. - - If no, go to :ref:`15 `. - -15. .. _alm-23001__li853150381432: - - Choose **More** > **Restart Service** to restart the Yarn service. In the alarm list, check whether **LoaderService Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`16 `. - -16. .. _alm-23001__li3662318181432: - - On the FusionInsight Manager, check whether the alarm list contains **Yarn Service Unavailable**. - - - If yes, go to :ref:`17 `. - - If no, go to :ref:`19 `. - -17. .. _alm-23001__li1368764681432: - - Rectify the fault by following the steps provided in **ALM-18000 Yarn Service Unavailable**. - -18. In the alarm list, check whether **Loader Service Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`19 `. - -**Check the network connection between Loader and dependent components.** - -19. .. _alm-23001__li2284337281432: - - On the FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader**. - -20. Click **Instance** and the LoaderServer instance list is displayed. - -21. .. _alm-23001__li5727208881432: - - Record the **Management IP Address** in the row of **LoaderServer(Active)**. - -22. Log in to the host where the active LoaderServer runs as **omm** user using the IP address obtained in :ref:`21 `. - -23. Run the **ping** command to check whether communication between the host that runs the active LoaderServer and the hosts that run the dependent components. (The dependent components include ZooKeeper, DBService, HDFS, Mapreduce and Yarn. Obtain the IP addresses of the hosts that run these services in the same way as that for obtaining the IP address of the active LoaderServer.) - - - If yes, go to :ref:`26 `. - - If no, go to :ref:`24 `. - -24. .. _alm-23001__li904948781432: - - Contact the administrator to restore the network. - -25. In the alarm list, check whether **Loader Service Unavailable** is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`26 `. - -**Collect fault information.** - -26. .. _alm-23001__li2799521581432: - - On the FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -27. Select the following nodes in the required cluster from the **Service** drop-down list: - - - ZooKeeper - - HDFS - - DBService - - Yarn - - Mapreduce - - Loader - -28. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -29. On the FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader**. - -30. Choose **More** > **Restart Service**, and click **OK**. - -31. Check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`32 `. - -32. .. _alm-23001__li2579152581432: - - Contact the O&M personnel and send the collected logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583087489.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23003_loader_task_execution_failure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23003_loader_task_execution_failure.rst deleted file mode 100644 index f02bd49..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23003_loader_task_execution_failure.rst +++ /dev/null @@ -1,120 +0,0 @@ -:original_name: ALM-23003.html - -.. _ALM-23003: - -ALM-23003 Loader Task Execution Failure -======================================= - -Description ------------ - -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 must be manually cleared. - -Attribute ---------- - -======== ============== ===================== -Alarm ID Alarm Severity Automatically Cleared -======== ============== ===================== -23003 Minor No -======== ============== ===================== - -Parameters ----------- - -=========== =========================================================== -Name Meaning -=========== =========================================================== -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. -JobID Specifies the ID of failed Loader job. -JobName Specifies the failed Loader job. -UserName Specifies the name of the user who submits the Loader job. -Details Supplementary information for which the alarm is generated. -=========== =========================================================== - -Impact on the System --------------------- - -An exception occurs during the execution of the submitted Loader job, and the execution fails. No execution result can be obtained. Execute the job again after rectifying the fault. - -Possible Causes ---------------- - -- Task parameters are incorrectly configured. -- Exceptions occur when Yarn is executing a job. - -Procedure ---------- - -**Check whether task parameters are incorrectly configured.** - -#. On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms** and click the alarm drop-down list from the alarm list, obtain the **Alarm Cause**. -#. If the alarm cause is "Failure to submit job", view error details in **Additional Information**, and go to the Loader WebUI to view the execution history of the job. - - .. note:: - - 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. - -#. Submit the task again. -#. Check whether the task executed successfully. - - - If yes, go to :ref:`9 `. - - If no, go to :ref:`5 `. - -**Check whether exceptions occur when Yarn is executing a job.** - -5. .. _alm-23003__li4864190683922: - - On FusionInsight Manager, click the alarm drop-down list from the alarm list, obtain the **Alarm Cause**. - -6. Check whether the Yarn activity is executed properly in the **Alarm Cause**. If the alarm cause is "Yarn execution failed", the Yarn activity is abnormal. - - - If yes, go to :ref:`7 `. - - If no, go to :ref:`10 `. - -7. .. _alm-23003__li4550592983922: - - Submit the task again. - -8. Please check whether the task executed successfully. - - - If yes, go to :ref:`9 `. - - If no, go to :ref:`10 `. - -9. .. _alm-23003__li4574774083922: - - In the alarm list, click **Clear** from **Operation** to manually clear the alarm. No further action is required. - -**Collect fault information.** - -10. .. _alm-23003__li6410647583922: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -11. Select the following nodes in the required cluster from the **Service** drop-down list: - - - DBService - - HDFS - - Loader - - Mapreduce - - Yarn - - ZooKeeper - -12. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -13. Contact the O&M personnel and send the collected logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system does not automatically clear this alarm, and you need to manually clear the alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532607822.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23004_loader_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23004_loader_heap_memory_usage_exceeds_the_threshold.rst deleted file mode 100644 index c608988..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23004_loader_heap_memory_usage_exceeds_the_threshold.rst +++ /dev/null @@ -1,100 +0,0 @@ -:original_name: ALM-23004.html - -.. _ALM-23004: - -ALM-23004 Loader Heap Memory Usage Exceeds the Threshold -======================================================== - -Description ------------ - -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 threshold (95% of the maximum memory) for 10 consecutive times. The alarm is cleared when the heap memory usage is less than the threshold. - -Attribute ---------- - -======== ============== ===================== -Alarm ID Alarm Severity Automatically Cleared -======== ============== ===================== -23004 Major Yes -======== ============== ===================== - -Parameters ----------- - -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ -| Name | Meaning | -+===================+==============================================================================================================================+ -| 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 triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated. | -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ - -Impact on the System --------------------- - -The heap memory overflow may cause a service breakdown. - -Possible Causes ---------------- - -The heap memory of the Loader instance is overused or the heap memory is inappropriately allocated. - -Procedure ---------- - -**Check heap memory usage.** - -#. On the FusionInsight Manager portal, choose **O&M** > **Alarm** > **Alarms** > **Loader Heap Memory Usage Exceeds the Threshold** > **Location.** Check the host name of the instance involved in this alarm. - -#. On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Instance**. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose **Customize** > **Memory** > **Loader Heap Memory Resource Percentage**. Click **OK**. - -#. Check whether the used heap memory of Loader reaches the threshold (the default value is 95% of the maximum heap memory) specified for Loader. - - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-23004__en-us_topic_0070543528_d0e41794: - - On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Configurations**. Click **All Configurations**. Increase the value of **-Xmx** in **GC_OPTS** as required, and click **Save**. Click **OK**. - - .. note:: - - - If this alarm is generated, the heap memory configured for the current Loader instance is insufficient for data transmission. You are advised to open the instance monitoring page, display the Loader heap memory resource status monitoring chart, and observe the change trend of the heap memory used by Loader in the monitoring chart. Then change the value of **-Xmx** to twice the current heap memory usage or to another value to meet site requirements. - - When setting the heap memory, you can set **-Xms** and **-Xmx** to similar values to avoid performance deterioration caused by heap size adjustment after each GC. - - Ensure that the sum of **-Xmx** and **XX:MaxPermSize** is not greater than the physical memory of the node server. - -#. Restart the affected services or instances and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Collect fault information.** - -6. .. _alm-23004__en-us_topic_0070543528_d0e41845: - - On the FusionInsight Manager portal, choose **O&M** > **Log** > **Download**. - -7. Select **Loader** in the required cluster from the **Service** drop-down list. - -8. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -9. Contact the O&M personnel and send the collected fault logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532927550.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23005_loader_non-heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23005_loader_non-heap_memory_usage_exceeds_the_threshold.rst deleted file mode 100644 index 8d84dbc..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23005_loader_non-heap_memory_usage_exceeds_the_threshold.rst +++ /dev/null @@ -1,98 +0,0 @@ -:original_name: ALM-23005.html - -.. _ALM-23005: - -ALM-23005 Loader Non-Heap Memory Usage Exceeds the Threshold -============================================================ - -Description ------------ - -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 threshold (80% of the maximum memory) for 5 consecutive times. The alarm is cleared when the non-heap memory usage is less than the threshold. - -Attribute ---------- - -======== ============== ===================== -Alarm ID Alarm Severity Automatically Cleared -======== ============== ===================== -23005 Major Yes -======== ============== ===================== - -Parameters ----------- - -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ -| Name | Meaning | -+===================+==============================================================================================================================+ -| 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 triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated. | -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ - -Impact on the System --------------------- - -The non-heap memory overflow may cause a service breakdown. - -Possible Causes ---------------- - -The non-heap memory of the Loader instance is overused or the non-heap memory is inappropriately allocated. - -Procedure ---------- - -**Check non-heap memory usage.** - -#. On the FusionInsight Manager portal, choose **O&M** > **Alarm** > **Alarms** > **Loader Non-Heap Memory Usage Exceeds the Threshold** > **Location.** Check the host name of the instance involved in this alarm. - -#. On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Instance**. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose **Customize** > **Memory** > **Loader Non Heap Memory Resource Percentage**. Click **OK**. - -#. Check whether the used non-heap memory of Loader reaches the threshold (the default value is 80% of the maximum non-heap memory) specified for Loader. - - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-23005__l9abf73fe3f00454bb3c00cace4971b5d: - - On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Configurations**. Click **All** **Configurations** Search **LOADER_GC_OPTS** in the search box. If the **-XX: MaxPermSize** parameter is not configured, set the initial value to **-XX: MaxPermSize=256M** for the first time. (If the alarm persists after the first adjustment, perform the second adjustment by referring to the following note.) And click **Save**. Click **OK**. - - .. note:: - - If this alarm is generated, the non-heap memory configured for the current Loader instance is insufficient for the service scenario. You are advised to open the instance monitoring page, open the Loader non-heap memory resource status monitoring chart, and observe the change trend of the non-heap memory used by Loader in the monitoring chart. Then change the value of **-XX:MaxPermSize** to twice the current non-heap memory usage or to another value to meet site requirements. - -#. Restart the affected services or instances and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Collect fault information.** - -6. .. _alm-23005__en-us_topic_0070543529_d0e42144: - - On the FusionInsight Manager portal, choose **O&M** > **Log** > **Download**. - -7. Select **Loader** in the required cluster from the **Service** drop-down list. - -8. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -9. Contact the O&M personnel and send the collected fault logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532767722.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23006_loader_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23006_loader_direct_memory_usage_exceeds_the_threshold.rst deleted file mode 100644 index 27d2ec8..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23006_loader_direct_memory_usage_exceeds_the_threshold.rst +++ /dev/null @@ -1,98 +0,0 @@ -:original_name: ALM-23006.html - -.. _ALM-23006: - -ALM-23006 Loader Direct Memory Usage Exceeds the Threshold -========================================================== - -Description ------------ - -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 threshold (80% of the maximum memory) for 5 consecutive times. The alarm is cleared when the direct memory usage of Loader is less than or equal to the threshold. - -Attribute ---------- - -======== ============== ===================== -Alarm ID Alarm Severity Automatically Cleared -======== ============== ===================== -23006 Major Yes -======== ============== ===================== - -Parameters ----------- - -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ -| Name | Meaning | -+===================+==============================================================================================================================+ -| 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 triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated. | -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ - -Impact on the System --------------------- - -The direct memory overflow may cause a service breakdown. - -Possible Causes ---------------- - -The direct memory of the Loader instance is overused or the direct memory is inappropriately allocated. - -Procedure ---------- - -**Check direct memory usage.** - -#. On the FusionInsight Manager portal, choose **O&M** > **Alarm** > **Alarms** > **Loader Direct Memory Usage Exceeds the Threshold** > **Location**. Check the host name of the instance involved in this alarm. - -#. On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Instance**. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose **Customize** > **Memory** > **Loader Memory Usage Statistics**. Click **OK**. - -#. Check whether the used direct memory of Loader reaches the threshold (the default value is 80% of the maximum direct memory) specified for Loader. - - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-23006__en-us_topic_0070543530_li79703172532: - - On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Configurations**. Click **All Configurations**. Search **LOADER_GC_OPTS** in the search box. Increase the value of **-XX:MaxDirectMemorySize** as required, and click **Save**. Click **OK**. - - .. note:: - - If this alarm is generated, the direct memory configured for the current Loader instance is insufficient for the service scenario. You are advised to open the instance monitoring page, display the Loader direct memory resource status monitoring chart, and observe the change trend of the direct memory used by Loader in the monitoring chart. Then change the value of **-XX:MaxDirectMemorySize** to twice the current direct memory usage or to another value to meet site requirements. - -#. Restart the affected services or instances and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Collect fault information.** - -6. .. _alm-23006__en-us_topic_0070543530_d0e42442: - - On the FusionInsight Manager portal, choose **O&M** > **Log** > **Download**. - -7. Select **Loader** in the required cluster from the **Service** drop-down list. - -8. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -9. Contact the O&M personnel and send the collected fault logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532767578.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23007_garbage_collection_gc_time_of_the_loader_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23007_garbage_collection_gc_time_of_the_loader_process_exceeds_the_threshold.rst deleted file mode 100644 index b562683..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-23007_garbage_collection_gc_time_of_the_loader_process_exceeds_the_threshold.rst +++ /dev/null @@ -1,98 +0,0 @@ -:original_name: ALM-23007.html - -.. _ALM-23007: - -ALM-23007 Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold -================================================================================== - -Description ------------ - -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 seconds**) for 5 consecutive times. The alarm is cleared when GC time is less than the threshold. - -Attribute ---------- - -======== ============== ===================== -Alarm ID Alarm Severity Automatically Cleared -======== ============== ===================== -23007 Major Yes -======== ============== ===================== - -Parameters ----------- - -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ -| Name | Meaning | -+===================+==============================================================================================================================+ -| 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 triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated. | -+-------------------+------------------------------------------------------------------------------------------------------------------------------+ - -Impact on the System --------------------- - -Loader service response is slow. - -Possible Causes ---------------- - -The heap memory of the Loader instance is overused or the heap memory is inappropriately allocated. - -Procedure ---------- - -**Check GC time.** - -#. On the FusionInsight Manager portal, choose **O&M** > **Alarm** > **Alarms** > **Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold** > **Location**. Check the host name of the instance involved in this alarm. - -#. On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Instance**. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose **Customize** > **GC** > **Garbage Collection (GC) Time of Loader**. Click **OK**. - -#. Check whether GC time of the Loader process every second exceeds the threshold (default value: **12 seconds**). - - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-23007__le43836763c17495db009983a29fba3de: - - On the FusionInsight Manager portal, choose **Cluster** > *Name of the desired cluster* > **Services** > **Loader** > **Configurations**. Click **All Configurations**. Search **LOADER_GC_OPTS** in the search box. Increase the value of **-Xmx** as required, and click **Save**. Click **OK**. - - .. note:: - - If this alarm is generated, the heap memory configured for the current Loader instance cannot meet the heap memory required for data transmission. You are advised to handle the problem by referring to :ref:`4 ` in section :ref:`ALM-23004 Loader Heap Memory Usage Exceeds the Threshold `. - -#. Restart the affected services or instances and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Collect fault information.** - -6. .. _alm-23007__en-us_topic_0070543531_d0e42747: - - On the FusionInsight Manager portal, choose **O&M** > **Log** > **Download**. - -7. Select **Loader** in the required cluster from the **Service** drop-down list. - -8. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -9. Contact the O&M personnel and send the collected fault logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582807565.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24000_flume_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24000_flume_service_unavailable.rst index b34239d..90da762 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24000_flume_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24000_flume_service_unavailable.rst @@ -80,4 +80,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24001_flume_agent_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24001_flume_agent_exception.rst index ee49c39..03f9f49 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24001_flume_agent_exception.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24001_flume_agent_exception.rst @@ -221,7 +221,7 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087521.png -.. |image2| image:: /_static/images/en-us_image_0000001582807813.png -.. |image3| image:: /_static/images/en-us_image_0000001532607870.png -.. |image4| image:: /_static/images/en-us_image_0000001583127505.png +.. |image1| image:: /_static/images/en-us_image_0000001088608580.png +.. |image2| image:: /_static/images/en-us_image_0000001135745627.png +.. |image3| image:: /_static/images/en-us_image_0000001135452179.png +.. |image4| image:: /_static/images/en-us_image_0269417447.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24003_flume_client_connection_interrupted.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24003_flume_client_connection_interrupted.rst index f953d97..4250de3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24003_flume_client_connection_interrupted.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24003_flume_client_connection_interrupted.rst @@ -120,4 +120,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24004_exception_occurs_when_flume_reads_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24004_exception_occurs_when_flume_reads_data.rst index 0304968..772534a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24004_exception_occurs_when_flume_reads_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24004_exception_occurs_when_flume_reads_data.rst @@ -144,4 +144,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927554.png +.. |image1| image:: /_static/images/en-us_image_0269417449.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24005_exception_occurs_when_flume_transmits_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24005_exception_occurs_when_flume_transmits_data.rst index 9ce0f16..f4b1896 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24005_exception_occurs_when_flume_transmits_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24005_exception_occurs_when_flume_transmits_data.rst @@ -154,4 +154,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24006_heap_memory_usage_of_flume_server_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24006_heap_memory_usage_of_flume_server_exceeds_the_threshold.rst index 656ca56..d527510 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24006_heap_memory_usage_of_flume_server_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24006_heap_memory_usage_of_flume_server_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24007_flume_server_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24007_flume_server_direct_memory_usage_exceeds_the_threshold.rst index 3e99bae..fb54f89 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24007_flume_server_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24007_flume_server_direct_memory_usage_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24008_flume_server_non_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24008_flume_server_non_heap_memory_usage_exceeds_the_threshold.rst index 17a5512..ce09299 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24008_flume_server_non_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24008_flume_server_non_heap_memory_usage_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24009_flume_server_garbage_collection_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24009_flume_server_garbage_collection_gc_time_exceeds_the_threshold.rst index 03e0036..9f912da 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24009_flume_server_garbage_collection_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24009_flume_server_garbage_collection_gc_time_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24010_flume_certificate_file_is_invalid_or_damaged.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24010_flume_certificate_file_is_invalid_or_damaged.rst index b1e8df9..421608f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24010_flume_certificate_file_is_invalid_or_damaged.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24010_flume_certificate_file_is_invalid_or_damaged.rst @@ -5,8 +5,6 @@ ALM-24010 Flume Certificate File Is Invalid or Damaged ====================================================== -This section applies to MRS 3.2.0 or later. - Description ----------- @@ -112,4 +110,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607646.png +.. |image1| image:: /_static/images/en-us_image_0000001214152530.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24011_flume_certificate_file_is_about_to_expire.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24011_flume_certificate_file_is_about_to_expire.rst index 7f7c4b1..f4ca0c7 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24011_flume_certificate_file_is_about_to_expire.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24011_flume_certificate_file_is_about_to_expire.rst @@ -5,8 +5,6 @@ ALM-24011 Flume Certificate File Is About to Expire =================================================== -This section applies to MRS 3.2.0 or later. - Description ----------- @@ -115,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807709.png +.. |image1| image:: /_static/images/en-us_image_0000001214312492.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24012_flume_certificate_file_has_expired.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24012_flume_certificate_file_has_expired.rst index bf359a4..1e81cb8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24012_flume_certificate_file_has_expired.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24012_flume_certificate_file_has_expired.rst @@ -5,8 +5,6 @@ ALM-24012 Flume Certificate File Has Expired ============================================ -This section applies to MRS 3.2.0 or later. - Description ----------- @@ -116,4 +114,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127261.png +.. |image1| image:: /_static/images/en-us_image_0000001259272397.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24013_flume_monitorserver_certificate_file_is_invalid_or_damaged.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24013_flume_monitorserver_certificate_file_is_invalid_or_damaged.rst index 61baf53..7540616 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24013_flume_monitorserver_certificate_file_is_invalid_or_damaged.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24013_flume_monitorserver_certificate_file_is_invalid_or_damaged.rst @@ -5,8 +5,6 @@ ALM-24013 Flume MonitorServer Certificate File Is Invalid or Damaged ==================================================================== -This section applies to MRS 3.2.0 or later. - Description ----------- @@ -112,4 +110,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087565.png +.. |image1| image:: /_static/images/en-us_image_0000001214315364.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24014_flume_monitorserver_certificate_is_about_to_expire.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24014_flume_monitorserver_certificate_is_about_to_expire.rst index 3ddd302..cc35ae4 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24014_flume_monitorserver_certificate_is_about_to_expire.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24014_flume_monitorserver_certificate_is_about_to_expire.rst @@ -5,8 +5,6 @@ ALM-24014 Flume MonitorServer Certificate Is About to Expire ============================================================ -This section applies to MRS 3.2.0 or later. - Description ----------- @@ -115,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767606.png +.. |image1| image:: /_static/images/en-us_image_0000001258875319.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24015_flume_monitorserver_certificate_file_has_expired.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24015_flume_monitorserver_certificate_file_has_expired.rst index 2095dc0..8f9a21b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24015_flume_monitorserver_certificate_file_has_expired.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-24015_flume_monitorserver_certificate_file_has_expired.rst @@ -5,8 +5,6 @@ ALM-24015 Flume MonitorServer Certificate File Has Expired ========================================================== -This section applies to MRS 3.2.0 or later. - Description ----------- @@ -116,4 +114,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448470.png +.. |image1| image:: /_static/images/en-us_image_0000001259115323.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25000_ldapserver_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25000_ldapserver_service_unavailable.rst index 272d5dc..9caa214 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25000_ldapserver_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25000_ldapserver_service_unavailable.rst @@ -121,4 +121,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448278.png +.. |image1| image:: /_static/images/en-us_image_0269417455.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25004_abnormal_ldapserver_data_synchronization.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25004_abnormal_ldapserver_data_synchronization.rst index 9d7f442..df4370e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25004_abnormal_ldapserver_data_synchronization.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25004_abnormal_ldapserver_data_synchronization.rst @@ -150,4 +150,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448478.png +.. |image1| image:: /_static/images/en-us_image_0269417456.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25005_nscd_service_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25005_nscd_service_exception.rst index 590dc95..575650f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25005_nscd_service_exception.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25005_nscd_service_exception.rst @@ -75,7 +75,7 @@ Procedure 5. .. _alm-25005__li423153448513: - Log in to the alarmed node as user **root** and run the **ping** command to check whether the network connectivity between this node and the LdapServer node is normal. + Log in to the alarmed node as user **root** and run the **ping** command to check whether the network connectivity between this node and the LdapServer node. is normal. - If yes, go to :ref:`6 `. - If no, contact network administrators to troubleshoot the fault. @@ -191,4 +191,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767398.png +.. |image1| image:: /_static/images/en-us_image_0263895532.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25006_sssd_service_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25006_sssd_service_exception.rst index a9c8e0c..ca32471 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25006_sssd_service_exception.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25006_sssd_service_exception.rst @@ -183,4 +183,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767598.png +.. |image1| image:: /_static/images/en-us_image_0269417458.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25500_krbserver_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25500_krbserver_service_unavailable.rst index 1d8884c..2ef4c3e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25500_krbserver_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-25500_krbserver_service_unavailable.rst @@ -114,4 +114,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448298.png +.. |image1| image:: /_static/images/en-us_image_0269417459.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26051_storm_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26051_storm_service_unavailable.rst index 526d5ac..e69c02b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26051_storm_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26051_storm_service_unavailable.rst @@ -147,4 +147,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087601.png +.. |image1| image:: /_static/images/en-us_image_0269417460.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26052_number_of_available_supervisors_of_the_storm_service_is_less_than_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26052_number_of_available_supervisors_of_the_storm_service_is_less_than_the_threshold.rst index fee50d9..5c55ed5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26052_number_of_available_supervisors_of_the_storm_service_is_less_than_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26052_number_of_available_supervisors_of_the_storm_service_is_less_than_the_threshold.rst @@ -102,4 +102,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127329.png +.. |image1| image:: /_static/images/en-us_image_0269417461.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26053_storm_slot_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26053_storm_slot_usage_exceeds_the_threshold.rst index 1901522..9d6be47 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26053_storm_slot_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26053_storm_slot_usage_exceeds_the_threshold.rst @@ -125,4 +125,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127341.png +.. |image1| image:: /_static/images/en-us_image_0269417462.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26054_nimbus_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26054_nimbus_heap_memory_usage_exceeds_the_threshold.rst index 948fad9..e9f549c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26054_nimbus_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-26054_nimbus_heap_memory_usage_exceeds_the_threshold.rst @@ -103,4 +103,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767486.png +.. |image1| image:: /_static/images/en-us_image_0269417463.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27001_dbservice_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27001_dbservice_service_unavailable.rst index 913cf45..f7cf97d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27001_dbservice_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27001_dbservice_service_unavailable.rst @@ -182,4 +182,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127425.png +.. |image1| image:: /_static/images/en-us_image_0269417464.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27003_dbservice_heartbeat_interruption_between_the_active_and_standby_nodes.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27003_dbservice_heartbeat_interruption_between_the_active_and_standby_nodes.rst index 77fa92a..74cdc71 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27003_dbservice_heartbeat_interruption_between_the_active_and_standby_nodes.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27003_dbservice_heartbeat_interruption_between_the_active_and_standby_nodes.rst @@ -103,5 +103,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767394.png -.. |image2| image:: /_static/images/en-us_image_0000001532927330.png +.. |image1| image:: /_static/images/en-us_image_0269417465.png +.. |image2| image:: /_static/images/en-us_image_0269417466.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27004_data_inconsistency_between_active_and_standby_dbservices.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27004_data_inconsistency_between_active_and_standby_dbservices.rst index c6aaf24..ca35987 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27004_data_inconsistency_between_active_and_standby_dbservices.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27004_data_inconsistency_between_active_and_standby_dbservices.rst @@ -156,4 +156,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927470.png +.. |image1| image:: /_static/images/en-us_image_0269417468.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27005_database_connections_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27005_database_connections_usage_exceeds_the_threshold.rst index a73a2d2..b39d9e7 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27005_database_connections_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27005_database_connections_usage_exceeds_the_threshold.rst @@ -64,7 +64,7 @@ Procedure .. _alm-27005__fig821715142011: - .. figure:: /_static/images/en-us_image_0000001532767514.png + .. figure:: /_static/images/en-us_image_0269417469.png :alt: **Figure 1** Number of connections used by database users **Figure 1** Number of connections used by database users @@ -82,7 +82,7 @@ Procedure .. _alm-27005__fig1567417179514: - .. figure:: /_static/images/en-us_image_0000001532448290.png + .. figure:: /_static/images/en-us_image_0000001086795516.png :alt: **Figure 2** Setting the maximum number of database connections **Figure 2** Setting the maximum number of database connections @@ -110,7 +110,7 @@ Procedure .. _alm-27005__fig14885145323516: - .. figure:: /_static/images/en-us_image_0000001532607774.png + .. figure:: /_static/images/en-us_image_0000001133372255.png :alt: **Figure 3** Setting alarm trigger count **Figure 3** Setting alarm trigger count @@ -119,7 +119,7 @@ Procedure .. _alm-27005__fig19690175212407: - .. figure:: /_static/images/en-us_image_0000001583087433.png + .. figure:: /_static/images/en-us_image_0000001390936180.png :alt: **Figure 4** Set alarm threshold **Figure 4** Set alarm threshold @@ -153,4 +153,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927446.png +.. |image1| image:: /_static/images/en-us_image_0269417473.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27006_disk_space_usage_of_the_data_directory_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27006_disk_space_usage_of_the_data_directory_exceeds_the_threshold.rst index 39ff62e..864879b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27006_disk_space_usage_of_the_data_directory_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27006_disk_space_usage_of_the_data_directory_exceeds_the_threshold.rst @@ -126,4 +126,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807605.png +.. |image1| image:: /_static/images/en-us_image_0269623978.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27007_database_enters_the_read-only_mode.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27007_database_enters_the_read-only_mode.rst index 7281443..40d8313 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27007_database_enters_the_read-only_mode.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-27007_database_enters_the_read-only_mode.rst @@ -149,4 +149,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767666.png +.. |image1| image:: /_static/images/en-us_image_0269624001.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38000_kafka_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38000_kafka_service_unavailable.rst index f10ab19..03da0d6 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38000_kafka_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38000_kafka_service_unavailable.rst @@ -134,4 +134,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927366.png +.. |image1| image:: /_static/images/en-us_image_0269417499.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38001_insufficient_kafka_disk_capacity.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38001_insufficient_kafka_disk_capacity.rst index caf875a..bdc688e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38001_insufficient_kafka_disk_capacity.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38001_insufficient_kafka_disk_capacity.rst @@ -255,4 +255,4 @@ Related Information - If yes, resolve the disk capacity insufficiency problem according to the handling method of "ALM-38001 Insufficient Kafka Disk Space" after the alarm is cleared. - If no, contact the O&M personnel. -.. |image1| image:: /_static/images/en-us_image_0000001532607862.png +.. |image1| image:: /_static/images/en-us_image_0269417500.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38002_kafka_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38002_kafka_heap_memory_usage_exceeds_the_threshold.rst index 0b0f8b7..fc597b5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38002_kafka_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38002_kafka_heap_memory_usage_exceeds_the_threshold.rst @@ -102,4 +102,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127365.png +.. |image1| image:: /_static/images/en-us_image_0269417501.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38004_kafka_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38004_kafka_direct_memory_usage_exceeds_the_threshold.rst index 9d291cc..387685e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38004_kafka_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38004_kafka_direct_memory_usage_exceeds_the_threshold.rst @@ -104,4 +104,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087461.png +.. |image1| image:: /_static/images/en-us_image_0269417502.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38005_gc_duration_of_the_broker_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38005_gc_duration_of_the_broker_process_exceeds_the_threshold.rst index e34954d..d78567b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38005_gc_duration_of_the_broker_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38005_gc_duration_of_the_broker_process_exceeds_the_threshold.rst @@ -103,4 +103,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087269.png +.. |image1| image:: /_static/images/en-us_image_0269417503.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38006_percentage_of_kafka_partitions_that_are_not_completely_synchronized_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38006_percentage_of_kafka_partitions_that_are_not_completely_synchronized_exceeds_the_threshold.rst index 8ab97e1..207c91d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38006_percentage_of_kafka_partitions_that_are_not_completely_synchronized_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38006_percentage_of_kafka_partitions_that_are_not_completely_synchronized_exceeds_the_threshold.rst @@ -106,4 +106,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927557.png +.. |image1| image:: /_static/images/en-us_image_0269417504.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38007_status_of_kafka_default_user_is_abnormal.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38007_status_of_kafka_default_user_is_abnormal.rst index cddd59f..8a92c65 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38007_status_of_kafka_default_user_is_abnormal.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38007_status_of_kafka_default_user_is_abnormal.rst @@ -111,4 +111,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807621.png +.. |image1| image:: /_static/images/en-us_image_0269417505.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38008_abnormal_kafka_data_directory_status.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38008_abnormal_kafka_data_directory_status.rst index e583111..248cf8e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38008_abnormal_kafka_data_directory_status.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38008_abnormal_kafka_data_directory_status.rst @@ -113,4 +113,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807601.png +.. |image1| image:: /_static/images/en-us_image_0269417506.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38009_busy_broker_disk_i_os_applicable_to_versions_later_than_mrs_3.1.0.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38009_busy_broker_disk_i_os_applicable_to_versions_later_than_mrs_3.1.0.rst index 431e5a4..c90deee 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38009_busy_broker_disk_i_os_applicable_to_versions_later_than_mrs_3.1.0.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38009_busy_broker_disk_i_os_applicable_to_versions_later_than_mrs_3.1.0.rst @@ -140,7 +140,7 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927450.png -.. |image2| image:: /_static/images/en-us_image_0000001532607778.png -.. |image3| image:: /_static/images/en-us_image_0000001583087429.png -.. |image4| image:: /_static/images/en-us_image_0000001582807721.png +.. |image1| image:: /_static/images/en-us_image_0263895771.png +.. |image2| image:: /_static/images/en-us_image_0000001441218685.png +.. |image3| image:: /_static/images/en-us_image_0000001441098753.png +.. |image4| image:: /_static/images/en-us_image_0263895859.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38010_topics_with_single_replica.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38010_topics_with_single_replica.rst index bb82433..61cf56f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38010_topics_with_single_replica.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38010_topics_with_single_replica.rst @@ -105,5 +105,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448170.png -.. |image2| image:: /_static/images/en-us_image_0000001582927549.png +.. |image1| image:: /_static/images/en-us_image_0269417510.png +.. |image2| image:: /_static/images/en-us_image_0000001125163135.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38011_user_connection_usage_on_broker_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38011_user_connection_usage_on_broker_exceeds_the_threshold.rst deleted file mode 100644 index c487577..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-38011_user_connection_usage_on_broker_exceeds_the_threshold.rst +++ /dev/null @@ -1,189 +0,0 @@ -:original_name: ALM-38011.html - -.. _ALM-38011: - -ALM-38011 User Connection Usage on Broker Exceeds the Threshold -=============================================================== - -Description ------------ - -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 threshold (80% by default) for 5 consecutive times. - -The number of times that smoothing is performed is **5**. This alarm is cleared when the connection usage of a user on the Broker is less than the threshold. - -The alarm can be automatically cleared. However, if the number of connections of a user suddenly becomes **0** and no connection is created, the alarm cannot be automatically cleared. You need to manually clear it. - -Attribute ---------- - -======== ============== ===================== -Alarm ID Alarm Severity Automatically Cleared -======== ============== ===================== -38011 Major Yes -======== ============== ===================== - -Parameters ----------- - -=========== ======================================================== -Name Meaning -=========== ======================================================== -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. -UserName Specifies the username for which the alarm is generated. -=========== ======================================================== - -Impact on the System --------------------- - -If the number of connections of a user is excessive, the user cannot create new connections to the Broker. - -Possible Causes ---------------- - -- The number of connections (created by a user) used by the client exceeds the preset threshold. -- The threshold for the connection usage does not meet service requirements. - -Procedure ---------- - -**Check the number of connections established by the same user on the client.** - -#. On the FusionInsight Manager home page, choose **O&M** > **Alarm** > **Alarms** > **User Connection Usage on Broker Exceeds the Threshold**. Check the host name and username of the Broker instance for which the alarm is generated in **Location**. - -#. .. _alm-38011__li19192924516: - - On FusionInsight Manager home page, choose **Cluster** > *Name of the desired cluster* > **Services** > **Kafka** > **Instance**. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down list in the upper right corner of the chart area, choose **Customize > Other**, and select **User Connection Usage on Broker**, **Maximum Number of User Connections on Broker**, and **Number of User Connections on Broker** to view the number of the current user connections on the Broker. - -#. Observe the number of real-time connections of the current alarm user and check whether the real-time monitoring data of the current user exists. - - - If yes, go to :ref:`4 `. - - If no, the current user has disconnected all connections. You need to clear the alarm manually, and no further action is required. - - .. note:: - - After the alarm user disconnects all connections, the monitoring data of the user disappears. In this case, the alarm will not be automatically cleared. You need to manually clear it. - -#. .. _alm-38011__li7238347142216: - - Check whether the user is authorized by the service side. - - If yes, go to :ref:`7 `. - - If no, go to :ref:`5 `. - -#. .. _alm-38011__li10246106955: - - Run the following command on the client to limit the number of connections of the user. There are two configuration rules based on the following commands: - - a. For the specific Broker and user, run the following command: - - **kafka-configs.sh --bootstrap-server** ** **--alter --add-config 'max.connections.per.user.overrides=[**\ **\ **:**\ **\ **]' --entity-type brokers --entity-name** ** **--command-config Kafka/kafka/config/producer.properties** - - .. note:: - - For unauthorized users, confirm with the service side to reduce the maximum number of connections of an unauthorized user or set the maximum number of connections to **0**. - - In the command, you need to specify the IP address and port number of Broker, set values of configuration items, and specify the **brokerId** and **username**. Here, the user refers to the authorized Kerberos user. - - The configuration updated using the command line tool can take effect dynamically. The configuration becomes invalid after the service is restarted. To make the configuration take effect after the restart, choose **Cluster** > *Name of the desired cluster* > **Services** > **Kafka** > **Configurations** > **All** **Configurations**> **Broker** > **Server** on the FusionInsight Manager home page and update the configuration to **max.connections.per.user.overrides**. - - b. For the specific use and default Broker (that is, all Broker instances in the cluster), run the following command: - - **kafka-configs.sh --bootstrap-server** ** **--alter --add-config 'max.connections.per.user.overrides=[**\ **\ **:**\ **\ **]' --entity-type brokers ---entity-default --command-config Kafka/kafka/config/client.properties** - - Example: - - **kafka-configs.sh --bootstrap-server 10.153.3.26:21007 --alter --add-config 'max.connections.per.user.overrides=[showcase:4]' --entity-type brokers --entity-name 1 --command-config Kafka/kafka/config/client.properties** - -#. Check whether the maximum number of connections is **0** and whether the number of connections of the current user decreases or remains unchanged according to :ref:`2 `. - - - If yes, manually clear the alarm and no further action is required. - - If no, go to :ref:`7 `. - -#. .. _alm-38011__li767116237265: - - Check whether the number of real-time connections and connection usage of the current user are sharply increased when they are compared with historical data, and whether have exceeded the specified maximum number of connections. - - - If yes, go to :ref:`8 `. - - If no, go to :ref:`9 `. - - .. note:: - - If there is an obvious increase after the comparison and the maximum number of connections has reached the preset value, the connections of the user may be abnormal. You need to confirm with the service party. - -**Check whether the number of user connections meets service requirements.** - -8. .. _alm-38011__li73329221446: - - Check whether the number of connections of the user meets service requirements. - - - If yes, go to :ref:`9 `. - - If no, contact the service party to rectify the fault. - - .. note:: - - If the number of user connections is abnormal, contact the service party to rectify the fault from the following aspects: - - - Check whether new services are added so that the number of user connections increases sharply. - - Check whether handle leakage occurs on the code at the service side. - -9. .. _alm-38011__li153332221440: - - Consider whether to increase the maximum number of connections of the user. - - - If yes, go to :ref:`10 `. - - If no, go to :ref:`12 `. - -10. .. _alm-38011__li123335223414: - - Increase the maximum number of connections based on the service requirements. Set the number of connections of the user on the Kafka client. For details, see :ref:`5 `. - -11. Wait for several minutes and then check whether the alarm is automatically cleared. - - - If yes, go to :ref:`12 `. - - If no, go to :ref:`2 `. - -12. .. _alm-38011__li17333142212420: - - Determine whether to add the user to the whitelist based on service requirements on the service side. - - - If yes, go to :ref:`13 `. - - If no, go to :ref:`15 `. - - .. note:: - - To add a user to the whitelist, you need to restart the Kafka service. However, this operation will cause service interruption and affect service running. Therefore, you must confirm with the service side before performing this operation. - -13. .. _alm-38011__li173338226416: - - On the FusionInsight Manager home page, choose **Cluster** > *Name of the desired cluster* > **Services** > **Kafka** > **Configurations** > **All Configurations** > **Broker(Role)** > **Server** to add the user to the **max.connections.per.user.whitelist** configuration item. - -14. Restart the service for the modification to take effect. In addition, you need to manually clear the alarm, and no further action is required. - -**Collect the fault information.** - -15. .. _alm-38011__li1473912318017: - - On the FusionInsight Manager homepage, choose **O&M** > **Log** > **Download**. - -16. Expand the **Service** drop-down list, and select **Kafka** for the target cluster. - -17. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -18. Contact the O&M personnel and send the collected fault logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583127485.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43001_spark2x_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43001_spark2x_service_unavailable.rst index ec3b5ad..61cc1a3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43001_spark2x_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43001_spark2x_service_unavailable.rst @@ -112,4 +112,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087465.png +.. |image1| image:: /_static/images/en-us_image_0263895574.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43006_heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43006_heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst index 08d5120..641e4ed 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43006_heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43006_heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448178.png +.. |image1| image:: /_static/images/en-us_image_0269417534.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43007_non-heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43007_non-heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst index 83060f1..c30d162 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43007_non-heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43007_non-heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927593.png +.. |image1| image:: /_static/images/en-us_image_0269417535.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43008_the_direct_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43008_the_direct_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst index 032f5a4..4467eb2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43008_the_direct_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43008_the_direct_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087597.png +.. |image1| image:: /_static/images/en-us_image_0269417537.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43009_jobhistory2x_process_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43009_jobhistory2x_process_gc_time_exceeds_the_threshold.rst index cbffa43..43118f2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43009_jobhistory2x_process_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43009_jobhistory2x_process_gc_time_exceeds_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927602.png +.. |image1| image:: /_static/images/en-us_image_0269417538.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43010_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43010_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst index ebf5fef..be41c7d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43010_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43010_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607830.png +.. |image1| image:: /_static/images/en-us_image_0269417539.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43011_non-heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43011_non-heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst index 4656323..fd13a13 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43011_non-heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43011_non-heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087413.png +.. |image1| image:: /_static/images/en-us_image_0269417540.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43012_direct_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43012_direct_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst index d0a256d..03f305e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43012_direct_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43012_direct_heap_memory_usage_of_the_jdbcserver2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927454.png +.. |image1| image:: /_static/images/en-us_image_0269417541.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43013_jdbcserver2x_process_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43013_jdbcserver2x_process_gc_time_exceeds_the_threshold.rst index ff33d73..af715fa 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43013_jdbcserver2x_process_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43013_jdbcserver2x_process_gc_time_exceeds_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767654.png +.. |image1| image:: /_static/images/en-us_image_0269417542.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43017_jdbcserver2x_process_full_gc_number_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43017_jdbcserver2x_process_full_gc_number_exceeds_the_threshold.rst index 942516a..514ac1d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43017_jdbcserver2x_process_full_gc_number_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43017_jdbcserver2x_process_full_gc_number_exceeds_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927594.gif +.. |image1| image:: /_static/images/en-us_image_0269417543.gif diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43018_jobhistory2x_process_full_gc_number_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43018_jobhistory2x_process_full_gc_number_exceeds_the_threshold.rst index 3db1f8f..61f4043 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43018_jobhistory2x_process_full_gc_number_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43018_jobhistory2x_process_full_gc_number_exceeds_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448294.gif +.. |image1| image:: /_static/images/en-us_image_0269417544.gif diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43019_heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43019_heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst index 9e969cf..703dea1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43019_heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43019_heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Reference None -.. |image1| image:: /_static/images/en-us_image_0000001532607898.png +.. |image1| image:: /_static/images/en-us_image_0269417545.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43020_non-heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43020_non-heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst index 6d50706..c12371a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43020_non-heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43020_non-heap_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Reference None -.. |image1| image:: /_static/images/en-us_image_0000001532927518.png +.. |image1| image:: /_static/images/en-us_image_0269417546.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43021_direct_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43021_direct_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst index 2979589..acb3a29 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43021_direct_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43021_direct_memory_usage_of_the_indexserver2x_process_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Reference None -.. |image1| image:: /_static/images/en-us_image_0000001532607882.png +.. |image1| image:: /_static/images/en-us_image_0269417547.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43022_indexserver2x_process_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43022_indexserver2x_process_gc_time_exceeds_the_threshold.rst index e7aadaa..ac62b4e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43022_indexserver2x_process_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43022_indexserver2x_process_gc_time_exceeds_the_threshold.rst @@ -91,4 +91,4 @@ Reference None -.. |image1| image:: /_static/images/en-us_image_0000001532607946.png +.. |image1| image:: /_static/images/en-us_image_0269417548.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43023_indexserver2x_process_full_gc_number_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43023_indexserver2x_process_full_gc_number_exceeds_the_threshold.rst index ebf7dee..5464335 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43023_indexserver2x_process_full_gc_number_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-43023_indexserver2x_process_full_gc_number_exceeds_the_threshold.rst @@ -91,4 +91,4 @@ Reference None -.. |image1| image:: /_static/images/en-us_image_0000001532607846.png +.. |image1| image:: /_static/images/en-us_image_0269417549.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45000_hetuengine_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45000_hetuengine_service_unavailable.rst deleted file mode 100644 index 69479b3..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45000_hetuengine_service_unavailable.rst +++ /dev/null @@ -1,235 +0,0 @@ -:original_name: ALM-45000.html - -.. _ALM-45000: - -ALM-45000 HetuEngine Service Unavailable -======================================== - -Description ------------ - -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 HetuEngine service recovers. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45000 Critical Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -HetuEngine tasks fail to execute. - -Possible Causes ---------------- - -- The KrbServer service is abnormal. -- The ZooKeeper service is abnormal. -- The HDFS service is abnormal. -- The Yarn service is abnormal. -- The DBService service is abnormal. -- The Hive service is abnormal. -- Thre are no HSBroker instances in HetuEngine. - -Procedure ---------- - -**Check the KrbServer service status.** - -#. On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarm**. - -#. In the alarm list, check whether the "ALM-25500 KrbServer Service Unavailable" alarm is generated. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`5 `. - -#. .. _alm-45000__en-us_topic_0254455541_li6449155931114: - - Clear "ALM-25500 KrbServer Service Unavailable" according to the alarm help. - -#. In the alarm list, check whether the alarm "ALM-45000 HetuEngine Service Unavailable" is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -**Check the ZooKeeper service status.** - -5. .. _alm-45000__en-us_topic_0254455541_li9811171991313: - - In the alarm list, check whether the alarm "ALM-12007 Process Fault" is generated. - - - If yes, go to :ref:`6 `. - - If no, go to :ref:`9 `. - -6. .. _alm-45000__en-us_topic_0254455541_li078811388136: - - In the alarm list, click |image1| in the row that contains the "Process Fault" alarm. Check whether the name of the service for which the alarm is generated is ZooKeeper in **Location Information**. - - - If yes, go to :ref:`7 `. - - If no, go to :ref:`9 `. - -7. .. _alm-45000__en-us_topic_0254455541_li8279173711910: - - Clear "ALM-12007 Process Fault" according to the alarm help. - -8. In the alarm list, check whether the alarm "ALM-45000 HetuEngine Service Unavailable" is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`9 `. - -**Check the HDFS service status.** - -9. .. _alm-45000__en-us_topic_0254455541_li1453212224251: - - In the alarm list, check whether the "ALM-14000 HDFS Service Unavailable" alarm is generated. - - - If yes, go to :ref:`10 `. - - If no, go to :ref:`12 `. - -10. .. _alm-45000__en-us_topic_0254455541_li11186103716269: - - Clear "ALM-14000 HDFS Service Unavailable" according to the alarm help. - -11. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`12 `. - -**Check the YARN service status.** - -12. .. _alm-45000__en-us_topic_0254455541_li164797109298: - - In the alarm list, check whether the "ALM-18000 YARN Service Unavailable" alarm is generated. - - - If yes, go to :ref:`13 `. - - If no, go to :ref:`15 `. - -13. .. _alm-45000__en-us_topic_0254455541_li850063073216: - - Clear "ALM-18000 YARN Service Unavailable" according to the alarm help. - -14. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`15 `. - -**Check the DBService service status.** - -15. .. _alm-45000__en-us_topic_0254455541_li1336315336331: - - In the alarm list, check whether the "ALM-27001 DBService Service Unavailable" alarm is generated. - - - If yes, go to :ref:`16 `. - - If no, go to :ref:`20 `. - -16. .. _alm-45000__en-us_topic_0254455541_li1427826153416: - - Clear "ALM-27001 DBService Service Unavailable" according to the alarm help. - -17. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`20 `. - -**Check the Hive service status.** - -18. In the alarm list, check whether the "ALM-16004 Hive Service Unavailable" alarm is generated. - - - If yes, go to :ref:`19 `. - - If no, go to :ref:`20 `. - -19. .. _alm-45000__en-us_topic_0254455541_li552411772716: - - Clear "ALM-16004 Hive Service Unavailable" according to the alarm help. - -20. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`20 `. - -**Check whether there are no HSBroker instances in HetuEngine.** - -21. .. _alm-45000__li9867630175315: - - On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Services** > **HetuEngine**. On the page that is displayed, click the **Instance** tab. - -22. Check whether there are no HSBroker instances. - - - If yes, click **Add Instance** to add one. - - If no, go to :ref:`23 `. - -23. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`23 `. - -**Check the network connection between HetuEngine and ZooKeeper, HDFS, YARN, DBService, and Hive.** - -24. .. _alm-45000__en-us_topic_0254455541_li1994811814357: - - On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Services** > **HetuEngine**. On the page that is displayed, click the **Instance** tab. - -25. .. _alm-45000__en-us_topic_0254455541_li7948128193518: - - Click the host name in the **HSBroker** row and record the management IP address in the **Basic Information** area. - -26. Log in to the host where HSBroker resides as user **omm** using the IP address obtained in :ref:`25 `. - -27. Run the **ping** command to check whether the network connection between the host where HSBroker resides and the hosts where ZooKeeper, HDFS, Yarn, DBService, and Hive reside is in the normal state. - - - If yes, go to :ref:`30 `. - - If no, go to :ref:`28 `. - -28. .. _alm-45000__en-us_topic_0254455541_li10151810164812: - - Contact the network administrator to restore the network. - -29. In the alarm list, check whether the "ALM-45000 HetuEngine Service Unavailable" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`30 `. - -**Collect fault information.** - -30. .. _alm-45000__en-us_topic_0254455541_li760014619484: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -31. Expand the **Service** drop-down list. In the **Services** dialog box that is displayed, select **HetuEngine** under the target cluster name, and click **OK**. - -32. 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**. - -33. Click |image2| 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**. - -34. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -After the fault is rectified, the system automatically clears this alarm. - -Reference ---------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532767734.png -.. |image2| image:: /_static/images/en-us_image_0000001532927662.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45001_faulty_hetuengine_compute_instances.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45001_faulty_hetuengine_compute_instances.rst deleted file mode 100644 index 360c0d7..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45001_faulty_hetuengine_compute_instances.rst +++ /dev/null @@ -1,154 +0,0 @@ -:original_name: ALM-45001.html - -.. _ALM-45001: - -ALM-45001 Faulty HetuEngine Compute Instances -============================================= - -This alarm applies only to MRS 3.2.0 or later. - -Description ------------ - -The system checks the HetuEngine compute instance status every 60 seconds. This alarm is generated when a HetuEngine compute instance is faulty. - -This alarm is cleared when all faulty HetuEngine compute instances are restored. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45001 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -HetuEngine tasks fail to execute. - -Possible Causes ---------------- - -- The HDFS service is abnormal. -- The Yarn service is abnormal. -- Yarn queue resources are insufficient. -- The process of compute instances is faulty. - -Procedure ---------- - -**Check the HDFS service status.** - -#. In the alarm list, check whether the "ALM-14000 HDFS Service Unavailable" alarm is generated. - - - If yes, go to :ref:`2 `. - - If no, go to :ref:`4 `. - -#. .. _alm-45001__li775719097: - - Clear "ALM-14000 HDFS Service Unavailable" according to the alarm help. - -#. In the alarm list, check whether the "ALM-45001 Faulty HetuEngine Compute Instances" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`4 `. - -**Check the YARN service status.** - -4. .. _alm-45001__en-us_topic_0254455541_li164797109298: - - In the alarm list, check whether the "ALM-18000 YARN Service Unavailable" alarm is generated. - - - If yes, go to :ref:`5 `. - - If no, go to :ref:`7 `. - -5. .. _alm-45001__en-us_topic_0254455541_li850063073216: - - Clear "ALM-18000 YARN Service Unavailable" according to the alarm help. - -6. In the alarm list, check whether the "ALM-45001 Faulty HetuEngine Compute Instances" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`7 `. - -**Check the YARN queue resource status.** - -7. .. _alm-45001__li202811552178: - - In the alarm list, check whether the "ALM-18022 Insufficient YARN Queue Resources" alarm is generated. - - - If yes, go to :ref:`8 `. - - If no, go to :ref:`10 `. - -8. .. _alm-45001__li151133170241: - - Clear "ALM-18022 Insufficient YARN Queue Resources" according to the alarm help. - -9. In the alarm list, check whether the "ALM-45001 Faulty HetuEngine Compute Instances" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`10 `. - -**Check the HetuEngine compute instance status.** - -10. .. _alm-45001__en-us_topic_0254455541_li1994811814357: - - Log in to FusionInsight Manager as an administrator who can access the HetuEngine web UI and choose **Cluster** > **Services** **> HetuEngine**. - -11. In the **Basic Information** area on the **Dashboard** tab page, click the link next to **HSConsole WebUI** to access the HSConsole page. - -12. On the compute instance page, check whether any compute instances are in the **FAULT** state. - - - If yes, go to :ref:`13 `. - - If no, go to :ref:`14 `. - -13. .. _alm-45001__en-us_topic_0254455541_li854392104615: - - In the **Operation** column of the target compute instance, click **Start** and wait until the instance is started. - -14. .. _alm-45001__en-us_topic_0254455541_li7665181304814: - - In the alarm list, check whether the "ALM-45001 Faulty HetuEngine Compute Instances" alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`15 `. - -**Collect fault information.** - -15. .. _alm-45001__en-us_topic_0254455541_li760014619484: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -16. Expand the **Service** drop-down list. In the **Services** dialog box that is displayed, select **HetuEngine** under the target cluster name, and click **OK**. - -17. 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**. - -18. Click |image1| 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**. - -19. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583127265.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45175_average_time_for_calling_obs_metadata_apis_is_greater_than_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45175_average_time_for_calling_obs_metadata_apis_is_greater_than_the_threshold.rst index f1bed5e..f95f56b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45175_average_time_for_calling_obs_metadata_apis_is_greater_than_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45175_average_time_for_calling_obs_metadata_apis_is_greater_than_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807905.png +.. |image1| image:: /_static/images/en-us_image_0276137859.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45176_success_rate_of_calling_obs_metadata_apis_is_lower_than_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45176_success_rate_of_calling_obs_metadata_apis_is_lower_than_the_threshold.rst index 5547f21..ca973c1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45176_success_rate_of_calling_obs_metadata_apis_is_lower_than_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45176_success_rate_of_calling_obs_metadata_apis_is_lower_than_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927530.png +.. |image1| image:: /_static/images/en-us_image_0276137858.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45177_success_rate_of_calling_obs_data_read_apis_is_lower_than_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45177_success_rate_of_calling_obs_data_read_apis_is_lower_than_the_threshold.rst index f8d443f..08a4cda 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45177_success_rate_of_calling_obs_data_read_apis_is_lower_than_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45177_success_rate_of_calling_obs_data_read_apis_is_lower_than_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607942.png +.. |image1| image:: /_static/images/en-us_image_0276137857.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45178_success_rate_of_calling_obs_data_write_apis_is_lower_than_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45178_success_rate_of_calling_obs_data_write_apis_is_lower_than_the_threshold.rst index aad5232..0344d38 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45178_success_rate_of_calling_obs_data_write_apis_is_lower_than_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45178_success_rate_of_calling_obs_data_write_apis_is_lower_than_the_threshold.rst @@ -91,4 +91,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927769.png +.. |image1| image:: /_static/images/en-us_image_0276137853.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45179_number_of_failed_obs_readfully_api_calls_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45179_number_of_failed_obs_readfully_api_calls_exceeds_the_threshold.rst index f4085cf..21f3318 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45179_number_of_failed_obs_readfully_api_calls_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45179_number_of_failed_obs_readfully_api_calls_exceeds_the_threshold.rst @@ -91,5 +91,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807641.png -.. |image2| image:: /_static/images/en-us_image_0000001532448210.png +.. |image1| image:: /_static/images/en-us_image_0000001298155472.png +.. |image2| image:: /_static/images/en-us_image_0000001296525586.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45180_number_of_failed_obs_read_api_calls_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45180_number_of_failed_obs_read_api_calls_exceeds_the_threshold.rst index 492ce48..a2c4ca4 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45180_number_of_failed_obs_read_api_calls_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45180_number_of_failed_obs_read_api_calls_exceeds_the_threshold.rst @@ -91,5 +91,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532607950.png -.. |image2| image:: /_static/images/en-us_image_0000001582927841.png +.. |image1| image:: /_static/images/en-us_image_0000001297838112.png +.. |image2| image:: /_static/images/en-us_image_0000001296365606.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45181_number_of_failed_obs_write_api_calls_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45181_number_of_failed_obs_write_api_calls_exceeds_the_threshold.rst index cea8ead..7421cd9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45181_number_of_failed_obs_write_api_calls_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45181_number_of_failed_obs_write_api_calls_exceeds_the_threshold.rst @@ -91,5 +91,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927622.png -.. |image2| image:: /_static/images/en-us_image_0000001583087609.png +.. |image1| image:: /_static/images/en-us_image_0000001351040425.png +.. |image2| image:: /_static/images/en-us_image_0000001349585581.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45182_number_of_throttled_obs_operations_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45182_number_of_throttled_obs_api_calls_exceeds_the_threshold.rst similarity index 79% rename from umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45182_number_of_throttled_obs_operations_exceeds_the_threshold.rst rename to umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45182_number_of_throttled_obs_api_calls_exceeds_the_threshold.rst index d142ee5..69dc54d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45182_number_of_throttled_obs_operations_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45182_number_of_throttled_obs_api_calls_exceeds_the_threshold.rst @@ -2,15 +2,15 @@ .. _ALM-45182: -ALM-45182 Number of Throttled OBS Operations Exceeds the Threshold -================================================================== +ALM-45182 Number of Throttled OBS API Calls Exceeds the Threshold +================================================================= Description ----------- -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 operations exceeds the threshold. +The system checks whether the number of throttled OBS API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of throttled API calls exceeds the threshold. -This alarm is automatically cleared when the number of throttled OBS operations is less than the threshold. +This alarm is automatically cleared when the number of throttled OBS API calls is less than the threshold. Attribute --------- @@ -51,7 +51,7 @@ The frequency of requesting OBS APIs is too high. Procedure --------- -#. Log in to FusionInsight Manager and choose **O&M** > **Alarm** > **Thresholds**. On the **Thresholds** page, choose **meta** > **Number of Throttled OBS Operations**. In the right pane, set **Threshold** or **Trigger Count** to a larger value as required. +#. Log in to FusionInsight Manager and choose **O&M** > **Alarm** > **Thresholds**. On the **Thresholds** page, choose **meta** > **Number of Throttled OBS API Calls**. In the right pane, set **Threshold** or **Trigger Count** to a larger value as required. #. Check whether the alarm is cleared. @@ -69,7 +69,7 @@ Procedure 4. .. _alm-45182__li19825189163317: - On FusionInsight Manager, choose **Cluster** > **Services** > **meta**. On the page that is displayed, click the **Chart** tab. On this tab page, select **OBS Throttled** in the **Chart Category** area. In the **Number of Throttled OBS Operations-All Instances** chart, view the host name of the instance that has the maximum number of throttled OBS API calls. For example, the host name is **node-ana-coreUQqJ0002**. + On FusionInsight Manager, choose **Cluster** > **Services** > **meta**. On the page that is displayed, click the **Chart** tab. On this tab page, select **OBS Throttled** in the **Chart Category** area. In the **Number of Throttled OBS API Calls-All Instances** chart, view the host name of the instance that has the maximum number of throttled OBS API calls. For example, the host name is **node-ana-corevpeO003**. |image1| @@ -90,5 +90,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087453.png -.. |image2| image:: /_static/images/en-us_image_0000001532607802.png +.. |image1| image:: /_static/images/en-us_image_0000001297841644.png +.. |image2| image:: /_static/images/en-us_image_0000001349825057.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45275_ranger_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45275_ranger_service_unavailable.rst index 86a5dad..0f06c58 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45275_ranger_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45275_ranger_service_unavailable.rst @@ -99,4 +99,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767366.png +.. |image1| image:: /_static/images/en-us_image_0293180907.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45276_abnormal_rangeradmin_status.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45276_abnormal_rangeradmin_status.rst index dd0f483..738c1cf 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45276_abnormal_rangeradmin_status.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45276_abnormal_rangeradmin_status.rst @@ -84,5 +84,5 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532927302.png -.. |image2| image:: /_static/images/en-us_image_0000001583087289.png +.. |image1| image:: /_static/images/en-us_image_0000001072559365.png +.. |image2| image:: /_static/images/en-us_image_0293234930.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45277_rangeradmin_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45277_rangeradmin_heap_memory_usage_exceeds_the_threshold.rst index 77cd7ba..1ef0fc0 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45277_rangeradmin_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45277_rangeradmin_heap_memory_usage_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582927529.png +.. |image1| image:: /_static/images/en-us_image_0293235730.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45278_rangeradmin_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45278_rangeradmin_direct_memory_usage_exceeds_the_threshold.rst index d6503ae..6406314 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45278_rangeradmin_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45278_rangeradmin_direct_memory_usage_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807585.png +.. |image1| image:: /_static/images/en-us_image_0293242788.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45279_rangeradmin_non_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45279_rangeradmin_non_heap_memory_usage_exceeds_the_threshold.rst index 126d765..8cfe9a3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45279_rangeradmin_non_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45279_rangeradmin_non_heap_memory_usage_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807581.png +.. |image1| image:: /_static/images/en-us_image_0293245149.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45280_rangeradmin_gc_duration_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45280_rangeradmin_gc_duration_exceeds_the_threshold.rst index a58d9e3..11a61e0 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45280_rangeradmin_gc_duration_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45280_rangeradmin_gc_duration_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767378.png +.. |image1| image:: /_static/images/en-us_image_0293246465.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45281_usersync_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45281_usersync_heap_memory_usage_exceeds_the_threshold.rst index d99f21d..69eca03 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45281_usersync_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45281_usersync_heap_memory_usage_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767382.png +.. |image1| image:: /_static/images/en-us_image_0293246731.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45282_usersync_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45282_usersync_direct_memory_usage_exceeds_the_threshold.rst index 880e118..8449d7a 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45282_usersync_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45282_usersync_direct_memory_usage_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448142.png +.. |image1| image:: /_static/images/en-us_image_0293247048.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45283_usersync_non_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45283_usersync_non_heap_memory_usage_exceeds_the_threshold.rst index d135903..31d4f31 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45283_usersync_non_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45283_usersync_non_heap_memory_usage_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448146.png +.. |image1| image:: /_static/images/en-us_image_0293247437.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45284_usersync_garbage_collection_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45284_usersync_garbage_collection_gc_time_exceeds_the_threshold.rst index 122aac3..976ae9d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45284_usersync_garbage_collection_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45284_usersync_garbage_collection_gc_time_exceeds_the_threshold.rst @@ -93,4 +93,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807577.png +.. |image1| image:: /_static/images/en-us_image_0293267262.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45285_tagsync_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45285_tagsync_heap_memory_usage_exceeds_the_threshold.rst index 9c6e764..b3223da 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45285_tagsync_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45285_tagsync_heap_memory_usage_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087281.png +.. |image1| image:: /_static/images/en-us_image_0293268152.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45286_tagsync_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45286_tagsync_direct_memory_usage_exceeds_the_threshold.rst index 6903a6b..e1f2c04 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45286_tagsync_direct_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45286_tagsync_direct_memory_usage_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087277.png +.. |image1| image:: /_static/images/en-us_image_0293269028.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45287_tagsync_non_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45287_tagsync_non_heap_memory_usage_exceeds_the_threshold.rst index 3e6f9d2..6cbe80f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45287_tagsync_non_heap_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45287_tagsync_non_heap_memory_usage_exceeds_the_threshold.rst @@ -95,4 +95,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767358.png +.. |image1| image:: /_static/images/en-us_image_0293269047.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45288_tagsync_garbage_collection_gc_time_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45288_tagsync_garbage_collection_gc_time_exceeds_the_threshold.rst index be8d449..e01fc76 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45288_tagsync_garbage_collection_gc_time_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45288_tagsync_garbage_collection_gc_time_exceeds_the_threshold.rst @@ -97,4 +97,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583087293.png +.. |image1| image:: /_static/images/en-us_image_0293269551.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45425_clickhouse_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45425_clickhouse_service_unavailable.rst index 89ddc8c..7bc762f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45425_clickhouse_service_unavailable.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45425_clickhouse_service_unavailable.rst @@ -138,4 +138,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532448422.png +.. |image1| image:: /_static/images/en-us_image_0295554634.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45426_clickhouse_service_quantity_quota_usage_in_zookeeper_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45426_clickhouse_service_quantity_quota_usage_in_zookeeper_exceeds_the_threshold.rst index 3c74ee0..cac3ee1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45426_clickhouse_service_quantity_quota_usage_in_zookeeper_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45426_clickhouse_service_quantity_quota_usage_in_zookeeper_exceeds_the_threshold.rst @@ -143,4 +143,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001583127525.png +.. |image1| image:: /_static/images/en-us_image_0295310731.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45427_clickhouse_service_capacity_quota_usage_in_zookeeper_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45427_clickhouse_service_capacity_quota_usage_in_zookeeper_exceeds_the_threshold.rst index d2a0713..ae15706 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45427_clickhouse_service_capacity_quota_usage_in_zookeeper_exceeds_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45427_clickhouse_service_capacity_quota_usage_in_zookeeper_exceeds_the_threshold.rst @@ -139,4 +139,4 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001532767414.png +.. |image1| image:: /_static/images/en-us_image_0295706662.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45428_clickhouse_disk_i_o_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45428_clickhouse_disk_i_o_exception.rst index 94b4454..28d6ba8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45428_clickhouse_disk_i_o_exception.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45428_clickhouse_disk_i_o_exception.rst @@ -46,36 +46,43 @@ Procedure --------- #. On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms** > **ALM-45428 ClickHouse Disk I/O Exception**. Check the role name and the IP address of the host where the alarm is generated in **Location**. + #. Use PuTTY to log in to the node for which the fault is generated as user **root**. + #. Run the **df -h** command to check the mount directory and find the disk mounted to the faulty directory. + #. Run the **smartctl -a /dev/sd\*** command to check disks. - - If **SMART Health Status: OK** is displayed, as shown in the following figure, the disk is healthy. In this case, go to :ref:`6 `. + - If **SMART Health Status: OK** is displayed, as shown in the following figure, the disk is healthy. In this case, go to :ref:`7 `. |image1| - - If the number following **Elements in grown defect list** is not 0, as shown in the following figure, the disk may have bad sectors. If **SMART Health Status: FAILURE** is displayed, the disk is in the sub-health state. In this case, contact O&M personnel. + - If the number following **Elements in grown defect list** is not 0, as shown in the following figure, the disk may have bad sectors. If **SMART Health Status: FAILURE** is displayed, the disk is in the sub-health state. In this case, go to :ref:`5 `. |image2| +#. .. _alm-45428__li838232512215: + + Rectify the fault by following the instructions provided in "Hard Disk Mounted to the ClickHouse Partition Directory Is Faulty" in . + #. After the fault is rectified, manually clear the alarm on FusionInsight Manager and check whether the alarm is generated again during the periodic check. - - If yes, go to :ref:`6 `. + - If yes, go to :ref:`7 `. - If no, no further action is required. **Collect the fault information.** -6. .. _alm-45428__li186532017115614: +7. .. _alm-45428__li186532017115614: On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. -7. Expand the **Service** drop-down list, and select **ClickHouse** for the target cluster. +8. Expand the **Service** drop-down list, and select **ClickHouse** for the target cluster. -8. Choose the corresponding host form the host list. +9. Choose the corresponding host form the host list. -9. Click |image3| 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**. +10. Click |image3| 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**. -10. Contact O&M personnel and provide the collected logs. +11. Contact O&M personnel and provide the collected logs. Alarm Clearing -------------- @@ -87,6 +94,6 @@ Related Information None -.. |image1| image:: /_static/images/en-us_image_0000001582807689.png -.. |image2| image:: /_static/images/en-us_image_0000001583127381.png -.. |image3| image:: /_static/images/en-us_image_0000001582927637.png +.. |image1| image:: /_static/images/en-us_image_0000001194201259.png +.. |image2| image:: /_static/images/en-us_image_0000001194201487.png +.. |image3| image:: /_static/images/en-us_image_0000001194317737.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45429_table_metadata_synchronization_failed_on_the_added_clickhouse_node.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45429_table_metadata_synchronization_failed_on_the_added_clickhouse_node.rst deleted file mode 100644 index 97ac4b9..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45429_table_metadata_synchronization_failed_on_the_added_clickhouse_node.rst +++ /dev/null @@ -1,115 +0,0 @@ -:original_name: ALM-45429.html - -.. _ALM-45429: - -ALM-45429 Table Metadata Synchronization Failed on the Added ClickHouse Node -============================================================================ - -.. note:: - - This section applies only to MRS 3.1.2 or later. - -Description ------------ - -This alarm is generated when the local table corresponding to the distributed table fails to be created during ClickHouse capacity expansion. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45429 Major No -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -The distributed table fails to be queried. - -Possible Causes ---------------- - -A node is stopped or faulty during capacity expansion. - -Procedure ---------- - -#. On FusionInsight Manager, choose **Cluster** > **Services** > **ClickHouse** > **Instance**. - -#. Check whether an instance is stopped, decommissioned, or faulty. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`4 `. - -#. .. _alm-45429__li1857611153310: - - Start the instance or rectify the instance fault until all instances are running properly. - -#. .. _alm-45429__li1457618110336: - - On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**, locate this alarm and the faulty host based on the location information. - -5. Log in to the faulty host as user **omm**. - -6. Run the following commands to initialize environment variables: - - **source** *Cluster installation directory*\ **/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/ENV_VARS** - - **source** *Cluster installation directory*\ **/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/clickhouse-env.sh** - - **export CLICKHOUSE_CONF_DIR=${CLICKHOUSE_CONF_DIR}** - -7. Run the following command to run the metadata synchronization tool to synchronize metadata from the existing node to the faulty node: - - **sh** *Cluster installation directory*\ **/FusionInsight_ClickHouse_*/install/FusionInsight-ClickHouse-*/clickhouse/sbin/clickhouse-create-meta.sh** **true** - -8. Run the following command to view the log information and check whether the metadata has been synchronized: - - **vim /var/log/Bigdata/clickhouse/clickhouseServer/start.log** - - - If the synchronization is complete, go to :ref:`9 `. - - If the synchronization fails, go to :ref:`10 `. - -9. .. _alm-45429__li185513552368: - - On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the **Alarm ID** column, locate the corresponding alarm and click **Clear** in the **Operation** column. In the displayed dialog box, click **OK** to manually clear the alarm. - -**Collect the fault information.** - -10. .. _alm-45429__li4749473185459: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -11. Expand the **Service** drop-down list, select **ClickHouse** for the target cluster, and click **OK**. - -12. Choose the corresponding host form the host list. - -13. Click |image1| 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**. - -14. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm needs to be manually cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582927545.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45430_permission_metadata_synchronization_failed_on_the_added_clickhouse_node.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45430_permission_metadata_synchronization_failed_on_the_added_clickhouse_node.rst deleted file mode 100644 index d2e3889..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45430_permission_metadata_synchronization_failed_on_the_added_clickhouse_node.rst +++ /dev/null @@ -1,116 +0,0 @@ -:original_name: ALM-45430.html - -.. _ALM-45430: - -ALM-45430 Permission Metadata Synchronization Failed on the Added ClickHouse Node -================================================================================= - -.. note:: - - This section applies only to MRS 3.1.2 or later. - -Description ------------ - -This alarm is generated when user and permission information fails to be synchronized during ClickHouse capacity expansion. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45430 Major No -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -The created user does not have operation permissions on the node. - -Possible Causes ---------------- - -A node is stopped or faulty during capacity expansion. - -Procedure ---------- - -#. On FusionInsight Manager, choose **Cluster** > **Services** > **ClickHouse** > **Instance**. - -#. Check whether an instance is stopped, decommissioned, or faulty. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`4 `. - -#. .. _alm-45430__li1857611153310: - - Start the instance or rectify the instance fault until all instances are running properly. - -#. .. _alm-45430__li1457618110336: - - On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**, locate this alarm and the faulty host based on the location information. - -5. Log in to the faulty host as user **omm**. - -6. Run the following commands to initialize environment variables: - - **source** *Cluster installation directory*\ **/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/ENV_VARS** - - **source** *Cluster installation directory*\ **/FusionInsight_ClickHouse_*/*_*_ClickHouseServer/etc/clickhouse-env.sh** - - **export CLICKHOUSE_CONF_DIR=${CLICKHOUSE_CONF_DIR}** - -7. Run the following command to run the metadata synchronization tool to synchronize metadata from the existing node to the faulty node: - - **sh** *Cluster installation directory*\ **/FusionInsight_ClickHouse_*/install/FusionInsight-ClickHouse-*/clickhouse/sbin/clickhouse-create-meta.sh** **true** - -8. Run the following command to view the log information and check whether the metadata has been synchronized: - - **vim /var/log/Bigdata/clickhouse/clickhouseServer/start.log** - - If the synchronization is complete, go to :ref:`9 `. - - If the synchronization fails, go to :ref:`10 `. - -9. .. _alm-45430__li185513552368: - - On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the **Alarm ID** column, locate the corresponding alarm and click **Clear** in the **Operation** column. In the displayed dialog box, click **OK** to manually clear the alarm. - -**Collect the fault information.** - -10. .. _alm-45430__li4749473185459: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -11. Expand the **Service** drop-down list, select **ClickHouse** for the target cluster, and click **OK**. - -12. Choose the corresponding host form the host list. - -13. Click |image1| 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**. - -14. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm needs to be manually cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532448154.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45431_improper_clickhouse_instance_distribution_for_topology_allocation.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45431_improper_clickhouse_instance_distribution_for_topology_allocation.rst deleted file mode 100644 index fb29e02..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45431_improper_clickhouse_instance_distribution_for_topology_allocation.rst +++ /dev/null @@ -1,68 +0,0 @@ -:original_name: ALM-45431.html - -.. _ALM-45431: - -ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation -=========================================================================== - -Description ------------ - -The ClickHouseServer instance distribution does not meet the topology allocation requirements. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45431 Critical No -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -Some ClickHouseServer instances are unavailable. - -Possible Causes ---------------- - -During installation or capacity expansion, the number of instances or allocation mode does not meet the topology requirements. - -Procedure ---------- - -#. On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**, locate the row that contains the alarm, and analyze the cause based on **Location** and **Additional Information**. -#. Handle the alarm based on the additional alarm information and handling method in the following table. - - +-------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Additional Information | Remarks | Handling Method | - +=============================================================+=====================================================================================================================================================================================================================================================+====================================================================================================================================================================================================================================================================================+ - | *n* ClickHouseServer instances should be added to other AZ. | This alarm is generated when a single cluster is deployed in cross-AZ DR mode. The ClickHouseServer instance deployment does not meet the cross-AZ DR topology allocation requirements. As a result, some instances cannot work properly. | a. On FusionInsight Manager, choose **Cluster** > **Services** > **ClickHouse**, click the **Instance** tab, locate the row that contains the alarm, view the host name in **Location**, and find the AZ for which the alarm is generated in the AZ column based on the host name. | - | | | b. On the **Instance** page, click **Add Instance** to add *n* ClickHouseServer instances to other AZs except the AZ where the alarm is generated. | - +-------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | *n* ClickHouseServer instances should be added. | This alarm is generated when a non-single-cluster is deployed in the default deployment mode of cross-AZ DR. The number of ClickHouseServer instances in the cluster is less than an even number. As a result, some instances cannot work properly. | a. Determine the number (*n*) of ClickHouseServer instances to be added based on the alarm information. | - | | | b. On FusionInsight Manager, choose **Cluster** > **Services** > **ClickHouse**, click the **Instance** tab, and add *n* ClickHouseServer instances to the cluster. | - +-------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - -Alarm Clearing --------------- - -This alarm needs to be manually cleared after the fault is rectified. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45432_clickhouse_user_synchronization_process_fails.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45432_clickhouse_user_synchronization_process_fails.rst deleted file mode 100644 index 7ad1abe..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45432_clickhouse_user_synchronization_process_fails.rst +++ /dev/null @@ -1,139 +0,0 @@ -:original_name: ALM-45432.html - -.. _ALM-45432: - -ALM-45432 ClickHouse User Synchronization Process Fails -======================================================= - -Description ------------ - -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 role synchronization process is faulty or the user role synchronization fails. - -This alarm is automatically cleared when the ClickHouse user role synchronization process or function becomes normal. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45432 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -Some ClickHouseServer instances are unavailable. - -Possible Causes ---------------- - -- The ClickHouse user role synchronization process is not started properly or exits abnormally. -- The ClickHouse user role synchronization process fails to synchronize user role information because the LdapServer service is faulty. - -Procedure ---------- - -**Check whether the ClickHouse user role synchronization process is normal.** - -#. Log in to FusionInsight Manager and choose **O&M** > **Alarm** > **Alarms**. On the page that is displayed, search for **ALM-45432 ClickHouse User Synchronization Process Fails**. - -#. Check the host name and additional information in the alarm details. - - - If the additional information is "Process clickhouse-ugsync is not exit.", go to :ref:`3 `. - - If the additional information is "Process clickhouse-ugsync sync user failed.", go to :ref:`6 `. - -#. .. _alm-45432__li172317474333: - - Log in to the faulty host as user **omm** and run the following command to check whether the ClickHouse user role synchronization process is normal: - - **ps -ef \| grep 'clickhouse-ugsync'** - - Abnormal result of the synchronization process: - - .. code-block:: console - - [omm@server-2110081635-0001 ~]$ ps -ef | grep 'clickhouse-ugsync' - omm 20104 13146 0 15:57 pts/7 00:00:00 grep --color=auto clickhouse-ugsync - - - If yes, the alarm is automatically cleared. If the alarm is cleared, no further action is required. If the alarm persists, go to :ref:`8 `. - - If no, go to :ref:`4 `. - -#. .. _alm-45432__li177241147103317: - - Log in to the faulty host as user **omm** and run the following command to check whether the crontab daemon task is correctly configured: - - **crontab -l** - - Normal setting of the crontab daemon task: - - .. code-block:: - - */5 * * * * bash /xxxxx/clickhouse_ugsync_check.sh >/dev/null 2>&1 - - - If yes, check whether the alarm is cleared 5 minutes later. If the alarm is cleared, no further action is required. If the alarm persists, go to :ref:`8 `. - - If no, go to :ref:`5 `. - -#. .. _alm-45432__li672411477337: - - Log in to FusionInsight Manager, choose **Cluster** > **Services** > **ClickHouse**. On the page that is displayed, click the **Instance** tab. On this tab page, find the abnormal ClickHouseServer instance based on the fault information, and restart it. Wait for 5 minutes and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Check whether the LdapServer service is normal.** - -6. .. _alm-45432__li622471521412: - - Log in to FusionInsight Manager, choose **Cluster** > **Services**, and check whether **Running Status** of LdapServer is **Normal**. - - - If yes, go to :ref:`8 `. - - If no, go to :ref:`7 `. - -7. .. _alm-45432__li18742173311518: - - Handle the LdapServer service unavailable alarm according to ALM-25000 LdapServer Service Unavailable. - - After **Running Status** of LdapServer becomes **Normal**, check whether this alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`8 `. - -**Collect fault information.** - -8. .. _alm-45432__li1272184713332: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -9. Expand the drop-down list next to the **Service** field. In the **Services** dialog box that is displayed, select **ClickHouseServer** for the target cluster. - -10. Expand the **Hosts** list. In the **Select Host** dialog box that is displayed, select the abnormal host, and click **OK**. - -11. Click |image1| 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**. - -12. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532607798.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45433_clickhouse_az_topology_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45433_clickhouse_az_topology_exception.rst deleted file mode 100644 index 6c86f83..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45433_clickhouse_az_topology_exception.rst +++ /dev/null @@ -1,134 +0,0 @@ -:original_name: ALM-45433.html - -.. _ALM-45433: - -ALM-45433 ClickHouse AZ Topology Exception -========================================== - -Description ------------ - -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-AZ HA does not take effect if backup nodes of the same shard are in the same AZ. - -This alarm is automatically cleared when the system detects that all shards meet the cross-AZ HA deployment requirements. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45433 Critical Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -Source Specifies the cluster for which the alarm is generated. -ServiceName Specifies the service for which the alarm is generated. -HostName Specifies the host for which the alarm is generated. -=========== ======================================================= - -Impact on the System --------------------- - -The current deployment of the ClickHouse service does not support cross-AZ HA. - -Possible Causes ---------------- - -After cross-AZ HA is enabled, all backup nodes of a shard are in the same AZ. - -Procedure ---------- - -**Modify the AZ of backup nodes.** - -#. Log in to the node where the client is installed as the client installation user. Run the following command to switch to the client installation directory: - - **cd** *{Client installation path}* - -#. Run the following command to configure environment variables: - - **source bigdata_env** - -#. Run the following command to authenticate the user (skip this step in normal mode): - - **kinit** *Component service user* - -#. Run the following command to log in to the client tool: - - **zkCli.sh -server**\ *Service IP address of the node where the ZooKeeper instance resides*\ **:**\ *Client port* - -#. Run the following command to view the current topology: - - **get /clickhouse/topo** - - .. note:: - - If the ClickHouse is installed with multiple services, run the **get /clickhouse{-n}/topo** command. For example, if the ClickHouse-1 is installed, run the **get /clickhouse-1/topo** command. - - .. code-block:: - - [zk: 192.168.20.36:24002(CONNECTED) 0] get /clickhouse/topo - - - - - - 1 - AZ1 - 192-168-20-205 - 21427 - - - 2 - AZ1 - 192-168-20-2205 - 21427 - - - - - -#. .. _alm-45433__li6955713123211: - - Select a host from the desired shard and deploy the host in another AZ. - -#. Log in to FusionInsight Manager, click **Host**, select the host you have deployed in :ref:`6 ` and choose **More** > **Reinstall** to reinstall the host. - -#. Choose **Cluster** > **Cross-AZ HA**, click **Configure AZ and Policy** and change the AZ information of the reinstalled host to the AZ planned in the :ref:`6 `. - -#. Wait for five minutes and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`10 `. - -**Collect fault information.** - -10. .. _alm-45433__li7445104417423: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -11. Expand the drop-down list next to the **Service** field. In the **Services** dialog box that is displayed, select **ClickHouseServer** for the target cluster. - -12. Expand the **Hosts** list. In the **Select Host** dialog box that is displayed, select the abnormal host, and click **OK**. - -13. Click |image1| 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**. - -14. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582927881.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45434_a_single_replica_exists_in_the_clickhouse_data_table.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45434_a_single_replica_exists_in_the_clickhouse_data_table.rst deleted file mode 100644 index 0cba20c..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45434_a_single_replica_exists_in_the_clickhouse_data_table.rst +++ /dev/null @@ -1,105 +0,0 @@ -:original_name: ALM-45434.html - -.. _ALM-45434: - -ALM-45434 A Single Replica Exists in the ClickHouse Data Table -============================================================== - -Description ------------ - -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 automatically cleared when the system detects that the custom logical cluster uses multiple replicas. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45434 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+-------------------------------------------------------------------+ -| Name | Meaning | -+=============+===================================================================+ -| 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 --------------------- - -If a hardware fault occurs, data cannot be restored. - -Possible Causes ---------------- - -The **metrika.xml** file in the ClickHouse configuration directory contains single-replica configuration. - -Procedure ---------- - -**Check whether the configuration in metrika.xml of the ClickHouse instance is correct.** - -#. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click |image1| to view the name of the host for which the alarm is generated. On the **Hosts** page, view the host IP address based on the host name. - -#. Log in to the host where the ClickHouse instance is abnormal, go to the configuration directory of the ClickHouse instance, and run the following commands: - - **cd** ${BIGDATA_HOME}\ **/FusionInsight_ClickHouse\_**\ *Version*\ **/**\ x_x\ **\_ClickHouseServer/etc** - - **cat metrika.xml** - -#. View the number of shards in each custom logical cluster and check that a single replica exists. Then, go to :ref:`4 `. - - .. note:: - - If a shard contains only one node, a single replica exists in a logical cluster, as shown in the following: - - .. code-block:: - - - true - - host-name1 - port - clickhouse - - - - -**Collect fault information.** - -4. .. _alm-45434__li153021955172417: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -5. Expand the **Service** drop-down list, and select **ClickHouse** for the target cluster. - -6. Expand the **Hosts** drop-down list. In the **Select Host** dialog box that is displayed, select the abnormal host, and click **OK**. - -7. Click |image2| 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**. - -8. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583087573.png -.. |image2| image:: /_static/images/en-us_image_0000001582927813.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45585_iotdb_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45585_iotdb_service_unavailable.rst deleted file mode 100644 index f9fa1bd..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45585_iotdb_service_unavailable.rst +++ /dev/null @@ -1,99 +0,0 @@ -:original_name: ALM-45585.html - -.. _ALM-45585: - -ALM-45585 IoTDB Service Unavailable -=================================== - -Description ------------ - -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 recovers. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45585 Critical Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -Users cannot use the IoTDB service properly. - -Possible Causes ---------------- - -- The KrbServer service is abnormal. -- More than 50% of IoTDBServer instances are faulty. - -Procedure ---------- - -**Check whether the KrbServer service on which the IoTDB depends is abnormal.** - -#. On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. - -#. In the alarm list, check whether ALM-25500 KrbServer Service Unavailable exists. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`5 `. - -#. .. _alm-45585__li1857611153310: - - Handle the alarm by referring to "ALM-25500 KrbServer Service Unavailable." - -#. After ALM-25500 is cleared, wait a few minutes and check whether the alarm HetuServer Service Unavailable is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -**Check whether IoTDBServer instances are faulty.** - -5. .. _alm-45585__li1336018269214: - - On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Service** > **IoTDB** > **Instance**. - -6. Check whether the percentage of faulty IoTDBServer instances exceeds 50%. If yes, restart the faulty IoTDBServer instances and check whether the status is restored. - - - If yes, no further action is required. - - If no, go to :ref:`7 `. - -**Collect the fault information.** - -7. .. _alm-45585__li4749473185459: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -8. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -9. Click |image1| 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**. - -10. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582927517.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45586_iotdbserver_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45586_iotdbserver_heap_memory_usage_exceeds_the_threshold.rst deleted file mode 100644 index 1f64c18..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45586_iotdbserver_heap_memory_usage_exceeds_the_threshold.rst +++ /dev/null @@ -1,93 +0,0 @@ -:original_name: ALM-45586.html - -.. _ALM-45586: - -ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold -============================================================= - -Description ------------ - -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% of the maximum memory). - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45586 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -If the available IoTDBServer process heap memory is insufficient, a memory overflow occurs and the service breaks down. - -Possible Causes ---------------- - -The heap memory of the IoTDBServer process is overused or the heap memory is inappropriately allocated. - -Procedure ---------- - -**Check the heap memory usage.** - -#. Log in to FusionInsight Manager and choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**. On the page that is displayed, locate the row containing the alarm whose **Alarm ID** is **45586**, view the role name in **Location**, and check the instance IP address. - -#. Choose **Cluster** > *Name of the desired cluster* > **Service** > **IoTDB** > **Instance**. Click the IoTDBServer for which the alarm is generated to go to **Dashboard**. Click the drop-down list in the upper right corner of the chart area and choose **Customize** > **Memory**. In the dialog box that is displayed, select **IoTDBServer Heap Memory Resource Percentage**, and click **OK**. Check whether the used non-heap memory of the IoTDBServer process reaches 90% (by default) of the maximum non-heap memory specified for IoTDBServer. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`5 `. - -#. .. _alm-45586__li1141514131368: - - Choose **Cluster** > *Name of the desired cluster* > **Service** > **IoTDB** > **Configuration**, click **All Configurations**, choose **IoTDBServer** > **System**, and increase the value of **-Xmx** in the **GC_OPTS** parameter. - - .. note:: - - - The default value of -**Xmx** is **2G**. - - If this alarm is occasionally generated, increase the value by 0.5 times. If this alarm is frequently generated, double the value. - - In the case of large service volume and high service concurrency, you are advised to add instances. - -#. Check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -**Collect the fault information.** - -5. .. _alm-45586__li4749473185459: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -6. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -7. Click |image1| 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**. - -8. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582927541.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45587_iotdbserver_gc_duration_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45587_iotdbserver_gc_duration_exceeds_the_threshold.rst deleted file mode 100644 index 1d22e63..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45587_iotdbserver_gc_duration_exceeds_the_threshold.rst +++ /dev/null @@ -1,98 +0,0 @@ -:original_name: ALM-45587.html - -.. _ALM-45587: - -ALM-45587 IoTDBServer GC Duration Exceeds the Threshold -======================================================= - -Description ------------ - -The system checks the GC duration of the IoTDBServer process every 60 seconds. This alarm is generated when the GC duration exceeds the threshold (12 seconds by default) for three consecutive times. You can choose **O&M** > **Alarm** > **Threshold Configuration** > *Name of the desired cluster* > **IoTDB** > **GC** > **Total GC duration of IoTDBServer process (IoTDBServer)** to change the threshold. This alarm is cleared when the GC duration is less than the threshold. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45587 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------------+---------------------------------------------------------+ -| Name | Meaning | -+===================+=========================================================+ -| 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 --------------------- - -A long GC duration of the IoTDBServer process may interrupt the services. - -Possible Causes ---------------- - -The heap memory of the IoTDBServer process is overused or inappropriately allocated, causing frequent occurrence of the GC process. - -Procedure ---------- - -**Check the GC duration.** - -#. Log in to FusionInsight Manager and choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**. On the page that is displayed, locate the row containing the alarm whose **Alarm ID** is **45587**, view the role name in **Location**, and check the instance IP address. - -#. Choose **Cluster** > *Name of the desired cluster* > **Service** > **IoTDB** > **Instance**. Click the IoTDBServer for which the alarm is generated to go to **Dashboard**. Click the drop-down list in the upper right corner of the chart area and choose **Customize** > **GC**. In the dialog box that is displayed, select **Garbage Collection (GC) Time of IoTDBServer**, and click **OK**. Check whether the GC time of the IoTDBServer process is greater than 12 seconds. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`5 `. - -#. .. _alm-45587__li1141514131368: - - Choose **Cluster** > *Name of the desired cluster* > **Service** > **IoTDB** > **Configuration**, click **All Configurations**, choose **IoTDBServer** > **System**, and increase the value of **-Xmx** in the **GC_OPTS** parameter. - - .. note:: - - - The default value of -**Xmx** is **2G**. - - If this alarm is occasionally generated, increase the value by 0.5 times. If this alarm is frequently generated, double the value. - - In the case of large service volume and high service concurrency, you are advised to add instances. - -#. Check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -**Collect the fault information.** - -5. .. _alm-45587__li4749473185459: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -6. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -7. Click |image1| 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**. - -8. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532448186.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45588_iotdbserver_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45588_iotdbserver_direct_memory_usage_exceeds_the_threshold.rst deleted file mode 100644 index bfc54d7..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45588_iotdbserver_direct_memory_usage_exceeds_the_threshold.rst +++ /dev/null @@ -1,100 +0,0 @@ -:original_name: ALM-45588.html - -.. _ALM-45588: - -ALM-45588 IoTDBServer Direct Memory Usage Exceeds the Threshold -=============================================================== - -Description ------------ - -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 exceeds the threshold (90% of the maximum memory) for five consecutive times. This alarm is cleared when the IoTDBServer direct memory usage is less than or equal to the threshold. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45588 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------------+---------------------------------------------------------+ -| Name | Meaning | -+===================+=========================================================+ -| 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 --------------------- - -Direct memory overflow may cause service breakdown. - -Possible Causes ---------------- - -The direct memory of the IoTDBServer process is overused or the direct memory is inappropriately allocated. - -Procedure ---------- - -**Check the direct memory usage.** - -#. Log in to FusionInsight Manager and choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**. On the page that is displayed, locate the row containing the alarm whose **Alarm ID** is **45588**, view the role name in **Location**, and check the instance IP address. - -#. Choose **Cluster** > *Name of the desired cluster* > **Service** > **IoTDB** > **Instance**. Click the IoTDBServer for which the alarm is generated to go to **Dashboard**. Click the drop-down list in the upper right corner of the chart area and choose **Customize** > **Memory**. In the dialog box that is displayed, select **IoTDBServer Direct Buffer Resource Percentage**, and click **OK**. - -#. Check whether the direct memory used by the IoTDBServer reaches the threshold (90% of the maximum direct memory by default). - - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45588__li10450762161055: - - On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Service** > **IoTDB** > **Configuration**, click **All Configurations**, choose **IoTDBServer** > **System**, increase the value of **-XX:MaxDirectMemorySize** in the **GC_OPTS** parameter as required, and save the configuration. - - .. note:: - - - If this alarm is generated, the direct memory configured for the IoTDBServer process cannot meet the requirements of the IoTDBServer process. - - You are advised to set **-XX:MaxDirectMemorySize** in **GC_OPTS** to twice the direct memory used by the IoTDBServer process. (You can change the value based on the actual service scenario.) - - To obtain the size of the direct memory used by the IoTDBServer process, choose **Customize** > **Memory** > **IoTDBServer Direct Memory Resource Status**. If **GC_OPTS** does not contain the **-XX:MaxDirectMemorySize** parameter, add it manually. - -#. Restart the affected services or instances and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Collect the fault information.** - -6. .. _alm-45588__d0e43963: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -7. Expand the **Service** drop-down list, and select **IoTDBServer** for the target cluster. - -8. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -9. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583087653.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45589_confignode_heap_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45589_confignode_heap_memory_usage_exceeds_the_threshold.rst deleted file mode 100644 index efa12bb..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45589_confignode_heap_memory_usage_exceeds_the_threshold.rst +++ /dev/null @@ -1,106 +0,0 @@ -:original_name: ALM-45589.html - -.. _ALM-45589: - -ALM-45589 ConfigNode Heap Memory Usage Exceeds the Threshold -============================================================ - -Description ------------ - -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 the threshold (90% of the maximum memory). This alarm is cleared when the heap memory usage of the ConfigNode process is less than the threshold. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45589 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -If the heap memory usage of the ConfigNode process is too high, the performance of the ConfigNode process is affected, and even the ConfigNode process becomes unavailable due to memory overflow. - -Possible Causes ---------------- - -The heap memory configured for the node is improper. As a result, the usage exceeds the threshold. - -Procedure ---------- - -**Check the heap memory configuration.** - -#. .. _alm-45589__li823572385459: - - Log in to FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the real-time alarm list, click |image1| in front of this alarm and view the role name and instance IP address in **Location**. - -#. Choose **Cluster** > **Services** > **IoTDB**. Click **Instance**, click the ConfigNode corresponding to the IP address obtained in :ref:`1 `, and check whether **ConfigNode Heap Memory Usage** on the **Dashboard** tab page reaches the threshold specified for the ConfigNode process. - - If the chart is not displayed, click the drop-down list in the upper right corner of the chart area and choose **Customize** > **Memory**. In the dialog box that is displayed, select **ConfigNode Heap Memory Usage** and click **OK**. - - .. note:: - - You can choose **O&M** > **Alarm** > **Threshold Configuration** > *Name of the desired cluster* > **IoTDB** > **Memory** > **ConfigNode Heap Memory Usage (ConfigNode)** to view the threshold. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45589__li1141514131368: - - Choose **Cluster** > **Services** > **IoTDB**. Click **Configurations** then **All Configurations**, click **ConfigNode**, and choose **System**. Set **-Xmx** in **GC_OPTS** to a larger value and save the configuration. - - .. note:: - - - The default value of -**Xmx** is **2G**. - - If this alarm is occasionally generated, increase the value of **-Xmx** by 0.5 times. If this alarm is frequently generated, double the value of **-Xmx**. - - In the case of large service volume and high service concurrency, you are advised to add instances. - -#. Click **Dashboard**. Click **Restart Service** to restart the IoTDB service for the configuration to take effect. - -#. Wait for about 120 seconds and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Collect fault information.** - -6. .. _alm-45589__li122373616176: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -7. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -8. 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**. - -9. Click |image2| 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**. - -10. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582807589.png -.. |image2| image:: /_static/images/en-us_image_0000001532607642.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45590_confignode_gc_duration_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45590_confignode_gc_duration_exceeds_the_threshold.rst deleted file mode 100644 index 9e9f329..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45590_confignode_gc_duration_exceeds_the_threshold.rst +++ /dev/null @@ -1,115 +0,0 @@ -:original_name: ALM-45590.html - -.. _ALM-45590: - -ALM-45590 ConfigNode GC Duration Exceeds the Threshold -====================================================== - -Description ------------ - -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) for three consecutive times. This alarm is cleared when the GC duration is less than the threshold. - -.. note:: - - You can choose **O&M** > **Alarm** > **Threshold Configuration** > *Name of the desired cluster* > **IoTDB** > **GC** > **Total GC duration of ConfigNode process (ConfigNode)** to increase the threshold by 20% each time. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45590 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------------+---------------------------------------------------------+ -| Name | Meaning | -+===================+=========================================================+ -| 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 --------------------- - -A long GC duration of the ConfigNode process may interrupt services. - -Possible Causes ---------------- - -The heap memory configured on the node is improper. As a result, GC occurs frequently. - -Procedure ---------- - -**Check the heap memory configuration.** - -#. .. _alm-45590__li823572385459: - - Log in to FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the real-time alarm list, click |image1| in the row containing this alarm and view the role name and instance IP address in **Location**. - -#. Choose **Cluster** > **Services** > **IoTDB**. Click **Instance**, click the ConfigNode corresponding to the IP address obtained by :ref:`1 `. Switch to the **Dashboard** tab page, locate the **Total GC Duration of ConfigNode** chart, and check whether the GC duration of the ConfigNode process exceeds the threshold. - - If the GC duration of ConfigNode is not displayed, click the drop-down list in the upper right corner of the chart area and choose **Customize** > **GC**. In the displayed dialog box, select **Total GC Duration of ConfigNode** and click **OK**. - - .. note:: - - You can choose **O&M** > **Alarm** > **Threshold Configuration** > *Name of the desired cluster* > **IoTDB** > **GC** > **Total GC duration of ConfigNode process (ConfigNode)** to view the threshold. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45590__li1141514131368: - - Choose **Cluster** > **Services** > **IoTDB**. Click **Configurations** then **All Configurations**, click **ConfigNode**, and choose **System**. Set **-Xmx** in **GC_OPTS** to a larger value and save the configuration. - - .. note:: - - - The default value of -**Xmx** is **2G**. - - If this alarm is occasionally generated, increase the value by 0.5 times. If this alarm is frequently generated, double the value. - - In the case of large service volume and high service concurrency, you are advised to add instances. - -#. Click **Dashboard**. Click **Restart Service** to restart the IoTDB service for the configuration to take effect. - -#. Check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Collect fault information.** - -6. .. _alm-45590__li4749473185459: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -7. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -8. 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**. - -9. Click |image2| 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**. - -10. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532448138.png -.. |image2| image:: /_static/images/en-us_image_0000001582807569.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45591_confignode_direct_memory_usage_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45591_confignode_direct_memory_usage_exceeds_the_threshold.rst deleted file mode 100644 index 1d6c74c..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45591_confignode_direct_memory_usage_exceeds_the_threshold.rst +++ /dev/null @@ -1,105 +0,0 @@ -:original_name: ALM-45591.html - -.. _ALM-45591: - -ALM-45591 ConfigNode Direct Memory Usage Exceeds the Threshold -============================================================== - -Description ------------ - -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 threshold for five consecutive times. That is, the direct memory configured for ConfigNode cannot meet service requirements. This alarm is cleared when the direct memory usage of ConfigNode is less than or equal to the threshold. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45591 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------------+---------------------------------------------------------+ -| Name | Meaning | -+===================+=========================================================+ -| 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 --------------------- - -Direct memory overflow may cause the IoTDB instance to be unavailable. - -Possible Causes ---------------- - -The direct memory configured for the node is improper. As a result, the usage exceeds the threshold. - -Procedure ---------- - -**Check the direct memory configuration.** - -#. .. _alm-45591__li823572385459: - - Log in to FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the real-time alarm list, click |image1| in front of this alarm and view the role name and instance IP address in **Location**. - -#. Choose **Cluster** > **Services** > **IoTDB**. Click **Instance**, click the ConfigNode corresponding to the IP address obtained in :ref:`1 `, and check whether **ConfigNode Direct Memory Usage** on the **Dashboard** tab page reaches the threshold specified for the ConfigNode process (90% of the maximum direct memory by default). - - If the chart is not displayed, click the drop-down list in the upper right corner of the chart area and choose **Customize** > **Memory**. In the dialog box that is displayed, select **ConfigNode Direct Memory Usage** and click **OK**. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`5 `. - -#. .. _alm-45591__li10450762161055: - - On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Services** > **IoTDB**. Click **Configurations** then **All Configurations**. Click **ConfigNode** and select **System**. Set **-XX:MaxDirectMemorySize** in **GC_OPTS** to a larger value as required and save the configuration. - - .. note:: - - - You are advised to set **-XX:MaxDirectMemorySize** in **GC_OPTS** to twice the direct memory used by the ConfigNode process. (You can change the value based on the actual service scenario.) - - To obtain the size of the direct memory used by the ConfigNode process, choose **Customize** > **Memory** > **ConfigNode Direct Memory Resource Status**. - - If **GC_OPTS** does not contain the **-XX:MaxDirectMemorySize** parameter, add it. - -#. Restart the affected IoTDB service or instances and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -**Collect fault information.** - -5. .. _alm-45591__d0e43963: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -6. Expand the **Service** drop-down list, and select **ConfigNode** for the destination cluster. - -7. 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**. - -8. Click |image2| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -9. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583127501.png -.. |image2| image:: /_static/images/en-us_image_0000001582807809.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45592_iotdbserver_rpc_execution_duration_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45592_iotdbserver_rpc_execution_duration_exceeds_the_threshold.rst deleted file mode 100644 index 05f9497..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45592_iotdbserver_rpc_execution_duration_exceeds_the_threshold.rst +++ /dev/null @@ -1,74 +0,0 @@ -:original_name: ALM-45592.html - -.. _ALM-45592: - -ALM-45592 IoTDBServer RPC Execution Duration Exceeds the Threshold -================================================================== - -Description ------------ - -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 alarm is cleared when the RPC execution time of the IoTDBServer process is less than the threshold. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45592 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -Running performance of the IoTDBServer process is affected. - -Possible Causes ---------------- - -The processing duration of an IoTDBServer RPC request exceeds the threshold. Logs need to be further analyzed to locate the cause. - -Procedure ---------- - -**Collect fault information.** - -#. .. _alm-45592__li17507311599: - - Log in to FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the real-time alarm list, click |image1| in front of this alarm and view the role name and instance IP address in **Location**. - -#. Choose **O&M** > **Log** > **Download**. - -#. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -#. Expand the **Hosts** drop-down list. In the **Select Host** dialog box that is displayed, select the host queried in :ref:`1 `, and click **OK**. - -#. Click |image2| 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**. - -#. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583087297.png -.. |image2| image:: /_static/images/en-us_image_0000001532448158.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45593_iotdbserver_flush_execution_duration_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45593_iotdbserver_flush_execution_duration_exceeds_the_threshold.rst deleted file mode 100644 index 0afbd3f..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45593_iotdbserver_flush_execution_duration_exceeds_the_threshold.rst +++ /dev/null @@ -1,74 +0,0 @@ -:original_name: ALM-45593.html - -.. _ALM-45593: - -ALM-45593 IoTDBServer Flush Execution Duration Exceeds the Threshold -==================================================================== - -Description ------------ - -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. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45593 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -Data write is blocked and the write operation performance is affected. - -Possible Causes ---------------- - -The IoTDB flushing on the node is slow. You need to further analyze logs. - -Procedure ---------- - -**Collect fault information.** - -#. .. _alm-45593__li7938175019120: - - Log in to FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the real-time alarm list, click |image1| in front of this alarm and view the role name and instance IP address in **Location**. - -#. Choose **O&M** > **Log** > **Download**. - -#. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -#. Expand the **Hosts** drop-down list. In the **Select Host** dialog box that is displayed, select the host queried in :ref:`1 `, and click **OK**. - -#. Click |image2| 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**. - -#. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532607638.png -.. |image2| image:: /_static/images/en-us_image_0000001532767370.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45594_iotdbserver_intra-space_merge_duration_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45594_iotdbserver_intra-space_merge_duration_exceeds_the_threshold.rst deleted file mode 100644 index e43d653..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45594_iotdbserver_intra-space_merge_duration_exceeds_the_threshold.rst +++ /dev/null @@ -1,74 +0,0 @@ -:original_name: ALM-45594.html - -.. _ALM-45594: - -ALM-45594 IoTDBServer Intra-Space Merge Duration Exceeds the Threshold -====================================================================== - -Description ------------ - -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. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45594 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -Data write is blocked and the write operation performance is affected. - -Possible Causes ---------------- - -The merge task in the IoTDB space of the node is slow. You need to further analyze logs. - -Procedure ---------- - -**Collect fault information.** - -#. .. _alm-45594__li8994111716159: - - Log in to FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the real-time alarm list, click |image1| in front of this alarm and view the role name and instance IP address in **Location**. - -#. Choose **O&M** > **Log** > **Download**. - -#. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -#. Expand the **Hosts** drop-down list. In the **Select Host** dialog box that is displayed, select the host queried in :ref:`1 `, and click **OK**. - -#. Click |image2| 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**. - -#. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583087629.png -.. |image2| image:: /_static/images/en-us_image_0000001532927642.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45595_iotdbserver_cross-space_merge_duration_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45595_iotdbserver_cross-space_merge_duration_exceeds_the_threshold.rst deleted file mode 100644 index b6084b2..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45595_iotdbserver_cross-space_merge_duration_exceeds_the_threshold.rst +++ /dev/null @@ -1,74 +0,0 @@ -:original_name: ALM-45595.html - -.. _ALM-45595: - -ALM-45595 IoTDBServer Cross-Space Merge Duration Exceeds the Threshold -====================================================================== - -Description ------------ - -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. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45595 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -Data write is blocked and the write operation performance is affected. - -Possible Causes ---------------- - -The IoTDB cross-space merge task on the node is slow. You need to further analyze logs. - -Procedure ---------- - -**Collect fault information.** - -#. .. _alm-45595__li598711218185: - - Log in to FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. In the real-time alarm list, click |image1| in front of this alarm and view the role name and instance IP address in **Location**. - -#. Choose **O&M** > **Log** > **Download**. - -#. Expand the **Service** drop-down list, select **IoTDB** for the target cluster, and click **OK**. - -#. Expand the **Hosts** drop-down list. In the **Select Host** dialog box that is displayed, select the host queried in :ref:`1 `, and click **OK**. - -#. Click |image2| 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**. - -#. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583127317.png -.. |image2| image:: /_static/images/en-us_image_0000001532448190.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45615_cdl_service_unavailable.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45615_cdl_service_unavailable.rst deleted file mode 100644 index adc8db7..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45615_cdl_service_unavailable.rst +++ /dev/null @@ -1,98 +0,0 @@ -:original_name: ALM-45615.html - -.. _ALM-45615: - -ALM-45615 CDL Service Unavailable -================================= - -Description ------------ - -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 the CDL health status is **UP**. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45615 Critical Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -The CDL service is abnormal. You cannot use FusionInsight Manager to perform cluster operations on the CDL service. The CDL service function is unavailable. - -Possible Causes ---------------- - -All CDLService or CDLConnector instances of the CDL service are abnormal, and the Kafka service is unavailable. - -Procedure ---------- - -**Check whether the Kafka service on which the CDL service depends is abnormal.** - -#. On FusionInsight Manager, choose **O&M** > **Alarm** > **Alarms**. - -#. In the alarm list, check whether ALM-38000 Kafka Service Unavailable exists. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`5 `. - -#. .. _alm-45615__li1857611153310: - - Handle the alarm by referring to "ALM-38000 Kafka Service Unavailable". - -#. After the alarm is cleared, wait a few minutes and check whether the alarm HetuServer Service Unavailable is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`5 `. - -**Check whether CDL instances are faulty.** - -5. .. _alm-45615__li1336018269214: - - On FusionInsight Manager, choose **Cluster** > *Name of the desired cluster* > **Service** > **CDL** > **Instance**. - -6. Check whether all CDLService and CDLConnector instances are faulty. - - - If yes, restart the CDL service and choose **Cluster** > *Name of the desired cluster* > **Services** > **CDL** > **More** > **Restart Service**. If the fault persists after the restart, go to :ref:`7 ` and contact O&M personnel to check CDL logs. - - If no, go to :ref:`7 `. - -**Collect the fault information.** - -7. .. _alm-45615__li4749473185459: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -8. Expand the **Service** drop-down list, and select **CDL** for the target cluster. - -9. Click |image1| 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**. - -10. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -After the service is restored, the system automatically clears the alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532767706.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45616_cdl_job_execution_exception.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45616_cdl_job_execution_exception.rst deleted file mode 100644 index cbfd46f..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45616_cdl_job_execution_exception.rst +++ /dev/null @@ -1,107 +0,0 @@ -:original_name: ALM-45616.html - -.. _ALM-45616: - -ALM-45616 CDL Job Execution Exception -===================================== - -Description ------------ - -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 stopped. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45616 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+---------------------------------------------------------------------+ -| Name | Meaning | -+=============+=====================================================================+ -| Source | Specifies the cluster for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| ServiceName | Specifies the service for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| JobName | Specifies the job for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| Username | Specifies the username of the job for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ - -Impact on the System --------------------- - -This alarm has no impact on the system. - -Possible Causes ---------------- - -The CDL task fails to be executed due to incorrect parameter settings or other reasons. On the **Job Management** page of the CDL web UI, locate the row where the job is located and click **Failed**/**Abnormal running** in the **Status** column to view the failure cause, or view the failure cause in the logs. - -Procedure ---------- - -#. Log in to FusionInsight Manager as a user who has the CDL job creation or administrator permission. - -#. .. _alm-45616__li7271425123815: - - Choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**, click |image1| in the row where **Alarm ID** is **45616**, and view the name of the job for which this alarm is generated in **Location**. - -#. Choose **Cluster** > **Services** > **CDL** and click the link next to **CDLService UI** to go to the CDL web UI. - -#. Locate the row where the failed job is located based on the job name obtained in :ref:`2 `, and click **Abnormal running** or **Failed** in the **Status** column. - - |image2| - -#. On the page that is displayed, view the error information and rectify the fault. For example, :ref:`Figure 1 ` shows that the task running on Yarn is manually killed. For details, see trace error information, as shown in :ref:`Figure 2 `. - - .. _alm-45616__fig1327218258386: - - .. figure:: /_static/images/en-us_image_0000001582807901.png - :alt: **Figure 1** CDL job exception - - **Figure 1** CDL job exception - - .. _alm-45616__fig16272152503813: - - .. figure:: /_static/images/en-us_image_0000001532927626.png - :alt: **Figure 2** Trace error information - - **Figure 2** Trace error information - -#. Rectify the fault based on the error information, execute the task again, and check whether the task can be executed successfully. - - - If yes, no further action is required. - - If no, go to :ref:`7 `. - -**Collect the fault information.** - -7. .. _alm-45616__li52711725153817: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -8. Select **CDL** in the required cluster for **Service**. - -9. Click |image3| 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**. - -10. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -After the job is successfully restored or stopped, the alarm is cleared if it has been reported. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582927849.png -.. |image2| image:: /_static/images/en-us_image_0000001532767690.png -.. |image3| image:: /_static/images/en-us_image_0000001583127597.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45617_data_queued_in_the_cdl_replication_slot_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45617_data_queued_in_the_cdl_replication_slot_exceeds_the_threshold.rst deleted file mode 100644 index 155b071..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45617_data_queued_in_the_cdl_replication_slot_exceeds_the_threshold.rst +++ /dev/null @@ -1,108 +0,0 @@ -:original_name: ALM-45617.html - -.. _ALM-45617: - -ALM-45617 Data Queued in the CDL Replication Slot Exceeds the Threshold -======================================================================= - -Description ------------ - -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 data queued in the replication slot configured for a CDL job exceeds the threshold every 5 minutes. This alarm is generated when the amount of data queued in the replication slot exceeds the threshold. This alarm is cleared when the number of data queued in the replication slot falls below the threshold. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45617 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+---------------------------------------------------------------------------+ -| Name | Meaning | -+=============+===========================================================================+ -| Source | Specifies the cluster for which the alarm is generated. | -+-------------+---------------------------------------------------------------------------+ -| ServiceName | Specifies the service for which the alarm is generated. | -+-------------+---------------------------------------------------------------------------+ -| JobName | Specifies the job for which the alarm is generated. | -+-------------+---------------------------------------------------------------------------+ -| DBName | Specifies the database for which the alarm is generated. | -+-------------+---------------------------------------------------------------------------+ -| SlotName | Specifies the database replication slot for which the alarm is generated. | -+-------------+---------------------------------------------------------------------------+ -| Lag | Specifies the data queued in the slot. | -+-------------+---------------------------------------------------------------------------+ - -Impact on the System --------------------- - -WALs are continuously accumulated in the source PostgreSQL database, causing the disk space of the source database to be used up. - -Possible Causes ---------------- - -The CDL job is abnormal, and data processing stops; the source database is updated quickly, and CDL data processing is slow. - -Procedure ---------- - -#. Log in to FusionInsight Manager as a user who has the CDL job creation or administrator permission. - -#. .. _alm-45617__li118681057135018: - - Choose **O&M**. In the navigation pane on the left, choose **Alarm** > **Alarms**, click |image1| in the row where **Alarm ID** is **45617**, and view the name of the job for which this alarm is generated in **Location**. - -#. Check whether **ALM-45616 CDL Job Execution Exception** is displayed in the alarm list. - - - If yes, handle the alarm by performing operations provided for **ALM-45616 CDL Job Execution Exception**. - - If no, go to :ref:`4 `. - -#. .. _alm-45617__li28682575508: - - Choose **Cluster** > **Services** > **CDL**. Click the link next to **CDLService UI** to go to the CDL web UI and check whether the job is displayed in the job list based on its name obtained in :ref:`2 `. - - - If yes, check whether the job is abnormal. - - - If it is abnormal, go to :ref:`5 `. - - If it is not, data processing is slow. Contact O&M personnel. - - - If no, go to :ref:`7 `. - -#. .. _alm-45617__li15868185712504: - - Click **Abnormal** or **Failed** in the row where the job is located and rectify the fault based on the error information displayed on the page. - -#. After rectifying the fault, run the job again and check whether the job can be executed successfully. - - - If yes, no further action is required. - - If no, go to :ref:`7 `. - -**Collect the fault information.** - -7. .. _alm-45617__li1486755735016: - - On FusionInsight Manager, choose **O&M**. In the navigation pane on the left, choose **Log** > **Download**. - -8. Select **CDL** in the required cluster for **Service**. - -9. Click |image2| 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**. - -10. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is cleared when the amount of data queued in the replication slot is less than the threshold. You do not need to manually clear the alarm. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001582927521.png -.. |image2| image:: /_static/images/en-us_image_0000001582807573.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45635_flinkserver_job_execution_failure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45635_flinkserver_job_execution_failure.rst deleted file mode 100644 index 4a9062f..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45635_flinkserver_job_execution_failure.rst +++ /dev/null @@ -1,112 +0,0 @@ -:original_name: ALM-45635.html - -.. _ALM-45635: - -ALM-45635 FlinkServer Job Execution Failure -=========================================== - -This section applies to MRS 3.2.0 or later. - -Description ------------ - -The system checks whether FlinkServer jobs fail to be executed every 10 seconds. This alarm is generated when a FlinkServer job fails. This alarm is cleared when the job is successfully restarted. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45635 Major Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -Source Specifies the cluster for which the alarm is generated. -ServiceName Specifies the service for which the alarm is generated. -JobName Specifies the job for which the alarm is generated. -=========== ======================================================= - -Impact on the System --------------------- - -This alarm has no impact on the system. - -Possible Causes ---------------- - -You can view failure causes in specific logs. - -Procedure ---------- - -#. Log in to Manager as a user who has the FlinkServer management permission. - -#. Choose **Cluster** > **Services** > **Yarn** and click the link next to **ResourceManager WebUI** to go to the Yarn page. - -#. Locate the failed job based on its name displayed in **Location**, search for and record the application ID of the failed job, and check whether the job logs are available on the Yarn page. - - - .. figure:: /_static/images/en-us_image_0000001583127393.png - :alt: **Figure 1** Application ID of a job - - **Figure 1** Application ID of a job - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45635__li109051158191: - - Click the application ID of the failed job to go to the job page. - - a. Click **Logs** in the **Logs** column to view JobManager logs. - - - .. figure:: /_static/images/en-us_image_0000001582807701.png - :alt: **Figure 2** Clicking Logs - - **Figure 2** Clicking Logs - - b. Click the ID in the **Attempt ID** column and click **Logs** in the **Logs** column to view TaskManager logs. - - - .. figure:: /_static/images/en-us_image_0000001583127389.png - :alt: **Figure 3** Clicking the ID in the Attempt ID column - - **Figure 3** Clicking the ID in the Attempt ID column - - - .. figure:: /_static/images/en-us_image_0000001532927426.png - :alt: **Figure 4** Clicking Logs - - **Figure 4** Clicking Logs - - .. note:: - - You can also log in to Manager as a user who has the FlinkServer management permission, choose **Cluster** > **Services** > **Flink**, click the link next to **Flink WebUI**. On the displayed Flink web UI, click **Job Management** and choose **More** > **Job Monitoring** in the **Operation** column to view the TaskManager logs. - -#. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. No further action is required. - -**If logs are unavailable on the Yarn page, download logs from HDFS.** - -6. .. _alm-45635__li5902415141913: - - On Manager, choose **Cluster** > **Services** > **HDFS**, click the link next to **NameNode WebUI** to go to the HDFS page, select **Utilities** > **Browse the file system**, and download logs in the **/tmp/logs/**\ *User name*\ **/logs/**\ *Application ID of the failed job* directory. - -7. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. - -Alarm Clearing --------------- - -After the job is successfully restarted, the alarm is cleared if it has been reported. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45636_flink_job_checkpoints_keep_failing.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45636_flink_job_checkpoints_keep_failing.rst deleted file mode 100644 index 04d6dca..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45636_flink_job_checkpoints_keep_failing.rst +++ /dev/null @@ -1,116 +0,0 @@ -:original_name: ALM-45636-1.html - -.. _ALM-45636-1: - -ALM-45636 Flink Job Checkpoints Keep Failing -============================================ - -This section applies to MRS 3.2.0 or later. - -Description ------------ - -The system checks the number of consecutive checkpoint failures based on the configured alarm checking interval. This alarm is generated when the number of consecutive checkpoint failures of a FlinkServer job reaches the configured threshold. This alarm is cleared when checkpoints are recovered or the job is successfully restarted. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45636 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+---------------------------------------------------------------------+ -| Name | Meaning | -+=============+=====================================================================+ -| Source | Specifies the cluster for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| ServiceName | Specifies the service for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| JobName | Specifies the job for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| Username | Specifies the username of the job for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ - -Impact on the System --------------------- - -This alarm has no impact on the system. - -Possible Causes ---------------- - -You can view failure causes in specific logs. - -Procedure ---------- - -#. Log in to Manager as a user who has the FlinkServer management permission. - -#. Choose **Cluster** > **Services** > **Yarn** and click the link next to **ResourceManager WebUI** to go to the Yarn page. - -#. Locate the failed job based on its name displayed in **Location**, search for and record the application ID of the failed job, and check whether the job logs are available on the Yarn page. - - - .. figure:: /_static/images/en-us_image_0000001583127445.png - :alt: **Figure 1** Application ID of a job - - **Figure 1** Application ID of a job - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45636-1__en-us_topic_0000001430978870_en-us_topic_0000001396557914_li109051158191: - - Click the application ID of the failed job to go to the job page. - - a. Click **Logs** in the **Logs** column to view JobManager logs. - - - .. figure:: /_static/images/en-us_image_0000001532448322.png - :alt: **Figure 2** Clicking Logs - - **Figure 2** Clicking Logs - - b. Click the ID in the **Attempt ID** column and click **Logs** in the **Logs** column to view TaskManager logs. - - - .. figure:: /_static/images/en-us_image_0000001582807753.png - :alt: **Figure 3** Clicking the ID in the Attempt ID column - - **Figure 3** Clicking the ID in the Attempt ID column - - - .. figure:: /_static/images/en-us_image_0000001532767546.png - :alt: **Figure 4** Clicking Logs - - **Figure 4** Clicking Logs - - .. note:: - - You can also log in to Manager as a user who has the FlinkServer management permission, choose **Cluster** > **Services** > **Flink**, click the link next to **Flink WebUI**. On the displayed Flink web UI, click **Job Management** and choose **More** > **Job Monitoring** in the **Operation** column to view the TaskManager logs. - -#. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. No further action is required. - -**If logs are unavailable on the Yarn page, download logs from HDFS.** - -6. .. _alm-45636-1__en-us_topic_0000001430978870_en-us_topic_0000001396557914_li5902415141913: - - On Manager, choose **Cluster** > **Services** > **HDFS**, click the link next to **NameNode WebUI** to go to the HDFS page, select **Utilities** > **Browse the file system**, and download logs in the **/tmp/logs/**\ *User name*\ **/logs/**\ *Application ID of the failed job* directory. - -7. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. - -Alarm Clearing --------------- - -This alarm is cleared when Flink job checkpoints are recovered or the job is successfully restarted. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45636_flinkserver_job_checkpoints_keep_failing.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45636_flinkserver_job_checkpoints_keep_failing.rst deleted file mode 100644 index 2eb1a6c..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45636_flinkserver_job_checkpoints_keep_failing.rst +++ /dev/null @@ -1,112 +0,0 @@ -:original_name: ALM-45636.html - -.. _ALM-45636: - -ALM-45636 FlinkServer Job Checkpoints Keep Failing -================================================== - -This section applies to MRS 3.2.0 or later. - -Description ------------ - -The system checks the number of consecutive checkpoint failures based on the configured alarm checking interval. This alarm is generated when the number of consecutive checkpoint failures of a FlinkServer job reaches the configured threshold. This alarm is cleared when checkpoints are recovered or the job is successfully restarted. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45636 Minor Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -Source Specifies the cluster for which the alarm is generated. -ServiceName Specifies the service for which the alarm is generated. -JobName Specifies the job for which the alarm is generated. -=========== ======================================================= - -Impact on the System --------------------- - -This alarm has no impact on the system. - -Possible Causes ---------------- - -You can view failure causes in specific logs. - -Procedure ---------- - -#. Log in to Manager as a user who has the FlinkServer management permission. - -#. Choose **Cluster** > **Services** > **Yarn** and click the link next to **ResourceManager WebUI** to go to the Yarn page. - -#. Locate the failed job based on its name displayed in **Location**, search for and record the application ID of the failed job, and check whether the job logs are available on the Yarn page. - - - .. figure:: /_static/images/en-us_image_0000001583127393.png - :alt: **Figure 1** Application ID of a job - - **Figure 1** Application ID of a job - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45636__en-us_topic_0000001150940918_li109051158191: - - Click the application ID of the failed job to go to the job page. - - a. Click **Logs** in the **Logs** column to view JobManager logs. - - - .. figure:: /_static/images/en-us_image_0000001582807701.png - :alt: **Figure 2** Clicking Logs - - **Figure 2** Clicking Logs - - b. Click the ID in the **Attempt ID** column and click **Logs** in the **Logs** column to view TaskManager logs. - - - .. figure:: /_static/images/en-us_image_0000001583127389.png - :alt: **Figure 3** Clicking the ID in the Attempt ID column - - **Figure 3** Clicking the ID in the Attempt ID column - - - .. figure:: /_static/images/en-us_image_0000001532927426.png - :alt: **Figure 4** Clicking Logs - - **Figure 4** Clicking Logs - - .. note:: - - You can also log in to Manager as a user who has the FlinkServer management permission, choose **Cluster** > **Services** > **Flink**, click the link next to **Flink WebUI**. On the displayed Flink web UI, click **Job Management** and choose **More** > **Job Monitoring** in the **Operation** column to view the TaskManager logs. - -#. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. No further action is required. - -**If logs are unavailable on the Yarn page, download logs from HDFS.** - -6. .. _alm-45636__en-us_topic_0000001150940918_li5902415141913: - - On Manager, choose **Cluster** > **Services** > **HDFS**, click the link next to **NameNode WebUI** to go to the HDFS page, select **Utilities** > **Browse the file system**, and download logs in the **/tmp/logs/**\ *User name*\ **/logs/**\ *Application ID of the failed job* directory. - -7. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. - -Alarm Clearing --------------- - -This alarm is cleared when FlinkServer job checkpoints are recovered or the job is successfully restarted. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45637_flinkserver_task_is_continuously_under_back_pressure.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45637_flinkserver_task_is_continuously_under_back_pressure.rst deleted file mode 100644 index 49553a5..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45637_flinkserver_task_is_continuously_under_back_pressure.rst +++ /dev/null @@ -1,112 +0,0 @@ -:original_name: ALM-45637.html - -.. _ALM-45637: - -ALM-45637 FlinkServer Task Is Continuously Under Back Pressure -============================================================== - -This section applies to MRS 3.1.2 or later. - -Description ------------ - -The system checks the back pressure duration of FlinkServer tasks based on the configured alarm checking interval. This alarm is generated when the back pressure duration of a FlinkServer task reaches the configured threshold. This alarm is cleared when the task back pressure is recovered or the job is successfully restarted. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45637 Minor Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -Source Specifies the cluster for which the alarm is generated. -ServiceName Specifies the service for which the alarm is generated. -JobName Specifies the job for which the alarm is generated. -=========== ======================================================= - -Impact on the System --------------------- - -This alarm has no impact on the system. - -Possible Causes ---------------- - -You can view the causes in the specific logs. - -Procedure ---------- - -#. Log in to Manager as a user who has the FlinkServer management permission. - -#. Choose **Cluster** > **Services** > **Yarn** and click the link next to **ResourceManager WebUI** to go to the Yarn page. - -#. Locate the failed job based on its name displayed in **Location**, search for and record the application ID of the failed job, and check whether the job logs are available on the Yarn page. - - - .. figure:: /_static/images/en-us_image_0000001583127393.png - :alt: **Figure 1** Application ID of a job - - **Figure 1** Application ID of a job - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45637__en-us_topic_0000001150940918_li109051158191: - - Click the application ID of the failed job to go to the job page. - - a. Click **Logs** in the **Logs** column to view JobManager logs. - - - .. figure:: /_static/images/en-us_image_0000001582807701.png - :alt: **Figure 2** Clicking Logs - - **Figure 2** Clicking Logs - - b. Click the ID in the **Attempt ID** column and click **Logs** in the **Logs** column to view TaskManager logs. - - - .. figure:: /_static/images/en-us_image_0000001583127389.png - :alt: **Figure 3** Clicking the ID in the Attempt ID column - - **Figure 3** Clicking the ID in the Attempt ID column - - - .. figure:: /_static/images/en-us_image_0000001532927426.png - :alt: **Figure 4** Clicking Logs - - **Figure 4** Clicking Logs - - .. note:: - - You can also log in to Manager as a user who has the FlinkServer management permission, choose **Cluster** > **Services** > **Flink**, click the link next to **Flink WebUI**. On the displayed Flink web UI, click **Job Management** and choose **More** > **Job Monitoring** in the **Operation** column to view the TaskManager logs. - -#. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. No further action is required. - -**If logs are unavailable on the Yarn page, download logs from HDFS.** - -6. .. _alm-45637__en-us_topic_0000001150940918_li5902415141913: - - On Manager, choose **Cluster** > **Services** > **HDFS**, click the link next to **NameNode WebUI** to go to the HDFS page, select **Utilities** > **Browse the file system**, and download logs in the **/tmp/logs/**\ *User name*\ **/logs/**\ *Application ID of the failed job* directory. - -7. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. - -Alarm Clearing --------------- - -This alarm is cleared when FlinkServer task back pressure is recovered or the job is successfully restarted. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45638_number_of_restarts_after_flink_job_failures_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45638_number_of_restarts_after_flink_job_failures_exceeds_the_threshold.rst deleted file mode 100644 index 26afccf..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45638_number_of_restarts_after_flink_job_failures_exceeds_the_threshold.rst +++ /dev/null @@ -1,116 +0,0 @@ -:original_name: ALM-45638-1.html - -.. _ALM-45638-1: - -ALM-45638 Number of Restarts After Flink Job Failures Exceeds the Threshold -=========================================================================== - -This section applies to MRS 3.2.0 or later. - -Description ------------ - -The system checks the number of Flink job restarts based on the alarm checking interval. This alarm is generated when the number exceeds the configured threshold. This alarm is cleared when the job is restarted. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45638 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+---------------------------------------------------------------------+ -| Name | Meaning | -+=============+=====================================================================+ -| Source | Specifies the cluster for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| ServiceName | Specifies the service for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| JobName | Specifies the job for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ -| Username | Specifies the username of the job for which the alarm is generated. | -+-------------+---------------------------------------------------------------------+ - -Impact on the System --------------------- - -This alarm has no impact on the system. - -Possible Causes ---------------- - -You can view the causes in the specific logs. - -Procedure ---------- - -#. Log in to Manager as a user who has the FlinkServer management permission. - -#. Choose **Cluster** > **Services** > **Yarn** and click the link next to **ResourceManager WebUI** to go to the Yarn page. - -#. Locate the failed job based on its name displayed in **Location**, search for and record the application ID of the failed job, and check whether the job logs are available on the Yarn page. - - - .. figure:: /_static/images/en-us_image_0000001532767354.png - :alt: **Figure 1** Application ID of a job - - **Figure 1** Application ID of a job - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45638-1__en-us_topic_0000001480898081_en-us_topic_0000001396557914_li109051158191: - - Click the application ID of the failed job to go to the job page. - - a. Click **Logs** in the **Logs** column to view JobManager logs. - - - .. figure:: /_static/images/en-us_image_0000001532927290.png - :alt: **Figure 2** Clicking Logs - - **Figure 2** Clicking Logs - - b. Click the ID in the **Attempt ID** column and click **Logs** in the **Logs** column to view TaskManager logs. - - - .. figure:: /_static/images/en-us_image_0000001532607622.png - :alt: **Figure 3** Clicking the ID in the Attempt ID column - - **Figure 3** Clicking the ID in the Attempt ID column - - - .. figure:: /_static/images/en-us_image_0000001583087273.png - :alt: **Figure 4** Clicking Logs - - **Figure 4** Clicking Logs - - .. note:: - - You can also log in to Manager as a user who has the FlinkServer management permission, choose **Cluster** > **Services** > **Flink**, click the link next to **Flink WebUI**. On the displayed Flink web UI, click **Job Management** and choose **More** > **Job Monitoring** in the **Operation** column to view the TaskManager logs. - -#. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. No further action is required. - -**If logs are unavailable on the Yarn page, download logs from HDFS.** - -6. .. _alm-45638-1__en-us_topic_0000001480898081_en-us_topic_0000001396557914_li5902415141913: - - On Manager, choose **Cluster** > **Services** > **HDFS**, click the link next to **NameNode WebUI** to go to the HDFS page, select **Utilities** > **Browse the file system**, and download logs in the **/tmp/logs/**\ *User name*\ **/logs/**\ *Application ID of the failed job* directory. - -7. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. - -Alarm Clearing --------------- - -This alarm is cleared when the Flink job is successfully restarted. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45638_number_of_restarts_after_flinkserver_job_failures_exceeds_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45638_number_of_restarts_after_flinkserver_job_failures_exceeds_the_threshold.rst deleted file mode 100644 index 09edf4e..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45638_number_of_restarts_after_flinkserver_job_failures_exceeds_the_threshold.rst +++ /dev/null @@ -1,112 +0,0 @@ -:original_name: ALM-45638.html - -.. _ALM-45638: - -ALM-45638 Number of Restarts After FlinkServer Job Failures Exceeds the Threshold -================================================================================= - -This section applies to MRS 3.1.2 or later. - -Description ------------ - -The system checks the number of FlinkServer job restarts based on the alarm checking interval. This alarm is generated when the number exceeds the configured threshold. This alarm is cleared when the job is restarted. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45638 Minor Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -Source Specifies the cluster for which the alarm is generated. -ServiceName Specifies the service for which the alarm is generated. -JobName Specifies the job for which the alarm is generated. -=========== ======================================================= - -Impact on the System --------------------- - -This alarm has no impact on the system. - -Possible Causes ---------------- - -You can view the causes in the specific logs. - -Procedure ---------- - -#. Log in to Manager as a user who has the FlinkServer management permission. - -#. Choose **Cluster** > **Services** > **Yarn** and click the link next to **ResourceManager WebUI** to go to the Yarn page. - -#. Locate the failed job based on its name displayed in **Location**, search for and record the application ID of the failed job, and check whether the job logs are available on the Yarn page. - - - .. figure:: /_static/images/en-us_image_0000001583127393.png - :alt: **Figure 1** Application ID of a job - - **Figure 1** Application ID of a job - - If yes, go to :ref:`4 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45638__en-us_topic_0000001150940918_li109051158191: - - Click the application ID of the failed job to go to the job page. - - a. Click **Logs** in the **Logs** column to view JobManager logs. - - - .. figure:: /_static/images/en-us_image_0000001582807701.png - :alt: **Figure 2** Clicking Logs - - **Figure 2** Clicking Logs - - b. Click the ID in the **Attempt ID** column and click **Logs** in the **Logs** column to view TaskManager logs. - - - .. figure:: /_static/images/en-us_image_0000001583127389.png - :alt: **Figure 3** Clicking the ID in the Attempt ID column - - **Figure 3** Clicking the ID in the Attempt ID column - - - .. figure:: /_static/images/en-us_image_0000001532927426.png - :alt: **Figure 4** Clicking Logs - - **Figure 4** Clicking Logs - - .. note:: - - You can also log in to Manager as a user who has the FlinkServer management permission, choose **Cluster** > **Services** > **Flink**, click the link next to **Flink WebUI**. On the displayed Flink web UI, click **Job Management** and choose **More** > **Job Monitoring** in the **Operation** column to view the TaskManager logs. - -#. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. No further action is required. - -**If logs are unavailable on the Yarn page, download logs from HDFS.** - -6. .. _alm-45638__en-us_topic_0000001150940918_li5902415141913: - - On Manager, choose **Cluster** > **Services** > **HDFS**, click the link next to **NameNode WebUI** to go to the HDFS page, select **Utilities** > **Browse the file system**, and download logs in the **/tmp/logs/**\ *User name*\ **/logs/**\ *Application ID of the failed job* directory. - -7. View the logs of the failed job to rectify the fault, or contact the O&M personnel personnel and send the collected fault logs. - -Alarm Clearing --------------- - -This alarm is cleared when the FlinkServer job is successfully restarted. - -Related Information -------------------- - -None diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45640_flinkserver_heartbeat_interruption_between_the_active_and_standby_nodes.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45640_flinkserver_heartbeat_interruption_between_the_active_and_standby_nodes.rst deleted file mode 100644 index a1964cd..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45640_flinkserver_heartbeat_interruption_between_the_active_and_standby_nodes.rst +++ /dev/null @@ -1,139 +0,0 @@ -:original_name: ALM-45640.html - -.. _ALM-45640: - -ALM-45640 FlinkServer Heartbeat Interruption Between the Active and Standby Nodes -================================================================================= - -This section applies to MRS 3.2.0 or later. - -Description ------------ - -This alarm is generated when the FlinkServer active node or standby node does not receive heartbeat messages from the peer for 30 seconds (heartbeat interruption duration configured in keepalive). - -This alarm is cleared when the heartbeat recovers. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45640 Minor Yes -======== ============== ========== - -Parameters ----------- - -=========== ======================================================= -Name Meaning -=========== ======================================================= -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. -=========== ======================================================= - -Impact on the System --------------------- - -During the FlinkServer heartbeat interruption, only one node can provide the service. If this node is faulty, no standby node is available for failover and the service is unavailable. - -Possible Causes ---------------- - -- The active or standby FlinkServer instance is in the stopped state. -- The NIC of the floating IP address of the HA system used by the FlinkServer node is incorrectly configured. FlinkServer fails to be started. -- The link between the active and standby FlinkServer nodes is abnormal. - -Procedure ---------- - -**Check the status of the active and standby FlinkServer instances.** - -#. Log in to FusionInsight Manager, choose **Cluster** > **Services** > **Flink** > **Instance**, and check the state of FlinkServer is normal. - - - If yes, go to :ref:`3 `. - - If no, go to :ref:`2 `. - -#. .. _alm-45640__li6097724617158: - - Select the abnormal FlinkServer instance and start the instance. After the instance is started, check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`3 `. - -**Check whether the link between the standby FlinkServer nodes is normal.** - -3. .. _alm-45640__li1192430217158: - - Choose **Cluster** > **Services** > **Flink** > **Instance**, and check the two service IP addresses of FlinkServer. - -4. Log in to the server where the abnormal FlinkServer instance locates as the **root** user. - -5. Run the following command to check whether the server of the other FlinkServer instance is reachable: - - **ping** *IP address of the other FlinkServer instance* - - - If yes, go to :ref:`8 `. - - If no, go to :ref:`6 `. - -6. .. _alm-45640__li6879155662418: - - Ask the network administrator to handle the network exception. - -7. Check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`8 `. - -**Check whether the logs of the node where the abnormal FlinkServer instance locates contains error information.** - -8. .. _alm-45640__li1856073032510: - - Log in to the server where the abnormal FlinkServer instance locates as the **root** user. - -9. Open the log file in the default directory **/var/log/Bigdata/flink/flinkserver/prestart.log** and check whether there is error message **Float ip** *x.x.x.x* **is invalid**. - - - If yes, go to :ref:`10 `. - - If no, go to :ref:`12 `. - -10. .. _alm-45640__li1885369317158: - - On FusionInsight Manager, choose **Cluster** > **Services** > **Flink** > **Configurations** > **All Configurations** and search for **flink.ha.floatip**. Change the parameter value to the correct floating IP address, save the configuration, and restart the Flink service. - - .. note:: - - Contact the network engineer to obtain the new floating IP address. - -11. Check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`12 `. - -**Collect the fault information.** - -12. .. _alm-45640__li5131512717158: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -13. Select the Flink service in the required cluster for **Service**. - -14. 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**. - -15. Click |image1| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -16. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001583127285.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45641_data_synchronization_exception_between_the_active_and_standby_flinkserver_nodes.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45641_data_synchronization_exception_between_the_active_and_standby_flinkserver_nodes.rst deleted file mode 100644 index 82c40ed..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/alm-45641_data_synchronization_exception_between_the_active_and_standby_flinkserver_nodes.rst +++ /dev/null @@ -1,197 +0,0 @@ -:original_name: ALM-45641.html - -.. _ALM-45641: - -ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes -========================================================================================= - -This section applies to MRS 3.2.0 or later. - -Description ------------ - -The system checks data synchronization between the active and standby FlinkServer nodes every 60 seconds. This alarm is generated when the standby FlinkServer node fails to synchronize files with the active FlinkServer node. - -This alarm is cleared when the standby FlinkServer synchronizes files with the active FlinkServer. - -Attribute ---------- - -======== ============== ========== -Alarm ID Alarm Severity Auto Clear -======== ============== ========== -45641 Major Yes -======== ============== ========== - -Parameters ----------- - -+-------------+-------------------------------------------------------------------+ -| Name | Meaning | -+=============+===================================================================+ -| 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 --------------------- - -Because the configuration files on the standby FlinkServer are not updated, some configurations will be lost after an active/standby switchover. FlinkServer and some components may not run properly. - -Possible Causes ---------------- - -- The link between the active and standby FlinkServer nodes is interrupted. -- The synchronization file does not exist or the file permission is required. - -Procedure ---------- - -**Check whether the network between the active and standby FlinkServer is in normal state.** - -#. On FusionInsight Manager, choose **Cluster** > **Services** > **ClickHouse** > **Instance**. View and record the IP addresses of active and standby FlinkServer. - -#. Log in to the active FlinkServer node as the **root** user. - -#. Run the following command to check whether the standby FlinkServer is reachable: - - **ping** *IP address of the standby FlinkServer* - - - If yes, go to :ref:`6 `. - - If no, go to :ref:`4 `. - -#. .. _alm-45641__li63406959171631: - - Contact the network administrator to check whether the network is faulty. - - - If yes, go to :ref:`5 `. - - If no, go to :ref:`6 `. - -#. .. _alm-45641__li19595462171631: - - Rectify the network fault and check whether the alarm is cleared from the alarm list. - - - If yes, no further action is required. - - If no, go to :ref:`6 `. - -**Check whether the storage space of the /srv/BigData/LocalBackup directory is full.** - -6. .. _alm-45641__li18750195794719: - - Run the following command to check whether the storage space of the **/srv/BigData/LocalBackup** directory is full: - - **df -hl /srv/BigData/LocalBackup** - - - If yes, go to :ref:`7 `. - - If no, go to :ref:`10 `. - -7. .. _alm-45641__li7740734122412: - - Run the following command to clear unnecessary backup files: - - **rm -rf** *Directory to be cleared* - - The following are two examples: - - **rm -rf** **/srv/BigData/LocalBackup/0/default-oms_20191211143443** - -8. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Backup Management**. - - In the **Operation** column of the backup task, click **Configure** and change the value of **Maximum Number of Backup Copies** to reduce the number of backup file sets. - -9. Wait for 1 minute and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`10 `. - -**Check whether the synchronization file exists and whether the file permission is valid.** - -10. .. _alm-45641__li13330195272015: - - Run the following command to check whether the synchronization file exists: - - **find /srv/BigData/ -name "sed*"** - - **find /opt -name "sed*"** - - - If yes, go to :ref:`11 `. - - If no, go to :ref:`12 `. - -11. .. _alm-45641__li6383747162115: - - Run the following command to check the synchronization file information and permission queried in :ref:`10 `: - - **ll** *Path of the file you want to search for* - - - If the file size is 0 and all values in the permission column are -, the file is a junk file. Run the following command to delete it: - - **rm -rf** *Files to be deleted* - - Wait for several minutes and check whether the alarm is cleared. If the alarm persists, go to :ref:`12 `. - - - If the file size is not 0, go to :ref:`12 `. - -12. .. _alm-45641__li210153713915: - - View the log file generated when the alarm is reported. - - a. Run the following command to go to the HA run log file path of the current cluster: - - **cd /var/log/Bigdata/flink/flinkserver/ha/runlog** - - b. Decompress log file and view the logs generated when the alarm is reported. - - For example, if the name of the file is **ha.log.2021-03-22_12-00-07.gz**, run the following command: - - **gunzip** *ha.log.2021-03-22_12-00-07.gz* - - **vi** *ha.log.2021-03-22_12-00-07* - - Check whether error information is displayed before and after the alarm generation time in the logs. - - - If it is displayed, rectify the fault based on the error information. Go to :ref:`13 `. - - For example, if the following error information is displayed, the directory permission is required. In this case, obtain the directory permission that is the same as the permission on a normal node. - - |image1| - - - If no, go to :ref:`14 `. - -13. .. _alm-45641__li259318693811: - - Wait for about 10 minutes and check whether the alarm is cleared. - - - If yes, no further action is required. - - If no, go to :ref:`14 `. - -**Collect fault information.** - -14. .. _alm-45641__li42141433171631: - - On FusionInsight Manager, choose **O&M** > **Log** > **Download**. - -15. Select FlinkServer information from **Services** and click **OK**. - -16. 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**. - -17. Click |image2| in the upper right corner, and set **Start Date** and **End Date** for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click **Download**. - -18. Contact O&M personnel and provide the collected logs. - -Alarm Clearing --------------- - -This alarm is automatically cleared after the fault is rectified. - -Related Information -------------------- - -None - -.. |image1| image:: /_static/images/en-us_image_0000001532767430.png -.. |image2| image:: /_static/images/en-us_image_0000001583127333.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/index.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/index.rst index ce851b5..1f4d5a8 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/index.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/alarm_reference_applicable_to_mrs_3.x/index.rst @@ -12,18 +12,16 @@ Alarm Reference (Applicable to MRS 3.\ *x*) - :ref:`ALM-12007 Process Fault ` - :ref:`ALM-12010 Manager Heartbeat Interruption Between the Active and Standby Nodes ` - :ref:`ALM-12011 Manager Data Synchronization Exception Between the Active and Standby Nodes ` -- :ref:`ALM-12012 NTP Service Is Abnormal ` - :ref:`ALM-12014 Partition Lost ` - :ref:`ALM-12015 Partition Filesystem Readonly ` - :ref:`ALM-12016 CPU Usage Exceeds the Threshold ` - :ref:`ALM-12017 Insufficient Disk Capacity ` - :ref:`ALM-12018 Memory Usage Exceeds the Threshold ` - :ref:`ALM-12027 Host PID Usage Exceeds the Threshold ` -- :ref:`ALM-12028 Number of Processes in the D State and Z State on a Host Exceeds the Threshold ` +- :ref:`ALM-12028 Number of Processes in the D State on a Host Exceeds the Threshold ` - :ref:`ALM-12033 Slow Disk Fault ` - :ref:`ALM-12034 Periodical Backup Failure ` - :ref:`ALM-12035 Unknown Data Status After Recovery Task Failure ` -- :ref:`ALM-12037 NTP Server Abnormal ` - :ref:`ALM-12038 Monitoring Indicator Dumping Failure ` - :ref:`ALM-12039 Active/Standby OMS Databases Not Synchronized ` - :ref:`ALM-12040 Insufficient System Entropy ` @@ -69,12 +67,8 @@ Alarm Reference (Applicable to MRS 3.\ *x*) - :ref:`ALM-12089 Inter-Node Network Is Abnormal ` - :ref:`ALM-12101 AZ Unhealthy ` - :ref:`ALM-12102 AZ HA Component Is Not Deployed Based on DR Requirements ` -- :ref:`ALM-12103 Executor Resource Exception ` -- :ref:`ALM-12104 Abnormal Knox Resources ` - :ref:`ALM-12110 Failed to get ECS temporary AK/SK ` -- :ref:`ALM-12172 Failed to Report Metrics to Cloud Eye ` - :ref:`ALM-12180 Suspended Disk I/O ` -- :ref:`ALM-12190 Number of Knox Connections Exceeds the Threshold ` - :ref:`ALM-13000 ZooKeeper Service Unavailable ` - :ref:`ALM-13001 Available ZooKeeper Connections Are Insufficient ` - :ref:`ALM-13002 ZooKeeper Direct Memory Usage Exceeds the Threshold ` @@ -171,14 +165,7 @@ Alarm Reference (Applicable to MRS 3.\ *x*) - :ref:`ALM-19018 HBase Compaction Queue Size Exceeds the Threshold ` - :ref:`ALM-19019 Number of HBase HFiles to Be Synchronized Exceeds the Threshold ` - :ref:`ALM-19020 Number of HBase WAL Files to Be Synchronized Exceeds the Threshold ` -- :ref:`ALM-19021 Handler Usage of RegionServer Exceeds the Threshold ` - :ref:`ALM-20002 Hue Service Unavailable ` -- :ref:`ALM-23001 Loader Service Unavailable ` -- :ref:`ALM-23003 Loader Task Execution Failure ` -- :ref:`ALM-23004 Loader Heap Memory Usage Exceeds the Threshold ` -- :ref:`ALM-23005 Loader Non-Heap Memory Usage Exceeds the Threshold ` -- :ref:`ALM-23006 Loader Direct Memory Usage Exceeds the Threshold ` -- :ref:`ALM-23007 Garbage Collection (GC) Time of the Loader Process Exceeds the Threshold ` - :ref:`ALM-24000 Flume Service Unavailable ` - :ref:`ALM-24001 Flume Agent Exception ` - :ref:`ALM-24003 Flume Client Connection Interrupted ` @@ -219,7 +206,6 @@ Alarm Reference (Applicable to MRS 3.\ *x*) - :ref:`ALM-38008 Abnormal Kafka Data Directory Status ` - :ref:`ALM-38009 Busy Broker Disk I/Os (Applicable to Versions Later Than MRS 3.1.0) ` - :ref:`ALM-38010 Topics with Single Replica ` -- :ref:`ALM-38011 User Connection Usage on Broker Exceeds the Threshold ` - :ref:`ALM-43001 Spark2x Service Unavailable ` - :ref:`ALM-43006 Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold ` - :ref:`ALM-43007 Non-Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold ` @@ -239,8 +225,6 @@ Alarm Reference (Applicable to MRS 3.\ *x*) - :ref:`ALM-44004 Presto Coordinator Resource Group Queuing Tasks Exceed the Threshold ` - :ref:`ALM-44005 Presto Coordinator Process GC Time Exceeds the Threshold ` - :ref:`ALM-44006 Presto Worker Process GC Time Exceeds the Threshold ` -- :ref:`ALM-45000 HetuEngine Service Unavailable ` -- :ref:`ALM-45001 Faulty HetuEngine Compute Instances ` - :ref:`ALM-45175 Average Time for Calling OBS Metadata APIs Is Greater than the Threshold ` - :ref:`ALM-45176 Success Rate of Calling OBS Metadata APIs Is Lower than the Threshold ` - :ref:`ALM-45177 Success Rate of Calling OBS Data Read APIs Is Lower than the Threshold ` @@ -248,7 +232,7 @@ Alarm Reference (Applicable to MRS 3.\ *x*) - :ref:`ALM-45179 Number of Failed OBS readFully API Calls Exceeds the Threshold ` - :ref:`ALM-45180 Number of Failed OBS read API Calls Exceeds the Threshold ` - :ref:`ALM-45181 Number of Failed OBS write API Calls Exceeds the Threshold ` -- :ref:`ALM-45182 Number of Throttled OBS Operations Exceeds the Threshold ` +- :ref:`ALM-45182 Number of Throttled OBS API Calls Exceeds the Threshold ` - :ref:`ALM-45275 Ranger Service Unavailable ` - :ref:`ALM-45276 Abnormal RangerAdmin Status ` - :ref:`ALM-45277 RangerAdmin Heap Memory Usage Exceeds the Threshold ` @@ -267,34 +251,6 @@ Alarm Reference (Applicable to MRS 3.\ *x*) - :ref:`ALM-45426 ClickHouse Service Quantity Quota Usage in ZooKeeper Exceeds the Threshold ` - :ref:`ALM-45427 ClickHouse Service Capacity Quota Usage in ZooKeeper Exceeds the Threshold ` - :ref:`ALM-45428 ClickHouse Disk I/O Exception ` -- :ref:`ALM-45429 Table Metadata Synchronization Failed on the Added ClickHouse Node ` -- :ref:`ALM-45430 Permission Metadata Synchronization Failed on the Added ClickHouse Node ` -- :ref:`ALM-45431 Improper ClickHouse Instance Distribution for Topology Allocation ` -- :ref:`ALM-45432 ClickHouse User Synchronization Process Fails ` -- :ref:`ALM-45433 ClickHouse AZ Topology Exception ` -- :ref:`ALM-45434 A Single Replica Exists in the ClickHouse Data Table ` -- :ref:`ALM-45585 IoTDB Service Unavailable ` -- :ref:`ALM-45586 IoTDBServer Heap Memory Usage Exceeds the Threshold ` -- :ref:`ALM-45587 IoTDBServer GC Duration Exceeds the Threshold ` -- :ref:`ALM-45588 IoTDBServer Direct Memory Usage Exceeds the Threshold ` -- :ref:`ALM-45589 ConfigNode Heap Memory Usage Exceeds the Threshold ` -- :ref:`ALM-45590 ConfigNode GC Duration Exceeds the Threshold ` -- :ref:`ALM-45591 ConfigNode Direct Memory Usage Exceeds the Threshold ` -- :ref:`ALM-45592 IoTDBServer RPC Execution Duration Exceeds the Threshold ` -- :ref:`ALM-45593 IoTDBServer Flush Execution Duration Exceeds the Threshold ` -- :ref:`ALM-45594 IoTDBServer Intra-Space Merge Duration Exceeds the Threshold ` -- :ref:`ALM-45595 IoTDBServer Cross-Space Merge Duration Exceeds the Threshold ` -- :ref:`ALM-45615 CDL Service Unavailable ` -- :ref:`ALM-45616 CDL Job Execution Exception ` -- :ref:`ALM-45617 Data Queued in the CDL Replication Slot Exceeds the Threshold ` -- :ref:`ALM-45635 FlinkServer Job Execution Failure ` -- :ref:`ALM-45636 FlinkServer Job Checkpoints Keep Failing ` -- :ref:`ALM-45636 Flink Job Checkpoints Keep Failing ` -- :ref:`ALM-45637 FlinkServer Task Is Continuously Under Back Pressure ` -- :ref:`ALM-45638 Number of Restarts After FlinkServer Job Failures Exceeds the Threshold ` -- :ref:`ALM-45638 Number of Restarts After Flink Job Failures Exceeds the Threshold ` -- :ref:`ALM-45640 FlinkServer Heartbeat Interruption Between the Active and Standby Nodes ` -- :ref:`ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes ` .. toctree:: :maxdepth: 1 @@ -307,18 +263,16 @@ Alarm Reference (Applicable to MRS 3.\ *x*) alm-12007_process_fault alm-12010_manager_heartbeat_interruption_between_the_active_and_standby_nodes alm-12011_manager_data_synchronization_exception_between_the_active_and_standby_nodes - alm-12012_ntp_service_is_abnormal alm-12014_partition_lost alm-12015_partition_filesystem_readonly alm-12016_cpu_usage_exceeds_the_threshold alm-12017_insufficient_disk_capacity alm-12018_memory_usage_exceeds_the_threshold alm-12027_host_pid_usage_exceeds_the_threshold - alm-12028_number_of_processes_in_the_d_state_and_z_state_on_a_host_exceeds_the_threshold + alm-12028_number_of_processes_in_the_d_state_on_a_host_exceeds_the_threshold alm-12033_slow_disk_fault alm-12034_periodical_backup_failure alm-12035_unknown_data_status_after_recovery_task_failure - alm-12037_ntp_server_abnormal alm-12038_monitoring_indicator_dumping_failure alm-12039_active_standby_oms_databases_not_synchronized alm-12040_insufficient_system_entropy @@ -364,12 +318,8 @@ Alarm Reference (Applicable to MRS 3.\ *x*) alm-12089_inter-node_network_is_abnormal alm-12101_az_unhealthy alm-12102_az_ha_component_is_not_deployed_based_on_dr_requirements - alm-12103_executor_resource_exception - alm-12104_abnormal_knox_resources alm-12110_failed_to_get_ecs_temporary_ak_sk - alm-12172_failed_to_report_metrics_to_cloud_eye alm-12180_suspended_disk_i_o - alm-12190_number_of_knox_connections_exceeds_the_threshold alm-13000_zookeeper_service_unavailable alm-13001_available_zookeeper_connections_are_insufficient alm-13002_zookeeper_direct_memory_usage_exceeds_the_threshold @@ -466,14 +416,7 @@ Alarm Reference (Applicable to MRS 3.\ *x*) alm-19018_hbase_compaction_queue_size_exceeds_the_threshold alm-19019_number_of_hbase_hfiles_to_be_synchronized_exceeds_the_threshold alm-19020_number_of_hbase_wal_files_to_be_synchronized_exceeds_the_threshold - alm-19021_handler_usage_of_regionserver_exceeds_the_threshold alm-20002_hue_service_unavailable - alm-23001_loader_service_unavailable - alm-23003_loader_task_execution_failure - alm-23004_loader_heap_memory_usage_exceeds_the_threshold - alm-23005_loader_non-heap_memory_usage_exceeds_the_threshold - alm-23006_loader_direct_memory_usage_exceeds_the_threshold - alm-23007_garbage_collection_gc_time_of_the_loader_process_exceeds_the_threshold alm-24000_flume_service_unavailable alm-24001_flume_agent_exception alm-24003_flume_client_connection_interrupted @@ -514,7 +457,6 @@ Alarm Reference (Applicable to MRS 3.\ *x*) alm-38008_abnormal_kafka_data_directory_status alm-38009_busy_broker_disk_i_os_applicable_to_versions_later_than_mrs_3.1.0 alm-38010_topics_with_single_replica - alm-38011_user_connection_usage_on_broker_exceeds_the_threshold alm-43001_spark2x_service_unavailable alm-43006_heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold alm-43007_non-heap_memory_usage_of_the_jobhistory2x_process_exceeds_the_threshold @@ -534,8 +476,6 @@ Alarm Reference (Applicable to MRS 3.\ *x*) alm-44004_presto_coordinator_resource_group_queuing_tasks_exceed_the_threshold alm-44005_presto_coordinator_process_gc_time_exceeds_the_threshold alm-44006_presto_worker_process_gc_time_exceeds_the_threshold - alm-45000_hetuengine_service_unavailable - alm-45001_faulty_hetuengine_compute_instances alm-45175_average_time_for_calling_obs_metadata_apis_is_greater_than_the_threshold alm-45176_success_rate_of_calling_obs_metadata_apis_is_lower_than_the_threshold alm-45177_success_rate_of_calling_obs_data_read_apis_is_lower_than_the_threshold @@ -543,7 +483,7 @@ Alarm Reference (Applicable to MRS 3.\ *x*) alm-45179_number_of_failed_obs_readfully_api_calls_exceeds_the_threshold alm-45180_number_of_failed_obs_read_api_calls_exceeds_the_threshold alm-45181_number_of_failed_obs_write_api_calls_exceeds_the_threshold - alm-45182_number_of_throttled_obs_operations_exceeds_the_threshold + alm-45182_number_of_throttled_obs_api_calls_exceeds_the_threshold alm-45275_ranger_service_unavailable alm-45276_abnormal_rangeradmin_status alm-45277_rangeradmin_heap_memory_usage_exceeds_the_threshold @@ -562,31 +502,3 @@ Alarm Reference (Applicable to MRS 3.\ *x*) alm-45426_clickhouse_service_quantity_quota_usage_in_zookeeper_exceeds_the_threshold alm-45427_clickhouse_service_capacity_quota_usage_in_zookeeper_exceeds_the_threshold alm-45428_clickhouse_disk_i_o_exception - alm-45429_table_metadata_synchronization_failed_on_the_added_clickhouse_node - alm-45430_permission_metadata_synchronization_failed_on_the_added_clickhouse_node - alm-45431_improper_clickhouse_instance_distribution_for_topology_allocation - alm-45432_clickhouse_user_synchronization_process_fails - alm-45433_clickhouse_az_topology_exception - alm-45434_a_single_replica_exists_in_the_clickhouse_data_table - alm-45585_iotdb_service_unavailable - alm-45586_iotdbserver_heap_memory_usage_exceeds_the_threshold - alm-45587_iotdbserver_gc_duration_exceeds_the_threshold - alm-45588_iotdbserver_direct_memory_usage_exceeds_the_threshold - alm-45589_confignode_heap_memory_usage_exceeds_the_threshold - alm-45590_confignode_gc_duration_exceeds_the_threshold - alm-45591_confignode_direct_memory_usage_exceeds_the_threshold - alm-45592_iotdbserver_rpc_execution_duration_exceeds_the_threshold - alm-45593_iotdbserver_flush_execution_duration_exceeds_the_threshold - alm-45594_iotdbserver_intra-space_merge_duration_exceeds_the_threshold - alm-45595_iotdbserver_cross-space_merge_duration_exceeds_the_threshold - alm-45615_cdl_service_unavailable - alm-45616_cdl_job_execution_exception - alm-45617_data_queued_in_the_cdl_replication_slot_exceeds_the_threshold - alm-45635_flinkserver_job_execution_failure - alm-45636_flinkserver_job_checkpoints_keep_failing - alm-45636_flink_job_checkpoints_keep_failing - alm-45637_flinkserver_task_is_continuously_under_back_pressure - alm-45638_number_of_restarts_after_flinkserver_job_failures_exceeds_the_threshold - alm-45638_number_of_restarts_after_flink_job_failures_exceeds_the_threshold - alm-45640_flinkserver_heartbeat_interruption_between_the_active_and_standby_nodes - alm-45641_data_synchronization_exception_between_the_active_and_standby_flinkserver_nodes diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/configuring_audit_log_dumping.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/configuring_audit_log_dumping.rst index 92f7ce4..30ebb7b 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/configuring_audit_log_dumping.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/configuring_audit_log_dumping.rst @@ -68,4 +68,4 @@ Procedure - **LOGLEVEL** indicates the security level. Value **0** indicates Critical, value **1** indicates Major, value **2** indicates Minor, and value **3** indicates Warning. - **OPERATERESULT** indicates the operation result. Value **0** indicates that the operation is successful, and value **1** indicates that the operation is failed. -.. |image1| image:: /_static/images/en-us_image_0000001442653657.png +.. |image1| image:: /_static/images/en-us_image_0263899218.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/overview.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/overview.rst index bf14528..2299912 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/overview.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/audit/overview.rst @@ -31,5 +31,5 @@ Log in to FusionInsight Manager and choose **Audit**. The **Audit** page display - You can click |image1| to manually refresh the current page or click |image2| to filter the columns displayed in the page. - Click **Export All** to export all audit information at a time. The audit information can be exported in **TXT** or **CSV** format. -.. |image1| image:: /_static/images/en-us_image_0000001442494041.png -.. |image2| image:: /_static/images/en-us_image_0000001442413865.png +.. |image1| image:: /_static/images/en-us_image_0263899268.png +.. |image2| image:: /_static/images/en-us_image_0000001369925585.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_cdl_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_cdl_data.rst deleted file mode 100644 index 1ad6600..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_cdl_data.rst +++ /dev/null @@ -1,76 +0,0 @@ -:original_name: admin_guide_000343.html - -.. _admin_guide_000343: - -Backing Up CDL Data -=================== - -Scenario --------- - -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 to recover the system if an exception occurs or the operation has not achieved the expected result, minimizing the adverse impacts on services. - -CDL data is stored in DBService and Kafka. You can create DBService and Kafka backup tasks on FusionInsight Manager to back up CDL data. Both automatic and manual backup tasks are supported. - -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 FusionInsight Manager, mutual trust has been configured. For details, see :ref:`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 :ref:`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. -- The backup type, period, policy, and other specifications have been planned based on the service requirements and you have checked whether *Data storage path*\ **/LocalBackup/** has sufficient space on the active and standby management nodes. -- 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 ---------- - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Backup Management**. - -#. Click **Create**. - -#. Set **Name** to the name of the backup task. - -#. Select the cluster to be operated from **Backup Object**. - -#. 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. - - .. table:: **Table 1** Periodic backup parameters - - +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Parameter | Description | - +===================================+=======================================================================================================================================================================================================================================================================================+ - | Started | Indicates the time when the task is started for the first time. | - +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Period | Indicates 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:: | - | | | - | | - Incremental backup is not supported when Manager data and component metadata are backed up. Only **Full backup every time** is supported. | - | | - If **Path Type** is set to **NFS** or **CIFS**, incremental backup cannot be used. When incremental backup is used for NFS or CIFS backup, the latest full backup data is updated each time the incremental backup is performed. Therefore, no new recovery point is generated. | - +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - -#. Set **Configuration** to **DBService** and **Kafka**. - - .. note:: - - If there are multiple DBService or Kafka services, all DBService or Kafka services are backed up by default. You can click **Assign Service** to specify the services to be backed up. - -#. Set **Path Type** of **DBService** to a backup directory type. For details about how to set the parameters, see :ref:`7 `. - -#. Set **Path Type** of **Kafka** to a backup directory type. For details about how to set the parameters, see :ref:`7 `. - -#. Click **OK**. - -#. 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*\ **\_**\ *Task creation time*, and the subdirectory is used to save data source backup files. - - The format of the backup file name is *Version*\ **\_**\ *Data source*\ **\_**\ *Task execution time*\ **.tar.gz**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_clickhouse_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_clickhouse_service_data.rst index ae5acb5..e4b80df 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_clickhouse_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_clickhouse_service_data.rst @@ -61,9 +61,7 @@ Procedure #. In **Configuration**, select **ClickHouse** under **Service Data**. -#. .. _admin_guide_000349__li4457996415256: - - Set **Path Type** of **ClickHouse** to a backup directory type. +#. Set **Path Type** of **ClickHouse** to a backup directory type. Currently, only the **RemoteHDFS** type is available. @@ -119,5 +117,5 @@ Procedure 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 *Data source_Task creation time*, and the subdirectory is used to save latest data source backup files. -.. |image1| image:: /_static/images/en-us_image_0000001442653737.png -.. |image2| image:: /_static/images/en-us_image_0000001392574070.png +.. |image1| image:: /_static/images/en-us_image_0000001197336255.png +.. |image2| image:: /_static/images/en-us_image_0000001151336594.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_dbservice_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_dbservice_data.rst index 72e8003..3163e90 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_dbservice_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_dbservice_data.rst @@ -63,9 +63,7 @@ Procedure If there are multiple DBService services, all DBService services are backed up by default. You can click **Assign Service** to specify the services to be backed up. -#. .. _admin_guide_000203__li4457996415256: - - Set **Path Type** of **DBService** to a backup directory type. +#. Set **Path Type** of **DBService** to a backup directory type. The following backup directory types are supported: diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hbase_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hbase_service_data.rst index 934c964..82a4846 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hbase_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hbase_service_data.rst @@ -169,5 +169,5 @@ Procedure 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. -.. |image1| image:: /_static/images/en-us_image_0000001392734022.png -.. |image2| image:: /_static/images/en-us_image_0000001442413937.png +.. |image1| image:: /_static/images/en-us_image_0263899673.png +.. |image2| image:: /_static/images/en-us_image_0263899411.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hdfs_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hdfs_service_data.rst index 32a8f16..2debb7f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hdfs_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hdfs_service_data.rst @@ -170,5 +170,5 @@ Procedure 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. -.. |image1| image:: /_static/images/en-us_image_0000001442494045.png -.. |image2| image:: /_static/images/en-us_image_0000001442413869.png +.. |image1| image:: /_static/images/en-us_image_0263899520.png +.. |image2| image:: /_static/images/en-us_image_0263899283.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hive_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hive_service_data.rst index 7c93f66..6fd297f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hive_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_hive_service_data.rst @@ -163,5 +163,5 @@ Procedure 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. -.. |image1| image:: /_static/images/en-us_image_0000001442494045.png -.. |image2| image:: /_static/images/en-us_image_0000001442413869.png +.. |image1| image:: /_static/images/en-us_image_0263899520.png +.. |image2| image:: /_static/images/en-us_image_0263899283.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_iotdb_metadata.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_iotdb_metadata.rst deleted file mode 100644 index 2da620a..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_iotdb_metadata.rst +++ /dev/null @@ -1,130 +0,0 @@ -:original_name: admin_guide_000350.html - -.. _admin_guide_000350: - -Backing Up IoTDB Metadata -========================= - -Scenario --------- - -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 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 FusionInsight Manager to back up IoTDB metadata. Both automatic and manual backup tasks are supported. - -Prerequisites -------------- - -- The backup type, period, policy, and other specifications have been planned based on the service requirements and you have checked whether *Data storage path*\ **/LocalBackup/** has sufficient space on the active and standby management nodes. - -- If you want to back up data to NAS, you have deployed the NAS server in advance. - -- 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. - -Procedure ---------- - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Backup Management**. - -#. Click **Create**. - -#. Set **Name** to the name of the backup task. - -#. Select the cluster to be operated from **Backup Object**. - -#. 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. - - .. table:: **Table 1** Periodic backup parameters - - +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------+ - | Parameter | Description | - +===================================+============================================================================================================================+ - | Started | Indicates the time when the task is started for the first time. | - +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------+ - | Period | The task execution interval. Value options include **Hours** and **Days**. | - +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------+ - | Backup Policy | Indicates a periodic backup policy. | - | | | - | | - **Full backup at the first time and incremental backup subsequently** | - | | - **Full backup every time** | - | | - **Full backup once every n times** | - | | | - | | .. note:: | - | | | - | | Incremental backup is not supported when component metadata is backed up. Only **Full backup every time** is supported. | - +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------+ - -#. In **Configuration**, select **IoTDB** under **Metadata and other data**. - - .. note:: - - If there are multiple IoTDB services, all IoTDB services are backed up by default. You can click **Assign Service** to specify the services to be backed up. - -#. Set **Path Type** of **IoTDB** to a backup directory type. - - The following backup directory types are supported: - - - **LocalDir**: indicates that the backup files are stored on the local disk of the active management node and the standby management node automatically synchronizes the backup files. By default, the backup files are stored in *Data storage path*\ **/LocalBackup/**. - - If you select this option, you need to set the maximum number of replicas to specify the number of backup file sets that can be retained in the backup directory. - - - **NFS**: indicates that backup files are stored in the NAS using the NFS 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 NAS server. - - **Server Shared Path**: indicates the configured shared directory of the NAS server. (The shared path of the server cannot be set to the root directory, and the user group and owner group of the shared path must be **nobody:nobody**.) - - **Maximum Number of Backup Copies**: indicates the number of backup file sets that can be retained in the backup directory. - - - **RemoteHDFS**: indicates that the backup files are stored in the HDFS directory of the standby cluster. - - If you select this option, set 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 of the standby cluster. - - - **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**. - - **Destination Active NameNode IP Address**: indicates the service plane IP address of the active NameNode in the standby cluster. - - **Destination Standby NameNode IP Address**: indicates the service plane IP address of the standby NameNode in the standby cluster. - - **Destination NameNode RPC Port**: indicates the value of **dfs.namenode.rpc.port** in the HDFS basic configuration of the standby cluster. - - **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**. - - **Maximum Number of Backup Copies**: indicates the number of backup file sets that can be retained in the backup directory. - - - **CIFS**: indicates that backup files are stored in the NAS using the CIFS 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 NAS server. - - **Port**: indicates the port number used to connect to the NAS server over the CIFS protocol. The default value is **445**. - - **Username**: indicates the username set when the CIFS protocol is configured. - - **Password**: indicates the password set when the CIFS protocol is configured. - - **Server Shared Path**: indicates the configured shared directory of the NAS server. (The shared path of the server cannot be set to the root directory, and the user group and owner group of the shared path must be **nobody:nobody**.) - - **Maximum Number of Backup Copies**: indicates the number of backup file sets that can be retained in the backup directory. - - - **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. - -#. Click **OK**. - -#. 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*\ **\_**\ *Task creation time*, and the subdirectory is used to save data source backup files. - - The format of the backup file name is *Version*\ **\_**\ *Data source*\ **\_**\ *Task execution time*\ **.tar.gz**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_iotdb_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_iotdb_service_data.rst deleted file mode 100644 index 0defc76..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/backing_up_iotdb_service_data.rst +++ /dev/null @@ -1,119 +0,0 @@ -:original_name: admin_guide_000360.html - -.. _admin_guide_000360: - -Backing Up IoTDB Service Data -============================= - -Scenario --------- - -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 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 FusionInsight Manager to back up IoTDB service data. Both automatic and manual backup tasks are supported. - -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. Currently, IoTDB data can be backed up only to HDFS. -- For the IoTDB cluster in normal mode, service data cannot be backed up to HDFS in a cluster in security mode. - -- If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same FusionInsight Manager, mutual trust has been configured. For details, see :ref:`Configuring Cross-Manager Mutual Trust Between Clusters `. If the active cluster is deployed in normal mode, no mutual trust is required. - -- Time is consistent between the active and standby clusters and the NTP services on the active and standby clusters use the same time source. -- The HDFS in the standby cluster has sufficient space. You are advised to save backup files in a custom directory. - -Procedure ---------- - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Backup Management**. - -#. Click **Create**. - -#. Set **Name** to the name of the backup task. - -#. Select the cluster to be operated from **Backup Object**. - -#. 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. - - .. table:: **Table 1** Periodic backup parameters - - +-----------------------------------+----------------------------------------------------------------------------+ - | Parameter | Description | - +===================================+============================================================================+ - | Started | Indicates the time when the task is started for the first time. | - +-----------------------------------+----------------------------------------------------------------------------+ - | Period | The task execution interval. Value options include **Hours** and **Days**. | - +-----------------------------------+----------------------------------------------------------------------------+ - | Backup Policy | Indicates a periodic backup policy. | - | | | - | | - **Full backup at the first time and incremental backup subsequently** | - | | - **Full backup every time** | - | | - **Full backup once every n times** | - +-----------------------------------+----------------------------------------------------------------------------+ - -#. In **Configuration**, choose **IoTDB** > **IoTDB** under **Service data**. - -#. Set **Path Type** of **IoTDB** to a backup directory type. - - The following backup directory types are supported: - - **RemoteHDFS**: indicates that the backup files are stored in the HDFS directory of the standby cluster. - - If you select this option, set 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 of the standby cluster. - - - **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**. - - **Destination Active NameNode IP Address**: indicates the service plane IP address of the active NameNode in the standby cluster. - - **Destination Standby NameNode IP Address**: indicates the service plane IP address of the standby NameNode in the standby cluster. - - **Destination NameNode RPC Port**: indicates the value of **dfs.namenode.rpc.port** in the HDFS basic configuration of the standby cluster. - - **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**. - - **Maximum Number of Backup Copies**: indicates the number of backup file sets that can be retained in the backup directory. - -#. Set **Backup Content** to one or multiple service data records 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. - - MRS 3.2.0 or later: - - a. Click **Add**. - b. Select the table to be backed up under **File Directory**, and click **Add** to add the table to **Backup Content**. - c. Click **OK**. - - - Selecting using regular expressions - - a. Click **Query Regular Expression**. - b. Enter the parent directory full path of the directory in the first text box as prompted. The directory must be the same as the existing directory, for example, **/root**. - c. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get all files or subdirectories in the parent directory, enter **([\\s\\S]*?)**. To get files whose names consist of letters and digits, for example, **file\ 1**, enter **file\\d\***. - d. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get objects containing **test**, enter **.*test.\***. To get objects starting with **test**, enter **test.\***. To get objects ending with **test**, enter **.*test**. - e. Click **Refresh** to view the displayed directories in **Directory Name**. - f. Click **Synchronize** to save the result. - - .. note:: - - - When entering regular expressions, click |image1| or |image2| to add or delete an expression. - - If the selected table or directory is incorrect, click **Clear Selected Node** to deselect it. - - The backup directory cannot contain files that have been written for a long time. Otherwise, the backup task will fail. Therefore, you are not advised to perform operations on the top-level directory, such as **/user**, **/tmp**, and **/mr-history**. - -#. 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 data to be backed up does not exist. - -#. Click **OK**. - -#. 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. - -.. |image1| image:: /_static/images/en-us_image_0000001584751969.png -.. |image2| image:: /_static/images/en-us_image_0000001534512058.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/index.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/index.rst index 41f03de..b13b799 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/index.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/backing_up_data/index.rst @@ -6,7 +6,6 @@ Backing Up Data =============== - :ref:`Backing Up Manager Data ` -- :ref:`Backing Up CDL Data ` - :ref:`Backing Up ClickHouse Metadata ` - :ref:`Backing Up ClickHouse Service Data ` - :ref:`Backing Up DBService Data ` @@ -15,8 +14,6 @@ Backing Up Data - :ref:`Backing Up NameNode Data ` - :ref:`Backing Up HDFS Service Data ` - :ref:`Backing Up Hive Service Data ` -- :ref:`Backing Up IoTDB Metadata ` -- :ref:`Backing Up IoTDB Service Data ` - :ref:`Backing Up Kafka Metadata ` .. toctree:: @@ -24,7 +21,6 @@ Backing Up Data :hidden: backing_up_manager_data - backing_up_cdl_data backing_up_clickhouse_metadata backing_up_clickhouse_service_data backing_up_dbservice_data @@ -33,6 +29,4 @@ Backing Up Data backing_up_namenode_data backing_up_hdfs_service_data backing_up_hive_service_data - backing_up_iotdb_metadata - backing_up_iotdb_service_data backing_up_kafka_metadata diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/index.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/index.rst index 9986431..a83fb75 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/index.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/index.rst @@ -6,7 +6,6 @@ Recovering Data =============== - :ref:`Restoring Manager Data ` -- :ref:`Restoring CDL Data ` - :ref:`Restoring ClickHouse Metadata ` - :ref:`Restoring ClickHouse Service Data ` - :ref:`Restoring DBService data ` @@ -15,8 +14,6 @@ Recovering Data - :ref:`Restoring NameNode Data ` - :ref:`Restoring HDFS Service Data ` - :ref:`Restoring Hive Service Data ` -- :ref:`Restoring IoTDB Metadata ` -- :ref:`Restoring IoTDB Service Data ` - :ref:`Restoring Kafka Metadata ` .. toctree:: @@ -24,7 +21,6 @@ Recovering Data :hidden: restoring_manager_data - restoring_cdl_data restoring_clickhouse_metadata restoring_clickhouse_service_data restoring_dbservice_data @@ -33,6 +29,4 @@ Recovering Data restoring_namenode_data restoring_hdfs_service_data restoring_hive_service_data - restoring_iotdb_metadata - restoring_iotdb_service_data restoring_kafka_metadata diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_cdl_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_cdl_data.rst deleted file mode 100644 index 8d42e61..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_cdl_data.rst +++ /dev/null @@ -1,78 +0,0 @@ -:original_name: admin_guide_000345.html - -.. _admin_guide_000345: - -Restoring CDL Data -================== - -Scenario --------- - -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 operations (such as upgrade and data adjustment) on CDL, an exception occurs or the expected result is not achieved. All modules are faulty and become unavailable. Data is migrated to a new cluster. - -CDL metadata is stored in DBService and Kafka. A system administrator can create DBService and Kafka restoration tasks on FusionInsight Manager to restore CDL data. Only manual restoration tasks are supported. - -.. important:: - - - Data restoration can be performed only when the system version is consistent with that during data backup. - - To restore the data when services are normal, manually back up the latest management data first and then restore the data. Otherwise, the DBService and Kafka data that is generated after the data backup and before the data restoration will be lost. - - By default, MRS clusters use DBService to store metadata of Hive, Hue, Loader, Spark, CDL, and Oozie. Restoring DBService data will restore the metadata of all these components. - -Impact on the System --------------------- - -- After the data is restored, the data generated after the data backup and before the data restoration is lost. -- After the data is restored, the configurations of the components that depend on DBService may expire and these components need to be restarted. -- After the metadata is restored, the offset information stored on ZooKeeper by Kafka consumers is rolled back, resulting in repeated consumption. - -Prerequisites -------------- - -- If you need to restore data from a remote HDFS, prepare a standby cluster. If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same FusionInsight Manager, mutual trust must be configured. For details, see :ref:`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 :ref:`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. - -- The status of the active and standby DBService instances is normal. If the status is abnormal, data restoration cannot be performed. - -- The Kafka service is disabled first, and then enabled upon data restoration. - -Procedure ---------- - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Backup Management**. - -#. In the row where the specified backup task is located, choose **More** > **View History** in the **Operation** column to display the historical execution records of the backup task. - - 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 where backup files are stored. - - Select the correct path, and manually copy the full path of backup files in **Backup Path**. - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Restoration Management**. - -#. Click **Create**. - -#. Set **Task Name** to the name of the restoration task. - -#. Select the cluster to be operated from **Recovery Object**. - -#. In the **Restoration Configuration** area, select **DBService** and **Kafka**. - - .. note:: - - If multiple DBService or Kafka services are installed, select the DBService or Kafka services to be restored. - -#. Set **Path Type** of **DBService** to a backup directory type. For details about how to configure the parameters, see :ref:`8 `. - -#. Set **Path Type** of **Kafka** to a backup directory type. For details about how to configure the parameters, see :ref:`8 `. - -#. Click **OK**. - -#. In the restoration task list, locate the row where the created task is located, and click **Start** in the **Operation** column. - - - After the restoration is successful, the progress bar is in green. - - After the restoration is successful, the restoration task cannot be executed again. - - If the restoration task fails during the first execution, rectify the fault and click **Retry** to execute the task again. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_clickhouse_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_clickhouse_service_data.rst index f904688..b6d83eb 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_clickhouse_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_clickhouse_service_data.rst @@ -64,9 +64,7 @@ Procedure #. In **Restoration Configuration**, select **ClickHouse** under **Service data**. -#. .. _admin_guide_000359__li4457996415256: - - Set **Path Type** of **ClickHouse** to a backup directory type. +#. Set **Path Type** of **ClickHouse** to a backup directory type. Currently, the backup directory supports only the **RemoteHDFS** type. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_iotdb_metadata.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_iotdb_metadata.rst deleted file mode 100644 index ed9bae4..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_iotdb_metadata.rst +++ /dev/null @@ -1,115 +0,0 @@ -:original_name: admin_guide_000351.html - -.. _admin_guide_000351: - -Restoring IoTDB Metadata -======================== - -Scenario --------- - -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 system can restore data timely when an exception is reported or an operation does not achieve the expected result, minimizing the impact on services. - -System administrators can create an IoTDB restoration task on FusionInsight Manager. Only manual restoration tasks are supported. - -.. important:: - - - Data restoration can be performed only when the system version is consistent with that during data backup. - - To restore the data when services are normal, manually back up the latest management data first and then restore the data. Otherwise, the IoTDB data that is generated after the data backup and before the data restoration will be lost. - - You are advised to restore the metadata of only one component in a restoration task to prevent the stop of a service or instance from affecting the data restoration of other components. If data of multiple components is restored at the same time, data restoration may fail. - -Impact on the System --------------------- - -After the metadata is restored, the data generated after the data backup and before the data restoration is lost. - -Procedure ---------- - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Backup Management**. - -#. In the row where the specified backup task is located, choose **More** > **View History** in the **Operation** column to display the historical execution records of the backup task. - - 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 where backup files are stored. - - Select the correct path, and manually copy the full path of backup files in **Backup Path**. - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Restoration Management**. - -#. Click **Create**. - -#. Set **Task Name** to the name of the restoration task. - -#. Select the cluster to be operated from **Recovery Object**. - -#. In **Restoration Configuration**, select **IoTDB** under **Metadata and other data**. - - .. note:: - - If multiple IoTDB services are installed, select the IoTDB service to be restored. - -#. Select a backup directory type for **Path Type**. - - The configurations vary based on backup directory types: - - - **LocalDir**: indicates that the backup files are stored on the local disk of the active management node. - - If you select this option, you also need to set **Source Path**, which indicates the backup file to be restored, for example, *Version_Data source_Task execution time*\ **.tar.gz**. - - - **NFS**: indicates that backup files are stored in NAS using the NFS protocol. - - If you select this option, configure 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 NAS server. - - **Source Path**: indicates the complete path of the backup file on the NAS server, for example, *Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time*\ **.tar.gz**. - - - **RemoteHDFS**: indicates that the backup files are stored in the HDFS directory of the standby cluster. - - If you select this option, 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 the IP address mode based on the cluster network type, for example, **IPv4** or **IPv6**. - - **Source Active NameNode IP Address**: indicates the service plane IP address of the active NameNode in the standby cluster. - - **Source Standby NameNode IP Address**: indicates the service plane IP address of the standby NameNode in the standby cluster. - - **Source NameNode RPC Port**: indicates the value of **dfs.namenode.rpc.port** in the HDFS basic configuration of the standby cluster. - - **Source Path**: indicates the full path of HDFS directory for storing backup data of the standby cluster, for example, *Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time*\ **.tar.gz**. - - - **CIFS**: indicates that backup files are stored in NAS using the CIFS protocol. - - If you select this option, configure 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 NAS server. - - **Port**: indicates the port number used to connect to the NAS server over the CIFS protocol. The default value is **445**. - - **Username**: indicates the username set when the CIFS protocol is configured. - - **Password**: indicates the password set when the CIFS protocol is configured. - - **Source Path**: indicates the complete path of the backup file on the NAS server, for example, *Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time*\ **.tar.gz**. - - - **SFTP**: indicates that backup files are stored in the server using the SFTP protocol. - - If you select this option, configure 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 complete 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**. - -#. Click **OK**. - -#. In the restoration task list, locate the row where the created task is located, and click **Start** in the **Operation** column. - - - After the restoration is successful, the progress bar is in green. - - After the restoration is successful, the restoration task cannot be executed again. - - If the restoration task fails during the first execution, rectify the fault and click **Retry** to execute the task again. - -#. Choose **Cluster** > **Services** and start the IoTDB service. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_iotdb_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_iotdb_service_data.rst deleted file mode 100644 index 2d91193..0000000 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_iotdb_service_data.rst +++ /dev/null @@ -1,96 +0,0 @@ -:original_name: admin_guide_000361.html - -.. _admin_guide_000361: - -Restoring IoTDB Service Data -============================ - -Scenario --------- - -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 major operations (such as upgrade and data adjustment) on IoTDB, an exception occurs or the expected result is not achieved. All modules are faulty and become unavailable. Data is migrated to a new cluster. - -System administrators can create an IoTDB restoration task on FusionInsight Manager. Only manual restoration tasks are supported. - -.. important:: - - - Data restoration can be performed only when the system version is consistent with that during data backup. - - To restore the data when services are normal, manually back up the latest management data first and then restore the data. Otherwise, the IoTDB data that is generated after the data backup and before the data restoration will be lost. - -Impact on the System --------------------- - -- During data restoration, user authentication stops and users cannot create new connections. -- After the data is restored, the data generated after the data backup and before the data restoration is lost. -- After the data is restored, the IoTDB upper-layer applications need to be started. - -Prerequisites -------------- - -- If you need to restore data from a remote HDFS, prepare a standby cluster. If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same FusionInsight Manager, mutual trust must be configured. For details, see :ref:`Configuring Cross-Manager Mutual Trust Between Clusters `. If the active cluster is deployed in normal mode, no mutual trust is required. - -- Time is consistent between the active and standby clusters and the NTP services on the active and standby clusters use the same time source. -- The IoTDB backup file save path is correct. -- The IoTDB upper-layer applications are stopped. - -Procedure ---------- - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Backup Management**. - -#. In the row where the specified backup task is located, choose **More** > **View History** in the **Operation** column to display the historical execution records of the backup task. - - 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 where backup files are stored. - - Select the correct path, and manually copy the full path of backup files in **Backup Path**. - -#. On FusionInsight Manager, choose **O&M** > **Backup and Restoration** > **Restoration Management**. - -#. Click **Create**. - -#. Set **Task Name** to the name of the restoration task. - -#. Select the cluster to be operated from **Recovery Object**. - -#. In **Restoration Configuration**, choose **IoTDB** > **IoTDB** under **Service Data**. - -#. .. _admin_guide_000361__li4457996415256: - - Set **Path Type** of **IoTDB** to a backup directory type. - - The following backup directory types are supported: - - **RemoteHDFS**: indicates that the backup files are stored in the HDFS directory of the standby cluster. - - If you select this option, 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 the IP address mode based on the cluster network type, for example, **IPv4** or **IPv6**. - - **Source Active NameNode IP Address**: indicates the service plane IP address of the active NameNode in the standby cluster. - - **Source Standby NameNode IP Address**: indicates the service plane IP address of the standby NameNode in the standby cluster. - - **Source NameNode RPC Port**: indicates the value of **dfs.namenode.rpc.port** in the HDFS basic configuration of the standby cluster. - - **Source Path**: indicates the full path of HDFS directory for storing backup data of the standby cluster, for example, *Backup path/Backup task name_Data source_Task creation time*. - - **Recovery Point List**: Click **Refresh** and select an IoTDB directory that has been backed up in the standby cluster. - -#. 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. - -#. Set **Force recovery** to **true**, which indicates that all backup data is forcibly restored when a data table with the same name already exists. If the data table contains new data added after backup, the new data will be lost after the data restoration. If you set the parameter to **false**, the restoration task is not executed if a data table with the same name exists. - -#. 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. - -#. Click **OK**. - -#. In the restoration task list, locate the row where the created task is located, and click **Start** in the **Operation** column. - - - After the restoration is successful, the progress bar is in green. - - After the restoration is successful, the restoration task cannot be executed again. - - If the restoration task fails during the first execution, rectify the fault and click **Retry** to execute the task again. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/viewing_backup_and_restoration_tasks.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/viewing_backup_and_restoration_tasks.rst index 5705f30..37f627d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/viewing_backup_and_restoration_tasks.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/viewing_backup_and_restoration_tasks.rst @@ -47,4 +47,4 @@ Related Tasks In the task list, locate a specified task and choose **More** > **Suspend** in the **Operation** column to suspend a backup task. Only periodic backup tasks can be suspended. Suspended backup tasks are no longer executed automatically. When you suspend a backup task that is being executed, the task execution stops. To resume a task, choose **More** > **Resume**. -.. |image1| image:: /_static/images/en-us_image_0000001392254858.png +.. |image1| image:: /_static/images/en-us_image_0263899323.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/managing_cluster_configurations.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/managing_cluster_configurations.rst index fcd5d25..5a58208 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/managing_cluster_configurations.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/managing_cluster_configurations.rst @@ -52,7 +52,7 @@ Procedure Some configuration items take effect only after the corresponding services are restarted. After the configurations are saved, restart the services or instances whose configurations have expired in a timely manner. -.. |image1| image:: /_static/images/en-us_image_0000001392414378.png -.. |image2| image:: /_static/images/en-us_image_0000001392254854.png -.. |image3| image:: /_static/images/en-us_image_0000001442653641.png -.. |image4| image:: /_static/images/en-us_image_0000001442773609.png +.. |image1| image:: /_static/images/en-us_image_0263899617.png +.. |image2| image:: /_static/images/en-us_image_0279536633.png +.. |image3| image:: /_static/images/en-us_image_0263899556.png +.. |image4| image:: /_static/images/en-us_image_0263899589.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/modifying_cluster_attributes.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/modifying_cluster_attributes.rst index 73de05d..448ae72 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/modifying_cluster_attributes.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/cluster_management/modifying_cluster_attributes.rst @@ -35,5 +35,5 @@ Procedure b. Click **OK** for the new description to take effect. -.. |image1| image:: /_static/images/en-us_image_0000001392414474.png -.. |image2| image:: /_static/images/en-us_image_0000001442773701.png +.. |image1| image:: /_static/images/en-us_image_0000001318563432.png +.. |image2| image:: /_static/images/en-us_image_0000001369864353.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/instance_group/managing_instance_groups.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/instance_group/managing_instance_groups.rst index 7835179..c564194 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/instance_group/managing_instance_groups.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/instance_group/managing_instance_groups.rst @@ -84,6 +84,6 @@ Deleting an Instance Group The default instance group cannot be deleted. -.. |image1| image:: /_static/images/en-us_image_0000001442413917.png -.. |image2| image:: /_static/images/en-us_image_0000001392414446.png -.. |image3| image:: /_static/images/en-us_image_0000001442773673.png +.. |image1| image:: /_static/images/en-us_image_0263899383.png +.. |image2| image:: /_static/images/en-us_image_0000001318441686.png +.. |image3| image:: /_static/images/en-us_image_0000001318122266.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/other_service_management_operations/resource_monitoring.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/other_service_management_operations/resource_monitoring.rst index aa5dc98..d364142 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/other_service_management_operations/resource_monitoring.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/other_service_management_operations/resource_monitoring.rst @@ -102,6 +102,6 @@ Some services in the cluster provide service-level resource monitoring metrics. | | Number of Connections (by Client IP Address) | Displays the ZooKeeper client connection resource status. | +-----------------------+------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001442413925.png -.. |image2| image:: /_static/images/en-us_image_0000001392734010.png -.. |image3| image:: /_static/images/en-us_image_0000001392254926.png +.. |image1| image:: /_static/images/en-us_image_0000001369965777.png +.. |image2| image:: /_static/images/en-us_image_0000001318119582.png +.. |image3| image:: /_static/images/en-us_image_0263899644.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/overview.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/overview.rst index 482a505..659f380 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/overview.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/overview.rst @@ -165,5 +165,5 @@ You can click a service in the service list to perform simple maintenance and ma | | | MonitorServer: 1 min | | +-----------------+------------------+-----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001442773661.png -.. |image2| image:: /_static/images/en-us_image_0000001442773661.png +.. |image1| image:: /_static/images/en-us_image_0263899406.png +.. |image2| image:: /_static/images/en-us_image_0263899406.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/assigning_user_permissions_after_cross-cluster_mutual_trust_is_configured.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/assigning_user_permissions_after_cross-cluster_mutual_trust_is_configured.rst index cdf7809..ceed687 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/assigning_user_permissions_after_cross-cluster_mutual_trust_is_configured.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/assigning_user_permissions_after_cross-cluster_mutual_trust_is_configured.rst @@ -37,4 +37,4 @@ Procedure #. Log in to the other FusionInsight Manager and repeat :ref:`2 ` to :ref:`4 ` to create a user with the same name and set permissions. -.. |image1| image:: /_static/images/en-us_image_0000001442413857.png +.. |image1| image:: /_static/images/en-us_image_0263899656.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/changing_managers_domain_name.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/changing_managers_domain_name.rst index add391b..fa863f2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/changing_managers_domain_name.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/changing_managers_domain_name.rst @@ -128,23 +128,16 @@ Procedure 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. -7. Log in to FusionInsight Manager using the new password of user **admin** (for example, **Admin@123Admin@123**). On the dashboard, click |image1| next to the name of the target cluster and select **Restart**. +7. Log in to FusionInsight Manager using the new password of user **admin** (for example, **Admin@123Admin@123**). On the dashboard, click |image1| 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**. + In the displayed dialog box, enter the password of the current login user and click **OK**. - In the displayed dialog box, click **OK**. Wait for a while until a message indicating that the operation is successful is displayed. Click **Finish**. + In the displayed dialog box, click **OK**. Wait for a while until a message indicating that the operation is successful is displayed. Click **Finish**. -8. Log out of FusionInsight Manager and then log in again. If the login is successful, the configuration is successful. +8. Log out of FusionInsight Manager and then log in again. If the login is successful, the configuration is successful. -9. Log in to the active management node as user **omm** and run the following command to update the configurations of the job submission client: +9. Log in to the active management node as user **omm** and run the following command to update the configurations of the job submission client: - **sh /opt/executor/bin/refresh-client-config.sh** + **sh /opt/executor/bin/refresh-client-config.sh** -10. If a HetuEngine compute instance is running, restart the compute instance. - - a. Log in to FusionInsight Manager as the user who is used to access the HetuEngine web UI. - b. Choose **Cluster** > **Services** > **HetuEngine** to go to the HetuEngine service page. - c. In the **Basic Information** area on the **Dashboard** page, click the link next to **HSConsole WebUI**. The HSConsole page is displayed. - d. For a running compute instance, click **Stop** in the **Operation** column. After the compute instance is in the **Stopped** state, click **Start** to restart the compute instance. - -.. |image1| image:: /_static/images/en-us_image_0000001442773721.jpg +.. |image1| image:: /_static/images/en-us_image_0267694670.jpg diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/configuring_cross-manager_mutual_trust_between_clusters.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/configuring_cross-manager_mutual_trust_between_clusters.rst index 0df9a6e..ada3620 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/configuring_cross-manager_mutual_trust_between_clusters.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/cluster_mutual_trust_management/configuring_cross-manager_mutual_trust_between_clusters.rst @@ -94,7 +94,7 @@ Procedure #. Log in to the other FusionInsight Manager and repeat the preceding operations. -.. |image1| image:: /_static/images/en-us_image_0000001392254850.png -.. |image2| image:: /_static/images/en-us_image_0000001442773601.png -.. |image3| image:: /_static/images/en-us_image_0000001442413845.png -.. |image4| image:: /_static/images/en-us_image_0000001392414374.png +.. |image1| image:: /_static/images/en-us_image_0278119935.png +.. |image2| image:: /_static/images/en-us_image_0263899403.png +.. |image3| image:: /_static/images/en-us_image_0263899531.png +.. |image4| image:: /_static/images/en-us_image_0263899495.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/switching_to_the_maintenance_mode.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/switching_to_the_maintenance_mode.rst index 48c7262..8a4b165 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/switching_to_the_maintenance_mode.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/switching_to_the_maintenance_mode.rst @@ -86,9 +86,9 @@ Procedure After maintenance is complete, you can select services and hosts in batches in the maintenance mode view and click **Exit Maintenance Mode** to make them exit the maintenance mode. -.. |image1| image:: /_static/images/en-us_image_0000001392254954.png -.. |image2| image:: /_static/images/en-us_image_0000001392734042.png -.. |image3| image:: /_static/images/en-us_image_0000001442413957.png -.. |image4| image:: /_static/images/en-us_image_0000001442773713.png -.. |image5| image:: /_static/images/en-us_image_0000001392734038.png -.. |image6| image:: /_static/images/en-us_image_0000001442773709.png +.. |image1| image:: /_static/images/en-us_image_0263899304.png +.. |image2| image:: /_static/images/en-us_image_0263899339.png +.. |image3| image:: /_static/images/en-us_image_0263899293.png +.. |image4| image:: /_static/images/en-us_image_0263899476.png +.. |image5| image:: /_static/images/en-us_image_0263899363.png +.. |image6| image:: /_static/images/en-us_image_0263899235.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/fusioninsight_manager_introduction.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/fusioninsight_manager_introduction.rst index d59ff4b..7dffcdd 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/fusioninsight_manager_introduction.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/fusioninsight_manager_introduction.rst @@ -49,4 +49,4 @@ The upper part of the page is the operation bar, the middle part is the display | System | Provides system management settings of FusionInsight Manager, such as user permission settings. For details, see :ref:`System Configuration `. | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001392574002.png +.. |image1| image:: /_static/images/en-us_image_0000001388681282.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/logging_in_to_fusioninsight_manager.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/logging_in_to_fusioninsight_manager.rst index f08b4d6..1dfce85 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/logging_in_to_fusioninsight_manager.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/logging_in_to_fusioninsight_manager.rst @@ -28,4 +28,4 @@ Procedure #. Move the cursor over |image1| in the upper right corner of home page, and choose **Logout** from the drop-down list. In the dialog box that is displayed, click **OK** to log out of the current user. -.. |image1| image:: /_static/images/en-us_image_0000001392254934.png +.. |image1| image:: /_static/images/en-us_image_0000001388996278.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/querying_the_fusioninsight_manager_version.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/querying_the_fusioninsight_manager_version.rst index cf1838e..3918e7f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/querying_the_fusioninsight_manager_version.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/getting_started/querying_the_fusioninsight_manager_version.rst @@ -34,4 +34,4 @@ By viewing the FusionInsight Manager version, you can prepare for system upgrade **\**\*** indicates the version number. Replace it with the actual version number. -.. |image1| image:: /_static/images/en-us_image_0000001392414486.png +.. |image1| image:: /_static/images/en-us_image_0000001438954277.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/managing_monitoring_metric_reports.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/managing_monitoring_metric_reports.rst index 3e177f9..f943499 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/managing_monitoring_metric_reports.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/managing_monitoring_metric_reports.rst @@ -65,8 +65,8 @@ Exporting Monitoring Data of a Specified Monitoring Item #. Click **Export**. -.. |image1| image:: /_static/images/en-us_image_0000001442653701.png -.. |image2| image:: /_static/images/en-us_image_0000001392414434.png -.. |image3| image:: /_static/images/en-us_image_0000001442494085.png -.. |image4| image:: /_static/images/en-us_image_0000001392254902.png -.. |image5| image:: /_static/images/en-us_image_0000001442773665.png +.. |image1| image:: /_static/images/en-us_image_0263899329.png +.. |image2| image:: /_static/images/en-us_image_0263899610.png +.. |image3| image:: /_static/images/en-us_image_0263899528.png +.. |image4| image:: /_static/images/en-us_image_0263899289.png +.. |image5| image:: /_static/images/en-us_image_0263899471.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/overview.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/overview.rst index c0de1bc..a1a4fd4 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/overview.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/home_page/overview.rst @@ -54,11 +54,11 @@ Alarm Analysis On the **Alarm Analysis** tab page, you can view the **Top 20 Alarms** table and **Analysis on Top 3 Alarms** chart. You can click an alarm name in the **Top 20 Alarms** table to view analysis information of this alarm only. Alarm analysis allows you to view top alarms and their occurrence time so you can handle alarms accordingly, improving system stability. -.. |image1| image:: /_static/images/en-us_image_0000001392734034.png -.. |image2| image:: /_static/images/en-us_image_0000001442494125.png -.. |image3| image:: /_static/images/en-us_image_0000001392254958.png -.. |image4| image:: /_static/images/en-us_image_0000001442653741.png -.. |image5| image:: /_static/images/en-us_image_0000001392574078.png -.. |image6| image:: /_static/images/en-us_image_0000001442653745.png -.. |image7| image:: /_static/images/en-us_image_0000001442653749.png -.. |image8| image:: /_static/images/en-us_image_0000001392414490.png +.. |image1| image:: /_static/images/en-us_image_0000001388835338.png +.. |image2| image:: /_static/images/en-us_image_0000001438841461.png +.. |image3| image:: /_static/images/en-us_image_0263899453.png +.. |image4| image:: /_static/images/en-us_image_0263899217.png +.. |image5| image:: /_static/images/en-us_image_0263899616.png +.. |image6| image:: /_static/images/en-us_image_0263899555.png +.. |image7| image:: /_static/images/en-us_image_0263899343.png +.. |image8| image:: /_static/images/en-us_image_0263899493.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_maintenance_operations/configuring_racks_for_hosts.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_maintenance_operations/configuring_racks_for_hosts.rst index c94c913..3436a0c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_maintenance_operations/configuring_racks_for_hosts.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_maintenance_operations/configuring_racks_for_hosts.rst @@ -84,4 +84,4 @@ Procedure #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001392414418.png +.. |image1| image:: /_static/images/en-us_image_0263899649.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_management_page/viewing_the_host_dashboard.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_management_page/viewing_the_host_dashboard.rst index 842cfe3..7950038 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_management_page/viewing_the_host_dashboard.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/host_management_page/viewing_the_host_dashboard.rst @@ -46,6 +46,6 @@ GPU Card Status Area If the host is configured with GPU cards, the GPU card status area displays the model, location, and status of the GPU card installed on the host. -.. |image1| image:: /_static/images/en-us_image_0000001392414478.png -.. |image2| image:: /_static/images/en-us_image_0000001392254950.png -.. |image3| image:: /_static/images/en-us_image_0000001442773705.png +.. |image1| image:: /_static/images/en-us_image_0263899316.png +.. |image2| image:: /_static/images/en-us_image_0263899637.png +.. |image3| image:: /_static/images/en-us_image_0263899593.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/cluster.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/cluster.rst index 3447f22..6e8c860 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/cluster.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/cluster.rst @@ -10,7 +10,7 @@ Log in to FusionInsight Manager and choose **Hosts** > **Resource Overview**. On By default, the monitoring data of the past one hour (**1h**) is displayed. You can click |image1| to customize a time range. Time range options are **1h**, **2h**, **6h**, **12h**, **1d**, **1w**, and **1m**. -.. figure:: /_static/images/en-us_image_0000001442653713.png +.. figure:: /_static/images/en-us_image_0000001369944573.png :alt: **Figure 1** Cluster tab **Figure 1** Cluster tab @@ -19,5 +19,5 @@ By default, the monitoring data of the past one hour (**1h**) is displayed. You - You can choose |image2| > **Customize** to customize the metrics to display on the tab page. For details about the metrics, see :ref:`Table 1 ` in :ref:`Distribution `. - You can click **Export Data** to export the metric values of each cluster within the time range you have specified. -.. |image1| image:: /_static/images/en-us_image_0000001392414454.png -.. |image2| image:: /_static/images/en-us_image_0000001442494097.png +.. |image1| image:: /_static/images/en-us_image_0000001318157588.png +.. |image2| image:: /_static/images/en-us_image_0263899311.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/distribution.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/distribution.rst index b2d2261..a354164 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/distribution.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/distribution.rst @@ -9,7 +9,7 @@ Log in to FusionInsight Manager and choose **Hosts** > **Resource Overview**. On .. _admin_guide_000064__fig10343181024812: -.. figure:: /_static/images/en-us_image_0000001442773633.png +.. figure:: /_static/images/en-us_image_0000001087459671.png :alt: **Figure 1** Distribution tab **Figure 1** Distribution tab @@ -86,4 +86,4 @@ Log in to FusionInsight Manager and choose **Hosts** > **Resource Overview**. On | | - Host PID Usage | +-----------------------------------+--------------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001392733954.png +.. |image1| image:: /_static/images/en-us_image_0000001318123498.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/host.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/host.rst index 2cebb2b..b5799b1 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/host.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/host.rst @@ -10,7 +10,7 @@ Log in to FusionInsight Manager and choose **Hosts** > **Resource Overview**. On You can click **Export Data** to export the configuration list of all hosts in the cluster, including the host name, management IP address, host type, number of cores, CPU architecture, memory capacity, and disk size. -.. figure:: /_static/images/en-us_image_0000001392254918.png +.. figure:: /_static/images/en-us_image_0000001369746545.png :alt: **Figure 1** Host tab **Figure 1** Host tab diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/trend.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/trend.rst index 8cc97c8..734d51e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/trend.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/hosts/resource_overview/trend.rst @@ -8,7 +8,7 @@ Trend Log in to FusionInsight and choose **Hosts** > **Resource Overview**. On the **Resource Overview** page that is displayed, click the **Trend** tab to view resource trends of all clusters or a single cluster. By default, the monitoring data of the past one hour (**1h**) is displayed. You can click |image1| to customize a time range. Time range options are **1h**, **2h**, **6h**, **12h**, **1d**, **1w**, and **1m**. By default, the trend chart of each metric displays the maximum, minimum, and average values of the entire cluster. -.. figure:: /_static/images/en-us_image_0000001442773637.png +.. figure:: /_static/images/en-us_image_0000001370061921.png :alt: **Figure 1** Trend tab **Figure 1** Trend tab @@ -17,5 +17,5 @@ Log in to FusionInsight and choose **Hosts** > **Resource Overview**. On the **R - You can choose |image2| > **Customize** to customize the metrics to display on the tab page. For details about the metrics, see :ref:`Table 1 ` in :ref:`Distribution `. - You can click **Export Data** to export the maximum, minimum, and average values of all nodes in the cluster for all selected metrics within the time range you have specified. -.. |image1| image:: /_static/images/en-us_image_0000001442653669.png -.. |image2| image:: /_static/images/en-us_image_0000001392573998.png +.. |image1| image:: /_static/images/en-us_image_0000001369965785.png +.. |image2| image:: /_static/images/en-us_image_0263899424.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/log_management/viewing_role_instance_logs.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/log_management/viewing_role_instance_logs.rst index efca3c5..8372310 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/log_management/viewing_role_instance_logs.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/log_management/viewing_role_instance_logs.rst @@ -25,7 +25,7 @@ Procedure - By default, a maximum of 100 lines of logs can be displayed. You can click **Load More** to view more logs. Click **Download** to download the log file to the local PC. For details about how to download service logs in batches, see :ref:`Log Download `. - .. figure:: /_static/images/en-us_image_0000001392254946.png + .. figure:: /_static/images/en-us_image_0000001318160568.png :alt: **Figure 1** Viewing instance logs **Figure 1** Viewing instance logs diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_alarm_masking_status.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_alarm_masking_status.rst index da915de..cde5aa9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_alarm_masking_status.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_alarm_masking_status.rst @@ -28,7 +28,7 @@ Procedure #. Select an alarm from the alarm list. - .. figure:: /_static/images/en-us_image_0000001392733962.png + .. figure:: /_static/images/en-us_image_0000001369953797.png :alt: **Figure 1** Masking an alarm **Figure 1** Masking an alarm diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_threshold.rst index 6156d22..be3d920 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/configuring_the_threshold.rst @@ -20,7 +20,7 @@ Procedure #. Select a monitoring metric for a host or service in the cluster. - .. figure:: /_static/images/en-us_image_0000001442413885.png + .. figure:: /_static/images/en-us_image_0263899436.png :alt: **Figure 1** Configuring the threshold for a metric **Figure 1** Configuring the threshold for a metric @@ -358,6 +358,6 @@ FusionInsight Manager alarm monitoring metrics are classified as node informatio | | | Capacity quota usage of the Clickhouse service in ZooKeeper | Capacity quota of ZooKeeper directory used by the ClickHouse service | 90% | +------------+---------------------------------+------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+-------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001392574010.png -.. |image2| image:: /_static/images/en-us_image_0000001392254890.png -.. |image3| image:: /_static/images/en-us_image_0000001442653685.png +.. |image1| image:: /_static/images/en-us_image_0263899498.png +.. |image2| image:: /_static/images/en-us_image_0263899452.png +.. |image3| image:: /_static/images/en-us_image_0263899582.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/overview_of_alarms_and_events.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/overview_of_alarms_and_events.rst index a6fcf6e..87a7d1c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/overview_of_alarms_and_events.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/alarms/overview_of_alarms_and_events.rst @@ -67,7 +67,7 @@ Events Log in to FusionInsight Manager and choose **O&M** > **Alarm** > **Events**. On the **Events** page that is displayed, you can view information about all events in the cluster, including the event name, ID, severity, generation time, object, and location. By default, the latest 10 events are displayed on each page. -.. figure:: /_static/images/en-us_image_0000001392254906.png +.. figure:: /_static/images/en-us_image_0263899271.png :alt: **Figure 1** Events page **Figure 1** Events page @@ -114,9 +114,9 @@ You can click |image4| on the left of an event to view detailed event parameters - You can filter events by object or cluster. - You can click **Advanced Search** to search for events by event ID, name, severity, start time, or end time. -.. |image1| image:: /_static/images/en-us_image_0000001392574038.png -.. |image2| image:: /_static/images/en-us_image_0000001392574030.png -.. |image3| image:: /_static/images/en-us_image_0000001392414438.png -.. |image4| image:: /_static/images/en-us_image_0000001392414442.png -.. |image5| image:: /_static/images/en-us_image_0000001392574030.png -.. |image6| image:: /_static/images/en-us_image_0000001392733994.png +.. |image1| image:: /_static/images/en-us_image_0263899504.png +.. |image2| image:: /_static/images/en-us_image_0263899662.png +.. |image3| image:: /_static/images/en-us_image_0263899597.png +.. |image4| image:: /_static/images/en-us_image_0263899384.png +.. |image5| image:: /_static/images/en-us_image_0263899662.png +.. |image6| image:: /_static/images/en-us_image_0000001318636944.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_download.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_download.rst index c51d71f..22d272f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_download.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_download.rst @@ -35,6 +35,6 @@ Procedure 192.168.204.124|suse-124|DBService:DBServer;KrbClient:KerberosClient;LdapClient:SlapdClient;LdapServer:SlapdServer;Manager:Manager;meta:meta -.. |image1| image:: /_static/images/en-us_image_0000001392254938.png -.. |image2| image:: /_static/images/en-us_image_0000001392414466.png -.. |image3| image:: /_static/images/en-us_image_0000001392574062.png +.. |image1| image:: /_static/images/en-us_image_0263899401.png +.. |image2| image:: /_static/images/en-us_image_0263899334.png +.. |image3| image:: /_static/images/en-us_image_0000001369965781.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_online_search.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_online_search.rst index 46d745e..55665cc 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_online_search.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o_and_m/log/log_online_search.rst @@ -101,5 +101,5 @@ Procedure Source Cluster Cluster for which logs need to be searched ============== ========================================== -.. |image1| image:: /_static/images/en-us_image_0000001442413841.png -.. |image2| image:: /_static/images/en-us_image_0000001442773597.png +.. |image1| image:: /_static/images/en-us_image_0000001369765661.png +.. |image2| image:: /_static/images/en-us_image_0263899392.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hfile_and_wal_encryption.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hfile_and_wal_encryption.rst index d003962..0c0a6a6 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hfile_and_wal_encryption.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hfile_and_wal_encryption.rst @@ -241,4 +241,4 @@ During the :ref:`HFile and WAL Encryption ` for the configuration take effect. -.. |image1| image:: /_static/images/en-us_image_0000001392734050.png +.. |image1| image:: /_static/images/en-us_image_0000001369886993.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/updating_ssh_keys_for_user_omm.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/updating_ssh_keys_for_user_omm.rst index d10ff66..700bd2c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/updating_ssh_keys_for_user_omm.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/updating_ssh_keys_for_user_omm.rst @@ -83,4 +83,4 @@ Procedure 12. Log in to FusionInsight Manager. On **Homepage**, locate the desired cluster and choose |image1| > **Start** to start the cluster. -.. |image1| image:: /_static/images/en-us_image_0000001442773649.png +.. |image1| image:: /_static/images/en-us_image_0263899299.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/default_permission_information.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/default_permission_information.rst index 983edb8..36005a6 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/default_permission_information.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/default_permission_information.rst @@ -58,15 +58,15 @@ User group +---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | hadoopmanager | Users added to this user group can have the O&M manager rights of HDFS and Yarn. The O&M manager of HDFS can access the NameNode WebUI and perform active to standby switchover manually. The O&M manager of Yarn can access the ResourceManager WebUI, operate NodeManager nodes, refresh queues, and set node labels, but cannot submit tasks. | +---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| | hetuadmin | HetuEngine administrator group. Users in this group have the permission to perform operations on HSConsole. | -+---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | hive | Common user group. Hive users must belong to this user group. | +---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| | cdladmin | CDL administrator group. Only users in this group can access CDL APIs. | +| | hive1 | Common user group. Hive1 users must belong to this user group. | +---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| | cdl | Common user group of CDL. Users in this group can create and query CDL jobs. | +| | hive2 | Common user group. Hive2 users must belong to this user group. | +---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| | iotdbgroup | Users added to this user group have the administrator rights of the IoTDB component. | +| | hive3 | Common user group. Hive3 users must belong to this user group. | ++---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| | hive4 | Common user group. Hive4 users must belong to this user group. | +---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | kafka | Kafka common user group. A user in this group can access a topic only when a user in the kafkaadmin group grants the read and write permission of the topic to the user. | +---------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/permission_verification_policies.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/permission_verification_policies.rst index 8f3965a..42554b5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/permission_verification_policies.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/permission_verification_policies.rst @@ -74,4 +74,4 @@ The following figure shows the process of determining condition priorities. If t For example, if you want to grant the read and write permissions of the **FileA** folder to the **groupA** user group, but the user in the group is not **UserA**, you can add an allowed condition and an exception condition. -.. |image1| image:: /_static/images/en-us_image_0000001392733938.png +.. |image1| image:: /_static/images/en-us_image_0265768517.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/right_model.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/right_model.rst index 8501f2b..2c61b99 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/right_model.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/right_model.rst @@ -13,7 +13,7 @@ FusionInsight adopts the role-based access control (RBAC) mode to manage rights The right model of FusionInsight consists four parts, that is users, user groups, roles, and rights. -.. figure:: /_static/images/en-us_image_0000001392574050.png +.. figure:: /_static/images/en-us_image_0263899538.png :alt: **Figure 1** Right model **Figure 1** Right model diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/user_account_list.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/user_account_list.rst index e55b844..72279df 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/user_account_list.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_overview/user_account_list.rst @@ -55,315 +55,471 @@ System Users Internal System Users --------------------- -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| User Type | Default User | Initial Password | Description | Password Change Method | -+============================+============================================+==================================+==================================================================================================================================================================================================================================================================================+=======================================================================================================================================+ -| Kerberos administrator | kadmin/admin | Admin@123 | Used to add, delete, modify, and query user accounts on Kerberos. | For details, see :ref:`Changing the Password for the Kerberos Administrator `. | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| OMS Kerberos administrator | kadmin/admin | Admin@123 | Used to add, delete, modify, and query user accounts on OMS Kerberos. | For details, see :ref:`Changing the Password for the OMS Kerberos Administrator `. | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| LDAP administrator | cn=root,dc=hadoop,dc=com | LdapChangeMe@123 | Used to add, delete, modify, and query the user account information on LDAP. | For details, see :ref:`Changing the Passwords of the LDAP Administrator and the LDAP User (Including OMS LDAP) `. | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| OMS LDAP administrator | cn=root,dc=hadoop,dc=com | LdapChangeMe@123 | Used to add, delete, modify, and query the user account information on OMS LDAP. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| LDAP user | cn=pg_search_dn,ou=Users,dc=hadoop,dc=com | Randomly generated by the system | Used to query information about users and user groups on LDAP. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| OMS LDAP user | cn=pg_search_dn,ou=Users,dc=hadoop,dc=com | Randomly generated by the system | Used to query information about users and user groups on OMS LDAP. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| LDAP administrator account | cn=krbkdc,ou=Users,dc=hadoop,dc=com | LdapChangeMe@123 | Used to query Kerberos component authentication account information. | For details, see :ref:`Changing the Password for the LDAP Administrator `. | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | cn=krbadmin,ou=Users,dc=hadoop,dc=com | LdapChangeMe@123 | Used to add, delete, modify, and query Kerberos component authentication account information. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| Component running user | cdl | CDCUser123! | CDL system administrator | For details, see :ref:`Changing the Password for a Component Running User `. | -| | | | | | -| | | | Currently, user permissions are not involved in CDL. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | iotdb | Iotdb@123 | This user is the IoTDB system administrator and has the following user permissions: | | -| | | | | | -| | | | #. IoTDB administrator permissions: | | -| | | | | | -| | | | - Creates or deletes a storage group. | | -| | | | - Uses TTL. | | -| | | | | | -| | | | #. IoTDB data operation permissions: | | -| | | | | | -| | | | - Creates, modifies, and deletes a time sequence. | | -| | | | - Writes, reads, and deletes data in a time sequence. | | -| | | | | | -| | | | #. Views user or role permission information. | | -| | | | #. Grants or revokes permissions to or from a user or role. | | -| | | | | | -| | | | .. note:: | | -| | | | | | -| | | | In a common cluster, the IoTDB service retains the open-source feature. The default username is **root**, and the default password is **root**. This user is an administrator and has all permissions, which cannot be assigned, revoked, or deleted. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hetuserver/hadoop.\ ** | Randomly generated by the system | This user is used to start HetuEngine and has the following permissions: | | -| | | | | | -| | | | - Accesses KrbServer and HDFS files in the cluster from HetuEngine. | | -| | | | - Used for communication between HetuEngine internal nodes. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hdfs | Hdfs@123 | This user is the HDFS system administrator and has the following permissions: | | -| | | | | | -| | | | #. File system operation permissions: | | -| | | | | | -| | | | - Views, modifies, and creates files. | | -| | | | - Views and creates directories. | | -| | | | - Views and modifies the groups where files belong. | | -| | | | - Views and sets disk quotas for users. | | -| | | | | | -| | | | #. HDFS management operation permissions: | | -| | | | | | -| | | | - Views the web UI status. | | -| | | | - Views and sets the active and standby HDFS status. | | -| | | | - Enters and exits the HDFS in security mode. | | -| | | | - Checks the HDFS file system. | | -| | | | | | -| | | | #. Logs in to the FTP service page. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hbase | Hbase@123 | This user is the HBase and HBase1 to HBase4 system administrator and has the following permissions: | | -| | | | | | -| | | | - Cluster management permission: Performs **Enable** and **Disable** operations on tables to trigger MajorCompact and ACL operations. | | -| | | | - Grants and revokes permissions, and shuts down the cluster. | | -| | | | - Table management permission: Creates, modifies, and deletes tables. | | -| | | | - Data management permission: Reads data in tables, column families, and columns. | | -| | | | - Logs in to the HMaster web UI. | | -| | | | - Logs in to the FTP service page. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | mapred | Mapred@123 | This user is the MapReduce system administrator and has the following permissions: | | -| | | | | | -| | | | - Submits, stops, and views the MapReduce tasks. | | -| | | | - Modifies the Yarn configuration parameters. | | -| | | | - Logs in to the FTP service page. | | -| | | | - Logs in to the Yarn web UI. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | zookeeper | ZooKeeper@123 | This user is the ZooKeeper system administrator and has the following permissions: | | -| | | | | | -| | | | - Adds, deletes, modifies, and queries all nodes in ZooKeeper. | | -| | | | - Modifies and queries quotas of all nodes in ZooKeeper. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | rangeradmin | Rangeradmin@123 | This user has the Ranger system management permissions and user permissions: | | -| | | | | | -| | | | - Ranger web UI management permission | | -| | | | - Management permission of each component that uses Ranger authentication | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | rangerauditor | Rangerauditor@123 | Default audit user of the Ranger system. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hive | Hive@123 | This user is the Hive system administrator and has the following permissions: | | -| | | | | | -| | | | #. Hive administrator permissions: | | -| | | | | | -| | | | - Creates, deletes, and modifies a database. | | -| | | | - Creates, queries, modifies, and deletes a table. | | -| | | | - Queries, inserts, and uploads data. | | -| | | | | | -| | | | #. HDFS file operation permissions: | | -| | | | | | -| | | | - Views, modifies, and creates files. | | -| | | | - Views and creates directories. | | -| | | | - Views and modifies the groups where files belong. | | -| | | | | | -| | | | #. Submits and stops the MapReduce tasks. | | -| | | | #. Ranger policy management permission | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | kafka | Kafka@123 | This user is the Kafka system administrator and has the following permissions: | | -| | | | | | -| | | | - Creates, deletes, produces, and consumes the topic; modifies the topic configuration. | | -| | | | - Controls the cluster metadata, modifies the configuration, migrates the replica, elects the leader, and manages ACL. | | -| | | | - Submits, queries, and deletes the consumer group offset. | | -| | | | - Queries the delegation token. | | -| | | | - Queries and submits the transaction. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | storm | Admin@123 | Storm system administrator | | -| | | | | | -| | | | User permission: Submits Storm tasks. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | rangerusersync | Randomly generated by the system | Synchronizes users and internal users of user groups. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | rangertagsync | Randomly generated by the system | Internal user for synchronizing tags. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | oms/manager | Randomly generated by the system | Controller and NodeAgent authentication user. The user has the permission on the **supergroup** group. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | backup/manager | Randomly generated by the system | User for running backup and restoration tasks. The user has the permission on the **supergroup**, **wheel**, and **ficommon** groups. After cross-system mutual trust is configured, the user has the permission to access data in the HDFS, HBase, Hive, and ZooKeeper systems. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hdfs/hadoop.\ ** | Randomly generated by the system | This user is used to start the HDFS and has the following permissions: | | -| | | | | | -| | | | #. File system operation permissions: | | -| | | | | | -| | | | - Views, modifies, and creates files. | | -| | | | - Views and creates directories. | | -| | | | - Views and modifies the groups where files belong. | | -| | | | - Views and sets disk quotas for users. | | -| | | | | | -| | | | #. HDFS management operation permissions: | | -| | | | | | -| | | | - Views the web UI status. | | -| | | | - Views and sets the active and standby HDFS status. | | -| | | | - Enters and exits the HDFS in security mode. | | -| | | | - Checks the HDFS file system. | | -| | | | | | -| | | | #. Logs in to the FTP service page. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | mapred/hadoop.\ ** | Randomly generated by the system | This user is used to start the MapReduce and has the following permissions: | | -| | | | | | -| | | | - Submits, stops, and views the MapReduce tasks. | | -| | | | - Modifies the Yarn configuration parameters. | | -| | | | - Logs in to the FTP service page. | | -| | | | - Logs in to the Yarn web UI. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | mr_zk/hadoop.\ ** | Randomly generated by the system | Used for MapReduce to access ZooKeeper. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hbase/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the HBase system startup. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hbase/zkclient.\ ** | Randomly generated by the system | User for HBase to perform ZooKeeper authentication in a security mode cluster. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | thrift/hadoop.\ ** | Randomly generated by the system | ThriftServer system startup user. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | thrift/** | Randomly generated by the system | User for the ThriftServer system to access HBase. This user has the read, write, execution, creation, and administration permission on all NameSpaces and tables of HBase. ** indicates the name of the host where the ThriftServer node is installed in the cluster. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hive/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the Hive system startup. The user permissions are as follows: | | -| | | | | | -| | | | #. Hive administrator permissions: | | -| | | | | | -| | | | - Creates, deletes, and modifies a database. | | -| | | | - Creates, queries, modifies, and deletes a table. | | -| | | | - Queries, inserts, and uploads data. | | -| | | | | | -| | | | #. HDFS file operation permissions: | | -| | | | | | -| | | | - Views, modifies, and creates files. | | -| | | | - Views and creates directories. | | -| | | | - Views and modifies the groups where files belong. | | -| | | | | | -| | | | #. Submits and stops the MapReduce tasks. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | loader/hadoop.\ ** | Randomly generated by the system | User for Loader system startup and Kerberos authentication | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | HTTP/** | Randomly generated by the system | Used to connect to the HTTP interface of each component. ** indicates the host name of a node in the cluster. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hue | Randomly generated by the system | User for Hue system startup, Kerberos authentication, and HDFS and Hive access | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | flume | Randomly generated by the system | User for Flume system startup and HDFS and Kafka access. The user has read and write permission of the HDFS directory **/flume**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | flume_server | Randomly generated by the system | User for Flume system startup and HDFS and Kafka access. The user has read and write permission of the HDFS directory **/flume**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | spark2x/hadoop.\ ** | Randomly generated by the system | This user is the Spark2x system administrator and has the following user permissions: | | -| | | | | | -| | | | 1. Starts the Spark2x service. | | -| | | | | | -| | | | 2. Submits Spark2x tasks. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | spark_zk/hadoop.\ ** | Randomly generated by the system | Used for Spark2x to access ZooKeeper. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | zookeeper/hadoop.\ ** | Randomly generated by the system | ZooKeeper system startup user. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | zkcli/hadoop.\ ** | Randomly generated by the system | ZooKeeper server login user. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | oozie | Randomly generated by the system | User for Oozie system startup and Kerberos authentication. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | kafka/hadoop.\ ** | Randomly generated by the system | Used for security authentication of Kafka. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | storm/hadoop.\ ** | Randomly generated by the system | Storm system startup user. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | storm_zk/hadoop.\ ** | Randomly generated by the system | Used for the Worker process to access ZooKeeper. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | flink/hadoop.\ ** | Randomly generated by the system | Internal user of the Flink service. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | check_ker_M | Randomly generated by the system | User who performs a system internal test about whether the Kerberos service is normal. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | tez | Randomly generated by the system | User for TezUI system startup, Kerberos authentication, and access to Yarn | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | K/M | Randomly generated by the system | Kerberos internal functional user. This user cannot be deleted, and its password cannot be changed. This internal account can only be used on nodes where Kerberos service is installed. | None | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | kadmin/changepw | Randomly generated by the system | | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | kadmin/history | Randomly generated by the system | | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | krbtgt\ ** | Randomly generated by the system | | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| LDAP user | admin | None | FusionInsight Manager administrator. | The LDAP user cannot log in to the system, and the password cannot be changed. | -| | | | | | -| | | | The primary group is **compcommon**, which does not have the group permission but has the permission of the **Manager_administrator** role. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | backup | | The primary group is **compcommon**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | backup/manager | | The primary group is **compcommon**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | oms | | The primary group is **compcommon**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | oms/manager | | The primary group is **compcommon**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | clientregister | | The primary group is **compcommon**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | zookeeper | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | zookeeper/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | zkcli | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | zkcli/hadoop.<*System domain name*> | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | flume | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | flume_server | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hdfs | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hdfs/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | mapred | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | mapred/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | mr_zk | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | mr_zk/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hue | | The primary group is **supergroup**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hive | | The primary group is **hive**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hive/hadoop.\ ** | | The primary group is **hive**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hbase | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hbase/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | thrift | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | thrift/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | oozie | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | hbase/zkclient.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | loader | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | loader/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | spark2x | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | spark2x/hadoop.\ ** | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | spark_zk | | The primary group is **hadoop**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | kafka | | The primary group is **kafkaadmin**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | kafka/hadoop.\ ** | | The primary group is **kafkaadmin**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | storm | | The primary group is **stormadmin**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | storm/hadoop.\ ** | | The primary group is **stormadmin**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | storm_zk | | The primary group is **storm**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | storm_zk/hadoop.\ ** | | The primary group is **storm**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | kms/hadoop | | The primary group is **kmsadmin**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | knox | | The primary group is **compcommon**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ -| | executor | | The primary group is **compcommon**. | | -+----------------------------+--------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| User Type | Default User | Initial Password | Description | Password Change Method | ++============================+===========================================+==================================+==================================================================================================================================================================================================================================================================================+=======================================================================================================================================+ +| Kerberos administrator | kadmin/admin | Admin@123 | Used to add, delete, modify, and query user accounts on Kerberos. | For details, see :ref:`Changing the Password for the Kerberos Administrator `. | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| OMS Kerberos administrator | kadmin/admin | Admin@123 | Used to add, delete, modify, and query user accounts on OMS Kerberos. | For details, see :ref:`Changing the Password for the OMS Kerberos Administrator `. | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| LDAP administrator | cn=root,dc=hadoop,dc=com | LdapChangeMe@123 | Used to add, delete, modify, and query the user account information on LDAP. | For details, see :ref:`Changing the Passwords of the LDAP Administrator and the LDAP User (Including OMS LDAP) `. | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| OMS LDAP administrator | cn=root,dc=hadoop,dc=com | LdapChangeMe@123 | Used to add, delete, modify, and query the user account information on OMS LDAP. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| LDAP user | cn=pg_search_dn,ou=Users,dc=hadoop,dc=com | Randomly generated by the system | Used to query information about users and user groups on LDAP. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| OMS LDAP user | cn=pg_search_dn,ou=Users,dc=hadoop,dc=com | Randomly generated by the system | Used to query information about users and user groups on OMS LDAP. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| LDAP administrator account | cn=krbkdc,ou=Users,dc=hadoop,dc=com | LdapChangeMe@123 | Used to query Kerberos component authentication account information. | For details, see :ref:`Changing the Password for the LDAP Administrator `. | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | cn=krbadmin,ou=Users,dc=hadoop,dc=com | LdapChangeMe@123 | Used to add, delete, modify, and query Kerberos component authentication account information. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| Component running user | hdfs | Hdfs@123 | This user is the HDFS system administrator and has the following permissions: | For details, see :ref:`Changing the Password for a Component Running User `. | +| | | | | | +| | | | #. File system operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | - Views and sets disk quotas for users. | | +| | | | | | +| | | | #. HDFS management operation permissions: | | +| | | | | | +| | | | - Views the web UI status. | | +| | | | - Views and sets the active and standby HDFS status. | | +| | | | - Enters and exits the HDFS in security mode. | | +| | | | - Checks the HDFS file system. | | +| | | | | | +| | | | #. Logs in to the FTP service page. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hbase | Hbase@123 | This user is the HBase and HBase1 to HBase4 system administrator and has the following permissions: | | +| | | | | | +| | | | - Cluster management permission: Performs **Enable** and **Disable** operations on tables to trigger MajorCompact and ACL operations. | | +| | | | - Grants and revokes permissions, and shuts down the cluster. | | +| | | | - Table management permission: Creates, modifies, and deletes tables. | | +| | | | - Data management permission: Reads data in tables, column families, and columns. | | +| | | | - Logs in to the HMaster web UI. | | +| | | | - Logs in to the FTP service page. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | mapred | Mapred@123 | This user is the MapReduce system administrator and has the following permissions: | | +| | | | | | +| | | | - Submits, stops, and views the MapReduce tasks. | | +| | | | - Modifies the Yarn configuration parameters. | | +| | | | - Logs in to the FTP service page. | | +| | | | - Logs in to the Yarn web UI. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | zookeeper | ZooKeeper@123 | This user is the ZooKeeper system administrator and has the following permissions: | | +| | | | | | +| | | | - Adds, deletes, modifies, and queries all nodes in ZooKeeper. | | +| | | | - Modifies and queries quotas of all nodes in ZooKeeper. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | rangeradmin | Rangeradmin@123 | This user has the Ranger system management permissions and user permissions: | | +| | | | | | +| | | | - Ranger web UI management permission | | +| | | | - Management permission of each component that uses Ranger authentication | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | rangerauditor | Rangerauditor@123 | Default audit user of the Ranger system. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive | Hive@123 | This user is the Hive system administrator and has the following permissions: | | +| | | | | | +| | | | #. Hive administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | +| | | | #. Ranger policy management permission | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive1 | Hive1@123 | This user is the Hive1 system administrator and has the following permissions: | | +| | | | | | +| | | | #. Hive1 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | +| | | | #. Ranger policy management permission | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive2 | Hive2@123 | This user is the Hive2 system administrator and has the following permissions: | | +| | | | | | +| | | | #. Hive2 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | +| | | | #. Ranger policy management permission | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive3 | Hive3@123 | This user is the Hive3 system administrator and has the following permissions: | | +| | | | | | +| | | | #. Hive3 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | +| | | | #. Ranger policy management permission | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive4 | Hive4@123 | This user is the Hive4 system administrator and has the following permissions: | | +| | | | | | +| | | | #. Hive4 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | +| | | | #. Ranger policy management permission | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | kafka | Kafka@123 | This user is the Kafka system administrator and has the following permissions: | | +| | | | | | +| | | | - Creates, deletes, produces, and consumes the topic; modifies the topic configuration. | | +| | | | - Controls the cluster metadata, modifies the configuration, migrates the replica, elects the leader, and manages ACL. | | +| | | | - Submits, queries, and deletes the consumer group offset. | | +| | | | - Queries the delegation token. | | +| | | | - Queries and submits the transaction. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | storm | Admin@123 | Storm system administrator | | +| | | | | | +| | | | User permission: Submits Storm tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | rangerusersync | Randomly generated by the system | Synchronizes users and internal users of user groups. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | rangertagsync | Randomly generated by the system | Internal user for synchronizing tags. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | oms/manager | Randomly generated by the system | Controller and NodeAgent authentication user. The user has the permission on the **supergroup** group. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | backup/manager | Randomly generated by the system | User for running backup and restoration tasks. The user has the permission on the **supergroup**, **wheel**, and **ficommon** groups. After cross-system mutual trust is configured, the user has the permission to access data in the HDFS, HBase, Hive, and ZooKeeper systems. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hdfs/hadoop.\ ** | Randomly generated by the system | This user is used to start the HDFS and has the following permissions: | | +| | | | | | +| | | | #. File system operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | - Views and sets disk quotas for users. | | +| | | | | | +| | | | #. HDFS management operation permissions: | | +| | | | | | +| | | | - Views the web UI status. | | +| | | | - Views and sets the active and standby HDFS status. | | +| | | | - Enters and exits the HDFS in security mode. | | +| | | | - Checks the HDFS file system. | | +| | | | | | +| | | | #. Logs in to the FTP service page. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | mapred/hadoop.\ ** | Randomly generated by the system | This user is used to start the MapReduce and has the following permissions: | | +| | | | | | +| | | | - Submits, stops, and views the MapReduce tasks. | | +| | | | - Modifies the Yarn configuration parameters. | | +| | | | - Logs in to the FTP service page. | | +| | | | - Logs in to the Yarn web UI. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | mr_zk/hadoop.\ ** | Randomly generated by the system | Used for MapReduce to access ZooKeeper. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hbase/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the HBase system startup. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hbase/zkclient.\ ** | Randomly generated by the system | User for HBase to perform ZooKeeper authentication in a security mode cluster. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | thrift/hadoop.\ ** | Randomly generated by the system | ThriftServer system startup user. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | thrift/** | Randomly generated by the system | User for the ThriftServer system to access HBase. This user has the read, write, execution, creation, and administration permission on all NameSpaces and tables of HBase. ** indicates the name of the host where the ThriftServer node is installed in the cluster. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the Hive system startup. The user permissions are as follows: | | +| | | | | | +| | | | #. Hive administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive1/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the Hive1 system startup. The user permissions are as follows: | | +| | | | | | +| | | | #. Hive1 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive2/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the Hive2 system startup. The user permissions are as follows: | | +| | | | | | +| | | | #. Hive2 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive3/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the Hive3 system startup. The user permissions are as follows: | | +| | | | | | +| | | | #. Hive3 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive4/hadoop.\ ** | Randomly generated by the system | User for the authentication between internal components during the Hive4 system startup. The user permissions are as follows: | | +| | | | | | +| | | | #. Hive4 administrator permissions: | | +| | | | | | +| | | | - Creates, deletes, and modifies a database. | | +| | | | - Creates, queries, modifies, and deletes a table. | | +| | | | - Queries, inserts, and uploads data. | | +| | | | | | +| | | | #. HDFS file operation permissions: | | +| | | | | | +| | | | - Views, modifies, and creates files. | | +| | | | - Views and creates directories. | | +| | | | - Views and modifies the groups where files belong. | | +| | | | | | +| | | | #. Submits and stops the MapReduce tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | loader/hadoop.\ ** | Randomly generated by the system | User for Loader system startup and Kerberos authentication | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | HTTP/** | Randomly generated by the system | Used to connect to the HTTP interface of each component. ** indicates the host name of a node in the cluster. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hue | Randomly generated by the system | User for Hue system startup, Kerberos authentication, and HDFS and Hive access | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | flume | Randomly generated by the system | User for Flume system startup and HDFS and Kafka access. The user has read and write permission of the HDFS directory **/flume**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | flume_server | Randomly generated by the system | User for Flume system startup and HDFS and Kafka access. The user has read and write permission of the HDFS directory **/flume**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x/hadoop.\ ** | Randomly generated by the system | This user is the Spark2x system administrator and has the following user permissions: | | +| | | | | | +| | | | 1. Starts the Spark2x service. | | +| | | | | | +| | | | 2. Submits Spark2x tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark_zk/hadoop.\ ** | Randomly generated by the system | Used for Spark2x to access ZooKeeper. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x1/hadoop.\ ** | Randomly generated by the system | This user is the Spark2x1 system administrator and has the following user permissions: | | +| | | | | | +| | | | #. Starts the Spark2x1 service. | | +| | | | #. Submits Spark2x tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x2/hadoop.\ ** | Randomly generated by the system | This user is the Spark2x2 system administrator and has the following user permissions: | | +| | | | | | +| | | | #. Starts the Spark2x2 service. | | +| | | | #. Submits Spark2x tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x3/hadoop.\ ** | Randomly generated by the system | This user is the Spark2x3 system administrator and has the following user permissions: | | +| | | | | | +| | | | #. Starts the Spark2x3 service. | | +| | | | #. Submits Spark2x tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x4/hadoop.\ ** | Randomly generated by the system | This user is the Spark2x4 system administrator and has the following user permissions: | | +| | | | | | +| | | | #. Starts the Spark2x4 service. | | +| | | | #. Submits Spark2x tasks. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | zookeeper/hadoop.\ ** | Randomly generated by the system | ZooKeeper system startup user. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | zkcli/hadoop.\ ** | Randomly generated by the system | ZooKeeper server login user. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | oozie | Randomly generated by the system | User for Oozie system startup and Kerberos authentication. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | kafka/hadoop.\ ** | Randomly generated by the system | Used for security authentication of Kafka. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | storm/hadoop.\ ** | Randomly generated by the system | Storm system startup user. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | storm_zk/hadoop.\ ** | Randomly generated by the system | Used for the Worker process to access ZooKeeper. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | flink/hadoop.\ ** | Randomly generated by the system | Internal user of the Flink service. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | check_ker_M | Randomly generated by the system | User who performs a system internal test about whether the Kerberos service is normal. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | tez | Randomly generated by the system | User for TezUI system startup, Kerberos authentication, and access to Yarn | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | K/M | Randomly generated by the system | Kerberos internal functional user. This user cannot be deleted, and its password cannot be changed. This internal account can only be used on nodes where Kerberos service is installed. | None | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | kadmin/changepw | Randomly generated by the system | | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | kadmin/history | Randomly generated by the system | | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | krbtgt\ ** | Randomly generated by the system | | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| LDAP user | admin | None | FusionInsight Manager administrator. | The LDAP user cannot log in to the system, and the password cannot be changed. | +| | | | | | +| | | | The primary group is **compcommon**, which does not have the group permission but has the permission of the **Manager_administrator** role. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | backup | | The primary group is **compcommon**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | backup/manager | | The primary group is **compcommon**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | oms | | The primary group is **compcommon**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | oms/manager | | The primary group is **compcommon**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | clientregister | | The primary group is **compcommon**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | zookeeper | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | zookeeper/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | zkcli | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | zkcli/hadoop.<*System domain name*> | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | flume | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | flume_server | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hdfs | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hdfs/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | mapred | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | mapred/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | mr_zk | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | mr_zk/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hue | | The primary group is **supergroup**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive | | The primary group is **hive**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive/hadoop.\ ** | | The primary group is **hive**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive1 | | The primary group is **hive1**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive1/hadoop.\ ** | | The primary group is **hive1**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive2 | | The primary group is **hive2**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive2/hadoop.\ ** | | The primary group is **hive2**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive3 | | The primary group is **hive3**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive3/hadoop.\ ** | | The primary group is **hive3**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive4 | | The primary group is **hive4**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hive4/hadoop.\ ** | | The primary group is **hive4**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hbase | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hbase/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | thrift | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | thrift/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | oozie | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | hbase/zkclient.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | loader | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | loader/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark_zk | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x1 | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x1/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x2 | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x2/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x4 | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | spark2x4/hadoop.\ ** | | The primary group is **hadoop**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | kafka | | The primary group is **kafkaadmin**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | kafka/hadoop.\ ** | | The primary group is **kafkaadmin**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | storm | | The primary group is **stormadmin**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | storm/hadoop.\ ** | | The primary group is **stormadmin**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | storm_zk | | The primary group is **storm**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | storm_zk/hadoop.\ ** | | The primary group is **storm**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | kms/hadoop | | The primary group is **kmsadmin**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | knox | | The primary group is **compcommon**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| | executor | | The primary group is **compcommon**. | | ++----------------------------+-------------------------------------------+----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------+ .. note:: @@ -376,30 +532,42 @@ Database Users The system database users include OMS database users and DBService database users. -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| Database Type | Default User | Initial Password | Description | Password Change Method | -+====================+==============+===================+=====================================================================================================================+==================================================================================================================+ -| OMS database | ommdba | dbChangeMe@123456 | OMS database administrator who performs maintenance operations, such as creating, starting, and stopping. | For details, see :ref:`Changing the Password of the OMS Database Administrator `. | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | omm | ChangeMe@123456 | User for accessing OMS database data | For details, see :ref:`Changing the Password for the Data Access User of the OMS Database `. | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| DBService database | omm | dbserverAdmin@123 | Administrator of the GaussDB database in the DBService component | For details, see :ref:`Changing the Password for a Component Database User `. | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | hive | HiveUser@ | User for Hive to connect to the DBService database **hivemeta**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | hue | HueUser@123 | User for Hue to connect to the DBService database **hue**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | sqoop | SqoopUser@ | User for Loader to connect to the DBService database **sqoop**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | sqoop\ *N* | SqoopUser@ | User for **Loader-**\ *N* to connect to the DBService database **sqoop**\ *N* when multiple services are installed. | | -| | | | | | -| | | | For example, the user for **Loader-1** to connect to the DBService database **sqoop1** is **sqoop1**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | oozie | OozieUser@ | User for Oozie to connect to the DBService database **oozie**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | rangeradmin | Admin12! | User for Ranger to connect to the DBService database **ranger**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | hetu | Random password | User for HetuEngine to connect to the DBService database **hetumeta**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ -| | cdl | Random password | User for CDL to connect to the DBService database **cdl**. | | -+--------------------+--------------+-------------------+---------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| Database Type | Default User | Initial Password | Description | Password Change Method | ++====================+==============+===================+============================================================================================================================+==================================================================================================================+ +| OMS database | ommdba | dbChangeMe@123456 | OMS database administrator who performs maintenance operations, such as creating, starting, and stopping. | For details, see :ref:`Changing the Password of the OMS Database Administrator `. | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | omm | ChangeMe@123456 | User for accessing OMS database data | For details, see :ref:`Changing the Password for the Data Access User of the OMS Database `. | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| DBService database | omm | dbserverAdmin@123 | Administrator of the GaussDB database in the DBService component | For details, see :ref:`Changing the Password for a Component Database User `. | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | hive | HiveUser@ | User for Hive to connect to the DBService database **hivemeta**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | hive1 | HiveUser@ | User for Hive1 to connect to the DBService database **hivemeta1**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | hive2 | HiveUser@ | User for Hive2 to connect to the DBService database **hivemeta2**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | hive3 | HiveUser@ | User for Hive3 to connect to the DBService database **hivemeta3**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | hive4 | HiveUser@ | User for Hive4 to connect to the DBService database **hivemeta4**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | hive\ *NN* | HiveUser@ | User for **Hive-**\ *N* to connect to the DBService database **hive**\ *N*\ **meta** when multiple services are installed. | | +| | | | | | +| | | | For example, the user for **Hive-1** to connect to the DBService database **hive1meta** is **hive11**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | hue | HueUser@123 | User for Hue to connect to the DBService database **hue**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | sqoop | SqoopUser@ | User for Loader to connect to the DBService database **sqoop**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | sqoop\ *N* | SqoopUser@ | User for **Loader-**\ *N* to connect to the DBService database **sqoop**\ *N* when multiple services are installed. | | +| | | | | | +| | | | For example, the user for **Loader-1** to connect to the DBService database **sqoop1** is **sqoop1**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | oozie | OozieUser@ | User for Oozie to connect to the DBService database **oozie**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | oozie\ *N* | OozieUser@ | User for **Oozie-**\ *N* to connect to the DBService database **oozie**\ *N* when multiple services are installed. | | +| | | | | | +| | | | For example, the user for **Oozie-1** to connect to the DBService database **oozie1** is **oozie1**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ +| | rangeradmin | Admin12! | User for Ranger to connect to the DBService database **ranger**. | | ++--------------------+--------------+-------------------+----------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/component_management/viewing_component_packages.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/component_management/viewing_component_packages.rst index 43d53f6..48c73c9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/component_management/viewing_component_packages.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/component_management/viewing_component_packages.rst @@ -22,4 +22,4 @@ Procedure #. Click |image1| on the left of a component name to view the services and version numbers contained in the component. -.. |image1| image:: /_static/images/en-us_image_0000001442653705.png +.. |image1| image:: /_static/images/en-us_image_0263899291.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_monitoring_metric_dumping.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_monitoring_metric_dumping.rst index 1664630..c8a7402 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_monitoring_metric_dumping.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_monitoring_metric_dumping.rst @@ -139,4 +139,4 @@ After the configuration is complete, the monitoring data reporting function peri For metrics whose collection period is 300s, you can find the corresponding metric description by referring to the second column, that is, **5-Minute Metric ID**. -.. |image1| image:: /_static/images/en-us_image_0000001392414386.png +.. |image1| image:: /_static/images/en-us_image_0263899496.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_snmp_northbound_parameters.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_snmp_northbound_parameters.rst index 454906b..6f5b2fe 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_snmp_northbound_parameters.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_snmp_northbound_parameters.rst @@ -79,4 +79,4 @@ Procedure #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001392414386.png +.. |image1| image:: /_static/images/en-us_image_0263899496.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_syslog_northbound_parameters.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_syslog_northbound_parameters.rst index 0486fc0..27f1e85 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_syslog_northbound_parameters.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_interconnections/configuring_syslog_northbound_parameters.rst @@ -184,4 +184,4 @@ Related Information | object | Alarm object | +-----------------------------------+--------------------------------------------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001392414386.png +.. |image1| image:: /_static/images/en-us_image_0263899496.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/creating_a_user.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/creating_a_user.rst index 57c7d72..e9830cd 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/creating_a_user.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/creating_a_user.rst @@ -23,7 +23,7 @@ Procedure #. Set **User Type** to **Human-Machine** or **Machine-Machine**. - - **Human-Machine** user: used for FusionInsight Manager O&M and component client operations. If you select this option, you also need to select the password policy and set **Password** and **Confirm Password**. + - **Human-Machine** user: used for FusionInsight Manager O&M and component client operations. If you select this option, you also need to set **Password** and **Confirm Password**. - **Machine-Machine** user: used for component application development. If you select this option, the password is randomly generated. #. In the **User Group** area, click **Add** to add one or more user groups to the list. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/modifying_user_information.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/modifying_user_information.rst index 668370a..1a1ff62 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/modifying_user_information.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/modifying_user_information.rst @@ -21,4 +21,8 @@ Procedure Modify the parameters based on service requirements. + .. note:: + + It takes three minutes at most for the change of the user group or role permissions to take effect. + #. Click **OK**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/security_policies/configuring_password_policies.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/security_policies/configuring_password_policies.rst index 739c2db..da8acdb 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/security_policies/configuring_password_policies.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/security_policies/configuring_password_policies.rst @@ -15,8 +15,8 @@ To keep up with service security requirements, you can set password security rul - 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) -------------------------------------------------------------- +Procedure +--------- #. Log in to FusionInsight Manager. @@ -51,79 +51,3 @@ Modifying a Password Policy (Versions Earlier than MRS 3.1.2) +------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ #. Click **OK** to save the configurations. Change the user password after modifying the password policy, and then the new password policy can take effect. - -Adding a Password Policy (MRS 3.1.2 and Later Versions) -------------------------------------------------------- - -#. Log in to FusionInsight Manager. - -#. Choose **System** > **Permission** > **Security Policy** > **Password Policy**. - -#. Click **Add Password Policy** and modify the password policy as prompted. - - For details about the parameters, see :ref:`Table 2 `. - - .. _admin_guide_000150__table18661123192217: - - .. table:: **Table 2** Password policy parameters - - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Parameter | Description | - +============================================================+==============================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ - | Password Policy Name | The value is a string of 3 to 32 characters, including case-insensitive letters, digits, underscores (_), and hyphens (-). It cannot start with a hyphen (-). | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Minimum Password Length | Indicates the minimum number of characters a password contains. The value ranges from **8** to **32**. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Character Types | Indicates how many character types in the following types a password can contain at least: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\\=`). The value can be **4** or **5**. The default value is **4**, which means that a password can contain uppercase letters, lowercase letters, digits, and special characters. If you set the parameter to **5**, a password can contain all the five character types mentioned above. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Password Retries | Indicates the number of consecutive wrong password attempts allowed before the system locks the user. The value ranges from **3** to **30**. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | User Lock Duration (Min) | Indicates the time period in which a user is locked when the user lockout conditions are met. The value ranges from **5** to **120**. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Password Validity Period (Day) | Indicates the validity period of a password. The value ranges from **0** to **90**. **0** indicates that the password is permanently valid. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Repetition Rule | Indicates the number of previous passwords that cannot be reused when you change the password. The value ranges from **1** to **5**. The default value is **1**. | - | | | - | | This policy applies to only human-machine accounts. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Password Expiration Notification (Days) | Indicates the number of days in advance users are notified that their passwords are about to expire. After the value is set, if the difference between the cluster time and the password expiration time is smaller than this value, the user receives password expiration notifications. When logging in to FusionInsight Manager, the user will be notified that the password is about to expire and a message is displayed asking the user to change the password. The value ranges from **0** to *X* (*X* must be set to the half of the password validity period and rounded down). Value **0** indicates that no notification is sent. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Interval for Deleting Authentication Failure Records (Min) | Indicates the interval of retaining incorrect password attempts. The value ranges from **0** to **1440**. **0** indicates that incorrect password attempts are permanently retained, and **1440** indicates that incorrect password attempts are retained for one day. | - +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - -#. Click **OK** to save the configurations. - - A new user uses the default password policy. After a new password policy is created, you can manually select the password policy when creating a user. You can modify the password policy of an existing user. For details, see :ref:`Modifying User Information `. - -.. note:: - - A maximum of 32 password policies can be created. - -Modifying a Password Policy (MRS 3.1.2 and Later Versions) ----------------------------------------------------------- - -#. Log in to FusionInsight Manager. - -#. Choose **System** > **Permission** > **Security Policy** > **Password Policy**. - -#. 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 :ref:`Table 2 `. - -#. Click **OK** to save the configurations. - -.. note:: - - - 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 and Later Versions) ---------------------------------------------------------- - -#. Log in to FusionInsight Manager. -#. Choose **System** > **Permission** > **Security Policy** > **Password Policy**. -#. Click **Delete** in the row that contains the target password policy. In the dialog box that is displayed, click **OK**. - -.. note:: - - The default password policy and the password policy that has been bound to a user cannot be deleted. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/importing_a_certificate.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/importing_a_certificate.rst index 1f07379..7e7a299 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/importing_a_certificate.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/importing_a_certificate.rst @@ -59,4 +59,4 @@ Procedure #. In the displayed dialog box, enter the password of the current login user and click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001392574046.png +.. |image1| image:: /_static/images/en-us_image_0263899546.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/oms_management/overview_of_the_oms_page.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/oms_management/overview_of_the_oms_page.rst index a375304..4ecf93f 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/oms_management/overview_of_the_oms_page.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/oms_management/overview_of_the_oms_page.rst @@ -59,4 +59,4 @@ System Parameters Connect to the DMPS cluster in large-scale cluster scenarios. -.. |image1| image:: /_static/images/en-us_image_0000001392734006.png +.. |image1| image:: /_static/images/en-us_image_0263899675.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/multi-tenancy_usage/process_overview.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/multi-tenancy_usage/process_overview.rst index e24df7a..e4eb339 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/multi-tenancy_usage/process_overview.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/multi-tenancy_usage/process_overview.rst @@ -10,7 +10,7 @@ Administrators need to determine the service scenarios of cluster resources and :ref:`Process Overview ` shows the process for creating a tenant. -.. figure:: /_static/images/en-us_image_0000001442653645.png +.. figure:: /_static/images/en-us_image_0263899222.png :alt: **Figure 1** Creating a tenant **Figure 1** Creating a tenant diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_management.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_management.rst index 7dcb99e..105a0b0 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_management.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_management.rst @@ -16,7 +16,7 @@ FusionInsight Manager provides the graphical multi-tenant management interface a .. _admin_guide_000091__fig2773161717323: -.. figure:: /_static/images/en-us_image_0000001442653677.png +.. figure:: /_static/images/en-us_image_0000001369960209.png :alt: **Figure 1** Tenant management page of FusionInsight Manager **Figure 1** Tenant management page of FusionInsight Manager @@ -67,7 +67,7 @@ Clear Resource Management .. _admin_guide_000091__fig136061232032: - .. figure:: /_static/images/en-us_image_0000001392414410.png + .. figure:: /_static/images/en-us_image_0263899641.png :alt: **Figure 2** Refined monitoring **Figure 2** Refined monitoring @@ -103,6 +103,6 @@ Clear Resource Management | | - Used AM Memory | | +-----------------------+-----------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0000001442413881.png -.. |image2| image:: /_static/images/en-us_image_0000001392733966.png -.. |image3| image:: /_static/images/en-us_image_0000001392254886.png +.. |image1| image:: /_static/images/en-us_image_0000001169371695.png +.. |image2| image:: /_static/images/en-us_image_0000001370085637.png +.. |image3| image:: /_static/images/en-us_image_0263899288.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_model.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_model.rst index c3312e0..6886334 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_model.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/multi-tenancy/technical_principles/multi-tenant_model.rst @@ -12,7 +12,7 @@ The following figure shows a multi-tenant model. .. _admin_guide_000092__f486ae0dbdc8a4d6285e9d6e8ac5cbde0: -.. figure:: /_static/images/en-us_image_0000001392733950.png +.. figure:: /_static/images/en-us_image_0263899456.png :alt: **Figure 1** Multi-tenant model **Figure 1** Multi-tenant model @@ -92,7 +92,7 @@ Tenant is a core concept of the FusionInsight big data platform. It plays an imp .. _admin_guide_000092__f0b6aaf15c16f487fa23a1a04eb45754f: -.. figure:: /_static/images/en-us_image_0000001442773629.png +.. figure:: /_static/images/en-us_image_0263899420.png :alt: **Figure 2** Platform transformation from user-centered to multi-tenant **Figure 2** Platform transformation from user-centered to multi-tenant diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_sub-tenant.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_sub-tenant.rst index 9fe647f..f84e49d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_sub-tenant.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_sub-tenant.rst @@ -113,4 +113,4 @@ Procedure Click **OK**. Wait until the system displays a message indicating that the tenant is successfully created. -.. |image1| image:: /_static/images/en-us_image_0000001442653665.png +.. |image1| image:: /_static/images/en-us_image_0263899238.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_tenant.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_tenant.rst index ef0b61e..8c5fde2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_tenant.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/creating_tenants/adding_a_tenant.rst @@ -122,4 +122,4 @@ Procedure Click **OK**. Wait until the system displays a message indicating that the tenant is successfully created. -.. |image1| image:: /_static/images/en-us_image_0000001442494033.png +.. |image1| image:: /_static/images/en-us_image_0263899570.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/adding_a_resource_pool.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/adding_a_resource_pool.rst index a2428da..b68344c 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/adding_a_resource_pool.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/adding_a_resource_pool.rst @@ -36,4 +36,4 @@ Procedure 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. -.. |image1| image:: /_static/images/en-us_image_0000001392733930.png +.. |image1| image:: /_static/images/en-us_image_0263899376.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/configuring_a_queue.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/configuring_a_queue.rst index 1e9dc11..a3df97d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/configuring_a_queue.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/configuring_a_queue.rst @@ -59,4 +59,4 @@ Procedure #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001442653673.png +.. |image1| image:: /_static/images/en-us_image_0000001369765657.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/modifying_a_resource_pool.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/modifying_a_resource_pool.rst index b39b4a0..ad77747 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/modifying_a_resource_pool.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_resources/modifying_a_resource_pool.rst @@ -23,5 +23,5 @@ Procedure #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001392414402.png -.. |image2| image:: /_static/images/en-us_image_0000001442413873.png +.. |image1| image:: /_static/images/en-us_image_0263899635.png +.. |image2| image:: /_static/images/en-us_image_0263899280.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/deleting_a_tenant.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/deleting_a_tenant.rst index 096cdf0..91e0d00 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/deleting_a_tenant.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/deleting_a_tenant.rst @@ -37,4 +37,4 @@ Procedure After the tenant is deleted, the queue of the tenant still exists in Yarn. The queue of the tenant is not displayed on the role management page in Yarn. -.. |image1| image:: /_static/images/en-us_image_0000001442413945.png +.. |image1| image:: /_static/images/en-us_image_0000001376041769.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/restoring_tenant_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/restoring_tenant_data.rst index ea588a5..35023f5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/restoring_tenant_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_capacity_scheduler/managing_tenants/restoring_tenant_data.rst @@ -30,4 +30,4 @@ Procedure #. In the **Restore Tenant Resource Data** window, select one or more components to restore data, and click **OK**. The system automatically restores the tenant data. -.. |image1| image:: /_static/images/en-us_image_0000001442494073.png +.. |image1| image:: /_static/images/en-us_image_0263899446.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_sub-tenant.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_sub-tenant.rst index 7e5b444..a2ce2fc 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_sub-tenant.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_sub-tenant.rst @@ -126,4 +126,4 @@ Procedure Click **OK**. Wait until the system displays a message indicating that the tenant is successfully created. -.. |image1| image:: /_static/images/en-us_image_0000001392254894.png +.. |image1| image:: /_static/images/en-us_image_0263899322.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_tenant.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_tenant.rst index d1ff096..ae5cbc7 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_tenant.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/creating_tenants/adding_a_tenant.rst @@ -121,4 +121,4 @@ Procedure Click **OK**. Wait until the system displays a message indicating that the tenant is successfully created. -.. |image1| image:: /_static/images/en-us_image_0000001392733934.png +.. |image1| image:: /_static/images/en-us_image_0263899257.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/adding_a_resource_pool.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/adding_a_resource_pool.rst index 322ecd0..075e5aa 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/adding_a_resource_pool.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/adding_a_resource_pool.rst @@ -36,4 +36,4 @@ Procedure 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. -.. |image1| image:: /_static/images/en-us_image_0000001442494081.png +.. |image1| image:: /_static/images/en-us_image_0263899621.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/configuring_a_queue.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/configuring_a_queue.rst index 144a2a8..d982784 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/configuring_a_queue.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/configuring_a_queue.rst @@ -64,4 +64,4 @@ Procedure #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001442494093.png +.. |image1| image:: /_static/images/en-us_image_0263899409.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/modifying_a_resource_pool.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/modifying_a_resource_pool.rst index d51542a..c464d9e 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/modifying_a_resource_pool.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_resources/modifying_a_resource_pool.rst @@ -23,5 +23,5 @@ Procedure #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001442653649.png -.. |image2| image:: /_static/images/en-us_image_0000001442773617.png +.. |image1| image:: /_static/images/en-us_image_0263899458.png +.. |image2| image:: /_static/images/en-us_image_0263899454.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/deleting_a_tenant.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/deleting_a_tenant.rst index ed48bf1..bbcd211 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/deleting_a_tenant.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/deleting_a_tenant.rst @@ -36,4 +36,4 @@ Procedure After the tenant is deleted, the queue of the tenant still exists in Yarn. The queue of the tenant is not displayed on the role management page in Yarn. -.. |image1| image:: /_static/images/en-us_image_0000001392414394.png +.. |image1| image:: /_static/images/en-us_image_0000001375852797.png diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/restoring_tenant_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/restoring_tenant_data.rst index c80d8bd..df493c5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/restoring_tenant_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/tenant_resources/using_the_superior_scheduler/managing_tenants/restoring_tenant_data.rst @@ -30,4 +30,4 @@ Procedure #. In the **Restore Tenant Resource Data** window, select one or more components to restore data, and click **OK**. The system automatically restores the tenant data. -.. |image1| image:: /_static/images/en-us_image_0000001442494073.png +.. |image1| image:: /_static/images/en-us_image_0263899446.png diff --git a/umn/source/high-risk_operations.rst b/umn/source/high-risk_operations.rst index 12301ac..0c32720 100644 --- a/umn/source/high-risk_operations.rst +++ b/umn/source/high-risk_operations.rst @@ -8,9 +8,9 @@ High-Risk Operations Forbidden Operations -------------------- -:ref:`Table 1 ` lists forbidden operations during the routine cluster operation and maintenance process. +:ref:`Table 1 ` lists forbidden operations during the routine cluster operation and maintenance process. -.. _mrs_01_0785__en-us_topic_0263899450_en-us_topic_0046737034_table44115416: +.. _mrs_01_0785__admin_guide_000295_en-us_topic_0046737034_table44115416: .. table:: **Table 1** Forbidden operations @@ -98,23 +98,10 @@ Manager High-Risk Operations | Change the default SSH port No. | After the default port (22) is changed, functions such as cluster creation, service/instance adding, host adding, and host reinstallation cannot be used, and results of cluster health check items for node mutual trust, **omm**/**ommdba** user password expiration, and others are incorrect. | ▲▲▲ | Before performing this operation, restore the SSH port to the default value. | None | +-----------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ -CDL High-risk Operations ------------------------- - -.. table:: **Table 4** CDL high-risk operations - - +-----------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - | Operation | Risk | Severity | Workaround | Check Item | - +===============================================+=================================================================================================================+==========+==========================================================================================================================================================================+================================================+ - | Start or stop basic components independently. | This operation has adverse impact on the basic functions of some services. As a result, service failures occur. | ▲▲▲ | Do not start or stop basic components such as Kafka, DBService, ZooKeeper, Kerberos, and LDAP separately. To start or stop basic components, select associated services. | Check whether the service status is normal. | - +-----------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - | Restart or stop services. | This operation may interrupt services. | ▲▲ | Restart or stop services when necessary. | Check whether the service is running properly. | - +-----------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - ClickHouse High-Risk Operations ------------------------------- -.. table:: **Table 5** ClickHouse high-risk operations +.. table:: **Table 4** ClickHouse high-risk operations +-----------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -139,7 +126,7 @@ ClickHouse High-Risk Operations DBService High-Risk Operations ------------------------------ -.. table:: **Table 6** DBService high-risk operations +.. table:: **Table 5** DBService high-risk operations +----------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -160,7 +147,7 @@ DBService High-Risk Operations Flink High-Risk Operations -------------------------- -.. table:: **Table 7** Flink high-risk operations +.. table:: **Table 6** Flink high-risk operations +--------------------------+----------------------------------------------------------------------------------+----------+----------------------------------------------------------------------------------------------------------------------+------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -173,7 +160,7 @@ Flink High-Risk Operations Flume High-Risk Operations -------------------------- -.. table:: **Table 8** Flume high-risk operations +.. table:: **Table 7** Flume high-risk operations +----------------------------------------------------------------------+-----------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -189,7 +176,7 @@ Flume High-Risk Operations HBase High-Risk Operations -------------------------- -.. table:: **Table 9** HBase high-risk operations +.. table:: **Table 8** HBase high-risk operations +-------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------+-------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -212,7 +199,7 @@ HBase High-Risk Operations HDFS High-Risk Operations ------------------------- -.. table:: **Table 10** HDFS high-risk operations +.. table:: **Table 9** HDFS high-risk operations +-----------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -231,29 +218,10 @@ HDFS High-Risk Operations | Change the remote procedure call (RPC) channel encryption mode (**hadoop.rpc.protection**) of each module in Hadoop. | This operation causes service faults and service exceptions. | ▲▲▲▲▲ | Strictly follow the prompt information when modifying related configuration items. Ensure that new values are valid. | Check whether HDFS and other services that depend on HDFS can properly start and provide services. | +-----------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------+ -HetuEngine High-Risk Operations -------------------------------- - -.. table:: **Table 11** HetuEngine high-risk operations - - +-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ - | Operation | Risk | Severity | Workaround | Check Item | - +=============================================================================================================================================================================================================+====================================================================================================================================+==========+==============================================================================================================================================================================+================================================================================================+ - | Delete all HSBroker instances. | All HetuEngine compute instances are deleted, information about interconnected data sources is lost, and services are unavailable. | ▲▲▲▲ | Before deleting HSBroker instances, ensure that at least one HSBroker instance exists. | Check whether the service is running properly and whether interrupted operations are restored. | - +-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ - | Modify the configuration items in the configuration files of the HetuEngine compute instance. The configuration files include the **coordinator.config.properties** and **worker.config.properties** files. | The HetuEngine compute instance fails to be started. | ▲▲▲ | Strictly follow the prompt information when modifying related configuration items. Ensure that new values are valid. | Check whether the service is running properly. | - +-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ - | Modify the configuration items in the JVM files of the HetuEngine compute instance. The JVM files include the **coordinator.jvm.config** and **worker.jvm.config** files. | The HetuEngine compute instance fails to be started. | ▲▲▲ | Strictly follow the prompt information when modifying related configuration items. Ensure that new values are valid. | Check whether the service is running properly. | - +-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ - | Delete the tenant who has started a HetuEngine compute instance. | The HetuEngine compute instance cannot be used. | ▲▲▲ | Before deleting a tenant, ensure that the HetuEngine compute instance corresponding to the tenant is no longer used and delete the HetuEngine compute instance on HSConsole. | Check whether the service is running properly. | - +-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ - | Restart Yarn when the HetuEngine compute instance is started and the auto scaling function is enabled. | The auto scaling function of the HetuEngine compute instance is unavailable. | ▲▲▲ | Before restarting Yarn, disable the auto scaling function of HetuEngine compute instance on HSConsole. | Check whether the service is running properly. | - +-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ - Hive High-Risk Operations ------------------------- -.. table:: **Table 12** Hive high-risk operations +.. table:: **Table 10** Hive high-risk operations +----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------+-------------+--------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -275,27 +243,10 @@ Hive High-Risk Operations | Direct different databases, tables, or partition files to the same path, for example, default warehouse path **/user/hive/warehouse**. | The creation operation may cause disordered data. After a database, table, or partition is deleted, other object data will be lost. | ▲▲▲▲▲ | Do not perform this operation. | Check whether files in the target path are lost. | +----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------+-------------+--------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------+ -IoTDB High-Risk Operations --------------------------- - -.. table:: **Table 13** IoTDB high-risk operations - - +-----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - | Operation | Risk | Severity | Workaround | Check Item | - +===========================================================+=================================================================================================================+==========+=================================================================================================================================+================================================+ - | Delete data directories. | This operation may cause service information loss. | ▲▲▲ | Do not delete data directories manually. | Check whether data directories are normal. | - +-----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - | Modify data directory content (file and folder creation). | This operation may cause the IoTDB instance of the node faults. | ▲▲▲ | Do not create or modify files or folders in the data directories manually. | Check whether data directories are normal. | - +-----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - | Start or stop basic components independently. | This operation has adverse impact on the basic functions of some services. As a result, service failures occur. | ▲▲▲ | Do not start or stop Kerberos, and LDAP basic components independently. Select related services when performing this operation. | Check whether the service status is normal. | - +-----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - | Restart or stop services. | This operation may interrupt services. | ▲▲ | Restart or stop services when necessary. | Check whether the service is running properly. | - +-----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------+ - Kafka High-Risk Operations -------------------------- -.. table:: **Table 14** Kafka high-risk operations +.. table:: **Table 11** Kafka high-risk operations +---------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -326,7 +277,7 @@ Kafka High-Risk Operations KrbServer High-Risk Operations ------------------------------ -.. table:: **Table 15** KrbServer high-risk operations +.. table:: **Table 12** KrbServer high-risk operations +-----------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -345,7 +296,7 @@ KrbServer High-Risk Operations LdapServer High-Risk Operations ------------------------------- -.. table:: **Table 16** LdapServer high-risk operations +.. table:: **Table 13** LdapServer high-risk operations +----------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -364,7 +315,7 @@ LdapServer High-Risk Operations Loader High-Risk Operations --------------------------- -.. table:: **Table 17** Loader high-risk operations +.. table:: **Table 14** Loader high-risk operations +----------------------------------------------------------------------------+--------------------------------------------------------------+----------+----------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -383,7 +334,7 @@ Spark2x High-risk Operations Spark high-risk operations apply to MRS 3.x earlier versions. -.. table:: **Table 18** Spark2x high-risk operations +.. table:: **Table 15** Spark2x high-risk operations +----------------------------------------------------------------------------------------+----------------------------------------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -406,7 +357,7 @@ Spark2x High-risk Operations Storm High-Risk Operations -------------------------- -.. table:: **Table 19** Storm high-risk operations +.. table:: **Table 16** Storm high-risk operations +------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -450,7 +401,7 @@ Storm High-Risk Operations Yarn High-Risk Operations ------------------------- -.. table:: **Table 20** Yarn high-risk operations +.. table:: **Table 17** Yarn high-risk operations +-------------------------------------------------------------------+----------------------------------------------------+-------------+------------------------------------------+--------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | @@ -463,7 +414,7 @@ Yarn High-Risk Operations ZooKeeper High-Risk Operations ------------------------------ -.. table:: **Table 21** ZooKeeper high-risk operations +.. table:: **Table 18** ZooKeeper high-risk operations +------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------+ | Operation | Risk | Severity | Workaround | Check Item | diff --git a/umn/source/index.rst b/umn/source/index.rst index f8ba644..a269132 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -22,5 +22,5 @@ MapReduce Service - User Guide data_backup_and_restoration/index appendix/index faq/index - glossary change_history + glossary diff --git a/umn/source/managing_clusters/cluster_o_and_m/checking_health_status/performing_a_health_check.rst b/umn/source/managing_clusters/cluster_o_and_m/checking_health_status/performing_a_health_check.rst index cdf6926..ddf3470 100644 --- a/umn/source/managing_clusters/cluster_o_and_m/checking_health_status/performing_a_health_check.rst +++ b/umn/source/managing_clusters/cluster_o_and_m/checking_health_status/performing_a_health_check.rst @@ -52,7 +52,7 @@ Procedure .. note:: - For MRS 1.7.2 or earlier, see :ref:`Performing a Health Check `. For MRS 3.\ *x* or later, see :ref:`Perform a Health Check `. + For MRS 1.7.2 or earlier, see :ref:`Performing a Health Check `. For MRS 3.\ *x* or later, see :ref:`Performing a Host Health Check `. #. Expand the node group information and select the check box of the host to be checked. #. Choose **Node** > **Start Host Health Check** to start the health check for the host. diff --git a/umn/source/managing_clusters/patch_management/index.rst b/umn/source/managing_clusters/patch_management/index.rst index 5dc6f8a..11e0545 100644 --- a/umn/source/managing_clusters/patch_management/index.rst +++ b/umn/source/managing_clusters/patch_management/index.rst @@ -9,7 +9,6 @@ Patch Management - :ref:`Patch Operation Guide for Versions from MRS 1.7.0 to MRS 2.1.0 ` - :ref:`Rolling Patches ` - :ref:`Restoring Patches for the Isolated Hosts ` -- :ref:`Patch Update ` .. toctree:: :maxdepth: 1 @@ -19,4 +18,3 @@ Patch Management patch_operation_guide_for_versions_from_mrs_1.7.0_to_mrs_2.1.0 rolling_patches restoring_patches_for_the_isolated_hosts - patch_update diff --git a/umn/source/managing_clusters/patch_management/patch_update.rst b/umn/source/managing_clusters/patch_management/patch_update.rst deleted file mode 100644 index 3adf945..0000000 --- a/umn/source/managing_clusters/patch_management/patch_update.rst +++ /dev/null @@ -1,18 +0,0 @@ -:original_name: mrs_01_248926.html - -.. _mrs_01_248926: - -Patch Update -============ - -When a new patch is available in the cluster, the system pushes the patch online. You can install the patch in a few clicks. - -.. note:: - - This section applies only to MRS 2.x and earlier versions, and MRS 3.2.0-LTS.1 and later versions. - -#. Log in to the MRS management console. -#. Choose **Clusters** > **Active Clusters** and click the name of your desired cluster. -#. On the cluster details page, click **Patches**. -#. Click **Learn more** in the **Patch Description** column of the target patch, read the description, and confirm the installation procedure and impact. -#. In the **Operation** column, click **Install** to install the target patch. diff --git a/umn/source/overview/components/cdl/cdl_basic_principles.rst b/umn/source/overview/components/cdl/cdl_basic_principles.rst deleted file mode 100644 index ba6c0c1..0000000 --- a/umn/source/overview/components/cdl/cdl_basic_principles.rst +++ /dev/null @@ -1,30 +0,0 @@ -:original_name: mrs_08_0098.html - -.. _mrs_08_0098: - -CDL Basic Principles -==================== - -Overview --------- - -Change Data Loader (CDL) is a real-time data integration service based on Kafka Connect. The CDL service captures data change events from various OLTP databases and push them to Kafka. Then, Sink Connector pushes the events to the big data ecosystem. - -Currently, CDL supports MySQL, PostgreSQL, Oracle, Hudi, Kafka, and ThirdParty-Kafka data sources. Data can be written to Kafka, Hudi, DWS, and ClickHouse. - -CDL structure -------------- - -The CDL service contains two important roles: CDLConnector and CDLService. CDLConnector, including Source Connector and Sink Connector, is the instance for executing data capture jobs. CDLService is the instance for managing and creating jobs. - -|image1| - -The CDLService instances of the CDL service work in multi-active mode. Any CDLService instance can perform service operations. The CDLConnector instances work in distributed mode and provide HA and rebalance capabilities. When tasks are created, the number of tasks specified is balanced among CDLConnector instances in a cluster to ensure that the number of tasks running on each instance is similar. If a CDLConnector instance is abnormal or a node breaks down, the number of tasks are rebalanced on other nodes. - - -.. figure:: /_static/images/en-us_image_0000001349190333.png - :alt: **Figure 1** Rebalance of a task - - **Figure 1** Rebalance of a task - -.. |image1| image:: /_static/images/en-us_image_0000001349309917.png diff --git a/umn/source/overview/components/cdl/index.rst b/umn/source/overview/components/cdl/index.rst deleted file mode 100644 index 936cdef..0000000 --- a/umn/source/overview/components/cdl/index.rst +++ /dev/null @@ -1,16 +0,0 @@ -:original_name: mrs_08_0097.html - -.. _mrs_08_0097: - -CDL -=== - -- :ref:`CDL Basic Principles ` -- :ref:`Relationship Between CDL and Other Components ` - -.. toctree:: - :maxdepth: 1 - :hidden: - - cdl_basic_principles - relationship_between_cdl_and_other_components diff --git a/umn/source/overview/components/cdl/relationship_between_cdl_and_other_components.rst b/umn/source/overview/components/cdl/relationship_between_cdl_and_other_components.rst deleted file mode 100644 index 3ef361a..0000000 --- a/umn/source/overview/components/cdl/relationship_between_cdl_and_other_components.rst +++ /dev/null @@ -1,8 +0,0 @@ -:original_name: mrs_08_0099.html - -.. _mrs_08_0099: - -Relationship Between CDL and Other Components -============================================= - -The CDL component is based on the Kafka Connect framework. Captured data is forwarded using Kafka topics. Therefore, the CDL component depends on the Kafka component. In addition, the CDL component stores task metadata and monitoring information that are also stored in a database. Therefore, the CDL component also depends on the DBService component. diff --git a/umn/source/overview/components/hive/hive_basic_principles.rst b/umn/source/overview/components/hive/hive_basic_principles.rst index edf71ef..4ae17dd 100644 --- a/umn/source/overview/components/hive/hive_basic_principles.rst +++ b/umn/source/overview/components/hive/hive_basic_principles.rst @@ -53,7 +53,7 @@ Hive is a single-instance service process that provides services by translating | MapReduce/YARN cluster | Provides distributed computing services. Most Hive data operations rely on MapReduce. The main function of HiveServer is to translate HQL statements into MapReduce jobs to process massive data. | +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -HCatalog is built on Hive Metastore and incorporates the DDL capability of Hive. HCatalog is also a Hadoop-based table and storage management layer that enables convenient data read/write on tables of HDFS by using different data processing tools such MapReduce. Besides, HCatalog also provides read/write APIs for these tools and uses a Hive CLI to publish commands for defining data and querying metadata. After encapsulating these commands, WebHCat Server can provide RESTful APIs, as shown in :ref:`Figure 2 `. +HCatalog is built on Hive Metastore and incorporates the DDL capability of Hive. HCatalog is also a Hadoop-based table and storage management layer that enables convenient data read/write on tables of HDFS by using different data processing tools such as Pig and MapReduce. Besides, HCatalog also provides read/write APIs for these tools and uses a Hive CLI to publish commands for defining data and querying metadata. After encapsulating these commands, WebHCat Server can provide RESTful APIs, as shown in :ref:`Figure 2 `. .. _mrs_08_001101__hive_f2: diff --git a/umn/source/overview/components/index.rst b/umn/source/overview/components/index.rst index ad52898..0a22125 100644 --- a/umn/source/overview/components/index.rst +++ b/umn/source/overview/components/index.rst @@ -5,11 +5,9 @@ Components ========== -- :ref:`List of MRS Component Versions ` - :ref:`Alluxio ` - :ref:`CarbonData ` - :ref:`ClickHouse ` -- :ref:`CDL ` - :ref:`DBService ` - :ref:`Flink ` - :ref:`Flume ` @@ -19,7 +17,6 @@ Components - :ref:`Hive ` - :ref:`Hudi ` - :ref:`Hue ` -- :ref:`IoTDB ` - :ref:`Kafka ` - :ref:`KafkaManager ` - :ref:`KrbServer and LdapServer ` @@ -41,11 +38,9 @@ Components :maxdepth: 1 :hidden: - list_of_mrs_component_versions alluxio carbondata clickhouse - cdl/index dbservice/index flink/index flume/index @@ -55,7 +50,6 @@ Components hive/index hudi hue/index - iotdb/index kafka/index kafkamanager krbserver_and_ldapserver/index diff --git a/umn/source/overview/components/iotdb/index.rst b/umn/source/overview/components/iotdb/index.rst deleted file mode 100644 index a3a8ed3..0000000 --- a/umn/source/overview/components/iotdb/index.rst +++ /dev/null @@ -1,18 +0,0 @@ -:original_name: mrs_08_0093.html - -.. _mrs_08_0093: - -IoTDB -===== - -- :ref:`IoTDB Basic Principles ` -- :ref:`Relationship Between IoTDB and Other Components ` -- :ref:`IoTDB Enhanced Open Source Features ` - -.. toctree:: - :maxdepth: 1 - :hidden: - - iotdb_basic_principles - relationship_between_iotdb_and_other_components - iotdb_enhanced_open_source_features diff --git a/umn/source/overview/components/iotdb/iotdb_basic_principles.rst b/umn/source/overview/components/iotdb/iotdb_basic_principles.rst deleted file mode 100644 index 6be3f71..0000000 --- a/umn/source/overview/components/iotdb/iotdb_basic_principles.rst +++ /dev/null @@ -1,53 +0,0 @@ -:original_name: mrs_08_0094.html - -.. _mrs_08_0094: - -IoTDB Basic Principles -====================== - -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 architecture and features high performance and rich functions. - -IoTDB sorts time series and stores indexes and chunks, greatly improving the query performance of time series data. IoTDB uses the Raft protocol to ensure data consistency. In time series scenarios, IoTDB pre-computes and stores data to improve analysis performance. Based on the characteristics of time series data, IoTDB provides powerful data encoding and compression capabilities. In addition, its replica mechanism ensures data security. IoTDB is deeply integrated with Apache Hadoop and Flink to meet the requirements of massive data storage, high-speed data reading, and complex data analysis in the industrial IoT field. - -IoTDB Architecture ------------------- - -The IoTDB suite consists of multiple components to provide a series of functions such as data collection, data writing, data storage, data query, data visualization, and data analysis. - -:ref:`Figure 1 ` shows the overall application architecture after all components of the IoTDB suite are used. IoTDB refers to the time series database component in the suite. - -.. _mrs_08_0094__fig121405277474: - -.. figure:: /_static/images/en-us_image_0000001535888150.png - :alt: **Figure 1** IoTDB architecture - - **Figure 1** IoTDB architecture - -- Users can use Java Database Connectivity (JDBC) or Session to import the time series data and system status data (such as server load, CPU usage and memory usage) collected from device sensors, as well as time series data in message queues, applications, or other databases, to the local or remote IoTDB. Users can also directly write the preceding data into a local TsFile file or a TsFile file in the HDFS. -- Users can write TsFile files to the HDFS to implement data processing tasks such as exception detection and machine learning on the Hadoop or Flink data processing platform. -- The TsFile-Hadoop or TsFile-Flink connector can be used to allow Hadoop or Flink to process the TsFile files written to the HDFS or local host. -- The analysis result can be written back to a TsFile in the same way. -- IoTDB and TsFile also provide client tools to meet users' requirements for viewing and writing data in SQL, script, and graphical formats. - -The IoTDB service includes two roles: IoTDBServer (DataNode) and ConfigNode. The role name DataNode of the community edition has the same name as the HDFS role. DataNode is renamed IoTDBServer. - -- ConfigNode: management role, which is responsible for DataNode data sharding and load balancing. -- IoTDBServer (DataNode): storage role, which is responsible for storing, querying, and writing data. - - -.. figure:: /_static/images/en-us_image_0000001586567997.png - :alt: **Figure 2** IoTDB distributed architecture - - **Figure 2** IoTDB distributed architecture - -IoTDB Principles ----------------- - -Based on the attribute hierarchy, attribute coverage, and subordinate relationships between data, the IoTDB data model can be represented as the attribute hierarchy, as shown in :ref:`Figure 3 `. The hierarchy is as follows: power group layer - power plant layer - device layer - sensor layer. **ROOT** is a root node, and each node at the sensor layer is a leaf node. According to the IoTDB syntax, the path from **ROOT** to a leaf node is separated by a dot (.). The complete path is used to name a time series in the IoTDB. For example, the time series name corresponding to the path on the left in the following figure is **ROOT.ln.wf01.wt01.status**. - -.. _mrs_08_0094__fig1285721116: - -.. figure:: /_static/images/en-us_image_0000001586807745.jpg - :alt: **Figure 3** IoTDB data model - - **Figure 3** IoTDB data model diff --git a/umn/source/overview/components/iotdb/iotdb_enhanced_open_source_features.rst b/umn/source/overview/components/iotdb/iotdb_enhanced_open_source_features.rst deleted file mode 100644 index 8425ce9..0000000 --- a/umn/source/overview/components/iotdb/iotdb_enhanced_open_source_features.rst +++ /dev/null @@ -1,23 +0,0 @@ -:original_name: mrs_08_0096.html - -.. _mrs_08_0096: - -IoTDB Enhanced Open Source Features -=================================== - -Visualization -------------- - -- Visualized O&M covers installation, uninstallation, one-click start and stop, configurations, clients, monitoring, alarms, health checks, and logs. -- Visualized permission management does not require background command line operations and supports read and write permission control at the database and table levels. -- Visualized log level configuration dynamically takes effect, supports visualized download and retrieval, and supports log audit. - -Security Hardening ------------------- - -User authentication supports Kerberos authentication and SSL encryption, which are compatible with the community authentication mode. - -Ecosystem Interconnection -------------------------- - -On the basis of native capabilities, the cluster interconnection with MQTT and CoAP is enhanced. diff --git a/umn/source/overview/components/iotdb/relationship_between_iotdb_and_other_components.rst b/umn/source/overview/components/iotdb/relationship_between_iotdb_and_other_components.rst deleted file mode 100644 index 645e5b0..0000000 --- a/umn/source/overview/components/iotdb/relationship_between_iotdb_and_other_components.rst +++ /dev/null @@ -1,8 +0,0 @@ -:original_name: mrs_08_0095.html - -.. _mrs_08_0095: - -Relationship Between IoTDB and Other Components -=============================================== - -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 component for Kerberos authentication. diff --git a/umn/source/overview/components/list_of_mrs_component_versions.rst b/umn/source/overview/components/list_of_mrs_component_versions.rst deleted file mode 100644 index 23168a9..0000000 --- a/umn/source/overview/components/list_of_mrs_component_versions.rst +++ /dev/null @@ -1,91 +0,0 @@ -:original_name: mrs_08_0005.html - -.. _mrs_08_0005: - -List of MRS Component Versions -============================== - -Components and Versions ------------------------ - -:ref:`Table 1 ` lists the components and their versions required by each MRS cluster version. - -.. note:: - - - 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. - -.. _mrs_08_0005__table640094615118: - -.. table:: **Table 1** MRS component versions - - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | Component | MRS 1.9.2 | MRS 2.1.0 | MRS 3.1.0-LTS.1 | MRS 3.1.2-LTS.3 | MRS 3.2.0-LTS.1 | - +============================================+===========+===========+=================+=================+=================+ - | :ref:`Alluxio ` | 2.0.1 | ``-`` | ``-`` | ``-`` | ``-`` | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`CarbonData ` | 1.6.1 | 1.6.1 | 2.0.1 | 2.2.0 | 2.2.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`CDL ` | ``-`` | ``-`` | ``-`` | ``-`` | 1.0.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`ClickHouse ` | ``-`` | ``-`` | 21.3.4.25 | 21.3.4.25 | 22.3.2.2 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`DBService ` | 1.0.0 | 1.0.0 | 2.7.0 | 2.7.0 | 2.7.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Flink ` | 1.7.0 | ``-`` | 1.12.0 | 1.12.2 | 1.15.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Flume ` | 1.6.0 | 1.7.0 | 1.9.0 | 1.9.0 | 1.9.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`HBase ` | 1.3.1 | 2.1.1 | 2.2.3 | 2.2.3 | 2.2.3 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`HDFS ` | 2.8.3 | 3.1.1 | 3.1.1 | 3.1.1 | 3.3.1 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`HetuEngine ` | ``-`` | ``-`` | 1.2.0 | 1.2.0 | 1.2.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Hive ` | 2.3.3 | 3.1.0 | 3.1.0 | 3.1.0 | 3.1.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Hudi ` | ``-`` | ``-`` | ``-`` | 0.9.0 | 0.11.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Hue ` | 3.11.0 | 3.11.0 | 4.7.0 | 4.7.0 | 4.7.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`IoTDB ` | ``-`` | ``-`` | ``-`` | ``-`` | 0.14.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Kafka ` | 1.1.0 | 1.1.0 | 2.11-2.4.0 | 2.11-2.4.0 | 2.11-2.4.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`KafkaManager ` | 1.3.3.1 | ``-`` | ``-`` | ``-`` | ``-`` | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`KrbServer ` | 1.15.2 | 1.15.2 | 1.17 | 1.18 | 1.18 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`LdapServer ` | 1.0.0 | 1.0.0 | 2.7.0 | 2.7.0 | 2.7.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Loader ` | 2.0.0 | 2.0.0 | 1.99.3 | 1.99.3 | 1.99.3 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`MapReduce ` | 2.8.3 | 3.1.1 | 3.1.1 | 3.1.1 | 3.3.1 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Oozie ` | ``-`` | ``-`` | 5.1.0 | 5.1.0 | 5.1.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`OpenTSDB ` | 2.3.0 | ``-`` | ``-`` | ``-`` | ``-`` | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Presto ` | 0.216 | 308 | ``-`` | ``-`` | ``-`` | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | Phoenix (integrated in HBase) | ``-`` | ``-`` | 5.0.0 | 5.0.0 | 5.0.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Ranger ` | 1.0.1 | ``-`` | 2.0.0 | 2.0.0 | 2.0.0 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Spark ` | 2.2.2 | 2.3.2 | ``-`` | ``-`` | ``-`` | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Spark2x ` | ``-`` | ``-`` | 2.4.5 | 3.1.1 | 3.1.1 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Storm ` | 1.2.1 | 1.2.1 | ``-`` | ``-`` | ``-`` | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`Tez ` | 0.9.1 | 0.9.1 | 0.9.2 | 0.9.2 | 0.9.2 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`YARN ` | 2.8.3 | 3.1.1 | 3.1.1 | 3.1.1 | 3.3.1 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`ZooKeeper ` | 3.5.1 | 3.5.1 | 3.5.6 | 3.6.3 | 3.6.3 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`MRS Manager ` | 1.9.2 | 2.1.0 | ``-`` | ``-`` | ``-`` | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ - | :ref:`FusionInsight Manager ` | ``-`` | ``-`` | 8.1.0 | 8.1.2 | 8.2.0.1 | - +--------------------------------------------+-----------+-----------+-----------------+-----------------+-----------------+ diff --git a/umn/source/overview/components/tez.rst b/umn/source/overview/components/tez.rst index cd6be4c..a8de303 100644 --- a/umn/source/overview/components/tez.rst +++ b/umn/source/overview/components/tez.rst @@ -5,7 +5,7 @@ Tez === -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 improving the performance of DAG jobs. If projects like Hive use Tez instead of MapReduce as the backbone of data processing, response time will be significantly reduced. Tez is built on YARN and can run MapReduce jobs without any modification. +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 improving the performance of DAG jobs. If projects like Hive and `Pig `__ use Tez instead of MapReduce as the backbone of data processing, response time will be significantly reduced. Tez is built on YARN and can run MapReduce jobs without any modification. MRS uses Tez as the default execution engine of Hive. Tez remarkably surpasses the original MapReduce computing engine in terms of execution efficiency. diff --git a/umn/source/overview/index.rst b/umn/source/overview/index.rst index c7be1d8..1160965 100644 --- a/umn/source/overview/index.rst +++ b/umn/source/overview/index.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0037341503.html +:original_name: en-us_topic_0000001295768772.html -.. _en-us_topic_0037341503: +.. _en-us_topic_0000001295768772: Overview ======== diff --git a/umn/source/security_description/security_authentication_principles_and_mechanisms.rst b/umn/source/security_description/security_authentication_principles_and_mechanisms.rst index ee2946c..bbd30a4 100644 --- a/umn/source/security_description/security_authentication_principles_and_mechanisms.rst +++ b/umn/source/security_description/security_authentication_principles_and_mechanisms.rst @@ -10,7 +10,7 @@ Function For clusters in security mode with Kerberos authentication enabled, security authentication is required during application development. -Kerberos, is now used to a concept in authentication. The Kerberos protocol adopts a client-server model and cryptographic algorithms such as AES (Advanced Encryption Standard). It provides mutual authentication, that is, both the client and the server can verify each other's identity. Kerberos is used to prevent interception and replay attacks and protect data integrity. It is a system that manages keys by using a symmetric key mechanism. +Kerberos, named after the ferocious three-headed guard dog of Hades from Greek mythology, is now used to a concept in authentication. The Kerberos protocol adopts a client-server model and cryptographic algorithms such as AES (Advanced Encryption Standard). It provides mutual authentication, that is, both the client and the server can verify each other's identity. Kerberos is used to prevent interception and replay attacks and protect data integrity. It is a system that manages keys by using a symmetric key mechanism. Architecture ------------ diff --git a/umn/source/using_an_mrs_client/installing_a_client/installing_a_client_version_3.x_or_later.rst b/umn/source/using_an_mrs_client/installing_a_client/installing_a_client_version_3.x_or_later.rst index 7769249..1f4bda1 100644 --- a/umn/source/using_an_mrs_client/installing_a_client/installing_a_client_version_3.x_or_later.rst +++ b/umn/source/using_an_mrs_client/installing_a_client/installing_a_client_version_3.x_or_later.rst @@ -23,21 +23,21 @@ Prerequisites .. table:: **Table 1** Reference list - +-------------------------+---------+-------------------------------------------------+ - | CPU Architecture | OS | Supported Version | - +=========================+=========+=================================================+ - | x86 computing | Euler | EulerOS 2.5 | - +-------------------------+---------+-------------------------------------------------+ - | | SUSE | SUSE Linux Enterprise Server 12 SP4 (SUSE 12.4) | - +-------------------------+---------+-------------------------------------------------+ - | | Red Hat | Red Hat-7.5-x86_64 (Red Hat 7.5) | - +-------------------------+---------+-------------------------------------------------+ - | | CentOS | CentOS 7.6 | - +-------------------------+---------+-------------------------------------------------+ - | Kunpeng computing (Arm) | Euler | EulerOS 2.8 | - +-------------------------+---------+-------------------------------------------------+ - | | CentOS | CentOS 7.6 | - +-------------------------+---------+-------------------------------------------------+ + +-------------------------+--------+-------------------------------------------------+ + | CPU Architecture | OS | Supported Version | + +=========================+========+=================================================+ + | x86 computing | Euler | EulerOS 2.5 | + +-------------------------+--------+-------------------------------------------------+ + | | SUSE | SUSE Linux Enterprise Server 12 SP4 (SUSE 12.4) | + +-------------------------+--------+-------------------------------------------------+ + | | RedHat | Red Hat-7.5-x86_64 (Red Hat 7.5) | + +-------------------------+--------+-------------------------------------------------+ + | | CentOS | CentOS 7.6 | + +-------------------------+--------+-------------------------------------------------+ + | Kunpeng computing (Arm) | Euler | EulerOS 2.8 | + +-------------------------+--------+-------------------------------------------------+ + | | CentOS | CentOS 7.6 | + +-------------------------+--------+-------------------------------------------------+ In addition, sufficient disk space is allocated for the ECS, for example, 40 GB. diff --git a/umn/source/using_an_mrs_client/updating_a_client/updating_a_client_version_3.x_or_later.rst b/umn/source/using_an_mrs_client/updating_a_client/updating_a_client_version_3.x_or_later.rst index 8901867..126e8b7 100644 --- a/umn/source/using_an_mrs_client/updating_a_client/updating_a_client_version_3.x_or_later.rst +++ b/umn/source/using_an_mrs_client/updating_a_client/updating_a_client_version_3.x_or_later.rst @@ -20,10 +20,10 @@ Updating the Client Configuration #. 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 :ref:`4 `. - - If no, click **OK**, specify a local save path, and download the complete client. Wait until the download is complete and go to :ref:`4 `. + - 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 :ref:`4 `. + - If no, click **OK**, specify a local save path, and download the complete client. Wait until the download is complete and go to :ref:`4 `. -#. .. _mrs_01_24209__en-us_topic_0263899336_en-us_topic_0193213946_l6af983f03121493ca3526296f5b650c3: +#. .. _mrs_01_24209__admin_guide_000173_en-us_topic_0193213946_l6af983f03121493ca3526296f5b650c3: Use WinSCP to save the compressed file to the client installation directory, for example, **/opt/hadoopclient**, as the client installation user.