Abacn commented on PR #25945: URL: https://github.com/apache/beam/pull/25945#issuecomment-1496430695
Generally, the backOff retry intermittent error (that a retry in place can success). If your concern is the persistent error (a dead connection) it should be handled by runner. That is, when the exception is popping up, the runner will create a new work item, which includes initializing a new DoFn instance, to retry the bundle. Handling all errors within DoFn, theoretically, it works, but not encouraged because it adds complexity to the implementation. If republish need more test, can we aim to fix the original issue (high port occupacy) that was a regression in 2.46.0 at the moment? -- 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]
