ketingli1 commented on issue #18202:
URL: 
https://github.com/apache/dolphinscheduler/issues/18202#issuecomment-4349234612

   
查到原因了,查看实例的执行日志,是因为租户配置的问题,要把work-server中的worker.tenant-config.default-tenant-enabled
 这个配置设置为true
   
   
   root@ubantu187:/opt/apache-dolphinscheduler-3.4.1-bin/worker-server/logs# 
cat 
/opt/apache-dolphinscheduler-3.4.1-bin/worker-server/logs/20260430/172115680413792/1/2/2.log
   2026-04-30 09:34:02.842 INFO  - 🐬 Initialize Task Context
   2026-04-30 09:34:02.845 ERROR - PhysicalTaskExecutor{id=2, name=imp_T005T, 
stat=INITIALIZED} execute failed
   org.apache.dolphinscheduler.plugin.task.api.TaskException: The tenantCode is 
default, please enable TenantConfig#isDefaultTenantEnabled
           at 
org.apache.dolphinscheduler.server.worker.utils.TenantUtils.getOrCreateActualTenant(TenantUtils.java:64)
           at 
org.apache.dolphinscheduler.server.worker.executor.PhysicalTaskExecutor.initializeTaskContext(PhysicalTaskExecutor.java:127)
           at 
org.apache.dolphinscheduler.task.executor.AbstractTaskExecutor.start(AbstractTaskExecutor.java:66)
           at 
org.apache.dolphinscheduler.task.executor.worker.TaskExecutorWorker.start(TaskExecutorWorker.java:65)
           at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
           at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
           at java.base/java.lang.Thread.run(Thread.java:834)
   2026-04-30 09:34:03.005 INFO  - 🐬 Finalize Task Instance
   2026-04-30 09:34:03.007 INFO  - FINALIZE_SESSION


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to