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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7.1
• Component/s: Recipes
• Assignee: Jordan Zimmerman
• Reporter: Jordan Zimmerman
• Created: 12/Jan/15 21:11
• Updated: 12/Jan/15 21:12
• Resolved: 12/Jan/15 21:12

Description

PR without a Jira: https://github.com/apache/curator/pull/43

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.