honkerjha commented on PR #17819:
URL: 
https://github.com/apache/dolphinscheduler/pull/17819#issuecomment-4051837056

   > > In DolphinScheduler 3.4.1, when both "Timeout Alert" and "Timeout 
Failure" are selected in the timeout policy settings, only the alert is sent, 
but the task does not fail as expected. Will this be fixed later?
   > 
   > Task timeout fail bug is fixed by this PR: #17818
   
   Has this issue been fixed in 3.4.1? I set up timeout failure for stored 
procedure tasks in DolphinScheduler 3.4.1, but it's not working as expected. 
@njnu-seafish 
   
   <img width="922" height="645" alt="image" 
src="https://github.com/user-attachments/assets/0aa1d218-a836-4ffc-a3e8-62ae5e11f54a";
 />
   <img width="907" height="523" alt="image" 
src="https://github.com/user-attachments/assets/45de6913-686a-4fcc-82db-7746ce4bd9ee";
 />
   <img width="617" height="818" alt="image" 
src="https://github.com/user-attachments/assets/e28bea02-2a5d-47fd-af55-13ff19bc66eb";
 />
   <img width="1209" height="465" alt="image" 
src="https://github.com/user-attachments/assets/58b925c8-31a2-4956-bc57-f0bbb45d90bd";
 />
   <img width="1424" height="119" alt="image" 
src="https://github.com/user-attachments/assets/dbcb28ce-4781-4bba-88cd-dfc180c8f2d4";
 />
   
   
   
   Looking at the execution logs of the stored procedure, the following content 
is present:
   ```
   2026-03-13 10:00:13.781 INFO  - setSqlParamsMap: Property with paramName: 
value1 put in sqlParamsMap of content call 
aSP_test20260204(null,null,${value1}); successfully.
   2026-03-13 10:01:13.783 INFO  - Try to cancel this procedure task
   2026-03-13 10:01:13.791 INFO  - This procedure task was canceled
   2026-03-13 10:02:44.029 INFO  - out parameter varchar key : value1 , value : 0
   ```
   So does the timeout failure strategy only cancel the execution of the stored 
procedure, rather than changing the status of this node to "failed"? I am 
wondering whether this is a bug or a software feature.
   
   


-- 
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