curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-146) discovery: registration of wrong/old service instance on RECONNECT
Date Sun, 21 Jun 2015 17:04:00 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595127#comment-14595127
] 

Jordan Zimmerman commented on CURATOR-146:
------------------------------------------

Is this still an issue. The OP should respond whether CURATOR-164 has fixed the issue or not.

> discovery: registration of wrong/old service instance on RECONNECT
> ------------------------------------------------------------------
>
>                 Key: CURATOR-146
>                 URL: https://issues.apache.org/jira/browse/CURATOR-146
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.6.0
>            Reporter: Kamen Petroff
>            Priority: Critical
>              Labels: discovery, patch
>         Attachments: curator.patch
>
>   Original Estimate: 1m
>  Remaining Estimate: 1m
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message