> hmm..... and is there no workaround for this, for this situation? I > mean, if the server dies isn't there any possibility that > the sender/client realizes this. If the timeout it's too large this > can be cumbersome. > > I tried reducing the timeout and indeed the client realizes faster > when the server exits but another problem arises: Without exiting the > server, > on the client side I get the error (retry exceed) when polling for a > recently posted send - this after some hours.
There's a tradeoff between detecting real failures faster, and reducing false errors detected because a response came too slowly. Clearly if a response may take an amount of time 'X' to be received under normal conditions, there's no way to conclude that the remote side has failed without waiting at least 'X'. - R. _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
