how does hm9000 actually determine application health?


Eric Poelke
 

Can anyone tell me or point me to some documentation about how hm9k actually determines application health?


Rob Dimsdale
 

You can find the source (with documentation) at:

https://github.com/cloudfoundry/hm9000

Is there a particular issue you are trying to resolve? Feel free to post logs (with sensitive info redacted).


Aleksey Zalesov
 

Short answer is app is healthy when it listens to $PORT. I think this check is done by DEA, though.

HM9000 listens to NATs for actual state and polls CC to grab desired state. Than it compares both states and issues start/stop commands through the NATs.

Alex Zalesov


Alexander Lomov <alexander.lomov@...>
 

On Oct 24, 2015, at 1:41 AM, Eric Poelke <epoelke(a)gmail.com<mailto:epoelke(a)gmail.com>> wrote:

Can anyone tell me or point me to some documentation about how hm9k actually determines application health?


Eric Poelke
 

Thanks guys. So I thought that I had come across the bit of its healthy if its listening on $PORT, but that got me thinking about the small worker process I just deployed. Since it does not listen on a port is it just assumed to be "ok"?


Jesse T. Alford
 

If the app doesn't have a bound route, it's not health checked on DEAs. If
it fails without actually exiting, the system won't notice.

(On Diego, the health check has to be explicitly disabled.)

On Tue, Oct 27, 2015, 8:12 AM Eric Poelke <epoelke(a)gmail.com> wrote:

Thanks guys. So I thought that I had come across the bit of its healthy
if its listening on $PORT, but that got me thinking about the small worker
process I just deployed. Since it does not listen on a port is it just
assumed to be "ok"?