You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/26 07:45:00 UTC

[jira] [Updated] (FLINK-10415) RestClient does not react to lost connection

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

ASF GitHub Bot updated FLINK-10415:
-----------------------------------
    Labels: pull-request-available  (was: )

> RestClient does not react to lost connection
> --------------------------------------------
>
>                 Key: FLINK-10415
>                 URL: https://issues.apache.org/jira/browse/FLINK-10415
>             Project: Flink
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 1.6.1, 1.7.0, 1.5.4
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> While working on FLINK-10403, I noticed that Flink's {{RestClient}} does not seem to react to a lost connections in time. When sending a request to the current leader it happened that the leader was killed just after establishing the connection. Then the {{RestClient}} did not fail the connection and was stuck in writing a request or retrieving a response from the lost leader. I'm wondering whether we should introduce a {{ReadTimeoutHandler}} and {{WriteTimeoutHandler}} to handle these problems.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)