Hi Frank, which version of Flink are you using? There was a problem with correctly recognizing failed asynchronous operations, see FLINK-6435 [1].
In general, if an exception occurs within AsyncFunction#asyncInvoke, then the job should fail. Depending on which restart strategy you have chosen, the job is retried or not. What Flink should not do is to retry for the unordered case and not retry for the ordered case. Maybe you could share the exact code you’re running in order to see whether you meant exception occurring within AsyncFunction#asyncInvoke or within a future which completes AsyncCollector. [1] https://issues.apache.org/jira/browse/FLINK-6435 Cheers, Till On Mon, May 22, 2017 at 9:36 PM, Frank Xue <frank....@bettercloud.com> wrote: > Hi, > > I have a question related to async io for Flink. I found that when running > unordered (AsyncDataStream.unorderedWait) failures within each individual > asyncInvoke is added back to be retried, but when I run it ordered > (AsyncDataStream.orderedWait) and an exception is thrown within > asyncInvoke, it just stops the whole process. Is this expected behavior? > > Thanks, > Frank > > -- > *Frank Xue* | Software Engineer | w. > 3405 Piedmont Rd. NE, Suite 325, Atlanta, GA 30305 > > <https://www.bettercloud.com?utm_source=bettercloud_email&utm_medium=email_signature&utm_campaign=unified_saas_management/> > *The First Multi-SaaS Management Platform > <https://www.bettercloud.com/whybettercloud?utm_source=bettercloud_email&utm_medium=email_signature&utm_campaign=video>* >
