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
When Consul is started with upstart, upstart emits a started event once the service is launched, but it takes several seconds before it is ready to serve requests. If you have other services, such as consul-replicate, which depend on Consul, they can thrash before Consul is ready.
A stanza can be added to the Consul upstart config that would delay emitting the event until it is ready, or a similar stanza can be added to the upstart configs of any services that depend on Consul. See http://upstart.ubuntu.com/cookbook/#post-start
I think it would make sense to add it to this cookbook, so that it's handled in one place, and also because it signals that Consul is truly ready.
Thoughts?
The text was updated successfully, but these errors were encountered:
When Consul is started with upstart, upstart emits a
started
event once the service is launched, but it takes several seconds before it is ready to serve requests. If you have other services, such as consul-replicate, which depend on Consul, they can thrash before Consul is ready.A stanza can be added to the Consul upstart config that would delay emitting the event until it is ready, or a similar stanza can be added to the upstart configs of any services that depend on Consul. See http://upstart.ubuntu.com/cookbook/#post-start
I think it would make sense to add it to this cookbook, so that it's handled in one place, and also because it signals that Consul is truly ready.
Thoughts?
The text was updated successfully, but these errors were encountered: