Perfect! Thanks a lot Karthik.
> On Oct 10, 2017, at 10:41 AM, Karthik Deivasigamani <karthi...@gmail.com>
> wrote:
>
> Thanks Kostas.
> Here is the JIRA : https://issues.apache.org/jira/browse/FLINK-7789
> <https://issues.apache.org/jira/browse/FLINK-7789>
>
> ~
> Karthik
>
> On Mon, Oct 9, 2017 at 7:12 PM, Kostas Kloudas <k.klou...@data-artisans.com
> <mailto:k.klou...@data-artisans.com>> wrote:
> Hi Karthik,
>
> Currently there is no way to provide a handler for timed-out requests.
> So the behavior is exactly what you described. A request fails, an exception
> is thrown and
> the job is restarted.
>
> A handler would be a nice addition. If you want, you can open a JIRA about it
> and if would like
> to work on it, feel free to submit a PR.
>
> Thanks,
> Kostas
>
>> On Oct 6, 2017, at 4:57 PM, Karthik Deivasigamani <karthi...@gmail.com
>> <mailto:karthi...@gmail.com>> wrote:
>>
>> Hi,
>> Is there a way to catch the timeouts thrown from async io operator?
>> We use async io API to make some high latency HTTP API calls. Currently when
>> the underlying http connection hangs and fails to timeout in the configured
>> time the async timeout kicks in and throws an exception which causes the job
>> to restart. Is there a way to catch this exception in application code? We
>> are apache flink 1.3.1
>> https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/stream/asyncio.html
>>
>> <https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/stream/asyncio.html>
>> ~
>> Karthik
>
>
