It is recommended to convert the copied task to a business email list new task, and check it according to the newly created task. If there is no conversion to confirm a few things:
Confirm the execution of the original task in the past week, if the operation is abnormal, communicate the specific reasons;
Confirm the logical difference between the new task and the original task, including SQL, parameters, etc.;
Confirm that the application, person in charge, market, queue, account number are consistent with the information filled in the application form;
The task description includes "application copy through the process, application ID and original task ID";
Run rule configuration attribute check: the cycle type and running time are consistent with the requisition. The timeout period is required and needs to be confirmed by communication. The maximum number of concurrent instances is selected to be less than 10.
Confirm the node number with the user;
Verify the cgroup configuration with the user to avoid insufficient resources to be killed or slow execution; for outbound tasks, it is recommended to increase the recommended value of memory by 1G;
Task monitoring, recommended configuration. Operations such as enabling tasks, modifying task running rules, modifying sql, model changes, and modifying task attributes may have an impact on the stability of the system, requiring the approval of the second-level person in charge, and stopping the application of the interface and task scheduling 3.5 Upgrade, and other tasks that are not related to the big promotion will no longer be approved. When the data quality service is abnormal and it is impossible to verify whether the data meets the requirements, the service is downgraded.