Gossip when a service is stopped / unloaded

[christophermaier]

When you shut down a service, whether with hab svc unload or hab svc stop, we need to gossip the fact that the Supervisor is no longer running that service.

We don't do this now, and so the only way for a service to "disappear" from the census is if its Supervisor dies, because we have a bit of a conflation of Supervisor presence and Service presence. If you're running on "disposable infrastructure", this may be less of a problem, but can be very surprising / puzzling / dangerous otherwise.

We should confirm that once you hab svc start a stopped service re-load a previously unloaded service that we still send out the appropriate "service added" rumors.

[jamessewell]

I just got stung by this - I'd been working on the assumption that when I stop a service it will be removed from my templated config files!

Any progress?

[christophermaier]

@jamessewell Not yet, but we hope to get to this soon.

[username-is-already-taken2]

Hi there, I came across this issue today, where my nginx config has stale members in it config. How are people working around this at the moment? what do I have to do to refresh my census data after I unload a svc to reflect the current state of play

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.