open-nomad/command/agent/consul
Michael Schurter 99d1486f32 Never remove unknown agent services
Fixes #2827

This is a tradeoff. The pro is that you can run separate client and
server agents on the same node and advertise both. The con is that if a
Nomad agent crashes and isn't restarted on that node in the same mode
its entry will not be cleaned up.

That con scenario seems far less likely to occur than the scenario on
the pro side, and even if we do leak an agent entry the checks will be
failing so nothing should attempt to use it.
2017-07-18 13:23:01 -07:00
..
catalog_testing.go Follow _testing.go convention for testing tools 2017-04-19 12:42:47 -07:00
client.go Never remove unknown agent services 2017-07-18 13:23:01 -07:00
int_test.go Client watches for allocation health using task state and Consul checks 2017-07-07 12:10:04 -07:00
script.go Thanks go vet! 2017-04-19 13:05:41 -07:00
script_test.go Thanks go vet! 2017-04-19 13:05:41 -07:00
unit_test.go Never remove unknown agent services 2017-07-18 13:23:01 -07:00