Decide how to handle disconnects #310
Description
The current model is AttributeIO update or a scan raises an exception, it stops and does not attempt to reconnect. The process will need to restarted once connection is re-established. This was done to prevent it from creating masses of log output.
What behaviour do we want?
- Just keep sending requests and logging errors
- Add some logic to AttributeIO to only log errors once and keep trying, but more quietly
- Stop the application and let K8s restart until it works
- How do we decide when to stop, when just one update loop stops? When all stop?
- Something else?
Thoughts @coretl, @gilesknap?