[CURATOR-146] discovery: registration of wrong/old service instance on RECONNECT

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.6.0
• Component/s: Recipes
• Labels: discovery patch
• Assignee: Unassigned
• Reporter: Kamen Petroff
• Created: 11/Sep/14 13:34
• Updated: 17/May/23 11:23
• Resolved: 17/May/23 11:23

Description

ServiceDiscoveryImpl.registerService() remembers service registrations in a map. However updateService() does not update the map.
This causes a wrong registration in the case of a RECONNECT - e.g. reRegisterServices() called by the ConnectionStateListener registers the old ServiceInstance instead of the updated one.

Issue Links

• is fixed by: CURATOR-164 curator-x-discovery: unregisterService is not guaranteed to remove the service, due to reconnectListener concurrency issue