Hi All,
When employing the ServiceDiscoveryManager and unicast discovery to
build a LookupCache of ServiceRegistrars, I've noticed that it takes
~30 minutes for registered ServiceDiscoverListeners to receive the
serviceRemoved event when a registrar goes away. When using multicast
discovery, the event is triggered almost immediately. Note that when
the ServiceRegistrar goes away on a given host, it is restarted, but
registered with a new ServiceID.
I believe that this discrepancy is due to the nature of unicast v.
multicast discovery, but I'm guessing that there is a configuration
property somewhere that I can use to decrease some Lease duration and
minimize the wait time.
Currently we are using the default configurations for our (transient)
ServiceRegistrars and our ServiceDiscoveryManager.
Thanks in advance,
Geoff.
