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-470) Newly added/Removed ServiceInstance should be passed to ServiceCacheListener#cacheChanged method
Date Thu, 07 Jun 2018 13:56:00 GMT

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

Jordan Zimmerman commented on CURATOR-470:
------------------------------------------

You need to know what instances have changed? The {{ServiceCacheListener}} interface would
need to change or we'd have to add a new type of listener for that. Please provide a PR with
the new functionality so that we can review it.

> Newly added/Removed ServiceInstance should be passed to ServiceCacheListener#cacheChanged
method 
> -------------------------------------------------------------------------------------------------
>
>                 Key: CURATOR-470
>                 URL: https://issues.apache.org/jira/browse/CURATOR-470
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: General, Recipes
>    Affects Versions: 4.0.1
>            Reporter: Jerry Chin
>            Priority: Major
>
> Hey fellows,
> We're using _service discovery_ extension to refactor our raw zookeeper based service
monitor.
> Every time a service instance exits or joins, the monitor must be notified and push
a notification to us, the only thing I found in _service discovery_ package meets the requirement
is {{ServiceCacheListener}} interface, but when the interface is fired, there's no way we
could know which service has changed.
> Please help !
> Thank in advance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message