Creating a Routing Policy

Prerequisites

Routing policies are supported only in full forwarding, local first, local federation, and gateway federation modes.

Context

• When a namespace is deleted, all HDFS SmartTakeover routing and path policies in the namespace are also deleted.
• When SmartTakeover is enabled, the performance reduces by less than 20% when 1 to 3 clusters are managed and by less than 25% when 3 to 10 clusters are managed as compared with that when no cluster is managed.
• The following describes the restrictions of the number of routing policies:
  • If SmartTakeover is enabled for multiple namespaces in an cluster and SmartTakeover is set to the local federation mode for some of these namespaces, a maximum of 3 storage clusters in an cluster (excluding the local cluster) can be managed.
  • If SmartTakeover is enabled for multiple namespaces in an cluster and SmartTakeover is set to the gateway federation mode for all of these namespaces, a maximum of 20 storage clusters in an cluster can be managed.

Procedure

1. Choose Resources > Resources > Namespace.
2. Select a desired account from the Account drop-down list in the upper left corner.
3. Click a desired namespace name to go to the details page. Choose SmartTakeover > Routing Policies.
4. Click Create.

   The Create Routing Policy page is displayed on the right.

5. Set the routing policy. Table 1 describes related parameters.

   Table 1 Routing policy parameters

   SmartTakeover Mode	Description
   Cluster Name	Indicates the name of a managed cluster. NOTE: The value contains 1 to 127 characters, including only digits, letters, underscores (_), periods (.), and hyphens (-). The value cannot be local. When the SmartTakeover mode is set to full forwarding or local first, the cluster name is optional. The default value is nsName. When the SmartTakeover mode is set to local federation or gateway federation, the cluster name is mandatory.
   Active Node Address	Indicates the service IP address of the active node in a managed cluster. For example, 10.1.1.1. For details about the values, see Table 2.
   Active Node Port	Indicates the port number of the active node in a managed cluster. For example, 1000. For details about the values, see Table 2.
   Configuring Standby Node	If this parameter is selected, you need to set Standby Node Address and Standby Node Port of a managed cluster. For details about the values, see Table 2.
   Authentication Mode	Indicates the authentication mode of a managed cluster. The value can be SIMPLE or KERBEROS. The default value is SIMPLE.
   Set the cluster as the default storage cluster	In federation modes, there is only one default managed cluster. If this parameter is selected, the default managed cluster is replaced with the current managed cluster. The first managed cluster is set to the default managed cluster. NOTE: This parameter is displayed only in gateway federation and local federation modes.

   Table 2 Information about the active and standby nodes in the storage cluster

   Storage Cluster Name	Storage Cluster Type	Service IP Address of the Active NameNode	Service IP Address of the Standby NameNode	Port
   hdp01	Hortonworks HDP cluster (HA mode enabled)	Service IP address of the active NameNode	Service IP address of the standby NameNode	8020
   hdp02	Hortonworks HDP cluster (HA mode disabled)	Service IP address of the active NameNode	None	8020
   fs801	FusionStorage 8.0.1 cluster	Dynamic IP address of namespace hotdir	None	8020
   fi01	FusionInsight cluster	Service IP address of the active NameNode	Service IP address of the standby NameNode	25000
   cdh01	Cloudera CDH cluster (HA mode enabled)	Service IP address of the active NameNode	Service IP address of the standby NameNode	8020
   cdh02	Cloudera CDH cluster (HA mode disabled)	Service IP address of the active NameNode	None	8020
   pacific01	Cluster of OceanStor Pacific series 8.1.3 and later versions	Namespace domain name	None	8020

6. Click OK.