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? 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? | | | If there are any patterns on how to deal with this scenario, please let me know. Thanks Mans
