[Feature Request]: Reduce FnApi error logs for processing that is cancelled for expected reasons

[scwhittle]

What would you like to happen?

The runner of a portable beam pipeline may start processing a bundle that it later wants to cancel. Possible reasons for this could be:

• hedging
• active work is invalidated due to runner restart/scaling and needs to retry

This cancellation is currently activated by returning an error on a state or data request for the bundle. This ends up cancelling the processing of the bundle but can result in logs as there is no way to distinguish such runner initiated cancellations from real errors.

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[scwhittle]

.take-issue

[scwhittle]

From discussion on beam-dev it sounds like there is agreement that adding a ErrorReason to the state request response instead of just error string would be useful for improving logging and error handling within sdks.

[github-actions]

This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

[github-actions]

This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.

[scwhittle]

I still plan on doing this once I get a chance