curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-275) Allow service instances to be disabled temporarily
Date Tue, 03 Nov 2015 00:20:27 GMT


ASF GitHub Bot commented on CURATOR-275:

Github user joelittlejohn commented on the pull request:
    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.

> Allow service instances to be disabled temporarily
> --------------------------------------------------
>                 Key: CURATOR-275
>                 URL:
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Recipes
>            Reporter: Joe Littlejohn
> Allow service instances to be temporarily removed from discovery (when using the Service
Discovery recipe). 
> This can be achieved with a new 'enabled' flag that is included as part of the service
instance node data in Zookeeper. Updating this flag via e.g. Exhibitor will allow an instance
to be disabled. When the flag is omitted, the service is assumed to be enabled, hence this
change is backward compatible.

This message was sent by Atlassian JIRA

View raw message