You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)?
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.
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
The text was updated successfully, but these errors were encountered: