SEZ9 commented on issue #11846: URL: https://github.com/apache/seatunnel/issues/11846#issuecomment-5385645093
Thanks for the detailed analysis with code paths and CI evidence (flakes on #10874, #10958, #10973, #11060, #11382). Confirming this is a valid production-side gap that PR #11641 only masks in tests; keeping this open to track a real fix. Suggested direction: make collectors like JobMetricExports.collect() fail-soft — catch SeaTunnelEngineRetryableException (and readiness races) and return empty samples instead of throwing, so one unready collector cannot fail the entire scrape. Alternatively, have /metrics return 503 Service Unavailable (without a stack trace) until CoordinatorService is wired up. Independent hardening: ExceptionHandlingFilter should not embed full Java stack traces in HTTP response bodies — log them server-side and return a generic error message. This is worth fixing regardless of the readiness race. <!-- streview-comment:472 --> -- 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]
