flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 陈梓立 (JIRA) <j...@apache.org>
Subject [jira] [Updated] (FLINK-10319) Too many requestPartitionState would crash JM
Date Wed, 12 Sep 2018 09:08:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

陈梓立 updated FLINK-10319:
    Summary: Too many requestPartitionState would crash JM  (was: Avoid requestPartitionState
from JM but always try retrigger)

> 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