[
https://issues.apache.org/jira/browse/CURATOR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986353#comment-14986353
]
ASF GitHub Bot commented on CURATOR-275:
----------------------------------------
Github user joelittlejohn commented on the pull request:
https://github.com/apache/curator/pull/116#issuecomment-153201962
There's some [more discussion about this on the mailing
list](http://mail-archives.apache.org/mod_mbox/curator-user/201510.mbox/%3CCABcULGHWQo_u0r6-KMiVQWa0z1Y%2Bt8paH%2BryOKbg6LUJ8HBTtQ%40mail.gmail.com%3E).
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: https://issues.apache.org/jira/browse/CURATOR-275
> 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
(v6.3.4#6332)
