Closed terryherron closed 5 years ago
so, it's on a scheduled executor right now, how different is that than retry? Not saying retry is a bad option.
The difference, if not mistaken, is that if publish event fails there is no retry. Next time the scheduled index check happens it has not changed so things remain in a bad state. I believe adding retry logic in this section will allow things to heal in case of a 404 or connection refused. Next week at some point I'll try to reproduce the issue in a testcase. Perhaps I'm mistaken here. Thanks.
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
Can retries increase the resilience of ConfigWatch? Specifically to retry on any random network failures. If this exception below is thrown and no other KV change occurs, the original KVs from the one event never get applied. In many cases, a retry attempt would help app instances achieve the desired state.
Thanks all, Terry