diff --git a/umn/source/conf.py b/umn/source/conf.py index 25596cb..c788205 100644 --- a/umn/source/conf.py +++ b/umn/source/conf.py @@ -35,6 +35,9 @@ sys.path.insert(0, os.path.abspath('../')) sys.path.insert(0, os.path.abspath('./')) # -- General configuration ---------------------------------------------------- +# https://docutils.sourceforge.io/docs/user/smartquotes.html - it does not +# what it is expected +smartquotes = False # Add any Sphinx extension module names here, as strings. They can be # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom ones. diff --git a/umn/source/configuring_a_cluster/communication_security_authorization.rst b/umn/source/configuring_a_cluster/communication_security_authorization.rst index 23220db..d9617ef 100644 --- a/umn/source/configuring_a_cluster/communication_security_authorization.rst +++ b/umn/source/configuring_a_cluster/communication_security_authorization.rst @@ -82,7 +82,6 @@ If the security group rules authorized in the cluster are insufficient for you t .. figure:: /_static/images/en-us_image_0000001349257145.png :alt: **Figure 1** Update - **Figure 1** Update #. Click **OK**. @@ -91,7 +90,6 @@ If the security group rules authorized in the cluster are insufficient for you t .. figure:: /_static/images/en-us_image_0000001295738056.png :alt: **Figure 2** Updating access control rules - **Figure 2** Updating access control rules .. |image1| image:: /_static/images/en-us_image_0000001349137565.png 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 9be1c79..f4d1232 100644 --- a/umn/source/configuring_a_cluster/creating_a_custom_cluster.rst +++ b/umn/source/configuring_a_cluster/creating_a_custom_cluster.rst @@ -348,7 +348,6 @@ If a cluster fails to be created, the failed task will be managed on the **Manag .. figure:: /_static/images/en-us_image_0000001296217700.png :alt: **Figure 1** Failed task management - **Figure 1** Failed task management :ref:`Table 5 ` lists the error codes of MRS cluster creation failures. 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 e0464e2..14cd530 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 @@ -87,15 +87,15 @@ Custom Cluster Template Description +-----------------------------------------------------------------------------------------------------------+--------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Node Deployment Principle | | Applicable Scenario | Networking Rule | +===========================================================================================================+==========================+==============================================================================================================================================================================================================================================================================================================================================+=========================================================================================================================================================================================================================================================================================================+ - | Management nodes, control nodes, and data nodes are deployed separately. | MN × 2 + CN × 9 + DN × n | (Recommended) This scheme is used when the number of data nodes is 500–2000. | - If the number of nodes in a cluster exceeds 200, the nodes are distributed to different subnets and the subnets are interconnected with each other in Layer 3 using core switches. Each subnet can contain a maximum of 200 nodes and the allocation of nodes to different subnets must be balanced. | + | Management nodes, control nodes, and data nodes are deployed separately. | MN x 2 + CN x 9 + DN x n | (Recommended) This scheme is used when the number of data nodes is 500-2000. | - If the number of nodes in a cluster exceeds 200, the nodes are distributed to different subnets and the subnets are interconnected with each other in Layer 3 using core switches. Each subnet can contain a maximum of 200 nodes and the allocation of nodes to different subnets must be balanced. | | | | | - If the number of nodes is less than 200, the nodes in the cluster are deployed in the same subnet and the nodes are interconnected with each other in Layer 2 using aggregation switches. | | (This scheme requires at least eight nodes.) | | | | +-----------------------------------------------------------------------------------------------------------+--------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | MN × 2 + CN × 5 + DN × n | (Recommended) This scheme is used when the number of data nodes is 100–500. | | + | | MN x 2 + CN x 5 + DN x n | (Recommended) This scheme is used when the number of data nodes is 100-500. | | +-----------------------------------------------------------------------------------------------------------+--------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | MN × 2 + CN × 3 + DN × n | (Recommended) This scheme is used when the number of data nodes is 30–100. | | + | | MN x 2 + CN x 3 + DN x n | (Recommended) This scheme is used when the number of data nodes is 30-100. | | +-----------------------------------------------------------------------------------------------------------+--------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | The management nodes and control nodes are deployed together, and the data nodes are deployed separately. | (MN+CN) × 3 + DN × n | (Recommended) This scheme is used when the number of data nodes is 3–30. | Nodes in the cluster are deployed in the same subnet and are interconnected with each other at Layer 2 through aggregation switches. | + | The management nodes and control nodes are deployed together, and the data nodes are deployed separately. | (MN+CN) x 3 + DN x n | (Recommended) This scheme is used when the number of data nodes is 3-30. | Nodes in the cluster are deployed in the same subnet and are interconnected with each other at Layer 2 through aggregation switches. | +-----------------------------------------------------------------------------------------------------------+--------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | The management nodes, control nodes, and data nodes are deployed together. | | - This scheme is applicable to a cluster having fewer than 6 nodes. | Nodes in the cluster are deployed in the same subnet and are interconnected with each other at Layer 2 through aggregation switches. | | | | - This scheme requires at least three nodes. | | diff --git a/umn/source/configuring_a_cluster/managing_data_connections/configuring_ranger_data_connections.rst b/umn/source/configuring_a_cluster/managing_data_connections/configuring_ranger_data_connections.rst index d2f3890..06882a7 100644 --- a/umn/source/configuring_a_cluster/managing_data_connections/configuring_ranger_data_connections.rst +++ b/umn/source/configuring_a_cluster/managing_data_connections/configuring_ranger_data_connections.rst @@ -33,7 +33,6 @@ This operation is required only for **MRS 3.1.0 or later**. .. figure:: /_static/images/en-us_image_0000001296217820.png :alt: **Figure 1** Disabling Ranger authentication - **Figure 1** Disabling Ranger authentication #. (Optional) To use an existing authentication policy, perform this step to export the authentication policy on the Ranger web page. After the Ranger metadata is switched, you can import the existing authentication policy again. The following uses Hive as an example. After the export, a policy file in JSON format is generated in a local directory. @@ -54,7 +53,6 @@ This operation is required only for **MRS 3.1.0 or later**. .. figure:: /_static/images/en-us_image_0000001349058021.png :alt: **Figure 2** Exporting authentication policies - **Figure 2** Exporting authentication policies f. .. _mrs_01_24051__li1947954718720: @@ -65,7 +63,6 @@ This operation is required only for **MRS 3.1.0 or later**. .. figure:: /_static/images/en-us_image_0000001348738221.png :alt: **Figure 3** Exporting Hive authentication policies - **Figure 3** Exporting Hive authentication policies Configuring a Data Connection for an MRS Cluster @@ -102,7 +99,6 @@ Configuring a Data Connection for an MRS Cluster .. figure:: /_static/images/en-us_image_0000001296058188.png :alt: **Figure 4** Restarting a service - **Figure 4** Restarting a service #. Enable Ranger authentication for the component to be authenticated. The Hive component is used as an example. @@ -117,7 +113,6 @@ Configuring a Data Connection for an MRS Cluster .. figure:: /_static/images/en-us_image_0000001295738404.png :alt: **Figure 5** Enabling Ranger authentication - **Figure 5** Enabling Ranger authentication #. Log in to the Ranger web UI and click the import button |image2| in the row of the Hive component. @@ -133,7 +128,6 @@ Configuring a Data Connection for an MRS Cluster .. figure:: /_static/images/en-us_image_0000001296217824.png :alt: **Figure 6** Importing authentication policies - **Figure 6** Importing authentication policies #. Restart the component for which Ranger authentication is enabled. diff --git a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_agency.rst b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_agency.rst index a79ef50..02ac960 100644 --- a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_agency.rst +++ b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_agency.rst @@ -137,7 +137,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001296217708.png :alt: **Figure 1** Returned file list - **Figure 1** Returned file list #. Verify that Hive can access OBS. @@ -164,7 +163,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001348738105.png :alt: **Figure 2** Returned table name - **Figure 2** Returned table name e. Press **Ctrl+C** to exit the Hive beeline. @@ -187,7 +185,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001349057897.png :alt: **Figure 3** Returned table name - **Figure 3** Returned table name d. Press **Ctrl+C** to exit the Spark beeline. @@ -212,7 +209,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001349257377.png :alt: **Figure 4** Return result - **Figure 4** Return result d. Run **exit** to exit the client. @@ -239,7 +235,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001349057901.png :alt: **Figure 5** Downloading the Presto user authentication credential - **Figure 5** Downloading the Presto user authentication credential #. On FusionInsight Manager for MRS 3.x or later,, choose **System > Permission > User**. In the row that contains the newly added user, click **More > Download Authentication Credential**. @@ -248,7 +243,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001296058088.png :alt: **Figure 6** Downloading the Presto user authentication credential - **Figure 6** Downloading the Presto user authentication credential e. .. _mrs_01_0768__li65281811161910: @@ -284,7 +278,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001296058084.png :alt: **Figure 7** Return result - **Figure 7** Return result j. Run **exit** to exit the client. @@ -300,7 +293,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001349137793.png :alt: **Figure 8** Creating a Flink job - **Figure 8** Creating a Flink job c. On OBS Console, go to the output path specified during job creation. If the output directory is automatically created and contains the job execution results, OBS access is successful. @@ -309,7 +301,6 @@ Step 4: Accessing the OBS File System .. figure:: /_static/images/en-us_image_0000001349137789.png :alt: **Figure 9** Flink job execution result - **Figure 9** Flink job execution result Reference diff --git a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_ak_sk.rst b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_ak_sk.rst index 3f92c82..b8c1aad 100644 --- a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_ak_sk.rst +++ b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/configuring_a_storage-compute_decoupled_cluster_ak_sk.rst @@ -119,7 +119,6 @@ Using Spark to Access OBS .. figure:: /_static/images/en-us_image_0000001295738100.png :alt: **Figure 1** Parameters for adding an OBS - **Figure 1** Parameters for adding an OBS #. Click **Save Configuration** and select **Restart the affected services or instances**. Restart the Spark service. diff --git a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hive_with_obs.rst b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hive_with_obs.rst index 887db20..028b296 100644 --- a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hive_with_obs.rst +++ b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hive_with_obs.rst @@ -51,7 +51,6 @@ Setting the Default Location of the Created Hive Table to the OBS Path .. figure:: /_static/images/en-us_image_0000001349057721.png :alt: **Figure 1** Configurations of **hive.metastore.warehouse.dir** - **Figure 1** Configurations of **hive.metastore.warehouse.dir** #. In the left navigation tree, choose **HiveServer** > **Customization**. Add **hive.metastore.warehouse.dir** to the **hive.metastore.customized.configs** and **hive.metastore.customized.configs** parameters, and set it to the OBS path. @@ -60,7 +59,6 @@ Setting the Default Location of the Created Hive Table to the OBS Path .. figure:: /_static/images/en-us_image_0000001349057725.png :alt: **Figure 2** hive.metastore.warehouse.dir configuration - **Figure 2** hive.metastore.warehouse.dir configuration #. Save the configurations and restart Hive. diff --git a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hudi_with_obs.rst b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hudi_with_obs.rst index d02feb6..61c376c 100644 --- a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hudi_with_obs.rst +++ b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_hudi_with_obs.rst @@ -76,7 +76,7 @@ Interconnecting Hudi with OBS **format("org.apache.hudi").** - **load(basePath + ``"/*/*/*/*")``** + **load(basePath + "/*/*/*/*")** **roViewDF.createOrReplaceTempView("hudi_ro_table")** diff --git a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_spark2x_with_obs.rst b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_spark2x_with_obs.rst index c9736be..7d98d3f 100644 --- a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_spark2x_with_obs.rst +++ b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_spark2x_with_obs.rst @@ -46,7 +46,6 @@ Using Spark Beeline After Cluster Installation .. figure:: /_static/images/en-us_image_0000001349057877.png :alt: **Figure 1** Verifying the created table name returned using Spark2x - **Figure 1** Verifying the created table name returned using Spark2x #. Press **Ctrl+C** to exit the Spark Beeline. diff --git a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_sqoop_with_external_storage_systems.rst b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_sqoop_with_external_storage_systems.rst index 12497e7..01438af 100644 --- a/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_sqoop_with_external_storage_systems.rst +++ b/umn/source/configuring_a_cluster_with_storage_and_compute_decoupled/using_a_storage-compute_decoupled_cluster/interconnecting_sqoop_with_external_storage_systems.rst @@ -102,11 +102,11 @@ Importing Data from MySQL to Hive Using the sqoop import Command +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | -z,-compress | Compresses sequence, text, and Avro data files using the GZIP compression algorithm. Data is not compressed by default. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | –compression-codec | Specifies the Hadoop compression codec. GZIP is used by default. | + | -compression-codec | Specifies the Hadoop compression codec. GZIP is used by default. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | –null-string | Specifies the string to be interpreted as **NULL** for string columns. | + | -null-string | Specifies the string to be interpreted as **NULL** for string columns. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | –null-non-string | Specifies the string to be interpreted as null for non-string columns. If this parameter is not specified, **NULL** will be used. | + | -null-non-string | Specifies the string to be interpreted as null for non-string columns. If this parameter is not specified, **NULL** will be used. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | -check-column (col) | Specifies the column for checking incremental data import, for example, **id**. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/data_backup_and_restoration/hbase_data.rst b/umn/source/data_backup_and_restoration/hbase_data.rst index 3303142..65aba7c 100644 --- a/umn/source/data_backup_and_restoration/hbase_data.rst +++ b/umn/source/data_backup_and_restoration/hbase_data.rst @@ -124,7 +124,6 @@ In the command, **member** indicates the name of the table to be exported. .. figure:: /_static/images/en-us_image_0000001349137569.png :alt: **Figure 1** Directory data - **Figure 1** Directory data #. Run the **create** command to create a table in the standby cluster with the same structure as that of the active cluster, for example, **member_import**. @@ -215,7 +214,7 @@ Offline backup of HDFS data means stopping the HBase service and allowing users **hadoop distcp -i /hbase/data hdfs://IP address of the active NameNode of the HDFS service in the standby cluster:Port number/hbase** - **hadoop distcp –update –append –delete /hbase/ hdfs://IP address of the active NameNode of the HDFS service in the standby cluster:Port number/hbase/** + **hadoop distcp -update -append -delete /hbase/ hdfs://IP address of the active NameNode of the HDFS service in the standby cluster:Port number/hbase/** The second command is used to incrementally copy files except the data directory. For example, data in **archive** may be referenced by the data directory. diff --git a/umn/source/data_backup_and_restoration/hdfs_data.rst b/umn/source/data_backup_and_restoration/hdfs_data.rst index e3a34b0..983707e 100644 --- a/umn/source/data_backup_and_restoration/hdfs_data.rst +++ b/umn/source/data_backup_and_restoration/hdfs_data.rst @@ -58,7 +58,7 @@ HDFS metadata information to be exported includes file and folder permissions an .. code-block:: - $HADOOP_HOME/bin/hdfs dfs –ls –R > /tmp/hdfs_meta.txt + $HADOOP_HOME/bin/hdfs dfs -ls -R > /tmp/hdfs_meta.txt The following provides description about the parameters in the preceding command. @@ -77,5 +77,5 @@ Based on the exported permission information, run the HDFS commands in the backg .. code-block:: - $HADOOP_HOME/bin/hdfs dfs –chmod - $HADOOP_HOME/bin/hdfs dfs –chown + $HADOOP_HOME/bin/hdfs dfs -chmod + $HADOOP_HOME/bin/hdfs dfs -chown 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 208b38a..da9f661 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 @@ -21,14 +21,13 @@ How Do I Check Whether the ResourceManager Configuration of Yarn Is Correct? .. figure:: /_static/images/en-us_image_0293129996.png :alt: **Figure 1** Synchronization configurations - **Figure 1** Synchronization configurations #. Log in to the Master nodes as user **root**. #. Run the **cd /opt/Bigdata/MRS_Current/*_*_ResourceManager/etc_UPDATED/** command to go to the **etc_UPDATED** directory. -#. Run the **grep '\.queues' capacity-scheduler.xml -A2** command to display all configured queues and check whether the queues are consistent with those displayed on Manager. +#. Run the **grep '\\.queues' capacity-scheduler.xml -A2** command to display all configured queues and check whether the queues are consistent with those displayed on Manager. **root-default** is hidden on the Manager page. @@ -36,7 +35,7 @@ How Do I Check Whether the ResourceManager Configuration of Yarn Is Correct? #. .. _mrs_03_1163__li941013146411: - Run the **grep '\.capacity' capacity-scheduler.xml -A2** command to display the value of each queue and check whether the value of each queue is the same as that displayed on Manager. Check whether the sum of the values configured for all queues is **100**. + Run the **grep '\\.capacity' capacity-scheduler.xml -A2** command to display the value of each queue and check whether the value of each queue is the same as that displayed on Manager. Check whether the sum of the values configured for all queues is **100**. - If the sum is **100**, the configuration is correct. - If the sum is not **100**, the configuration is incorrect. Perform the following steps to rectify the fault. 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 f31af30..658459d 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 @@ -38,7 +38,6 @@ How Do I Connect to Spark Beeline from MRS? .. figure:: /_static/images/en-us_image_0264281176.png :alt: **Figure 1** Returned table name - **Figure 1** Returned table name #. Press **Ctrl+C** to exit the Spark Beeline. 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 1815523..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 @@ -18,7 +18,6 @@ Solutions: .. figure:: /_static/images/en-us_image_0000001205479339.png :alt: **Figure 1** Changing the **component_env** file - **Figure 1** Changing the **component_env** file #. Run the following command to verify the configuration: 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 91615f7..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 @@ -29,5 +29,4 @@ How Do I Configure the knox Memory? .. 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 0e5dbc4..771a6d0 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 @@ -21,7 +21,6 @@ How Do I Do If the Time on MRS Nodes Is Incorrect? .. figure:: /_static/images/en-us_image_0000001229685789.png :alt: **Figure 1** Adding the master node IP addresses - **Figure 1** Adding the master node IP addresses #. .. _mrs_03_1211__li1924115541119: 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 f8ee840..22630eb 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 @@ -22,5 +22,4 @@ You can view operation logs of clusters and jobs on the **Operation Logs** page. .. figure:: /_static/images/en-us_image_0264281200.png :alt: **Figure 1** Log information - **Figure 1** Log information diff --git a/umn/source/faq/kerberos_usage/how_do_i_access_presto_in_a_cluster_with_kerberos_authentication_enabled.rst b/umn/source/faq/kerberos_usage/how_do_i_access_presto_in_a_cluster_with_kerberos_authentication_enabled.rst index 64d46e8..aa393f7 100644 --- a/umn/source/faq/kerberos_usage/how_do_i_access_presto_in_a_cluster_with_kerberos_authentication_enabled.rst +++ b/umn/source/faq/kerberos_usage/how_do_i_access_presto_in_a_cluster_with_kerberos_authentication_enabled.rst @@ -35,7 +35,6 @@ How Do I Access Presto in a Cluster with Kerberos Authentication Enabled? .. figure:: /_static/images/en-us_image_0264281104.png :alt: **Figure 1** Downloading the Presto user authentication credential - **Figure 1** Downloading the Presto user authentication credential - Operations on FusionInsight Manager: @@ -75,7 +74,6 @@ How Do I Access Presto in a Cluster with Kerberos Authentication Enabled? .. figure:: /_static/images/en-us_image_0264281044.png :alt: **Figure 2** Return result - **Figure 2** Return result j. Run **exit** to exit the client. 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 3d19430..8e9bb28 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 @@ -37,7 +37,6 @@ How Do I Access Spark in a Cluster with Kerberos Authentication Enabled? .. figure:: /_static/images/en-us_image_0000001153149209.png :alt: **Figure 1** Returned table name - **Figure 1** Returned table name #. Press **Ctrl+C** to exit Spark Beeline. diff --git a/umn/source/faq/kerberos_usage/how_do_i_prevent_kerberos_authentication_expiration.rst b/umn/source/faq/kerberos_usage/how_do_i_prevent_kerberos_authentication_expiration.rst index e535fec..69190d1 100644 --- a/umn/source/faq/kerberos_usage/how_do_i_prevent_kerberos_authentication_expiration.rst +++ b/umn/source/faq/kerberos_usage/how_do_i_prevent_kerberos_authentication_expiration.rst @@ -37,4 +37,4 @@ How Do I Prevent Kerberos Authentication Expiration? Example: - **spark-shell --principal spark2x/hadoop.**\ <*System domain name*>@<*System domain name*>\ **--keytab ${BIGDATA_HOME}/FusionInsight_Spark2x_8.1.0.1/install/FusionInsight-Spark2x-2.4.5/keytab/spark2x/SparkResource/spark2x.keytab --master yarn** + **spark-shell --principal spark2x/hadoop.**\ <*System domain name*>@<*System domain name*>\ ** --keytab ${BIGDATA_HOME}/FusionInsight_Spark2x_8.1.0.1/install/FusionInsight-Spark2x-2.4.5/keytab/spark2x/SparkResource/spark2x.keytab --master yarn** 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 8c0d81e..80c2bf3 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 @@ -67,7 +67,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383824.png :alt: **Figure 1** Setting alarm smoothing times - **Figure 1** Setting alarm smoothing times On **Host CPU Usage** page and click **Modify** in the **Operation** column to change the alarm threshold, as shown in :ref:`Figure 2 `. @@ -77,7 +76,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383825.png :alt: **Figure 2** Setting an alarm threshold - **Figure 2** Setting an alarm threshold #. After 2 minutes, check whether the alarm is cleared. 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 37d3a69..26ed652 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 @@ -70,7 +70,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383827.png :alt: **Figure 1** Setting an alarm threshold - **Figure 1** Setting an alarm threshold #. After 2 minutes, check whether the alarm is cleared. 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 610bc7a..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 @@ -84,7 +84,7 @@ Procedure 6. If the memory usage exceeds the threshold, perform memory capacity expansion. -7. Run the command **free -m \| grep Mem\: \| awk '{printf("%s,", $3 \* 100 / $2)}'** to check the system memory usage. +7. Run the command **free -m \| grep Mem\\: \| awk '{printf("%s,", $3 \* 100 / $2)}'** to check the system memory usage. 8. Wait for 5 minutes, check whether the alarm is cleared. 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_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 index 00d75c3..aa20d59 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_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 @@ -59,7 +59,7 @@ Procedure #. 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}'** + **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}'** #. Check whether the command output is empty. 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 f5e9d3d..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 @@ -82,7 +82,7 @@ Procedure #. .. _alm-12040__li34867421105655: - Run the **ps -ef \| grep -v "grep" \| grep rngd \| tr -d " " \| grep "\-r/dev/urandom"** command and check the command output. + Run the **ps -ef \| grep -v "grep" \| grep rngd \| tr -d " " \| grep "\\-r/dev/urandom"** command and check the command output. - If the command is executed successfully, rngd has been installed and configured correctly and is running properly. Go to :ref:`8 `. @@ -112,7 +112,7 @@ Procedure .. code-block:: Type=simple - ExecStar=/usr/sbin/haveged -w 1024 -v 1 –Foreground + ExecStar=/usr/sbin/haveged -w 1024 -v 1 -Foreground SuccessExitStatus=137 143 Restart=always 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 56e3e95..c40199a 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 @@ -241,7 +241,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001194891604.png :alt: **Figure 1** Configuring the alarm threshold - **Figure 1** Configuring the alarm threshold 16. After 5 minutes, check whether the alarm is cleared. 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 922cf5d..1e76407 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 @@ -74,7 +74,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001194571658.png :alt: **Figure 1** Configuring the alarm threshold - **Figure 1** Configuring the alarm threshold #. After 5 minutes, check whether the alarm is cleared. 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 9fde4cd..50924f5 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 @@ -74,7 +74,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001239731545.png :alt: **Figure 1** Configuring the alarm threshold - **Figure 1** Configuring the alarm threshold #. After 5 minutes, check whether the alarm is cleared. 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 d61dad9..322588b 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 @@ -74,7 +74,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001239611529.png :alt: **Figure 1** Configuring the alarm threshold - **Figure 1** Configuring the alarm threshold #. After 5 minutes, check whether the alarm is cleared. 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 ee841d3..1d2896a 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 @@ -74,7 +74,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383871.png :alt: **Figure 1** Setting alarm thresholds - **Figure 1** Setting alarm thresholds #. Wait for 5 minutes, and check whether the alarm is cleared. 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 4e0ded5..e615f57 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 @@ -74,7 +74,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383874.png :alt: **Figure 1** Setting alarm thresholds - **Figure 1** Setting alarm thresholds #. Wait for 5 minutes, and check whether the alarm is cleared. 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 904b2df..a363dbc 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 @@ -69,7 +69,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383904.jpg :alt: **Figure 1** Setting Trigger Count - **Figure 1** Setting Trigger Count Set the alarm threshold based on the actual process usage. To check the process usage, choose **O&M** > **Alarm** > **Thresholds** > *Name of the desired cluster* > **Host**> **Process** > **omm Process Usage**, as shown in :ref:`Figure 2 `. @@ -79,7 +78,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383905.png :alt: **Figure 2** Setting an alarm threshold - **Figure 2** Setting an alarm threshold #. 2 minutes later, check whether the alarm is cleared. 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 53dc357..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 @@ -72,7 +72,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269383933.png :alt: **Figure 1** Cluster information - **Figure 1** Cluster information 5. In the early morning of the next day, check whether this alarm is cleared. 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 6ec98cd..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 @@ -159,7 +159,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269417415.png :alt: **Figure 1** HBase system table - **Figure 1** HBase system table 18. .. _alm-19000__li52774331192610: @@ -187,7 +186,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269417416.png :alt: **Figure 2** HMaster is being started - **Figure 2** HMaster is being started .. _alm-19000__fig41660353192610: @@ -195,7 +193,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269417417.png :alt: **Figure 3** HMaster is started - **Figure 3** HMaster is started - If yes, go to :ref:`20 `. @@ -209,7 +206,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269417418.png :alt: **Figure 4** Region in Transition - **Figure 4** Region in Transition - If yes, go to :ref:`21 `. 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 a153c9f..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 @@ -66,7 +66,6 @@ Procedure .. figure:: /_static/images/en-us_image_0276801805.png :alt: **Figure 1** WebUI of HBase instance - **Figure 1** WebUI of HBase instance **Enable load balancing.** 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 00f33b8..d1d3503 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 @@ -67,7 +67,6 @@ Procedure .. 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 #. Wait for 2 minutes and check whether the alarm is automatically cleared. @@ -86,7 +85,6 @@ Procedure .. 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 5. After the maximum number of database connections is changed, restart DBService (do not restart the upper-layer services). @@ -115,7 +113,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001133372255.png :alt: **Figure 3** Setting alarm trigger count - **Figure 3** Setting alarm trigger count Based on the actual database connection usage, choose **O&M** >\ **Alarm** > **Thresholds** > *Name of the desired cluster* > **DBService > Database > Database Connections Usage (DBServer)**. In the **Database Connections Usage (DBServer)** area, click **Modify** in the **Operation** column. In the **Modify Rule** dialog box, modify the required parameters and click **OK** as shown in :ref:`Figure 4 `. @@ -125,7 +122,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001193639590.png :alt: **Figure 4** Set alarm threshold - **Figure 4** Set alarm threshold 8. Wait for 2 minutes and check whether the alarm is automatically cleared. 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 a9acac3..b6a8fc2 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 @@ -91,7 +91,7 @@ Procedure Run the following command to check whether the ClickHouse cluster topology information can be obtained. - **get /clickhouse/config/**\ *value of*\ **macros.id**\ *in* :ref:`3 `/metrika.xml + **get /clickhouse/config/**\ *value of* **macros.id** *in* :ref:`3 `/metrika.xml - If yes, go to :ref:`6 `. - If no, go to :ref:`9 `. 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 a5b7a5f..ae102bc 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 @@ -20,7 +20,6 @@ Log in to FusionInsight Manager and choose **Audit**. The **Audit** page display .. figure:: /_static/images/en-us_image_0000001318467884.png :alt: **Figure 1** Audit information list - **Figure 1** Audit information list - You can select audit logs at the **Critical**, **Major**, **Minor**, or **Notice** level from the **All risk levels** drop-down list. 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 5ecc787..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 @@ -94,7 +94,7 @@ Procedure a. Click **Query Regular Expression**. b. Enter the database where the ClickHouse tables are located in the first text box as prompted. The database must be the same as the existing database, for example, **default**. - c. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get all tables in the database, enter **([\s\S]*?)**. To get tables named in the format of letters and digits, for example, **tb1**, enter **tb\d\***. + c. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get all tables in the database, enter **([\\s\\S]*?)**. To get tables named in the format of letters and digits, for example, **tb1**, enter **tb\\d\***. d. Click **Refresh** to view the displayed tables in **Directory Name**. e. Click **Synchronize** to save the result. 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 2952cb2..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 @@ -145,7 +145,7 @@ Procedure a. Click **Query Regular Expression**. b. Enter the namespace where the HBase tables are located in the first text box as prompted. The namespace must be the same as the existing namespace, for example, **default**. - c. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get all tables in the namespace, enter **([\s\S]*?)**. To get tables whose names consist of letters and digits, for example, **tb1**, enter **tb\d\***. + c. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get all tables in the namespace, enter **([\\s\\S]*?)**. To get tables whose names consist of letters and digits, for example, **tb1**, enter **tb\\d\***. d. Click **Refresh** to view the displayed tables in **Directory Name**. e. Click **Synchronize** to save the result. 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 88a4edd..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 @@ -144,7 +144,7 @@ Procedure 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, **/tmp**. - 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\***. + 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. Click **Refresh** to view the displayed directories in **Directory Name**. e. Click **Synchronize** to save the result. 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 84d0ccd..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 @@ -138,7 +138,7 @@ Procedure a. Click **Query Regular Expression**. b. Enter the database where the Hive tables are located in the first text box as prompted. The database must be the same as the existing database, for example, **default**. - c. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get all tables in the database, enter **([\s\S]*?)**. To get tables whose names consist of letters and digits, for example, **tb1**, enter **tb\d\***. + c. Enter a regular expression in the second text box. Standard regular expressions are supported. For example, to get all tables in the database, enter **([\\s\\S]*?)**. To get tables whose names consist of letters and digits, for example, **tb1**, enter **tb\\d\***. d. Click **Refresh** to view the displayed tables in **Directory Name**. e. Click **Synchronize** to save the result. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/enabling_cross-cluster_replication.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/enabling_cross-cluster_replication.rst index 67b5336..38f1062 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/enabling_cross-cluster_replication.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/enabling_cross-cluster_replication.rst @@ -30,7 +30,7 @@ Procedure #. .. _admin_guide_000200__en-us_topic_0046736761_li45131484: - Choose **Cluster** > ****Name of the desired cluster** > \ Services** > **Yarn** > **Configurations**, and click **All Configurations**. + Choose **Cluster** > ****Name of the desired cluster** > Services** > **Yarn** > **Configurations**, and click **All Configurations**. #. In the navigation pane, choose **Yarn** > **Distcp**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/how_do_i_configure_the_environment_when_i_create_a_clickhouse_backup_task_on_fusioninsight_manager_and_set_the_path_type_to_remotehdfs.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/how_do_i_configure_the_environment_when_i_create_a_clickhouse_backup_task_on_fusioninsight_manager_and_set_the_path_type_to_remotehdfs.rst index 8bc1056..df9d767 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/how_do_i_configure_the_environment_when_i_create_a_clickhouse_backup_task_on_fusioninsight_manager_and_set_the_path_type_to_remotehdfs.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/how_do_i_configure_the_environment_when_i_create_a_clickhouse_backup_task_on_fusioninsight_manager_and_set_the_path_type_to_remotehdfs.rst @@ -23,7 +23,7 @@ Answer #. After the client file package is generated, download the client to the local PC as prompted and decompress the package. - For example, if the client file package is **FusionInsight_Cluster_1_HDFS_Client.tar**, decompress it to obtain **FusionInsight_Cluster_1_HDFS_ClientConfig_ConfigFiles.tar**, and then decompress **FusionInsight_Cluster_1_HDFS_ClientConfig_ConfigFiles.tar** to the **D:\FusionInsight_Cluster_1_HDFS_ClientConfig_ConfigFiles** directory on the local PC. The directory name cannot contain spaces. + For example, if the client file package is **FusionInsight_Cluster_1_HDFS_Client.tar**, decompress it to obtain **FusionInsight_Cluster_1_HDFS_ClientConfig_ConfigFiles.tar**, and then decompress **FusionInsight_Cluster_1_HDFS_ClientConfig_ConfigFiles.tar** to the **D:\\FusionInsight_Cluster_1_HDFS_ClientConfig_ConfigFiles** directory on the local PC. The directory name cannot contain spaces. #. .. _admin_guide_000357__li73411714152720: diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_dbservice_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_dbservice_data.rst index 500e04a..457cab2 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_dbservice_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_dbservice_data.rst @@ -81,7 +81,7 @@ Procedure If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **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**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_metadata.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_metadata.rst index 64baddf..352a7e3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_metadata.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_metadata.rst @@ -80,7 +80,7 @@ Procedure If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **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**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_service_data.rst index c803559..b9fddb0 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hbase_service_data.rst @@ -67,7 +67,7 @@ Procedure - **RemoteHDFS**: indicates that the backup files are stored in the HDFS directory of the standby cluster. If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **Source Path**: indicates the full path of the backup file in the HDFS, for example, *Backup path/Backup task name_Data source_Task creation time*. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hdfs_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hdfs_service_data.rst index dd6c50c..07f1922 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hdfs_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hdfs_service_data.rst @@ -69,7 +69,7 @@ Procedure If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **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*. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hive_service_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hive_service_data.rst index 5c233db..2049916 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hive_service_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_hive_service_data.rst @@ -69,7 +69,7 @@ Procedure - **RemoteHDFS**: indicates that the backup files are stored in the HDFS directory of the standby cluster. If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **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*. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_kafka_metadata.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_kafka_metadata.rst index 12b63c5..eb20115 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_kafka_metadata.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_kafka_metadata.rst @@ -81,7 +81,7 @@ Procedure If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **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**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_manager_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_manager_data.rst index 4a67a4a..dd8078d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_manager_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_manager_data.rst @@ -82,7 +82,7 @@ Procedure If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **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**. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_namenode_data.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_namenode_data.rst index d58ad80..9a84c21 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_namenode_data.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/backup_and_recovery_management/recovering_data/restoring_namenode_data.rst @@ -82,7 +82,7 @@ Procedure If you select **RemoteHDFS**, set the following parameters: - - **Source NameService Name**: indicates the NameService name of the backup data cluster.You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote cluster. + - **Source NameService Name**: indicates the NameService name of the backup data cluster. You can enter the built-in NameService name of the remote cluster, for example, **haclusterX**, **haclusterX1**, **haclusterX2**, **haclusterX3**, or **haclusterX4**. You can also enter a configured NameService name of the remote 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 NameNode IP Address**: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node. - **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**. 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 f95ca3b..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 @@ -31,7 +31,7 @@ Procedure a. Click |image2| and enter a new description. - Enter a maximum of 199 characters. Only letters, digits, commas (,), periods (.), underscores (_), spaces, and newline characters (\n) are allowed. + Enter a maximum of 199 characters. Only letters, digits, commas (,), periods (.), underscores (_), spaces, and newline characters (\\n) are allowed. b. Click **OK** for the new description to take effect. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/viewing_the_instance_configuration_file.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/viewing_the_instance_configuration_file.rst index 214dfe3..c7f3978 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/viewing_the_instance_configuration_file.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/instance_management/viewing_the_instance_configuration_file.rst @@ -25,7 +25,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001318280410.png :alt: **Figure 1** Viewing the instance configuration file - **Figure 1** Viewing the instance configuration file #. Click the name of the configuration file to be viewed to view the parameter values in the configuration file. 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 46551ba..ec6d3f6 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 @@ -14,7 +14,6 @@ Log in to FusionInsight Manager. Choose **Cluster**, click the name of the desir .. figure:: /_static/images/en-us_image_0000001318094514.png :alt: **Figure 1** Service management page - **Figure 1** Service management page Functional Area diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/service_configuration/modifying_service_configuration_parameters.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/service_configuration/modifying_service_configuration_parameters.rst index 59b4798..026f9d3 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/service_configuration/modifying_service_configuration_parameters.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster/managing_a_service/service_configuration/modifying_service_configuration_parameters.rst @@ -39,7 +39,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001318599190.png :alt: **Figure 1** Configuration parameter navigation tree - **Figure 1** Configuration parameter navigation tree #. In the navigation tree, select the specified parameter category and change the parameter values on the right. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/configuring_client/installing_a_client.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/configuring_client/installing_a_client.rst index 5ddaf81..4470094 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/configuring_client/installing_a_client.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/cluster_management/configuring_client/installing_a_client.rst @@ -38,7 +38,6 @@ Procedure .. figure:: /_static/images/en-us_image_0263899243.png :alt: **Figure 1** Downloading a client - **Figure 1** Downloading a client .. note:: 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 54c26d8..9888e62 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 @@ -90,7 +90,6 @@ Procedure .. figure:: /_static/images/en-us_image_0269662620.png :alt: **Figure 1** Exiting the maintenance mode in batches - **Figure 1** Exiting the maintenance mode in batches .. |image1| image:: /_static/images/en-us_image_0263899304.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 15f0b59..87ea150 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 @@ -25,7 +25,6 @@ FusionInsight Manager provides a unified cluster management platform, facilitati .. figure:: /_static/images/en-us_image_0279806562.png :alt: **Figure 1** FusionInsight Manager GUI - **Figure 1** FusionInsight Manager GUI The upper part of the page is the operation bar, the middle part is the display area, and the bottom part is the taskbar. 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 ecf3563..43ac5b8 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 @@ -22,7 +22,7 @@ Procedure The password must: - Contain 8 to 64 characters. - - Contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\?`). + - Contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\\?`). - Be different from the username or the username spelled backwards. - Be different from the current password. 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 d7bab3f..55457e4 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 @@ -13,7 +13,6 @@ After you log in to FusionInsight Manager, **Homepage** is displayed by default. .. figure:: /_static/images/en-us_image_0263899253.png :alt: **Figure 1** Cluster status information - **Figure 1** Cluster status information - Click |image1| to view the task name, cluster, status, progress, start time, and end time of the last 100 operation tasks in **Task Management Center**. 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 eaa5386..d3359f0 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 @@ -20,7 +20,6 @@ Hadoop uses a file directory structure to represent hosts. :ref:`Figure 1 **Resource Overview**. On .. figure:: /_static/images/en-us_image_0000001087459671.png :alt: **Figure 1** Distribution tab - **Figure 1** Distribution tab - You can click **Select Metric** to customize the metric to monitor. :ref:`Table 1 ` describes all the metrics that you can select. After you select a metric, the host distribution in each range of the metric is displayed. 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 2d5e33c..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 @@ -13,7 +13,6 @@ You can click **Export Data** to export the configuration list of all hosts in t .. figure:: /_static/images/en-us_image_0000001369746545.png :alt: **Figure 1** Host tab - **Figure 1** Host tab Basic Configurations (CPU/Memory) 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 e9270c5..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 @@ -11,7 +11,6 @@ Log in to FusionInsight and choose **Hosts** > **Resource Overview**. On the **R .. figure:: /_static/images/en-us_image_0000001370061921.png :alt: **Figure 1** Trend tab - **Figure 1** Trend tab - You can click **Add Host to Chart** to add trend lines of up to 12 hosts to the trend charts. 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 770c631..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 @@ -28,5 +28,4 @@ Procedure .. 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&m/alarms/configuring_the_alarm_masking_status.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/configuring_the_alarm_masking_status.rst index 7ebeff4..cde5aa9 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/configuring_the_alarm_masking_status.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/configuring_the_alarm_masking_status.rst @@ -31,7 +31,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001369953797.png :alt: **Figure 1** Masking an alarm - **Figure 1** Masking an alarm The information about the alarm is displayed, including the alarm name, ID, severity, masking status, and operations can be performed on the alarm. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/configuring_the_threshold.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/configuring_the_threshold.rst index 5288c55..be3d920 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/configuring_the_threshold.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/configuring_the_threshold.rst @@ -23,7 +23,6 @@ Procedure .. 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 For example, after selecting **Host Memory Usage**, the information about this indicator threshold is displayed. @@ -59,7 +58,7 @@ Procedure +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ | Add Date | This parameter is available only when **Date** is set to **Others**. You can set the date when the rule takes effect. Multiple options are available. | 09-30 | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Thresholds | This parameter is used to set the time range when the rule takes effect. | Start and End Time: 00:00–08:30 | + | Thresholds | This parameter is used to set the time range when the rule takes effect. | Start and End Time: 00:00-08:30 | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ | | Threshold of the rule monitoring metric | Threshold: 10 | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/overview_of_alarms_and_events.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/overview_of_alarms_and_events.rst index dc109db..af974f5 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/overview_of_alarms_and_events.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/o&m/alarms/overview_of_alarms_and_events.rst @@ -15,7 +15,6 @@ Log in to FusionInsight Manager and choose **O&M** > **Alarm** > **Alarms**. On .. figure:: /_static/images/en-us_image_0263899646.png :alt: **Figure 1** Alarms - **Figure 1** Alarms You can click |image1| on the left of an alarm to view detailed alarm parameters. :ref:`Table 1 ` describes the parameters. @@ -78,7 +77,6 @@ Log in to FusionInsight Manager and choose **O&M** > **Alarm** > **Events**. On .. figure:: /_static/images/en-us_image_0263899271.png :alt: **Figure 2** Events page - **Figure 2** Events page You can click |image4| on the left of an event to view detailed event parameters. :ref:`Table 2 ` describes the parameters. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_a_component_running_user.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_a_component_running_user.rst index c01ae85..2b10fad 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_a_component_running_user.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_a_component_running_user.rst @@ -55,7 +55,7 @@ Procedure The password must meet the following complexity requirements by default: - The password contains at least 8 characters. - - The password contains at least four types of the following characters: Uppercase letters, lowercase letters, digits, spaces, and special characters which can only be :literal:`~`!?,.;-_'(){}[]/<>@#$%^&*+|\=.` + - The password contains at least four types of the following characters: Uppercase letters, lowercase letters, digits, spaces, and special characters which can only be :literal:`~`!?,.;-_'(){}[]/<>@#$%^&*+|\\=.` - The password cannot be the same as the username or the username spelled backwards. - The password cannot be a common easily-cracked passwords, for example, **Admin@12345**. - The password cannot be the same as the password used in latest *N* times. *N* indicates the value of **Number of Historical Passwords** configured in :ref:`Configuring Password Policies `. This policy applies to only human-machine accounts. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_kerberos_administrator.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_kerberos_administrator.rst index 8b668e6..97efc19 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_kerberos_administrator.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_kerberos_administrator.rst @@ -37,7 +37,7 @@ Procedure The password must meet the following complexity requirements by default: - The password contains at least 8 characters. - - The password contains at least four types of the following characters: Uppercase letters, lowercase letters, digits, spaces, and special characters which can only be :literal:`~`!?,.;-_'(){}[]/<>@#$%^&*+|\=.` + - The password contains at least four types of the following characters: Uppercase letters, lowercase letters, digits, spaces, and special characters which can only be :literal:`~`!?,.;-_'(){}[]/<>@#$%^&*+|\\=.` - The password cannot be the same as the username or the username spelled backwards. - The password cannot be a common easily-cracked passwords, for example, **Admin@12345**. - The password cannot be the same as the password used in the last *N* times. *N* indicates the value of **Repetition Rule** in :ref:`Configuring Password Policies `. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_oms_kerberos_administrator.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_oms_kerberos_administrator.rst index 7300b7d..e77865d 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_oms_kerberos_administrator.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_internal_user/changing_the_password_for_the_oms_kerberos_administrator.rst @@ -32,7 +32,7 @@ Procedure The password must meet the following complexity requirements by default: - The password contains at least 8 characters. - - The password contains at least four types of the following characters: uppercase letters, lowercase letters, digits, and special characters can only be :literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\=.` + - The password contains at least four types of the following characters: uppercase letters, lowercase letters, digits, and special characters can only be :literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\\=.` - The password cannot be the same as the username or the username spelled backwards. - The password cannot be a common easily-cracked passwords, for example, **Admin@12345**. - The password cannot be the same as the password used in the last *N* times. *N* indicates the value of **Repetition Rule** in :ref:`Configuring Password Policies `. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_user/changing_the_password_for_user_admin.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_user/changing_the_password_for_user_admin.rst index 4a118d9..e2ca247 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_user/changing_the_password_for_user_admin.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/account_management/changing_the_password_for_a_system_user/changing_the_password_for_user_admin.rst @@ -26,7 +26,7 @@ Procedure The password must meet the following complexity requirements by default: - The password contains 8 to 64 characters. - - The password contains at least four types of the following characters: Uppercase letters, lowercase letters, digits, spaces, and special characters which can only be :literal:`~`!?,.;-_'(){}[]/<>@#$%^&*+|\=.` + - The password contains at least four types of the following characters: Uppercase letters, lowercase letters, digits, spaces, and special characters which can only be :literal:`~`!?,.;-_'(){}[]/<>@#$%^&*+|\\=.` - The password cannot be the same as the username or the username spelled backwards. - The password cannot be a common easily-cracked passwords. - The password cannot be the same as the password used in the last *N* times. *N* indicates the value of **Repetition Rule** in :ref:`Configuring Password Policies `. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hardening_policies.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hardening_policies.rst index 874272c..b3ed7df 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hardening_policies.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/security_management/security_hardening/hardening_policies.rst @@ -39,7 +39,7 @@ Hardening JDK Obtain the Java Cryptography Extension (JCE) package whose version matches that of JDK. The JCE package contains **local_policy.jar** and **US_export_policy.jar**. Copy the JAR files to the following directory and replace the files in the directory. - Linux: *JDK installation directory*\ **/jre/lib/security** - - Windows: *JDK installation directory*\ **\\jre\lib\security** + - Windows: *JDK installation directory*\ **\\jre\\lib\\security** .. note:: @@ -50,4 +50,4 @@ Hardening JDK Obtain **SMS4JA.jar** in the *client installation directory*\ **/JDK/jdk/jre/lib/ext/** directory, and copy the JAR package to the following directory: - Linux: *JDK installation directory*\ **/jre/lib/ext/** - - Windows: *JDK installation directory*\ **\\jre\lib\ext\\** + - Windows: *JDK installation directory*\ **\\jre\\lib\\ext\\** 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 836efa3..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 @@ -16,7 +16,6 @@ The right model of FusionInsight consists four parts, that is users, user groups .. figure:: /_static/images/en-us_image_0263899538.png :alt: **Figure 1** Right model - **Figure 1** Right model - **Right** 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 9a0839d..71668c5 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 @@ -60,7 +60,7 @@ Procedure | | | | | | | **Severity Level** and **Facility** determine the priority of the sent message. | | | | | - | | | **Priority** = **Facility** × 8 + **Severity Level** | + | | | **Priority** = **Facility** x 8 + **Severity Level** | | | | | | | | For details about the values of **Severity Level** and **Facility**, see :ref:`Table 2 `. | +---------------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/changing_a_user_password.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/changing_a_user_password.rst index 816e21c..65bd2ea 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/changing_a_user_password.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/changing_a_user_password.rst @@ -34,7 +34,7 @@ Changing the Password on FusionInsight Manager By default, the password must meet the following complexity requirements: - The password contains at least 8 characters. - - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\?`). + - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\\?`). - The password cannot be the same as the username or the username spelled backwards. - The password cannot be a common easily-cracked password. - The password cannot be the same as the password used in the latest *N* times. *N* indicates the value of **Repetition Rule** configured in :ref:`Configuring Password Policies `. @@ -61,7 +61,7 @@ Changing the Password on the Client By default, the password must meet the following complexity requirements: - The password contains at least 8 characters. - - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\?`). + - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\\?`). - The password cannot be the same as the username or the username spelled backwards. - The password cannot be a common easily-cracked password. - The password cannot be the same as the password used in the latest *N* times. *N* indicates the value of **Repetition Rule** configured in :ref:`Configuring Password Policies `. diff --git a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/initializing_a_password.rst b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/initializing_a_password.rst index a887c07..1b8cc41 100644 --- a/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/initializing_a_password.rst +++ b/umn/source/fusioninsight_manager_operation_guide_applicable_to_3.x/system_configuration/configuring_permissions/managing_users/initializing_a_password.rst @@ -28,7 +28,7 @@ Procedure The password must meet the following complexity requirements by default: - The password contains at least 8 characters. - - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\?`). + - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`\`~!@#$%^&*()-_=+|[{}];',<.>/\\?`). - The password cannot be the same as the username or the username spelled backwards. - The password cannot be a common easily-cracked password. - The password cannot be the same as the password used in the latest *N* times. *N* indicates the value of **Repetition Rule** configured in :ref:`Configuring Password Policies `. 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 70476e0..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 @@ -35,7 +35,7 @@ Procedure +============================================================+==========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ | Minimum Password Length | Indicates the minimum number of characters a password contains. The value ranges from **8** to **32**. The default value is **8**. | +------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | 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. | + | 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**. The default value is **5**. | +------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 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 a0f2139..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 @@ -32,7 +32,7 @@ Prerequisites To avoid potential security risks, the password must meet the following complexity requirements: - It must contain at least eight characters. - - It must contain at least four of the following character types: uppercase letters, lowercase letters, digits, and special characters :literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\=.` + - It must contain at least four of the following character types: uppercase letters, lowercase letters, digits, and special characters :literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\\=.` - When applying for certificates from the certificate administrator, you have provided the password for accessing the key file and applied for the certificate files in CRT, CER, CERT, and PEM formats and the key files in KEY and PEM formats. The requested certificates must have the issuing function. 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 ae94e1d..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 @@ -13,7 +13,6 @@ Administrators need to determine the service scenarios of cluster resources and .. figure:: /_static/images/en-us_image_0263899222.png :alt: **Figure 1** Creating a tenant - **Figure 1** Creating a tenant :ref:`Table 1 ` describes the operations for 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 5ae861a..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 @@ -19,7 +19,6 @@ FusionInsight Manager provides the graphical multi-tenant management interface a .. 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 **Hierarchical Tenant Management** @@ -71,7 +70,6 @@ Clear Resource Management .. figure:: /_static/images/en-us_image_0263899641.png :alt: **Figure 2** Refined monitoring - **Figure 2** Refined monitoring By default, the real-time monitoring data is displayed. You can click |image2| to customize a time range. The default time ranges include 4 hours, 8 hours, 12 hours, 1 day, 1 week, and 1 month. Click |image3| and select **Export** to export the monitoring metric information. 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 488af73..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 @@ -15,7 +15,6 @@ The following figure shows a multi-tenant model. .. figure:: /_static/images/en-us_image_0263899456.png :alt: **Figure 1** Multi-tenant model - **Figure 1** Multi-tenant model :ref:`Table 1 ` describes the concepts involved in :ref:`Figure 1 `. @@ -96,7 +95,6 @@ Tenant is a core concept of the FusionInsight big data platform. It plays an imp .. 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 On a user-centered big data platform, users can directly access and use all resources and services. diff --git a/umn/source/managing_clusters/cluster_o&m/changing_the_subnet_of_a_cluster.rst b/umn/source/managing_clusters/cluster_o&m/changing_the_subnet_of_a_cluster.rst index 47ef7bc..885890f 100644 --- a/umn/source/managing_clusters/cluster_o&m/changing_the_subnet_of_a_cluster.rst +++ b/umn/source/managing_clusters/cluster_o&m/changing_the_subnet_of_a_cluster.rst @@ -47,7 +47,6 @@ Changing a Subnet When a Network ACL Is Associated .. figure:: /_static/images/en-us_image_0000001348738033.png :alt: **Figure 1** Network ACLs - **Figure 1** Network ACLs #. .. _mrs_01_24259__li1734493314818: diff --git a/umn/source/managing_clusters/cluster_o&m/importing_and_exporting_data.rst b/umn/source/managing_clusters/cluster_o&m/importing_and_exporting_data.rst index fdcf185..c51adf6 100644 --- a/umn/source/managing_clusters/cluster_o&m/importing_and_exporting_data.rst +++ b/umn/source/managing_clusters/cluster_o&m/importing_and_exporting_data.rst @@ -29,7 +29,7 @@ You can perform the following steps to import files and directories: #. Choose **Clusters > Active Clusters** and click the name of the cluster to be queried to enter the page displaying the cluster's information. -#. Clickthe **Files** tab, and go to the file management page. +#. Click the **Files** tab, and go to the file management page. #. Select **HDFS File List**. @@ -41,7 +41,7 @@ You can perform the following steps to import files and directories: - The folder name contains a maximum of 255 characters, and the full path cannot exceed 1,023 characters. - The folder name cannot be empty. - - The folder name cannot contain the following special characters: :literal:`/:*?"<>|\;&,'`!{}[]$%+` + - The folder name cannot contain the following special characters: :literal:`/:*?"<>|\\;&,'`!{}[]$%+` - The value cannot start or end with a period (.). - The spaces at the beginning and end are ignored. diff --git a/umn/source/managing_clusters/job_management/running_a_flink_job.rst b/umn/source/managing_clusters/job_management/running_a_flink_job.rst index 402b39f..3217ad2 100644 --- a/umn/source/managing_clusters/job_management/running_a_flink_job.rst +++ b/umn/source/managing_clusters/job_management/running_a_flink_job.rst @@ -206,7 +206,7 @@ In MRS 3.x and later versions, the default installation path of the client is /o security.ssl.keystore: ssl/flink.keystore security.ssl.truststore: ssl/flink.truststore - #. For MRS 3.x or earlier:Change the values of the following parameters in the **flink-conf.yaml** file to relative paths: + #. For MRS 3.x or earlier: Change the values of the following parameters in the **flink-conf.yaml** file to relative paths: .. code-block:: diff --git a/umn/source/managing_clusters/job_management/running_a_sparksql_job.rst b/umn/source/managing_clusters/job_management/running_a_sparksql_job.rst index d98d9f9..640dee5 100644 --- a/umn/source/managing_clusters/job_management/running_a_sparksql_job.rst +++ b/umn/source/managing_clusters/job_management/running_a_sparksql_job.rst @@ -211,7 +211,7 @@ In MRS 3.x and later versions, the default installation path of the client is /o #. Log in to the node where the Spark client is located, upload the user authentication credential created in :ref:`2 ` to the **/opt** directory of the cluster, and run the following command to decompress the package: - **tar –xvf MRSTest \_**\ *xxxxxx*\ **\_keytab.tar** + **tar -xvf MRSTest \_**\ *xxxxxx*\ **\_keytab.tar** After the decompression, you obtain the **user.keytab** and **krb5.conf** files. diff --git a/umn/source/managing_clusters/job_management/running_a_sparksubmit_job.rst b/umn/source/managing_clusters/job_management/running_a_sparksubmit_job.rst index 68c3c73..6aecd06 100644 --- a/umn/source/managing_clusters/job_management/running_a_sparksubmit_job.rst +++ b/umn/source/managing_clusters/job_management/running_a_sparksubmit_job.rst @@ -217,7 +217,7 @@ In MRS 3.x and later versions, the default installation path of the client is /o #. Upload the authentication credential of the user created in :ref:`2 ` to the **/opt** directory of the cluster and run the following command to decompress the credential: - **tar –xvf MRSTest \_\ xxxxxx\ \_keytab.tar** + **tar -xvf MRSTest \_\ xxxxxx\ \_keytab.tar** You will obtain two files: **user.keytab** and **krb5.conf**. diff --git a/umn/source/managing_clusters/logging_in_to_a_cluster/logging_in_to_an_ecs.rst b/umn/source/managing_clusters/logging_in_to_a_cluster/logging_in_to_an_ecs.rst index cd959ba..3a3fc1a 100644 --- a/umn/source/managing_clusters/logging_in_to_a_cluster/logging_in_to_an_ecs.rst +++ b/umn/source/managing_clusters/logging_in_to_a_cluster/logging_in_to_an_ecs.rst @@ -51,7 +51,7 @@ To log in to the Linux ECS from local Windows, perform the operations described #. In the **Actions** area, click **Load** and import the private key file you used during ECS creation. - Ensure that the private key file is in the format of **All files (``*``.\ ``*``)**. + Ensure that the private key file is in the format of **All files (*.*)**. #. Click **Save private key**. @@ -85,7 +85,6 @@ To log in to the Linux ECS from local Windows, perform the operations described .. figure:: /_static/images/en-us_image_0000001295898104.png :alt: **Figure 1** Clicking **Session** - **Figure 1** Clicking **Session** #. Click **Open** to log in to the ECS. diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst index 8be3c3c..4be22fe 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12018_memory_usage_exceeds_the_threshold.rst @@ -53,7 +53,7 @@ Procedure a. Go to the MRS cluster details page. In the alarm list on the alarm management tab page, click the row that contains the alarm. In the alarm details, view the host address of the alarm. b. Log in to the node for which the alarm is generated. - c. Run **free -m \| grep Mem\: \| awk '{printf("%s,", ($3-$6-$7) \* 100 / $2)}'** to check the system memory usage. + c. Run **free -m \| grep Mem\\: \| awk '{printf("%s,", ($3-$6-$7) \* 100 / $2)}'** to check the system memory usage. d. If the memory usage exceeds the threshold, expand the memory capacity. e. Wait 5 minutes and check whether the alarm is cleared. diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_on_the_host_exceeds_the_threshold.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_on_the_host_exceeds_the_threshold.rst index 454c778..1948ce8 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_on_the_host_exceeds_the_threshold.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12028_number_of_processes_in_the_d_state_on_the_host_exceeds_the_threshold.rst @@ -63,7 +63,7 @@ The host responds slowly to I/O (disk I/O and network I/O) requests and a proces d. 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 D \| awk '{print $2}'** + **ps -elf \| grep -v "\\[thread_checkio\\]" \| awk 'NR!=1 {print $2, $3, $4}' \| grep omm \| awk -F' ' '{print $1, $3}' \| grep D \| awk '{print $2}'** e. Check whether the command output is empty. diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12040_insufficient_system_entropy.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12040_insufficient_system_entropy.rst index 6871243..8c53f2b 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12040_insufficient_system_entropy.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/alarm_reference_applicable_to_versions_earlier_than_mrs_3.x/alm-12040_insufficient_system_entropy.rst @@ -51,7 +51,7 @@ Procedure #. Log in to the node for which the alarm is generated and run the **sudo su - root** command to switch to user **root**. -#. Run the **/bin/rpm -qa \| grep -w "rng-tools"** command. If the command is executed successfully, run the **ps -ef \| grep -v "grep" \| grep rngd \| tr -d " " \| grep "\-o/dev/random" \| grep "\-r/dev/urandom"** command and view the command output. +#. Run the **/bin/rpm -qa \| grep -w "rng-tools"** command. If the command is executed successfully, run the **ps -ef \| grep -v "grep" \| grep rngd \| tr -d " " \| grep "\\-o/dev/random" \| grep "\\-r/dev/urandom"** command and view the command output. - If the command is executed successfully, the rngd service is installed, correctly configured, and is running properly. Go to :ref:`8 `. - If the command is not executed successfully, the rngd service is not running properly. Then go to :ref:`5 `. diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/deleting_a_user.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/deleting_a_user.rst index 1b587c6..912ba60 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/deleting_a_user.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/deleting_a_user.rst @@ -36,7 +36,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001349058005.png :alt: **Figure 1** Deleting a user - **Figure 1** Deleting a user #. Click **OK**. diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/modifying_a_password_policy.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/modifying_a_password_policy.rst index 29a3fd1..e494387 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/modifying_a_password_policy.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/modifying_a_password_policy.rst @@ -42,7 +42,7 @@ Procedure +==============================================================+================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ | **Minimum Password Length** | Indicates the minimum number of characters a password contains. The value ranges from 8 to 32. The default value is **8**. | +--------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | **Number of Character Types** | Indicates the minimum number of character types a password contains. The character types include uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\=`). The value can be **3** or **4**. The default value **3** indicates that the password must contain at least three types of the following characters: uppercase letters, lowercase letters, digits, special characters, and spaces. | + | **Number of Character Types** | Indicates the minimum number of character types a password contains. The character types include uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\\=`). The value can be **3** or **4**. The default value **3** indicates that the password must contain at least three types of the following characters: uppercase letters, lowercase letters, digits, special characters, and spaces. | +--------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | **Password Validity Period (days)** | Indicates the validity period (days) of a password. The value ranges from 0 to 90. Value **0** means that the password is permanently valid. The default value is **90**. | +--------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/users_and_permissions_of_mrs_clusters.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/users_and_permissions_of_mrs_clusters.rst index f93d259..c6e0864 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/users_and_permissions_of_mrs_clusters.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/mrs_multi-user_permission_management/users_and_permissions_of_mrs_clusters.rst @@ -156,5 +156,4 @@ In practice, MRS cluster users must understand the service scenarios of big data .. figure:: /_static/images/en-us_image_0000001349057881.png :alt: **Figure 1** Process of creating a user - **Figure 1** Process of creating a user diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/permissions_management/modifying_a_password_policy.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/permissions_management/modifying_a_password_policy.rst index 40d7345..bc23940 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/permissions_management/modifying_a_password_policy.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/permissions_management/modifying_a_password_policy.rst @@ -30,7 +30,7 @@ Procedure +==============================================================+==============================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ | **Minimum Password Length** | Indicates the minimum number of characters a password contains. The value ranges from 8 to 32. The default value is **8**. | +--------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | **Number of Character Types** | Indicates the minimum number of character types a password contains. The character types are uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\=`). The value can be **3** or **4**. The default value **3** indicates that the password must contain at least three types of the following characters: uppercase letters, lowercase letters, digits, special characters, and spaces. | + | **Number of Character Types** | Indicates the minimum number of character types a password contains. The character types are uppercase letters, lowercase letters, digits, spaces, and special characters (:literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\\=`). The value can be **3** or **4**. The default value **3** indicates that the password must contain at least three types of the following characters: uppercase letters, lowercase letters, digits, special characters, and spaces. | +--------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | **Password Validity Period (days)** | Indicates the validity period (days) of a password. The value ranges from 0 to 90. 0 means that the password is permanently valid. The default value is **90**. | +--------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/changing_the_passwords_of_the_ldap_administrator_and_the_ldap_user.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/changing_the_passwords_of_the_ldap_administrator_and_the_ldap_user.rst index 4429bdf..b2b0c1f 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/changing_the_passwords_of_the_ldap_administrator_and_the_ldap_user.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/changing_the_passwords_of_the_ldap_administrator_and_the_ldap_user.rst @@ -29,7 +29,7 @@ Procedure The default password complexity requirements are as follows: - The password contains 16 to 32 characters. - - The password must contain at least three types of the following: uppercase letters, lowercase letters, digits, and special characters (:literal:`\`~!@#$%^&*()-_=+\|[{}];:",<.>/?`). + - The password must contain at least three types of the following: uppercase letters, lowercase letters, digits, and special characters (:literal:`\`~!@#$%^&*()-_=+\\|[{}];:",<.>/?`). - The password cannot be the username or the reverse username. - The new password cannot be the same as the current password. diff --git a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/replacing_the_ha_certificate.rst b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/replacing_the_ha_certificate.rst index 331dc7d..a5f73fa 100644 --- a/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/replacing_the_ha_certificate.rst +++ b/umn/source/mrs_manager_operation_guide_applicable_to_2.x_and_earlier_versions/security_management/replacing_the_ha_certificate.rst @@ -27,7 +27,7 @@ Prerequisites To avoid potential security risks, the password must meet the following complexity requirements: - The password must contain at least eight characters. - - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, and special characters (:literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\=`). + - The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, and special characters (:literal:`~`!?,.:;-_'(){}[]/<>@#$%^&*+|\\=`). Procedure --------- diff --git a/umn/source/mrs_quick_start/uploading_data_and_programs.rst b/umn/source/mrs_quick_start/uploading_data_and_programs.rst index b3eb74f..230d34a 100644 --- a/umn/source/mrs_quick_start/uploading_data_and_programs.rst +++ b/umn/source/mrs_quick_start/uploading_data_and_programs.rst @@ -23,7 +23,7 @@ You can perform the following steps to import files and directories: #. Choose **Clusters > Active Clusters** and click the name of the cluster to be queried to enter the page displaying the cluster's information. -#. Clickthe **Files** tab to go to the file management page. +#. Click the **Files** tab to go to the file management page. #. Select **HDFS File List**. @@ -35,7 +35,7 @@ You can perform the following steps to import files and directories: - The folder name contains a maximum of 255 characters. The full path cannot exceed 1,023 characters. - The folder name cannot be empty. - - The folder name cannot contain the following special characters: :literal:`/:*?"<>|\;&,'`!{}[]$%+` + - The folder name cannot contain the following special characters: :literal:`/:*?"<>|\\;&,'`!{}[]$%+` - The value cannot start or end with a period (.). - The spaces at the beginning and end are ignored. diff --git a/umn/source/mrs_quick_start/using_clusters_with_kerberos_authentication_enabled.rst b/umn/source/mrs_quick_start/using_clusters_with_kerberos_authentication_enabled.rst index 2d453b0..4d63e01 100644 --- a/umn/source/mrs_quick_start/using_clusters_with_kerberos_authentication_enabled.rst +++ b/umn/source/mrs_quick_start/using_clusters_with_kerberos_authentication_enabled.rst @@ -208,5 +208,4 @@ You have compiled the program and prepared data files, for example, **mapreduce- .. figure:: /_static/images/en-us_image_0000001296058144.png :alt: **Figure 1** Program running result - **Figure 1** Program running result diff --git a/umn/source/overview/application_scenarios.rst b/umn/source/overview/application_scenarios.rst index 8f17472..c8a318a 100644 --- a/umn/source/overview/application_scenarios.rst +++ b/umn/source/overview/application_scenarios.rst @@ -23,7 +23,6 @@ In the environmental protection industry, climate data is stored on OBS and peri .. figure:: /_static/images/en-us_image_0000001349190341.png :alt: **Figure 1** Large-scale data analysis in the environmental protection industry - **Figure 1** Large-scale data analysis in the environmental protection industry MRS has the following advantages in this scenario. @@ -43,7 +42,6 @@ For example, in the IoV industry, an automobile company stores data on HBase, wh .. figure:: /_static/images/en-us_image_0000001296750238.png :alt: **Figure 2** Large-scale data storage in the IoV industry - **Figure 2** Large-scale data storage in the IoV industry MRS has the following advantages in this scenario. @@ -63,7 +61,6 @@ For example, in the Internet of elevators & escalators (IoEE) industry, data of .. figure:: /_static/images/en-us_image_0000001349390633.png :alt: **Figure 3** Low-latency streaming processing in the IoEE industry - **Figure 3** Low-latency streaming processing in the IoEE industry MRS has the following advantages in this scenario. diff --git a/umn/source/overview/components/alluxio.rst b/umn/source/overview/components/alluxio.rst index 8ceaf54..2fa35e8 100644 --- a/umn/source/overview/components/alluxio.rst +++ b/umn/source/overview/components/alluxio.rst @@ -11,7 +11,6 @@ Alluxio is data orchestration technology for analytics and AI for the cloud. In .. figure:: /_static/images/en-us_image_0000001296430738.png :alt: **Figure 1** Alluxio architecture - **Figure 1** Alluxio architecture Advantages: diff --git a/umn/source/overview/components/carbondata.rst b/umn/source/overview/components/carbondata.rst index 8854286..ba04758 100644 --- a/umn/source/overview/components/carbondata.rst +++ b/umn/source/overview/components/carbondata.rst @@ -11,7 +11,6 @@ CarbonData is a new Apache Hadoop native data-store format. CarbonData allows fa .. figure:: /_static/images/en-us_image_0000001349110485.png :alt: **Figure 1** Basic architecture of CarbonData - **Figure 1** Basic architecture of CarbonData The purpose of using CarbonData is to provide quick response to ad hoc queries of big data. Essentially, CarbonData is an Online Analytical Processing (OLAP) engine, which stores data using tables similar to those in Relational Database Management System (RDBMS). You can import more than 10 TB data to tables created in CarbonData format, and CarbonData automatically organizes and stores data using the compressed multi-dimensional indexes. After data is loaded to CarbonData, CarbonData responds to ad hoc queries in seconds. diff --git a/umn/source/overview/components/clickhouse.rst b/umn/source/overview/components/clickhouse.rst index 2418b45..e554d70 100644 --- a/umn/source/overview/components/clickhouse.rst +++ b/umn/source/overview/components/clickhouse.rst @@ -95,7 +95,6 @@ MRS ClickHouse has advantages such as automatic cluster mode, HA deployment, and .. figure:: /_static/images/en-us_image_0000001349110441.png :alt: **Figure 1** ClickHouse cluster - **Figure 1** ClickHouse cluster Users are unaware of data partitions and replica storage in common database systems. However, ClickHouse allows you to proactively plan and define detailed configurations such as shards, partitions, and replica locations. The ClickHouse instance of MRS packs the work in a unified manner and adapts it to the automatic mode, implementing unified management, which is flexible and easy to use. A ClickHouse instance consists of three ZooKeeper nodes and multiple ClickHouse nodes. The Dedicated Replica mode is used to ensure high reliability of dual data copies. @@ -104,7 +103,6 @@ MRS ClickHouse has advantages such as automatic cluster mode, HA deployment, and .. figure:: /_static/images/en-us_image_0000001349390609.png :alt: **Figure 2** ClickHouse cluster structure - **Figure 2** ClickHouse cluster structure - Smooth and Elastic Scaling @@ -126,7 +124,6 @@ MRS ClickHouse has advantages such as automatic cluster mode, HA deployment, and .. figure:: /_static/images/en-us_image_0000001296590598.png :alt: **Figure 3** HA deployment architecture - **Figure 3** HA deployment architecture .. |image1| image:: /_static/images/en-us_image_0000001296270774.png diff --git a/umn/source/overview/components/dbservice/dbservice_basic_principles.rst b/umn/source/overview/components/dbservice/dbservice_basic_principles.rst index d8ecee5..181a1e9 100644 --- a/umn/source/overview/components/dbservice/dbservice_basic_principles.rst +++ b/umn/source/overview/components/dbservice/dbservice_basic_principles.rst @@ -24,7 +24,6 @@ DBService in the cluster works in active/standby mode. Two DBServer instances ar .. figure:: /_static/images/en-us_image_0000001349390605.png :alt: **Figure 1** DBService architecture - **Figure 1** DBService architecture :ref:`Table 1 ` describes the modules shown in :ref:`Figure 1 ` diff --git a/umn/source/overview/components/flink/flink_basic_principles.rst b/umn/source/overview/components/flink/flink_basic_principles.rst index 50a8f34..6e35177 100644 --- a/umn/source/overview/components/flink/flink_basic_principles.rst +++ b/umn/source/overview/components/flink/flink_basic_principles.rst @@ -19,7 +19,6 @@ Flink provides high-concurrency pipeline data processing, millisecond-level late .. figure:: /_static/images/en-us_image_0000001296750242.png :alt: **Figure 1** Technology stack of Flink - **Figure 1** Technology stack of Flink Flink provides the following features in the current version: @@ -42,7 +41,6 @@ Flink Architecture .. figure:: /_static/images/en-us_image_0000001349390641.png :alt: **Figure 2** Flink architecture - **Figure 2** Flink architecture As shown in the above figure, the entire Flink system consists of three parts: @@ -77,7 +75,6 @@ Flink Principles .. figure:: /_static/images/en-us_image_0000001296590630.png :alt: **Figure 3** Example of Flink DataStream - **Figure 3** Example of Flink DataStream As shown in :ref:`Figure 3 `, **FlinkKafkaConsumer** is a source operator; Map, KeyBy, TimeWindow, and Apply are transformation operators; RollingSink is a sink operator. @@ -95,7 +92,6 @@ Flink Principles .. figure:: /_static/images/en-us_image_0000001296750246.png :alt: **Figure 4** Operator - **Figure 4** Operator - Operators with high density can be optimized. Flink chains operator subtasks together into a task, that is, an operator chain. Each operator chain is executed by one thread on TaskManager, as shown in :ref:`Figure 5 `. @@ -105,7 +101,6 @@ Flink Principles .. figure:: /_static/images/en-us_image_0000001296430770.png :alt: **Figure 5** Operator chain - **Figure 5** Operator chain - In the upper part of :ref:`Figure 5 `, the condensed Source and Map operators are chained into an Operator Chain, that is, a larger operator. The Operator Chain, KeyBy, and Sink all represent an operator respectively and are connected with each other through streams. Each operator corresponds to one task during the running. Namely, there are three tasks in the upper part. diff --git a/umn/source/overview/components/flink/flink_enhanced_open_source_features/job_pipeline.rst b/umn/source/overview/components/flink/flink_enhanced_open_source_features/job_pipeline.rst index 917a3ec..20bb877 100644 --- a/umn/source/overview/components/flink/flink_enhanced_open_source_features/job_pipeline.rst +++ b/umn/source/overview/components/flink/flink_enhanced_open_source_features/job_pipeline.rst @@ -27,7 +27,6 @@ A pipeline consists of multiple Flink jobs connected through TCP. Upstream jobs .. figure:: /_static/images/en-us_image_0000001349390637.png :alt: **Figure 1** Job pipeline - **Figure 1** Job pipeline **Job Pipeline Principles** @@ -36,7 +35,6 @@ A pipeline consists of multiple Flink jobs connected through TCP. Upstream jobs .. figure:: /_static/images/en-us_image_0000001349110473.png :alt: **Figure 2** Job pipeline principles - **Figure 2** Job pipeline principles - NettySink and NettySource @@ -189,5 +187,4 @@ The relationship between the jobs may be many-to-many. The concurrency between e .. figure:: /_static/images/en-us_image_0000001349190345.png :alt: **Figure 3** Relationship diagram - **Figure 3** Relationship diagram diff --git a/umn/source/overview/components/flink/flink_enhanced_open_source_features/window.rst b/umn/source/overview/components/flink/flink_enhanced_open_source_features/window.rst index a553b5d..8d7fa67 100644 --- a/umn/source/overview/components/flink/flink_enhanced_open_source_features/window.rst +++ b/umn/source/overview/components/flink/flink_enhanced_open_source_features/window.rst @@ -26,7 +26,6 @@ If a block of data arrives, it is assigned to four different windows (20/5 = 4). .. figure:: /_static/images/en-us_image_0000001349390625.png :alt: **Figure 1** Original structure of a window - **Figure 1** Original structure of a window If a data block arrives at the 102nd second, it is assigned to windows [85, 105), [90, 110), [95, 115), and [100, 120). @@ -43,7 +42,6 @@ As mentioned in the preceding, there are excessive data copies when original dat .. figure:: /_static/images/en-us_image_0000001296430762.png :alt: **Figure 2** Window optimization - **Figure 2** Window optimization #. When a data block arrives, it is not assigned to a specific window. Instead, Flink determines the pane to which the data block belongs based on the timestamp of the data block, and saves the data block into the pane. @@ -54,7 +52,6 @@ As mentioned in the preceding, there are excessive data copies when original dat .. figure:: /_static/images/en-us_image_0000001296590610.png :alt: **Figure 3** Saving data in a window - **Figure 3** Saving data in a window #. To trigger a window, compute all panes contained in the window, and combine all these panes into a complete window. @@ -63,7 +60,6 @@ As mentioned in the preceding, there are excessive data copies when original dat .. figure:: /_static/images/en-us_image_0000001349110457.png :alt: **Figure 4** Triggering a window - **Figure 4** Triggering a window #. If a pane is not required, you can delete it from the memory. @@ -72,7 +68,6 @@ As mentioned in the preceding, there are excessive data copies when original dat .. figure:: /_static/images/en-us_image_0000001349309913.png :alt: **Figure 5** Deleting a window - **Figure 5** Deleting a window After optimization, the quantity of data copies in the memory and snapshot is greatly reduced. diff --git a/umn/source/overview/components/flink/flink_ha_solution.rst b/umn/source/overview/components/flink/flink_ha_solution.rst index 3e90c91..2a6fbcb 100644 --- a/umn/source/overview/components/flink/flink_ha_solution.rst +++ b/umn/source/overview/components/flink/flink_ha_solution.rst @@ -36,7 +36,6 @@ In the standalone mode, multiple JobManagers can be started and ZooKeeper elects .. figure:: /_static/images/en-us_image_0000001296270790.png :alt: **Figure 1** Switchover process - **Figure 1** Switchover process **Restoring TaskManager** diff --git a/umn/source/overview/components/flink/relationship_with_other_components.rst b/umn/source/overview/components/flink/relationship_with_other_components.rst index fc4f64d..f1cb39a 100644 --- a/umn/source/overview/components/flink/relationship_with_other_components.rst +++ b/umn/source/overview/components/flink/relationship_with_other_components.rst @@ -17,7 +17,6 @@ Flink supports Yarn-based cluster management mode. In this mode, Flink serves as .. figure:: /_static/images/en-us_image_0000001349390773.png :alt: **Figure 1** Flink interaction with Yarn - **Figure 1** Flink interaction with Yarn #. The Flink YARN Client first checks whether there are sufficient resources for starting the Yarn cluster. If yes, the Flink Yarn client uploads JAR packages and configuration files to HDFS. diff --git a/umn/source/overview/components/flume/flume_basic_principles.rst b/umn/source/overview/components/flume/flume_basic_principles.rst index a79f9d3..5c1e3cf 100644 --- a/umn/source/overview/components/flume/flume_basic_principles.rst +++ b/umn/source/overview/components/flume/flume_basic_principles.rst @@ -11,7 +11,6 @@ Flume Basic Principles .. figure:: /_static/images/en-us_image_0000001296590606.png :alt: **Figure 1** Flume-NG architecture - **Figure 1** Flume-NG architecture A Flume-NG consists of agents. Each agent consists of three components (source, channel, and sink). A source is used for receiving data. A channel is used for transmitting data. A sink is used for sending data to the next end. @@ -59,7 +58,6 @@ As shown in :ref:`Figure 2 `, a Flume client ca .. figure:: /_static/images/en-us_image_0000001349390617.png :alt: **Figure 2** Flume structure - **Figure 2** Flume structure The reliability of Flume depends on transaction switchovers between agents. If the next agent breaks down, the channel stores data persistently and transmits data until the agent recovers. The availability of Flume depends on the built-in load balancing and failover mechanisms. Both the channel and agent can be configured with multiple entities between which they can use load balancing policies. Each agent is a Java Virtual Machine (JVM) process. A server can have multiple agents. Collection nodes (for example, Agents 1, 2, 3) process logs. Aggregation nodes (for example, Agent 4) write the logs into HDFS. The agent of each collection node can select multiple aggregation nodes for load balancing. @@ -68,7 +66,6 @@ The reliability of Flume depends on transaction switchovers between agents. If t .. figure:: /_static/images/en-us_image_0000001296270782.png :alt: **Figure 3** Flume cascading - **Figure 3** Flume cascading For details about Flume architecture and principles, see https://flume.apache.org/releases/1.9.0.html. @@ -85,7 +82,6 @@ Principle .. figure:: /_static/images/en-us_image_0000001296430750.png :alt: **Figure 4** Data transmission process - **Figure 4** Data transmission process #. Flume ensures reliable data transmission based on transactions. When data flows from one agent to another agent, the two transactions take effect. The sink of Agent 1 (agent that sends a message) needs to obtain a message from a channel and sends the message to Agent 2 (agent that receives the message). If Agent 2 receives and successfully processes the message, Agent 1 will submit a transaction, indicating a successful and reliable data transmission. diff --git a/umn/source/overview/components/hbase/hbase_basic_principles.rst b/umn/source/overview/components/hbase/hbase_basic_principles.rst index 8607e30..227162b 100644 --- a/umn/source/overview/components/hbase/hbase_basic_principles.rst +++ b/umn/source/overview/components/hbase/hbase_basic_principles.rst @@ -25,7 +25,6 @@ An HBase cluster consists of active and standby HMaster processes and multiple R .. figure:: /_static/images/en-us_image_0000001296590642.png :alt: **Figure 1** HBase architecture - **Figure 1** HBase architecture .. table:: **Table 1** Module description @@ -63,7 +62,6 @@ HBase Principles .. figure:: /_static/images/en-us_image_0000001296270818.png :alt: **Figure 2** HBase data model - **Figure 2** HBase data model .. table:: **Table 2** Concepts @@ -91,7 +89,6 @@ HBase Principles .. figure:: /_static/images/en-us_image_0000001349190357.png :alt: **Figure 3** RegionServer data storage structure - **Figure 3** RegionServer data storage structure :ref:`Table 3 ` lists each component of Region described in :ref:`Figure 3 `. @@ -125,7 +122,6 @@ HBase Principles .. figure:: /_static/images/en-us_image_0000001349309941.png :alt: **Figure 4** Mapping relationships between metadata tables and user tables - **Figure 4** Mapping relationships between metadata tables and user tables - **Data Operation Process** @@ -137,7 +133,6 @@ HBase Principles .. figure:: /_static/images/en-us_image_0000001296430786.png :alt: **Figure 5** Data processing - **Figure 5** Data processing #. When you add, delete, modify, and query HBase data, the HBase client first connects to ZooKeeper to obtain information about the RegionServer where the **hbase:meta** table is located. If you modify the namespace, such as creating and deleting a table, you need to access HMaster to update the meta information. diff --git a/umn/source/overview/components/hbase/hbase_enhanced_open_source_features.rst b/umn/source/overview/components/hbase/hbase_enhanced_open_source_features.rst index 1dc94aa..8d53445 100644 --- a/umn/source/overview/components/hbase/hbase_enhanced_open_source_features.rst +++ b/umn/source/overview/components/hbase/hbase_enhanced_open_source_features.rst @@ -18,7 +18,6 @@ HBase HIndex is designed to address these issues. HBase HIndex enables HBase to .. figure:: /_static/images/en-us_image_0000001349110477.png :alt: **Figure 1** HIndex - **Figure 1** HIndex - Rolling upgrade is not supported for index data. @@ -181,7 +180,6 @@ To achieve better performance when regions are divided based on user requirement .. figure:: /_static/images/en-us_image_0000001296270810.png :alt: **Figure 2** Multi-point division - **Figure 2** Multi-point division Connection Limitation @@ -213,7 +211,6 @@ As shown in :ref:`Figure 3 `, M .. figure:: /_static/images/en-us_image_0000001296590634.png :alt: **Figure 3** MOB data storage principle - **Figure 3** MOB data storage principle HFS @@ -251,7 +248,6 @@ The HBase resource utilization can be improved when multiple RegionServers are d .. figure:: /_static/images/en-us_image_0000001349190349.png :alt: **Figure 4** Improved HBase resource utilization - **Figure 4** Improved HBase resource utilization HBase Dual-Read diff --git a/umn/source/overview/components/hbase/hbase_ha_solution.rst b/umn/source/overview/components/hbase/hbase_ha_solution.rst index e733e7d..c673cbe 100644 --- a/umn/source/overview/components/hbase/hbase_ha_solution.rst +++ b/umn/source/overview/components/hbase/hbase_ha_solution.rst @@ -14,7 +14,6 @@ HMaster in HBase allocates Regions. When one RegionServer service is stopped, HM .. figure:: /_static/images/en-us_image_0000001349190369.png :alt: **Figure 1** HMaster HA implementation architecture - **Figure 1** HMaster HA implementation architecture The HMaster HA architecture is implemented by creating the ephemeral ZooKeeper node in a ZooKeeper cluster. diff --git a/umn/source/overview/components/hbase/relationship_with_other_components.rst b/umn/source/overview/components/hbase/relationship_with_other_components.rst index 2e7d872..10a9a13 100644 --- a/umn/source/overview/components/hbase/relationship_with_other_components.rst +++ b/umn/source/overview/components/hbase/relationship_with_other_components.rst @@ -20,7 +20,6 @@ Relationship Between ZooKeeper and HBase .. figure:: /_static/images/en-us_image_0000001349110589.png :alt: **Figure 1** Relationship between ZooKeeper and HBase - **Figure 1** Relationship between ZooKeeper and HBase #. HRegionServer registers itself to ZooKeeper in Ephemeral node. ZooKeeper stores the HBase information, including the HBase metadata and HMaster addresses. diff --git a/umn/source/overview/components/hdfs/hdfs_basic_principles.rst b/umn/source/overview/components/hdfs/hdfs_basic_principles.rst index 842a696..41cd298 100644 --- a/umn/source/overview/components/hdfs/hdfs_basic_principles.rst +++ b/umn/source/overview/components/hdfs/hdfs_basic_principles.rst @@ -21,7 +21,6 @@ The communication between NameNodes and DataNodes is based on Transmission Contr .. figure:: /_static/images/en-us_image_0000001349110533.png :alt: **Figure 1** HA HDFS architecture - **Figure 1** HA HDFS architecture :ref:`Table 1 ` describes the functions of each module shown in :ref:`Figure 1 `. @@ -67,7 +66,6 @@ The communication between NameNodes and DataNodes is based on Transmission Contr .. figure:: /_static/images/en-us_image_0000001296590686.png :alt: **Figure 2** QJM-based HDFS architecture - **Figure 2** QJM-based HDFS architecture Principle @@ -82,7 +80,6 @@ MRS uses the HDFS copy mechanism to ensure data reliability. One backup file is .. figure:: /_static/images/en-us_image_0000001296430834.png :alt: **Figure 3** HDFS architecture - **Figure 3** HDFS architecture The HDFS component of MRS supports the following features: diff --git a/umn/source/overview/components/hdfs/hdfs_enhanced_open_source_features.rst b/umn/source/overview/components/hdfs/hdfs_enhanced_open_source_features.rst index f37e493..a4b1a3c 100644 --- a/umn/source/overview/components/hdfs/hdfs_enhanced_open_source_features.rst +++ b/umn/source/overview/components/hdfs/hdfs_enhanced_open_source_features.rst @@ -21,7 +21,6 @@ In the offline data summary and statistics scenario, Join is a frequently used c .. figure:: /_static/images/en-us_image_0000001296270802.png :alt: **Figure 1** Data transmission in the non-colocation scenario - **Figure 1** Data transmission in the non-colocation scenario Data tables are stored in physical file system by HDFS block. Therefore, if two to-be-joined blocks are put into the same host accordingly after they are partitioned by join key, you can obtain the results directly from Map join in the local node without any data transfer in the Reduce process of the join calculation. This will greatly improve the performance. @@ -32,7 +31,6 @@ With the identical distribution feature of HDFS data, a same distribution ID is .. figure:: /_static/images/en-us_image_0000001296270806.png :alt: **Figure 2** Data block distribution in colocation and non-colocation scenarios - **Figure 2** Data block distribution in colocation and non-colocation scenarios Enhanced Open Source Feature: Damaged Hard Disk Volume Configuration @@ -47,7 +45,6 @@ The value of **dfs.datanode.failed.volumes.tolerated** ranges from -1 to the num .. figure:: /_static/images/en-us_image_0000001296590626.png :alt: **Figure 3** Item being set to 0 - **Figure 3** Item being set to 0 For example, three data storage volumes are mounted to a DataNode, and **dfs.datanode.failed.volumes.tolerated** is set to 1. In this case, if one data storage volume of the DataNode is unavailable, this DataNode can still provide services, as shown in :ref:`Figure 4 `. @@ -57,7 +54,6 @@ For example, three data storage volumes are mounted to a DataNode, and **dfs.dat .. figure:: /_static/images/en-us_image_0000001349110469.png :alt: **Figure 4** Item being set to 1 - **Figure 4** Item being set to 1 This native configuration item has some defects. When the number of data storage volumes in each DataNode is inconsistent, you need to configure each DataNode independently instead of generating the unified configuration file for all nodes. @@ -69,7 +65,6 @@ Assume that there are three DataNodes in a cluster. The first node has three dat .. figure:: /_static/images/en-us_image_0000001296430774.jpg :alt: **Figure 5** Attribute configuration before being enhanced - **Figure 5** Attribute configuration before being enhanced In self-developed enhanced HDFS, this configuration item is enhanced, with a value **-1** added. When this configuration item is set to **-1**, all DataNodes can provide services as long as one data storage volume in all DataNodes is available. @@ -81,7 +76,6 @@ To resolve the problem in the preceding example, set this configuration to **-1* .. figure:: /_static/images/en-us_image_0000001349190337.jpg :alt: **Figure 6** Attribute configuration after being enhanced - **Figure 6** Attribute configuration after being enhanced Enhanced Open Source Feature: HDFS Startup Acceleration @@ -111,7 +105,6 @@ You need to configure the nodes for storing HDFS file data blocks based on data .. figure:: /_static/images/en-us_image_0000001296590622.png :alt: **Figure 7** Example of label-based block placement policy - **Figure 7** Example of label-based block placement policy Enhanced Open Source Feature: HDFS Load Balance diff --git a/umn/source/overview/components/hdfs/hdfs_ha_solution.rst b/umn/source/overview/components/hdfs/hdfs_ha_solution.rst index 1e201ac..609219f 100644 --- a/umn/source/overview/components/hdfs/hdfs_ha_solution.rst +++ b/umn/source/overview/components/hdfs/hdfs_ha_solution.rst @@ -23,7 +23,6 @@ HDFS HA Implementation .. figure:: /_static/images/en-us_image_0000001349110445.jpg :alt: **Figure 1** Typical HA deployment - **Figure 1** Typical HA deployment In a typical HA cluster (as shown in :ref:`Figure 1 `), two NameNodes need to be configured on two independent servers, respectively. At any time point, one NameNode is in the active state, and the other NameNode is in the standby state. The active NameNode is responsible for all client operations in the cluster, while the standby NameNode maintains synchronization with the active node to provide fast switchover if necessary. diff --git a/umn/source/overview/components/hdfs/relationship_between_hdfs_and_other_components.rst b/umn/source/overview/components/hdfs/relationship_between_hdfs_and_other_components.rst index 61b972c..4b9d8cd 100644 --- a/umn/source/overview/components/hdfs/relationship_between_hdfs_and_other_components.rst +++ b/umn/source/overview/components/hdfs/relationship_between_hdfs_and_other_components.rst @@ -30,7 +30,6 @@ Spark involves Driver and Executor. Driver schedules tasks and Executor runs tas .. figure:: /_static/images/en-us_image_0000001349390697.png :alt: **Figure 1** File reading process - **Figure 1** File reading process The file reading process is as follows: @@ -47,7 +46,6 @@ The file reading process is as follows: .. figure:: /_static/images/en-us_image_0000001296270866.png :alt: **Figure 2** File writing process - **Figure 2** File writing process The file writing process is as follows: @@ -70,7 +68,6 @@ Relationship Between HDFS and ZooKeeper .. figure:: /_static/images/en-us_image_0000001349309985.png :alt: **Figure 3** Relationship between ZooKeeper and HDFS - **Figure 3** Relationship between ZooKeeper and HDFS As the client of a ZooKeeper cluster, ZKFailoverController (ZKFC) monitors the status of NameNode. ZKFC is deployed only in the node where NameNode resides, and in both the active and standby HDFS NameNodes. diff --git a/umn/source/overview/components/hetuengine/hetuengine_product_overview.rst b/umn/source/overview/components/hetuengine/hetuengine_product_overview.rst index 17af800..1c6785b 100644 --- a/umn/source/overview/components/hetuengine/hetuengine_product_overview.rst +++ b/umn/source/overview/components/hetuengine/hetuengine_product_overview.rst @@ -22,7 +22,6 @@ HetuEngine consists of different modules. :ref:`Figure 1 ` shows the join process when the CBO is enabled. @@ -116,7 +113,6 @@ As shown in the preceding table, the **item** table has a better filtering effec .. figure:: /_static/images/en-us_image_0000001349190397.png :alt: **Figure 4** Join process when the CBO is enabled - **Figure 4** Join process when the CBO is enabled After the CBO is enabled, the number of intermediate data entries is reduced from 495,000,000 to 2,900,000 and thus the execution time can be remarkably reduced. diff --git a/umn/source/overview/components/hudi.rst b/umn/source/overview/components/hudi.rst index 4d59517..df90ece 100644 --- a/umn/source/overview/components/hudi.rst +++ b/umn/source/overview/components/hudi.rst @@ -15,7 +15,6 @@ Hudi is the file organization layer of the data lake. It manages Parquet files, .. figure:: /_static/images/en-us_image_0000001349190321.png :alt: **Figure 1** Basic architecture of Hudi - **Figure 1** Basic architecture of Hudi Feature diff --git a/umn/source/overview/components/hue/hue_basic_principles.rst b/umn/source/overview/components/hue/hue_basic_principles.rst index 63a7d90..113dcb6 100644 --- a/umn/source/overview/components/hue/hue_basic_principles.rst +++ b/umn/source/overview/components/hue/hue_basic_principles.rst @@ -51,7 +51,6 @@ Hue consists of Supervisor Process and WebServer. Supervisor Process is the core .. figure:: /_static/images/en-us_image_0000001296750298.png :alt: **Figure 1** Hue architecture - **Figure 1** Hue architecture :ref:`Table 1 ` describes the components shown in :ref:`Figure 1 `. diff --git a/umn/source/overview/components/kafka/kafka_basic_principles.rst b/umn/source/overview/components/kafka/kafka_basic_principles.rst index 8be98e2..b8b52b7 100644 --- a/umn/source/overview/components/kafka/kafka_basic_principles.rst +++ b/umn/source/overview/components/kafka/kafka_basic_principles.rst @@ -16,7 +16,6 @@ Producers publish data to topics, and consumers subscribe to the topics and cons .. figure:: /_static/images/en-us_image_0000001349190373.png :alt: **Figure 1** Kafka architecture - **Figure 1** Kafka architecture .. table:: **Table 1** Kafka architecture description @@ -42,7 +41,6 @@ Producers publish data to topics, and consumers subscribe to the topics and cons .. figure:: /_static/images/en-us_image_0000001349110501.png :alt: **Figure 2** Relationships between Kafka modules - **Figure 2** Relationships between Kafka modules Consumers label themselves with a consumer group name, and each message published to a topic is delivered to one consumer instance within each subscribing consumer group. If all the consumer instances belong to the same consumer group, loads are evenly distributed among the consumers. As shown in the preceding figure, Consumer1 and Consumer2 work in load-sharing mode; Consumer3, Consumer4, Consumer5, and Consumer6 work in load-sharing mode. If all the consumer instances belong to different consumer groups, messages are broadcast to all consumers. As shown in the preceding figure, the messages in Topic 1 are broadcast to all consumers in Consumer Group1 and Consumer Group2. diff --git a/umn/source/overview/components/kafka/relationship_between_kafka_and_other_components.rst b/umn/source/overview/components/kafka/relationship_between_kafka_and_other_components.rst index 56fb581..63f28c1 100644 --- a/umn/source/overview/components/kafka/relationship_between_kafka_and_other_components.rst +++ b/umn/source/overview/components/kafka/relationship_between_kafka_and_other_components.rst @@ -11,5 +11,4 @@ As a message publishing and subscription system, Kafka provides high-speed data .. figure:: /_static/images/en-us_image_0000001296270858.png :alt: **Figure 1** Relationship with Other Components - **Figure 1** Relationship with Other Components diff --git a/umn/source/overview/components/krbserver_and_ldapserver/krbserver_and_ldapserver_principles.rst b/umn/source/overview/components/krbserver_and_ldapserver/krbserver_and_ldapserver_principles.rst index 8ad3abf..2dca521 100644 --- a/umn/source/overview/components/krbserver_and_ldapserver/krbserver_and_ldapserver_principles.rst +++ b/umn/source/overview/components/krbserver_and_ldapserver/krbserver_and_ldapserver_principles.rst @@ -22,7 +22,6 @@ The security authentication function for user login depends on Kerberos and LDAP .. figure:: /_static/images/en-us_image_0000001349309949.png :alt: **Figure 1** Security authentication architecture - **Figure 1** Security authentication architecture :ref:`Figure 1 ` includes three scenarios: @@ -70,7 +69,6 @@ Principle .. figure:: /_static/images/en-us_image_0000001349390661.png :alt: **Figure 2** Authentication process - **Figure 2** Authentication process **LDAP data read and write** @@ -79,7 +77,6 @@ Principle .. figure:: /_static/images/en-us_image_0000001296750266.png :alt: **Figure 3** Data modification process - **Figure 3** Data modification process **LDAP data synchronization** @@ -90,7 +87,6 @@ Principle .. figure:: /_static/images/en-us_image_0000001296590650.png :alt: **Figure 4** OMS LDAP data synchronization - **Figure 4** OMS LDAP data synchronization Data synchronization direction before cluster installation: Data is synchronized from the active OMS LDAP to the standby OMS LDAP. @@ -101,7 +97,6 @@ Principle .. figure:: /_static/images/en-us_image_0000001296270830.png :alt: **Figure 5** LDAP data synchronization - **Figure 5** LDAP data synchronization Data synchronization direction after cluster installation: Data is synchronized from the active OMS LDAP to the standby OMS LDAP, standby component LDAP, and standby component LDAP. diff --git a/umn/source/overview/components/loader/loader_basic_principles.rst b/umn/source/overview/components/loader/loader_basic_principles.rst index dd14d2d..ef6bdd3 100644 --- a/umn/source/overview/components/loader/loader_basic_principles.rst +++ b/umn/source/overview/components/loader/loader_basic_principles.rst @@ -14,7 +14,6 @@ A Loader model consists of Loader Client and Loader Server, as shown in :ref:`Fi .. figure:: /_static/images/en-us_image_0000001349309893.png :alt: **Figure 1** Loader model - **Figure 1** Loader model :ref:`Table 1 ` describes the functions of each module shown in the preceding figure. diff --git a/umn/source/overview/components/manager/manager_basic_principles.rst b/umn/source/overview/components/manager/manager_basic_principles.rst index c2401f5..4365182 100644 --- a/umn/source/overview/components/manager/manager_basic_principles.rst +++ b/umn/source/overview/components/manager/manager_basic_principles.rst @@ -22,7 +22,6 @@ Architecture .. figure:: /_static/images/en-us_image_0000001349390649.png :alt: **Figure 1** Manager logical architecture - **Figure 1** Manager logical architecture Manager consists of OMS and OMA. diff --git a/umn/source/overview/components/mapreduce/mapreduce_basic_principles.rst b/umn/source/overview/components/mapreduce/mapreduce_basic_principles.rst index d65d18f..32cc027 100644 --- a/umn/source/overview/components/mapreduce/mapreduce_basic_principles.rst +++ b/umn/source/overview/components/mapreduce/mapreduce_basic_principles.rst @@ -13,7 +13,6 @@ Current software implementation is as follows: Specify a Map function to map a s .. figure:: /_static/images/en-us_image_0000001296750206.png :alt: **Figure 1** Distributed batch processing engine - **Figure 1** Distributed batch processing engine MapReduce is a software framework for processing large datasets in parallel. The root of MapReduce is the Map and Reduce functions in functional programming. The Map function accepts a group of data and transforms it into a key-value pair list. Each element in the input domain corresponds to a key-value pair. The Reduce function accepts the list generated by the Map function, and then shrinks the key-value pair list based on the keys. MapReduce divides a task into multiple parts and allocates them to different devices for processing. In this way, the task can be finished in a distributed environment instead of a single powerful server. @@ -30,5 +29,4 @@ As shown in :ref:`Figure 2 `, M .. figure:: /_static/images/en-us_image_0000001296590594.png :alt: **Figure 2** Basic architecture of Apache YARN and MapReduce - **Figure 2** Basic architecture of Apache YARN and MapReduce diff --git a/umn/source/overview/components/mapreduce/mapreduce_enhanced_open_source_features.rst b/umn/source/overview/components/mapreduce/mapreduce_enhanced_open_source_features.rst index 29736ed..edb6168 100644 --- a/umn/source/overview/components/mapreduce/mapreduce_enhanced_open_source_features.rst +++ b/umn/source/overview/components/mapreduce/mapreduce_enhanced_open_source_features.rst @@ -14,7 +14,6 @@ JobHistoryServer (JHS) is the server used to view historical MapReduce task info .. figure:: /_static/images/en-us_image_0000001296590602.png :alt: **Figure 1** Status transition of the JobHistoryServer HA active/standby switchover - **Figure 1** Status transition of the JobHistoryServer HA active/standby switchover **JobHistoryServer High Availability** @@ -34,14 +33,12 @@ The figure below shows the workflow of a MapReduce task. .. figure:: /_static/images/en-us_image_0000001349390613.png :alt: **Figure 2** MapReduce job - **Figure 2** MapReduce job .. figure:: /_static/images/en-us_image_0000001349190317.png :alt: **Figure 3** MapReduce job execution flow - **Figure 3** MapReduce job execution flow The Reduce process is divided into three different steps: Copy, Sort (actually supposed to be called Merge), and Reduce. In Copy phase, Reducer tries to fetch the output of Maps from NodeManagers and store it on Reducer either in memory or on disk. Shuffle (Sort and Merge) phase then begins. All the fetched map outputs are being sorted, and segments from different map outputs are merged before being sent to Reducer. When a job has a large number of maps to be processed, the shuffle process is time-consuming. For specific tasks (for example, SQL tasks such as hash join and hash aggregation), sorting is not mandatory during the shuffle process. However, the sorting is required by default in the shuffle process. diff --git a/umn/source/overview/components/oozie/oozie_basic_principles.rst b/umn/source/overview/components/oozie/oozie_basic_principles.rst index c36ded5..cb718e6 100644 --- a/umn/source/overview/components/oozie/oozie_basic_principles.rst +++ b/umn/source/overview/components/oozie/oozie_basic_principles.rst @@ -22,7 +22,6 @@ Oozie provides an Ext-based web console, through which users can view and monito .. figure:: /_static/images/en-us_image_0000001296590678.png :alt: **Figure 1** Oozie architecture - **Figure 1** Oozie architecture :ref:`Table 1 ` describes the functions of each module shown in :ref:`Figure 1 `. diff --git a/umn/source/overview/components/opentsdb.rst b/umn/source/overview/components/opentsdb.rst index 39272e5..301fe70 100644 --- a/umn/source/overview/components/opentsdb.rst +++ b/umn/source/overview/components/opentsdb.rst @@ -13,7 +13,6 @@ OpenTSDB consists of a Time Series Daemon (TSD) as well as a set of command line .. figure:: /_static/images/en-us_image_0000001296430758.png :alt: **Figure 1** OpenTSDB architecture - **Figure 1** OpenTSDB architecture Application scenarios of OpenTSDB have the following features: diff --git a/umn/source/overview/components/presto.rst b/umn/source/overview/components/presto.rst index 388b975..92b2d68 100644 --- a/umn/source/overview/components/presto.rst +++ b/umn/source/overview/components/presto.rst @@ -13,7 +13,6 @@ Presto allows querying data where it lives, including HDFS, Hive, HBase, Cassand .. figure:: /_static/images/en-us_image_0000001349190389.png :alt: **Figure 1** Presto architecture - **Figure 1** Presto architecture Presto runs in a cluster in distributed mode and contains one coordinator and multiple worker processes. Query requests are submitted from clients (for example, CLI) to the coordinator. The coordinator parses SQL statements, generates execution plans, and distributes the plans to multiple worker processes for execution. diff --git a/umn/source/overview/components/ranger/ranger_basic_principles.rst b/umn/source/overview/components/ranger/ranger_basic_principles.rst index 48f96e5..beaa1d8 100644 --- a/umn/source/overview/components/ranger/ranger_basic_principles.rst +++ b/umn/source/overview/components/ranger/ranger_basic_principles.rst @@ -14,7 +14,6 @@ Ranger Basic Principles .. figure:: /_static/images/en-us_image_0000001349190301.png :alt: **Figure 1** Ranger structure - **Figure 1** Ranger structure .. table:: **Table 1** Architecture description diff --git a/umn/source/overview/components/ranger/relationship_between_ranger_and_other_components.rst b/umn/source/overview/components/ranger/relationship_between_ranger_and_other_components.rst index 31492b0..cf218bb 100644 --- a/umn/source/overview/components/ranger/relationship_between_ranger_and_other_components.rst +++ b/umn/source/overview/components/ranger/relationship_between_ranger_and_other_components.rst @@ -11,5 +11,4 @@ Ranger provides PABC-based authentication plug-ins for components to run on thei .. figure:: /_static/images/en-us_image_0000001349309953.png :alt: **Figure 1** Relationship Between Ranger and Other Components - **Figure 1** Relationship Between Ranger and Other Components diff --git a/umn/source/overview/components/spark/basic_principles_of_spark.rst b/umn/source/overview/components/spark/basic_principles_of_spark.rst index cd81736..fd6b363 100644 --- a/umn/source/overview/components/spark/basic_principles_of_spark.rst +++ b/umn/source/overview/components/spark/basic_principles_of_spark.rst @@ -46,7 +46,6 @@ Architecture .. figure:: /_static/images/en-us_image_0000001296750270.png :alt: **Figure 1** Spark architecture - **Figure 1** Spark architecture .. _mrs_08_00081__t386bd3ecfd8a42f28d5c5a8f64ca341c: @@ -90,7 +89,6 @@ Spark Application Running Principle .. figure:: /_static/images/en-us_image_0000001296590654.png :alt: **Figure 2** Spark application running architecture - **Figure 2** Spark application running architecture :ref:`Figure 3 ` shows the Master and Worker modes adopted by Spark. A user submits an application on the Spark client, and then the scheduler divides a job into multiple tasks and sends the tasks to each Worker for execution. Each Worker reports the computation results to Driver (Master), and then the Driver aggregates and returns the results to the client. @@ -100,7 +98,6 @@ Spark Application Running Principle .. figure:: /_static/images/en-us_image_0000001296270838.png :alt: **Figure 3** Spark Master-Worker mode - **Figure 3** Spark Master-Worker mode Note the following about the architecture: @@ -131,7 +128,6 @@ Spark Streaming is a real-time computing framework built on the Spark, which exp .. figure:: /_static/images/en-us_image_0000001349390673.png :alt: **Figure 4** Data transmission through Direct Kafka API - **Figure 4** Data transmission through Direct Kafka API After the failure, Spark Streaming can read data from Kafka again and process the data segment. The processing result is the same no matter Spark Streaming fails or not, because the semantic is processed only once. @@ -147,7 +143,6 @@ Spark Streaming is a real-time computing framework built on the Spark, which exp .. figure:: /_static/images/en-us_image_0000001296270842.png :alt: **Figure 5** Data transfer lifecycle - **Figure 5** Data transfer lifecycle #. Receive data (blue arrow). @@ -200,7 +195,6 @@ When a failed driver is restarted, restart it as follows: .. figure:: /_static/images/en-us_image_0000001296590658.png :alt: **Figure 6** Computing recovery process - **Figure 6** Computing recovery process #. Recover computing. (Orange arrow) @@ -234,7 +228,6 @@ SparkSQL and DataSet Principle .. figure:: /_static/images/en-us_image_0000001296430802.png :alt: **Figure 7** SparkSQL and DataSet - **Figure 7** SparkSQL and DataSet Spark SQL is a module for processing structured data. In Spark application, SQL statements or DataSet APIs can be seamlessly used for querying structured data. @@ -344,7 +337,6 @@ The core of Structured Streaming is to take streaming data as an incremental dat .. figure:: /_static/images/en-us_image_0000001349390669.png :alt: **Figure 8** Unbounded table of Structured Streaming - **Figure 8** Unbounded table of Structured Streaming Each query operation will generate a result table. At each trigger interval, updated data will be synchronized to the result table. Whenever the result table is updated, the updated result will be written into an external storage system. @@ -353,7 +345,6 @@ Each query operation will generate a result table. At each trigger interval, upd .. figure:: /_static/images/en-us_image_0000001296750274.png :alt: **Figure 9** Structured Streaming data processing model - **Figure 9** Structured Streaming data processing model Storage modes of Structured Streaming at the output phase are as follows: @@ -388,7 +379,6 @@ Basic Concepts .. figure:: /_static/images/en-us_image_0000001296430806.png :alt: **Figure 10** RDD dependency - **Figure 10** RDD dependency - **Narrow dependency**: Each partition of the parent RDD is used by at most one partition of the child RDD. @@ -405,7 +395,6 @@ Basic Concepts .. figure:: /_static/images/en-us_image_0000001349110505.png :alt: **Figure 11** RDD operation - **Figure 11** RDD operation The data and operation model of RDD are quite different from those of Scala. @@ -465,7 +454,6 @@ Basic Concepts .. figure:: /_static/images/en-us_image_0000001349309957.png :alt: **Figure 12** Algorithm process - **Figure 12** Algorithm process Shuffle is a bridge to connect data. The following describes the implementation of shuffle in Spark. diff --git a/umn/source/overview/components/spark/relationship_among_spark,_hdfs,_and_yarn.rst b/umn/source/overview/components/spark/relationship_among_spark,_hdfs,_and_yarn.rst index 314cfd7..88e8300 100644 --- a/umn/source/overview/components/spark/relationship_among_spark,_hdfs,_and_yarn.rst +++ b/umn/source/overview/components/spark/relationship_among_spark,_hdfs,_and_yarn.rst @@ -19,7 +19,6 @@ Spark involves Driver and Executor. Driver schedules tasks and Executor runs tas .. figure:: /_static/images/en-us_image_0000001296270798.png :alt: **Figure 1** File reading process - **Figure 1** File reading process The file reading process is as follows: @@ -36,7 +35,6 @@ The file reading process is as follows: .. figure:: /_static/images/en-us_image_0000001349390629.png :alt: **Figure 2** File writing process - **Figure 2** File writing process The file writing process is as follows: @@ -63,7 +61,6 @@ The Spark computing and scheduling can be implemented using Yarn mode. Spark enj .. figure:: /_static/images/en-us_image_0000001296590618.png :alt: **Figure 3** Spark on Yarn-cluster operation framework - **Figure 3** Spark on Yarn-cluster operation framework Spark on Yarn-cluster implementation process: @@ -89,7 +86,6 @@ The Spark computing and scheduling can be implemented using Yarn mode. Spark enj .. figure:: /_static/images/en-us_image_0000001296430766.png :alt: **Figure 4** Spark on Yarn-client operation framework - **Figure 4** Spark on Yarn-client operation framework Spark on Yarn-client implementation process: diff --git a/umn/source/overview/components/spark/spark_ha_solution.rst b/umn/source/overview/components/spark/spark_ha_solution.rst index 2a78efd..5220cd3 100644 --- a/umn/source/overview/components/spark/spark_ha_solution.rst +++ b/umn/source/overview/components/spark/spark_ha_solution.rst @@ -25,7 +25,6 @@ The multi-active instance HA mode not only can prevent service interruption caus .. figure:: /_static/images/en-us_image_0000001349110489.png :alt: **Figure 1** Spark JDBCServer HA - **Figure 1** Spark JDBCServer HA #. When a JDBCServer is started, it registers with ZooKeeper by writing node information in a specified directory. Node information includes the instance IP address, port number, version, and serial number. @@ -117,7 +116,6 @@ In multi-tenant mode, JDBCServers are bound with tenants. Each tenant correspond .. figure:: /_static/images/en-us_image_0000001349309945.png :alt: **Figure 2** Multi-tenant mode of Spark JDBCServer - **Figure 2** Multi-tenant mode of Spark JDBCServer #. When ProxyServer is started, it registers with ZooKeeper by writing node information in a specified directory. Node information includes the instance IP address, port number, version, and serial number. diff --git a/umn/source/overview/components/spark2x/basic_principles_of_spark2x.rst b/umn/source/overview/components/spark2x/basic_principles_of_spark2x.rst index 29b8952..2e18430 100644 --- a/umn/source/overview/components/spark2x/basic_principles_of_spark2x.rst +++ b/umn/source/overview/components/spark2x/basic_principles_of_spark2x.rst @@ -31,7 +31,6 @@ Architecture .. figure:: /_static/images/en-us_image_0000001296430814.png :alt: **Figure 1** Spark architecture - **Figure 1** Spark architecture .. _mrs_08_007101__t91e81509880f400c9830f64cf706a81d: @@ -75,7 +74,6 @@ Spark Principle .. figure:: /_static/images/en-us_image_0000001296590670.png :alt: **Figure 2** Spark application running architecture - **Figure 2** Spark application running architecture Spark uses Master and Worker modes, as shown in :ref:`Figure 3 `. A user submits an application on the Spark client, and then the scheduler divides a job into multiple tasks and sends the tasks to each Worker for execution. Each Worker reports the computation results to Driver (Master), and then the Driver aggregates and returns the results to the client. @@ -85,7 +83,6 @@ Spark uses Master and Worker modes, as shown in :ref:`Figure 3 ` describes the components shown in :ref:`Figure 1 `. @@ -58,7 +57,6 @@ A scheduler maintains queue information. You can submit applications to one or m .. figure:: /_static/images/en-us_image_0000001296590614.png :alt: **Figure 2** Resource allocation model - **Figure 2** Resource allocation model Principle diff --git a/umn/source/overview/components/yarn/yarn_enhanced_open_source_features.rst b/umn/source/overview/components/yarn/yarn_enhanced_open_source_features.rst index 303f4fd..49c4b09 100644 --- a/umn/source/overview/components/yarn/yarn_enhanced_open_source_features.rst +++ b/umn/source/overview/components/yarn/yarn_enhanced_open_source_features.rst @@ -65,7 +65,6 @@ Similar to open source Fair Scheduler and Capacity Scheduler, Superior Scheduler .. figure:: /_static/images/en-us_image_0000001296430794.jpg :alt: **Figure 1** Internal architecture of Superior Scheduler - **Figure 1** Internal architecture of Superior Scheduler In :ref:`Figure 1 `, Superior Scheduler consists of the following modules: @@ -82,7 +81,6 @@ In :ref:`Figure 1 `, Superior S .. figure:: /_static/images/en-us_image_0000001349110493.png :alt: **Figure 2** Comparison of Superior Scheduler with open source schedulers - **Figure 2** Comparison of Superior Scheduler with open source schedulers Apart from the enhanced system throughput and utilization, Superior Scheduler provides following major scheduling features: @@ -116,7 +114,6 @@ Apart from the enhanced system throughput and utilization, Superior Scheduler pr .. figure:: /_static/images/en-us_image_0000001296590646.jpg :alt: **Figure 3** Resource scheduling policies - **Figure 3** Resource scheduling policies .. note:: @@ -192,7 +189,6 @@ To solve this problem, the CPU resources are allocated to each container based o .. figure:: /_static/images/en-us_image_0000001296750262.png :alt: **Figure 4** CPU quota - **Figure 4** CPU quota Enhanced Open Source Feature: Optimizing Restart Performance @@ -206,5 +202,4 @@ To speed up the startup, obtain the list of unfinished applications before start .. figure:: /_static/images/en-us_image_0000001349190361.jpg :alt: **Figure 5** Starting the ResourceManager recovery - **Figure 5** Starting the ResourceManager recovery diff --git a/umn/source/overview/components/yarn/yarn_ha_solution.rst b/umn/source/overview/components/yarn/yarn_ha_solution.rst index 4359f0b..0302bd5 100644 --- a/umn/source/overview/components/yarn/yarn_ha_solution.rst +++ b/umn/source/overview/components/yarn/yarn_ha_solution.rst @@ -15,7 +15,6 @@ ResourceManager in Yarn manages resources and schedules tasks in the cluster. In .. figure:: /_static/images/en-us_image_0000001296430826.png :alt: **Figure 1** ResourceManager HA architecture - **Figure 1** ResourceManager HA architecture ResourceManager HA is achieved using active-standby ResourceManager nodes, as shown in :ref:`Figure 1 `. Similar to the HDFS HA solution, the ResourceManager HA allows only one ResourceManager node to be in the active state at any time. When the active ResourceManager fails, the active-standby switchover can be triggered automatically or manually. diff --git a/umn/source/overview/components/zookeeper/relationship_between_zookeeper_and_other_components.rst b/umn/source/overview/components/zookeeper/relationship_between_zookeeper_and_other_components.rst index 6430c1b..a1e6750 100644 --- a/umn/source/overview/components/zookeeper/relationship_between_zookeeper_and_other_components.rst +++ b/umn/source/overview/components/zookeeper/relationship_between_zookeeper_and_other_components.rst @@ -15,7 +15,6 @@ Relationship Between ZooKeeper and HDFS .. figure:: /_static/images/en-us_image_0000001349190409.png :alt: **Figure 1** Relationship between ZooKeeper and HDFS - **Figure 1** Relationship between ZooKeeper and HDFS As the client of a ZooKeeper cluster, ZKFailoverController (ZKFC) monitors the status of NameNode. ZKFC is deployed only in the node where NameNode resides, and in both the active and standby HDFS NameNodes. @@ -33,7 +32,6 @@ Relationship Between ZooKeeper and YARN .. figure:: /_static/images/en-us_image_0000001296750310.png :alt: **Figure 2** Relationship Between ZooKeeper and YARN - **Figure 2** Relationship Between ZooKeeper and YARN #. When the system is started, ResourceManager attempts to write state information to ZooKeeper. ResourceManager that first writes state information to ZooKeeper is selected as the active ResourceManager, and others are standby ResourceManagers. The standby ResourceManagers periodically monitor active ResourceManager election information in ZooKeeper. @@ -49,7 +47,6 @@ Relationship Between ZooKeeper and HBase .. figure:: /_static/images/en-us_image_0000001349390705.png :alt: **Figure 3** Relationship between ZooKeeper and HBase - **Figure 3** Relationship between ZooKeeper and HBase #. HRegionServer registers itself to ZooKeeper on Ephemeral node. ZooKeeper stores the HBase information, including the HBase metadata and HMaster addresses. @@ -66,7 +63,6 @@ Relationship Between ZooKeeper and Kafka .. figure:: /_static/images/en-us_image_0000001296590694.png :alt: **Figure 4** Relationship between ZooKeeper and Kafka - **Figure 4** Relationship between ZooKeeper and Kafka #. Broker uses ZooKeeper to register broker information and elect a partition leader. diff --git a/umn/source/overview/components/zookeeper/zookeeper_basic_principle.rst b/umn/source/overview/components/zookeeper/zookeeper_basic_principle.rst index 718fba6..63bcc2d 100644 --- a/umn/source/overview/components/zookeeper/zookeeper_basic_principle.rst +++ b/umn/source/overview/components/zookeeper/zookeeper_basic_principle.rst @@ -23,7 +23,6 @@ Nodes in a ZooKeeper cluster have three roles: Leader, Follower, and Observer. : .. figure:: /_static/images/en-us_image_0000001349310065.png :alt: **Figure 1** ZooKeeper architecture - **Figure 1** ZooKeeper architecture :ref:`Table 1 ` describes the functions of each module shown in :ref:`Figure 1 `. diff --git a/umn/source/overview/functions/message_notification.rst b/umn/source/overview/functions/message_notification.rst index 4fb67fc..3192d86 100644 --- a/umn/source/overview/functions/message_notification.rst +++ b/umn/source/overview/functions/message_notification.rst @@ -32,5 +32,4 @@ You can create a topic and configure topic policies to control publisher and sub .. figure:: /_static/images/en-us_image_0000001296750222.png :alt: **Figure 1** Implementation process - **Figure 1** Implementation process diff --git a/umn/source/overview/what_is_mrs.rst b/umn/source/overview/what_is_mrs.rst index 7de69a6..b96c48d 100644 --- a/umn/source/overview/what_is_mrs.rst +++ b/umn/source/overview/what_is_mrs.rst @@ -23,7 +23,6 @@ Product Architecture .. figure:: /_static/images/en-us_image_0000001349309961.png :alt: **Figure 1** MRS architecture - **Figure 1** MRS architecture MRS architecture includes infrastructure and big data processing phases. diff --git a/umn/source/preparing_a_user/creating_an_mrs_user.rst b/umn/source/preparing_a_user/creating_an_mrs_user.rst index a8af45d..24daada 100644 --- a/umn/source/preparing_a_user/creating_an_mrs_user.rst +++ b/umn/source/preparing_a_user/creating_an_mrs_user.rst @@ -28,7 +28,6 @@ Process Flow .. figure:: /_static/images/en-us_image_0000001296217532.gif :alt: **Figure 1** Process for granting MRS permissions - **Figure 1** Process for granting MRS permissions #. .. _mrs_01_0453__li895020818018: 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 884c92c..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, 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. +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 ------------ @@ -22,7 +22,6 @@ Kerberos architecture is shown in :ref:`Figure 1 *\ **Logging In to a Linux ECS**\ *>*\ **Login Using an SSH Password**\ *in the Elastic Cloud Server User Guide*. +- To enable users to log in to a Linux ECS using a password (SSH), see **Instances** *>* **Logging In to a Linux ECS** *>* **Login Using an SSH Password** *in the Elastic Cloud Server User Guide*. Installing a Client on the Core Node ------------------------------------ @@ -184,7 +184,6 @@ Installing a Client on a Node Outside the Cluster .. figure:: /_static/images/en-us_image_0000001348738173.png :alt: **Figure 1** Adding the Master node IP addresses - **Figure 1** Adding the Master node IP addresses c. Run the **service ntpd stop** command to stop the NTP service. 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 0cbf193..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 @@ -12,7 +12,7 @@ Updating the Client Configuration **Method 1**: -#. Log in to FusionInsight Manager. For details, see :ref:`Accessing FusionInsight Manager (MRS 3.x or Later) `.Click the name of the cluster to be operated in the **Cluster** drop-down list. +#. Log in to FusionInsight Manager. For details, see :ref:`Accessing FusionInsight Manager (MRS 3.x or Later) `. Click the name of the cluster to be operated in the **Cluster** drop-down list. #. Choose **More** > **Download Client** > **Configuration Files Only**. diff --git a/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_flink_client.rst b/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_flink_client.rst index ca4b108..2ade4c5 100644 --- a/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_flink_client.rst +++ b/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_flink_client.rst @@ -136,21 +136,18 @@ Using the Flink Client (Versions Earlier Than MRS 3.x) .. figure:: /_static/images/en-us_image_0000001349057797.png :alt: **Figure 1** Job submitted successfully on Yarn - **Figure 1** Job submitted successfully on Yarn .. figure:: /_static/images/en-us_image_0000001296217612.png :alt: **Figure 2** Session started successfully - **Figure 2** Session started successfully .. figure:: /_static/images/en-us_image_0000001296217608.png :alt: **Figure 3** Job submitted successfully in the session - **Figure 3** Job submitted successfully in the session #. Go to the native YARN service page, find the application of the job, and click the application name to go to the job details page. For details, see `Viewing Flink Job Information `__. @@ -163,7 +160,6 @@ Using the Flink Client (Versions Earlier Than MRS 3.x) .. figure:: /_static/images/en-us_image_0000001349257273.png :alt: **Figure 4** Application - **Figure 4** Application Using the Flink Client (MRS 3.x or Later) @@ -327,21 +323,18 @@ Using the Flink Client (MRS 3.x or Later) .. figure:: /_static/images/en-us_image_0000001349257277.png :alt: **Figure 5** Job submitted successfully on Yarn - **Figure 5** Job submitted successfully on Yarn .. figure:: /_static/images/en-us_image_0000001296057980.png :alt: **Figure 6** Session started successfully - **Figure 6** Session started successfully .. figure:: /_static/images/en-us_image_0000001349137689.png :alt: **Figure 7** Job submitted successfully in the session - **Figure 7** Job submitted successfully in the session #. Go to the native YARN service page, find the application of the job, and click the application name to go to the job details page. For details, see `Viewing Flink Job Information `__. @@ -354,5 +347,4 @@ Using the Flink Client (MRS 3.x or Later) .. figure:: /_static/images/en-us_image_0000001296057976.png :alt: **Figure 8** Application - **Figure 8** Application diff --git a/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_hive_client.rst b/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_hive_client.rst index 0bd6e65..e2fbc83 100644 --- a/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_hive_client.rst +++ b/umn/source/using_an_mrs_client/using_the_client_of_each_component/using_a_hive_client.rst @@ -65,7 +65,7 @@ Using the Hive Client (Versions Earlier Than MRS 3.x) Setting method: If beeline has not been started, run the **beeline --entireLineAsCommand=false** command. If the beeline has been started, run the **!set entireLineAsCommand false** command. - After the setting, if a statement contains semicolons (**;**) that do not indicate the end of the statement, escape characters must be added, for example, **select concat_ws('\;', collect_set(col1)) from tbl**. + After the setting, if a statement contains semicolons (**;**) that do not indicate the end of the statement, escape characters must be added, for example, **select concat_ws('\\;', collect_set(col1)) from tbl**. Using the Hive Client (MRS 3.x or Later) ---------------------------------------- @@ -116,7 +116,7 @@ Using the Hive Client (MRS 3.x or Later) Setting method: If beeline has not been started, run the **beeline --entireLineAsCommand=false** command. If the beeline has been started, run the **!set entireLineAsCommand false** command. - After the setting, if a statement contains semicolons (**;**) that do not indicate the end of the statement, escape characters must be added, for example, **select concat_ws('\;', collect_set(col1)) from tbl**. + After the setting, if a statement contains semicolons (**;**) that do not indicate the end of the statement, escape characters must be added, for example, **select concat_ws('\\;', collect_set(col1)) from tbl**. Common Hive Client Commands ---------------------------