You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "ahmedabu98 (via GitHub)" <gi...@apache.org> on 2024/09/17 21:09:35 UTC
[I] [Feature Request]: Add option to set maximum Storage API streams when using autosharding [beam]
ahmedabu98 opened a new issue, #32490:
URL: https://github.com/apache/beam/issues/32490
### What would you like to happen?
Users can either set a fixed number of streams using `--numStorageWriteApiStreams` or let the runner/sink decide by using autosharding.
The Storage API sink's auto-sharding relies on [GroupIntoBatches.withShardedKey()](https://github.com/apache/beam/blob/85581a3c02facbf20efc5b1d9720dd9cdecbd45e/sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/GroupIntoBatches.java#L272) to determine a number of parallel shards beforehand, then creates one write stream for each shard. Beam's implementation of GroupIntoBatches simply creates one per DoFn instance/thread.
The DataflowRunner overrides GroupIntoBatches to offer a more fine-tuned experience where parallelism is determined using signals such as accumulated backlog. When backlog is huge, the increase in parallelism forces the sink to create many streams and can end up exhausting BigQuery's CreateWriteStream [quota](https://cloud.google.com/bigquery/quotas#write-api-limits).
To handle this better, we should allow the user to specify a maximum number of streams:
- Extend a new BigQuery option `--maxNumStorageWriteApiStreams` (only applicable for streaming writes with autosharding)
- Extend a GroupIntoBatches.withShardedKey()**.withMaxNumShards()** function
- This is required for both the local Beam implementation as well as the DataflowRunner override
### 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
- [X] 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
--
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
Re: [I] [Feature Request]: Add option to set maximum Storage API streams when using autosharding [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #32490: [Feature Request]: Add option to set maximum Storage API streams when using autosharding
URL: https://github.com/apache/beam/issues/32490
--
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
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Add option to set maximum Storage API streams when using autosharding [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #32490:
URL: https://github.com/apache/beam/issues/32490#issuecomment-3253538036
This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.
--
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
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Add option to set maximum Storage API streams when using autosharding [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #32490:
URL: https://github.com/apache/beam/issues/32490#issuecomment-3150536584
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.
--
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
For queries about this service, please contact Infrastructure at:
users@infra.apache.org