You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/12/11 08:38:00 UTC
[jira] [Updated] (FLINK-20574) Throttle number of remote invocation
requests on startup or restores with large backlogs
[ https://issues.apache.org/jira/browse/FLINK-20574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-20574:
-----------------------------------
Labels: pull-request-available (was: )
> Throttle number of remote invocation requests on startup or restores with large backlogs
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-20574
> URL: https://issues.apache.org/jira/browse/FLINK-20574
> Project: Flink
> Issue Type: Improvement
> Components: Stateful Functions
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Major
> Labels: pull-request-available
> Fix For: statefun-2.3.0
>
>
> On startup or restores, the {{RequestReplyFunction}} may heavily load the remote functions with multiple concurrent invocation requests if there is a large backlog of restored or historical events to process through.
> The new protocol introduced by FLINK-20265 emphasizes this much more due to the nature of extra invocation roundtrips if the function has state declarations (i.e., the first hoard of concurrent invocations would all fail with an {{IncompleteInvocationContext}} and requires invocation patching + state registrations).
> We should think about how to apply throttling to mitigate these scenarios.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)