You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/10/12 17:25:01 UTC
[jira] [Commented] (BEAM-12685) Allow managed thread count in
AvroIO
[ https://issues.apache.org/jira/browse/BEAM-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427821#comment-17427821 ]
Beam JIRA Bot commented on BEAM-12685:
--------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> Allow managed thread count in AvroIO
> ------------------------------------
>
> Key: BEAM-12685
> URL: https://issues.apache.org/jira/browse/BEAM-12685
> Project: Beam
> Issue Type: Improvement
> Components: io-java-avro, io-java-files
> Reporter: Dylan Hercher
> Priority: P3
> Original Estimate: 2h
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> During execution, the `ReadAllViaFileBasedSource` runs ReShuffle and creates an un-grouped set of file range readers. This can easily cause OOM issues when the number of groups changes as there is no limit to the number of concurrent file reads.
>
> Using Reshuffle.viaRandomKeys.withNumBuckets instead will allow the same default behavior, but lets the user configure the number of readers as and when needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)