curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From serranom <>
Subject [GitHub] curator pull request: [CURATOR-275] Allow service instances to be ...
Date Wed, 04 Nov 2015 14:59:21 GMT
Github user serranom commented on the pull request:
    Makes sense now.  Thanks.  I do wonder how you would envision this being
    used at the API level.  Changing data just at the ZK level implies internal
    knowledge of the znode layout which doesn't seem to be intended to be
    exposed by the service-discovery framework.
    On Mon, Nov 2, 2015 at 7:20 PM Joe Littlejohn <>
    > There's some more discussion about this on the mailing list
    > <>
    > .
    > The goal here is to allow a single instance to be removed temporarily from
    > discovery by updating only Zookeeper - without having to rely on all
    > clients implementing some method of forcing unregister/reregister. A few
    > users have implemented their own solution to this, but this feels like a
    > very useful core feature that ideally shouldn't require further
    > customization of all clients.
    > Imagine this as similar to taking an instance out of a load balancer (e.g.
    > when troubleshooting some problem affecting one instance). It's very useful
    > for Curator to be able to avoid sending instances to a node without having
    > that node unregister, since it requires no action or implementation from
    > the client.
    > —
    > Reply to this email directly or view it on GitHub
    > <>.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message