q4q5q6qw
q4q5q6qw
> Did you want to modify the port of the worker-server? No, Now after starting, the output of using netstat -ntlp is: tcp 0 0 0.0.0.0:1234 0.0.0.0:* LISTEN 3533851/java tcp...
> After the worker-server is down, should the backlog of task instances be run or not? If run it, it will cause excessive pressure on the worker-server, as you said....
> Does there exist back pressure? Could you please find out it from metrics. The same problem occurs on a 64U128G machine in the production environment. The number of tasks...
```shell [INFO] 2024-04-04 23:30:01.607 +0800 org.apache.dolphinscheduler.server.master.runner.StateWheelExecuteThread:[209] - [WorkflowInstance-197582][TaskInstance-203517] - remove task instance from retry check list [ERROR] 2024-04-04 23:30:01.607 +0800 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[443] - [WorkflowInstance-197574][TaskInstance-203510] - Task finish failed, get a exception,...
```shell [ERROR] 2024-04-04 23:30:01.607 +0800 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[317] - [WorkflowInstance-197574][TaskInstance-203510] - State event handle error, get a unknown exception, will retry this event: TaskStateEvent(processInstanceId=197574, taskInstanceId=203510, taskCode=0, status=TaskExecutionStatus{code=6, desc='failure'}, type=TASK_STATE_CHANGE, key=null, channel=null, context=null)...
```shell [INFO] 2024-04-07 20:12:40.475 +0800 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1799] - [WorkflowInstance-35830][TaskInstance-35992] - There is no need to update the workflow instance state, origin state: WorkflowExecutionStatus{code=7, desc='success'}, target state: WorkflowExecutionStatus{code=7, desc='success'} [INFO] 2024-04-07 20:12:40.475...
It seems that the qrtz_triggers table contains the scheduled task of the deleted process. How to associate the workflow defined in the t_ds_process_definition table with the data in the qrtz_triggers...
3.2.0 has the same problem
[INFO] 2024-02-03 17:50:49.460 +0800 org.apache.dolphinscheduler.api.aspect.AccessLogAspect:[107] - REQUEST TRACE_ID:12483001530752, LOGIN_USER:csb_soc_user, URI:/dolphinscheduler/projects/7848358598592/process-definition/12483001532224/release, METHOD:POST, HANDLER:org.apache.dolphinscheduler.api.controller.ProcessDefinitionController.releaseProcessDefinition, ARGS:{code=12483001532224, projectCode=7848358598592, releaseState=ONLINE} [INFO] 2024-02-03 17:50:49.641 +0800 org.apache.dolphinscheduler.service.cache.impl.CacheNotifyServiceImpl:[115] - send result, command:Command [type=CACHE_EXPIRE, opaque=3295, bodyLen=62] [INFO] 2024-02-03 17:50:49.644...
After the machine specifications of the master and worker services are expanded and the system is restarted, new tasks can be executed properly. Why are all old tasks executed properly...