You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/04/02 09:02:00 UTC

[jira] [Closed] (FLINK-16836) Losing leadership does not clear rpc connection in JobManagerLeaderListener

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

Till Rohrmann closed FLINK-16836.
---------------------------------
    Fix Version/s: 1.10.1
                   1.9.3
       Resolution: Fixed

Fixed via

1.10.1: dede2ae753806214aac0c3552a7f2909ea881a51
1.9.3: fa2d98f2d7a8d31d26a82e0017204001bef56d61

> Losing leadership does not clear rpc connection in JobManagerLeaderListener
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-16836
>                 URL: https://issues.apache.org/jira/browse/FLINK-16836
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.11.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.3, 1.10.1, 1.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When losing the leadership the {{JobManagerLeaderListener}} closes the current {{rpcConnection}} but does not clear the field. This can lead to a failure of {{JobManagerLeaderListener#reconnect}} if this method is called after the {{JobMaster}} has lost its leadership.
> I propose to clear the field so that {{RegisteredRpcConnection#tryReconnect}} won't be called on a closed rpc connection.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)