nielifeng commented on PR #11564: URL: https://github.com/apache/seatunnel/pull/11564#issuecomment-5088534325
Follow-up validation after review findings: - Fixed the success-response exception boundary so a failed `sendResponse(null)` is never followed by a second failure response. - Added a focused red/green regression: the previous implementation fails with `expected: <1> but was: <2>`; the updated implementation passes. - Strengthened the remote offload test with 4 target generic-operation threads while 3 are deliberately occupied. With the offload executor saturated, another remote generic operation still completes through the only available generic thread. This is local test isolation only; the real cluster was never set back to 1 thread. - Fresh local result: `ReportMetricsOperationTest` 3/3 passed, failures/errors/skips 0/0/0. - Independent code review found no P0-P3 issue. Second-cluster load evidence remains: patched 60/min x 20m completed 1200/1200; patched generic=4 60/min x 10m completed 600/600; metrics failure/interrupted 0/0; no failed jobs; slots fully recovered. The cluster was rolled back to the original JAR and generic threads=50 after validation. The final response-boundary change affects only response-delivery failure handling and is covered by the new local red/green test. -- 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]
