beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stas Levin (JIRA)" <>
Subject [jira] [Resolved] (BEAM-2074) SourceDStream's rate control mechanism may not work
Date Mon, 01 May 2017 13:31:04 GMT


Stas Levin resolved BEAM-2074.
       Resolution: Fixed
    Fix Version/s: First stable release

> SourceDStream's rate control mechanism may not work
> ---------------------------------------------------
>                 Key: BEAM-2074
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Stas Levin
>            Assignee: Stas Levin
>             Fix For: First stable release
> If the {{boundMaxRecords}} for {{SourceDStream}} is not set (as a result of users choosing
not to specify {{SparkPipelineOptions.setMaxRecordsPerBatch()}}), {{SourceDStream}} is designed
to use {{rateControlledMaxRecords()}} to determine the max number of records it should be
> However, at the moment {{SourceDStream}} only consults  {{rateControlledMaxRecords()}}
once, when it is created, thus following
> instantiations of {{MicrobatchSource}} will be using the now-set-in-stone {{boundMaxRecords}}
value without consulting with {{rateControlledMaxRecords()}}, making the rate controlling
mechanism sub-optimal.

This message was sent by Atlassian JIRA

View raw message