[GitHub] [beam] Polber opened a new issue, #25648: [Feature Request]: FileIO should limit writes to GCS when throttling is detected.

["Polber (via GitHub)" <gi...@apache.org>]

Polber opened a new issue, #25648:
URL: https://github.com/apache/beam/issues/25648

   ### What would you like to happen?
   
   GCS has 1000 write per second and 5000 read per second capacity which can be exceeded during certain operations such as `writeDynamic()`. The sink should be responsible for backing off write requests that exceed the capacity when a runner decides to try and ramp up operations for optimization purposes.
   
   ### 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
   - [X] Component: IO connector
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] 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-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org