scwhittle opened a new issue, #34705: URL: https://github.com/apache/beam/issues/34705
### 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 - [x] 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 - [x] Component: Google Cloud Dataflow Runner -- 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: github-unsubscr...@beam.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
