Add a custom resource group

Limits

• The difference between the time of the ECS instance where a custom resource group resides and the current Internet time must be within 2 minutes. Otherwise, service requests may time out and nodes may fail to be run on the custom resource group.
• If the timeout error message response code is not 200 exists in the log file of alisatasknode, the custom resource group was inaccessible within the specific time period. The ECS server hosting the custom resource group can continue working if the exception persists for no more than 10 minutes. To find the exception details, view the heartbeat.log file in the /home/admin/alisatasknode/logs directory.

Purchase an ECS instance

View the hostname and internal IP address of the ECS instance

Log on to the ECS console. In the left-side navigation pane, choose Instances & Images > Instances. On the page that appears, view the hostname and IP address of the purchased ECS instance.

Enable port 8000 for reading logs

1. Add a security group rule.

   Log on to the ECS console. In the left-side navigation pane, choose Network & Security > Security Groups. On the page that appears, find the target security group and click Add Rules in the Actions column.

2. On the Security Group Rules > Inbound page that appears, click Add Security Group Rule in the upper-right corner.
3. In the Add Security Group Rule dialog box that appears, set the parameters. Set Authorization Object to the fixed IP address of Data Integration and Port Range to 8000/8000.

Add a custom resource group

1. In the left-side navigation pane, click Custom Resource Group. The Custom Resource Group page appears.
2. Click Add Resource Group in the upper-right corner.
   Note By default, the Custom Resource Group page lists only your custom resource groups, but not the default resource group.
3. In the Add Resource Group dialog box that appears, set Resource Group Name and click Next.
4. In the Add Server dialog box that appears, set the parameters and click Next.

   Parameter	Description
   Network Type	The network type of the ECS instance. Currently, the classic network type is supported only for ECS instances in the China (Shanghai) region. You can only set this parameter to VPC for ECS instances in other regions.
   Server Name or ECS UUID	The hostname of the ECS instance when Network Type is set to Classic Network. To obtain the hostname, log on to the ECS instance and run the hostname command. The UUID of the ECS instance when Network Type is set to VPC. To obtain the UUID, log on to the ECS instance and run the dmidecode | grep UUID command.
   Server IP Address	The internal IP address of the ECS instance.
   Server CPU (Cores)	The number of CPU cores on the ECS instance. We recommend that you configure at least four CPU cores for an ECS instance hosting a custom resource group.
   Server RAM (GB)	The memory of the ECS instance. We recommend that you configure at least 8 GB RAM and 80 GB disk space for an ECS instance hosting a custom resource group.

   Note To add an ECS instance that resides in a VPC, enter the UUID of the ECS instance. To obtain the UUID, log on to the ECS instance and run the dmidecode | grep UUID command.

   For example, if the dmidecode | grep UUID command returns UUID: 713F4718-8446-4433-A8EC-6B5B62D7****, the UUID is 713F4718-8446-4433-A8EC-6B5B62D7****.

5. Install and initialize the Agent.
   If an ECS instance is newly purchased and has never been used, follow these steps:

   1. Log on to the ECS instance through Secure Shell (SSH) as the root user.
   2. Run the following commands:

      chown admin:admin /opt/taobao  //Grant the admin user the permission to access the /opt/taobao directory.
      wget https://alisaproxy.shuju.aliyun.com/install.sh --no-check-certificate
      sh install.sh --user_name=*****19d --password=****h1bm --enable_uuid=false

   3. Wait for a while, click Refresh in the Add Server dialog box, and check whether the service status changes to Available.
   4. Enable port 8000 on the ECS instance.
      Note If an error occurs when you run the install.sh script or you have to run it again, run the rm –rf install.sh command in the same directory as the install.sh script to delete the generated file. Then, run the install.sh script again. The commands that need to be run during the installation and initialization process differ for each user. Run relevant commands according to instructions on the initialization interface.

If the service status remains Stopped after the preceding steps, the hostname may not be bound to an IP address, as shown in the following figure.

Select the custom resource group for a sync node

On the configuration tab of a sync node, select the custom resource group for Resource Group in the Channel section.