[
https://issues.apache.org/jira/browse/BEAM-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549098#comment-17549098
]
Danny McCormick commented on BEAM-11547:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/20706
> Nexmark ratelimiting mode doesn't work
> --------------------------------------
>
> Key: BEAM-11547
> URL: https://issues.apache.org/jira/browse/BEAM-11547
> Project: Beam
> Issue Type: Bug
> Components: testing-nexmark
> Affects Versions: 2.24.0, 2.25.0, 2.26.0
> Reporter: Teodor Spæren
> Priority: P3
> Labels: nexmark
>
> When using the {{--isRateLimited}} option for Nexmark, the system is supposed
> to hold events back until they are supposed to be sent, in accordance to the
> event generations rule.
> What happens today is that the events are pushed into the backlog, but are
> never actually replayed. This leads to only a few events being sent.
> When I tested this with the direct runner and flink I saw that the generator
> got resumed all the time, and when it gets resumed the backlog is not
> restored. I hacked together a solution for this locally, but even with the
> queue collected, most events still lack. From my tests only 1/10 make it
> through.
> I don't really know the nexmark code well enough to benchmark anymore beyond
> this.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
