[
https://issues.apache.org/jira/browse/FLINK-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329670#comment-14329670
]
ASF GitHub Bot commented on FLINK-1582:
---------------------------------------
Github user mbalassi commented on the pull request:
https://github.com/apache/flink/pull/424#issuecomment-75330500
I was thinking as high as a minute to have as a limit. But after
reconsidering it I am for your argument, trying to establish the connection
every couple of seconds should not be a big overhead, so my whole idea might be
an overkill. Let us have your version for now and generalize it on request.
> SocketStream gets stuck when socket closes
> ------------------------------------------
>
> Key: FLINK-1582
> URL: https://issues.apache.org/jira/browse/FLINK-1582
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 0.8, 0.9
> Reporter: Márton Balassi
> Labels: starter
>
> When the server side of the socket closes the socket stream reader does not
> terminate. When the socket is reinitiated it does not reconnect just gets
> stuck.
> It would be nice to add options for the user have the reader should behave
> when the socket is down: terminate immediately (good for testing and
> examples) or wait a specified time - possibly forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
