[
https://issues.apache.org/jira/browse/FLINK-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611764#comment-16611764
]
ASF GitHub Bot commented on FLINK-10319:
----------------------------------------
Clarkkkkk commented on issue #6680: [FLINK-10319] [runtime] Avoid
requestPartitionState from JM but alway…
URL: https://github.com/apache/flink/pull/6680#issuecomment-420563206
Hi @TisonKun , I am not sure if it fails the execution too eagerly? I think
the too problem that many RPC requests and block JM can be resolved by add a
single-thread thread pool so that only one request would be issued at the same
time. What do you think?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Avoid requestPartitionState from JM but always try retrigger
> ------------------------------------------------------------
>
> Key: FLINK-10319
> URL: https://issues.apache.org/jira/browse/FLINK-10319
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.7.0
> Reporter: 陈梓立
> Assignee: 陈梓立
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> Do not requestPartitionState from JM on partition request fail, which may
> generate too many RPC requests and block JM.
> We gain little benefit to check what state producer is in, which in the other
> hand crash JM by too many RPC requests. Task could always
> retriggerPartitionRequest from its InputGate, it would be fail if the
> producer has gone and succeed if the producer alive. Anyway, no need to ask
> for JM for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
