curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joelittlejohn <...@git.apache.org>
Subject [GitHub] curator pull request: [CURATOR-275] Allow service instances to be ...
Date Tue, 03 Nov 2015 00:19:57 GMT
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.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message