curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-275) Allow service instances to be disabled temporarily
Date Mon, 02 Nov 2015 23:15:27 GMT

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

ASF GitHub Bot commented on CURATOR-275:
----------------------------------------

Github user serranom commented on the pull request:

    https://github.com/apache/curator/pull/116#issuecomment-153188362
  
    why not just unregister and then re-register the service?


> 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)

Mime
View raw message