Hi M Singh, Our internal has this scenario too, as far as I know, Flink does not have this internal mechanism in 1.9 too. I can share my solution: - In async function, start a thread factory. - Send the call to thread factory when this call has failed. Do refresh security token too. Actually, deal with anything in function. As long as we finally call the relevant methods of ResultFuture.
Best, Jingsong Lee On Tue, Dec 10, 2019 at 3:25 AM M Singh <mans2si...@yahoo.com> wrote: > Hi Folks: > > I am working on a project where I will be using Flink's async processing > capabilities. The job has to make http request using a token. The token > expires periodically and needs to be refreshed. > > So, I was looking for patterns for handling async call failures and > retries when the token expires. I found this link Re: Backoff strategies > for async IO functions? > <http://mail-archives.apache.org/mod_mbox/flink-user/201903.mbox/%3CCAC27z=pou2chkxxcomu5ty60n6fhlhjxbwcyb2tqkkz3yrb...@mail.gmail.com%3E> > and > it appears that Flink does not support retries and periodically refresh a > security token. I am using 1.6 at the moment but am planning to migrate to > 1.9 soon. > > Re: Backoff strategies for async IO functions? > > > <http://mail-archives.apache.org/mod_mbox/flink-user/201903.mbox/%3CCAC27z=pou2chkxxcomu5ty60n6fhlhjxbwcyb2tqkkz3yrb...@mail.gmail.com%3E> > > > If there are any patterns on how to deal with this scenario, please let me > know. > > Thanks > > Mans > > -- Best, Jingsong Lee
