If the client's server becomes unreachable (e.g. routing problem), the client does not notice and does not re-register at a different server. gosa-si-client would notice this because it periodically tried to re-register at its server. However with 1000s of clients this produces unnecessary traffic. Consider a different solution. The underlying problem is not that the client loses its server but that the server cannot reach the client so that commands (e.g. user messages) sent to the client get lost.
One idea to deal with this:
If server A cannot reach its client to transmit a command, ask other servers to forward the request (one after another with success feedback to avoid duplicate messages). Since go-susi accepts messages from all servers this is possible.
From mux2...@gmail.com on February 06, 2014 09:48:20
If the client's server becomes unreachable (e.g. routing problem), the client does not notice and does not re-register at a different server. gosa-si-client would notice this because it periodically tried to re-register at its server. However with 1000s of clients this produces unnecessary traffic. Consider a different solution. The underlying problem is not that the client loses its server but that the server cannot reach the client so that commands (e.g. user messages) sent to the client get lost.
One idea to deal with this:
If server A cannot reach its client to transmit a command, ask other servers to forward the request (one after another with success feedback to avoid duplicate messages). Since go-susi accepts messages from all servers this is possible.
Original issue: http://code.google.com/p/go-susi/issues/detail?id=167