lostluck commented on issue #25314: URL: https://github.com/apache/beam/issues/25314#issuecomment-1487756187
Due to the way the container contract operates, the logging on termination has no meaningful threadID, step ID etc. Fatalf was used because the SDK harness should never be exiting normally. It'd be up to the runner to manager the logging service to elide any noise from a normally terminating job (eg. due to successful completion, or due to repeated bundle failures). Basically, the "thread, step etc" ids aren't useful in debugging since it's noting that a separate process crashed, and it's not intended to try and recover at this level. It needs to log the failure, and exit out. It would have a meaningful worker ID however which could lead to debugging WRT profiling and similar (at least on the Dataflow UI). -- 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]
