You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Stas Levin (JIRA)" <ji...@apache.org> on 2017/04/25 09:28:04 UTC

[jira] [Created] (BEAM-2074) SourceDStream's rate control mechanism may not work

Stas Levin created BEAM-2074:
--------------------------------

             Summary: SourceDStream's rate control mechanism may not work
                 Key: BEAM-2074
                 URL: https://issues.apache.org/jira/browse/BEAM-2074
             Project: Beam
          Issue Type: Bug
          Components: runner-spark
            Reporter: Stas Levin
            Assignee: Stas Levin


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 reading.

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
(v6.3.15#6346)