DanielLeens commented on issue #13320:
URL: https://github.com/apache/seatunnel/issues/13320#issuecomment-6983720639

   Confirmed the probe-exception → failure-state behavior on 
`89f91a89af15f33d97a942d8b65f4fc1b0c80bf5` (Java 11.0.27).
   
   Steps:
   1. Construct a real PhysicalVertex with IMap state `RUNNING`, an owned slot, 
and a worker address that remains in the membership set.
   2. Invoke actual `initStateFuture()` with a mocked 
`CheckTaskGroupIsExecutingOperation` invocation result.
   3. Control A: result `true` leaves both vertex and IMap `RUNNING`.
   4. Control B: result `false` changes both to `FAILING`.
   5. Fault case: invocation `.get()` throws `ExecutionException`. Both vertex 
and IMap become `FAILING`, exactly as for `false`. Verify only one probe 
invocation was read.
   
   [Executable probe and exact build/run 
commands](https://github.com/apache/seatunnel/issues/13316#issuecomment-6983695881):
 see the three `probe(...)` calls in `LifecycleRepros.java`.
   
   This is a focused invocation-failure test of the real production method. The 
remote task is a test double: I have not independently shown a healthy real 
worker being failed during a real partition/GC pause. The confirmed behavior is 
that an unknown probe result caused by invocation failure is treated like “not 
executing.”
   


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