backends should set a ttl?

[virtuald]

I keep ending up with various invalid keys when rebooting a system, presumably because of an ordering problem on shutdown. However, you could imagine that if a host had a hard shutdown, then the keys associated with containers on the host would never go invalid either.

Currently (at least with etcd backend), registrator does not set a TTL, so the key lives forever and is never removed. A TTL (or some expiration mechanism) should be set on the keys so they expire.

[progrium]

Hmm, yeah I'm thinking of a heartbeat option that will cause values to be
set with a TTL and then registrator handles triggering a heartbeat method
of the registry interface.

On Sat, Jul 26, 2014 at 10:58 PM, Dustin Spicuzza notifications@github.com
wrote:

I keep ending up with various invalid keys when rebooting a system,
presumably because of an ordering problem on shutdown. However, you could
imagine that if a host had a hard shutdown, then the keys associated with
containers on the host would never go invalid either.

Currently (at least with etcd backend), registrator does not set a TTL, so
the key lives forever and is never removed. A TTL (or some expiration
mechanism) should be set on the keys so they expire.

—
Reply to this email directly or view it on GitHub
https://github.com/progrium/registrator/issues/5.

Jeff Lindsay
http://progrium.com

[progrium]

This is lower priority though since the main use case is with Consul services, which includes health checks that would resolve this.