Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup services when TTL expired #6

Closed
j0hnsmith opened this issue Dec 8, 2015 · 2 comments
Closed

Cleanup services when TTL expired #6

j0hnsmith opened this issue Dec 8, 2015 · 2 comments

Comments

@j0hnsmith
Copy link

Once the TTL for a service has expired, is there any expectation that the service will come back with Triton (scaled down: no, service updated: no, hardware failure: maybe, os update: yes)?

Would it make sense for a cleanup process to exist within this container (once a service has been down say 30 mins or whatever)?

hashicorp/consul#679

@misterbisson
Copy link
Contributor

@j0hnsmith: I think you're right to link to hashicorp/consul#679, as it's definitely a question that affects Consul generally.

My use is typically via http://containerbuddy.io, which will now deregister services when the container is stopped, thanks to TritonDataCenter/containerpilot#22.

@j0hnsmith
Copy link
Author

I am using containerbuddy with that feature but I was using docker kill to see what would happen, the discussion in that pull covers the different stop/kill containerbuddy behaviours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants