[ 
https://issues.apache.org/jira/browse/GOBBLIN-2181?focusedWorklogId=948332&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-948332
 ]

ASF GitHub Bot logged work on GOBBLIN-2181:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Dec/24 18:17
            Start Date: 13/Dec/24 18:17
    Worklog Time Spent: 10m 
      Work Description: vsinghal85 commented on code in PR #4084:
URL: https://github.com/apache/gobblin/pull/4084#discussion_r1884317058


##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/orchestration/DagProcessingEngine.java:
##########
@@ -149,6 +158,16 @@ public void run() {
           dagTask.conclude();
           log.info(dagProc.contextualizeStatus("concluded dagTask"));
         } catch (Exception e) {
+          log.error("DagProcEngineThread: " + 
dagProc.contextualizeStatus("error"), e);
+          if (!DagProcessingEngine.isTransientException(e)) {
+            DagActionStore.DagAction dagAction = dagTask.getDagAction();
+            if (dagAction != null) {

Review Comment:
   removed





Issue Time Tracking
-------------------

    Worklog Id:     (was: 948332)
    Time Spent: 3h 10m  (was: 3h)

> Non transient exception handling by flowspec removal
> ----------------------------------------------------
>
>                 Key: GOBBLIN-2181
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2181
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: Vaibhav Singhal
>            Priority: Major
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> - Many times we experience failures in flow initialization or processing due 
> to which flow could not be concluded properly
>  - Azkaban client exceptions and SQLIntegrityViolation exceptions are 
> examples which have caused failures in recent history
>  - Currently most of these failures are by default considered transient 
> exceptions and are retried infinitely
>  - As a side effect, it causes flows not to conclude and causes failures in 
> future flow submissions which have caused incidents recently
>  
>  - As a first step we want to consider all exceptions as non transient and 
> not retry and remove conclude the flow by removing flowspec and dag action
>  - This issue tracks the changes to conclude the flow for non transient 
> exceptions and also mark them as failure to reflect the correct status of the 
> flow



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to