This topic provides answers to other frequently asked questions about Operation Center.
-
Nodes and instances
-
Resource groups
-
Other
What is the relationship between auto triggered nodes and auto triggered node instances, data backfill instances, and test instances?
Every night, DataWorks uses your auto triggered nodes to automatically generate and schedule cycle instances for the next day. You can also manually trigger an auto triggered node to generate and run a data backfill instance or a test instance.
When creating a node, you can opt to generate an instance immediately upon publishing. After the node is published to Operation Center, the instance appears on the Cycle Instance page.
How long are logs for instances and the instances retained?
Instances that run on the shared resource group for scheduling are retained for one month (30 days), and logs for the instances are retained for one week (7 days).
Instances that run on exclusive resource groups for scheduling are retained for one month (30 days), and logs for the instances are also retained for one month (30 days).
-
If the logs for a completed instance exceed 3 MB, the system automatically clears them daily.
-
You cannot manually delete an instance after it is generated. If a node no longer needs to run, you can freeze the auto triggered node or the instance. Freezing an auto triggered node differs from freezing an instance. For more information, see Freeze and unfreeze a node.
Why cannot I perform big data computing on a resource group for scheduling?
Resource groups for scheduling are used to schedule nodes and provide only limited resources. Therefore, resource groups for scheduling are not suitable for big data computing. MaxCompute can process large amounts of data. We recommend that you use MaxCompute for big data computing.
How do I adjust the priority of a node instance?
To adjust the priority of a node instance, adjust the priority of the baseline to which the node instance belongs. The priority of a baseline can be set to 1, 3, 5, 7, or 8. A larger value indicates a higher priority. The system preferentially allocates scheduling resources to a baseline with a higher priority.
Adjust the baseline priority to change the run priority of daily instances generated from an auto triggered node.
-
Go to the Operation Center page.
-
In the left-side navigation pane, choose .
-
Click Edit in the Actions column of the baseline that you want to modify.
-
In the Modify Baseline dialog box, set the Priority parameter.
-
Click Completed.
How do I view the priority of a node instance?
You can find a node's priority in .