[
https://issues.apache.org/jira/browse/FLINK-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-10415.
---------------------------------
Resolution: Fixed
Fixed via
1.7.0:
559b8f14ea9cc873a64f9c7954951882444693ac
28591f321f90d713b81b4e4428da12cf22109469
08e25db3326ebf9b9acb022dc5644528d44882ae
1.6.2:
91639923e2a8f4dde271b90d3917b1b2e8d6878a
8a046177dbfff63b3a9285885ad70f85c22c99ca
c634277c113b6e96a9031ec87805fc5392461458
1.5.5:
a7b89bbf22162a61b8b540388fb7994c53cd0b00
ea01369801af9d4968c559e2864d97d85414ca78
ce08427e0c5a2f374c361db4476d74faeebf219d
> 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)
