Story #8036
synchronization should respond to various MN down conditions to avoid syncFailures
0%
Description
Currently, synchronization does heed the Node.status='DOWN' in harvesting, but this is limited, especially when there are long delays between harvest and processing. tDAR uses HTTP 502 / 503 responses (not sure which) to signal that the node is temporarily down, for example. Also, for network segregation events, where a node cannot even be reached, synchronization should halt processing - the member node cannot even be notified of sync failures in these situations.
Thoughts on implementation would be adding Observer pattern to libclient (and/or NodeComms in synchronization) so the task can be tried again at a later time. Also try to read the Retry-After header with 503 responses.
History
#1 Updated by Dave Vieglais over 6 years ago
- Sprint set to Infrastructure backlog
#2 Updated by Rob Nahf over 6 years ago
thoughts include having the CN setting and checking down status for a node when it encounters down or other non-connectivity situations
