Tuesday 18th July 2017

Discovery Message routing is recovering

A frozen Docker installation in our Discovery server resulted in timeouts while updating the network topology on our routing components. After the local caches expired, components could no longer determine where to send messages, and eventually treated every message as if it were for a different network. After forcing a restart on our Discovery server, the issue was resolved. Routing components are recovering.