This topic provides answers to other frequently asked questions about Operation Center.
- FAQ about resource groups
- FAQ about other items
How long are the logs of resource groups for scheduling and node instances that are run on such resource groups retained?
The logs of the shared resource group for scheduling are retained for one week, and the node instances that are run on this type of resource group are retained for one month.
The logs of an exclusive resource group for scheduling are permanently retained, and the node instances that are run on this type of resource group are retained for one month.
Why am I unable to 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 configure a priority for an ODPS node?
Logic description: The higher the priority of a baseline with which an ODPS node is associated, the faster DataWorks and MaxCompute allocate resources for the ODPS node.
- The priority that DataWorks schedules a node instance also indicates the priority that DataWorks allocates scheduling resources for the node instance. A large value indicates a high priority. You can go to Operation Center, open the directed acyclic graph (DAG) of an auto triggered node instance, and then click Show Details to view the priority of the node instance on the General tab. By default, the priority of a node instance is 1. The priority of a node instance that is associated with a baseline is the same as the priority of the baseline.
- The priority of a baseline can be 1, 3, 5, 7, or 8. A large value indicates a high priority. You can create a baseline to protect your data security and configure a high priority for the baseline. For more information, visit Data Asset Management.
- The priority of an SQL task in MaxCompute can be an integer from 1 to 9. A small value indicates a high priority.
- A baseline with a priority of 8 corresponds to an SQL task with a priority of 1. Both the baseline and the SQL task have the highest priority.
- A higher priority for a baseline indicates a higher scheduling priority for the nodes that are associated with the baseline in DataWorks, and a higher priority for SQL tasks in MaxCompute.
- Go to the Operation Center page.
- In the left-side navigation pane, choose .
- Find the baseline whose priority you want to adjust and click Change in the Actions column.
- In the Change Baseline dialog box, configure the Priority parameter.
- Click OK.