All Products
Search
Document Center

DataWorks:Manage real-time synchronization nodes

Last Updated:Aug 18, 2023

The Real Time DI page of the DataWorks console displays all real-time synchronization nodes that are committed to and run by the scheduling system.

Go to the Real Time DI page

  1. Log on to the DataWorks console.
  2. In the left-side navigation pane, click Workspaces.
  3. In the top navigation bar, select the region where your workspace resides. On the Workspaces page, find your workspace and click DataStudio in the Actions column.
  4. On the DataStudio page, click the 图标 icon in the upper-left corner and choose All Products > Data Development And Task Operation > Operation Center.

  5. In the left-side navigation pane of the Operation Center page, click the 图标 icon next to RealTime Task.

  6. Select Real Time DI from the drop-down list. The Real Time DI page appears.

View real-time synchronization nodes in the node list

The node list displays real-time synchronization nodes that are run by the scheduling system. You can manage these nodes and perform O&M operations on these nodes. For example, you can view the basic information, properties, and running information of a real-time synchronization node. You can also start or undeploy a real-time synchronization node.11

Area

Description

1

In this area, you can specify filter conditions to search for real-time synchronization nodes.

You can specify the following filter conditions to search for nodes: Node name or ID, Node Status, Owner, Source Type, Source Name, Operated By, Destination Type, Destination Name, and Data Integration Resource Group.

Note

When you search for nodes by node name, the search result is affected by other filter conditions that you specified. Only the nodes that meet all filter conditions are displayed.

2

In this area, you can view the following information about the real-time synchronization node that you want to query:

  • ID: the ID of the node.

  • Node Name: the name of the node. You can click the node name to go to the details page of the node.

  • Status: the status of the node. The node can be in one of the following states: Running, Not Running, Waiting for resources, Exception, and Stop or Stopping.

  • Description: the description of the node.

  • Business Latency: the period of time between the current time and the offset from which incremental data starts to be synchronized.

  • Current Synchronization Site: the offset at which incremental data is being synchronized.

  • Recent operation time: the time when the node was last modified.

  • Operated By: the user who last modified the node.

  • Source Type: the type of the source.

  • Source data source: the name of the source.

  • Destination Type: the type of the destination.

  • Destination: the name of the destination.

  • Owner: the owner of the workspace to which the node belongs.

  • Current Start Site: the offset from which incremental data starts to be synchronized.

  • Data Read Speed (Bytes per Second): the speed at which the data is read.

  • Record read speed (RPS): the speed at which the read data is written to logs.

  • Data Integration Resource Group: the resource group that is used to run the node.

3

In this area, you can perform the following operations on multiple nodes at a time:

  • Start: Start the nodes that are not run.

  • Stop: Stop the nodes that are running.

  • Undeploy: Undeploy the nodes that are not run, abnormal, or stopped.

  • Configure Alert Rule: Configure alert rules for the nodes.

  • Operation alarm: Delete, enable, or disable alert rules and modify alert rules based on alert metric types.

  • Change Owner: Change the owners of the nodes. This helps you search for and manage nodes by owner.

View the details of a real-time synchronization node

Find the real-time synchronization node that you want to query and click the node name to go to the details panel of the node. In the details panel of the node, you can view the details of the node on the Operation Information, Log, Basic Properties, Task configuration, Failover records, and DDL records tabs.

Perform operations on a real-time synchronization node

  • Start a real-time synchronization node

    Find the node that you want to start and click Start in the Operation column. In the Start dialog box, configure the parameters and click Confirm. The system starts to run the node.

    If you select Reset site, you must configure the Time and Time zone parameters.

  • Stop a real-time synchronization node

    Find the real-time synchronization node that you want to stop and click Stop in the Operation column. Then, click Stop in the message that appears to stop the node.

  • Undeploy a real-time synchronization node

    Find the node that you want to undeploy and click Undeploy in the Operation column. Then, click Undeploy in the message that appears to undeploy the node.

  • View the alert rule settings of a real-time synchronization node

    • Find the node whose alert rule settings you want to view and click View Alert Settings in the Operation column. The Alert Events tab appears. On this tab, you can configure the Occurrence Time, Alert Level, and Rules parameters to view the alert events of the node.

    • Click Alert Rules to go to the Alert Rules tab. On this tab, you can view all the alert rules that are created for the node. You can view the metrics and status of an alert rule. You can also modify, pause, delete, or test an alert rule. If you want to create an alert rule, click Create Rule in the upper-right corner of the Alert Rules tab and configure the parameters. The following table describes the parameters.22

      Parameter

      Description

      Required

      Name

      The name of the alert rule.

      Yes

      Description

      The description of the alert rule.

      No

      Metrics

      The type of metric that triggers an alert. The Metrics parameter and the Threshold parameter must be used in pairs. The value of the Threshold parameter varies based on that of the Metrics parameter. Valid values: Node Status, Business Latency, Failover, Not Supported by DDL Statements, DDL Notification, and Dirty Data.

      Yes

      Threshold

      The thresholds for the metrics that are specified by the Metrics parameter.

      • If you set the Metrics parameter to Node Status, you must specify the interval at which alerts are triggered.

      • If you set the Metrics parameter to Business Latency, you must specify a duration for the business latency and another duration during which an alert can last after the duration for the business latency elapses.

      • If you set the Metrics parameter to Not Supported by DDL Statements, you need to only select an alert level.

      • For a node that is run in non-distributed execution mode, if you set the Metrics parameter to Failover, you must specify a duration and the maximum number of failovers that can be performed within the duration before an alert is triggered. For a node that is run in distributed execution mode, if you set the Metrics parameter to Failover, you must specify a duration and the maximum number of failovers that can be performed for a slice of the node within the duration before an alert is triggered.

      Yes

      Alert Interval

      The minimum interval at which alerts are reported. Default value: 5. Minimum value: 1. Unit: minutes.

      Yes

      WARNING

      The method used to receive a notification for a WARNING-level alert. Valid values: Mail, SMS, and DingTalk.

      Note
      • Mail: If you want to use a RAM user to receive the notification, you must use an Alibaba Cloud account to add the email address of the RAM user in user information.

      • SMS: If you want to use a RAM user to receive the notification, you must use an Alibaba Cloud account to add the mobile phone number of the RAM user in user information.

      • DingTalk: If you want to receive the notification by using a DingTalk chatbot, you must configure a DingTalk chatbot for your DingTalk group and add the keyword DataWorks for the DingTalk chatbot.

      No

      CRITICAL

      The method used to receive a notification for a CRITICAL-level alert. Valid values: Mail, SMS, and DingTalk.

      No

      Receiver (Non-DingTalk)

      The alert contact to whom alert notifications are sent.

      Yes