You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As shown in FIG. Flow is always stuck in the killing state. Even if the kill operation is performed, the corresponding executor only performs the cancel action, and there is no more log information.
Executor log info 2024/03/15 15:01:18.918 +0800 INFO [ExecutorServlet] [Azkaban] User zhangqiming has called action cancel on 818255 2024/03/15 15:01:18.918 +0800 INFO [ExecutorServlet] [Azkaban] Cancel called. 2024/03/15 15:01:18.918 +0800 INFO [FlowRunner] [Azkaban] Flow killed by zhangqiming 2024/03/15 15:01:50.275 +0800 INFO [FlowRunnerManager] [Azkaban] # of executing flows: 22 20
Jmx info
As shown in FIG. 22 Flow states are stuck in killing state.
The text was updated successfully, but these errors were encountered:
Executor log info
2024/03/15 15:01:18.918 +0800 INFO [ExecutorServlet] [Azkaban] User zhangqiming has called action cancel on 818255 2024/03/15 15:01:18.918 +0800 INFO [ExecutorServlet] [Azkaban] Cancel called. 2024/03/15 15:01:18.918 +0800 INFO [FlowRunner] [Azkaban] Flow killed by zhangqiming 2024/03/15 15:01:50.275 +0800 INFO [FlowRunnerManager] [Azkaban] # of executing flows: 22 20
Jmx info
As shown in FIG. 22 Flow states are stuck in killing state.
The text was updated successfully, but these errors were encountered: