Hi, You can increase a timeout, that’s one way to tackle it.
In Flink 1.6.0 there will be possibility to override default Flink’s behaviour regarding handling timeouts: https://issues.apache.org/jira/browse/FLINK-7789 <https://issues.apache.org/jira/browse/FLINK-7789> to handle them, instead of out right failing. Also if you can not wait for the new release, you always could copy AsyncWaitOperator with AsyncFunction into your code base and apply the changes from the above mentioned ticket (https://github.com/apache/flink/pull/6091/files <https://github.com/apache/flink/pull/6091/files>) Piotrek > On 6 Jun 2018, at 10:39, 陈卓 <zhuoch...@yirendai.com> wrote: > > HI > The asynchronous IO of flink 1.4.2 will throw timeout exception when the > timeout setting is one second and the invoke time setting is greater than > twenty seconds. Unfortunately the timeout exception cannot be captured, which > leads to abnormal exit of the process. So my question is how to deal with > this situation to keep the jvm executing. > > the exception info: > <image002.jpg> > > code as follows > <image010.jpg> > > <image011.jpg> > <image012.jpg> > > > <image014.jpg> > > > -- > Thanks > zhuo chen
