[
https://issues.apache.org/jira/browse/BEAM-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295437#comment-17295437
]
Beam JIRA Bot commented on BEAM-11547:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: nexmark, stale-P2
>
> 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.3.4#803005)
