Currently mod_tile communicates with renderd via a Unix domain socket. Renderd as the listening side of the socket must create the socket. However if mod_tile starts up before renderd then connecting to the socket will result in an error.
The current error handling for this part of the mod_tile initialisation is to propagate the error up the call stack, which effectively aborts the mod_tile. In real world scenarios the start up order of mod_tile and renderd is not guaranteed, so the error handling needs to be more resilient.
A progressive retry mechanism for connecting to the renderd socket is one way of making the error handling more resilient.
Currently mod_tile communicates with renderd via a Unix domain socket. Renderd as the listening side of the socket must create the socket. However if mod_tile starts up before renderd then connecting to the socket will result in an error.
The current error handling for this part of the mod_tile initialisation is to propagate the error up the call stack, which effectively aborts the mod_tile. In real world scenarios the start up order of mod_tile and renderd is not guaranteed, so the error handling needs to be more resilient.
A progressive retry mechanism for connecting to the renderd socket is one way of making the error handling more resilient.