[
https://issues.apache.org/jira/browse/FLINK-20574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20574:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
>
> 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)
