DataWorks:Node failures

I have configured rerun properties for my node, but the node does not rerun after it fails. In addition, the error message Task Run Timed Out, Killed by System!!! appears. What do I do?

• Problem description:

  The Rerun parameter in the Schedule section of the Properties panel is set to Allow Regardless of Running Status or Allow upon Failure Only for the node. However, the node does not rerun after it fails, and the error message Task Run Timed Out, Killed by System!!! appears.

• Possible cause:

  The Timeout Definition parameter in the Schedule section of the Properties panel is configured for the node. If the execution duration of the node exceeds the value of the Timeout Definition parameter, the node automatically stops and does not rerun. A node that fails to be run due to a timeout cannot be rerun.

• Solution:

  Manually rerun the node.

What do I do if the following error is reported for a node when the node is run: OSError: [Errno 7] Argument list too long?

• Problem description:

  The following error is reported for a node when the node is run: OSError:[Errno 7] Argument list too long.

• Possible cause:

  The executed SQL code exceeds 128 KB in size.

• Solution:

  Split the SQL code and execute it again.

  Note The number of SQL commands in a single node cannot exceed 200.

ODPS-0420095: Access Denied - Authorization Failed [4093], You have NO privilege to do the restricted operation on {acs:odps:*:projects/xxxx}. Access Mode is AllDenied.

• Cause:

  The project to which the job you run belongs is disabled.

• Solution:
  • Check whether your account has overdue payments or whether the default computing quota of the project is a subscription quota and the related subscription service is expired. If your account has overdue payments or the subscription quota is expired, top up your account or renew your subscription. Your project will recover within about 2 to 30 minutes based on the number of orders and the number of jobs that belong to your MaxCompute project.
  • If your account does not have overdue payments or the subscription quota is not expired, your project is manually disabled. Go to the Projects page of the MaxCompute console to restore your project.

What do I do if the message ODPS-0420061: Invalid parameter in HTTP request - Fetched data is larger than the rendering limitation. Please try to reduce your limit size or column number appears?

Specify a threshold for the number of data records that can be returned in your SQL statement. If you want to obtain more data records, you can export the data records. If you want to obtain more than 10,000 data records, use a Tunnel command to export the data records.

What do I do if the data synchronized by using multiple threads is out of order?

A synchronization node reads data from MaxCompute tables in random order. If you do not configure order settings, the data returned by the synchronization node is also out of order.

By default, the data synchronized from MaxCompute is stored in random order. If you want to obtain sorted data, configure order settings for the synchronized data. For example, you can configure order by xx limit n in the SQL statement of the synchronization node to sort data.

What do I do if my synchronization node that uses an AnalyticDB for MySQL data source and runs on a shared resource group fails to run?

Purchase an exclusive resource group for scheduling, associate the resource group with the virtual private cloud (VPC) in which the AnalyticDB for MySQL data source resides, and then run the synchronization node on the exclusive resource group for scheduling. For more information, see Establish a network connection between a resource group and a data source.

When I run a data synchronization node that uses a MySQL data source, the system displays an error message indicating that the Java Database Connectivity (JDBC) driver for the MySQL node is not supported. What do I do?

• The error message sql execute failed! The JDBC driver is not supported. appears because
• the MySQL data source that you selected is not added by using the connection string mode.
• Select a MySQL data source that is added by using the connection string mode. You can refer to the operations in Add a MySQL data source to go to the Data Source page, find the required data source, and then click Edit in the Operation column. In the Edit MySQL Data Source dialog box, view the mode that is used to add the data source.

How do I view the logs of a for-each node, do-while node, or PAI node in Operation Center?

Click the name of the desired instance of a for-each node, do-while node, or PAI node on the Cycle Instance page in Operation Center, and right-click the instance in the directed acyclic graph (DAG) of the instance and select View Internal Nodes.

What do I do if the error message error in your condition run fail appears when I run a branch node?

• Check whether the branch conditions that you specify for the branch node comply with the specifications of the Python syntax.
• If the output of the ancestor assignment node of the branch node is strings, you must enclose variables in single quotation marks (') for the branch node to reference the variables.

What do I do if the error message None Ftp connection info!! appears when I run an FTP Check node?

• Problem description: The FTP Check node that is used to check whether the FTP data source contains the Done file fails to run, and the error message None Ftp connection info!! appears.
• Possible cause: The FTP data source is incorrectly configured. As a result, the FTP Check node fails to obtain information about the FTP data source.
• Solution: Go to the Data Source page to check whether the configurations of the data source that you use are correct. For more information about how to go to the Data Source page, see Add and manage data sources. If no FTP data source is available on the Data Source page, you must add an FTP data source. For more information, see Add an FTP data source.

What do I do if the error message Connect Failed appears when I run an FTP Check node?

• Problem description: The FTP Check node that is used to check whether the FTP data source contains the Done file fails to run, and the error message Connect Failed appears.
• Possible cause: The FTP data source fails to connect to the FTP server.
• Solution: Run the telnet IP address Port number command to check whether the FTP server is normal. Replace the IP address and port number in this command with the IP address and port number of the FTP data source. You can log on to the DataWorks console and view the IP address and port number of the FTP data source on the Data Source page. For more information about how to go to the Data Source page, see Add and manage data sources.

What do I do if the error message The current time has exceeded the end-check time point! appears when I run an FTP Check node?

• Problem description: The FTP Check node that is used to check whether the FTP data source contains the Done file fails to run, and the error message The current time has exceeded the end-check time point! appears.
• Cause: The time specified for the Check stop time parameter has elapsed.
• Solution: Change the value of the Check stop time parameter based on your business requirements on the configuration tab of the FTP Check node. For more information, see Create an FTP Check node.

What do I do if the error message File not Exists or exceeded the end-check time point! appears when I run an FTP Check node?

• Problem description: The FTP Check node that is used to check whether the FTP data source contains the Done file fails to run, and the error message File not Exists or exceeded the end-check time point! appears.
• Cause: One possible cause is that the FTP Check node does not find the Done file before the time specified for the Check stop time parameter arrives. Another possible cause is that the time specified for the Check stop time parameter has elapsed.
• Solution: This is an expected error. If this error message appears, DataWorks does not trigger the descendant node of the FTP Check node to run.

What do I do if the error message no available machine resources under the task resource group appears for my resource group for scheduling?

• Problem description: The system displays the following error message for the resource group for scheduling: no available machine resources under the task resource group
• Solution: Change the resource group for scheduling that you use to run your node. To change the resource group, perform the following operations: Log on to the DataWorks console and go to Operation Center. In the left-side navigation pane of the Operation Center page, choose Cycle Task Maintenance > Cycle Task. On the Cycle Task page, select the auto triggered node for which you want to change the resource group, click Show Details, and then click the Edit icon next to the Scheduling Resource Group field.