LuciferYang opened a new pull request, #56698:
URL: https://github.com/apache/spark/pull/56698

   ### What changes were proposed in this pull request?
   `TriggeredGraphExecution.getRunTerminationReason` decided which failed 
flow's reason to report by calling `collectFirst` over `failureTracker`, a 
`ConcurrentHashMap` whose iteration order is unspecified. When more than one 
flow exhausts its retries (a non-retryable `StopFlowExecution`), the flow whose 
reason gets surfaced therefore varied from run to run.
   
   This extracts a small pure helper, `chooseRunTerminationReason`, that 
considers only the stopped flows and picks the earliest one by 
`(lastFailTimestamp, flowName)`, so the reported reason is stable across 
otherwise-identical runs. `getRunTerminationReason` now calls it and falls back 
to `UnexpectedRunFailure()`. The previous code also computed 
`graphForExecution.flow(...)` and `lastException` only to discard them; those 
are dropped.
   
   ### Why are the changes needed?
   Two runs that fail the same way could report different termination reasons 
(different flow name and cause), which is confusing in logs and events and 
makes the outcome non-reproducible.
   
   ### Does this PR introduce _any_ user-facing change?
   No. The reported reason was already one of the failing flows; it is now 
chosen deterministically.
   
   ### How was this patch tested?
   Added unit tests for `chooseRunTerminationReason` in 
`TriggeredGraphExecutionSuite`: the earliest failure wins regardless of 
iteration order, ties are broken by flow name, and retryable failures are 
ignored. They fail against the previous order-dependent selection and pass with 
this change.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   Generated-by: Claude Code (Claude Opus 4.8)
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to