Graceful restart of icegridnode without failing client lookups possible?
We want to restart several of our icegridnode processes to update both the configuration file (new
IceSSL.Trust* properties) and update to 3.6.4 (see important fixes in changelog). Such a restart is very risky in production because while the process is restarting, client lookups to the registry will most probably not work. Is it possible for the registry to wait until the icegridnode is back up instead of immediately answering lookup requests with a failure (
Ice::NoEndpointException)? Or do you other ideas how to keep Ice calls working while a node is shortly down?