flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10319) Too many requestPartitionState would crash JM
Date Mon, 17 Sep 2018 03:18:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617035#comment-16617035

ASF GitHub Bot commented on FLINK-10319:

TisonKun commented on issue #6680: [FLINK-10319] [runtime] Too many requestPartitionState
would crash JM
URL: https://github.com/apache/flink/pull/6680#issuecomment-421882434
   cc @StephanEwen @twalthr 

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:

> Too many requestPartitionState would crash JM
> ---------------------------------------------
>                 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

View raw message